Related
[Q&A] [GT-I9001][ROM][ION][4.4.4][KTU84Q] CyanogenMod 11.0 by ADC-Team - Release 13
Q&A for [GT-I9001][ROM][ION][4.4.4][KTU84Q] CyanogenMod 11.0 by ADC-Team - Release 13 [EOL]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [GT-I9001][ROM][ION][4.4.4][KTU84Q] CyanogenMod 11.0 by ADC-Team - Release 13 [EOL]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
I too had some problem with last R13 update:
- Contacts in SIM are no longer seen, so they can't be transferred to phone,
- Found WI-FI and mobile network turned off, may airplane mode have been set on by itself?
Now went back to R11
Brightness issue
Hello, loving the ROM so far!
Only thing I dont know how to solve is max brightness after I reboot the phone (I have set mine to minimum).
It gets back to minimum after the screen turns off or after I manually set it off.
I tried factory reset, didnt help.
Thanks for the help!
upgrade new rom
Hi,
last week i installed this version
20140910 Release 12 on my samsung galaxy s plus
followed all steps from the openings post of this thread:
http://forum.xda-developers.com/showthread.php?t=2579431
I used CWM.
My question is with steps should i take if i want to upgrade to
20141011 Release 13 [EOL]?
Thanks a lot
First you have to update TWRP to 2.8.0.0. from there you can flash R13 and reboot.
Gesendet von meinem Nexus 5 mit Tapatalk 2
Installing CM11 rel11, serial disappeared - best way to restore?
Hi folks!
I've upgraded the stock firmware to CM11 rel11 from this thread on a i9001. Now it is on EOL rel13.
By the initial upgrade I assume the serial number turned unknown, so now I am only able to make emergency calls. Until now it didn't make me upset at all, however recently my priorities have changed. (In a nutshell: VOIP telephony was kicking in, thus it would be handy to turn my GPS device a 3G and callback capable... well... phone.)
Before the upgrade operation I followed the recommendation and created a backup of /efs and /persist. Not surprisingly the backed up and current images of these partitions do differ on some bits. However at this point I became a bit confused, and teh internetz didn't answer (yet?) my questions:
- Shall I simply dd the original images back, reboot, and problem is solved? Or doing so I will brick my precious device (being even unable to restore the current state of these partitions) thus lose even navigation?
- Is there any better restore tool around that supports i9001?
- Am I totally off track, and should make some other magic? (Like using some 2013 patch that kicks out S/N check, etc.)
Thank you in advance!
Project dead?
I have tried to download R13 files. All downloads hosted by devhost failed because the files seem to be unavailable. Tested with Chrome and Dolphin on i9300 and i9001.
Can you or someone who has already downloaded the files please provide an additional mirror?
And why is R13 EOL if there is no clue of a newer Version? Have you stopped the development completely or are you preparing for Lollipop?
I have the same problem as PsychoGame
"Hello ADC-Team,
First of all thank you for all your hard work on this device, it's much appreciated.
Second I want to report a small bug which I've encountered and am unable to get past. I followed the next steps in flashing:
I flashed TWRP 2.8.0.0 on my Samsung Galaxy S Plus.
Rebooted into TWRP 2.8.0.0
Completely wiped the device (Cache, Dalvik Cache, Android Secure, SD-card, System & Data)
After full wipe installed the cm-11.0-20141011-ION-dev_connection_team-release13-ariesve.zip
After flashing CM11 installed GAPPS package
Cleared Cache and Dalvik Cache once more
Rebooted and set-up device
After the device has been set-up I'm unable to use the contacts app for some reason.
I've tried clearing Cache/Dalvik Cache and Fix Permission but this error still persists
Reflashed the CM11 package again but still no luck, the error still persists.
Does anyone have a suggestion, or is anyone also facing this same problem?
Greetings PsychoGame "
I'm unable to open my contacts, i din't have the problem with release 12. Is there a know solution?
Yes I share the same problem, as said in post 21 oct 2014 at 07:30 PM.
I can't use the contacts because they can't be read in the SIM and can't be exported to the thelepone memory.
Tried with wiping, cleaning, etc., but I had to step back to a previous release (R11) very well working.
Looking at the lenght of the files I could see that R11 is 210.888 KB, R12 is 211.708, and R13 is decreased to 189.921.
Something lost
deduud1 said:
I have the same problem as PsychoGame
"Hello ADC-Team,
First of all thank you for all your hard work on this device, it's much appreciated.
Second I want to report a small bug which I've encountered and am unable to get past. I followed the next steps in flashing:
I flashed TWRP 2.8.0.0 on my Samsung Galaxy S Plus.
Rebooted into TWRP 2.8.0.0
Completely wiped the device (Cache, Dalvik Cache, Android Secure, SD-card, System & Data)
After full wipe installed the cm-11.0-20141011-ION-dev_connection_team-release13-ariesve.zip
After flashing CM11 installed GAPPS package
Cleared Cache and Dalvik Cache once more
Rebooted and set-up device
After the device has been set-up I'm unable to use the contacts app for some reason.
I've tried clearing Cache/Dalvik Cache and Fix Permission but this error still persists
Reflashed the CM11 package again but still no luck, the error still persists.
Does anyone have a suggestion, or is anyone also facing this same problem?
Greetings PsychoGame "
I'm unable to open my contacts, i din't have the problem with release 12. Is there a know solution?
Click to expand...
Click to collapse
I don't share this. The contacts are properly downloaded from Google and I can access them normally. I can also add contacts and save them!
Edit: were did you save your contacts? If you've saved them on your sim card, I'd suggest an app called 'sim contacts'. I found out I had some very old contacts stored on the sim card! I almost forgot this possibility...
smitharro said:
I don't share this. The contacts are properly downloaded from Google and I can access them normally. I can also add contacts and save them!
Edit: were did you save your contacts? If you've saved them on your sim card, I'd suggest an app called 'sim contacts'. I found out I had some very old contacts stored on the sim card! I almost forgot this possibility...
Click to expand...
Click to collapse
I reinstalled the rom and gabs again in my pc at home and the problem is gone. I have another question I like the english language on my phone because if there is a problem and a solution it is mostly written in english. I live in the Netherlands, i tried language english us but that gave problems with reception. My provider signal (t mobile) disconected sometimes ramdomly. My solution was select english united kingdom instead of Dutch and Nederland. My question about that solution is: Is it possible that i have slighter worse reception than if i select country Netherlands and language dutch of shouldn't that change make any difrent i means of reception signal strenght?
Thanks for the fast response smitharro
deduud1 said:
I reinstalled the rom and gabs again in my pc at home and the problem is gone. I have another question I like the english language on my phone because if there is a problem and a solution it is mostly written in english. I live in the Netherlands, i tried language english us but that gave problems with reception. My provider signal (t mobile) disconected sometimes ramdomly. My solution was select english united kingdom instead of Dutch and Nederland. My question about that solution is: Is it possible that i have slighter worse reception than if i select country Netherlands and language dutch of shouldn't that change make any difrent i means of reception signal strenght?
Thanks for the fast response smitharro
Click to expand...
Click to collapse
I don't think the language settings of your interferes with the signal of your provider. I always use English with Kpn..
Hello folks,
I still am having problems with contacts from SIM.
To make short a long story:
-1-I have my contacts (216) in SIM.
-2-I must have them in SIM because sometimes I have to put SIM in other phones neither Android nor Google.
-3-That means I do not save my contacts in Google Cloud.
-4-CM11 doesn't use SIM directly (R/W), so I used to select all contacts in SIM and transfer to Phone Memory (not in Google Cloud).
-5-I could do that until R11 and R12.
-6-(Note_1 : before an update I perform a total wipe and a factory reset)
-7-Now I installed R13 with the same procedure: factory reset and instal ZIP
-8-The transfer of contacts is not possible because contacts in SIM are no longer visible,
-9-If I install R12, copy contacts to phone, then install R13 on it without erasing nothing (cache, dalvik, reset) then i can see contacts previously transferred under R12.
Note (tried as suggested by smitharro) "sim contacts" from market. It Reads and Writes contacts on SIM, but cannot transfer to Phone, I get this message "operation failure. try again".
My question is: how can I transfer contacts from SIM to phone under R13 as per step -7- and not pass via step -9-?
I may make something wrong, but do not understand what.
Help please
Many Thanks
callegan said:
Hello folks,
I still am having problems with contacts from SIM.
To make short a long story:
-1-I have my contacts (216) in SIM.
-2-I must have them in SIM because sometimes I have to put SIM in other phones neither Android nor Google.
-3-That means I do not save my contacts in Google Cloud.
-4-CM11 doesn't use SIM directly (R/W), so I used to select all contacts in SIM and transfer to Phone Memory (not in Google Cloud).
-5-I could do that until R11 and R12.
-6-(Note_1 : before an update I perform a total wipe and a factory reset)
-7-Now I installed R13 with the same procedure: factory reset and instal ZIP
-8-The transfer of contacts is not possible because contacts in SIM are no longer visible,
-9-If I install R12, copy contacts to phone, then install R13 on it without erasing nothing (cache, dalvik, reset) then i can see contacts previously transferred under R12.
Note (tried as suggested by smitharro) "sim contacts" from market. It Reads and Writes contacts on SIM, but cannot transfer to Phone, I get this message "operation failure. try again".
My question is: how can I transfer contacts from SIM to phone under R13 as per step -7- and not pass via step -9-?
I may make something wrong, but do not understand what.
Help please
Many Thanks
Click to expand...
Click to collapse
I tried to copy one of my old contacts from the Sim to the phone with 'Sim contacts'. It works perfect! The contact is visible in in 'contacts' after this operation! It isn't visible when it's only on the Sim card however... Sorry but I'm afraid I can't give you a solution for this, other than just use Android phones...
Hello people,
Thanks smitharro for the test you did with "sim contacts" with R13.
It doesn't work with me; if I try to copy with "sim contacts" (by Needom Studio), it gives me the message "Operation Failure" and stops.
BUT
Then I tried with "sim manager" (by Robotobia) and all was perfect: I could copy from Sim to Phone and from Phone to Sim.
(Info: my sim operator is WIND, memory capacity 64 KB)
I hope this could be useful for other people that might have same problems.
Hello
callegan said:
Hello people,
Thanks smitharro for the test you did with "sim contacts" with R13.
It doesn't work with me; if I try to copy with "sim contacts" (by Needom Studio), it gives me the message "Operation Failure" and stops.
BUT
Then I tried with "sim manager" (by Robotobia) and all was perfect: I could copy from Sim to Phone and from Phone to Sim.
(Info: my sim operator is WIND, memory capacity 64 KB)
I hope this could be useful for other people that might have same problems.
Hello
Click to expand...
Click to collapse
Glad it finally worked out for you! I used the Needom Studio app. That one worked fine for me. Don't know why it didn't work for you. Most important: your problem is (somewhat) solved, although it's just a workaround. The Rom still doesn't read the sim-contacts 'by itself'. For me, personally, that's not an issue. Hope the rom will be made 'perfect' before it reaches it's real EOL... On the other hand, nothing in life is absolutely perfect! remember: this rom is brought to us absolutely with no charge by people who volunteer to do this development, just because they like doing this.
Still confused
Hi again
I'm still confused, whether it is safe to dd my saved partitions back to restore my serial number. (Still not 100% sure if these partitions are bound to a particular firmware revision, e.g. only usable as a source to harverst my serial from, not to restore anything; and neither 100% sure if dd is the best tool to rewrite them.)
Having no - even a short - answer means I am asking something pretty obvious? By my opinion if it were obvious, google had answered it already - but it didn't.
Any answers appreciated.
chronosynclastic said:
Hi folks!
I've upgraded the stock firmware to CM11 rel11 from this thread on a i9001. Now it is on EOL rel13.
By the initial upgrade I assume the serial number turned unknown, so now I am only able to make emergency calls. Until now it didn't make me upset at all, however recently my priorities have changed. (In a nutshell: VOIP telephony was kicking in, thus it would be handy to turn my GPS device a 3G and callback capable... well... phone.)
Before the upgrade operation I followed the recommendation and created a backup of /efs and /persist. Not surprisingly the backed up and current images of these partitions do differ on some bits. However at this point I became a bit confused, and teh internetz didn't answer (yet?) my questions:
- Shall I simply dd the original images back, reboot, and problem is solved? Or doing so I will brick my precious device (being even unable to restore the current state of these partitions) thus lose even navigation?
- Is there any better restore tool around that supports i9001?
- Am I totally off track, and should make some other magic? (Like using some 2013 patch that kicks out S/N check, etc.)
Thank you in advance!
Click to expand...
Click to collapse
chronosynclastic said:
Hi again
I'm still confused, whether it is safe to dd my saved partitions back to restore my serial number. (Still not 100% sure if these partitions are bound to a particular firmware revision, e.g. only usable as a source to harverst my serial from, not to restore anything; and neither 100% sure if dd is the best tool to rewrite them.)
Having no - even a short - answer means I am asking something pretty obvious? By my opinion if it were obvious, google had answered it already - but it didn't.
Any answers appreciated.
Click to expand...
Click to collapse
First of all, your question is not fully clear to me. What doe you mean by serial number? You're IMEI number? If you've lost that, your phone is nothing more than a small tablet. This is a unique number to identify your phone on the provider's network. So you'll have to restore the backup!
The serial number in my phone however is 'unknown' in the rom. But the rom works fine! There's no need to have that for the use of this phone. I don't know where it was stored in the original rom, but be very careful with messing with the 'EFS' partition!
Thank you for your reply!
My IMEI number remained well, however I learned that both IMEI and serial (S/N) is needed to have a phone (e.g. to connect to carrier) instead of having a tablet.
For example here is said: "IMEI is showing now but still no calls and sms. I also noticed that the serial number is not the same as the one written at the back of the phone. I have read that restoring EFS solves this problem".
There is also some magic ("azira patch") to S3 that states the same. It operates by bypassing serial check, but since it is old (2013) and originally for S3, I'd rather stuck restoring my /efs partition.
Backing up /efs is written down everywhere. Restoring it... well. Mostly external tools are mentioned, that don't support i9001.
Even further, suppose restoring /efs and /persist is the solution for my problem, I think I know how to do that. At least by dd. What I don't know is that the structure of these partitions is fix or may change between Android versions. And of course: if I rewrite them to original, will my device boot again?
Considering these, any idea if I'm off track, or not?
smitharro said:
First of all, your question is not fully clear to me. What doe you mean by serial number? You're IMEI number? If you've lost that, your phone is nothing more than a small tablet. This is a unique number to identify your phone on the provider's network. So you'll have to restore the backup!
The serial number in my phone however is 'unknown' in the rom. But the rom works fine! There's no need to have that for the use of this phone. I don't know where it was stored in the original rom, but be very careful with messing with the 'EFS' partition!
Click to expand...
Click to collapse
I never touched my /efs partition nor will I ever! My phone is running fine without the serial number displaying in the rom! I can make phone calls, send text messages and I have mobile data! So you really don't have to restore the serial number. Possibly it's still there and still used by the provider, but is the settings app simply not reading it... Sorry I can't help you more. I'm not a developer, just a user...
I got trwp and my cellphone rooted before i installed Lollipop, as you know ia had to find someone that upload a backup version done from trwp, well the thing is a found it and intalled too, the guy who uploaded made the backup to work with the dual sim version, even if he did that to the rom, everything works very good on my cellphone, the only thing that is not working anymore are the messages, hang out or google messenger, none of those work when i try to send a sms or mms says this: A red triangle with sim-1, and nothing more, could you tell me why the hell is this happning to my moto xt1063? could you help me some how?
chere said:
I got trwp and my cellphone rooted before i installed Lollipop, as you know ia had to find someone that upload a backup version done from trwp, well the thing is a found it and intalled too, the guy who uploaded made the backup to work with the dual sim version, even if he did that to the rom, everything works very good on my cellphone, the only thing that is not working anymore are the messages, hang out or google messenger, none of those work when i try to send a sms or mms says this: A red triangle with sim-1, and nothing more, could you tell me why the hell is this happning to my moto xt1063? could you help me some how?
Click to expand...
Click to collapse
Try to fix the APN networks... go to conextion > More > Mobil Networks > points of access > Restore predt. values
well i got a new problem here.
so basically, i can't write any SMS. That problem occured after I installed the SLiM-rom. Now I can't write any SMS anymore (using the Stock Messaging App). It always tells me that "could not send" error... I've tried google messaging, didn't work either. But calling does work for some reason.
anyone knowing how to solve that problem?
#edit: I just tried entering an USSD code, it tells me that i no connection or invalid mmi code.
I ran into that problem as well after going through a few roms. I think the issues is not doing a full wipe/erasing user data before flashing. That should fix it.
Nurmi_CEO said:
I ran into that problem as well after going through a few roms. I think the issues is not doing a full wipe/erasing user data before flashing. That should fix it.
Click to expand...
Click to collapse
Isn't there any other way to solve that problem? If anyone needs the logcat to spot the problem (and there are some errors, I just don't know what they mean), I can give it to you.
Hey!
I had the same error, also with SLiM Rom. Sadly, I can only confirm, what Nurmi already said, after a full wipe of data I was able to send SMS again. Trying to restore my data partition which i backuped via TWRP before i started troubleshooting, led to loss of SMS function again. Some people said, the problem could be PRFC 1.0 and lower. However, if you don't want to do a full wipe, try messaging app signal. It can also be used to send SMS and worked in my case, whereas stock messaging ap as well as hangouts didn't. Only problem here ist, that in Ultra stamina you can't send SMS either, because you can only use stock apps.
Hope I could help you.
Cheers!
fab_ben said:
Hey!
I had the same error, also with SLiM Rom. Sadly, I can only confirm, what Nurmi already said, after a full wipe of data I was able to send SMS again. Trying to restore my data partition which i backuped via TWRP before i started troubleshooting, led to loss of SMS function again. Some people said, the problem could be PRFC 1.0 and lower. However, if you don't want to do a full wipe, try messaging app signal. It can also be used to send SMS and worked in my case, whereas stock messaging ap as well as hangouts didn't. Only problem here ist, that in Ultra stamina you can't send SMS either, because you can only use stock apps.
Hope I could help you.
Cheers!
Click to expand...
Click to collapse
So basically, I have to reflash the ROM fully with Wipe Data + Cache + Dalvik?
Kinda sucks, hopefully this problem gets sorted out somehow
As I said, you could try Signal for SMS messaging, but you still won't be able to send SMS in ultra stamina
Edit: also, I can neither confirm, nor deny that the problem is caused by Slim ROM itself
I faced this issue as well, but i did not use any custom roms. I have a UK Z3C and i had flashed the latest US rom. I was able to fix the issue by downloading the UK rom and flashing it again. It could be the US rom on a UK phone problem. I downloaded the ftf using xperifirm from flashtool and flashed them.
I faced this problem with prerooted CE1. I have no solution for now
First install any other messaging app from play store then make it default messaging app. After that open Sony messaging again and make Sony default messaging app again. This should solve the problem.
Sent from my D5803 using XDA Free mobile app
Pedimento said:
First install any other messaging app from play store then make it default messaging app. After that open Sony messaging again and make Sony default messaging app again. This should solve the problem.
Sent from my D5803 using XDA Free mobile app
Click to expand...
Click to collapse
10x
Will try
Pedimento said:
First install any other messaging app from play store then make it default messaging app. After that open Sony messaging again and make Sony default messaging app again. This should solve the problem.
Sent from my D5803 using XDA Free mobile app
Click to expand...
Click to collapse
I had installed google messaging and one more sms app but they dont work too
If I do a factory reset will I lost the root and recovery?!?!
One more try using clear data and cache of Sony messaging first. I solved this problem in this way.
Sent from my D5803 using XDA Free mobile app
Pedimento said:
One more try using clear data and cache of Sony messaging first. I solved this problem in this way.
Sent from my D5803 using XDA Free mobile app
Click to expand...
Click to collapse
I did but still get error "Could not send"
The problem was solved with factory reset.
No root and recovery lost
pepitoff said:
The problem was solved with factory reset.
No root and recovery lost
Click to expand...
Click to collapse
I do it the same . factory reset on .264 i dont lose my root. I restore all apps and data by titanium backup and sms working now . I change firmware many times from 4.4 and newer meet this problem before it was first time.
Still can't send sms
I hope someone can help, I updated from 4.4 to 5.1.1. Now I can't send sms, I can receive sms and mms and make and receive phone calls as well use the internet.
I've flashed back to 4.4, factory reset (wiped), pc companion phone repaired, reset phone again and updated to 5.1.1 again, tried textra, signal, hangouts and stock app. But I can't send a text. I've read about rooting and using other programs but I think it is a bit beyond my scope. Any other suggestions would be much appreciated. , it's not the sim , I've tried it in another phone and it works fine too.
Edit: I have a D5833 on telechoice in Australia.
Working out out slowly
Ok, so I got a hold of another phone today, it appears my provider (Telechoice,Australia ) may be at fault. I put a different sim card in my phone and it all worked as advertised, put my sim card in another phone and I get the same issues. Worst part is, is that this is the 2nd sim card now..
So what might cause 2 sim cards to fail with the exact same issues??
Hello Everyone...
Posting here first rather than in the "Update Failure" thread because I'm not so sure I have a "failure" with the update....just an issue after the udpate.
I have 2 cloned HTC M9 phones. I say "cloned" as they are exactly the same make, model, ROM, etc (one business, one personal phone). They have the following information if needed:
Sprint HTC M9
SuperSU Free v2.65
Custom ROM ViperOneM9 3.5.0 with no custom kernal
Android 5.1
HTC Sense 7.0
Kernal (standard) 3.10.49-perf-g26c593c
[email protected] #1
SMP PREEMPT
I updated some apps this as I normally do through Google Play. A little while afterward I was prompted to update the SU Binary. I did so on one of my phones. I hit the TWRP option (on the right side of the prompt screen), nothing happened, phone did not reset so I rebooted into recovery. The update ran automatically and the phone rebooted.
I noticed two issues (perhaps there are more). The huge problem is that I cannot make OUTGOING calls. I use a custom dialer PixelPhone Pro. I click on a contact to dial and nothing happens. I type in number to dial, hit the green "send" button to make the call, nothing happens.
I also tried the stock Phone app....same thing, cannot dial out.
I attempted to update the Profile and PRL for the phone, however, as that appears to need to make a "special call" that function is not working either
The other problem I noticed is with an app I have called Quick Settings. The app is always accessible through the pull-down notifications on the phone. Although the app is still installed and functional, it no longer appears in the pull-down notifications. I tried to reset the option to show it there (turning the option off and back on) and it will not show up despite the proper setting chosen.
I still have full root access as I tried a couple root apps (such as Titanium Pro) and have full root access.
I have been prompted on my other phone to update the SU Binary and I am concerned with doing so. Any idea why this is happening and how I can troubleshoot and fit my outgoing call issue??
THANK YOU all very much!!
Scott
Hey guys....
Anyone else have this issue or similar?? So what are my options....how do I get my phone back to being able to make calls??
Thank you for your help....
Scott
Scudderb said:
Hey guys....
Anyone else have this issue or similar?? So what are my options....how do I get my phone back to being able to make calls??
Thank you for your help....
Scott
Click to expand...
Click to collapse
**UPDATE**
Still problems....
Right after I first updated the binary the "only" problem was that I could not make calls which I could use the other functions of the phone. I rebooted the phone and I cannot reach any function of the phone because I constantly get the message "...the process com.android.phone has stopped" obviously related to the previous problems.
I dirty-flashed the ROM...that did no help. I even tried to flash an older SuperSU version (I don't know what that would have done....I'm running on HOPE now ) and that didn't help. Re-dirty-flashed the ROM a second time. Again that didn't help.
I flashed an old backup and THAT WORKED fine. Problem is that the backup is 6 months old. I could quit and totally clean/wipe/install the ROM and start again from scratch but I reeeeeeallly don't have time for that at the moment.
Is there ANY way I can simply get my com.android.phone process back?? Why did all this happen in the first place??
ANY help is greatly appreciated!! THANK YOU!!!
I upgraded to OOS 10 Stable, and immediately started having issues where I would not receive the contents of MMS, but I would receive notifications of them saying "message expired or not available".
Most of the advice I got was to downgrade back to the latest OOS 9, but I didn't want to most likely lose most of my data.
Here's what I would recommend trying:
Option A: Resetting Your APN settings
Open the Settings app
Tap on "WiFi and internet"
Tap on "Sim & network"
Choose the SIM you are having issues with (can be both, in which case do the following steps for each SIM)
Select "Access Point Names"
Tap the 3-dot menu icon at the top-right, then tap "Reset to default".
Reboot your device.
Option B: Flash older Modem images
Go to this XDA thread for stock ROM images.
Download the file named "9.0.17-OnePlus6TOxygen_34_OTA_024_all_1909112343_d5b1905-FASTBOOT.zip"
While the file is downloading, make sure you have USB debugging enabled and and can flash partitions in fastboot. This should require an unlocked bootloader to do so (TAKE A BACKUP BEFORE UNLOCKING THE BOOTLOADER).
Once the file is done downloading, locate the file on your computer, and unzip it.
Inside you'll find another zip file called "images.zip". Unzip this into its own subdirectory.
Go inside that new subdirectory and you'll see a bunch of img files. The one we need to look at is the modem.img file.
Open a command prompt / terminal on your PC in that subdirectory.
Type the following commands into the terminal:
Check if your device shows up in ADB:
Code:
adb devices
Reboot to fastboot:
Code:
adb reboot-bootloader
Check if your device shows up in fastboot:
Code:
fastboot devices
If it appears in fastboot, flash both the modem A and B partitions with the old modem image like so:
Code:
fastboot flash modem_a modem.img
fastboot flash modem_b modem.img
fastboot reboot
If you're still getting issues, try resettign the APN as described in Option A above.
This worked for me on OOS 10 Stable on Verizon with one SIM card in my OnePlus 6T.
Were you running into this issue?
https://forums.oneplus.com/threads/...fter-android-10-update.1134562/#post-21036876
I have MMS working currently with Pulse and the stock OnePlus Messages app, but had to finally abandon Google's Messages which I really prefer over everything.
I had reset APN, tried setting manually, and had no luck, but now I'm curious to try an older modem!
Edit: No luck here Flashed both modems, reset APN, but still get expired messages in Google Messages.
mrpeters said:
Were you running into this issue?
https://forums.oneplus.com/threads/...fter-android-10-update.1134562/#post-21036876
I have MMS working currently with Pulse and the stock OnePlus Messages app, but had to finally abandon Google's Messages which I really prefer over everything.
I had reset APN, tried setting manually, and had no luck, but now I'm curious to try an older modem!
Edit: No luck here Flashed both modems, reset APN, but still get expired messages in Google Messages.
Click to expand...
Click to collapse
My issue was similar, but I could not get any MMS whatsoever on any messaging app, even the OnePlus and Verizon ones.
What was the last version of OOS you were running that had working MMS? Some people reported that even 9.0.17 wasn't working for them, and their alternative was to revert to 9.0.13
EddieK23 said:
My issue was similar, but I could not get any MMS whatsoever on any messaging app, even the OnePlus and Verizon ones.
What was the last version of OOS you were running that had working MMS? Some people reported that even 9.0.17 wasn't working for them, and their alternative was to revert to 9.0.13
Click to expand...
Click to collapse
I can't say with certainty that I was on 9.0.17 and not 9.0.13 but I'm pretty sure I had taken the latest OTA a little while before installing the Android 10 OTA.
Having this same issue here, MMS works OK with OnePlus's app, but not Google Messages. Just got the latest 10.0.1 udpate, and the problem persists.
The last working modem file for me was on 9.0.13, I can still send MMS on other versions but I need to disable wifi first for some reason.
You guys struggle way to much for a service that I consider obsolete... MMS is a service back from the medieval smartphones era (if I can call those smartphones) when wap was the way to receive multimedia messages. There are so many alternatives now, that makes the struggle now pointless...
demeez said:
The last working modem file for me was on 9.0.13, I can still send MMS on other versions but I need to disable wifi first for some reason.
Click to expand...
Click to collapse
9.0.13 modem with OOS 10.0 Stable or 10.0.1 Stable?
chasemyass said:
You guys struggle way to much for a service that I consider obsolete... MMS is a service back from the medieval smartphones era (if I can call those smartphones) when wap was the way to receive multimedia messages. There are so many alternatives now, that makes the struggle now pointless...
Click to expand...
Click to collapse
If only I can prevent any and all of my friends, family, and co-workers from ever sending me MMS, then I'd never have to worry about it!
But honestly though, I agree MMS is pretty pointless and just uses up my data for no real reason.
Then again, it means I don't have to have certain people connect with me on social network messaging apps to send me MMS.
demeez said:
The last working modem file for me was on 9.0.13, I can still send MMS on other versions but I need to disable wifi first for some reason.
Click to expand...
Click to collapse
mrpeters said:
9.0.13 modem with OOS 10.0 Stable or 10.0.1 Stable?
Click to expand...
Click to collapse
9.0.13 modem works on 10.0 Stable for me, haven't updated to 10.1 Stable yet.
Who's your carriers? I have TMobile, completely removed the stock messaging app and use Google's exclusively. No problems at all here, international 6t with latest 10.1. If Verizon, I read somewhere on these boards about a couple files someone copied over and fixed their issue. I can't say for certain it was MMS or SMS, I'll see if I can track the post down.
---------- Post added at 10:12 PM ---------- Previous post was at 09:45 PM ----------
A little searching, couldn't find what I was looking for but I read in one of the posts about 2 files being copied over...I wish I'd had paid better attention, didn't apply to me so just kinda breezed over it.
I found a fix!
After getting no help from Google or OnePlus, I went back to Verizon and had them get me a brand new SIM card. I'm not sure what changed, the APN settings all look identical to my old one, but it fixed the issue. I can receive MMS on any apps now without any issues. (on 10.0.1 anyway)
Bandalo76 said:
I found a fix!
After getting no help from Google or OnePlus, I went back to Verizon and had them get me a brand new SIM card. I'm not sure what changed, the APN settings all look identical to my old one, but it fixed the issue. I can receive MMS on any apps now without any issues. (on 10.0.1 anyway)
Click to expand...
Click to collapse
Have you updated to a newer version of OxygenOS since having Verizon replace the SIM? I have been to Verizon twice now, and both times they have replaced the SIM. It works great, until OxygenOS updates, and then it breaks again. This has been super frustrating, especially because I don't get a notification that the MMS failed to download. I'll go days and then talk to someone in person and they'll ask why I haven't been replying to group chats; then I'll come to find out that I haven't been getting any group messages, nor have I gotten a message saying they failed to download.
For anyone that hasn't seen this, and to help link the two different threads, here's something from the Google Messages community site: support.google.com/messages/thread/18774467
I have sent messages in to both Google and OnePlus, so if I (by some miracle) get a workable resolution, I'll share it here and on the Google community thread.
mason-johnson said:
Have you updated to a newer version of OxygenOS since having Verizon replace the SIM? I have been to Verizon twice now, and both times they have replaced the SIM. It works great, until OxygenOS updates, and then it breaks again. This has been super frustrating, especially because I don't get a notification that the MMS failed to download. I'll go days and then talk to someone in person and they'll ask why I haven't been replying to group chats; then I'll come to find out that I haven't been getting any group messages, nor have I gotten a message saying they failed to download.
For anyone that hasn't seen this, and to help link the two different threads, here's something from the Google Messages community site: support.google.com/messages/thread/18774467
I have sent messages in to both Google and OnePlus, so if I (by some miracle) get a workable resolution, I'll share it here and on the Google community thread.
Click to expand...
Click to collapse
There's another thread that's talking about this issue: https://forum.xda-developers.com/on...dating-to-android-t3999711/page2#post81270021
I posted a reply over there with a possible fix from OnePlus about clearing the system cache. It worked for me, but for how long is anyone's guess.
Came just to chime in and say I'm glad I'm not alone in this struggle... Such a shame to not be able to use Android Messages. Has anyone come up with a permanent fix yet? Does it work fine if you are on a none OOS ROM?
I followed Option A, rebooted to recovery, using TWRP cleared Dalvik/ART cache. Booted up and IT WORKS OMG IT WORKS!!!! Now I can stop using the Default messenger and Signal which splits my conversations and now only use Signal. I was seriously considering downgrading to 9 before coming across this post. Thank you OP.
Also anyone trying to test, I use the following site its sends an MMS to your phone.
https://www.twilio.com/mms
I'm so sick and tired of all this bull**** of A10, both GPS and MMS not working and nobody can tell why, and how fix this.