Develop Bugs

Gaps not working on 4.1.1

Every time I try a custom cm10 Rom or even the new preview of aokp when I flash gaps when I reboot it just reboot back into recovery. I have tried flashing right after flashing the Rom, I have tried flashing Rom first then reboot into Rom then back into recovery, I have tried wiping cache, nothing every time I flash gaps I can't get back into the Rom
Sent from my Galaxy Nexus using Tapatalk 2

yes its not working on these roms i've tried: CM10, AOKP, Bugless Beast ...

blowtorch said:
yes its not working on these roms i've tried: CM10, AOKP, Bugless Beast ...
Click to expand...
Click to collapse
Are you getting the same error where it just reboot into recovery
Sent from my Galaxy Nexus using Tapatalk 2

dislplin01 said:
Every time I try a custom cm10 Rom or even the new preview of aokp when I flash gaps when I reboot it just reboot back into recovery. I have tried flashing right after flashing the Rom, I have tried flashing Rom first then reboot into Rom then back into recovery, I have tried wiping cache, nothing every time I flash gaps I can't get back into the Rom
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
are you using the right gapps? have you tried redownloading them at all?

dislplin01 said:
Every time I try a custom cm10 Rom or even the new preview of aokp when I flash gaps when I reboot it just reboot back into recovery. I have tried flashing right after flashing the Rom, I have tried flashing Rom first then reboot into Rom then back into recovery, I have tried wiping cache, nothing every time I flash gaps I can't get back into the Rom
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Try a full wipe?

simms22 said:
are you using the right gapps? have you tried redownloading them at all?
Click to expand...
Click to collapse
3bananas said:
Try a full wipe?
Click to expand...
Click to collapse
Yea I have the correct gapps and have tried a full wipe I don't understand I downloaded the gapps from aokp post in Google± still same thing on any jelly bean Rom
Sent from my Galaxy Nexus using Tapatalk 2

I'm thinking it's the recovery I'm using clock work mod 6.0.0.1 touch I will update later and try it out let you guys know
Sent from my Galaxy Nexus using Tapatalk 2

derp nvm

I'm having the same problem with TeamEOS ROM. I tried everything above too. I'm using ClockworkMod 6.0.1.0.

I'm having the same issue.
Whenever I flash a ROM without Gapps bundled, then flash the Gapps package, I just boot back into CWM. I tried the two Gapps packages for Jellybean I could find, neither worked. Another issue I found is if I flash some modded Gapps packages (such as the one for the Team Bamf JB ROM or others) I can boot, but the apps aren't installed, and some functions might actually be missing after the flash.
I tried this with both JB ROMS and ICS ROMS, same story with both.
Another interesting thing, when I try to flash the MrMaddon Galaxy SIII Add-On pack, it installs the TW5 launcher, it themes everything, but none of the sounds, apps, or widgets are installed. This is for both the JB Light version, and the full version for ICS.
Flash a ROM with the Gapps already installed, everything is fine and dandy. I really want to use Paranoid Android, and the other amazing ROMs available for my GNex, but I don't want to have to do without Google Now and Google Voice. I've grown partial to them lol.

Is flashing an updated ROM the same process as flashing the original?

Sorry for the noob question. I searched but i couldn't find the answer I'm looking for. Here's the deal...i have had alot of rooted phones but i just rooted my own phone for the first time,obviously the GNex. I used the toolkit i found on here and it went great. I am using TWRP recovery cause it was recommended by AOKP and when i flashed there new Jb ROM i noticed how twrp is set up a lot different then CWM. I found out that i had to factory wipe before flashing. So getting to my question. When i flash the update do i do that same wipe or do i wipe cache,davlik and/or system? Also i gotta do a back up first right? Then with gapps is it the same steps as flashing the update? If someone can show me the way that would be great. Thanks.
Sent from my Galaxy Nexus using xda app-developers app

1. Backup current ROM
2. Wipe
3. Flash new ROM
4. Flash GAPPs (if required)
5. Reboot

