I need some professional debugging help. I haven't been able to find a solution to my issue and I have been searching and trying different things for weeks. My wife received an ATT&T Captivate second hand. Everything seemed to work fine for a couple of weeks. Installed Pudding Camera and camera started having issued. Uninstalled, but issues remained. Eventually camera stopped working. I have rooted other phones, so I took this as an opportunity to start fresh. Have installed multiple ROMs and done multiple Roots and Unroots trying to figure out the problem. I even replaced the camera, but cannot catch a break on this one.
From the logs it seems the camera is already busy. I have tried every camera patch I could find, along with the ROMs with which they are supposed to work. I am at my wits end and could really use some help/perspective/ideas.
Here are the steps I have done multiple times and in almost every order I can image.
Flashed factory Eclair using Odin-
Flashed factory Froyo using Odin-
Flashed factory GB using Odin-
Flashed factory JB using Odin-
Flashed CM10 using CWM Recovery
Flashed Captivating using CWM Recovery
Flashed Xperia (sp) using CWM Recovery
Have used various kernels, Semaphore, Devil, etc
Have used various gapps required for each version
Have wiped Dalvik, factory reset/wipe cache, fixed permissions in every order I can imagine
Have rebooted in between installs and reinstalled ROMs
I really love the challenge of figuring this stuff out, but I just don't have the knowledge to move forward. I am beaten.
Suggestions?
Related
i have had my ATT N1 for a few months now and all has been great. I rooted awhile back and have been using Cyanogen 5.0.7 to great success. I have the pershoot kernal and never really had any issues.
Well, that has all changed. Recently I have been rebooting any many different occasions. It almost always does it when I am in Maps and navigation, which is not good because I need it in my life having relocated.
I have decided that maybe I will look to update my Cyanogen or maybe go over to 2.2. I did this today and still having these issues. I tried Kang and it still rebooted randomly and when I tried Modacos r17 it just would keep rebooting at the setup screen. I think that has to do with not having the stock kernal.
Any clues as to what is happening? I really need help and do not want to stop using Android, but I need my phone to be reliable.
If it happens on any ROM and with no correlation to anything - sounds like HW problem.
Did you use overclocked kernel?
I do have a overclocked under volted kernal
sounds like bad sw. get back to stock 2.1 update 1 (if you can) and see if your phone is stable...
WIPE all ( everything ) , and flash 2.2
http://forum.xda-developers.com/showthread.php?t=692609
Follow those 3 easy steps there !
Does your phone lock up (unresponsive) before rebooting?
Phone doesnt lock up. I tried wiping evertyhing but could not wipe the sd partition. Is that necessary? I have done full wipe's (data, dalvik, & cache) and still had similar results. I have updated my kernal to the newest pershoot and I installed Kang .9b1 and so far have only had 1 rebbot. It happened when I was in the browser and went to a flash heavy site to see how it worked. Is there any 2.2 roms that keep it close to stock? I am not a total fan of adw launcher.
Have a look in this thread,
http://forum.xda-developers.com/showthread.php?t=703687
I'm really determined to figure out what is causing this issue for so many people! I've managed to cure my reboots for the time being, and it seems it is kernel related. That said, we need as many people as possible to give feedback as experiences seem to differ in regards to the ROMs and Kernels people are using.
Regards.
I looked over that thread and see some similarities but it is still not totally consistent with my issues. I am running Kang now fine but still have reboots that I won't call so random anymore. It happens when I use Maps for the first time, and definitely when I go to a flash site on the browser.
I cannot successfully use any other ROM since once I install it it goes into boot loop. This is driving me crazy and do not like the thought of being stuck to one ROM since it is the complete reason I bought this phone.
I'm posting here because I don't know what else to do, my phone freezes using any froyo rom. It happens randomly and sometimes will not happen until I reboot the phone, but it makes my phone pretty much unusable. I've tried the leaked froyo rom, BB, CM 6 1&2 and countless others. I've tried wiping data / cache and formating the SD card (worked until i put my music back on), and I'm about to just try stock 2.2 and exchange it for a new one if it wont work.
Anyone else have this problem that could help me?
One thing I didn't see you do...
Have you at all root your phone to install the desired froyo rom for your phone?
Yes I am rooted, I'm currently on CM 5.0.8 and very happy but I would really like to get froyo working.
Alright. This is what I've done to get Froyo working on my Droid: I rooted my phone, downloaded BB v4 and changed the name of the file to update, installed Rom Manager on my phone(then found out I can download the roms from here as well), reboot into recovery through rom manager, wiped data & cache, selected install zip, then selected reboot phone. It took a bit to register but it converted over with BB v4.
I think I've found my problem
droidforums.net/forum/tech-issues-bug-reports-suggestions/67526-music-sd-card-causes-bb-4-freeze.html
this sounds like my exact problem, I'm going to look through my library and see if there is a corrupt file then try again
Hopefully that is the source of the issue and that'll be solved quickly. Good luck to ya
I've flashed and flashed and flashed both ICS and GB roms on my bionic and I've yet to find one that works. I've had more luck with ICS roms than GB, but still I get roms that the dialer is bugged and you can't hear anyone or anything when using it. My data drops every 2 seconds on both ICS and GB roms.
I've tried Eclipse roms, everything worked fine, but I couldn't hear no one on the phone unless they called me first. So I had to get rid of that one for that reason.
I've tried every ICS rom out there, gummy works the best for me, but I get data drops every 2 seconds, bluetooth (which I use all the time) works, but if you forget to leave it on you can't hear nothing on calls. And for some reason it's started doing the same as Eclipse rom is doing, I can't hear no one on the phone not even if they call me and bluetooth is not on.
I've then tried Liberty rom, and I couldn't get data working period, the phone wouldn't work either.
Did I just get a crappy phone that just doesn't like to be flashed so many times or what?
Are you wiping data, cache & dalvik when you switch ROMs? Not doing wipes is the biggest cause of ROM malfunctions. Some ROMs just don't like it when you don't wipe. ROMs are built under the impression that they're starting out with a blank /data partition.
I ran Eclipse 2.2 for a while and everything on it worked without issue. However, Ice Cream Sandwich ROMs are a problem and will continue to be a problem for everyone. To me, it's a miracle that ICS ROMs even boot up on the Bionic. The locked bootloader means that the kernel cannot be modified except by official Motorola updates. This means that all these ICS builds are running on a Gingerbread kernel.
Yea, I'm wiping everything on each flash.
When I flashed the Eclipse rom, I wiped data, cache, dalvik and everything was fine except the call issue where I couldn't hear anything but people could call me and it'd be fine.
I've had better luck with the ICS roms than the GB roms though for some reason, minus the bluetooth/data issues.
What are you using to Flash, Bootstrap or SafeStrap? I know Eclipse has been giving me minor issues, but all and all it still works. Forget about trying Liberty or even anything else unless the Dev. modifies them to work with the 902 radios. There have been some people trying out the new radio leaks such as 904 and 905, but if they ever issue a true OTA you have to FXZ back to the 902 in order to apply the update. To touch up on some other stuff you can do also is format the internal storage. There could be something in there causing those issues to happen. Before I flash a new 902 compatible rom I go and backup everything important onto my external storage using ES file explore and then format the internal using the storage settings in the system settings.
I do the wipe data/factory reset, not sure if that gets the internal storage or not. Followed by the wipe cache, wipe dalvik.
I was using Safestrap, but FXZ'd back to stock and started using Bootstrap. Right now I'm sitting on the stock rom with bloatware frozen.
Hey all,
I installed CM10 Helly Bean (DerTeufel) port for Captivate V10 with full wipe.
It seemed to be working fine... fooled around a bit, tried out Google Now, etc.
Was restoring apps (not data) w/ Titanium Backup.. forget if it had finished or not...
Didn't try to run any of these programs or anything, just tried to unlock and the touchscreen was not responsive... Tried wiping cache+dalvik + fixing permissions... tried reinstalling ROM and GAPPS...
All are in a non-responsive bootloop.
I'm starting over now with another factory wipe... as of now it is stuck on "Welcome" Screen and touchscreen is not responding... AND.. it just restarted
Any ideas as to the problem... Was it Titanium Backup related? Should I resist running that again (assuming this ever works)?
I would post this on Development thread but I still don't have my 10 posts, heh, mostly a long-time lurker...
Thanks!
Worse than I thought!
So It's worse than I thought... I gave up and re-flashed slim (ICS)... and the same problem still exists... boots up, looks normal, can't touch anything.... eventually it reboots....
Suggestions?
Would ODIN flash do anything different? I9000 bootloaders?
ScruffMcG said:
Hey all,
I installed CM10 Helly Bean (DerTeufel) port for Captivate V10 with full wipe.
It seemed to be working fine... fooled around a bit, tried out Google Now, etc.
Was restoring apps (not data) w/ Titanium Backup.. forget if it had finished or not...
Didn't try to run any of these programs or anything, just tried to unlock and the touchscreen was not responsive... Tried wiping cache+dalvik + fixing permissions... tried reinstalling ROM and GAPPS...
All are in a non-responsive bootloop.
I'm starting over now with another factory wipe... as of now it is stuck on "Welcome" Screen and touchscreen is not responding... AND.. it just restarted
Any ideas as to the problem... Was it Titanium Backup related? Should I resist running that again (assuming this ever works)?
I would post this on Development thread but I still don't have my 10 posts, heh, mostly a long-time lurker...
Thanks!
Click to expand...
Click to collapse
sorry I'm just going to post twice so I can post to development...
yeah... 10char
What I can suggest is, go back to GB. Download a one click Odin w/ bootloaders, you can search that in the dev forum. After that flash it with a corn kernel so you can have a working CWM. And then Go to recovery, have a full wipe (data,cache,dalvik) TWICE and flash this--
Slimmed Down V10 by cbalt
Wipe Data/Factory Reset/Wipe Dalvik
Flash http://www.mediafire.com/?9p212pempybwnj3
Then Flash http://www.mediafire.com/download.php?bdjabcmobz6aw6k
Then Fix Permissions
Then Reboot
Click to expand...
Click to collapse
I can recommend you that one because it's the one the I'm currently using right now and I can say that it's working like a charm.
The method above is the one I'm using everytime I flash a ROM. I always do a full wipe so I won't be encountering any issues or whatsoever.
About TiBu, I am not sure if that's where the issue coming from because I've been using TiBu for a long time and haven't encountered that. Just always remember, if you are using backup using TiBu, just backup the User Apps+Data, DO NOT INCLUDE THE SYSTEM APP. Goodluck!
So you think w/bootloaders will help?
I have flashed every odin w/o bootloaders that I have access too and all get me stuck at ATT bootscreen....
Little hesitant to reflash my bootloaders since I was/am already on GB bootloaders, but if it might help I may have to do it...
I actually was on that JB version (but with the normal gapps b/c I wanted google now...)... now I'm on no version of anything hahah
takeoutttt said:
What I can suggest is, go back to GB. Download a one click Odin w/ bootloaders, you can search that in the dev forum. After that flash it with a corn kernel so you can have a working CWM. And then Go to recovery, have a full wipe (data,cache,dalvik) TWICE and flash this--
I can recommend you that one because it's the one the I'm currently using right now and I can say that it's working like a charm.
The method above is the one I'm using everytime I flash a ROM. I always do a full wipe so I won't be encountering any issues or whatsoever.
About TiBu, I am not sure if that's where the issue coming from because I've been using TiBu for a long time and haven't encountered that. Just always remember, if you are using backup using TiBu, just backup the User Apps+Data, DO NOT INCLUDE THE SYSTEM APP. Goodluck!
Click to expand...
Click to collapse
I met a problem. I do not know wether or not it is common. The phone will reboot by itself sometimes.
Do you have the same problem?
same here
seems as though many of the problems experienced by one are shared by the other
this is logical as they share many common points including the same partition and both jellybean derivations
I was having issues... accelerometer and audio issues.
All came out right as rain after flashing back to stock and reflashing
ScruffMcG said:
yeah... 10char
Click to expand...
Click to collapse
Hi folks,
Way back when, when I first got the RAZR i, I installed omar's ROM. Very pleased with the way it ran. However now, some 6 months later, I cannot install his updated ROM (RazRi_JB_X-M8-NoBT2). And it has me baffled! I do a factory wipe, reformatted: data, cache, dalvik and system and install via CWM. And it bootloops consistently. I have to install stock ROM via RSD-lite, then re-root etc. And tried again several times, same result. JellyAOSP does the same (based on Omar's ROM AFAIK), but Pi=Llama's ROM installs...but can' be used as something is screwy with the WiFi with this ROM for me.
Can some kind soul tell me what I may have overlooked, as I am certain I follow the correct procedure as I did ages ago, but I am screwing up somewhere!
I know I should post this under Omar's thread....but I don't have enough posts to use it.
Thanks in advance
Coxie