Hi there,
Last week, I get the OTA from my OWO CSC, it get updated to ZTO and the PDA version is CTCA. Not sure if this is newer or have a big difference from CTC9.
Does anybody here from OWO CSC and with this update experience some issues?.
I have already tried everything, also have received some help in this forum and it helps for few hours and then the problem appears again.
Regarding few points I have tried:
-I have already flashed again CTCA ZTO CSC using odin.
-I have already flashed the previous one, CTC9 ARO CSC using odin.
-I have done a factory reset with the CTCA ZTO CSC using the recovery menu.
Once i finished to reset the phone, i downloaded all appss and configured the phone from 0. Just restored some settings that i have backed up using samsung cloud. The phone works super perfectly for 48 hours and this morning it started again with the constant reboot.
Regarding few points i do have a question first, do you know or does it exist any software that can detect what reboots the phone or any log that track the error that can cause the phone to reboot?
I came from ZTO BTB9 that was from march security patch and till now it never happen to me before with this phone and Odin updates. I did not do and touch anything during update period, did it till the end. IT was just plugged into the charger. The phone finished the process completely normal, after it ends, i start it using and checking the new features. I configured the camera, the keyboard and not much. Not installed any software, just update all apps to the latest from store (samsung and google). The reboot is just random, the first one i detect while running app booster from samsung, but then it reboots without running that app (just reboot again). It looks like a softt reboot or a quick reboot because it get quickly back again but i should put the pin and it loads all again (notification from 0). It does not show the screen that say "samsung galaxy note 10+ powered by androird", just the "Samsung" logo screen and then lock screen. I did not reboot it as soon as it ends updating. The cache wipe did it just this morning after i detect it reboot over the night. It reboots like 6 time already. Since the previous one to last one have passed 3 hours but the very first reboots occurs between 20 or 10 minuts from each other. Now the reboot happen every 1 minute.
It looks like there is a problem somewhere and it sounds like a software problem. But i'm trying to know if it is a build problem or personal problem.
Now i have the phone running in SAFE MODE and it is fine, so for sure is something in system that try to synch, update or w hatever in background that crash the phone. I have the same apps as always installed, no new apps added so far
Thanks for the time.
Regards.
Yamil.
Related
Hello everyone I'm Italian and I have problems with my stock galaxy tab 3 7.0 T211.
Often when I turn on the tablet the process systemui crash, then while using, many other app randomly lock, and I must open them 2-3 times to be used in normal way.
It happens also that the tablet will block for a couple of seconds and restart it automatically, but restart is not normal but is much faster.
I tried to do a factory reset from recovery, I installed with odin before the stock firmware 4.1.2 (XXAMK6) and then the 4.4.2 (XXBNI1), but in all cases nothing, the tablet gave me the same problems, particularly the problem of the process are terminated .
It also happened that during the first configuration (language, time, wifi network password, etc.) the configuration process crash, and I had to start all over again. All this even though I had just installed the firmware with odin.
I do not know what to do, it seems to me absurd that despite I start from a clean base and I use odin to flash a stock rom the tablet gives these problems, I do not understand what could depend.
I hope you can help me, any help or advice is welcome.
Many thanks to all!
Been there, done that
midnighteight said:
Hello everyone I'm Italian and I have problems with my stock galaxy tab 3 7.0 T211.
Often when I turn on the tablet the process systemui crash, then while using, many other app randomly lock, and I must open them 2-3 times to be used in normal way.
It happens also that the tablet will block for a couple of seconds and restart it automatically, but restart is not normal but is much faster.
I tried to do a factory reset from recovery, I installed with odin before the stock firmware 4.1.2 (XXAMK6) and then the 4.4.2 (XXBNI1), but in all cases nothing, the tablet gave me the same problems, particularly the problem of the process are terminated .
It also happened that during the first configuration (language, time, wifi network password, etc.) the configuration process crash, and I had to start all over again. All this even though I had just installed the firmware with odin.
I do not know what to do, it seems to me absurd that despite I start from a clean base and I use odin to flash a stock rom the tablet gives these problems, I do not understand what could depend.
I hope you can help me, any help or advice is welcome.
Many thanks to all!
Click to expand...
Click to collapse
This happened with me too but only after updating to KitKat 4.4.2 with Odin, I tried a couple of times and even used firmwares for other regions (mine is international version unlocked so it should work with no problems), I then Initialized the device using Kies 3 to the latest firmware available for my region for the SM-T211, it went OK, I still get crashes, I mean the problem hasn't totally been solved, but it's much much less crashes now than before when device was flashed with Odin (may I say that it was the same stock rom with the same build number from both Odin and Kies 3, still the one from Kies 3 was much more stable)
I troll here a lot for information, as I fix devices for friends for free, so if I'm posting up for help here it means I've run out of internet solutions and energy. Mods, I've spent a week searching and reading through threads, no single thread solved my issue which is why I'm posting up; please move the post if it better fits elsewhere.
The Phone: T-Mobile Samsung Galaxy S4 SGH-M919
Current Firmware: M919UVUFNK2 Stock T-Mobile (M919UVUFNK2_M919TMBFNK2_M919UVUFNK2_HOME.tar.md5)
Current Bootloader: M919UVUFNK2 (also verified with getprop ro.bootloader)
Current Baseband: M919UVUFNK2
PDA: M919UVUFNK2
Hardware Revision: REV0.7
Current Android Version: 4.4.4
Current Kernel: 3.4.0-2437203 [email protected] #1 Mon Nov 17 19:20:38 KST 2014
Current Build: KTU84P.M919UVUFNK2
Device/Product: jfltetmo
CSC Code: TMB
Firmware CSC: (blank)
Active CSC: TMB
Product Code: SGH-M919XXXTMB
GPS Works: Yes, verified
BT Works: Yes, verified
WiFi Works: Yes, verified (all bands, secure and unsecure)
Sound Works: Randomly, causes issues. When it does work it is crystal clear
Network Radio Works: Yes, verified
Battery: 2 new batteries, one OEM and one Rav
IMEI/ESN: Free and clear, verified to be a TMO device by TMO
Error Messages Seen (if any): "Process system isn't responding"
Odin Versions Used: All 3.x up through 3.10.6
Alternate ROM Tries: Candy5 v2.1.0 jfltetmo
Alternate Recovery: TWRP 2.8.4
Odin "Double-Flash w/o Auto-Reboot" Used: Yes, multiple times (even triple and quadruple times)
FSCK Used: Yes, no issues detected
The Story:
I was presented with a challenge, fix a phone which just came back from the manufacturer. Sadly, not the first time I've had to clean their mess up. It was sent in under warranty because of screen bubbles, and returned with an OEM LCD, and a new battery. And, before anyone asks, the manufacturer refuses to take a look at it again. It's now out of warranty (by a month or so) and they said it worked fine when it left their hands. Yes it did, but only for a few weeks. From the time they shipped it back out until it crashed, nothing had changed on the user's end, no software additions or anything.
Appeared to only need re-flashing. After it booted and reached the unlock screen it seemed fine. If you unlocked the phone, it would immediately freeze up. When it did this it would usually be frozen for about a minute or two and then reset itself. Most of the time it would return to the lock screen, sometimes it would hang on the T-Mobile flash screen. One time I was able to get in but once it started syncing messages it locked up again. It had the latest firmware (M919UVUFNK2).
I used OEM recovery to wipe the cache and return it to factory fresh. It quickly booted up to the lock screen and everything seemed fine, I swiped and moved around the menus like normal. Sound was random though, sometimes it would work, sometimes not. Wifi, Bluetooth, Data .. everything worked like it should. I began to notice, however, that anytime something tried to use sound (ringer, notification, changing the volume) the system would lock up and stutter somewhat. Eventually it got to the point where it would just hard-lock every time sound was used. So I wiped it fresh and clean again--I wiped it several times in a row infact, just to be sure.
Again, everything seemed fine but sound would be random, and sound always seems to trigger issues. A few times I immediately muted all audio as soon as I factory-reset and rebooted the phone, in order to see if that mattered. One of those times it locked up within 2 minutes of use, and the other times it locked up eventually. It seems to last longer when audio is muted, but I wouldn't correlate that directly because it's not easy to scientifically prove.
In order to see what might be going on I went to install CatLog from the sdcard, but that needs root to work properly. I tried using SuperSU and CF-Auto-Root (jfltetmo/sghm919) to no avail. What happens when either of these methods are used: They run flawlessly and say everything is good, but upon rebooting the phone locks up at the Tmo flash screen. No matter what I do, rooting causes it to lock, and when it's locked the phone gets ultra hot as if the CPU is stuck in a loop.
After re-flashing the stock rom umpteen times and getting the same issues, I tried finding a PIT file to no avail. Gave up on that. For giggles I tried previous TMO stock roms. I realize that you normally can't do this, and some advise against it, but when you're up a creek it sometimes doesn't hurt to try, and I've had this work on other phones in the past. I tried ll of them actually, in chronological order of release so as to simulate upgrading:
These wouldn't flash to the phone at all:
M919UVUEMK2
M919UVUAMDL
These flashed/took and actually worked without an issue, they just all eventually locked up like NK2:
M919UVUFNH7
M919UVUFNB4
M919UVUAMDB
I re-flashed NK2 another 20 times or so, still producing the same problem. Decided to try 5.x out in case that might solve something. So far I've only tried 1 rom for it, Candy5. Several times I was able to get it to boot and use it just fine. One time it actually lasted almost 2 days. Since I'm talking about Candy, the folks did a fine job with it, I really like the layout/aesthetics. Free plug there.
Sadly, it crashes under Candy as well. Same problem as with NK2. Boot crashes, boot loops, sound issues. I've since sucessfully reverted to NK2. Presently it's sitting on my desk receiving emails, downloading apps and working just fine. I have all audio disabled. It's been going for about an hour. (edit, right as I posted this it crashed and rebooted itself)
My Theory:
Theory 1: The reason I want to re-PIT is because I theorize something in the filesystem, somewhere, has taken an epic dump. The more the phone is used the quicker it crashes--this happens almost every single time, and battery/CPU temps are normal. After a certain amount of use/time, the phone craps itself. Storage use isn't always sequential, so something is mapped as good when it isn't, and when it's put to use it dies. One way I correlate this with sound is that perhaps the system doesn't cache the soundbyte, so when it goes to read the file it craps.
Theory 2: Same as above, but instead of storage, the problem is bad RAM causing the same data corruption/issue. No easy way to solve this. I will be stress-testing the RAM chips tonight. Update: I stress-tested the CPU and RAM using some available apps, and ran it for quite a long time. Didn't seem to cause or exacerbate the issue any.
Closing:
Anyone have any ideas? I thought maybe re-PITing the thing may help, but couldn't find any files on it. The only other TMO S4 I have access to is a friend's who doesn't want it rooted (a requirement to read a PIT file I've been told). I appreciate any advice/input on this matter. Would be nice to get this thing going.
Did you pay for the repairs using a credit card? If so call the card company and contest the charge since it wasn't fixed properly.
It's not my device, and as stated in the post, it was repaired under warranty at no cost to the consumer.
Hello! I am going to describe my issue with 2 years old nexus 5x which is restarting randomly.
It all started a couple of days ago when my phone started to ask me to enter PIN code. That happened randomly. After entering the code my phone worked completely ok.
But yesterday it started restarting on its own. The restart happened once, than I suddenly got a message before loading screen saying: "Your device is corrupt. It can not be trusted and may not work properly".
Today my Nexus restarted around 10 times. These restarts do not depand on phone usage, since it is restarting randomly (when charging, when not charging, when using it, when screen is off).
I decided to clear cache partition factory reset it and update apps. Unfortunately that did not help, since my phone is restarting even more frequently. Normally it freezes for 5 seconds and than restarts. Sometimes I still get the message: "Your device is corrupt...", but not always.
My Nexus has not been modified (it is not rooted and it is running android 8.1 with november security patch). Also apps have been installed only from play store and not from unknown sources.
I would really need your help. Has anybody experienced any similar issues or does anybody know what could cause the restarting?
Thank you in advance.
@tic_tac7: probably it's a conveniant variant of BLOD. So save everything important on another storage immediately.
This message comes from bootloader. Because the reboots happen also during standby, it's imo useless to flash a kernel which lets the big core sleep, but that's a misty guess. Nevertheless you could try the latest ABC-Oreo (needs TWRP by ADB) without anything more for testing. If reboots are going on > bin.
rp158 said:
@tic_tac7: probably it's a conveniant variant of BLOD. So save everything important on another storage immediately.
This message comes from bootloader. Because the reboots happen also during standby, it's imo useless to flash a kernel which lets the big core sleep, but that's a misty guess. Nevertheless you could try the latest ABC-Oreo (needs TWRP by ADB) without anything more for testing. If reboots are going on > bin.
Click to expand...
Click to collapse
Thank you for your response. Is installing a custom rom the only possible soultion?
No. It's no solution. It's a vague trial.
tic_tac7 said:
Thank you for your response. Is installing a custom rom the only possible soultion?
Click to expand...
Click to collapse
If you are original owner of phone for up to 30 months, go here and let LG fix (or attempt to) the phone. Mine required two repairs. If you are not in the US, check with LG support in your country.
Hello all,
My Note 10+ notified me that the Jan update is available and as usual I chose to install it. However, it rebooted and now won't boot past the Samsung logo. It gets past the initial Powered by Android screen to the "Samsung" logo where it dims then suddenly reboots to the Powered by Android screen again. It does this a second time then eventually goes to a screen saying that the phone couldn't start normally etc.
I haven't backed up my Whatsapp or more crucially my 2FA recovery codes for some important services.
Is there any chance that I can rescue my phone without factoring reset?
Could installing BSL7 (December build) fix this?
I have the same issue
What Model 10+
What model Note 10 do you have?
Cheers
UK Samsung dual sim model
SM-N975F/DS
Update:
Tried installing BSL7 and things got worse in that it wouldn't even attempt to boot the system. Reinstalling BSLD put it back in the current state which is a bootloop with a delay that allows me to run some adb commands before it reboots.
Guys I'm getting desperate here. Should I be asking elsewhere on the forum?
I found a new build N975FXXS1BSLE with CSC of THL. Since downgrading didn't seem to work, would flashing everything from the seemingly newer BSLE build along with the HOME_CSC_OMC_OXM_N975FOXM1BSL7 from BSL7 cause any issues? I've never mixed builds like that.
I'm thinking the OS and everything else will be from BSLE but CSC will be from the BTU build.
Please help
I had no issues at first, but when I tried to turn on Secure Folder it started the bootloop, I partially solved it by disabling and clearing secure folder app data and cache, can you guys try that and confirm?
crzr said:
I had no issues at first, but when I tried to turn on Secure Folder it started the bootloop, I partially solved it by disabling and clearing secure folder app data and cache, can you guys try that and confirm?
Click to expand...
Click to collapse
Dammit Samsung. I had Secure Folder enabled before updating. How on earth do I disable it now without factory resetting?
Update:
So I flashed the Thai build and it went as far as showing a small window "updating apps xx of xx" but when it finished it bootlooped again so I reverted to BSLD and it did the same but is still bootlooping.
Hello everyone.
I'm currently with an annoying issue:
My Samsung Galaxy S9 (non-rooted) is randomly rebooting only while idle.
Whenever I'm charging, playing or perform any interactive activity, the phone works as it has been working for the past 2 years.
As soon as I left it idle for a while, it simply reboots. Usually do not take more than an hour for the reboot to happen.
Already performed a facory reset, cleared cache, force shutdown (power + volume down), worked on safe mode and nothing seems to lead me to the root cause.
It started on tuesday (December 29th @2020).
Thanks in advance,
Caio
I have had a similar problem for a long time. Sometimes my Galaxy has given to restart without stopping as far as it wants ... Once it happened to me that for a day it did not stop restarting after installing the Google assistant, only by entering safe mode and deleting it I could solve it .. . And one of the last was that I changed the CSC and the mobile just did not stop restarting, even after downloading and reloading it, I deleted and formatted absolutely everything and I could not use the mobile normally ... After several tests I realized that it restarted after unlocking, so I deactivated the passwords and fingerprint but it did not work, so it occurred to me to install another launcher and problem solved. I have no idea why this is happening to me, maybe is an error in the internal memory due to a bug in the firmware (?)... Anyway, I had read some time ago that there were similar problems caused by a GPU failure in the Snapdragon models, but I no idea.
Renos_Z said:
I have had a similar problem for a long time. Sometimes my Galaxy has given to restart without stopping as far as it wants ... Once it happened to me that for a day it did not stop restarting after installing the Google assistant, only by entering safe mode and deleting it I could solve it .. . And one of the last was that I changed the CSC and the mobile just did not stop restarting, even after downloading and reloading it, I deleted and formatted absolutely everything and I could not use the mobile normally ... After several tests I realized that it restarted after unlocking, so I deactivated the passwords and fingerprint but it did not work, so it occurred to me to install another launcher and problem solved. I have no idea why this is happening to me, maybe is an error in the internal memory due to a bug in the firmware (?)... Anyway, I had read some time ago that there were similar problems caused by a GPU failure in the Snapdragon models, but I no idea.
Click to expand...
Click to collapse
I already use Nova Launcher, so I dont think this will fix my problem. Now its taking more time between rebooting cycles buts its still there.
I guess my last attempt will be to flash a stock ROM and see if it works.
CaioBomani said:
Hello everyone.
I'm currently with an annoying issue:
My Samsung Galaxy S9 (non-rooted) is randomly rebooting only while idle.
Whenever I'm charging, playing or perform any interactive activity, the phone works as it has been working for the past 2 years.
As soon as I left it idle for a while, it simply reboots. Usually do not take more than an hour for the reboot to happen.
Already performed a facory reset, cleared cache, force shutdown (power + volume down), worked on safe mode and nothing seems to lead me to the root cause.
It started on tuesday (December 29th @2020).
Thanks in advance,
Caio
Click to expand...
Click to collapse
reflash firmware via Odin. gert FW(firmware) from sammobile.com/firmware and use SamFirm to download, as it downloads 4x faster than from thr site directly. When flashing, use the HOME_CSC vs just the CSC file, as the csc factory resets whereas home_csc keeps your files and settings etc etc. If that doesnt fix it, you have a hardware issue(IMO, at least, and ive been rooting samsungs for a decade). If you have a hardware issue, id get it as good as i could and use the trade-in specials sammy has going