i was trying game guardian on my phone and suddenly a weird noise came out of the mobile(like a hard vibrate) and phone restarted,
now the camera is not working i tried diff camera apps it says "could not connect to camera"
Is there any way to know if the camera is damaged without opening the case ??
How worst the damage could be ? or how much it will cost to repair it, any idea ?
The1sameer said:
i was trying game guardian on my phone and suddenly a weird noise came out of the mobile(like a hard vibrate) and phone restarted,
now the camera is not working i tried diff camera apps it says "could not connect to camera"
Is there any way to know if the camera is damaged without opening the case ??
How worst the damage could be ? or how much it will cost to repair it, any idea ?
Click to expand...
Click to collapse
Which Rom are u using???? Try with some third party cam apps like Camera Ics,Camera jb+(paid)....
If It doesnt work then reflash the rom.
Reboot must have happened due to multitasking.
Flash Stock Rom again it will definitely help you !
Sent from my HTC Desire S using xda app-developers app
The1sameer said:
i was trying game guardian on my phone and suddenly a weird noise came out of the mobile(like a hard vibrate) and phone restarted,
now the camera is not working i tried diff camera apps it says "could not connect to camera"
Is there any way to know if the camera is damaged without opening the case ??
How worst the damage could be ? or how much it will cost to repair it, any idea ?
Click to expand...
Click to collapse
Clean install for sure? Did you drop your phone?
Sent from my Nexus 7 using Tapatalk HD
Or try Flashing Rom properly.
Flash into cwm recovery goto mounts and storage mount system and sd ext if exists on ur sd format both then go back then simply flash the stock Rom
Recommended " European"
Sent from my HTC Desire S using xda app-developers app
never head or anything like this before ..but try wiping everything and try to reflash any rom ..!!!
CM10 fixed the issue :good:
Related
This is pretty bizarre.
I have been running CM7 nightly 180 with Trinity for about a month now. I woke up to my phone vibrating a bit - my K9 mail app got reset so it was redownloading old emails. I tried to open my Twitter app and that was reset as well. After that a bunch of force close dialogues popped up, so I rebooted my phone thinking it glitched up. Once I did that, it would show the Google logo, then the first Trinity logo, and just hang there. It did not get to the Trinity animation.
I can get into recovery, and from there I tried to restore to a backup, and it says E:Can't mount /sdcard. Do I have to Odin to fix this or is there another option? I remember the same error happening to my Vibrant, and that was the only solution.
Does anyone have any explanation as to why this happened? I didn't do anything unusual with the phone or install anything new/different at all. I plugged it in, went to bed, and woke up to this.
Strange :S. Did you try to mount SD card from recovery while you have your phone conected to PC? I hope it's not faulty storage memory problem...
Sent from my Nexus S using XDA App
I just tried, CWM says "Error mounting /sdcard!" This all happened with my Vibrant. It said all of the same things and I had to use Odin, and it worked, but my /sdcard was completely wiped. It just doesn't make sense since this time I didn't do anything differently; I think on my Vibrant I had installed a new ROM and then it messed up. This time it's like a phantom f**k up.
That doesn't sound so good . Seen few people with same problem, and most of them sent their devices for repairs. It was some hardware error where Odin couldn't help.
Can't be sure if that is the same problem, but it easily could be. I'm not expert, I'm just sharing what I've seen before. Let's hope I'm wrong about this one...
Ugh I really hope not. I bought this phone on eBay in August, I still owe money to Bill Me Later -_-
Off to Samsung it goes
Sent from my Nexus S 4G using xda premium
Get into recovery mode by turning phone off then hold volume up button then press the power button. It should go to recovery. In recovery go to advanced the mount SD card and mount data. Then try doing a restore
Sent from my Nexus S 4G using xda premium
bille3939 said:
Get into recovery mode by turning phone off then hold volume up button then press the power button. It should go to recovery. In recovery go to advanced the mount SD card and mount data. Then try doing a restore
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
Try to read again what OP wrote in his/her posts...
Have you tried flashing another recovery? Or even, lock and unlock the bootloader? It should format your sd card and that might fix it.
Sent from my Google Nexus S using XDA App
I recall having a similar problem in recovery, I just can't remember what I did to fix it!
Sent from my Google Nexus S using XDA App
You could also try this.
http://forum.xda-developers.com/showpost.php?p=18316565&postcount=29
Try use other version of recovery. It is a bug from I dunno which version of recovery.
Accidentally sent from my Google Nexus S using XDA Premium
I'm on version 5.0.0.0 of CWM, is that the buggy one by chance?
I can't get the USB driver to install here at work (Windows), I am going to have to wait til I get home to flash an updated version of CWM from my Mac.
Flashing a new recovery didn't help. My /sdcard still says error for everything. I wish Odin worked on Macs.
Just used someone's PC to use Odin and my phone hangs at "verify image (ipbl)... success." I think I'm going to throw in the towel and cut my losses at this point. I don't really have any other options.
Amazing but working solution for the same problem!
There is a post in Google mobile support were many people had the same problem and one guy exposes the solution, because I am new user, I can't link outside xda so I tell you the fix:
It's said to be a common hardware problem in this device, for me it just works when I power on after heating up with a hot air gun (other people say a hair dryer is enough)
I hope that you find this information useful
any news?? i have the same problem :'(
Heating Works
Thanks I have the same problem. I was not able to mount any of the system or sdcard partitions. Heated the phone with a heat gun and it starts up.
palpablo said:
There is a post in Google mobile support were many people had the same problem and one guy exposes the solution, because I am new user, I can't link outside xda so I tell you the fix:
It's said to be a common hardware problem in this device, for me it just works when I power on after heating up with a hot air gun (other people say a hair dryer is enough)
I hope that you find this information useful
Click to expand...
Click to collapse
i need some help with my one s ok i was on trickdroid 7.0.0 for U.S user and my wifi waqsnt working so i went back and tried to go back to axiom s and so i put it on the sd card and booted up into recovery and wiped sysem cache and davlik then i installed the axiom rom which went good and then i boot up and it says android is upgrading and that stuff but heres where the problem came about, it got me to the lockscreen but then it say process.acore and process.android.phone have stopped then it keeps popping that up and i dismiss them all but it keeps coming again and again then as i dismiss those it also has one more thing added to it, it says google search has unfortunately stopped so i dismiss that as well but as i keep on dismissing those it keeps popping up then it restarts and starts all over again, it does this before i even get to unlock the phone. please help i currently have it off i dont want to mess it up anymore than what it it i can get into bootloader and recovery but i hvent made a nandroid so im really scared, please help the only rom i have on my sd card is the axiom rom and i even tried to reflash the rom over but the same thing happens it says that then it reboots....please help i dont want to have a bricked phone....... btw in case you need to know some more i was using twrp recovery with hboot on 1.09 but please help:crying:
anybody got anything? im scared andit just scares me big time that it does this, it hardly does this and just wanna figure out how to solve this........feedback woulod be greatly appreciated.
it is not bricked, not even soft brick, don't understand the panic every time, I flash my device about 20 times every day with experimental stuff and nearly 80% cause a bootlop or crashes and sometimes a soft brick..
Just copy new ROM to your sdcard
torxx said:
it is not bricked, not even soft brick, don't understand the panic every time, I flash my device about 20 times every day with experimental stuff and nearly 80% cause a bootlop or crashes and sometimes a soft brick..
Just copy new ROM to your sdcard
Click to expand...
Click to collapse
ok how do i do that thru recovery or thru the phone because when i turn it on it boots up it just pops that up and wont let me do much in the phone with that popping up everytime so thru recovery? right?
leohdz148 said:
ok how do i do that thru recovery or thru the phone because when i turn it on it boots up it just pops that up and wont let me do much in the phone with that popping up everytime so thru recovery? right?
Click to expand...
Click to collapse
edit: i just flashed like 3 different roms and it still gives me the same thing, im gonna try and see if the new trickdroid doesnt do that and see what happens
leohdz148 said:
edit: i just flashed like 3 different roms and it still gives me the same thing, im gonna try and see if the new trickdroid doesnt do that and see what happens
Click to expand...
Click to collapse
another edit: it worked but all im getting is that the process android.process.acore has stopped and it keeps popping up any clues? everything works its just that that keeps popping up on it but i cant find it anywhere? any clues? anyone?
torxx is saying adb push a rom to phone thru command window. Do all the wipes you said you have done. It is good you wipe System also. Maybe try to reformat sd card, all fat32. Back it up first. I had better luck reformatting thru phone than a windows reformat program. Don't know why as sdformatter always worked on Nexus One. Maybe because of the internal card of the 1s as opposed to removable sdcard.
rugmankc said:
torxx is saying adb push a rom to phone thru command window. Do all the wipes you said you have done. It is good you wipe System also. Maybe try to reformat sd card, all fat32. Back it up first. I had better luck reformatting thru phone than a windows reformat program. Don't know why as sdformatter always worked on Nexus One. Maybe because of the internal card of the 1s as opposed to removable sdcard.
Click to expand...
Click to collapse
Oh well I got it fixed, had to factory reset my data and cache and reflash it over my current one and boom, it works again but I appreciate the feedback
Sent from my HTC VLE_U using xda app-developers app
Glad you got it--
Ok so now another problem came up, everything works good, my YouTube app plays videos but it stays stuck loading up then it plays sound for a second or two then it reloads the video and does that repeatedly and it keeps going on till I exit the app, plus the camcorder don't work, the camera app works and takes pics fine but I can't record or playback any videos in my gallery, but when I install a video player it plays the videos I can't really play in my gallery, but when I click on camcorder on the camera app it loads up then it just closes it without warning and it keeps doing that until I restart it and then it works for a little bit then it does it again. Srry to bother you guys with such little things like this but I like my phone fully working plus I like to take pics while I record but it keeps fc'ing so I just want to fix that. Any clues?
Sent from my One S
hi i am having probelm with my camera, everytime i am opening the application it prompt an error which says "camera fail" its not force closing just failure, i think it is not a hardware problem but sumting is missing to make the camera run..plz help me bout htis problem, and one last thing, my phone cant get into download mode everytime i pressing combo mode which is vol down+home+power on button it goes nohing, so my idea it to take the battery out, and when i reinserted the battery it automatically boot itself without pressing the power button..any idea how to fic this problem?
mizukage said:
Nid help bout camera, always closing although i flashdd kpe and kpq, stil error is existing.
Sent from my GT-I9003 using xda app-developers app
Click to expand...
Click to collapse
Try flashing from PIT ..
U can refer the guide from here - http://forum.xda-developers.com/showthread.php?t=1133787
mdaamir1989 said:
Try flashing from PIT ..
U can refer the guide from here - http://forum.xda-developers.com/showthread.php?t=1133787
Click to expand...
Click to collapse
i am currently running on poseidon rom, is it ok if i flash pit file?
EDIT: can any one reupload there camera.apk? please needed it badly, my camera is force closing, how to fix this damn thing,
please help me, just flashed kpe twice and kpq still camera not working.. can any one help me here..?please please
Re: Camera error
how about 3party camera app from playstore did you try??
Sent from my MT25i
Re: Camera error
Yes i already tried camera fr0m playstore and still the error prompted when i opening the said app..
Cant attachd log file of catlog im using mobile.
Sent from my GT-I9003 using xda app-developers app
can any one help me with this problem?
You can use mobile odin to flash the latest stock rom
Sent from my GT-I9300 using xda premium
nikhil18 said:
You can use mobile odin to flash the latest stock rom
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
flashing is not helping to revive my camera to function again, i already tried it several times with different firmware, still error persist..any options?
mizukage said:
so my idea it to take the battery out, and when i reinserted the battery it automatically boot itself without pressing the power button..any idea how to fic this problem?
Click to expand...
Click to collapse
If it boots on battery insert without pressing the power button, it seems like it could be a hardware problem, as in the power button being damaged or stuck. If this is the case, your normal phone operation will also be affected, if not impossible. Maybe this is also the cause of your camera app not working...
so far i only got two problems..1st is upload mode reset when my battery temperature is high and the other problem is the camera which fails after executing.i dont know how to fix the camera issue i already tried copy/paste from other stock rom still it appears..is there any tool to revive it or to check how the camera is failing to execute?
I combined some more things because I didnt want to spam section with thread for every thing
1. Backlight on hardware buttons is "shaky" Im afraid they will die. any idea why is that happening?
2. Everytime I start up my phone between LG silver logo and boot animation there is something like a white noise sometimes its green and red and sometimes when I flash in recovery and reboot it even shows 4 small pictures of recovery next to each other in weird colors. I will take picutre of it l8r.
3. Sometimes Phone just dies while Im using it. Randomly it just goes black and turns off not even a boot animation like i said it dies. On ics roms it happened sometimes now I on jellybam. After flashing pureaudio and pureperformance mod I decided to uninstall pureperf through flashable zip in thread. The installation was aborted I dont have idea why . after trying to uninstall pureperf unsuccesfully it happens often but (im not sure about this) only when listening to music or only when phone isn't charger . I don't know which one is problem.
please help my phone is going crazy and I dont have idea why :/
1. Could be a loose connection inside the phone. Or maybe some software conflict.
2. No idea, but see 3.
3. No idea except maybe you have too many mods and some do not agree.
It is always good to take a Nandroid backup before installing anything in recovery. If you have a backup from before the mods you could restore it and see what happens. Your firmware and bootloader need to be compatible with the ROM you restore (like if you have wkpark bootloader, and you try to restore a backup that had stock bootloader, you will get a security error, if I remember correctly).
drastic00 said:
1. Could be a loose connection inside the phone. Or maybe some software conflict.
2. No idea, but see 3.
3. No idea except maybe you have too many mods and some do not agree.
It is always good to take a Nandroid backup before installing anything in recovery. If you have a backup from before the mods you could restore it and see what happens. Your firmware and bootloader need to be compatible with the ROM you restore (like if you have wkpark bootloader, and you try to restore a backup that had stock bootloader, you will get a security error, if I remember correctly).
Click to expand...
Click to collapse
Im on Jellybam 4.2.2 wkparks bootloader and pureperformance and pureaudio are only mods I flashed and i flashed jb videorecord fix and arc+libs CM10. Do I need any special tools to fix loosr connection? . i found out that phone dies only when on battery so phone just ends signal with battery or other way but I think phone has to do with it because before flashing those two mods that did not happen. And about the startup. Could I jam some chip inside somehow? That weird screen is showing up for a long time it started when VR3D came out. (But I wasnt using vr3d at the time)
Also didn't you have any of these issues? You have supercharger and this mod has it integrated too
Edit: when listening to music it happens too . i turn om music it goes for 5 seconds and phone dies. When i try to reboot phone dies during booting only boots up when I put phone in charger. If phone is in charger music works fine. Pure mods and battery somehow don't work together . I would wipe them but they are so damn good
Sent from my LG-P920 using xda app-developers app
I dont understand how can software f*** up hardware like that. I did wipe flashed xbsalls v28b prerooted through lg flash tool. After that phone still randomly dies and after reboot battery showd 1% of battery left. Help me dude please is it faulty hardware?
Sent from my LG-P920 using xda app-developers app
The software runs the hardware so if there is a software issue, hardware could function incorrectly
It could be hardware since the problem carried over to another ROM. The digitizer should plug into the motherboard by a cable. You could make sure it is seated all the way.
drastic00 said:
The software runs the hardware so if there is a software issue, hardware could function incorrectly
It could be hardware since the problem carried over to another ROM. The digitizer should plug into the motherboard by a cable. You could make sure it is seated all the way.
Click to expand...
Click to collapse
Why digitizer? Digitizer works properly
Sent from my LG-P920 using xda app-developers app
I mean LCD and lights. I'd check that all cables are seated, that nothing is loose and causing the problem(s).
Hello guys I was wondering if anyone can help me with this issue. But first things first the details!
I have kitkat AOSPA 4.0 Beta-6 installed on my xl with thunderzap kernel 4.1 r2 with internal storage fix. I have been running this ROM and kernel on my phone for about 3 to 4 days max.
Now when the issue happened was this morning. The alarm went off my phone and was working fine. I then noticed the battery was at 20% so i decided to switch off the phone and plug it into the mains. I then went out for about 2-3hrs by the time I got back I noticed that the display did not light up with the charging logo when I pressed the power button. I tried to switch it on but nothing happens what so ever.
Things that I have already tried.
-Removed battery for 10mins
-Leave it on charge again for 3hrs
-Tried to enter into flash mode and fastboot.
I have connected the phone to the pc without the battery and the led just lights up green very briefly. My pc detects it as a Qualcomm HS-USB QDLoader 9008 (COM4).
I have run out of ideas and any help you provide will be very appreciated.
HatchetEgg said:
Hello guys I was wondering if anyone can help me with this issue. But first things first the details!
I have kitkat AOSPA 4.0 Beta-6 installed on my xl with thunderzap kernel 4.1 r2 with internal storage fix. I have been running this ROM and kernel on my phone for about 3 to 4 days max.
Now when the issue happened was this morning. The alarm went off my phone and was working fine. I then noticed the battery was at 20% so i decided to switch off the phone and plug it into the mains. I then went out for about 2-3hrs by the time I got back I noticed that the display did not light up with the charging logo when I pressed the power button. I tried to switch it on but nothing happens what so ever.
Things that I have already tried.
-Removed battery for 10mins
-Leave it on charge again for 3hrs
-Tried to enter into flash mode and fastboot.
I have connected the phone to the pc without the battery and the led just lights up green very briefly. My pc detects it as a Qualcomm HS-USB QDLoader 9008 (COM4).
I have run out of ideas and any help you provide will be very appreciated.
Click to expand...
Click to collapse
this happens to me before month (ill send it to RMA and got new motherboard) ive got accidental pc poweroff while flashing
at this moment theres no other way how to revive this state bcz nobody have proper data to program internal mlc via QPST and without this one it means you have dead motherboard, you need to send it to RMA
edit: before you shut off phone you maybe do something wrong, like formating whole internal memory or switching internal to external or something like that ... phone is now in download mode for qpst sw, so it looks like you have no bootloader so phone doesnt know how to boot to os
Flashing_Expert said:
this happens to me before month (ill send it to RMA and got new motherboard) ive got accidental pc poweroff while flashing
at this moment there no other way how to revive this state bcz nobody have proper data to program internal mlc via QPST and without this one it means you have dead motherboard, you need to send it to RMA
Click to expand...
Click to collapse
Thanks for your help. The strange thing is this is my 3rd xperia l because of the same issue it only seems to happen only when flashing another rom other than stock. When I had the same issue they told me there was nothing wrong with it.
I had a Samsung galaxy ace before Major difference in spec I know but I had never had any issues flashing a new rom.
Would they actually repair the phone? as it is rooted and unlocked bootloader?
Propably first ''Sudden Death'' noticed on Xperia L.. That's not funny, Sony.
HatchetEgg said:
Thanks for your help. The strange thing is this is my 3rd xperia l because of the same issue it only seems to happen only when flashing another rom other than stock. When I had the same issue they told me there was nothing wrong with it.
I had a Samsung galaxy ace before Major difference in spec I know but I had never had any issues flashing a new rom.
Would they actually repair the phone? as it is rooted and unlocked bootloader?
Click to expand...
Click to collapse
if mobo is dead they even cant read internal memory, so be calm they probably replace mobo to new one without any asking...
and this is not bcz flashing this is only bcz human factor...
Flashing_Expert said:
if mobo is dead they even cant read internal memory, so be calm they probably replace mobo to new one without any asking...
and this is not bcz flashing this is only bcz human factor...
Click to expand...
Click to collapse
Interesting well it wont be long until I have a new contract anyway. Hopefully I will get a new one. I just wont use a custom rom ever again.
Thanks for your support on this matter.
EDIT: Is there anyway to get the bootloader to work again if thats the reason to why it will not boot.
On the rom that I used for it. It had emulated the internal storage just to get the 4g back.
Try to flash a stock ftf, losing your data (I'm sorry) if you can enter flashmode. Then try to not install the Kernel, possibly the problem is there.
Luck!
Sent from my C2105 using xda app-developers app
HatchetEgg said:
Interesting well it wont be long until I have a new contract anyway. Hopefully I will get a new one. I just wont use a custom rom ever again.
Thanks for your support on this matter.
EDIT: Is there anyway to get the bootloader to work again if thats the reason to why it will not boot.
On the rom that I used for it. It had emulated the internal storage just to get the 4g back.
Click to expand...
Click to collapse
no theres no other way to get internal memory back, its gone, its erased (whole 8gb memory, even partitions or bootloader is erased) or memory chips are broken nothing more or less
theres a sw called QPST from qualcomm for programming internal memory (mainly for right partitions formating inside mmc and basic BL programming) without it theres no other option than get your xl to RMA and mobo change
---------- Post added at 10:19 PM ---------- Previous post was at 10:16 PM ----------
ArnauGonzalez98 said:
Try to flash a stock ftf, losing your data (I'm sorry) if you can enter flashmode. Then try to not install the Kernel, possibly the problem is there.
Luck!
Sent from my C2105 using xda app-developers app
Click to expand...
Click to collapse
OP said that in first comment that his xl is dead without flashmode/fastboot mode, and if it shows in pc after connection qhusb dload driver memory is broken or formated, mobo=dead
kernel surely cant broke your xl, only playing with memory like switch internal/external
Sorry Man, your phone is now at the heavens of mobile phones.
Buy another XL!
Sent from my C2105 using xda app-developers app