Database Users

I9000 Camera Failed. Here is how to fix.

Hi,
I tried upgrading the camera firmware.
The upgrade worked, but after that I could not use the camera any more as it said "Camera Failed".
Here is the fix:
There are 3 steps for the camera to get onto the camera chip itself.
A: /system/firmware
B: Somewhere else on the phone
C: The camera chip.
Backup first:
Use the "CAM FW to Phone dump" to backup your current firmware.
I have not yet found out where on the phone this ends up, so I do not know how to copy it a PC for backup purposes.
FIX Proceedure:
Copy the new camera firmware to A.
Reboot the phone. After the reboot, the camera firmware will be copied from A to B.
Use the "Phone to CAM FW" option to flash the firmware from B to C.
Reboot the phone as requested, and you should then have a working camera again.
I used the camera-wave.7z to fix mine. (Found in another thread)
The "Show Camera FW version" gives totally bogus information. It shows only the FW version of the files at A, and not the contents of the camera chip itself.

Was this meant to be a useful post?

Yes. It has the FIX proceedure.
It contains an extra "reboot" step that if not followed, results in the same old firmware being flashed to the camera, and not the new firmware, thus failing to fix the problem.

after flashing wave fw no sgs fw worked for me so don't think it's really a fix - i could do that as much as i want - replacing fw and none would work then go back to waves. but the wave FW is pretty crapy against updated sgs fw in quality. in the end i went to service and they replaced my camera module.

are u sure it works?? my camera flash process arrives to 98% then it hold on for 5 seconds and then it tells flash success but nothing change!

I cant find any donwloadfile for the neuw firmeware...
can someone help me????

HELP my N9005 bugs after I flash stock firmware

DAY 1: My phone bootloops when i flashed a modem. So I flashed a firmware base on my country (Philippines N9005XXUEND6). I used odin 3.09 for flashing, did check the FRESET TIME, AUTOREBOOT, AP BOX and BOOTLOADER UPDATE.. It was successful but on the homescreen, "setup wizard has stopped" flashes on screen so I factory reset via stock recovery, then it runs ok.. Set up is done,. But another problems are:
1. entering camera, it shows black screen then says "warning: camera failed".
2. entering the phone dialler it takes seconds to respond
3. music is freezes
4. unlocking the phone it takes seconds to open
5.wakelock takes seconds also to respond
6. no sound
N9005XXUEND6 is the firmware I flashed.
DAY 2: I flashed a different firmwares XXUEND5, XXUENB4, but i notice that i after flashing, no setup wizard in the homescreen. It is the same settings,wallpaper and i have the messages and conversations in my inbox. It looks like the firmware didnt update but i look up in the baseband and build version it does change.. A friend of mind says that after flashing a firmware setup wizard must pop on the screen but mine doesnt.HELP ME MASTERS.. Im losing hope..
I cant figure out the problem, my drivers is installed, i have the firmwares, odin 3.09, and all required tools for flashing
please help me masters.. I did trying reflash the firware and do the reset, the problem persist.. thanks in advance

I have a similar problem, but I think yours is much more simpler hopefully
You find the data unchanged because you didn't do a factory reset
To do so, turn off your phone then open recovery mode by pressing VOLUME+, HOME & POWER buttons together until it opens
Choose Wipe Data/ Factory Reset --> Yes
then reboot your phone
My phone turned out to have a RAM problem and still haven't fixed it, it will cost me a lot especially that I voided my warranty because I rooted the phone

The same problem exactly!!! And I do all reset severel times! Help us!!!

Garri1980 said:
The same problem exactly!!! And I do all reset severel times! Help us!!!
Click to expand...
Click to collapse
If you could fix it don't forget to tell us about it
BTW I found a post online that says the problem could be due to separated camera from the motherboard
So if you don't have warranty as myself you should get it to maintenance service and tell them to check the camera

moustafaatchy said:
I have a similar problem, but I think yours is much more simpler hopefully
You find the data unchanged because you didn't do a factory reset
To do so, turn off your phone then open recovery mode by pressing VOLUME+, HOME & POWER buttons together until it opens
Choose Wipe Data/ Factory Reset --> Yes
then reboot your phone
My phone turned out to have a RAM problem and still haven't fixed it, it will cost me a lot especially that I voided my warranty because I rooted the phone
Click to expand...
Click to collapse
-i did that also sir but the problem persist..

moustafaatchy said:
If you could fix it don't forget to tell us about it
BTW I found a post online that says the problem could be due to separated camera from the motherboard
So if you don't have warranty as myself you should get it to maintenance service and tell them to check the camera
Click to expand...
Click to collapse
- Sir before i flash the modem, the phone works flawlessly but when it bootloops and i flash a stock firmware the other day the problem began to appear..

ian_drimworld73 said:
- Sir before i flash the modem, the phone works flawlessly but when it bootloops and i flash a stock firmware the other day the problem began to appear..
Click to expand...
Click to collapse
What is your Knox Warranty Void status ?
if it's still 0x0, you should send it to Samsung service

moustafaatchy said:
What is your Knox Warranty Void status ?
if it's still 0x0, you should send it to Samsung service
Click to expand...
Click to collapse
-0x1

ian_drimworld73 said:
-0x1
Click to expand...
Click to collapse
Then I guess your problem is like mine .. it could be hardware related :\
After I installed this ROM I found the camera working but not video camera and still can't play videos but there are no hangs
It still has problems but it sort of confirmed that I have a hardware problem
You need to be rooted
It's an AOSP ROM without Samsung Touchwiz ..
http://downloadandroidrom.com/file/...esurrection_Remix_KK_v5.0.9-20140416-hlte.zip
http://mirror41.downloadandroidrom....ock-4.4.2-20140207-signed.zip?token=866958839
Boot into Recovery .. Do a Factory Reset .. then flash the ROM then the gapps

