Database Develop

Lollipop causing phone to turn off

Idk what's the problem with Samsung phones and updates. I had the same problem with my Note 3 when KitKat got released, I had to get a replacement phone. Lucky for me the replacements Note 3 didn't have the update on it. However I wasn't so lucky with the Note 4.
I accidently hit the update on my notifications when I was half sleep.
Anyways.
Every since Lollipop been installed on my Note 4, it has been a nightmare from hell.
When I installed it on my original Note 4, I kept having my keyboard become unresponsive. Force close on multiple apps (stock Web, camera, calender, and more).
I called T-Mobile to see if they could send me a replacement. They "tried" to fix it, saying that I should do a factory reset and clear cache , which I already tried before I called numerous times.
Finally they said they said they were going to send me out a replacement phone.
I also asked if anyone have been complaining about Lollipop they said no, they were totally oblivious to Lollipop having any kinks (as always ). It's crazy they said that because I have read over 100 post bashing the new update.
I received the Note 4. I turned the phone on and Lollipop was already installed. I called T-Mobile and asked why was Lollipop installed on my replacement, they informed me that they are sending out the phones with Lollipop, and assured there would be no problems with it.
With in the first hour, my phone would turn off and not turn back on. I knew there was nothing wrong with the battery because it was on 90% and it worked flawless with another phone. So I drained all the electricity out the phone and put the battery back in. That worked, but it did over 20 times within that day. I called T-Mobile again , they told me I would have to go to a store and see if they could diagnosis the phone.
The next day I went to the store, everything came back clear on the diagnosis, but they could see it turn off randomly.
I called customer care and explained the situation and told them I need a replacement.
Now I am waiting on a replacement. If this one don't work, I think I will have to get on whole different phone. I'm on the verge of getting a flip phone because I know that I don't want to have an iPhone.
Anyone having these issues with the update Lollipop?

I've never heard about an update getting positive reviews from users, most get bashed.
Fortunately I don't have those issues, nor have I had any with updates. Have you tried to odin the stock firmware? That's all I can really think of.

MajorTom_ said:
I've never heard about an update getting positive reviews from users, most get bashed.
Fortunately I don't have those issues, nor have I had any with updates. Have you tried to odin the stock firmware? That's all I can really think of.
Click to expand...
Click to collapse
It seems like I tried everything. I haven't tried that though. I will try that today, if my phone ever boots up.

W0man09 said:
It seems like I tried everything. I haven't tried that though. I will try that today, if my phone ever boots up.
Click to expand...
Click to collapse
As long as you can get it into download mode something may be possible.

Odin to stock lollipop, factory reset / data wipe.
Additionally, I would consider a custom rom.
..........
If you really like kitkat better you could also Odin to stock kitkat, factory reset / data wipe.

MajorTom_ said:
As long as you can get it into download mode something may be possible.
Click to expand...
Click to collapse
Lol thanks for the help. I can't even get it to turn on, to get it in download mode. ??
. Now I'm just waiting on T-Mobile to send the replacement.

Samsung Pass declares my never been rooted phone to be rooted and refuses to open

Has anybody seen this? My phone has never been rooted, had it since new. I double checked with root check and knox check from the play store to confirm. Samsung Pass gives the error shown in the attached photo. Samsung Pay works perfectly. This started somewhere around Thursday evening 1/31 and Friday morning 2/1. I went to log in to an app and Pass told me that it required an update before it could work. I went to the galaxy app store and found there were no updates, so I went to the samsung pass app directly and got this.

Official rom?

Completely official, no modifications whatsoever.

Any app installed that can confuse it? Then I would try wiping cache partition followed by trying if it works in safe mode followed by uninstalling updates for it, which will reset it losing all your pass data.

