Camera not working......plz help !!! - Nexus One Q&A, Help & Troubleshooting

I have been using desire alpha from day one it was release and after updated to alpha 12 .there seems to be some problem with my camera app it doesn't open just hangs on black screen tried wipe couple of times even tried stock rom and CY 5.0.4.1 but no use the camera force closes at black screen and sometimes i get an error "process com.android.camera" force close .............please help !

Try recovering to old nandroid backup, redownload the Alpha12, re-wipe and re-install?

Postal Dude said:
Try recovering to old nandroid backup, redownload the Alpha12, re-wipe and re-install?
Click to expand...
Click to collapse
already tried that ..tried complete wipe unrooted then rooted ...tried old backup.......no help ! just black screen

what ROM are you on now ??

lolittle said:
what ROM are you on now ??
Click to expand...
Click to collapse
right now I am on alpha 12 .

Attatched camera apk so try
adb push HTCCamera.apk /system/app/
If that does not work then do this
Go to recovery
Wipe, Wipe delvik cache etc
Do fresh install of CMs ROM or a Stock ROM
check camera after
EDIT: And next time you should post in either Q & A or General!!
This does not belong in development

lolittle said:
Attatched camera apk so try
adb push HTCCamera.apk /system/app/
If that does not work then do this
Go to recovery
Wipe, Wipe delvik cache etc
Do fresh install of CMs ROM or a Stock ROM
check camera after
EDIT: And next time you should post in either Q & A or General!!
This does not belong in development
Click to expand...
Click to collapse
Thanx bro just tried the both .........no use i think its a hardware problem .Is it possible to test the hardware ?

Don't think it's hardware as I'm on the same ROM as you and had the exact same issue !!
Luckily I got it resolved - though to be honest I'm not sure what exactly I did to fix it.
I got frustrated and did a combination of wipes, cleaning the cache, fix apk uid mismatches, clear storage and eventually it just started working

arifhanid said:
Don't think it's hardware as I'm on the same ROM as you and had the exact same issue !!
Luckily I got it resolved - though to be honest I'm not sure what exactly I did to fix it.
I got frustrated and did a combination of wipes, cleaning the cache, fix apk uid mismatches, clear storage and eventually it just started working
Click to expand...
Click to collapse
i have tried almost everything ...........gonna try apk uid fix ...lets c keepin my fingers crossed