moustafaatchy said:
Then I guess your problem is like mine .. it could be hardware related :\
After I installed this ROM I found the camera working but not video camera and still can't play videos but there are no hangs
It still has problems but it sort of confirmed that I have a hardware problem
You need to be rooted
It's an AOSP ROM without Samsung Touchwiz ..
http://downloadandroidrom.com/file/...esurrection_Remix_KK_v5.0.9-20140416-hlte.zip
http://mirror41.downloadandroidrom....ock-4.4.2-20140207-signed.zip?token=866958839
Boot into Recovery .. Do a Factory Reset .. then flash the ROM then the gapps
Click to expand...
Click to collapse
-thanks for the info sir.. but i guess its not hardware because i handle the phone carefully and it does not drop on the floor. I will thanks

-go to recovery, wipe data
- go to download mode, reflash via odin
reboot

arinsms said:
-go to recovery, wipe data
- go to download mode, reflash via odin
reboot
Click to expand...
Click to collapse
-I did that several times sir. still no luck

Hey, did you burn plywood the correct version of rum for your device? Moreover, you must make fool wipe, what version you had before making the root? That if there is a 4.3 to try to go back to 4.4.2
Sorry for bed English
Sent from my SM-N900 using XDA Free mobile app

ian_drimworld73 said:
-thanks for the info sir.. but i guess its not hardware because i handle the phone carefully and it does not drop on the floor. I will thanks
Click to expand...
Click to collapse
You said you tried updating the firmware of your region and the problem persists .. You should let someone flash the software using a BOX (not just using odin) (preferably go to Samsung)
if it's not solved then it's most probably a hardware problem .. I didn't drop my phone either but that's not necessary

Same problems with my n9005
ian_drimworld73 said:
DAY 1: My phone bootloops when i flashed a modem. So I flashed a firmware base on my country (Philippines N9005XXUEND6). I used odin 3.09 for flashing, did check the FRESET TIME, AUTOREBOOT, AP BOX and BOOTLOADER UPDATE.. It was successful but on the homescreen, "setup wizard has stopped" flashes on screen so I factory reset via stock recovery, then it runs ok.. Set up is done,. But another problems are:
1. entering camera, it shows black screen then says "warning: camera failed".
2. entering the phone dialler it takes seconds to respond
3. music is freezes
4. unlocking the phone it takes seconds to open
5.wakelock takes seconds also to respond
6. no sound
N9005XXUEND6 is the firmware I flashed.
DAY 2: I flashed a different firmwares XXUEND5, XXUENB4, but i notice that i after flashing, no setup wizard in the homescreen. It is the same settings,wallpaper and i have the messages and conversations in my inbox. It looks like the firmware didnt update but i look up in the baseband and build version it does change.. A friend of mind says that after flashing a firmware setup wizard must pop on the screen but mine doesnt.HELP ME MASTERS.. Im losing hope..
I cant figure out the problem, my drivers is installed, i have the firmwares, odin 3.09, and all required tools for flashing
please help me masters.. I did trying reflash the firware and do the reset, the problem persist.. thanks in advance
Click to expand...
Click to collapse
Hello guys what is described up is happening same to me ... tryied to update firmware from sammobile with a stock firmware Vodafone Romania and Odin show me some new lines when it updates like NON NHUL and a TGZ ZT etc ... suddenly failed to update .. and the phone freezed ... messagge was FAILED to update .. I did a restart and the two comps showed and the text : failed to upgrade firmware etc etc ... try use emergency firmware update trough kies ... restarted V Down +home +power : ) tryied to reinstal my fisrt NC2 Poland firmware succeded but
1. no sound
no camera
no music I guess That is a problem with the new Firmware ?Q? Probably we can ask MR. Chainfire or someone hwo knows ? I tryied all things ... but nothing happened even to restore data from kies /backup/trough Odin reflash old backup with TRP/CWM.
ANY ADVISE ? Never download even from sammobile or sammupdate if they say is ok if you never saw someone hwo succes
NEWS : I've noticed that suddenly when try to update again my Note3 shows only one language Chinese , probably becouse this new update NF at the end is for chinese exinos ????
1.Tryied to install CM last nightlies ...now the device work lmost 90%.
Bugs : No sound yet ...but i can acces settings sounds
E-mail has stoped
When i receive a call the phone shows answer/reject mode ..when i answer the phone become black screen amd keep vibrate.
Trying to call ...the phone call wizard has stoped wait/stop.
Things solved : Again can send and receive sms/mms
Camera works again and flashes
Sec android wizard works ...
Pit file euro open worked. I'm still having problems .
I checked. Again to see ...i tryied to install a singapore firmware nf6 I guess that was the problem.

solved mine
pisicutumic said:
Hello guys what is described up is happening same to me ... tryied to update firmware from sammobile with a stock firmware Vodafone Romania and Odin show me some new lines when it updates like NON NHUL and a TGZ ZT etc ... suddenly failed to update .. and the phone freezed ... messagge was FAILED to update .. I did a restart and the two comps showed and the text : failed to upgrade firmware etc etc ... try use emergency firmware update trough kies ... restarted V Down +home +power : ) tryied to reinstal my fisrt NC2 Poland firmware succeded but
1. no sound
no camera
no music I guess That is a problem with the new Firmware ?Q? Probably we can ask MR. Chainfire or someone hwo knows ? I tryied all things ... but nothing happened even to restore data from kies /backup/trough Odin reflash old backup with TRP/CWM.
ANY ADVISE ? Never download even from sammobile or sammupdate if they say is ok if you never saw someone hwo succes
NEWS : I've noticed that suddenly when try to update again my Note3 shows only one language Chinese , probably becouse this new update NF at the end is for chinese exinos ????
1.Tryied to install CM last nightlies ...now the device work lmost 90%.
Bugs : No sound yet ...but i can acces settings sounds
E-mail has stoped
When i receive a call the phone shows answer/reject mode ..when i answer the phone become black screen amd keep vibrate.
Trying to call ...the phone call wizard has stoped wait/stop.
Things solved : Again can send and receive sms/mms
Camera works again and flashes
Sec android wizard works ...
Pit file euro open worked. I'm still having problems .
I checked. Again to see ...i tryied to install a singapore firmware nf6 I guess that was the problem.
Click to expand...
Click to collapse
-bro my note3 is back.. just flash the singapore latest firmware at flash it via odin your problem will be solved! Godbless

NEWS
ian_drimworld73 said:
-bro my note3 is back.. just flash the singapore latest firmware at flash it via odin your problem will be solved! Godbless
Click to expand...
Click to collapse
I saw now the CSC is XSP this is the only prb but also is csc free no bloatware.also you can root back again and you can restore your old settings except :
1. CSC settings and APP settings that camed with your original firmware
2. when insert your sim back you will be notified to update internet settings to your provider ( for me Vodafone RO) , you can change them back to google.com . is ok THX for your apreciation.

Collection of potential camera fixes for Nougat (Black screen, crashes) - Suggestions

Hi all,
I finally managed to get a Nougat ROM running on my device - except for the camera. It keeps showing a black screen (closes and pops up in intervals of about 1s). I of course searched the forum but it looked like noone has really managed to find a reliable solution. First some background for my device: VNS-L31 (Dual Sim) which was running on fully stock/fully working C432B160 firmware (no root, locked bootloader, after factory reset) and then upgraded to Nougat C432B370 using FirmwareFinder (FullOTA-MF-PV). Installation worked fine, everything running as expected except for the camera - as said. I exactly followed the steps outlined in this thread here: https://forum.xda-developers.com/hu...android-7-emui-5-0-vns-l-cb360-links-t3565117
Factory resetting after upgrading doesn't solve the issue. After upgrading to B370, I also updated to C432B388 - but to no avail. What I find a little strange is this: Connecting the device to the computer and investigating the device info correctly shows build/device/manufacturer etc. However, in build.prop it shows information about the NRD90M test-keys release with generic_a15 device. Could this hint at some issue? Also, checking the device info with
Code:
*#*#2846579#*#*
shows this: Manufacture information: NEMO_L21E_VB. I actually expected something with "L31" there - but well, I also don't really know what this specific thing stands for.
Now, here are certain things I came across when looking for solutions:
Suggestion by @Meticulus: https://forum.xda-developers.com/showpost.php?p=69990309&postcount=226
I tried the suggestion by Meticulus, but unfortunately it didn't work. Does there exist a modification for newer builds that might work? (I just don't understand why that should help - to me it looks moreorless like restarting the camera).
Some fix in build.prop mentioned by @danielegta : https://forum.xda-developers.com/showpost.php?p=72280947&postcount=7
I have absolutely no idea what the build.prop modification is supposed to be. Can anyone elaborate?
A TWRP related fix: http://www.htcmania.com/showpost.php?p=25093316&postcount=31
A bit afraid to try the TWRP fix by BadWolf. It seems to be for B328 builds... So I am a bit unsure whether I should try it on newer build. According to members in the German android-hilfe.de forum, it once solved these issues, but as said for older builds.
Edit: I tried the fix on B370 but it has no effect.
Use the fix in #3, but reflash system.img if the fix doesn't help: https://forum.xda-developers.com/showpost.php?p=70069246&postcount=26
Unfortunately this also didn't work for me
Use TWRP-flashable .zip files as given in this thread here: https://forum.xda-developers.com/huawei-p9lite/how-to/nougat-official-firmware-t3512932
I tried this today, but unfortunately it ends up in the same state as I was when upgrading B160 -> B370 using Firmware Finder. Everything except for the camera works.
Edit: I notice that in TWRP there are always errors about not being able to mount /data and /cust. Is this normal or does it hint at some error/malfunction when updating via flashable zip?
Use TWRP-flashable .zip as in #5 but instead of flashing the two .zip without restarting the device, first flash update.zip, then restart phone, flash Nougat TWRP, flash update_data_full_VNS_Lxx_xx_xx.zip as described in this post: https://forum.xda-developers.com/showpost.php?p=70704697&postcount=7
Tried this in the following way: stock MM -> unlock bootloader and flash TWRP -> flash update.zip -> flash Nougat TWRP -> flash update_data_. Doesn't help. Also I cannot confirm what I read somewhere here on xda (some user mentioned that his camera was working when he only flashed the update.zip - this is not true for me).
Other things I tried for uprading the OS that are not necessarily meant to fix the camera issue, but might:
Use B336 as intermediate step: B160 => B336 => B370 (=> B388) as suggested by @vozilo here: https://forum.xda-developers.com/huawei-p9lite/how-to/how-to-b388-nougat-maybe-b381-guide-t3612072
Unfortunately this does not solve the issue. The camera doesn't work in any of the versions flashed after B160.
Go from B160 direcly to B388: didn't help
Does anyone know of something else that might help or could someone maybe comment on the "known" fixes, especially if there might be some changes that could be done to commands/build.prop or even local.prop that eventually help?
Thank you very much,
theluk

_theluk_ said:
Hi all,
I finally managed to get a Nougat ROM running on my device - except for the camera. It keeps showing a black screen (closes and pops up in intervals of about 1s). I of course searched the forum but it looked like noone has really managed to find a solution. First some background for my device: VNS-L31 (Dual Sim) which was running on fully stock/fully working C432B160 firmware and then upgraded to Nougat C432B370 using FirmwareFinder. Installation worked fine, everything running as expected except for the camera as said. I exactly followed the steps outlined in this thread here: https://forum.xda-developers.com/hu...android-7-emui-5-0-vns-l-cb360-links-t3565117
Factory resetting doesn't solve the issue. Afterwards, I also updated to C432B388 to no avail. What I find a little strange is this: Connecting the device to the computer and investigating the device info correctly shows build/device/manufacturer etc. However, in build.prop it shows information about the NRD90M test-keys release with generic_a15 device. Also, checking the device info with shows this: Manufacture information: NEMO_L21E_VB. I actually expected something with "L31" there - but well, I also don't really know what this specific thing stands for.
Now, here are certain things I came across when looking for solutions:
Suggestion by Meticulus: https://forum.xda-developers.com/showpost.php?p=69990309&postcount=226
I tried the suggestion by Meticulus, but unfortunately it didn't work. Does there exist a modification for newer builds that might work? (I just don't understand why that should help - to me it looks moreorless like restarting the camera).
Some fix in build.prop: https://forum.xda-developers.com/showpost.php?p=72280947&postcount=7
I have absolutely no idea what the build.prop modification is supposed to be. Can anyone elaborate?
A TWRP related fix: http://www.htcmania.com/showpost.php?p=25093316&postcount=31
A bit afraid to try the TWRP fix by BadWolf. It seems to be for B328 builds... So I am a bit unsure whether I should try it on newer build. According to members in the German android-hilfe.de forum, it once solved these issues, but as said for older builds.
Does anyone know of something that might help or could someone maybe comment on the "known" fixes?
Thank you very much,
theluk
Click to expand...
Click to collapse
I had the same problem, and i fixed it by (un)rooting and (un)rooting again