phil.culler said:
Has anybody seen this? My phone has never been rooted, had it since new. I double checked with root check and knox check from the play store to confirm. Samsung Pass gives the error shown in the attached photo. Samsung Pay works perfectly. This started somewhere around Thursday evening 1/31 and Friday morning 2/1. I went to log in to an app and Pass told me that it required an update before it could work. I went to the galaxy app store and found there were no updates, so I went to the samsung pass app directly and got this.
Click to expand...
Click to collapse
Where did you purchase your phone from ? Playstore apps tell me knox is not tripped but i am rooted!
Turn off the device. While device is off, Press the Power button, Volume Down, and Home buttons and hold until you see a Warning screen, press Volume Up (continue). At the top left of the screen you'll see "Knox Warranty Void: X (0x000X)" where X is the number of times Knox has been tripped

N1NJATH3ORY said:
Where did you purchase your phone from ? Playstore apps tell me knox is not tripped but i am rooted!
Turn off the device. While device is off, Press the Power button, Volume Down, and Home buttons and hold until you see a Warning screen, press Volume Up (continue). At the top left of the screen you'll see "Knox Warranty Void: X (0x000X)" where X is the number of times Knox has been tripped
Click to expand...
Click to collapse
I purchased it brand new from tmobile and broke the seal myself. Knox has never been tripped. Status screen shows WARRANTY VOID:0X0.

If knox tripped, samsung pay won't work anyway so maybe software problem. Try reset like @raul6 said, if still not working try hard reset maybe

Are you running thenfirmware the device cane with or have you flashed that TMB U1 firmware that is available on this forum and from some of the firmware image sites? The TMB U1 is not an actual official firmware and is a combination firmware, which breaks updates and gives similar error messages even though the device isn't rooted.

Any solution for this? My wife's phone will not open Samsung pass or Samsung health. Both say phone is rooted. Knox is 0x0 and software is official. She wouldn't know where to start to root her phone.
Samsung Pay works fine.

Bo21 said:
Any solution for this? My wife's phone will not open Samsung pass or Samsung health. Both say phone is rooted. Knox is 0x0 and software is official. She wouldn't know where to start to root her phone.
Samsung Pay works fine.
Click to expand...
Click to collapse
Call Samsung? ?

Not yet. Either calling Samsung or going to take it to a Best Buy for the Samsung support there. Just seeing if this was solved before I lose a few hours of time.

Did a factory reset and all seems to be fine.

Glad some others are having this concern. I've contacted Samsung twice about this via chat and have been told to send it in for repairs with a 2 week turn around (not gonna happen ) and more recently that I should take it to a service center 20 miles away and they have the tools to fix this. When I asked if this is a known issue, they immediately denied it but assured me the service center would have the tools to fix the problem they deny having.

phil.culler said:
Glad some others are having this concern. I've contacted Samsung twice about this via chat and have been told to send it in for repairs with a 2 week turn around (not gonna happen ) and more recently that I should take it to a service center 20 miles away and they have the tools to fix this. When I asked if this is a known issue, they immediately denied it but assured me the service center would have the tools to fix the problem they deny having.
Click to expand...
Click to collapse
Considering that the fault appears to be a software issue, I suspect the service centre is just going to wipe, flash the latest OS version and hand it to you back, so yeah, they should have the tools. Also it doesn't sound like they denied the existence of the issue you're having, just that it's not a "known issue".

...

hello same pb here, i re up the topic
https://photos.app.goo.gl/Zk28rduw4VQ1Y5VA7
received reconditionned phone S9
knox is ok, but samsung pass / security folder / health, don't work
any idea ?!?
did they "modify" the knox ?!?

Bo21 said:
Did a factory reset and all seems to be fine.
Click to expand...
Click to collapse
Yotitchy said:
hello same pb here, i re up the topic
https://photos.app.goo.gl/Zk28rduw4VQ1Y5VA7
received reconditionned phone S9
knox is ok, but samsung pass / security folder / health, don't work
any idea ?!?
did they "modify" the knox ?!?
Click to expand...
Click to collapse
factory reset the phone. its a software issue.

done 2 times then a third time while reading this topic ;_;
is it possible now to put back a knox to 0 after root ?!?

Yotitchy said:
done 2 times then a third time while reading this topic ;_;
is it possible now to put back a knox to 0 after root ?!?
Click to expand...
Click to collapse
no, Knox cannot be reverted back to 0. you have to live with that.

