Lots of us have been frustrated with the latest updates negatively affecting the Adaptive Fast Charge and mabe some other features. To be blunt , I have tried everything imaginable: Wipe cache partition, numerous reboots, failed attempts to fully root the phone (got to lollipop downgrade, no wifi) Then bricked it. How aggravating of an update experience!! Well, this is what finally worked for me and I believe for all. Back up your phone, Use the Samsung Smart Switch on your PC to access the phone, select "more" in upper right corner, emergency software recovery, initialization, device initialization. This will wipe the current flash and reinstall. I dont recommend using the Verizon update assistant to do this since that is what caused the problem. I believe the software package is too big to install the way updates are usually done, causing a file to not load fully. My phone is Fast Charging again after doing this and hopefully will continue to do so. Samsung should be looking into a possible patch to make sure all good.
If you tried and failed at fully rooting like I did and bricked your phone. Plug into your PC and use the Verizon upgrade assistant to repair the phone. It worked like a charm. Smart Switch wouldn't recognize the phone in this state and Odin would not put the lollipop back on as planned, so no root. If I would have known all the extra steps required to root in advance, I would have skipped it entirely. There really isnt an easy way to root these.
Update: It has been a couple days since the reflash, my phone is back to slow charging with fast charge working intermittently. Looks like a software update/patch is going to be the fix. Call your service provider and complain that we want this issue resolved ASAP.
Related
Hello all,
I just received my shiny new HOX yesterday and it was working very well at first, however last night I updated it to the latest firmware (with Sense 4.1) and now it will not connect to the mobile network at all (no bars, won't find any networks when I manually search). I have noticed that it seems to be stuck in airplane mode.
Under airplane mode in the settings page it says "off", then a few seconds later it will say "turning off...", then it will go back to saying "off" and then back to "turning off.." and so on. I think it must be a bug in the firmware because I have tested the sim card in another phone (worked fine), and it was working fine before the update.
The only way to see if it is a bug in the firmware (as far as I am aware) would be to install a different ROM. However, I cannot find any way to install a new ROM (custom or stock) without unlocking the bootloader and therefore voiding the warranty (which I don't want to do in case it turns out to be a hardware issue).
I should also add that I could return the phone, but I would like to leave that as a last resort because I live in the middle of nowhere and trying to post stuff if a pain in the ass (and expensive).
I have also tried both a hard and soft reset, with no luck.
This is my first HTC device so I don't really know what I'm doing (although I have plenty of experience rooting and flashing my S2)
Any suggestions would be greatly appreciated
same prob
i've the same problem since the last update. hope it will fixed soon.
ms141289 said:
i've the same problem since the last update. hope it will fixed soon.
Click to expand...
Click to collapse
I'm glad I'm not the person having this problem . Does anyone know if it is definitely a firmware issue? (I might feel more confident about flashing a custom ROM if that's definitely the problem)
Anybody?
Maybe something went wrong with the OTA flash?
First thing HTC will do is flash the RUU to ensure it's back to stock. It will delete all your data, but it's worth a go.
You can use adb backup.
I have been having issues with my Note3 ever since the kit kat update back in April. It worked flawlessly on Jelly Bean and I had no issues for over 3 months. I updated to kit kat via Kies with everything completely stock. Since then I get completely random reboots, it could happen when launching an app or even unlocking the screen, and it happens 2 or 3 times a day. So far I have tried 2 factory resets, clearing dalvik cache, and replacing the battery with an Anker replacement. I have tried turning off auto-updating of apps, and turning off wifi scanning. I have also tried running the phone with no apps installed. So far nothing has worked.
I have read several posts with people blaming the stock kernal for these reboots, but there is no definitive solution to this problem. I am looking for any and all help the community has to offer.
Some additional info:
Running latest stock rom- rooted via effortless method
Stock Recovery
Knox is still 0x0
No sd card in phone
Since you have no issues doing a factory reset, I recommend the following:
1.). Backup all the data you need
2.) Download the newest carrier available firmware for you from sammobile.com
3.) Flash via Odin
4.) Once finished and phone has rebooted, return to stock recovery and perform another data wipe
That will 100% fix your issues, sounds like maybe a corrupt system partition or libs
icenight89 said:
Since you have no issues doing a factory reset, I recommend the following:
1.). Backup all the data you need
2.) Download the newest carrier available firmware for you from sammobile.com
3.) Flash via Odin
4.) Once finished and phone has rebooted, return to stock recovery and perform another data wipe
That will 100% fix your issues, sounds like maybe a corrupt system partition or libs
Click to expand...
Click to collapse
Thanks, I'll give this a try. Last night I uninstalled a bunch of bloat ware with titanium backup to make sure it's still not an app issue. If it reboots again I'll reflash the firmware. Since I'll. Be flashing stock it shouldn't trip knox right?
No, latest firmware complete stock will not trip Knox, as long as you're either doing a parallel upgrade NF9 > NF9 or NB4 > NF9. A downgrade will either fail or trip.
For anyone reading this, i tried to reflash the stock nf9 kernal to see if that was the issue, but i got a restart about 4 hours later. I am going to reflash the firmware via odin and report back.
I am having this issue for a long time. i have done everything, and finally i gave up, as i think it is a hardware issue. what make me confuse is the problem start since the day i upgrade to kit-kat. with every firmware come out i have a new problem. the latest "NF9" my phone just hang and black screen untill i press the power button for 30 second, then will restart. what make crazy is that it shuts off at night, and when i woke up i miss the alarm.
I'm sad to report that the reflash didn't work. I reflashed the NF9 firmware using odin about 4 days ago and it was fine for awhile, but I got 2 reboots today. I'm not sure what is causing this, but I am still open to suggestions. I don't think its hardware related since it didn't do this before kitkat. I still have my samsung warranty until february I believe, so if worst comes to worst then ill have to send it in, but i'm not sure what they will do about it.
The only thing I havent tried is replacing the sim card. Could a sim card cause a reboot issue like this?
i have already done it, even the SD card, still same problem.
Is there some kind of log feature in android that logs crash events or errors somewhere so i can maybe figure out what the problem is?
by the way i think i have solve my problem by updating busybox and supersu. i had to install busybox to system/xbin. and since that day i haven't encounter any restart or freez. almost 2 week. i hope that fix your problem as well.
makki666 said:
by the way i think i have solve my problem by updating busybox and supersu. i had to install busybox to system/xbin. and since that day i haven't encounter any restart or freez. almost 2 week. i hope that fix your problem as well.
Click to expand...
Click to collapse
I do not have busybox installed, and SuperSU is up to date. Also, the restarts happen with or without root ie without SuperSU. I still dont think its an app problem.
Just an update for anyone reading this. I have installed SetCPU to manage cpu clock speeds. I have had it installed for about a week and have not had an update with my custom profiles. It seems the restarts occur when cpu speed is at about ~675MHz. Not sure if its hardware or software yet. Any help is appreciated!
Update. I sent my phone in to samsung for repair. It looks like they just reflashed the firmware. After having it up and running again for 15 minutes the phone rebooted again. I contacted samsung and they recommended sending it in again. I'm not sure if it's worth it to send in again or if i should break my warranty and flash a custom rom. Any suggestions are welcome!
I get restarts because the modem crashes... its a known issue apparently
gtharea said:
I get restarts because the modem crashes... its a known issue apparently
Click to expand...
Click to collapse
I cant believe its taken over a year for this issue to get fixed. Im almost positive its a software issue since it never happened on jelly bean. It's strange that not a lot of people have this problem though. A lot of people must have already flashed custom roms I may send it in again since I still have knox 0x0 and see if they do anything else besides reflash the firmware this time. If they only do a reflash again i will just flash a new rom and hopefully everything will be fixed
Final Update:
I sent my phone back to Samsung, apparently my issues were a hardware problem. This time they replaced the "PBA assembly" aka the mainboard. I have had the phone back for almost two weeks without a single restart. I believe my restart problems are over. I hope this information helps anyone with similar issues. I would recommend sending it to Samsung for warranty repair if you are still under warranty. :good:
_bhaves_ said:
Final Update:
I sent my phone back to Samsung, apparently my issues were a hardware problem. This time they replaced the "PBA assembly" aka the mainboard. I have had the phone back for almost two weeks without a single restart. I believe my restart problems are over. I hope this information helps anyone with similar issues. I would recommend sending it to Samsung for warranty repair if you are still under warranty. :good:
Click to expand...
Click to collapse
I had the same problem but already tripped knox so iffy on sending it in. Funny thing is I did the external sd write fix and the phone has not rebooted since, going on 3 days.
meoshe said:
I had the same problem but already tripped knox so iffy on sending it in. Funny thing is I did the external sd write fix and the phone has not rebooted since, going on 3 days.
Click to expand...
Click to collapse
I would get reboots even without an SD card put in the phone, so I don't think that would have helped me. I havent had a reboot since I've had the device back
I'm currently running Android 5.1 Build H81010e.
Since last week, my phone has alerted me that a software update is available. I start installation, the phone resets, and the notification comes right back after 2-3 minutes. It's been in an endless loop for at least the last week. Now my phone resets every 3-5 hours attempting to force the update, but it doesn't seem to ever install.
Anyone else having this problem on AT&T? Is my build the most recent? Any ideas on how to fix it?
If you want root, don't take the update.http://forum.xda-developers.com/g4/help/how-to-prevent-updates-g4-t3148650
If you don't care about root, go to Settings > Smart Cleaning and use the cleaner. It may remove the update file and let you download it again.
Since AT&T blocked recovery mode, there's no easy way for us to clear the cache, so you may need to factory reset to get the update to download again.
Apologies for resurrecting an old post however this is the closest forum topic I can find. I have a G4 and I have the same issue as above. I keep getting a notification of a software update and when I try to install the update it just restarts and then 2 minutes later I get the same notification of an update. It's an endless circle lol. I have tried smart cleaning twice and each time I check for a system update and I get the original notification and the endless loop begins again. Is there anything else I can do to update my device? I'm not keen on performing a factory reset or rooting my device if at all possible. Also I'm not with AT&T. I'm with an Australian carrier.
Many thanks
So like many of you, I have been really frustrated with T Mobile that they are the only carrier not to upgrade their Note 2 to Android 4.4, and they probably never will. There are more an more apps that I cannot run, some of which are important to me. So I gave up with calling T Mobile, and struck out on the custom ROM trail, seeing that CM has a 4.4 mod for this phone. After rooting and attempting to unlock (not necessary) and changing to custom recovery, I managed to get the CM mod loaded and running, after many hours of learning by trying everything, I got the phone running on the CM 4.4 mod, only to find that I could not make any calls, as there are no mods, anywhere, that support T Mobiles WiFi calling. I guess T Mobile uses that because their network is weak, but hey, I have used Sprint, AT&T and Verizon over the years, and every network has holes, especially inside buildings. It so happens that both where I work and at my home is spotty, so I cannot survive as a phone without WiFi calling. After all, for all of the bells and whistles, a Smart Phone is first and foremost a Phone. So after all that, I started on a new trail, unrooting and installing a stock mod.
There are lots of help out here that tell how to unroot and go back to stock, and they are all trash, every one of them. I tried stock mods from several sources (SAMMOBILE and others) and only found two out of six update versions that even functioned on my phone, and only one of those actually worked like it should, and that was the very first 4.1.1 version T889UVALJ1 that came with my phone years ago. No LTE and more apps that would not install at this level. I was hoping to at least get to the T889UVCOH4 version of 4.3, which is the current latest version from T Mobile.So here I was, an older version of ROM on my phone, no LTE, Flash counter not at zero, and Knox telling the world the phone was modified, excluding any chance of help. Why in the world did I even step into these problems. And then I made a startling discovery.
As I tried to at least restore the data backup I did before this whole thing started by using Smart Switch from Samsung, I found that not even that would recognize my phone because of the older version of android so I could not even get to my backups. When I got the phone it used Kies, but with the 4.3 version of android, Samsung changed over to Smart Switch. So at that moment I felt I was completely screwed. Then I saw the little "More" button on the Smart Switch dialog that was telling me my phone was not supported, and I clicked it. It brought me to some other options, and one was emergency recovery, which allowed for an initialization after a failed upgrade. I did not expect much, as my phone was not supported anymore, but I could not see any other option, so I chose to initialize the phone for recovery.
Well guess what, everything ran perfect, and when the process was completed, my phone was just like new, no flash record, no Knox report, a completely authorized phone. It was if I had never rooted it at all, and I had flashed a dozen ROMs. So for everyone that has a bricked or soft bricked Samsung phone or find out the custom ROMs are not what you were hoping for, all you need to do to get it back is install Samsung's Smart Switch on your computer and click the little "more" button on the screen and reinitialize your phone. It will be like the whole rooting and ROM experience was a bad dream, And yes, the backup did load when I was finished. It is that simple. This should work for any Samsung with Android 4.3 or higher on any carrier.
So about a few years ago, I tried to root my galaxy note 4 (n910aucu2doi3), but I guess it rejected the root because it instantly bricked my phone, to the point where I had to completely wipe it using android recovery. The only way to get my operating system back was to download it online and install it through my PC (I had to find the exact version for my phone as well, 5.1.1 at the time, because it rejected every single other version).
Everything seemed to be working fine, except that I couldn't install software updates on my phone anymore. It was permanently stuck on 5.1.1. It was a bit of an annoyance but I didn't think much of it at the time.
Fast forward to now, and I'm getting several signs that my OS may be corrupted. My phone is constantly freezing, crashing and restarting. Maneuvering through applications causes the phone to freeze for a few seconds before either restarting or crashing the app. I want to say it's definitely a software issue, but I did install a new battery recently and it was working fine for a few weeks, could that be the issue?
If not, I want to start over, but I'm not sure how, and I don't know if it's safe to do a factory reset on this OS. Is there anyway I can get a fresh stock version of an android OS that can also update?
Any help is appreciated, I'm pretty much desperate.
I manually updated to 6.0.1 with the help of this thread https://forum.xda-developers.com/note-4-att/general/updates-thread-t3663943
It seems to have fixed the issues so far, and my phone can automatically update again