soulpilot said:
i have tried almost everything ...........gonna try apk uid fix ...lets c keepin my fingers crossed
Click to expand...
Click to collapse
no luck still havin the black screen :-( :-( :-(

You should probably try reformatting the sdcard, along with wiping data and ext(if you have it). That would pretty much rule out software altogether.
Try reflashing the rom after that and it should work.

If it's any help - just before i got my camera back my Nexus was stuck on boot screen with the nexus logo with the open padlock.
I then had to go into Boot Loader to update the new ROM.
I guess if you can get it to hang on the Nexus initial bootup screen then it may work...

i think no can really help me on this issue !!!

Related

[Q] What is happening to my phone?

Hello,
Running Darky's 9.2 with HardcoreSpeedmod kernel on froyo 2.2 JLK, I have completed the battery calibrate and changed my file format to ext4. Everything appeared to be fine until after I rebooted from CWM.
I get the Nexus fireworks splash screen and it sits there for about an hour followed by 1 vibrate then few minutes later a series of vibrates then 1 vibrate etc...
I boot into recovery mode and do a reset and it's fine. So I thought...
I try to access the app market and it says "Application is not installed on your phone"
Is my phone about to be bricked, or is there some files that have just got corrupted?
Thanks in advance.
or is there some files that have just got corrupted?
If you install a rom and something breaks 3 routes to look at .
One bad flash = reflash
Two bad flash due to something left behind on the system = wipe and clean flash
Three Error prone rom or built in problem bug etc = Use another rom
jje
JJEgan said:
or is there some files that have just got corrupted?
If you install a rom and something breaks 3 routes to look at .
One bad flash = reflash
Two bad flash due to something left behind on the system = wipe and clean flash
Three Error prone rom or built in problem bug etc = Use another rom
jje
Click to expand...
Click to collapse
Yes... hopefully it is just corrupted files and a simple factory reset will do it.
Rashar said:
Yes... hopefully it is just corrupted files and a simple factory reset will do it.
Click to expand...
Click to collapse
I am afraid not. When my market starts not to install apps, hard reset does not fix the problem - you should re-partition with stock ROM trough ODIN and then apply Darky's ROM.
HTH
thug_life_inc said:
I am afraid not. When my market starts not to install apps, hard reset does not fix the problem - you should re-partition with stock ROM trough ODIN and then apply Darky's ROM.
HTH
Click to expand...
Click to collapse
Since I did a reset and loaded everything back, my market icon is back and functioning properly now. Are you saying that even though it's working now it could end up getting corrupted again?
I don't want to touch it now as it is running so beautifully...lol
Rashar said:
Since I did a reset and loaded everything back, my market icon is back and functioning properly now. Are you saying that even though it's working now it could end up getting corrupted again?
I don't want to touch it now as it is running so beautifully...lol
Click to expand...
Click to collapse
Yes, flashing too much custom ROMs can cause the apps to stop installing/downloading - at least this is one of the most common symptoms.
HTH

[Q] hit the CM permission button while updating caused issues

i was updating my touchpad CM9 to V2 from aplha .06 and i just downloaded it stright to the touchpad with wifi and went to update it. I wiped the cach and all that but right before i went to install the CM9 i accidently hit the fix permissions button, it was like 5 am had just woken up and was in a hurry. Now that i try to boot to CM it wont do it at all it just reboots. I was wondering if anyone had an insight on it and could help me let me know.
Thanks in advance
plada2315 said:
i was updating my touchpad CM9 to V2 from aplha .06 and i just downloaded it stright to the touchpad with wifi and went to update it. I wiped the cach and all that but right before i went to install the CM9 i accidently hit the fix permissions button, it was like 5 am had just woken up and was in a hurry. Now that i try to boot to CM it wont do it at all it just reboots. I was wondering if anyone had an insight on it and could help me let me know.
Thanks in advance
Click to expand...
Click to collapse
Try flashing over.
Wipe data, cache and Dalvik and start fresh. It sounds like you had a bad flash...
plada2315 said:
i was updating my touchpad CM9 to V2 from aplha .06 and i just downloaded it stright to the touchpad with wifi and went to update it. I wiped the cach and all that but right before i went to install the CM9 i accidently hit the fix permissions button, it was like 5 am had just woken up and was in a hurry. Now that i try to boot to CM it wont do it at all it just reboots. I was wondering if anyone had an insight on it and could help me let me know.
Thanks in advance
Click to expand...
Click to collapse
I did the exact same thing and thought I had screwed things up. Luckily I had backed up prior so I simply restored it and it appears to have been fixed. There might be another way to remedy this in case you don't have back up though.
Good luck with finding a solution.
Sent from my MIUI Evo 3D

CyanogenMod 9 - Home Button & Lock Screen

[SOLVED]
Sorry I keep posting things to myself and solving it on my own after hours -__-.. I already struggled hours beforehand and was frustrated..
Anyways, I went to CMW recovery mod, deleted the back up that I backed earlier. And then format/reset to factory mod / wipe partition / cache / Dalv. Then I went to boot my device but after 10 minutes, it'd still be loading cyanogen.... so I reinstalled the CyanogenMod9. Wiped all the things I mentioned above again and when it loaded to OS, it worked..
I have no idea what was causing it.. probably the back up file interfering somehow? Because that's the only thing I got rid of and everything went back to normal.
_________________
Hey guys, I successfully installed CyanogenMod 9 on my Gingerbread 2.3.5.
Everything is great and slick. I used to use CyanogenMod 7.
Funny thing is, I enabled the lock screen (pattern) and it seems to be not working? I don't know if I'm missing something but after leaving my phone for good 20 minutes, I came back to turn on (from sleep) and it wasn't asking for lock screen pattern. I tried slide too, same.
Also, from my previous versions, whenever I was in setting or any app, if I were to press on Home Button it would bring my back to main screen. My Home button no longer does this. I have no idea what it does now, I press it and the phone vibrates (indicates that its been pressed) but no effect. I have to literately press Back like 5 times just to return to Main menu.
Is there something I'm suppose to enable or something?
Let me know, thank you
-Dan
danroh said:
[SOLVED]
Sorry I keep posting things to myself and solving it on my own after hours -__-..
Click to expand...
Click to collapse
lol, hate when that happens
Hey danroh,
I had same issue with home button and lockscreen and this steps fixed problem:
1) I accidentally downloaded Jelly Bean gapps instead of ICS version
2) Reinstalled CM9
3) Downloaded experimental build and flashed that over stable one
4) Flashed with proper ICS gapps
5) Factory reset/Data wipe, Clear Dalvik cache
6) Reboot
-----
Hit thanks if that worked for you
HElp ME
hard2play said:
Hey danroh,
I had same issue with home button and lockscreen and this steps fixed problem:
1) I accidentally downloaded Jelly Bean gapps instead of ICS version
2) Reinstalled CM9
3) Downloaded experimental build and flashed that over stable one
4) Flashed with proper ICS gapps
5) Factory reset/Data wipe, Clear Dalvik cache
6) Reboot
-----
Hit thanks if that worked for you
Click to expand...
Click to collapse
IT didnt wok, maybe because i dont have the needed gapps. Do you have a link?
danroh said:
[SOLVED]
Sorry I keep posting things to myself and solving it on my own after hours -__-.. I already struggled hours beforehand and was frustrated..
Anyways, I went to CMW recovery mod, deleted the back up that I backed earlier. And then format/reset to factory mod / wipe partition / cache / Dalv. Then I went to boot my device but after 10 minutes, it'd still be loading cyanogen.... so I reinstalled the CyanogenMod9. Wiped all the things I mentioned above again and when it loaded to OS, it worked..
I have no idea what was causing it.. probably the back up file interfering somehow? Because that's the only thing I got rid of and everything went back to normal.
Click to expand...
Click to collapse
Weirdly, my brother's Galaxy S had the same thing. Home button just would not work after installing CM9. Tried a few things, failed.
Then, I found this thread and I remembered that I'd backed up his old CM7 a while before. Deleted that backup in CWM Recovery, factory wiped/cache wipe, reinstalled CM9 and Gapps for 9 and boom, everything was fine.
EDIT:
Another thing to note is that when the home button wouldn't work, there was no Lockscreen either, just like you had. On first boot it didn't prompt me for a google account either, which it did do after I deleted the backup.
hard2play said:
Hey danroh,
I had same issue with home button and lockscreen and this steps fixed problem:
1) I accidentally downloaded Jelly Bean gapps instead of ICS version
2) Reinstalled CM9
3) Downloaded experimental build and flashed that over stable one
4) Flashed with proper ICS gapps
5) Factory reset/Data wipe, Clear Dalvik cache
6) Reboot
-----
Hit thanks if that worked for you
Click to expand...
Click to collapse
hey man!!..thnx for your guide...i w as actually in great trouble coz of this error..nd now its fixed!!...thnx a lot!!...

