Hey all,
----- TL;DR Version ------
Phone crashed.
Galaxy S logo looping on startup.
No recovery mode, only download mode.
Tried all steps in http://forum.xda-developers.com/showthread.php?t=1457458,
Even tried pit file.
Odin cannot write *anything*, phone shows no change on display or after reboot.
-------------------------------------
Long term fan, first time poster. I use a rooted Galaxy S2 running a custom rom (I bought it this way) that I really didn't pay much attention to, it was working beautifully for nearly a year. I have flashed phones in the past successfully as a long term android user - but have no real experience beyond that.
I was using it the other night, when all the sudden many many programs stopped responding while I had an incoming phone call that I couldn't answer. I tried to remove the battery as it was hardlocked but when I went to boot it back up it stuck at my carriers logo, then the Galaxy S logo looping continually.
Recovery mode is also not accessible (as that seems to load beyond the point of that logo playing - where it locks).
I've read through the guide below extensively, and have tried all the steps in combinatination with several other roms from the links provided in it, http://samfirmware.com/, and various posts on this forum - as well as one that has been shown to work on the exact model and carrier (even purchased around the same time) in my country..
http://forum.xda-developers.com/showthread.php?t=1457458
I can get to download mode - but the problem seems to be that no matter what Odin tries - it cannot actually write ANY data (even a .pit file attempt failed to make any changes - even if the change were to be bricking my device lol..)
I've also tried two USB cables in different USB ports as the article suggests..
Thoughts? Suggestions? Time to find someone with a jtag in Australia?
Many thanks,
Hajuu
Given you've well & truly done your homework (which is a refreshing change from the 'Hlap mai fone broked !' threads we normally see here which contain no detail whatsoever), sounds borked. I would link you to a partition scanner which may have been useful if you had recovery, but that obviously isn't an option for you.
Someone posted a thread in here maybe a week/two weeks ago there was a place in Sydney that did JTAGs (might be quicker than sending it OS). Alternatively, start calling mobile repair places in your area, might find one that does JTAGs. Or, try this site, might give you a headstart.
Also, I'd keep trying the below steps (and with a 2nd/3rd PC if possible) in the meantime. You never know, you might get lucky
Stuff to try when Odin doesn't work
-------------------------------------------------------
*Must run Odin as administrator in Windoze.
*Ensure Kies & it's processes aren't running in Windoze task manager. Kill them if they are.
*Try different USB ports; you must be using a 'powered' or mainboard port.
*Try different USB cables (particularly the cable that came with the phone if you're not using it now)
*Try different versions of Odin (search on here/Google)
*Uninstall Kies, reboot, redownload & reinstall it, reboot, try the flash again.
*Check the rom/kernel you download for corruption. Programs like 7Zip, IZarc, WinRar, etc will allow you to 'test' the rom file you download. If there are any errors/any of the files fail the test, bad download. Try again/try downloading with a different internet connection if it keeps happening.
*Run Windoze Update.
*And if all this fails, try a different PC. And then try all the above steps on the 2nd PC if necessary.
Well, thanks anyway - i'll take that to pretty much mean "Yeah.. You're going to have to jtag it" haha ^_^
I find it risky to invest probably $50-100 minimum to send it somewhere, when it might not even help at all (it could always be a hardware fault with the memory), Thus doing it myself seems the best option
I found some gear for about 160 euro - but I don't really know much about how it's supposed to work..
I don't know what kind of rom or anything you'd need or what kind of software to use.. My basic understanding is that it's a direct interface to the memory, where you're doing a complete sector by sector rewrite, so I wouldn't imagine you'd use the standard .tar.md5 type thing
How is doing it yourself the best option.I can get my phone jtagged for £25,and if it doesnt work then I only pay postage.
Attempting to do it yourself will almost certainly guarantee you'll:-
a) Waste €160 on something you more than likely will never use again and
b) More than certainly end up having to get a new phone because you'll bork your SGS2 so badly.
If it can't be JTAG'd, all you're paying is postage. Whoopdedoo. And besides, who says it can be JTAG'd anyway ? It may be able to be. You're only going to find that out if/when someone who knows what they're doing & has the gear takes a look at it. If it can't bet JTAG'd, then you're looking at a MB replacement (either from a donor phone or a new one from Samsung/authorised repairer)
If I were in your situation, I wouldn't be tempting fate. I'd either be paying postage to/from a JTAG repairer, or getting a new phone.
"Most places will only charge postage if they can't fix it" probably would have sufficed heh.. I never claimed to know a lot about it, just weighing up my options.
Thanks for the information anyway, I will be sending it off to a place I found today.
Related
I have a problem with Galaxy s2. Basically it started to drain my battery like hell.
It gets empty in about 10 hours.
Now when I want to flash the phone once again in order to get everything back as it was when I bought it I cannot. This is due to MTP connection activating itself as soon as I turn on the phone. And I cannot enable usb debugging due to that as it says that I have to remove the USB cable.
In addition my phone charges itself really fast about 2 hours. And when I try to power it on without charger plugged in it gives me charging image and yellow triangle with ! in it and thermometer aside flickering. Does anyone have any ideas how to fix my phone?
Have you tried using CWM to wipe all data + clear all cache, then do a fresh re-install?
Yes I tried it now. It still says my USB is connected when its not. And now it doesnt unlock my sim card.
Factory reset that dont work return phone to a service centre ..
jje
Well thats the case I have voided warranty already. Wondering if there are any chances I could put old rom back before returning it?
Make a DIY USB JIG then flash it back to stock rom and have it checked.
EarlZ said:
Make a DIY USB JIG then flash it back to stock rom and have it checked.
Click to expand...
Click to collapse
Not sure what do you mean by DIY USB JIG but I cannot flash it because I cannot switch USB debugging on... Thats the case it shows me that USB is always connected when it isnt and when USB is connected it doesnt let to switch on USB debugging.
Route is source stock rom and Odin load stock rom into Odin enter download mode on phone and then connect cable and flash rom .
No download mode
http://forum.xda-developers.com/showthread.php?t=819551
jje
JJEgan said:
Route is source stock rom and Odin load stock rom into Odin enter download mode on phone and then connect cable and flash rom .
No download mode
http://forum.xda-developers.com/showthread.php?t=819551
jje
Click to expand...
Click to collapse
Thank you all who have replied. I have now managed to get over the USB issue somehow but still something is wrong either with battery sensor or battery. When I power off my phone it switches on automatically and shows the thermometer and battery charge icon. Anyone else have had this problem? It also charges up to 95% and it bursts to 100% very quickly.
EDIT: Now I tried my friends battery and I did not get the flickering temp error and my friend didnt get it with my battery as well. So something now I'm totally out of ideas.
Service centre .
jje
I am having the same issues here, wonder if the topic creator resolved this in any way? I am thinking of getting a new battery?
Just FYI wear a condom or something on your galaxy S II. As it turns out from service my phone supposedly has liquid damage which does not the warranty apply. I have to pay 240 euros in order to get it fixed :S
Hey Guys.
I had an S1 7 months prior to buying the S2, and have upgraded/fresh installed ROMS many many times over the past year. Once the S1 bricked during an upgrade and I was able to get it into Download Mode without using a micro-USB jig from instructions on this website. If my memory serves me correctly, it was a procedure something fairly simple like hold the Home, Volume Up and Power buttons continuously until the phone goes into forced Download Mode.
However, this procedure doesn't work with the S2 or I'm remembering it incorrectly, and I'm unable to find that instruction webpage again. Now my S2 is almost bricked showing a message I've not seen before, "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
So far, I cannot get past this message and Kies 2.0.2.11071_128 doesn't recognize the device nor that emergency recovery is needed.
Unfortunately Samsung programmers haven't been quite smart enough or forward thinking enough to make Kies work from behind a proxy which requires authentication (I live and work on a university campus and the only way to the internet is via proxy and authentication) and it has never shown in the past 9 months of usage that it needs to update itself nor finds any official ROM releases. Therefore I've been forced to use Odin and ROMs from here or samfirmware.com for my updates. Until now, there has never been any major problems that I couldn't get around.
Do any of you have instructions on how I can get my S2 into download mode so as to get Odin to recognize the device? It is not possible for me to make my own JIG here in Thailand as there is nowhere for me to go purchase electronic equipment and parts such as soldering irons and resistors. I am a computer engineer and could easily build such if it were possible to get needed parts.
Thanks hugely in advance for any help offered.
Just order a high from ebay
Sent from my GT-I9100 using XDA Premium App
cmcole101 said:
Hey Guys.
I had an S1 7 months prior to buying the S2, and have upgraded/fresh installed ROMS many many times over the past year. Once the S1 bricked during an upgrade and I was able to get it into Download Mode without using a micro-USB jig from instructions on this website. If my memory serves me correctly, it was a procedure something fairly simple like hold the Home, Volume Up and Power buttons continuously until the phone goes into forced Download Mode.
However, this procedure doesn't work with the S2 or I'm remembering it incorrectly, and I'm unable to find that instruction webpage again. Now my S2 is almost bricked showing a message I've not seen before, "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
So far, I cannot get past this message and Kies 2.0.2.11071_128 doesn't recognize the device nor that emergency recovery is needed.
Unfortunately Samsung programmers haven't been quite smart enough or forward thinking enough to make Kies work from behind a proxy which requires authentication (I live and work on a university campus and the only way to the internet is via proxy and authentication) and it has never shown in the past 9 months of usage that it needs to update itself nor finds any official ROM releases. Therefore I've been forced to use Odin and ROMs from here or samfirmware.com for my updates. Until now, there has never been any major problems that I couldn't get around.
Do any of you have instructions on how I can get my S2 into download mode so as to get Odin to recognize the device? It is not possible for me to make my own JIG here in Thailand as there is nowhere for me to go purchase electronic equipment and parts such as soldering irons and resistors. I am a computer engineer and could easily build such if it were possible to get needed parts.
Thanks hugely in advance for any help offered.
Click to expand...
Click to collapse
Well kiss my rosy red butt-cheeks! Speaking from personal experience as tech support, I know empirically to replicate something 52 times prior to asking for assistance. This instance shouldn't have been an exception!
Directly after posting this request for assistance, I decided to try Odin once again and DANGED if this time it found my device even with the "Firmware encountered" error showing. Odin stopped around 90% and forced me to reset my S2, but this time it went right into Download mode with nary a fuss. Now Odin just successfully installed KG6.
So if there is anything to be learned from this experience, either by other users with similar issues or myself, it is "if at 1st you don't succeed, try again and again and again and again."
Dear forum members,
I have scoured google for assistance, and nothing seems to work.
I short, this is what happened. I downloaded Heimdall in order to flash my Galaxy S2 with an original Samsung rom to get rid of my operators bloatware. I downloaded a pre-packed gingerbread heimdal package and set to work. Because my phone PIT did not match the one in the package, Heimdall would not continue without a repartition. I checked the repartition, Heimdall connected to the phone and started transferring the PIT file. Here is where it went wrong. I got an error message stating: Error: "failed to confirm end of PIT file transfer". I tried again but this time, Heimdall could not connect to the phone. I pulled out the phone and tried to reboot, but to no avail. I cannot enter download or recovery mode, the phone doesn't react to being plugged into the charger, although it does get a little hot. My guess is I screwed up the partition table - how to I fix this problem??? Please help!!
Although you used Heimdall, it is always recommended not to touch PIT and repartition with Odin so the same should apply.
To confirm, you have the i9100 correct? Not the USA Tmobile or ATT SGS2? If a USB jig wont get you into download mode, you will have to send the phone to samsung for repair and it will be fairly expensive.
My learned colleague Kaze is correct (as per usual ).
Sadly, if you are unable to get into download mode via the a three button reboot or with a jig, you will need to have the phone JTAG repaired by a 3rd party repairer (probably cheaper option) or Samsung (probably more expensive option).
Yes I have the i9100. This is bad news! I've ordered a jig and I'll see if that works. If not, I'll try and return the phone. I haven't rooted it before so there will be no counts on the rom counter.
Great... another one that didin't do his homework before flashing stuff. Honestly, you guys must be made of money or at least growing money trees in the garden. I'd die of shame if I ever did something like this to my £400 device...
The JIG probably won't work, you have to send it into Samsung or buy a JTAG box and fix it yourself.
I have a GT-i9100. Odin originally worked and detected 'er fine in Download mode, but now I fear I have bricked 'er.
I flashed superatmos_I9100G_kernel_v3.2 not realizing the G. Now I can enter download mode, can't enter recovery, and can't boot to Android. I'm yet to try the jig, but if all else fails I'll bust out my soldering iron and have at it (will that do the trick?)
Stuff to try when Odin doesn't work:-
*Must run Odin as administrator in Windoze.
*Ensure Kies & it's processes aren't running in Windoze task manager. Kill them if they are.
*Try different USB ports; you must be using a 'powered' or mainboard port.
*Try different USB cables (particularly the cable that came with the phone if you're not using it now)
*Try different versions of Odin (search on here/Google)
*Uninstall Kies, reboot, redownload & reinstall it, reboot, try the flash again. Also run Windoze Update.
And if all this fails, try a different PC. If it doesn't work first go on the other PC, go thru the above steps.
If you get to the stage where the phone shows no signs of life (no boot, no recovery, no download mode), you can try a jig but it probably won't work. But obviously you cross that bridge if you come to it.
Try changing the USB port and get your hands on a Jig from somewhere...
Windoze :thumbup:
Sent from my GneX....Oh you jelly bro?
87 Mazda RX-7
just put phone in download mode and flash stock firmware with odin
Sent from my GT-I9100 using xda premium
I dont think that if you followed the above u will have the problem again
Sent from my GT-I9100 using xda premium
Try plugging your phone in before starting ODIN, it only detects my phone if I do that.
Hello, I know the precise answer to your question and it's really quite simple, there are only 36 easy and simple to follow step you need to perform in order to restore your device to its original working self.
To divulge these steps however I will require the payment you offered upfront. I think £2 per step is reasonable (or $4 or 10 euros respectably). Taking the 36 steps into account that comes to an affordable £72 ($144, 360 euros). I'm sure you would rather pay this extremely reasonable sum that have to spend upwards of £500 on a new device. So would I. After you pay the initial amount I will send you the ebook containing the 36 steps in a .xjnaiaw format. This format can only be opened by a xjnaiaw reader, which I will honourably throw in for free. When you get your xjnaiaw reader simply make an account, be sure to pay the one off joining fee of 25% of your annual income and hey preso, you have yourself not only a guide to easily and quickly fix your phone, but a beautiful new ebook reader as well. You win on all front.
Please PM for my payment details and to discuss this fantastic offer further, I look forward to doing business with you.
Same situation
I'm in the exact same situation you were in. What ever came of it? What can I do?!
Thanks
smb20 said:
I have a GT-i9100. Odin originally worked and detected 'er fine in Download mode, but now I fear I have bricked 'er.
I flashed superatmos_I9100G_kernel_v3.2 not realizing the G. Now I can enter download mode, can't enter recovery, and can't boot to Android. I'm yet to try the jig, but if all else fails I'll bust out my soldering iron and have at it (will that do the trick?)
Click to expand...
Click to collapse
Hi I am trying to fix a friends s2, its all stock and no root. Odin doesnt seem to want to flash the md5 files, either says nand write and stops or stay at BOOT stage.
any ideas muchly appreciated
Been covered so many times I've lost count this week (the 'Odin won't work' thing; search for similar threads). If you have recovery (I assume you probably don't, but, anyways), do a factory reset/wipe. And if not search for those threads as per the first sentence (CBA retyping the troubleshooting steps out given they've been regurgitated here thousands of times already).
Edit - You haven't exactly provided a great deal of info either, but as I'm not posting to this thread again, I'm not fussed if you provide more info or not.
MistahBungle said:
Been covered so many times I've lost count this week (the 'Odin won't work' thing; search for similar threads). If you have recovery (I assume you probably don't, but, anyways), do a factory reset/wipe. And if not search for those threads as per the first sentence (CBA retyping the troubleshooting steps out given they've been regurgitated here thousands of times already).
Edit - You haven't exactly provided a great deal of info either, but as I'm not posting to this thread again, I'm not fussed if you provide more info or not.
Click to expand...
Click to collapse
there is no recovery as its not been rooted/flashed in any way.
You can get in to download mode and thats it. What further info do you want, its on o2 in the uk
Andyokane said:
there is no recovery as its not been rooted/flashed in any way.
You can get in to download mode and thats it. What further info do you want, its on o2 in the uk
Click to expand...
Click to collapse
oh and I HAVE been searching the threads I post on here all the time and know how to use the forum, All the guides say get in to recovery (which I cant do) If I could i'd be laughing
Andyokane said:
oh and I HAVE been searching the threads I post on here all the time and know how to use the forum, All the guides say get in to recovery (which I cant do) If I could i'd be laughing
Click to expand...
Click to collapse
seriously searched my balls off now and still cant find a solution... had faith in you lot
No lying allowed!
Sent from the little guy
Andyokane said:
had faith in you lot
Click to expand...
Click to collapse
All you get on here now is spamming and stupid pics getting posted now.....
Damn, you're starting to imagining things.
Get it together.
Sent from the little guy
theunderling said:
All you get on here now is spamming and stupid pics getting posted now.....
Click to expand...
Click to collapse
tell me about it mate. That and pointless replies ^
- its amazing how each section of xda differs too, I use the s3, s4 hox, kindle, and htc one and its a nice place to be. Instant responses and friendly natured
Right. This is the final time I'm posting these steps ever (I'm deleting the txt file I have them stored in on my PC, so anyone who wants to make a copy of these steps, do it now) on here:-
Flash/Odin doesn't work blurb -
*Must run Odin as administrator in Windoze.
*Ensure Kies & it's processes aren't running in Windoze task manager. Kill them if they are.
*Try different USB ports; you must be using a 'powered' or mainboard port.
*Try different USB cables (particularly the cable that came with the phone if you're not using it now)
*Try different versions of Odin (search on here/Google)
*Uninstall Kies, reboot, redownload & reinstall it, reboot, try the flash again.
*Turn off antivirus/antispyware/antimalware.
*Check the rom/kernel you download for corruption. Either check the MD5 sum if you have it (use md5summer or similar), if you don't have the md5 sum or can't check it, programs like 7Zip, IZarc, WinRar, etc will allow you to 'test' the rom file you download. If there are any errors/any of the files fail the test, bad download. Try again/try downloading with a different internet connection if it keeps happening.
*Run Windoze Update.
*And if all these steps fail, try a different PC. And if it won't work first go on a 2nd PC, go thru the above steps on that PC. Still doesn't work ? User error (will be almost impossible to say what given we're not there looking over your shoulder, almost always something very obvious being missed) or borked phone - return to service centre or local mobile shop.
I suspect many cases where people (say) they do all the above & still can't get it to work involve problems with the USB ports on the machines they're using. Something along the lines of the port is unable to maintain a constant connection between PC & phone; if that connection drops for even a millisecond (probably not even long enough to be registered as a broken connection by the PC in the normal way), you end up with a constantly failing flash at best and a bad flash which borks your phone at worst.
Obviously the only way I'd be able to test the theory would be to examine/test a bunch of PC's belonging to people who experience this issue, but I've given this issue a lot of thought over the past 18 mths & it's the best explanation I've got for those instances where people are being completely honest about having tried all the steps over & over and on multiple machines (a very very small % of people, most people either simply don't do every step over & over and say they do, or they forget they've forgotten they did A, B & C but not F) & still find they can't flash successfully (and it isn't a case of the phone being borked).
MistahBungle said:
Right. This is the final time I'm posting these steps ever (I'm deleting the txt file I have them stored in on my PC, so anyone who wants to make a copy of these steps, do it now) on here:-
Click to expand...
Click to collapse
@MistahBungle:
Do you mind if these steps are re-posted, if its said that originally you posted them?
Knock yourself out. Copy, publish, repost & plaster as widely as you like
Edit - I actually saw a similar list initially posted by JJEgan ages ago (>1 yr), and then added some things to it, so he deserves ultimate credit.
MistahBungle said:
Knock yourself out. Copy, publish, repost & plaster as widely as you like
Edit - I actually saw a similar list initially posted by JJEgan ages ago (>1 yr), and then added some things to it, so he deserves ultimate credit.
Click to expand...
Click to collapse
Will do. Once I finished re-posting it (possibly soon at the given rate of 'my flash didnt work plz help' posts), someone else may take it on, as you did from JJEgan. I haven't been around for a year, but if I see his posts I will thank him
tried all that apart from the different computer tip. Will try it tonight at work and report back.
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).