Munawar Mehmood said:
no, Knox cannot be reverted back to 0. you have to live with that.
Click to expand...
Click to collapse
read previous post... my knox IS 0 but samsung pass says phone is root

S10 Camera Failed with a Twist

Hey all, searched the forum but 0 results for "Camera Failed"
So about a month ago I went swimming in the community pool with my S10. I went swimming and water park with my S8 and S9 never any issues. This time maybe I stayed in too long, haha.
So the next morning I did notice moisture on the front and rear cameras! Doh! Fired up the camera only to get "camera failed". No biggie, I have premium protection with TMo which does cover this ($99 deductible). I went to make a claim and there was an issue with the warranty not being added on my account, but TMo takes care of it's customers and added it for me and started to process the claim. A few days later the moisture disappeared, and then a few days after that the camera was resurrected!
My replacement didn't show up so when I logged in the rep said for whatever reason it didn't go through, but we were able to cancel the claim. Back in business!
Fast forward to 2 days ago when TMo pushed an update to the phone. I updated with the latest software and immediately noticed I'm back to "Camera failed". I have tried the basics like clearing cache, clearing app cache, booting into recovery to clear the cache, and in safe mode. Still no go.
The kicker is (and this was also apparent during the first failure) the camera app shows failed, and all apps that use the camera also throw an error about accessing the camera EXCEPT the Poshmark fashion marketplace app. It access the camera no issues, front and back! I also uninstalled Poshmark, cleared cache, and rebooted without success.
So I was wondering if anyone had any ideas before I try a factory reset because it takes a while to restore a lot of my settings and customization. And if that doesn't work I'll wait a few days and see if it comes back to life like last time and if it doesn't, file a warranty claim.
Thanks

I think I'd still do a reset and try the camera without restoring anything. If it fails then, you've already done the reset for the return. If it works still don't restore anything, live with it a few hours and keep trying different settings with both front and rear cameras. If you can't make it break, then do your restore. I know a restore is tough to do sometimes, but I hate those nagging problems you can't put a finger on.

Tel864 said:
I think I'd still do a reset and try the camera without restoring anything. If it fails then, you've already done the reset for the return. If it works still don't restore anything, live with it a few hours and keep trying different settings with both front and rear cameras. If you can't make it break, then do your restore. I know a restore is tough to do sometimes, but I hate those nagging problems you can't put a finger on.
Click to expand...
Click to collapse
Yeah I know there isn't a lot of options left at this point. But it's weird that the poshmark app has no problems accessing the camera when everything else does, and that after the TMO update it killed my camera again.
Thank you

Similar problem
Nurmi_CEO said:
Yeah I know there isn't a lot of options left at this point. But it's weird that the poshmark app has no problems accessing the camera when everything else does, and that after the TMO update it killed my camera again.
Thank you
Click to expand...
Click to collapse
Well I had the same problem on my s10, however it was being used in heavy rains and the next morning there was moisture in both the front &back cameras.
However it was still taking pictures (full of blur), no it wasn't showing any camera failed error. I took it to the service centre where they had the phone disassembled and heated up the camera module. The phone is working fine ever since, I recently got the June update (India) and my phone's camera is still working properly. Do try a factory reset and let me know as we whatever happens

Nurmi_CEO said:
Yeah I know there isn't a lot of options left at this point. But it's weird that the poshmark app has no problems accessing the camera when everything else does, and that after the TMO update it killed my camera again.
Thank you
Click to expand...
Click to collapse
T-Mobile should push another update with camera night mode, QR code and so on. At least we(people in US) are waiting for it! See if the upcoming update fixes the issue. Don't you use Samsung back up? It is built-in to your phone. I always use it and it saved placement of your home screen shortcuts, settings(most of them), your apps and other stuff.

pma1504 said:
Well I had the same problem on my s10, however it was being used in heavy rains and the next morning there was moisture in both the front &back cameras.
However it was still taking pictures (full of blur), no it wasn't showing any camera failed error. I took it to the service centre where they had the phone disassembled and heated up the camera module. The phone is working fine ever since, I recently got the June update (India) and my phone's camera is still working properly. Do try a factory reset and let me know as we whatever happens
Click to expand...
Click to collapse
I will and see what happens. Thanks!

