Soo...
When I got the phone, I was able to remove the bloatware; cant quite remember what I used or downloaded to the phone. It was a while back and lost all my files on the laptop.
However,
I updated my Samsung Galaxy S8 and it seems like it was fine for a day or so, all of the sudden it started boot-looping..
Just restarting and showing the Samsung Galaxy S8 screen, over; and over..
I am looking to reset it, and hopefully remove all of the T-Mobile bloatware again. I have tried a couple of these methods however each one seems to fail at some point. So I have no clue what state my phone is in, or what needs to be done.
Below is the information to my phone, any chance I could get some assistance to something that will get me back to at least using the phone. Or even better, using my phone without the bloatware; just simple Google apps.
Any help would be GREATLY appreciated. Thanks again ahead of time!
SAMSUNG GALAXY S8
SM-G950UZKATMB
(Last time it worked, I had updated it to OREO)
Related
Ok, so Friday morning I woke up and my phone was stuck in exhibition (desk) mode. I had to remove the battery twice to get it to boot into android and stay there.
This is a NON ROOTED Captivate. Using stock Froyo from Kies.
After I get it into Froyo, I went to make a phone call, and then the dialer sends the call, and vanishes. The phone freezes. The call goes through, but I now have no access to the rest of the phone. No ability to use the dial pad, or even to shut off the phone. I have to manually remove the battery.
After 48 hours I was pissed off. I'm out of warranty with AT&T by a month because I bought it on launch day last year.
So I used Odin to reset it to stock Eclair, and tested it, worse than in Froyo! The phone actually froze and the call didn't even go through! So I re-updated via Kies.
I'm back to square one. I have no idea where to go from here. HELP! I don't want to suffer this until the Galaxy S 2's come out here in the states, and I don't want to flash it to a custom rom if at all possible. Resetting it to stock should have fixed the issue if it was software, right? So it has to be hardware, right? But how does that make sense that only the phone function would be affected?
HELP!
Thanks in advance,
Tiberius Reign
^ Any recently downloaded app, widget, etc. that could be suspect ?? Anything come to mind that u may have done right before this started ??
I see u went to stock eclair, but i ask the above just in case u might have reinstalled everything after u went stock.
I tested the phone without installing any apps. I had a worse problem. The damn phone rebooted. I upgraded back to Froyo, and it became manageable. I saw someone else who was having similar issues with com.android.phone freezing and locking up all the time. Mine does it some of the time, and it's getting worse. I tried the delvik clear etc that was listed, and it still didn't help.
I'm kind of at my wits end here.
A lot of us i think are starting to have this problem. I had started a thread a while back about it but was never able to solve the problem. here is my original thread http://forum.xda-developers.com/showthread.php?t=1168128
here are threads of other people having a similar problem that i have also replied in
http://forum.xda-developers.com/showthread.php?t=1204823
http://forum.xda-developers.com/showthread.php?t=1226807
i think would should all stick to replying back to one thread maybe this one because its newer, this way it can be easier for us to help each other find a solution to this problem.
I used the Kingo Root method to root my Note 3 that was running 4.3. When I decided that I was ready to go ahead with the AT&T 4.4.2 FOTA; I used it to un-root so my phone would accept the update. Both processes indicated that they were successful. However; my Note 3 will not accept the update under any circumstances. It downloads the FOTA - which takes close to an hour - and gets to the 25% install point after rebooting and fails with "Invalid Signature" appearing for a few seconds after the "Installation Failed!". It then unceremoniously does a factory restore and I'm left with, yet, another setup procedure and reinstallation of all of my apps, passwords, etc.
This has happened twice with two different phones - the other being my Samsung S4. Exactly the same sequence. I took the S4 to Best Buy, after AT&T forced an update to it, and it, too, failed. Samsung did a direct flash to the S4 and it indicated that it took the 4.4.2 successfully. However, when the phone rebooted, it was still 4.3. Samsung scratched their head and couldn't figure it out. I see no sense in try to do the same with the Note 3 since it will likely be the same experience.
Neither phone show the KNOX trigger having been tripped, and both show "Official" as though nothing had ever been done. I never did any modifications to either phone, other than the root / un-root to stall the FOTA, until I was sure that I was comfortable with the update.
I sent an email to the same effect as this post to Kingo, with no response.
Has anyone had the same experience?
I know that for a while, there was a great deal of concern over the Kingo Root method, but thought that it had been resolved and that any myths had been debunked.
Did I shoot myself in the foot?
Hey friend, this has been asked A LOT in this forum. All you had to do what look through the first page and you'd see this topic.
However you're scared and our phone are probably our more personal and needed device so I understand your impatience and panic.
How to fix: http://forum.xda-developers.com/showthread.php?t=2701062
Be well, relax, everything is going to be ok. You're not alone . We're with you my new friend.
Sent from my SM-P600 using Tapatalk
Sorry for posting in the wrong thread. I searched over the weekend, but didn't see what looked like an answer.
Thank you so much for posting the direct link! And, thanks for not mountain climbing me about the gaffe.
I'm still fairly new to this, so I genuinely beg everyone's pardon for the mis-post. I'm still trying to learn how to navigate through the different sub-forums. I'll try to be more courteous in the future.
Now, I'm in a REAL pickle! AT&T is trying to cram KK down my throat on my Note 3 and I have about 4 hours (according to their website) to respond before they force it. On the AT&T variant; there is no way that I know of to block the update; except temporarily. Then; it's back to the wash, rinse, repeat cycle of having to restore my phone and apps - EVERY time the update fails!
I still haven't done the downgrade; because after rooting and installing a custom 4.4.2 ROM on my kid's phone least night; I decided that I want to re-root my Note 3 and install KNOXRAID as a custom on my Note 3.
My dilemma is; if AT&T crams the update down my throat - as they did with my S4; it's going to fail again, and I'm going to have to start from scratch again, and again until I find a solution.
I tried re-rooting my Note 3 with Kingo, but it fails every time, now.
So; what should I do? My hunch is that I'm going to have to do the 4.3 fix and restore it back to factory, but then it would allow AT&T to actually force THEIR KK into the N3, and I'd be screwed, until a root method is obtained for KK.
PLEASE! Any suggestions? I suppose, for the short term; I could cut off my N3; install my SIM into my S4 and use it until I'm able to resolve the issue with the N3. I need Total Recall to work on my N3, and KK will definitely kill it.
*UPDATE* I turned the N3 off, removed the battery and SIM and installed the SIM in the S4, and am using it for the short term. Unfortunately; my S4 already has the AT&T KK update installed, and I need to resolve the issue with the N3 as quickly as I can. My hunch is; to avoid them doing it again; I'm going to have to turn off Wi-Fi and place the N3 in "Airplane" mode and leave the SIM card out of it until I'm comfortable - and have a clear method of installing KNOXRAID.
Still hoping for a solution. At this pint; I'm not that concerned about tripping the KNOX sensor on the N3, but would prefer to be able to flash back if I needed to enforce my warranty.
Thanks!
Hi all
I am not technical and am not really sure what to even call this issue, but have done numerous searches on this and other forums over a few weeks and am not able to find anything like it. I'm sure there must be, but because there is nothing onscreen to help identify the issue I don't know what to search for next.
I few weeks ago I got a message to upgrade the O/S. I didn't do it at work, as my reception there is pretty lousy. When I did do it I had good reception. When it had finished, it then wanted to install. I left it until the next day, when I was home again with a strong signal. It commenced installation but when it got to 91% it rebooted and started over again. This has been happening ever since and the only way to stop it is to remove the battery. I've tried leaving the battery out for several hours, draining it, and all the different kinds of reboots but nothing helps. I was able to get it into download mode, but then it got stuck in there. I was able to get it back to the other screen and don't know what to do now.
The only thing on the screen is a standing android guy with a blue polyhedron rotating in his belly, and an upload percentage. It always restarts at 91%.
I don't want to mess anything up, because this is a borrowed phone - after my previous two Nexus 4s chucked it in. I ended up having to send the first N4 back to Google and lost everything on the phone, but the other one has a lot of data I really want to keep, so I won't do that again.
Is anyone able to help me with this issue?
Altotude
Hi Everyone,
I wanted to reach out to this group to seek urgent help. I have the samsung galaxy s5 from at&t and it has the latest update of 6.0.1 in installed in september. After that started the issues. My phone got extremely..i mean literally hot while charging and a complete charge never lasted more than a few hours with battery draining like crazy. I thought it could be apps and i disabled location, bluetooth, removed apps that i dont use, stopped some apps that i felt not needed, yet the battery drain and heating persisted. I did a factory reset multiple times and it did not help. I did the wipe cache partition too yet even that did not help. Few days ago another issues started. My NFC enabled automatically and the option to disable it was greyed out and i was not sure on how to switch it off. the last straw was Wi-Fi which got switched off and the option was greyed out with me having no chance to enable it and connect it to Wi-Fi. I was totally flumoxed on what was happening. I reached out to samsung and also at&t and essentially they disowned me saying the phone is out of warranty and they can not help. I still owe 3 more EMI to at&t and i hold a $650 brick technically.
I tried rooting it through "towelroot" but the app said its not compatible with this phone. i tried Odin and run the stock rom but the process was always stuck at connection even though the driver was all identified. I wanted to install the CM13 or CM14 to see if i can get my phone back but without the phone being rooted, i was in no position to run the custom ROM or install the recovery. I have been searching google for the last 2 days to see if there is any method which will help me but i was not able to get any. I knew XDA Developers was a group of members who are experts in helping android users realize the true potential of the smart phones.
Can anyone please help me in resolving the issue. My phone model is SM-G900A and it has the knox and android 6.0.1 update.
Thanks ®ards
KC
Email - [email protected] / [email protected]
Hello,
I have a Samsung Galaxy Note 3, N900A, Android Version 5.0 on AT&T, Baseband N900AUEOC1, Kernal 3.4.0-4335446, rooted.
If I turn the phone off and then back on again or reboot I get a long white scree with the AT&T logo, Android is upgrading... Optimizing app # of 316, then a long time I can use the phone.
I did some online searching, and found some really old posts. I don't mess with the configuration much. I rooted it many months (years?) ago, and can't recall why. I think i wanted a hotspot, but that never worked out for me.
I suspect that AT&T is sending an over the air update and does not like the rooted phone. I searched thee settings in an effort to turn off auto update with no luck. I am hoping for something other than: wipe, reload...
Service Disabler from the Play Store ended up working.
Easy to use and dumped some bloatware while I was in there.
meyen90 said:
Hello,
I have a Samsung Galaxy Note 3, N900A, Android Version 5.0 on AT&T, Baseband N900AUEOC1, Kernal 3.4.0-4335446, rooted.
If I turn the phone off and then back on again or reboot I get a long white scree with the AT&T logo, Android is upgrading... Optimizing app # of 316, then a long time I can use the phone.
I did some online searching, and found some really old posts. I don't mess with the configuration much. I rooted it many months (years?) ago, and can't recall why. I think i wanted a hotspot, but that never worked out for me.
I suspect that AT&T is sending an over the air update and does not like the rooted phone. I searched thee settings in an effort to turn off auto update with no luck. I am hoping for something other than: wipe, reload...
Click to expand...
Click to collapse
Un-Fxed
Well this is a little frustrating. Went on and off with no update process yesterday. Today I rebooted and the 316 updates were optimized. I looked at the service disable app and the AT&T update service was still disabled.
Anyone have any thoughts?
Clearing the cache seemed to help. Let's see if the updates come back over the next few days...
No updates yesterday. Today there are 322 apps to optimizing... Anyone seen and fixed this before?
I started having the same problem 2 weeks ago after updating SU . Looks like they sent out 2 bad updates. Here is a link to the issue. I have been unable to solve it and their recommendations is to reroot the phone.
https://forum.xda-developers.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703
Thank you pinkpanther28. A true smoking gun. I disabled SuperSU and the update issues was gone. Enabled SuperSU and sure enough it came right back. The real irony is that I upgraded to SuperSU Pro to make sure 'Disable Service" had access. For now I will leave SuperSU disabled....
Well so much for the smoking gun. I turned my phone on this morning and the updates issue is back, even with both SuperSU and SuperSU Pro disabled. Does anyone have any ideas?