Related
Ok, more than fairly new to android. Ive ran on windows, windows mobile and blackberry for a very long time. Finally decided Android seemed like the hot ticket (cus f*** apple) and im trying to get into this stuff.
Im a geek whose been de-geeked (haven't spent much time on the computer in the last 8-12 months, comps currently unplugged and still packed after a move, currently at a library to post this.... you get my point), and so im limping into the android world. I bought and love my epic, but I didnt buy it to run it stock so im looking to upgrade. Things I really want in a rom/want my epic to do (i understand if not ALL are possible):
-Full Flash (10.1?)
-Preferred Froyo base
-I dont mind the look/feel of the stock Shell, but Ive never experienced any others so I guess Im open to suggestions and testing them out.
-For some reason, my images don't load in full quality, Ive been told some ROMs fix this. id like it fixed.
... My list is surprisingly shorter than I initially thought it would be when I started this post... so I may edit it soon as I remember other important things.
P.S. Ive done some searching around, don't flame me. It seems hard (extremely hard) to look at each one ROM individually, see its features and what is has to offer, compare and contrast and then pick one. Ive seen a few lists with random ones compared, but no list of all of them (I imagine that would be very hard to keep up to date). It seems more like, when someone makes a ROM they say what it is, what it does, what is has and if you miss the bandwagon then you miss it completely.
Thank you for all recommendations
I like bonsai rom on froyo. Its fast and very stable. It also has swap enabled. If you wanted to go to this froyo rom for flash support then you have to upgrade cause your on eclair now. The easiest way to get to this rom is to go into the dev. Section and find the one click root plus clockwork version 3. Not 2.5.5 but version 3. But before you do that you need use a program called Odin to flash your modem from di18 eclair to dk28 froyo. Then once you boot into cwm it will change your filesystem over from rfs to ext4 and then you flash the bonsai rom and your done. Sorry I don't have links for you I'm using tapatalk and its a pain in the ass to post links but go to the dev section and look its all in there. Good luck
Sent from my Evo Killer!!!
I've tried a few different roms but so far I like ViperRom's frozen 4.0.3 the best. It has flash and is very very stable. Its based on dk28 and the step by step instructions are a breeze on their thread. It uses cwm 2.5 and everything is available on their thread.
Sent from my [frozen] epic.
Thank you guys for the responces, ill check them both out when I get to a real computer. Odin sounds like fun ;D sorry it took me so long just to check up on my own thread, life is... life.
Sent from my SPH-D700 using XDA App
musclehead84 said:
I like bonsai rom on froyo. Its fast and very stable. It also has swap enabled. If you wanted to go to this froyo rom for flash support then you have to upgrade cause your on eclair now. The easiest way to get to this rom is to go into the dev. Section and find the one click root plus clockwork version 3. Not 2.5.5 but version 3. But before you do that you need use a program called Odin to flash your modem from di18 eclair to dk28 froyo. Then once you boot into cwm it will change your filesystem over from rfs to ext4 and then you flash the bonsai rom and your done. Sorry I don't have links for you I'm using tapatalk and its a pain in the ass to post links but go to the dev section and look its all in there. Good luck
Sent from my Evo Killer!!!
Click to expand...
Click to collapse
One thing I've had aa question on for a while...do you HAVE to do the odin method? It ddoesn't really affect me anymore, but I installed 2.2 through an update.zip
I was wondering if there are any differences.
Sent from my Epic 4G
acer1096xxx said:
One thing I've had aa question on for a while...do you HAVE to do the odin method? It ddoesn't really affect me anymore, but I installed 2.2 through an update.zip
I was wondering if there are any differences.
Sent from my Epic 4G
Click to expand...
Click to collapse
No there isnt, i updated via updatezip both 2.2 and the modem, i first flashed the modem, then tried to flash 2.2 but i had to flash the d118 stock rom unrooted then it updated and then i was able to ext my system then get on bonsai.
Since ive had my epic, ive avoided odin all together..
which themes and roms can I use if I rooted using odin?
and if i have drockstar.clean.kernal.eco5v 1.02 installed
too root i used eco5x_dxc.tar
hope that helps hard to get this far and lost without trying something and getting locked no load or looping and having to reflash
how do i flash it, instructions do i have to change it to anything or download and flash?
is there something on the market to help flash, use odin or recovery, change name to flash?
All of them. I reccomemt SRF 1.1.1 + twilight kernal 1.11 (in same thread) if you like froyo or marcusant rom if you want gingerbread. Make sure you are using cwm 3.0.2.5
Did the news get around about a guy named butcher pete?
I dont think it matters if you rooted via odin as to the themes as much as it does the kernel supporting the them and the modem supporting it and the version of rom you are running. I have noticed there are quite a few that will go together but you have to make sure of them all
okay then what and how do i know what i can put toghether
this is alot different then running the moment
that was alot easier
is there something that would let me know which rom i can run compared to theme, etc?
and how do i go about doing that?
this is alot different then the moment so like they say.....still wet behind the ears, but learning from you
Let me just say this first. If you have read anything the most from this site it is research it. There are alot of wiki and posts for almost everything. I rushed into it and was so in a bad way and someone helped me out so here I am. what have you done to your phone. Rooted??If so did you CW3 or Odin. Are you stock dk28...
this could go on and on. If anyone sees a problem with what you are saying or something doesnt seem right the Devs will jump in. But if it is handled in wiki or past posts...dont expect a fast response. Not that they are neglecting...but they are busy.
rooted using odin...eco5x_dxc.tar
and i have drockstar.clean.kernal.eco5v 1.02 installed
thats all i have done
got all from sdx site not rushing had phone for 2 months so another day
isnt going to hurt, want to be safe and learn
different from moment
so?
What clockwork mod version do u have?
Sent From My Evo Killer!
2.5.1.0 can I upgrade it and how?
In the development section there are numerous ways to upgrade to cwm 3 and root at the same time. And qbking77 has great tutorial vids on youtube to show you the steps.
rootxda said:
2.5.1.0 can I upgrade it and how?
Click to expand...
Click to collapse
I have put together a new Rom version of SyndicateRom Frozen 1.1.0 called RandomRom. It includes many of the updates and modifications made to 1.1.1.
More specifically, it includes the Genocide Kernel and solves freezes. It also comes Pre-Journaled.
You'll also find the link to the CWM 3.0.2.5 upgrade thread in the changelog. Everything you will need should be linked.
So i was getting rather bored with my Rom and i wanted to get a new one, so i was looking up new Roms and me being a amateur and these things i thought i would be pretty ok since i got the first time, and the second time down, 3rd times the charm? i decided to get BakedSnack 1.9, the information is on their site Bakedsnackshack for the Evo, the latest near the top of that download page. This where the info is and i simply followed the instructions but i really wasnt sure about the beginning information about the Wimax and radio updated, since the second link for the radio was broken (if anyone has that i would love it or some advice really) i skipped those two requirements and decided to try, so i backed up my rom (Which totally didnt work) and went ahead and cleared and tried to install, which it did not work just said (bad) and didnt want to go any further, so considering the file was fine, the only thing i did wrong was not have the requirements, i am rooted and have a custom recovery, and now im pretty upset i lost my favorite recover even though i spent 5 minutes recovering that didnt actually work till i decided to recover, was wondering if anyone can help me get this going to actually work since i have nothing really much to lose, and if someone can get me going on this Baked Snack Rom, id really appreciate it and may thousands of dollars rain on the head of that special person to give advice, i eagerly await a answer
Be careful flashing radios. you can very easily lose your wimax keys and therefore never again be able to use 4g. With that being said.. What recovery are you using? Clockworkmod or Amon Ra? If you used Clockworkmod you'll need to go to Backup/restore... Choose the folder you see next then highlight the last one and select restore.If you can see your sdcard.. it should be in a folder called Clockworkmod\Backup\Yourbackup... Your trying to get to the last folder "yourbackup". Once that's selected choose restore.
It'll help us alot more knowing if you can see that folder and also what recovery your actually running. So you might have to reinstall all your programs.. no biggie.. it's a learning experience and it will only make you wiser next time. Bakedsnack is an older rom though if I remember correctly. Might wanna find something more current.. Synergy, Kingsrom Alliance,MikG are examples of 3.0 sense based roms that are on the cutting edge. Kingsrom, Koni's Elite Series III, Myn's,Mikfroyo are all great Froyo based roms. I have no experience with Bakedsnack but I'm sure it is good as well.
I think the first warning light would have been when your backup failed.
To me, that means, do not proceed until I can do a good back-up.
If you're not using Amon, Ra, I suggest you switch to it.
CWM just has some flaws, and AR is just better.
Since a lot of people have asked me about TWRP 2 for Epic Touch and SGS2 devices, here's the deal:
1) I don't own an Epic Touch or a SGS2 device of any kind.
2) As some may be aware, many Samsung devices do not have and/or properly use a recovery partition. Instead the recovery is packed as a second ramdisk or as a separate recovery.rc in the same ramdisk in the boot image. This means that every time you install a new ROM or kernel, you will get stuck with whatever recovery is included with the boot image.
3) We do have a process that lets you inject TWRP into boot images that are still using the dual ramdisk setup typically found in CM7 boot images. I believe that somewhere along the development path of CM9, the boot image packing method changed to a single ramdisk with 2 init files (recovery.rc). This type of setup is much more difficult (if not impossible) to do "injection" and since I don't have a device in hand to work with I have no plans to attempt to create an injection method for this new type of boot image. The injection process still appears to work on CM7 boot images and some kernel devs for SGS2-type devices have not moved to the new method (yet).
4) We now have code that compiles in CM9. This new code base is much simpler to get started with - you just replace the bootable/recovery folder with the TWRP source code and grab a copy of our slightly modified 1.20 busybox code and you're ready to compile TWRP after adding a few build flags to your BoardConfig.
5) The TWRP source code is all public, including the GUI. It's pretty easy to compile and work with and we have a nice guide to help you out here: http://tinyw.in/nP7d
If you need help integrating TWRP into your builds or have questions about compiling TWRP, feel free to find us in #twrp on Freenode. TWRP works very well with thew GooManager app and if you host your ROM on http://goo.im, your users can receive notifications of ROM updates and easily download and flash the update almost like a regular OTA update. In addition, http://goo.im now supports automatic differential zip creation. You upload an update to your ROM and goo will create a zip with just the changes. Your users get smaller downloads, faster installs, and less wear and tear on the device since only the updated / deleted files get replaced, but this functionality is only easy to use with a supported recovery like TWRP. Please consider adding TWRP to your builds and using http://goo.im and GooManager! All of this functionality is free to you and your users!
If you're feeling really adventurous, you're welcome to install this for the Epic Touch after installing a copy of CM7. I was told by a tester that it was working fine but use at your own risk and be prepared to Odin / heimdall a working boot image if something goes wrong! Note that backups and restores done in TWRP / CWM are not easily interchangable!
http://goo.im/devs/OpenRecovery/epictouch/openrecovery-twrp-2.1.2-epic4gtouch-signed.zip
I can probably create the same kind of a zip for SGS2 International if someone is willing to stop by #twrp on Freenode to test it. I do know that someone has successfully tested a ramdisk on the SGS2 with Exynos so TWRP should work on this device with relative ease.
Also note that it appears for the time being that most Samsung devices released in the USA where all team win members live, are going to be using Qualcomm chipsets instead of Exynos. This means that the only Samsung device that's readily available in the USA that uses the new boot image methods is the Epic Touch. We have a release for the AT&T Galaxy Note and Skyrocket but both of these devices use the Qualcomm chipset which uses a "normal" and separate recovery partition.
No idea what this is about but I got the second post! Woot
Thanks for letting us know about this but we don't have a working cm7 anyway.... do we? I haven't seen one. Also, if I'm reading this correctly, it seems to me any dev who wanted to could repack twrp in any Rom at release. But why would they? Not to take away from the work done by all the twrp team but when I had it on my evo shift it was buggy and rarely formatted everything properly. Has this been fixed or was it a device specific issue?
Sent from my SPH-D710 using xda premium
abadasstanker69 said:
Thanks for letting us know about this but we don't have a working cm7 anyway.... do we? I haven't seen one. Also, if I'm reading this correctly, it seems to me any dev who wanted to could repack twrp in any Rom at release. But why would they? Not to take away from the work done by all the twrp team but when I had it on my evo shift it was buggy and rarely formatted everything properly. Has this been fixed or was it a device specific issue?
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
There is a working CM7 for the E4GT. It's posted over at Rootzwiki. TWRP worked fantastically on my Evo and Evo 3D. Glad to see we have another option besides CWM. Hopefully we can get past the bricking issue with ICS roms and I can throw this on my phone permanently.
Thanks Dees_Troy!
Agree worked awesome on my e3d looks to be great
Thanks for this
Sent from my SPH-D710 using xda premium
Team win ftw!!
Sent from my SPH-D710 using xda premium
I love using TWRP and goo.manager on my cm9 touchpad. So easy to use. Glad our amazing devs have more options.
Just wanted to say I used TWRP on my 3D and Nexus S and was my favorite recovery hands down. Would love to see it come to the Epic Touch.
Sent from my SPH-D710 using Xparent ICS Blue Tapatalk 2
I'm going to second everyone that likes twrp. I also enjoyed the recovery very much and it was the one thing I missed when moving to e4gt. I can't wait for source on ICS. If someone doesn't build it into a kernel, I'll be doing some kernel research and building it for myself.
Sent from my SPH-D710 using Tapatalk 2
This is great news I'm tired of not having a working recovery on ics
abadasstanker69 said:
Thanks for letting us know about this but we don't have a working cm7 anyway.... do we? I haven't seen one. Also, if I'm reading this correctly, it seems to me any dev who wanted to could repack twrp in any Rom at release. But why would they? Not to take away from the work done by all the twrp team but when I had it on my evo shift it was buggy and rarely formatted everything properly. Has this been fixed or was it a device specific issue?
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
first off the evo shift is an older lower end phone, so performance on any recovery besides cwm which is so basic is probably iffy. TWRP has been pretty amazing on the evo3d and also on my Gnex, and if it gets ported in any working for on the e4gt id be happy to use it for my wife's phone.
if i understood this correctly, twrp recognized the issue with a constant recovery on the e4gt, and they are basically giving us the source to build it into our roms instead of the the stock recovery, so its atleast there on install. it would be nice to see the developers working on cm9 on this phone integrate it into the rom.
This does sound like a step in a good direction but I have to ask....
How do we not have working recovery? It takes literally 45 seconds extra to flash EL26 and then reflash current after the backup is made...sure it isn't "ICS recovery" but it's the result I'm interested in..
are we this lazy that a less-than-one-minute procedure is worth whining about?
Not taking a shot at anybody.. just sayin. I see people complain about this more than anything and they could have made 10,000 backups with the time that they were posting complaints about it.
Especially now that stock kernels can flash...let's let it go.
Kebetz said:
This does sound like a step in a good direction but I have to ask....
How do we not have working recovery? It takes literally 45 seconds extra to flash EL26 and then reflash current after the backup is made...sure it isn't "ICS recovery" but it's the result I'm interested in..
are we this lazy that a less-than-one-minute procedure is worth whining about?
Not taking a shot at anybody.. just sayin. I see people complain about this more than anything and they could have made 10,000 backups with the time that they were posting complaints about it.
Especially now that stock kernels can flash...let's let it go.
Click to expand...
Click to collapse
i want a working one already because i dont have the means to get mobile odin, and im rarely home, i came from the og epic and most of my flashing was done on the go. Now im lucky to update my rom once a week. A working recovery that wont brick my phone is a huge plus for people on the go
Kebetz said:
This does sound like a step in a good direction but I have to ask....
How do we not have working recovery? It takes literally 45 seconds extra to flash EL26 and then reflash current after the backup is made...sure it isn't "ICS recovery" but it's the result I'm interested in..
are we this lazy that a less-than-one-minute procedure is worth whining about?
Not taking a shot at anybody.. just sayin. I see people complain about this more than anything and they could have made 10,000 backups with the time that they were posting complaints about it.
Especially now that stock kernels can flash...let's let it go.
Click to expand...
Click to collapse
I don't mind flashing the EL26 Stock CWM kernel at all. With Mobile Odin it literally takes a minute tops. But I like having the best on my phone and IMO the best recovery out right now is TWRP. It's always worked REALLY well for me. Not one single issue ever. Add in the other features, like compressing backups to save space which may not be a big deal with this device but anyone who's used Sense 3.0 could testify how awesome that feature is. Along with being able to theme every aspect of the recovery and as a themer I just love that option. That's just to name a few. So again, in my case it's not about being lazy but more about wanting the best available for my phone. So if TWRP is a possibility I would love to see it.
I have to agree with tiffany. It is more about the recovery itself. I use mobile odin and take no issue with the current methods but I also would like to have TWRP running on my phone. Hopefully source is released soon and we can take advantage of this. Thank you for posting the links for it and hopefully one of our devs can help to make this happen.
Ok, I admit, odining back to el26 isn't something to complain about for normal flashing. But when trying to alter system files to get the result you are looking for can become somewhat frustrating when a boot loop occurs. Normally a battery pull and a quick flash gets you back in the game. In my experience though, as I'm sure other cracks flashers can agree, sometimes you just have to flash something new, right before you step out the door. Lo and behold you realize you have just set yourself up for failure, failure to boot that is. As I stated in another thread, a lot of folks have busy lives and don't spend every moment reading xda, all they want to do is grab what's hot and flash it with the same procedure as every other Android device that they have come to know and love. In my opinion, working recovery = happy forums. And soon enough we will, and when we do, I want to be sporting TWRP.
Sent from my SPH-D710 using Tapatalk 2
Why all the fuss over something that you use for 5-10 minutes when you flash a ROM, theme, etc.? How much time are you spending in Recovery?
The next thing you know people will want the "Download" mode to be themed and "prettied up" too.
Does anyone remember what it took to customize phones 4-5 years ago? Oh wait, this is XDA, I forgot it's the land of "gimme gimme gimme" and hardly ever about "thank you" or "how can I help you with that?". Users just want to be "alpha" testers so that they can have the newest, hardly do they ever upload logcats, dmesg logs, or help in troubleshooting.
-Daryel
daryelv said:
Why all the fuss over something that you use for 5-10 minutes when you flash a ROM, theme, etc.? How much time are you spending in Recovery?
The next thing you know people will want the "Download" mode to be themed and "prettied up" too.
Does anyone remember what it took to customize phones 4-5 years ago? Oh wait, this is XDA, I forgot it's the land of "gimme gimme gimme" and hardly ever about "thank you" or "how can I help you with that?". Users just want to be "alpha" testers so that they can have the newest, hardly do they ever upload logcats, dmesg logs, or help in troubleshooting.
-Daryel
Click to expand...
Click to collapse
Sure this is true of some but I get thanked all the time for the work I do. There will always be the gimmie gimmie gimmie people, no matter what your doing.
And yeah if I could theme download mode I probably would. Just the way I am.
graffix31 said:
I love using TWRP and goo.manager on my cm9 touchpad. So easy to use. Glad our amazing devs have more options.
Click to expand...
Click to collapse
For those who haven't seen this in action, its worth a look. It is nice to open up goomanager and see all of the latest ROMs and versions that are hosted in goo. You can select the ROM you want and the script flashes it for you and IT WORKS! It is very slick. I would love for a dev to take this on!
Would love to see a themed download mode
Sent from my SPH-D710 using Tapatalk
Due to an error in the kernels we've been flashing to our devices, a lot of users have been experiencing a FULL BRICK. Full brick meaning you may as well play golf with your phone, it's dead.
I've been told there is a fix, BUT YOU MUST NOT FLASH ANYTHING FROM CWM. The bug is originating from flashing a corrupt kernel from CWM or mobile ODIN.
Here's a cut from the article:
Thanks to XDA Elite Recognized Developer Entropy512, we have learned that most devices that are receiving leaks are at a very high risk of never waking up after a flash. It turns out that there is a major bug in the leaked ICS kernel that affects the /data partition in the eMMC chip, which apparently gets corrupted during certain operations such as wiping and flashing. This was originally believed to be affecting only operations performed in custom recoveries such as CWM. However, there have been reports of hard bricks being produced from the flashing from stock recoveries as well. The affected devices are:
All Epic 4G Touch (SPH-D710) ICS leaks
All Galaxy Note (GT-N7000) ICS leaks
The AT&T Galaxy S II (SGH-I777) UCLD3 leak – and probably all others
Korean SHW-M250S/K/L official releases and any kernel built from their source
Entropy and other devs have posted several warnings scattered throughout the site, in which they explain in detail what is happening. Our suggestion is that users should stay away from flashing ICS from leaks until the bug in the kernel has been completely fixed—unless of course, you are looking to hard brick your device. Remember, this is not something that can be resurrected via Unbrickable Mod or even via JTAG, as this is a firmware error in the eMMC.
Click to expand...
Click to collapse
Just like you, I don't wish to brick my E4GT. xST4T1K has posted a comprehensive guide to find your options on removing the affected ICS kernels from your device, and hopefully resulting in you not bricking the crap out of your phone. Go check this page: http://forum.xda-developers.com/showthread.php?t=1525495
I DO NOT take credit for finding this bug, credit goes to Entropy512 and XDA TV's EGZTHUNDER1 for alerting me of this bug. I have safely removed the affected ICS kernel from my phone and custom builds, now it's your turn.
The only reason I'm requesting a sticky in the wrong forum (Yes, I know I posted in the development branch) is because most users won't know about these affected kernels before trying their newly rooted E4GT into some ICS bling.. Next thing you know, you've got a two day old brick with a shiny screen.
Please, once again, GO TO THIS PAGE and explore the options of returning your phone back to dry land.
As a reminder, DO NOT FLASH ANYTHING FROM CWM OR MOBILE ODIN.
While I have heard that flashing a non-ICS kernel from ODIN has fixed these issues, we're looking more into that now.. I have alerted xST4T1K of this, and we'll get back to you with confirmed results.
Safe flashing, XDA members.
Maybe this sticky from the general forum should just be moved over to here.
http://forum.xda-developers.com/showthread.php?p=23149990
Sent from my SPH-D710 using Tapatalk 2
Weve kinda known this for a while now since the February leaks... js. Still, safe flashing everyone lol.
first off, many have been warned by all the devs, myself and other users since these unlocked recoveries came out and then the repacked recoveries started up again...
USE CALKULIN'S FORMAT ALL OR CALKULINS MODIFIED FORMAT ALL, to do any wiping...
DO NOT WIPE FROM STOCK OR CWM RECOVERIES...
If you do what is said above, you won't brick your device.
Why do you wipe from the stock when all you have to do is flash 1 file to do it all for you?
NOW again....
USE CALKULIN'S FORMAT ALL OR CALKULINS MODIFIED FORMAT ALL, to do any wiping...
DO NOT WIPE FROM STOCK OR CWM RECOVERIES...
Quite Easy.
In the end, it's called following directions.
Edit: just to clarify... Wiping cache/dalvik cache from stock or cwm repacked recoveries is safe.
The issue is Wiping Data (Don't use the option)
bigpeng said:
first off, many have been warned by all the devs, myself and other users since these unlocked recoveries came out and then the repacked recoveries started up again...
USE CALKULIN'S FORMAT ALL OR CALKULINS MODIFIED FORMAT ALL, to do any wiping...
DO NOT WIPE FROM STOCK OR CWM RECOVERIES...
If you do what is said above, you won't brick your device.
Why do you wipe from the stock when all you have to do is flash 1 file to do it all for you?
NOW again....
USE CALKULIN'S FORMAT ALL OR CALKULINS MODIFIED FORMAT ALL, to do any wiping...
DO NOT WIPE FROM STOCK OR CWM RECOVERIES...
Quite Easy.
In the end, it's called following directions.
Click to expand...
Click to collapse
So my question is... What about flashing mod's that require only wiping cache and dalvik??? I guess I've been lucky with wiping cache and dalvik from cwm recoveries but does this mean no more mod's until source is released???
Sent from my SPH-D710 using Tapatalk 2
bigpeng said:
first off, many have been warned by all the devs, myself and other users since these unlocked recoveries came out and then the repacked recoveries started up again...
USE CALKULIN'S FORMAT ALL OR CALKULINS MODIFIED FORMAT ALL, to do any wiping...
DO NOT WIPE FROM STOCK OR CWM RECOVERIES...
If you do what is said above, you won't brick your device.
Why do you wipe from the stock when all you have to do is flash 1 file to do it all for you?
NOW again....
USE CALKULIN'S FORMAT ALL OR CALKULINS MODIFIED FORMAT ALL, to do any wiping...
DO NOT WIPE FROM STOCK OR CWM RECOVERIES...
Quite Easy.
In the end, it's called following directions.
Click to expand...
Click to collapse
In a world where users flash before they research, common sense doesn't have a stronghold.
DjKurt said:
So my question is... What about flashing mod's that require only wiping cache and dalvik??? I guess I've been lucky with wiping cache and dalvik from cwm recoveries but does this mean no more mod's until source is released???
Sent from my SPH-D710 using Tapatalk 2
Click to expand...
Click to collapse
The issue is from Wiping Data from stock and cwm recoveries, you can wipe cache and dalvik with no worries. Those don't mess with partitions.
Sent from my SPH-D710 using xda premium
You may be able to flash wipe mods and such but imsince I bricked mine doing just that. I will not flash anything in an ics recovery. I will Odin modems and will flash roms and kernels in one session and that is always coming from stock GB. Take for what its worth. Not saying the above mentioned ways aren't worth noting. But flashing the format script in blue cwm while on ICS is what bricked me.
scarmon25 said:
You may be able to flash wipe mods and such but imsince I bricked mine doing just that. I will not flash anything in an ics recovery. I will Odin modems and will flash roms and kernels in one session and that is always coming from stock GB. Take for what its worth. Not saying the above mentioned ways aren't worth noting. But flashing the format script in blue cwm while on ICS is what bricked me.
Click to expand...
Click to collapse
That sucks, sorry to hear that...
I was one of the first to test cwm repacked recoveries for agat63 since FE10 and have flashed 37 times to and from different roms and done backups and restores countless times and I've been fine.
I haven't been fearful of any bricks since I tested these repacked kernels.
Hope it does get figured out once source hits though.
Edit: btw what kernel (with or without cwm repack?) did you brick in?
Sent from my SPH-D710 using xda premium
It was back when CM9 first was released. I was using the el26 cwm kernel to flash. I was on one of the ice builds I can't remember. I odined the kernel cwm combo el26 and then ran a format all and flashed cm9 and ggot the blue light special haha
Its all good though. I have read alot of info in this including the one mentioned. One thing that was mentioned in one of them is that the bug had been triggered be deleteing a large file off the internal memory. That worried me. So I've been weary of ICS builds since. The fact that the issue seems to be that info getting wrote to a certain block of the emmc has me worried that it could be triggered by more then wiping of flashing. I have ran agats ROMs and I have to say he seems to be doing something right. Whether it is because he is staying TouchWiz or what for some reason his users seem tto not have many issues. But just keep in mind that it may not just be kernel/recovery related.
Safe flashing is key and I never want to see someone brick. Just be careful in whatever you do.
Sorry, I haven't had much of a chance to update my thread lately but I will soon. With all the leaks that were consistently being released, it wasn't feasible to update it every other day. The thread already has everything you need to know about bricking so I figured if you couldn't figure out how to prevent a brick with the information given, then you should probably buy an IPhone and never attempt flashing in the first place.
xST4T1K said:
Sorry, I haven't had much of a chance to update my thread lately but I will soon. With all the leaks that were consistently being released, it wasn't feasible to update it every other day. The thread already has everything you need to know about bricking so I figured if you couldn't figure out how to prevent a brick with the information given, then you should probably buy an IPhone and never attempt flashing in the first place.
Click to expand...
Click to collapse
I couldn't have said it any better, my friend!
As far as those who've bricked their phones, it is truly unfortunate.. Google themselves has been brought into light on this situation, and are working to correct this issue in the kernels that they've been adding in with their firmware.
As far as your useless phones go.. Try filing for an insurance claim, I guess! NOT my professionally recommended advice.. But IF someone were to have stolen that useless phone of yours and you were to never see it again.. Well, who am I to say that's not a reason to get a replacement from asurion! Lol!
By the way, xST4T1K.. Bumped you thanks count up a little more.
Thank goodness I ran into these threads before I decided to flash anything else.. Been running a solid ICS rom for a few weeks, now. But I'd rather get back to safe land on GingerBread Island and use Apex Launcher. Wouldn't care for the huge difference in the settings menu. Would miss the lockscreen, though.. Not aiming my finger at an unlock tab has gotten habitual!
crazy.. not sure i agree with this thread.. its scaring people away from trying awesome roms.. if you search in any ics rom or aosp ics rom you hear little about people bricking there phones.. there are clear instructions to install and if you dont know what your doing and cant follow instructions dont do it or you will have a brick. ive been on ics since the first leak and have had to odin many times after a "soft brick" from me not following instructions but its simple.. dont format data on any ics kernel/cwm and you'll be fine..
Sent from my SPH-D710 using XDA
elliwigy said:
crazy.. not sure i agree with this thread.. its scaring people away from trying awesome roms.. if you search in any ics rom or aosp ics rom you hear little about people bricking there phones.. there are clear instructions to install and if you dont know what your doing and cant follow instructions dont do it or you will have a brick. ive been on ics since the first leak and have had to odin many times after a "soft brick" from me not following instructions but its simple.. dont format data on any ics kernel/cwm and you'll be fine..
Sent from my SPH-D710 using XDA
Click to expand...
Click to collapse
I would never want to scare anyone away from trying these great builds on XDA. What I do want though is to make people aware that no matter how many tines you flash something. Always treat the flash your about to do as if it was your first. Sometimes we get to comfortable in what we're doing. We have to remember that this is a pretty expensive device and if something happens you may be buying a new one outright. Not everyone has insurance or can throw out that kind of cash. Do safe flashing practices and make sure you read the OP. When flashing leaked software make sure to flash from stock or the most current OEM released build such as EL29 in this case. Verify the right files are in the right slots of Odin. Make sure you're flashing files in the right sequence when in a custom recovery. Thing like that. I believe in the openness of android and never want to see anyone say they aren't going to flash something because they are scared. With the right ammount of reading and precautions. There is no reason to be scared.
Just for example. And this is not an exaggeration. Between this phone,my wife's phone, my last phone, my wife's last phone, and numerous friends phones. I have well over 200+ flashes. I have only had one actual brick. And that brick was because I got too comfortable in what I was doing. So, odds are if you take tthe time to do it right. You will succeed. Also.
i cant figure out why this is not locked yet....
i agree scarmon.. you said it better than i could.. if i wasnt tech savvy and i read the op i would have been scared away.. it says in all caps not to flash in cwm and says many have experienced bricks.. it can be worded differently but its freedom of speech.. when the initial leak came out and we had rogue ics kernels and the LOSt kernel we werent sure why people were having bricks until we figured out what was causing it.. we've known this for a while and since then hard bricks have dropped drastically.. and every single developer insisted not flashing from ics kernels and every rom has a disclaimer in the op for this reason.. only bricks ive read have been user error for a while ie. unplugging device during odin flash or battery dieing during mobile odin flash etc.. plus this is in the dev thread.. right now most people come here for ics roms since thats what devs are working on.. and many have gone safely back to gingerbread many times.. the ics roms have hundreds of thousands if not millions of hits and how many posts about hard bricks?
Sent from my SPH-D710 using XDA
I've been flashing ICS roms since FB17 and haven't had any bricks. I've been making sure to only flash things from EL26 and it's been smooth sailing.
Now I'm running the most recent AOKP and it's running very well.
Your credit is pretty thin too. Entropy is a big name in this issue but him and some random dude that apparently notified you very very late about this issue doesn't even cover half of it.
The front page news on the issue was pretty late as well. Just lets the general population know about it.
ijoshv2 said:
While I have heard that flashing a non-ICS kernel from ODIN has fixed these issues, we're looking more into that now.. I have alerted xST4T1K of this, and we'll get back to you with confirmed results.
Click to expand...
Click to collapse
Its things like this "While I have heard" that is the problem with your post. That and begging for a sticky, talk to a moderator if you feel its important.
Flashing a non-ics kernel through ODIN does not fix any issue. Flashing from a safe Kernel avoids the issue, If your on ICS flashing the GB Kernel from ODIN would be the safe method. Gingerbread as far as we have known and hundreds of flashes per person per hundreds of phones later. No one has been known to trigger the eMMC firmware bug though gingerbread. So yes flashing from a Gingerbread kernel as we have since the phone came out is the safest known way. You don't need anyone to tell you that.
You come in and say "Do not flash anything from CWM". This is inaccurate it suggests one can not flash from EG30+ CWM which has never been a known danger. Obviously EK02 would be more popular due to supporting full modems rather than patch. EL26 was the last to have true CWM which is why EL29 Rogue is less often suggested.
ijoshv2 said:
The only reason I'm requesting a sticky in the wrong forum (Yes, I know I posted in the development branch) is because most users won't know about these affected kernels before trying their newly rooted E4GT into some ICS bling.. Next thing you know, you've got a two day old brick with a shiny screen.
Click to expand...
Click to collapse
The danger is not in flashing ICS. The unknowing user is going to be flashing ICS from EL29 which is safe. The danger is after they are there, and they try a factory reset, or install a CWM or Unlocked Recovery Kernel and flash something, or flash an update.zip through stock recovery. Yes they need to know, the information should be accurate however.
If anyone wants details of this emmc firmware bug, there's some really knowledgeable people in this thread.
http://forum.xda-developers.com/showthread.php?t=1644364
The info is very detailed, but these are the individuals to watch. OP if your serious about helping our community with this emmc bug, I hope you join in that conversation instead of asking to sticky this thread.
Sent from my SPH-D710