Database Develop

[Q] Captivate flashing/stock rom issues - ideas?

Hey all,
First let me say that I did read the FAQ and followed the instructions for flashing my Captivate.
I like the TouchWiz type interface, so I tried the stock roms suggested in post 6 (I9000XWJM6 for Europe and I9000UGJH2 for Australia/Americas).
When I flashed the I9000XWJM6, it flashed successfully. However, when it rebooted and tried to apply the customizations for AT&T, it errored out. It stayed in the recovery console and wouldn't let me select any options.
So I flashed back to AT&T stock ROM, and that worked ok. I then tried the I9000UGJH2 rom. While that was successful, I get accelerometer issues. Anytime I go to a menu, say like Contacts, it rotates 90 degrees like I rotated counterlclockwise, even though I'm holding it vertical. If I rotate it clockwise so I'm holding it in a landscape orientation, it goes back to portrait like I was holding it vertical. Going into sound and display settings, it behaves if I uncheck the orientation box.
I really don't want the AT&T crap on this phone. I'd greatly appreciate any help and suggestions, even a rom (Samsung stock or cooked) that would suit my prefence.
I come from the Windows Mobile world with HTC phones and used cooked roms before, so I'm comfortable with the concept. However, I am a Droid noob.
Thanks in advance!
Super

I would love to find an easy place to find a list of working or experimental roms for the captivate.seems to be overlooked by the devs
Sent from my SAMSUNG-SGH-I897 using XDA App

Seems there are some slight differences. Maybe some more love will come with the Vibrant being out on T-Mo now. Guess there are enough hardware differences that it doesn't quite work right with the stock/modded roms.

Superguy said:
Hey all,
First let me say that I did read the FAQ and followed the instructions for flashing my Captivate.
I like the TouchWiz type interface, so I tried the stock roms suggested in post 6 (I9000XWJM6 for Europe and I9000UGJH2 for Australia/Americas).
When I flashed the I9000XWJM6, it flashed successfully. However, when it rebooted and tried to apply the customizations for AT&T, it errored out. It stayed in the recovery console and wouldn't let me select any options.
So I flashed back to AT&T stock ROM, and that worked ok. I then tried the I9000UGJH2 rom. While that was successful, I get accelerometer issues. Anytime I go to a menu, say like Contacts, it rotates 90 degrees like I rotated counterlclockwise, even though I'm holding it vertical. If I rotate it clockwise so I'm holding it in a landscape orientation, it goes back to portrait like I was holding it vertical. Going into sound and display settings, it behaves if I uncheck the orientation box.
I really don't want the AT&T crap on this phone. I'd greatly appreciate any help and suggestions, even a rom (Samsung stock or cooked) that would suit my prefence.
I come from the Windows Mobile world with HTC phones and used cooked roms before, so I'm comfortable with the concept. However, I am a Droid noob.
Thanks in advance!
Super
Click to expand...
Click to collapse
I assume you have a Captivate and you want to run European ROMs. There is a full guide over in the CAPTIVATE forum (I would know, I too have a Captivate). When flashing an international ROM, you don't use anything designed for the Captivate after that (except returning to stock). Root would be i9000 root methods. Also, if you're running a 2.1 ROM, you need to flash the captivate kernel to fix things like accelerometer issues. (all of this is in the sticky in the captivate forum)
Lessonz101 said:
I would love to find an easy place to find a list of working or experimental roms for the captivate.seems to be overlooked by the devs
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
it's not overlooked, you're just not in the captivate forum

Thanks. I must have missed it - found the forum on Google and I'm reading thru that thread now.

[FIX][08.04.2011]Patch for "Screen won't come on after device wakes" (RHO_S2_00895)

