Develop Bugs

How Not To Brick Your E4GT (UPDATED 10/13/12)

-PLEASE READ THE WHOLE THREAD BEFORE ASKING, OR STATING ANYTHING OR YOU WILL BE TROLLED (BADLY)
-YOU, AND ONLY YOU ARE RESPONSIBLE FOR YOU'RE ACTIONS. IF YOU FLASH AND BRICK YOU'RE PHONE, ONLY YOU ARE TO BLAME.
Sorry guys it's been a while since I've been able to update this thread, I'm extremely glad to see that it's being used throughout the E4GT community. Well I guess it's time to update this so lets get started, and please forgive me if I miss anything as I have been on ICS mainly for a long time.
-Are you on a rom with a stock recovery or with a kernel released prior to SOURCE? Use Odin buddy!
______________________________________________
Just because we have source now, does not mean you can't still brick you're device. In fact many people are still on ICS builds prior to FF18 or newer, this includes people using stock kernels as well. Do not use the recovery on you're phone to do anything, The stock recovery is meant for files signed by Samsung and only Samsung, Roms prior to source with a custom recovery had the dreaded EMMC bug which would brick some people with a simple wipe. If any of the above applies to you and you wish to get back to GB or ICS then click on the following link that corresponds to you're desire and follow the steps.
EL29 One Click Link Below
__________________________________________________
http://forum.xda-developers.com/showthread.php?t=1433101
__________________________________________________
ICS FF18 (Original ICS OTA update) Link Below
__________________________________________________
http://forum.xda-developers.com/showthread.php?t=1721229
__________________________________________________
ICS FI27 (Newest ICS OTA update) Link Below
__________________________________________________
http://forum.xda-developers.com/showthread.php?t=1932032
__________________________________________________
-After you install the .Tar file to you're phone, you'll need to install a custom recovery using a Auto Root Package found below, just follow the instructions. (use the FF18 Combo to install a custom recovery on the FI27 version)
http://forum.xda-developers.com/showthread.php?t=1342728
_________________________________________________________________________________________________
-Wanna flash to ICS from GB?
_______________________________________________________________________________________
Simply pick the ICS rom you wish to use and flash using the OP's instructions. The issue of flashing to ICS from GB never really existed. If you are still worried about the risks of flashing to ICS, then use the Odin One Click method above and you're guaranteed fine.
_______________________________________________________________________________________
-Wanna Flash to GB from ICS?(includes restoring backups to GB roms too)
_______________________________________________________________________________________
This is where issues began to occur, prior to source release. The EMMC bug was present during the ICS leaks leading up to source release FF18 (FF18 OTA not being the issue). If you are on a rom which already contains a source kernel (FF18 and newer) Flashing to GB is the same as flashing to another rom, just follow the OP's instructions. If you're on a leaked rom with a stock recovery, or custom recovery, use the Odin One Click method to get back to GB or ICS. DO NOT WIPE IN NON-SOURCE KERNELS--- EVER
_______________________________________________________________________________________
-Wanna Flash Good ol' CyanogenMod, or Something else AOSP?
____________________________________________________
-CyanogenMod 9 as of recent bulids has a proven SAFE RECOVERY, so you should be able to flash to, and from without issues
-I am unsure if CyanogenMod 10, or other Jellybean AOSP roms have a safe recovery, so I recommend this method below
Always use the EL26CWM kernel to flash AOSP roms. I myself, have flashed CyanogenMod 9 with multiple non-CWM kernels without issues, but better safe then sorry right? Thanks to rwilco12, we now have a repository for kernels, and modems so give him a big thanks. You can find the EL26 CWM kernel here.
http://rwilco12.androidfilehost.com/?dir=Kernels/Recovery Kernels/GB/Chris41g/Stock CWM
Simply download the rom you wish to flash, as well as the EL26CWM kernel. Flash the kernel, and reboot back into the recovery. When you're phone restarts back into recovery press up, down, up, down with you're volume buttons to enable the selection button (power on/off button). Now flash the rom USING THE RECOMMENDED FLASHING INSTRUCTIONS. Instructions of roms may differ from others so be sure to read the Original Post by the dev before flashing.
-Are you on an AOSP rom and you wish to flash to a TW rom or other?
____________________________________________________________________________
Follow the same instructions for flashing to an AOSP rom, except replace the AOSP rom with the rom of you're choice. You can also use the One Click Odin Method from before. I have used both of these methods for flashing a different rom while on AOSP multiple times without any issues whatsoever.
________________________________________________________________________________________________
-Bricking Info
_________________________________
-For more info on the EMMC chip corruption issue from kernels prior to source go here
http://forum.xda-developers.com/showthread.php?t=1644364
________________________________________________
MISC
_________________________________________________________________________________________________
-Stick with source kernels and you should be safe
-Stay away from touch recovery, unless it's source-based
-Stay away from Rom manager, It's not, and probably never will be optimized for our phone
-Thanks
__________________________________________________________________________________________________
Calkulin, Mijj,all of Team Venom, all of Team Rejectz, agat, good ol' ruj22, rwilco12, garwynn, Ja5on for the title, all devs, and themers

