Related
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.
Title says all, can I flash it threw CWM also
Sent from my SPH-D710 using XDA
You could, you would not want to. Your phone would likely not boot as an ICS install with a GB kernel won't.
Since there is no proper ICS CWM there is little reason to do such a thing. But you should still be able to get into recovery and hopefully download mode.
LeKtRiCzzz said:
Title says all, can I flash it threw CWM also
Sent from my SPH-D710 using XDA
Click to expand...
Click to collapse
Like rain said, it wont boot and theres a possiblity of a brick when flashing. So no, dont do it.
Of course not silly!
Sent from my SPH-D710 using Tapatalk 2
It won't brick, but it won't boot properly.
You can boot into Recovery though.
You can also boot into ODIN D/L mode because that is handled by the bootloader and is immune to bad kernels (which is not saying it is immune to bad flashing skills or not reading instructions)
Not flaming, this is an honest question...
Why?
Sent from my SPH-D710 using Tapatalk 2
Wizard Knight said:
Not flaming, this is an honest question...
Why?
Click to expand...
Click to collapse
ICS is a linux 3.0 kernel. GB is a linux 2.6 kernel. The most likely reason why is there are some change in sections of the kernel which affect android so it can't boot. You'd have to look at the boot log files to see exactly why.
So basically a GB ROM is looking for a 2.6 kernel and a 3.0 kernel doesn't look sufficiently similar for it to boot properly.
Actually i think his question was to the OP. Jus' Sayin!
RainMotorsports said:
Actually i think his question was to the OP. Jus' Sayin!
Click to expand...
Click to collapse
This
Sent from my SPH-D710 using Tapatalk 2
I've read through most of these threads an I'm pretty sure there is no CWM for ICS for the Epic 4G Touch. Is this correct?
I have the s2 for tmobile and it is practically unbrickable compared to this phone. My friend has the Epic and I installed ICS AOKP. It is way more difficult on his phone. I don't understand why it is so different. Given, we have different hardware, but neither one of us have the source for ICS or kernel. But I do have the same CWM no matter what rom I'm on.
1. Is it possible to have CWM on the Epic 4G Touch?
2. His ext_sdcard is not showing up. How to I make it work? I tried DirectoryBind to no avail. Maybe I'm doing something wrong.
3. Can i flash zips in ICS recovery? Ive never seen the recovery it put me in before.
4. Am I missing something?
I was under time costraints when helping him out and honestly I'm just happy i got AOKP running on his phone without any issues.
I appreciate all the work everyone has done so please don't take anything I said the wrong way.
Thanks in advance an i look firward to hearing from anyone...
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
We need ICS kernel source before we can have a proper CWM kernel for ICS.
Sent from my SPH-D710 using XDA
We had CWM on ICS for a little bit, but it was causinga ton of bricks because the partitions are handled differently in ICS. I wouldn't attempt to flash anything in ICS recovery because you risk bricking the device. We likely won't have CWM for it until kernel source drops.
If you need to flash something, the best way to do it is to Odin back to EL26, install CWM, and flash everything (ROM, kernel, modem etc.) in one recovery session. Most of the threads for AOSP ICS roms have specific flashing instructions in the first post.
Sent while hanging with that really hoopy frood Ford Prefect.
blackroseMD1 said:
We had CWM on ICS for a little bit, but it was causinga ton of bricks because the partitions are handled differently in ICS. I wouldn't attempt to flash anything in ICS recovery because you risk bricking the device. We likely won't have CWM for it until kernel source drops.
If you need to flash something, the best way to do it is to Odin back to EL26, install CWM, and flash everything (ROM, kernel, modem etc.) in one recovery session. Most of the threads for AOSP ICS roms have specific flashing instructions in the first post.
Sent while hanging with that really hoopy frood Ford Prefect.
Click to expand...
Click to collapse
Thanks for the info. I guess I'm spoiled on my T989! We dont have source either. We didnt even have a proper leak til yesterday, but ICS runs great because our devs are ridiculous.
I have him running FD26 so I will flash back el26 for the mods. I left his baseband alone and it seems to be running fine.
Thanks again. I appreciate the help
Edit: One more thing. I need to reset the flash counter and remove the yellow triangle every time i go back to cwm right?
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
You don't need to remove it, it's really just personal preference and if it makes you happy you can, lol.
Sent from my SPH-D710 using Tapatalk
Sn1per 117 said:
You don't need to remove it, it's really just personal preference and if it makes you happy you can, lol.
Sent from my SPH-D710 using Tapatalk
Click to expand...
Click to collapse
Lol! Its just so ugly. I wish there was a kernel for the Epic that had a cool bootanimation. My friend saw my. Darkside kernel boot and wants it now. He doesn't understand because he thinks our phones are identical.
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
Look here guys http://forum.xda-developers.com/showthread.php?p=25659129#post25659129
I noticed the repacked kernel might not work with AOSP though. I think that I will flash him back to GB until source is released. I don't want want him to accidentally brick.
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
xyros7 said:
I noticed the repacked kernel might not work with AOSP though. I think that I will flash him back to GB until source is released. I don't want want him to accidentally brick.
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
Click to expand...
Click to collapse
I've been mostly staying on gb roms just for stability and battery life. As long as you read the instructions and don't try to be insanely flash happy you'll be fine.
Sent from my SPH-D710 using Tapatalk
so i have made up my mind i am switching to the epic miss the big screen... and my question is what rom do i need to be on in order to activate i had some issues with activating last time on my rooted evo 4g i want to make this activation as quick and smooth as possible any responses would be greatly appreciated
Stock FC09. Or you could be on the Peoples ROM. Should be any stock touchwiz rom will allow you to switch the phone over to another line.
Sent From My Sprint Galaxy Nexus
are you sure??
Bfitz26 said:
are you sure??
Click to expand...
Click to collapse
Positive... the hands free activation is present on all touchwiz roms. But if your buying an Epic and plan on manually entering its ESN on your Line then you will need a touchwiz ROM to use the Dialer Codes they direct you to use. Its not too hard. Did it with my old epic when i got my Gnex... put my epic on another Line.
no it's my wifes phone i am swapping phones for the shift with the epic and it's already rooted with thunderbird 2.2 or something can you link me the stock rom i can just flash in cwm this forums has so much unorginization it is confusing to me..
Bfitz26 said:
no it's my wifes phone i am swapping phones for the shift with the epic and it's already rooted with thunderbird 2.2 or something can you link me the stock rom i can just flash in cwm this forums has so much unorginization it is confusing to me..
Click to expand...
Click to collapse
Unorginized????
This is literally like the cleanest Forum i've seen you want to see unorginized go to the Gnex forums. Its Thunderhawk, btw.
Here is the stock prerooted FC09 Rom that you can flash through CWM.
Stock FC09 Deodexed Prerooted
You might want to confirm wether or not your on BML or MTD.... before just flashing whatever otherwise you will brick the phone.
thanks sorry about the noob question's how can find out what i am on?
Bfitz26 said:
thanks sorry about the noob question's how can find out what i am on?
Click to expand...
Click to collapse
Should be able to tell in the about phone.. see if you can find anything that says MTD in it. Otherwise go to her applications and tell me what the full amount of space is there.. if its MTD it should be around 670mb's (both installed apps and free space) If its alot less than its BML. If on BML you can flash either.. if on MTD you can only flash MTD.
I am guessing you are on BML. I seem to remember that ROM from the Froyo days. You may want to upgrade to CWM 5.0.2.7 and flash a current ROM from development like The People's ROM (cheap plug).
Sent from my SPH-D700 using xda premium
well i don't see anything and i guess she is on random rom ei22 or something and 322 mb free when i open up manage applicatoins..
Have you made a cwm backup? If not go ahead and do it. Then go into the clockworkmod\backup folder and click on the backup to open it. If is says yaffs2 in the filenames that is MTD. If rfs or ext4 then you are on BML.
Sent from my SPH-D700 using xda premium
Bfitz26 said:
well i don't see anything and i guess she is on random rom ei22 or something and 322 mb free when i open up manage applicatoins..
Click to expand...
Click to collapse
Yeah then your on BML i would go ahead and flash the MTD one.. gives you more space.
ÜBER™ said:
Yeah then your on BML i would go ahead and flash the MTD one.. gives you more space.
Click to expand...
Click to collapse
Homestly that and speed
Sent from my SPH-D700 using xda premium
i thought the mtd one will brick you isnt' mtd and bml and ext4 just different file formates similar to fat and fat32 and so on i don't want to brick or at least go throught the trouble of odining..
Bfitz26 said:
i thought the mtd one will brick you isnt' mtd and bml and ext4 just different file formates similar to fat and fat32 and so on i don't want to brick or at least go throught the trouble of odining..
Click to expand...
Click to collapse
No like I said if you flash BML on MTD then you soft brick the phone. Then and only then but if you flash MTD over BML it will convert you to MTD.
Mtd is a partition map as well as bml. Ext4 is a file system that bml uses. However mtd uses yaffs2.
Sent from my Galaxy Nexus using xda premium
Oh ok thanks still trying to find a time when I am off work and the activation team is open
Sent from my PG06100 using Xparent ICS Blue Tapatalk 2
Bfitz26 said:
Oh ok thanks still trying to find a time when I am off work and the activation team is open
Sent from my PG06100 using Xparent ICS Blue Tapatalk 2
Click to expand...
Click to collapse
You can do it online? Sign in and hit the chat button that usually pops up next to your user name and you can chat with a rep.
Sent From My Sprint Galaxy Nexus
Oh **** nice I will have to do that
Sent from my PG06100 using Xparent ICS Blue Tapatalk 2
Bfitz26 said:
Oh **** nice I will have to do that
Sent from my PG06100 using Xparent ICS Blue Tapatalk 2
Click to expand...
Click to collapse
Yeah they will guide you on how to transfer the imei and phone number with dialer codes its pretty simple. Just be specific.
Sent From My Sprint Galaxy Nexus
Do u know there hours of operation by any chance?
Sent from my PG06100 using Xparent ICS Blue Tapatalk 2
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.