The Offical how I hard bricked my E4GT thread

Search This thread
By:
Advanced…
scarmon25

scarmon25

Senior Member
Feb 18, 2011
5,689
2,159
Knoxville, TN
Damn that sucks. More bricks. We need to start putting the word out to not flash any other build from an ICS build without Odining to stock GB first. I have been doing that and haven't had any issues so far. Hopefully that will prevent me from bricking again.
 
I

Isriam

Senior Member
Sep 12, 2006
568
120
can the OP update the first page to add mobiletechvideos.com as a place for repair? Costs 50 bucks and owner says it can be done. Ships to texas.
 
B

brennam7

Senior Member
Nov 23, 2011
285
112
Milwaukee, WI
Add me to the brick list!

Was on CM9, flashed a different version of it, tried booting, got stuck at the boot animation (for like 5 minutes) tried booting into recovery, and could no longer wipe data.

I've tried restoring to el29, fb21, pretty much everything. Always fails on the data.img.

Unless someone knows how to re-partition the /data partition, i'm eff'd! guess i should just stop flashing!
 
Epix4G

Epix4G

Senior Member
Sep 14, 2011
2,665
1,028
phoenix
I have went from ics to GB like 8 times and only had problem1 time had to wipe data to get to boot....always Odin back and then restore from there.... Los was killing me ...Even on fb21 radio and fb17 kernel cm9 time without signal was always 20 to 30 %

Sent from my SPH-D710 using xda premium
 
Dchibro

Dchibro

Senior Member
Jul 28, 2011
1,040
280
San Diego, CA
digitalcrash said:
So yes if you are on ics with any recovery you can NOT wipe data or you will brick

Sent from my SPH-D710 using XDA App
Click to expand...
Click to collapse

I don't know if it's as simple as that. I went from FB17 to FB21 by ...

1) Booting into Rogue FB17 CWM repack recovery
2) Installing Calk's wipe all ZIP
3) Installing FB21 ROM
4) Installing FB21 Modem
5) Reboot

All went fine. No brick.

I later used sfhub's autoroot tool to push over the FB21 CWM kernel repack. Again, rebooted fine.

EDIT - I've also Nandroid restored my GB ROM to get a GPS lock, shutdown, booted back into CWM and restored my FB21 ICS ROM. Don't know what to say really, but it seems I've done a lot of the things that people are suspecting are causing the bricks.
 
Last edited:
Epix4G

Epix4G

Senior Member
Sep 14, 2011
2,665
1,028
phoenix
Dchibro said:
I don't know if it's as simple as that. I went from FB17 to FB21 by ...

1) Booting into Rogue FB17 CWM repack recovery
2) Installing Calk's wipe all ZIP
3) Installing FB21 ROM
4) Installing FB21 Modem
5) Reboot

All went fine. No brick.

I later used sfhub's autoroot tool to push over the FB21 CWM kernel repack. Again, rebooted fine.

EDIT - I've also Nandroid restored my GB ROM to get a GPS lock, shutdown, booted back into CWM and restored my FB21 ICS ROM. Don't know what to say really, but it seems I've done a lot of the things that people are suspecting are causing the bricks.
Click to expand...
Click to collapse

All it takes is once to corrupt the data partition and you have a brick better to be safe

Sent from my SPH-D710 using xda premium
 
Dchibro

Dchibro

Senior Member
Jul 28, 2011
1,040
280
San Diego, CA
Epix4G said:
All it takes is once to corrupt the data partition and you have a brick better to be safe

Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse

Yeah you're probably right. After finally reading this whole thread I'm going to follow your advice and Odin a full EL29 before I go anywhere from here until this stuff gets worked out. Too many unknowns for my taste.
 
Epix4G

Epix4G

Senior Member
Sep 14, 2011
2,665
1,028
phoenix
Dchibro said:
Yeah you're probably right. After finally reading this whole thread I'm going to follow your advice and Odin a full EL29 before I go anywhere from here until this stuff gets worked out. Too many unknowns for my taste.
Click to expand...
Click to collapse

That's the thing no one knows for sure what is happening but most involve touch recovery...I just went back to cm7 last night and used mobile Odin pro to do it and it worked great ...

Sent from my SPH-D710 using xda premium
 
krazyflipj

krazyflipj

Senior Member
Jan 14, 2008
2,827
440
clipcarl said:
When mine bricked I was not touching the data partition at all. I was reinstalling a ROM and did not wipe data.
Click to expand...
Click to collapse

Based on your previous post, looks like the issue was that you were flashing CM9 3.1 with SH's Rogue Recovery. Remember, when 3.1 was released, there was no custom recovery for it. I believe/recommend the only way of flashing CM9 3.1 is with a stock CWM recovery (Found in CM7 rom). If you want Rogue Recovery, make sure you have stock CWM recovery found in cm7, flash CM93.1, then flash CM9 Rogue Recovery in the same session.
 
Last edited:
Epix4G

Epix4G

Senior Member
Sep 14, 2011
2,665
1,028
phoenix
One of the devs said that Samsung moved the data partition a little in ics .... Don't remember where I saw it but that could be the reason no one has had a brick when Odin back yo GB vs just restore back or flash back from ics .... Safer to Odin in my opinion

Sent from my SPH-D710 using xda premium
 
O

ojones838

Senior Member
Oct 16, 2011
81
6
Louisville
Visit to Sprint Store was unproductive

