Database Users

So odin will not work for neither my computers.. and bricked.

So i accidently bricked my phone trying to update my modwm to the newest froyo one.
Now I keep trying too odin back to stock but it wont work. Ive bricked before and used my laptop and it restored but now it doesnt work on my laptop nor my desktop. They either both say the device is unknown or it connects and when I try to flash it either freezes on file analyses or param.
Im going to go to the sprint store later today and try to get a new one. When I try to turn my phone on i get the little phone arrow computer sign. Do you think if I tell them that my phone froze so I took out the battery and that happened they will believe me? Idk how much of rooting the sprint employees know. Should I deny everything?

You will likely need to tell the tech that you had some bugs (force closes or something) and tried to do a reset through recovery mode and ended up with a non-working phone. Techs will likely know a bit about rooting and roms, especially if they have their own android phone. They also know that rooting and 3rd party roms void your warranty and they are supposed to deny claims where the phone was running 3rd party roms.

Can they tell if I rooted it just by the phone to computer sign? I went to a sprint store earlier and they told me to go to the corperate store because he didnt know what that meant.. Also I bought it from bestbuy so if sprint doesnt cover it would bestbuy?

sasha101 said:
Can they tell if I rooted it just by the phone to computer sign? I went to a sprint store earlier and they told me to go to the corperate store because he didnt know what that meant.. Also I bought it from bestbuy so if sprint doesnt cover it would bestbuy?
Click to expand...
Click to collapse
Bestbuy won't cover it. And if you plan on exchanging the phone, you'll have to go to the Sprint Corporate center. I bricked my phone the other day and it was only a $35 exchange for a new Samsung Epic. I only had to wait a day for a new one. They won't give you a new battery or SD card, so make sure to hold on to those.
Sorry about your phone.

If the phone is off can you hold the 1 button on the keyboard and power button and does a yellow downloading screen come on?
Sent from my SPH-D700 using XDA App

tphillips78 said:
If the phone is off can you hold the 1 button on the keyboard and power button and does a yellow downloading screen come on?
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
I don't think it would matter, truthfully. If the computer doesn't recognize the phone to begin with, putting the phone into download mode won't have any effect.

acer1096xxx said:
I don't think it would matter, truthfully. If the computer doesn't recognize the phone to begin with, putting the phone into download mode won't have any effect.
Click to expand...
Click to collapse
Different usb cable maybe? If sasha101 can get into download mode the phone isn't bricked and there is at least still hope. Maybe re downloading odin and other files as well. Just a thought.
Sent from my rooted Samsung Epic 4Gless device running ViperRom Trinity V3.0.3 using XDA App

I usually have to rotate between the different pits (512, 513, 528, and no pit) before I can get it to succesfully flash, so this is something you can try.

I would definitly try a different cable. I wasn't able to use odin to load 2.1 and in fact I bricked (I think). Tried 2 different cables and tried someone else's pc. NO go. Went back to the best set of directions I had found, redownloaded all the software needed, borrowed my wife's cable and started over. Everything worked like I was told it should. I really believe I had cables. Will try to find a new good one for the next time I try Odin.
Good luck and Marry Christmas.
George MacDonald
Sent from my SPH-D700 using XDA App

Randyshear on youtube explains this process flawlessly very informative
Sent from my SPH-D700 using XDA App

Umm.. if its not recognizing your phone you either didn't download the drivers; or they didn't install right. So.. (re)install them..
If this doesn't work its your cable; you'll need a new one.
Also; android isn't bricked until you can't get into download mode anymore.
Just because it doesn't boot doesn't mean its not bricked.
Sent from my SPH-D700 using XDA App

Epic 4G Bricked?

I was coming from 2.2, wanted to go back to stock 2.1. Went through ODIN to load the DI18 stock modem/rom/kernel. Used same files before, but this time it failed on flashing for some reason. Anyways, now my device won't even power on. No Samsung logo, nothing. If I hold 1 and power. I can't even get to download mode. Plugging the USB cable while device is off doesn't even get the indicator light to come on, or even the battery charging logo thing. Ideas?

