Database Info

3 button Combo

This is a request, hopefully I will not get flamed for posting this.
I am not a programmer, I cant do what you guys do...just not my thing. There are MANY people that have problem with the 3 button combo stopping working. I experienced this myself on my second captivate. Is there anyone out there solid enough and willing to commit the time to solve this issue? It is obviously a software issue and I feel confident that if one of the senior solid members devoted time to it could solve it. I can say that if I have the ability to boot into download mode I will do just about anything to this phone because I will have the ability to always revert and start over. When I lost that ability, it crippled my phone in my mind cause problems occur, that is just how it goes eventually no matter if you follow directions perfectly or not.
Anyway, its easy for me to ask others to figure this out...its just beyond my current abilities and I think there are many on this board that would really love for a fix to be there. I also think its a worthy area to put time into considering the amount of people that have had issues with this. It doesnt always come down to people not knowing what to do, what combination works...for some of us it was a software issue that no options worked for. Anyway, that is my rant....I just have great faith that someone on here is solid enough to solve the issue...it just isnt me!!

FLAME WAR!!!
Seriously though, I feel your pain, I had two crappy cappies. Lucked out on the third.
Hope someone does figure it out.
Now let the FLAME WAR BEGIN!!!

I think froyo solved this issue because now my 3button combo works.

Some reported that JH7 fixed it too but it does not work for many and Im sure Froyo is the same deal. Anyway, just a thought as it would help many.

I would prefer adb to the button combos...
Just
1. connect ur phone in debugging mode
2. Press Win+R to open up a cammandline window
3. enter the folder with adb
for recovery mode, type in
adb reboot recovery
for download mode, type in
adb reboot download
This method does not require root, and extends the life of your buttons as well
adb usually comes with lagfix or sideloading patchs.

I agree that those methods are great but the problem is if you cant boot the device, the 3 button combos are your only choice.

gocats7 said:
This is a request, hopefully I will not get flamed for posting this.
I am not a programmer, I cant do what you guys do...just not my thing. There are MANY people that have problem with the 3 button combo stopping working. I experienced this myself on my second captivate. Is there anyone out there solid enough and willing to commit the time to solve this issue? It is obviously a software issue and I feel confident that if one of the senior solid members devoted time to it could solve it. I can say that if I have the ability to boot into download mode I will do just about anything to this phone because I will have the ability to always revert and start over. When I lost that ability, it crippled my phone in my mind cause problems occur, that is just how it goes eventually no matter if you follow directions perfectly or not.
Anyway, its easy for me to ask others to figure this out...its just beyond my current abilities and I think there are many on this board that would really love for a fix to be there. I also think its a worthy area to put time into considering the amount of people that have had issues with this. It doesnt always come down to people not knowing what to do, what combination works...for some of us it was a software issue that no options worked for. Anyway, that is my rant....I just have great faith that someone on here is solid enough to solve the issue...it just isnt me!!
Click to expand...
Click to collapse
The problem isn't necessarily "obviously software". The JH7 OTA "fixed" the problem, but really it didn't, because if you Odin'd back, you have the problem again. We looked and looked in that release to try to find what was in it that fixed the problem, we could not find it. Tell me why Odin will not take away or give 3 button recovery to phones that already have it, or don't have it, but it will if you get it from the OTA. Also, why does it take so long for Samsung to provide a fix, but the fix actually isn't a fix, it is just a cover up. I am leaning very heavily on this is a hardware issue. If you think about it, why is it that you can completely destroy your phone, but you can still get into download mode? This is because your second bootloader still works (I believe) but why is it impossible to break this? I think it is because this is a hardware issue, and we can never get a real, permanent fix.