Well, for updating purpose you've only to wipe cache and dalvik (but i think it's not mandatory for all the rom) then you straight flash the rom and gapps (everytime both) then you reboot and you're good to go! And backup is always welcome!

[email protected] said:
Well, for updating purpose you've only to wipe cache and dalvik (but i think it's not mandatory for all the rom) then you straight flash the rom and gapps (everytime both) then you reboot and you're good to go! And backup is always welcome!
Click to expand...
Click to collapse
Thank you. I wasn't sure exactly what to wipe........my ass i know, but still learning this stuff.
Sent from my Galaxy Nexus using xda app-developers app

EddyOS said:
1. Backup current ROM
2. Wipe
3. Flash new ROM
4. Flash GAPPs (if required)
5. Reboot
Click to expand...
Click to collapse
If you're staying on the same rom with just an update you probably don't have to wipe unless you have issues upon reboot but otherwise you probably always should.

so i got an update notification from goo saying my rom and gapps have an update (aokp jb 4.2 mr1 build 2) so i flashed em and i got my stock reboot screen then every google app foreclosing over and over but rom still there. what the hell????

This is for sprint ain't it?!!?
Sent from my Galaxy Nexus using xda app-developers app

elliot2112 said:
This is for sprint ain't it?!!?
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Toro would be Verizon.
sent from my Google Galaxy Nexus

bk201doesntexist said:
Toro would be Verizon.
sent from my Google Galaxy Nexus
Click to expand...
Click to collapse
well what happened here then? i looked on aokp and its not there. its the one i have now build 1. im really confused. the new gapps update is 20120429. it must be wrong if everything google was foreclosing. so what did goo.im give me?

ok it is build 2 on aokp. so gapps must be the same one i have been using? because this new one everything was foreclosing.

Better off doing updates manually and not using an app to do it for you

elliot2112 said:
well what happened here then? i looked on aokp and its not there. its the one i have now build 1. im really confused. the new gapps update is 20120429. it must be wrong if everything google was foreclosing. so what did goo.im give me?
Click to expand...
Click to collapse
From the date I think you flashed a gapps for jb 4.1 on a 4.2 ROM. Pretty sure that the 4.2 gapps is dated 12/12/12.

EddyOS said:
Better off doing updates manually and not using an app to do it for you
Click to expand...
Click to collapse
ya thats what im about to do now.

i went and downloaded build 2 straight from aokp and flashed that with same gapps for build 1 cause that hasnt changed on there site. my boot animation is the stock nexus logo instead of that pink unicorn with the gears. i figured it still wasnt working but everything seems to be running normal.....actually really fricken smooth and snappier. thanks for all your input everybody!

[Q]Can't open camera CM10

Hey guys, as you may tell I'm newly registered, but have been looking for a solution for my problem for a while now.
I have the Sprint Galaxy S3 16GB and flashed CyanogenMod 10.0 along with the Ktoonsez kernel. Everything works perfectly, but when I open the camera, it says "Can't connect to the camera". The camera works when I re-flash the stock rom, so it's not a hardware issue.
I've followed this thread but my firmware is ZHFJ02 whick isn't any of the download options.
Thanks in advance for any answers.

kj4pvf said:
Hey guys, as you may tell I'm newly registered, but have been looking for a solution for my problem for a while now.
I have the Sprint Galaxy S3 16GB and flashed CyanogenMod 10.0 along with the Ktoonsez kernel. Everything works perfectly, but when I open the camera, it says "Can't connect to the camera". The camera works when I re-flash the stock rom, so it's not a hardware issue.
I've followed this thread but my firmware is ZHFJ02 whick isn't any of the download options.
Thanks in advance for any answers.
Click to expand...
Click to collapse
I would suggest to try to flash an M snapshot of CM10.1 and try to use the camera on that. I use CM10.1 as a daily ROM, its battery life for me has been just about the same as CM10 and I haven't found any bugs that concern me. It may be worth a shot just to see if the camera work on CM10.1. Good luck!

