Hi everyone, new here and a complete noob hopefully i'm posting in the right place and i don't sound too thick.
A colleague of mine has the S2 and it seems as if the OS is corrupted. The phone boots but on the home screen she is bombarded with continuous messages about a process failing and having to stop.
There is a whole load of photos on the phone she would like to retrieve which leads me into the second issue, despite the fact the phone will charge, USB connectivity to the computer is not working and saying the device is not recognized. i have installed Kies as well as the MTP driver to no sucess. More over the phone via USB keeps on disconnecting/reconnecting every few seconds.
All this leads me to my questions
Would it be possible to re-flash the stock firmware via an SD card in recovery or odin mode?
Would doing so (if possible & successful) keep the pictures or will this be erased?
Open to suggestions anyone may have and thanks in advance.
Yes, try flashing a stock rom with Odin first in download mode. No, flashing a one part firmware will not erase her stuff normally, though I'm not the type of person to give 100% guarantees on anything phone-related.
Sounds like a dodgy USB board/port which is on the way out will probably make it hard to do an Odin flash of stock though. What you've described definitely sounds like it's on the fritz. If you can't get a successful stock flash after trying absolutely everything & those USB issues persist/seem to be the problem, replace the USB board/port. This is quick/cheap (maybe US$10, often less)/easy to do yourself. If you decide to do this, search for KeithRoss39's guide in the General section (do an advanced search on his username), this thread has all the info you need to get it done.
This should enable you to get a successful stock flash & hopefully fix the issues assuming it's not something else hardware-wise, which you're only going to find out by doing these things first. If you have trouble getting a flash away once you've replaced the board/port (and even before you do that), search for Hopper8's 'Odin troubleshooting' thread & try the stuff suggested in the thread.
MistahBungle said:
Yes, try flashing a stock rom with Odin first in download mode. No, flashing a one part firmware will not erase her stuff normally, though I'm not the type of person to give 100% guarantees on anything phone-related.
Sounds like a dodgy USB board/port which is on the way out will probably make it hard to do an Odin flash of stock though. What you've described definitely sounds like it's on the fritz. If you can't get a successful stock flash after trying absolutely everything & those USB issues persist/seem to be the problem, replace the USB board/port. This is quick/cheap (maybe US$10, often less)/easy to do yourself. If you decide to do this, search for KeithRoss39's guide in the General section (do an advanced search on his username), this thread has all the info you need to get it done.
This should enable you to get a successful stock flash & hopefully fix the issues assuming it's not something else hardware-wise, which you're only going to find out by doing these things first. If you have trouble getting a flash away once you've replaced the board/port (and even before you do that), search for Hopper8's 'Odin troubleshooting' thread & try the stuff suggested in the thread.
Click to expand...
Click to collapse
Thanks for the swift reply.
Just took a quick look at KeithRoss39's guide and the micro USB replacement vid and it does seem quite easy and inexpensive to do.
The photos are her main concern and i don't want to attempt flashing her phone as it currently is considering the very temperamental state the USB connection is in.
I'll mull over this option with her as ironically it seems to be the safest route to go down.
Thanks very much for your help mate:highfive:
You should be fine, there shouldn't be any data loss. But I'm not going to be one of those people that tells you flashing a phone is entirely risk free. Because it isn't. As long as everything is working as it should be (PC with reliable USB ports, phone USB port working normally), the risk of any individual flash going bad is very very small.
No worries Let us know how you go/if you get stuck/etc.
Related
I got my GSII on launch day and here in the past couple days my phone won't charge. I can put it in the dock and it goes into carmode and if I have the jig it it will recognize it when i reboot into download mode.
Is there anything I can do to fix it?
AT&T wants me to take it to a corp store to make sure it isn't damaged before they will exchange it, but I am running AOKP right now and I can't get it connected to my computer to flash a GB rom. Any help would be greatly appreciated.
dekkon said:
I got my GSII on launch day and here in the past couple days my phone won't charge. I can put it in the dock and it goes into carmode and if I have the jig it it will recognize it when i reboot into download mode.
Is there anything I can do to fix it?
AT&T wants me to take it to a corp store to make sure it isn't damaged before they will exchange it, but I am running AOKP right now and I can't get it connected to my computer to flash a GB rom. Any help would be greatly appreciated.
Click to expand...
Click to collapse
If I were you and intending to take it back to the manufacturer, I'd make sure the flash counter is reset (There could be a yellow triangle when you power on your phone or not, don't send it back to them with aokp on it I warn you of this.)
If you are using a linux based enviroment you could use heimdall to flash a kernel that would give you CWM back, and also if your linux and adb is there, you could mount usb storage and attach some rom that'd be 2.3 related.
From there, while in recovery still, I would format /system /data /datadata /cache, reboot recovery (under advanced, not 3 button.) Then I'd install the 2.3 zip and modem and boot it up.
Now you are back on gingerbread, but to send it back you need complete stock.
You could heimdall flash the stock firmware and would be set.
If your using windows make sure the correct drivers are installed, download is vol up+down no power button, make sure odin is open before plugged in, then connect your phone and you should be set.
I don't know your desktop enviroment but I hope this helped.
Have a good day
Thank you for your help, but I guess I should have clarified something in my original post. I can't get any computer to recognize the phone. If it weren't for the fact that the dock and usb jib are recognized, I'd think the usb port was completely dead.
I thought it might be the rom/kernel I'm running (AOKP/Siyah) but even when it is turned off I can't get it to start charging. Luckily I have an external dock charger and an extra battery I can use to keep it powered up
dekkon said:
Thank you for your help, but I guess I should have clarified something in my original post. I can't get any computer to recognize the phone. If it weren't for the fact that the dock and usb jib are recognized, I'd think the usb port was completely dead.
I thought it might be the rom/kernel I'm running (AOKP/Siyah) but even when it is turned off I can't get it to start charging. Luckily I have an external dock charger and an extra battery I can use to keep it powered up
Click to expand...
Click to collapse
Heartbreak.
I had this problem with a Captivate, never did figure out a solution (link below). I ended up getting an insurance claim denied (which was 100% my fault since I didn't know the rules and unwittingly told them I was attempting to claim outside the 30 day window) so I invoked the "I'm a 10 year customer and I've never asked for anything" clause and was granted a very early upgrade to get a GS2. It was very frustrating and disappointing. I'm nowhere near an expert but I searched for weeks and I couldn't find anyone else with the same problem. It actually looks like a few others have had something similar happen since I gave up and stopped checking my thread but no obvious solutions so far.
Anyway I hope you have better luck than I did but if nothing else, I hope it helps to know you're not completely alone with having had this problem.
http://forum.xda-developers.com/showthread.php?t=994567
Well, this is what I would do:
Flash your very first Nandroid (should be a stock OS with custom Kernel), then you just need to flash the Kernel back to stock, follow this post http://forum.xda-developers.com/showthread.php?t=1602761 to flash a Kernel with Mobile Odin.
If you don't have a GB Nandroid, things are a little more complicated, but not terribly so. IF your flash counter has not been toggled, I'd try the following:
Download the stock image from this thread http://forum.xda-developers.com/showthread.php?p=18630030#post18630030 and again use Mobile Odin to flash back to GB. Download the image to Dropbox, and unzip it there, use the Dropbox app on your phone to move all the files to the root of your SD card (or would it be the internal card? Not sure, never done this before). This way you get the files on your phone and can return to stock with Mobile Odin.
If your flash counter has incremented, you'll need to try your jig when you get back to stock and see if it clears the counter. If not, it's a bit more complicated, you'll need to flash an older version of GB 2.3.4 AND the bootloaders (flashing bootloader ***WARNING***, if ANYTHING goes wrong with this process, you hard brick your phone, flashing bootloaders is NOT recommended) once you have the old bootloader flashed, you can use the jig, take the OTA update if you want or just return the phone. Don't forget to do a factory reset and remove your SD Card.
Wink
---------- Post added at 12:06 PM ---------- Previous post was at 12:03 PM ----------
Another thing you might try that some have reported success with, use a q-tip with a bit of alcohol on your USB port, and try a new cable, you might just get lucky and get one more connection out of it, in which case you could use the standard return to stock methods outlined here http://forum.xda-developers.com/showthread.php?p=18630030#post18630030
Paper clip to readjust your port if your comfortable doing that. Not a great option but it has saved my phone twice when alcohol wouldn't
Sent from my SGH-I777 using Tapatalk 2
nyamoV2 said:
Paper clip to readjust your port if your comfortable doing that. Not a great option but it has saved my phone twice when alcohol wouldn't
Sent from my SGH-I777 using Tapatalk 2
Click to expand...
Click to collapse
Good thinking! I keep dental tools on hand for such occasions, but a paperclip! What good thinking!
+ 1 cookie!
Wink
1. My phone wont boot .. gets stuck at The S2 GT-I9100 logo stuff.
2. When trying to get in to recovery it says: "E:Can't mount /cache/recovery/command"
3. I can get in to download mode though
4. My computer wont recognise the phone in either recovery or download mode. It says its a "Universal Serial Bus (USB) Controller" in device manager.
5. Yes, i've installed the Samsung USB drivers. Uninstalled/reinstalled them 100 times. Not running Kies. Tried rebooting computer.
6. Tried shifting cables, ports and so on.
Any other suggestion? I think its bricked ... or?
Try another PC maybe?
Sounds like a driver's conflict.
Sent from the little guy
gastonw said:
Try another PC maybe?
Sounds like a driver's conflict.
Sent from the little guy
Click to expand...
Click to collapse
Will try later, too tired now .. been fiddling with it for 12 hours now. I think i'm getting ready to go to a mental instutition. I need my phone! I got a retarded old LG as a backup now.
Pop up a Valium, it'll help you thru.
Sent from the little guy
It could connect fine on another computer. But i couldnt find a stock rom that ODIN would write to it. It always said something about write failure.
Any suggestions?
Keep trying. In a lot of these cases, you'll try 9 Odin flashes (as an example) & they all fail, and for one reason or another the 10th works.
Look for Hopper8's 'Odin won't work' thread. There will be stuff in that thread you haven't tried yet. Basically it's a case of perseverance unless you want to take it to a service centre.
MistahBungle said:
Keep trying. In a lot of these cases, you'll try 9 Odin flashes (as an example) & they all fail, and for one reason or another the 10th works.
Look for Hopper8's 'Odin won't work' thread. There will be stuff in that thread you haven't tried yet. Basically it's a case of perseverance unless you want to take it to a service centre.
Click to expand...
Click to collapse
I'll keep trying. No way im gonna pay for it when i know i can do it myself (warranty expired) But thats gonna be tomorrow .. thinking about reinstalling windows on my own computer to get the Samsung Drivers working on my own, so i dont have to go to some one else each time i feel like trying
You wouldn't have the link to the thread? There are like a million odin threads
Nevermind i found it
Hi
I just can't seem to get Odin to flash my S2. I am new to android hacking but I'm no 'tech-tard'. I have read a lot the Odin related threads on here and on google and can't seem to get it to work. I'll explain what I'm trying to do and what I have done so far.
What I want to do is to setup my old S2 for my mum, she is Vietnamese and would be great to have Vietnamese Language support so that menus, etc..are in Vietnamese! I have tried some locale apps but they're very limited. So basically I want to flash the phone with a firmware which has Vietnamese.
My phone is a UK Vodafone S2 and it's fully updated. The info on the phone is as follows:
Model Number GT-I9100
Android Version 4.1.2
Baseband Version I9100BULS3
Kernel Version 3.1.31-1484249
[email protected]#3
SMP PREEMPT Tue Dec 3 20:24:29
KST 2013
Build Number JZ054K.I9100XWMS2
I have installed Kies, have got MTP drivers installed and have got samsung usb drivers installed (v1.5.33.0). I have Odin 1.85, 3.07 and 3.09. One thing to note is that I have never been able to connect to Kies even though all the drivers are installed and working as I can access the phone via windows explorer.
The firmware I've been trying to flash is I9100DXLSD_I9100OLBLSD_I9100DXLS8_HOME.tar.md5 This firmware also came with SS_DL.dll (i'm not sure what I'm suppose to do with this file)
I have tried using the original S2 usb cable, S4 usb cable, HTC usb cable and Nexus 7 usb cable. I have tried the front and rear USB ports on my pc (although have yet to try every single rear usb port)
I think I have done clean installs of Kies and the USB drivers, by using YourUninstaller to remove them and clean up the registry, reboot. Reinstalling Kies and USB drivers and rebooting again.
I've turned on USB debugging on the phone. The phone is in download mode. I start up Odin as admin, plug the phone in and Odin sees the phone and I get the messages 'Added!' and COMx where x is 3, 4 or 5. In Odin 3.07 or 3.09 when loading the firmware, the firmware is confirmed ok but when flash is started it stalls at 'SetupConnection'. I've left it for about 15 mins and still stuck there. In Odin 1.85 it's similar except I eventually get a FAIL after the SetupConnection step.
I'm not sure what else I can do, apart form try another computer. Any help would be much appreciated.
Thanks
Q
take a look at hopper8's odin troubleshooting thread stickied in general section
TheImpossibleEnemy said:
take a look at hopper8's odin troubleshooting thread stickied in general section
Click to expand...
Click to collapse
Yeah, I've read that and followed it and still no luck.
That thread is the 'Bible' for these situations; there really isn't much else that isn't in the thread which can be suggested in these situations.
So...Your options are:-
*Try everything (you haven't done that yet) in the thread over and over and over and over until you get a successful flash. When these are recoverable (and the majority are), they're almost always fixed with perseverance.
*Give up & take your phone to a Samsung service centre (who will take a lot of your money) or a local mobile repair shop (who will charge you a bit less money) for diagnosis/repair. Obviously you're in their hands with regard to trusting them to honestly diagnose what's wrong & charge you accordingly.
The only other thing which comes to mind in this situation is an idea KeithRoss39 has bandied about recently; flash fails in this situation are sometimes caused by a malfunctioning USB board in the phone (this has become a very common fault with this phone as the time since it's initial release has increased).
Thing is, if this is indeed the case here, it's possible that your previous attempts at flashing have already corrupted the NAND, and only a motherboard replacement is fixing this. If this hasn't already happened & the board is faulty, any further flashing attempts might give you this result. But unless you know how to diagnose electronics like this, you have no way of knowing whether this is the case or not.
So, you can proceed as above, or you can stop attempting to flash right now & replace the USB board/port yourself before you attempt any further flashes. Keith has a guide in General (not stickied, there's a link in Hopper's thread) which will enable you to get this done quickly/easily/cheaply yourself if you decide to go down this path.
delete
MistahBungle said:
That thread is the 'Bible' for these situations; there really isn't much else that isn't in the thread which can be suggested in these situations.
So...Your options are:-
*Try everything (you haven't done that yet) in the thread over and over and over and over until you get a successful flash. When these are recoverable (and the majority are), they're almost always fixed with perseverance.
*Give up & take your phone to a Samsung service centre (who will take a lot of your money) or a local mobile repair shop (who will charge you a bit less money) for diagnosis/repair. Obviously you're in their hands with regard to trusting them to honestly diagnose what's wrong & charge you accordingly.
The only other thing which comes to mind in this situation is an idea KeithRoss39 has bandied about recently; flash fails in this situation are sometimes caused by a malfunctioning USB board in the phone (this has become a very common fault with this phone as the time since it's initial release has increased).
Thing is, if this is indeed the case here, it's possible that your previous attempts at flashing have already corrupted the NAND, and only a motherboard replacement is fixing this. If this hasn't already happened & the board is faulty, any further flashing attempts might give you this result. But unless you know how to diagnose electronics like this, you have no way of knowing whether this is the case or not.
So, you can proceed as above, or you can stop attempting to flash right now & replace the USB board/port yourself before you attempt any further flashes. Keith has a guide in General (not stickied, there's a link in Hopper's thread) which will enable you to get this done quickly/easily/cheaply yourself if you decide to go down this path.
Click to expand...
Click to collapse
I don't think the USB board is faulty. It charges fine and I can access the phone via windows explorer, transferring and copying files.
You try uninstall all drivers (kies and samsung usb) ,and install again only a usb drivers (without kies).
^^^
Didn't bother to read the OP, eh ?
Download Odin v3.07 And Connect your phone to pc using download mode. ( Power + Vol. D + Home ). And in odin click pda and choose ur downloaded tar file. Just let it flash. And see. Try Splitting that .tar file to CSC, PDA, MODEM using splitfus. Check google for further help.
Hit thanks if I helped you
Sent from my GT-I9100 using XDA Premium 4 mobile app
Someone else who didn't read the OP. Fantastic.
Bullit Lee said:
Download Odin v3.07 And Connect your phone to pc using download mode. ( Power + Vol. D + Home ). And in odin click pda and choose ur downloaded tar file. Just let it flash. And see. Try Splitting that .tar file to CSC, PDA, MODEM using splitfus. Check google for further help.
Hit thanks if I helped you
Sent from my GT-I9100 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I'll give that a shot.
Been reading about the default recovery console. Is it possible to flash the vietnamese 4.1.2 firmware over my uk 4.1.2 firmware using ADB? From what I've ready you could transfer the firmware to a memory card and use the apply update from external storage? Is this correct or would would it have to be done via ADB sideload from the SDK?
Thanks
Can't be done with stock on the S2 to the best of my knowledge (can with some other phones).
Sir, pls help me
i was using cm11 snapshot when this happened
i wiped data/factory reset my phone because i want to change to other rom
but after i wiped data i forgot to install new rom and i clicked reboot system now
after that my phone only show galaxy s2 text then goes blank then galaxy s2 text and repeatedly
i cant enter recovery mode, odin didnt recognize my phone because i didnt tick debugging mode because i cant see debugging mode after i updated to cm11 and i cant even do a hard reset through physical key
pls help me.. am i doing wrong?
i tried odin in windows 8
help me guys T_T
You don't need to have USB debugging on to flash with Odin; Odin operates at a 'lower level' than that.
Find Hopper8's 'Odin troubleshooting' thread stickied in General & go through the troubleshooting steps methodically/as many times as you need to in order to get a successful flash.
MistahBungle said:
You don't need to have USB debugging on to flash with Odin; Odin operates at a 'lower level' than that.
Find Hopper8's 'Odin troubleshooting' thread stickied in General & go through the troubleshooting steps methodically/as many times as you need to in order to get a successful flash.
Click to expand...
Click to collapse
i tried and once detected, i try to flash but failed
it says "Can't open the serial(COM) port."
any idea sir?
Go through all the troubleshooting steps in that thread one by one; if you do this, you will solve whatever is stopping your phone & PC from recognising each other.
Edit - Only hint I'm giving you (because the whole purpose of having a thread like that is so people like me don't have to go through this stuff over & over with people for the 8,963rd time over the past 2.5 yrs) - in your case; start with different USB cables (particularly the one that came with the phone/original Samsung cables) & different USB ports on the PC (no hubs - use mainboard ports only). These are for starters. If they don't work then you go through everything else in the thread one by one.
Right. No more hints, everything you need to fix your phone is in that thread.
MistahBungle said:
Go through all the troubleshooting steps in that thread one by one; if you do this, you will solve whatever is stopping your phone & PC from recognising each other.
Edit - Only hint I'm giving you (because the whole purpose of having a thread like that is so people like me don't have to go through this stuff over & over with people for the 8,963rd time over the past 2.5 yrs) - in your case; start with different USB cables (particularly the one that came with the phone/original Samsung cables) & different USB ports on the PC (no hubs - use mainboard ports only). These are for starters. If they don't work then you go through everything else in the thread one by one.
Right. No more hints, everything you need to fix your phone is in that thread.
Click to expand...
Click to collapse
tried everything and no luck
is it possible that my phone has mini-usb port error?
because it takes about 2 seconds delay to respong carghing when i plug it in
It's possible, yes. Only way you're going to know if this is the case/not is by replacing it (the entire board, not just the port itself) though. It's certainly quick/cheap to do yourself, so you don't have a great deal to lose by replacing it (apart from ~US$10) & seeing if this fixes the issue. Search for KeithRoss39's guide in General (search specifically for 'replacing USB charger board'), has all the info you need to help you get this done.
MistahBungle said:
It's possible, yes. Only way you're going to know if this is the case/not is by replacing it (the entire board, not just the port itself) though. It's certainly quick/cheap to do yourself, so you don't have a great deal to lose by replacing it (apart from ~US$10) & seeing if this fixes the issue. Search for KeithRoss39's guide in General (search specifically for 'replacing USB charger board'), has all the info you need to help you get this done.
Click to expand...
Click to collapse
sent my phone to service already because i just newbie who only know about flashing-recovery-download mode, didnt know about hardware at all
anyway, thanks for helping me :laugh:
Hello everyone!
I tried to Upgrade this S2 i9100 phone from android 2.3 to 4.1.2. I used ODIN 1.87 and I9100XWMS3 ROM. when I started ODIN to flash the ROM it stucked in connecting or something like that for a long time, so i unplugged the cable and removed the battery. after that I can't turn on the phone, or go to Download/Recovery mode and anything I do just the first picture appears.
So is it Bricked or something?
is there any soulution?
when plug it to pc and open ODIN, it recognizes the phone. and when I try to flash the ROM it fails (like the second picture).
Probably not bricked; that picture of the phone/PC on the screen means the phone is in forced download mode. One way or another you need to get a successful Odin flash, and the way you do that is find Hopper8's 'Odin troubleshooting' thread stickied in General & go through the troubleshooting steps in a methodical way as many times as you need to until you do get a successful flash.
MistahBungle said:
Probably not bricked; that picture of the phone/PC on the screen means the phone is in forced download mode. One way or another you need to get a successful Odin flash, and the way you do that is find Hopper8's 'Odin troubleshooting' thread stickied in General & go through the troubleshooting steps in a methodical way as many times as you need to until you do get a successful flash.
Click to expand...
Click to collapse
Thanks man. I was freaked out, because it's someone else's phone. when you said it's a forced download mode, I thought there must be some way. and I've found the solution here:
http://forum.xda-developers.com/galaxy-s2/general/repair-i9100g-samsung-galaxy-s2-flashed-t1448765
I just thought that the Phone was a i9100 like my old one, but it turned out to be a i9100G. So originally a wrong firmware caused the problem. and the pit file in that topic solved it.
Thanks again man.
Good work figuring out what caused the problem & doing the research/fixing yourself