Charkatak said:
T-Mobile should push another update with camera night mode, QR code and so on. At least we(people in US) are waiting for it! See if the upcoming update fixes the issue. Don't you use Samsung back up? It is built-in to your phone. I always use it and it saved placement of your home screen shortcuts, settings(most of them), your apps and other stuff.
Click to expand...
Click to collapse
Ok I will do a factory reset and see what happens and checkout Samsung backup. Thanks

pma1504 said:
Well I had the same problem on my s10, however it was being used in heavy rains and the next morning there was moisture in both the front &back cameras.
However it was still taking pictures (full of blur), no it wasn't showing any camera failed error. I took it to the service centre where they had the phone disassembled and heated up the camera module. The phone is working fine ever since, I recently got the June update (India) and my phone's camera is still working properly. Do try a factory reset and let me know as we whatever happens
Click to expand...
Click to collapse
No go on the reset. Same thing. Camera failed on every app except Poshmark.
I'm going to ride it out this week and if it's still dead by Sunday I'll file an insurance claim

I'm hoping it does start working, now even I'm worried about updates breaking my camera (I got no insurance on this). Still I don't understand why the camera failed popup came on your device in the first place ( even if it had moisture) because even I had gotten the camera full of fog however it was still working properly (I took it to the service centre In a day though). I'm attaching the most recent update that I received, this water damage thingy actually happened on the 12th of June

Hello, i had the Same issue after the May Update. I tried evertyhing Clearing Cache Reset Phone....
I went to an samsung store they changed my front camera as warrenty case so i paid nothing. Till today no problems, camera works fine again.

Nurmi_CEO said:
No go on the reset. Same thing. Camera failed on every app except Poshmark.
I'm going to ride it out this week and if it's still dead by Sunday I'll file an insurance claim
Click to expand...
Click to collapse
I have trouble wrapping my head around it working with Poshmark only. Outside of reflashing the rom I can't see anything else to try, yet it does point to a software and not a hardware problem.

Tel864 said:
I have trouble wrapping my head around it working with Poshmark only. Outside of reflashing the rom I can't see anything else to try, yet it does point to a software and not a hardware problem.
Click to expand...
Click to collapse
When I did a reset on the phone, I held the volume up + bixby to boot into the bootloader and selected "wipe data/factory reset".
It's been a while since I have been rooting and modding my phones since the S8 and up Snapdragons were non rootable for the longest time. Would it be a "cleaner fresher reset" if I used Odin to flash the stock firmware? Is Odin still a thing anymore with the newest Galaxies?

Nurmi_CEO said:
When I did a reset on the phone, I held the volume up + bixby to boot into the bootloader and selected "wipe data/factory reset".
It's been a while since I have been rooting and modding my phones since the S8 and up Snapdragons were non rootable for the longest time. Would it be a "cleaner fresher reset" if I used Odin to flash the stock firmware? Is Odin still a thing anymore with the newest Galaxies?
Click to expand...
Click to collapse
Yeah you're right Odin still works with modern Samsung phones (it did with my old j7 prime-exynos android 8.1). You can try reflashing the stock firmware and maybe downgrading it if that's possible. Honestly Samsung devices have become a disappointment now to me

Software update bug!

Has anyone here experienced samsung galaxy note 8 screen gets this greening/yellowish discoloration whenever phone heats up after the latest software update?? Also the battery drains too fast unlike before.

Got the same issue!
I just got the exact same issue.
I was just watching youtube video then open an app then suddenly my screen turn yellowish and black turned faded. Also got horizontal lines if brightness is set to around 20%-70%. This happens right from boot up of the phone where Samsung logo appears.
Also I noticed that my phone gets warmer.
Mine still not back to normal.
I have read that this also happened to Note9 users.
Any update for a possible solution?
Thank you

I didn't find any solution yet but go join our telegram named "samsung display problems" there's a lot of memebers there and every one experience this issue so they made a group, pls email me at [email protected]

