Database Info

[Q] Cannot get from GB to ICS at all.

I keep running into problems after flashing any ICS custom ROM. (Maybe I should try going to an ICS Stock ROM first).
Most times it just loops on the loading screen.
- Phone is rooted of course.
- I usually have the Emancipation GB custom rom before flashing to this one or a Stock GB with root and red CWM.
- I follow instructions to a 'tee'
- When I do reboot, it loops at Samsung logo.
The last time I tried (Dark Knight ICS Rom), just recently, I flashed then rebooted into recovery (from advance-boot to recovery), and it didn't go to recovery mode, it just looped.
So currently I'm on Stock GB with root and red CWM.
What am I doing wrong?
What are some things I should consider?
Some of the GB custom roms are nice yes, but I rooted mainly so I could get ICS.
Thanks for any help anyone can offer/

http://forum.xda-developers.com/showthread.php?t=1610374
Wipe cache/Wipe dalvick/factory restore
You flash the rom
Then Gapps
Restart....Then it bootloops?

omansteveo said:
http://forum.xda-developers.com/showthread.php?t=1610374
Wipe cache/Wipe dalvick/factory restore
You flash the rom
Then Gapps
Restart....Then it bootloops?
Click to expand...
Click to collapse
Yeah pretty much.
Only happens for ICS ROMs. Well the ones I've tried.
Still new at this, so I'll keep trying and that link you posted is one of my most visited links.

Skebodan said:
Yeah pretty much.
Only happens for ICS ROMs. Well the ones I've tried.
Still new at this, so I'll keep trying and that link you posted is one of my most visited links.
Click to expand...
Click to collapse
Ive been at it for about 5 months now and have bricked my phone like 20 times ha ha...so Ill do what I can to help. I've been successful going from GB to ICS to JB and vice versa. Try this also....When you phone starts to boot loop pull the battery and boot into recovery. Then wipe everything again and reflash the rom and gapps

omansteveo said:
Ive been at it for about 5 months now and have bricked my phone like 20 times ha ha...so Ill do what I can to help. I've been successful going from GB to ICS to JB and vice versa. Try this also....When you phone starts to boot loop pull the battery and boot into recovery. Then wipe everything again and reflash the rom and gapps
Click to expand...
Click to collapse
lol alright thanks man. I've bricked mine about twice now. Just started about a week lol.
I'll give you an update in about 2 hours. Got to get ready for work

I have gone from Emancipation to this in the past with no prob... just follow his instructions for install and you are good to go - credit and thanks to Entropy512.
http://forum.xda-developers.com/showthread.php?t=1601844

