Few days before, I've submitted my phone to service centre for wifi problem, they hv replaced pcb and I received it with KK rom. Now, the camera not working for JB roms. I reflashed it with stock JB rom using sp tools but the problem still as it was.
Previously, I've heard of same problem with persons who received their phone with KK rom out of box.
Had anyone of them resolved their issue???
Related
Hi, I followed the procedure for rooting and flashing galaxy s2 gt-i9100 perfectly. I also downloaded the files for my device only and not any other device. The problem started 2 days back when I was on resurrection remix jelly bean rom with Aliyah kernel. I started to randomly not recieve calls. My friends complained that it would go straight to voicemail. So I took it to the service center and they told me the motherboard was screwed. They installed a new motherboard and the phone was working fine until I flashed cyanogenmod 10 with their own kernel. The problem reappeared. Is the problem because I installed the rom or what?
Dark viper said:
Hi, I followed the procedure for rooting and flashing galaxy s2 gt-i9100 perfectly. I also downloaded the files for my device only and not any other device. The problem started 2 days back when I was on resurrection remix jelly bean rom with Aliyah kernel. I started to randomly not recieve calls. My friends complained that it would go straight to voicemail. So I took it to the service center and they told me the motherboard was screwed. They installed a new motherboard and the phone was working fine until I flashed cyanogenmod 10 with their own kernel. The problem reappeared. Is the problem because I installed the rom or what?
Click to expand...
Click to collapse
Never heard of such a thing, I do not believe that a custom ROM that was compiled for the correct phone model and flashed correctly is likely to screw up the motherboard. Make the phone act funny such as losing calls? Sure, that could happen and could be the ROM or kernel or firmware, but the motherboard? I don't believe so.
I would flash the stock ROM and kernel back and see if the problem occurs again before drawing any other conclusions.
Have you tried switching baseband?
Sent from my GT-I9100 using Tapatalk 2
It could be a bad flash, an incompatible Rom, a conflicting app, bad signal or just bad Carma
I too doubt it can affect a motherboard physically. You can brick your phone when installing if something goes extremely wrong (very rare these days), but the physical board should be just fine.
Did you flash back to stock before taking it to the service center? They might not even be able to read the phone's software if it's not stock.
Most will just send you away if they see you have been flashing roms :-/
I hope it was under warranty, because if they "replaced the Mother board" on your dime, I think you got hosed. It worked fine, because they set it back to Stock.
I think they saw that you flashed a custom ROM and just reversed it to stock and told you they changed the motherboard cause i doubt it is the custom ROM fault.....just yesterday i rooted and flashed such a device and works fine
Maybe its even the baseband version the problem.....once a rom didnt booted up.on a galaxy 5 and after a changed it the device runned well
Sent from my HTC HD2 using Tapatalk 2
Maybe the new custom rom found other cell site for you always check the network and signal.
Anyway the carrier was just messing with about the motherboard they dislike custom roms.
i flashed back to the offical firmware and the problem still was there.
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
Hello everybody!
There's something strange happening on my P5110. Here's the thing... when I use the tablet with one finger, everything moves as smooth as I expect... but when I try to use the pinch to zoom or just the multitouch (2 or more fingers) it may become less responsive and less smooth at the scrolling. The way to fix that is by shutting down the screen and turning it on again (I presume that it's a software issue). I use the stock 4.1.2 rom and I tried with factory reset and by searching the web, with no success. Any ideas?
I hope that someone could help me out with this issue.
Thanks in advance.
Had same problem
Barktooth said:
Hello everybody!
There's something strange happening on my P5110. Here's the thing... when I use the tablet with one finger, everything moves as smooth as I expect... but when I try to use the pinch to zoom or just the multitouch (2 or more fingers) it may become less responsive and less smooth at the scrolling. The way to fix that is by shutting down the screen and turning it on again (I presume that it's a software issue). I use the stock 4.1.2 rom and I tried with factory reset and by searching the web, with no success. Any ideas?
I hope that someone could help me out with this issue.
Thanks in advance.
Click to expand...
Click to collapse
Hi Barktooth ,
I had the same problem with my P5110. I was on stock 4.03 DBT and after the update to 4.1.1 Btu I had the same issue with pinch zoom like you.
I tried everything .. flashing other stock versions, resetting and so on. But the problem stayed. Then i sent it to samsung. They reinstalled the stock 4.03 DBT version. But the Problem wasn't solved. I sent it again to samsung with a video to show them the issue. Now they solved the problem by changing the motherboard. I'm now on stock 4.03 with a new motherboard and without any issue. I think you have to send it to a samsung service center. Did the problem appear after flashing a stock rom?
fredy66 said:
Hi Barktooth ,
I had the same problem with my P5110. I was on stock 4.03 DBT and after the update to 4.1.1 Btu I had the same issue with pinch zoom like you.
I tried everything .. flashing other stock versions, resetting and so on. But the problem stayed. Then i sent it to samsung. They reinstalled the stock 4.03 DBT version. But the Problem wasn't solved. I sent it again to samsung with a video to show them the issue. Now they solved the problem by changing the motherboard. I'm now on stock 4.03 with a new motherboard and without any issue. I think you have to send it to a samsung service center. Did the problem appear after flashing a stock rom?
Click to expand...
Click to collapse
Hi fredy66!
Thanks a lot for the answer. It was exactly the same for me. The issue appeared after flashing the 4.1.2 stock firmware... and is staying even if I flash another firmware or by hard resetting my device. I have far mor problems though... I don't know if there's any Samsung service center around my city and my warranty is gone. I'll try to find one.
Thanks again for the answer!... I thought it was a software issue... but now it is a hardware issue =(.
Issue
Barktooth said:
Hi fredy66!
Thanks a lot for the answer. It was exactly the same for me. The issue appeared after flashing the 4.1.2 stock firmware... and is staying even if I flash another firmware or by hard resetting my device. I have far mor problems though... I don't know if there's any Samsung service center around my city and my warranty is gone. I'll try to find one.
Thanks again for the answer!... I thought it was a software issue... but now it is a hardware issue =(.
Click to expand...
Click to collapse
Hi Barktooth,
This is really strange. Maybe it's a software problem and the service center only couldn't solve it by flashing the normal stock firmware. It's possible that some p5110 needs a special driver because of a problem with the touch controller on some motherboards. Did you update the tablet with kies or by ota? I flashed my p5110 with odin. Have you tried cm? I'm now afraid of flashing again.
fredy66 said:
Hi Barktooth,
This is really strange. Maybe it's a software problem and the service center only couldn't solve it by flashing the normal stock firmware. It's possible that some p5110 needs a special driver because of a problem with the touch controller on some motherboards. Did you update the tablet with kies or by ota? I flashed my p5110 with odin. Have you tried cm? I'm now afraid of flashing again.
Click to expand...
Click to collapse
Hello fredy66!
I flashed the 4.1.2 stock firmware via odin too. I tried reflashing another version without luck. I'm gonna try with the 4.2.2 stock firmware and see if that solves the problem. It's really strange... I had a Galaxy S for a long time and flashed it like there was no tomorrow... nothing happened to that device... it works flawlessly even now. That's why I thought it was a software issue... but it seems that just a few of us had the bad luck =(.
I'll try the 4.2.2 and if it solves the problem, then I'll tell you through this topic
Thanks again for your time!
Hey there everyone.
I flashed skullface's CM, and one of the bugs is that the vibration isn't working, which I am fine with, but later when I returned to stock firmware, the vibration still isn't working! I tried installing stock 4.1.2 and then upgraded to 4.2.2, still vibration isn't working.
I am pretty sure that it isn't a hardware problem since I don't remember dropping it before the problem appeared, and I am sure I did the flashing steps right. Any help would be truly appreciated.
strange,i i did flash skullface's cm in the past,and my vibration still work afterwards.
try flash again and do a complete wipe,see if it got any change,if not,i think you have to send it to service center(make sure you reset the binary count first)
I tried reflashing the stock multiple times after making sure I wiped everything, I can't return it to the service centre cause I bought it from another country.