DemonWav said:
The problem isn't necessarily "obviously software". The JH7 OTA "fixed" the problem, but really it didn't, because if you Odin'd back, you have the problem again. We looked and looked in that release to try to find what was in it that fixed the problem, we could not find it. Tell me why Odin will not take away or give 3 button recovery to phones that already have it, or don't have it, but it will if you get it from the OTA. Also, why does it take so long for Samsung to provide a fix, but the fix actually isn't a fix, it is just a cover up. I am leaning very heavily on this is a hardware issue. If you think about it, why is it that you can completely destroy your phone, but you can still get into download mode? This is because your second bootloader still works (I believe) but why is it impossible to break this? I think it is because this is a hardware issue, and we can never get a real, permanent fix.
Click to expand...
Click to collapse
word.
Also, for those of you who can get their phone to show the computer/phone screen, all you need to do is hold all the buttons and the screen will eventually restart, then you let go of the power button (but keep holding the others) this should get you in recovery mode... I read this somewhere on the forums and it has saved me many times!!! (my button combos only work this way)

We will just have to agree to disagree because I do not think it is a hardware issue and I do not agree with your logic. Mine worked perfect until I changed software. Others claim JH7 (software change) made theirs work again. I could go into more details about why I think the issue is software based but I wont convince you and you will not convince me. The request hasnt been met with much enthusiam so the thread should probably just close.

I was one of those who gained 3 button abilities with the update. we now know that JH7 and apparently Froyo will enable the 3 button combo. But if you ODIN back to 2.1, the 3 button combo no longer works.
My question is that once Froyo is officially released and we can ODIN back to stock on 2.2 (which we already can I think because of the leak), doesn't that mean we now have 3 button combo for good because technically, you won't need to ODIN back to 2.1 when Froyo is officially supported by samsung.
Or am i just confused? lol

gocats7 said:
We will just have to agree to disagree because I do not think it is a hardware issue and I do not agree with your logic. Mine worked perfect until I changed software. Others claim JH7 (software change) made theirs work again. I could go into more details about why I think the issue is software based but I wont convince you and you will not convince me. The request hasnt been met with much enthusiam so the thread should probably just close.
Click to expand...
Click to collapse
Probably because its old news. http://forum.xda-developers.com/showthread.php?t=784147 I've already made the same request, but we got nowhere on it. Like I said, we have tried to find the problem, or what is fixing it, but we just can't find it. It's amazing that it does at least temporarily fix the problem, because from what we found, it shouldn't.

n19htmare said:
I was one of those who gained 3 button abilities with the update. we now know that JH7 and apparently Froyo will enable the 3 button combo. But if you ODIN back to 2.1, the 3 button combo no longer works.
My question is that once Froyo is officially released and we can ODIN back to stock on 2.2 (which we already can I think because of the leak), doesn't that mean we now have 3 button combo for good because technically, you won't need to ODIN back to 2.1 when Froyo is officially supported by samsung.
Or am i just confused? lol
Click to expand...
Click to collapse
im in the same situation as you. froyo enabled the 3 button combo.
im thinking that since we dont have to odin back to 2.1 anymore, we will always have 3button combo. but can someone clarify this?

here is an easy way to get into recover/download mode without the 3 buttons:
First root your phone (most people on this site have done this)
then download Android Terminal Emulator from the market
once it is finished downloading, open and you should be at a blue screen, type "su" (without quotes obviously). It will ask for root access/super user permission. Click Yes. Now type "reboot download" to enter download mode, type reboot recovery for recovery, and reboot for plain old rebooting. It may say you don't have permission or something when you first try, just restart phone and try again.
Hope that helps. My button combos don't work either, so thats what I use flawlessly every time.

whenemusattack said:
here is an easy way to get into recover/download mode without the 3 buttons:
First root your phone (most people on this site have done this)
then download Android Terminal Emulator from the market
once it is finished downloading, open and you should be at a blue screen, type "su" (without quotes obviously). It will ask for root access/super user permission. Click Yes. Now type "reboot download" to enter download mode, type reboot recovery for recovery, and reboot for plain old rebooting. It may say you don't have permission or something when you first try, just restart phone and try again.
Hope that helps. My button combos don't work either, so thats what I use flawlessly every time.
Click to expand...
Click to collapse
this will definitely work but im thinking the main concern for people is when they brick their phone and cant get it to boot up. ADB and Android Terminal Emulator only works when the phone is booted up. With no 3 button combo support, idk what people can do when it wont boot up

