Database Users

[Q] Bricked my "epic"

yeah I am pretty sure I bricked my epic, I can't get it to boot it just goes to a screen that show a cell phone and a pc with a triangle and an exlamation mark inbetween them, I can boot into download and would flash with odin but neither of my computers will not recognize the "epic", just says unknown device i the device manager of my pc's, also if I plug in the usb while it's off it will boot into clockwork recovery and I can install a recovey but as soon as I reboot it it goes back to the phone, computer, and triagle with the exlamation mark screen... Anyone have an ideas of what to do ? ? ?

You should have "bricked" in quotes, not Epic. :-D
If you can get into download mode, then it's not truly bricked. I went through the same panic first time trying to use Odin. It is really flaky, just keep trying. Keep rebooting the phone and the computers. Try different versions of Odin, try different USB ports, try different USB cables. Uninstall and reinstall the Samsung drivers, stand on one foot while patting your head and clicking start. Any damn random variable you can think of. Just when you're about to bounce your Epic off the wall, it will magically work. I think Odin is fueled by tears and frustration.

Bricked - it means that your device is as useful as a brick. there is nothing you can do with it save for making various youtube videos about breaking said device...
if your intrested in seeing a a true brick looks like delted the flash and off your psp (3k and pspgo) or install a lower foreign version of the wii system menu on a brand new wii. better yet download a bio flashing utility (doesnt matter which one preferably the one FOR your computer) and halfway thru unplug the computer.. then you may understand what a brick is.
this is nothing personal but honestly after teh whole dk05 leak your probably the 15th person ive read that posted something along the lines of "ZOMG i bricked my phone it turns on and stuff and theres guides on how to fix it but itz brickeddd!!"

i like "paratheticals" when they arent really "required". i think its "funny".

shabbypenguin said:
Bricked - it means that your device is as useful as a brick. there is nothing you can do with it save for making various youtube videos about breaking said device...
if your intrested in seeing a a true brick looks like delted the flash and off your psp (3k and pspgo) or install a lower foreign version of the wii system menu on a brand new wii. better yet download a bio flashing utility (doesnt matter which one preferably the one FOR your computer) and halfway thru unplug the computer.. then you may understand what a brick is.
this is nothing personal but honestly after teh whole dk05 leak your probably the 15th person ive read that posted something along the lines of "ZOMG i bricked my phone it turns on and stuff and theres guides on how to fix it but itz brickeddd!!"
Click to expand...
Click to collapse
Well put. Not bricked. Did you install the samsung drivers? Please read the the section on rooting and recovery....
http://forum.xda-developers.com/showthread.php?t=798067
....followed by the ODIN thread
http://forum.xda-developers.com/showthread.php?t=773032

Those are not "paratheticals". They are "quotes". (this is parenthetical)
austin420 said:
i like "paratheticals" when they arent really "required". i think its "funny".
Click to expand...
Click to collapse

"nice"
D)

Sounds like you didn't have the sammy drivers installed.

I was trying to put 2.2 on my epic and crashed
I was trying to put 2.2 on my epic the entire device went blank and will not turn on or show that it is being charged. would you consider that completely bricked?

Try a battery pull. Worked for me.
Sent from my SPH-D700 using XDA App

if it boots into recovery and download there is a way to save it... if you cannot get to either of those then your Fu*ked lol... like it was said before follow the links in the wiki and they will guide you... it just seems like your having a driver issue, try a different cord, worked for me when i had the same issue. the one that came with the phone sucks for connecting to pc, find a shorter cord and it should work

Bricked epic4g using odin

I know there are various threads like this one but my situation is a bit different. I tried using odin to clean install 2.2 to then use the custom rom epic experience. I attempted to install 2.2 using odin but it would get stuck in "setup connection" and I would have to quit and try again. Last time I tried my phone got the "phone connection caution computer" icon and to get into recovery I would have to hold the power and camera button, not the volume down button. When I go to try and install things straight from my SD card I would get an error like "status 7" cus I didn't have the sprint apps to install 2.2. I believe I get these errors installing straight from the card cus I rooted my phone, modifying the kernal cus I read somewhere because when trying to update, it tries to verify but can't cus things are missing or edited cus of the root. I can't try to use odin again because my computer can't recognize the phone anymore regardless reinstalling the samsung drivers. SOOOO, I'm basically ****ing stuck for sure I think. The way I access the SD card is by using an adapter. The only way I see this working is if I find a fix using the SD card, but it's looking slim cus of the stupid root.

I don't know much about this yet, as I'm still learning myself. Did you try using another usb port and are you putting the phone in download mode?. Restart the computer and the phone. Make sure odin is running before you plug in the phone as well. And try another usb port. Are you using the cable that came with the phone? That one trends to have problems for some people.
Edit: I don't believe your phone is bricked either, people tend to throw the word around to much because that arnt quite sure about the definition. Just hang in there and the community will help you get back up and running. Good luck
Sent from my shoe, I mean....Epic shoe... I mean Samsung Epic!