afive720 said:
I was coming from 2.2, wanted to go back to stock 2.1. Went through ODIN to load the DI18 stock modem/rom/kernel. Used same files before, but this time it failed on flashing for some reason. Anyways, now my device won't even power on. No Samsung logo, nothing. If I hold 1 and power. I can't even get to download mode. Plugging the USB cable while device is off doesn't even get the indicator light to come on, or even the battery charging logo thing. Ideas?
Click to expand...
Click to collapse
Did you try removing the battery, holding the power button, and then re-inserting the battery?

mattallica76 said:
Did you try removing the battery, holding the power button, and then re-inserting the battery?
Click to expand...
Click to collapse
Yea, just tried that , still nothing

afive720 said:
Yea, just tried that , still nothing
Click to expand...
Click to collapse
Was the battery fully charged when you started the process?

Congratulations, I believe you have a true brick. Looks like a trip to the Sprint store.

mattallica76 said:
Was the battery fully charged when you started the process?
Click to expand...
Click to collapse
Battery was about at 90%. Yea, sucks.

That is weird that the phone would go beserk if you had the Samsung drivers, ODIN and the DI18 files. I would try to pull the battery a couple more times alternating startups (i.e. try to boot into recovery, if that fails, pull battery, try to boot into download mode, if that fails, pull battery, try normal boot). If that doesn't work and you have a spare battery, try that battery. I would try everything before going to the store.

afive720 said:
Battery was about at 90%. Yea, sucks.
Click to expand...
Click to collapse
For future reference, you only need the di18 tar in pda to flash back to stock. It includes the modem and kernel already. The PIT file is used only when flashing individual components like the modem or kernel by themselves.

running_the_dream said:
That is weird that the phone would go beserk if you had the Samsung drivers, ODIN and the DI18 files. I would try to pull the battery a couple more times alternating startups (i.e. try to boot into recovery, if that fails, pull battery, try to boot into download mode, if that fails, pull battery, try normal boot). If that doesn't work and you have a spare battery, try that battery. I would try everything before going to the store.
Click to expand...
Click to collapse
Been trying it all morning. The Samsung logo doesn't even come on. It acts as if the battery is completely dead, no matter what you do. Download mode should have at least worked, I have never seen it happen.

afive720 said:
Been trying it all morning. The Samsung logo doesn't even come on. It acts as if the battery is completely dead, no matter what you do. Download mode should have at least worked, I have never seen it happen.
Click to expand...
Click to collapse
If you can't get into download mode, your bricked. I'm not tryin to be a negative Nancy, just sayin. Don't worry, it happens to the best of us. I bricked an Epic once because I checked re-partition instead of Auto-Reboot.

mattallica76 said:
If you can't get into download mode, your bricked. I'm not tryin to be a negative Nancy, just sayin. Don't worry, it happens to the best of us. I bricked an Epic once because I checked re-partition instead of Auto-Reboot.
Click to expand...
Click to collapse
That's what I meant, I have the PIT and TAR files and I just flash, did it a number of times to this day with no issues. I just don't understand how it is possible to get to the point where download mode would not even work. I had my phone replaced 3 weeks ago for earpiece being blown too.

afive720 said:
That's what I meant, I have the PIT and TAR files and I just flash, did it a number of times to this day with no issues. I just don't understand how it is possible to get to the point where download mode would not even work. I had my phone replaced 3 weeks ago for earpiece being blown too.
Click to expand...
Click to collapse
That's the nature of the beast. I always feel like I'm playing Russian Roulette with odin ever since I bricked that one.

mattallica76 said:
That's the nature of the beast. I always feel like I'm playing Russian Roulette with odin ever since I bricked that one.
Click to expand...
Click to collapse
You know, I've had TEP for awhile, never used it. Took it off, then Earpiece goes out and now this/

..I had the exact same thing happen took to the Sprint store...forgot to clear out my sd card completely and found out it was rooted...but the techs at sprint can tell when the phone is bricked because a normal unrooted phone doesn't have that problem....try to bs your way thru ut otherwise TEP will not cover....sorry bro
Sent from my SPH-D700 using XDA App