[FIX][08.04.2011]Patch for "Screen won't come on after device wakes" (RHO_S2_00895)
Problem: Device doesn't come back from suspended mode. Pressing the power button, sliding out the keyboard or taking out the stylus does nothing.
Occurrence: Random.
Quick fix: None known.
Request: Kinda all over the Rhod forums.
Affected ROMs: HTC Stock S2 2.07, all custom roms based on 2.07 drivers. Probably 2.10 drivers are partly affected too.
Patch:
For stock roms (standard HTC patch package, .exe)
For custom roms (download this if you're unsure, works for stock roms too)
For cooks (extract and put into OEMDrivers)

Thanks!
Let's see (in time) if the SOD's are finished for us.

HRQ.SLV said:
Thanks!
Let's see (in time) if the SOD's are finished for us.
Click to expand...
Click to collapse
It must be a matter of settings or hardware, I never suffered from SoD.

Jackos said:
It must be a matter of settings or hardware, I never suffered from SoD.
Click to expand...
Click to collapse
That's because youre a great cook!
This thread should be sticky...

HRQ.SLV said:
That's because youre a great cook!
This thread should be sticky...
Click to expand...
Click to collapse
Not only this one should be sticky...

.......Done

Installed. Didn't work . I think the flex cable is crapping out. Also had the problem where if the screen was fully slid, it'd black out. Now it's been like that every postion.
Although, the power button works to turn the screen off, it won't turn it back on.

It doesn't work for me either
The only thing that I was able to install on my Tilt 2 (latest stock ROM) was this file Jackos RHO_S2_00895.cab
Nothing changed.
The screen goes on but what stays off is the backlight and the only way to get the backlight to stay on in a reboot. Then try to adjust the brightness from the settings menu and moving the slides doesn't do anything. The brightness stays to the max no matter what.
Is it the light sensor? can it be disabled or checked somehow?
Thanks anyway I hope your fix helps others,
G

Jackos said:
It must be a matter of settings or hardware, I never suffered from SoD.
Click to expand...
Click to collapse
Thanks for sharing...I have had SOD only with certain builds...its been a while since I had one...

KnightmareCS said:
Installed. Didn't work . I think the flex cable is crapping out. Also had the problem where if the screen was fully slid, it'd black out. Now it's been like that every postion.
Although, the power button works to turn the screen off, it won't turn it back on.
Click to expand...
Click to collapse
Does it sometimes don't come back or always?
SoD, Sleep Of Death, so called the hangup issue does happen only after the device is suspended for a long time. It does occur kinda often, but not always if you turn off the screen. If your device never comes back from standby it isn't a problem with SoD for sure.

That would be my [email protected] cable....
KnightmareCS said:
Installed. Didn't work . I think the flex cable is crapping out. Also had the problem where if the screen was fully slid, it'd black out. Now it's been like that every postion.
Although, the power button works to turn the screen off, it won't turn it back on.
Click to expand...
Click to collapse

bisanti said:
The only thing that I was able to install on my Tilt 2 (latest stock ROM) was this file Jackos RHO_S2_00895.cab
Nothing changed.
The screen goes on but what stays off is the backlight and the only way to get the backlight to stay on in a reboot. Then try to adjust the brightness from the settings menu and moving the slides doesn't do anything. The brightness stays to the max no matter what.
Is it the light sensor? can it be disabled or checked somehow?
Thanks anyway I hope your fix helps others,
G
Click to expand...
Click to collapse
The exe file (for stock roms) is intended to work on Europe roms. I have no knowledge of HTC releasing this patch for other regions.
It's no fix for any problem with the phone The patch doesn't even touch the backlight thing.

Jackos said:
Does it sometimes don't come back or always?
SoD, Sleep Of Death, so called the hangup issue does happen only after the device is suspended for a long time. It does occur kinda often, but not always if you turn off the screen. If your device never comes back from standby it isn't a problem with SoD for sure.
Click to expand...
Click to collapse
It happens all the time. I turn the phone on via the power button. Boots up. Let it sit till backlight goes off. Press power button, nothing happens.
I can turn the phone on, press the power button to turn the backlight off and when I press it again, nothing happens.
Wild Child said:
That would be my [email protected] cable....
Click to expand...
Click to collapse
I do not think it's a flexcable problem. If I can turn the screen off and power on the device with the 'power button', it has to be something software.
I have to check again if the device comes back on, but with really really low backlight.
It's annoying, I have to restart to see a text, missed call, etc.
Thanks for your help so far.

Won't wake up
I tried loading this patch after doing yet another hard reset to try to recover from these outages. It doesn't work. Within an hour of installing it, the problem came back. My specific problem is the system goes to sleep after a minute, and it usually comes back with the power button. But after normal usage for awhile (sometimes hours, sometimes weeks without a problem), it goes to sleep and needs a red-button-reset to turn back on. Then as soon as it goes to sleep again after powering up, it's off forever. The only real recover after reaching this "cycle of death" is a hard reset (full memory erase, back to factory settings). Then it will work normally again for awhile.
I'm not sure if this is exactly the problem the other submitters were seeing, but it is surely related.
I'm off to do yet another factory reset. WM 6.5 is not worth a tinker's damn.
(AT&T Tilt 2 with ROM 2.10.502.4)

pbarschall said:
I tried loading this patch after doing yet another hard reset to try to recover from these outages. It doesn't work. Within an hour of installing it, the problem came back. My specific problem is the system goes to sleep after a minute, and it usually comes back with the power button. But after normal usage for awhile (sometimes hours, sometimes weeks without a problem), it goes to sleep and needs a red-button-reset to turn back on. Then as soon as it goes to sleep again after powering up, it's off forever. The only real recover after reaching this "cycle of death" is a hard reset (full memory erase, back to factory settings). Then it will work normally again for awhile.
I'm not sure if this is exactly the problem the other submitters were seeing, but it is surely related.
I'm off to do yet another factory reset. WM 6.5 is not worth a tinker's damn.
(AT&T Tilt 2 with ROM 2.10.502.4)
Click to expand...
Click to collapse
It's a pity that it doesn't work for you. This is a patch for Europe branded devices, I don't even see the fix at any other region-based HTC support site.
Personally I never experienced SoD, so I cannot guarantee that it does work. All I know is that this fix is supposed to help with "constant hang". Whatever it is. It's a official fix and I didn't encounter any problems with running it on my Europe branded Rhod.

Jackos is this in your ROM? I have found several times my TP2 needs a reset as the power button does not bring it life. If I take the stylus out (when this happens) the row of keys light up, but still the display is blank. I assume it's already in your ROM (Jackos S3 1.1.2 SleekBASIC) otherwise I would have installed it.

It's going to be included from version 1.1.3 and up.

Jackos said:
It's a pity that it doesn't work for you. This is a patch for Europe branded devices, I don't even see the fix at any other region-based HTC support site.
Personally I never experienced SoD, so I cannot guarantee that it does work. All I know is that this fix is supposed to help with "constant hang". Whatever it is. It's a official fix and I didn't encounter any problems with running it on my Europe branded Rhod.
Click to expand...
Click to collapse
So...how do I uninstall it? I am on sprint in the US and have the latest official win 6.5 ROM and downloaded this update on my phone through a tech website and after installing it none of my keys works except for the power button. Apparently being for Europe it has corrupted my phone and none of the talk, end, windows, back or keyboard buttons work now. I need to revert this update, is there a way without doing a hard reset. I don't want to reconfigure all my settings that aren't backed up.

scottandmo said:
So...how do I uninstall it? I am on sprint in the US and have the latest official win 6.5 ROM and downloaded this update on my phone through a tech website and after installing it none of my keys works except for the power button. No talk, end, windows, back or keyboard buttons work now. I need to revert this update, is there a way without doing a hard reset. I don't want to reconfigure all my settings that aren't backed up.
Click to expand...
Click to collapse
If anything really fails, navigate into /Windows/ directory using your favorite file manager and "delete" those two files:
Code:
debuglog.dll
HtcPm.dll
Probably deleting the second file should fix your keyboard issues.

Jackos said:
If anything really fails, navigate into /Windows/ directory using your favorite file manager and "delete" those two files:
Code:
debuglog.dll
HtcPm.dll
Probably deleting the second file should fix your keyboard issues.
Click to expand...
Click to collapse
Deleting the HtcPm.dll and rebooting fixed it, Thanks! I'm assuming that won't have any other side effects...

[Q] Captivate will no longer vibrate

My captivate will no longer vibrate. Haptic intensity is up, vibrate is turned on. I even went to the test using sgs tools. Nothing. I am running Serendipity 6.4. It's been a while since it has vibrated, but I'm just now getting around to asking the fine folks here. Thanks for any info.

Probably a hardware problem, flash to stock and see if it vibrates then.

ok so, noob question. Do I just find a stock ROM and flash it? or is there a different procedure? If it's just a matter of finding a stock OS ROM, where might i find one?

http://forum.xda-developers.com/showthread.php?t=731989
you really should've know that BEFORE you flashed away from stock.

thanks, backing up apps and flashing right meow. will i have to reinstall clockwork and reroot? Any suggestions if I dont get my vibration back? Also, any ROM suggestions? Ive been running serendipity 6.4 for a while now and have enjoyed it, but i want a change.

that will take you back to stock 2.1 like you just turned it on for the first time.
if the vibration doesnt work from there call and ***** to at&t or samsung and get a warranty replacement as that would be a hardware issue.
if you still have the update.zip with clockwork on it rooting isnt needed just have that on the root directory of the /sdcard and 'reinstall packages' twice to install a rom.
as for rom suggestions noone can really tell you as its all based on personal preference.

no vibration. oh well. I'd rather not sit on hold with at&t or samsung

Thanks to the people that helped me. I think it's probably a hardware issue and now I will take it up with AT&T . I really do hate being on hold.

I have the same issue. Did you replace the speaker/vibrator assembly? Thinking about buying one from Mobiletechvideo guy.

New captivate (now what to mod!?)

First of all I will post the phone info so everyone knows where I stand.
model: SGH-I897 att version
firmware: 2.1-update1
build: ECLAIR
I know its a bit behind other android phones atm so I'm looking to mod it and do not know where to start.
All info is appreciated

youtube.
try mobiletechvideos channel.

Before you flash anything, read, read, and read more.
Make sure your button combos are in working order, vol up and down and power button pressed simultaneously, when the AT&T splash screen appears for the second time, release only the power button and keep holding the volume buttons until the recovery screen appears. If successful congratulations you now know how to access recovery mode.
To get into Download mode (you will need this to flash with Odin back to stock a.k.a. where you are now) power off, then remove battery, replace battery, pluh usb cable into pc, now, press and hold both volume up and down buttons and plug in usb cable to phone, within a few seconds you should see a yellow screem with an adroid shovelling that reads do not turn off target. If successful, conratulations you have access to download mode.
You should pick up a JIG in case you can't access Download mode, ever. Go to www.MobileTechVideos.com and you will find them there along with some very usefull video how to's.
Go read the ROM threads over in the developement section of this forum, there are lots of really nice ROMS there.

^what he said! then flash continuum 6.1!!

Fasty is very fast but it is 2.2 (Froyo). And Mosaic is an all around good choice for a ROM along with Continuum 6.1 (Just my opinion)

Thanks for the info

Paragon RC 6 is a pretty good rom in my opinion. So is fasty's, anyone experiencing any bugs with fasty's?
Sent from my SAMSUNG-SGH-I897 using XDA App

I love fasty. Im using the newest 2.5 build and i love the battery life and the 1.4 ghz overclock and the voodoo lag fix.

Glad to see people recommending TC roms Buddy, pass by our forums (link in my sig) if you want to get continuum up and running. Guys there will help you out.

I have always found Firefly and Pheonix 7/ultimate very stable and reliable if you want to stick to Froyo builds. I have only in the last 2 weeks switched to a gingerbread build as I got tired of waiting for Rogers to update to gingerbread. As someone mentioned above do allot of reading, I am very anal about stuff so I search before I do anything all the answers are in here you just have to be willing to read, hence why this is only my 3rd post. good Luck with reading and picking a ROM to go with.

Help diagnosing freezes and random reboots

I am hoping someone has dealt with either of the following problems, and come up with a way to effectively diagnose and fix either.
The phone - 1101 build; running AT&T Stock KK4; rooted via kernel swap method (using stock KK4 kernel after swap, i.e., do not have clockwork recovery); some AT&T bloatware frozen with TiBu, otherwise stock with root
Problem #1 - roughly once a day, the phone will freeze when in sleep mode; I have had this happen with both the slide to unlock and Exchange PIN lock screen up; when I hit power to wake the phone, the screen wakes up but is unresponsive and then the screen won't shot off again; live wallpaper is frozen in place, but if the phone was plugged in, the battery icon continues with the animation loop. And if the phone is not plugged in, battery power drops rapidly in this state.
The phone isn't completely dead, because if I connect/disconnect it via USB (set to debug mode) to my laptop, the computer recognizes the phone is connected, but it is dead enough that if I call the phone, it does not recognize the missed call. The only way I can restore the phone is a battery pull. Usually it takes several minutes for the phone to come back after this, acting like it would if I had flushed the dalvik cache or installed an update.zip from recovery.
Problem #2 -also roughly once a day, at random times the screen will wake up momentarily, then clear, and I will hear the AT&T boot up sound, after a short while, the phone will run through the media scanner and any other startup launches, acting as though it had been turned on, but the battery stats show continuous uptime throughout. I have had this happen when using the phone, including when on a phone call (and the call did not drop).
I have seen problem #2 on virtually all of the AT&T GB leaks, and it seems to get more frequent the more apps that are installed. I had not seen problem #1 until recently.
The phone is out of warranty, and owned by my employer. I am not due for a new phone from them until July. I've done more master clear/reflash stock cycles than I care to admit, tried replacing/testing for disk errors the external SD card, etc..., and am afraid of doing that and having the problems come up again.
Any thoughts on how to diagnose either of these problems?

Hmm... I don't really think there is an exact diagnosis for any of these issues. Some phones are just problematic like that. The only thing I can suggest is trying a different ROM or kernel, and that might help your stability.

I have the exact same problems. Hope someone comes up with a fix. The only help I can give you is that when the phone freezes, instead of pulling the battery, you can hold the vol up & power buttons for 10 seconds and the phone will restart. Easier than pulling your phone apart, especially if you have it in a case, like I do.
Sent from my SAMSUNG-SGH-I897 using Tapatalk

korockinout13 said:
Hmm... I don't really think there is an exact diagnosis for any of these issues. Some phones are just problematic like that. The only thing I can suggest is trying a different ROM or kernel, and that might help your stability.
Click to expand...
Click to collapse
So, the way I see it, unfortunately these problems could be a function of:
Bad hardware
Misbehaving app
ROM issue
Kernel issue
I tried pretty much every leaked AT&T GB ROM and had random reboots with all of them. Seems to track with the number of apps installed, but can't prove that. I have not tried any custom ROMs or kernels.
Since this is technically not my phone, I am trying to avoid doing anything that can't really be undone if I need to turn the phone back in at some point. And I need something that can be a daily driver for work calls and Exchange email, and rely heavily on tethering when I am on the road.
Anyone with ideas on what to test, or how to capture enough log information to figure out where the problem is, would be a big help. Otherwise, I am stuck riding this out until July when I can get a new phone from my employer.

Nothing you do can't be undone, it's just a simple Odin flash away.
Be sure to back up your efs folder before flashing too much

studacris said:
Nothing you do can't be undone, it's just a simple Odin flash away.
Be sure to back up your efs folder before flashing too much
Click to expand...
Click to collapse
I've used Odin with the various GB leaks; if I go further afield (heck, performance is dicey already, how many more problems could I have with one of the ICS alphas), is it still a straight shot back to stock KK4, or are there other steps to do first?
And before I go down that road, any suggestions on diagnostics (other than yet again pulling apps off of the Captivate to see if one of them is the culprit...?)

stoobie-doo said:
I've used Odin with the various GB leaks; if I go further afield (heck, performance is dicey already, how many more problems could I have with one of the ICS alphas), is it still a straight shot back to stock KK4, or are there other steps to do first?
And before I go down that road, any suggestions on diagnostics (other than yet again pulling apps off of the Captivate to see if one of them is the culprit...?)
Click to expand...
Click to collapse
You actually might have less problems on ICS. But it all depends. You can always get back to stock with one, bootloader-free, safe flash. Diagnostics wise, there isn't really much you can do besides removing apps. I would only worry about the ones that are constantly running in the background, as they could possibly be screwing with the phone while in sleep. I think it's unlikely that this sort of testing would actually help though. I still say try something different.

stoobie-doo said:
Anyone with ideas on what to test, or how to capture enough log information to figure out where the problem is, would be a big help. Otherwise, I am stuck riding this out until July when I can get a new phone from my employer.
Click to expand...
Click to collapse
I am having the same issues except in my case I have tried to recreate the conditions and check memory and I am close to maxing it out. Part of my problem is that I come from a Palm background and I have found that Android, or at least the Cappy, is not as responsive (I was really spoiled by Cards on my Pre) I was thinking that my Android noobness is causing me to push the phone too hard and locking it up. FWIW, you might want to check memory issues