mxcoldhit said:
I don't know much about this yet, as I'm still learning myself. Did you try using another usb port and are you putting the phone in download mode?. Restart the computer and the phone. Make sure odin is running before you plug in the phone as well. And try another usb port. Are you using the cable that came with the phone? That one trends to have problems for some people.
Edit: I don't believe your phone is bricked either, people tend to throw the word around to much because that arnt quite sure about the definition. Just hang in there and the community will help you get back up and running. Good luck
Sent from my shoe, I mean....Epic shoe... I mean Samsung Epic!
Click to expand...
Click to collapse
You see, I'm out of options. Last thing I thought of was installing a custom rom 2.1 rom cus 2.2 roms need odin, but I try to install and I get a signature error or whatever. I'm about to throw the phone against the wall, crack the screen, and use my warranty and get a new phone cus I literally tried EVERYTHING. I spent my ****ing 8 hours of my saturday trying to fix this.

Try a different computer my new Dell XPS 9100 will never reconize my Epic, however, my wifes laptop will always reconize it. I know that sounds weird, I always thought I had a poblem with my phone but it ended up being my computer.
Sent from my SPH-D700 using XDA App

cbpagent72 said:
Try a different computer my new Dell XPS 9100 will never reconize my Epic, however, my wifes laptop will always reconize it. I know that sounds weird, I always thought I had a poblem with my phone but it ended up being my computer.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
omfg, I used my mom's lappy and the drivers worked. Meaning I can try and use an odin fix.