Pony Express said:
I have gone from Emancipation to this in the past with no prob... just follow his instructions for install and you are good to go - credit and thanks to Entropy512.
http://forum.xda-developers.com/showthread.php?t=1601844
Click to expand...
Click to collapse
To be honest I was running from using Entropy's build.
Fear of it being too technical (It's actually the first thread I saw when I was thinking of going to ICS). So I used it and my phone is up and running now on ICS.
Won't be able to play around with it as much until I get home from work but thanks for mentioning it again.
Now to go and read the thread all the way through (kidding) well see if the problems he had are still occurring.
Thanks again guys.

For me, using Entropy's build made it easy to go to any other ICS rom for the Infuse- it is great as is or as a "stepping-stone" to other ICS builds. Glad it worked for you.

Yea man it was nice. I don't even need the other custom roms, this has everything I wanted.
And since it has a theme chooser, I'm good for life on the look of it.
I might try and customize my own stuff in the future but for now, all is right with my Infuse. I was going to get the Note but I got a brand new phone right here.

Having trouble with different kernals, quick question.

So i rooted my GS3 and ran the CleanROM6 R2 just fine and the new synergy just fine. However i can only run the new JellyBeans13 with the stock kernel, the other two kernels freeze at the Samsung Galaxy SIII screen every time. I am running CWM6023. I was wondering if that needed to be updated and if so how to update the CWM, also if anyone else has had that issue with certain Kernels. I want the Ktweaker that's why it bothers me right now i have the stock Jellybeans 13 rom and kernel. I am just confused it is the only rom that has done this to me.

Some kernels required a dalvik cache wipe in order for it to work properly.

jmxc23 said:
Some kernels required a dalvik cache wipe in order for it to work properly.
Click to expand...
Click to collapse
I do a Dalvik wipe everytime, i was just wondering if i needed a newer version of CWM.

Is your boot loader unlocked??
Sent from a Shaftamle Galaxy S3
Hit the "Thanks" button if I helped you!!

I know the kernels have been locking phones that are on latest updates. I believe they just found out what was causing the locks, so expect to see updated kernels over the next few days. You should run the stock kernel (supplied with the rom) until the updates are rolled out.
Sent from my PACmaned SCH-I535

JB13 has an issue if you use a different kernel that won't show a boot animation. It may not be freezing.

Can not connect to the camera. Still no solution? CM10.0.

Hi, I can't seem to find my way around this issue. Every time I try to open any camera app, it doesn't allow me and says it's unable to connect. Is there no sure solution to this yet? I tried flashing new cameras through recovery. Nothing works at all. I have tried flashing fixes from several threads on a clean start, different camera apps, clearing caches, clean wiping, and other things I can't even remember at this point with all the frustration. What's up with this?
TW based ROMs work. AOSP seems to not. I lost the thread explaining how to dial the codes into a TW based ROM, but another problem with this for me is, I am extremely confused as to how to do some of the steps explained in that thread (hence why I closed it, looks like that should be the way out for me though?).

Same problem
CZory91 said:
Hi, I can't seem to find my way around this issue. Every time I try to open any camera app, it doesn't allow me and says it's unable to connect. Is there no sure solution to this yet? I tried flashing new cameras through recovery. Nothing works at all. I have tried flashing fixes from several threads on a clean start, different camera apps, clearing caches, clean wiping, and other things I can't even remember at this point with all the frustration. What's up with this?
TW based ROMs work. AOSP seems to not. I lost the thread explaining how to dial the codes into a TW based ROM, but another problem with this for me is, I am extremely confused as to how to do some of the steps explained in that thread (hence why I closed it, looks like that should be the way out for me though?).
Click to expand...
Click to collapse
I am having the same problem you are. I am running paranoid android and cant get the camera / gallery to work. I hope somebody can help. I had it working on Beans rom build 13 but that is TW. I am going to have to bail on pa if there isn't a fix

bmanderle said:
I am having the same problem you are. I am running paranoid android and cant get the camera / gallery to work. I hope somebody can help. I had it working on Beans rom build 13 but that is TW. I am going to have to bail on pa if there isn't a fix
Click to expand...
Click to collapse
It's an AOSP problem based on the firmware of your camera when getting the phone from what I've seen.
http://forum.xda-developers.com/showthread.php?p=37072484#post37072484
Here's the thread I was talking about, however I'm confused about how to go about zipping and unzipping these files. Or even how to get to them to place the files in to begin with considering internal SD card is the only thing that comes up for USB storage. Unless you're supposed to move them in and out from within android.

Would really like a confirm on whether or not this works for the Verizon version, and whether or not it's a different process/if this even works at all, rather not break it fully
Why is this not more of a widespread issue? it seems so crucial that many are having but nobody seems to be talking about it or wanting to find a definite fix for it?

CZory91 said:
Would really like a confirm on whether or not this works for the Verizon version, and whether or not it's a different process/if this even works at all, rather not break it fully
Why is this not more of a widespread issue? it seems so crucial that many are having but nobody seems to be talking about it or wanting to find a definite fix for it?
Click to expand...
Click to collapse
I had the camera problem on MIUI...
Before flashing, I made a backup of my system with CW
I extracted the SlimISP_ZH.bin from my backup and
copied it to my /data directory and it worked fine.
Link: d-h.st/dwx
(I can't post links yet)
maybe... someone post the fix in this forum and make it sticky... lol

Ughhhhhhhhh. This is getting irritating. Going to revive the thread.
I flashed the new firmware (MD3) for this phone. I had everything good and working with CM10... Guess what, borken camera, same issues...
I can't post links yet, but it's in the android development thread with this title:
★ [Rom][I535VRBMD3][4.1.2] Stock Root Odex/Deodex [05/29/13]★
Except... this time I cannot do the simple copy/paste of the bin files this time, why is that?
At this point I just want my VRBLK3 (I think?) firmware back.. Where can I get it to reverse what I just downloaded, in essence?
Also.. What the heck kind of hurdles am I going to have to go through when CM10.1 is complete?.. I don't think I'll be updating my phone past 10.1 at this rate if this continues, really irritating.

CZory91 said:
Ughhhhhhhhh. This is getting irritating. Going to revive the thread.
I flashed the new firmware (MD3) for this phone. I had everything good and working with CM10... Guess what, borken camera, same issues...
I can't post links yet, but it's in the android development thread with this title:
★ [Rom][I535VRBMD3][4.1.2] Stock Root Odex/Deodex [05/29/13]★
Except... this time I cannot do the simple copy/paste of the bin files this time, why is that?
At this point I just want my VRBLK3 (I think?) firmware back.. Where can I get it to reverse what I just downloaded, in essence?
Also.. What the heck kind of hurdles am I going to have to go through when CM10.1 is complete?.. I don't think I'll be updating my phone past 10.1 at this rate if this continues, really irritating.
Click to expand...
Click to collapse
did you flash this after flashing the rom?
http://forum.xda-developers.com/showthread.php?t=1788313
---------- Post added at 04:47 AM ---------- Previous post was at 04:41 AM ----------
dandydon414 said:
did you flash this after flashing the rom?
http://forum.xda-developers.com/showthread.php?t=1788313
Click to expand...
Click to collapse
my advice, odin back to stock (4.1.2), root and install this rom
http://forum.xda-developers.com/showthread.php?t=1788313
has been great for me, no issues whatsoever

dandydon414 said:
did you flash this after flashing the rom?
http://forum.xda-developers.com/showthread.php?t=1788313
---------- Post added at 04:47 AM ---------- Previous post was at 04:41 AM ----------
my advice, odin back to stock (4.1.2), root and install this rom
http://forum.xda-developers.com/showthread.php?t=1788313
has been great for me, no issues whatsoever
Click to expand...
Click to collapse
Yes, that is the post. I also tried MB1 out of curiosity, no dice on either of them. I had a perfectly working CM10. I dun goofed :\.
That was my next step (rerooting, installing that firmware AIO, and then installing CM10). However my question is this, what happens when more firmware comes out? I have to re root and start over again?

If you flashed md3 just flash back mb1 and you will fix that problem. I had the issue. Pulled the firmware from invisiblek for mb1 and back to normal on liquid smooth
Sent from my GT-P5113 using xda premium

bbqsfire said:
If you flashed md3 just flash back mb1 and you will fix that problem. I had the issue. Pulled the firmware from invisiblek for mb1 and back to normal on liquid smooth
Sent from my GT-P5113 using xda premium
Click to expand...
Click to collapse
for some reason I haven't good luck running cm roms on the s3........have much better luck with tw based rom. that's why I recommend a restock and basically start all over from scratch

dandydon414 said:
for some reason I haven't good luck running cm roms on the s3........have much better luck with tw based rom. that's why I recommend a restock and basically start all over from scratch
Click to expand...
Click to collapse
Yeah I think a clean slate is definitely needed from time to time. I swap roms frequently but liquid gives me the best battery life right now from my tests so I keep going back. I Get scared telling people to odin because so mant people soft brick while screwing up a flash inodin or hard brick because they flash a non Verizon rom
Sent from my GT-P5113 using xda premium

bbqsfire said:
Yeah I think a clean slate is definitely needed from time to time. I swap roms frequently but liquid gives me the best battery life right now from my tests so I keep going back. I Get scared telling people to odin because so mant people soft brick while screwing up a flash inodin or hard brick because they flash a non Verizon rom
Sent from my GT-P5113 using xda premium
Click to expand...
Click to collapse
good point. saw where someone flashed an i9300 s3 rom on the verizon s3 and brick city. my problem with aokp, cm, liquid, carbon, baked bean, I've tried them all, is constant freezing forcing me to pull the battery. I love the features of those roms but I hate having to pull the battery all the time

Hmm, over the past couple days I've tried out a few different ROMs on my girlfriend's S3 here, and on each one I would get this "Could not connect to the camera" error, every single time upon opening the camera app. One of the Paranoid Android ROMs, Liquid Smooth, and Synergy (even the Touchwiz camera was broken on that!).
I can restore to the original backup I made of the stock ROM, and the camera works fine again. But as soon as I try a different ROM, no camera.
I'd love to get an AOSP ROM running on this phone, but having a working camera is a requirement, and I can't figure out what I'm doing wrong. Searching the individual threads for the ROMs yields little help, and I'm getting exactly the same error on different ROMS, so I feel like I'm doing something wrong on a higher level. Any chance that switching from TWRP to CWM would make a difference? I don't see why it would, but I suppose it's something I could try.

bbqsfire said:
If you flashed md3 just flash back mb1 and you will fix that problem. I had the issue. Pulled the firmware from invisiblek for mb1 and back to normal on liquid smooth
Sent from my GT-P5113 using xda premium
Click to expand...
Click to collapse
Yep, I'm saying I tried that, still nothing :\ I'm going to flash MB1 and get the stock files again to see if it will do anything but I doubt it.

CZory91 said:
Yep, I'm saying I tried that, still nothing :\ I'm going to flash MB1 and get the stock files again to see if it will do anything but I doubt it.
Click to expand...
Click to collapse
Have you tried odin back to MB1 or even LK3 and letting it go through the OTA's? Those OTA's also update rpm, and other partitions, that as far as I know don't get updated when we flash these stock files on xda unless we flash them ourselves. Maybe something screwed up and is being persistent since those partitions aren't getting updated along the way?

Watanuki-Kun said:
Have you tried odin back to MB1 or even LK3 and letting it go through the OTA's? Those OTA's also update rpm, and other partitions, that as far as I know don't get updated when we flash these stock files on xda unless we flash them ourselves. Maybe something screwed up and is being persistent since those partitions aren't getting updated along the way?
Click to expand...
Click to collapse
I'm honestly just going to restart from scratch and re root when CM10.1 is fully done (hopefully soon...) Nothing is working. Flashed to MB1 firmware on CM 10. Tan MB1 CleanROM. Camera worked in CleanROM, copy/pasted onto my CM10 after the restore, still nothing... Seriously mind boggling.

CZory91 said:
I'm honestly just going to restart from scratch and re root when CM10.1 is fully done (hopefully soon...) Nothing is working. Flashed to MB1 firmware on CM 10. Tan MB1 CleanROM. Camera worked in CleanROM, copy/pasted onto my CM10 after the restore, still nothing... Seriously mind boggling.
Click to expand...
Click to collapse
Probably best, that would be my first thing to try if I had that problem, restarting from scratch. If all else fails, restarting from scratch will wipe out everything. If that failed, I would probably suspect hardware issue.

Watanuki-Kun said:
Have you tried odin back to MB1...
Click to expand...
Click to collapse
Flashing the MB1 firmware fixed the camera for me on AOSP. I flashed this zip in recovery after the ROM was installed:
http://invisiblek.org/sch-i535/firmware/
Link was obtained from here (FAQ about it):
http://rootzwiki.com/topic/34053-firmware-vrbmd3-modemrpmtzsbl-verizon-sgs3-sch-i535/

dandydon414 said:
good point. saw where someone flashed an i9300 s3 rom on the verizon s3 and brick city. my problem with aokp, cm, liquid, carbon, baked bean, I've tried them all, is constant freezing forcing me to pull the battery. I love the features of those roms but I hate having to pull the battery all the time
Click to expand...
Click to collapse
Well I would recommend liquid 2.5 with the kernel that comes with it and I never change any of the overclocking settings. I don't have to pull the battery at all on this one.
Sent from my SCH-I535 using xda premium

TunedReference said:
Flashing the MB1 firmware fixed the camera for me on AOSP. I flashed this zip in recovery after the ROM was installed:
http://invisiblek.org/sch-i535/firmware/
Link was obtained from here (FAQ about it):
http://rootzwiki.com/topic/34053-firmware-vrbmd3-modemrpmtzsbl-verizon-sgs3-sch-i535/
Click to expand...
Click to collapse
Yep, that's what I tried. Nothing.

[Q] Phone application force closes after finishing a call...

Hello, all.
I have a T-Mobile Blaze 4G with rooted stock ROM (Gingerbread), flashed radio version T989UVMC6, manually debloated and dewizzed. I'm running Halo launcher and Busybox Free version 9.6.
Since almost the first day I've had this phone, it would occasionally force close the phone process, usually when hanging up the phone with the Bluetooth radio on and paired with an earpiece. It happened bone stock, rooted, after I changed the modem, whenever. It seemed to happen less often after I changed the modem. The process always starts back up, but the Bluetooth device connection and system sound controls are wonky (unusable) until the phone is rebooted.
The only thing that seems to stop it is running Zepplinrox's V6 Supercharger script. That, however, occasionally freezes the entire system when trying to open certain apps, requiring a reboot. I've run earch after search on this subject, and nobody else seems to have this problem. The only thing I haven't tried is wiping the whole thing and flashing a custom ICS or JB ROM. I tried Dark Knight ver. 8 and hated it pretty much instantly.
I have two questions. Number one; Will flashing a custom ROM fix this situation? I figure that this must be a problem with the crappy stock Samsung ROM. Number two; Which ROM is fully functional and stable? I'd really like to keep this phone dependable. I don't care about the latest and greatest funky cool features that are hit-or-miss at best. I just need dependable, fast and functional.

Since you have been having issues for a while, I would suggest starting fresh. With a few runs of black hole wipe from cwm. Add a run of the gremlin remover for extra cleanliness. Then a flash of the latest ICS rooted stock rom and kernel, for reliability.
Black hole wipe. http://forum.xda-developers.com/showthread.php?t=1721057
Gremlin remover, FSC http://forum.xda-developers.com/showthread.php?t=2218713
Uvmb1 ics ROM http://forum.xda-developers.com/showthread.php?t=2329081

Romman0 said:
Since you have been having issues for a while, I would suggest starting fresh. With a few runs of black hole wipe from cwm. Add a run of the gremlin remover for extra cleanliness. Then a flash of the latest ICS rooted stock rom and kernel, for reliability.
Black hole wipe. http://forum.xda-developers.com/showthread.php?t=1721057
Gremlin remover, FSC http://forum.xda-developers.com/showthread.php?t=2218713
Uvmb1 ics ROM http://forum.xda-developers.com/showthread.php?t=2329081
Click to expand...
Click to collapse
I'll definitely go for the rooted version! Does it matter what order in which the ROM and the kernel are flashed? Also, I take it from the name of the download link that I'll have to go through the process of de-bloating this thing again. S'okay, I actually enjoy that part, but I don't want to screw it up since I've not messed with anything newer than GB. Is there a good guide somewhere on the forum for apps that can be dumped safely? I know there was one for GB stock root.
Thanks for the response.

ionizd said:
I'll definitely go for the rooted version! Does it matter what order in which the ROM and the kernel are flashed? Also, I take it from the name of the download link that I'll have to go through the process of de-bloating this thing again. S'okay, I actually enjoy that part, but I don't want to screw it up since I've not messed with anything newer than GB. Is there a good guide somewhere on the forum for apps that can be dumped safely? I know there was one for GB stock root.
Thanks for the response.
Click to expand...
Click to collapse
Flash the ROM then the kernel, rewipe cache and davlik, then profit.
The most recent ICS debloating thread. http://forum.xda-developers.com/showthread.php?t=2183726&highlight=debloat

Romman0 said:
Flash the ROM then the kernel, rewipe cache and davlik, then profit.
The most recent ICS debloating thread. http://forum.xda-developers.com/showthread.php?t=2183726&highlight=debloat
Click to expand...
Click to collapse
A few more silly questions; Do I need GAPPS or is that just for CM? Aren't the CM 10 ICS nightlies fairly stable and relatively bug-free? I use CM7 on my Nook color and it's...okay... Just a few little annoying things pop up with that. To be honest, I like the idea of starting with a clean slate and adding stuff I like rather than pulling stuff out of the Samsung stock ROM, but the issues I've had with the Nook and CM7 have sort of scared me off. Your opinions?

ionizd said:
A few more silly questions; Do I need GAPPS or is that just for CM? Aren't the CM 10 ICS nightlies fairly stable and relatively bug-free? I use CM7 on my Nook color and it's...okay... Just a few little annoying things pop up with that. To be honest, I like the idea of starting with a clean slate and adding stuff I like rather than pulling stuff out of the Samsung stock ROM, but the issues I've had with the Nook and CM7 have sort of scared me off. Your opinions?
Click to expand...
Click to collapse
All the AOSP ROMs for the Blaze needs GAPPs. And yes. The latest CM10 nightly is stable. And you said CM10 ICS? CM9 is ICS and CM10 is Jellybean.

ionizd said:
A few more silly questions; Do I need GAPPS or is that just for CM? Aren't the CM 10 ICS nightlies fairly stable and relatively bug-free? I use CM7 on my Nook color and it's...okay... Just a few little annoying things pop up with that. To be honest, I like the idea of starting with a clean slate and adding stuff I like rather than pulling stuff out of the Samsung stock ROM, but the issues I've had with the Nook and CM7 have sort of scared me off. Your opinions?
Click to expand...
Click to collapse
The stock roms don't require gapps, but like Wolf said the cm10 jb variants do.
If your willing to use cm10 it is very stable. Just use the latest CM10 nightly and not the old stable version.
Here http://forum.xda-developers.com/showthread.php?t=1922935
The jb gapps 20121011 http://goo.im/gapps/gapps-jb-20121011-signed.zip

xWolf13 said:
All the AOSP ROMs for the Blaze needs GAPPs. And yes. The latest CM10 nightly is stable. And you said CM10 ICS? CM9 is ICS and CM10 is Jellybean.
Click to expand...
Click to collapse
Of course. I get a bit confused ever since people started talking about 10.1.

Okay, I went ahead and installed the stock rooted ROM with the stock kernel. Went through the debloating process (mostly, there are some apps that I'm not sure I can do without so they stay for now), and did some customizing. I'm seeing a bit more battery drain. Is this an issue with ICS or do I need to try another kernel or supercharge the phone? I also have this crazy issue with ROM Manager ver. 5.5.3.0. It tells me that there is an updated version of Clockworkmod Recovery, but it freezes when I try to flash from ROM Manager. Also, ROM Manager freezes when I try to reboot into Clockworkmod Recovery. Maybe I need to test a bit more before I mess with it any more.
**EDIT** Well, it looks as if my CWM recovery installation is corrupted. Can I reflash it without messing up my current ROM?

ionizd said:
Okay, I went ahead and installed the stock rooted ROM with the stock kernel. Went through the debloating process (mostly, there are some apps that I'm not sure I can do without so they stay for now), and did some customizing. I'm seeing a bit more battery drain. Is this an issue with ICS or do I need to try another kernel or supercharge the phone? I also have this crazy issue with ROM Manager ver. 5.5.3.0. It tells me that there is an updated version of Clockworkmod Recovery, but it freezes when I try to flash from ROM Manager. Also, ROM Manager freezes when I try to reboot into Clockworkmod Recovery. Maybe I need to test a bit more before I mess with it any more.
**EDIT** Well, it looks as if my CWM recovery installation is corrupted. Can I reflash it without messing up my current ROM?
Click to expand...
Click to collapse
Yes, with Odin, in the Dev forum
BTW, stay away from ROM Manager with our device. I've softbricked so many times because of it, it's ridiculous

jparnell8839 said:
Yes, with Odin, in the Dev forum
BTW, stay away from ROM Manager with our device. I've softbricked so many times because of it, it's ridiculous
Click to expand...
Click to collapse
Used this method http://forum.xda-developers.com/showthread.php?t=2011585, it worked well. Still have the battery drain issue, though. : /

ionizd said:
Used this method http://forum.xda-developers.com/showthread.php?t=2011585, it worked well. Still have the battery drain issue, though. : /
Click to expand...
Click to collapse
Since you have it setup, except for battery life. I would make a backup, then try a mod one at a time and see if any help. Also check the battery stats to see if anything of is seen. ICS will use more juice than GB, generally.
I would suggest Nos/direct injection, supercharger, or cross breeder. I would use one and see, then restore and try another.
http://forum.xda-developers.com/forumdisplay.php?f=565

Some time later...
I've been using the stock rooted ICS ROM since my last post, debloated and dewizzed of course, with Holo Launcher and T989UVMC6 baseband version flashed. Just over a month has passed, and I have good news!
I FREAKING LOVE THIS PHONE!!!
All of the force close and freezing issues have vanished, the phone's battery lasts almost as long as it did on GB, it's WAY more user friendly, and the phone is as fast as it ever was.
The bad news is that my wife got a GS4 and I lust after it now. : /
Thanks to everyone for their help!

I Give Up: 4.3 Camera Issues

Hey guys been searching and reading and searching and reading for the past two days and I cannot get a fix for this camera issue. "Camera Error: Can't connect to the camera.". It seems to only be with Android 4.3 Roms (I.E. Paranoid Android, Slimbean, CarbonRom etc) as when I rooted and installed CleanRom there was no issue. Stock rooted camera also works. I am currently utilizing CWM for all of my flashes/recoveries/backups
Here are the things I have tried based off of search and other threads;
Reflashing Roms and their Gapps multiple times with no luck
Odin'd to stock TWICE and reflashed utilizing the soft brick method VRALEC and VRALF Boothchains as well as stock.vzw_root66.zip.
Reflashed my baseband from MB3 to MB1 to MF1 with no change.
I've tried uninstalling the gallery.apk using TiBackup and reinstalling with different galleries with no luck.
My next step it to attempt to flash a different Kernel.
I honestly love the 4.3 Paranoid Android 3.99 Rom but don't think I can sacrifice not having a camera. Any help from the Gurus would be greatly appreciated and thanks will be given!
Chris

Kennedy87 said:
Hey guys been searching and reading and searching and reading for the past two days and I cannot get a fix for this camera issue. "Camera Error: Can't connect to the camera.". It seems to only be with Android 4.3 Roms (I.E. Paranoid Android, Slimbean, CarbonRom etc) as when I rooted and installed CleanRom there was no issue. Stock rooted camera also works. I am currently utilizing CWM for all of my flashes/recoveries/backups
Here are the things I have tried based off of search and other threads;
Reflashing Roms and their Gapps multiple times with no luck
Odin'd to stock TWICE and reflashed utilizing the soft brick method VRALEC and VRALF Boothchains as well as stock.vzw_root66.zip.
Reflashed my baseband from MB3 to MB1 to MF1 with no change.
I've tried uninstalling the gallery.apk using TiBackup and reinstalling with different galleries with no luck.
My next step it to attempt to flash a different Kernel.
I honestly love the 4.3 Paranoid Android 3.99 Rom but don't think I can sacrifice not having a camera. Any help from the Gurus would be greatly appreciated and thanks will be given!
Chris
Click to expand...
Click to collapse
Try flashing the latest Paranoid Android, Latest BMS or Ktoonsez Kernel, and the supported GAPPS.

macman159 said:
Try flashing the latest Paranoid Android, Latest BMS or Ktoonsez Kernel, and the supported GAPPS.
Click to expand...
Click to collapse
Tried flashing withe the BMS Kernel and still no luck. Can't connect to camera. Very frustrating. Thanks for the attempt.

In this thread on Rootz, I was trying to help a user out and they somehowe got their camera to work despite my suggestion which is a little more involved than what you have done so far. The user somehow got it working by doing a factory reset and wiping caches, then flashing their AOSP rom and VRBMF1 firmware in the same session then booting into the rom.
Here is my more involved suggestion as well.

SlimSnoopOS said:
In this thread on Rootz, I was trying to help a user out and they somehowe got their camera to work despite my suggestion which is a little more involved than what you have done so far. The user somehow got it working by doing a factory reset and wiping caches, then flashing their AOSP rom and VRBMF1 firmware in the same session then booting into the rom.
Here is my more involved suggestion as well.
Click to expand...
Click to collapse
Thank you Slim just saw you're suggestions. I guess I will first try doing what OP of the post you linked did first if all else fails I guess could try the ODIN method as described in the XDA Link you provided...Youre suggest was the ODIN method utilizing the PIT method correct? I guess I'l re-odin to root66 stock and try the method stated.:good:

FYI I am currently running CleanRom 7 with ZERO camera issues. 4.1.2.

Kennedy87 said:
FYI I am currently running CleanRom 7 with ZERO camera issues. 4.1.2.
Click to expand...
Click to collapse
Ahh, this is good. I misread and was thinking it stopped working entirely which has happened to people as well. I'm so used to people having it permanently stop working even after flashing back to TW.
Kennedy87 said:
Thank you Slim just saw you're suggestions. I guess I will first try doing what OP of the post you linked did first if all else fails I guess could try the ODIN method as described in the XDA Link you provided...Youre suggest was the ODIN method utilizing the PIT method correct? I guess I'l re-odin to root66 stock and try the method stated.:good:
Click to expand...
Click to collapse
Yea, but since it's only an AOSP issue and not permanently broken, idk how likely this is to resolve it for you. It's a shot anyway.
Sent from my SCH-I535 using Tapatalk 4