it happened to me once back in the samsung moment days... Just clear ur memory card and take it to sprint...
tell them it just won't power on and you don't have another battery or charger to check what it is...

xcolt45 said:
..I had the exact same thing happen took to the Sprint store...forgot to clear out my sd card completely and found out it was rooted...but the techs at sprint can tell when the phone is bricked because a normal unrooted phone doesn't have that problem....try to bs your way thru ut otherwise TEP will not cover....sorry bro
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
"Normal unrooted phones", can have that problem. I've seen someone plug their phone into a car charger and then ZAP! Instabrick. When I took mine back to the store, they didn't even question me as to what happened. They saw that it would not turn on, and swapped it out for another one.

I think the op said that he/she deactivated his/her TEP though. Hopefully you are a premium Sprint user and can get an upgrade price for a new phone.

running_the_dream said:
I think the op said that he/she deactivated his/her TEP though. Hopefully you are a premium Sprint user and can get an upgrade price for a new phone.
Click to expand...
Click to collapse
I got it 30 day bounced to a new Epic basically. Didn't cost me $35 even .

Nice! Happy to hear it

I had a very similar experience, when the "Official" DK28 release first became available.
I was already running a custom rom, and found that I had the official DK28 required detection of the stock rom, so I figured, it would be no big deal to flash back. I followed the instructions explicitly, and bricked it.
After struggling with it for about 4 hours, I decided a trip to the Sprint store in the morning was the best remedy.
It was only like 10 days after I bought it, and I went back to the store where I bought it. I just said "It won't start up. I'm not sure what's going on with it." and the Sprint store rep proceeded to fumble around with it for about 10 minutes before she finally goes "Hmmmm, I've never seen anything like this before. Let me go grab another one from the back." and I got a 2nd headphone set/ac-usb adapter in the process.

Samsung Vibrant Hard Bricked, Any solutions?

Hi, I just tried flashing an official froyo rom for Odin3 and it was a sucess, but after it suceeded, my phone just shut off on its own. I tried pressing the power button and nothing happens. I have also tried many methods such as taking out battery, hold volume down+up buttons, then plug usb and put back battery. Another method that I tried from my first hard-brick was holding the Volume up and power button then putting in back the battery which does not work on the second break. Are there any solutions other than using a JIG? Thanks for the responses and help.

The best way to fix it is to go to a T-Mobile store, tell them you flashed your phone to a custom rom and everything went perfect, until it rebooted. Then ask them to exchange it for a new vibrant at no charge even though you voided your warranty. Then ask them if they sell the jigs also because that might come in handy the next time you brick your vibrant.

djquick said:
The best way to fix it is to go to a T-Mobile store, tell them you flashed your phone to a custom rom and everything went perfect, until it rebooted. Then ask them to exchange it for a new vibrant at no charge even though you voided your warranty. Then ask them if they sell the jigs also because that might come in handy the next time you brick your vibrant.
Click to expand...
Click to collapse
The problem is I don't have warranty for this phone, I'm not sure if they would exchange it.

You didn't get it....hmmmm.

TheSneakerWhore said:
You didn't get it....hmmmm.
Click to expand...
Click to collapse
I would've got the warranty but my parents bought for me lol, the warranty cost alot when it first came out so my parents didn't want it

snowball34 said:
I would've got the warranty but my parents bought for me lol, the warranty cost alot when it first came out so my parents didn't want it
Click to expand...
Click to collapse
No, it's a lil more snarky than that--he was BS'ing you all the way.
JTAG might do the trick.

TheSneakerWhore said:
No, it's a lil more snarky than that--he was BS'ing you all the way.
JTAG might do the trick.
Click to expand...
Click to collapse
So they are no solutions on how to un-brick my phone other than jigging it?

Try removing everything and open ODIN , plug the usb cable in to your pc & phone... hold down the volume down & power button & put the battery in...just to make sure you tried all combinations...
In actuality, you should do the steps above but hold the volume up & down buttons and put the battery in to get to download mode.
You can also try and remove everything, have odin open, plug the usb into your pc only, hold the volume up&down buttons, put the battery in(keeping the buttons pressed) and then plug the usb into the phone.
*********************************
if you can't add to the conversation, then move along and stop bashing someone looking for help...just sayin..

