Related
I've been using the Jellybro kang of CyanogenMod (10-20121120-SKANK-d2vzw). I had NFC working as recently as the 11/3 build, but when I flashed the 11/5 build NFC broke.
I tried flashing a stock JB (deodexed and rooted) rom, enabling NFC and restoring back to my nandroid, but the NFC still wasn't fixed. I've tried the NFCfix.zip and that didn't work either.
Do I need to flash stock.vzw_root66.tar in Odin and turn on NFC? Or is there a specific stock rom I should be using?
What am I doing wrong, or what else should I try? I've done my best to search the forums and figure out a solution, so figure me if there has been clearly hashed out elsewhere.
Thanks!
[edit] Solution: flash this NFC fix http://www.mediafire.com/?y6vx27cpaasqhxs
i use an ICS rom to fix my NFC, have you tried that instead of JB TW?
ddurandSGS3 said:
i use an ICS rom to fix my NFC, have you tried that instead of JB TW?
Click to expand...
Click to collapse
Let me give it a shot. Are you suggesting any TW ICS rom or specifically a stock ICS? Can you link me to the rom you use, please?
Thanks!
Have a look at http://rootzwiki.com/topic/36150-aosp-and-nfc/page__st__10 .... on that page, someone created a flashable zip that fixed my NFC, direct link to zip (flash via recovery) http://www.mediafire.com/?y6vx27cpaasqhxs
*edit* I see that you've tried an NFC fix before, so had I and it didn't work. This one did!
i use a stock rooted from scottt that i have saved on my laptop to fix my NFC.
ive seen people ahve success wth the zips floating around, try that first its quickest easiest
Polymira said:
Have a look at http://rootzwiki.com/topic/36150-aosp-and-nfc/page__st__10 .... on that page, someone created a flashable zip that fixed my NFC, direct link to zip (flash via recovery) http://www.mediafire.com/?y6vx27cpaasqhxs
*edit* I see that you've tried an NFC fix before, so had I and it didn't work. This one did!
Click to expand...
Click to collapse
Perfect! That fixed it. Thank you very much.
try this
http://forum.xda-developers.com/showpost.php?p=32029713&postcount=8367
No matter what I do, I cannot get my NFC to enable. I've flashed both the posted fixes and I've reverted completely back to stock, unrooted ICS, and several other ICS TW ROMs and NFC will not turn on. Has this happened to anyone? Does anyone have any ideas on how to fix it? I was on PA 2.52 and had used wallet for a few weeks before NFC quit. Now it's just completely dead
majixx11 said:
No matter what I do, I cannot get my NFC to enable. I've flashed both the posted fixes and I've reverted completely back to stock, unrooted ICS, and several other ICS TW ROMs and NFC will not turn on. Has this happened to anyone? Does anyone have any ideas on how to fix it? I was on PA 2.52 and had used wallet for a few weeks before NFC quit. Now it's just completely dead
Click to expand...
Click to collapse
I'm having the exact same problem and seems like no one can help with this
On my S4 I9505 I can turn on S4 but then nothing happens whenever I try to scan any tag... Any ideas? I flashed different stock roms and tested 3 different batteries with visible loop antennas on them. Nothing works.
I have had Bean's Jelly 'Beans' ROM installed on my GS3 since I first got the phone in October. Verizon had to replace my phone this past week, and once I received the new one, I did the customary procedure of rooting it and installing a custom ROM. However, after I install a ROM, the Camera always breaks (I get the message "Camera Failed" and the camera screen is black when I open the stock camera app).
I have already researched the issue, and it seems there is a history of some S3's coming out of the box with a broken camera, but it is important to note that the camera works fine as long as I revert back to the stock (and rooted) rom. When installing the Jelly 'Beans' ROM, I have selected 4 different kernel options(Beans custom stock, imoseyon lean kernel, ktoonsez, and faux kernel), thinking that may be the issue, but each one still leaves a broken camera. I have also tried installing an aftermarket camera app, in case the S3 camera apk is somehow broken, and have flashed the Photosphere Camera. Nothing will get the camera to work (and yes, my battery is fully charged).
Not being able to install a custom ROM is a pretty big deal to me, and not having a working camera is a deal breaker. Unfortunately, I won't be able to get Verizon to replace the phone again since it all works on the stock ROM. Does anyone have any ideas? I have tried several things I have read in the forums, but nothing has worked so far. Thank you all in advance for your help!
tfc87 said:
I have had Bean's Jelly 'Beans' ROM installed on my GS3 since I first got the phone in October. Verizon had to replace my phone this past week, and once I received the new one, I did the customary procedure of rooting it and installing a custom ROM. However, after I install a ROM, the Camera always breaks (I get the message "Camera Failed" and the camera screen is black when I open the stock camera app).
I have already researched the issue, and it seems there is a history of some S3's coming out of the box with a broken camera, but it is important to note that the camera works fine as long as I revert back to the stock (and rooted) rom. When installing the Jelly 'Beans' ROM, I have selected 4 different kernel options(Beans custom stock, imoseyon lean kernel, ktoonsez, and faux kernel), thinking that may be the issue, but each one still leaves a broken camera. I have also tried installing an aftermarket camera app, in case the S3 camera apk is somehow broken, and have flashed the Photosphere Camera. Nothing will get the camera to work (and yes, my battery is fully charged).
Not being able to install a custom ROM is a pretty big deal to me, and not having a working camera is a deal breaker. Unfortunately, I won't be able to get Verizon to replace the phone again since it all works on the stock ROM. Does anyone have any ideas? I have tried several things I have read in the forums, but nothing has worked so far. Thank you all in advance for your help!
Click to expand...
Click to collapse
I'm going to go ahead and help myself out and respond to my own question. Upon even further research (yes, I know everyone says people don't look hard enough), I believe the issue relates to the Firmware version. Supposedly the newest firmware breaks the camera unless it's on the stock rom. There are modified firmwares out there that change the part that breaks the camera, but I believe I am going to downgrade the modem and all from what was pre-installed and see if it works.
tfc87 said:
I'm going to go ahead and help myself out and respond to my own question. Upon even further research (yes, I know everyone says people don't look hard enough), I believe the issue relates to the Firmware version. Supposedly the newest firmware breaks the camera unless it's on the stock rom. There are modified firmwares out there that change the part that breaks the camera, but I believe I am going to downgrade the modem and all from what was pre-installed and see if it works.
Click to expand...
Click to collapse
if its a custom Rom (Stock but maby some extras such as overclocking or somethin) they are Sometimes Broken They will try to fix it sometimes, upgrading to a higher android version it is sometimes is Quite hard to Fix everything.
Trozzul said:
if its a custom Rom (Stock but maby some extras such as overclocking or somethin) they are Sometimes Broken They will try to fix it sometimes, upgrading to a higher android version it is sometimes is Quite hard to Fix everything.
Click to expand...
Click to collapse
I downgraded the firmware to VRBMB1 and went back to that custom rom and the camera works flawlessly. I read in the firmware forum that the new firmware is doing this to a lot of people...I just happened to have one of the phones that came with it pre-installed. Problem solved and hopefully this post will help someone out...if not...it helped myself out at least.
tfc87 said:
I downgraded the firmware to VRBMB1 and went back to that custom rom and the camera works flawlessly. I read in the firmware forum that the new firmware is doing this to a lot of people...I just happened to have one of the phones that came with it pre-installed. Problem solved and hopefully this post will help someone out...if not...it helped myself out at least.
Click to expand...
Click to collapse
maby just wait till next firmware and they will fix it?
Trozzul said:
maby just wait till next firmware and they will fix it?
Click to expand...
Click to collapse
Yeah I'm sure it will be fixed. Either way, I don't recommend that newest firmware...signal seems to be the worst out of all of the ones I've tried...for me at least. Seems to be a lot of complaints out there with it anyways.
Similiar issue?
I am having a similiar issue with my US Cell GS3. I bought the donor version of mskip's Samsung Galaxy S3 Unified Toolkit and rooted my device yesterday now my camera is doing the same thing...fires up to a black screen, hangs a few seconds then says camera failed. I'm running Android 4.1.2, build R530UVXAMD4. I've read in a few places that I may have to either downgrade my kernel or flash with some sort of alternate firmware.
Any assistance provided is greatly appreciated!
Sterling8356 said:
I am having a similiar issue with my US Cell GS3. I bought the donor version of mskip's Samsung Galaxy S3 Unified Toolkit and rooted my device yesterday now my camera is doing the same thing...fires up to a black screen, hangs a few seconds then says camera failed. I'm running Android 4.1.2, build R530UVXAMD4. I've read in a few places that I may have to either downgrade my kernel or flash with some sort of alternate firmware.
Any assistance provided is greatly appreciated!
Click to expand...
Click to collapse
did you figure this out?
im having same problem
I had the same problem while flashing one of my friend's S3...i just did the whole process once again..and everything works fine
Sent from my Galaxy Note II using xda premium
tfc87 said:
I have had Bean's Jelly 'Beans' ROM installed on my GS3 since I first got the phone in October. Verizon had to replace my phone this past week, and once I received the new one, I did the customary procedure of rooting it and installing a custom ROM. However, after I install a ROM, the Camera always breaks (I get the message "Camera Failed" and the camera screen is black when I open the stock camera app).
I have already researched the issue, and it seems there is a history of some S3's coming out of the box with a broken camera, but it is important to note that the camera works fine as long as I revert back to the stock (and rooted) rom. When installing the Jelly 'Beans' ROM, I have selected 4 different kernel options(Beans custom stock, imoseyon lean kernel, ktoonsez, and faux kernel), thinking that may be the issue, but each one still leaves a broken camera. I have also tried installing an aftermarket camera app, in case the S3 camera apk is somehow broken, and have flashed the Photosphere Camera. Nothing will get the camera to work (and yes, my battery is fully charged).
Not being able to install a custom ROM is a pretty big deal to me, and not having a working camera is a deal breaker. Unfortunately, I won't be able to get Verizon to replace the phone again since it all works on the stock ROM. Does anyone have any ideas? I have tried several things I have read in the forums, but nothing has worked so far. Thank you all in advance for your help!
Click to expand...
Click to collapse
I have had the same problem when I installed a certain custom rom (can't remember the name ) on my s3. But later I found that during installation of the rom, there was an option to choose one of four kernels, and if I chose Boeffla kernel (included in the options) my camera wouldn't work. So I just reverted back to the stock kernel and walah! My camera works again.
Hey All,
I purchased a jawbone UP this weekend and was running Slim Rom on my HD. The way the UP works is it syncs its data through the 3.5mm headphone jack. The first one I bought wouldn't get recognized at all on any 4.2.2 ROM and when I revert back to a 4.1.2 based ROM it would recognized and unlock and everything, just woudlnt sync. I ended up with a defect DOA device and had to get a new one.
the new one however now works fine on the 4.1.2 ROM. i havent tried to switch back to 4.2.2 yet but i have a hunch that it won't work.
I wanted to know if anyone else has one of these and if they are using a 4.2.2 ROM and have it working. if so what ROM and Kernel combo are you using? I didnt wanna go nuts flashing random crap just to see if it works but i'll get a feeler here and see
thanks,
It's a known issue with 4.2.2 ROM. I had the issue with my Bionic too. I ended up returning it.
I can vouch that it works on the carbon night lies.
But it works with stock
I had the same issue with my Buttered AOKP ROM. Since I used SS3, I switched to my stock ROM and everything works fine. So, I just switch ROMs (a matter of a couple of reboots) whenever I want to sync data. I know it sucks... But till Jawbone supports custom ROMs, this seems the only way to use the UP app.
I have installed UP on both ROMS (my stock ROM (4.0.3) for syncing and on my 4.2.2 ROM for my other data-wrangling stuff).
GPE kit-kat
I have the galaxy s4... i was running gummy rom 4.4.2 and had this problem. I didn't want to go stock cuz i would lose tethering ability unless I modded this separately, so i tried the Google play edition and this works for me. have been using since with no problems.
xavierroy said:
I had the same issue with my Buttered AOKP ROM. Since I used SS3, I switched to my stock ROM and everything works fine. So, I just switch ROMs (a matter of a couple of reboots) whenever I want to sync data. I know it sucks... But till Jawbone supports custom ROMs, this seems the only way to use the UP app.
I have installed UP on both ROMS (my stock ROM (4.0.3) for syncing and on my 4.2.2 ROM for my other data-wrangling stuff).
Click to expand...
Click to collapse
Hi guys,
As the title stated, I couldn't get the wifi to work at all. I tried flashing both stock and custom roms, but I still couldn't make it work. When I slide the wifi "on", it immediately slides back to "off". It didn't even scan for networks. Does anyone know what is the cause of this problem and how can I fix it? The last working custom rom I used was the Infusion rom. Right after I install the stock firmware, the wifi no longer works anymore.
Thanks.
failmuch said:
Hi guys,
As the title stated, I couldn't get the wifi to work at all. I tried flashing both stock and custom roms, but I still couldn't make it work. When I slide the wifi "on", it immediately slides back to "off". It didn't even scan for networks. Does anyone know what is the cause of this problem and how can I fix it? The last working custom rom I used was the Infusion rom. Right after I install the stock firmware, the wifi no longer works anymore.
Thanks.
Click to expand...
Click to collapse
I got the same exact problem after I flashed the faux kernel. :/ Were you able to find a solution yet?
Hi all,
Did anyone able to use gps with custom rom ( I would say CM base). I research and try everything that's I could find here but not success.
Every time I do clean wipe everything including a internal storage. So that will nothing left behind.
I know that stock is work fine with gps. some said that install and replace stock but I have no idea that what file will left in our device when we delete all.
Always had the same problem when running Paranoid Android (not tried other ROMs). Had to return to stock, where GPS runs fine. Would also love to kknow how people have got it functioning.
I am trying too. I modified gps.conf files, tried some workarounds mentioned in cm11 thread like restoring GPS Status backup from stock with titanium so far with no success. Some people say that it works but it doesn't on mine whatever I do.
I run on CM and I don't have any problem. Everything works fine with gps and I didn't use any fix or something similar.
I'm on CM 11-20140627 and I have 1032 phone.
Interesting, why does it work on some while it doesn't on others? Maybe some variants are having problems...
I have xt1033 asia version.
spajdo said:
I run on CM and I don't have any problem. Everything works fine with gps and I didn't use any fix or something similar.
I'm on CM 11-20140627 and I have 1032 phone.
Click to expand...
Click to collapse
Which recovery did you use?
CWM
As I wonder is about library missing or some partition need from stock ?
I've also been using the micro gapps package, would this matter?
I had problems with Paranoid Android and GPS too... If anyone know something about that, please comment!
TMaxtor said:
I had problems with Paranoid Android and GPS too... If anyone know something about that, please comment!
Click to expand...
Click to collapse
Hey i found a solution, you have do this flash following in this order.
- flash stock 4.4.4 (depend on your current)
- flash cm
- flash gapp
I try this twice and work like a charm.
Sent from my Moto G using XDA Free mobile app
thestory101 said:
Hey i found a solution, you have do this flash following in this order.
- flash stock 4.4.4 (depend on your current)
- flash cm
- flash gapp
I try this twice and work like a charm.
Sent from my Moto G using XDA Free mobile app
Click to expand...
Click to collapse
I am having he same problem on XT1032 running Carbon ROM. GPS worked fine on stock, no signal with Carbon.
I found many answers saying to flash stock and then reflash custom ROM. I will try it, but I wonder, how does this help? Isn't the phone restoring the whole system? Do I have to keep the gps.conf from stock?
I've read in some CM thread on here you need to flash stock ROM then enable GPS and get a lock. Once you've done that then flash your custom rom. Sounds STUPID and dosent make sense I know, but a lot of people say this is how they got it to work.
EDIT: I can confirm. I've just flashed stock 4.4.4 and played around with google maps. Flashed CM11 nightly and my GPS is now working ok
am05 said:
I've read in some CM thread on here you need to flash stock ROM then enable GPS and get a lock. Once you've done that then flash your custom rom. Sounds STUPID and dosent make sense I know, but a lot of people say this is how they got it to work.
EDIT: I can confirm. I've just flashed stock 4.4.4 and played around with google maps. Flashed CM11 nightly and my GPS is now working ok
Click to expand...
Click to collapse
Did you wipe anything, like Dalvik, Cache and Data, or you just flashed it over?
am05 said:
I've read in some CM thread on here you need to flash stock ROM then enable GPS and get a lock. Once you've done that then flash your custom rom. Sounds STUPID and dosent make sense I know, but a lot of people say this is how they got it to work.
EDIT: I can confirm. I've just flashed stock 4.4.4 and played around with google maps. Flashed CM11 nightly and my GPS is now working ok
Click to expand...
Click to collapse
Sorry people, I was so happy to have my phone back working, I forgot to write it back here.
Yes it worked indeed, all I did was flashing back the stock, going outside to have a gps lock with gmaps, then re-flashing back the Carbon. I also kept a copy of the gps.conf, but I never needed it, the GPS got a fix quickly. Working fine so far, it only takes some tens of seconds to fix, from time to time.
I can't remember if I also did all the wiping, I think I didn't, but I made so many trials in a couple days, I am not sure.
Thanks a lot guys!
am05 said:
I've read in some CM thread on here you need to flash stock ROM then enable GPS and get a lock. Once you've done that then flash your custom rom. Sounds STUPID and dosent make sense I know, but a lot of people say this is how they got it to work.
EDIT: I can confirm. I've just flashed stock 4.4.4 and played around with google maps. Flashed CM11 nightly and my GPS is now working ok
Click to expand...
Click to collapse
Yes, this worked for me too on PA.
I couldn't even see a single sat (it wasn't just a lock problem). No matter with gps patch, gpx fix app, or gps.conf I used.
What I did?: Back to stock, lock GPS, flash again the custom ROM (but don't wipe /system!).
Good luck on that guys, it should work for you too.
thestory101 said:
Hi all,
Did anyone able to use gps with custom rom ( I would say CM base). I research and try everything that's I could find here but not success.
Every time I do clean wipe everything including a internal storage. So that will nothing left behind.
I know that stock is work fine with gps. some said that install and replace stock but I have no idea that what file will left in our device when we delete all.
Click to expand...
Click to collapse
GPS works fine on this unofficial CM11 rom for me. Stable daily driver rom for me, YMMV.
General advice is to:
- make sure you get a GPS lock on stock rom first
- flash CM11 (or other custom rom)
There may not be a file left on the device. it may just be that stock contains the code to initialize the GPS functionality on the SoC or chipset firmware. Whatever, it works...