Odin can be tricky to use because of a few factors other than itself. 1) if you can, use a deskto pc and attach to a usb port literally on the motherboard, no front or pci, this may work, but this I what I found (reading countless threads) to be the most failsafe for everyone. 2) your sammy usb cable is for charging or non critical data transfer ONLY, as it is garbage... repeatedly proven in the threads. 3) reboot pc and phone, boot phone into download mode, (hold down 1. On physical keyboard and press power... DO NOT CONNECT YET! Start up odin, place files where needed (.pit, etc...) uncheck all but what you're told in the flashing instructions with the file you're flashing, most have awesome detals, but sometimes your little issue is resolved on page 50 of the thread... not in the OP. Ok so now plug in the usb connection, odin should find it. If it doesn't, search for drivers, uninstall, reinstall start over, OR you have a bad connection, refer back to usb port and cable. I have 1 out of 4 mobo usb ports that the drivers will maintain a connection to, so try another. Then, once odin has a connection, make sure you're following the guides to the T (and read all the posts)... after that, odin is your best friend. The problem lies elsewhere... odin is the goods. If you have run into problems maintaining connection, and plan to re-root, read all the one click posts and if it drops connection a lot, enter the commands in one by one, repeat if one fails till it sticks. There are way better guides, but you seem to have run into the same issues I did, and after hours and hours, I got that scary ass reconnect me now screen. Just read the whole threads, and if your problem hasn't already been resolved, post in the appropriate thread, so others may learn from your discoveries!
Don't give up, once you figure out the quirks of the relationship between your pc and phone, and of course meticulously follow instructions, your elation when successful will make you forget that pesky 'bricked' screen... trust me I got it too, and no matter how much everyone says you can't brick these following instructions on here... its still scary till it all works. If things are wonky, wipe, go back to DI18 and start over... or just sit tight for froyo roms... good luck!
Oh, and sorry for no links, but it would seem you've probly already read em all... not sure I can do links...

Maybe its just my eeepc that doesn't like the drivers, good luck! Sounds like you're on the way... oh don't forget with the drivers to let em install on connect, leave it plugged in for like 10 mins, unplug, it will then complain it wasn't done, reconnect, then after that finishes, reboot. Crazy drivers...

At least I got a computer recognizing my phone, so I can try and use odin. I've been trying to use this fix
http://forum.xda-developers.com/showthread.php?p=9755894#post9755894
and so far odin has been stuck at this one step "file analysis..."

Yeah I used that method to no avail, but it was about 3 pasts old at the time, so I figured id try
something more stable. Tried a couple dk17 roms, then went back to 2.1 and am now using syndicate xtreme. Id suggest going back to DI18, then go from there. Let me check for another post of mine, theres a dialer code I had to do too at one point...
Ok when doing one click root, someone suggested ##8778# in the dialer, then keyboard enter, then set UART to pda not modem. This and removing comodo firewall, all the sudden my intermittent connection was solid. Not responsible for what this does, but it worked for me. Never found out what it does..... still curious. So this may help you even in odin, try to flash di18 after doing this, then the all in one rom you're looking at...

Oddly enough, I managed to semi-brick my phone several hours ago - my wireless adapter was on the same USB header, and both the wireless adapter and the phone crapped out while trying to flash with Odin.
Thankfully I was still able to get into download mode, and plugging the phone into a different USB port worked fine.

After some more research, about 10 hours of it, odin finally cooperated with me after I downloaded about every kind of file that could make my phone work and finally got it into 2.1
I first flashed the stock kernal to get it working, then flashed stock 2.1
Now I'm that my phone isn't rooted anymore I tried installing 2.2 through the recovery menu and I still get error status 7. Any ideas?

Probly best to post in the thread for the package/rom you are trying to install... others using it should be able to help... or you can do a 2.1 rom and wait for a final froyo based rom... glad to hear you're not bricked... the only way I've heard you can absolutely do that with these is installing a GSM rom or something crazy like that... but non-functional phone is scary regardless...

ungovernable1977 said:
Probly best to post in the thread for the package/rom you are trying to install... others using it should be able to help... or you can do a 2.1 rom and wait for a final froyo based rom... glad to hear you're not bricked... the only way I've heard you can absolutely do that with these is installing a GSM rom or something crazy like that... but non-functional phone is scary regardless...
Click to expand...
Click to collapse
Alright I completely fixed my phone. After I rooted my phone on 2.1, I then used odin v1.6 to install the froyo .tar file into pda and it worked. I then rooted it again so now I'm back to normal. Honestly, I did so many things I forgot what I did but I now have my phone functional. Thanks for help everyone, I greatly appreciate it!

[Q] Having second thoughts

To start off with I have had my phone rooted since my g1 in 2009. I did not hesitate to root my mytouch earlier this month and it was successful. Unfortunately, my phone would no longer boot (not turn on at all) after a week of being rooted. I am not sure if rooting caused the error but now I am afraid to root my replacement. I wanted to at least flash my backup but I am afraid to even root for that. Also I should add that I root to flash roms not because I think it's "cool". Can anyone give me advice on if I should root again?

What did you flash right before the phone would not boot or turn on at all? Perhaps it is not the root but the roms that you are flashing. I certainly am not an expert but perhaps you might just try rooting and than wait a few days before trying to flash any roms. Also all that I have read states that you should read up on all the procedures and follow them to the letter. I have had that brought to my attention in a couple of instances. I just received my replacement (screen issues) and have rooted it again and so far things seem okay. I am going to wait and read and learn more before I flash a rom again. Good luck!!

tenbeau said:
What did you flash right before the phone would not boot or turn on at all? Perhaps it is not the root but the roms that you are flashing. I certainly am not an expert but perhaps you might just try rooting and than wait a few days before trying to flash any roms. Also all that I have read states that you should read up on all the procedures and follow them to the letter. I have had that brought to my attention in a couple of instances. I just received my replacement (screen issues) and have rooted it again and so far things seem okay. I am going to wait and read and learn more before I flash a rom again. Good luck!!
Click to expand...
Click to collapse
Yeah, I had flashed the hd port after using the z port and that's when the issues started. I think I will root again and just try to be more careful even though i am pretty sure I followed all instructions.m

Sounds like to me it was just timing between phone hardware and your flashing. Unless you are screwing around with with the ROMs prior to flashing without knowing what your doing you should have no issues. If it was ROM related you would see these boards all lit up with people having the same issues...and you simply dont see that.

[Q] Did Alpharev just brick my phone?? Please help!

Ooookay, so I'm really hoping I don't have a bricked phone here, but it isn't looking too good.
I have a Bell Legend and I decided to try the modified alpharev iso to S-OFF my phone. Using the counting method I managed to get through the first two steps just fine, but at step 3 my timing must have been off and the phone froze, not letting me hit fastboot. I kept trying, and waited another 20 minutes, but after it was obvious nothing would happen, I pulled the battery to start over.
I was able to fake-flash my way back into clockwork recovery and then restored a previous nandroid backup, but my phone simply would not boot back into the OS after the restore, it just hangs at the HTC logo indefinitely. I let it sit for over half an hour and still NOTHING.
Is my phone bricked? If not, is there anything I can do to fix this?

Oh, and if it helps, when the alpharev utility prompted me about whether I wanted to flash its custom clockworkmod recovery I said yes.. not sure if that was the right call.
And I never got to/through step 3 of the flash, and that's supposedly the only part of the process during which bricking the phone could occur, so I'm pretty lost on what's happening here, but I would really appreciate some help :S

If you are still able to turn it on I guess you haven't bricked your phone.
Btw your thread title is wrong, Alpharev never brick your phone. It is you as the user that brick it, you should know the risk (mentioned very clearly) and yet still attempt the procedure.
Sent from my Legend using Tapatalk

Maybe my memory is off or the procedure for Bell Legends are different, but aren't the 3rd step straight foreward? I mean no timing? Anyway I don't think your phone is bricked, unless you pulled the connection/battery after the procedure started flashing the bootloader.
Edit: I see that you never got to step 3 if I understand correctly. Maybe wiping and reflashing helps.
Sent from my Legend using XDA App

Just run the alpharev once more to try for step 3 again.. tried several times myself before getting the timing right.. as yes as mentioned.. Alpharev never brick phones.. Users does..
Sent from my Legend using XDA App

fatthumb said:
If you are still able to turn it on I guess you haven't bricked your phone.
Btw your thread title is wrong, Alpharev never brick your phone. It is you as the user that brick it, you should know the risk (mentioned very clearly) and yet still attempt the procedure.
Sent from my Legend using Tapatalk
Click to expand...
Click to collapse
Yes, I'm very much aware that it was my own silly actions that led to my predicament and I in no way blame the alpharev team, they've done a great job. I just made that the thread title so that people would be aware of what I was doing before I messed up my phone, but again, totally my fault, not alpharev's
Anyways, I've solved the problem, probably won't try to S-OFF my phone again until I do some more reading.

MaBlo said:
Maybe my memory is off or the procedure for Bell Legends are different, but aren't the 3rd step straight foreward? I mean no timing? Anyway I don't think your phone is bricked, unless you pulled the connection/battery after the procedure started flashing the bootloader.
Edit: I see that you never got to step 3 if I understand correctly. Maybe wiping and reflashing helps.
Sent from my Legend using XDA App
Click to expand...
Click to collapse
No, your memory is spot on, I'm mistaken. I meant steps 1 and 2, I guess I didn't make it to step 3. If I messed up at step 3 only THEN would I have been completely screwed. Fixed the problem, I must have had a corrupt nandroid backup. Restored an earlier backup and now the phone is running fine. Premature panicking!

[Q] Downgraded, Next Step: Debranding

I have one of those Legends that require a downgrade before you root, but I decided to chicken out and after I downgraded to 1.31 or whatever it was, I decided to debrand my Bell Legend and chicken out to get the worldwide Froyo OTA. Plus, it was getting late, I didn't want to accidentally screw up the rooting because I was tired.
Anyway, after I downgraded, I installed a system update that brought me to Eclair-update-1. I don't think that was a really good idea.
Because afterwards, when I tried installing the debranded RUU from the debrand thread, it resulted in an error and I have to keep what I have right now.
UNLESS YOU GUYS HELP.
What did I do wrong? I'm only still a kid. Hell, I thought I bricked my phone halfway through installing the first RUU because there was something wrong with the drivers, I ALMOST TEARED UP FFS.
Oh yeah, and wtf is up with this BS where you format the SD card to turn it into a Goldcard, and HTC Footprints just decides to move its crap into the SD card RIGHT AFTER I FORMAT IT. It's not important, but I was just wondering.
I might have been missing some details (it's late) so please post below and tell me what I'm missing.
Thanks in advance!
PS: Oh yeah, have I voided my warranty yet? Technically, I mean. I COULD still clean it up somehow, and make it seem like I didn't do anything to it, right?
PS2: OK, now I'm getting USB errors 171 and 170 when installing RUUs. I can't get out of the RUU I'm on. Oh crap.
PS3: I just got Error 140, BOOTLOADER Error. What did I do wrong here?
At least I'm at the phone's home screen now, no more unfamilar scary-ass HTC LOGO territory.

Basically the update to "2.1-update1" brought you back to where you were before the downgrade. Your phone is stock right now.
So first relax and get some sleep
Do the downgrade again. DO NOT UPDATE.
Continue the debranding/gold card procedure.
good luck
p.s. your warranty might technically be void when you install another ROM or debrand or root, mostly they don't care as long as you didnt drop it in water . There is always a way to bring it back to stock/unroot

Oh my goodness I love you. I just noticed (while I was tired, wow, that's strange) that the strange ROM number within the About Phone menu finally clicked with what I've been doing! NO UPDATE.
So I decided to call it a night after I try once more.
So I downgraded to w/e. It was fine.
And I tried the debranding RUU. Then I got a bootloader error. I guess I'll try to find out what that means when I wake up, I'm super sleepy. (Unless you guys can help me 'til then )
It was error 140 or something like that, but it booted me fine to my downgraded ROM, so I'm good for the time being.
Good night!
EPIC ACHIEVEMENT EDIT:
Alright, I rooted it. Sweat all over the place, but hey, don't blame me. The problem above is still experienced by many people all over the internet, unfortunately. Too bad I can't answer it.
Just a question before I flash my first ROM with ClockworkMod: What about fixes? How do I flash those? Super noobish, but yeah.