Aroma Installer Nightmare! Doesnt install just black screens then reboots

Everytime I try and install any Aroma installer, i can get though all the menu's, making all selections, but then once I click to actually start the installation, the phone screen just goes black, and the phone reboots, without the installation having completed. Which is quite an annoyance seeing as most installers are Aroma for the HTC One!
I have tried multiple recoveries (TWRP, CWM, CWM touch) all have the same error. I temporarily solved it for 1 install, by reflasing the boot image of my ROM (trickdroid 7.0)
No idea what has caused this, does anyone have a clue how to fix it? That doesn't involve a complete wipe?
Also, using volume keys makes no difference on this, only prevents crashing during menus
Video of what I mean is here: http://www.youtube.com/watch?v=KEP9aJzUFGo
dh2311 said:
Everytime I try and install any Aroma installer, i can get though all the menu's, making all selections, but then once I click to actually start the installation, the phone screen just goes black, and the phone reboots, without the installation having completed. Which is quite an annoyance seeing as most installers are Aroma for the HTC One!
I have tried multiple recoveries (TWRP, CWM, CWM touch) all have the same error. I temporarily solved it for 1 install, by reflasing the boot image of my ROM (trickdroid 7.0)
No idea what has caused this, does anyone have a clue how to fix it? That doesn't involve a complete wipe?
Also, using volume keys makes no difference on this, only prevents crashing during menus
Video of what I mean is uploading as I type this, allow 20 minutes (my internet is that bad)
Click to expand...
Click to collapse
first i would say dont have your phone plugged in while flashing and second make sure your phone is cool not hot. seems to get worse for me when the phone gets hot. also there is a new sense rom that doesnt use aroma its called rayglobe 4.0
skinsfanbdh said:
first i would say dont have your phone plugged in while flashing and second make sure your phone is cool not hot. seems to get worse for me when the phone gets hot. also there is a new sense rom that doesnt use aroma its called rayglobe 4.0
Click to expand...
Click to collapse
Phone wasn't plugged in, and the issue i'm having it with now is the kernel, I have the ROM installed, problem didn't start until a day or so after the rom install. Can't tell what started it
dh2311 said:
Phone wasn't plugged in, and the issue i'm having it with now is the kernel, I have the ROM installed, problem didn't start until a day or so after the rom install. Can't tell what started it
Click to expand...
Click to collapse
are you wiping davlik and cache before flashing that will also help and you might want to try fastboot erase cache
skinsfanbdh said:
are you wiping davlik and cache before flashing that will also help and you might want to try fastboot erase cache
Click to expand...
Click to collapse
Just tried that, same error after fastboot cache wipe aswell as davlik cache. So frustrated, only just got a HTC one, usually a nexus guy, and never had experience with Aroma before this, not a good first impression of Aroma
dh2311 said:
Just tried that, same error after fastboot cache wipe aswell as davlik cache. So frustrated, only just got a HTC one, usually a nexus guy, and never had experience with Aroma before this, not a good first impression of Aroma
Click to expand...
Click to collapse
yea its an aroma issue not phone or rom issue. have you used all in one toolkit to fastboot erase cache and install recovery
skinsfanbdh said:
yea its an aroma issue not phone or rom issue. have you used all in one toolkit to fastboot erase cache and install recovery
Click to expand...
Click to collapse
I'm on mac, so it would require Parallels, so I just type them out to save the hassle. I'm manually installing the kernel now, flashing boot.img in fastboot and pushing all the extras via ADB but I'd still like to figure out whats up with my phone and Aroma. It's not like the zips are faulty, its every single aroma installer, so something on my phone must be up
dh2311 said:
I'm on mac, so it would require Parallels, so I just type them out to save the hassle. I'm manually installing the kernel now, flashing boot.img in fastboot and pushing all the extras via ADB but I'd still like to figure out whats up with my phone and Aroma. It's not like the zips are faulty, its every single aroma installer, so something on my phone must be up
Click to expand...
Click to collapse
yea maybe. every once and a while aroma gives me a lot of issues but most of the time it only takes 1-3 times to install. but if you get tired of it give rayglobe a try i think its pretty good
skinsfanbdh said:
yea maybe. every once and a while aroma gives me a lot of issues but most of the time it only takes 1-3 times to install. but if you get tired of it give rayglobe a try i think its pretty good
Click to expand...
Click to collapse
I'm not overexaggerating when I say I've tried this about 20 times. Going for a full wipe, back to RUU and see if that solves all this
dh2311 said:
I'm not overexaggerating when I say I've tried this about 20 times. Going for a full wipe, back to RUU and see if that solves all this
Click to expand...
Click to collapse
ive had that also i just restored my backup and quit for the day then tried the next day and it worked
dh2311 said:
I'm not overexaggerating when I say I've tried this about 20 times. Going for a full wipe, back to RUU and see if that solves all this
Click to expand...
Click to collapse
try with re-downloading the file and put it in root of your sd card
rambo12345 said:
try with re-downloading the file and put it in root of your sd card
Click to expand...
Click to collapse
tried that as well, tried all kinds of different directories, and redownloading the files, but files that did work and I have installed now wont, so i have no clue whats happened
dh2311 said:
tried that as well, tried all kinds of different directories, and redownloading the files, but files that did work and I have installed now wont, so i have no clue whats happened
Click to expand...
Click to collapse
Are you touching the screen at all? Like even the slightest touch? I know that in the ARHD thread it mentioned that's an issue and will cause problems. I know that I accidentally touched it and messed everything up for me. I am now super careful when I flash to make sure I touch nothing except the buttons.
Okay, in a weird turn of events, I thought i would rather than going to an RUU just wipe everything and reinstall everything, and the Aroma installers for the ROM and tweaks are working so far...
EVERYTHING WORKED! Dont know whether it was the wipe, just luck, installing using only volume keys and power button. But this seems to have gone away :fingers-crossed:
nolimit78 said:
Are you touching the screen at all? Like even the slightest touch? I know that in the ARHD thread it mentioned that's an issue and will cause problems. I know that I accidentally touched it and messed everything up for me. I am now super careful when I flash to make sure I touch nothing except the buttons.
Click to expand...
Click to collapse
I could well be... have some working now, but if one breaks, Ill try reinstalling using volume keys and power button and never touch the screen
awesome. glad you got through it bro:good:

