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.
Related
Just curious as to why we shouldn't flash ics roms when using ics recovery. I follow the devs advice when it comes to this. I always odin back to gb before flashing any new roms but i have flashed the same ics rom over with ics recovery just to see what would happen and everything went fine. So my qeuston is why? Whats broken with ics recovery that makes it unsafe? Just asking thanks
There is some interaction between custom recovery and the ICS kernel that has been damaging the emmc memory (/data partition)
If you want to read about it try this thread:
http://forum.xda-developers.com/showthread.php?t=1504808
sfhub said:
There is some interaction between custom recovery and the ICS kernel that has been damaging the emmc memory (/data partition)
If you want to read about it try this thread:
http://forum.xda-developers.com/showthread.php?t=1504808
Click to expand...
Click to collapse
thanks for your quick respons
UNfortunately, this is news to me as I have been so busy the last couple months that when I do come to these boards I download a rom and leave and never noticed the disclaimer until last night
I read through that entire thread and, while my phone is still working fine at the moment, is there any way to scan for corrupt partitions? Or are there any early warning signs? All the problems I read were unable to boot, is it possible to do damage but still be able to boot?
I've flashed roms/kernels/modems about 15 times through an ics recovery
Your lucky.
from what i know your good going from gb to ics ...its when going from ics back to gb or going between different ics roms ...cause i havent had a problem flashing updates through ics recovery for specific roms...if that makes any sense to you guys...i have yet to have any problems cause i try to play it safe...for ex. i am curently runing calks fd02 rom and last night i went into recovery and wiped everything cache,sys,and data ..and flashed the rom iver again everything went fine but im assuming its because the partitions are already there...
Yeah i have flashed many ics roms using ics recovery. Even restored back to gb from them. Only time I've used gb recovery was to do anything aosp or aokp. Other that ics recovery.never an issue.
Sent from my SPH-D710 using Tapatalk 2 Beta-5
r we referring to ics recovery from a stock kernel? the one that shows the droid in the background?
or are we also referring to rogue ics recovery?
papajetta said:
r we referring to ics recovery from a stock kernel? the one that shows the droid in the background?
or are we also referring to rogue ics recovery?
Click to expand...
Click to collapse
rogue
There is some interaction between custom recovery and the ICS kernel that has been damaging the emmc memory (/data partition)
If you want to read about it try this thread:
http://forum.xda-developers.com/show....php?t=1504808
Click to expand...
Click to collapse
Any idea on how long it'll take to fix this?
All depends on when source code for ics on our phone is released, so once the final build is achieved.
Sent from my SPH-D710 using XDA
schwab002 said:
Any idea on how long it'll take to fix this?
Click to expand...
Click to collapse
if you had read the thread, you would know there is no fix for it.
graffix31 said:
Yeah i have flashed many ics roms using ics recovery. Even restored back to gb from them. Only time I've used gb recovery was to do anything aosp or aokp. Other that ics recovery.never an issue.
Sent from my SPH-D710 using Tapatalk 2 Beta-5
Click to expand...
Click to collapse
It's usually wiping data or cache that kills it.
i think some people may be confused.
this does not mean you cannot use ICS kernel's.. it simply means you cannot wipe partitions while in recovery WHILE ALSO being on an ICS kernel.
the workaround? odin/mobile odin the el26 or el29 kernel/recovery combos if you wanna flash a new rom or wipe a partition.
if you flashed something while on an ICS kernel and are worried something may be wrong with your phone.. no need to worry... if your phone works.. then nothing happened. but from now on.. if you are on an ICS rom(ics tw or cm9).. odin to a GB kernel before reflashing/wiping.
---------- Post added at 04:49 PM ---------- Previous post was at 04:48 PM ----------
autoprime said:
i think some people may be confused.
this does not mean you cannot use ICS kernel's.. it simply means you cannot wipe partitions while in recovery WHILE ALSO being on an ICS kernel.
the workaround? odin/mobile odin the el26 or el29 kernel/recovery combos if you wanna flash a new rom or wipe a partition.
if you flashed something while on an ICS kernel and are worried something may be wrong with your phone.. no need to worry... if your phone works.. then nothing happened. but from now on.. if you are on an ICS rom(ics tw or cm9).. odin to a GB kernel before reflashing/wiping.
Click to expand...
Click to collapse
also..
sergioperalta81 said:
rogue
Click to expand...
Click to collapse
rogue is not the issue here.
The source for the kernel will show devs how to safely interact with the phones partitions, as of right now its comparable to a 25000 piece puzzle...but you don't have a picture to reference, its gonna take a long time and a lot of mistakes to figure it out (reverse engineering, bricks, etc...), so its better just to wait for the reference picture (kernel source) since we know it will come (eventually).
Sent from my SPH-D710 using Tapatalk 2
rianbechtold said:
UNfortunately, this is news to me as I have been so busy the last couple months that when I do come to these boards I download a rom and leave and never noticed the disclaimer until last night
I read through that entire thread and, while my phone is still working fine at the moment, is there any way to scan for corrupt partitions? Or are there any early warning signs? All the problems I read were unable to boot, is it possible to do damage but still be able to boot?
I've flashed roms/kernels/modems about 15 times through an ics recovery
Click to expand...
Click to collapse
I'd question how lucky you are. I did the same thing and the next time I restarted my phone... Brick. Luckily, if it does happen and you take it to a Sprint store, they'll ask to check it out for an hour to see if there's any physical/water damage. When they see there's none, they'll replace it for 35 dollars.
Hopefully your just ok though. I'd save all you're media as I lost mine.
Sent from my SPH-D710 using Tapatalk
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'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
Could somebody please explain why flashing a ROM (AOKP) on this kernel/recovery would brick my phone? I'm not blaming anyone but myself, but I just really don't want to go through it again. My problem is I thought being on Agats kernel I would be safe. But obviously I was wrong. Yes I know, FAIL. At least I got some good years in before popping my brick cherry. :laugh:
http://forum.xda-developers.com/showthread.php?t=1879381
jtadak said:
Could somebody please explain why flashing a ROM on this kernal/recovery would brick my phone? I'm not blaming anyone but myself, but I just really don't want to go through it again. My problem is I thought being on Agats kernel I would be safe. But obviously I was wrong. Yes I know, FAIL. At least I got some good years in before popping my brick cherry. :laugh:
http://forum.xda-developers.com/showthread.php?t=1879381
Click to expand...
Click to collapse
Well, All flashing involves risk. I have flashed many times from that kernel/recovery. What were you flashing? (ROM / KERNEL) did it have the update script binary call for eMMC_format_all comand? Sorry to hear that you bricked.
g_ding84 said:
Well, All flashing involves risk. I have flashed many times from that kernel/recovery. What were you flashing? (ROM / KERNEL) did it have the update script binary call for eMMC_format_all comand? Sorry to hear that you bricked.
Click to expand...
Click to collapse
I know it's risky, but I mean not like that. Followed instuctions and flashed per instructions like always. I was flashing AOKP. But would it matter what I was flashing, or where I'm flashing from? I do not know if it had any updates. I guess I had hoped if it was unsafe, or "risky" it would have been in the OP. I'm just trying to figure out what the heck I'm missing here. Thanks, I'll be getting a new one $35 so it's not horrible.
jtadak said:
I know it's risky, but I mean not like that. Followed instuctions and flashed per instructions like always. I was flashing AOKP. But would it matter what I was flashing, or where I'm flashing from? I do not know if it had any updates. I guess I had hoped if it was unsafe, or "risky" it would have been in the OP. I'm just trying to figure out what the heck I'm missing here. Thanks, I'll be getting a new one $35 so it's not horrible.
Click to expand...
Click to collapse
Your not the first person that has bricked from that combo. I have never had any issues with agats or any other "safe" kernel. Vanberge had the same issue.
link: http://forum.xda-developers.com/showthread.php?t=1912529&highlight=brick
g_ding84 said:
Your not the first person that has bricked from that combo. I have never had any issues with agats or any other "safe" kernel. Vanberge had the same issue.
link: http://forum.xda-developers.com/showthread.php?t=1912529&highlight=brick
Click to expand...
Click to collapse
Thanks. Wow, I sure wish I came accross that sooner. Haha, oh well. It's how it goes. I just read that whole thread and posted my brick as well to maybe help develop some more awareness. It's el29 from here on out no matter what. Sheesh.
jtadak said:
Thanks. Wow, I sure wish I came accross that sooner. Haha, oh well. It's how it goes. I just read that whole thread and posted my brick as well to maybe help develop some more awareness. It's el29 from here on out no matter what. Sheesh.
Click to expand...
Click to collapse
Thats what I do, unless it TW ICS to TW ICS.
Sent from my SPH-D710 using XDA
So you don't want to EL29 when flashing from TW ICS to TW ICS? Haven't heard that one...
jtadak said:
So you don't want to EL29 when flashing from TW ICS to TW ICS? Haven't heard that one...
Click to expand...
Click to collapse
Can you guys send me a link to the AOKP build you tried? Think we may want to ask someone to test update-binary and see if the problem lies in there.
garwynn said:
Can you guys send me a link to the AOKP build you tried? Think we may want to ask someone to test update-binary and see if the problem lies in there.
Click to expand...
Click to collapse
I believe it is this one. http://forum.xda-developers.com/showthread.php?t=1881046
Sent from my SPH-D710 using xda app-developers app
jtadak said:
So you don't want to EL29 when flashing from TW ICS to TW ICS? Haven't heard that one...
Click to expand...
Click to collapse
The main thing is do what your comfortable with. You can do either of them. But i keep a copy of el29 direct boot kernel on my sd card.
Sent from my SPH-D710 using XDA
BluesRulez said:
I believe it is this one. http://forum.xda-developers.com/showthread.php?t=1881046
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
That's the one...
g_ding84 said:
The main thing is do what your comfortable with. You can do either of them. But i keep a copy of el29 direct boot kernel on my sd card.
Sent from my SPH-D710 using XDA
Click to expand...
Click to collapse
Yes, so do I. I just didn't here :laugh: So you use CWM to flash TW ICS to TW ICS?
I use the el26 kernel or I use chris41g's twrp kernelor even his cwm kernel. They will overwrite the updater binaries using its own. However some zips will not like it and abort. Its safe as hell though. El26 is the first choice though
sent from my BAD A$$ Epic touch
Well went down to Sprint. $35 and getting a new phone Friday most likely. Could be worse I guess.
I'm having some issues with my phone rebooting or powering off frequently, especially when I plug it into a charger. I don't think I have the power button issue. I suspect it is the battery (although the battery was replaced Oct 2012 at the sprint store) and have another on the way. I want to exhaust every possible option in testing, so I want to take my phone to off the shelf stock. I currently am running rooted sprint JB, and I am looking for a way to remove all user files on internal storage as well as the tweaks (have comadose installed and had kobridge before) just to make sure it is not from a bad flash. I know how to go back to stock unrooted GB27 with Nodata via ODIN, however I want to make sure ALL tweaks and user files are removed too. Ideas?
chaosbuzz said:
I'm having some issues with my phone rebooting or powering off frequently, especially when I plug it into a charger. I don't think I have the power button issue. I suspect it is the battery (although the battery was replaced Oct 2012 at the sprint store) and have another on the way. I want to exhaust every possible option in testing, so I want to take my phone to off the shelf stock. I currently am running rooted sprint JB, and I am looking for a way to remove all user files on internal storage as well as the tweaks (have comadose installed and had kobridge before) just to make sure it is not from a bad flash. I know how to go back to stock unrooted GB27 with Nodata via ODIN, however I want to make sure ALL tweaks and user files are removed too. Ideas?
Click to expand...
Click to collapse
The only thing I can say is if you have a CWM recovery installed boot into it and wipe all storage areas with that, then use the ODIN one-click RESTORE version (not NODATA as RESTORE will wipe all user data from the phone). That's about the best I can do for you. I just did it the other day to my phone and it wiped literally everything from the device, including the custom boot-screen.
http://forum.xda-developers.com/showthread.php?t=2191954
A slip of the tongue, I meant restore, not nodata. I can mobileodin el29 directboot. What should I do in CWM to ensure all internal storage, system data, and tweaks is completely wiped? I usually use JB format all x2 but that doesn't delete pictures etc, so I am assuming it's leaving possible conflicts from flashing roms
OK, I flashed el29 directboot to CWM, formatted EVERYTHING I had an option to in CWM, did a restore to stock unrooted but it still knew my wifi password when the phone powered on which makes me think not all the data had been reset...
Try stock recovery do a "factory reset"after that it should ask you for wifi password.
Pp.
Sent from a jelly bean shooting Epic. In your eye ....... phone.
chaosbuzz said:
A slip of the tongue, I meant restore, not nodata. I can mobileodin el29 directboot. What should I do in CWM to ensure all internal storage, system data, and tweaks is completely wiped? I usually use JB format all x2 but that doesn't delete pictures etc, so I am assuming it's leaving possible conflicts from flashing roms
Click to expand...
Click to collapse
If you are rooted, use Mobile Odin Lite to flash a stock EL29 KERNEL (.tar). - I would highly suggest this particular way as it's how I do it and I've never had any issues doing it with Mobile Odin Lite. Mobile Odin Lite
If you're going to use CWM to flash the stock EL29 KERNEL, use the .zip version.
You could also always try the One-Click EL29 KERNEL, but I've never used a One-Click before so I can't help you on that process but I'd imagine it's the same as flashing the ROM with a One-Click.
http://www.rwilco12.com/downloads.p...int) (SPH-D710)/Kernels/Stock (TW) Kernels/GB
After that just do a factory reset through the stock recovery. You should be all set after that.
SOURCE for KERNELS - Thanks rwilco12. *tips hat*
SOURCE for Mobile Odin Lite - Thanks Chainfire *tips hat*
Kherr said:
If you are rooted, use Mobile Odin Lite to flash a stock EL29 KERNEL (.tar). - I would highly suggest this particular way as it's how I do it and I've never had any issues doing it with Mobile Odin Lite. Mobile Odin Lite
If you're going to use CWM to flash the stock EL29 KERNEL, use the .zip version.
You could also always try the One-Click EL29 KERNEL, but I've never used a One-Click before so I can't help you on that process but I'd imagine it's the same as flashing the ROM with a One-Click.
http://www.rwilco12.com/downloads.p...int) (SPH-D710)/Kernels/Stock (TW) Kernels/GB
After that just do a factory reset through the stock recovery. You should be all set after that.
SOURCE for KERNELS - Thanks rwilco12. *tips hat*
SOURCE for Mobile Odin Lite - Thanks Chainfire *tips hat*
Click to expand...
Click to collapse
I used mobile odin lite to flash EL29 directboot kernel. This allows the use of CWM after flashing the kernel. Once in CWM I formatted everything I could in CWM and formatted cache and dalvik. From there, I used a one click desktop ODIN to flash stock sprint unrooted. IAfter all this, I am still having issues with constant restarts. I replaced the battery and am still having the problem. I am unsure if this is software or I have a power button issue. Does anyone have any tips I can try?
chaosbuzz said:
I used mobile odin lite to flash EL29 directboot kernel. This allows the use of CWM after flashing the kernel. Once in CWM I formatted everything I could in CWM and formatted cache and dalvik. From there, I used a one click desktop ODIN to flash stock sprint unrooted. IAfter all this, I am still having issues with constant restarts. I replaced the battery and am still having the problem. I am unsure if this is software or I have a power button issue. Does anyone have any tips I can try?
Click to expand...
Click to collapse
Well, then I'd probably say it's a power button issue, but I've also heard of moisture in the charger port (not necessarily liquid damage, could just be moisture in the air) might cause random bootloops as well. Could be a number of things, but you've stamped out your issue from being software related (as far as I can see). Sorry I couldn't be of more help to you.
Depending on what stock ROM you want there's a one click you run through odin that's wipes the internal memory as well
Sent from my SPH-D710 using xda app-developers app
Oh man... This is bad. You don't have to do all that confusing stuff!
Here is the link for the stock FL24 build for E4GT D710:
http://www.sxtpdevelopers.com/showthread.php?t=116
Download that file, run it, put phone into recovery, plug phone into computer and press start once "COM" shows up on the one-click...the usual. When I use this, once the phone boots up I always just go into settings-->privacy-->restore phone and check format USB (that is if you want everything deleted off your SD card). I back everything up to my 64GB removable sd card before I do this.
Hope I helped!
Sent from my SPH-D710 using xda app-developers app
smsnodgrass said:
Oh man... This is bad. You don't have to do all that confusing stuff!
Here is the link for the stock FL24 build for E4GT D710:
http://www.sxtpdevelopers.com/showthread.php?t=116
Download that file, run it, put phone into recovery, plug phone into computer and press start once "COM" shows up on the one-click...the usual. When I use this, once the phone boots up I always just go into settings-->privacy-->restore phone and check format USB (that is if you want everything deleted off your SD card). I back everything up to my 64GB removable sd card before I do this.
Hope I helped!
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
Just curious, but any particular reason why flashing to stock ICS may be better than stock JB in this case?
Thanks.
chaosbuzz said:
Just curious, but any particular reason why flashing to stock ICS may be better than stock JB in this case?
Thanks.
Click to expand...
Click to collapse
It's not. I don't think he realizes that JB has gone official.
Sent from my SPH-D710 using xda premium
chaosbuzz said:
Just curious, but any particular reason why flashing to stock ICS may be better than stock JB in this case?
Thanks.
Click to expand...
Click to collapse
graydiggy said:
It's not. I don't think he realizes that JB has gone official.
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
I go back to ICS because, at least in my area, 4.1.2 JB has not gone OTA which, imo, you can't go wrong with it. It's stable and it's just what I do. I'll eventually switch to a stock JB build for a one-click restore, just not yet. I'm not living under a shell I know JB has gone official.
smsnodgrass said:
I go back to ICS because, at least in my area, 4.1.2 JB has not gone OTA which, imo, you can't go wrong with it. It's stable and it's just what I do. I'll eventually switch to a stock JB build for a one-click restore, just not yet. I'm not living under a shell I know JB has gone official.
Click to expand...
Click to collapse
JB is not an area specific thing... You can only officially get it over the wire from Samsung's site or by using kies. They will not do it over the air. So no matter where you are in the world, JB is official for all three variants of the E4GT.
ICS is the worst thing to hit the E4GT and is not stable. You obviously do live under a shell if you think it is. IMO, CM10.1 is more stable.
So, let's try not to make poor excuses with completely wrong information when posting next time.
Sent from my SPH-D710 using xda premium
graydiggy said:
JB is not an area specific thing... You can only officially get it over the wire from Samsung's site or by using kies. They will not do it over the air. So no matter where you are in the world, JB is official for all three variants of the E4GT.
ICS is the worst thing to hit the E4GT and is not stable. You obviously do live under a shell if you think it is. IMO, CM10.1 is more stable.
So, let's try not to make poor excuses with completely wrong information when posting next time.
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
Hahaha woah there dood...let's not get offensive, no need to be so harsh! If I've learned anything from Miley Cirus it's that
1) never let your weed-eater cut your hair and...
2)Everybody makes mistakes :good: :good:
Jesus man, sorry I haven't devoted my life to learning everything there is to know about cell phones just so I can take people down and attack them on online forums. Although, if that's all you can do to boost your self-esteem, then go for it. make me feel stupid! I am living under a shell. I make poor excuses. I am an idiot. I know nothing about anything. I should probably rethink my life.
Thank you, Mr. "Graydiggy" for this eye-opening experience
Rough night for me. My bad. All I am saying is that you should take more time to read. A little bit of bad advice could render someone's phone unusable. Even though your advice was decent, you could have possibly left someone in the dark when it comes to a much better version to use.
Like you said, mistakes are made, but some mistakes can cost hundreds of dollars. Its better to know what you are talking about and if you aren't sure, search for the answer.
Sent from my SPH-D710 using xda premium
graydiggy said:
ICS is the worst thing to hit the E4GT and is not stable. You obviously do live under a shell if you think it is. IMO, CM10.1 is more stable.
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
Gee, grey didn't know you felt that way about ics.?
And people kept telling me I was crazy!
Pp. :beer::thumbup:
From my Epic Touch full of Xparent Blue Tapatalk 2.
graydiggy said:
Rough night for me. My bad. All I am saying is that you should take more time to read. A little bit of bad advice could render someone's phone unusable. Even though your advice was decent, you could have possibly left someone in the dark when it comes to a much better version to use.
Like you said, mistakes are made, but some mistakes can cost hundreds of dollars. Its better to know what you are talking about and if you aren't sure, search for the answer.
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
Yeah I gotchu maynee..no worries, I was just kinda posting what I do and I still don't really think running a ics one-click versus a 4.1.2 one-click is a hundred(s) dollar midtake. For some reason though I hadn't even thought about downloading a 4.1.2 one-click. probably a lot easier and hassle free?
Its not that it is a costly mistake, but it can be quite troublesome. I was saying that one should know every detail of something before posting. I have seen many a brick happen do to someone saying to do one thing that was completely wrong. So even if it has no potential of bricking you, take into account that it could just be wrong.
GB27 Is the best in terms of stock ROMs. People that say otherwise either don't know what they are talking about or it's horrible user error and misinformation.
Sent from my SPH-D710 using xda premium