LakeSoccer2 said:
I would suggest to try to flash an M snapshot of CM10.1 and try to use the camera on that. I use CM10.1 as a daily ROM, its battery life for me has been just about the same as CM10 and I haven't found any bugs that concern me. It may be worth a shot just to see if the camera work on CM10.1. Good luck!
Click to expand...
Click to collapse
What snapshot do you use
Sent From My Rooted, S-OFF'd Blackberry Curve using the iOS XDA Application for Android.

LakeSoccer2 said:
I would suggest to try to flash an M snapshot of CM10.1 and try to use the camera on that. I use CM10.1 as a daily ROM, its battery life for me has been just about the same as CM10 and I haven't found any bugs that concern me. It may be worth a shot just to see if the camera work on CM10.1. Good luck!
Click to expand...
Click to collapse
I have flashed 10.1 snapshot, but no dice. I think it's more of a lack of firmware than the rom itself.

Whiplashh said:
What snapshot do you use
Sent From My Rooted, S-OFF'd Blackberry Curve using the iOS XDA Application for Android.
Click to expand...
Click to collapse
I am running the latest M snapshot which can be found here. Its date added is: 2013-01-21 02:18:19 and it is 163.46 MB.
kj4pvf said:
I have flashed 10.1 snapshot, but no dice. I think it's more of a lack of firmware than the rom itself.
Click to expand...
Click to collapse
Were you on Ktoonsez kernel? Also, what gapps are you flashing?

LakeSoccer2 said:
Were you on Ktoonsez kernel? Also, what gapps are you flashing?
Click to expand...
Click to collapse
I was on Ktoonsez for 10.1 as I am now, and I flashed the correct kernel for 4.2 because I triple checked before I flashed.
When I installed 10.1 I flashed the 20121212 gapps.
Right now, on 10.0, I'm using 20121011.
I got the gapps from roozwiki

I'm running the nightly cm10.1 with the stock kernel, and the camera is lovely.
sent from a secret underground bunker

kj4pvf said:
Hey guys, as you may tell I'm newly registered, but have been looking for a solution for my problem for a while now.
I have the Sprint Galaxy S3 16GB and flashed CyanogenMod 10.0 along with the Ktoonsez kernel. Everything works perfectly, but when I open the camera, it says "Can't connect to the camera". The camera works when I re-flash the stock rom, so it's not a hardware issue.
I've followed this thread but my firmware is ZHFJ02 whick isn't any of the download options.
Thanks in advance for any answers.
Click to expand...
Click to collapse
Per other suggestions, and not trying to browbeat you, but flashing to a newer better version of CM (10.1 M version) is a not too burdensome final solution to your problem.
But if you are loathe to do it for some unstated reason... nm.
HTH
Sconnie

Thanks guys. I will upgrade to 10.1 just with stock kernel to see if that fixes the problem. Just one more quick question, can I use the built in CM upgrade to upgrade directly or do I need to re-flash with the new gapps?
All help is greatly appreciated
Sent from my SPH-L710 using Tapatalk 2

I'm unfamiliar with the cm updater.
I use ROM manager to download and install updates, and I install the gapps every time.
ROM manager notifies me when a new nightly is available.
sent from a secret underground bunker

mjben said:
I'm unfamiliar with the cm updater.
I use ROM manager to download and install updates, and I install the gapps every time.
ROM manager notifies me when a new nightly is available.
sent from a secret underground bunker
Click to expand...
Click to collapse
I'm having the same issue but it's happens on other rooms as well.
Any suggestions

Well I updated to 10.1 experimental but the camera still isn't working. MMS isn't working either. thanks for all the support in advance.
Sent from my SPH-L710 using Tapatalk 2

