Related
first time I flashed aokp it was all gravy until I tried to boot into recovery, I got the Android System Recovery. I got scared and I read around and ended up odin'ing back to stock and flashing another rom.
I really like aokp so I wanted to try it again. I made very sure I followed the directions, I did not flash from an ICS recovery. I try booting into recovery to see if it worked this time and sure enough, there is android system recovery again, what am I doing wrong?
I searched for this too and saw that someone said to reinstall the packages and reboot, and do it again or something like that and it would boot into CWM, but that was for a different phone so I wasnt gonna try that.
Can I just run the eg4tauto.zip and isntall el26 with cwm to get recovery back and be good, or do I need to odin?
Any help would be greatly appreciated.
krook250 said:
first time I flashed aokp it was all gravy until I tried to boot into recovery, I got the Android System Recovery. I got scared and I read around and ended up odin'ing back to stock and flashing another rom.
You need to read the OP in the thread.
I really like aokp so I wanted to try it again. I made very sure I followed the directions, I did not flash from an ICS recovery. I try booting into recovery to see if it worked this time and sure enough, there is android system recovery again, what am I doing wrong?
I searched for this too and saw that someone said to reinstall the packages and reboot, and do it again or something like that and it would boot into CWM, but that was for a different phone so I wasnt gonna try that.
Can I just run the eg4tauto.zip and isntall el26 with cwm to get recovery back and be good, or do I need to odin?
Any help would be greatly appreciated.
Click to expand...
Click to collapse
There is no cwm on aokp codename etc for a reason ....to stop people from bring stupid and bricking ....don't use a ics kernel with cwm for anything .... Use el26 to flash any ROM u need and when you want to go to another use mobile Odin or regular Odin to flash el26 kernel again and boot into cwm .... El26 is a GB kernel and won't boot a ics ROM ....then you can flash anything GB or ics
Sent from my SPH-D710 using Tapatalk 2 Beta-5
thanks for your response, but I think I am more confused, I was trying to flash a different modem. when I am not connected to 4g, my data is terrible, with 4g, I am all good. I was going to try a different modem. In the OP, for modems it says this:
Modems
FC18 Modem: DOWNLOAD
Flash through Stock CWM Recovery OR pull the modem.bin out of the .zip file and flash in the Phone option in Odin(mobile Odin doesnt flash modem)
Click to expand...
Click to collapse
You probably should flash back to a touch wiz ROM.....you can Odin the el29 tar or one click from sfhub .
http://forum.xda-developers.com/showthread.php?t=1433101
you can Odin the modem and then update profile and prl in tw then you can flash the el26 cwm http://www.mediafire.com/?hkydca9ob98z89m
and go back to aokp or codename etc
Sent from my SPH-D710 using Tapatalk 2 Beta-5
sorry if this is a dumb questions, but what if I get stuck in a boot loop and I have no recovery? just go into download mode and odin my way out?
one other thing, I started flashing ics roms with venum ice and flashed to mijjz ics and caulks and others and never had a problem, was I just lucky so far? I don't recall mijjz or venum's installation instructions saying I needed to odin back to stock before flashing. Sorry for the noob questions, but I've read a bunch and just trying to piece it all together. I read so I don't brick, but then I end up with more questions.
I'm also wondering about this I've spent a good deal of time trying to put the time line of the et4g together and I think I got most of it....just got my shiny white et4g two days ago my wife has had hers. for about 4 mo. shes much less fearless when it comes to flashing on this phone. (however shes settled in on build 27 of aokp, and I doubts shes gonna be flashing anytime too soon.) I'm coming over from my NS4G which always had clear cut rules to flashing! CWM all day. The only thing(s) I ever had to watch for was is it aosp, or not? An do I do a wipe or not? (I got in the habit of wiping just to be safe, and man I flash with the best of them! At least 2 times a week)
OK, OK sorry about the ramblings of my history my real questions are:
A) So Im sitting on alpha 2 of CM9 (nice piece of work I must Say) I made sure I was in the green, and had everything lined up to flash this one! went smooth of course. It wasn't until after my flash that I tried to make a nandroid....I get why theres no clockwork! but I'm totally clueless on how to back up with out it, or if you even can make one with stock recovery?
Can I keep CM9, and flash a kernel with rouge recovery to the make a nandroid? Or is there another way to go about this (I like to make nandroid often as a easy way to restore data after I play around with stuff and brake Wifi or what have you, and scrap unneeded back ups as I find out what I can and cant do with MY phone.)
I really really love Cryogen 9 (yeah its not as far along as I would like it to be ex- cm7 for the ns4g or kangs aokp builds) But there a team I'm familiar with. An I like there stuff, but I'm really nerves about where I go from here if/when i decide to change to something else.What are the guide lines for flashing from cm9 to say another ICS build? and is CM9 compatible with other kernels or only the one that is came packed with?
B) can someone straight up make a new clean thread with proper flashing tech. and no filler or out dated info then the have a mod stick it and close it>>>>simplify this for those of us that know what were doing....until things go funk for some reason, or another and that leaves ,us we are completely lost!
Well after wrighting my first novel (joke haha) I would like to thank everyone thats put up there time and money to make phones OURS and more powerful then what hit the shelfs an allowing me to get the most customized electronic device I have ever seen with the exception of my PC. Clapping
If you want to backup your system with the stock cm9a2 kernel, just mobile odin/odin el26 kernel/recovery, boot into cwm, flash stock cm9a2 kernel, now while still in cwm do a nand backup. That way it will be a full backup.
Sent from my SPH-D710 using xda premium
I know I'm a little late, but there is CWM for the AOKP rom. The FC07 BootImg on the e4gtuato.zip file worked fine for me on the older version which was based off of FC15.
faceyourfaces said:
I know I'm a little late, but there is CWM for the AOKP rom. The FC07 BootImg on the e4gtuato.zip file worked fine for me on the older version which was based off of FC15.
Click to expand...
Click to collapse
I would try that, but these folks have me scurred about using cwm within aokp. I have flashed between caulks ics/venum ice, anakonda/mijjz goodness,xplod mini and a couple other ICS roms all from cwm with absolutely no issues so far.
I am thoroughly confused right now. I am on aokp build 28 with a few significant issues and not sure what what direction to go next. I know how to get out of aokp safely now, but not sure which rom i want to go to, little issues with each that I dont know how to fix yet.
krook250 said:
I would try that, but these folks have me scurred about using cwm within aokp. I have flashed between caulks ics/venum ice, anakonda/mijjz goodness,xplod mini and a couple other ICS roms all from cwm with absolutely no issues so far.
I am thoroughly confused right now. I am on aokp build 28 with a few significant issues and not sure what what direction to go next. I know how to get out of aokp safely now, but not sure which rom i want to go to, little issues with each that I dont know how to fix yet.
Click to expand...
Click to collapse
Read this thread it happens when using ics kernel with cwm .and then tell us u want to use cwm with a ics kernel.....it bricks phones please read it and understand
http://forum.xda-developers.com/showthread.php?t=1525495
That's why people are using Odin to get el26 GB on their phones to flash with
Sent from my SPH-D710 using Tapatalk 2 Beta-5
krook250 said:
I would try that, but these folks have me scurred about using cwm within aokp. I have flashed between caulks ics/venum ice, anakonda/mijjz goodness,xplod mini and a couple other ICS roms all from cwm with absolutely no issues so far.
I am thoroughly confused right now. I am on aokp build 28 with a few significant issues and not sure what what direction to go next. I know how to get out of aokp safely now, but not sure which rom i want to go to, little issues with each that I dont know how to fix yet.
Click to expand...
Click to collapse
If you have been having luck thats fine but I can not see how you have not noticed int eh OP of the ICS roms and the OP of the recoveries it gives you instructions on what to do and what not to do. Also there are quite a few threads in here about the horror stories of the now infamous blue light of death. Once again if you have escaped this then maybe you should tell us your secret to success. Honestly the few extra steps it takes to ensure your phone stays your phone is well worth it.
Like Epix has posted please read up a little just incase something happens to you or anyone else who claims no problems so you know how to help yourself. Hopefully we wont have to see a I Think I just bricked my Phone thread from you.
Odin EL26 CWM and basically everything else stays the same after that... except you would need to either reflash the ICS rom you are using or have a copy of the kernel readily available
Epix4G said:
Read this thread it happens when using ics kernel with cwm .and then tell us u want to use cwm with a ics kernel.....it bricks phones please read it and understand
http://forum.xda-developers.com/showthread.php?t=1525495
That's why people are using Odin to get el26 GB on their phones to flash with
Sent from my SPH-D710 using Tapatalk 2 Beta-5
Click to expand...
Click to collapse
I've read that, hence the reason for my posts. I am not going to load cwm and start flashing away. From aokp, I will odin back to GB before I flash any new ICS roms. I also won't be flashing between other ICS roms, even ones I have done before with no problems. I odin every time now, but it is putting a serious damper on my flashing addiction.
I could flash 3 roms in the time it takes me to odin back to GB, lol!
krook250 said:
I've read that, hence the reason for my posts. I am not going to load cwm and start flashing away. From aokp, I will odin back to GB before I flash any new ICS roms. I also won't be flashing between other ICS roms, even ones I have done before with no problems. I odin every time now, but it is putting a serious damper on my flashing addiction.
I could flash 3 roms in the time it takes me to odin back to GB, lol!
Click to expand...
Click to collapse
I don't Odin to stock all the time I mobile Odin the el26 cwm kernel and then boot strait into recovery as the GB kernel won't boot the ics ROM and then I flash from there but I also u caulks format all too ....
Sent from my SPH-D710 using Tapatalk 2 Beta-5
Epix4G said:
I don't Odin to stock all the time I mobile Odin the el26 cwm kernel and then boot strait into recovery as the GB kernel won't boot the ics ROM and then I flash from there but I also u caulks format all too ....
Sent from my SPH-D710 using Tapatalk 2 Beta-5
Click to expand...
Click to collapse
Thus is what I used to do at first myself I would flash the CWM kernel then just nandroid back my old rom and keep it moving. It just basically seems that as long as you do everything in a GB kernel based recovery as long as it is not the Touch recovery you should be OK
Sent from my SPH-D710 using Tapatalk
I am gonna look into mobile Odin so i don't have to be sitting at a PC to do work. So if I go back to gb and get my modem biz straightened out then flash an ics rom, my modem changes will stick?
It seems like this issue is isolated to sprint only, right? Much buddy on att is flashing ics over ics like crazy. And he said he hasn't seen anything like this over there.
Sent from my SPH-D710 using XDA
I've only used the ICS recovery on AOKP to change modems and flash GB roms because it probably wouldn't work too well with other ICS roms.
krook250 said:
I am gonna look into mobile Odin so i don't have to be sitting at a PC to do work. So if I go back to gb and get my modem biz straightened out then flash an ics rom, my modem changes will stick?
It seems like this issue is isolated to sprint only, right? Much buddy on att is flashing ics over ics like crazy. And he said he hasn't seen anything like this over there.
Sent from my SPH-D710 using XDA
Click to expand...
Click to collapse
UPDATE: It seems that using recovery on Touchwiz-based ICS roms (like Blend ICS) is safe but it is much more dangerous on roms built from stock (like CM9). Your buddy must be using roms based off of leaked builds and not stock AOSP.
------------------
If you flashed back to Gingerbread to change your modems and installed an Ice Cream Sandwich rom over it the modem should stay.
faceyourfaces said:
I've only used the ICS recovery on AOKP to change modems and flash GB roms because it probably wouldn't work too well with other ICS roms.
UPDATE: It seems that using recovery on Touchwiz-based ICS roms (like Blend ICS) is safe but it is much more dangerous on roms built from stock (like CM9). Your buddy must be using roms based off of leaked builds and not stock AOSP.
------------------
If you flashed back to Gingerbread to change your modems and installed an Ice Cream Sandwich rom over it the modem should stay.
Click to expand...
Click to collapse
It has nothing to do with that it's the ics kernel and aosp and tw is using the same kernel but with minor changed , because there is no source released there can't be a built from source aosp kernel ....there is no safe ics kernel with cwm when source is released they will fix it, but the note has the same problem
Sent from my SPH-D710 using Tapatalk 2 Beta-5
Epix4G said:
It has nothing to do with that it's the ics kernel and aosp and tw is using the same kernel but with minor changed , because there is no source released there can't be a built from source aosp kernel ....there is no safe ics kernel with cwm when source is released they will fix it, but the note has the same problem
Sent from my SPH-D710 using Tapatalk 2 Beta-5
Click to expand...
Click to collapse
The recovery that came with Blend ICS worked fine for me though. Trying to flash using recoveries on other ICS roms gave me soft bricks. Would you have any idea how Blend worked for me?
faceyourfaces said:
The recovery that came with Blend ICS worked fine for me though. Trying to flash using recoveries on other ICS roms gave me soft bricks. Would you have any idea how Blend worked for me?
Click to expand...
Click to collapse
It is the same recovery and soft bricks ate usually from not wiping right....but use that kernel with cwm and wipe data and your risking a b.l.o.d. It doesn't take much ....the thing is Samsung changed a couple things with how the data partition is handled and they also changed a couple other partitions and sfhub said he thinks it writes over two of the partitions at the same time when wiping and makes both unusable creating a brick
... writers thing is it damages the emmc somehow and makes it even impossible to jtag it .... Which should really never happen
Sent from my SPH-D710 using Tapatalk 2 Beta-5
Epix4G said:
It is the same recovery and soft bricks ate usually from not wiping right....but use that kernel with cwm and wipe data and your risking a b.l.o.d. It doesn't take much ....the thing is Samsung changed a couple things with how the data partition is handled and they also changed a couple other partitions and sfhub said he thinks it writes over two of the partitions at the same time when wiping and makes both unusable creating a brick
Click to expand...
Click to collapse
So the best thing I guess would be to just to avoid ICS recoveries all around.
I'm just wondering. I came from the first epic and that was much easier to flash stuff on to. I came to this phone and was able to successfully root flash and boot on the first attempt. Do people not read the whole first post?
Sent from my SPH-D710 using Tapatalk 2 Beta-5
Sent from my SPH-D710 using xda premium
If you asked this question about 1-2 months ago, then the cause is because the whole transition to ICS, especially from AOSP roms hasn't been smooth. During that time, the cause for bricks wasn't quite known and people who always wanted the latest roms suffered the most.
...with that said, if you still brick now though, then yeah, it's because you aren't reading the directions properly lol.
I don't flash anything until QB king makes a how-to video and I go follow it step by step as it's playing, don't see any other way if your playing it safe.
It was kind of hit and miss when first ics was coming out but they have figured out Samsung allowed a couple partitions to be written to on ics that wasn't that way on GB but until source is released for or phone people who don't read and flash with ics kernels will continue to brick ....its sad that its still happening
Sent from my SPH-D710 using Tapatalk 2
Yeah it's because of the issue with wiping partitions while running an ICS kernel repacked with CWM. This issue is much more pervasive, if not exclusive to AOSP ROMs. Some of the early bricks didn't necessarily involve an AOSP ROM, but rather CWM Touch recovery and "temp" recovery via ROM Manager. Today, they seem to all be flashing an ICS kernel repacked with CWM on an AOSP ROM then running some kind of system format.
People on the whole have never read or educated themselves before flashing, so until the issue is resolved (hopefully when Samsung publishes their kernel source code) there will continue to be bricks. Those that read and stay in the loop will be saved the frustration.
FYI, there were VERY few bricks prior to the ICS leaks, and the few that bricked was the typical bad Odin, cable yanked mid flash, flashed the wrong firmware type of stuff. This phone WAS very hard to hard brick pre-ICS leaks.
Ah, well hopfully it returns to its hard to brick status once the ics source is out. Will we be able to have cwm permenitly once the source Is out?
Sent from my SPH-D710 using Tapatalk 2 Beta-5
ShinigamiH4ck3r said:
Ah, well hopfully it returns to its hard to brick status once the ics source is out. Will we be able to have cwm permenitly once the source Is out?
Sent from my SPH-D710 using Tapatalk 2 Beta-5
Click to expand...
Click to collapse
Nope its part of the kernel when you install a new kernel it will overwrite your cwm and give you whatever is packaged with it if its the same ROM usually the dev will use the same cwm but some devs like different versions rouge acs etc ....
Sent from my SPH-D710 using Tapatalk 2
Damn, will the recoveries that come with the kernels not brick my phone at least? Or will I have to Odin every time I update/change a ROM
Sent from my SPH-D710 using Tapatalk 2 Beta-5
ShinigamiH4ck3r said:
Damn, will the recoveries that come with the kernels not brick my phone at least? Or will I have to Odin every time I update/change a ROM
Sent from my SPH-D710 using Tapatalk 2 Beta-5
Click to expand...
Click to collapse
Your only sure fire safe route is to Odin or Mobile Odin the EL26 kernel with CWM recovery then wipe and flash from there. People flashing Touchwiz ROMs are using ICS recovery and wiping with format all or modified format zip and seem to be OK but the bricks are random. People have bricked wiping data, cache, and dalvik invidually as well so its best to play it safe unless you are willing to accept the fact that a random brick may happen
Sent from either ET4G or NS4G using Xparent Tapatalk 2
ShinigamiH4ck3r said:
Damn, will the recoveries that come with the kernels not brick my phone at least? Or will I have to Odin every time I update/change a ROM
Sent from my SPH-D710 using Tapatalk 2 Beta-5
Click to expand...
Click to collapse
Once the source comes out the kernels and ics in general should become more stable so that bricks won't happen.
I have model SPH-D710.
I followed the guide here.
I had no problems whatsoever until the final reboot. Now my phone's stuck at the 2nd loading animation... the one with the android on the skateboard in the middle of the screen with the blue things coming at you.
I can boot into Odin mode. I cannot, however, boot into recovery mode.
Is there anything I can do? Did I totally screw up my phone to where I'm going to just have to buy a new one and cry about it because my dad would have killed me for voiding my warranty on "such an expensive phone?"
Try regular booting again
This happened on my og epic and my nexus s when I install cm9
Just holding the power button to tun off them holding it to turn on helps
Also it takes a while to boot up
Sent from my SPH-D710 using xda premium
gtuansdiamm said:
Try regular booting again
This happened on my og epic and my nexus s when I install cm9
Just holding the power button to tun off them holding it to turn on helps
Also it takes a while to boot up
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
I'm going to have to let it charge now... It died sitting on that animation for the last hour.
So... it's still not working
This is what you do
Odin to el29
Get root and recovery (just get cwm nothing fancy like rogue)
Go to recovery
Wipe everything
THen install cm9
You have have flashed from an pics recovery and that doesn't work so use el29
Sent from my SPH-D710 using xda premium
Don't think it was mentioned but Alpha 5 does not have recovery, this was done to prevent people from doing stupid things like factory resetting or installing roms.
The nightly builds have a safe recovery as well as themselves safe to flash on ICS recoveries if you need to head that direction next. But a replacement for Alpha 5 will be out in eventuality with all that as well.
I got it to work after I flashed back to GB and then back to alpha 5.
No idea what went wrong before, but it works now!
You probably flashed from an ics recovery
For some reason we can't get rom flashing on ics to work
Every one has been using Odin to go to el29 or at least they flashed the kernel with the recovery of el29 them flashed the rom
Sent from my SPH-D710 using xda premium
EL29?
Am I missing something here? I've been using EL26 to flash.
Should I be using EL29? Because i don't want be doing something that can potentially harm my phone.
Sent from my sprint Samsung galaxy s2 Epic 4g touch with ics using cm9 on the blazing slow now network
gilbydakid said:
EL29?
Am I missing something here? I've been using EL26 to flash.
Should I be using EL29? Because i don't want be doing something that can potentially harm my phone.
Sent from my sprint Samsung galaxy s2 Epic 4g touch with ics using cm9 on the blazing slow now network
Click to expand...
Click to collapse
You are ok with EL26.... just keep following what the OP says in the rom threads and you will be alright.
gilbydakid said:
EL29?
Am I missing something here? I've been using EL26 to flash.
Should I be using EL29? Because i don't want be doing something that can potentially harm my phone.
Sent from my sprint Samsung galaxy s2 Epic 4g touch with ics using cm9 on the blazing slow now network
Click to expand...
Click to collapse
You can use the EL26 kernel on EL29 some people flash just the EL26 kernel for recovery, other people odin to EL29 and use the auto rooter to flash the EL26 CWM or EL29 Rogue kernel. Last i checked the CM9 brick from flashing with Rogue is a simple soft brick easily fixed with odin.
gtuansdiamm said:
You probably flashed from an ics recovery
For some reason we can't get rom flashing on ics to work
Every one has been using Odin to go to el29 or at least they flashed the kernel with the recovery of el29 them flashed the rom
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
My friend you may have a little homework to do. Things have improved greatly for us in reference to flashing roms with certain recoveries and kernels for ICS. I for one use the nightlys for CM9 and flashing roms and wiping has been fixed.
Do yourself a favor and stroll through development and read up on the new stuff that has come about over the last couple weeks or so.
Enjoy guys and OP glad you got your phone back up and running. Next time don't panic!
playya said:
My friend you may have a little homework to do. Things have improved greatly for us in reference to flashing roms with certain recoveries and kernels for ICS. I for one use the nightlys for CM9 and flashing roms and wiping has been fixed.
Do yourself a favor and stroll through development and read up on the new stuff that has come about over the last couple weeks or so.
Enjoy guys and OP glad you got your phone back up and running. Next time don't panic!
Click to expand...
Click to collapse
Hey if it ain't broke don't fix it you know
I really don't know current happenings in the Dec section cause well I've been busy.
Lets just keep things friendly only say this cause well I don't know you tone
Sent from my SPH-D710 using xda premium
So I just went from running pure stock rooted FI25, flashed agat's 0.5.4 source built kernel via odin, then rebooted into that custom recovery and flashed AOKP 3.1, flashed JB Gapps, and rebooted to blue LED.
We all run the risk I guess; just frustrating to see it happen on a process I've done literally hundreds of times.
Ordered a Jig and we'll see what happens.
Sorry man. That really sucks.
El26 kernel with cwm it is then.. 100% of the time.
Sent from my SPH-D710 using xda app-developers app
Are you sure that kernel was flashed? Did you see that it was agat recovery? Did you wipe? How did you wipe? What gapps did you flash? Are you sure you're actually hard bricked (not just soft)? These are just some questions I have that are useful...
Anyways, sorry to hear if you are legitimately bricked.
Sent from my SPH-D710 using Tapatalk
Click here for custom mods for your E4GT
Thanks for the warning.
Pp.
Sent from my ginger infused Mayan calculator.
sniper said:
Are you sure that kernel was flashed? Did you see that it was agat recovery? Did you wipe? How did you wipe? What gapps did you flash? Are you sure you're actually hard bricked (not just soft)? These are just some questions I have that are useful...
Anyways, sorry to hear if you are legitimately bricked.
Sent from my SPH-D710 using Tapatalk
Click here for custom mods for your E4GT
Click to expand...
Click to collapse
I odin'd to Agat source 0.5.4, rebooted.
Flashed Calk's format all script to do the wiping (did not even do factory reset)
Flashed aokp 3.1 unofficial
flashed gapps-jb-20120726
rebooted to blue led
edit
yes I saw it was agat recovery; I was running FI25 stock kernel before that (pure stock, no repack) so there's no question as to kernel version.
I still have my odin window open and have verified the file i flashed
sniper said:
Are you sure that kernel was flashed? Did you see that it was agat recovery? Did you wipe? How did you wipe? What gapps did you flash? Are you sure you're actually hard bricked (not just soft)? These are just some questions I have that are useful...
Anyways, sorry to hear if you are legitimately bricked.
Sent from my SPH-D710 using Tapatalk
Click here for custom mods for your E4GT
Click to expand...
Click to collapse
Agat's FH13 kernel isn't safe. It doesn't have the MMC_CAP_ERASE command removed.
Dude it happens ..i got screwed on that miui build that got locked ..my fault or not ..bottom line that sh*t sucks
Sent from my SPH-D710 using xda app-developers app
times_infinity said:
Agat's FH13 kernel isn't safe. It doesn't have the MMC_CAP_ERASE command removed.
Click to expand...
Click to collapse
That wouldnt matter if it were only used to install. Erase Cap is just that, an ERASE cap. To my knowledge it absolutely cannot be triggered by an install, although ot may have been present yet dormant. It sounds to me like mis-partitioning. just my $0.02..
Either way, if you cam get the power cycled you MAY be able to boot into DL mode and then after that huge IF you could find somebody who could help you set up a couple tests to find the damage and then partition around it. You may lose a gb or two but its better than Asurion getting more of our money..
This is the reason why I play it safe and keep a copy of el26 kernel zip.and tar on my sd card so when it comes to times like this doing a wiping data/factory reset. I know theres safe kernels out there but I only use them when im just wiping cache and dalvik only but when it comes down to doing a data/factory reset my safest kernel is el26.
Sent from my SPH-D710 using xda premium
PhAkEer said:
That wouldnt matter if it were only used to install. Erase Cap is just that, an ERASE cap. To my knowledge it absolutely cannot be triggered by an install, although ot may have been present yet dormant. It sounds to me like mis-partitioning. just my $0.02..
Either way, if you cam get the power cycled you MAY be able to boot into DL mode and then after that huge IF you could find somebody who could help you set up a couple tests to find the damage and then partition around it. You may lose a gb or two but its better than Asurion getting more of our money..
Click to expand...
Click to collapse
He used calk's format all. The script calls a format of the partition just like hitting factory reset in recovery. Which calls MMC_CAP_ERASE. That's what caused the brick.
Sent from my SCH-I500 using xda app-developers app
vanberge said:
So I just went from running pure stock rooted FI25, flashed agat's 0.5.4 source built kernel via odin, then rebooted into that custom recovery and flashed AOKP 3.1, flashed JB Gapps, and rebooted to blue LED.
We all run the risk I guess; just frustrating to see it happen on a process I've done literally hundreds of times.
Ordered a Jig and we'll see what happens.
Click to expand...
Click to collapse
Agat's kernals are for TW based roms only
bigdaddy619 said:
Agat's kernals are for TW based roms only
Click to expand...
Click to collapse
He flashed it for the included recovery.
Sent from my SCH-I500 using xda app-developers app
Below is a copy of the post I made in my kernel thread:
I don't think it's kernel related.
Guys I'm not saying I'm perfect nor I'm trying to defend myself.
my v0.5.4 has been downloaded:
tar format 569 times
zip format 587 times.
This totaling over 1100 times.
If kernel/recovery wouldn't be safe we would of have more of this problem.
More bricks.
I think there's something went wrong.
I can't say what and I can't say why. But knowing that the kernel has been used so many times without any hick ups or problems
makes me think there should be something not kernel related.
I really feel sorry for the brick and I hate the fact that it happened wile using my kernel.
I'll gladly fix any problem and/or brick cause.
Just checked source on my laptop.
CAP_ERASE command is not there.
Unless something went terribly wrong and it came back somehow it should not be there.
End of quote.
I might be wrong. I need any input I can get.
Please let me know if you thing there something wrong in my logic.
I wanna help and I wanna fix any possible problem but it looks like I can't do it alone.
Chip in guys and help me make our experience as safe as possible.
Thanks in advance for any input/idea/thought.
times_infinity said:
He used calk's format all. The script calls a format of the partition just like hitting factory reset in recovery. Which calls MMC_CAP_ERASE. That's what caused the brick.
Sent from my SCH-I500 using xda app-developers app
Click to expand...
Click to collapse
I've used calks format all multiple times on unsafe recoveries before I knew about the brick bug and my phone was fine. I remember reading a lot of people used calks script and their phone didn't brick...
Sent from my SPH-D710 using Tapatalk 2
It could be the same reason why chris41g's AOSP kernels were vulnerable to the brick bug for a short while. You may want to reach out to him to see if he's able to provide some advice as to why it happened. Also, entropy is one of the most knowledgeable people on the brick bug, so you may want to reach out to him as well.
OP - I'm sorry you bricked man. This is the reason that even with all of these "safe" recoveries, I still do all of my flashing from stock EL26. It's tried and true and it only takes an extra 30 seconds at the most to flash using Mobile Odin.
Sent from my SPH-D710 using Tapatalk 2
Dchibro said:
It could be the same reason why chris41g's AOSP kernels were vulnerable to the brick bug for a short while. You may want to reach out to him to see if he's able to provide some advice as to why it happened. Also, entropy is one of the most knowledgeable people on the brick bug, so you may want to reach out to him as well.
OP - I'm sorry you bricked man. This is the reason that even with all of these "safe" recoveries, I still do all of my flashing from stock EL26. It's tried and true and it only takes an extra 30 seconds at the most to flash using Mobile Odin.
Sent from my SPH-D710 using Tapatalk 2
Click to expand...
Click to collapse
Yep. Seeing this thread is enough reason for me to keep using that method as well.
Sent from my SPH-D710 using xda premium
Dchibro said:
It could be the same reason why chris41g's AOSP kernels were vulnerable to the brick bug for a short while. You may want to reach out to him to see if he's able to provide some advice as to why it happened. Also, entropy is one of the most knowledgeable people on the brick bug, so you may want to reach out to him as well.
OP - I'm sorry you bricked man. This is the reason that even with all of these "safe" recoveries, I still do all of my flashing from stock EL26. It's tried and true and it only takes an extra 30 seconds at the most to flash using Mobile Odin.
Sent from my SPH-D710 using Tapatalk 2
Click to expand...
Click to collapse
This is the first Ive heard of an Ecap on an Agat.. That being said,
Its something we are all always at risk (SLIGHTLY) because the negative effects of EraseCap a built into the phone. ICS software just so happens send a command that makes it more likely to be triggered...
El26 is only and can only be as safe as an ics source built kernel IF the source kernel has the Ecap hair trigger removed.
Sent from my SPH-D710 using Tapatalk 2
PhAkEer said:
El26 is only and can only be as safe as an ics source built kernel IF the source kernel has the Ecap hair trigger removed.
Sent from my SPH-D710 using Tapatalk 2
Click to expand...
Click to collapse
And therein lies the rub. The only way to know it's truly safe is to dig into the code and actually know what to look for. Most people, myself included, either don't or don't want to take the time. Also, things change, kernel bases change, and since we're all human, mistakes can get made. There's no mistake that can be made when flashing from a GB based kernel.
I certainly wouldn't mind the days when I could use my current recovery for anything I wanted to do, but for me, those days are over on this phone. The alternative is barely an inconvenience anyways.
Sent from my SPH-D710 using Tapatalk 2
Dchibro said:
And therein lies the rub. The only way to know it's truly safe is to dig into the code and actually know what to look for. Most people, myself included, either don't or don't want to take the time. Also, things change, kernel bases change, and since we're all human, mistakes can get made. There's no mistake that can be made when flashing from a GB based kernel.
I certainly wouldn't mind the days when I could use my current recovery for anything I wanted to do, but for me, those days are over on this phone. The alternative is barely an inconvenience anyways.
Sent from my SPH-D710 using Tapatalk 2
Click to expand...
Click to collapse
I dont think your quite hearing me....
the damage is done by mmc firmware that is on a level too deep for us to alter. It has been in every single epic touch since it was a wee little memory card on a little moving belt with the others...
Fy,gb,ics,jb has nothing to do do with it. If it were an Android issue it wouldve been fixed immediately and if it were a simple removal of a single line Samsung wouldve dealt with it just based on XDA forum knowledge...
It is embedded in your device.
As said, ICS just had an aspect that made it considerably more likely
Dchibro said:
And therein lies the rub. The only way to know it's truly safe is to dig into the code and actually know what to look for. Most people, myself included, either don't or don't want to take the time. Also, things change, kernel bases change, and since we're all human, mistakes can get made. There's no mistake that can be made when flashing from a GB based kernel.
I certainly wouldn't mind the days when I could use my current recovery for anything I wanted to do, but for me, those days are over on this phone. The alternative is barely an inconvenience anyways.
Sent from my SPH-D710 using Tapatalk 2
Click to expand...
Click to collapse
PhAkEer said:
I dont think your quite hearing me....
the damage is done by mmc firmware that is on a level too deep for us to alter. It has been in every single epic touch since it was a wee little memory card on a little moving belt with the others...
Fy,gb,ics,jb has nothing to do do with it. If it were an Android issue it wouldve been fixed immediately and if it were a simple removal of a single line Samsung wouldve dealt with it just based on XDA forum knowledge...
It is embedded in your device.
As said, ICS just had an aspect that made it considerably more likely
Click to expand...
Click to collapse
the only way to keep the bug from being triggered is to remove the function that causes it in the mmc driver source.
Hey guys,
I purchased this phone today, went home and immediately rooted the phone.
Everything went fine, until I tried flashing a custom recovery than the problem occurred,
I'm on a FL24 basebad with 4.0.4, and every time my phone boots 10 seconds later it restarts.
What's going on?
I rooted the phone with Odin, once rooted I installed mobile Odin and flashed a customer "Kernel / Recovery" now the phone constantly reboots.
Install the stock kernel.
Sent from my SPH-D710 using xda premium
Well the kernel I flashed was 0.4.0, I heard that one has reboot issues so I flashed 0.3.0 and it's working great.
The only thing I can't figure out now is how to flash CWM, keeps taking me to the download screen when booting into "recovery".
Trytohaxme said:
Well the kernel I flashed was 0.4.0, I heard that one has reboot issues so I flashed 0.3.0 and it's working great.
The only thing I can't figure out now is how to flash CWM, keeps taking me to the download screen when booting into "recovery".
Click to expand...
Click to collapse
To boot to recovery
Vol up plus power and hold
Once the splash screen shows, release power and continue to hold Vol up.
You will get to recovery.
Sent from my SPH-D710 using xda premium
I must not have been holding it long enough, appreciate the reply.
How come E4GT ROMS are so large in size, back when I had an EVO and Optimus roms were about 100MB, E4GT are about 500mb?
Well sounds like the recovery was either flashed wrong or is defective for whatever reason..
Here is how to root that version by qb77king. He is very good http://www.youtube.com/watch?v=gqmKN2ewatk&feature=youtube_gdata_player.....
here is a video for the recovery http://www.youtube.com/watch?v=Kb63ldWtnoM&feature=youtube_gdata_player
So I'd like to help but need to know more info to go by. Did you enable USB debugging when you flashed the recovery? Anyways go ahead and go to stockroms.net. there you can find a stock ROM to flash your phone with unless its virgin or boost.
I recommend just getting stock jellybean or wild for the night cyanogen.. I know you just bought it but I can tell you its worth it ICS is horrible,Too many problems. You can actually find a jellybean ROM that is already rooted when u flash it.. Anyways download the android root toolkit from the market... This will save your phone's root
Sent from my SPH-D710 using xda premium
rockingfreely said:
Well sounds like the recovery was either flashed wrong or is defective for whatever reason..
Here is how to root that version by qb77king. He is very good http://www.youtube.com/watch?v=gqmKN2ewatk&feature=youtube_gdata_player.....
here is a video for the recovery http://www.youtube.com/watch?v=Kb63ldWtnoM&feature=youtube_gdata_player
So I'd like to help but need to know more info to go by. Did you enable USB debugging when you flashed the recovery? Anyways go ahead and go to stockroms.net. there you can find a stock ROM to flash your phone with unless its virgin or boost.
I recommend just getting stock jellybean or wild for the night cyanogen.. I know you just bought it but I can tell you its worth it ICS is horrible,Too many problems. You can actually find a jellybean ROM that is already rooted when u flash it.. Anyways download the android root toolkit from the market... This will save your phone's root
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
No. Already fixed.
Don't listen to this guy.
Sent from my SPH-D710 using xda premium
Hey Trytohoaxme. So as of right now there is no cmw for ICS. There is Agat recovery which is based off of cwm that is for either a ICS ROM or jelly bean ROM. I have cmw that is a jingerbread kernal that interfaces with CyanogenMod 10.1 which has 4.2.2 jellybean. If you flash clockworkmod it won't work with a stock rom your phone won't be able to boost up..
Graydiggy u are pretty rude. I hope to god your mom raised you better. Show some respect on this forum, XDA is a place for positive feedback, not negative people who criticize others who which are naive and conceited.
Sent from my SPH-D710 using xda premium
rockingfreely said:
Graydiggy u are pretty rude. ...criticize others who which are naive and conceited.
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
Who's conceited?
I'm pretty sure he's just trying to help and avoid misinformation, no need to get offended, bud... And the op stated the issue was already resolved.
He never asked about cwm specifically, just a custom recovery. On TW ICS I've used Agat's, Ruj's, and Slesh's kernels/recoveries without issue. There's really no need for EL26/CWM tar unless you want to play it safe (which i do) going from TW to AOSP or vise versa.
And yes stock TW ROMs are huge. AOSP ROMs end up around 240 megs (give or take) including Gapps.
Trolling from my Cricket-flashed Galaxy S2 E4GT using Tapatalk 2
rockingfreely said:
Hey Trytohoaxme. So as of right now there is no cmw for ICS. There is Agat recovery which is based off of cwm that is for either a ICS ROM or jelly bean ROM. I have cmw that is a jingerbread kernal that interfaces with CyanogenMod 10.1 which has 4.2.2 jellybean. If you flash clockworkmod it won't work with a stock rom your phone won't be able to boost up..
Graydiggy u are pretty rude. I hope to god your mom raised you better. Show some respect on this forum, XDA is a place for positive feedback, not negative people who criticize others who which are naive and conceited.
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
Well when people like you give incorrect information like you are currently doing, or makes everything more complicated than it should be, again, something you are doing, I will be rude. ICS has had source for a very very long time and has had a CWM for a long time. JB does not. I have been here for a long time and there is a reason I have recognized contributor. I may be rude, but when someone else risks someone's expensive phone, sometimes it takes being rude. If you can't handle it, oh well.
The reason for my response was because the issue was solved and the stockroms.net is not a site that I trust. We have a repository for all of our stock ROMs.
Sent from my SPH-D710 using xda premium
I already upgraded from ICS FL24 to JB GB27.
The problem I have as of now is, I don't know which roms are compatible with my device?
I'm on JB 4.1.2 GB27, does that mean I can only flash GB27 roms?
Trytohaxme said:
I already upgraded from ICS FL24 to JB GB27.
The problem I have as of now is, I don't know which roms are compatible with my device?
I'm on JB 4.1.2 GB27, does that mean I can only flash GB27 roms?
Click to expand...
Click to collapse
You can flash any ROM for the E4GT... You are in the right forums for that.
Oh okay, I was asking because the thread title of most ROMs say "[ROM] FL24 Kuban Kernal" ETC..
Since I'm on GB24, I can still use EL26 ROMs and all?
Trytohaxme said:
Oh okay, I was asking because the thread title of most ROMs say "[ROM] FL24 Kuban Kernal" ETC..
Since I'm on GB24, I can still use EL26 ROMs and all?
Click to expand...
Click to collapse
Just read the instructions for each ROM. They will tell you exactly what is needed.
Sent from my SPH-D710 using xda app-developers app