I hard bricked my Vibrant about two months ago when I tried to odin the boot loaders and I didn't buy a warranty when I bought the phone. Samsung gives you a one year warranty on your vibrant from the day of purchase. Since Vibrants were released last July, you should still have the manufacturer's warranty. Just call up Samsung and tell them your phone didn't turn on after you tried updating to 2.2 from 2.1. They will have you send in it in and they'll fix it free of charge. As long as the phone is a true hard brick they won't know you messed with it since they won't be able to turn it on. This process worked for me.
Edit. Make sure you say that you tried updating through Kies.
Sent from my GT-I9000 using XDA Premium App

+1, to the reply above.
Sent from my SGH-T959 using XDA App

onajjar1012 said:
I hard bricked my Vibrant about two months ago when I tried to odin the boot loaders and I didn't buy a warranty when I bought the phone. Samsung gives you a one year warranty on your vibrant from the day of purchase. Since Vibrants were released last July, you should still have the manufacturer's warranty. Just call up Samsung and tell them your phone didn't turn on after you tried updating to 2.2 from 2.1. They will have you send in it in and they'll fix it free of charge. As long as the phone is a true hard brick they won't know you messed with it since they won't be able to turn it on. This process worked for me.
Edit. Make sure you say that you tried updating through Kies.
Sent from my GT-I9000 using XDA Premium App
Click to expand...
Click to collapse
So Samsung automatically gives my Vibrant a one year warranty starting the day I bought it?

Yes. All new phones come with a one year warranty including Samsung phones.
Sent from my GT-I9000 using XDA Premium App

power off phone
pull out battery
GRAB THIS STUFF : http://forum.xda-developers.com/showthread.php?t=1047087
turn on odin
attach phone to pc with usb cable
now while holding down both volume buttons put battery back in.
now you should be in download mode and go back to stock with odin from here!
make sure u put the proper .pit and .pda file in there proper places on odin and ur set to go.
Enjoy and also make sure u have the proper samsung drivers

[Q] Surely I've bricked my Galaxy S

Hi,
I've searched and searched and I actually come to the conclusion that it is certainly bricked but all the related answers have somewhat different problems not exactly the same as mine.
Basically I was doing a firmware upgrade from 2.2.1 to 2.3.3 with Odin and it failed right at the end, the phone was stuck on the android download screen and Odin stopped.
I could not do anything, the phone wouldn't get out of that state and Odin was finished. I took out the battery and now the phone does not turn on on any mode. Tried simply turning on the phone, nothing, recovery mode, nothing, download mode, nada... The phone simply does not do anything, it is as if it didn't have any battery.
The conclusion I guess is that it is bricked and nothing can be done other than going down to service but would like to triple check just in case.
Grateful for any help.
Thanks

No boot screen?, nothing?
Sent from my Samsung Galaxy S II using the xda premium app.

kotaro_14 said:
No boot screen?, nothing?
Sent from my Samsung Galaxy S II using the xda premium app.
Click to expand...
Click to collapse
Absolutely nothing, I have taken the battery out for a while to no avail. It does not respond to anything..

Try the USB JIG

theos0o said:
Try the USB JIG
Click to expand...
Click to collapse
That's the only thing I have not tried, before doing the walk of shame to SCS I will do that, i will be a little pissed if I butcher a usb cable for nothing but will try and let you know.
Would SCS cover it under warranty if I made up some story about laptop freezing mid update or so?

pokemi said:
That's the only thing I have not tried, before doing the walk of shame to SCS I will do that, i will be a little pissed if I butcher a usb cable for nothing but will try and let you know.
Would SCS cover it under warranty if I made up some story about laptop freezing mid update or so?
Click to expand...
Click to collapse
I guess that if USB JIG doesn't work they won't be able to find out much, so.. possibly yes

Have you tried holding download mode combo when battery is out and then plugging in battery while holding those keys?

Wesku said:
Have you tried holding download mode combo when battery is out and then plugging in battery while holding those keys?
Click to expand...
Click to collapse
I thought I did but just tried now just in case.... Nothing

The USB JIG will do nothing if no boot screen or anything comes up.
You're screwed.
Sent from my Samsung Galaxy S II using the xda premium app.

kotaro_14 said:
The USB JIG will do nothing if no boot screen or anything comes up.
You're screwed.
Sent from my Samsung Galaxy S II using the xda premium app.
Click to expand...
Click to collapse
That's what I thought. I will go to SCS tomorrow and test my luck... Will let you guys know.

[Q] how to save hard bricked nexus 4??

Hi all, so I went to flash Franco kernel on my n4, and I clicked on nexus 4 kernels, but somehow ended up going to the page with the gnex kernels, and flashed that instead. I didn't realize that till after I bricked my phone when I went on my friends phone and then checked the page. Idk how that happened that I was directed to the gnex kernel page, but I was. So anyway, I hard bricked my phone and wondering if There's any way to save it? It won't even boot up, or go into bootloader mode, or anything. please help?? Thanks!

Try holding volume down and then plugin your usb cable in your pc. Worked for me and mine is still hardbricked! Maybe you can get into fastboot and restore

lowtje said:
Try holding volume down and then plugin your usb cable in your pc. Worked for me and mine is still hardbricked! Maybe you can get into fastboot and restore
Click to expand...
Click to collapse
it doesnt even turn on, and i have a mac :/ i have no way to get into fastboot mode

It doesn't turn on? What did you mean? Do you see the Google logo when you press the power button? Try holding volume keys and power to get to fast boot.
Try downloading the drivers from the pdanets software. I think they have a Mac version which will enable you to use fast boot on Mac. Go to Google factory images page and download the nexus 4 image. Unzip it and use flash the boot image by using the fastboot command : fastboot flash boot boot.IMG
Sent from my Nexus 4 using xda app-developers app

Ieatnoobs said:
It doesn't turn on? What did you mean? Do you see the Google logo when you press the power button? Try holding volume keys and power to get to fast boot.
Try downloading the drivers from the pdanets software. I think they have a Mac version which will enable you to use fast boot on Mac. Go to Google factory images page and download the nexus 4 image. Unzip it and use flash the boot image by using the fastboot command : fastboot flash boot boot.IMG
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
like i mean that no matter how long i hold the power button, the phone doesnt turn on. its just a black screen. no logo, no boot anumation, nothing. i cant even boot into fastboot or recovery, so i cant do any fastboot commands

Maybe the battery is dead? Try charging it?
Sent from my Nexus 4 using xda app-developers app

Melad360 said:
like i mean that no matter how long i hold the power button, the phone doesnt turn on. its just a black screen. no logo, no boot anumation, nothing. i cant even boot into fastboot or recovery, so i cant do any fastboot commands
Click to expand...
Click to collapse
Leave it in the charger overnight. And try to use an high amp charger like the ipad one
Sent from my iPad using Tapatalk HD

lowtje said:
Leave it in the charger overnight. And try to use an high amp charger like the ipad one
Sent from my iPad using Tapatalk HD
Click to expand...
Click to collapse
it was at 95% when i bricked it though, theres no way the battery is dead :/

so i called google about replacing it, they said that they will email the original buyer (my dad) to authorize an exchange, so i might be able to get a new n4

Melad360 said:
so i called google about replacing it, they said that they will email the original buyer (my dad) to authorize an exchange, so i might be able to get a new n4
Click to expand...
Click to collapse
Not to sound like an asshole or anything but to be completely honest, I kinda hope Google doesn't replace that phone of your for free. You messed it up by not double checking everything twice before clicking that confirm button when you went to flash a new kernel. You knew that if you messed up your phone is dead. But now Google has to shell out a new phone because YOU messed up, not Google.
Gonna ruin it for people that actually did get a defected device...

Melad360 said:
so i called google about replacing it, they said that they will email the original buyer (my dad) to authorize an exchange, so i might be able to get a new n4
Click to expand...
Click to collapse
Not cool. You need to fix this yourself.
What were you thinking flashing stuff to your phone but not having the ability to use fastboot and other dev tools? If you're going to intentionally gut out the functionality of your phone, have the tools and willingness to deal with problems! This isn't Google's fault, don't leave them with the bill!
Sent from my Nexus 4

