So heres a question:
Wgy do we have rogue recovery with the kernels when we cant flash ROMs from it.
Well we arent supposed to.
Why not repack the kernel with pure CWM and eliminate everyone form having to take the extra step of flshing back to CWM before flashing a new ROM
tramane said:
So heres a question:
Wgy do we have rogue recovery with the kernels when we cant flash ROMs from it.
Well we arent supposed to.
Why not repack the kernel with pure CWM and eliminate everyone form having to take the extra step of flshing back to CWM before flashing a new ROM
Click to expand...
Click to collapse
It won't matter as its the ics kernel that is the problem not rouge not Acs not cwm.....
Sent from my SPH-D710 using xda premium
I've been flashing with it. So have plenty of others. Some people bricked and they may have been using rogue but I wrecked a Honda once.... Its usually user error.
Sent from my SPH-D710 using XDA
You have a point.Im coming from original Epic 4g and im deffinetly confused about the kernels on Epic Touch.
This is what I mean:On original Epic they had kernels that you could flash on top of just about any rom in cwm or odin.But for Epic Touch im yet to find any kernels for it.Yes there are some stock EL29EG31,etc.. in wiki pages but thats it?
There are only two kernels on wiki that are non stock and they are Hitman's kernel and Rogue kernel,is that all we got?Og Epic had about 30 different nonstock kernels.
So my question is this:
1 Are Rogue and Hitman kernels come with their own cwm?
2 Are Rogue and Hitman are only two nonstock kernels?
3 Are all the other lernels on wiki EL29,EL26,EG30,etc.. are just stock or modified stock?
4 Can any of those kernels(besides ics Rogue of course) be flashed to any GB rom?
5 Are there any difference between different versions of Rogue and Hitman?Or latest is the best?
6 And if Rogue and Hitman also come bundled with their own version of cwm,what is the difference between those two cwm's?
I been on original epic xda forums for years and this **** is confusing,they should make a thread for new people.
Pretty sure its not user error, given that at least 3 of our most prominent bleeding edge devs bricked doing it. I made the mistake of believing it was user error, but all evidence points to the contrary.
The reason we have recovery on ICS kernels is there are things at this point that you can safely flash (basically, anything that doesn't wipe data). You can safely flash the visual voicemail .zips from rogue ICS recovery on AOSP roms, for example. But you can't flash a whole rom. You can make a nandroid for later restore from EL26 cwm. You can do a lot of things actually. Just don't flash an actual rom, and you should be fine.
lviv the reason there aren't many options on the ET for recovery is there aren't many devs that work with it. SteadyHawkin repacks rogue for us, and that's about it. We used to have a few others that did so, but now it's just SH. Personally I don't really care as rogue recovery works perfectly fine, and the reason we use stock CWM from EL26 is because it's all we need (no point in repacking another kernel since we all have access to that one, why waste the effort to put CWM on EL29 when chris41g did a fine job on EL26 and we are all using it for ICS flashing right now?). No point putting any more work into packing a diff recovery on ICS kernels when there's no source and there's a ton of fear of bricking going on.
I'm certainly no dev, but those are my observations.
I've said this before in the threads discussing the bricks. I am not a dev, so they can correct me.
I don't think the bricks had anything to do with the rogue repacks. I think it has to do with the way ICS handles the data partition. It seemed like the bulk of the bricks happened when we tried a factory reset, or wipe data and at that point we burned up our emmc chips.
Sounds crazy that that is possible just wiping a data partition, but it was pretty consistent.
At first I thought it was the temp touch recovery because that was what people were using when ICS was first leaked. I think most of us were also flashing it through the stock recover rather than odin or mobile odin. But, it began happening with rogue repacks as well.
Once the source drops these problems will probably clear up.
To the ops question, someone already answered. We can flash just about everything else with the repacks. I prefer the rogue repacks because he has streamlined them making them handier to use.
Sent from my SPH-D710 using Tapatalk
I understand that some have had luck and others haven't. It just seems to me that if it doesn't brick every phone then it can't be the recovery itself. There has to be another common denominator. I guess the issue is that until that common denominator is figured out it could be dangerous to use.
Sent from my SPH-D710 using XDA
Devi0124 said:
I understand that some have had luck and others haven't. It just seems to me that if it doesn't brick every phone then it can't be the recovery itself. There has to be another common denominator. I guess the issue is that until that common denominator is figured out it could be dangerous to use.
Sent from my SPH-D710 using XDA
Click to expand...
Click to collapse
Exactly, I have been flashing things with the Rouge recoveries with no issues at all. I always use the Format all zip though and not the wipe in recovery, and that does wipe data so not really sure what is causing people to brick there phones.
I've never bricked using the ICS repacked recoveries, and I've used em to flash to different roms without format.zips before we knew it was even an issue, but now that I know this could potentially brick your phone, I won't be doing anything in recovery anymore except flashing themes or something that does not involve wiping. I'm not longer on ICS anymore though, as I see it completely pointless until official is out. Too much flashing, and not enough functionality ATM to see usable, runs kinda slow too, not complaining at all just stating why I'm not on it, when it's official it will be great, and the devs will be able to tweak the final build for some massive speed.
It is the data partition I believe, I'm not 100% sure on this but I think the wipe in recovery doesnt actually just wipe but reformats and resets the partition sizes whereas the wipeall zips just erase the data leaving the partitions alone
To simplify compare it to reformatting your harddrive in your PC.vs just factory resetting it or deleteing the data off of the drive leaving the OS intact but removing added on data
Sent from my SPH-D710 using xda premium
i flashed roms with rouge
FYI there's evidence of problems in the kernel source.
I9100 update4 seems fine - but apparently Koreans are having lots of problems with the SHW-M250S/K/L source drop, and also gokhanmoral of SiyahKernel encountered a bunch of bricks when he attempted to rebase on the SHW-M250* source code base.
I'm another original epic owner that just switched to the touch....I've rooted and flashed ics.....now over there on the epic 4g we don't have ics source either...but we have cwm that flashes roms ,backups, restores, we can even flash a ROM to boot from the sdcard to calibrate the sensors and update your prl....so why do we need source on the touch to acquire those luxuries?
XDA Premium
rujelus22 said:
Exactly, I have been flashing things with the Rouge recoveries with no issues at all. I always use the Format all zip though and not the wipe in recovery, and that does wipe data so not really sure what is causing people to brick there phones.
Click to expand...
Click to collapse
Same here as far as flashing things via rogue recovery. I even nandroided back to a gb rom from the fc24 repack, after wiping manually. I am not a fan of wipe all, i just like to verify my actions, so I do it manually. I am definitely not sure what is causing issues, but different phones have different actions on kernels in general, and our phones arent even near ready to handle them. That is why it is taking so long in order to push out official ICS, cause they need it to function on every phone, not just one. I am running mijjah XPLOD mini, and it works fantastic on my phone, but during charging it overheated until I flashed over the FD19 kernel.... Then problem solved. Maybe just a lot of these phones were first gen epic touches, and they couldnt handle the newest kernel..... I just bought my phone in december, so maybe my phone can handle it.... Just a something to ponder over.
Sent from my SPH-D710 using xda premium
Entropy512 said:
FYI there's evidence of problems in the kernel source.
I9100 update4 seems fine - but apparently Koreans are having lots of problems with the SHW-M250S/K/L source drop, and also gokhanmoral of SiyahKernel encountered a bunch of bricks when he attempted to rebase on the SHW-M250* source code base.
Click to expand...
Click to collapse
Thanks Entropy512 for the great response and insight! I hope more of the newbies (and some of the other hold outs) read your post. If guys like you, SiyahKernel, SteadyHawkin and some of other unbelievably fantastic devs can major issues and/or brick their device, and have found it to be the kernal (the other 'real' devs' have said that too!); than I for one and going with that! Thanks for all your work. Hopefully we'll get the final real source soon and than can pick through that.
-EViL-KoNCEPTz- said:
It is the data partition I believe, I'm not 100% sure on this but I think the wipe in recovery doesnt actually just wipe but reformats and resets the partition sizes whereas the wipeall zips just erase the data leaving the partitions alone
To simplify compare it to reformatting your harddrive in your PC.vs just factory resetting it or deleteing the data off of the drive leaving the OS intact but removing added on data
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
I think you nailed it EK. If you watch what's going on in recovery when you flash the format all zip, it formats system which is not the same as a factory reset. After system it formats cache and dalvik. I haven't heard of any bricks flashing Calkulin's format all zip with an ICS recovery and then flashing an ICS rom. I've done it myself a few times but to be safe I now flash the EL26 kernel first.
Related
So I flashed the Samurai Kernel over the rebirth RC. The post blatantly said to have patience. How much patience should I have? It has sat at the Samsung screen for over 10 minutes - should I wipe everything x3 and reflash again? Keep waiting? Should I throw my "epic" failphone against a wall?
What say you xda?
Crap like this happens often. If you test or build your own roms, kernels, themes, mods, this stuff is normal and you just deal with it. Redownload, reflash, and try again. If you continue to have issues, either you don't know what your doing, or maybe you should ask for help with a more positive tone.
Sent from shane6374's Epic via Tapatalk
Well, you could erase your frustrations by flashing the rfstoext4 or vise versa. That will work better than destroying your phone.
Sent from my MIUI Epicaladocious.
Maybe an accidental full wipe?
Sent from my SPH-D710 using xda premium
I'd recommend using odin to either go back to stock EC05 and use the the one click root/cwm purple recovery and then boot up, turn on usb mass storage and copy a rom that already has the kernel in it like ACS ICS. That's the best way imo to have a successful flash with no hiccups.
Or, take the easy way out and just boot into recovery and flash the ICS ACS rom after wiping data, cache, dalvik x3.
Also, please keep in mind that official gingerbread is still very young in this community and it'll take a few weeks to get everything working smoothing and seemlessly as far as roms/kernels go.
Sent from an Icy Gingified OG Epic...
I'm really trying to understand the difference. Is it more a personal preference in using a touch interface & options, or are there some core differences as to why you should use one over the other, especially in flashing the ICS ports we're using on our T989's.
In one post I've been reading, they're instructing you to use 'touch recovery' to flash the ROM. And in other post I've been reading, a highly trusted member said he won't use touch anymore because of issues he's had with it. I've seen it go both ways many times.
I read in another post, that one member thought the 2 versions handled the cache partition differently. If that's the case, doesn't using thederekjay's Darkside SuperWipe make that null & void anyway, because it formats, erases and aligns all the disks partitions properly anyway before you flash?
I've never used touch to flash an ICS ROM, or any ROM yet, and I'm certainly not against it. But I haven't had a lot of the issues that some are having either to make me go that way. So I'm trying to determine, or see if you guys really think that using one version over the other can really make a difference in the stability of the ROM; and if so...then why? Thanks!
And of course; if the OP tells me to use touch recovery to flash their ROM, I will certainly do so if I flash the ROM. Just trying to get a better understanding.
I use touch. Its just a personal preference. Then again the errors are a hit or miss thing.
Sent from my SGH-T989 using Tapatalk
recovery version doesn't matter. it would be quite cumbersome to flash a different recovery every time i wanted a different rom. Touch vs no touch just affects GUI and user interacting, nothing more.
When in RECOVERY I want stability ....no touch gimmicks necessary if there's even the slightest chance of an error.
Sent from my SGH-T989 using XDA
bzlik88 said:
When in RECOVERY I want stability ....no touch gimmicks necessary if there's even the slightest chance of an error.
Sent from my SGH-T989 using XDA
Click to expand...
Click to collapse
word. having to button press your way thru the menues is a security feature.
SGS2 (T989) on CM7_373R5
Touch is the best way!!
I used for much time the Classic CWM, until I want flash the new ICS Rom; I have a lot problems, boot loop, kernel loop, reboots, FCS…. My solution was the new CWM Touch Version.
After I make all wipes with this CWM Touch version all things on ICS for T-Mobile t989 works very very well.
In my opinion non-touch recovery works best because its stable and touch recovery is still experimental and can still have some bugs.
Sent from my SGH-T989 using XDA
osangoqui said:
I used for much time the Classic CWM, until I want flash the new ICS Rom; I have a lot problems, boot loop, kernel loop, reboots, FCS…. My solution was the new CWM Touch Version.
After I make all wipes with this CWM Touch version all things on ICS for T-Mobile t989 works very very well.
Click to expand...
Click to collapse
I had the same experience. Which was confusing.
I figured it was just people not flashing properly which was causing the issues.
So I used non-touch CWM. Tried 4 times with various combinations of wiping to try and get it to boot. To no avail.
Flash touch CWM, flash once, works perfectly. So confused as to why that is.
So this is what confuses me. I was just reading through some posts at the 'NexusMod' thread. A member posted that some of the issues another member was having with the ROM was due to the user using standard recovery. He said standard recovery makes the cache partition as r/o instead of r/w and this is causing some of the issues when people flash the ICS ROMS.
Really? So in GB ROMS it doesn't matter if it's r/o because I've always used standard recovery and never had, or heard of these issues before related to the recovery?
So there's that big of a difference between the 2 versions of recovery that one leaves the cache partition as r/o and the other r/w. That seems pretty major to me if true. I'm not doubting anybody here, just trying to get a better understanding so I know which recovery to use.
I like and just feel safer using the non-touch version. But if need be, I could go touch... If I need too.
Sent from my SAMSUNG-SGH-T989 using Tapatalk
Are the ics roms safe to flash? The 1st time I flashed a ics rom,i had probs. No recovery,glitchy and jus plain janky. Im sure they have come along way. Can som1 recommend a safe stable ics rom that also has rogue recovery or acs?
Sent from my SPH-D710 using xda premium
If you want to go back to gingerbread use el29 restore get recovery then flash CyanogenMod 9 it is better than most roms based off leaks.
Here is the latest stock ICS.
http://forum.xda-developers.com/showthread.php?t=1694695
Give the devs a little time and you can flash a kernel with the recovery you want.
harley1rocker said:
Are the ics roms safe to flash? The 1st time I flashed a ics rom,i had probs. No recovery,glitchy and jus plain janky. Im sure they have come along way. Can som1 recommend a safe stable ics rom that also has rogue recovery or acs?
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
They are safe to flash if you follow OP directions. Always flash from el26 cwm recovery and you're good. If you cant live without recovery, flash a touchwiz rom and use agat63s repack recovery.
SFhub just released an updated FF02+CWM repack built on GB code to avoid the eMMC lockup bug. However, you need to check the ROM and see if update-binary is corrected or not.
Please look for his post on this here:
http://forum.xda-developers.com/showthread.php?t=1694695&page=7
The other safe solution is the one that has been known - go back to EL26 and flash away from there. (GB doesn't have the offending code that causes the bug to be triggered.)
I've been using Calkulin's E4GT 2 v1.6 ICS rom since version 1.6 came out (FE22) and I haven't had a single crash or FC, and I've been getting good battery life.. I never even get close to dying and thats even with a couple hours of screen on time (games, facebook, lots of texting, ~1hour talk time).
I'd say go for it =) Just make sure you follow all instructions carefully! This ROM was very easy to flash.. I had been using Calkulin's GB rom (el29) and all I had to do was wipe my caches and flash his .zip file in CWM.. bam, ICS ^_^
When you say safe what is it you really mean... cuz its all SAFE if you know what you are doing..
Well nothing is ever 100% safe. There is always a small chance you could screw things up somehow (the eg31 deal back when the phone was first released, the emmc bug, etc). There are always possible unknown side effects that don't become obvious until down the line.
That said, if you are careful, the odds of doing something irreversible are extremely small on a phone that has been out for a few months or more.
Sent from my SPH-D710 using Tapatalk 2
I've been flashing roms for several months now...I've tried nearly every ICS one out there. I've really enjoyed quite a few but the urge always kicks in to try a shiny new one once I see those screenies. Until now, due to being fearful of bricking my phone and not knowing a correct way, I've always made a nandroid only as a safety valve in case something went wrong. Luckily, nothing ever did and I never had to use one. Every time I tried something new, I started from scratch. Every time I went back to an older rom, I did the same. Quite time consuming and no doubt unnecessary. But now I've set up and backed up several roms just the way I like them and would like to go back and forth without having to download every app from scratch and configuring screens, fonts, settings, etc...
These are all ICS roms that I've set up, specifically Blu Kuban, Anakonda, m'ICS, and Wicked Sensations. Now I see Hooligan and I've just got to give it a spin. My question is...what is the safest procedure to go back to my other nandroid backup roms? EL26 and restore? Or are the newer kernels safe to go from one ICS rom to another?
I'm sure this is a dumb question but it's just a procedure I've avoided up until now due to paranoia.
Grab Agat's latest kernel. Him and Chris41g put together a safe and awesome kernel. I've done loads of wipes and restores. I am an image freak; left over habits from loads of disaster recovery work. And it makes messing with all these great ROMS ready and fun.
Sent from my SPH-D710 using xda premium
leaderbuilder said:
Grab Agat's latest kernel. Him and Chris41g put together a safe and awesome kernel. I've done loads of wipes and restores. I am an image freak; left over habits from loads of disaster recovery work. And it makes messing with all these great ROMS ready and fun.
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
Thank you, sir. Just what I was hoping to hear!
Yes, i can also vouch for the safety of agat's awesome kernels. I used it several times to flash from ics to gb and everything was smooth.
I rooted my sister's E4GT last year and she's still running Calkulin's E4GT ROM v2.6 and her current kernel is 2.6.35.7-SPH-D710.EL13-CL806482
She's still on Gingerbread, and I want her to enjoy the ICS experience or JB if there's any stable JB ROMs.
My phone is an EVO so I am not comfortable/familiar with the Samsung pitfalls. I don't want to brick my sister's phone.
On my phone I'd download the zip, and in recovery factory reset, wipe data, cache, dalvik, system, and then flash the ROM, but I've read that could lead to a brick on the E4GT.
What's the safest way for me to flash some ICS/JB ROMs for her to try out?
Sent from my EVO
Easily answered by reading a couple posts. Use search.
Odin safe el26 with cwm, calkulin format all x2, flash rom.
Sent from my SPH-D710 using XDA
Bannjio said:
Easily answered by reading a couple posts. Use search.
Odin safe el26 with cwm, calkulin format all x2, flash rom.
Sent from my SPH-D710 using XDA
Click to expand...
Click to collapse
Just look at ICS roms and first few post to see how they perform. Flash away.
The safest recovery to use is el 26 cwm
http://chris41g.devphone.org/EpicTouch/Stock Repack/EL26/StockCWM-EL26.tar.md5 For Odin or Mobile Odin if you have that.
You can just flash just about anything once you are in that recovery. The only major difference for you to know is that once you flash the rom, the kernel that is packed into the rom will also change the recovery. Also I do not really think there is a need to use a wipe all zip just unnecessary and usually causes error's when installing certain roms.
Most of the newer rom's do come with a safe recovery, but if you are unsure and have not read much and verified that the included recovery in the rom is safe I would recommend using el26cwm.
You can also use this recovery, this one will boot straight to recovery
http://shabbypenguin.com/k0/ecm/E4GT-EL29-directbootCWM-v3.tar.md5
im0rtalz said:
The safest recovery to use is el 26 cwm
http://chris41g.devphone.org/EpicTouch/Stock Repack/EL26/StockCWM-EL26.tar.md5 For Odin or Mobile Odin if you have that.
You can just flash just about anything once you are in that recovery. The only major difference for you to know is that once you flash the rom, the kernel that is packed into the rom will also change the recovery. Also I do not really think there is a need to use a wipe all zip just unnecessary and usually causes error's when installing certain roms.
Most of the newer rom's do come with a safe recovery, but if you are unsure and have not read much and verified that the included recovery in the rom is safe I would recommend using el26cwm.
You can also use this recovery, this one will boot straight to recovery
http://shabbypenguin.com/k0/ecm/E4GT-EL29-directbootCWM-v3.tar.md5
Click to expand...
Click to collapse
Thank you, Was trying to find the recovery to direct that way first but couldn't find the link ( plus at work so little destracted)
im0rtalz said:
Also I do not really think there is a need to use a wipe all zip just unnecessary and usually causes error's when installing certain roms.
Click to expand...
Click to collapse
Most of the roms I have flashed say to use format all. I always use it and haven't come acrossed any errors. Doesn't mean it is absolutely necessary or will not cause errors though.
Sent from my SPH-D710 using XDA
Thanks everyone for responding. I'm good to go!
Sent from my EVO using xda app-developers app