kj4pvf said:
Well I updated to 10.1 experimental but the camera still isn't working. MMS isn't working either. thanks for all the support in advance.
Sent from my SPH-L710 using Tapatalk 2
Click to expand...
Click to collapse
How are you at wiping partitions and flashing zips?
Personally, I would mount and format the system partition, then install the cm zip and gapps. Wipe you're caches and then I would expect everything to work fine.
Remember, always make a nandroid backup!
sent from a secret underground bunker

Well what I've been doing is:
1. Go into clockwork and wipe data and cache partition
2. Wipe cache partition just to be safe
3. Wipe dalvik
4. Flash rom then gapps and restart.
That's how I've been doing it this whole time
Sent from my SPH-L710 using Tapatalk 2

Ok, that sounds basically OK. You probly don't need to wipe your data, at least not right away.
Before flashing the ROM and gapps, go to mounts and storage, then mount system, format system, then flash ROM and gapps.
I wouldn't bother wiping data unless I had more problems afterwards.
sent from a secret underground bunker

I did what you recommended but it still didn't work. As an interesting side note, the partitioning is a little odd. All my personal info and downloads are in a sub folder called /0/ Just wondering if that's normal
Sent from my SPH-L710 using Tapatalk 2

kj4pvf said:
I did what you recommended but it still didn't work. As an interesting side note, the partitioning is a little odd. All my personal info and downloads are in a sub folder called /0/ Just wondering if that's normal
Sent from my SPH-L710 using Tapatalk 2
Click to expand...
Click to collapse
The 0 folder is normal, from JB and up all data is stored there (why, I dont know)
Sent from my PG06100

mjben said:
Ok, that sounds basically OK. You probly don't need to wipe your data, at least not right away.
Before flashing the ROM and gapps, go to mounts and storage, then mount system, format system, then flash ROM and gapps.
I wouldn't bother wiping data unless I had more problems afterwards.
sent from a secret underground bunker
Click to expand...
Click to collapse
I've tried all suggestions listed on this to fix the same issue on any ROM's I use. Would there be a mod or something out there that I could flash to replace it. All I get is a failed to connect to camera.

I dunno man. You may consider going 100% stock and cleaning up any signs of root and flashing and then, if the camera still isn't working, take then phone back to Sprint and see about exchanging it.
sent from a secret underground bunker

mjben said:
I dunno man. You may consider going 100% stock and cleaning up any signs of root and flashing and then, if the camera still isn't working, take then phone back to Sprint and see about exchanging it.
sent from a secret underground bunker
Click to expand...
Click to collapse
The camera works 100% in stock, even when rooted and with a custom kernel, the camera works with the stock rom.
Must be a firmware issue.

Any 4.2.2 ROM makes my camera crash

Hello,
I'm sorry if this is a repost of any sort . I am currently running a 4.1.2 rom and as it turns out any 4.1.2 rom that I run will have a functioning camera for my phone. However whenever I try to flash any 4.2 .2 rom on my phone the camera ceases to run correctly. I'm flashing the rom with clockworkmod touch and I have also tried flashing a camera fix I found on xda. I have even tried using third party camera apps, but those don't work either. Can anyone try to point me in the right direction or even try to help me troubleshoot this thing??
Thanks in advance
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

i'll begin with the question of what did you wipe before you flashed 4.2.2 and what ROM/release have you tried flashing?

Flash to factory stock and if ur camera still doesn't work it must logically be a hardware issue. Please guys correct me if I'm wrong
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

xBeerdroiDx said:
i'll begin with the question of what did you wipe before you flashed 4.2.2 and what ROM/release have you tried flashing?
Click to expand...
Click to collapse
I had just updated cwm to the latest touch version about a month ago. After that I was still on stock TW 4.1.1. Then, I tried flashing a 4.2.2 jellybam v7.6 and the camera stopped working so I flashed back to stock and the camera worked fine. I then tried flashing to the latest realease of CM 10.1 nightly
about 3 weeks ago but the camera didnt work so I flashed to 4.1.2 CSROM v1.4 then 1.5 and the camera worked fine. So I then tried CM10.0 4.1.2 and the camera still worked so last night I flashed to the latest CM nightly and the camera stopped working. Any thoughts?
Cprager said:
Flash to factory stock and if ur camera still doesn't work it must logically be a hardware issue. Please guys correct me if I'm wrong
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
I did and it still works. So it can't be a hardware issue. It has to do with how my phone flashes the software because I haven't seen anyone else having the same issues with the ROMS that I have been flashing.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

