Hello all,
To keep it concise:
Received my SII from Vodafone yestersday - all is well.
Proceeded to flash the phone with XWK37 firmware and rooted the phone by flashing chainfire's insecure kernel, applying root and then flashing the stock XWK37 kernel - have used Odin before and all is well.
By the time I finish playing with the phone it's 3.00am so I put the SII on charge (battery at around 30%) - all is still suspiciously well.
Get up at 7am to take my kid to school and when I get back I discover that the menu key no longer does anything when pressed (home key and return key still work fine) - it doesn't light up nor does it bring up a menu - all is not well.
So far I've tried:
Reflashing both the firmware and kernal - no effect.
Removing sim card, sd card and battery - no effect.
Hard resetting (both via button method and android privacy menu) / formatting sd card - no effect.
Dialling *#*#2663#*#* and updating the touch firmware - no effect.
Accused my wife of breaking my phone before she went to work - no effect.
Now If it's a hardware problem (which would be disappointing since I've only had the phone for 1 day) then I'm stuck since there is no stock UK Vodafone firmware available yet to flash back to before handing in for repair - plus I don't want to go back to using my N97 in the meantime.
Yes I preordered the N97 before it was released and got myself stuck in an 18 year contract - words can't describe how much I hate that worthless piece of Nokia - I kept it to teach myself a lesson, early adoptions don't pay off.
The only other relevant thing I can think of is that I was trying to install ADW launcher (previously used it a lot) before I went to sleep last night however although the phone claimed that it downloaded and installed - no icon appeared and I was unable to launch it although it's wallpapers showed up when I was switching my live wallpaper.
Can anyone help with any idea's of what it might be aside from a hardware issue?
If it is a hardware issue, anyone know when the Vodafone UK firmware might shown up?
Tell you what, I'll throw in a free N97 for anyone who solves the problem
Thanks guys.
K37 firmware ????
I would flash old firmware like WKDD .
Possible with pit and repartition checked if that failed . Not used either yet on SGS2 but always cleared SGS1 by that method .
jje
Thanks for the reply jje,
The XWKE7 is the latest generic XEU firmware available from this guide:
http://forum.xda-developers.com/showthread.php?t=1075278
I flashed it exactly as the guide stipulated.
However I didn't even think to try flashing it to a earlier version to see if the problem might be with the actual firmware.
Should be finishing work in a couple of hours so will try flashing the older XWKDD
firmware and see if that relocates the menu key.
Will update as soon as I know.
Damn.
No luck - tried flashing KDD (and also KE1/KE2 for good measure) accompanied by full memory wipes - still no luck. All these firmware files come in one .tar package which i place into the PDA section of Odin.
Even tried one where the pda, modem and csc were split into seperate files from:
http://forum.xda-developers.com/showthread.php?t=1075278&page=11
Still no return of the menu key.
When I am flashing - I leave the pit section of Odin completely alone and leave re-partition unticked - I take it this is correct?
It's strange because apart from the menu key - the S2 is working perfectly.
The only other thing I can think of is that the Vodafone branded version of the S2 in won't work with any other generic firmware which is pretty unlikely methinks.
jje - "...possible with pit and repartition checked if that failed.." - I didn't quite understand what you were recommending there mate - should I be using a pit file and checking repartition?
Any other ideas guys?
Off to go glare at my wife's dumbed down yet fully working iphone - it's laughing at me...
I've got the same problem. The menu button works just when it wants. Sometimes it doesn't react at all, sometimes it works perfectly.
I have KE1 firmware, I have rooted it and unrooted (for sim unlocking), then installed original kernel via Odin. Everything was wonderful and I was the happiest guy in the world! One day later the button began behaving like a goast! as chronicpoetic mentioned.
I would like to try installing the new firmware via Odin, but I am afraid that if it's hardware problem, then it won't be taken by service.
Any suggestions?
sounds like hardware faults guys :/
Thank you for reply! I thougt it was too, but... read below
I found out something else.
The menu button works, but with an extreme long delay - 15-30 seconds! More often just right after screen unlock. It just appears and disappers 30 times if I pushed it 30 times before.
And still it can work just perfectly. Sometimes after connecting it to PC or charging it. That dosn't work like a rule.
I am trying to find the reason of such unusual behaviour, but I am lack of expirience.
Any help?
Hello man
I hope that my info will help you
I was in samfirmware.com site and i remembered your problem and i recall that you say Vodafone
so i saw "Provider Samsung I9100 Firmwares" and one of them looks like Vodafone firmware...... please see this site hope to helps you:
http://www.samfirmware.com/WEBPROTECT-i9100.htm
sorry for my bad english
Yeapp, I visited the partner of samsung service center, they said it was a hardware.
Same thing here, any progres?
Just revisited this post - I managed to get a hold of the original Vodafone Firmware from Intratech's thread, flashed it and returned the phone - turns out it was a hardware fault.
Vodafone promptly replaced mine folks.
Sent from my GT-I9100 using xda premium
I am at wits end. Got it rooted and everything, but used the wrong kernal. I had good sucess with my Captivate, so I tried a similar procedure. Unfortunetly, when I boot the phone I end up with "Can't acess to '/system/csc/ATT/system/'. I'm not sure if this is the right spot to post but at the risk of looking like an idiot, I'll beg
Edit: I do have access to download mode, and Odin.
Im sorry i cant help you, im not good enough, but i guess we (who's able to help) need more informations.
Model of your S2? i9100 or 9100g?
What kind of wrong kernel you flashed?
Is your phone a standard or a AT&T S2?
I think this infos can be very helpfull
It's the i777, the kernal was the XWKDD, and it's an AT&T. It worked fine, rooted, got Busybox and everything to work. But I noticed the back button didn't work, and the home button backed me up. To I attempted to install a ROM, and then it won't start. I got one installed, but it sits at the clockwork recovery screen. The power button won't function as OK, so I can't qipe the data.
Designgears has started a ATT sgs2 ROM. you can use that. http://forum.xda-developers.com/showthread.php?t=1286939
I discovered the 3-file way to do it in another thread, but this unfortunately leaves me back and my search button not functioning.
Edit: Fairly certain I turned it into the european version of the phone, since the 2 buttons don't work and the default clock is 24 hour.
As an update, I can get most things to work except I can't get the button configuration correct...which isn't an issue until I try to use CWM or something of that sort...any help to get the button config back to standard I777 would be GREATLY appreciated
Wrong forum!!!
Try here: http://forum.xda-developers.com/forumdisplay.php?f=1301
My apologies, I don't know my way around here like I do at OCN.
I've spent a couple days searching, but there doesn't appear to be a relevant enough thread to help me here, so I've resorted to asking for help, hopefully you guys can help me figure this out.
I got my girlfriend a used Telus SGH-T959D (same thing as the T-mobile version pretty well) several months back. It was on stock 2.1 and worked fine but was very laggy compared to my rooted HTC Desire on oxygen 2.3.2. So I rooted it and installed a 2.2 rom with Voodoo sound control (but no lagfix), and she's been using it this way for months now. It was better than stock but still laggy. I can't remember what rom it was but it was based on Samsuck firmware, hence why it's still laggy I guess.
For some reason, when I originally rooted it I had trouble with CWM recovery not installing, I can't even remember now what exactly was happening, but I managed to get the rom installed without a proper custom recovery, so when I go into recovery it's just the stock Samsung recovery, with no options for nandroid backup, restore, flash zip from sd card, etc. Basically I can't do anything useful in recovery.
Anyways lately, worse and worse she has been getting the Android text message to wrong recipient bug. If you aren't aware of it, it causes messages you sent to go to a different person in your text message message list. No it is not user error.
So I decided to try and data wipe. After this there is basically no launcher when it boots up. The notification pulldown is there and working, and it shows the phone has a signal and wifi is turning on and working, capacitive buttons light up when you press them, but you can't do anything except grab the pulldown.
It won't connect to USB when booted up, phone shows a message that you must close running processes first, or something like that. But I cannot flash a rom from recovery anyways, since it only brings up a stock recovery.
I can get it into download mode, if I hold my tongue just right and try several times, but not sure what to try to flash with Odin. I already downloaded an ICS Passion rom, but then reading the tutorial saw that I must first download CM7 and install that, then upgrade the bootloaders to the GB ones, then flash the ICS rom. I would really like to at least upgrade to 2.3 and something not based on Samsung fw, but the main priority is to get it working again.
Anyways, whatever you guys can suggest to try would be greatly appreciated. Thanks.
Honestly bro, everything I'm seeing in Google makes it seem like that phone is more on par with the Galaxy S Fascinate than with our Vibrant. Although on the exterior they all look so similar... I dunno, maybe check out their forums and see if you get anymore help there?
Here's the link:http://forum.xda-developers.com/forumdisplay.php?f=718
Goodluck!
The title of this thread looks similar to my problem with my Samsung Vibrant. So I would ask it here, too.
I'm not sure if I bricked my vibrant, it's still power up, only to to first screen, which has the words Vibrant (and) Samsung and stay there forever.
I first rooted my Vibrant successfully.
Then, I've followed the instructions below:
1. Download the latest version of the ROM from the original development page.
2. Transfer the downloaded zip file to the root of the internal SD card on your phone.
3. Turn off your phone and wait for complete shutdown (wait for capacitive button lights to go off).
4. Then, boot into Clockworkmod (CWM) recovery. To do so, press and hold these 3 buttons together: Volume Up, Volume Down, & the Power button till the screen turns on, then let go of the buttons. In recovery, use Volume keys to scroll up and down and power key to select an option.
5. Perform a full Wipe (this will not wipe your SD cards)
a. Wipe data / factory reset –> then Select Yes - Wipe data/Factory reset on the next screen.
b. Select “mounts and storage“, then select “format system” -> select “Yes” on next screen to confirm. Then, select “go back” to go back to the main recovery menu.
6. Now scroll to “Install zip from sdcard” and select it.
7. Select “Choose zip from sdcard”. Scroll to the file you transferred in Step 2 and select it.
8. Now confirm installation by selecting “Yes — Install **your_rom_file_name**.zip – The ROM will start installing.
9. The phone will reboot to recovery in the middle of the installation, then continue installing the ROM.
When I got to step 7, instead of running the zip file downloaded on step 1. I run the update.zip (something like that). And I couldn't get back to the CWM recovery screen anymore. Only I can boot it to the regular recovery screen, where it let you:
reboot the system
reinstall packages
delete all user data
delete cache data.
Or boot up to the screen described at the beginning of this post.
So what should/can do to fix this problem?
I think my phone is t959 (it's t-mobile Samsung Vibrant)
Thanks for the reply. As far as I thought the only similarity between this and the at t fascinate was the name fascinate. There's is the i5000 and mine is the t959d? Should this post be moved over there? I found a thread there with someone having partly. the same issue as mine not being able to install cwm but its been there for days and likely will not be replied to.
I've spent a lot of time trying to fix messed-up installs. Seems to me that if for any reason you can't rrflash the rom, or reflashing and wiping doesn't work, just Odin-ing back to JFD and going from there is the best bet.
Well I was about to go ahead and download stock JFD and try flashing that but it appears that Mega upload has been shutdown by the FBI for fraudulent activity, and Rapid share is not working either. Maybe they're too busy because of the mega Upload shutdown or they were owned by the same people and have also been shut down. So now I'm not sure where to even find files that are safe to flash.
I just spent another hour on here and Android forums, and basically all the the threads are one or two posts, with no resolution to the OP, and none of the downloads links anywhere are working. I'm pretty patient but I'm ready to give up. Does anyone want to trade a soft bricked T959D in mint condition for any old beatup HTC that works? I've had my fill of Samsung's now.
No trade sorry but if you want to donate shoot me a pm.
Before you dump it, give me some time to look into this and I'll see if I can get you up and running with some files. Sammys are way user friendly unless you aren't doing something right, then you could always go back to stock.
Hold the phone. Haha. I'll get back to you.
You too ciditin
Thanks Woodrube, I will definitely wait patiently as long as I know I'm going to be able to sort it out eventually. I'm busy with schoolwork so even though I enjoy this kind of thing I hate spending hours upon hours on it just trying to get the phone operational again.
I've been spoiled by my htc desire, it's been almost foolproof to do anything after spending a short time reading a few FAQ's and there have been no close calls. Soon I'll probably try an ICS rom once they get a bit more stable.
I will definitely do a donate if you can help me get it going with a decent rom. I would love to have lag fix on it since my girlfriend is a bit annoyed at the lag.
Since I got my first Android phone in August 2010, I've rooted and rom'd an LG Shine Plus, LG Optimus One, HTC Desire, the T959D and Galaxy S2 T989D (sold after I got it on an early renewal). I also had to fix my sisters I9000M after a failed 2.3 update operation. So I'm no expert on this, but I've got a little bit of experience messing around with stuff. Just they all require different processes, different programs to do the job, so you have to relearn it for every new phone.
The Samsung's have been the biggest pain compared to the others, but I think it's mostly because the Canadian versions are always slightly different than the Tmobile version, but besides that Samsung always has several different versions of the same.
If I get this thing up and running again I will probably check out your GPS fix thread, cause the GPS on this phone would lock on but it was way out to lunch. Like 6 streets away from us out to lunch.
I found the way to fix my problem, hopefully it'll fix yours.
I was able to restore my stock.
Here is what you have to do.
WARNING!!! THIS WILL WIPE ANY DATA ON YOUR DEVICE, IT WILL REPLACE YOUR BASEBAND, KERNEL, RECOVERY AND OS.
DOWNLOADS:
ODIN application
512 PIT file - I can't post link so pm me
T-Mobile Vibrant JFD Image – I can't post link so pm me
USB Drivers from the Samsung Galaxy S – 32 Bit Windows Download \ 64 Bit Windows Download (again I can't post link, yet)
INSTRUCTIONS:
1. Turn off your phone (remove battery, and usb cable to pc).
2. Plug usb cable to your phone (this is just for easy to connect to the PC in the next step), do NOT connect it to your pc just yet.
3. Get your phone into DOWNLOAD mode by holding the Volume Up, Volume down, and plug your usb cable to your PC. A yellow digging Android sign should be on the screen of your phone. This may take a few tries to get it right.
3. Launch ODIN.The third box dow from the top-left box should then say a COM port (the box under the top-left box should be yellow).
4. In ODIN, load each file with its corresponding field:
___a. Click PIT and select *.pit file extracting from the 512 PIT file above.
___b. Click PDA and select the *.tar, stock JFD file.
5. Don’t check anything else, the other two boxes should be checked by default (Auto Reboot and Reset Time)
6. Hit “start.” Be patient for a couple minutes! (The bar under the top left box should show the progress, and on you phone, too)
7. You should have your Vibrant back in with stock configuration.
Good luck!
NOTE: COM3 worked fine for me. COM should not matter as long as you are using the correct drivers.
350Rocket said:
I will definitely do a donate if you can help me get it going with a decent rom. I would love to have lag fix on it since my girlfriend is a bit annoyed at the lag.
Click to expand...
Click to collapse
Ok. I wasn't soliciting for a monetary donation, I was just going off that you wanted to trade. I can't trade but if you ever want to donate your phone then just PM me.
I have to agree with kawika that everything I have read has been that your model number is for the Fascinate. Easy tip off would be; does your phone have a sim card? It is probably a CDMA phone with no sim slot. I suggest getting the files you need from the Fascinate forums as I am almost positive that the T959 files will not work on the T959d. Since you have modded a I-9000m you know that they are slightly different than the I-9000. Same thing goes with this circumstance.
Good luck and sorry that there wasn't more I could do but it is just a different phone.
@Citidin - Good to see you got yours solved. If you have questions, please ask (in the correct thread for your question a this one will probably be closed out).
It definitely has a sim card and it's HSPA, I pulled the Sim card out and put it in my HTC Desire for her to use, and put my SIM card in this crappy little LG Optimus One that's too small for me to type on. So I guarantee it has a sim card and is nothing like the Verizon phones which will not work on any of the Canadian carriers AFAIK. I think nobody understands what the phone is, and that's why almost every thread with a problem like this ends in 0 replies. I think from now on I will stay away from Samsung's abortion phones that they sell in Canada. Or at least I will research community support before getting one.
Ours is called the Fascinate, but its completely different model # than theirs, it is the T959D. Just like how the new Telus galaxy S2x is the T989D, same phone as the T mobile T989_.
For some reason there seems to be a few posts in the Fascinate section, for Telus only, I think that only started because of confusion about what the phone was, but the phone has nothing in common with the Verizon CDMA version. Actually I think if you look up, just about every phone that Telus or Bell (same network basically) gets, is a phone that T mobile got first. HTC Amaze being another one. HTC Desire Z is the same as the Tmobile G2.
Sorry I misunderstood you about donating the phone itself. My last effort will be the JFD file that Citidin sent me a link to. Hopefully that gets it going. If not I will stash it away until I have extra time to try again.
Well once I got the JFD file downloaded and put phone in download mode, turned on Odin, realized the PC recognizes the device attached and being malfunctioned, so I cannot flash with Odin.
I tried Heimdall which I downloaded yesterday, but the program won't load as it says I'm missing a DLL file.
I tried Android flasher which I downloaded who knows when, and tried to just install a recovery image with it, but it gets stuck while pushing recovery image and the program locks up.
I decided to try my girlfriends Laptop instead of mine after maybe 40 failed attempts to get Odin to communicate on mine, and to my surprise it recognized it right away. I transferred my files, with the JFD to this computer and then flashed with Odin. It took about 2 minutes and it was up and running. I checked about phone and it said 2.3.3 firmware. Really confused I looked back at odin and realized I flashed the I9000M stock 2.3.3 firmware (KG3) that I flashed on my sisters phone back around xmas. I forgot I did that on this laptop.
Anyways it is working as it should except for the home button not working (which I had already read about in a thread about using I9000M or Vibrant roms on the T959D).
While it is unfortunately stock again, the 2.3.3 should fix the original problem of sending to texts to the wrong recipient, and it also seems a lot less laggy. I think I'll just let her try it as is and hope she is happy.
If you use the JFD file from the link I sent you, it should be the stock Tmobile Vibrant.
Similar problem
Sorry dont mean to hijack your thread but I think I am having a similar problem - posted in the wrong spot before so hopefully I am ok here...
Have a Vibrant and some how got crossed up on it.
I have been able to use Odin to update the phone, however after it says its done, it does a reboot as it supposed to, shows the samsung screen then just shuts down.
After about a hundred tries, someone pointed me to Eugene's no brick. I tried that and it will fix it so it will boot and go into recovery, but I can't seem to do much once I get there. My only options are to update, wide data and wipe cache. Can't get to the point where I can load an update onto the unit.
I tried wide data and reset, then reboot. It shows the samsung vibrant logo, then the splash screen, then the big S and then screen goes black and the cap buttons stay lit.
If I try to go back and load the stock pit and jfd file, it just goes back to not booting at all and shutting down after the logo
I cant seem to get it into recovery unless I do Eugene's fix
In one of my earlier attempts, I did check to repartition as direct in one of the other threads - been chasing this a while now!
Edit: It was originally a bell phone - does this matter?
If it was a Bell phone than it should be the I9000M. It sounds like your problem is a bit different than mine was. I was able to get into recovery mode and download mode just fine. I just didn't know which files to flash with.
I intended to flash the JFD that citidin sent me, but I accidentally use the KJ3 (latest I9000M 2.3.3 firmware). The I9000 and Vibrant roms are compatible with the T959D Telus Fascinate though, only problem being no home or search button.
It sounds like the Eugene thing (whatever that is, I'm not familiar) gets you into stock recovery. Like my original issue, you cannot flash or mount the sd card, or much of anything with the stock recovery.
Do you know that the file your flashing is compatible with your phone (the I9000M I assume)? More info that would probably help, is what firmware did you have on it before, was it JFD? What update did you try on it? Bootloader version - there are gingerbread bootloaders, and froyo bootloaders I think?
Have you tried different files other than the one that doesn't seem to boot up for you? I think most of the tutorials I've looked at, said not to check repartition. When i finally got this T959D working with the I9000 rom I did not check repartition and did not select a pit file, just the PDA, phone, CSC.
Yes it is a I9000M - I was trying to load the JFD tar file along with the 512 pit file. I followed a thread in the I9000 section and loaded a JPD tar file onto it, now it shows up as a I9000B - maybe I should stop
I can now get into recovery and or download (i think the steps are differant than hold both volume buttons - mine is holding the volume one way for recovery and the other way for download, along with home and power)
Wondering if I am in this bind because it isnt really what most are calling a Vibrant - maybe under Bell it is something else.
Bootloader? didn't know I had to do anything there
I just picked up the phone used from someone - I assumed it was stock and didn't do a good check to see what was on it.
I9000m is not the Vibrate but rather the Bell version of the Captivate. There is a dev section for the I9000m in the I9000 group.
I would definately stop what you are doing and read over there.
******
Also 350 you can re-map your keys to work but I am mobile now and cant search it for you. Reason being that the. Vibrant keys are laid out differently in, ahh can't think right niece where they are, but it is fixable. Just search key remap or remapping.
Thanks very much for the help - have to wonder why they cant call them the same names regardless of where they are sold - guess thats why they get the big bucks
Hello!
I'm a newbie and I really need help with my bricked(?) phone. First a short intro to how the problem came to be:
I own an old (but I still love it) and extremely rare phone, the original Samsung Galaxy Beam (I8520).
There is no official update for it, so it is stuck on Android 2.1.
The thing I miss is Netflix, and Netflix officially only supports 2.2+, so I thought I could try to fool Netflix into running anyway by editing puild.prop.
But to be safe, I used an app called Device Spoofer. In this I could try different model infos by selecting different phones in a list.
I tried a couple and found one it would except. Then it required a reboot, I believe, and now my phone won't start up.
I get to the Samsung logo and then a Starhub carrier logo, as usual, and then the phone just turns black.
There is supposed to be a way to get into download mode by holding some buttons, but that doesn't work on my phone. I have read something about it being a bug on some Samsung models. But anyway, I have bought one of those usb sticks that puts the phone into download mode, and it works.
I have tried to use ADB, but it doesn't seem to find my phone. I also tried to flash a firmware to the phone, but that doesn't work either, Odin gets stuck at "SetupConnection..". The only firmware I have found online is one called I8520STHJI1.tar, which is the last firmware version made for the phone and the version that is factory installed on my phone.
The I8520STHJI1.tar contains the following files:
cache.rfs
modem.bin
ramdisk.img
SS_DL.dll
system.rfs
userdata.rfs
zImage.img
Is there anything that can be done?
Thank you!
After googling, it seems that I need a certain version Odin to be able to flash the i8520.
What I need is Multi Downloader v.1.7.3L
Does anybody have that?
Hi all,
I am stuck. Here is my sad story.
I have an ATT S7 that I was attempting to load the S7 Tmobile image using Odin. After hitting the encryption error in odin, my searching led to the PrinceComsey version and that got around that problem. I then hit a Fail(Auth) error and tried a few other suggestions that I found. The last part I tired as ticking the "update phone bootloader" option. Odin failed again, this time, the phone was stuck in recovery menu loop. I tried to clear and restore to factory settings, but couldn't get out the loop. Finally, it stopped booting the base menu and now I get the wonderful blue screen exclamation mark that tells me I need to use Samsung's Emergency recovery. I can't even turn the device off now. The only other thing I can get it to do is to get to the download screen.
From all I have read, it seems the next step is to upload a valid stock image with Odin and that should be that. So that's where I am stuck. I have tried a couple different images, but they all fail in one way or another. I think what I need help with is figuring out which image is the right one to install. At this point I just want to get back to a working phone, so an ATT image is fine for now, but would ultimately want to get to a Tmobile image now that I have switched carries.
Any help is much appreciated!
Use smartswitch to restore stock software.
Also, try to use the right forum , you probably get more help
Oh dang... I claim temporary insanity for putting this in the S6 forum. ugh.
In any case, thanks for the response. I got it all figured out. Here are some tidbits in case it is helpful to someone in the future.
1) Yes I tried the emergency recovery using smart switch. It turns out that you need the device serial number. It also turns out that on my ATT supplied S7, there is no s/n etched on the back. And just for laughs, it isn't even printed on the original box. So if you do not have it written down and your device isn't functioning. You are SOL.
2) After several failed attempts, the magic formula was the modified Odin and the Jan'17 SM-G390T build that I found. I selected all four files for flashing and the n-th time was the charm.
3) I am now running the Tmobile build of Nougat on my ATT S7 with everything working as it should. That includes the phone using the tmobile signal booster that the ATT build couldn't find and has wifi calling available. It is exactly as I wanted.