Could you please elaborate a little bit more on what you exactly did? Because for me I was fully stock (including locked bootloader) when upgrading from B160 to B370. Right after the upgrade finished I did a factory reset and the problem already appeared. Are you suggesting to root, unroot and root again? I mean I can try, but I don't see why this could help, so please let me know if I got your point correctly

_theluk_ said:
Could you please elaborate a little bit more on what you exactly did? Because for me I was fully stock (including locked bootloader) when upgrading from B160 to B370. Right after the upgrade finished I did a factory reset and the problem already appeared. Are you suggesting to root, unroot and root again? I mean I can try, but I don't see why this could help, so please let me know if I got your point correctly
Click to expand...
Click to collapse
Ok so usually u should upgrade like 160>b336>b370... The problem might be that you missed a step, not sure though. Try to factory reset first, then go back to b160 and to b336 and then to b370

Unfortunately your suggestion didn't work for me. But it also looks like FF didn't "send" all of the update package to the updater. I chose the 1.6GB FullOTA-MF-PV for B336 but in the system updater it only downloaded 1.2GB. I suspect the data update wasn't downloaded which surely caused issues. Will have to try that again, I guess

_theluk_ said:
Unfortunately your suggestion didn't work for me. But it also looks like FF didn't "send" all of the update package to the updater. I chose the 1.6GB FullOTA-MF-PV for B336 but in the system updater it only downloaded 1.2GB. I suspect the data update wasn't downloaded which surely caused issues. Will have to try that again, I guess
Click to expand...
Click to collapse
try updating through the stock updater

mjz2cool said:
try updating through the stock updater
Click to expand...
Click to collapse
Unfortunately the stock updater doesn't show any updates. So I have to enforce this by using the proxy method provided in Firmware Finder. As I understood this is the "fully" official way of updating, since it does use the "system update" feature provided inside settings of the phone. I will try it again later today to see what could've gone wrong. Maybe I'll just try one of the other B336 firmwares that are listed as FullOTA in FF.

Major update to OP - including new stuff and new information about what I tried. Any other suggestions? I am out of ideas for now and will probably have to live with MM until Huawei has solved this issue

After a suggestion to try VNS-L21 firmware I did, after flashing the corresponding oeminfo. And indeed this worked nicely. Upgrading to Nougat B370 worked and camera is working as well.

_theluk_ said:
after flashing the corresponding oeminfo
Click to expand...
Click to collapse
Hello,
Sorry but I'm a noob, can you explain to me what do you mean by "flashing the corresponding oeminfo" ? Does it mean you had to somehow "trick" your phone so it believes it's L21 instead of L31 or something ?
I have the same problem on the phone of my girlfriend (although I don't recall it's a dual sim one), I'd really like to solve this.
Thank you

_theluk_ said:
...
Suggestion by @Meticulus: https://forum.xda-developers.com/showpost.php?p=69990309&postcount=226
I tried the suggestion by Meticulus, but unfortunately it didn't work. Does there exist a modification for newer builds that might work? (I just don't understand why that should help - to me it looks moreorless like restarting the camera).
...
Click to expand...
Click to collapse
Ah, one of number of my statements taken out of context. When I worked on CM13, initially only the P9 Lite was supported. After a NEMO user tested this, which was proof of concept that the nemo camera could work on my p9 lite ROM, I added support for NEMO in my AOSP ROMs. So, the reason this helped was that it restarted the camera to work with NEMO and not VENUS, for which it was originally started.
As for your problem, Developer Options -> Take Bug Report ->FULL and post?

Note 4 N910C Emergency Call only (Not Registered to Network) IMEICERT:PASS (IMEI Ok )

Greetings Folks
I have a N910C and as mentioned in title recently I got stuck in to this issue
How it happened
I had CF-Rooted my phone and Odin flashed TWRP for custom ROMS so I tried a few and was not getting the perfomance thought SimplROM would do it for me in order to install that ROM it said in instructions to install latest Modem and Bootloader
So i tried downloading the ones given in v6C BL was downloaded but CP kept on giving me errors getting stuck at 7% on mega so being stupid I downloaded DPCB(MODEM) While ROM was offering DPK4
So everything went fine until after boot I realized am facing Not Registered to Network
Since I had experienced this before on other phone I went ASAP in dialer to check my IMEI & SN both are still intact
I knew about EFS unfortunately I backed it up on Phone Storage which was wiped for ROM and I forgot (So dont have EFS Backup )
I do recall years ago back when I had S3 I experienced this and sometimes flashing different firmware(CSC ,Modem) fixed it
What I have tried so far
I have already tried several stock ROMs most of em had DPI1 Baseband except 2 other ROMS no luck
tried combination file method too (the one that helps downgrade to kitkat i believe ) no luck
Tried XEO repair Firmware no luck
any suggestions ??
and on that contrary now that I am not on stock is there any way to find out which CSC and Stock ROM this phone originally was one or came with with IMEI or Serial I believe ?
Thanks in Advance

Anyone??

under the battery there's the serial number
install on your pc samsung smart switch program
run it with option of emergency software recovery - device initialisation
input the model of your phone
input the serial number
start
have patience and a good connection
your phone will (eventually) get the latest official firmware
https://www.blogtechtips.com/2017/06/24/easily-restore-samsung-device-firmware-with-smart-switch/
at least you'll have a working phone with stock rom
from here on you can try again and get informed better on what to do
good luck

w41ru5 said:
under the battery there's the serial number
install on your pc samsung smart switch program
run it with option of emergency software recovery - device initialisation
input the model of your phone
input the serial number
start
have patience and a good connection
your phone will (eventually) get the latest official firmware
https://www.blogtechtips.com/2017/06/24/easily-restore-samsung-device-firmware-with-smart-switch/
at least you'll have a working phone with stock rom
from here on you can try again and get informed better on what to do
good luck
Click to expand...
Click to collapse
Hey there bud I have almost tried most of fixes I could I'll give Smart Switch a try as I recall I checked before it didn't have initialization just the recovery mode, while in Kies 3 I did try initialization method by model and SN but it prompted device doesn't support initialization
Anyways do you think it could fix network?
Sent from my Pixel 2 XL using Tapatalk

crossmedia said:
Hey there bud I have almost tried most of fixes I could I'll give Smart Switch a try as I recall I checked before it didn't have initialization just the recovery mode, while in Kies 3 I did try initialization method by model and SN but it prompted device doesn't support initialization
Anyways do you think it could fix network?
Click to expand...
Click to collapse
Maybe restore the efs from recovery, if you have a backup that was working.

w41ru5 said:
Maybe restore the efs from recovery, if you have a backup that was working.
Click to expand...
Click to collapse
Jist checked not getting initialization option on smart switch ill see a work around it if its a version thing , as for working backup I lost it mate it was in twrp folder in phone storage it got wiped recovery softwares out there only help recovering media mostly if mass storage mount was option could have tried recovering for PC but that has been long gone since ICS
Sent from my Pixel 2 XL using Tapatalk

Yep. Same problem as mine. Im kinda lost now since i dont have anything; even in stock rom it cannot go beyond connecting to my carrier. It only able to read my contact.
Im guessing its a motherboard problem? Isnt it @w41ru5?

VannM said:
Yep. Same problem as mine. Im kinda lost now since i dont have anything; even in stock rom it cannot go beyond connecting to my carrier. It only able to read my contact.
Im guessing its a motherboard problem? Isnt it @w41ru5?
Click to expand...
Click to collapse
I don't know. Usually it's a modem issue when not recognizing the sim.
If it's a 910F snapdragon it might be the infamous eMMC issue.
If you have an EFS backup try to restore it from recovery TWRP.

Assuming its modem problem, its related to motherboard i guess, right?
Finally got the phone working, only to discovered that SIM not working. Really wasting my time and hype!
Plus, its hard to search for n910c replacement board here.

VannM said:
Assuming its modem problem, its related to motherboard i guess, right?
Finally got the phone working, only to discovered that SIM not working. Really wasting my time and hype!
Plus, its hard to search for n910c replacement board here.
Click to expand...
Click to collapse
The firmware, not the physical one.
Did you try to flash the 4 files repair firmware?
This is an example, I don't know what phone you have
https://firmware.gem-flash.com/index.php?a=downloads&b=folder&id=7081
Did you try the SmartSwitch pc program?

"...4 file repair..."- what? Ive google it until im almost run out of data here and you have a possible solution? You must be active in note4 forum.
One thing i noticed that, the IMEI and Serial Number are different from the sticker included.
I will try it, but not immediately; waiting for thurday-friday for data renewal.
My phone is n910c
EDIT : just checked the page you gave. I have few question;
What should i do with the files? What are the step? What are the program needed?
Is it related to SmartSwitch as you mention; need to use it?
Thanks!

VannM said:
"...4 file repair..."- what? Ive google it until im almost run out of data here and you have a possible solution? You must be active in note4 forum.
One thing i noticed that, the IMEI and Serial Number are different from the sticker included.
I will try it, but not immediately; waiting for thurday-friday for data renewal.
My phone is n910c
EDIT : just checked the page you gave. I have few question;
What should i do with the files? What are the step? What are the program needed?
Is it related to SmartSwitch as you mention; need to use it?
Thanks!
Click to expand...
Click to collapse
1. It's good you still have the IMEI. Not so important if they're different from the sticker. Where did you buy the phone from?
2. So if you go to check the 4 files repair, you need to search on that site the files for a 910C.
3. Did the phone worked on your country provider? If yes, maybe you need to search for the 4files corresponding to your region code.
4. These 4files have to be flashed with Odin
https://zfirmware.com/download-samsung-repair-firmwares/
5. SmartSwitch is an alternative to get the latest firmware for your phone according with the model and serial number.
https://www.sammobile.com/forum/threads/29914-SmartSwitch-Install-amp-update-or-replace-firmware

the "firmware.gem" are useless. the error says i need another package (i assume a quota) to download the needed files.
im currently testing "zfirmware", but have a doubt since it only give 1 type file (which country is it i dunno). but yeah, since my phone like that, it wouldnt hurt to try
EDIT : yep, nothing changed. the device not even bricked.

VannM said:
the "firmware.gem" are useless. the error says i need another package (i assume a quota) to download the needed files.
im currently testing "zfirmware", but have a doubt since it only give 1 type file (which country is it i dunno). but yeah, since my phone like that, it wouldnt hurt to try
EDIT : yep, nothing changed. the device not even bricked.
Click to expand...
Click to collapse
If something does not work, why do you give up so easy?
http://www.mediafire.com/file/a2fdo0xm9nat5jt/N910CXXS2DPJ3_N910CZTO2DPE2_ZTO.zip - this is marshmallow
https://androidfilehost.com/?fid=24269982087001472 - this is for lolipop
Put the phone in download mode, open Odin and try.
And try the smartswitch also.

w41ru5 said:
If something does not work, why do you give up so easy?
Click to expand...
Click to collapse
That hurts. A lot. Explanation below.
w41ru5 said:
http://www.mediafire.com/file/a2fdo0xm9nat5jt/N910CXXS2DPJ3_N910CZTO2DPE2_ZTO.zip - this is marshmallow
https://androidfilehost.com/?fid=24269982087001472 - this is for lolipop
Put the phone in download mode, open Odin and try.
And try the smartswitch also.
Click to expand...
Click to collapse
I tried files from LP and MM. It didnt work. And also smartswitch.
I was hoping that it will brick the phone (if i ever missed a step or incorrect file) but it didnt.
Might as well try looking for replacement board (or even a refurbished note4).
Thanks though for the suggestion @w41ru5!

