Hi all. My S2 seems to have stopped recognising my SIM card, and won't display the IMEI number when I type *#06#. I think it may be related to this issue:
http://forum.xda-developers.com/showthread.php?p=7997364
The network name is just shown as "(No service)", there is an exclamation triangle at the top left of my status bar, and a flight mode logo at the top right. Interestingly the phone is not actually in flight mode, long pressing the power button gives me the option to turn it on - but it never actually does it, it just sort of hangs in the process. Trying to access the mobile networks area of settings throws up the error "insert SIM card to access network services".
Unfortunately I have never rooted my phone, flashed or backed anything up.. so the majority of that thread doesn't really apply (or make much sense!) to me. This just started when I was putting my phone in and out of flight mode today. Based on this, what would be everybody's recommend plan of action? I found an app on the marketplace which seems to be designed to sort this out (assuming it's the issue in the thread I linked):
https://play.google.com/store/apps/details?id=com.helroz.GSII_Repair&hl=en
Like I say though, I've never actually rooted my phone. Do people agree it may be worth trying to root my phone for this app? I'm no longer under warranty anyway. I was also wondering about doing a factory reset - does anybody know if that would fix this issue, or does it not touch the files which are causing the issue?
Thanks in advance!
UPDATE 1 - just read that a factory reset won't do anything, so ignore that question - unless that's incorrect! Swinging towards rooting and getting busybox so I can run that app. All stuff which I know nothing about unfortunately.. I know I'll be able to find it online, but if anybody happens to have any nice easy guides, please feel free to post them here and save me some time
UPDATE 2 - fixed! Here's what I did, in case it helps anybody..
Rooted my phone using the following steps from Chainfire (http://forum.xda-developers.com/showthread.php?t=1103399):
- Unzip the attached CF-Root-xxx-vX.X.zip (these files can be downloaded from the same thread)
- (USB) Disconnect your phone from your computer
- Start ODIN
- Click the PDA button, and select CF-Root-xxx-vX.X.tar
- Put your phone in download mode
- (USB) Connect the phone to your computer
- Make sure repartition is NOT checked
- Click the START button
- Wait for the phone to reboot
- Done (if it took you more than 30 seconds, you need practise!)
Downloaded and used this app:
https://play.google.com/store/apps/details?id=com.helroz.GSII_Repair
Thanks to everybody who replied, and donations will be made to Chainfire and Helroz
If you've got no warranty you have nothing to lose by rooting your phone & trying the fixes, right ?
Thread stickied near the top of Q&A & the guides/tutorials stickied near the top of General have all the info you'll ever need.
Im experiencing issues with losing my IMEI for no apparent reason, but I am rooted and have efs backup so its matter of minute or two to restore it. However Would like to know why its happening...
In this post might be solution for your case considering you dont have EFS backup already...
http://forum.xda-developers.com/showthread.php?t=1264021
Hope you will fix it mate, cheers
MistahBungle said:
If you've got no warranty you have nothing to lose by rooting your phone & trying the fixes, right ?
Thread stickied near the top of Q&A & the guides/tutorials stickied near the top of General have all the info you'll ever need.
Click to expand...
Click to collapse
Yeah, pretty much! Just slightly nervous as it's not something I know anything about at the moment, don't want to do more harm than good.
Kepavi said:
Im experiencing issues with losing my IMEI for no apparent reason, but I am rooted and have efs backup so its matter of minute or two to restore it. However Would like to know why its happening...
In this post might be solution for your case considering you dont have EFS backup already...
http://forum.xda-developers.com/showthread.php?t=1264021
Hope you will fix it mate, cheers
Click to expand...
Click to collapse
Thanks for that link, I had seen it but was unsure because it seems to be designed for people who've flashed a custom ROM, which I haven't.. but not sure if that would make a difference?
As MistahBungle said, probably not got much to lose so I'll give rooting a try. Has been on my to-do list for a while anyway. If I can't fix it that way, is this something that a Samsung service centre would deal with, or how else would I go about this?
Another quick question - I've noticed that my battery is now draining very quickly, just since this has started happening. Battery usage shows "cell standby" as being the main culprit, 95%. I've had a search about this, I'm guessing it's to do with the fact that my phone is constantly trying to get onto a network? The time is "100% without a network signal". Seems logical to me, but I wouldn't have thought it would do that if there's no SIM inserted in the phone..? Unfortunately I still can't seem to actually put the phone fully in flight mode, despite there being a flight mode logo in the notification bar. Oh well!
EDIT - this has been resolved, don't worry about answering my questions if you stumble across this thread. Details of the fix in the first post
Related
Does anyone know a way to know if an sms has indeed been sent away? some Sms's just don't arrive and there is no notice to confirm the fact that it was sent off.
Lionel,
Pocket PC 2003 solves this. It displays a little message bubble when a message has been successfully sent.
I have seen that in Pocket PC 2002, if I write and send a message and turn off the display before the message leaves my phone, it will never go. But it will give you the error messge when you go back into your SMS's.
Regards
Keith Burke
Dublin, Ireland
many thanks, so I guess I'll have to get pcc 2003!
greetings,
Lionel
And you can cook it up from here
http://cuba.calyx.nl/~jsummers/ROMkitchen/
Go for the 4.00.10
Best of luck
Hi Ranger,
Can I be sure everything will work all right by upgrading to 4.00.10? I read quite some comments about a series of problems and some people going back to previous versions. Isn't it going to bust up my phone settings in Belgium? Someone wrote not to do any upgrades unless your an expert technician.
2. If I do go on with the upgrade can I just use sd-backup and get my stuff back from Sd-card? Isn't that going to restore my old system?
3. I don't know anything about technics. Most of the options on http://cuba.calyx.nl/~jsummers/ROMkitchen/ sound like Chinese to me.
Sorry for all the dumb questions, but I want to make sure I'm not going to run into trouble.
Hi Ranger,
I decided to run the risk anyway. I can probably do a hard reset and backup if I get into deep trouble.
I went to your link, but as I am a complete beginner at this, I got stuck after 'building the rom now'! I asked for the 'Installer.exe' but couldn't find it on my pc. What shoud I do?
greetings,
Lionel
Ok, first off. Back up your XDA ROM to your SD card. I've never done this, but I'm sure once this is done you can copy it to your desk top.
Secondly, yes there is a possability that it will kill your phone. See http://www.xda-developers.com/forum/viewtopic.php?t=1624
But I have never had a problem, once I stick to my golden rule. Close EVERY PROGRAM that you possibly can while doing the upgrade. And son't touch your computer while it is doing it as well. It's a tiny price to pay. If you're using USB it shouldn't take more than 5 minutes. With Serial cable, I heard it can take upto 20 minutes, maybe more.
As far as downloading it, after you've selected the options in the ROM kitchen [whici belongs to Jeff Summers by the way, not me ] make sure that the bar up the top is still green, NOT RED.
Next, down the bottom there are three options. For yourself, choose the EXE file. After a few seconds, might take upto 30 seconds, up the top of the screen will be a button to down load your file. Just save it somewhere on your computer and run it.
Make sure that your phone is in it's cradle which should be conntected to your computer [or connect the phone to the computer with a serial or usb cable]. Also make sure that the power cable is plugged in.
I think some people have advised taking out your SIM card but i never have.
That should be it.
Let me know either way. If it messes up, just pray that it's after 5% or 10%, so I hear. If so we can try the second option.
Regards
Keith Burke
Dublin, Ireland
One last thing. Take a note of your Network provider settings [GPRS etc...] before you upgrade. They will not be in the new 2003 image.
I forgot when I was doing mine and no longer have my GPRS settings
Hi Keith,
I'm trying it out right away. I have the backup on the sd-card, so that should work fine.
Just be careful with your SD card. I have heard a few reports that it sometimes gets erased in the PDA. Can't remember when or where but if you search the forum you might find it.
Good Luck. It's worth it.
if all you need are sms delivery reports, just click on options when in the compose sms screen and then click on delivery reports, unfortunately you have to do this for every sms as there doesnt seem to be a way to switch it on permanently.
ranger said:
And you can cook it up from here
http://cuba.calyx.nl/~jsummers/ROMkitchen/
Go for the 4.00.10
Best of luck
Click to expand...
Click to collapse
Does this have a radio update ?
Regards
René
Hi,
I've been trying to cook about 20 times since the 1. of August. Tried about everything. Tried all the roms, with and without adding software. Turning off my firewall. Trying all the Rom's. No other programs running.
This is what happens every time:
After selecting the items, I choose the 'install.exe' option and choose 'build rom now'. It starts doing 'something'. I have ADSL and after about 10 seconds the blue bar at the bottom is completed. At the top of the window in the yellow background it keeps saying
'Creating rom... Please be patient
copying rom Files
running mkrom
even after waiting for 30 minutes nothing more happens.
What am I doing wrong?
greetings,
Lionel
Radio Upgrade
@rk
No.
There's no Radio Stack Unit (RSU) Upgrade integrated.
As it depends on the location, where you live, be carefull, which you choose.
For me living in (good ol') Europe the RSU 4.21.00 from O2 UK webside is working.
My native language is Greek and naturally I send Greek sms.
The only problem is that XDA sends them using Unicode character set meaning that over 70 character messages will be splitted.
Does anybody know of any solution on this issue?
I have an O2 payg sim card, even though I ask for delivery reports on sms each time I dont get them, reason being the remaining balance comes in as an sms which cancels the process somehow. Has anybody got a solution to this?
regarding the last, on o2, put *0# in the subject line, and the main sms in the body.
neil
ukneil said:
regarding the last, on o2, put *0# in the subject line, and the main sms in the body.
neil
Click to expand...
Click to collapse
Thank you very much, that worked a treat, I was told by somebody to put that *0# before the fone number, no wonder it didnt work, thanks again.
Hello all,
I'm new here, have read lots of the information available, but came here looking for an answer that I haven't found yet.
Situation is the following.
I got this Qtek2020 (or XDA II) from my dad who used it for his work. The reason he stopped using it is because the "phone" function itself is kind off acting weird.
Sometimes it is just nog possible to get into phone mode, neither of the two methods make te device display the dial pad...
- hitting the green button
- going Start-> phone
(It's kind off like a non responding program in windows when you want to execute it)
To make things clear, the phone works fine if we go to contacts and then choose the option to call the contact.
The question is, does this problem seem familiar and is there a way to fix it by for example putting a new rom on the device?
Any help or input about this is greatly appreciated.
Thanks in advance
I think the HARD RESET should help . After a long... long work configuration data and other settings going to be ... melted . If U don't store on devise impotrant data just remove the battery for about 20 mins .
ive searched for things such as "sleep crash", "sleep bug", "screen wont turn on" etc. but can seem to find anything that tells me anything other than turn off wifi (which i tried to no avail). My issue is that when i press the power button for 1 second to turn off my archos 70 screen it will not turn back on. Same thing happens when i let it fall asleep. If i leave it plugged in and not allow it to turn off screen i have no issues. My apologies if i just don't know what words to search for ... i tried. In on the .4 firmware (latest) with no mods. This has happened through the last 3 firmwares from archos. Any ideas?
Have a you tried a full reinitialization (in settings > repair and formatting) and then reinstalling the latest firmware? If you have just been updating the firmware, the problem may have been deeper.
Thats strange... I have a similar issue with my 101: when i leave my tablet asleep for more than 20min, I can't turn it back on without doing a hard reset. Now it only happens when I simply shut off the screen and leave it alone. If I hold the power button and use deep sleep though, it works just fine. When I can't get it started I notice the little power light is on, but the screen stays black... any suggestions??
I have read somewhere in this forums that re-calibrating your screen from Settings might help, but I still didn't tied - if someone try please post results.
Techngro said:
Have a you tried a full reinitialization (in settings > repair and formatting) and then reinstalling the latest firmware? If you have just been updating the firmware, the problem may have been deeper.
Click to expand...
Click to collapse
I will try this and report back. I have been installing firmware over the issue
Sent from my PC36100 using XDA App
nenadr said:
I have read somewhere in this forums that re-calibrating your screen from Settings might help, but I still didn't tied - if someone try please post results.
Click to expand...
Click to collapse
I am try before formatting and report back
Sent from my PC36100 using XDA App
nenadr said:
I have read somewhere in this forums that re-calibrating your screen from Settings might help, but I still didn't tied - if someone try please post results.
Click to expand...
Click to collapse
this worked!!
mallman said:
this worked!!
Click to expand...
Click to collapse
spoke too soon. did not work. it stopped after a few tries
it works again if i recalibrate but wont hold.
Zoidpilot said:
Thats strange... I have a similar issue with my 101: when i leave my tablet asleep for more than 20min, I can't turn it back on without doing a hard reset. Now it only happens when I simply shut off the screen and leave it alone. If I hold the power button and use deep sleep though, it works just fine. When I can't get it started I notice the little power light is on, but the screen stays black... any suggestions??
Click to expand...
Click to collapse
by the way, the deep sleep option also kills mine.
Search softlocker in market, not a perfect solution but fir me work rigth. Reduce the reboots.
Sent from my A101IT using Tapatalk
ramso said:
Search softlocker in market, not a perfect solution but fir me work rigth. Reduce the reboots.
Sent from my A101IT using Tapatalk
Click to expand...
Click to collapse
just tried it . i hit the icon to disable sleeping. i pressed the screen button and when i went to turn screen back on it would not wake. Did i use the app wrong?
No, you use the app rigth. The app only disable deepsleep.
Sent from my A101IT using Tapatalk
i had the same problem on my 32, albeit not that frequently. Downloading the FW and reflashing it seems to have made the problem go away.
You know what? Strangely enough after I replied to your post I downloaded the latest fw (2.1.4) and the problem seems to have gone away no special flash no repair I just installed and rebooted and so far no prob... I will keep testing this and post results
Edit* Ok so far so good... no problems. I'm actually surprised I'm getting better response from the device despite everyone's warnings about 2.1.4. But that's another topic. I think its just a bad install of your current FW, but I'm just guessing... My device has had the issue since I got it, I just decided to live with it but like I said the latest update fixed it... So it HAS to be the FW
bbop said:
i had the same problem on my 32, albeit not that frequently. Downloading the FW and reflashing it seems to have made the problem go away.
Click to expand...
Click to collapse
err I'm afraid that I spoke too soo. My device keeps getting stuck and won't awake from sleep. This seems to happen most after switching wifi on or off, specifically whilst the device is playing music.
Zoidpilot said:
You know what? Strangely enough after I replied to your post I downloaded the latest fw (2.1.4) and the problem seems to have gone away no special flash no repair I just installed and rebooted and so far no prob... I will keep testing this and post results
Edit* Ok so far so good... no problems. I'm actually surprised I'm getting better response from the device despite everyone's warnings about 2.1.4. But that's another topic. I think its just a bad install of your current FW, but I'm just guessing... My device has had the issue since I got it, I just decided to live with it but like I said the latest update fixed it... So it HAS to be the FW
Click to expand...
Click to collapse
how are you installing the firmware? maybe im doing it wrong. I let the device update to latest 2.1.4 and then i wiped it via the settings and repair menu in android.
Edit**
like this??:
Step 1: Download the android 2.2 firmware for your archos tablet from here,you might a get a false positive notification from your browser as they are unaware of .AOS format, so ignore that and download it.
Step 2:Go to Menu > Settings > Device Storage & USB connection > USB connection mode of your tablet and set the connection mode to Mobile Media Device (MTP) and now connect your Tablet to pc.
Step 3:Now when the tablet is detected you will see a hard drive icon,double tap and open it and copy and paste the firmware (.AOS) file into the hard drive(make sure you dont copy it in any folder inside it like Music,Videos etc).
Unplug the USB connection and the Archos device will automatically locate the update file and will prompt you for the update,just follow the screen options and you are done,if it does not prompt you for an update then you might have accidentally misplaced the file in one of the folders,just locate the .AOS file from the file manager and and open it to start the update.
No no it wasn't that complicated... It was actually the simplest fix for a difficult problem. My device when I got it was running 2.1.2 out the box... Even then It had the screen problem. When I got the chance I installed 2.1.3 OVER THE AIR. Straight from Archos. Still had the issue though, I figured it would have been fixed but was greatly disappointed... Then I sort of just lived with the problem for awhile... I saw that the 2.1.4 update was released but was wary about downloading it because sooo many people are having issues. Just the other day though, the device cut off on me again and I figured to hell with it... So I downloaded the 2.1.4 OTA as well... no website, no manual install, I just let the device run its course on its own. After the update, it rebooted normally and it's been working great since... Sorry to hear not everyone is so fortunate... I really hope this helps somewhat
So about a day ago my phone got stolen. Now the phone in question had an utterly obliterated screen of which rendered it completely useless for now. However i am more interested in the sd card rather than the phone it self. When trying to ping it with Android Device Manager it just says that the location is unavailable so there seems to be no internet connection.
So i tried installing Android Lost through the Play Store and pushing a message with the command "androidlost register" to no avail. So by this time i assumed that the SIM card had been plucked out and done for. But i tried pushing another text message earlier today to it with the same command but this time with delivery reports enabled. And i got a message that said that it'd been delivered.
So this has to mean that the sim card is still in there and the phone is still on but no internet connection right?
Now is there any way to have Android Device Manager notify me whenever it comes online? My operator has a feature where i can enter the IMEI and lock the phone through that. But what kind of lock would that enable? Is it just like having the phone locked down with a pattern lock? Also could it affect the sdcard? If so then in what way? How is .nomedia files treated on Touchwiz own gallery app and file explorer? If this guy has left the SIM in then i can undoubtedly also assume that he has left the sd card in as well. Is there any way at all to wipe and or pull the files from the sd card? I'm ready to do pretty much anything even if it requires to hire a blackhat who'll get this **** done for me. I don't think what kind of phone this is really matters but it's an S4 LTE running CM11 with a six number code enabled, this isn't really something that's he's gonna get through if he fixes the screen is he?
As for now it seems that the phone is turned off since i am no longer getting delivery reports and my kik messages are just not getting through.
If this is way too much then i'd appreciate if someone could point me in the right direction of where someone might be able to help me.
First time posting here so if the thread is in the wrong place feel free to move it.
Bump
BE2026
The stock oxygen OS has a text message bug that apparently isnt fixed yet, so i thought id try a different rom.
I unlocked the bootloader, worked great.
Then i flashed TWRP and it worked great.
I then proceeded to try and flash DerpFest and when the ADB sideload (ACCORDING TO THE DIRECTIONS) was done, it is suppose to reboot into the new os. but I get nothing.
So Ive tried, a bunch of stuff. I tried using orangefox and it doesnt support SD cards and the sideload option just crashes. So then i try TWRP recovery instead of billies recovery and when i select the image to install in TWRP, and then 'swipe to flash' TWRP instantly resets. and nothing happens.
So then i tried the MSMdownloader tool and it will not recognize the phone at all. all adv and fastboot commands work great.
Can someone help me?
I tried switch A or B, and flashing both,
I tried to go back to stock and i cant even get that to work.
Help meh please, i just bought this phone and now i cant even use it
I also cannot get the MSMdownloader to work. it shows my phone on the list in EDL mode. but com port is empty. device id is empty. all the fields are empty and it just says waiting on device. nothing happens.
For MSM, did you get the driver properly installed?
[OPN105G][OOS 86AA/89BA] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com
arda99 said:
For MSM, did you get the driver properly installed?
[OPN105G][OOS 86AA/89BA] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com
Click to expand...
Click to collapse
everyone comes up as it should in the device manager. sad face....
Just to be sure, what do you actually SEE? IIRC it was tricky the first times I used it, until I figured everything out.
There is a separate driver from the MSM tool itself; that makes your phone show up as a Qualcomm something or other... but only for about 3 seconds! In that time, you have to start the upload. Thus, I'd have the tool RUNNING, mouse over the start button, THEN plug in phone.... when it shows up, click, and wait till it says something akin to "beginning firehose download"... then you can let go of buttons on phone, sit back, and watch the magic.
Given a proper setup, it's really odd that this fails, for anything other than a completely bricked phone (e.g. dropped it in the ocean)... if you can get into FB or recovery, you should be able to have MSM recover to stock 100%.
Hope that helps.
SomeRandomGuy said:
Just to be sure, what do you actually SEE? IIRC it was tricky the first times I used it, until I figured everything out.
There is a separate driver from the MSM tool itself; that makes your phone show up as a Qualcomm something or other... but only for about 3 seconds! In that time, you have to start the upload. Thus, I'd have the tool RUNNING, mouse over the start button, THEN plug in phone.... when it shows up, click, and wait till it says something akin to "beginning firehose download"... then you can let go of buttons on phone, sit back, and watch the magic.
Given a proper setup, it's really odd that this fails, for anything other than a completely bricked phone (e.g. dropped it in the ocean)... if you can get into FB or recovery, you should be able to have MSM recover to stock 100%.
Hope that helps.
Click to expand...
Click to collapse
OH wow it did. Thank you, the documentation for that side of MSMd is vague. So after trying like 3 different "qualcomm" drivers I finally got it to work! As in the stock android 10 is loaded and the phone is no longer bricked. However, when I try the same methods again to actually put a custom rom on this phone the same thing is still happening.
No matter what OS i try to flash, no matter what mode or slot, or what recovery 'program' i use like twrp or orange FOX, nothing seems to actually boot into an OS. it just loops into Fastbook.
Can anyone help me? I dont want to use oxygenOS
I had a somewhat similar experience in loading custom ROMs, and simply took to de-bloating the stock image (emphasis on de-google-services, de-OnePlusSpyware, and de-auto-OTA). Still not really happy, compiling AOSP source now to try to swap out some of the system APKs that annoy me for customized ones. If there are only a few things that sour you to OOS, maybe I (or others) can help cure those? Debloat and replace...
I wish I had more silver bullets for you on custom ROMs, but you aren't alone. At least know that you can now go back to stock no matter how bad a ROM is... a lot of other phones, not so much.
So the main reason for me not wanting to use Oxygen OS is because when initally setting up the phone, everything works great. for about 2 or 3 days. then for what ever reason i cannot receive text messages. If I factory reset the phone, or put my simcard into another telephone all of them come rushing in.
In the event of me factory reseting my phone, ill get text messages from 3 or 4 days ago.
and it always works. as soon as my friend is texting me and i dont recieve it, i just factory reset then boom its there.
I tried everything, different SMS apps, update this, android 11 that. it always did it to me, like clockwork. like the phone installs an update and breaks text messages. I tried contacting oneplus customer support but that shhit is a joke. they told me they are aware of multiple isolated incidents about this and that the only thing to do left is to send it in. I JUST BOUGHT THIS THINg, im not about to send my device away, right after paying for it. I paid you guys $400 just to NOT have a telephone for 8-16 weeks?
SomeRandomGuy said:
I wish I had more silver bullets for you on custom ROMs, but you aren't alone. At least know that you can now go back to stock no matter how bad a ROM is... a lot of other phones, not so much.
Click to expand...
Click to collapse
See thats the thing, Ive never gotten another room, to boot. at all. no splash screen, no bootlogo nothing. it always just goes back to fastboot. it never tries to boot an OS. i follow these billie instructions and nothing happens. its the same result. I have tried all the different versions in this forum. from pixel experience to derpfest. all work great, untill the very last step where they say side load rom/flash and then reboot. your new os should be booting! and it doesnt.
Wow, that's a new one for me. I wish I knew more about the internals (slowly learning) to help troubleshoot. I would GUESS that if you can change phones (e.g. you said you can put the sim in a new phone, and get a backup of messages delivered), that it isn't so much that the phone is dropping them as it is not getting them in the first place.
With no guarantees- this is a SWAG- have you checked your APN settings? Most definitely, these come through as part of a new registration (duh), and consequently can get messed up for $diety knows why later... but at least you may be able to get a known-good set of settings (post reset, post registration) to compare to after terrorists strike and you are no longer getting messages. It should be easy to add a new APN with the "right" settings and manually select it.
If it is something like that, odds are an alternative ROM would just do the same thing; I assume there's some kind of handshake standard for initialization of the carrier network. I'm on TMo and happy to share my settings, if it helps....?
Looks like RCS issue as 1+ switched to google phone/msg in OOS11.
Read here.
Turn Off RCS "Chat" When You Switch Phones or Else...
Now that Verizon has committed to RCS with Google, the three major US carriers are all onboard. RCS is here (unlike 5G) and will be a big part of your messaging experience going forward, assuming you have an Android phone. And while RCS is great and a big improvement on traditional text...
www.droid-life.com
How to turn off RCS chats
messages.google.com
arda99 said:
Looks like RCS issue as 1+ switched to google phone/msg in OOS11.
Read here.
Turn Off RCS "Chat" When You Switch Phones or Else...
Now that Verizon has committed to RCS with Google, the three major US carriers are all onboard. RCS is here (unlike 5G) and will be a big part of your messaging experience going forward, assuming you have an Android phone. And while RCS is great and a big improvement on traditional text...
www.droid-life.com
How to turn off RCS chats
messages.google.com
Click to expand...
Click to collapse
sadly this has nothing to do with my problem.
After much testing and another go round of fractory resets and then magicly i recieve texts again. There is nothing that can stop the factory oxygen OS from updating or downloading and installing some update that completely brtiks message functionality. Can someone help me maybe mod or edit the factory ROM image to prevent this?
I found out in the "google assisnt" of setting up your phone for the first time, if i set it to remind me tomorrow then im all good and i can keep using the phone. as soon as i go back to that "setup" and hit continue, the next screen says "installing updates" and then I can no longer receive texts. Does anyone know how to bypass/get rid of this auto matic update thats in the "first time run wizard for adroid" or whatever the FUCFKA its called.
Please, I really think this phone might just be a lost cause
agentruley said:
sadly this has nothing to do with my problem.
After much testing and another go round of fractory resets and then magicly i recieve texts again. There is nothing that can stop the factory oxygen OS from updating or downloading and installing some update that completely brtiks message functionality. Can someone help me maybe mod or edit the factory ROM image to prevent this?
I found out in the "google assisnt" of setting up your phone for the first time, if i set it to remind me tomorrow then im all good and i can keep using the phone. as soon as i go back to that "setup" and hit continue, the next screen says "installing updates" and then I can no longer receive texts. Does anyone know how to bypass/get rid of this auto matic update thats in the "first time run wizard for adroid" or whatever the FUCFKA its called.
Please, I really think this phone might just be a lost cause
Click to expand...
Click to collapse
"carrier services"? that's the only one I can think of. Try to uninstall the update, or if you don't have it in your phone, install it.
I had to go through the setup process again. First time the DF just didn't catch. I read ADB sideload can be broken as **** sometimes.
arda99 said:
"carrier services"? that's the only one I can think of. Try to uninstall the update, or if you don't have it in your phone, install it.
Click to expand...
Click to collapse
Sadly this has nothing to do with my problem. Installing newer/ using older versions do not change the behavior.
The phone breaks as soon as I go back to the "Google Assisnt" -Setting up your phone for the first time- wizard and instead of selecting "Remind me tomorrow" i select next, and then the following screen says "Installing updates" and then the telephone will no longer recieve text messages. Does anyone have any help?
Oneplus customer service is terrible and they told me to buy another device.
This is the last phone i will ever purchase from them