No introductions here, just want to get straight to business... I don't mean to sound so impulsive but I've just been so annoyed by this and I just want a working phone again. I am running Stock Jelly Bean 4.1.2 on the carrier Vodafone (I have not rooted my phone). I have looked around the forums for answers but all of them don't seem to work for me.
This all started over a month ago when I was on Youtube and suddenly the touchscreen froze (the video was still playing) and the buttons were unresponsive. I pulled the battery out and put it back in after a few seconds. When I turned it back on it came to the 'Samsung' animation again and again (a boot loop).
Not knowing that the best option here want to go into recovery and do a factory reset, I went to recovery mode and wiped the cache partition. I rebooted the phone. But this time I was stuck on the 'Samsung Galaxy S2 GT-I9100' screen. I also found out that my recovery mode was not working. It would just have the android robot with a sphere in the middle for ages then it would reboot into the 'GT-I9100' screen. My download mode however, is still functional to this day.
As I've been told, as long as you have access to download mode, there is still hope for recovering your phone and putting it back to normal. So far I have tried:
Installing multiple stock JB ROM's such as the ROM's with LSW and MS2 on the end of the file. I have tried two versions of Odin (1.35 and 3.07) but with no results. The downloads of the ROM were no problem.The flash would be OK up until 'cache.img'. The flash would then freeze then proceed to say a big red 'FAIL'. Note that I have tried to do this on multiple computers while using different USB ports (mainport with no USB hub) for each flash. I have Kies installed but have killed all the processes and opened Odin as an administrator. I have used the original S2 cable that came with my phone and one other data cable, but still no results. I refuse to flash any PIT files because I don't like the risk associated with them. I have yet to flash these firmwares:
LSJ (JB leak), LSD, LSS, LS8, MS7
The drivers might be the problem so I might reinstall them but I don't know how...
Yesterday, I was told by a friend that he had the same problem before and all he did to simply fix this was to download the S2 Jeboo custom kernel (which has CMW with it). He also said rooting the phone would also fix it. I have attempted to flash said kernel with Odin 1.35 when it got stuck when the green bar was full. I pulled out the battery and the USB, put the battery back in and the USB (in a different port) and attempted to flash again. Nothing. I notice now that there is a yellow triangle below the 'GT-I9100' screen when I attempt to boot the phone and that my custom binary count has increased to 2. When I attempt to go into recovery mode the screen flashes twice and just stays in the 'GT-I9100' screen instead of the android robot from earlier.
That's it really. I hope someone can help me in this almost hopeless situation... I have typed about this before on another forum but I had no replies that would help me. I could go to a service centre but my warranty's gone and the yellow triangle might cause some problems. The information from xda-developers has always been solid and reliable... so can someone help me out
Same as everyone else in this situation - find Hopper8's 'Odin troubleshooting' thread stickied in General, and go through the troubleshooting steps in a methodical manner until you get a successful stock flash, as this is the only way you're fixing it.
In your situation/given what you've already tried, I would be downloading the 3 part firmware (the 'leak' you referred to) linked to in the thread & flashing that first, which will wipe your phone & hopefully remove any remnants of what was previously on the phone which may be tripping you up.
This may not be successful first time, your flash may still barf as the one's you've tried so far have; in this case it's a matter of going through as many of the suggestions in the thread as many times as you need to until you meet success (including multiple PCs if necessary). When these are recoverable (and most are), they're often fixed by perseverance.
That thread is 'the bible' in these situations, and there isn't anything else which isn't in the thread that can be suggested in these situations, so you really do need to try absolutely every thing in that thread if you want your phone fixed.
MistahBungle said:
Same as everyone else in this situation - find Hopper8's 'Odin troubleshooting' thread stickied in General, and go through the troubleshooting steps in a methodical manner until you get a successful stock flash, as this is the only way you're fixing it.
In your situation/given what you've already tried, I would be downloading the 3 part firmware (the 'leak' you referred to) linked to in the thread & flashing that first, which will wipe your phone & hopefully remove any remnants of what was previously on the phone which may be tripping you up.
This may not be successful first time, your flash may still barf as the one's you've tried so far have; in this case it's a matter of going through as many of the suggestions in the thread as many times as you need to until you meet success (including multiple PCs if necessary). When these are recoverable (and most are), they're often fixed by perseverance.
That thread is 'the bible' in these situations, and there isn't anything else which isn't in the thread that can be suggested in these situations, so you really do need to try absolutely every thing in that thread if you want your phone fixed.
Click to expand...
Click to collapse
Thanks for the quick reply, I will look into the guide in more detail and follow the instructions carefully. In regards to the flashing of the JB leak, will this fix the problem of being unable to access recovery mode? And is there any other firmwares you recommend flashing? I really don't want to wipe my phone, as I'm saving the flash of the JB leak as a last resort.
Given what you've already tried & the information you've provided, if I was in your situation I'd be starting with the leak. But that's up to you. If you don't want to do that, you'll need to go through everything in Hopper's thread methodically; eventually you'll get a successful stock flash (and you may end up having to flash the leak to fix it anyway).
Will the leak fix your problem ? Quite possibly, but possibly not. What it will do (if it works) is take you back to a stock setup, so you'll have access to stock recovery. You may end up with bootloop after the flash even though it's successful; in that case you boot into recovery & do a wipe/factory reset.
So far as what stock firmwares to flash, it doesn't matter; they're all essentially the same. The only important thing is you get a firmware on your phone/working. But if it was me in that situation, I'd be sticking with firmwares released by your carrier (flash one of these after the leak if you go down that path).
There isn't a lot else beyond what I've already told you & I can offer; we have that thread as 'the reference' in these situations, neither I nor anyone else here can offer you anything which isn't in that thread. It's the gold standard & covers this issue from every possible angle.
Related
Hello, sorry if this has already been answered but I did look around at similar scenarios and it seems to me that using odin to flash the stock kernel should fix it but on my device, however, it doesn't fix my problem. I beleive what I did was select update firmware from .zip in clockwork on accident. Idk if this is what you consider a "boot loop" because it doesnt restart it just sits there at the black galaxy s2 screen. Any insight would be great. I hate to have to buy a new one as it is quite alot of money. Like I said, sorry if this is already answered but after looking around for hours I still hve had no luck. Thanks in advance, Alex
Can you get into recovery (volume up+home+power) or download mode (volume down+home+power)?
I can get in to download and recovery mode both
The outlook is promising then. Without knowing what you've flashed, it's impossible to say what damage you've done, but if you don't mind losing your data, you can certainly get back to a working state by following [READ THIS] Got a Boot Loop? Don't post a New Thread!.
Before going down that route though, if you do want to keep your data, let us know what you flashed as it might be recoverable (maybe you just flashed the wrong kernel).
I can't say for sure what i flashed but I can say that i either flashed with an update or updated with a kernel??? sound right??? idk. the data isnt near as important to me as the 680 dollars my carrier will charge me for a new s2. Right now im using a junk alcatel tribe and im going through galaxy withdrawls.
Well before flashing anything else, make sure you definitely have an I9100, not some other variant (I notice you mentioned dollars). If you have a different model, you're in the wrong forums and might make things worse by following advice for the I9100.
I was pretty sure that it is the I9100 but i took the battery out and double checked. it IS the I9100
also for what it's worth when going into recovery(stock version) right after the text reading updating application it gives me an error in red. (E:install_application_for_customer:Can't unmount /preload copy application failed) and after the (Appling [yes it really spells it appling] Multi-CSC) it says Can't access to '/system/csc/TTT/system/'. However, the line after it says that it says Successfully applied multi-CSC
My first attempt to get back to a working phone without losing data would be to flash a stock kernel then, have you tried that?
Ok.. done.. but it still sits at the galaxy screen except now it has the triange due to the custom firmware
If that hasn't got you up and running then it's probably time to bite the bullet and follow the instructions from the boot loop thread linked above (which will also remove the triangle).
Maybe you can answer another question for me. When in recovery mode it says apply update from sdcard... why does it say that when it doesnt actually read from the sdcard? i have checked with the sdcard both in and out and the file directory in the recovery mode doesnt change. is it calling the usb storage an sd card?
ok when flashing a stock rom do i use the phone option in odin or the pda still
If you're flashing a stock rom from [ROM+Guide]Official i9100 Firmwares KG, KH1/2/3/4, KI1/2/3/4/8, KJ1/2 Download, then just follow the instructions from there (but usually PDA).
:'( Still wont boot.
What does happen, did any steps fail, any error messages?
Everything went smooth with no errors. No steps failed. Sitting at the boot screen is all it does though
Did you definitely wipe user data? (step 3). The final step of that thread is to try flashing a ROM which wipes, such as (non-stock) VillainROM 1.1.
well... yes i definitely wiped the user data and it was successfull when doing so. I didnt try the villian rom just because I thought that it was an optional thing but i will def. try it now that you bring it up. and hey, i really appreciate the help no matter what the outcome
(VillainROM 1.1 - XWKE7 base) I'm a UHKG7..... is this going to be a problem? just something i noticed and thought I would ask before going ahead
Hello all,
I have tried many things before asking for help, but nothing worked so far.
Here is the story:
I was on ICS 4.0.4, with default ROM coming from carrier.
I wanted to install CM9.1,
spent countless hours doing all backup and reading tutorial.
Tried finally yesterday and it was stuck doing "wiping data". Left it for 20min+ and nothing.
After restarting it, it is now stuck on the boot logo.
I couldn't enter anymore CWM or stock recovery (up+home+power), but could enter Download mode.
So I tried a couple of things I have read on the forum, like installing Siyah-s2-v5.0.1.tar through Odin 3.04 but I still cannot enter recovery mode.
I've read (too late) about the mmc brick bug (couldn't find anyone speaking about it in any tutorial until I reached this point... nothing on CM wiki or in other tuto... classic!).
I hope I'm not in this case though as I can still go to DL mode, and the phones having the brick bug are completely dead (blank screen or no DL mode), as per http://forum.xda-developers.com/showthread.php?t=1756242
I managed to finally get CWM working only by using GT-I9100_ICS_ClockworkMod-Recovery_5.5.0.4.tar from Odin, then tried to install CM9.1 from SD card but after reboot it is stuck on the blue cyanogenmod animation boot screen and nothing happens.
Tried also to restore from CWM my nandroid backup, but during the restore it seems to hang then restart by itself, and then I'm back to Galaxy S boot logo (the animated one with the big S).
And after this I have lost again access to recovery mode.
I can't go back to stock and I can't install CM... I was not expecting such issues, it all seemed pretty basic on paper.
I'm really stressed and don't know what to do
Flash a stock rom in Odin (download mode), re-root your phone/flash a kernel with CWM, restore your backup ?
Hi,
thanks for answering,
I have tried to locate such a rom, but I'm not sure which one... is there a specific one to try ? could you point me to it please ?
so far I have tried I9100XXLPQ_I9100OXALPQ_I9100XXLPQ_HOME.tar.md5
but no luck
you also say "re-root", at the time I used this method:
[GUIDE] ROOT/UNROOT Stock ICS Firmware without flashing unsecure kernel - xda-developers
http://forum.xda-developers.com/showthread.php?t=1501719
Do I need root to install Siyah kernel from Odin ?
I'm trying one from sammobile... let's hope :/
The bad thing is I had no Yellow triangle at the beginning since I'm stuck in this boot loop or no boot to be precise.
Now that I have tried different things to fix it, it is still not working and I have my flash counter = 10.
I cannot even go back to the shop, is there a way to reset it knowing I cannot even reach the OS, I have only DL mode or CWM...
Use a stock rom for your region/carrier (or any stock rom from any region really), it doesn't really matter as I presume you'll be restoring a backup and/or going back to a custom rom anyway won't you ?
Samfirmware & AndroidFirmwares.net have lots of stock roms.
No, you don't need root to flash an Odin version of Siyah. So yes, you can flash that after you've got stock up & running to root your phone rather than re-rooting your phone by flashing a CFRoot kernel or using another root method. Just make sure the version of Siyah you're going to flash matches up with the stock rom you've got on (I.E if you flash a GB stock rom use GB Siyah, ICS stock = use ICS Siyah, etc, etc).
thank you again, I'm downloading the rom from sammobile matching my carrier,
Would you be so kind to send me a PM with your skype username or anything to "chat" with you ? I'm really worried and I spent all night already trying to fix it with no progress at all
Don't worry about the flash counter. That's the least of your problems while your phone is borked Worry about it when it's fixed. There's nothing you can do about the triangle while your phone is cactus.
When you've got it up & running again, use Triangle Away.
But first things first.
---------- Post added at 04:02 AM ---------- Previous post was at 03:59 AM ----------
You're welcome.
Um, no. Absolutely not. Nothing personal, but if I did that for every person who's asked me for 'hands on' help since I've been here, I'd have spent my time doing nothing else. I don't do 'personal' with people from XDA (which is why I have PM's blocked except for mods).
Besides, you're going to learn much more fixing this yourself. I've given you a stack of information thus far, ball is in your court. Every answer to every question you could possibly ask is on this site. It just sometimes takes a bit of work/reading on your part to find it.
megosu said:
thank you again, I'm downloading the rom from sammobile matching my carrier,
Would you be so kind to send me a PM with your skype username or anything to "chat" with you ? I'm really worried and I spent all night already trying to fix it with no progress at all
Click to expand...
Click to collapse
ok I understand.. it is just I have literally spent more than 8 hours on it and had not make any progress at all (even worse I cannot return it to the shop because of the yellow triangle).
I appreciate your help, it gives me a bit of hope but I'm in a very bad situation and I feel I have read and do so much already with no success at all.
I will try your option of restoring the one from Sammobile, I have tried other before without any luck, maybe this one will do... (5min left to DL it).
thanks again for your support
I know where you're coming from. The first flash I tried when I got my phone in 2011 borked because I was careless, and it took me a bit over a day to get the right info/files/etc to get it fixed. I know it's frustrating/tiring/annoying & you're wondering at the start whether you can even fix it. But as long as you've got download mode 99 times out of 100 you can save it.
And as I said, it's good experience; once you've fixed it, you'll be able to handle anything that comes up in future
Let us know how you go. I'm going to bed shortly, but I'm sure someone else will step up & help if you have any further problems.
You're welcome Happy to point you in the right direction.
I have flashed the rom, the exact same one as I had before everything happened...
if it helps, I flashed it from Odin 3.04 as PDA.
I9100BVLPH_I9100TMULPH_I9100BVLPE_HOME.tar.md5
I'm now back to the Samsung GALAXY S2 GT-I9100 logo and nothing happens.
I cannot use recovery mode,
I can use DL mode (it shows 11 counts and current binary as Samsung official.)
update:
I left the phone on the first logo for about 5min and it moved to the next Samsung Galaxy S2 logo, with the big animated S.
I'm waiting but nothing else is happening.
I'm still desperate to fix it.
One thing which can be relevant, whenever I try to wipe or format /data from CWM, my phone is restarting after a few minutes or is saying it cannot be done.
I can format /cache and /system.
Could it be the root cause ? Any way of fixing it ?
Thank you
update: I cannot mount /data from CWM, it says Error mounting /data!
is it the brick bug ? :|
Easy now....your device is still good.
Those animations should take like 1-2 mins when you flash a rom.
Now, you are completly sure that you are actually flashing the right ROM for your device model?
If so, just keep flashing stock roms until you're up and running again, so you can start from scrap.
I tried, the issue is as soon as I flash a stock rom (through Odin), then I can't get into stock recovery mode anymore, I have to flash GT-I9100_ICS_ClockworkMod-Recovery_5.5.0.4.tar to get back the recovery mode.
I tried to flash several times, I think it is down to the fact I cannot mount or format /data.
Which is why I'm wondering if it is the famous brick bug.
My device is GT-I9100 and I took the stock rom from sammobile:
I9100BVLPH_I9100TMULPH_I9100BVLPE_HOME.tar.md5 which is ICS 4.0.4 (that I had before trying to move to CM9.1 and having all this mess in my hands.)
flash this:
http://www.sammobile.com/2012/11/15/i9100xxlsj-%E2%80%93-galaxy-s-ii-android-4-1-2-jelly-bean-test-firmware/.
you are on siyah kernel right?
what you wanna do know is to get to whatever rom your flashing, forget about cmw for now.
this also might help:
http://forum.xda-developers.com/showthread.php?t=1457458
So it is not lost yet ? Not the brick bug ?
just to be sure:
you want me to install through Odin: Siyah-s2-v5.0.1-CWM.zip
then going back to DL mode
I flash through Odin: I9100XXLSJ_I9100OXXLS1_OXX.zip (coming from your link).
anything I'm missing (even if it seems obvious, please let me know as I'm maybe missing something important)
?
I still cannot do Factory reset... is it a problem ?
I dunno what kernel you are using, If stock 4.0.4 kernel you should flash siyah first (safe kernel, no brick bug), and then countinue flashing the ROM. Check out the brick bug thread in general SII forum for directions if you want.
BTW, Odin recognizes your phone right? Check it out, you'll get a huge long breath.
BTW 2: you don't have any kies applications running in your pc.....am I right? if so, CLOSE THEM ALL!
I did had stock 4.0.4 kernel when I first tried to follow CM9.1 wiki, and I did a factory reset through CWM... which is why I think I might have bricked it...
I have checked the brick bug thread (too late it seems...) but so far I can't be sure if I'm in this case or not as they say they can't even reach DL mode, and I can.
Odin recognizes my phone, yes, but anything I flash is stuck on the animated logo.
I do not have Kies installed, just installed the drivers.
Hi all,
Was on Slim Bean 4.2.2 Build 7, but encountered a boot loop for some reason. So I proceeded to flash the stock roms (4.1.2) as listed. Tried several times flashing different roms on that page (just flashing the PDA file), but to no avail. Odin always says that the flash is successful, but the boot loop still continues. Does anyone have any advice on how to get past this boot loop? Thank you so much!
Short of persevering (I.E try different stock roms - different Android versions, released by different carriers), try Hopper8's 'Odin won't flash' thread. Though it appears your flash has been successful, something is obviously not right (almost impossible to say what that might be given we're not there with you watching over your shoulder). Stuff like trying different cables, different USB ports, uninstalling/reinstalling Kies & even different PC's is worth trying (and other stuff in his thread). Also, try flashing a 3 part stock rom (as per Hopper's thread), this should wipe any 'remnants' which might be causing the issue you're seeing & might work (maybe try this first).
Also, I'm going to ask the obvious - if recovery is working, have you booted into recovery after flashing & done a wipe ? Obviously if you have no recovery you won't be able to do this.
Thanks for the reply. I have tried going into recovery mode, but to no avail.
Would I be able to flash a 3 part rom if I just flashed a stock rom? Just wanted to make sure I don't brick it.
A three part rom is a stock rom, but unlike a one part rom which you flash in the PDA section of Odin, the CSC file will wipe your phone in the process, which is what we want if we're working with the theory you flashing one part stock roms up until now seems to be 'leaving something behind' which might be causing persistent bootloops.
If you're worried about bricking your phone, take it to a service centre & pay to have it fixed (All they'll do is try & flash a stock rom/wipe the phone which you're capable of doing for free yourself). You're looking for a simple fix, there isn't one. If you persevere, you'll fix it eventually. This has been the experience on here over the past 2 yrs or so.
MistahBungle said:
A three part rom is a stock rom, but unlike a one part rom which you flash in the PDA section of Odin, the CSC file will wipe your phone in the process, which is what we want if we're working with the theory you flashing one part stock roms up until now seems to be 'leaving something behind' which might be causing persistent bootloops.
If you're worried about bricking your phone, take it to a service centre & pay to have it fixed (All they'll do is try & flash a stock rom/wipe the phone which you're capable of doing for free yourself). You're looking for a simple fix, there isn't one. If you persevere, you'll fix it eventually. This has been the experience on here over the past 2 yrs or so.
Click to expand...
Click to collapse
Thank you MistahBungle! For some reason, a three part rom did the trick. Not sure why though. But I'm so grateful for your help!
There you go. Our theory re: previous flashes leaving something behind must have been right. You're welcome Glad you got it sorted.
darknezx said:
Thank you MistahBungle! For some reason, a three part rom did the trick. Not sure why though.
Click to expand...
Click to collapse
Good for you! Please add [SOLVED] to the title of your post then.
"To err is human, to forgive is divine."
Sent from my SGS II
Hello,
I was able to root my SGSII GT-I9100T using Clockworkmod. I then proceeded to flash Android KitKat but during that procedure, my phone displayed an error with the emmc (or something like that) and the installation was aborted. I can get onto the Recovery screen but I can't get any further, i.e. I can't get to my apps, messages etc.
I do not have a backup of prior to the error in the flash. The top of the screen I am able to see says: CWM-based Recovery v6.0.1.2-Siyah. I have wiped my data and cache with no luck. Everytime I reboot, it goes back to the same screen.
Also, I am with Vodafone Australia, and they do not appear to have a downloadable stock ROM.
I want to get my phone back to prior to rooting, obviously with the default settings (but this doesn't matter).
What should I do? Am I able to repair it?
Yes, you're able to repair it easily. If you don't have any backup, doing a wipe from recovery (which can sometimes fix this) isn't an option for you because obviously you'll lose data if you wipe. I'm also thinking perhaps you've flashed the wrong version of Siyah; you could always re-read (or read) the Siyah threads on here to make doubly sure you've flashed the correct build for your Android version (I don't remember which is which, been ages since I've used Siyah), and if it is a case of you having flashed the wrong build, flashing the right build might well solve your problem & give you a rooted phone. You could also find the PhilZ thread on here, read it, and flash that which should also help you to achieve that aim.
But...if you really want to go back to where you were before you started...
Download a stock rom for Voda AU from Samfirmware (Doesn't matter which one, up to you. You'll need to sign up in order to do so), and flash it following the instructions in the thread titled 'Flash Stock firmware/ROM...' stickied near the top of Q&A.
If you're unable to get a successful Odin flash/or it fails for whatever reason, find Hopper8's 'Odin troubleshooting' guide stickied in the General section & try the stuff in that thread, which should enable you to get through any issues & get a successful Odin flash which will take your phone back to the state it was in before you attempted to root it.
Normally flashing a one part stock rom like this won't involve data loss, but there are never any water-tight guarantees.
Edit - For future reference, if you ever decide to mod your phone even slightly, always back everything up before you do anything. Don't be like the 95% of people on here who do this & then end up in the **** because they didn't back stuff up. The reality is, if you're going to mod, stuff goes wrong eventually for everyone (as you've just found out).
Thank you, I will attempt to flash a stock from that website.
Just to clarify, I first installed CWM (not the Siyah version), and that was working fine. I was able to boot and do whatever. I then proceeded to flash an Android KitKat ROM but this resulted in an error. I then flashed Siyah (which may have made it worse) because from what I read at the time, it could have fixed my problem. So it must have been from the ROM, whether it be my phone being not compatible with it etc., rather than the wrong version of Siyah (although, as I said before, it could have made it worse).
Yep, rom incompatibility. Siyah stopped being developed with ICS, so won't work with KK roms; kernels need to be compatible with the Android version of the rom in question.
Doing what you did is no drama usually, worst case result is normally what happened to you I.E bootloop which won't go away without going back to stock, unless you get a bad flash. It's actually a good learning experience, because now you'll know how to recover if you flash stuff in future
I managed to flash the stock version and thankfully, my phone is back to 'normal'. Luckily I always had intentions on resetting it to factory settings. Indeed it has been a good learning experience :good: Thanks for your help, MistahBungle.
No worries. Glad you got it sorted
Hey guys,
First off, although I hope that it turns out to be very easy to fix and that I've been an ass for being unable to find it myself, I've been trying to figure this out for several hours and I can really use your advice.
The S2 is upgraded to the latest version (I think, it's been several months since last update) of ICS, via KIES. Never did any modding on it.
Problem: (Not sure if this is really the cause of the problem, but) I have never been able to check the way my internal and external RAM and SD-card has been filled up, by which I mean the standard overview in the S2's settings. The information would not simply not load. A few days ago though, I had a lot of time on my hands, so I just kept it running on that screen for a very long time. When I came to check again: it was stuck in the bootscreen ('flashing Samsung logo').
It is still stuck at this screen, despite removing battery several times and removing SD-card. I am able to get into System recovery as well as Download mode. I have wiped the cache partition via System recovery. Also I have tried to reset it via KIES, but despite the computer's System messages saying that it is recognized, it does not get past the connection screen in KIES ("machine not responding''). So there's seems to be nothing I can do via KIES.
My true question: Is my only option left to 'wipe data/factory reset' in the phone's Recovery system, or am I missing another solution?
I hope that you can help me out with this.
Thanks!
You can try flashing a stock rom with Odin, that may fix it without a factory reset. Get one for your country/carrier from Samfirmware (not 4.0.4) & flash it following the instructions in thread stickied near top of Q&A titled 'Flash stock firmware'. If you have problems with the flash, find Hopper8's 'Odin troubleshooting' thread stickied in the General section & go through the troubleshooting steps in a methodical manner until you get a successful flash.
It's 50/50 whether this will fix it on its own, you may end up having to do a factory reset after the flash anyway, so try it & see.
I presume we're talking about an I9100 ? (S2 is a generic term, there's a number of variants).
Thanks for your swift reply!
Yes it's the GT-I9100. For which there actually seems to be no firmware for, for Holland/Netherlands on Sammobile.com. Any advice where I could then get it?
Plenty of firmwares available for the Netherlands on Samfirmware (yes I just checked), use a different browser and/or turn off any script blockers/similar - their site is heavily script dependent & won't work properly if you're blocking them.
And any firmware will do really, I just assume many people in this situation will stay on stock firmware, so you may as well stick with your country/carrier as this rom will have a modem bundled that will work well with your carrier, if you start flashing stock roms for other countries/carriers, that might not be the case.
It took me a while to figure it all out, but I eventually managed to do it! But something went wrong after flashing, I think.
These were ODIN's last messages:
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
Then my phone restarted. After having been stuck at the Samsung logo for a few minutes, it changed! It started upgrading the Android-system by 'Optimising applications' and then by 'Opening applications'. But.. It's now stuck at opening the applications.
Is it possible that this is due to me having removed the SD-card at start? I do have most of my apps on the SD-card.
Thanks so far! I have appreciated it very much
So far no succes I'm afraid.
As I told in the post above, after the first flash my mobile got to the 'Opening applications' screen during rebooting. Because it got stuck there, I thought it might have to do with my external sd-card (which holds most of my apps) not being in the phone during flash. So I flashed it again, this time with the sd-card inside the phone.
Still no luck! Once again stuck the Samsung logo.
Any idea what else I could try?
SOLVED
Hey guys, just to give an update! It finally worked!
After flashing a few times, I performed a wipe data/factory reset after all. After having done so (and giving it another 10 minutes) it worked!
I have lost all my contacts and my stories in my Notes, but I guess that couldn't be avoided. No chance of getting (especially) the Notes back I presume?
Either way, thanks for kicking me in the right direction MistahBungle! Not sure if it'll actually give you any rewards, but I referred you on Sammobile
Good man. Glad you fixed it (sorry I wasn't around to see your other posts yesterday). Yep, I did say there was a chance you'd need to do a factory reset after flash, and half of these we see are fixed by just flashing & the other half need a reset.
If you're staying on stock, make sure you backup your stuff with Kies or Google, and most apps have the ability to create backups which you should keep copies of on your external sd card if you have one, and on your PC.
You're welcome (thanks for the referral on Samfirmware)