AaronYoLungz said:
so last night I flashed to the latest CM nightly and the camera stopped working. Any thoughts?
Click to expand...
Click to collapse
if the camera stopped working simply from updating your current ROM to the latest release than a wipe and reflash could possibly have ironed out this issue. this is assuming you dirty flashed the update. we all do that, but in the event things dont funtion properly afterwards, a wipe is required.

xBeerdroiDx said:
if the camera stopped working simply from updating your current ROM to the latest release than a wipe and reflash could possibly have ironed out this issue. this is assuming you dirty flashed the update. we all do that, but in the event things dont funtion properly afterwards, a wipe is required.
Click to expand...
Click to collapse
Well before I flashed any rom I always wiped all user data, I wiped the cache and dalvik cache and in some cases I even formatted the system in advanced settings. In every case the camera never worked.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

If it could help, I can get a report of the crash... The only thing is I would need guidance on going about getting it.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

i would back everything up. you have a working nandroid to fall back on?
then i would fully wipe the device and start over. you seem to be having problems with 4.2.2, not specifically aosp. it appears aosp and touchwiz 4.1.1 and 4.1.2 are working for you. correct? when transitioning android versions, its basically required to wipe everything in order to avoid issues. make sure you have the latest gapps for 4.2.2. that may be your problem right there.
in the event you choose to wipe and reflash a 4.2.2 rom,
- backup your files
- have a nandroid, the rom you want and gapps on a micro sd card.
- boot into recovery
- wipe data/factory reset
- wipe cache
- wipe dalvik
- format /system
- format /data + media
- flash rom from external sd card
- flash gapps from external sd card
- reboot and let your phone sit a few minutes then reboot again. check it out.
you wont get any ROM support from devs on your issues until you come from a complete wipe. a hassle to set everything up again but it will likely be your fix. if not, we can go a different direction.

Alright I'll try this now. I will keep you updated
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

AaronYoLungz said:
Alright I'll try this now. I will keep you updated
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
did you make sure you were flashing the correct gapps for your version of android? i'd hate to see you do all this for an incorrect gapps issue. yes, keep me posted

xBeerdroiDx said:
did you make sure you were flashing the correct gapps for your version of android? i'd hate to see you do all this for an incorrect gapps issue. yes, keep me posted
Click to expand...
Click to collapse
Alright I followed all of the above steps and my phone camera still isnt working. For clarification, gallery app works but when I actually try to use the camera I get a "Camera Error - Cannot connect to camera " popup window with an okay button below it.

AaronYoLungz said:
Alright I followed all of the above steps and my phone camera still isnt working. For clarification, gallery app works but when I actually try to use the camera I get a "Camera Error - Cannot connect to camera " popup window with an okay button below it.
Click to expand...
Click to collapse
what ROM and release did you end up flashing?

xBeerdroiDx said:
what ROM and release did you end up flashing?
Click to expand...
Click to collapse
ROM: cm-10.1-20130521-NIGHTLY-d2att
Gapps: gapps-jb-20130301-signed
EDIT: The problem described in the post#11 has always been the case

i would do 1 of 2 things: flash this 4.2 camera zip in recovery and see if that camera and gallery work or flash a different 4.2.2 ROM like tasks. this will help determine if its just cm10.1 thats giving you grief.
if you download and flash the 4.2 camera, just wipe cache, dalvik and flash the zip. in the event you get a freeze up when taking a picture with auto-focus, you have to set the scene to "Action" mode.
hit me back