Hey xST4T1K, great idea for a thread man, and great accumulation of information. As it seems, I have seen quite a few bricked devices in the Q&A lately. Hopefully new members of this community will take a moment to read this and understand some of the problems that others are having in hopes that it will help at least one person from brickin' their celly. Thanks again xST4T1K...

I really think that something like this should be stickied....

jasone4gt said:
Hey xST4T1K, great idea for a thread man, and great accumulation of information. As it seems, I have seen quite a few bricked devices in the Q&A lately. Hopefully new members of this community will take a moment to read this and understand some of the problems that others are having in hopes that it will help at least one person from brickin' their celly. Thanks again xST4T1K...
Click to expand...
Click to collapse
No problem man, If you have anything to add please feel free, I know I missed some things I'm sure, but glad you like it!

shiftr182 said:
I really think that something like this should be stickied....
Click to expand...
Click to collapse
Exactly what I was thinking. With a title something along the lines of How to not brick your device.

shiftr182 said:
I really think that something like this should be stickied....
Click to expand...
Click to collapse
Agreed, I was surprised I hadn't seen any other threads like it yet

jasone4gt said:
Exactly what I was thinking. With a title something along the lines of How to not brick your device.
Click to expand...
Click to collapse
Lol renamed and gave you credit for the tittle

Some of us, myself included , bricked by using odin. I'm very experienced in modding my phones and I bricked one, so its not a lack of knowledge that caused this. I was going from one of the ics builds back to a stock rooted rom using one of sfhubs all in one odin packages and it some how screwed up the data partition. I had done it several times without issue so it surprised me when it bricked it. I think that I was using the touch recovery when it happened but I'm not positive. Hope this helps someone.
Sent from my MB855 using XDA App

xST4T1K said:
Lol renamed and gave you credit for the tittle
Click to expand...
Click to collapse
LOL nice, you didn't have to do that it's your thread, but thanks man!

jasone4gt said:
LOL nice, you didn't have to do that it's your thread, but thanks man!
Click to expand...
Click to collapse
Lol it's a way better title then mine bro, plus hopefully it will open up to more people

stonesaber said:
Some of us, myself included , bricked by using odin. I'm very experienced in modding my phones and I bricked one, so its not a lack of knowledge that caused this. I was going from one of the ics builds back to a stock rooted rom using one of sfhubs all in one odin packages and it some how screwed up the data partition. I had done it several times without issue so it surprised me when it bricked it. I think that I was using the touch recovery when it happened but I'm not positive. Hope this helps someone.
Sent from my MB855 using XDA App
Click to expand...
Click to collapse
Actually, more then likely your device isn't bricked, sfhub helped someone else with the same issue unbrick they're device. Look around the q&a section and you'll find it. I also mentioned touch recovery as a possible issue, gotta read broski. Doesn't matter how experienced you are, you can still have a brick with one wrong move, even devs brick sometimes, I've been doing this for 5 years now and even I almost did the other day.

xST4T1K said:
Actually, more then likely your device isn't bricked, sfhub helped someone else with the same issue unbrick they're device. Look around the q&a section and you'll find it. I also mentioned touch recovery as a possible issue, gotta read broski. Doesn't matter how experienced you are, you can still have a brick with one wrong move, even devs brick sometimes, I've been doing this for 5 years now and even I almost did the other day.
Click to expand...
Click to collapse
There was nothing to read. I was one of the first. I tried everything before finally sending it to Josh at mobiletechvideos.com. It's on the way back and should be here @ Sat. According to him in the main tread though, even he was unable to repair it but he didn't mention mine being un-repairable in the emails he sent me. I'll find out soon and let everyone know.

stonesaber said:
There was nothing to read. I was one of the first. I tried everything before finally sending it to Josh at mobiletechvideos.com. It's on the way back and should be here @ Sat. According to him in the main tread though, even he was unable to repair it but he didn't mention mine being un-repairable in the emails he sent me. I'll find out soon and let everyone know.
Click to expand...
Click to collapse
Calm down buddy! just be more careful when flashing that's all, and stay away from touch recovery, even Steady debated pulling the link because of bricking issues.

xST4T1K said:
Calm down buddy! just be more careful when flashing that's all, and stay away from touch recovery, even Steady debated pulling the link because of bricking issues.
Click to expand...
Click to collapse
I'm perfectly calm. As stated, I was one of the first to brick using touch recovery so even if the link was pulled, it would've been too late for me. I do not need anyone jumping to conclusions without having the facts. That is all.

stonesaber said:
I'm perfectly calm. As stated, I was one of the first to brick using touch recovery so even if the link was pulled, it would've been too late for me. I do not need anyone jumping to conclusions without having the facts. That is all.
Click to expand...
Click to collapse
Completely understand now, didn't know how long ago you bricked so sorry for the assumption, hope you get it restored. I know this thread may not solve everyone's issue but please understand that I put it up so people were aware that things may be an issue

This is great to see before I start flashing thank you
Sent from my SPH-D710 using xda premium

Sheldon_ said:
This is great to see before I start flashing thank you
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
At least you took the time to read this before posting another thread that you bricked you phone doing the same thing others are doing and not reading first..... My hats off to you good sir
Sent from my SPH-D710 using Tapatalk

Epix4G said:
At least you took the time to read this before posting another thread that you bricked you phone doing the same thing others are doing and not reading first..... My hats off to you good sir
Sent from my SPH-D710 using Tapatalk
Click to expand...
Click to collapse
Agreed, too many people are getting flash happy and not paying attention to the forums anymore

Haha thanks guys
Sent from my SPH-D710 using xda premium

I've bricked mine a different way. Was playing around with a CM9 test build, and bricked mine pretty good. I can get to odin and recovery, and sometimes it will loop the boot animation infinitely.
Everytime i try a OC odin, it hangs at data.img forever, i can't restore any rom, tried reflashing the rom that 'broke' my phone, not sure where else to head. looking like $35 at sprint ain't too shabby

[Q] Jelly Bean ROMs stuck at loading screen

I tried loading a couple Jelly Bean roms for my Verizon GNex.
It's unlocked and everything and it was on 4.0.4 Build IMM76K with superuser and CWM recovery. The whole deal.
I ran recovery and tried to load these 2 ROMS, 2 seperate times starting from a fresh 4.0.4 build each time:
BAMF you jelly v1.3: http://forum.xda-developers.com/showthread.php?t=1744389
and
Team Liquid Vicious-toro V3: http://forum.xda-developers.com/showthread.php?t=1738018
Someone suggested to try a different kernel, but I'm not sure what that means.
What should I do?

are you using the touch recovery?

Did you WIPE DATA first?
Sent from my Galaxy Nexus using Tapatalk 2

Try Team Vicious's again, and be patient. I remember when I first flashed V1 I waited about 2-5 minutes before it brought me to the welcome screen. The Kernel that comes with Vicious is fine, although I've been using Faux's Kernel and am LOVING it.
You can flash kernels the same way you flash ROMs, as long as it is in a ZIP file, you are good to go. Just make sure it is compatible with Jelly Bean.
Let me know what method you are using to flash ROMs and I will try to be more detailed if needed.

Yes I am using the touch recovery. Am I not suppose to?

iamTWOcats said:
Yes I am using the touch recovery. Am I not suppose to?
Click to expand...
Click to collapse
its been known to have issues. use the regular cwm

Did you fix permissions?
What loading screen? Google screen or boot animation?
Jeez, people need to search for real, like 3 threads on this already. Why don't you ask over in respective rom thread? Better yet, I don't believe bamf or vicious devs would release a rom without making sure it boots.
Sent from my i9250

Zepius said:
its been known to have issues. use the regular cwm
Click to expand...
Click to collapse
Been using touch for months. Never had an issue.
Sent from my Galaxy Nexus using Tapatalk 2

Did you wipe data or try flashing over your other ROM?
Sent from my Galaxy Nexus using Tapatalk 2

Same boat here ..tried 2 different rom and kernel.. stock in boot loop.. last week I manage to flash vicious jb rom and it works great..then I try to flash different rom last night and im stock in boot loop and now back to ics.. I hope someone can help us with this..
Sent from my Galaxy Nexus using XDA Premium App

GNex stuck at Jelly Bean ROMs boot animation loading screen
I'm in a similar situation. After I flashed my Verizon GNex to Vicious Jelly Bean V3 everything seemed fine. So I decided to try my luck at flashing a theme as well. The phone is stuck on an endless JellyBean animation screen. My laptop no longer recognizes the Samsung drivers ie. they won't load, so I have no way to talk to this thing. I've tried to initiate recovery mode on the phone and it won't work either. Anybody know something I could try? I'm obviously new at this so any help would be appreciated.

