I just bought Samsung Galaxy S II about two days ago. I got AT&T network. It was working perfectly....
When I turned of and turned on the device, the Status Bar suddenly crashed. A popout window occur saying,
Sorry!
The application Status Bar (process com.android.systemui) has stopped unexpectedly. Please try again.
then the only option was Force Close saying on the screen; I could not use even the Home, Back, Option keys.
I took out the simcard and when i turned on, still the same problem.
I took out the battery and put back in, still the same problem.
I could even factory reset the whole thing the Samsung Account is halting it. I was enetering the correct password..It kept saying Error Processing failed.
are there any ways to fix this problem?
thanks in advance!
this is making me upset. I like this phone a lot.
jambachever said:
I just bought Samsung Galaxy S II about two days ago. I got AT&T network. It was working perfectly....
When I turned of and turned on the device, the Status Bar suddenly crashed. A popout window occur saying,
Sorry!
The application Status Bar (process com.android.systemui) has stopped unexpectedly. Please try again.
then the only option was Force Close saying on the screen; I could not use even the Home, Back, Option keys.
I took out the simcard and when i turned on, still the same problem.
I took out the battery and put back in, still the same problem.
I could even factory reset the whole thing the Samsung Account is halting it. I was enetering the correct password..It kept saying Error Processing failed.
are there any ways to fix this problem?
thanks in advance!
this is making me upset. I like this phone a lot.
Click to expand...
Click to collapse
What you need to do is flash a new ROM to the device, the ROM has somehow become corrupted.. Go to Intratech's thread in the DEV section and download the latest 2.3.4 ROM and flash that using the instructions on his thread, all is well, its 99.999999999 a software problem the 0.0000000001 is because you never know
[email protected]
Thank you I will try it now!!!!!!
I see he has not packaged a 2.3.4 ROM yet so try this one, Its KF2 and is the best ROM after the new 2.3.4 ROM I was running this up to yesterday, and will be ok for you until you need to upgrade again later
http://www.multiupload.com/P2AHY9IJPW
jambachever said:
Thank you I will try it now!!!!!!
Click to expand...
Click to collapse
Hope all went well Jamba
[email protected]
Sent from my Samsung Galactic Crusader S II
I have another problem tho. After I updated the device, I lost my data, which i could not connect to the internet. how can i put back my AT&T apn settings? any idea?
Thanks in advance!
jambachever said:
I have another problem tho. After I updated the device, I lost my data, which i could not connect to the internet. how can i put back my AT&T apn settings? any idea?
Thanks in advance!
Click to expand...
Click to collapse
You need to go to AT&T website and you will find it there if not, Google at&t apn settings)
[email protected]
Sent from my Samsung Galactic Crusader S II
I'm kind of stuck and could use your help. It's much appreciated. I have an unlocked C6833 I've been using as a "mini tablet" (no SIM card/no mods/in the US). I received notification yesterday that there was an up date (I'm guessing the latest) so I downloaded it. I thought everything was going fine until I checked this morning and nothing---
Computer can't access phone when connected.
I can't access anything on the phone. The pic attached is the only thing that shows when I press the power button and then it turns off and the green dot starts to flash again.
Attached is a pic of whats going on.
IRONLUNG said:
I'm kind of stuck and could use your help. It's much appreciated. I have an unlocked C6833 I've been using as a "mini tablet" (no SIM card/no mods/in the US). I received notification yesterday that there was an up date (I'm guessing the latest) so I downloaded it. I thought everything was going fine until I checked this morning and nothing---
Computer can't access phone when connected.
I can't access anything on the phone. The pic attached is the only thing that shows when I press the power button and then it turns off and the green dot starts to flash again.
Attached is a pic of whats going on.
Click to expand...
Click to collapse
What it says on the first screen? I can't read it. Can't you keep pressing next?
I think the error message said initialbootsetup not responding or something to that affect. I couldn't really do anything with the phone.
It turns out that the Sony servers were overloaded or had some glitch because of the release and a lot of people trying to upgrade were stopped in their tracks.
I should've known.....never had a problem like this w/ any other phone (first Sony). Seems like they've always had some sort of problem w/ their servers and whatnot. Oh well live and learn......
It's all good now. I was able to upgrade via usb/PCC the next morning.
Sent from my HTC One using XDA Free mobile app
phone: Samsung Galaxy s9+
android version: 10 (upgraded from 9, pushed out by tmobile)
one ui version: 2.1 (also pushed out by tmobile)
model #: sm-g965u1
Since the 7/1/2020 update, I get a notification from omadm that a firmware update is not complete. This notification cannot be dismissed, and omadm cannot be disabled. auto retries every 60 minutes.
Also, I get another notification that wakes the phone up every 60 minutes
"Attention android update is successful" I will get this same notification again in 60 minutes.
The phone was never rooted by me. But I did buy it used off of Amazon. Phone was working fine with android 9.
I'd just like to stop the notifications. Except for the notifications, the phone works. I can make and receive calls, texting works and I can browse the web. All of my apps work.
Does anyone know how to stop the notifications?
I've already tried removing my sim card. This doesn't do anything.
I had the same problem with an unlocked used S10+ I purchased on Amazon. I had to send it back for other reasons but I got similar notifications. This seemed to work for some people:
SOLUTION (AT LEAST WITH MY GALAXY NOTE 10 +)
Had the same problem on a Samsung Galaxy S10 and here's the solution that seemed to work:
Go to 'Settings' > 'Software update' and hit 'UICC Unlock'
It loads for a moment, then says SIM Restricted... Hit 'OK'
It takes you back to the 'Settings' > 'Software update screen'. Hit 'Download and install'
It loads for a moment, then says Your software is up to date...
Then open that notification saying the profile didn't update.
It loads for a minute, then says Profile updated... Hit 'OK'
It loads again for another minute and says something similarly. Hit 'OK'
Click to expand...
Click to collapse
https://support.google.com/fi/thread/56884144?hl=en&msgid=66380028
If you find a solution that works let me know b/c I'm still interested in getting an newer galaxy phone.
shady909 said:
I had the same problem with an unlocked used S10+ I purchased on Amazon. I had to send it back for other reasons but I got similar notifications. This seemed to work for some people:
https://support.google.com/fi/thread/56884144?hl=en&msgid=66380028
If you find a solution that works let me know b/c I'm still interested in getting an newer galaxy phone.
Click to expand...
Click to collapse
This did not work.
wiping the cache did not work
resetting the phone did not work.
Every hour, the phone wakes up on it's own and does the failed to update thing.
I'd root the phone, but I found out the phone is basically unrootable
It's crap like this that makes me HATE androids, not that Apple is any better. Apples are basically built for morons.
BTW, I did not see what is posted in the above fix. It makes me think some guy put that on his website just to get clicks for the ads on his page.
I tried flashing, this did not work either. As soon as you accept any update from your carrier you get this error back. In my case initially, flashing the stock firmware seemed to work. I did not see the error. But the first update that T-Mobile sent to me was the time zone update, which I got After flashing the phone with the latest stock firmware from sammobile. As soon as I accepted that update, the error came back.
someone in the T-mobile forums suggested using ADB to remove omadm. This can be done as a standard user, apparently, something I did not know.
linking back to the original forum post on this site:
https://forum.xda-developers.com/showpost.php?p=77194732&postcount=11
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