Related
Whenever I tap on it to turn it on it will say connection error, or something of that sort. It worked fine on stock before I rooted it and went to a custom rom. I restored the stock rom and went back to it.. and now it stopped working?
What should I do?
Does anyone have any input?
could be the rom. are you trying to use wallet?
Some roms its buggy and some it works, from what ive gathered its a kernel thing and what you will have to do is play with kernel/rom combos until you get a working one.
besides wallet what would you use it for?
tevil said:
could be the rom. are you trying to use wallet?
Some roms its buggy and some it works, from what ive gathered its a kernel thing and what you will have to do is play with kernel/rom combos until you get a working one.
besides wallet what would you use it for?
Click to expand...
Click to collapse
Want to know what's pathetic? It doesn't work on STOCK 2.3.6.... STOCK. But it works on bugless beast (ics 4.0.3).
& I use it for Android Beam..
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.
For those of you who took the 4.3 ota what is your opinion of the updated ,and did you come from a custom rom.I was thinking of talking official 4.3 just curious to here feedback on it ,I know once I do it bootloader is locked for good .I am on Liquid smooth love it but I miss the Samsung features and having a glitch free phone I know ill get back on the verizon ota, been running custom rom since first week of owning phone think im ready to go back stock as long as official 4.3 is good
=phatreno;49148087]For those of you who took the 4.3 ota what is your opinion of the updated ,and did you come from a custom rom.I was thinking of talking official 4.3 just curious to here feedback on it ,I know once I do it bootloader is locked for good .I am on Liquid smooth love it but I miss the Samsung features and having a glitch free phone I know ill get back on the verizon ota, been running custom rom since first week of owning phone think im ready to go back stock as long as official 4.3 is good[/QUOTE]
Why take the OTA when you can just flash the stock Rom? I personally like it but I've always liked TW roms
kieso said:
=phatreno;49148087]For those of you who took the 4.3 ota what is your opinion of the updated ,and did you come from a custom rom.I was thinking of talking official 4.3 just curious to here feedback on it ,I know once I do it bootloader is locked for good .I am on Liquid smooth love it but I miss the Samsung features and having a glitch free phone I know ill get back on the verizon ota, been running custom rom since first week of owning phone think im ready to go back stock as long as official 4.3 is good
Click to expand...
Click to collapse
Why take the OTA when you can just flash the stock Rom? I personally like it but I've always liked TW roms[/QUOTE
I know that there' one out there you can flash and maintain a unlocked bootloader but reading the thread sounds like there's a lot of issues with it I use my phone for work so need something 100% eliable Liquid is almost there but still have to do battery pulls get f/c's ,I did have another phone so it didn't matter now this is my only phone
let me rephrase that didn't mean take the ota but flash the official 4.3 which would lock boot loader to take the ota I would have to revert to stock then take the ota easier just flashing 4.3
After a long time flashing custom rom and kernel on my wife S3 and always hear complaints about issue, I decided to flash stock 4.3. Now she's happy with her phone, everything is working smoothly and the phone is pretty fast and snappy, battery life is the best. I have to say, 4.3 is a great improvement over 4.1.2. My recommendation is if you like to play around with flashing custom rom and ok with all the bugs hear and there then it would be fine, but if you want a daily driver, stable phone then stock 4.3 is the way to go. While she's on custom rom, many times when we at a party and when she tried to take picture the camera FC, or displayed weird color, the gps acting up, phone lockup needed to pull the battery to reset etc...Again, if you want a stable, good battery life, go with stock 4.3 and with just root.(I need root to install wifi tethering). Now she has a perfect phone and no more complaints.
buhohitr said:
After a long time flashing custom rom and kernel on my wife S3 and always hear complaints about issue, I decided to flash stock 4.3. Now she's happy with her phone, everything is working smoothly and the phone is pretty fast and snappy, battery life is the best. I have to say, 4.3 is a great improvement over 4.1.2. My recommendation is if you like to play around with flashing custom rom and ok with all the bugs hear and there then it would be fine, but if you want a daily driver, stable phone then stock 4.3 is the way to go. While she's on custom rom, many times when we at a party and when she tried to take picture the camera FC, or displayed weird color, the gps acting up, phone lockup needed to pull the battery to reset etc...Again, if you want a stable, good battery life, go with stock 4.3 and with just root.(I need root to install wifi tethering). Now she has a perfect phone and no more complaints.
Click to expand...
Click to collapse
that sounds like what I needed to here,did you flash 4.3 or revert to stock and take the ota not sure if there's a difference I already downloaded the stock 4.3
I've had zero issues on the 4.3 rom.
Make a backup and give it a run.
Sent from my SCH-I535 using xda app-developers app
phatreno said:
that sounds like what I needed to here,did you flash 4.3 or revert to stock and take the ota not sure if there's a difference I already downloaded the stock 4.3
Click to expand...
Click to collapse
It's depended on what apps you installed on your phone, most of them should be fine with 4.3. When ever I upgrade to a new version, I like a clean install. Do a factory reset (this will wipe all your installed apps and reset your phone back to factory condition, make sure you have a backup of your apps), then let the upgrade run. Once done use saferoot to root.
from crack flasher to stock
i've been a crack flasher since my DX days, having flashed just a couple days after getting my S3. I've been on Hyperdrive, Synergy, AOKP, OSE, stock and various versions of CM to include the best, Mastamoons unofficial.
had to get a replacement phone, and as i was setting it up, the damn thing updated to 4.3 itself.
now... i still get that crackflashing urge, but i will admit, i like having the phone stock. i can make it look like its on any of the other roms, just with minor alterations.
antenna's on the latest is the best i've ever seen, everything works great, and don't see the lag on 4.3 TW as on others.
guess i can live with this for a while, and i do have faith in the DEV community that someone will break the latest, just as in previous versions. But for now, i can live with stock as everything works great!
:victory:
buhohitr said:
It's depended on what apps you installed on your phone, most of them should be fine with 4.3. When ever I upgrade to a new version, I like a clean install. Do a factory reset (this will wipe all your installed apps and reset your phone back to factory condition, make sure you have a backup of your apps), then let the upgrade run. Once done use saferoot to root.
Click to expand...
Click to collapse
ok thanks
Please go here for any further...http://forum.xda-developers.com/showthread.php?t=2575661
The Problem/Symptoms: I've been running a version of last CM10.2 for the past year. On February 20th, I was able to send a single SMS and then subsequent texts failed. I could still receive SMS, send/receive MMS, send/receive calls and send/receive data. If I toggle airplane mode/reboot I can send another SMS and then subsequent sms are undeliverable.
What wont work: Flashing to CM11 does not change the issue.
Disabling Voice+ does not change the issue
Factory Reset does not change the issue
Workarounds: Toggle Airplane mode
Switching Mobile Network to CDMA only (not permanent)
Change your number to a different area code
Going back to a Touchwiz based ROM
The Solution
net-cat said:
Alright. I think I've refined my process and it results in having a newer radio as well as not having to ODIN things or do dd commands.
NOTE: This isn't fully tested. When I did this, my phone wasn't showing the issue. I did this after doing my original procedure, but the GPS stopped working after I updated the radio from VRALF2 to VRBMB1. You shouldn't need to do the original procedure for this to work, but I haven't tested that. At the very least, the original procedure still works and this one can be used afterward if you need the newer radio. (GSM support...)
Ideally, we'll want to get to a procedure that doesn't use ODIN or dd. Hopefully this is a step in that direction.
Requirements:
A rooted stock ROM of the VRUCML1/4.3 vintage. I used Scott's Stock Rooted Knox Free VRUCML1 - 4.3 - DeOdex - V2. (Thread here.)
VRBMB1 AIO Flash, available here. (Thread here.)
I'm going to assume you know how to boot into and use recovery.
NOTE: Do NOT let the stock ROM install any updates.
Starting with my CM11 M3 install, I did a nandroid backup. (Recovery is CWM Touch 6.0.4.5, but I doubt that matters.)
Flash the VRBMB1 AIO.
Wipe data and cache.
Flash the stock ROM.
Boot into the stock ROM.
The reprovisioning seems to happen as a part of ROM's initial boot up.
Send a few text messages to test. (I sent them to Twitter.)
Launch the Maps application, turn on your GPS and let it get a lock. If you don't, when you boot back into your ROM, you probably won't have working GPS.
This would be a good time to back up your IMEI if you haven't already done so.
Reboot into your recovery, wipe data/cache and restore your nandroid backup.
At this point, you'll be running your preferred ROM with a less archaic radio than my previous post.
DO NOT UPGRADE YOUR RADIO. The moment I upgraded my radio, the problem came back!
CM11 M3 will work just fine with the old radio. I've rebooted several times over the last few hours and it still works fine. (Time will tell if it's a long term fix or not.)
Click to expand...
Click to collapse
buffal0b1ll said:
I put a MB1 aoi zip in my dropbox for you. It's from invisblek.org which isn't working now for some reason https://www.dropbox.com/s/7b1aqspo40fxl00/VRBMB1.aio.zip
Click to expand...
Click to collapse
Notes: There are threads for the S4 with this identical problem. All updated information I have seen is listed above. If anyone knows more please post as I am going to keep this updated. If this does/doesn't work for you please post and let the community know. Feel free to hit the thanks button if it works for you.
This exact thing happened to me. I tried many fixes with no luck. After hours of hacking around in settings, I found a ROM of verizon's 4.3 OTA update and flashed that through ODIN. My texts are working just fine again. Kind of a cheap method of fixing my problem. I wish I could have taken more time to find a fix, but I needed to be able to communicate with people that day.
Stock 4.3 is kind of lame:
-4.3 is killing my battery faster than ever. CM11 had me going for days without charging and now I've needed to charge everyday.
-Stock 4.3 is laggier/slower than CM11. It tends to stutter for me.
-4.3 came with a new boot loader which no developers have exploited to install custom ROMs yet. This leaves you stuck with Verizon bloat. I hate all these damn apps. Going to try to safe root & see if I can't do some cleanup work.
Enough ranting. Just wanted to let you know you are not alone with this problem. Hopefully someone will figure it out. Missing my cyanogen mod already
It seems this problem has happened on other phones also running Cyanogenmod. I found this thread http://forum.xda-developers.com/showthread.php?t=2654822
It looks like the symptoms have all showed up at the same time approximately. (February 19th, 2014). Still looking for a better answer than going back to stock TW...
Edit: And another thread http://forum.xda-developers.com/showthread.php?t=2659280 This one suggests its all AOSP roms. But it seems many people are unaffected... I don't understand why/how.
edit2: and another thread http://forum.xda-developers.com/showthread.php?p=50627899
Just looking for more info
Sent from my SCH-I535 using Tapatalk
Dex954 said:
Just looking for more info
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
SO this is the current status that I know.
The problem happens for everyone with a 570/717 area codes + on verizon + running Cyanogenmod (possibly any AOSP) + while connected to LTE which started on Feb 20th (the day before KitKat came out offically).
Current Workarounds:
Switch to TouchWiz based Roms
Switch your radios to be CDMA only
Call verizon and switch your number to a different area code
I know the workarounds all suck but that all I know for now. Switching SIM cards won't work. If I anyone knows anything more please feel free to let me know.
I'm 717
Sent from my SCH-I535 using Tapatalk
I have still be unable to find a solution for this issue. I think I have to give up on CM and go back to a TW based. If I hear anything new I'll update the post but I don't have the time to be wasting on my phone at the moment. If someone finds or hears of a fix or if it magically goes away as it started, please post it.
And spread the word if there are any other ROMs that this is occurring on. It seems the pool of those affected is just too small.
I have already had to give up. Been running slows tw. I take it Verizon didn't get back to you?
Sent from my SCH-I535 using Tapatalk
Here is my thread guys. Same issue. I am gonna get on the fog horn with some Verizon buddies I have http://forum.xda-developers.com/showthread.php?t=2662658
DreamFX said:
Here is my thread guys. Same issue. I am gonna get on the fog horn with some Verizon buddies I have http://forum.xda-developers.com/showthread.php?t=2662658
Click to expand...
Click to collapse
Godspeed my friend.
Anyone try aosp to see if fixed yet?
Nope. Still having issues. Tried gummy and cm. TW based roms are fine. In 717.
capt730 said:
Nope. Still having issues. Tried gummy and cm. TW based roms are fine. In 717.
Click to expand...
Click to collapse
I try every other day. 717 for me. Remaining hopeful it's fixed... One day...
What gapps are you using? I have been using the PA 0Day gapps. Going to try the gapps package from invisblek and see if that makes a difference.
Sent from my GT-N5110 using XDA Premium 4 mobile app
capt730 said:
What gapps are you using? I have been using the PA 0Day gapps. Going to try the gapps package from invisblek and see if that makes a difference.
Sent from my GT-N5110 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
It won't. It isn't software dependent. People who had already flashed builds prior to the 20th magically had issues starting on that date, so it isn't a problem with new builds, and it only happens to those in the 717-570 areas so it isn't a problem with AOSP code. It has to be a Verizon network issue, I just have no idea how.
Sent from my SCH-I535 using XDA Premium 4 mobile app
I have run TW base roms almost 100% of the time. Prior to the 20th, I had flashed cm11 3 or 4 times to see if camera worked and was never on it more than a day. I also had issues where music in my sd card wasn't being found but it was fine on TW. Could it be the unified build causing an issue? I have no issues on Clean Rom 8, wicked sensations or old and slows stock based roms.
*Edit* I have installed Gummy and CM 11 with PA Mini Modular apps and the CM Gapps from Invisiblek, let it set up. I then shut it down, removed battery and sim and then put everything back in and still the same issue. 1st text message goes through, then the rest after that just fail. I tried regular message app, Hangouts and Verizon messaging. All same results. I go back to my CR8 backup and all is fine. It's bizarre because everything else seems to be working fine and is very fast & smooth.
capt730 said:
I have run TW base roms almost 100% of the time. Prior to the 20th, I had flashed cm11 3 or 4 times to see if camera worked and was never on it more than a day. I also had issues where music in my sd card wasn't being found but it was fine on TW. Could it be the unified build causing an issue? I have no issues on Clean Rom 8, wicked sensations or old and slows stock based roms.
*Edit* I have installed Gummy and CM 11 with PA Mini Modular apps and the CM Gapps from Invisiblek, let it set up. I then shut it down, removed battery and sim and then put everything back in and still the same issue. 1st text message goes through, then the rest after that just fail. I tried regular message app, Hangouts and Verizon messaging. All same results. I go back to my CR8 backup and all is fine. It's bizarre because everything else seems to be working fine and is very fast & smooth.
Click to expand...
Click to collapse
It can't be an issue with the unified builds because going back and flashing an older build yields the same results. If you're willing to make the trade-off, you can set your phone to CDMA only. Texts will send, but you'll have no 3G or 4G.
I'm ok with using CR8, Beans or other stock roms. Can't see paying for LTE and not using it lol. Was curious to see how aosp has been coming along and sms was really the only issue I was having.
Obaterista93 said:
It can't be an issue with the unified builds because going back and flashing an older build yields the same results. If you're willing to make the trade-off, you can set your phone to CDMA only. Texts will send, but you'll have no 3G or 4G.
Click to expand...
Click to collapse
I was using masta's 10.2 build for over 6 months without even thinking about flashing new builds. The 20th is when the problem started for me. Upgrading to CM11 didn't change it. I just installed Hyperdrive and everything is back to normal.
I wish I could go back to CM but it just doesn't work in this area. And I don't know what I can do about it,
Whisk_33 said:
I was using masta's 10.2 build for over 6 months without even thinking about flashing new builds. The 20th is when the problem started for me. Upgrading to CM11 didn't change it. I just installed Hyperdrive and everything is back to normal.
I wish I could go back to CM but it just doesn't work in this area. And I don't know what I can do about it,
Click to expand...
Click to collapse
Basically. I've talked to a few friends who have worked for carriers and stuff, and everyone is stumped as to how something like this can even happen. Luckily I'm pretty much always in WiFi so I can survive on CDMA only.
So, I'm buying this to replace my evo 4g and I was wondering how I would go about using a custom ROM for this and having the apns and data working correctly.
I plan to activate it on Ting.
To be a bit clearer, I want to use a custom ROM and I want to be sure that it'll work. So first, can anyone on Ting confirm that they're running a custom ROM (preferably KitKat) with no problems?
And I assume I'd have to activate the phone first, then install a custom ROM. Would I have any problems doing that? Would the apns be messed up? Or should everything be fine as long as I activate the phone and update everything on stock before installing a ROM? Reason I ask is because I know some Roms don't allow the *#*# thing needed to activate a phone on a new network.
Thanks!
I am using mine on Ting. I had used my first Q as unrooted stock JB, which worked pretty well for a year, but then it reached a near--bricked state where it wouldn't boot past the yellow Sprint screen. I couldn't resolve this in a timely fashion, so wound up buying a second Q which runs stock ICS, but failed to download the stock JB update.
In the meantime, I unlocked both phones' bootloaders, and tried a few kItkat ROMs on my original phone before settling on CM 10.2, which is a JB ROM. I then switched my Ting activation (back) to this phone. The lack of #*# commands isn't really a problem with respect to re-activation, but it is a problem with respect to PRLs and (perhaps) APNs. I recommend Ting activation and a PRL update prior to installing your custom ROM.
Like others, I would like to learn about a stable kitkat ROM where bluetooth, wifi, and phone data/sms/calling all work reliably. My other primary requirement is the ability to play DRM'd downloaded Amazon Prime Music, which didn't work on the kitkat ROMs I tried, but does work on my JB ROM.
Sent from my XT897 using Tapatalk