It's possible to easily get into download/recover mode via the method posted above or adb shell. The problem is if your phone cannot boot. This almost happened to me today when I tried to remove the sl4a lagfix before DG switched to OCLF.
The button combos originally worked on my Captivate, but stopped working at some point after I one-clicked back to JF6 and then flashed Cognition 2.2, as at the very least Cognition 2.2 is not guaranteed to restore the button combos. I have not tried the stock Froyo leak, so I cannot comment on that. At some point this week or next weekend, I will one-click to JF6, update to JH7, then install Cognition 2.2 from there and see if that restores it.

BTW my phone's 3 combo now works after One-Click Froyo. So it seems to me the 3 button issue is software related.

whenemusattack said:
BTW my phone's 3 combo now works after One-Click Froyo. So it seems to me the 3 button issue is software related.
Click to expand...
Click to collapse
Which to me is weird because most recovery/debug modes are not or should not be affected by software. In which case it makes recovery totally pointless if your software is corrupt (point of recovery is to FIX the corrupt software).
it still doesn't make sense why SOME samsung phones will ALWAYS work with 3 button even on 2.1 and others wont at all.
In my case, I don't really care because I'm not an aggressive flasher and usually don't flash beta stuff etc.

[HELP] What do I do now? Captivate dead.

Yessss another dead captivate thread.
I think I'm gonna go die now.
I followed the video guide to install a custom ROM, in the development thread to the letter, and now my phone wont even turn on... (now that im thinking about it, I think I may have left the debugging mode OFF before I went to flash back to stock, maybe thats why?)
I got into download mode, plugged the phone into odin3 JF6 one click, it started and at some point during the process it said "removed" even though I didnt touch anything, and then i got a weird msg saying my device is not recognized, keep in mind the drivers were installed properly, and I had everything double checked before i flashed....
wtf do I do now? Cant boot at all or go back into download mode. this is my third galaxy, got it two days ago ffs.

My only 2 suggestions. Go to the Dev section and in the guides there is a method to make a USB Jig without solder or anything. You're out like $1 if it doesn't work.
Also, what rev is your phone? There's been some threads started saying the newer Rev phones, maybe 1010 and up crap out using normal One-click. Do check your rev level under the battery and do a search of the forums. I know I have seen the threads.
good luck.

1 reboot pc
2 use different usb ports (direct to motherboard)
3 open odin first as administrator
Sent from my GT-I9000 using XDA App

bobbylx said:
My only 2 suggestions. Go to the Dev section and in the guides there is a method to make a USB Jig without solder or anything. You're out like $1 if it doesn't work.
Also, what rev is your phone? There's been some threads started saying the newer Rev phones, maybe 1010 and up crap out using normal One-click. Do check your rev level under the battery and do a search of the forums. I know I have seen the threads.
good luck.
Click to expand...
Click to collapse
I'm not sure if I was looking at the right place, but I think its 10.12. I'll do a search and see what comes up, thanks for your help.
JayPhill89 said:
1 reboot pc
2 use different usb ports (direct to motherboard)
3 open odin first as administrator
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
I'll try that, thanks.

Open Odin first then,
1. Remove your battery for 30 seconds, remove external SD card and SIM card
2. Reinsert battery.
3. Hold down both volume buttons and while holding them down plug the phone in.
It should get into download mode then. I bricked my phone and it wouldn't boot up at all and this worked for me.
On a side note, I have not had much luck flashing or doing much of anything on Windows 7 64 bit. I would suggest trying it on an XP machine if you have access to one.

G.Hook said:
Open Odin first then,
1. Remove your battery for 30 seconds, remove external SD card and SIM card
2. Reinsert battery.
3. Hold down both volume buttons and while holding them down plug the phone in.
It should get into download mode then. I bricked my phone and it wouldn't boot up at all and this worked for me.
On a side note, I have not had much luck flashing or doing much of anything on Windows 7 64 bit. I would suggest trying it on an XP machine if you have access to one.
Click to expand...
Click to collapse
I've tried every possible key combination out there and nothing works. I think my best bet is a Jig, unfortunately the source didnt have any transistors in stock so im SOL for now.