Greetings again folks reading your replies above I have been trying almost every fix there is out there
First of all about Emergency Calls Only/Not Registered on Network
It can be due to several causes its can be Hardware ie faulty modem
it can be bad network coverage
it can be bad simcard
it can be SW with EFS problems or maybe even on rare occasion a modem file that you flashed
EFS can be either bad IMEI with CERT : FAIL or Just Network with IMEI and SN intact
just dial *#0011*# and see if you have CERT : PASS ( also someone with good IMEI/CERT and working network can share screenshot so i can compare whats wrong)
I am certain mine is EFS related because it happened after flashing modem DPCB modem via ODIN (I had TWRP EFS backup but the blunder I made was backing it up on phone storage and being careless forgot it was there and was wiped for custom ROM flashing process)
So far what I have tried
Combination File Method (and even downgrade to KK 4.4.4 )
Repair Firmware that include AP,BL,CP,CSC and even PIT
Kies 3 or Older Smart Switch says (Device doesn't support initialization ) since initialization feature was removed by Samsung on newer Smartswitch(since it was being used for wrong reasons? read somewhere)
Several different firmware's
OTA update
My IMEI CERT says PASS if only we had a network patch like Ariza Patch (for Galaxy S3) for Note 4 then we would be in luck so far at this point I dont think flashing ROM's would even help with bad EFS our only luck is Box e.g Z3x or Octo dont know if we are allowed to talk about those here (ill edit post if not)
these box applications have Network Patch for most Samsung models but I don't see one for N910C in most versions
for those with bad IMEI they can try writing good cert or efs on note 4 since they have already lost it I am sitting on it because my EFS is good on that part and for some reason box app isnt allowing me to back up my CERT if I am able to back up current cert then ill give those a try but I would prefer current IMEI since in my country IMEI should be verified to use the phone or you have to pay tax
I know its Bad EFS for sure because using Box application I chose reset EFS(after backing up current faulty EFS with good IMEI) upon reboot phone's imei was changed with no SN network came back for few seconds then gone again ,this happened to many users that have tried resetting EFS so I restored my original EFS
if anyone here with N910C and root can give me EFS folder I can corelate if any file required for network is missing since i have good IMEI
Cheers!

Help with NFC Crashing - AT&T S8 Active

Hey,
Need some help. My brand new AT&T S8 Active arrived yesterday. Since I am located outside the US I'm stuck with utilising Odin to update the software.
The current version listed on the AT&T website was 5CSK1 and I was able to track down the update:
https://forum.xda-developers.com/showpost.php?p=81251867&postcount=743
It installed successfully, everything is going well however I am unable turn on NFC. The toggle found in the settings menu is off and when I attempt to switch it on it greys out for a few seconds then the 'NFC keeps stopping' error appears on the bottom of the screen.
I've cleared the cache/data for the NFC app - no luck,
I've performed a factory reset via recovery menu - no luck.
I've installed the previous build 5CSJ3 from: https://forum.xda-developers.com/showpost.php?p=80903399&postcount=187 with a factory reset straight after - no luck.
I'm currently back on the latest K1 build.
Logcat shows errors with 'libnfc_nci' and a 'Fatal Exception' for the 'com.android.nfc' process. And to top it all off the NFC app is draining my battery.
If anyone can help me that would be awesome.

dchalkley said:
Hey,
Need some help. My brand new AT&T S8 Active arrived yesterday. Since I am located outside the US I'm stuck with utilising Odin to update the software.
The current version listed on the AT&T website was 5CSK1 and I was able to track down the update:
https://forum.xda-developers.com/showpost.php?p=81251867&postcount=743
It installed successfully, everything is going well however I am unable turn on NFC. The toggle found in the settings menu is off and when I attempt to switch it on it greys out for a few seconds then the 'NFC keeps stopping' error appears on the bottom of the screen.
I've cleared the cache/data for the NFC app - no luck,
I've performed a factory reset via recovery menu - no luck.
I've installed the previous build 5CSJ3 from: https://forum.xda-developers.com/showpost.php?p=80903399&postcount=187 with a factory reset straight after - no luck.
I'm currently back on the latest K1 build.
Logcat shows errors with 'libnfc_nci' and a 'Fatal Exception' for the 'com.android.nfc' process. And to top it all off the NFC app is draining my battery.
If anyone can help me that would be awesome.
Click to expand...
Click to collapse
ugh, the active line... there hasnt ever been much support for those. All you can really do is keep flashing the stock firmware and hope that the errors resolve themselves.
Side note: have you noticed how they stopped making the active phones? They were a dismal failure. All they are is the regular phone in a case that you cant take off :/

dchalkley said:
Hey,
Need some help. My brand new AT&T S8 Active arrived yesterday. Since I am located outside the US I'm stuck with utilising Odin to update the software.
The current version listed on the AT&T website was 5CSK1 and I was able to track down the update:
https://forum.xda-developers.com/showpost.php?p=81251867&postcount=743
It installed successfully, everything is going well however I am unable turn on NFC. The toggle found in the settings menu is off and when I attempt to switch it on it greys out for a few seconds then the 'NFC keeps stopping' error appears on the bottom of the screen.
I've cleared the cache/data for the NFC app - no luck,
I've performed a factory reset via recovery menu - no luck.
I've installed the previous build 5CSJ3 from: https://forum.xda-developers.com/showpost.php?p=80903399&postcount=187 with a factory reset straight after - no luck.
I'm currently back on the latest K1 build.
Logcat shows errors with 'libnfc_nci' and a 'Fatal Exception' for the 'com.android.nfc' process. And to top it all off the NFC app is draining my battery.
If anyone can help me that would be awesome.
Click to expand...
Click to collapse
Might try redownloading a different firmware from a differ location. I had this issue on a lg back in the day the camera wouldnt work no matter what I always restored stock with one firm I had. And it ended up being a bad download. Another possibility is a bad NFC chip. If it's new I'd have it warranted

Thankyou, Thankyou Youdoofus and TheMadScientist for your advice.
Woke up early today (3am) with coffee in hand I tried again downloading the K1 and J3 builds; neither worked.
Unfortunately there's no alternative download for them... Google points to the XDA forums which seem to come from some Russian forum.
I've gone to an earlier build - 5CSI3 - https://forum.xda-developers.com/showpost.php?p=80505887&postcount=186 which works.
So it's not a NFC chip issue, yay. Now, just need to figure out what I'll do when the next update hits at the end of this month.

dchalkley said:
Thankyou, Thankyou Youdoofus and TheMadScientist for your advice.
Woke up early today (3am) with coffee in hand I tried again downloading the K1 and J3 builds; neither worked.
Unfortunately there's no alternative download for them... Google points to the XDA forums which seem to come from some Russian forum.
I've gone to an earlier build - 5CSI3 - https://forum.xda-developers.com/showpost.php?p=80505887&postcount=186 which works.
So it's not a NFC chip issue, yay. Now, just need to figure out what I'll do when the next update hits at the end of this month.
Click to expand...
Click to collapse
Make sure your using the latest odin build 3.13. I dont have an active. **** I read it wrong so it does work on other builds?

TheMadScientist said:
Make sure your using the latest odin build 3.13. I dont have an active. **** I read it wrong so it does work on other builds?
Click to expand...
Click to collapse
Yeah, it's working on the 5CSI3 build from October 2019, there's been two recent updates since then (and another will come at the end of the month). I don't know what's happening as no one else has reported this issue .
Just wanting to be on the most recent version for security and the annoyance of having data wiped every update.
Edit: Yeah, Odin v3.13.1 . No errors being displayed, all green.

This issue is very likely to be caused by 3rd party sim unlock or FRP removal and meddling with knox.
I have been trying to get around this problem and it seems it is either a security measure to disable nfc payments on triggering knoxguard or problem with modem.
this problem started after CSJ3 update afaik and only on some phones, if someone can explain this would be great.
Solution:
You will lose all data so backup is recommended
Remove your SIM card, re-install the firmware with ODIN and check Nand Erase auto reboot and F. reset time
Check your KG status(checking or prenormal) on the bootloader, and in settings>device care you will see Security is disabled and it crashes when you click it.
I also noticed the settings menu is weird with many broken options and dailer codes dont work anymore.
EDIT: Workaround Solution:
THIS IS FOR G892A ONLY who have problem with NFC after updating to builds after December 2019
Disclaimer: do at your own risk and can break your phone signal or system detected as rooted/custom
note: you will lose all data, ONLY check "Auto Reboot" and "F. Reset Time" in odin
1) Backup your data
2) Delete your google account, so FRP : OFF in bootloader (this can cause problems if not done)
3) Flash 5 firmware files G892AUCS5CTC1 (latest rom with march 2020 security) and get back to bootloader
4) Flash 3 files from G892AUCS5CSI3 : BL, CP and CSC
(odin will say PASS, but recovery will give error)
5) select wipe data partition then reboot to system
when the phone starts you will see NFC logo in statusbar means you are successful
if you get errors while using odin: flash combination file : G892AUCU5ASD1 if this doesnt work it means you have different problem (cable, socket, pc, bad chip)
i tried flashing CP file only and phone booted into UPLOAD mode, so dont panic if you get into UPLOAD mode just reboot with 3 buttons to recovery and start over