xBeerdroiDx said:
i would do 1 of 2 things: flash this 4.2 camera zip in recovery and see if that camera and gallery work or flash a different 4.2.2 ROM like tasks. this will help determine if its just cm10.1 thats giving you grief.
if you download and flash the 4.2 camera, just wipe cache, dalvik and flash the zip. in the event you get a freeze up when taking a picture with auto-focus, you have to set the scene to "Action" mode.
hit me back
Click to expand...
Click to collapse
Should I remove Gallery4.apk and Gallery2.apk from /system/app?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

You can use a file Explorer to move those 2 to a different folder so that you can move them back if need be

xBeerdroiDx said:
You can use a file Explorer to move those 2 to a different folder so that you can move them back if need be
Click to expand...
Click to collapse
Alright so I ended moving the gallery, then flashing the new camera app in CWM then wiped the cache and dalvik. No luck, so I tried restarting my phone, fixing permissions, and nothing worked. I then full wiped my phone and flashed Vanilla Rootbox, tested camera and it didnt work. It still said "Camera Error- Can't connect to camera" . . I flashed the camera zip provided followed by a cache and dalvik wipe but I got the same message. Following the above steps I did the exact same thing with AOKP and the exact same thing happened.
Is it possible that my phone just can't support 4.2.2?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

Is it possible that an outdated version of Odin could be the problem?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

[Q] My phone freezes and restarts when starting up a CM ROM

I was using the latest alpha of CM11, then i i wanted to get back to CM10.2, i did all i had to do (wipes, and stuff) and when starting up, the phone frezees and keep on doing this...
I also have searched about this issue and found no answer.

tpag02 said:
I was using the latest alpha of CM11, then i i wanted to get back to CM10.2, i did all i had to do (wipes, and stuff) and when starting up, the phone frezees and keep on doing this...
I also have searched about this issue and found no answer.
Click to expand...
Click to collapse
Have you tried booting to recovery, then doing an advanced wipe (system/data/cache/dalvik) and reflashing rom/gapps?
What version of recovery are you using?

Almite said:
Have you tried booting to recovery, then doing an advanced wipe (system/data/cache/dalvik) and reflashing rom/gapps?
What version of recovery are you using?
Click to expand...
Click to collapse
yes, i have. I also got back to stock, used an older recover, flashed with an older version of CM and nothing. I first was using CWM 6.0.3.7., after that I used 6.0.4.3, then an older version of TWRP but nothing. I also tried booting to system without flashing gapps.
With stock ROM everything works just fine.

Just wipeout internal and external card once and than install with twrp 2.6.1.0. And don't forget to say thanks
Sent from my SGH-T989 using xda app-developers app

iamdofus said:
Just wipeout internal and external card once and than install with twrp 2.6.1.0. And don't forget to say thanks
Sent from my SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
Well, thank you, but it didn´t work.

it happened to me the same thing months ago. never had solution. still in waiting. attempt internal and external SD format. and followed the same. I hope someday they can come up with the solution! : (

i have the same problem too

I try to install multiple ROM 4.2.2 and I could only install one version AOKP Milstone JB1. I also worked the other. however all 4.1.2 rom if I worked. I could not install any 4.3 and 4.4 now does not know what is the problem but I've tried everything! anyone found the solution yet but I see I'm not the only one! (excuse my bad English, not my language )

Well you all are right, I am also using shadow mastery (stock rooted rom). Just because I had the same problem sometimes stucking and rebooting and sometimes after going in gallery. Even I can't use 4.3 and 4.4 roms. Anyone have to contact with room developer or someone who know about this problem.
Sent from my SGH-T989 using xda premium

You might want to find an Official T-Mobile or Telus 4.1.2 or 4.0.3/4.0.4 rom that is Odin flashable, not one that has been custom made/flashable from recovery - then just start over after getting back to true stock, change to TWRP or CWM recovery that is 4.3+ compatiable, root and then flash rom/gapps etc.