Related
I have a Galaxy S 2, I777 from AT&T. I had been running UnNamed 2.0 for a while. I started messing around with different modem files trying to get my data rate a little higher. When those failed to work, I decided to go back to stock and start from scratch. This is where my trouble begins:
I flashed with ATTGalaxyS2Unroot_SGH-i777.tar using Odin 1.85. I've used that before and all was well. After this flash, I'm stuck in a boot loop. The galaxy s 2 logo just keeps recycling.
I have tried a lot of other items I've found on here in various threads about getting out of a boot loop, but have not been successful. I was able to get to the stock recovery mode, chose to wipe user data and did the "yes I'm sure" option. The phone rebooted and I have not been able to get back to it. When it tries, I get in yellow "deleting cryption meta data" and then the phone reboots.
My last attempt was flashing with i777uckh7-cl503881 full. Odin writes everything, says pass and the phone reboots. After it restarts, it quickly goes through some items:
-- Intalling package...
Finding update package...
Opening update package...
Verifying update package...
Installing update...
Successfuly installed package...
-- Copying media files...
successfully copied meida files (yes, media is misspelled on the screen)
-- Wiping cache...
Formatting /cache...
Cache wipe complete.
--Updating application...
Successfully updated application.
--Appling Multi-CSC...(again yes, applying is mispelled on the screen)
installing Multi-CSC
Can't access to '/system/csc/02U/system/'.
Successfully applied multi-CSC
Rebooting.
then I get the boot loop all over again. I am still able to get to download mode using the volume button, and my jig still boots to download mode too, so I think there's still hope, but I don't know what to do next.
Any help would be greatly appreciated.
The "deleting cryption meta data" error has been a particularly difficult one to get out of. I only remember seeing one person solve the problem, and I believe that the solution was to flash the siyah kernel. But you may find more details if you search on "deleting cryption meta data xda" or possibly "deleting cryption meta data siyah" as keywords.
Creepyncrawly:
Thank you for your post. I didn't find anything searching for that, but, I downloaded and flashed siyah kernel and was able to get to a recovery mode.
I am now restoring the nandroid backup that I made (luckily I was smart enough to do that) before I started messing with modems and stuff.
We'll see how this goes
you sir are a life saver. I was able to restore the nand backup and boot into the os again.
creepyncrawly said:
The "deleting cryption meta data" error has been a particularly difficult one to get out of. I only remember seeing one person solve the problem, and I believe that the solution was to flash the siyah kernel. But you may find more details if you search on "deleting cryption meta data xda" or possibly "deleting cryption meta data siyah" as keywords.
Click to expand...
Click to collapse
I think (but I'm not sure), but any custom kernel with CWM should be able to do this... It's only the stock kernel that has a recovery which does anything when device encryption is found.
Entropy512 said:
I think (but I'm not sure), but any custom kernel with CWM should be able to do this... It's only the stock kernel that has a recovery which does anything when device encryption is found.
Click to expand...
Click to collapse
I did not think of that, but it makes sense now. At the time, I figured I would stop and get help before I made it worse. Why I didn't restore to my backup to begin with is beyond me.
Do you think I could return to stock now, or is it more of a "once you have this problem you always have it" type thing? I'm going to leave it as is for now because it seems to be working fine. There may come a day though when I need to return to stock.
For those who are experiencing the "Deleting Cryption Meta Data" problem, creepyncrawly is correct, it is difficult to solve, but the following steps seem to solve it reliably:
Download and install the I777UCKH7-CL503881 Stock Binaries from creepyncrawly's download repository. Use heimdall or odin to load the stock binaries. You may need to load the param.lfs and/or the bootloaders. However, it may work without loading these files (and loading the bootloaders can be in the "danger zone")*.
With the stock binaries installed, the device will be in a boot loop, and entering recovery mode will either indicate that the device is installing CSC (unsuccessfully), or indicate that it is "Deleting Cryption Meta Data". In either case, you will be unable to actually access anything in the recovery.
In order to get to a working recovery, load the SGH-I777_ClockworkMod-Recovery_5.0.2.3. You'll need to untar this file to get to the zImage kernel file*.
With the CWM kernel installed, you should be able to actually enter recovery mode by holding down Volume Up + Volume Down + Power until the Samsung logo appears for a second time. Note: In this version of CWM recovery, the home button is the 'select' button and the power button acts as the back button. This is different than most versions of CWM.
Using the recovery run both clear data/factory rest and format sd card (in mounts and storage).
Finally, install the Siyah Kernel, using either heimdall* or CWM.
At this point, the phone should be restored, and you can re-flash the I777UCKH7-CL503881 stock kernel (on any other compatible kernel).
onecoolpilot said:
Do you think I could return to stock now, or is it more of a "once you have this problem you always have it" type thing? I'm going to leave it as is for now because it seems to be working fine. There may come a day though when I need to return to stock.
Click to expand...
Click to collapse
You can re-flash any kernel you like.
Thanks everyone who directed me to the steps for solving this problem!
* To load these kernel files, put the phone in ODIN mode by holding down the "Volume Down" button while the phone is connected to USB. Use either the ODIN or Heimdall tool to actually flash the device. See this post for complete instructions on flashing the files.
I've followed these directions multiple times but I can't seem to get past the Rethink Possible screen.
Steps I have taken:
Flashed full binaries
Went back into download mode with no reboot and flashed CWM (listed above)
Went straight into CWM
Wiped Data
Formatted SD
Flashed Siyah via CWM
Rebooted
Saw I was stuck at Rethink Possible
Cussed
I seem to get stuck at the boot screen on ANY Gingerbread rom I flash. I can flash ICS roms and they boot successfully. However, my device has the 0x19 FW bug and I would like to not make it a paperweight.
Red_81 said:
I've followed these directions multiple times but I can't seem to get past the Rethink Possible screen.
Steps I have taken:
Flashed full binaries
Went back into download mode with no reboot and flashed CWM (listed above)
Went straight into CWM
Wiped Data
Formatted SD
Flashed Siyah via CWM
Rebooted
Saw I was stuck at Rethink Possible
Cussed
I seem to get stuck at the boot screen on ANY Gingerbread rom I flash. I can flash ICS roms and they boot successfully. However, my device has the 0x19 FW bug and I would like to not make it a paperweight.
Click to expand...
Click to collapse
Is this the "Oh crap its stuck in a bootloop I'll sell it cheap on eBay" SGII that you bought on ebay for cheap, or a different phone?
Do you know the history of this phone? Knowing it can help with troubleshooting.
Did you ever see the "Deleting cryption meta data" error message?
As far as having vulnerability to the eMMC firmware bug, you are safe as long as you don't use the buggy kernel, which is pretty much out of the picture by now.
LOL, you read my other post. It is one and the same. The standard story from the seller. "I gave it to my Brother in Law and now it is like this." He stated it did boot properly before. Liquid indicator checks out (haven't pulled the back off to check the full indicator).
I don't get the "Deleting cryption meta data" but I do get the "multi-csc error". Wiping data doesn't seem to take care of that one.
It's really odd because I can flash ICS roms with no problems, but the GB ones stick at the bootscreen every time. Even CM7 stuck there.
I may have to try to rule out hardware damage at this point
OK, so you don't really know exactly what was done to the phone. I wouldn't rule out hardware damage, but I seriously doubt it, at least let's assume that there is some explanation in firmware. Really, the only things that could be wrong:
bootloaders
param.lfs
partitioning
Which stock package did you flash, the one from the return to stock guide (that doesn't have bootloaders, etc.) or the one from the Download Repository that does have bootloaders?
And where exactly is the phone right now firmware wise?
creepyncrawly said:
OK, so you don't really know exactly what was done to the phone. I wouldn't rule out hardware damage, but I seriously doubt it, at least let's assume that there is some explanation in firmware. Really, the only things that could be wrong:
bootloaders
param.lfs
partitioning
Which stock package did you flash, the one from the return to stock guide (that doesn't have bootloaders, etc.) or the one from the Download Repository that does have bootloaders?
And where exactly is the phone right now firmware wise?
Click to expand...
Click to collapse
The one from the repository with bootloaders. I tried the one without bootloaders first, but it did not fix it.
Currently I flashed over to ShoStock2. However, I'm getting alot of problems on that too (Com.android.phone not responding).
I can try to flash back to stock at any moment because I have no data on the phone.
I did try using the latest version of Heimdall, but it kept crashing at 42% (from what I read that is a known bug)
So the one thing you have not tried is flashing PIT? I wouldn't try that next if it was my phone, however, since it is the area I know the least about. There is not a whole lot of information available about using PIT with the I777 (as in nothing I could find).
The behavior of flashing to ICS and running OK but bootlooping on Gingerbread is new to me.
If you have a jig, does the jig boot the phone to download mode?
The phone should be recoverable. If it was mine, I would start by flashing the full stock package with bootloaders and param.lfs again. Then wipe data/factory reset from 3e recovery. Then flash the Gingerbread Siyah kernel. And then wipe data/factory reset from CWM Recovery.
Actually, I thought I typed that before.
I did flash the PIT file at one point out of desperation.
I have a jig that works beautifully (wipes the counter too) and has been a big help through this whole thing. That tells me I should at least have the correct bootloaders.
Do I need to let it attempt to boot between each flash or just go directly one to the other?
After a little Google, I think your phone has a problem with efs, corrupted or some such. Read this.
creepyncrawly said:
After a little Google, I think your phone has a problem with efs, corrupted or some such. Read this.
Click to expand...
Click to collapse
I actually found and tried that a few days ago. Never got that error message before. But I flashed the repair anyway. No change.
I did manage to just let the phone run for a while and all the process error messages went away, but the dialer refuses to start. I also noticed I don't think I'm getting any sound out of the earpiece.
I think I'm going to have to take the back off to check for water damage and to make sure they didn't bleach the dot.
I'll attempt to do some more flashing later tonight if the wife lets me.
Under normal circumstances, if you get the multi csc error after flashing back to stock, a wipe data/factory reset will clear it, and it will boot successfully.
creepyncrawly said:
Under normal circumstances, if you get the multi csc error after flashing back to stock, a wipe data/factory reset will clear it, and it will boot successfully.
Click to expand...
Click to collapse
Lol. Under normal circumstances indeed. I appreciate all the help so far. I wonder if there is something borked with the chip.
Sent from my SAMSUNG-SGH-I897 using XDA
Not sure if it helps much since you said you think the correct bootloaders are there but I had the exact same problem as you a couple months back. Like an idiot I flashed the original "one click" ATT ICS leak from Rootzwiki that updated my bootloaders. After this attempting to go back to CM7 resulted in me soft bricking the phone. The ONLY rom that would flash and work was that same ICS one click. Everything else Odin just failed on. Eventually I managed to get the complete stock GB back on it by flashing the full package in creepys guide several times. I gave up on Odin on my pc and had to remove Kies from my Mac so Heimdall would work but it flashed finally and I was saved. If you search through my posts here and find that thread maybe there's something in there that will help cause it sounds like you're having a bootloader issue like I did..
Sent from my SAMSUNG-SGH-I777 using Tapatalk
Thanks. I'll take a look.
On a side note.... I can't get any sound from the device. I'm thinking now that it might be hardware related.
Sent from my SGH-I777 using xda premium
[Q][GT-I9100M Virgin/Bell] Can't Unbrick, always "Complete(Write) operation failed"
Hey everyone, thanks for taking the time to look at this and potentially help me with this issue. I'm pretty new to all of this, so I'm hoping for a little guidance in my moment of need!
First off, I'd like to say that I have tried just about every solution offered on this wonderful site and all to no avail... I currently own a SOFT-bricked (CAN open download mode, CAN'T open recovery mode) Samsung Galaxy S II (model number GT-I9100M) and have had no success in unbricking it. From what I gather (please correct me if any of this is incorrect) I need to flash the stock kernel for my phone, which should be the UGKG2 version that I have already downloaded and tried to flash. The issue I am having right now is that every time I try to flash using Odin3 v1.85 (KIES doesn't recognize my phone at this stage) I get the error "Complete(Write) operation failed." It doesn't matter what I attempt to flash, I always get this error and am told that the flash has FAILED.
The custom binary counter on my phone is up to 7 attempts now, and still no working kernel or even a working recovery mode.
A little backlog on how I ended up here, in tldr format:
1. Friend gave me the software-unlocked Virgin Mobile phone. He unlocked it so I could use it with my provider, Telus.
2. I received the JB update and allowed it to patch (unbeknown to me that it would re-lock my phone.)
3. Phone became locked and I didn't have a SIM-Unlock code (nor did I want to buy one...)
4. I attempted to re-root my phone and, long story short, something went wrong (wrong file perhaps). I can't remember what I did at this point, but the end result was that the phone would no longer load. I could only (and still can only) access download mode.
5. After several attempts of correcting my firmware and all that via searching threads, I decided to finally MAKE one so that I might get some direct help.
So now I'm here. As I've said, I have tried basically every solution that I have read about: changing my USB port, reinstalling KIES for my phone drivers, I have removed my SIM-card and Micro-SD, I have researched the firmware I need and am sure that I have the correct one, but ODIN still will not write. I have NOT done anything related to the bootloader or re-partition as I hear that tinkering there could REALLY put me in hot water, though if someone can tell me exactly what needs to be done to them (if anything) then I welcome the information.
Once again, thanks for reading and if you require ANY additional information or screenshots, please reply here and I will respond ASAP!
Do you have Kies installed on the computer you're trying to flash with? If so, ensure it's not running (kill via Task Manager) and try again perhaps... I had that happen to me when I was in the exact same situation as you and it worked for me ...
If not, try rebooting, kill Kies again, and try again. I've also had that work for me (oddly enough)..
@Porkchops: Thanks for the reply! I have tried re-installing KIES (for the Samsung drivers) and restarted my computer to allow for the drivers to finish the installation. After my computer restarts, I place the USB into a different port on the back of my computer and plug my phone into the cord. At this point windows identifies the device and its port, then I kill KIES through task manager (I have tried both killing KIES before and after plugging my phone into the computer, there doesn't seem to be a difference) and then proceed to open Odin. After Odin is open I then make sure only AUTO-REBOOT and F. RESET TIME are checked before proceeding to place the "Kernel_I9100MUGKG2.tar" (which I got from the forums here, cannot remember the link but I will post it when I find it, and yes my phone model is SPECIFICALLY GT-I9100M from Virgin Mobile).
UPDATE:
After Flashing this kernel, I get as far as I have yet (this is the ONLY KERNEL I HAVE FOUND that will PASS in odin, after doing all of these preparations for the flash) and my phone will load to the boot screen with the /!\ yellow triangle. From here, the phone will still not load however and sits at the Boot logo. After waiting over 20 minutes to see if it does anything else, I attempt to enter Recovery mode (Volume Up + Home + Power) and my phone screen changes to a Battery Charging screen with a frozen loading circle on the battery. This is where I am stuck at currently, however I am attempting to charge my phone as I type this to make sure that I am not getting this screen due to an empty battery!
Will post update if anything happens,
Cheers
IVT
Unplug your phone then try to get into recovery mode and do a factory reset. Also worth noting if you get a factory recovery mode or CWM... The S2 is nothing but a pain in the ass when the phone is plugged in and you're trying to turn it on
---------- Post added at 08:40 PM ---------- Previous post was at 08:38 PM ----------
Even if you can only get to recovery (And provided it's not stock recovery) you could always load a ROM onto your SD card (provided you have a micro SD card reader or something available) and install it from CWM/custom recovery ...
Porkchops said:
Unplug your phone then try to get into recovery mode and do a factory reset. Also worth noting if you get a factory recovery mode or CWM... The S2 is nothing but a pain in the ass when the phone is plugged in and you're trying to turn it on
---------- Post added at 08:40 PM ---------- Previous post was at 08:38 PM ----------
Even if you can only get to recovery (And provided it's not stock recovery) you could always load a ROM onto your SD card (provided you have a micro SD card reader or something available) and install it from CWM/custom recovery ...
Click to expand...
Click to collapse
I tried unplugging my phone and entering Recovery Mode though it still only loads to the Samsung Galaxy S II GT-I9100 boot screen with the yellow /!\ triangle. All attempts to enter recovery mode return me to this screen after the phone resets. I have a SD reader, though seeing as I cannot enter Recovery mode at this point, that wont help me yet (though you have a good point about putting the new ROM on it and installing it on the phone that way.) Any idea on how to re-obtain Recovery mode when I can only load as far as the Boot screen?
Thanks for the replies by they way, I appreciate them all.
EDIT: I've found that when trying to restart the phone while connected to a power source (either a wall socket or my computer's USB port) the phone will NOT load the boot logo, and instead loads the image of the empty battery with the frozen loading circle. Not sure if this information is important, but figure'd I would supply as much info as possible.
IVT
I think your issue might be that your phone is trying to run with a gingerbread kernel and a jelly bean firmware... If the GB kernel was flashed successfully, I would say try flashing a gingerbread firmware and see if you can get that to go.. If that won't work, perhaps try flashing a JB ROM that has a kernel included (the hard part will be finding one that can flash without CWM...
I think at the moment your best bet is to try the mgugk2 firmware though, since you already got the kernel flashed for it, then flash a Cf mgugk2 kernel to get CWM, do a nandroid backup and flash whatever you want through CWM from there
Porkchops said:
I think your issue might be that your phone is trying to run with a gingerbread kernel and a jelly bean firmware... If the GB kernel was flashed successfully, I would say try flashing a gingerbread firmware and see if you can get that to go.. If that won't work, perhaps try flashing a JB ROM that has a kernel included (the hard part will be finding one that can flash without CWM...
I think at the moment your best bet is to try the mgugk2 firmware though, since you already got the kernel flashed for it, then flash a Cf mgugk2 kernel to get CWM, do a nandroid backup and flash whatever you want through CWM from there
Click to expand...
Click to collapse
Thanks for the suggestion! Right now I have the firmware downloaded, however when I try to flash it through ODIN (I'm going to assume I still need to PDA flash it?) Odin FAILS to write, leaving me in the 100% soft-bricked state once again, not even loading to the boot screen until I re-flash the kernel. Suggestions or maybe links to somewhere here that would have the firmware I can use? Or possibly a link to somewhere that has the Kernel+Firmware AIO?
Thanks again,
IVT
UPDATE: I have successfully flashed CF-Root-SGS2_XX_OXA_KG6-v4.1-CWM4.tar in an effort to get CWM working. Im going to assume that the CF-root doesn't have the firmware packaged with it, as even with this flash I still reach the boot logo (though it DOES flash through Odin successfully.) Which firmware should I flash / How should I flash it, as I must be doing SOMETHING wrong to make every firmware flash fail when done through PDA.
Thanks
That's messed up that it will let you flash kernels without an issue but won't let you flash firmwares... Maybe try re downloading your firmware or run it against the MD5 hash as its possible it may have been corrupted during download. As for firmware, the exact version shouldn't matter as long and you match GB firmware with GB kernel and so on....
Flash siyah v5 and/or v6 from gokhanmoral.com and see if you can get to recovery.
You might wanna flash another ROM, maybe an I9100 JB ROM.
Thanks for the responses.
@Porkchops: Yea tell me about it, I have a feeling its this inability to flash firmware that's giving me the most grief. I have 3 versions of the firmware I need right now, though none of them work. I have tried ICS and JB stock wares, neither to any avail. As of yet the only non-stock / modified software ive been able to flash has been the KG6 CF-Root Kernel, though still no success with ROMs or stock Firmware. Thanks for all of your responses, what would you reccomend I do at this point? Would it be worth looking for an old version of a kernel and an older firmware? (ie should I maybe try to get a GB kernel and firmware running if I cant find a working match of ICS or JB?) Thanks again!
@gastonw: Hey thanks for responding,I dont have a vast knowledge of all this yet so bare with me. Would the Siyah kernel leave me rooted (like the CF-Root Kernels) or would I need to root it after flashing? This wouldnt affect me using it, I just like to know what I'm getting into. Also what ROM would you reccomend pairing with this kernel? Would I simply PDA flash Siyah and PDA flash the ROM after the phone auto-restarts? Thanks again,
Cheers to both of you,
IVT
How long are you pressing the buttons for entering recovery?
Keep volume up + home button + power button pressed for as long as it takes. Mines restarts about three times before entering recovery. If you flashed CF-root succesfully, then you should be able to enter recovery mode.
If that doesn't work, try restoring your phone with plain old Kies. I'm not sure if it works, but give it a shot. Here is the how-to.
http://forum.xda-developers.com/showthread.php?t=1984717
@Lennyz1988: Thanks for the reply. So far I have only tried entering recovery up to two restarts (restarting once with Vol. Up + Home + Power, then doing it again once it restarts) though I have not tried three times like you said worked for you. I will try this when I get home today though and I'll post an update when I test it. As for KIES im a little out of luck using it, as my phone isn't recognized by KIES in its current state (even though I have all of the proper drivers, I guess not having a working firmware is blocking KIES from interaction with the device? Thanks for the suggestion, do you have any idea of being able to recover my phone enough so that KIES will recognize it again? I have tried something similar to the guide you linked but after I selected my device and enter my serial, KIES gives me some error stating that no firmware could be linked to the device I entered? I could have entered it wrong, though I tried about 2 or 3 times with no luck. I will try the exact way the guide explains when I get home today, so thank you for the link and suggestion. Also, thanks for the reply by the way!
Re: [Q][GT-I9100M Virgin/Bell] Can't Unbrick, always "Complete(Write) operation faile
Siyah will get you rooted and will install CWM recovery.
Sent from the little guy
UPDATE: Ok, so my current status today is as follows.
1. I have tried the suggestion of multiple restarts to get into Recovery Mode while the CF-Root kernel is flashed, however the situation did not change and I still only get the boot logo screen with the yellow /!\ triangle. I have tried holding for a total of 5 minutes and nothing happened, same goes for holding the buttons until it restarts, releaseing the buttons, and repressing them to restart again. No change after 10 restarts, but thanks for the suggestions! Any other ideas to share?
2. I have attempted to follow the link provided for recovering through KIES, however when I enter my model and s/n KIES gives me the message "GT-I9100 does not support initalising." I have also tried using my exact model, which is the GT-I9100M and still got the same message, except that it said "GT-I9100M does not support initalising." Not sure if I entered something incorrectly? I make sure that the model number is all capitalized as GT-I9100 and GT-I9100M, and I enter all 11 characters from my S/N (serial number). Have I done this wrong or is there some reason that KIES doesn't support my phone?
3. Currently about to try flashing Siyah and going to see how that works, I will post an update once I get the results.
UPDATE: Ok I have been able to flash Siyah, however I still cannot enter recovery mode. Any suggestions on a ROM to try and flash? As I've said, im using a Samsung Galaxy S II, model GT-I9100M from Virgin Mobile in Canada. Do I need a kernel with UGKG2 support, as that's apparently the proper firmware version that I need for this device?
Once again, many thanks to all of you for your time.
Cheers,
IVT
UPDATE (02/25 4:50pm EST): Still having immense troubles getting recovery mode to boot... I have tried using the following:
KERNEL: CF-Root ; FLASH: Successful ; RECOVERY MODE: Unable to access
KERNEL: Siyah ; FLASH: Successful ; RECOVERY MODE: Unable to access
KERNEL: CWM Recovery ; FLASH: Successful ; RECOVERY MODE: Unable to access (http://forum.xda-developers.com/showthread.php?t=1118693&highlight=kg2)
Could the issue with flashing ROMs and being unable to enter Recovery Mode both be caused by my phone not being wiped? If so, is there any way to hard-wipe the device without using a recovery manager?
Thanks,
IVT
Alright.
1. Uninstall kies completely.
2. Download the latest version of kies.
3. Install kies and make sure the drivers are selected during the install process.
4. Disable virusscanners
5. Put the device in download mode.
6. Plug the device in a backport usb (not the front). Also try different usb cables. Some work and some don't.
7. Kill all kies processes in the task manager.
8. Download the latest version of Odin. Also keep the 1.85 so you can try both. Make sure you run Odin as an Administrator!
9. Try to flash now.
If it fails, try a different cable. Then try the same procedure on a different pc. If it keeps failing report back.
Btw, I9100M is the same as I9100.
Here is a thread with stock firmwares:
http://forum.xda-developers.com/showthread.php?t=1544487
First try the latest. DONT use .pit or re-partition yet. If that one does not work try this version:
I9100XWLP3
And if that doesn't work, try only flashing CWM recovery. Try first the JB version and if it fails the ICS.
http://forum.xda-developers.com/showthread.php?t=1118693
Re: [Q][GT-I9100M Virgin/Bell] Can't Unbrick, always "Complete(Write) operation faile
Amen to the above.
I, on the other hand, would like you to flash this: http://www.sammobile.com/2012/11/15/i9100xxlsj-–-galaxy-s-ii-android-4-1-2-jelly-bean-test-firmware/
Only CODE, MODEM and CSC.
If the flash is successful, you should be able to pass the boot animation.
Sent from the little guy
Can you post the complete logs from Odin after trying the above? Please use something like http://pastebin.com so the topic won't get filled.
If the above fails then we will try flashing a bootloader and after that we could try using .pit and re-partition.
Re: [Q][GT-I9100M Virgin/Bell] Can't Unbrick, always "Complete(Write) operation faile
I think odin flashes are successful all the time in this case.
Sent from the little guy
Alright guys, thanks for the in depth and excellent suggestions! Currently downloading I9100XXLSJ (I9100XXLSJ_I9100OXXLS1_OXX) from gastonw's suggestion and will post what Odin does in this case. Once its finished downloading I will grab the newest version of firmware from your suggestion Lennyz1988 (have to wait between downloads, both HF mirrors) and will also post what happens when/ if I flash that (in the case that the JB Test firmware fails.)
Before flashing either I will uninstall KIES, reinstall it with drivers, disable all anti-spyware and anti-virus software, use a backport USB, and attempt using both v1.85 and v3.04 of ODIN3. I will also attempt to use all 3 windows-based machines in my house to attempt to flash, as well as trying all 4 of the cables available to me. I'm hoping that by using all of these precautions I will have success eventually.
Also, after I reinstall KIES windows update tries to re-find drivers for my phone too upon connection to my usb port. Should I let windows find the drivers or cancel it? Worst case scenario I could always try with both, letting it finish installing the drivers it finds and rejecting its installation, though I guess the safest bet is to just reject WU from downloading its own.
Well, I apparently have a heap of work ahead of me, with all of these variations to try.
(3 computers) * (4 cables) * (2 odin versions) * (11 total USB ports) = 264 variations to try, not including different firmware attempts! Seems insane, so I'm hoping I don't need to wait until the 263rd (or more) for success. I will post a pastebin of my ODIN logs as I go, so expect regular updates.
Once again, thanks for all of the help everyone. I seriously appreciate your time and input!
Cheers,
IVT
EDIT: I just want to clear up some murky understanding here, but when I flash a kernel do I need to then find a corresponding firmware and flash that afterwards? Or should I be able to get into Recovery Mode with just the kernel? Also when I do flash firmware, do I need the kernel installed BEFORE I flash firmware / ROMs or does it matter what order I do it in (I'm assuming that you need a kernel already flashed before the firmware will even flash at all?) And lastly, do I need a working stock firmware present before I can flash a modified ROM? If anyone has a good link for me to read/ watch an explanation on how modded kernels interact with modded ROMs I would appreciate the extra information (I'm trying to understand if maybe I'm not using compatible kernels and ROMs.)
Thanks everyone!
UPDATES: The following were done in order from top to bottom, meaning that CWM v5 was done first, followed by flashing CWM v5, etc etc... All flashes (unless stated otherwise) were flashed with ONLY [F. Reset Time] and [Auto Reboot] checked!
Kernel: CWM Recovery [ICS - 5.5.0.4]
Odin Version: v3.04
Flash: SUCCESSFUL
Recovery Mode: NO
Download Source: http://forum.xda-developers.com/showthread.php?t=1118693
Pastebin: http://pastebin.com/MR97fJLz
Kernel: CWM Recovery [JB - 6.0.2.7]
Odin Version: v3.04
Flash: SUCCESSFUL
Recovery Mode: NO
Download Source: http://forum.xda-developers.com/showthread.php?t=1118693
Pastebin: http://pastebin.com/vGWmdjkc
*NOTE: Upon reset and testing for Recovery access, I have found that after removing/ reinserting my battery and holding Vol.Up + Home + Power the phone will reset and still give me the boot logo with the yellow /!\ triangle, however if I keep the buttons held the screen will flash to black for a second before again returning to the boot logo screen. This will only happen once, and the device will not flash to black again if I keep the buttons held for any extra time. not sure if this is useful, though I am trying to provide any information I can.
Firmware: I9100XXLSJ + CSC + MODEM (provided by gastonw's link)
Odin Version: v.3.04
Flash: FAILED
Recovery Mode: NO
Download Source: http://www.sammobile.com/2012/11/15/i9100xxlsj-–-galaxy-s-ii-android-4-1-2-jelly-bean-test-firmware/
Pastebin: http://pastebin.com/VqTu5GyS
*NOTE: I place CODE_I9100XXLSJ.tar in [PDA], MODEM_I9100XXLS6.tar in [PHONE], and CSC_HOME_OXX_I9100OXXLS1.tar in [CSC].
*NOTE: This was flashed after the CWM Recovery JB version (v6). Not sure if the CWM kernel would affect the flashing of this firmware? Im going to try flashing the beta JB Siyah v6.0b5 (which I know will flash) and then the firmware again to see if there is any change...
UPDATE: After trying to flash the Siyah kernel and then reflash the test firmware above, ODIN still fails.
Here is the pastebin: http://pastebin.com/e4hDW9F7
SEMI-UPDATE: Also, I've noticed that occasionally Odin will lag before failing (sometimes the program stops responding for a moment, but it comes back. Other times it just a looooong time to do anything and then fails.) Sometimes Odin just completely hangs, doesn't stop responding but stays at the "Firmware update start" step.
Besides this little problem, I also notice that I have yet to find a .md5 that will successfully flash. Not sure if its connected to the format or just my usual flashing problem though.
Lastly, the error log for writing .md5 files is as follows (this was I9100XWLP3_I9100O2ULP4_I9100XXLPR_HOME.tar.md5 that was recommended):
Pastebin: http://pastebin.com/AYhxSywi
invalidtarget said:
Alright guys, thanks for the in depth and excellent suggestions! Currently downloading I9100XXLSJ (I9100XXLSJ_I9100OXXLS1_OXX) from gastonw's suggestion and will post what Odin does in this case. Once its finished downloading I will grab the newest version of firmware from your suggestion Lennyz1988 (have to wait between downloads, both HF mirrors) and will also post what happens when/ if I flash that (in the case that the JB Test firmware fails.)
Before flashing either I will uninstall KIES, reinstall it with drivers, disable all anti-spyware and anti-virus software, use a backport USB, and attempt using both v1.85 and v3.04 of ODIN3. I will also attempt to use all 3 windows-based machines in my house to attempt to flash, as well as trying all 4 of the cables available to me. I'm hoping that by using all of these precautions I will have success eventually.
Also, after I reinstall KIES windows update tries to re-find drivers for my phone too upon connection to my usb port. Should I let windows find the drivers or cancel it? Worst case scenario I could always try with both, letting it finish installing the drivers it finds and rejecting its installation, though I guess the safest bet is to just reject WU from downloading its own.
Well, I apparently have a heap of work ahead of me, with all of these variations to try.
(3 computers) * (4 cables) * (2 odin versions) * (11 total USB ports) = 264 variations to try, not including different firmware attempts! Seems insane, so I'm hoping I don't need to wait until the 263rd (or more) for success. I will post a pastebin of my ODIN logs as I go, so expect regular updates.
Once again, thanks for all of the help everyone. I seriously appreciate your time and input!
Cheers,
IVT
EDIT: I just want to clear up some murky understanding here, but when I flash a kernel do I need to then find a corresponding firmware and flash that afterwards? Or should I be able to get into Recovery Mode with just the kernel? Also when I do flash firmware, do I need the kernel installed BEFORE I flash firmware / ROMs or does it matter what order I do it in (I'm assuming that you need a kernel already flashed before the firmware will even flash at all?) And lastly, do I need a working stock firmware present before I can flash a modified ROM? If anyone has a good link for me to read/ watch an explanation on how modded kernels interact with modded ROMs I would appreciate the extra information (I'm trying to understand if maybe I'm not using compatible kernels and ROMs.)
Thanks everyone!
UPDATES: The following were done in order from top to bottom, meaning that CWM v5 was done first, followed by flashing CWM v5, etc etc... All flashes (unless stated otherwise) were flashed with ONLY [F. Reset Time] and [Auto Reboot] checked!
Kernel: CWM Recovery [ICS - 5.5.0.4]
Odin Version: v3.04
Flash: SUCCESSFUL
Recovery Mode: NO
Download Source: http://forum.xda-developers.com/showthread.php?t=1118693
Pastebin: http://pastebin.com/MR97fJLz
Kernel: CWM Recovery [JB - 6.0.2.7]
Odin Version: v3.04
Flash: SUCCESSFUL
Recovery Mode: NO
Download Source: http://forum.xda-developers.com/showthread.php?t=1118693
Pastebin: http://pastebin.com/vGWmdjkc
*NOTE: Upon reset and testing for Recovery access, I have found that after removing/ reinserting my battery and holding Vol.Up + Home + Power the phone will reset and still give me the boot logo with the yellow /!\ triangle, however if I keep the buttons held the screen will flash to black for a second before again returning to the boot logo screen. This will only happen once, and the device will not flash to black again if I keep the buttons held for any extra time. not sure if this is useful, though I am trying to provide any information I can.
Firmware: I9100XXLSJ + CSC + MODEM (provided by gastonw's link)
Odin Version: v.3.04
Flash: FAILED
Recovery Mode: NO
Download Source: http://www.sammobile.com/2012/11/15/i9100xxlsj-–-galaxy-s-ii-android-4-1-2-jelly-bean-test-firmware/
Pastebin: http://pastebin.com/VqTu5GyS
*NOTE: I place CODE_I9100XXLSJ.tar in [PDA], MODEM_I9100XXLS6.tar in [PHONE], and CSC_HOME_OXX_I9100OXXLS1.tar in [CSC].
*NOTE: This was flashed after the CWM Recovery JB version (v6). Not sure if the CWM kernel would affect the flashing of this firmware? Im going to try flashing the beta JB Siyah v6.0b5 (which I know will flash) and then the firmware again to see if there is any change...
UPDATE: After trying to flash the Siyah kernel and then reflash the test firmware above, ODIN still fails.
Here is the pastebin: http://pastebin.com/e4hDW9F7
SEMI-UPDATE: Also, I've noticed that occasionally Odin will lag before failing (sometimes the program stops responding for a moment, but it comes back. Other times it just a looooong time to do anything and then fails.) Sometimes Odin just completely hangs, doesn't stop responding but stays at the "Firmware update start" step.
Besides this little problem, I also notice that I have yet to find a .md5 that will successfully flash. Not sure if its connected to the format or just my usual flashing problem though.
Lastly, the error log for writing .md5 files is as follows (this was I9100XWLP3_I9100O2ULP4_I9100XXLPR_HOME.tar.md5 that was recommended):
Pastebin: http://pastebin.com/AYhxSywi
Click to expand...
Click to collapse
EDIT: I have noticed that basically all firmware and md5s fail at NAND Write. I hear this can be fixed through reinstalling the proper USB Drivers (will attempt to do this, AGAIN...) but can also mean that my NAND Memory is corrupted (a little pessimistic to think down this line, because I'm pretty sure that means my phone is finished...) I doubt its corrupted since I can flash kernels still, but I'm no expert. Any observations, insight, or opinions are welcome.
Thanks,
IVT
Edit: Was just looking around and kind of thought of something. If my NAND Writing is the problem, wouldn't repartitioning my phone offer a potential fix? Could the problem I have with accessing my Recovery be because of the messed up partitions?
Someone give me some feedback on this idea, and if you agree how would I go about doing something? I've heard to generally stay away from PIT and Bootloaders, as they are a little less forgiving than firmware and kernel flashing.
This is a special case that requires extensive help from you guys (hopefully).
Problem: According to the ATT Samsung specialist the Bootloader I am using is corrupted
Attempted Solution: I have attempted to flash the stock SBL onto my phone but after trying every version of Odin3 (1.83-3.09) it did not work.
**The bar was entirely GREEN but it never finished**
Suggested Solution: Flash the stock ROM back onto the phone using Odin3
Outcome: After trying three different ROMs, all downloaded from Sammobile, using every version of Odin3 (1.83-3.09) only seemed to reach the end then fail at Modem.bin
I was wondering if anyone has any idea how to fix my phone, the original issue was that it never made it past the Samsung logo (not the Galaxy S2 Logo but the actual Samsung logo) the new issue is that it has the Samsung Galaxy SII Logo with the wrong model name (international model) and the small yellow triangle.
If my phone is permanently broken that's fine because I have a temporary phone I just want to get my files off of the phone before using my new one
I have a Jig
I can get it into Odin mode
I cannot get it into Recovery mode
I can get it into Factory mode
Help me please, I have no idea what else to do
Use this version of Odin, or just do more Google fu and find another place to download it from. [ http://forum.xda-developers.com/showpost.php?p=20229527&postcount=46 it may be the version of Odin you're using that's messing you up.
The link Phalanx7621 posted was supposed to point to the Download Repository (link is in my signature.)
The preferred version of Odin is 1.85. If you need it, the download link for Odin3 v1.85 at the top of the Download Repository is a working link.
If the boot loader was corrupt, the phone would be a true brick (no sign of life.) If the secondary boot loader was corrupt, the phone would not boot as far as the Samsung logo. It sounds to me like the AT&T Samsung specialist you received that information from was not fully informed.
The I9100 splash screen with the yellow warning triangle is due to flashing a custom kernel, so nothing to worry about. It can be cleared by flashing a stock kernel. Using the following procedure would have put that on your phone anyway by flashing the Siyah kernel, and then will removed it when stock Gingerbread is flashed.
Please note: The link in the Download Repository for the stock Gingerbread that you need to flash is not working, and I have yet to re-upload all these items to a new host. You will have to download this from the sammobile firmware page. It is the I777UCKH7 / I777ATTKH7 dated 2011 August. You'll need to sign in to download it. The registration is free. Edit: sammobile has not uploaded this file to a new host yet either. I will have to upload it and the sbl for you, but since today is Christmas, you may have to wait a day or two. At least you know that there will eventually be something to try.
Edit: The required files are now available with Dev-Host links in the Download Repository.
I think you will probably recover the phone by assuming it has nand read/write corruption and following this sequence:
Instructions to clear nand read/write corruption.
Odin3 v1.85 is recommended.
1) Download the Tar version of Siyah 2.6.14 Kernel. Flash it in PDA. Without ticking Re-Partitioning
2) Flash the Tar.md5 of the full stock Gingerbread distribution from the Download Repository, I777UCKH7 including the bootloaders and everything, in the PDA slot.
3) If that is successful you are done. If it is not, then:
4) Download the SBL Bootloader from the Download Repository. Flash it as PDA in ODIN, without ticking Re-Partitioning. (Please observe normal bootloader flashing caution.)
5) Flash the Kernel, as in step 1.
6) Flash the full stock Gingerbread distribution, as in step 2.
Attempt #1
When attempting to flash the Kernel in Odin3 v1.85 the bar was fully green but the program never said complete (I left it going for a few hours to no avail)
I tried flashing the SBL and the same issue happened, the bar was fully green but it never said complete (I had previously downloaded the SBL)
When attempting to flash the Gingerbread stock it does not even go past the SBL1 part, the bar does not have any green within it and the program still says NAND Write Start.
I'm not the best with this sort of thing but from observation it seems that my NAND is corrupt and isn't allowing anything to be properly flashed.
By the way: the Custom Binary Download now says: Yes (5 counts) which tells me that the phone recognizes that something is being flashed but it's not working properly
I'm back to being stuck and I think this phone may be truly broken :/
I don't think ur phone is broken.
Try a different usb/micro usb cable. Try a different usb port on ur pc (don't use a usb hub). Make sure the phone's micro usb port is clear of dirt/debris, etc.
Usually when i've had problems with Odin flashes it is something as simple as doing these things that results in a successful flash.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Same Issue
I'm having the same issue exactly as OP. The green bar loads, but then stops at NAND Write Start. I've switched usb ports, pcs, and cords and nothing seems to work. Is my phone beyond repair then?
androidrequest said:
I'm having the same issue exactly as OP. The green bar loads, but then stops at NAND Write Start. I've switched usb ports, pcs, and cords and nothing seems to work. Is my phone beyond repair then?
Click to expand...
Click to collapse
Did you follow exactly the sequence in post #3? If not, please try that.
creepyncrawly said:
Did you follow exactly the sequence in post #3? If not, please try that.
Click to expand...
Click to collapse
Yes, I tried that sequence exactly. It actually won't advance past #1. The green bar loads in Odin under kernel, but stops working at NAND Write Start. And trying the sbl ends with the same result (I believe it's the first download in the Download Repository). All of the flash attempts have failed or frozen, but the Custom Binary Download count is at 3.
I flashed a few roms like PACman and SHOstock and it booted up but it seems that it was lagging quite badly and camera showed a black screen. I thought it was the phone's camera that was broken. I flashed the UCLE5 rooted found here: http://forum.xda-developers.com/showpost.php?p=20229527&postcount=46 and it booted up just fine. However, camera crashes when I tried to take a picture (atleast it's not a black screen now) and it randomly crashes and reboot.
When I tried to flash UCKH7, I get stuck on the "Rethink Possible" screen and did not get anywhere else.
Can anyone help me? I bought this phone for my brother and the previous owner flashed some stuffs already so I just want it back to its original state with stock before going forward with custom roms..
Boot into recovery. With the phone off, hold all three buttons, vol+ vol- pwr, until the initial screen shows, goes black and shows again, then release buttons. Once in stock recovery, perform a wipe data/factory reset. After this, the phone should boot. Then test the camera to see if it is working correctly, and test other functions of the phone.
Does the previous owner say the phone was working fully functional before you got it?
If you get the phone to boot and working correctly, then you should flash the latest stock firmware which is UCMD8, or a good stable custom firmware. Be happy to help with that as well.
I performed the wipe in the stock recovery and it is stuck at the "Rethink Possible" screen. Only time that I got it to boot was to load the UCLE5. UCKK6 and UCKH7 didn't boot for me. I will try the UCMD8 but I don't understand why 1 stock would boot while the other one didn't.
Previous owner said it was working okay for him but he didn't know about the phone being rooted and made some kind of update or changes to the phone (software wise). I'm guessing he flashed it weirdly or something like that. I saw the count as 25 when I got into the "download recovery" portion to flash UCLE5 through ODIN. Maybe he flashed it wrongly and it has messed something up.
Since a wipe data/factory reset will not clear the problem, it is safe to assume that there is some issue with memory. Since your were able to get the phone to boot at least once, but it was not functioning normally, it is fairly safe to assume that the memory is not permanently damaged. Based on these assumptions, I would guess that there may be nand read/write corruption. My reasoning may be incorrect, but it is sensible to try to clear the nand r/w corruption next to see if that will clear up the issues.
Instructions to clear nand read/write corruption. It is critical to follow these steps in order.
Odin3 v1.85 is recommended.
Perform a wipe data/factory reset both before, and after if needed.
1) Download the Tar version of Siyah 2.6.14 Kernel. Flash it in PDA Without ticking Re-Partitioning
2) Flash the Tar.md5 of the full stock Gingerbread distribution from the Download Repository, I777UCKH7 including the bootloaders and everything, in the PDA slot.
3) If that is successful you are done. If it is not, then:
4) Download the SBL Bootloader from the Download Repository. Flash it as PDA in ODIN, without ticking Re-Partitioning. (Please observe normal bootloader flashing caution.)
5) Flash the Kernel, as in step 1.
6) Flash the full stock Gingerbread distribution, as in step 2.
I followed all of your steps and it seems that I am still at the "Rethink Possible" screen. Even after flashing and wiping everything according to your directions.
I downloaded the "I777UCKH7-REV02-home-low-CL503881.tar.md5.7z" which I assumed was the full UCKH7 that you mentioned in your post. After flashing and wiping, it still hangs. I flashed the "I777 UCKH7 sbl.tar" and repeated step 1 and 2, wiped and it still hangs.
When I am doing a "wipe data/factory reset" I see an error under "Appling Multi-CSC".
This is what I see,
Installing Multi-CSC
Can't access to '/system/csc/ATT/system/'.
Successfully applied multi-CSC
Click to expand...
Click to collapse
Does this have anything to do with the hanging at the boot screen?
nomoney4me said:
Does this have anything to do with the hanging at the boot screen?
Click to expand...
Click to collapse
I'm not sure. Most of what I know about this phone is gained from observation of the information that people have posted in these forums over the past two and a half years. I haven't seen an issue exactly like yours, as far as I can remember. There was one case where the phone would boot into the system, but not function properly. When it was sent to Mobile Tech Videos for jtag repair, it was found to have damaged emmc memory. I just don't know whether your issue is similar to that one or not. Any further advice is beyond the scope of my understanding.
What I have seen happen a few times is that if a person keeps trying to get the phone working, eventually some operation (flash or whatever) works differently and the phone then works. This would indicate trying different equipment, as in different pc, different cable, etc. I know that the flash is completing successfully so I don't know if this is irrelevant advice or not.
Another thing to try could be re-partitioning the memory when you flash. There is an I777 pit in the download repository. I have no experience with using it, but I remember at least two cases where a phone was recovered by flashing the pit. In one case, flashing the pit with the firmware the first time didn't clear the problem, but then flashing the firmware again worked. Flashing the pit is generally considered risky, especially if you don't know exactly what the correct steps are, but at this point, what is there to lose?
I got myself an AT&T branded S2 (i777). I used Samsung Kies to update to the latest firmware and something happened while doing so. I turn on the phone now and it says "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
Recovery in Kies doesn't work.
I can get into download mode. Although I can't seem to get Odin to be successfully done, always fails.
Is there any solutions to fix my problem?
I have searched and found fixes for the international version, but that does me no good as mine is the SGH-I777. I just want to be able to have a working phone again.
I'm pretty sure we can get your phone back to working.
A more detailed description of your inability to flash with Odin would be helpful.
What were you trying to flash?
Were you able to get Odin to recognize the phone?
What were the error messages in Odin?
After you answer, I'll give you some things to try.
That would be awesome.
- Tried using I777UCKH7-CL503881-Full it gets to sbl.bin and then fails.
- Tried using Odin v1.85 with a stock i777 tar file. Sticks at factoryfs.img and then fails.
- Odin does recognize the phone.
The majority of issues with failed flashes have to do with the connection between the computer and the phone. The standard advice is, use another cable, use another USB port on the computer, or even use another computer. However, lets skip that step for now, and assume that the connection is good.
It's possible that there is an issue with nand read/write memory corruption. Let's see what happens if we clear nand r/w memory. I assume that you know how to use Odin correctly, but if you want additional instructions, I can post some.
Instructions to clear nand read/write corruption. Instructions are specific; do them in order, and don't skip.
Odin3 v1.85 is recommended.
1) Download the Tar version of Siyah 2.6.14 Kernel. Flash it in PDA. Without ticking Re-Partitioning
2) Flash the Tar.md5 of the full stock Gingerbread distribution from the Download Repository, I777UCKH7 including the bootloaders and everything, in the PDA slot.
3) If that is successful you are done. If it is not, then:
4) Download the SBL Bootloader from the Download Repository. Flash it as PDA in ODIN, without ticking Re-Partitioning. (Please observe normal bootloader flashing caution.)
5) Flash the Kernel, as in step 1.
6) Flash the full stock Gingerbread distribution, as in step 2.
Link to the download repository is in my sig.
---------- Post added at 09:04 PM ---------- Previous post was at 08:57 PM ----------
The latest stock for this phone is I777UCMD8, which you can also get in the Download Repository. I would suggest you flash that after you get the phone back to working. Or, if you want to customize, there are good versions of custom firmware available in the forums.
I try to check in to the forums every couple of days, at least. It was just serendipity that I came into the forum 10 minutes after you posted. I'll try to remember to keep an eye on this thread more often, but sometimes I get a littly busy, so if I'm mia, just be patient.
Re-tried Siyah with a different cable and used back usb ports instead. Was successful with Siyah.
I don't want to mess the phone up anymore than needed, which exact one should I flash?
fluttershys said:
Re-tried Siyah with a different cable and used back usb ports instead. Was successful with Siyah.
I don't want to mess the phone up anymore than needed, which exact one should I flash?
Click to expand...
Click to collapse
Okay. Maybe your issue was only a connection issue. But I would suggest that you complete the sequence above exactly as written. As it says, instructions are specific; do them in order, and don't skip.
If the issue is nand r/w corruption, this should fix it. If that was not the issue, this will not do any harm. The firmware used is the oldest original firmware for the I777, and is seriously out of date. But it is known to fix the specific issue of nand r/w corruption.
Once you have the phone working normally, ie. booting into system without issue, then you should probably flash the latest stock firmware as I suggested earlier, or the custom firmware of your choice.
Thank you for all the help. I was actually able to use Kies and re-do the firmware that way. I have done the framaroot root.
Is there a ROM and Kernel that you would suggest using for the I777?
You need to decide whether you want firmware that is Samsung touchwiz based, or AOSP based.
If you want touchwiz, you should look at cooked or SHOstock3. No one is doing active development right now, but these two are stable and each is good in its own way.
If you want AOSP, I can't recommend anything since I haven't flashed them, but would suggest you read the development forum and look at the threads for firmware that have been actively posted in the past few months.
The latest touchwiz is Jelly Bean, but with AOSP you can get Kit Kat, or even Lollipop.