Vcek said:
This issue is very likely to be caused by 3rd party sim unlock or FRP removal and meddling with knox.
I have been trying to get around this problem and it seems it is either a security measure to disable nfc payments on triggering knoxguard or problem with modem.
this problem started after CSJ3 update afaik and only on some phones, if someone can explain this would be great.
Solution:
You will lose all data so backup is recommended
Remove your SIM card, re-install the firmware with ODIN and check Nand Erase auto reboot and F. reset time
Check your KG status(checking or prenormal) on the bootloader, and in settings>device care you will see Security is disabled and it crashes when you click it.
I also noticed the settings menu is weird with many broken options and dailer codes dont work anymore.
EDIT: Workaround Solution:
THIS IS FOR G892A ONLY who have problem with NFC after updating to builds after December 2019
Disclaimer: do at your own risk and can break your phone signal or system detected as rooted/custom
note: you will lose all data, ONLY check "Auto Reboot" and "F. Reset Time" in odin
1) Backup your data
2) Delete your google account, so FRP : OFF in bootloader (this can cause problems if not done)
3) Flash 5 firmware files G892AUCS5CTC1 (latest rom with march 2020 security) and get back to bootloader
4) Flash 3 files from G892AUCS5CSI3 : BL, CP and CSC
(odin will say PASS, but recovery will give error)
5) select wipe data partition then reboot to system
when the phone starts you will see NFC logo in statusbar means you are successful
if you get errors while using odin: flash combination file : G892AUCU5ASD1 if this doesnt work it means you have different problem (cable, socket, pc, bad chip)
i tried flashing CP file only and phone booted into UPLOAD mode, so dont panic if you get into UPLOAD mode just reboot with 3 buttons to recovery and start over
Click to expand...
Click to collapse
Hello There!..kind of new about this so..long story short..
Phone had Android 8, and I really love Night mode on Android 9, so...I've found BL, AP, CP, CSC, USER Data ROM for GALAXY S8 ACTIVE AT&T Unlocked, however..I am a little bit afraid of any NAND Erase.
I am not an expert, but I can tell you are. By any chance do you have any vide or graphic tutorial abot how you can perform these actions? It is very odd that I am unable to have any *# codes working, and lately, I've received this odd message about NFC Service has stopped, so...any graphic step by step guide will be highly appreciated it.
I've tried ....soft reset, then factory reset, then flash again ODIN (BL, AP,CP, CSC and USER DATA ) But I have no idea how to back up my data, and it will be very helpful to have G892AUCS5CSI3 as well.
Thank you very much for your time, I hope you can help me and I appreciate very much your time.
The one that I have is AP_G892AUCS5CTC1_CL16888298_QB29841048_REV00_user_low_ship_MULTI_CERT_meta_OS9.tar
BL_G892AUCS5CTC1_CL16888298_QB29841048_REV00_user_low_ship_MULTI_CERT.tar
CP_G892AUCS5CTC1_CP15398738_CL16888298_QB29841048_REV00_user_low_ship_MULTI_CERT.tar
CSC_ATT_G892AATT5CTC1_CL16888298_QB29841048_REV00_user_low_ship_MULTI_CERT.tar
USERDATA_G892AUCS5CTC1_CL16888298_QB29841048_REV00_user_low_ship_MULTI_CERT.tar

