[Q] camera failed error after kitkat upgrade - Galaxy Grand 2 Q&A, Help & Troubleshooting

Hi, I own a grand 2 lte sm-g7105 and i updated my phone to android kitkat 4.4.2 when i open camera it says camera failed .i tried clearing app data and cache of camera and also did the factory reset but the problem remain same.I'm unable to downgrade to jellybean also.Please anybody help me.

qasim799 said:
Hi, I own a grand 2 lte sm-g7105 and i updated my phone to android kitkat 4.4.2 when i open camera it says camera failed .i tried clearing app data and cache of camera and also did the factory reset but the problem remain same.I'm unable to downgrade to jellybean also.Please anybody help me.
Click to expand...
Click to collapse
Try clearing cache from recovery if it doesn't work try factory resetting and of that also doesn't work then you can always flash stock firmware from Odin..

kuldude said:
Try clearing cache from recovery if it doesn't work try factory resetting and of that also doesn't work then you can always flash stock firmware from Odin..
Click to expand...
Click to collapse
tried flashing through odin but the problem remains same because problem is in 4.4.2 update i think it should be downgraded to 4.3 jellybean
an you help me in downgrading?

I know this was not an answer you expected but the best you can do is to take it to service center or try downgrading and hard brick your phone

kuldude said:
I know this was not an answer you expected but the best you can do is to take it to service center or try downgrading and hard brick your phone
Click to expand...
Click to collapse
I have no warranty of my phone and i tried downgrading it didn't hardbricked my phone just a error appear on my phone sbl1 sw rev check failed fused 2 binary 1 and restarted normally

qasim799 said:
Hi, I own a grand 2 lte sm-g7105 and i updated my phone to android kitkat 4.4.2 when i open camera it says camera failed .i tried clearing app data and cache of camera and also did the factory reset but the problem remain same.I'm unable to downgrade to jellybean also.Please anybody help me.
Click to expand...
Click to collapse
Same things happens to me. The only solution for u is to remove any batter saver, process cleaner or memory cleaner. and restart the phone see how ur phone reacts.

Related

[Q] Keeps rebooting after KK update

