My front facing gives me a prompt that "camera is unable to initialize". Should I wait until the droid 4 comes out to call verizon for a replacement? Oh yeah, anybody know the fix. Thanks
are you running a custom rom? have you rooted your phone? have you changed it in any way? is there any noticeable physical damage to your phone? need some details before we can help you
joshpersaud said:
are you running a custom rom?
Click to expand...
Click to collapse
Yes I was running steel droid 4.5, played with cm9 ics a little but it wasnt for me
joshpersaud said:
have you rooted your phone?
Click to expand...
Click to collapse
Yes I needed to root in order to install a custom rom
joshpersaud said:
have you changed it in any way?
Click to expand...
Click to collapse
See the above
joshpersaud said:
is there any noticeable physical damage to your phone?
Click to expand...
Click to collapse
No
Oh yeah and I just flashed back to the stock rom and it still gives me the message, I may go to VZW tomm to get a fresh droid 3 and sell that & my hp touchpad for a Galaxy nexus...still up in the air about it though
oh yeah, save your keystrokes on the obvious advice, i pulled the battery, i went to settings ->applications ->manage applications and cleared the defaults, i wiped data, cache, dalvik and reflashed...i even reflashed to stock, its not working....I tried different camera apps, downloaded the atrix blur camera, nothing
When you say flashed to stock, do you mean fastboot flash? If that doesn't fix it go for the replacment.
Sent from my XT860 using xda premium
Endoroid said:
When you say flashed to stock, do you mean fastboot flash? If that doesn't fix it go for the replacment.
Sent from my XT860 using xda premium
Click to expand...
Click to collapse
Yeah I did fastboot through rsd lite...still nada, I guess ill stop by vzw after work tomm
Update...Vzw replaced my phone
anyone find a fix on this yet?
Best to wipe cache etc plus format the system folder prior to flashing roms in the mounts section of recovery.
-smc
Sent from my DROID3 using xda premium
I have the same issue on my Droid 3. It happened after I rooted but I am running the stock rom. I only rooted to debloat. I even rebloated but the issue is still there. I have seen on many threads where this happens on Droid 3 even with stock roms and no root. The facing camera was always flaky. As it turns out, I really don't miss it. The root/debloat and nearly doubled my battery life. I know, it should not have made that big of a difference but it has.
Im having the same problem, i think its an well known hardware issue from Droid 3, lots of users had experienced failure in front facing camera..
Related
What is happening? Pulled battery 5 times already today...what should I do and would pulling battery as often as this affect my phone or battery?
-------------------------------------
Sent via the XDA Tapatalk App
Anyone?
-------------------------------------
Sent via the XDA Tapatalk App
What sort of set up are you running there?
Stock, non-rooted N1? Or did you upgrade to FroYo over an existing install using Paul's zip? Any applications installed? When is the phone freezing?
Would love to help, but I think we're going to need a little bit more information from you first.
What sort of set up are you running there?
Stock, non-rooted N1? Or did you upgrade to FroYo over an existing install using Paul's zip? Any applications installed? When is the phone freezing?
Would love to help, but I think we're going to need a little bit more information from you first.
Click to expand...
Click to collapse
Previously rooted N1 back to stock rom prior installing froyo from Paul's direct install file for rooted N1 because I lacked stock recovery image.
Basic apps installed like ebuddy news apps etc. didn't install anything different from old install.
Like I mentioned phone stalls in while in sleep mode. Need to pull battery. Cannot soft or hard reset phone.
Ive been reading a lot on xda and didnt notice this occurring in pther phones thats y i decided to open a new thread.
Any help is appreciated thanks!
-------------------------------------
Sent via the XDA Tapatalk App
rensky said:
Previously rooted N1 back to stock rom prior installing froyo from Paul's direct install file for rooted N1 because I lacked stock recovery image.
Basic apps installed like ebuddy news apps etc. didn't install anything different from old install.
Like I mentioned phone stalls in while in sleep mode. Need to pull battery. Cannot soft or hard reset phone.
Ive been reading a lot on xda and didnt notice this occurring in pther phones thats y i decided to open a new thread.
Any help is appreciated thanks!
-------------------------------------
Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
Did you wipe? If not, usually a wipe helps. I wiped and have not had a single issue of FC...Freezing or anything. I went from Enom to Wipe to Paul's Zip with Radio.
I have the same problem. Until now the screen stayed black after the other party ended the call. Had to pull battery 3 times.
Problem exists even after reflashing, wiping and clearing storage.
Im om pre-rooted frf50 from paul. Gonna try with an older radio..
Previously rooted N1 back to stock rom prior installing froyo from Paul's direct install file for rooted N1 because I lacked stock recovery image.
Click to expand...
Click to collapse
Did you wipe? If not, usually a wipe helps. I wiped and have not had a single issue of FC...Freezing or anything. I went from Enom to Wipe to Paul's Zip with Radio.
Click to expand...
Click to collapse
I did wipe prior flashing to Paul's zip with radio.
-------------------------------------
Sent via the XDA Tapatalk App
I have the same problem. Until now the screen stayed black after the other party ended the call. Had to pull battery 3 times.
Problem exists even after reflashing, wiping and clearing storage.
Im om pre-rooted frf50 from paul. Gonna try with an older radio..
Click to expand...
Click to collapse
Can u post whether flashing with an older radio will help and provide link to the older radio? Thanks! Hope it works for you.
-------------------------------------
Sent via the XDA Tapatalk App
rensky said:
Can u post whether flashing with an older radio will help and provide link to the older radio? Thanks! Hope it works for you.
-------------------------------------
Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
I am testing with 4.04.00.03_2
http://forum.xda-developers.com/showpost.php?p=6026480&postcount=3
SurfHost said:
I am testing with 4.04.00.03_2
http://forum.xda-developers.com/showpost.php?p=6026480&postcount=3
Click to expand...
Click to collapse
does it work?
Im having similar issues with my 2.2 installation. I have it installed on my wife's non-rooted N1.
Not just that but the market is not even usable. Even if I clear cache.
Again, her phone is not rooted, I wipped everything from her phone then applied Froyo and its been a nightmare. Her phone isn't even stable enough to use and I cant seem to figure it out.
I need to find a way back to 2.1 without having to root her phone. She is adamant about me not doing that to her phone even though Ive rooted all the phones I've ever used with no issues.
I was having the same problem on my N1. Started suddenly two days after the manual upgrade to 2.2. The phone would either freeze to a black screen or sometimes the live wallpaper would continue but the phone was unresponsive even to the power button. Needed to pull the battery to restart.
It stopped after I:
* Turned off live wallpaper
* Uninstalled LauncherPro Beta
* Removed the Pure Calender Widget (was broken after 2.2 update anyway)
* Charged the battery (was down to below 10% when it started happening repeatedly).
Anyone one of them (or none of them) could have been the culprit. My guess it was one of the last two (PureCalender or battery) but haven't had time to troubleshoot it. Try some of these and see if it helps.
Ive tried all that on her phone. I just wiped it again completely and re flashed just in case that was the issue. Phone still had all the issues described in this thread.
I wiped the sd card, wiped all previous system files via the stock recovery and re flashed the update zip. You cant get anymore clean than that and its still so unstable the phone its unusable. I have to either hope soft booting works or pull the battery as a last ditch.
Is there any way I could downgrade her phone to 2.1 without rooting? I tried the shipping rom in the sticky above but it seems that isn't totally legit for stock use because the phone doesn't like how its signed.
I guess I could call google/htc tomorrow but who knows where that'll get me. The only bonus iud that her phone is not rooted so she didn't really have her warranty voided.
-------------------------------------
Sent via the XDA Tapatalk App
I was having the same problem on my N1. Started suddenly two days after the manual upgrade to 2.2. The phone would either freeze to a black screen or sometimes the live wallpaper would continue but the phone was unresponsive even to the power button. Needed to pull the battery to restart.
It stopped after I:
* Turned off live wallpaper
* Uninstalled LauncherPro Beta
* Removed the Pure Calender Widget (was broken after 2.2 update anyway)
* Charged the battery (was down to below 10% when it started happening repeatedly).
Anyone one of them (or none of them) could have been the culprit. My guess it was one of the last two (PureCalender or battery) but haven't had time to troubleshoot it. Try some of these and see if it helps.
Click to expand...
Click to collapse
I was worried if I was the only one with this problem. Phone improved today (3rd day of using) but I didn't do anything to it. Only hanged once when someone called. Hanged on calling in screen and had to pull battery.
Only once compared to 7 times yesterday!
-------------------------------------
Sent via the XDA Tapatalk App
rensky said:
does it work?
Click to expand...
Click to collapse
Yes until now it does. Sometimes the power button is reacting a little late but i havent had to pull the battery yet with the older radio.
You might want to download it again and flash that to see if you had a corrupt download. First copy all data from the sd and partition it. Just make everything fat. I havent used the stock recovery in ages so I cant recall if you can partition from there, if you cant, do it on the pc. Wipe everything that the stock recovery can wipe. Then try to flash your new download of the update. You can do this fairly quickly and its worth a try before you go through the process of reverting to 2.1.
krabman said:
You might want to download it again and flash that to see if you had a corrupt download. First copy all data from the sd and partition it. Just make everything fat. I havent used the stock recovery in ages so I cant recall if you can partition from there, if you cant, do it on the pc. Wipe everything that the stock recovery can wipe. Then try to flash your new download of the update. You can do this fairly quickly and its worth a try before you go through the process of reverting to 2.1.
Click to expand...
Click to collapse
I'll give this a shot when I get home from work. I'll report back on if it works or not. Thanks for the idea.
Interesting, not that I'm complaining, but after a few days of using 2.2 it seems more stable now....? haven't had any freezes today...yet.
Power button response also getting better.
-------------------------------------
Sent via the XDA Tapatalk App
I haven't had any issues for a few days as well. Still wondering if it had to do with the battery level.
-------------------------------------
Sent via the XDA Tapatalk App
SurfHost said:
I have the same problem. Until now the screen stayed black after the other party ended the call. Had to pull battery 3 times.
Problem exists even after reflashing, wiping and clearing storage.
Im om pre-rooted frf50 from paul. Gonna try with an older radio..
Click to expand...
Click to collapse
Older radios are not 100% compatible.
For unknown reasons, the SBF recovery in RSD lite 5.5 comes up with a "pass" result when the SBF itself actually fails. It runs like it worked, but on the final reboot, I get an endless bootloop.
Backstory:
I made a rom, flashed it, bootloop, go to SBF, SBF passes but bootloops.
*ps i've tried it 4 additional times and each time still bootloops even though it says "pass"
I've done this at least 4 times in the past 3 days trying to get my rom to flash. What the FUUUUUUUUUU*K is it doing this for now?
Wipe data/cache after you SBF.
Sent from my DROID3 using xda premium
kshen1 said:
Wipe data/cache after you SBF.
Sent from my DROID3 using xda premium
Click to expand...
Click to collapse
I can't get into anything.
The SBF bootloops.
did you try a battery pull and booting into recovery
shane1 said:
did you try a battery pull and booting into recovery
Click to expand...
Click to collapse
battery pull over 20 times at least.
no more cwm, i sbf'd. everything is stock. 100% stock. but bootlooping.
Try to flash the chinese rom, see if it boot then flash back the verizon rom.
The Solutor said:
Try to flash the chinese rom, see if it boot then flash back the verizon rom.
Click to expand...
Click to collapse
What the f...No don't do this.
Did you download the correct SBF for your system version? I know there are both 959 and 890 SBFs out there.
Sent from my DROID3 using xda premium
You wont have CWM after doing the SBF but you can still boot into the stock moto recovery and wipe data/cache
kshen1 said:
What the f...No don't do this.
Click to expand...
Click to collapse
And why
The Solutor said:
And why
Click to expand...
Click to collapse
Different phone, different everything.
lordgodgeneral said:
You wont have CWM after doing the SBF but you can still boot into the stock moto recovery and wipe data/cache
Click to expand...
Click to collapse
I can still do that? I'll try that and give it a go when I get back home. I thought the stock recovery had no options though....
kshen1;18233443 said:
Did you download the correct SBF for your system version? I know there are both 959 and 890 SBFs out there.
Sent from my DROID3 using xda premium
Click to expand...
Click to collapse
Yep, been using the same one the whole time, 890.
Sent from my dad's DROIDX using XDA App
dpwhitty11 said:
Different phone, different /system.
Click to expand...
Click to collapse
And then ?
I suggested this way purposely, because the different organization will lead to a wiped phone.
The Solutor said:
And then ?
I suggested this way purposely, because the different organization will lead to a wiped phone.
Click to expand...
Click to collapse
Its a different model phone. It would be a brick, not a bootloop, if I did that.
Sent from my DROIDX using XDA App
The Solutor said:
And then ?
I suggested this way purposely, because the different organization will lead to a wiped phone.
Click to expand...
Click to collapse
Lmao...
Dpwhitty go into stock recovery after sbf and wipe data.
Sent from my DROID3 using xda premium
kshen1 said:
Lmao...
Dpwhitty go into stock recovery after sbf and wipe data.
Sent from my DROID3 using xda premium
Click to expand...
Click to collapse
lol, that guy....
Kshen, I left my phone at home, i'll do that when I get back.
Sent from my DROIDX using XDA App
I go into recovery and I get the little android guy and that white triangle with the orange exclamation mark inside it. No options or menus in there.
dpwhitty11 said:
Its a different model phone. It would be a brick, not a bootloop, if I did that.
Click to expand...
Click to collapse
Is better to open the mouth having something useful to say, and not to spread urban legends.
(for the record I have the chinese rom installed on my phone, which is a verizon phone.)
Is a way better rom in many areas, but my purpose was not to suggest a different rom, but to solve a problem, with a safe solution, as I'm used to do in the last 30 years.
dpwhitty11 said:
I go into recovery and I get the little android guy and that white triangle with the orange exclamation mark inside it. No options or menus in there.
Click to expand...
Click to collapse
Press in both volume keys. That'll bring up some options. You'll see factory reset/wipe data there
Sent from my DROID3 using XDA App
erismaster said:
Press in both volume keys. That'll bring up some options. You'll see factory reset/wipe data there
Sent from my DROID3 using XDA App
Click to expand...
Click to collapse
That worked.
Thank you so much guys, thought I was a goner for a while.
The Solutor said:
Is better to open the mouth having something useful to say, and not to spread urban legends.
(for the record I have the chinese rom installed on my phone, which is a verizon phone.)
Is a way better rom in many areas, but my purpose was not to suggest a different rom, but to solve a problem, with a safe solution, as I'm used to do in the last 30 years.
Click to expand...
Click to collapse
Ok
Sent from my DROID3 using xda premium
dpwhitty11 said:
That worked.
Thank you so much guys, thought I was a goner for a while.
Click to expand...
Click to collapse
Yeah NP haha I knew wiping data would solve the issue
Sent from my DROID3 using xda premium
Hey guys, i have a motorolla droid 3. xt862. I am running cyanogen mod 7 and it is rooted. i flashed the Blur_Version.5.6.890.XT862.Verizon.en.US file using stock recovery and now the droid 3 bootstrap is gone and wifi wont work. im stuck with cm7 which doesnt work. I would just like to go back to the way it was when i got it stock rom and everything. I have no interest in custom roms because absolutely nothing works and it is all very buggy. Please i need help urgently! i hope im not stuck
watermummy7 said:
Hey guys, i have a motorolla droid 3. xt862. I am running cyanogen mod 7 and it is rooted. i flashed the Blur_Version.5.6.890.XT862.Verizon.en.US file using stock recovery and now the droid 3 bootstrap is gone and wifi wont work. im stuck with cm7 which doesnt work. I would just like to go back to the way it was when i got it stock rom and everything. I have no interest in custom roms because absolutely nothing works and it is all very buggy. Please i need help urgently! i hope im not stuck
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1255198
Flash the correct SBF and you'll be set; back to normal
Thanks! ill give it a shot and let ya know!
Cameron6472 said:
http://forum.xda-developers.com/showthread.php?t=1255198
Flash the correct SBF and you'll be set; back to normal
Click to expand...
Click to collapse
The link i s broken and i haver under 10 posts so im unable to post on that forum to let him know this..
I found the same file somewhere else but when i apply pdate from sd card with the file it just gets stuck at that and nothing happens. It goes back to the recovery symbol with an arrow and thats it
watermummy7 said:
I found the same file somewhere else but when i apply pdate from sd card with the file it just gets stuck at that and nothing happens. It goes back to the recovery symbol with an arrow and thats it
Click to expand...
Click to collapse
Try with this instead
Trythe trhread in my signature.. has saved me maaaanytimes ans is in multiupload
Enviado desde mi XT862 usando Tapatalk
watermummy7 said:
I found the same file somewhere else but when i apply pdate from sd card with the file it just gets stuck at that and nothing happens. It goes back to the recovery symbol with an arrow and thats it
Click to expand...
Click to collapse
Apply update from SD card? You must be doing the wrong process. The SBF file is flashed on your phone in conjunction with the RSD lite Windows application
Cameron6472 said:
Apply update from SD card? You must be doing the wrong process. The SBF file is flashed on your phone in conjunction with the RSD lite Windows application
Click to expand...
Click to collapse
Yes thankyou, im still a learning noob lol. I successfully am back to gingerbread 2.3.4 for droid 3. Re-rooted got adw launcher and everythings works including the camera! That's the main reason I wont flash any custom roms even stable ones because camera just simply doesn't work. Thanks for everyones help on this forum! Id like to know some really cool mods and hacks I can do to this thing
watermummy7 said:
Re-rooted got adw launcher and everythings works including the camera!
Click to expand...
Click to collapse
Why did you need to root to install adw? or you just rooting to remove bloat?
watermummy7 said:
That's the main reason I wont flash any custom roms even stable ones because camera just simply doesn't work.
Click to expand...
Click to collapse
Hashcode's ICS rom has [mostly] working camera
Rooting mainly to remove bloatware and ads from applications. Also to overclock cpu thats about it. I had to use an sbf file because I was stuck in cm7 with no recovery and the wifi didn't work.
Sent from my DROID3 using XDA App
Cameron6472 said:
Hashcode's ICS rom has [mostly] working camera
Click to expand...
Click to collapse
Yeah I've tried the ics and it was really nice! Id just rather wait for a more stable release. Only problem I had with cm9 is some applications wouldn't open in fullscreen, it was weird..
Sent from my DROID3 using XDA App
do your wifi can turn on again?
zeigk said:
do your wifi can turn on again?
Click to expand...
Click to collapse
Yes, everythings working perfectly again
Sent from my DROID3 using XDA App
While I'm thinking about it, I wanted to ask a question. I had to revert back to the stock ROM, and went to re-add root and Safestrap 2.10. All went well with the install, but when I went to enable the Safe System, and I rebooted, the phone did the POST (Motorola symbol), got to the SafeStrap splash, then the screen went blank. None of the keys would do anything, and the only way I could make anything happen, was to pull the battery. I had to go back into Safestrap, and disable it again. Anyone else experience this?
-Roger
cpnbnanamn said:
While I'm thinking about it, I wanted to ask a question. I had to revert back to the stock ROM, and went to re-add root and Safestrap 2.10. All went well with the install, but when I went to enable the Safe System, and I rebooted, the phone did the POST (Motorola symbol), got to the SafeStrap splash, then the screen went blank. None of the keys would do anything, and the only way I could make anything happen, was to pull the battery. I had to go back into Safestrap, and disable it again. Anyone else experience this?
-Roger
Click to expand...
Click to collapse
Did you flash something in safe mode before rebooting?
Sent from my XT860 using xda premium
Endoroid said:
Did you flash something in safe mode before rebooting?
Sent from my XT860 using xda premium
Click to expand...
Click to collapse
No, just enabled it, allowed it to do it's backup, then rebooted. Thought for sure I was going to have to reload SBF again.
-Roger
cpnbnanamn said:
No, just enabled it, allowed it to do it's backup, then rebooted. Thought for sure I was going to have to reload SBF again.
-Roger
Click to expand...
Click to collapse
The first time you enable safe mode you need to flash a rom. You tried to boot... Nothing, thus the black screen
Sent from my XT860 using xda premium
Endoroid said:
The first time you enable safe mode you need to flash a rom. You tried to boot... Nothing, thus the black screen
Sent from my XT860 using xda premium
Click to expand...
Click to collapse
Ahh.. that makes sense. Do we have any idea when a more stable ROM is coming out for the D3?
cpnbnanamn said:
Ahh.. that makes sense. Do we have any idea when a more stable ROM is coming out for the D3?
Click to expand...
Click to collapse
All gb roms are stable. It's just ics that has issues, however the kexec cm9 currently in alpha will be stable, likely in the next few weeks
Sent from my XT860 using xda premium
Endoroid said:
All gb roms are stable. It's just ics that has issues, however the kexec cm9 currently in alpha will be stable, likely in the next few weeks
Sent from my XT860 using xda premium
Click to expand...
Click to collapse
The kexec ICS from 8/6 is surprising stable for me. I've been running it for nearly a week and while I've had some reboots and a couple of freezes that required a battery pull, it's run better than I expected.
I have had the problem with leaving bluetooth on and answering a call without a headset - no audio until BT turned off.
Also, as advertised, no camera. Another note, the car dock USB audio doesn't work.
I've even scripted a mount to keep the Play Music directory on the external SD card and mass storage mount on the computer works better than stock with the mount in place. Internal sd doesn't mount though.
Sent from my XT862 using Tapatalk 2
Hey guys, I was running Maximum overdrive v1.0 and beastmode 56.8 kernel (no tweaks) when my phone starts freezing and rebooting. It would happen often and even at times It wouldn't boot completely I would have to remove the battery for It to boot. Then It started to get "kernel panic ulpoad mode" I odin flashed back to stock MM but same issues going on. Any ideas? Or its time for a new phone? Thank you
Sent from my SM-N910T using Tapatalk
carmona_sc said:
Hey guys, I was running Maximum overdrive v1.0 and beastmode 56.8 kernel (no tweaks) when my phone starts freezing and rebooting. It would happen often and even at times It wouldn't boot completely I would have to remove the battery for It to boot. Then It started to get "kernel panic ulpoad mode" I odin flashed back to stock MM but same issues going on. Any ideas? Or its time for a new phone? Thank you
Sent from my SM-N910T using Tapatalk
Click to expand...
Click to collapse
I was curious cause I never heard of that , and some people said a factory reset solved the problem . However a fresh Odin install is good. Did you wipe system as well as the normal wipes?
Bubba Fett said:
I was curious cause I never heard of that , and some people said a factory reset solved the problem . However a fresh Odin install is good. Did you wipe system as well as the normal wipes?
Click to expand...
Click to collapse
Yes I did, and nothing seemed to work, even went back to stock 5.1 and same issues consist.
Sent from my SM-N910T using Tapatalk
carmona_sc said:
Yes I did, and nothing seemed to work, even went back to stock 5.1 and same issues consist.
Sent from my SM-N910T using Tapatalk
Click to expand...
Click to collapse
Yikes. I didn't even see a ton of info on the subject. I can't imagine there is anything left on the device to cause any issues. Hopefully someone with more knowledge about this sees this post. Note 7 release party Aug 2nd if it comes to that!
same issue i see alot of people with it, its the emmc i confirmed it beause yesterday while i was alseep my emmc decided to give up on life no recovery no download failed to read emmc, the problem is repairing it im not gonna take it to samsung as they will charge almost the price of a new phone i have found a chip for it but it says it has sm n910p/f firmware on it not sure if it would be an issue as i could reflash the tmobile firmware on it.
http://www.aliexpress.com/item/Bran...2630152207.html?spm=2114.40010708.4.13.nPWCQ2
any advice on the chip?
So, what was the final solution?