I've got a Galaxy S4 active from at&t and rooted it. One of these days, it updated something and stopped working, saying that it found an unauthorized system software. I tried uploading a diferent operational system but at&t got a lock that doesn't let you update the operational system. Is there any way to fix this problem?
Related
Hello,
A collegue is running Android 2.1 on her Galaxy S. I believe it has the codename GT-I9000. She is currently running firmware version PDA:JF3 / PHONE:JF3 / CSCJF1.
Since Samsung released their Froyo update some while ago and it is believed that Froyo significantly increases the performace. This is a stock installation. The phone isn't rooted.
When I connect the phone to Samsung Kies (2.0) it reports that there is a new version, like it is supposed to be. Screenshot here.
However, when I initiate the upgrade the process fails at Downloading (0%) and reports that the server returned '403 Forbidden'. Samsung fails to respond for more information about this message.
I'm hoping that someone here knows a way to possibly fix this altough this seems like a server-side error. If not, is there a way to manually upgrade the phone without losing contacts, media and installed applications?
Thank you in advance;
Jorijn
bump bump bump
I have an SCH-i800 that I have CM9 (p1c 9.1.0) installed on. I have been using it for several weeks with no problem. Since I am planning on going on a trip, I decided to active pre-paid Verizon service for the tablet. At first, I attempted to activate the device. It went through the phone call but after a minute, it just sat at activating. That is when I noticed that the radio state in the status bar had an X on it. I rebooted the tablet to try again and got "com.android.phone has topped unexpectedly". I re-flashed CM9 (at the time I was using 9.0.0) and it worked again. Activation was not necessary. After a day, the error came up again and radio state went to off with an X. I tried 9.1.0, same problem after a day. I even tried a nightly CM10, same problem. Reboots, cache wipes, permission fixes do not make it work. The error persists until a re-flash of CM. I see on the Support Downloads for the Verizon Tablet, there are two modem files. My baseband version is currently S:I800.0.3V.EI04. I have attempted to "flash" these both via Odin (which failed after a couple minutes) and ZIP (which looked like it worked) to the EC02 on the site, but my baseband doesn't seem to change.
So my first question is, is there a how-to on flashing as I have searched high and low on one for the Verizon Tab specifically, and have yet to find one. Is there a ZIP file that is specifically meant for the i800? I am almost certain this is my problem and that a downgrade (this tablet when stock was updated to the latest Verizon image).
My second question is, has anyone else experienced this? Is there someone that is using a CM9 Verizon tab with EI04 baseband and not have this problem?
Is there a way I can track down what crashed the program? I have tried logcat, but it doesn't appear to give me much detail other than to tell me that it stopped.
And if you ask, no I did not use the Verizon service with this tablet before putting CM9 on it, so I wouldn't know if it worked before.
Any input that someone could provide would be useful. Thanks!
Hey all,
Looking for some assistance here. I apologize in advance for not having specifics on everything, but it's been a couple years since I've needed to do anything with this phone (SM-G900A). I picked it up used a couple years ago and shortly after, I did a NOX unlock and rooted the phone for two reasons - using Titanium Backup and to unlock the WiFi hot spot. I recently noticed that something had happened and my root access wasn't working correctly- guessing from one of the OTA updates that was attempting to occur on my phone. I say attempt, because I don't believe they ever successfully installed since they always seemed to error out. I'm currently on StraightTalk, not an AT&T customer. Something weird was up with it though, because I could never uninstall the Xposed Framework or app, yet Pokémon Go was recognizing it was rooted and blocking my access. I should also mention that I had towelroot running on the phone and it's showing the custom unlocked padlock on startup.
Fast forward to last night- I wanted to return it back to the stock ROM so I did my research, found a couple different tutorials that included the correct ROMs and applied one - G900AUCU1ANCE_G900AATT1ANCE_ATT.zip. After flashing, the phone will not boot and freezes halfway through the swirls around the Samsung logo, then goes blank. The blue notification light also stays lit on the phone.
Thinking it was most likely bootloader related, I found another ROM that included separate AP, BL, CSC files. I attempted to flash the bootloader, which failed and I got the following error on the phone - SW REV CHECK FAIL : [aboot]Fused 2 > Binary 1
At any rate, it seems like my boot loader somehow got corrupted or isn't compatible with this ROM, but I was hoping some of you experts out there could provide some answers. At this point my phone is dead, so I'm hoping I can get it restored very soon.
Thanks in advance guys!
The issue identified in this thread (http://forum.xda-developers.com/galaxy-s5/help/g900a-stuck-samsung-logo-black-screen-d-t3050369) seems very similar to mine as well as what's described on this website- http://www.galaxys5update.com/fix-black-screen-with-pulsating-blue-led-on-galaxy-s5-g900a/
I'm seeing the pulsing blue light as well. How do I find the 4.4.4 OA1 Kernel identified in the first link?
I updated my moto x4 from Oreo to pie using flash using boot loader. my boot loader is still locked and software status is official too. It still is unable to update to January security update. Please help !!
yes I have also facing same issue... i have also try by safe mode but shows something not right .... reconnecting to server... might be Moto update Services try to connect moto server which has not able to connect due some issue in server... hope so this is issue...
you can connect to moto support team let me know what they are say for this issue.
They told to reset and try again.. to do that I got to backup my data which LL take time.. so on hold as of now
Yup, same here. I got the Android 1 Google Fi model (Bootloader unlocked, unrooted). I'll try again in a week and see if it resolves itself.
And another ~ bought 2, mine showed the update 3 days before my wife's but won't start (download and install now, via wifi only and it reverts back to the settings screen). She got the notification last night and it took first try. First time I've had this issue in the 4 months I've had the phone, just glad I'm not alone here....
Since you're official/fully stock, there's not really any alternatives besides factory reset or await for full image is available to manually flash via fastboot method. You do not need to unlock long as you stick with motorola firmwares. Links in FAQs thread.
Nothing new here? Mine keeps nagging me to do the update, start it and it shows getting to 17% on step 3 of 6, then just kicks me back out to the setting screen.
This is my first android phone (from a flip), couldn't get lineageos to work with my provider (RedPocket) and have neutered as much of the google crap as possible. Right on down to disabling all permissions for Play Store. Could that be part of my issue?
It has been nagging me since last few weeks, no solution apparently
New Update:
Could actually able to fix the issue by installing a vpn and set it as a USA based server.
My phone was bought in US and I was using it elsewhere. After using an USA based IP it downloaded the update and voila.
Recently I have installed the latest firmware update onto my N950N. Since then my device has been getting the IMS Service has stopped error. I have tried allot of the troubleshooting steps on the internet, which don't work. I have even performed a hard factory reset of the device. That didn't work either. Can anybody provide me with any assistance please?
The recent 11-09-2019 update has resolved this error!! Just wish that they released it earlier so I wouldn't have to purchase a Note 9 N960N!!!!!!!
Lol