waffleman911 said:
Not to sound like an asshole or anything but to be completely honest, I kinda hope Google doesn't replace that phone of your for free. You messed it up by not double checking everything twice before clicking that confirm button when you went to flash a new kernel. You knew that if you messed up your phone is dead. But now Google has to shell out a new phone because YOU messed up, not Google.
Gonna ruin it for people that actually did get a defected device...
Click to expand...
Click to collapse
how can i double check something that doesnt have a device model on it? it simply says "Franco.kernel nightly r-number.zip", i dont know how i managed to end up on the gnex kernel list, when i specifically clicked on nexus 4 kernels. that was beyond my control, its not like i made a stupid mistake on purpose. i double checked everything, making sure i was on the right xda page, and i downloaded a zip file not an img file, etc, i did everything i could do, yet little things slip

Melad360 said:
how can i double check something that doesnt have a device model on it? it simply says "Franco.kernel nightly r-number.zip", i dont know how i managed to end up on the gnex kernel list, when i specifically clicked on nexus 4 kernels. that was beyond my control, its not like i made a stupid mistake on purpose. i double checked everything, making sure i was on the right xda page, and i downloaded a zip file not an img file, etc, i did everything i could do, yet little things slip
Click to expand...
Click to collapse
Post the url you click that forwarded you to the gnex page. I'd be willing to bet that it says up top in orange, something along the line of "gnex>android development>gnex kernels"
Did you read the comments of that thread?
When you were in TWRP/CWM, the name of the file didn't hint at either gnex or nexus 4? It should have, if I'm not mistaken. There are always few ways to double check the file you downloaded.

Melad360 said:
how can i double check something that doesnt have a device model on it? it simply says "Franco.kernel nightly r-number.zip", i dont know how i managed to end up on the gnex kernel list, when i specifically clicked on nexus 4 kernels. that was beyond my control, its not like i made a stupid mistake on purpose. i double checked everything, making sure i was on the right xda page, and i downloaded a zip file not an img file, etc, i did everything i could do, yet little things slip
Click to expand...
Click to collapse
But this is Google's fault?
Sent from my iPad 4

k everyone calm down. I am sure all of us made that stupid mistake someday. None of us are perfect humans. We learn from mistakes. At least thats what we are suppose to do. Anyway, glad it worked out for OP.

So...it won't turn on at all? Did you someone flash a bootloader or something?

Maybe JTAG it. Hire somebody who knows how to use that technology and you could get it restored.

Melad360 said:
how can i double check something that doesnt have a device model on it? it simply says "Franco.kernel nightly r-number.zip", i dont know how i managed to end up on the gnex kernel list, when i specifically clicked on nexus 4 kernels. that was beyond my control, its not like i made a stupid mistake on purpose. i double checked everything, making sure i was on the right xda page, and i downloaded a zip file not an img file, etc, i did everything i could do, yet little things slip
Click to expand...
Click to collapse
Obviously this isn't the case because the links work just fine..
Sent from my Nexus 4 using Tapatalk 2

I`m calling google to tell them not to give a free phone to that guy! He should be charged every penny for the new phone!

Not to troll the OP, but man I'm seeing these threads all the time now and it's seriously annoying and down right fraudulent!
If you buy a new car, drive it off the lot and wreck it five miles down the road while breaking every traffic law known to man, you can not bring the heap of metal and plastic back to the dealership and demand another.
YOU voided your warranty! YOU flashed third party firmware! YOU improperly flashed third party firmware and bricked your device as a result. Do not blame Google, Franco, or anyone else for YOUR mistake!
Google has no responsibility for your device now, they guarantee that it works from the factory in the condition they sold it in. Once you click 'Yes' in the bootloader to unlock your device, you're on your own should you screw up... That's what that message is telling you!
I, for one, enjoy getting a nice phone at a great price. People like you are the reason carriers and OEMs charge $600+ now! Take responsibility for breaking it... Perhaps next time you should read, then when you think you know enough, read some more!
Spoiled children...
Sent from my Nexus 4 using xda premium