Related
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!
So I lent my brother my nexus s that had cm7 on it. He got into the clockworkmod, went to mounts/storage, and proceeded to format everything (bootloader, boot data, etc. everything in there) he said he thought that would fix the force closes, I figured no biggie, but now I can't even get the phone into download mode and I have no idea what to do, the phone will simply not turn on
wow.... dont even know why he would do that.
rule 1: dont lend people your phone.
and i dont know why you would try and get into download mode, Odin isn't the first thing you want to go to.
1. turn the phone off (if it isnt already)
2. hold volume up + power
... what happens? does bootloader mode pop up?
- plug your phone in your computer's USB
- does the sound for USB plugged in occur?
- does computer detect it?
Can't access fastboot.
Phone sometimes recognizes it and says this device is not recognized and it couldn't install the usb driver, sometimes when i plug it in it does nothing.
Didn't want to lend it to him, had no choice. I told him he should have just fixed the permissions on the phone, but then again he's not exactly android literate.
thats just dumb on his part.. i dont know why he would try and mess with your device. if it has problems, just ask you first.
its probably bricked if you cant access download or bootloader... definitely bricked if the computer is unable to detect it
your only way out of it is to get a replacement
In Device/Drivers of windows under Unspecified there's this:
SEC S5PC110 Test/BD
says drivers are not installed
Anybody out there with a solution?
I think there is more than one driver you can try, though I've never flashed anything in Windows (Linux already comes with the driver ), so I don't know for sure. I think I've seen people mentioned a few drivers before, try search for all the "brick" threads here.
Easiest solution might be to download a Linux live distribution (f.e. ubuntu) and run fastboot from there. No need to install any drivers.
Kicking him in the nuts will probably make you feel better... I don't know if it'll fix your phone though.
jruweaver said:
Kicking him in the nuts will probably make you feel better... I don't know if it'll fix your phone though.
Click to expand...
Click to collapse
lmao!!!!!!!!!!
KryPTiCk0d3 said:
lmao!!!!!!!!!!
Click to expand...
Click to collapse
While funny, it doesn't help one bit.
I would try the various methods to get into download mode and use Odin to fix it ...you might be screwed tho
Sent from my Nexus S using XDA App
SphericalPuma said:
While funny, it doesn't help one bit.
Click to expand...
Click to collapse
Unfortunately with the state your phone is in it is probably going to be the best advice you get.
Sent from my Nexus S using XDA App
http://forum.xda-developers.com/showthread.php?t=1000175
any chance that this could help you?
Ddi you ever get your phone sorted ? I'm now in the same situation !
Yes, hit up http://www.mobiletechvideos.com/blog/?page_id=970 For 50 bucks they'll fix your phone and ship it back to you in no time. They got my phone on a Friday, I got it back on either Monday or Tuesday. Of course they're based in Texas and I'm in STL so it could differ for you, but the point is, they're fast, reliable, and professional.
Thanks for that - I'm based in Ireland but I'll give them a shout and see if we can do business......
Thanks a million for the reference PUMA. Please contact me when you are in need of a brick fix. I fix hundreds of Galaxy S / Samsung / HTC variants and several others in a brick of nearly any scenario. I've devoted a lot of time to providing and almost unseen service to people in need versus parting the phone out or trashing it.
Actually, not my phone but a friend's. I was trying to restore it to stock with Odin in order to flash Cyanogen, however Odin was being a real PITA. Through numerous attempts, Odin would refuse to finish the restoration process, often hanging at sbl.bin or Setting PIT file. I tried at least ten times to get it to flash correctly. The final time I decided to let it sit overnight and flash, just in case. When I got up this morning though, it was still hung up. I unplugged the phone and pulled the battery like I had done multiple times the night before, so that I coould give it one last try before I went to work. But this time, the phone wouldn't go into download mode. I had been using the USB and 3 button combo method, but nothing this time. The phone shows no signs of life at this point, and I really don't have anything short of a JTAG left to try on it. Now I have to buy my friend a new phone.
Has anyone else experienced this kind of terrible performance from ODIN? And is there anything other than JTAG I can try. If there is someone out there that can fix it with JTAG, I would also pay money for that. I don't have the soldering skills necessary to fix this thing.
They sell the pre made jigs you can buy, just search for it and you will find plenty
Sent from my SGH-I897 using XDA App
The battery doesn't charge in download mode, the battery could very well just be dead. Pull the battery, reinsert it and plug in the phone to charge it, if all it does is get really hot and never shows any sign of life that is a brick. Check your PM.
super coffee said:
Through numerous attempts, Odin would refuse to finish the restoration process, often hanging at sbl.bin or Setting PIT file. I tried at least ten times to get it to flash correctly.
Click to expand...
Click to collapse
Can't really blame anyone but yourself for that one.. If it hung at sbl.bin and you managed to not brick it, you dodged a bullet.
Anyway, sounds like you dodged several bullets and then the inevitable happened. A jig won't help, and you're correct in your assumption that JTAG is your only way out. Fortunately for you, one of our fellow captivaters is still offering (at least to my knowledge) a free JTAG service. You should contact him to see if he'd be willing to restore your device, his name is connexion2005.
For future reference, don't flash back to stock unless you really need to. And when you do, don't flash an image that includes bootloaders. If you have bootloaders that work (3 button combo enabled on 2.2- bootloaders or 2.3 bootloaders), use a non one-click odin with an image that doesn't include sbl.bin or boot.bin; otherwise you're just taking unnecessary risks.
little8020 said:
They sell the pre made jigs you can buy, just search for it and you will find plenty
Sent from my SGH-I897 using XDA App
Click to expand...
Click to collapse
I got one off eBay for 10 bucks. Probably the best investment I've made as I have encountered about every brick situation you could imagine.
This may sound stupid, but maybe trying to flash GB bootloaders with ODIN(not one-click) could work? Exhausting all options before sending your phone in or having somebody JTAG would be preferable.
+1...they are well worth the money if you do any ROM flashing!
I have same problems before. 3 button combo method didn't work at all. No JTAG at that time.
When you plug your phone to computer, make sure it still can detect "SAMSUNG Android USB composite Device", but not "Unknown devices".
Even I wasn't on download mode or recovery mode, the odin able detect my phone as COM port then I was using Odin3 v1.8. then I put "galaxys-bootloader-JVB.tar.md5" to bootloader since I already have 2.3.3 rom before.
Another "dad, my friend has this problem" thread!?
For future reference, use Heimdall and read instructions thoroughly and multiple times. I just started using Heimdall when I made my move to flash gingerbread again when the KF1 ROM came out and I love it. Regardless how well a program works though, it's only as good as the person operating it. There are TONS of people here far more educated than me when it comes to flashing anything, but I have never bricked, or soft bricked even (yet) and I flash a decent amount.
If all else fails, I did have good luck with Josh @ mobiletechvideos (haven't posted enough times to be allowed to post the link, but he's on youtube. He's also here as connexion2005) he was able to unbrick my phone for $50. The post office does not seem to like to deliver mail from him to me, but I'm typing this on the phone he unbricked.
Sent from my GT-I9000 using XDA App
Josh @ mobiletechvideos rocks!
He unbricked my Captivate!
There is not a problem with odin! Why do people always say don't use odin because it will brick your phone. You have to use it correctly. Make sure before you even open odin that the computer recognizes your phone and you have all of the correct drivers, etc. installed BEFORE even messing with odin. Also be sure to connect to a usb port that is connected to your hard drive to limit the chance of the computer not recognizing your device.
megatronisabeast said:
Also be sure to connect to a usb port that is connected to your hard drive to limit the chance of the computer not recognizing your device.
Click to expand...
Click to collapse
Your hard drive has usb ports?
You mean motherboard?
cappysw10 said:
Your hard drive has usb ports?
You mean motherboard?
Click to expand...
Click to collapse
Yes, the motherboard! Was in the middle of a tech class when I posted that! Guess I can't multi task! Thanks!
Thanks for the feedback guys. I'm here when you need the impossible done to your Captivate...
megatronisabeast said:
There is not a problem with odin! Why do people always say don't use odin because it will brick your phone. You have to use it correctly. Make sure before you even open odin that the computer recognizes your phone and you have all of the correct drivers, etc. installed BEFORE even messing with odin. Also be sure to connect to a usb port that is connected to your hard drive to limit the chance of the computer not recognizing your device.
Click to expand...
Click to collapse
I've had odin fail a few times in a row on me when flashing gb bootloaders for i897. I had odin flashed countless times on multiple devices and computers. I'm pretty sure Odin isn't foolproof. Not everything can be contributed to pebcak, although the vary majority of problems posted on xda are...
kimchi0400 said:
I've had odin fail a few times in a row on me when flashing gb bootloaders for i897. I had odin flashed countless times on multiple devices and computers. I'm pretty sure Odin isn't foolproof. Not everything can be contributed to pebcak, although the vary majority of problems posted on xda are...
Click to expand...
Click to collapse
everytime odin has 'failed' for me, it's been a user error on my part. you need to follow the steps sequentially otherwise you have a higher probability of failure/brickage.
rmal0 said:
everytime odin has 'failed' for me, it's been a user error on my part. you need to follow the steps sequentially otherwise you have a higher probability of failure/brickage.
Click to expand...
Click to collapse
I honestly think that a lot of information here on XDA is only partial and this will get some into trouble. I know people say "search for it, it's here" and it is but the problem is that 10% of the time the information that someone is looking for is buried in a thread and the other 90% the search results list the same question being asked and answered with "it's here search" or "Did you search??"
There honestly should be posting guidelines, for everyone, I mean people take all the time to write disclaimers why not proper directions? Is there a standard Template? If I'm missing it please feel free to point it out.
For example:
This is a 9000/897/896 based ROM
This ROM needs the following bootloaders: ....
This ROM contains Bootloaders: Yes/No
This ROM will change your product code: Yes/No
This ROM requires a Davlik wipe to work: Yes/No
This Kernel is 9000/897/896 based
blah blah blah.......
If the information is readily and easily available then the amount of "dumb" question should go down dramatically and then there will be a "standard"
But then again it's Android/Linux, being fragmented is half the fun..
</rant>Just needed to vent...
Alright, so, to get started, I am actually decently tech savvy, and I wish i had rooted my phone before I even tried following the crap that samsung put up, but heres how it went.
I have a Samsung Infuse 4G on the ATT network
I finally found out how to update to Gingerbread through Kies. I spent all night charging my phone, went to Kies, and started the upgrade. About 6% through the upgrade, it said it needed an emergency recovery. I was worried, and I followed all instructions. I let the emergency recovery page sit for a day, and all it did was sit at 6% the whole time, so I resorted to my next best option, rooting it.
I have tried Ultimate Unbrick, One Click Unbrick, and Hiemdall, though I didn't get extensive with Hiemdall.
One Click said it was successful, but my phone doesn't turn on, so I tried the emergency recovery again, and still sat at 6%, then it switched to that it couldn't fix it.
Ultimate Unbrick starts off well, seeming as it is doing soemthing, but then freezes at factoryfs.rfs. Mind you I am running it in compatability mode for XP SP2 as an administrator, and I have run it on Win7 as an admin as well.
Hiemdall I got a little confused, so Im going to try that again.
Im gonna have to say, Im done with Samsung after this phone. Ive had samsung phones for 10 years (not by choice, im 19 and my mom pays for it), and every time something stupid happens, its like they kill themselves on purpose.
Is anyone possibly able to help me get my phone back to working condition? I wont be able to get a new phone for about a month, and thats only if I can find a job, which is hard when I have no phone.
Thank you to anyone who can help.
Does your phone display anything on its screen at all? If so, there's still hope.
Have you installed drivers properly?
Make sure that anything related to Kies is killed on your computer's task manager.
Try using different USB ports.
As much as possible, use a Windows XP. I had the same "stuck at factoryfs.rfs" problem and I tried it at an XP and it worked.
If nothing works, try buying a jig off of e-bay. They're about a dollar or two. Invest in some.
If it's completely borked, time to go buy an S3.
Sent from my SAMSUNG-SGH-I997 using xda premium
I can get into download mode where it shows the android shoveling in a caution sign
I installed the drivers
I havent checked that kies thing yet, Ill do that now
Ill try another USB port and get back to ya on that part
I don't own any computers with windows XP. Only a Win7 and a crappy laptop with Ubuntu on it (the laptop is crappy, not ubuntu)
Im so broke a candybar looks like rich food
And Im done with Samsung after this, Ill prob go windows phone and hack the Android market onto it.
LMAO Idk I still like Samsung over HTC and Apple. It can get really complicated --yes -- but it's worth.
Also, make sure to restart computer and then do the things I suggested you to do.
Sent from my SAMSUNG-SGH-I997 using xda premium
Im aiming for Nokia.
So, I disabled kies
Restarted my computer
Tried a different USB port
restarted Odin
Reran everything
and now, it wont even get to factoryfs.rfs
Do you possibly have a link to Hiemdall thats the newest version?
You should restart before disabling Kies. This is because of the fact that when you restart, your computer re-runs Kies.
Sent from my SAMSUNG-SGH-I997 using xda premium
I disabled after I restarted as well. Sorry, my steps were out of order.
Hmmm that's odd. Try it on a different computer tomorrow. Possibly a friend's?
Sent from my SAMSUNG-SGH-I997 using xda premium
Im gonna try heimdall first and see if I can contact a friend tomorrow. I just moved and my friends out here are more busy than the other ones I used to live by.
Heimdall Link.
Try fresh installation remove drivers from Driver Manger, run the drivers again and use Heimdall package. you need to have latest java and it need to be run as application not in any of the zip/jar file opener like 7zip etc., right click and you will see run using java<your version >
http://forum.xda-developers.com/showthread.php?t=1524081
it is clearly explained on the link what to do,
If you found difficult you can read the thread to see some probable answers as well.
Hope it will solve your query.
OK, My first attempt at messing with the firmware on an Android phone resulted in dismal failure and a dead phone..
Here's the scenario as events unfolded..
Bought an unlocked Galaxy S 4G
Trying to connect my phone to my PC resulted in dismal failure, wondered if it might be a dodgy firmware someone had installed.
*#2663# to update the TSP firmware. This just hung on the updating screen. Eventually the battery gave out. (Don't ask me why I was updating the Touch Screen Panel Firmware, I don't know.. I was fiddling. )
Recharged the battery and rebooted the phone.. Menu and Back buttons on touch pannel light but don't work.
Searched this forum and many others, seems to be a common problem but no clues as to how to resolve.
So I downloaded Odin 307 and the USB drivers, put phone in download mode, installed the following via Odin
CODE_T959VUVKG4_CL385158_REV00_user_low_noship.tar
SGH-T959V-CSC-TMB-VIBRANTP.tar
T959VUVKG4-Phone-CL1037720.tar
Worked fine, but didn't fix the issue with the TSP.
Somewhere I read that maybe it was partition corruption, so I decided to repartition. Ticked the "Repartition" box and used Hawk_Sidekick_VibrantPlus_831.pit (All four of these came as a package I found linked to on this site somewhere.) Odin said it was ok, but now I can't even power the phone on. Screen stays blank. Computer does not recognise USB device. Odin doesn't see it. It seems to be dead.
So.. Is there a rescue remedy from this scenario, or do I use this piece of glass and electronics to wedge my door open?
Please help I'm not going to pretend I knew what I was doing, but I'd like to unbrick this thing so I can at least make phone calls on it and send emails to people saying what a plonker I've been..
Thanks. :crying:
Do you have a T959V or T959 ?
Check under your battery.
Sent from my SGH-T959V using xda premium
T959V
No, I've not tried that. I'll give it a go.
The Heimdall One Click has saved my phone quite a few times, it's simple and effective! Let us know how it goes!
Sent from my Illūsîøn'd Galaxy S³
Ok, so I managed to get it into Download mode and reflashed it in Odin. I'm going to have a go with "oneclick" and see what happens, but at this point the only outstanding thing to fix is the TSP, which is still kaput. (Maybe one click will fix that) I've searched and searched on this forum, there's a whole bunch of dead threads where people have killed their TSP, and no resulting fixes posted. If anyone has any ideas, its would be great if you could post them, because at the moment, "menu" and "back" are still U/S.
Thanks for your help so far. If I get a solution, I'll post it here, I hate abandoned threads where people leech solutions to their probems and don't give feedback.
OK, So I tried this : http://forum.xda-developers.com/showpost.php?p=23121150&postcount=12&nocache=1&z=6720291850525859
No luck..
Next thing to try is an older version of the O/S, apparently if I put on then it downgrades one of the firmware, and running the update again fixes the issue. (On can only hope.. Now I gotta go see if I can find an older version of the OS and try this http://forum.xda-developers.com/showpost.php?p=21987511&postcount=9
:fingers-crossed:
Oh well.. On the plus side, I bought this little cheap phone to play around and learn on.. I seem to be doing just that. :cyclops: