Hi,
I am using an un-rooted Nexus One phone with Froyo (2.2.1).
The camera has stopped working unexpectedly.
Whenever I start the camera app, it gives me the error:
"Activity Camers (in application Camera) is not working"
It gives me the option to wait, force close or report.
If I select wait, it just hangs in there and pops the above msg again.
If I force close the app, and try to start it again, I get the error:
"Cannot connect to camera"
The phone did not fall down and is always handled properly.
This happened all of a sudden.
The last thing I did with the phone was to copy songs to the SD card.
I have factory reset the phone twice and formatted SD card, even swapped SD cards, but no luck yet.
I am based in India, the phone was bought in the US, I have no warranty.
Any help will be appreciated.
Thanks.
Sorry but I think your camera just died it is possible for the camera to die without any physical abuse but it is uncommon. The only other thing I can recommend would be to root and install a custom ROM (or at least a kernel) and see what happens but I don't think it will fix it.
Resolved....
Thanks Dude Random21..!!
Actually, I just resolved the issue about 30 mins ago.. Was downloading the apps and restoring its state as it was before I had factory reset it.
Well, after doing everything related to software to fix the issue, I concluded that it might be a hardware issue.
So, I started to search for threads involving camera hardware issues.
I took hints from the following post:
Google "Camera on my Nexus One not working - no flash either...all apps that use camera also not working - Help!?!?! " and you will be lucky..
(I cannot post links as I am a newbie)
Saw all videos on youtube about nexus teardown and just finished doing it.
I checked all the connections/internal wiring on the phone and once done, rebooted the phone and it worked..
Unfortunately my phone received a couple of scratches along the way, so others should be more careful about it.
Thanks for your help.
--- sent from my nexus one
No problem, I do what I can to help out. And good for you for having the guts to fix your nexus one's hardware cause I'm pretty sure that if I had an issue like that I would't have the guts to tear it down myself even with ifixit.
Remove (renaming is better) the DCIM directory from SDCARD. It is probably a corrupted (or incompatible with 2.3) file. After that, the camera cames back to life, then you can copy your “Camera” directory to the new DCIM directory created by your phone.
HTH
Related
This just started today. If I go to open the Camera, the screen goes black and then a few seconds later the force close window pops up.
I tried closing everything with Advanced Task Manager. Same problem.
Powered off the phone and rebooted. Same problem.
It was working a few days ago and I haven't installed any new apps or done anything drastic since.
I have a feeling wiping will fix it, but I wanted to see if anyone else had this problem and fixed it before doing that.
Running JF1.5 ADP currently.
RueTheDay said:
This just started today. If I go to open the Camera, the screen goes black and then a few seconds later the force close window pops up.
I tried closing everything with Advanced Task Manager. Same problem.
Powered off the phone and rebooted. Same problem.
It was working a few days ago and I haven't installed any new apps or done anything drastic since.
I have a feeling wiping will fix it, but I wanted to see if anyone else had this problem and fixed it before doing that.
Running JF1.5 ADP currently.
Click to expand...
Click to collapse
Try using adb to delete the camera.apk and then redownload JF and pul the apk out of it and repush it to your phone
****. Just upgraded to JF 1.51 ADP and wiped, but camera still not working. Will now try the US CBR43 version of JF1.51 to see what happens. I hope this isn't a hardware issue.
Same problem with JF1.51.
Then I did a Nandroid restore to a date when I know the camera was working. - Same problem.
Then installed the latest Cyanogen ROM. Same problem.
I'm out of ideas. Help!
Try the camcorder? They're technically seperate apps. Also, go download some third party camera or recorder, like Qik or SnapPhoto. If none of those work, it's most likely a hardware problem.
When the camera app can't access the camera (such as a malfunction or other problem) it returns an error because part of its components (in this case, the most important) isn't working. Try even going to another build, like Cyan's, to see if anything else gets resolved.
lukekirstein said:
Try the camcorder? They're technically seperate apps. Also, go download some third party camera or recorder, like Qik or SnapPhoto. If none of those work, it's most likely a hardware problem.
When the camera app can't access the camera (such as a malfunction or other problem) it returns an error because part of its components (in this case, the most important) isn't working. Try even going to another build, like Cyan's, to see if anything else gets resolved.
Click to expand...
Click to collapse
Tried Cyan's ROM. Same problem. Moved apps off SD and back to memory, same problem. I'm going to try the phone with a different SD card as a long shot. If that doesn't fix it, I'm thinking definitely hardware.
RueTheDay said:
Tried Cyan's ROM. Same problem. Moved apps off SD and back to memory, same problem. I'm going to try the phone with a different SD card as a long shot. If that doesn't fix it, I'm thinking definitely hardware.
Click to expand...
Click to collapse
Did you try a third party app?
lukekirstein said:
Did you try a third party app?
Click to expand...
Click to collapse
Yeah same problem.
If it's hardware, do I need to unroot it before going back to T-Mobile?
Yep, sounds like a hardware problem. It'd be a good idea to try to unroot it, unless you're on T-Mobile's phone insurance, in which case it's no-questions-asked.
What in the blue ****?
I was having issues with Touchdown (Exchange sync) force closing, so I upgraded to the latest version which fixed that. Then just for ****s and giggles I tried the camera and it's working now. I doubt the two are related, but man WTF.
Anyway, on the plus side, I do like the latest Cyanogen ROM better than the JF1.5.
eh..okay then. Change the thread title to [SOLVED] please
Edit thread doesn't let me change the title.
Anyway, it was the SD card. Reformatted my EXT2 partition and redid apps2sd and it started working again. Then started getting a bunch of force closes on other apps. Ultimately reflashed back to JF1.51 and moved all my apps back to main memory. Everything works flawless now.
I rooted my G1 the day I bought it in April and did app2sd shortly after. Nothing but problems. Tried every apps2sd method. They all work fine for a few weeks and then start falling apart.
Ok, so everything was working fine yesterday. I woke up this morning and decided to play a little 'world of photo'. It FC's, so I mess with it for a little bit before just trying to open my normal camera. When I try to open my camera, it puts the screen in sleep mode, so I have to hit the power button and unlock the screen like normal, then it gives me the error "Cannot connect to camera".
My phone is rooted and flashed with the latest Cyanogen business, but like I said, nothing was altered, updated, downloaded, etc. My camera just stopped working. Anyone have any thoughts or ideas? Really hoping to get this resolved without having to contact HTC, as I'm sure the unlocked bootloader screen will cost me a small fortune.
If I open an alternative camera app, it opens, but doesn't work. I can back out and then go to my default camera and it works until I close it. Then it won't open again without having to go through the steps of opening the other app, etc.
I'd try a nandroid restore.
Tried it already. Tried restoring back to original, wiping, everything else. Nothing worked. Camera wasn't working all morning, now all of a sudden it's working again. Guess I'll just count my lucky chickens and chalk this up as a win...
Well, my happiness was short lived. Still having the same problem. I'm really not sure what exactly it could be. But the fact it worked the one time today gives me hope.
also having this problem. tried a nand backup and also wiping and re-flashing the gapps and the cm-5.0.4.1 update.. still nothing
it seems my camera went bad somehow, tried even flashing the stock rom, nothing... i'm calling htc, crap my phone is unlocked.. wish me luck.
update: yeap, im getting a replacement. they put $529 on hold on a credit card, send you the device and once they get the "damaged" device they release the funds... meh..
Hey velazcod, you think we can get an update on his this worked out? I'm having the same camera problem and I too am bootloader unlocked. I'd like to hear how HTC handled your unlocked device.
sorry for not posting a status before... so here is what happened:
- Called HTC and they didnt have any issues replacing the phone since the issue seemed to he a hardware issue. They have been nice about this, depends on the hardware issue, I guess if you burn the motherboard they will probably get *****y.
- You can send it to get repaired or replaced, both are in warranty, unless they find some other issue (water damage, etc). However, if you decide to get it replaced they would take your credit card, and put $528 on hold for a few days until they get the original phone back. They dont actually charge it to the credit card, just an authorization, it all depends in your bank, for example my bank (chase) put the money back in my account after 5 days.
- Anyway, I got my "new" N1, and I double checked everything before unlocking the bootloader and doing our stuff. The phone was crap, it was slow and the sticker on the battery cover seemed like it was removed, maybe a refurbished unit. I called and *****ed about it, and they said I needed to send my original phone back, and then later on request another replacement. I kept *****ing because I could live with a bad camera for a few weeks, but not with a slow phone
- Anyways, in the end they allowed me to send back that refurbished unit. After a few weeks i had no response from them and I had to call them, a day after i got my new phone, this time it was good, so i unlocked it, did my thing, factory reset the original phone and sent it on its way.
- It all seemed good for a few weeks, until i got a call from HTC saying that I needed to pay for a repair fee ($60 something) because they had found the problem had been user damage. the girl had no idea how to back that up, and i kept saying that i had never drop the phone or broken the camera in purpose (which is true). She said she was going to escalate the issue and I would get a call back. Still waiting.
In the end I got my new phone and we are all happy, but be careful, I love HTC but don't let them screw you.
Sent from my Nexus One using the XDA mobile application powered by Tapatalk
$60 isn't that bad. I would be interested in exactly what they found.
yes that isnt that bad. and i would pay it no problems if it really was my fault. but really, i take care badly of my phones and i had never drop or have done anything to my phone that would cause this camera issue.
besides, the girl that called me had no idea what really happened or what they found, when they call me i will post the info here.
Quick update:
I was having the "cannot connect to camera" error. Turns out that it was an issue with my memory card. Apparently, the card was slightly mis-seated.
Prior to discovering that, I tried everything. I flashed other ROMs, nandroid flashed back to stock, and manually restored to stock.
The weird thing is that the memory card was still functioning properly in every other aspect. I could browse my phots in the gallery and browse the contents of the memory card in Astro. Prior to my discovery, I had also formatted the memory from the settings menu. On a whim, I shut the phone down, removed the memory card, reinserted the memory card, booted it back up and gave it a shot. To my surprise, it worked!
I just thought I'd let you guys know so anyone else having a similar issue can try reseating the memory card before giving up and paying HTC for repair.
moto211 said:
Quick update:
I was having the "cannot connect to camera" error. Turns out that it was an issue with my memory card. Apparently, the card was slightly mis-seated.
Prior to discovering that, I tried everything. I flashed other ROMs, nandroid flashed back to stock, and manually restored to stock.
The weird thing is that the memory card was still functioning properly in every other aspect. I could browse my phots in the gallery and browse the contents of the memory card in Astro. Prior to my discovery, I had also formatted the memory from the settings menu. On a whim, I shut the phone down, removed the memory card, reinserted the memory card, booted it back up and gave it a shot. To my surprise, it worked!
I just thought I'd let you guys know so anyone else having a similar issue can try reseating the memory card before giving up and paying HTC for repair.
Click to expand...
Click to collapse
Well, keep in mind that it could be a placebo effect, and you think you are fixing it by fiddling the SD card but its not real.
The reason I tell you that is because, when the issue started happening for me, I would get that error randomly, and then it started happening more frequently until it totally stopped working.
Also, the Camera app not detecting the SD card gets an error when you try to take a picture and it actually says the specific SD card error. Try taking the SD card out and try it out, you will get a visual of the camera on the display, but when you try to take the picture it gives out the "SD card not detected" error... on the other hand, you might be experiencing something totally different.
This error "cannot connect to camera" also comes with the camera app not loading completely and visual of the camera not loading on the screen. Also try loading up the Barcode Scanner, you should get a similar error and no visual of the camera.
I agree that it could be placebo effect. But, I was experiencing all of the things you describe regarding the camera app not loading completely and barcode scanner not working properly. I know the error that you're talking about when you open the camera app without any memory card at all and that definitely was not what I was experiencing. Also, the was nothing random or intermittent my cannot connect to camera errors. It stopped working about four days ago and no ammount of reboots, reflashes, or nandroid restores could bring it back. It wasn't until I reseated the memory card that the camera was able to load and function again. My suspicion is that when a memory card is present and you open the camera app, it tries to do something with the card as part of the loading process. I suspect that the card being slightly mis-seated causes this to fail and prevents the camera from loading properly.
I will definitely keeps you guys posted. Hopefully this is a lasting fix and not a placebo.
moto211 said:
I agree that it could be placebo effect. But, I was experiencing all of the things you describe regarding the camera app not loading completely and barcode scanner not working properly. I know the error that you're talking about when you open the camera app without any memory card at all and that definitely was not what I was experiencing. Also, the was nothing random or intermittent my cannot connect to camera errors. It stopped working about four days ago and no ammount of reboots, reflashes, or nandroid restores could bring it back. It wasn't until I reseated the memory card that the camera was able to load and function again. My suspicion is that when a memory card is present and you open the camera app, it tries to do something with the card as part of the loading process. I suspect that the card being slightly mis-seated causes this to fail and prevents the camera from loading properly.
I will definitely keeps you guys posted. Hopefully this is a lasting fix and not a placebo.
Click to expand...
Click to collapse
I see what you mean. Makes sense, keep us posted.
Update:
So, although the fix I previously mentioned did work, I started having other issues that indicated that the actual camera hardware was failing. When I would start up the camera app the camera image displayed on the screen started showing color distortion. Sometimes it would do that and sometimes it wouldn't. I noticed that if it wasn't distorted, I could lightly squeeze the sides of the phone and the image would become distorted and would not go back to normal after I stopped squeezing. I figured that indicated hardware issues but decided to try a low level format on my memory card just in case it was an issue of bad blocks on the card. The format didn't fix anything. A few hours later, the camera died and never came back. I started a ticket with HTC for an advanced replacement. I received my new phone on Friday and am sending back the old one today. I restored it to unrooted factory ROM and recovery image. I will keep you guys posted as to what, if any charges they try to stick me with.
moto211 said:
Update:
So, although the fix I previously mentioned did work,......
Click to expand...
Click to collapse
crap, that's what i thought. that sucks. keep us posted :-/
Final update:
I returned my phone with the broken camera on Monday. Tuesday I received an email stated that they had received my device and it had a link to website that I could use to get updates on the status of the repair/return. I checked in the following day with no change. Today it showed this:
Status: We have completed your case. If you can help us improve our service, or would like to comment, please contact HTC customer service representatives.
Service Type: Repair
Service Model: C4-On site exchange
Failure Description: C/x states can not open camera app-freezes or force closes
I even called HTC to make that the ticket was closed and that they didn't need anything else from me. They said that everything was good.
moto211 said:
Final update:
I returned my phone with the broken camera on Monday. Tuesday I received an email stated that they had received my device and it had a link to website that I could use to get updates on the status of the repair/return. I checked in the following day with no change. Today it showed this:
Status: We have completed your case. If you can help us improve our service, or would like to comment, please contact HTC customer service representatives.
Service Type: Repair
Service Model: C4-On site exchange
Failure Description: C/x states can not open camera app-freezes or force closes
I even called HTC to make that the ticket was closed and that they didn't need anything else from me. They said that everything was good.
Click to expand...
Click to collapse
Good to hear that.
On my case, I was never contacted again by the "escalated rep"... but I just checked my ticket/case and it seemed to have been closed, so I guess good news.
Hello Guys,
I am having the same problem as you both had. Í am seeing the same symptoms such as not able to run the camera app. My phone screen goes blank when i try to open the camera app and the bar scanner program says it cannot connect to the camera and that I might need to restart my device. I have tried to use previous roms and removed the sd card but nothing seems to work. I am wanting to send it in for repair but I wanted to know what else I should do to my phone besides reflashing the stock rom. Did either of you have the amonRa recovery program and how did you remove it if you did. Is there anything else I should do?
Thanks.
I got the original shipping rom package from modaco and renamed it PASSIMG.zip and flashed it from the bootloader. It restored everything to stock...recovery, radio, and os.
Hi,
I have a rooted GT-i9000m (bell Galaxy S Vibrant). I used the one click lag fix to root my phone and it works fine.
A few days ago out of no where all the apps started auto closing as soon as i opened them and then both the menu and back touch buttons lit up and the screen went black. I held the power down till it rebooted only to get and error with com.android.calendar even tho I never use the app. When it finish's booting none of my installed apps are showing.
The first time it happened with com.android.app and I did a full wipe and factory reset and just reinstalled everything.
Ideally I don't want to system reset to factory settings again and lose all my files and notes that i copied back on to the phone 2days ago...
Please note I have tried clearing the data for the calendar app in settings -> apps and i cleared the calendar back up. My problem is that none of my installed apps are showing...
(Update) I also cant reinstall or update apps due to a Installation error - Insufficient storage. But there's room on both SD cards. I also set 850mb for apps when i did the one click lag fix and i don't have 850mb of apps installed.
(Update 2) I did a factory reset again this time i didn't format the internal and external SD cards. (It works like new again) Thus I got to keep all my personal files and ring tones ect. The only thing that was deleted that I didn't back up is my Notes. This leads me to my new question whats best for backing up apps on a rooted SGS (bell Vibrant)?
If anyone has answers they would be much appreciated.
i had the same problem
install rom manager from the market place
there is a option in there "Fix Permissions" just run that and it will fix it up for you
only takes 1-2min to run
Tried what you said but i cant install anything... I get Installation Error - Insufficient storage available.
I now understand the cause of the problem. I change my battery once and some times twice a day. At first I would wait for the long shut down (untill the screen goes totaly black) and then take off the back and swap out the battery. At least 3 times the phone would boot up and ask me for the network unlock code (I bought the unlock code directly from bell for 75$). I found this rather annoying so i tried just taking the battery out wile it was on (idle) and it appeared to work flawlessly at least 20-30 times before the phone would start to do an endless force close loop cycle. This kept forcing me to do a factory reset on the phone. I can only assume the one click lag fix and my disregard for the need of the shutdown before removing the battery must be all the cause of my problems.
I will try and see if my phone is more stable with out the one click lag fix.
nope that is not the cause of the problem
but it sounds like you are another victim of the lag fixes that is killing your internal SD card.
not the fault of the lag fix, it just make the problem apear sooner than later
I have been having a similar issue and I'm using Voodoo lagfix. I think it's because I took the battery out before it had completely shut down.
read this
http://forum.xda-developers.com/showthread.php?t=793404
Well the phone bit the dust today. I opened up google maps to look up an address and it crashed with the usual error. So i rebooted the phone and now it stays stuck at the boot logo. (the glowing S with both touch keys staying lit) So i did the recovery thing again but this time I had to do the Vol-up + home + power in order to get the phone working some what. IDK but it wont let me log into my google account to sync my contacts. My APN settings are correct and working and I even tried off my Wifi at home. I'll just hope its a google problem and not my phone acting up. Thanks for the pointer to the bad internal SD. That may be the problem kinda hard to prove it to Samy thoe...
I get force close errors after about 4-7 days of use. Now its gotten worse. A few days ago I was looking up an address and my phone crashed and rebooted it self. It then hug at the S boot logo for 20mins. I got to my friends apartment building to find my phone still stuck at this boot logo. I couldn't remember his apartment number or buzzer code... Normally i just check my contacts list and buzz the code. I was standing out side in the Canadian fall cold wind trying to get this phone to work... OMG i almost just smashed it on the spot. Anyways I remembered about something i had read on this forum about the recovery mode ( i had used it to root ) so i tried that out got the little menu and tried every option before having to do the dreaded factory reset. Well nothing work with the exception of the factory reset it got my phone working in about 5mins... LOL
Anyways I thought I might try upgrading the firmware when I got home. What a mistake... I cant control my phones MP3 player via my bluetooth car stereo any longer. Tried everything even a factory reset and formatting the internal and external SD's. I tried running it with out rooting it again and with out the lag fix in hopes that I wouldn't get a force close error. Wouldn't you know it about 5 hours after the factory reset un-rooted just after i finish coping over all my music. I get a force close error! So I tried again and this time the phone ran for about 30hours before it started giving me force close errors about the email now...
Sigh I've tried just about everything in my power to make this phone work. So I assumed it must be the phone... I called Samsung up to get a RMA going... Wouldn't you know it they tell me that I have to call my carrier to get it RMA/repaired. I try to explain that I bought the phone with out a contract and bought the unlock code from Bell so I could use it on Fido. They tell me to call Fido... ROFL Fido wouldn't even give me their APN settings when i got this phone so knew they would be of no help. They don't even have one android phone in their line up i tell the sammy rep. So they tell me I should go back to the Bell store I bought it from to get it repaired/RMA'ed.
I doubt Bell will be of much help but here's hoping.
Do you think my phone is broken, bad flash, buggy memory, ect and needs to be RMA'ed?
Update...
I got my phone back from repairs 2 weeks ago. They flat out replaced the phone for a new one. This was a huge headache for me because the new one wasn't unlocked. Took Bell 2 hours to get the new one unlocked wile my wife waited out side double parked downtown! (I thought it would be a quick pick up and I would be out) The blue-tooth works flawlessly again!!
Much to my dismay the replacement phone has started acting up much like my first one did. It gets several force close errors a day and has gotten to the point where it no longer can send or receive text messages (using Handcent). The stock Music Player app also force closes at random with more frequently. It looks like I got another Lemon. This time around I did NOT root, lag-fix, or flash firmware. I will be sending it for repairs as soon as I can afford to buy another phone to use wile this one is off at repairs. My back up phone is a 3~ year old Iphone3g that my son has made his... (cracked screen, vol rockers dont work, power button is jammed in, the LCD screen it self is bleeding on the top edge)
The Vibrant never let me down other than as a phone. As a divx player or using all-share it rocks! I use these features A LOT to play my 720p divx movies on any TV or the projector in the bedroom .
with that being said I might keep the phone just as a portable movie player to bring from place to place and put my sim in something more stable.
In late December my first 9000M died on me (internal sd failure). I sent it directly to Samsung and they replaced the phone with a new one. I got the new phone about a couple of weeks ago and now some problems are starting to show up. Both my old and new 9000M's were manufactured in 10.08. The new one came back with JL2 installed and I haven't done anything other than unlock and root.
Last night I went to go use Google Goggles. When I launched it, it went to a black screen and the phone vibrated a few times then force closed. I tried it again and the camera view would show up then go black and then show up again and keep repeating this cycle. So then I tried the camera and that was doing the same thing (flashing on/off). I rebooted the phone and tried again. This time Google Goggles would take a picture but it would keep scanning forever. I reinstalled Google Goggles and it worked for one picture last night
Now skip ahead to today. Goggles force closes again. When I start the camera it seems like it is going to work but when I try take a picture, the camera starts flashing on/off and then a warning comes up and it says "camera failed" then eventually the camera app closes.
Does this sound like the start of an internal sd card failure? I had similar problems with my last Galaxy S before it died but it was different apps failing just before the phone went completely black and never woke up again.
This is a bit ridiculous and I don't think I would buy another Samsung phone anytime soon. I'm not sure what I will do if this one is dead because I would rather not have to deal with the same problem a third time.
Thanks for your input.
Could definitely be the start of the SD card failure. The good news is you'd be able to call Bell, and they'd ship a new phone to you within 3-5 days and apply a $100 credit towards your account, so you wouldn't have to deal with Samsung.
I'd try performing a factory reset to rule out a problem with the software, and if the FCs keep occurring I'd flash a different ROM. If the problems still persist on a different ROM, seems like you should give Bell a call sometime soon.
seeARMS said:
Could definitely be the start of the SD card failure. The good news is you'd be able to call Bell, and they'd ship a new phone to you within 3-5 days and apply a $100 credit towards your account, so you wouldn't have to deal with Samsung.
I'd try performing a factory reset to rule out a problem with the software, and if the FCs keep occurring I'd flash a different ROM. If the problems still persist on a different ROM, seems like you should give Bell a call sometime soon.
Click to expand...
Click to collapse
Actually I'm not a Bell customer so no good news there. I will try a factory reset.
The factory reset worked but then I used Titanium Backup to restore all my apps and settings and then my camera was broken again. It is highly likely that my camera files were corrupt already the last time I backed up. So I did yet another factory reset and this time I won't restore backups and I will see how long it lasts.
Here we go again... Yesterday the video camera would fail to record. Now the still camera either says "Camera failed" or the viewfinder screen flashes between the camera image and black until it force closes.
I'm starting to hate the 9000M.
Hey everyone,
I'm getting this error when I try to switch on my LG 4XHD.
"Security Error
Error !!! Read morningcall"
To give you a background, I actually happened to drop my phone on a very rough and uneven concrete surface, screen-first. This developed cracks on the glass, but everything else was perfectly normal (the touch sensitivity, screen, camera, etc.) so I stopped using the phone and removed the SIM card until I could get the glass replaced. But a few days ago I switched it on (without the SIM card) just to make sure everything was still OK and also turned on the WiFi. I then went into Google Chrome and tried to open google.com, but my phone hung up, so I had to remove the battery and start the phone again, and that is when I started getting this error. Since then I've been getting this error whenever I try to switch on the phone and it does'nt get past that, not even allowing me to switch it off.
There is a lot of important data in the internal storage of which I would like to take a backup before doing anything.
Can someone please help me fix my phone?
Thanks a lot for your help in advance...
Likhit6 said:
Hey everyone,
I'm getting this error when I try to switch on my LG 4XHD.
"Security Error
Error !!! Read morningcall"
To give you a background, I actually happened to drop my phone on a very rough and uneven concrete surface, screen-first. This developed cracks on the glass, but everything else was perfectly normal (the touch sensitivity, screen, camera, etc.) so I stopped using the phone and removed the SIM card until I could get the glass replaced. But a few days ago I switched it on (without the SIM card) just to make sure everything was still OK and also turned on the WiFi. I then went into Google Chrome and tried to open google.com, but my phone hung up, so I had to remove the battery and start the phone again, and that is when I started getting this error. Since then I've been getting this error whenever I try to switch on the phone and it does'nt get past that, not even allowing me to switch it off.
There is a lot of important data in the internal storage of which I would like to take a backup before doing anything.
Can someone please help me fix my phone?
Thanks a lot for your help in advance...
Click to expand...
Click to collapse
One more thing that happened before it hung up is that Whatsapp gave an error saying the date was incorrect and also the Onavo data monitoring app said I used up 325% of 3G my data. Just wanted to mention these in case there are any known bugs related to these.
Likhit6 said:
One more thing that happened before it hung up is that Whatsapp gave an error saying the date was incorrect and also the Onavo data monitoring app said I used up 325% of 3G my data. Just wanted to mention these in case there are any known bugs related to these.
Click to expand...
Click to collapse
Can someone please at least help me take a back of my files in the internal storage when the phone is in this condition?
I think you would not be able to make any backup now ( I personally had this morning call problem as well but it was because of some other problems) the only thing that you can do is restart in software update mode and re flash with LG Flash Tool. You can find the thread named under "Rollback to ICS by SnXo.
I hope it can help you and don't forget to thank him for his post.
Sent from my LG-P880 using xda premium app.
Like what I said hit " Thanks" Button.
sPEADy said:
I think you would not be able to make any backup now ( I personally had this morning call problem as well but it was because of some other problems) the only thing that you can do is restart in software update mode and re flash with LG Flash Tool. You can find the thread named under "Rollback to ICS by SnXo.
I hope it can help you and don't forget to thank him for his post.
Sent from my LG-P880 using xda premium app.
Like what I said hit " Thanks" Button.
Click to expand...
Click to collapse
Sad to know I cant backup my files now. But, nevertheless, thanks a lot for the reply and suggestion...