SOLVED!
So...I've followed the steps to install only BL, CP and CSC using G892AUCS5CSI3...however, the system started as usual, and actually did not work =(
RESOLUTION:
INSTALL THE FULL G892AUCS5CSI3. Worked as magic =)
thank you for the thread!!

moncd6 said:
Hello There!..kind of new about this so..long story short..
Phone had Android 8, and I really love Night mode on Android 9, so...I've found BL, AP, CP, CSC, USER Data ROM for GALAXY S8 ACTIVE AT&T Unlocked, however..I am a little bit afraid of any NAND Erase.
I am not an expert, but I can tell you are. By any chance do you have any vide or graphic tutorial abot how you can perform these actions? It is very odd that I am unable to have any *# codes working, and lately, I've received this odd message about NFC Service has stopped, so...any graphic step by step guide will be highly appreciated it.
I've tried ....soft reset, then factory reset, then flash again ODIN (BL, AP,CP, CSC and USER DATA ) But I have no idea how to back up my data, and it will be very helpful to have G892AUCS5CSI3 as well.
Thank you very much for your time, I hope you can help me and I appreciate very much your time.
The one that I have is AP_G892AUCS5CTC1_CL16888298_QB29841048_REV00_user_low_ship_MULTI_CERT_meta_OS9.tar
BL_G892AUCS5CTC1_CL16888298_QB29841048_REV00_user_low_ship_MULTI_CERT.tar
CP_G892AUCS5CTC1_CP15398738_CL16888298_QB29841048_REV00_user_low_ship_MULTI_CERT.tar
CSC_ATT_G892AATT5CTC1_CL16888298_QB29841048_REV00_user_low_ship_MULTI_CERT.tar
USERDATA_G892AUCS5CTC1_CL16888298_QB29841048_REV00_user_low_ship_MULTI_CERT.tar
Click to expand...
Click to collapse
You can backup your data with Samsung backup and restore to Samsung cloud or to your PC with Samsung's Smart Switch app.
As for tutorial I'll try to make one with images for the latest ROM G892AUCU5CTF4 dated 20-Aug-2020 with August security patch. I'll upload it later as I still have to backup my phone before updating.

Thanks!
Thank you so much!
Is it G892AUCU5CTF4 a estable versión for S8 Active? Or does it has any other bugs? I had to "downgrade" and now things are pretty cool, however, I would love to have the newest version. Thank you!

moncd6 said:
Thank you so much!
Is it G892AUCU5CTF4 a estable versión for S8 Active? Or does it has any other bugs? I had to "downgrade" and now things are pretty cool, however, I would love to have the newest version. Thank you!
Click to expand...
Click to collapse
It doesn't have any bugs but some people have issue with flashing new builds, if you have this issue just install CSI3 build or earlier

dchalkley said:
It installed successfully, everything is going well however I am unable turn on NFC. The toggle found in the settings menu is off and when I attempt to switch it on it greys out for a few seconds then the 'NFC keeps stopping' error appears on the bottom of the screen.
I've cleared the cache/data for the NFC app - no luck,
I've performed a factory reset via recovery menu - no luck.
I've installed the previous build 5CSJ3 from: https://forum.xda-developers.com/showpost.php?p=80903399&postcount=187 with a factory reset straight after - no luck.
... And to top it all off the NFC app is draining my battery.
Click to expand...
Click to collapse
Same. I also tried CTA2 and CTL1. Everything after CSI3 has NFC crashing and excessive battery drain. I've tried multiple flashes on multiple phones.
dchalkley said:
I tried again downloading the K1 and J3 builds; neither worked.
Unfortunately there's no alternative download for them... Google points to the XDA forums which seem to come from some Russian forum.
I've gone to an earlier build - 5CSI3 - https://forum.xda-developers.com/showpost.php?p=80505887&postcount=186 which works.
So it's not a NFC chip issue, yay. Now, just need to figure out what I'll do when the next update hits at the end of this month.
Click to expand...
Click to collapse
Same.
dchalkley said:
I don't know what's happening as no one else has reported this issue .
Edit: Yeah, Odin v3.13.1 . No errors being displayed, all green.
Click to expand...
Click to collapse
Same here. I used Odin 3.14.1, though.
Vcek said:
Solution:
You will lose all data so backup is recommended
Remove your SIM card, re-install the firmware with ODIN and check Nand Erase auto reboot and F. reset time
Click to expand...
Click to collapse
This did not work for me, not even with "Nand Erase" checked.
moncd6 said:
It is very odd that I am unable to have any *# codes working, and lately, I've received this odd message about NFC Service has stopped, so...
Click to expand...
Click to collapse
Same. The problem of the secret dialer codes not working parallels the NFC problem for me; that is to say that it doesn't work on any firmware after CSI3.

moncd6 said:
SOLVED!
So...I've followed the steps to install only BL, CP and CSC using G892AUCS5CSI3...however, the system started as usual, and actually did not work =(
RESOLUTION:
INSTALL THE FULL G892AUCS5CSI3. Worked as magic =)
thank you for the thread!!
Click to expand...
Click to collapse
Can you please upload G892AUCS5CSI3? it's all dead links i got

rerenz said:
Can you please upload G892AUCS5CSI3? it's all dead links i got
Click to expand...
Click to collapse
Same. I'm not sure where I originally got it from, but here's a reupload from my archives. I created a list of MD5 checksums if you care to check the five files for corruption.

voidxor said:
Same. I'm not sure where I originally got it from, but here's a reupload from my archives. I created a list of MD5 checksums if you care to check the five files for corruption.
Click to expand...
Click to collapse
Finally, it works! My NFC is back. Thanks, pal.