I bricked my E4GT by flashing a ICS 4.0.3 ROM. So yesterday I went to a Sprint Store and was told that flashing ANYTHING that didn't come from Sprint voided my warranty. And that since I wasn't a Sprint subscriber (Credo Mobile subscriber), they couldn't work on my phone. From what they were saying they couldn't even work on it by me paying for it. I was hoping to get reflashed by JTAG. So today I'll call Credo and try to get an exchange. The phone is just over a month old. And since Credo doesn't have any means of troubleshooting or repair like Sprint, all they can do is exchange it. Or maybe I can just take it to a cell phone repair shop and see if they can JTAG it. WHATEVER, I just need my phone back. I may even have to "update" my phone meaning just buy another one for almost full price and chalk it up to my stupidity. I should have known better to flash a ROM from Zedomax immediately before checking it out by searching for comments etc.,first. I feel a little better knowing that Samsung phones respond to the JTAG very nicely. Now everything depends on what Credo tells me today. Will update...
 
nevrlow

nevrlow

Senior Member
Jul 27, 2011
3,013
537
virginia beach
Bricking a phone is never a good time. I've only Bricked one phone thank God. I got a g1 back in the day and rooted successful. Traded it for a white T2. I Bricked that one. haven't Bricked a phone since. Scary stuff.

Sent from My HD2 with GingerBreadz.
 
You must log in or register to reply here.

Similar threads

Calkulin
[ ROM ] Calkulin's E4GT v3.0 [ EL29 l Fast l Tweaked l Battery Saver Script ]
Replies
12K
Views
2M
elliwigy
elliwigy
kc_exactly
ICS for Epic Touch!!! FF18 Update thread
Replies
11K
Views
2M
M
mikelav456
Calkulin
[ ROM ] Calkulin's E4GT 2 v1.6 [ ICS l FE22 l Tweaked l Battery Saver Script ]
Replies
5K
Views
907K
jerryp7
jerryp7
rwilco12
  • Locked
[ROM][TN] MIJJz JB GOODNESS JB 4.1.2 FK23 v1.0.3 (Updated 12/21/2012)
Replies
18K
Views
2M
bilgerryan
bilgerryan
KBizzle
  • Locked
[ROM][E4GT][11/11/12] PARANOIDANDROID 2.54 4.1.2 | Hybrid, Size&UI on PerAppBasis
Replies
5K
Views
557K
Chef_Tony
Chef_Tony

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 4
    S
    sfhub
    E4gt wasn't really brickable either until:

    People saw ics test releases coming out for the intl gs2 and started flashing them getting the intl bootloader which rendered their usb port inoperable even though they could get intk odin dl mode.

    Ics test releases started coming out for e4gt which ended up using a linux 3.0 kernel which has slightly changed how partitions are accesed. This coupled with a suggestion that people combine cwm touch with the new kernel caused the 2nd set of bricks.

    Both these conditions didn't exist during tge og epic days you remember. There was far less confusion about the intl galaxy s and there was no 3.0 linux kernel with ics.
    View
    3
    iBustCh3rries
    iBustCh3rries
    Well since I just bricked my phone I decided to start this tread. I figured it would be helpful for people to read to keep them from bricking their phone by not following the same process of the unlucky few who have hard bricked their device.

    I flashed the Rogue CM9 kernel through Mobile Odin Pro and while on the FB17 leak from Calk which is where I think I made my mistake. when I went to flash CM9 alpha 3.1 it got stuck at install for about 15 minutes before i decided to the battery which I knew was a HORRIBLE idea. When I tried to boot back up all I got was a blue light. My guess is that the phone didn't like that I had a AOSP Kernel while on a TW rom and got confused and froze because it didn't know what to do next. The good news it that sprint is ever so gracious to provide me with a new phone coming in the mail on Thursday since they don't have any in stock. I just told them I got a update and when it installed it wouldn't boot back up and I should hopefully be back in business with some CM9 yumminess later this week :D thank the cellular gods for insurance!


    Some users are reporting that mobiletechvideos.com is somewhere you can send your phone too have it brought back from the dead.
    View
    2
    ReActiveDisorder
    ReActiveDisorder
    Oh I bricked my ET4G by........by.........No wait, Ive never bricked my sh** before. Lol.

    4257422d-04c5-2caa.jpg


    ^^^What he said :rolleyes:

    Sent from my SPH-D710 using xda premium
    View
    2
    spbeeking
    spbeeking
    After I got the blue led of death, I took it into sprint and played dumb. (The guy from mobiletechvideos emailed me and said that he probably couldnt fix my phone) I told sprint that it dropped it the middle of an update, and wouldnt boot. Came back two hours later, and they said they tried to swap the screen. (Idiots) Left 5 minutes later with a brand new one. Social Engineering at its finest.
    View
    2
    S
    sfhub
    Imo it is more productive to concentrate on providing solutions rather than ripping on each other.

    It is hard to get down to the bottom of the issue with cwm touch fake flashed onto an ics linux 3.0 kernel when previously it had only been paired with a gb linux 2.6 kernel, especially when one is working blind and doesn't have the source for either.

    I did notice the major/minor dev numbers changed for the /data partition between the ics 3.0 kernel and the gb 2.6 kernel while most of the other partitions stayed the same. That might explain why all the other partitions are fine and it is /data that is hosed. I would start there and see if there is any hard-coded partition info that wouldn't adjust.
    View

New posts