My once bricked E4GT! - Samsung Epic 4G Touch

To be honest,
Once I got to the rogue et recovery I cried a little (because I actually got there.)
7 hours worth of beating sleep, numb legs from sitting down, afro being dry, and Samantha (samsung support person, cause I really was going to send my phone in..)
Two batteries *thank god!
Don't really, can't explain much. Just a load of reading of the "download shabby's/acs leaked fb17...." thread, xda search tool, google, and youtube.
I'm just glad, I found some way to enable recovery. No, 2 weeks without a phone, no going to the shipping retail location, no "not having my little cloud(white e4gt) in my hand." ....cheesy
I hear birds chirping outside, wow, and the sun is starting to come up.
Now I must figure out what I need to do next in recovery, then get out this desk chair (because my dsfgh...), and go to sleep!
XDA ROCKS!

Wut? You saying you brought your E4GT back from a brick?
Sent from my SPH-D710 using Tapatalk

How did that happen?

I'm guessing it wasn't a real brick as in blue light of death. Probably stuck in a boot loop or something.
Sent from my SPH-D710 using Tapatalk

What type of brick lol? A soft brick all you need to do is go into download mode and ODIN over some new firmware, forget recovery lol. Unless it was a super brick from flashing ICS recovery where you luckily have recovery... your still pretty screwed. But if it was just a bootloop, soft brick the fix is simple.

slick_rick said:
I'm guessing it wasn't a real brick as in blue light of death. Probably stuck in a boot loop or something.
Sent from my SPH-D710 using Tapatalk
Click to expand...
Click to collapse
How do you fix from boot loop ( the yellow triangle )? I can get in recovery and odim but which ever rom I flash it will not boot up...only to the triangle. In the recovery mode it take very long time to format the data and setting.....waiting time is like one minute. Any help?

K.0.0.L. said:
How do you fix from boot loop ( the yellow triangle )? I can get in recovery and odim but which ever rom I flash it will not boot up...only to the triangle. In the recovery mode it take very long time to format the data and setting.....waiting time is like one minute. Any help?
Click to expand...
Click to collapse
...People lack so many details. What rom where you on when the phone last worked, what were you flashing when it screwed up. What is ODIN getting stuck on?
Your either easily fixable, really screwed or completely screwed. Welcome to the 3 possibilities. Without any details for all I know your on Gingerbread and did something retarded or you were flashing in Ice Cream Sandwich and screwed yourself not following directions.

RainMotorsports said:
...People lack so many details. What rom where you on when the phone last worked, what were you flashing when it screwed up. What is ODIN getting stuck on?
Your either easily fixable, really screwed or completely screwed. Welcome to the 3 possibilities. Without any details for all I know your on Gingerbread and did something retarded or you were flashing in Ice Cream Sandwich and screwed yourself not following directions.
Click to expand...
Click to collapse
I was on wicked sensation and flash to AOKP build 39....It never happen to me before but somehow this time it did. I use culklins format all and during the data format it get stuck for long time then I remove the battery and it just never able to go pass beyond that. Just couple hour ago I let it sit on that process and it finally format the data and system..I then flash the AOKP but it get stuck on the boot animation......so I decided to ordin to stock kernel EL26 and now same old thing again...unable to go beyond boot loop. My custom binary download is 11 counts...........I have order the USB jig from ebay to see if it can help to erase the counts, maybe that is the issue why not booting up

K.0.0.L. said:
I was on wicked sensation and flash to AOKP build 39....It never happen to me before but somehow this time it did. I use culklins format all and during the data format it get stuck for long time then I remove the battery and it just never able to go pass beyond that. Just couple hour ago I let it sit on that process and it finally format the data and system..I then flash the AOKP but it get stuck on the boot animation......so I decided to ordin to stock kernel EL26 and now same old thing again...unable to go beyond boot loop. My custom binary download is 11 counts...........I have order the USB jig from ebay to see if it can help to erase the counts, maybe that is the issue why not booting up
Click to expand...
Click to collapse
Wicked sensation is an ICS rom right? Did you flash AOKP 39 from ICS Recovery? The one thing you should not do? If the rom does not have a safe updater binary there is a high chance of super brick when flashing from even a safe ICS recovery, and even higher from the regular repacks. NEVER factory reset from any non safe ics recovery and never flash a zip in ICS recovery unless it is marked as safe to do so.
If when trying to ODIN stock firmware it gets stuck at Data.img then you really did it this time. From what I have heard there are 2 levels of the super brick. The kind where you can still get to download and recovery and the kind where you cant. Stuck on Data.img on the first kind is a bad sign.
As far as the triangle goes that comes up any time you odin an unsigned kernel etc like the el26 cwm one. It is just an indicator and should not be a part of your problem.

Flash any stock gb kernel it should remove the triangle! (ODIN)