Domdominic said:
Has anyone here experienced samsung galaxy note 8 screen gets this greening/yellowish discoloration whenever phone heats up after the latest software update?? Also the battery drains too fast unlike before.
Click to expand...
Click to collapse
It cames after an update?
Did you try Factory reset?

Yes i already did,

I have never noticed that and I have all the latest updates installed on my N950N. Have you tried wiping the Cache Partition?

Hi.
I have a Samsung Note 8 with a case like @Domdominic in the previous update, after updating the new version on April 12 with CSC DTC3, the screen error is gone but my fingerprints did not work after updating. I don't know if this is a computer error or a software issue and I still don't know how to fix it.

Nolove2404 said:
Hi.
I have a Samsung Note 8 with a case like @Domdominic in the previous update, after updating the new version on April 12 with CSC DTC3, the screen error is gone but my fingerprints did not work after updating. I don't know if this is a computer error or a software issue and I still don't know how to fix it.
Click to expand...
Click to collapse
Have you tried manually reinstalling the OS back onto your device using a computer and Odin? That is always the last resort if your device is not functioning properly. The worst case scenario is that your device is experiencing a component failure and it needs to be replaced.

iceepyon said:
Have you tried manually reinstalling the OS back onto your device using a computer and Odin? That is always the last resort if your device is not functioning properly. The worst case scenario is that your device is experiencing a component failure and it needs to be replaced.
Click to expand...
Click to collapse
Thank you, maybe I will try to use Odin back to the older OS or wait for a new patch from samsung. :crying::crying: or buy a new phone

Nolove2404 said:
Thank you, maybe I will try to use Odin back to the older OS or wait for a new patch from samsung. :crying::crying: or buy a new phone
Click to expand...
Click to collapse
You could always delete all your fingerprints and reset them. Could be that your old fingerprint settings got corrupted. As I said before reinstalling the OS is a last resort.

S20FE Bricked itself

Hey so my father's phone just kinda bricked itself one morning. We don't know how or why. But he did tell me he installed the newest software update a few days ago, meaning he got OneUI 5.0.
If it matters, this is a german version of the S20FE, unfortunately im unaware if he has the Samsung CPU or Snapdragon CPU version.
I'm tasked with getting the data off the phone, but unfortunately i can not boot into android. The phone either freezes at the "Samsung Secured by Knox" logo or bootloops at that logo. When charging it does not show battery percentage, only the lightning symbol.
I can easily access the downloading mode, but recovery mode is very hard to get to, usually because of the bootloop, takes me around 10 to 30 minutes to get into.
Wiping Cache partition does not work, "repair apps" results in the bootloop
The logs always end displaying 3 times the same error: unable to set property "ro.boottime.init.mount.cache" to "1": error code: 0x18
Does anyone have an idea on how to get all the files off of it? I heard you can use Odin to flash it without losing data but also heard that it doesnt work since OneUI 3.1, and since OneUI 5.0 is very fresh i don't think anyone ever tried flashing it without data loss.

Unless you can boot it into safe mode you're boned.
If he really needs the data... take it to a data recovery specialist. Rates are around $800 for advanced recovery services, it may be less.
Otherwise see if a factory reset fixes it. Always redundantly and regularly backup critical data to avoid complete data lose.

blackhawk said:
Unless you can boot it into safe mode you're boned.
If he really needs the data... take it to a data recovery specialist. Rates are around $800 for advanced recovery services, it may be less.
Otherwise see if a factory reset fixes it. Always redundantly and regularly backup critical data to avoid complete data lose.
Click to expand...
Click to collapse
Safe Mode Freezes up
And knowing my Father, he won't pay that amount of money to recover the data..

JojoOn3DS said:
Safe Mode Freezes up
And knowing my Father, he won't pay that amount of money to recover the data..
Click to expand...
Click to collapse
Maybe it's a lesson he needs to learn the hard way. Androids rarely crash and burn but it does happen. Messing with the firmware is always a risk. One reason why I never do OTA updates/upgrades.
Data is fragile... not redundantly backing it up is an open invitation for trouble. A drop, water exposure, a near lighting strike, a hardware failure, malware, etc can destroy the data if that's the sole copy of it. Really it's only a matter of time until it happens. He needs to take a more vested interest in the device... or suffer the consequences.
Maybe someone here can help you but hands on by a specialist maybe the only viable shot there is at recovering the data now.