I have just had an OTA update to kitkat but after the upgrade, the phone keeps rebooting. I have tried switching it off, take out battery, clear cache, but it does not solve the problem. Can anyone help please?
koj012 said:
I have just had an OTA update to kitkat but after the upgrade, the phone keeps rebooting. I have tried switching it off, take out battery, clear cache, but it does not solve the problem. Can anyone help please?
Click to expand...
Click to collapse
Which region? -- reboot into recovery and clear you cache/dalvik etc -- you could try grabbing the stock and reflashing it via Odin. (it won't hurt your knox etc )
radicalisto said:
Which region? -- reboot into recovery and clear you cache/dalvik etc -- you could try grabbing the stock and reflashing it via Odin. (it won't hurt your knox etc )
Click to expand...
Click to collapse
XME Malaysia. Already rebooted into recovery and cleared cache. No change, problem remains. Stock still not available in samfirmware yet as it was just released today. Can I flash the polish version and reflash to xme version later when it is available? will it trigger knox, wipe data, etc? Please advice...tq
koj012 said:
XME Malaysia. Already rebooted into recovery and cleared cache. No change, problem remains. Stock still not available in samfirmware yet as it was just released today. Can I flash the polish version and reflash to xme version later when it is available? will it trigger knox, wipe data, etc? Please advice...tq
Click to expand...
Click to collapse
So long as you do not have the HK Note (which since you have XME I assume you don't) the Polish version is fine, then yes you can switch to XME when it's freely available. At least by doing this, you can assess whether the phone is at fault or it's a hardware issue.
radicalisto said:
So long as you do not have the HK Note (which since you have XME I assume you don't) the Polish version is fine, then yes you can switch to XME when it's freely available. At least by doing this, you can assess whether the phone is at fault or it's a hardware issue.
Click to expand...
Click to collapse
TQ for your advice. So, flashing to official polish rom and back will not void 'official' status or trigger knox? will it also wipe data in the phone?
koj012 said:
TQ for your advice. So, flashing to official polish rom and back will not void 'official' status or trigger knox? will it also wipe data in the phone?
Click to expand...
Click to collapse
It won't trip No. The Official XEO version won't wipe any data either.
Same here
I aave the Sprint version and installed a 4.4 ROM over 4.3 .Phone is now stuck in reboot loop . I've wiped everything (Along with factory reset)and installed latest CM ...no dice. I've tried to set persmissions again from TWPR ...no dice.
What can i do ? Again....Sprint version (N990P) updated to 4.4 so i can't go back to official 4.3 ( and no official rom for 4.4 yet ).
Please
gogupintenogu said:
I aave the Sprint version and installed a 4.4 ROM over 4.3 .Phone is now stuck in reboot loop . I've wiped everything (Along with factory reset)and installed latest CM ...no dice. I've tried to set persmissions again from TWPR ...no dice.
What can i do ? Again....Sprint version (N990P) updated to 4.4 so i can't go back to official 4.3 ( and no official rom for 4.4 yet ).
Please
Click to expand...
Click to collapse
Is yours Exynos or Snapdragon? -- You could try the N900 Russian 4.4.2 update, or the N9005 Polish update. Not entirely sure if they'll even work tbh -- you probably won't get any data though it'll be calls only until your official ROM comes out (unless the new updates have Sprint settings or you can manually set the APN)
EDIT: PS 4.3 baseband ROMS like CM won't work since you've update to 4.4 boot loader..
koj012 said:
I have just had an OTA update to kitkat but after the upgrade, the phone keeps rebooting. I have tried switching it off, take out battery, clear cache, but it does not solve the problem. Can anyone help please?
Click to expand...
Click to collapse
Did you ever experience anything from this thread? http://forum.xda-developers.com/showthread.php?p=49663665#post49663665
Had the same issue too. Upgraded OTA to Kit Kat and was stucked in reboot loop. Deleting cache partition in recovery mode and booting in safe mode doesn't help. I fixed it by resetting it to factory default in recovery mode. If u didn't back up for data beforehand, try removing the SIM before rebooting. It worked for me and it allowed me to back up via Kies before wiping it clean in recovery mode later
Sent from my SM-N9005 using Tapatalk
bgoh82 said:
Had the same issue too. Upgraded OTA to Kit Kat and was stucked in reboot loop. Deleting cache partition in recovery mode and booting in safe mode doesn't help. I fixed it by resetting it to factory default in recovery mode. If u didn't back up for data beforehand, try removing the SIM before rebooting. It worked for me and it allowed me to back up via Kies before wiping it clean in recovery mode later
Sent from my SM-N9005 using Tapatalk
Click to expand...
Click to collapse
I have solved this bug by turning off the location service in connection settings
When the device boots i can access the settings before it reboots again and then make the handphone in airplane mode
Then after few minutes i can turn on the wifi
Then I turned off the location setting
Then turn off the airplane mode.
I cannot believe that samsung let the update goes to its users with such a big error.
N9005 (Malaysia) stock (not rooted)

[Q] My Note III is bricked??

Hi guys, I am new here, I am now finding help anywhere about my Note III recent problem...
My note III is SM-N9005 Malaysia version, I did root it with CF Auto Root and I had been using it without problems until yesterday morning,
This is my case :
I realized my alarm was written "Clock has been not responding" and I lost my network service, then I tried to restart my phone,
Since I restart, it became worst, my phone went into boot loop and sometimes freeze on the "Samsung Galaxy Note 3" screen,
But in a few times of reboot, it will be able to boot into homescreen, but still no service for the network, and everything processes work extremely slow, even freezing and crashing!
What I tried to do to fix it :
-I went to the Samsung service center, and the technician said that my warranty is voided (Ofcourse I knew it), and he told me that this problem is due to software problem instead of hardware.
-I did flash my kernel with stock kernel again which was downloaded from Sammobile, but it did not fix my problem,
-And I tried to hard reset and factory reset of my phone, it did not help too,
-I am also tried to clear cache and dalvik cache and reboot the device, it didn't seems working...
I have already done what I could but I still yet to fix my phone, what should I do now, any experts can guild me?? T^T
Thank you
KelvinEclipse said:
Hi guys, I am new here, I am now finding help anywhere about my Note III recent problem...
My note III is SM-N9005 Malaysia version, I did root it with CF Auto Root and I had been using it without problems until yesterday morning,
This is my case :
I realized my alarm was written "Clock has been not responding" and I lost my network service, then I tried to restart my phone,
Since I restart, it became worst, my phone went into boot loop and sometimes freeze on the "Samsung Galaxy Note 3" screen,
But in a few times of reboot, it will be able to boot into homescreen, but still no service for the network, and everything processes work extremely slow, even freezing and crashing!
What I tried to do to fix it :
-I went to the Samsung service center, and the technician said that my warranty is voided (Ofcourse I knew it), and he told me that this problem is due to software problem instead of hardware.
-I did flash my kernel with stock kernel again which was downloaded from Sammobile, but it did not fix my problem,
-And I tried to hard reset and factory reset of my phone, it did not help too,
-I am also tried to clear cache and dalvik cache and reboot the device, it didn't seems working...
I have already done what I could but I still yet to fix my phone, what should I do now, any experts can guild me?? T^T
Thank you
Click to expand...
Click to collapse
have you done a EFS backup? it helps if you run into problems like this....
check here...http://forum.xda-developers.com/showthread.php?t=2298104
this works on note 8 though
welard said:
have you done a EFS backup? it helps if you run into problems like this....
check here...http://forum.xda-developers.com/showthread.php?t=2298104
this works on note 8 though
Click to expand...
Click to collapse
I didn't really know about EFS while I root my phone, I just knew it recently due to my current issue, so I didn't backup it....
Is there any other solution??? Or could I recover my EFS eventhough I didn't do a backup??
BTW, thx for reply~
KelvinEclipse said:
I didn't really know about EFS while I root my phone, I just knew it recently due to my current issue, so I didn't backup it....
Is there any other solution??? Or could I recover my EFS eventhough I didn't do a backup??
BTW, thx for reply~
Click to expand...
Click to collapse
check your internal card or sd card for a folder called Backups or something similar, if your running a custom rom normally EFS is automatically stored there if your custom rom does do EFS backup automatically at install....if not do a search on the forum for EFS RECOVERY or re-flash your rom it may help or may not, but im sure it wont though...
also read though the link i sent you there maybe some think there that may help you
you can try to do install new firmware with odin 3:09 kitkate see how it behaves ....
ANDROIDXFOREVER said:
you can try to do install new firmware with odin 3:09 kitkate see how it behaves ....
Click to expand...
Click to collapse
Its not bricked if its still working. Have you tried turning on your phone without a sim card / sd card inserted?
also try *#06# to see if your imei number is presant..
try flashing stock rom
in the same boat hope u get it sorted, i just flashed the omega v14 onto my note and its stuck on the first screen
yulaw5110 said:
in the same boat hope u get it sorted, i just flashed the omega v14 onto my note and its stuck on the first screen
Click to expand...
Click to collapse
Reboot into recovery and wipe cache partition and then scroll to advanced and wipe dalvik cache, then reboot your phone
Sent from my SM-N9005 using XDA Premium 4 mobile app
Thanks guys for the replies
-I went for a search for the backup folder in either of the storage mentioned by I didn't see a file called "backup"... I think I deleted it since the factory reset I've done yesterday, I went to many forums hat talk about EFS, and it wont help my problem cos all of them are talk about "Backup/recover", where I didn't backup my EFS earlier...
-I tried for the IMEI code, that's the reason I know about EFS, it shows "null/null", and most the information are showing unknown, such as baseband version, IMEISV, IP Address, Bluetooth Address.
-My current situation is whatever I flash into my phone, it just wont help, the problem didn't improvise at all...
Thanks..
KelvinEclipse said:
Thanks guys for the replies
-I went for a search for the backup folder in either of the storage mentioned by I didn't see a file called "backup"... I think I deleted it since the factory reset I've done yesterday, I went to many forums hat talk about EFS, and it wont help my problem cos all of them are talk about "Backup/recover", where I didn't backup my EFS earlier...
-I tried for the IMEI code, that's the reason I know about EFS, it shows "null/null", and most the information are showing unknown, such as baseband version, IMEISV, IP Address, Bluetooth Address.
-My current situation is whatever I flash into my phone, it just wont help, the problem didn't improvise at all...
Thanks..
Click to expand...
Click to collapse
download Stock firmware from sammobile or samsung updates
turn phone off, boot into recovery mode wipe data/factory reset, wipe cache partition
turn phone off, boot into download mode
use odin v 3.09 load your downloaded firmware into AP, check update boot loader box, don't check anything else and click start.
once it finishes flashing, it will reboot by itself.
if it fails then you might want to repeat the process above one more time.
if still fails u might want to do emergency recovery via kies.
Good luck and hope this helps.
doodydood said:
download Stock firmware from sammobile or samsung updates
turn phone off, boot into recovery mode wipe data/factory reset, wipe cache partition
turn phone off, boot into download mode
use odin v 3.09 load your downloaded firmware into AP, check update boot loader box, don't check anything else and click start.
once it finishes flashing, it will reboot by itself.
if it fails then you might want to repeat the process above one more time.
if still fails u might want to do emergency recovery via kies.
Good luck and hope this helps.
Click to expand...
Click to collapse
Thanks for the reply
I have tried the odin method and it didn't work...
Now I am trying for the kies emergency recovery method, and I will reply if there are any improvements...
Hi guys, I think have some new clues to determine my problem now
I flashed a custom recovery into my phone this morning,
and I realise that my /system, /efs and /firmware-modem is unmounted,
I tried to mount them, it was successful, but when I reboot the device, the problem still there,
Boot loop, no IMEI, no Baseband Version, Lag Processes,
and I went back to recovery again, I realised they have been unmounted again...
Any idea what is the problem guys??
Thx
doodydood said:
download Stock firmware from sammobile or samsung updates
turn phone off, boot into recovery mode wipe data/factory reset, wipe cache partition
turn phone off, boot into download mode
use odin v 3.09 load your downloaded firmware into AP, check update boot loader box, don't check anything else and click start.
once it finishes flashing, it will reboot by itself.
if it fails then you might want to repeat the process above one more time.
if still fails u might want to do emergency recovery via kies.
Good luck and hope this helps.
Click to expand...
Click to collapse
Hi there,
I have tried the kies emergency recovery method, but it was unsuccessful,
My note 3 was connected to the kies, but when I run Emergency Firmware Recovery,
My device was instantly disconnected with kies
And I have also tried the Firmware Upgrade and Initialisation,
The Kies showed me that my device is not supported with initialisation...
Anything I should do??
Thx
speedyjay said:
Reboot into recovery and wipe cache partition and then scroll to advanced and wipe dalvik cache, then reboot your phone
Sent from my SM-N9005 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
i actually found a different kernal in the omega thread and that seemed to sort it, thanks tho

[Q] Unfortunately, System UI has stopped

Hi,
I was messaging a friend on my phone when all of a sudden it shuts down. Now when it reloads after the samsung logo I box pops up saying Unfortunately, System UI has stopped. I flashed lollipop over a week ago and everything was going great until now... Any ideas anyone? I tried to flash again but MMC_write fail at start. so no go. Odin sees it. TWRP is available but I cant restore since my restore point has disappeared. I cant mount anything besides system and micro sd. Cant get int Adb sideload either.
Thank you in advance for any help anyone can offer or lead me to an answer.
Of_Winter said:
Hi,
I was messaging a friend on my phone when all of a sudden it shuts down. Now when it reloads after the samsung logo I box pops up saying Unfortunately, System UI has stopped. I flashed lollipop over a week ago and everything was going great until now... Any ideas anyone? I tried to flash again but MMC_write fail at start. so no go. Odin sees it. TWRP is available but I cant restore since my restore point has disappeared. I cant mount anything besides system and micro sd. Cant get int Adb sideload either.
Thank you in advance for any help anyone can offer or lead me to an answer.
Click to expand...
Click to collapse
Hi, go to recovery ,make a wipe data factory reset and the reflash the rom
dabenaute said:
Hi, go to recovery ,make a wipe data factory reset and the reflash the rom
Click to expand...
Click to collapse
It fails due to the fact that it cant mount data, cache, or internal storage. Any other ideas? Man I wish it was that simple though would have been free from the stress last few days.
Thanks,
I got the same problem when i flashed cf root for kitkat on my SM-N9005 5.0 lollipop, i simply reflashed the stock rom via odin and problem solved
Dahdoul said:
I got the same problem when i flashed cf root for kitkat on my SM-N9005 5.0 lollipop, i simply reflashed the stock rom via odin and problem solved
Click to expand...
Click to collapse
I was thinking the same, however everytime I try to flash something with odin it fails. On the screen it says MMC: MMC_write fail not sure how to get around this part. Sent to samsung tech guy and he said he couldn't either. any other ideas?
Is it ok on xda to bump a thread? if not my bad. Still desperately looking for an answer on this topic.
Anyone with ideas? It's been since feb and still sitting in the corner looking all sad.... IF all else fails is there a way to brick the phone completely so that Samsung will honor my warranty? Microwave? Oven? Something?!!?

Rear video camera hang and crashed

my Note 3 has finally got a problem. when want to record video, the app crashed. Only can take photo with rear camera and front camera works . Cleared cache, changed ROMs from 4.4.2 all the way to LP MIUI and modem and hlos.bins, all to no avail. reformat MicroSD card also cannot.
Customer service said maybe sensor or camera gone to the dogs. Anyone can help?
So I solved it by:
Using Odin 3.11.1
I have already tried Factory reset, wipe cache, wipe dalvik, flashed the latest stock Lolipop or older lollipop with ODin and nothing solved the problem.
So I tried to flash the latest stock lolipop with Odin and marking checked (Auto Reboot , F. Reset Time , Phone EFS clear, Phone Bootloader update).
I suspect that the Phone EFS clear did the trick. It's function is related to the modem and radio of the phone. And clearly the modem has a problem here.
I hope this will help anybody out there having this issue.
This problem happened after trying to flash lollipop using FlashFire app to reserve the root that I had in my previos Android KK 4.4.2.
Phone: Galaxy Note3 N9005 Malaysian

Note 3 lolipop problem

Hi to everyone,
I have some problems with my SM-N9005 I will explain everything from beginning what I did so you can have a clear picture. I had stock 4.4.2 rom when I bought my phone but I am a app freak so I had to do root actually my friend did it using odin because I am not so good with android knowledge. That was almost 2 years ago and with 4.4.2 I had no problems. Using camera, recording, wifi everything worked great. I have fastest class San Disk 64 GB memory card and I set camera video to save directly on it and it worked without any problems. This past month my phone started to be slow because of 2 years junk and using so I decided to put latest custom rom (I think 5.1.x something) but my friend was afraid if we dont put good rom that we will brick my phone so he told me to do a reset factory defaults and the phone will be unrooted and then go to software update option and update it to 5.0. I couldn't do that because it reported error phone changed or something like it was rooted but it was not. Lucky for me before root we did cwm backup of my phone so my friend restored backup and then we tried again software update again but still same error phone is changed (I was hundred precent sure that phone is unrooted but still no luck). Then we decided to install Kies and do firmware upgrade from options tab and it worked. It was 1.3 Gb update and kies showed that it is 5.0 and last firmware version for note 3. So I am using phone for few days now but I noticed few problems. Everytime I restart phone it forgets all wifi passwords and also when I come home I meen when I change ruter same story. Today I wanted to talk a picture and when I took a picture and go to gallery to see it (from camera up left corner see last image) phone restarted and when I wanted to record a video it said recording failed and then it restarts every time.Everything else is working great, phone is fast,maybe battery drains faster than on 4.4.2 but it is not a big problem for me. Sorry for my english if I have some mistakes. Can you help me please with these 2 issues?
??
Anyone please?
Did you try with a factory reset ?https://www.androidpit.com/factory-reset-note-3
You could possibly try flashing the stock android 5.0 with odin, that should be the best way of making sure everything is installed properly unless anyone thinks that would be a bad idea.
Chris
I tried factory reset and same story, ok I will try with odin I will go to see my friend in few days and then I will post results
So I solved it by:
Using Odin 3.11.1
I have already tried Factory reset, wipe cache, wipe dalvik, flashed the latest stock Lolipop or older lollipop with ODin and nothing solved the problem.
So I tried to flash the latest stock lolipop with Odin and marking checked (Auto Reboot , F. Reset Time , Phone EFS clear, Phone Bootloader update).
I suspect that the Phone EFS clear did the trick. It's function is related to the modem and radio of the phone. And clearly the modem has a problem here.
I hope this will help anybody out there having this issue.
This problem happened after trying to flash lollipop using FlashFire app to reserve the root that I had in my previos Android KK 4.4.2.
Phone: Galaxy Note3 N9005 Malaysian

Categories

Resources