Same problem over here with a friends Gnex. Same JB that installs and boots fine on my Gnex will not run on his. Weird issue
bk201doesntexist said:
Did you fix permissions?
What loading screen? Google screen or boot animation?
Jeez, people need to search for real, like 3 threads on this already. Why don't you ask over in respective rom thread? Better yet, I don't believe bamf or vicious devs would release a rom without making sure it boots.
Sent from my i9250
Click to expand...
Click to collapse
Jeez why don't you try helping the OP?

[Q] Reset to stock rom

Just got into the rooting scene again. I rooted my phone with CWM and LiquidSmooth, but I liked the stock Samsung rom better. Looks like the LiquidSmooth is kind of bugged, the gallery is not as good at the default, camera app isn't really good etc.
I've found the stock rom for 4.1.2 for my I9305, but when I flash it, it just makes an exclamation mark when booting and gets stuck at Samsung logo.
Now the problem is, that It won't connect to Samsung Kies. I want to reset the phone to factory rom, but Samsung won't connect to phone in Download mode.
I know the rules of a forum etc. and I have really been searching, but sometimes you need personal advice, because I really tried a lot of things
Got CWM-based Recovery v6.0.2.8 right now.
I've tried flashing with Odin and I9305XXBLL3_I9305HTDBLL2_I9305XXBLL3_HOME.tar - But doesn't really work.
Thank you in advance!

And at the same time as making this thread, I tried flashing with the rom again, and now it works. Think I forgot to do factory/cache reset.
My fault! Hope this thread helps someone else in the future.

Put "SOLVED" in thread title please
Thanks
Sent from my PG06100

It's good he figured it out cause he got the wrong thread. This is SPH-L710 forum not the I9305 forum.
Transmitted with a portable device using Xparent Blue Tapatalk 2

edfunkycold said:
It's good he figured it out cause he got the wrong thread. This is SPH-L710 forum not the I9305 forum.
Transmitted with a portable device using Xparent Blue Tapatalk 2
Click to expand...
Click to collapse
Oh true. All i read was his last post
Sent from my PG06100

Epic 4G Touch - Constantly Rebooting!

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

JellyBam v7.2.0 epicmtd stable rom wont boot

I Found JellyBam v7.2.0 epicmtd stable rom here http://goo.im/devs/JellyBam/Samsung Epic 4G - Epicmtd
I tried installing it but failed in the recovery anyone willing to fix it? thanks

JellyBam was abandoned, so all JellyBam thread was closed
Almost all device had a problem of that
Sent from my JellyBeer v.4.14 epicmtd (b3)

Dropple said:
JellyBam was abandoned, so all JellyBam thread was closed
Almost all device had a problem of that
Sent from my JellyBeer v.4.14 epicmtd (b3)
Click to expand...
Click to collapse
Oh ok thanks for the info, also dropple thanks for jellybeer! :thumbup:
Sent from my SPH-D700 using xda premium

Jshugzda said:
I Found JellyBam v7.2.0 epicmtd stable rom here http://goo.im/devs/JellyBam/Samsung Epic 4G - Epicmtd
I tried installing it but failed in the recovery anyone willing to fix it? thanks
Click to expand...
Click to collapse
Hi, I just made the same mistake as you except that I'm stuck with that boot animation going in a loop until I take out the battery, I can put the battery back in and boot into recoverybut I've got nothing to flash as I deleted the last ROM I was using (omega rom).would anybody know how to fix my problem ?

crrryan said:
Hi, I just made the same mistake as you except that I'm stuck with that boot animation going in a loop until I take out the battery, I can put the battery back in and boot into recoverybut I've got nothing to flash as I deleted the last ROM I was using (omega rom).would anybody know how to fix my problem ?
Click to expand...
Click to collapse
Open a help thread in your device's Q/A forum. Our device never had a rom called "Omega".

I'm using a galaxy note 2, which does have one. After I booted it to teamwin recovery I played around and got it to work, so thanks anyway
Sent from my Nexus 10 using xda app-developers app

Hi ryan and hugz
Over the past week i have been trying to find a good rom for my epic. I think i have a bad phone, as any rom i use still has the same problems as stock.
I thought i hard bricked my phone a couple of days ago. Follow this thread to Odin back to stock, then root as usual, if you can not resolve your issues. Once back to stock and rooted, you should be able to restore nand, if you made one, once you reinstall cwm or twrp.
http://forum.xda-developers.com/showthread.php?t=1052813
Always remember to backup with TiBu to keep reinstalling apps simple.
Sent from a rooted candy bar