[Q] Any Way out when a CM 12 theme start to misbehaves after installation

Whenever a CM 12 theme misbehaves after installing where you cant access other things on the phone apart from constant popups of applications closing and misbehaving, what is the right solution in such a scenario to get back to normal working of phone ,
I have read something regarding deleting a folder from TWRP which resets the theme,
If anybody knows any solution apart from installing the ROM again.
Thank you in advance..
shamuX said:
Whenever a CM 12 theme misbehaves after installing where you cant access other things on the phone apart from constant popups of applications closing and misbehaving, what is the right solution in such a scenario to get back to normal working of phone ,
I have read something regarding deleting a folder from TWRP which resets the theme,
If anybody knows any solution apart from installing the ROM again.
Thank you in advance..
Click to expand...
Click to collapse
reflash your rom, dirty(not wiping anything).
simms22 said:
reflash your rom, dirty(not wiping anything).
Click to expand...
Click to collapse
That actually won't help as the theme would still be installed and applied. You should be able to delete the theme apk from the file manager in TWRP though. Haven't tried it myself but that should make the theme engine default back to system theme.
Reboot to safe mode.. Atleast you can do that as the reboot menu appears on top of everything regardless what's going on the inside..
Just reapply stock theme..
And reboot..
Sent from my Galaxy Nexus using Tapatalk 2 Pro

Categories

Resources