I have been able to unbrick Samsung devices in the past. I have posted what I did on this website.

blackhawk said:
Maybe it's a lesson he needs to learn the hard way. Androids rarely crash and burn but it does happen. Messing with the firmware is always a risk. One reason why I never do OTA updates/upgrades.
Data is fragile... not redundantly backing it up is an open invitation for trouble. A drop, water exposure, a near lighting strike, a hardware failure, malware, etc can destroy the data if that's the sole copy of it. Really it's only a matter of time until it happens. He needs to take a more vested interest in the device... or suffer the consequences.
Maybe someone here can help you but hands on by a specialist maybe the only viable shot there is at recovering the data now.
Click to expand...
Click to collapse
Update, he sais he has his files on google drive. Now i tried to reinstall android using Odin3, i installed OneUI 4 with android 12, the farthest that i got was now a charging indicator showing percentage and the samsung android bootlogo after the bootloader logo. but then it crashes. OneUI 5 android 13 makes it bootloop again. The last thing i might do is just root the device

JojoOn3DS said:
Update, he sais he has his files on google drive. Now i tried to reinstall android using Odin3, i installed OneUI 4 with android 12, the farthest that i got was now a charging indicator showing percentage and the samsung android bootlogo after the bootloader logo. but then it crashes. OneUI 5 android 13 makes it bootloop again. The last thing i might do is just root the device
Click to expand...
Click to collapse
Well that's good... if it works.
You try the last version it was running on before it went to hell? If was me I use the earliest version available. I would not root it as dad will likely get in trouble for sure... and lose some core features forever.
First thing I would have tried is a factory reset. Anytime you flash firmware you're taking a risk; there's zero risk to clearing the user data partition.

blackhawk said:
Well that's good... if it works.
You try the last version it was running on before it went to hell? If was me I use the earliest version available. I would not root it as dad will likely get in trouble for sure... and lose some core features forever.
First thing I would have tried is a factory reset. Anytime you flash firmware you're taking a risk; there's zero risk to clearing the user data partition.
Click to expand...
Click to collapse
The data is already gone, it was backed up by Google Drive and my dad got the data on his older phone now. The earliest version i can install after an OneUI 4 update is OneUI 4 android 12, which i have already tried, any older than that results in a Fail because the device refuses to flash OneUI 3 or older.
It does boot android *sometimes* with OneUI 4 Android 12. but never to the "Welcome" screen. OneUI 5 Android 13 causes it to reboot nonstop again (like originally). I am planning on downloading different versions of OneUI 4 android 12 for this device and see if it ever boots fully.
Allthough this seems like a software defect, im starting to doubt the battery itself, because when it was charging it only showed 5% after an entire night on the charger.

JojoOn3DS said:
The data is already gone, it was backed up by Google Drive and my dad got the data on his older phone now. The earliest version i can install after an OneUI 4 update is OneUI 4 android 12, which i have already tried, any older than that results in a Fail because the device refuses to flash OneUI 3 or older.
It does boot android *sometimes* with OneUI 4 Android 12. but never to the "Welcome" screen. OneUI 5 Android 13 causes it to reboot nonstop again (like originally). I am planning on downloading different versions of OneUI 4 android 12 for this device and see if it ever boots fully.
Allthough this seems like a software defect, im starting to doubt the battery itself, because when it was charging it only showed 5% after an entire night on the charger.
Click to expand...
Click to collapse
If SOT sucks now...
Replace the battery before you attempt another flash. Not worth bricking a phone over a battery.

blackhawk said:
If SOT sucks now...
Replace the battery before you attempt another flash. Not worth bricking a phone over a battery.
Click to expand...
Click to collapse
Yeah will probably do that, i have already flashed it like 30 times probably haha, still soft bricked like before but not hard bricked.

JojoOn3DS said:
Yeah will probably do that, i have already flashed it like 30 times probably haha, still soft bricked like before but not hard bricked.
Click to expand...
Click to collapse
No harm, no foul...