Use JIG ... It will be your last help.

Use it as a paper weight.

If you look up samsung captivate jig on ebay you will find some pre built. I bought one not long ago just to have and it works just fine.
I hope this helps. Best of luck to you.
Sent from my GT-I9000 using XDA App

Sounds like you are a victim of the one size odin fits all debacle. You will indeed need a jig to recover and then you must use odin to flash jh2 or later firmware to your phone. Unfortunately, most guides still direct people to flash jf6 even though your situation comes up on a regular basis.

Check out this link for a jig. And there is a video to show you how to build one. Or mobiletechvideo guy sells them for 17 bucks.
http://forum.xda-developers.com/showthread.php?t=889128&highlight=usb+jig
Sent from my SGH-I897 using XDA App

newter55 said:
Sounds like you are a victim of the one size odin fits all debacle. You will indeed need a jig to recover and then you must use odin to flash jh2 or later firmware to your phone. Unfortunately, most guides still direct people to flash jf6 even though your situation comes up on a regular basis.
Click to expand...
Click to collapse
It seems to me like there's consistent irregularities with the entire process, its not uniform at all, which is very frustrating, every one faces different problems, and the solution is never the same.
Anyways, I went out and bought 3 resistors, turns out they were the wrong ones, I found out the colors werent the same of what I needed, but then that just goes to show you how difficult it is, its partly my fault i got the wrong ones, but someone like me who doesnt know much about hardware hacking, walks into an electronic store, faced with several options, is some times lost.
Oh well, I could've fixed it, had I got the right resistors, but then again, who was going to guarantee I wasn't going to kill it again, for the exact same reason I mentioned in the first post, because I need to consider a few things here, first and foremost, that I have a rogers branded device, and these are the ATT forums.
I called rogers and a replacement has been placed, I should be getting it by friday, or tomorrow if im lucky, with whatever comfort that brings, I still have several concerns, and now that I've basically rendered 3 devices to "almost" none-working condition (this one being an exception because I can "possibly" fix it) I'm not even sure how far I want to go.

rsnt said:
It seems to me like there's consistent irregularities with the entire process, its not uniform at all, which is very frustrating, every one faces different problems, and the solution is never the same.
Anyways, I went out and bought 3 resistors, turns out they were the wrong ones, I found out the colors werent the same of what I needed, but then that just goes to show you how difficult it is, its partly my fault i got the wrong ones, but someone like me who doesnt know much about hardware hacking, walks into an electronic store, faced with several options, is some times lost.
Oh well, I could've fixed it, had I got the right resistors, but then again, who was going to guarantee I wasn't going to kill it again, for the exact same reason I mentioned in the first post, because I need to consider a few things here, first and foremost, that I have a rogers branded device, and these are the ATT forums.
I called rogers and a replacement has been placed, I should be getting it by friday, or tomorrow if im lucky, with whatever comfort that brings, I still have several concerns, and now that I've basically rendered 3 devices to "almost" none-working condition (this one being an exception because I can "possibly" fix it) I'm not even sure how far I want to go.
Click to expand...
Click to collapse
My first captivate went fubar within my 30 days and I damaged the nv_data.bin on my second captivate and was stuck with the test IMEI. Samsung fixed my second one for free. Now I'm at the point where I'm totally sure about what precautions I need to take to keep me out of trouble but I'm not sure if I want to risk it again, heh.
The cheap jig does work. It helped me when I accidentally unplugged my phone during an odin flash.

Yes, you make a good point. You will find that most of the guides are written by people like myself who have an early revision or a phone from the initial release. For most of us, from what I've read and experienced, our phones are really hard to brick, ie, button recovery always works, odin one-click works, etc.
I honestly don't know all the differences now between revs. The first hiccup was the phones missing button recovery/download, and now it seems that people are having issues using the Odin One-click that we have been using for months.
I would recommend with your next phone check the rev or manufacture date, then search the forums for people with similar or same revs that have been successful at flashing and find out what they did.
good luck

