Just got my 10 today. Rooted and S-Off right out of the box. I'm now in the process of setting it all up and noticed the camera app opens for a second but shows no picture and then closes. I installed Google Camera and upon opening it just hangs. I uninstalled a bunch of stock stuff so something may have broken it, although I didn't touch anything camera related.
Any ideas?
I can't get any camera app to work actually.
thenags said:
I can't get any camera app to work actually.
Click to expand...
Click to collapse
Did you install a custom kernel?
If you are on the latest ROM 180.xxx and using a custom kernel that could be the problem.
fokus said:
Did you install a custom kernel?
If you are on the latest ROM 180.xxx and using a custom kernel that could be the problem.
Click to expand...
Click to collapse
I didn't install a custom kernel, no. I'm using the stock ROM just rooted.
No idea why this worked but I restored my original original backup before making a single change. When it booted it was still booting into the system I had fully setup but with the addition of everything I had deleted. I went through in titanium and deleted all the exact same things again. 1000% the same. And now the camera and everything is functioning as it should.
Now I just gotta wait for an AOSP ROM.
Sent from my 2PS64 using Tapatalk
I just got a replacement US unlocked version, my camera is blurry at a distance, and won't focus at all. Only rooted and S-Off.
Same problem
thenags said:
No idea why this worked but I restored my original original backup before making a single change. When it booted it was still booting into the system I had fully setup but with the addition of everything I had deleted. I went through in titanium and deleted all the exact same things again. 1000% the same. And now the camera and everything is functioning as it should.
Now I just gotta wait for an AOSP ROM.
Sent from my 2PS64 using Tapatalk
Click to expand...
Click to collapse
I've got a new HTC 10 (64GB) Taiwanese stock and received two OTA's after setting it up. It brought the software to 1.80.709.1 but broke the camera in the process! I'm experiencing the same thing as you are. Click on the camera and it shuts in a second without displaying anything in the viewfinder. Try to access the camera from another app, no luck, just black screen.
I bought the device online and have been trying to organise a replacement but it's taking forever. I've done everything relating to the camera (clearing cache/data to updates, downgrades) and even a factory reset but couldn't solve the issue. I'm pretty darn sure it's not a hardware issue because the camera was working fine before I did the two software updates and I did not drop or impact the phone. So I think if I can reflash 1.80.709.1 or go back to my original ROM and re-do the OTAs I might be ok. But how can I do that without rooting... (want to avoid root if I can).
I've been trying to find the stock RUU for the 1.80.709.1 without any luck (closest I got was the TWRP zip but don't want to deal with that if I can avoid). I've got the RUU for 1.80.617.1 from the HTC US site (Int Unlocked/Dev) but I'm not sure if I flash this would something else break. Particularly around LTE reception / Bands.
Any advice?
Related
Hi all,
this is the 3rd time this is happening to me with different ROMs. The problem is:
The phone boots up normal, I can swipe to unlock, enter my PIN, but after pressing OK it won't unlock the SIM. If I lock the screen it won't come back on. It stays black whatever I do. After some time the phone reboots (soft reboot) and everything starts from the beginning.
The first time this happened I was using Modacos Ir9. I had the phone switched off over night and switched it on. Only thing that seemed to help was completely unrooting the phone and rerooting it again.
The second time I was using codeworkx CM9 Builds and tried to update. I restored my nandroid, but it kept happening. Flashing the XXKK1 Radio did the trick here.
Now it is happening again. This time I installed dropbox and the phone froze on the setup wizard...
I don't want to unroot the phone, it takes forever to restore the SD card.
Any advice on this one?
Update:
- Flashed the following radio images without any success: XXKL1, KRKL1, UGKL1 and XXKK1
- Used my older nandroids from CM9 and Modaco Ir10. NOT WORKING
- Wiped every nandroid. NOT WORKING AT ALL
- Reflashed CM9 and Ir10. Still NOT WORKING
I'm so lost I'm going to revert to stock and unroot... and try how far I can throw an 1 month old GNx from the fourth story.
I don't know much on the development part so I don't know why its doing that I can only suggest using odin and going back to stock.
Sent from my Galaxy Nexus using xda premium
I had similar problems with mine once. Only thing that helped me out wasn't unrooting though. A complete factory reset was enough to make me go on again.
I posted a thread here then to ask people if anyone experianced the same but got no reaction what so ever zo I guess "we" are a dark minority.
I don't know what it caused it or what the solution might be but a Factory reset did it for me.
Good Luck!
C-4Nati said:
I don't know much on the development part so I don't know why its doing that I can only suggest using odin and going back to stock.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Last time it was working again after reverting to stock. But I bought it to use Custom Roms
I would say go back to stock w/ odin, Wipe everything and start again.
Diger36 said:
I had similar problems with mine once. Only thing that helped me out wasn't unrooting though. A complete factory reset was enough to make me go on again.
Click to expand...
Click to collapse
Factory Reset wasn't helping unfortunatly.
Flashed the original factory image through fastboot. Now everything is working again. I'm restoring my SD backup now and will try to get CM9 working again.
If it would keep failing in stock I could return the phone. Now I'm left with "hopefully it isn't happening a fourth time" and "My phone doesn't work I need 4 hours to get ich working"
the_alien said:
Factory Reset wasn't helping unfortunatly.
Flashed the original factory image through fastboot. Now everything is working again. I'm restoring my SD backup now and will try to get CM9 working again.
If it would keep failing in stock I could return the phone. Now I'm left with "hopefully it isn't happening a fourth time" and "My phone doesn't work I need 4 hours to get ich working"
Click to expand...
Click to collapse
Fastboot flash stock google images. And your phone isn't bricked. Stop using the term wrong. It's most likely a software issue or you're doing the rom flash procedure incorrectly.
A bricked phone is a phone that is unaw to go into bootloader and recovery mode and cannot start android.
Sent from my Galaxy Nexus using xda premium
zephiK said:
Fastboot flash stock google images. And your phone isn't bricked. Stop using the term wrong. It's most likely a software issue or you're doing the rom flash procedure incorrectly.
A bricked phone is a phone that is unaw to go into bootloader and recovery mode and cannot start android.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Sorry for using the term wrong, I thought it just referes to broken phones.
The ROM flash is correct and it runs for some time and the problem occours after a few days... the only thing that helped was reverting to factory images and after that restore the nandroid from the "broken" Rom.
So the Rom works... than keeps crashing, I do a nandroid backup and only a factory image stops the crashes. But the Rom keeps working after I restore it.
I can't see why this could be a hardware issue. And I can't see how I should explain it to the store "Yes, it is working but not with custom roms, and I bought the Nexus because of custom roms..."
the_alien said:
Sorry for using the term wrong, I thought it just referes to broken phones.
The ROM flash is correct and it runs for some time and the problem occours after a few days... the only thing that helped was reverting to factory images and after that restore the nandroid from the "broken" Rom.
So the Rom works... than keeps crashing, I do a nandroid backup and only a factory image stops the crashes. But the Rom keeps working after I restore it.
I can't see why this could be a hardware issue. And I can't see how I should explain it to the store "Yes, it is working but not with custom roms, and I bought the Nexus because of custom roms..."
Click to expand...
Click to collapse
I'm willing to bet an app is causing it.
Sent from my Galaxy Nexus using xda premium
One of my colleagues had this issue with an early CM9 build on his Nexus S - turned out it was an app that is incompatible with ICS. Every time it tried to launch a notification, poof. So I would have to side with Josh in the post above mine.
A way for you to verify / discredit this theory would be : When you say it works with the stock ROM, are you re-installing everything you have when you are on stock? My understanding from what you've written above is that you're only getting your full suite of apps back when you restore your (presumably custom ROM) nandroid backup...
Potterified said:
One of my colleagues had this issue with an early CM9 build on his Nexus S - turned out it was an app that is incompatible with ICS. Every time it tried to launch a notification, poof. So I would have to side with Josh in the post above mine.
A way for you to verify / discredit this theory would be : When you say it works with the stock ROM, are you re-installing everything you have when you are on stock? My understanding from what you've written above is that you're only getting your full suite of apps back when you restore your (presumably custom ROM) nandroid backup...
Click to expand...
Click to collapse
It can't be any app or ROM because IF it happens, it happens on all ROMs, regardless of wipe or not.
It just happened again and i wiped everything and tried using AOKP MS 3. Wasn't working... So I tried using the phone without the SIM card, because the hell only breaks loose after entering my PIN. And it worked. I could use the phone...
I put it back in and it worked...
I'm restoring my CM9 nandroid right now. I'm hoping it works...
edit: Nope, ripping out the SIM doesn't work. I'm reverting to stock and wait what happens. If it crashes again I'm trying to return it.
Has anybody else had this problem? Everytime the phone reboots, loads of apps break completely, and the only way to fix this is either by moving the app to the storage and back, or by restoring a titanium backup and praying the data is restored
It's a wholly tedious and not a nice thing to do every time you need to rebbot the device. Is there a solution to the problem? I'm using the stock 4.0.3 Rom supplied by Orange, and unlocked and rooted using the htcdev method.
Sent from my HTC One X using xda app-developers app
Hi, something has gone wrong, you'll need to wipe, re-flash etc
freakzone said:
Hi, something has gone wrong, you'll need to wipe, re-flash etc
Click to expand...
Click to collapse
Huh, kinda unusual for a huge carrier like Orange to ship phones with problems that can only be fixed by re-flashing. Probably some meddling on their part that's made it unstable. I'll wipe/flash the normal stock 4.0.3 ROM, and see if that helps.
Kyoraki said:
Huh, kinda unusual for a huge carrier like Orange to ship phones with problems that can only be fixed by re-flashing. Probably some meddling on their part that's made it unstable. I'll wipe/flash the normal stock 4.0.3 ROM, and see if that helps.
Click to expand...
Click to collapse
Three shipped me an HTC Desire and the gmail app crashed every single time with the stock rom. If you wish you can bring it to orange and they will sort it out for you. I assumed you were looking for a different type of solution.
Hey there everyone,
I am honestly at a bit of a loss.
I have an AT&T GS3, and I noticed that all the bloatware was SERIOUSLY draining the battery and hogging up RAM, so I thought it would be a great idea to get a custom rom to enhance my phone.
I used the GS3 Toolkit to flash TWRP recovery. - All went well
I read up on some different Roms, and i chose to install http://forum.xda-developers.com/showthread.php?t=2089821
I installed RLS16
I followed the instructions,
Wipe data/factory reset
Wipe dalvik cache
Wipe /system
I went through the Aroma installer and chose to install the Developer's Pick.
This includes a bunch of little addons like 4.2 camera, gallery, keyboard, etc.
but it also installs lean kernel.
The install went fine, nothing said it failed
but once i was in the rom. Things got terrible.
My phone randomly crashed and shut off, like within minutes each time, camera would crash the phone, causing it to shut off, etc.
So i went through the GS3 toolkit, downloaded and reflashed the stock Rom and recovery.
Once it booted, I keep getting "Unfortunately Messaging has Stopped" and I cannot receive or send text messages, even through other texting programs like Handcent SMS.
No matter what, it keeps crashing (the messaging, not the rom). I factory reset, wiped, everything. Nothing will fix it.
I thought that maybe the stock rom doesnt include stock kernel? So i went online, downloaded the stock kernel, flashed, reflashed stock rom, and STILL the same thing. Messaging has stopped working.
Also as a side note, when i tried to do a google voice search. I get a page saying Sorry and that my computer or phone might be sending network requests or something along those lines.
I cannot think of anything else I can do....
If anyone has any idea, please let me know...
Thanks!
eternalcold said:
Hey there everyone,
I am honestly at a bit of a loss.
I have an AT&T GS3, and I noticed that all the bloatware was SERIOUSLY draining the battery and hogging up RAM, so I thought it would be a great idea to get a custom rom to enhance my phone.
I used the GS3 Toolkit to flash TWRP recovery. - All went well
I read up on some different Roms, and i chose to install http://forum.xda-developers.com/showthread.php?t=2089821
I installed RLS16
I followed the instructions,
Wipe data/factory reset
Wipe dalvik cache
Wipe /system
I went through the Aroma installer and chose to install the Developer's Pick.
This includes a bunch of little addons like 4.2 camera, gallery, keyboard, etc.
but it also installs lean kernel.
The install went fine, nothing said it failed
but once i was in the rom. Things got terrible.
My phone randomly crashed and shut off, like within minutes each time, camera would crash the phone, causing it to shut off, etc.
So i went through the GS3 toolkit, downloaded and reflashed the stock Rom and recovery.
Once it booted, I keep getting "Unfortunately Messaging has Stopped" and I cannot receive or send text messages, even through other texting programs like Handcent SMS.
No matter what, it keeps crashing (the messaging, not the rom). I factory reset, wiped, everything. Nothing will fix it.
I thought that maybe the stock rom doesnt include stock kernel? So i went online, downloaded the stock kernel, flashed, reflashed stock rom, and STILL the same thing. Messaging has stopped working.
Also as a side note, when i tried to do a google voice search. I get a page saying Sorry and that my computer or phone might be sending network requests or something along those lines.
I cannot think of anything else I can do....
If anyone has any idea, please let me know...
Thanks!
Click to expand...
Click to collapse
When you flashed stock, did you flash the one for your carrier? (It should flash the kernel at the same time)
Did you try clearing the messaging app's data/cache?
Did you try flashing another custom ROM to see if you still get the errors? If not, could give 4.2.1 a shot.
BWolf56 said:
When you flashed stock, did you flash the one for your carrier? (It should flash the kernel at the same time)
Did you try clearing the messaging app's data/cache?
Did you try flashing another custom ROM to see if you still get the errors? If not, could give 4.2.1 a shot.
Click to expand...
Click to collapse
Yeah i flashed the one for my carrier. And i figured it would do the kernel, but just in case i tried flashing it separately....
and yeah i did try wiping the data/cache, but i will try it again.
and I could always try flashing another custom rom. Do you have any suggestions? i just want one that works quickly, is stable, and has messaging lol
eternalcold said:
Yeah i flashed the one for my carrier. And i figured it would do the kernel, but just in case i tried flashing it separately....
and yeah i did try wiping the data/cache, but i will try it again.
and I could always try flashing another custom rom. Do you have any suggestions? i just want one that works quickly, is stable, and has messaging lol
Click to expand...
Click to collapse
Look in my sig I don't give suggestion per say cause it's up to the user's preference but I'll always be running something that works.
BWolf56 said:
Look in my sig I don't give suggestion per say cause it's up to the user's preference but I'll always be running something that works.
Click to expand...
Click to collapse
I might try that one out. I was looking at some reviews, someone said there may be Bluetooth issues. I just bought the Moga, and i need BT to work perfecty...
Any input on that?
eternalcold said:
I might try that one out. I was looking at some reviews, someone said there may be Bluetooth issues. I just bought the Moga, and i need BT to work perfecty...
Any input on that?
Click to expand...
Click to collapse
Best thing to do is to read changelogs but for now I'll give you the answer, it has been fixed a few releases ago in Task650's AOKP.
BWolf56 said:
Best thing to do is to read changelogs but for now I'll give you the answer, it has been fixed a few releases ago in Task650's AOKP.
Click to expand...
Click to collapse
Alright, i'll flash that one, i'll post to here when it's finished. Thanks!
Did you check your IMEI?
xBeerdroiDx said:
Did you check your IMEI?
Click to expand...
Click to collapse
Just checked, my IMEI is there.
Also, i found this thread
http://forum.xda-developers.com/showthread.php?t=1804782
but their images wont show. Any idea what route they are taking to solve this??
eternalcold said:
Just checked, my IMEI is there.
Also, i found this thread
http://forum.xda-developers.com/showthread.php?t=1804782
but their images wont show. Any idea what route they are taking to solve this??
Click to expand...
Click to collapse
That guy flashed the bootloaders. I'm not sure what the pictures are supposed to be but they don't seem to lead to anything.
My take on it: Don't play with bootloaders, it's the only way to really brick your phone (if something goes wrong that is).
BWolf56 said:
That guy flashed the bootloaders. I'm not sure what the pictures are supposed to be but they don't seem to lead to anything.
My take on it: Don't play with bootloaders, it's the only way to really brick your phone (if something goes wrong that is).
Click to expand...
Click to collapse
Understood, I wont mess with them.
I really just want to understand a couple things.
1. Why did the ROM I installed before work for everyone else except me? and i followed the instructions.
and 2. after flashing to stock, how am I unable to fix this?
mainly to just learn what went wrong.
Sometimes the reason just...you had a bad flash or something broke down in there. I did the CF easy root method and flashed TWRP in goo manager and then started flashing. I've never tried the toolkit but like anything many times it just depends on the download you got or a bad flash. We've all had several...just hate when it involves rooting or using ODIN.
hednik said:
Sometimes the reason just...you had a bad flash or something broke down in there. I did the CF easy root method and flashed TWRP in goo manager and then started flashing. I've never tried the toolkit but like anything many times it just depends on the download you got or a bad flash. We've all had several...just hate when it involves rooting or using ODIN.
Click to expand...
Click to collapse
Thanks,
Is there any way to repair it?
Alright, so....
I think i have figured out what the issue was. Or by random chance got it fixed.
I was going to try to install the Synergy Rom. And while going through the custom setup, i noticed "Install AOSP Messaging" and "Install TW Messaging"
I chose the TW messaging, and went through the rest of the installer.
For some reason i kept hanging at the "Samsung Galaxy S3" logo, and it would not boot.
(Honestly, i've used custom roms since the HTC Touch Pro 2, and i've NEVER had such issues. And i personally think the TP2 was way more difficult lol)
So I ONCE AGAIN flashed to stock. and randomly the messaging works!
I only can guess that even when flashing the stock rom, it doesnt change something regarding the messaging app. I'm not sure. All i know is that i'm on stock again and everything is working. I highly doubt i'm going to try another custom rom for a while until i have a full understanding of what happened.
But in case anyone else was having this problem, i hope this helped.
So 2 days ago a friend bought an HTC Desire HD. It was working fine, but since it was second hand he wanted to hard reset it, and so he did. After he did that it started doing what I am showing in the video below(but it was with an older version, gingerbread I think). It was also going in CWM 10 sec after it was put into a charger. After I tried installing custom roms and roots, I installed what is said to be a stock ruu:
RUU_Ace_Sense30_S_HTC_WWE_3.12.405.1_Radio_12.65.60.29_26.14.04.28_M_release_225512_signed
Click to expand...
Click to collapse
It is obviously(visually) a newer version of the software the phone uses, than the one it had when he first gave the phone to me.
Nothing seems to have worked at this point, I'm desperate. After that 4th option of the setup(scheduled sync) it just goes black screen with a status bar and nothing. When he first gave it to me it used to display an error that said something like setup couldn't load, and with options to close it, wait for it, or tell HTC about it. It CAN receive SMS and calls, but there just isn't any GUI(menu, or whatever it's called).
I'm also providing a picture of the bootloader below.
I don't need the phone to be rooted or with any particular ROM or version, I just need it working normally.
Any help/assistance will be welcome! Thanks in advance
VIDEO:
youtube.com/watch?v=aNI1t4KjY-0&feature=youtu.be
youtube.com/watch?v=aNI1t4KjY-0&feature=youtu.be
Just makes it easier to click on it. :beer:
Edit: Try booting without the sd card, but aside from that, no idea.
You can also try flashing a stable gb rom see if you get the same issue.
Sent from a dream.
<-------- new user here. cant post links thanks
iLoveAlkohola said:
<-------- new user here. cant post links thanks
Click to expand...
Click to collapse
If you already have s-off and cwm, why not just flash rooted stock rom? It should work fine if the rom can be flashed successfully.
If it is not, it is most probably hardware issues, although i am not so sure myself.
yumm91 said:
If you already have s-off and cwm, why not just flash rooted stock rom? It should work fine if the rom can be flashed successfully.
If it is not, it is most probably hardware issues, although i am not so sure myself.
Click to expand...
Click to collapse
As I said, before installing the newest stock ruu(with which I lost cwm and can''t seem to get it back), I installed some custom roms, all of them with the same effect. But thanks for the suggestion.
iLoveAlkohola said:
As I said, before installing the newest stock ruu(with which I lost cwm and can''t seem to get it back), I installed some custom roms, all of them with the same effect. But thanks for the suggestion.
Click to expand...
Click to collapse
Make a full wipe before flashing the Ruu. Flash a custom recovery in fastboot, do a full wipe, then flash a ROM (stock or custom) To see what happens
Already did all that. When I first got the phone I used the full wipe function of cwm(and of the stock recovery) a couple of times, but every time it was stuck at that point of the initial setup with the error showing up.
Is there a file SPECIFICALLY for the initial setup that I can flash to the phone, because I flashed different recoveries, roms, boots and even radios manually before installing the stock ruu. I haven't set up a phone before, so I'm not sure, but as I can see there are still 2 or 3 options left to select ,after that scheduled sync option, before the phone could run the main menu(gui or whatever).
Oh, and btw, when I updated it with that ruu, the setup visually changed and by that I figure out it gets flashed as part of the ruu, but still with the same problem. Can it be some kind of hardware problem of the internal memory? No matter how much I searched and where I looked I never found someone with a problem even close to this one.
Teichopsia said:
Edit: Try booting without the sd card, but aside from that, no idea.
You can also try flashing a stable gb rom see if you get the same issue.
Sent from a dream.
Click to expand...
Click to collapse
Whatever I was doing to the phone it didn't usually have an sdcard in it and was booting without an sd card, tried with and without, no changes.
After I installed that sense ruu i can't seem to get back to gb, any ideas how to do it? I also can't get cwm to work now, even though it flashes without any error or problem I can only ge the htcdev root(already did) with this ruu, I think but I don't get any changes except that there is a watermark on the first line of bootloader.
Hi all,
I have an ATT samsung galaxy s3, out of warranty period. My phone's camera has stopped working entirely since 2 months. Its really frustrating! I have tried everything from going back to stock roms then custom roms.
A little history:
- I installed an app ipcam to monitor my baby, I left the cam on with flashlight and was gone for half an hour, since then I had cam freezing probs until one day it stopped working.
- I was trying a lot of options and one day the camera worked only for 5 mins. then when i tried again it was not working.
Please help!
I am currently on android 4.3, Intergalactic ROM 4.1 and MJB baseband.
I also had my sd card corrupted during that same time and have started using a new memory card since 1 week.
Did you try downloading another camera from the play store?
Yes I tired all sorts of camera apks none work....
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Yes I tried all sorts of camera apks none work....
I feel the file system is corrupted or something but I did factory reset and clean system, cache, dalvik cache, before installing roms so that should take care of it, but doesn't seem to help. I was on liquidsmooth 4.4 earlier when my problems began and I had installed some kernel had done dirty flashing, then I did a clean install of stock fw, but the problem still existed.
I read somewhere that switching bootloaders can screw camera files. So how to correct it there must be something I can do. I need to click my rowing baby's pictures I am missing all those moments when you wish you had a good camera at hand to make videos !
lilpyxie said:
Yes I tried all sorts of camera apks none work....
I feel the file system is corrupted or something but I did factory reset and clean system, cache, dalvik cache, before installing roms so that should take care of it, but doesn't seem to help. I was on liquidsmooth 4.4 earlier when my problems began and I had installed some kernel had done dirty flashing, then I did a clean install of stock fw, but the problem still existed.
I read somewhere that switching bootloaders can screw camera files. So how to correct it there must be something I can do. I need to click my rowing baby's pictures I am missing all those moments when you wish you had a good camera at hand to make videos !
Click to expand...
Click to collapse
that really sucks, we just had my little man not to long ago and i take lots of pictures. i had trouble with my N7 after flashing an update to the rom the camera from the gallery app was non existent and i could only take pictures from facebook with their camera app. I tried some apps from play store and other areas and i got the message "camera system not recognized" or something to that extent. I downloaded gallery+ with the camera app included and it's worked ever since. Although i only follow one developer when it comes to the N7 (although i use to switch a lot before hand).
i just got my S3 about 2 weeks ago so i'm not familiar with this gadget but.. maybe you fried your camera's hardware? i really hope i'm wrong and someone more experienced can lend a hand. i swapped bootloaders (we could of took different routes of course), played with just a few roms on the S3 but stopped after i learned more about touchwiz (cant believe i actually like a stock based rom :laugh.
sorry for my story lol, did you try the facebook camera (the take a picture option or something like that), i know it sounds silly but again it was the only thing that worked on my N7 besides the gallery camera app. Hope you get it working again! :good:
I tried the gallery ± and Facebook app anything that needs camera doesn't work... But thanks for your input... M glad you understand my plight of not being able to take my baby's pics...
I am on mj boot loader and the camera rear fw I found does null null in sys/class/camera I guess that is the problem.. The system is not being able to connect to the camera ...I don't think it's a hardware issue cuz camera worked for five minutes when I had done a clean install..
I was on liquid smooth before that's where problems started I did done update then installed the previous version... Don't remember what was it exactly
I'm so hoping somebody can help me in this someone who has a better knowledge of how the camera files are laid..I have camera 1.5 in my phone if that helps...
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Plz anybody suggest something!!
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Not sure if this will help but I was on 4.1.1 and I flashed to a 4.3 ROM and had nothing but issues. I flashed back to my 4.1.1 and I got the SAME camera error.
Turned out that that the 4.3 ROM included a bootloader update that was not compatible with the 4.1.1 ROM, it broke the camera.
I downgraded back to the 4.1.1 bootloader and the camera started working again.
Please note that some bootloaders can NOT be downgraded and you will brick your phone.
Thanks for your reply, I'm on MJB boot loader and I guess one can't downgrade from that to a 4.1.1 system so is there no hope for my camera recovery?
Are there any files that I can copy paste to make it work.. ? What happens when the boot loader changes? Why can't we have a boot loader that would run camera on 4.1.1? ..plz guys I know this can b done.. There must be a way...
Sent from my SAMSUNG-SGH-I747 using xda app-developers app