Hello,
I don't know why but my Galaxy S6's back camera just keeps on force closing.
No matter what I try:
- Rebooting
- Flashing a new Rom through TWRP
- Odin to stock
- Wipe everything on recovery
- Clear camera cache, data and force stop it
-Booting into Safe Mode
I'm out of ideas, anyone know how this can be fixed?
I would also like to add that, about 2 months ago the same thing happened to my phone and after trying all of the above that time also, nothing was working. I took it to tmobile and a representetive asked me "have you tried rebooting?" And as he asked he was rebooting my phone in front of me. I said "Yes" and when the phone booted back up, he opened the Camera app and it was working -__-
I have been rebooting for the past 2 days hoping for that to happen again, to no avail.
If using Odin to go back to stock and it still doesn't work, you're probably looking at a hardware issue. Have you tried another camera app to see if that has the same issues?
Related
I rooted my droid 4 a few months ago when I first got it so I could tether. I removed a couple of programs using titanium backup (blockbuster app and some other bloat). Phone worked fine until monday when the touchscreen stopped working. I did a reboot (power + volume down) whereupon it just sat at the M "Dual Core" logo. I tried booting into the recovery menu but selecting "recovery" didn't do anything - it would just hang.
Last night I was able to get it working again by going into the recovery menu and selecting asp fastboot, then using RSDLite to push a stock Droid 4 ROM onto the phone. However, it didn't wipe my old system, and didnt install over it either because all my files were there, and the programs I removed were still gone. So the phone worked for a few hours then the touchscreen stopped working again.
I repeated the process with RSDLite and after a few failed attempts where the phone would hang while booting, I finally got it to boot into the OS again. And this is where I am at now.
I am pretty sure that the problem is related to the OS that is on the phone now and that I need to wipe the phone and start fresh with either a custom ROM or the stock D4 ROM. The problem is that I can't get recovery to do a factory reset. As I mentioned above, recovery just hangs and doesn't do anything. I am reasonably literate when it comes to this stuff but I get really confused because there are so many different ways that people seem to do this stuff (safestrap, bootstrap, CM( etc). I would love to try CM9 but my priority right now is just to have a phone that works. Any help would be greatly appreciated.
Thanks.
whoisthisis said:
I rooted my droid 4 a few months ago when I first got it so I could tether. I removed a couple of programs using titanium backup (blockbuster app and some other bloat). Phone worked fine until monday when the touchscreen stopped working. I did a reboot (power + volume down) whereupon it just sat at the M "Dual Core" logo. I tried booting into the recovery menu but selecting "recovery" didn't do anything - it would just hang.
Last night I was able to get it working again by going into the recovery menu and selecting asp fastboot, then using RSDLite to push a stock Droid 4 ROM onto the phone. However, it didn't wipe my old system, and didnt install over it either because all my files were there, and the programs I removed were still gone. So the phone worked for a few hours then the touchscreen stopped working again.
I repeated the process with RSDLite and after a few failed attempts where the phone would hang while booting, I finally got it to boot into the OS again. And this is where I am at now.
I am pretty sure that the problem is related to the OS that is on the phone now and that I need to wipe the phone and start fresh with either a custom ROM or the stock D4 ROM. The problem is that I can't get recovery to do a factory reset. As I mentioned above, recovery just hangs and doesn't do anything. I am reasonably literate when it comes to this stuff but I get really confused because there are so many different ways that people seem to do this stuff (safestrap, bootstrap, CM( etc). I would love to try CM9 but my priority right now is just to have a phone that works. Any help would be greatly appreciated.
Thanks.
Click to expand...
Click to collapse
select recovery by holding the vol buttons and power on boot just like fastboot. press vol - for recovery. when u see dead droid hit both vol up and vol down and theres the recovery
Thanks, I was finally able to get into recovery. Wiped data and did a factory reset which again got stuck at the logo screen. Went back into fastboot and ran RSDlite again to flash the stock ROM which gets me to the "Welcome to Droid4" screen where it says "touch the android to start" but the touchscreen is unresponsive. Starting to think there is something physically wrong with the phone....
send it to motorola, I've heard their customer support is pretty good. but if you voided your warranty by rooting/flashing other roms, I've heard bricking the phone and sending it in works to get a new one too
The only way I can send it back is through an insurance claim so I am trying to save myself $75j if this thing will just work. I just did a reboot and now the touchscreen seems to be working so I am going through the setup process....so weird.
Update: I was able to get the phone to load up and configured my google account etc. It appears that the phone is now running on completely stock installation of OS.....
whoisthisis said:
The only way I can send it back is through an insurance claim so I am trying to save myself $75j if this thing will just work. I just did a reboot and now the touchscreen seems to be working so I am going through the setup process....so weird.
Update: I was able to get the phone to load up and configured my google account etc. It appears that the phone is now running on completely stock installation of OS.....
Click to expand...
Click to collapse
So it has been a couple days now and the phone works totally fine. It looks like the problem was that by removing whatever bloatware that I did, the phone's OS got borked when VZW pushed an update of some kind. Flashing the stock ROM without doing a factory wipe would temporarily solve the problem but eventually the update would get pushed again and the whole thing would lock up again. The factory wipe + reinstall seems to have been the solution to the problem.
Hey guys. I have a bit of a problem here. My friends t mobile note 4 keeps freezing. I've tried everything i could and nothing will fix it. Is this symptom of the emmc chip starting to fail?
Heres what i tried:
- Used 3 different batteries, 2 cables.
- Booted in recovery mode to factory reset and clear cache.
- Odin stock latest firmware and downgrading. When i did this phone would go into a recovery loop giving me the message "installing system update.." then would either freeze with line artifacts or say "no command".
- Re-partitioned using pit file in odin + nand erase all.
- Rooted and flashed twrp recovery. This allowed me to boot up the phone normally. 9/10 times the phone would fail to boot up 100% as it would freeze.
- Tried flashing a custom rom, but would freeze in the process and restart.
Does anyone know what the problem is? Thanks.
EDIT: I found that if i put the phone inside a freezer for 5 minutes, it temporarily fixes the problem. as soon as the phone warms up, it will freeze and restart.
Any resolution on your dilemma? My att note 4 is also doing this. I might try and pull the phone apart and try some kind of thermal paste.
ayeitschris said:
Hey guys. I have a bit of a problem here. My friends t mobile note 4 keeps freezing. I've tried everything i could and nothing will fix it. Is this symptom of the emmc chip starting to fail?
Heres what i tried:
- Used 3 different batteries, 2 cables.
- Booted in recovery mode to factory reset and clear cache.
- Odin stock latest firmware and downgrading. When i did this phone would go into a recovery loop giving me the message "installing system update.." then would either freeze with line artifacts or say "no command".
- Re-partitioned using pit file in odin + nand erase all.
- Rooted and flashed twrp recovery. This allowed me to boot up the phone normally. 9/10 times the phone would fail to boot up 100% as it would freeze.
- Tried flashing a custom rom, but would freeze in the process and restart.
Does anyone know what the problem is? Thanks.
EDIT: I found that if i put the phone inside a freezer for 5 minutes, it temporarily fixes the problem. as soon as the phone warms up, it will freeze and restart.
Click to expand...
Click to collapse
Maybe we could try and spoof the temp? :0
Since a few days now, my Note 5 N920C just randomly freezes, hangs and reboots. Sometimes the screen goes black and then it reboots sometimes the screen is just the last thing i was using and then it reboots. It even happens when im in recovery trying to flash a zip or when the phone is switched off and charging.
I have tried:
1) Wiping Cache
2) Wiping all data / Factory reset
3) Safe mode (Still reboots)
4) Uninstalling all apps
5) Flashing stock firmware from Samsung Smart Switch
6) Rooting and flashing a new kernel (SkyHigh)
After all of this i still have the same problem. Is there something else i can do? Phone is not in warranty so i really want to make sure there is nothing else i can do to fix or understand the problem before spending money on repairs.
Thanks in advance
Have you checked that there is no power-related issues with the device?
So first off thanks for reading and trying to help.
I am having the following problem:
First of no updates were installed recently. I did update to the latest December update in early January.
Few days ago my phone SM-N910T froze up and seemed to have shut down. After being unable to restart i pulled the battery, put it back in and nothing happened. I left it out for 5 minutes plugged it back in and the phone booted up. But as soon as the screen turned off the phone heated up and would not turn on. I've been dying to just start anew anyway so I tried using Kies to restore the phone however this failed twice.
I downloaded Odin and Stock N910T3UVS3EPK2.
I flashed TWRP Recovery. And then tried to Flash the firmware which failed several times and i started getting errors.
“Could not do normal boot, mmc_read failed”
Kernel is not seandroid enforcing
as well as others.
After rebooting it several times it started working I was able to log in and set everything up, but the phone started freezing up again.
I blew everything away did a Data Wipe in TWRP. I then downloaded N910T3UVS3EPK2 Stock Rooted Odex from here.
When trying to flash it, it failed several times. and i started getting No Pit Binary errors. After trying several times with different cables and USB ports it finally took. But i am still having the same problems with freezing and restarting.
THE ONLY THING THAT HELPED: And this is a band aid fix, is I installed the wake lock app from the google store and enable Partial Wake Lock.
The phone is stable but only until i restart it at which point it goes into Download Mode and i have to restart several times and prey it boots up.
HALP! :crying:
I had the same problem, and MANY MANY others have this issue too. For months i fought with it without any success. I ordered new motherboard and now my phone is working again.
Please check General forum. There is a big thread about installing KitKat from another phone which apparently fixed this issue. Dig around that thread and read about it, might be a solution!
AntonJart said:
I had the same problem, and MANY MANY others have this issue too. For months i fought with it without any success. I ordered new motherboard and now my phone is working again.
Please check General forum. There is a big thread about installing KitKat from another phone which apparently fixed this issue. Dig around that thread and read about it, might be a solution!
Click to expand...
Click to collapse
I saw that thread, but most of those people started having the issue after the update. If the kit kat update fixes it then i'm at a loss. And since a new board fixed the issue for you that means most likely the the memory is beginning to fail. That's how SSDs die anyway.
tempy1 said:
So first off thanks for reading and trying to help.
I am having the following problem:
First of no updates were installed recently. I did update to the latest December update in early January.
Few days ago my phone SM-N910T froze up and seemed to have shut down. After being unable to restart i pulled the battery, put it back in and nothing happened. I left it out for 5 minutes plugged it back in and the phone booted up. But as soon as the screen turned off the phone heated up and would not turn on. I've been dying to just start anew anyway so I tried using Kies to restore the phone however this failed twice.
I downloaded Odin and Stock N910T3UVS3EPK2.
I flashed TWRP Recovery. And then tried to Flash the firmware which failed several times and i started getting errors.
“Could not do normal boot, mmc_read failed”
Kernel is not seandroid enforcing
as well as others.
After rebooting it several times it started working I was able to log in and set everything up, but the phone started freezing up again.
I blew everything away did a Data Wipe in TWRP. I then downloaded N910T3UVS3EPK2 Stock Rooted Odex from here.
When trying to flash it, it failed several times. and i started getting No Pit Binary errors. After trying several times with different cables and USB ports it finally took. But i am still having the same problems with freezing and restarting.
THE ONLY THING THAT HELPED: And this is a band aid fix, is I installed the wake lock app from the google store and enable Partial Wake Lock.
The phone is stable but only until i restart it at which point it goes into Download Mode and i have to restart several times and prey it boots up.
HALP! :crying:
Click to expand...
Click to collapse
Do you have "T3"or "T" model?
The files given below is for "T" variant do not try if you have T3.
It sounds crazy to tell you but trust me this will work.
Put your phone in freezer for about 2 hours then do the steps below if you want to recover your device as it was before.
Go to download mode
Flash 5.0.1 modem via odin choose (CP) tab this will fix emmc read fail error.
https://www.androidfilehost.com/?fid=24052804347820086
Dont reboot to system go to download mode again.
Then flash full 5.1.1 lollipop ok1 firmware
https://www.androidfilehost.com/?fid=312968873555011894
.once it pass dont let the phone reboot.
Go to stock recovery and wipe cache & data factory reset.
Reboot wait 10 minutes dont touch anything let the phone rest.
Complete setup and dont download anything any apps go to software update and take all marshmallow ota updates.
Once finish do factory reset again and you will get clean operating system without any issues.
Trex888 said:
Do you have "T3"or "T" model?
The files given below is for "T" variant do not try if you have T3.
It sounds crazy to tell you but trust me this will work.
Put your phone in freezer for about 2 hours then do the steps below if you want to recover your device as it was before.
Go to download mode
Flash 5.0.1 modem via odin choose (CP) tab this will fix emmc read fail error.
https://www.androidfilehost.com/?fid=24052804347820086
Dont reboot to system go to download mode again.
Then flash full 5.1.1 lollipop ok1 firmware
https://www.androidfilehost.com/?fid=312968873555011894
.once it pass dont let the phone reboot.
Go to stock recovery and wipe cache & data factory reset.
Reboot wait 10 minutes dont touch anything let the phone rest.
Complete setup and dont download anything any apps go to software update and take all marshmallow ota updates.
Once finish do factory reset again and you will get clean operating system without any issues.
Click to expand...
Click to collapse
I have the " T " variant
I've read this before. I am a logical person I want to understand why this would work. Also when placing the phone in the freezer (i feel like i'm being pranked) do i place it in there with the battery?
I will definitely try this since I have nothing to lose. But i have a phone heavy next few weeks and i don't have a backup
tempy1 said:
I have the " T " variant
I've read this before. I am a logical person I want to understand why this would work. Also when placing the phone in the freezer (i feel like i'm being pranked) do i place it in there with the battery?
I will definitely try this since I have nothing to lose. But i have a phone heavy next few weeks and i don't have a backup
Click to expand...
Click to collapse
Without battery in freezer.
No idea how it works but good thing is hopefully it will work cuz lot of users even recover their hard bricked devices by this.
As you said you have nothing to lose so give it a try and make sure be patient dont give up and do this when you have enough time to do at least couple of hours.
I should mention that I had an 'injured' 910t after upgrading, and the freezer thing worked for months. I think there is a thermal issue and something is physically getting de-soldered in the motherboard. @Trex888, I will try your fix - I got a NEW Note4 2 weeks ago and it is running 5.0.1 and it bricked....
IF ANY OTHER COMPANY SOLD A PHONE WITH STYLUS, i WOULD TOSS THE NOTE4 IN THE TRASH....
keithwwalker said:
I should mention that I had an 'injured' 910t after upgrading, and the freezer thing worked for months. I think there is a thermal issue and something is physically getting de-soldered in the motherboard. @Trex888, I will try your fix - I got a NEW Note4 2 weeks ago and it is running 5.0.1 and it bricked....
IF ANY OTHER COMPANY SOLD A PHONE WITH STYLUS, i WOULD TOSS THE NOTE4 IN THE TRASH....
Click to expand...
Click to collapse
so wait the freezer thing was not even a permanent fix?
No, the freezer sometimes helps you get a bricked device so that it turns on. It doesn't fix thermal issues. I believe it helps some electrical connection that has broken come into contact again.
I can't go to download mode or recovery. I tried both ways But there is no way to use my device.
Trex888 said:
Do you have "T3"or "T" model?
The files given below is for "T" variant do not try if you have T3.
It sounds crazy to tell you but trust me this will work.
Put your phone in freezer for about 2 hours then do the steps below if you want to recover your device as it was before.
Go to download mode
Flash 5.0.1 modem via odin choose (CP) tab this will fix emmc read fail error.
https://www.androidfilehost.com/?fid=24052804347820086
Dont reboot to system go to download mode again.
Then flash full 5.1.1 lollipop ok1 firmware
https://www.androidfilehost.com/?fid=312968873555011894
.once it pass dont let the phone reboot.
Go to stock recovery and wipe cache & data factory reset.
Reboot wait 10 minutes dont touch anything let the phone rest.
Complete setup and dont download anything any apps go to software update and take all marshmallow ota updates.
Once finish do factory reset again and you will get clean operating system without any issues.
Click to expand...
Click to collapse
So i recently had a baby, thus i had no time at all to get my phone to work. WakeLock app was working alright.
But last night the phone just died. all attempts to revive failed. I left it in the freezer until the morning and it booted up but quickly locked up after about 5 minutes of use and became unresponsive.
I tried your method.
I failed right away. Modem could not be written..
I tried flashing the pit files like i did previously and that failed as well.
Any suggestions are appreciated. I am phoneless
EDIT#2: After I left the phone in the freezer for longer (3 hours). The odin firmware update went through !!!! This furtherst i've gone so far.
I went into recovery and did everything you said.
BUT now i have Kernel Panic Upload Mode on my screen with a little green android
EDit#3 few battery pulls later. And an over 15 minute wait time on the android logo and then about the same on the t-mobile logo i got into the OS. I did the OTA update, the phone heated up and a few restarts later it froze up like it did previously
Back to square 1
EDIT: THIS helped for a few days
https://forum.xda-developers.com/note-4-tmobile/general/ddi-mmcread-failed-boot-error-fix-t3434335
Day 2: and all went back to the phone not waking up and after screen is turned off
I've been facing a weird problem with my G800H since yesterday. The phone will reboot constantly. It will boot into android, I will even be able to open apps, but it will suddenly reboot after a minute or so. I didn't do anything to my phone for it to start doing this. The weirdest part is that the rebooting will happen even if I am in recovery mode (TWRP). Also, the phone will automatically turn on if I take off the battery and put it back in, something that never happened before.
I use stock 6.0.1 (rooted) and TWRP 3.0.
Things I've already tried:
Charging it;
Safe mode (same problem);
Taking off SD card (who knows);
Wipe cache/dalvik (phone restarts before finishing);
Re-install ROM ( Download mode (ODIN) doesn't open, insta-restart after 'press volume up to enter odin').
I really dont want to do a full factory reset, only as a last resort, as i don't even know if it will have time to do so, or even if it will fix it. Does anyone know a way for wiping the cache without having to format it ( takes too long in TWRP so phone restarts before finishing ), or maybe have some other way of entering download mode, maybe with adb, or finding out what went wrong. Any sugestions on what to do or what happened?
I (my wife) have the exact same problem, I bought a new battery which didn't solve the problem.
Also tried a factory reset, didn't help either.
It is a non rooted phone...
Next try is a custom rom, hope it helps...
Install an app that records logs like Logcat, set it in record mode and wait until the phone reboots. Then look through the file, study what happens near the end when the phone turns off. You'll most likely find the cause there.