@bobby
I wasnt trying to diminish the help that the guides provide. The work that went into creating them is certainly appreciated. The problem arises when so many people just tell newcomers to flash with x version of odin without considering the changes that have occured in the newer builds.
Sent from my Liquid Metal using XDA App

newter55 said:
@bobby
I wasnt trying to diminish the help that the guides provide. The work that went into creating them is certainly appreciated. The problem arises when so many people just tell newcomers to flash with x version of odin without considering the changes that have occured in the newer builds.
Sent from my Liquid Metal using XDA App
Click to expand...
Click to collapse
I agree with you completely. I tend to take it for granted that button recovery works for me and that good old odin one-click does too. It seems we need to start collecting data and making new guides.
Something like,
If you have rev, 1006, 1007,1008 go here,
If you have rev 1009 to 1012 go here,
etc.

latest update,
Two cables, and six resistors later, my phone won't go into download mode, lol, I'm not even sure I did things right, I'm gonna try stripping the same cable, used in one of those videos on how to make a jig, I still have three extra resistors.
I'm starting to think its because of it being with rogers. im gonna search the forums.

A micro usb breakout board is the simplest method for constructing a jig.

Wow, I guess I'm lucky that the used Captivate I picked up for my gf is an older one at 1007. Root procedure for her went without a hitch.
From stock rom, all set up and in daily use, WITHOUT ROOTING first.
Put clockwork update.zip on her sdcard.
Reboot into recovery.
Reinstall packages twice to get into clockwork recovery.
Wipe data/factory reset.
Flash Cognition.
Profit.
She's been using it this way for two weeks and loves it so much more than stock.
What was so complicated about the procedure you followed? Or was it the same as this but it just didn't work?

rsnt said:
...and now that I've basically rendered 3 devices to "almost" none-working condition (this one being an exception because I can "possibly" fix it) I'm not even sure how far I want to go.
Click to expand...
Click to collapse
I think you may have a good point. Eventually your carrier will stop replacing bricks for you. If you still have the inclination to play with flashing, investing in a jig would definately be a wise investment and if I were in your shoes, I wouldn't flash anything without one. I made a jig for myself before I ever flashed anything but luckily I have never had to use it, probably because I took the time (about a month and a half of trolling around here reading.) to research what all was involved with what I was about to jump into. Just something to consider in case you want to try again. Good luck!

[Q]Urgent - Rogers Captivate phone has AT&T firmware after ODIN 2.2 upgrade

