Page 1 of 2 12 LastLast
Results 1 to 25 of 28
Like Tree8Likes
  1. Thread Author  Thread Author    #1  

    Exclamation IMPORTANT! READ THIS - Regarding the EMMC Brick Bug on the E4GT

    ** UPDATE ** 7/27/2012

    As of today, many Kernel + Recovery packages have been modified to remove the offending function that can trigger the EMMC brick bug. For full information on the bug, refer to the link to the XDA thread I posted in the 6/19/2012 update.

    The important thing here is that if you are going to perform any wipe data, format system, restore nandroid backups or any other functions in recovery that involves partition formatting, you need to be 100% sure you are doing it from a confirmed "SAFE" kernel/recovery repack. Most if not all recently released kernels will very likely be safe from the bug, and state as such in their description. But, there are still some older "unsafe" kernels floating around, so make sure you know what's on your phone before you use your custom recovery to flash anything else.

    Also, in a real head scratcher, Samsung never did remove the offending function from their kernel. Android developers for the E4GT have had to do it after the fact. Then again, knowing Samsung software development, I probably shouldn't be surprised by this.

    I'm going to leave the information from the original post below for reference for the time being, however some specifics may be outdated as of today.


    ** UPDATE ** 6/19/2012

    Thanks to the efforts of Android Central and XDA forum members sfhub , garwynn, and Entropy (who worked on this issue on the Galaxy Note), and the countless others who offered insight, as well as a few who risked and in at least one case, bricked their own device, the cause of the EMMC failure (also referred to as a lockup) has been identified. The real golden bit of information came from communications that garwynn was able to initiate with an Android programmer at Google.

    Information on the entire issue can be found here:

    This is a bit technical, but it's the bottom line ...

    We now have an update on why this bug is happening and which PRV/fwrevs are affected. PRV/fwrev 0x19 are susceptible to the EMMC /data corruption issue (which should now be referred to as EMMC lockup issue). PRV/fwrev 0x25 has the fix for the lockup issue but has a separate 32KB of zeros data corruption issue, which is being patched in the kernel (our kernels don't have that patch). All these problems are in the EMMC firmware. It can potentially be updated, but nothing is publicly available. EMMC lockup issue is triggered on erasing the EMMC. The only piece we have not been able to explain is why GB-based kernels seem immune to the EMMC lockup problem whereas ICS seems more susceptible to the problem. Presumably both are doing ERASE commands, but possibly in slightly different ways.


    As of this update, we do not quite yet have the all clear to go wiping data from an ICS kernel. It's looking very likely that Samsung has fixed the issue by removing the MMC_CAP_ERASE function from the mmc driver (I think I got that right), but we won't know for sure until the source code for our final ICS build is published. Until source code is released, and all ROM and kernel developers get on the same base, I think it's best practice to continue to exercise caution and only perform data and system formats from a recovery that is packaged with the Gingerbread based EL26 kernel. This will ensure that you will not lock your EMMC chip up until the all clear is given.


    Original post follows (dated 3/14/2012) ...

    Okay guys. The purpose of this is to get a sufficient warning posted, and potentially save you the headache of hard bricking your E4GT, if you decide to flash one of the ICS leaks or unofficial CM9. Many people have bricked their phones over the last 6ish weeks, and my goal is to help readers who come here not suffer the same fate. Here's what's going on ....

    So on the E4GT, recovery is packaged together with the kernel (like all Samsung phones and many others). So in order to install custom recovery like the popular Clockwork Mod (CWM), you need to flash a new kernel that's been repackaged with it. However, it's been determined that something about the stock ICS kernel for our phone and CWM MAY corrupt and/or damage the data partition of flash memory. When a ICS+CWM kernel is running on your phone, and you boot into recovery and perform a format (also known as a wipe), there is a chance that flash memory will become damaged and your phone will be hard bricked. There have been some brick situations where even a JTAG could not write to the data partition and recover the phone. THIS IS BAD JUJU! When JTAG can't revive a phone, you know this is particularly nasty and something you'd want to avoid.

    So, it is highly recommended that once you have ICS or CM9 on your phone, before you change to ANYTHING else that involves a format or wipe of any partitions, that you Odin back to a Gingerbread ROM and Kernel+CWM, and then flash from there. While this takes more time, it's the safest way to work with these builds right now, until this gets figured out. Also, DO NOT RESTORE A NANDROID BACKUP OF YOUR GB ROM WHILE ON A ICS+CWM KERNEL ... ODIN BACK TO ONE MANUALLY, THEN RESTORE YOUR BACKUP FROM THERE! I bold this because on a Nandroid restore, just about every partition is formatted so you risk bricking your phone.

    If you have an ICS leaked build or Unofficial CM9 on your phone, please heed the following warnings ...

    [WARN]* DO NOT use ROM Manager at all, and more importantly, do not use ROM Manager to load Temp CWM to flash anything!
    * DO NOT use ANY version of Clockwork Mod TOUCH Recovery to format internal storage or flash anything!
    * DO NOT perform a /system or /data wipe using CWM while on an ICS kernel! Use Odin to flash back to a Gingerbread ROM and Kernel+CWM then move to something else ICS related from there.
    * DO NOT try to restore a Nandroid backup in CWM while on a ICS kernel! [/WARN]

    Working with the Samsung ICS Leak Builds

    So say for example, you have the stock FB27 ICS leak on your phone, and you want to try Calkulin's custom FC07 ROM. Follow these steps ...

    1) Download the and follow the instructions to flash the stock EL29 ROM and kernel.

    2) Download sfhub's and follow the instructions to install the EL29+CWM kernel repack.

    * NOTE: sfhub created a special one-click package that already includes the EL29 kernel+CWM for use in flashing back to GB from a ICS build. However, flashing this in Odin increases the flash count and causes the yellow triangle on the boot screen. If you know how to deal with these, feel free to use it. If not, I suggest doing #1 and #2 as it avoids this issue.

    3) Download Calkulin's FC09 ROM, the FC09 modem, and Calkulin's Format All ZIP, and place them on your internal storage or external SD card.

    4) Boot into CWM, install the Format all ZIP, Install the ROM, and Install the Modem all in the same CWM session.

    The end result here will be Calkulin's custom FC09 ROM with the stock FC09 kernel and stock recovery (no CWM). These instructions apply for all ICS related ROMs (except for CM9 ... see below for info), so you can follow these steps in most scenarios.

    Working with CM9 and other AOSP based ROMs

    I highly suggest you avoid the ICS AOSP ROMs for now unless you really know what you're doing. This includes CM9, AKOP, Codename Android, or any other AOSP based ICS ROM. If you don't know the difference between EK02 and FB27 or what they mean, don't flash AOSP. If you don't fully understand what a kernel is, or how recovery is linked to it, don't flash AOSP. If you don't know when you need to format /system and /data and when you do not need to, don't flash AOSP.

    I say the above because from my observations, the majority of the hard bricks that have taken place have in some way involved CM9. You can certainly hard brick on a Samsung ICS leak, but the occurrences have been significantly less (again from my observations). I'm not trying to demonize CM9, just trying to emphasize the need to exercise caution.

    If you do decide to flash CM9, follow the instructions VERY carefully. If you flash AOSP, decide you don't like it and want to go back to a GB ROM or one of the ICS leaks, FOR THE LOVE OF ALL THAT IS HOLY AND GOOD DO NOT USE YOUR RECOVERY TO DO ANYTHING!!!!! In the case of all the AOSP ROMs, the devs suggest you use the stock EL26 CWM repack (not Rogue repack). So I recommend using the EL26 Odin One-Click to flash the full ROM, then Odin the stock EL26+CWM kernel (). Flashing the EL26 ROM may be unnecessary but I'm suggesting it as an extra precaution. Get everything ICS AOSP related off that phone before you use recovery to do anything is my stance.

    PHEW!

    The current opinion is that there is something about the ICS kernel Samsung wrote for our particular phone that is causing the problem when formatting data using a custom recovery (CWM in this case). Unfortunately, unless Samsung magically fixes it, we're going to have to wait until the ICS update officially rolls out and Samsung publishes the kernel source code before we will even have a chance to know what may be causing this, or how to possibly fix it.

    Until you get the all clear, be careful, follow the above guidelines, and you'll be just fine and able to enjoy ICS until it's released officially.
    Last edited by JayWill72; 07-27-2012 at 07:11 PM.
    Thanked by 11:
    + Show/Hide list of the thanked
  2. #2  
    dtm_stretch's Avatar
    Awesome Possum

    Posts
    726 Posts
    ROM
    AOSP JB/CM9

    Default Re: IMPORTANT! READ THIS Before Working With ICS Leaks or CM9!!

    Did you read the whole first post before you scrolled here? No? Then read all of it! No shortcuts or you will brick your phone!

    Well, it should be pretty obvious now with this thread. I think the CM9 team said they were going to stop packaging the rom with a kernel so that individuals will have to odin a kernel to flash or do anything. Honestly, I am kind of surprised that the issue doesn't get more attention, at least from Team Cyangenmod or Koush.
    Thanked by 2:
    epidenimus, JayWill and garwynn like this.
  3. #3  

    Angry Re: IMPORTANT! READ THIS Before Working With ICS Leaks or CM9!!

    Amen- bricked my SECOND Epic today in exactly the same scenario- going back from CM9 and not paying attention. Off to JTAG with fingers crossed. Wish I had seen your warning first and I wouldn't have written off the first fail as bad luck
    Thanks for posting this !
  4. #4  

    Default Re: IMPORTANT! READ THIS Before Working With ICS Leaks or CM9!!

    FYI, I made this a sticky the day it was posted and it will stay here for all to "hopefully" see so they don't end up in a brick.
    Paul
    Moderator Team Leader @ Android Central





    Thanked by 2:
  5. Thread Author  Thread Author    #5  

    Default Re: IMPORTANT! READ THIS Before Working With ICS Leaks or CM9!!

    Quote Originally Posted by crw11 View Post
    Amen- bricked my SECOND Epic today in exactly the same scenario- going back from CM9 and not paying attention. Off to JTAG with fingers crossed. Wish I had seen your warning first and I wouldn't have written off the first fail as bad luck
    Thanks for posting this !
    Ugh sorry man. Yeah you have to be extremely careful with the unofficial CM9 builds right now. One wrong move and it's brick city. Good luck with your JTAG. I hope they can revive it for you.
    Current Device: LG G2 (D800 - AT&T)
  6. #6  
    garwynn's Avatar

    Posts
    341 Posts
    ROM
    Stock! (For now...)

    Default Re: IMPORTANT! READ THIS Before Working With ICS Leaks or CM9!!

    Unfortunately JTAG will not restore from this brick - MobileTechVideos has said in previous discussion that he will not have people ship it to him after verifying hardware I/O errors with this brick.

    Another indication of how serious this issue is:
    1) Galaxy Note is having the same problem (thanks to MobileTechVideos for sharing that news).
    2) Newer ICS leaks, such as Calkulin's FC14, are no longer being packed with CWM. <--- *Edit* See post immediately below.

    If you want to try ICS by ODIN, and are available. Make sure that you thank the people providing these leaks.
    Last edited by garwynn; 03-16-2012 at 12:15 PM. Reason: Correction based on new information below
  7. Thread Author  Thread Author    #7  

    Default Re: IMPORTANT! READ THIS Before Working With ICS Leaks or CM9!!

    Well, none of the ICS leaks have CWM included because the leaks are usually posted well in advance of Steady Hawkin getting the kernel repacked, not necessarily because of the brick issues. In fact, here's a post from Calkulin this morning regarding FC14 and his own custom ROM ...

    Quote Originally Posted by Calkulin
    Actually I had it done since about 12pm yesterday, just waiting on repacked kernel to do testing
    Calkulin is obviously working with CWM on his ROMs, and he has yet to brick his device that we know of. Something to think about.

    Not everyone is convinced that there is an issue with the Rogue CWM repacks, myself included, except in the case of unofficial CM9. There does seem to be a lot people still flashing Calk's Format All ZIP while on a Samsung ICS ROM and kernel, and are not bricking their phones. I did it twice myself, successfully, before I started to take extra precautions. I believe there is something about how Samsung's ICS kernel, the CM9 ROM, and CWM react to each other that is causing the majority of the bricks, but until we have the source, this is all speculation.

    But in my view, when you don't know the true cause of the issue, there's nothing wrong with throwing a huge net over everything. Using Odin to get back to a GB ROM and kernel only takes an extra 15 minutes at the most, and it's worth not taking any chances at this point, thus my recommendations in the OP.
    Current Device: LG G2 (D800 - AT&T)
  8. #8  

    Default Re: IMPORTANT! READ THIS Before Working With ICS Leaks or CM9!!

    thank u guys still on stock but glad i saw dis .. now off to get some ice cream
  9. #9  

    Default Re: IMPORTANT! READ THIS Before Working With ICS Leaks or CM9!!

    Thanks for putting this post together.
    [How-To] Rooting LS670ZVH
    Installed ZVH by mistake? Use simple update.zip to revert to ZVD / Froyo
  10. #10  
    garwynn's Avatar

    Posts
    341 Posts
    ROM
    Stock! (For now...)

    Default Re: IMPORTANT! READ THIS Before Working With ICS Leaks or CM9!!

    This is a similar thread on XDA for those who check those forums out:



    Most of what is linked has already been covered well in the OP, but it never hurts to share what's available...
  11. #11  

    Default Re: IMPORTANT! READ THIS Before Working With ICS Leaks or CM9!!

    Happy to report that I just got my hard-bricked E4G back from JTAG @ MobileTechVideos. Working great!
    Very relieved. I'll check out the XDA thread too.
    Thanks!
  12. #12  
    dtm_stretch's Avatar
    Awesome Possum

    Posts
    726 Posts
    ROM
    AOSP JB/CM9

    Default Re: IMPORTANT! READ THIS Before Working With ICS Leaks or CM9!!

    Quote Originally Posted by crw11 View Post
    Happy to report that I just got my hard-bricked E4G back from JTAG @ MobileTechVideos. Working great!
    Very relieved. I'll check out the XDA thread too.
    Thanks!
    This is great to hear, do you mind telling us a little bit more about how you bricked and the methods you used for JTAG. This will help user determine if JTAG is even an option and hopefully you can link them to the best way to use this service.
  13. #13  
    rexalbel's Avatar

    Posts
    13 Posts
    Global Posts
    995 Global Posts

    Default Re: IMPORTANT! READ THIS Before Working With ICS Leaks or CM9!!

    I've been using the blend ICS roms I'm on 2.5 based off the FC18 leak. I like it. Seems smoother then stock GB el26. There are still some small bugs. I haven't tested GPS on this build, but notifications sometimes stop and I need to reset, and little visual bugs here and there. It's good enough for a daily driver for now. I really would prefer CM9, but I'm not about to go near that mess right now. imo samsung did a horrible job of updating their theme to complement ICS. so eventually I will want a stock ICS build, but for now the blend roms are the closest one can get as far as stability goes. I'm sure CM9 will eventually become stable correct? I have only used CM on my HP touchpad and had no issues with flashing the roms with that. Have CM9 alpha 2 on it right now and love it. Haven't used webos since. Would like the camera to work someday though.

    Anywho anyone waning ICS i suggest use the blend roms.
  14. #14  
    thenameisnigel's Avatar

    Posts
    1,417 Posts
    Global Posts
    1,427 Global Posts
    ROM
    Stock

    Default Re: IMPORTANT! READ THIS Before Working With TW ICS Leaks or AOSP

    Quote Originally Posted by JayWill72 View Post
    Okay guys. The purpose of this is to get a sufficient warning posted, and potentially save you the headache of hard bricking your E4GT, if you decide to flash one of the ICS leaks or unofficial CM9. Many people have bricked their phones over the last 6ish weeks, and my goal is to help readers who come here not suffer the same fate. Here's what's going on ....

    So on the E4GT, recovery is packaged together with the kernel (like all Samsung phones and many others). So in order to install custom recovery like the popular Clockwork Mod (CWM), you need to flash a new kernel that's been repackaged with it. However, it's been determined that something about the stock ICS kernel for our phone and CWM MAY corrupt and/or damage the data partition of flash memory. When a ICS+CWM kernel is running on your phone, and you boot into recovery and perform a format (also known as a wipe), there is a chance that flash memory will become damaged and your phone will be hard bricked. There have been some brick situations where even a JTAG could not write to the data partition and recover the phone. THIS IS BAD JUJU! When JTAG can't revive a phone, you know this is particularly nasty and something you'd want to avoid.

    So, it is highly recommended that once you have ICS or CM9 on your phone, before you change to ANYTHING else that involves a format or wipe of any partitions, that you Odin back to a Gingerbread ROM and Kernel+CWM, and then flash from there. While this takes more time, it's the safest way to work with these builds right now, until this gets figured out. Also, DO NOT RESTORE A NANDROID BACKUP OF YOUR GB ROM WHILE ON A ICS+CWM KERNEL ... ODIN BACK TO ONE MANUALLY, THEN RESTORE YOUR BACKUP FROM THERE! I bold this because on a Nandroid restore, just about every partition is formatted so you risk bricking your phone.

    If you have an ICS leaked build or Unofficial CM9 on your phone, please heed the following warnings ...

    [WARN]* DO NOT use ROM Manager at all, and more importantly, do not use ROM Manager to load Temp CWM to flash anything!
    * DO NOT use ANY version of Clockwork Mod TOUCH Recovery to format internal storage or flash anything!
    * DO NOT perform a /system or /data wipe using CWM while on an ICS kernel! Use Odin to flash back to a Gingerbread ROM and Kernel+CWM then move to something else ICS related from there.
    * DO NOT try to restore a Nandroid backup in CWM while on a ICS kernel! [/WARN]

    Working with the Samsung ICS Leak Builds

    So say for example, you have the stock FB27 ICS leak on your phone, and you want to try Calkulin's custom FC07 ROM. Follow these steps ...

    1) Download the and follow the instructions to flash the stock EL29 ROM and kernel.

    2) Download sfhub's and follow the instructions to install the EL29+CWM kernel repack.

    * NOTE: sfhub created a special one-click package that already includes the EL29 kernel+CWM for use in flashing back to GB from a ICS build. However, flashing this in Odin increases the flash count and causes the yellow triangle on the boot screen. If you know how to deal with these, feel free to use it. If not, I suggest doing #1 and #2 as it avoids this issue.

    3) Download Calkulin's FC09 ROM, the FC09 modem, and Calkulin's Format All ZIP, and place them on your internal storage or external SD card.

    4) Boot into CWM, install the Format all ZIP, Install the ROM, and Install the Modem all in the same CWM session.

    The end result here will be Calkulin's custom FC09 ROM with the stock FC09 kernel and stock recovery (no CWM). These instructions apply for all ICS related ROMs (except for CM9 ... see below for info), so you can follow these steps in most scenarios.

    Working with CM9 and other AOSP based ROMs

    I highly suggest you avoid the ICS AOSP ROMs for now unless you really know what you're doing. This includes CM9, AKOP, Codename Android, or any other AOSP based ICS ROM. If you don't know the difference between EK02 and FB27 or what they mean, don't flash AOSP. If you don't fully understand what a kernel is, or how recovery is linked to it, don't flash AOSP. If you don't know when you need to format /system and /data and when you do not need to, don't flash AOSP.

    I say the above because from my observations, the majority of the hard bricks that have taken place have in some way involved CM9. You can certainly hard brick on a Samsung ICS leak, but the occurrences have been significantly less (again from my observations). I'm not trying to demonize CM9, just trying to emphasize the need to exercise caution.

    If you do decide to flash CM9, follow the instructions VERY carefully. If you flash AOSP, decide you don't like it and want to go back to a GB ROM or one of the ICS leaks, FOR THE LOVE OF ALL THAT IS HOLY AND GOOD DO NOT USE YOUR RECOVERY TO DO ANYTHING!!!!! In the case of all the AOSP ROMs, the devs suggest you use the stock EL26 CWM repack (not Rogue repack). So I recommend using the EL26 Odin One-Click to flash the full ROM, then Odin the stock EL26+CWM kernel (). Flashing the EL26 ROM may be unnecessary but I'm suggesting it as an extra precaution. Get everything ICS AOSP related off that phone before you use recovery to do anything is my stance.

    PHEW!

    The current opinion is that there is something about the ICS kernel Samsung wrote for our particular phone that is causing the problem when formatting data using a custom recovery (CWM in this case). Unfortunately, unless Samsung magically fixes it, we're going to have to wait until the ICS update officially rolls out and Samsung publishes the kernel source code before we will even have a chance to know what may be causing this, or how to possibly fix it.PASS!

    Until you get the all clear, be careful, follow the above guidelines, and you'll be just fine and able to enjoy ICS until it's released officially.
    Just joined this forum after upgrading from the LG Optimus S. I thought I was great at Hacks for Androids but this Galaxy is something different. I can't risk a paperweight...
  15. #15  
    garwynn's Avatar

    Posts
    341 Posts
    ROM
    Stock! (For now...)

    Default Re: IMPORTANT! READ THIS Before Working With TW ICS Leaks or AOSP

    @JayWill,

    When you have time you may want to update the first post to reflect what we've found out since last updated. There's been quite a lot of progress on this...
  16. Thread Author  Thread Author    #16  

    Default

    Quote Originally Posted by garwynn View Post
    @JayWill,

    When you have time you may want to update the first post to reflect what we've found out since last updated. There's been quite a lot of progress on this...
    Yeah I'll get it updated with the current state of affairs later today. Thanks for reminding me.

    Sent from my SPH-D710 using Tapatalk 2
  17. Thread Author  Thread Author    #17  

    Default Re: IMPORTANT! READ THIS Before Working With TW ICS Leaks or AOSP

    OP has been updated. Hopefully I got the jist of it in there. Thanks again for all of your efforts on this issue garwynn. Without your Q&A with Mr. Sumrall we'd probably still be theorizing on the cause of the issue.
    Current Device: LG G2 (D800 - AT&T)
  18. #18  
    garwynn's Avatar

    Posts
    341 Posts
    ROM
    Stock! (For now...)

    Default Re: IMPORTANT! READ THIS Before Working With TW ICS Leaks or AOSP

    Just an update: This applies to the official ICS release as well unfortunately. The link to the official XDA discussion has "safe" kernel alternatives that will give the Touchwiz experience without the lockup risk.
  19. Thread Author  Thread Author    #19  

    Default Re: IMPORTANT! READ THIS Before Working With TW ICS Leaks or AOSP

    Quote Originally Posted by garwynn View Post
    Just an update: This applies to the official ICS release as well unfortunately. The link to the official XDA discussion has "safe" kernel alternatives that will give the Touchwiz experience without the lockup risk.
    Which is unbelievable really. Hopefully they at least did something that doesn't trigger the offending function when performing a factory reset/system restore. The development community can avoid the bug by only creating "safe" kernels. Non-rooted owners don't have this option. If a factory reset causes a EMMC lockup there's going to be a huge outcry.
    Current Device: LG G2 (D800 - AT&T)
  20. Thread Author  Thread Author    #20  

    Default Re: IMPORTANT! READ THIS - Regarding the EMMC Brick Bug on the E4

    OP updated.
    Current Device: LG G2 (D800 - AT&T)
  21. #21  

    Default Re: IMPORTANT! READ THIS - Regarding the EMMC Brick Bug on the E4

    Hello fellas,

    I manually upgraded my E4GT to ICS which was a huge mistake on my part due to my phone freezing for the first time and the OS sucking up all my battery life but thanks to you guys I followed all the instructions carefully and Odin my E4GT back to Gingerbread.
    By the way, !Gingerbread is king!
  22. #22  
    Tonay's Avatar

    Posts
    284 Posts
    ROM
    CM7

    Default Re: IMPORTANT! READ THIS - Regarding the EMMC Brick Bug on the E4

    So are people still bricking there phones if they don't odin one click back to gingerbread from any ICS or CM ROM?
    CLICK THAT "THANKS" BUTTON
  23. Thread Author  Thread Author    #23  

    Default Re: IMPORTANT! READ THIS - Regarding the EMMC Brick Bug on the E4

    Quote Originally Posted by Tonay View Post
    So are people still bricking there phones if they don't odin one click back to gingerbread from any ICS or CM ROM?
    It can happen, but many ICS kernel/recoveries have now been patched to be "safe" from the EMMC brick bug.

    Also, to clarify, you don't necessarily have to Odin back to a full GB system. Most people who want to play it extra safe, and always flash from a GB based kernel/recovery, use Mobile Odin to "temp flash" the EL26 kernel/recovery, boot directly from that recovery on the reboot, and flash from there (having the files ready on the phone already prior to flashing the EL26 kernel).

    It's important to understand that it's the kernel on your phone at the time of any emmc formats that matters.
    Current Device: LG G2 (D800 - AT&T)
  24. #24  

    Default Re: IMPORTANT! READ THIS - Regarding the EMMC Brick Bug on the E4

    Gingerbread=windows xp. Ice Cream Sandwich =windows vista.
  25. #25  
    thenameisnigel's Avatar

    Posts
    1,417 Posts
    Global Posts
    1,427 Global Posts
    ROM
    Stock

    Default

    Quote Originally Posted by moonoverparma00 View Post
    Gingerbread=windows xp. Ice Cream Sandwich =windows vista.
    Ice cream sandwich = windows 8

    Sent from my Epic 4G Touch running the world's best operating system.


    Official OpenROM Developer
    Want to contribute to OpenROM? Click HERE.
    Want to view my personal GitHub? Click HERE.
Page 1 of 2 12 LastLast

Posting Permissions

B