I don't really know what's up right now...
The whole reason I'm in this mess is me changing settings when I first flashed AOKP 39. Like setting display, changing the wallpaper. Just going straight down the whole setting page.
I got to the DPI settings, changed it to something lower, 240 i think. Rebooted... Didn't like it, changed it back to the original, rebooted... the words and all were original but not the status bar, not the lock screen, not the navi bar.
It was super weird!
So I thought:
"...doing a factory reset would allow me to start fresh again. If that doesn't work, I can just start completely over(odin back to gb). that way I can install gapps(the arrangement of back and enter buttons confused me, causing me to restart)"
All of a sudden, phone didn't work. Can't really remember what happened at the time. If it went into boot loop or not. But it didn't go into the rom.
Somehow, I ending up doing stuff, since I just got it a week ago I really didn't know much, was just learning as I went. "new phone, new things to learn"
Anyways, ending up with "A" recovery, and I've always been able to get into ODIN.
recovery that works is: rogue_ET-recovery-1.2.2-FB27-rc0.tar
Now that I have some kind of recovery and odin I thought, maybe I could get back to stock. Just don't know how, thats were doing more searches came in. Still got NOTHING. lol.
I was aware of not flashing ics from an ics dadada messages. hint: i read stuff
I did a factory reset which caused all of this. Kinda know I shouldn't of done it now, ...never came across anything about not doing it at the time. I still haven't, I'll google that too.
Umm.. flashing stuff through pda doesn't work. to be more specific
when I look at the progress, it doesn't include data.img (so it PASS)
if I odin something and it says data.img, then its stuck there.
so that recovery I'm using: (volup+pwr)
bootscreen(samsung galaxy s II) -> quick led(blue) -> bootscreen(samsung galaxy s II) -> recovery
any other tries when getting into recovery WITHOUT odin rogue_ET-recovery-1.2.2-FB27-rc0.tar: (volup+pwr)
quick led(blue) -> bootscreen(samsung galaxy s II) -> quick led(blue) -> bootscreen(samsung galaxy s II) bootloop bootloop bootloop. Sometimes it will stay there for a few minutes then bootloop again.
-----
so right now, ....still trying to find a solution. I'm still on google and xda searching. I really don't want to do anything else because both batteries I think are nearly dead...
When I started flashing, I was on ParanoidAndroid, then I found AOKP 39. It worked, was awesome. But I did a factory reset from the settings within the rom and now Im typing this...
flashing in recovery, when trying to erase data(it doesn't work.) though cache and dalvik does.

AndroidRocksSocks said:
When I started flashing, I was on ParanoidAndroid, then I found AOKP 39. It worked, was awesome. But I did a factory reset from the settings within the rom and now Im typing this...
Click to expand...
Click to collapse
Suicide.
AndroidRocksSocks said:
flashing in recovery, when trying to erase data(it doesn't work.) though cache and dalvik does.
Click to expand...
Click to collapse
Because the /Data partition is borked.

RainMotorsports said:
Suicide.
Because the /Data partition is borked.
Click to expand...
Click to collapse
Right, had* to be something.
CPR?

If all you get is the blue led.... Its done. That's what I was seeing when I bricked my first e4gt. On AOKP it says in red all caps too, do not do anything with this kernal.. Probably not word for word, but unless its a safe recovery as stated, you can't do anything with it, not even wipes.

evo-t said:
If all you get is the blue led.... Its done. That's what I was seeing when I bricked my first e4gt. On AOKP it says in red all caps too, do not do anything with this kernal.. Probably not word for word, but unless its a safe recovery as stated, you can't do anything with it, not even wipes.
Click to expand...
Click to collapse
....lol he already said he is getting past that. Still the same issue though he is Super Bricked.
AndroidRocksSocks said:
Right, hand to be something.
CPR?
Click to expand...
Click to collapse
Your at the level where some people seemed to have been able to repartition the eMMC around the origina /Data area consuming space other partitions normally used. Its not considered stable.
There is no premenant fix that can be applied by you, a sprint store, or even jtag service. The Super Brick bug corruption occurs at the lowest possible level. You basically need Samsung to fix it, though just about anyone on the eMMC partner list technically can.
Phone replacement is the primary option or you can see about getting info about the repart here - http://forum.xda-developers.com/showthread.php?t=1644364

Great, ha-ha.
Well, I look into that repart info. If I can't handle it. All I have to do is print out the ups shipping label and send it in. So sad... anything I need to do when sending it in? As in, do I need to put it at some kind of "ok" state? Ugh, I hate this.

AndroidRocksSocks said:
Great, ha-ha.
Well, I look into that repart info. If I can't handle it. All I have to do is print out the ups shipping label and send it in. So sad... anything I need to do when sending it in? As in, do I need to put it at some kind of "ok" state? Ugh, I hate this.
Click to expand...
Click to collapse
I would see about odining over the stock EL29 kernel but the yellow triangle is still going to say hey look at me. If that USB jig arrives should be able to reset the counter.
If its via insurance it wont matter.

RainMotorsports said:
I would see about odining over the stock EL29 kernel but the yellow triangle is still going to say hey look at me. If that USB jig arrives should be able to reset the counter.
If its via insurance it wont matter.
Click to expand...
Click to collapse
Ya know, I was planning to go outside today...
This test thing looks alright though.
I guess I'll follow the steps and the following questions from others who have or are doing it.

AndroidRocksSocks said:
Ya know, I was planning to go outside today...
This test thing looks alright though.
I guess I'll follow the steps and the following questions from others who have or are doing it.
Click to expand...
Click to collapse
Which test? The AOKP 37/ CM9 Alpha 5 test? That was for people wanting to flash things without bricking their phone. I think you caught my link before i changed it to the original post.

RainMotorsports said:
Which test? The AOKP 37/ CM9 Alpha 5 test? That was for people wanting to flash things without bricking their phone. I think you caught my link before i changed it to the original post.
Click to expand...
Click to collapse
Oh wait a min...
Right, yea I did.
This one: Discussion thread for /data EMMC lockup/corruption bug

Related

[Q] Boot Looping Evo

Hey Guys-
Couldnt find a thread similar so I'll start my own.
6 days ago i updated my rom to CM 7.0.3 and the newest version of Savaged Zen Kernel (dont remember version). Everything was fine until leaving work last night and it began to boot loop in my pocket while driving home. Phone had worked as normal all day (web, text, talk), no changes made to phone either. The only thing i can do is get into the bootloader (by holding power and volume up). Although when i try to enter recovery from there to flash a backup, it just puts me back into the boot sequence again. Any help guys?
http://api.viglink.com/api/click?fo...ersonic-v2.3 - xda-developers&txt=PC36IMG.zip
download that rename PC36IMG and put on root of sd card now go into bootloader go into fastboot and it should stay start update press volume up for yes and then when its done put yes it gonna reboot now take out battery put it in evo again and go into bootloader againthen from bootloader go into recovery from there and you should see amon-ra and from there try to do a nandroid or flash a new rom
I got the update to go through, but now when it prompts me for a reboot it just keeps looping. Even when i select no i dont want to reboot and then try and go into recovery, it loops.
try taking out battery for 2 hours and try again
cool will let it rest and let you know the results when I try again.
ar4senal said:
cool will let it rest and let you know the results when I try again.
Click to expand...
Click to collapse
Do you have insurance on your Evo? Is it still within it's 1 year warranty? It sounds like you got the eternal bootloop of death. Is your bootloader S-on or S-off? The condition you're experiencing is unexplained and usually not fixable. running an RUU is your only hope, and if that failed...your pretty much out of luck.
See this thread: http://forum.xda-developers.com/showthread.php?t=1009672&highlight=boot+looping+no+recovery+access
Yea I'm pretty sure it is still under warranty. I got the phone last August. My bootloader is S-Off. Ill check that thread out.
All you should need to do is wipe and re flash cm7... Our write and re store a back up
Sent by Supersonic!
could be the battery is bad and it is just not getting a constant connection, thus boot looping. i had this issue with a bad battery, swapped it out, no problems
For the record, I mis-spoke...
Sent by Supersonic!
Yea Its not taking anything I flash onto it. No way to get the S On back either. After reading that thread its looking like I am gonna have to somehow fully brick it and take it back to Sprint for a new one......UGH!
First, there are a lot of instances of this happening. Well, not a LOT, but there are several threads about it.
Anyhow, give me a few minutes to upload a file to my mediafire. It's a walk through someone on here wrote that is very detailed and it takes some work, but if everything else fails, it has been known to work.
I'll post the link in a few.
http://www.mediafire.com/download.php?9zc41jsfs7sm1qf
That's it.
You said that you installed the new recovery and still getting loops. That's because you didn't do anything in recovery. Go into recovery and try wiping cache/dalvik cache. See if it boots. If it doesn't go back into recovery go to the wipe menu and wipe everything except SD card and rotate settings. Reflash cm7 and it should work. Loops are a common thing and easy fix
P.s. I don't know if you did this but ill throw it in there anyway. You have to wipe cache and dalvik cache when flashing new kernels.
Sent from my PC36100 using XDA Premium App
ar4senal said:
Yea Its not taking anything I flash onto it. No way to get the S On back either. After reading that thread its looking like I am gonna have to somehow fully brick it and take it back to Sprint for a new one......UGH!
Click to expand...
Click to collapse
You can get s-on with 2 files one you flash in recovery the other in the bootloader (the same way you updated to amon recovery). I would post a link but can't cuz I'm on my evo. Just go into the evo development section and there is a thread like 2nd or 3rd page maybe farther back that is called "how to unroot in 2 steps" or something like that. Just did it for a friend 2 days ago so I know it works.
Sent from my PC36100 using XDA Premium App
The issue is that I cannot get into recovery AT ALL. Have tried numerous things. It just wont go into recovery. I bit the bullet and took it into the Sprint Store, they pulled up bootloader and never noticed the S Off at the top. Unfortunately my phone had undergone some sort of water damage. (?) So they were unable to do anything for me, looks like ill be paying the $100 deductible for the refurb.
On a side note the tech at the store told me he has been harvesting parts from evos and epics, and has amassed quite a collection of odds and ends, and that if I ever needed a screen replaced, etc. He would do it under the table for a small charge instead of going through the insurance company. Since i still have the phone ill try all these things again just to see if I can get it working again.
@HipCat- Posted before i read your post....Ill try those steps here in a minute. Thats something I have not tried.
PhxkinMassacre said:
You can get s-on with 2 files one you flash in recovery the other in the bootloader (the same way you updated to amon recovery). I would post a link but can't cuz I'm on my evo. Just go into the evo development section and there is a thread like 2nd or 3rd page maybe farther back that is called "how to unroot in 2 steps" or something like that. Just did it for a friend 2 days ago so I know it works.
Sent from my PC36100 using XDA Premium App
Click to expand...
Click to collapse
I cant get into recovery.....

[Q] Stuck in an unual bootloop... Help Please!!!

I cannot get passed the samsung galaxy s2 screen. When i go to recovery it takes forever to try to wipe cache and system and comes up with miscellaneous red text problems. I have never had this happen and have flashed roms since this phone came out. Does anyone know how to get passed this??? I even odined back to various versions of os to included EK02, EL29, EL29 ROOTED, using one clicks and regular odin. Is there anyway to get passed this problem. I looked all through the forums and still can't get the phone to boot. Please help
Were you trying out CM9/AOKP? Did you do wipe data/factory reset in an ICS kernel?
Yes... I was trying the AOKP :-( I was tired so i may have used clockworkmod to wipe while on ics kernel. I know i should have used mobile odin to change kernel, I had no problem going from ics to ics or ics to GB with AGAT's . Have a made a fatal mistake? You knew exactly which rom i was trying. I know not to do that but i may have on accident. Can i get passed this? I can only get to the samsung galaxy screen. and then it turns off and comes back on. Even with the phone off and on charge... The battery charge icon shows up frozen
Can you get to download mode?
Try to boot into download mode from a cold boot, if you can do that I would suggest using ODIN, the flashing god, to restore your phone back to a stock ROM. Preferably EL29, then if that is successful use ODIN again to flash FF11.
Sent from my SPH-D710 using xda premium
I can get to download mode but when i use OC it gets stuck shortly before the modem flash. I have been successful in using 1.85 with the EL29 tar but it still does the same thing. I will try ff11 to see if that works. So many red text errors in recovery. Sometimes i can wipe data sometimes i can't. I even got to a point where i actually used nandroid to restore my backup of wicked sensations ff11 (which i was success doing a few times before the brick) I will try again... with your suggestions. Thank all of you trying to help. This is very frustrating
UGH!!! Tried the FF11 one click and it still stops at the datafs portion! Just freezes. Going to wait a year to download the odin tar from slow file factory and hope that brings some progress... If anyone knows how to get past this, it would greatly be appreciated
That doesn't sound good. Sorry man. Some people have had luck pulling the battery and leaving out our for a few hours then trying the oneclick again. Sounds like you're hard bricked though.
Sent from my SPH-D710 using xda premium
You're bricked my friend ... there goes another victim
There's a bug in the EMMC firmware that causes the phone to lockup when certain mmc erase operations are done. This basically causes a superbrick which can't be fixed at this time.
The best you can hope for is to map around the problem, which is some effort and you'll always feel you phone isn't complete.
I would suggest you get it replaced.
What is considered mapping around the problem? Is there any way i can return to sprint or will that be a no go seeing how i can't reset the binary counter (as far as a know) without a jig? It is really stranger because i can odin back using a tar but one click odins freeze at data img. I can even get to different recoveries and some are functional for wiping cache and data, even restoring nandroid but once i get to the galaxy s2 screen it's game over. And of course when charging the phone the battery logo is frozen
mremale said:
What is considered mapping around the problem? Is there any way i can return to sprint or will that be a no go seeing how i can't reset the binary counter (as far as a know) without a jig? It is really stranger because i can odin back using a tar but one click odins freeze at data img. I can even get to different recoveries and some are functional for wiping cache and data, even restoring nandroid but once i get to the galaxy s2 screen it's game over. And of course when charging the phone the battery logo is frozen
Click to expand...
Click to collapse
Same here, exactly the same.
Does any of this add up to yours? What's happening completely sucks. :/
My once bricked....
mremale said:
It is really stranger because i can odin back using a tar but one click odins freeze at data img. I can even get to different recoveries and some are functional for wiping cache and data, even restoring nandroid but once i get to the galaxy s2 screen it's game over. And of course when charging the phone the battery logo is frozen
Click to expand...
Click to collapse
Nothing is strange about it. The area of flash the /Data partition is mapped to is corrupted at the wearlevelfs level, something that cant be fixed by JTAG. From what I have seen there are 2 levels, the blue light of death and then able to get to recovery and download. The causes are pretty well known, known by Google and some parts of Samsung before we even knew about it.
Have you tried using ODIN to go back to EL26? sometimes EL29 doesn't work when i flash back to that version.
First off, thank you ALL for your replies and attempts to help. It is very appreciated! I odin'd to pretty much every kernel and rom i could. Some got me further than others. The end result was still the same. I get to see either the frozen battery charging icon or samsung galaxy s2 logo and nothing else. I did finally find a stock unrooted EL29 md5 (since everyone is on the one clicks these days) and was able to odin back to stock unrooted with no yellow triangle in hopes that my visit to sprint doesn't bad. This sucks, i can't believe i am hard bricked yet i can odin, get to recoveries, and even flash roms as well as nandroid restore. I looked into the Jtag thing i the post before this one says that's a no go too. Hopefully someone will have a miracle fix or sprint has a heart...
Think those of us with this problem are pretty much screwed...
If this helps anyone out there who may have an answer for me... I had just clean installed AOKP-39 and had a barrage of force closes... I went back into recovery (Actually didn't try flash from ics to ics or ics to gb) to wipe data, cache, ect... and that was the end of my glorious Epic 4g touch! Don't wipe anything people... If you can manage to open mobile odin through all the bs force closes, head back home that way!!!! Still hoping someone has the all spark for my Epic
mremale said:
If this helps anyone out there who may have an answer for me... I had just clean installed AOKP-39 and had a barrage of force closes... I went back into recovery (Actually didn't try flash from ics to ics or ics to gb) to wipe data, cache, ect... and that was the end of my glorious Epic 4g touch! Don't wipe anything people... If you can manage to open mobile odin through all the bs force closes, head back home that way!!!! Still hoping someone has the all spark for my Epic
Click to expand...
Click to collapse
ah, so it looks like you had a bad download of AOKP or a bad flash (they happen) and in your panic forgot to Mobile Odin back and instead you reflashed AOKP from the stock recovery?
Sorry to hear about the brick. It's definitely a good lesson for newer members to read. If you have insurance, at least you'll only have to shell out $60 or so.
Yeah, i think it may have been a bad flash. I don't know what the deal was with all the force close notifications. I didn't try to flash back, i tried to do a wipe and then the trouble came. It was bad after that, so i tried to flash and it was the same situation
To those who have recently suffered a brick due to this issue I will kindly suggest still consider taking your phone to Sprint to ask for replacement. It certainly doesn't hurt to try. As a fallback contact Samsung and you can ask them to fix/replace under warranty.
And just to clarify - is there anyone before this rash of bricks that didn't or wasn't able to get their E4GT replaced? Just curious because it seemed like just about everyone was good.

I read, I watched, I searched, I bricked(Hard)

So just got this phone a couple of weeks ago. I feel like Im no stranger to rooting/flashing, but obviously Im no expert. Ive flashed custom roms on ppc6600, ppc6700, Treo 600w, HTC Diamond, Palm Pre(rooted it, no roms), Samsung Moment, Hero, Evo 4g, Evo 3d, Hp touchpad, and for a few weeks my Epic Touch4g. Ive never had a single problem until today. I must admit when I got this phone, for the first time I was actually scared to root it/flash roms. I read and re-read everything I could find, and finally took the plunge. I had great luck until I tried to flash the jellybean port.
I was originally on Agats rom tFF18_v0.1.0 which I flashed through ODIN. I tried a few other TW roms but ultimately kept Agats rom as my nandroid back up. Since it was a safe kernel/recovery I would always restore my nandroid to do any wipes or flashes. I thought this was being safe.
This morning I updated the kernel with AGAT_v0.3.0 with tREC_v0.2.1 7/19/12, which I flashed through agats recovery. Worked fine. I then wanted to try out CM9. So heres what I did:
I downloaded/flashed the newest nightly and Gapps and flashed them in Agats recovery which worked fine. I loved CM9 so I made a nandroid back up along with my other agat rom backup. I did notice that it was a different recovery but just assumed it was safe since it was a newer nightly. (Mistake?)
I kept CM9 for a few hours and saw that a JB port was available on androidcentral. Had flashed enough without issue, so I thought I try it out.
Heres where I screwed up.
I downloaded the JB port, JB gapps and it said to get chris41g's [Kernel][AOSP] Safe CWM6/TWRP which I did.
First I wiped data(full wipe), cache, and dalvik, then tried to flash the rom in CMW recovery that came with CM9. It gave me an error and aborted the flash.
Then I rebooted the phone back into CM9 because I thought maybe I had a bad download. I went back to the site reread the OP and noticed I was supposed to flash chris41g's recovery first, so I went back into recovery, flashed the Kernel, rebooted back into recovery and tried to flash JB. I didnt wipe anything, I just flashed it. It seemed to do its normal thing, but the progress bar never grew, it just sat there. I let it sit for like 10mins and the next thing I noticed, the screen was off. I picked up the phone, hit the power button.....nothing except the blue light I had read so much about.
I accept full responsibility for what I did. But to be honest, Im really confused what I did wrong. I was under the impression that most bricks happened when doing wipes? This happened when flashing the rom, which Im sure wipes before flashing, so maybe that where I had the problem? Im gonna go to sprint tomorrow and see if they can help, so hopefully Ill get a replacement, but I DONT want it to happen again. Sorry for the MAJORLY long post, but I wanted to be thorough with my explanation so I dont make the same mistake, and maybe someone else could learn from my screw up.
If possible, please be gentle, I already feel like a total idiot.......
EDIT: BTW, if I didnt make it clear, Im COMPLETELY aware this was my fault. I knew what I was getting into, and messed up somewhere by not FOLLOWING directions to a tee.
Your mistake was not wiping anything at the jb flash part.
Plus i think people was flashing jb using the el26 recovery (cwm5) but dont quote me on that i havent read the jb flash procedure throughly
Sent from my SPH-D710 using xda app-developers app
Sometimes stuff like that just happens... Let us know how the replacement goes
Sent from my SGH-I897 using Tapatalk 2
I read somewhere they wont release the jb post on here because of all the bricks that was going on. Tell sprint u prolonged the ics update and ignored it. Then u finally decided to install and it would not boot at all
Sent from my SPH-D710 using xda app-developers app
rovar said:
Your mistake was not wiping anything at the jb flash part.
Plus i think people was flashing jb using the el26 recovery (cwm5) but dont quote me on that i havent read the jb flash procedure throughly
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
Yeah I thought people were using Chris41g's EL26 CWM as well. Sbrissen himself said when in doubt use EL.
Thanks for the responses guys. My phone now has no solid blue light. Just a VERY VERY dim flashing blue light. Its been plugged in for the charger for like 2 hours. Is it possible maybe something just went wrong with battery? It was plugged in when I flashed, and the battery was pretty full, but not topped off...
vinscuzzy said:
So just got this phone a couple of weeks ago. I feel like Im no stranger to rooting/flashing, but obviously Im no expert. Ive flashed custom roms on ppc6600, ppc6700, Treo 600w, HTC Diamond, Palm Pre(rooted it, no roms), Samsung Moment, Hero, Evo 4g, Evo 3d, Hp touchpad, and for a few weeks my Epic Touch4g. Ive never had a single problem until today. I must admit when I got this phone, for the first time I was actually scared to root it/flash roms. I read and re-read everything I could find, and finally took the plunge. I had great luck until I tried to flash the jellybean port.
I was originally on Agats rom tFF18_v0.1.0 which I flashed through ODIN. I tried a few other TW roms but ultimately kept Agats rom as my nandroid back up. Since it was a safe kernel/recovery I would always restore my nandroid to do any wipes or flashes. I thought this was being safe.
This morning I updated the kernel with AGAT_v0.3.0 with tREC_v0.2.1 7/19/12, which I flashed through agats recovery. Worked fine. I then wanted to try out CM9. So heres what I did:
I downloaded/flashed the newest nightly and Gapps and flashed them in Agats recovery which worked fine. I loved CM9 so I made a nandroid back up along with my other agat rom backup. I did notice that it was a different recovery but just assumed it was safe since it was a newer nightly. (Mistake?)
I kept CM9 for a few hours and saw that a JB port was available on androidcentral. Had flashed enough without issue, so I thought I try it out.
Heres where I screwed up.
I downloaded the JB port, JB gapps and it said to get chris41g's [Kernel][AOSP] Safe CWM6/TWRP which I did.
First I wiped data(full wipe), cache, and dalvik, then tried to flash the rom in CMW recovery that came with CM9. It gave me an error and aborted the flash.
Then I rebooted the phone back into CM9 because I thought maybe I had a bad download. I went back to the site reread the OP and noticed I was supposed to flash chris41g's recovery first, so I went back into recovery, flashed the Kernel, rebooted back into recovery and tried to flash JB. I didnt wipe anything, I just flashed it. It seemed to do its normal thing, but the progress bar never grew, it just sat there. I let it sit for like 10mins and the next thing I noticed, the screen was off. I picked up the phone, hit the power button.....nothing except the blue light I had read so much about.
I accept full responsibility for what I did. But to be honest, Im really confused what I did wrong. I was under the impression that most bricks happened when doing wipes? This happened when flashing the rom, which Im sure wipes before flashing, so maybe that where I had the problem? Im gonna go to sprint tomorrow and see if they can help, so hopefully Ill get a replacement, but I DONT want it to happen again. Sorry for the MAJORLY long post, but I wanted to be thorough with my explanation so I dont make the same mistake, and maybe someone else could learn from my screw up.
If possible, please be gentle, I already feel like a total idiot.......
Click to expand...
Click to collapse
I like story's like this that are long very interesting when bored I'm sorry for your lost...try simple small stuff like the stable good looking fully working roms
sent from my DeRpY SuPeRsOnIc
vinscuzzy said:
Thanks for the responses guys. My phone now has no solid blue light. Just a VERY VERY dim flashing blue light. Its been plugged in for the charger for like 2 hours. Is it possible maybe something just went wrong with battery? It was plugged in when I flashed, and the battery was pretty full, but not topped off...
Click to expand...
Click to collapse
Seems unlikely to be the battery, sorry bud :/ seems like your issue was not wiping anything before flashing the jb rom. Not to mention the jelly bean port is unstable as is. And the ics recoveries. I don't care if people say they're safe, i still odin to el26 to flash. I would've stayed away from jb regardless. But thanks for being mature about what happened, you more than most bricks actually seem like you're careful and read.
Swyped from a Galaxy S2
vinscuzzy said:
So just got this phone a couple of weeks ago. I feel like Im no stranger to rooting/flashing, but obviously Im no expert. Ive flashed custom roms on ppc6600, ppc6700, Treo 600w, HTC Diamond, Palm Pre(rooted it, no roms), Samsung Moment, Hero, Evo 4g, Evo 3d, Hp touchpad, and for a few weeks my Epic Touch4g. Ive never had a single problem until today. I must admit when I got this phone, for the first time I was actually scared to root it/flash roms. I read and re-read everything I could find, and finally took the plunge. I had great luck until I tried to flash the jellybean port.
I was originally on Agats rom tFF18_v0.1.0 which I flashed through ODIN. I tried a few other TW roms but ultimately kept Agats rom as my nandroid back up. Since it was a safe kernel/recovery I would always restore my nandroid to do any wipes or flashes. I thought this was being safe.
This morning I updated the kernel with AGAT_v0.3.0 with tREC_v0.2.1 7/19/12, which I flashed through agats recovery. Worked fine. I then wanted to try out CM9. So heres what I did:
I downloaded/flashed the newest nightly and Gapps and flashed them in Agats recovery which worked fine. I loved CM9 so I made a nandroid back up along with my other agat rom backup. I did notice that it was a different recovery but just assumed it was safe since it was a newer nightly. (Mistake?)
I kept CM9 for a few hours and saw that a JB port was available on androidcentral. Had flashed enough without issue, so I thought I try it out.
Heres where I screwed up.
I downloaded the JB port, JB gapps and it said to get chris41g's [Kernel][AOSP] Safe CWM6/TWRP which I did.
First I wiped data(full wipe), cache, and dalvik, then tried to flash the rom in CMW recovery that came with CM9. It gave me an error and aborted the flash.
Then I rebooted the phone back into CM9 because I thought maybe I had a bad download. I went back to the site reread the OP and noticed I was supposed to flash chris41g's recovery first, so I went back into recovery, flashed the Kernel, rebooted back into recovery and tried to flash JB. I didnt wipe anything, I just flashed it. It seemed to do its normal thing, but the progress bar never grew, it just sat there. I let it sit for like 10mins and the next thing I noticed, the screen was off. I picked up the phone, hit the power button.....nothing except the blue light I had read so much about.
I accept full responsibility for what I did. But to be honest, Im really confused what I did wrong. I was under the impression that most bricks happened when doing wipes? This happened when flashing the rom, which Im sure wipes before flashing, so maybe that where I had the problem? Im gonna go to sprint tomorrow and see if they can help, so hopefully Ill get a replacement, but I DONT want it to happen again. Sorry for the MAJORLY long post, but I wanted to be thorough with my explanation so I dont make the same mistake, and maybe someone else could learn from my screw up.
If possible, please be gentle, I already feel like a total idiot.......
EDIT: BTW, if I didnt make it clear, Im COMPLETELY aware this was my fault. I knew what I was getting into, and messed up somewhere by not FOLLOWING directions to a tee.
Click to expand...
Click to collapse
Where did you have the JB ROM located, on your internal memory or your SDcard?
And wait, Flashing blue light? When mine bricked using the same methods you were using, save for the lack of wiping and I used calk's wipeall before flashing, I had a solid blue light.
Eh, Least now I have a paperweight with a nice light on it for now.
Ophois said:
Where did you have the JB ROM located, on your internal memory or your SDcard?
And wait, Flashing blue light? When mine bricked using the same methods you were using, save for the lack of wiping and I used calk's wipeall before flashing, I had a solid blue light.
Eh, Least now I have a paperweight with a nice light on it for now.
Click to expand...
Click to collapse
it was on the internal memory. And yeah, its weird. It started as a solid blue light for like an hour. I plugged in the charger and a few hours later I thought the light was completely off, but if you look real close, its a super dim flashing blue light.
vinscuzzy said:
it was on the internal memory. And yeah, its weird. It started as a solid blue light for like an hour. I plugged in the charger and a few hours later I thought the light was completely off, but if you look real close, its a super dim flashing blue light.
Click to expand...
Click to collapse
Alright, That's two people who got a brick and had flashed it from their internal.
I'll try and get ahold of the other user who bricked their device and find where they had it and from there, We'll know a probable cause and how to prevent it.
I flashed sb's jb from internal. no problem here.
on el26.
please not I am not trying to be a wise ass; however have you read through this post http://forum.xda-developers.com/showthread.php?t=1525495 ? I have "bricked" a few times and have been able to revive my phone using Odin (the pc version). seems as long as you can get the phone into "download" mode (volume rocker down and power button) be sure to check out QBKing77's posts on YouTube. you have nothing to lose and everything to gain
good luck
al_b said:
please not I am not trying to be a wise ass; however have you read through this post http://forum.xda-developers.com/showthread.php?t=1525495 ? I have "bricked" a few times and have been able to revive my phone using Odin (the pc version). seems as long as you can get the phone into "download" mode (volume rocker down and power button) be sure to check out QBKing77's posts on YouTube. you have nothing to lose and everything to gain
good luck
Click to expand...
Click to collapse
Yeah, that was the post that scared me to even root the phone. I can't get into download mode, and have been trying every combination of turning it on, vol up/dwn, plugging it in without the battery, tried different cables, chargers, scoured all the different Samsung forums to see if there was a way to force into download mode, nothing. Its completely dead. I got this phone right around the time the kernel source got released and that post hasn't been updated since may, so I kinda came to the conclusion(stupidly) that maybe the problem had been fixed. I wasn't around for all the leaks that were causing the bricks.
not being able to get into download mode = not good. there are also dongles out there that cost $5 +/-. might work. I believe you mentioned you have insurance, if that is true take the device to your local corporate Sprint store and play "Micky the dunce" i.e. I have no idea what happened to it; I was updating my PRL and this is what happened ... of course if you accidently backed over it with your car on the way to the store that may dissuade them from trying to resurrect it
vinscuzzy said:
Yeah, that was the post that scared me to even root the phone. I can't get into download mode, and have been trying every combination of turning it on, vol up/dwn, plugging it in without the battery, tried different cables, chargers, scoured all the different Samsung forums to see if there was a way to force into download mode, nothing. Its completely dead. I got this phone right around the time the kernel source got released and that post hasn't been updated since may, so I kinda came to the conclusion(stupidly) that maybe the problem had been fixed. I wasn't around for all the leaks that were causing the bricks.
Click to expand...
Click to collapse
the MMC_CAP_ERASE code that causes the emmc controller to bug out and brick is still present in the FF18 kernel, entropy512 has been in contact with samsung about this, but last time i read the emmc thread a a few days ago he was still having difficulty convincing samsung that it was actually their code directly causing all these bricks... sorry about the brick, I just spent some time with cm10 and the vanilla jb rom and thanks to you and the other gentleman that bricked flashing from internal sd I double checked that the zips were on the external... so at least you've helped some of us out! good luck with sprint
does DirectoryBind_0.2.0k.apk help with the EMMC freakiness? a month or so ago this was useful work around. http://forum.xda-developers.com/showthread.php?t=1410262&highlight=directorybind
gershee said:
I flashed sb's jb from internal. no problem here.
on el26.
Click to expand...
Click to collapse
That is the difference, The other two and I appear to have flashed it from internal but we were using CWM6.
I guess CWM6+Internal=brick whereas EL26+Internal=good to go
Though this is all conjecture, I cannot be completely sure with such a small sample size.
When I was little I once had a jelly bean stuck in my nose.
Good luck.
Pp.
Delivered to you via Mayan technology .
No worries happened to me too( sadly :/). On the lighter/much, much darker side[you choose] sprint reps. won't be able to look at your phones files probably. When it happened to me the tech just came out with the 'WTF?' face and said what did you do, to which I replied "I applied the EL29 update and my phone bricked" cheers.
Sent from my Galaxy S2 E4GT

ICS update from sprint STUCK IN BOOTLOOP!

This is amazing, I just got a replacement ET4G from sprint. I was hesitant to flash anything, cuz my last one bricked, blue light, completley dead. So I was waiting for something to tickle my fancy IE a stable JB rom, or maybe just boredom. I woke up this morning, and low and behold... the update was waiting for me. Already downloaded, just waitin for me to install. I knew at some point Id be flashing a rom, so I almost didnt take it, but then I decided, well this way Ill have the newwest modem, bla, bla, bla. So I applied the update, and boom... stuck in a bootloop. HAHA! Anyway, does anyone where it downloads the update? I think is on the root of my sd card, but theres nothing with todays date on there. I found a file from 7-20 called update.zip, but Im worried that was from my old ET4g... Im scared to flash it again, cuz what if Im wrong???? Is it safe to do a factory reset in recovery? Or am I at risk to get hit with the EMMC bug???
Can you get into odin/download mode?
Sent from my SPH-D710 using Tapatalk
Click here for custom mods for your E4GT
vinscuzzy said:
This is amazing, I just got a replacement ET4G from sprint. I was hesitant to flash anything, cuz my last one bricked, blue light, completley dead. So I was waiting for something to tickle my fancy IE a stable JB rom, or maybe just boredom. I woke up this morning, and low and behold... the update was waiting for me. Already downloaded, just waitin for me to install. I knew at some point Id be flashing a rom, so I almost didnt take it, but then I decided, well this way Ill have the newwest modem, bla, bla, bla. So I applied the update, and boom... stuck in a bootloop. HAHA! Anyway, does anyone where it downloads the update? I think is on the root of my sd card, but theres nothing with todays date on there. I found a file from 7-20 called update.zip, but Im worried that was from my old ET4g... Im scared to flash it again, cuz what if Im wrong???? Is it safe to do a factory reset in recovery? Or am I at risk to get hit with the EMMC bug???
Click to expand...
Click to collapse
The latest update goes into /cache internally. (It's been pulled out in the last few weeks to look for changes) But it should be gone once applied.
As far as the brick issue - sfhub says the risk is still there. Personally, I have done a reset and not bricked. Others have reset with no brick.
I'd take sniper's suggestion on getting to download mode and using a one click.
MoHoGalore said:
The latest update goes into /cache internally. (It's been pulled out in the last few weeks to look for changes) But it should be gone once applied.
As far as the brick issue - sfhub says the risk is still there. Personally, I have done a reset and not bricked. Others have reset with no brick.
I'd take sniper's suggestion on getting to download mode and using a one click.
Click to expand...
Click to collapse
Yeah, i wasnt around a computer b4, but i got to one and one clicked ff18. Funny though, i actually(for the 1st time ever) took a major os update, and it fails. Good job Sprint! Oh well, at least xda is here to help.

[Q] Tmobile Samsung Galaxy S3 bricked after install of LiquidSmooth

Hey guys,
So I desperately need some help here. I rooted my phone using the ODIN method, which worked fine. I put 2 ROMS on the internal memory in order to see which I liked best. I was only able to install one before my phone started heading downhill.
Basically after installing LiquidSmooth (the "stable" one) my phone started wigging out: not letting me access the external SD card (it didn't even see that I had one, and I popped it to reset it), not letting me even open a web browser, saying I had no connection via 3G (which is strange because it's a 4G phone, and it stated so before I installed LiquidSmooth) and just generally not letting me do anything.
Logically I figured I'd just replace the ROM with another, so I tried to install the "Pac-Man" d2tmo ROM... but LiquidSmooth was the only one starting up, no matter what I did (soft reboot, factory restore from keypad, UP vol + power + home, and even from inside the phone settings.) Nothing worked. I even tried to recover a backup I had made before I installed LiquidSmooth, but the menu just kept saying no data present (which is especially odd, since I even put the backup on my desktop, but I just can't get the phone to run it)
I figured, okay well maybe I'll just have to restore from the vol + pow + home screen. Bigger mistake. Now my phone won't boot at all, and I'm at a loss for words. I've rooted other phones with no issue before (I even had to recode a bit of a "one-click" program to root my ol' Galaxy S Vibrant) and now I just don't know what to do.
Here's what I need to know: If I can recover to factory (and if so, what other ROMs are good... I was mislead by everyone saying LiquidSmooth was great *grrr*), and if not, what exactly are my options to get this thing running at all.
Oh, and I was running Jellybean 4.1.1 and it got bumped to 4.2.2 when I installed LiquidSmooth, if that helps at all.
Thanks so much for any and all help.
OneIdiotInATree said:
Hey guys,
So I desperately need some help here. I rooted my phone using the ODIN method, which worked fine. I put 2 ROMS on the internal memory in order to see which I liked best. I was only able to install one before my phone started heading downhill.
Basically after installing LiquidSmooth (the "stable" one) my phone started wigging out: not letting me access the external SD card (it didn't even see that I had one, and I popped it to reset it), not letting me even open a web browser, saying I had no connection via 3G (which is strange because it's a 4G phone, and it stated so before I installed LiquidSmooth) and just generally not letting me do anything.
Logically I figured I'd just replace the ROM with another, so I tried to install the "Pac-Man" d2tmo ROM... but LiquidSmooth was the only one starting up, no matter what I did (soft reboot, factory restore from keypad, UP vol + power + home, and even from inside the phone settings.) Nothing worked. I even tried to recover a backup I had made before I installed LiquidSmooth, but the menu just kept saying no data present (which is especially odd, since I even put the backup on my desktop, but I just can't get the phone to run it)
I figured, okay well maybe I'll just have to restore from the vol + pow + home screen. Bigger mistake. Now my phone won't boot at all, and I'm at a loss for words. I've rooted other phones with no issue before (I even had to recode a bit of a "one-click" program to root my ol' Galaxy S Vibrant) and now I just don't know what to do.
Here's what I need to know: If I can recover to factory (and if so, what other ROMs are good... I was mislead by everyone saying LiquidSmooth was great *grrr*), and if not, what exactly are my options to get this thing running at all.
Oh, and I was running Jellybean 4.1.1 and it got bumped to 4.2.2 when I installed LiquidSmooth, if that helps at all.
Thanks so much for any and all help.
Click to expand...
Click to collapse
Did you flash the latest recovery? Did you wipe data when flashing to a 4.2.2 aosp ROM from 4.1.1 tw? You'll need to do that before and not dirty flashing. Have you done a battery pull? And then tried to enter recovery?
Sent from my SGH-T999 using xda app-developers app
monkeypaws said:
Did you flash the latest recovery? Did you wipe data when flashing to a 4.2.2 aosp ROM from 4.1.1 tw? You'll need to do that before and not dirty flashing. Have you done a battery pull? And then tried to enter recovery?
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
It auto-wiped to upgrade to 4.2.2, so if there is a way to downgrade it to get it to work, I'd love to know. At the moment all I can access is the Clockwork Mod boot list from the vol+pow+home route. Did a battery pull and entered recovery. Still nothing. If I try to boot without going through the vol+pow+home method, it just vibrates and then nothing.
Update recovery.
Wipe everything except sd cards.
Install rom.
Install Gapps.
Factory reset.
Done.
Aerowinder said:
Update recovery.
Wipe everything except sd cards.
Install rom.
Install Gapps.
Factory reset.
Done.
Click to expand...
Click to collapse
I formatted everything from that vol+pow+home menu.
Gapps? Is that something I should install from SD?
Sorry, I'm just a bit overwhelmed by something I thought would be easy...
OneIdiotInATree said:
I formatted everything from that vol+pow+home menu.
Gapps? Is that something I should install from SD?
Sorry, I'm just a bit overwhelmed by something I thought would be easy...
Click to expand...
Click to collapse
Gapps are Google apps that are required to flash after flashing an aosp ROM. They are usually included as a separate download in the first post of the wrong you are downloading. Make sure you download the right gapps. There shod be a setti ng in cwm to turn on USB connection when connected to comp. So you can load the gapps to your SD card. Then re wipe phone through recovery, reflash the rom , the in the same menu reflash gapps. Then reboot. It should then load properly . Otherwise. If you can access download mode, restore stock rom with Odin, reroot and try again from step one.
Sent from my SGH-T999 using xda app-developers app
If you fix your phone try using twrp instead of cwm thats what i had to do and DL the 2013 version of gapps. I have the latest pacman ROM and the only thing i had to do after install was clear data and cache for the rom control via apps-all-rom control. Well hope this helps.
Sent from my SGH-T999 using xda app-developers app
SamsungGui said:
If you fix your phone try using twrp instead of cwm thats what i had to do and DL the 2013 version of gapps. I have the latest pacman ROM and the only thing i had to do after install was clear data and cache for the rom control via apps-all-rom control. Well hope this helps.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
Alright, I just installed both LiquidSmooth again followed by GApps, factory reset the phone, and restarted. Now the phone will not start up (even the vibration) or allow a shift into cwm. Why did this happen? Is there a way to reverse this since now I've lost the ability to even access the cwm?
At this point, I just want to restore to the original loadout, but I've been unable to do that too.
By the way, I do appreciate all the advice on this problem. I'm frazzled beyond belief and have a very expensive paperweight currently.
OneIdiotInATree said:
Alright, I just installed both LiquidSmooth again followed by GApps, factory reset the phone, and restarted. Now the phone will not start up (even the vibration) or allow a shift into cwm. Why did this happen? Is there a way to reverse this since now I've lost the ability to even access the cwm?
At this point, I just want to restore to the original loadout, but I've been unable to do that too.
By the way, I do appreciate all the advice on this problem. I'm frazzled beyond belief and have a very expensive paperweight currently.
Click to expand...
Click to collapse
Make sure you have the ROM of choice and compatible Google apps on your SD card.
Now do the following
1. Pull battery out of phone
2. Put battery into phone
3. Boot into recovery (volume +, home button, power button)
4. Wipe cache
5. Wipe dalvik cache
6. Wipe data/factory reset
7. Install ROM
8. Install gapps (Google apps)
9. Wipe cache
10. Wipe dalvik cache
11. Reboot phone
Once booted up and logged into Google account, go to play store, search for goo manager, download goo manager, open goo manager and press the menu button and install the open recovery script....now you'll have twrp (team win recovery project).
|When Emotion Goes Up, Logic Goes Down|
|Even If You Fall Face First You're Still Moving Forward|
707BeastMode707 said:
Make sure you have the ROM of choice and compatible Google apps on your SD card.
Now do the following
1. Pull battery out of phone
2. Put battery into phone
3. Boot into recovery (volume +, home button, power button)
4. Wipe cache
5. Wipe dalvik cache
6. Wipe data/factory reset
7. Install ROM
8. Install gapps (Google apps)
9. Wipe cache
10. Wipe dalvik cache
11. Reboot phone
Once booted up and logged into Google account, go to play store, search for goo manager, download goo manager, open goo manager and press the menu button and install the open recovery script....now you'll have twrp (team win recovery project).
|When Emotion Goes Up, Logic Goes Down|
|Even If You Fall Face First You're Still Moving Forward|
Click to expand...
Click to collapse
I finished most of these steps, but when I rebooted my phone after installing both LiquidSmooth and Gapps, it refused to start. Now I can neither turn it on or go back into recovery mode. The phone is just dead now. What would cause this? I've taken the battery (and everything else for that matter) out again and again, charged it for the last hour, and nothing has changed.
Okay follow this to get to stock and make sure it can at least do that. http://forum.xda-developers.com/showthread.php?t=2136921
Sent from my SGH-T999 using xda app-developers app
OneIdiotInATree said:
I finished most of these steps, but when I rebooted my phone after installing both LiquidSmooth and Gapps, it refused to start. Now I can neither turn it on or go back into recovery mode. The phone is just dead now. What would cause this? I've taken the battery (and everything else for that matter) out again and again, charged it for the last hour, and nothing has changed.
Click to expand...
Click to collapse
Are you sure you have a T-Mobile phone?
monkeypaws said:
Okay follow this to get to stock and make sure it can at least do that. http://forum.xda-developers.com/showthread.php?t=2136921
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
Thanks for the set of instructions, but I am unable to either start it (power button), put it in cwm (pwr+up+home) or download mode as mentioned (pwr+down+home). I don't get a vibration; I don't get anything. Is this totally bricked now? Since the device isn't on, I can't do anything with Odin or the SD card.
What country do you live in, and how did you acquire your phone? Looks like you maybe have the intl version.
I would say try to get into download mode with the physical bottons if that dint work try a jig u can get on ebay like 5 bucks they are always handy.if u can get in to dl mode odin a root66.tar then install recovery.if that dobt worj u prib install liquid rom but fir diff device abd hard brixk u f that case hope u have insurance ti replace they will never know u rooted ir have it jtaged
Its bricked, jtag repair only way .
Stop flashing in my opinion theres a huge issue with the t999 rom compatility and someone mentioned of tw roms being labeled as aosp.roms,I would root but stay away from flashing.until someone figures this out .Theres way to many brick topics lately i find to be oddly connected to the same causes .
Some will say bs but trust me theres something going on..even the most experienced flashers are bricking the t999 its to me the most easiest brickable device i ever delt with.
lojak29 said:
Its bricked, jtag repair only way .
Stop flashing in my opinion theres a huge issue with the t999 rom compatility and someone mentioned of tw roms being labeled as aosp.roms,I would root but stay away from flashing.until someone figures this out .Theres way to many brick topics lately i find to be oddly connected to the same causes .
Some will say bs but trust me theres something going on..even the most experienced flashers are bricking the t999 its to me the most easiest brickable device i ever delt with.
Click to expand...
Click to collapse
it honestly sounds like he has he international version not the US variant. so i think thats the mistake not the phone
lojak29 said:
Its bricked, jtag repair only way .
Stop flashing in my opinion theres a huge issue with the t999 rom compatility and someone mentioned of tw roms being labeled as aosp.roms,I would root but stay away from flashing.until someone figures this out .Theres way to many brick topics lately i find to be oddly connected to the same causes .
Some will say bs but trust me theres something going on..even the most experienced flashers are bricking the t999 its to me the most easiest brickable device i ever delt with.
Click to expand...
Click to collapse
99% of the bricking is user error...the reason for the increase in "bricked" topics is cause by the amount of users of the T999...its the most heavily used phone by a wide margin now.
Ive far from an expert but have been flashing since the G1 days and have experience with many phones...in my opinion the t999 is darn near unbrickable unless you didnt follow the directions or use a reputable developer when selecting a rom...
To the OP:
What is the actual model of your phone ? you came with an issue and have not really posted much about the specifics of your phone...
sounds like your phone is not partitioned correctly which probably happened by not following the correct directions
there is so much more info needed to diagnose your issue its silly...
Ive been using wicked roms from day one on the t999 and I dont remember seeing anyone hardbrick a phone yet and there are thousands of users using wicked roms...
---------- Post added at 10:58 AM ---------- Previous post was at 10:16 AM ----------
Also...was your phone charged when you last tried to flash something? long ago my phone died while flashing ( lessoned learned) ...
pull the battery for awhile...put it back in and try to charge it...
then try to odin back to stock after its charged...
Even if AOSP and TW ROMs were labelled wrong... what difference would it make ? Sure, it could be misleading and all but it's hardly going to brick a phone just give you something you might not have exactly wanted (if that's even actually happening).
I also wonder if this phone is actually an International version instead of the T-Mobile one.
OP, it looks like you need JTAG repair now. If you don't honestly know what exact model you have talk to the JTAG repair service people about it - since they can most likely JTAG either they can just tell you which phone you have once they've fixed it.
Pennycake said:
Even if AOSP and TW ROMs were labelled wrong... what difference would it make ? Sure, it could be misleading and all but it's hardly going to brick a phone just give you something you might not have exactly wanted (if that's even actually happening).
I also wonder if this phone is actually an International version instead of the T-Mobile one.
OP, it looks like you need JTAG repair now. If you don't honestly know what exact model you have talk to the JTAG repair service people about it - since they can most likely JTAG either they can just tell you which phone you have once they've fixed it.
Click to expand...
Click to collapse
OP just has to remove the battery cover and battery and bam! There's a label with Sammy's logo along with device model and other info about the phone.
|When Emotion Goes Up, Logic Goes Down|
|Even If You Fall Face First You're Still Moving Forward|

Categories

Resources