Well, I think I'm deep poo.
I'll save the introduction, being a new member, for later, and focus on an urgent problem that needs help.
Basically, being stuck on 2.1, I tried to find the easier way to upgrade my Captivate to 2.2. My Kies didn't work (even though I tried many solutions), so I had to find new ways to update my phone to Froyo. Take note that my Captivate is locked on Rogers (meaning I have a SIM card inside already). Also, my phone isn't rooted.
I stumbled upon this; "considering I can't post links, I'll give the directions for you, so you find the page I'm talking about; it's on techpetals.net and the article name is "How to Install Froyo on Captivate – Android 2.2 Froyo for Samsung Captivate Leaked"
I completed all the steps and this is where the problem shows its ugly face.
The HUGE problem comes from the fact that my phone is now like a stock, locked AT&T phone. What I mean by that is that the boot screen shows the AT&T logo. Everything is stock, such as in the early AT&T Captivate YouTube review. All my contacts are probably lost (I hope there's a way to retrieve them back). I can blame myself, as much as I can blame the author of the article who didn't mention that the solution only applied to US phones (likely). At least the menu shows that the firmware's 2.2.
I'm in limbo and I don't know what to do. There are so many things to fix here. I don't know what to do and I urgently need your help. What should I do, people?
Any kind of help would be appreciated.

What seems to be the problem? Do you want to go back to stock or do you just want to remove the ATT boot screen?

carboncopy01 said:
What seems to be the problem? Do you want to go back to stock or do you just want to remove the ATT boot screen?
Click to expand...
Click to collapse
Thanks for the reply. A little update on my situation: I've followed the steps mentioned on the mmacleod.ca - updating the rogers samsung galaxy s to android froyo 2 2 froyo article, which helped me set my APN. 2.2. is working great, but my issue now is the fact that I lost my contacts (which were stored on the internal memory) and the AT&T boot screen.
Are these solvable issues?

Is my Samsung Infuse DEAD?

Hey, guys. Hoping some of you experts can help me diagnose what's wrong with my Samsung Infuse. I bought it off Craigslist at the end of May, and the guy had the phone with the original screen protector on it, with the original case and all accessories, so I had no reason to believe it had any problems. He told me the phone was already rooted & unlocked, which I wanted since I signed up with Straight Talk. I used it for June & July and had a host of problems, so I put on the CM10 ROM last week to see if it helped. It didn't. Here are the problems I continuously encounter:
1. When going to unlock my phone with a pattern, once in awhile it won't detect my finger-presses. Sometimes nothing shows up at all, sometimes one of the dots will highlight as I pass over it, but it won't draw. Eventually the screen turns off, and I turn it on and try it again. Usually it ends up working.
2. The battery dies much quicker than I expect it should. I tried running JuiceDefender and not running JuiceDefender, and it doesn't seem to make a difference. Even without using my phone much for anything, even with the screen off, the battery will run out before the day is out. It's like if you were driving and had a hole in your tire... seems like some sort of a leak.
3. The cell radio seems flaky. Sometimes I won't get texts on time. A lot of the time I can't access any data, which is very important as I use Google Voice for lots of my texting, so I send a text and it won't go out. Loading web pages or reloading my email shows that it is a data problem.
Those are the primary problems, and I suspect that somehow they are all related. I'm not sure if the Craigslist guy sold me a lemon, or there is some other problem that came up. I've tried multiple ROM's and disabling every app I can think of. Can anyone think of anything that would cause these problems & any way to fix it? Or do I just own a broke phone that I have to throw in the garbage?
Thanks in advance for reading!

a whole slew of problems can lead to a whole slew of possibilities for your issues.
first, i wasnt aware that you could do any of this on a straight talk phone, but i could be wrong. i am not the "expert" you may be looking or hoping for, though one i am sure will show up.
second, i think the response you may get is......did you go to JB straight from Gingerbread??? that will cause HUGE problems.
dd you read OP and follow to a tee??? again HUUUUGGEE problems.
the "never fail" here.....READ READ READ. feel confident as to what you are doing and follow steps one at a time. UNDERSTAND steps one at a time.
first thing that never hurts.....return to stock and start from scratch.
"super everything thread" under development.
Odin "stock-root & modded 3e rcovery.
follow all directions TO THE TTT.
if that doesnt work, you might have to get some mortar, you've got yourself a BRICK.
i know almost everyone else here is more of a expert than i am, but i do believe that is where they will tell you to start
good luck and be sure and thank the experts

captemo said:
first, i wasnt aware that you could do any of this on a straight talk phone, but i could be wrong. i am not the "expert" you may be looking or hoping for, though one i am sure will show up.
second, i think the response you may get is......did you go to JB straight from Gingerbread??? that will cause HUGE problems.
dd you read OP and follow to a tee??? again HUUUUGGEE problems.
first thing that never hurts.....return to stock and start from scratch.
"super everything thread" under development.
Odin "stock-root & modded 3e rcovery.
follow all directions TO THE TTT.
if that doesnt work, you might have to get some mortar, you've got yourself a BRICK.
Click to expand...
Click to collapse
While I have no idea what you're getting at by your Straight Talk comment, as ST is little more than AT&T service that's sold through a 3rd party at a discounted rate, the fact that he's using ST may be part of his problems, at least in regards to the network issues. I'm also having an unbelievable amount of data issues on ST. ST is having some network problems that are affecting a decent amount of customers who are on their AT&T network.
One thing that the OP may want to try is this: Download DNS Changer from the Play Store, and change your primary and secondary DNS to OpenDNS1 and OpenDNS2. Or try different settings, as there are a bunch that are available. That has made at least some difference with my data connectivity issues.
Based on my own experience, having tried to go to JB directly from GB, is that if it's going to affect your radio, it's likely to completely wipe out your EFS data so you won't have ANY cellular or data networking capabilities. As stated, that's simply based on how it worked out for me, and there could easily be other side-effects that just didn't happen to show up for me.
I agree with returning completely to stock UCLB3, with the GB bootloaders. Then flash Entropy's 4.4.2012 Kernel, which will also install CWM Recovery. I'd personally reccomend Heimdall, as it seems to be somewhat simpler. Detailed information on returning to stock via Heimdall can be found in this thread:
http://forum.xda-developers.com/showthread.php?t=1629079&highlight=heimdall+uclb3
If you use it, be sure to thank qkster for making it available. He's probably the most helpful person you're likely to find on this forum, especially where us noobs are concerned.

I would take it back to stock and start all over.
Here is a very helpful thread.
http://forum.xda-developers.com/showthread.php?t=1700416

I agree with parrot head. When issues arise go back to stock. That's the best part of our phones. They are damn near impossible to really mess up. Just have to be ware of bootloader flash going wrong. If you got your gb rom from keis your good to go though.
Sent from my SGH-I997 using xda app-developers app

Appreciate the response, guys. I guess it doesn't hurt to try to start from scratch... AGAIN! It just seems like I'm putting an awful lot of hours into putting new ROM's and bootloaders on this phone. Going to be especially frustrating if I go through all the steps and it still doesn't fix my issues, which would mean my phone is broke. Oh well, guess I have little other choice.

All of the issues sound related..
It shouldn't take long to drop to stock and flash up to JB.. I've bobbled and missed steps here and there and have had to return from stock more times than I care to admit.. even rooting and flashing up the ladder only take about 20 minutes if even that..
Good luck!

drnecropolis said:
All of the issues sound related..
It shouldn't take long to drop to stock and flash up to JB.. I've bobbled and missed steps here and there and have had to return from stock more times than I care to admit.. even rooting and flashing up the ladder only take about 20 minutes if even that..
Good luck!
Click to expand...
Click to collapse
Yes, the flashing process isn't that long, it's getting back my phone to all of my customized settings that ends up taking weeks. Home screen icon positioning, logging in to every app, system settings, etc.

Didn't create a backup?

drnecropolis said:
Didn't create a backup?
Click to expand...
Click to collapse
I've always created backups with Titanium Backup, but when I restore the apps, a lot of them ask me to re-login or re-verify myself.

Thanks for the advice guys.
Spent a whole day going back to stock, then CWM red, then ICS, then Jellybean. Things seem to be markedly better, but the phone still seems laggy in a few places. Is this just because it's not the latest and greatest processor?
Also, the GPS just does not work right. It's still identifying me as being in Missouri even though I'm in Nevada. Consistently. Do I just have to live with that?

veeRob said:
Thanks for the advice guys.
Spent a whole day going back to stock, then CWM red, then ICS, then Jellybean. Things seem to be markedly better, but the phone still seems laggy in a few places. Is this just because it's not the latest and greatest processor?
Also, the GPS just does not work right. It's still identifying me as being in Missouri even though I'm in Nevada. Consistently. Do I just have to live with that?
Click to expand...
Click to collapse
Are you still using the Trebuchet Launcher that comes built-in to the JB ROM? If so, that may be part of your lag problems. I just use ADW EX launcher. Here's an excerpt from the Paranoid Android JB OP:
******* EVERYONE: If you experience a sudden lag for no reason, IT is due to Trebuchet. GOOD NEWS though... From reading the log cat on my end, there is a very simple fix... Go to settings -Launcher - Homescreen - And Check "Resize any widget" and you are good to go! Instantly fixes the lag problem that a few have been experiencing. I have located the source code that needs to be changed and this will be enabled by default on future builds. ********
Click to expand...
Click to collapse
As far as the GPS goes, I think Samsung just used ****ty receivers in the Infuse. My GPS isn't quite as bad as yours seems to be, but it's nowhere near as accurate or reliable as the GPS chipset in my crummy little Optimus V.

[Q] Is my phone bricked???

Okay, I bought a used MT4GS from a fairly reputable phone reseller called CPR (cell phone repair.) I bought it back in March or April of this year. I immediately rooted and installed a custom rom and CWM. A few months ago I upgraded my rom to CM9 and about a month ago I began having problems. The isses were minor at first, the hardware buttons on the outside of the phone would stop working but I could open the phone and use the ones on the keyboard. Then in the past two weeks all of the buttons would stop working. I thought it was a hardware problem so today I dropped it off at CPR and they took it apart and tested all of the buttons. According to them all the buttons tested out fine. So I have a phone that the only thing that works is the touch screen. Here is the odd thing. If I hold the volume down while booting I get the fastboot menu and can navigate it using the volume keys. If I go into recovery mode none of the buttons work same as in the phone. So either this is a software problem or a systemboard problem. Because my power and volume buttons work on the recovery menu I'm inclined to believe it's a software problem but I'm a little lost on how to fix it. I just tried to boot the phone again and it's now stuck on the boot animation and does nothing. Please help!!!

I was curious if you tried a reinstall before your keys went completely berserk...but no matter now. Sometimes a person will get a bad download though and you can get some WEIRD results from them.
Anyway....this is how I answered on the CM9 Thread if you hadn't seen it......
I've never heard of a ROM brickng a phone especially gradually but I suppose anything is possible. If what you're wanting to do is to return to stock & just kinda "start over" then just go to This Thread and scroll down to the files labeled as "Return to Stock" & download the correct file according to your installed software. Then you can just place it in the root directory of your SD card and reboot into Hboot. PG59IMG files are designed to run from your bootloader and you just answer the few questions it asks as it does.

WeekendsR2Short said:
I was curious if you tried a reinstall before your keys went completely berserk...but no matter now. Sometimes a person will get a bad download though and you can get some WEIRD results from them.
Anyway....this is how I answered on the CM9 Thread if you hadn't seen it......
I've never heard of a ROM brickng a phone especially gradually but I suppose anything is possible. If what you're wanting to do is to return to stock & just kinda "start over" then just go to This Thread and scroll down to the files labeled as "Return to Stock" & download the correct file according to your installed software. Then you can just place it in the root directory of your SD card and reboot into Hboot. PG59IMG files are designed to run from your bootloader and you just answer the few questions it asks as it does.
Click to expand...
Click to collapse
Yeah I actually did that last night. Got to watch the intro animation from HTC/T-Mobile etc. Still no buttons. I'm guessing that the system board has a bad chip since the buttons tested out okay. That is more consistent with the gradual failure than a software bug. Now if there were a rom made for a phone without buttons then I'd be in good shape. Luckily I found an identical phone on Craigslist for $85 which I feel is reasonable for a discontinued phone. Does anybody have recommendations on QWERTY Android phones for T-Mobile that are better than the MT4GS?

Someone mentioned that Samsung is coming out with one soon but I can't remember the name for squat.

If it's for T-Mobile then I suggest the Samsung Relay 4G. Else better wait for Samsung Stratosphere 2 fior Verizon if you might consider changing networks for the sake of a better phone.

THAAAAT'S the one! Samsung Relay 4G. Thank you kind sir!:good:

Samsung took over for HTC, who took over for crApple.

blackknightavalon said:
Samsung took over for HTC, who took over for crApple.
Click to expand...
Click to collapse
Samsung also.

First off let me say I'm sorry about the death of your MT4GS - mine died over a month ago and I'm still in mourning. However, the Relay is a nice little device. I don't want to be accused of attempting to recruit people again, but at the risk of saying so it is an upgrade from the HTC product in MOST ways - some people don't like the screen as much and the camera is definitely inferior. However, it's a nice device. I'm happy with it honestly. TouchWIZ takes some getting used to but since HTC didn't give us ICS, even ICSense... and Samsung has ICS on here with JB to come... I'm satisfied. If you are still curious we have a thread in the G2/Desire forum that we are using until XDA gives us a dedicated forum.
Sent from my SGH-T699 using xda app-developers app