Hello Everyone,
I have a rogers captivate. I was trying to update to 2.3 android using Odin . I followed the whole process as stated. After rebooting, I got AT&T logo??? and the phone will not boot, go into recovery mode, or connect to my computer. Have I messed up my phone. Please advice.
how did you get an AT&T logo if it doesnt boot?
also what part of the process were you at? gingerbread shouldnt give the white ATT screen
it should give the "i9000" screen with gingerbread.
or were you flashing stock ATT first?
there is nothing wrong with having the wrong boot screen AND A FIX WAS RELEASED LAST NIGHT FOR GB
the fix for stock ATT has been out for a while. AND MY STOCK ROM FIXES IT TOO!
did you read the part about the button combos changing with gingerbread? or if you are on the ATT stock, use old button combos. Also you should have found my stock rom link before flashing, info there too!, its in my sig,
you have to give us more information to help you.
I beleive I was installing it to stock ATT first. That is when this happened. I was on Odin one click install. I remember the phone saying "do not disconnect the target". then all the installation was done from odin. This phone had 2.2 from samsung.Right now all that happens is that the phone starts and a flashing att logo on white background stays..
please let me know what other info is needed. i will post it all to the best possible
boot into download mode and flash ATT stock again. something messed up
are you using the "one click odin" or the other odin?
and what gingerbread are you trying after?
how do i do that. i have tried vol up+down+power combo. still the same flashing logo with no menus. i was using one click odin. and i was still on installing stock android. never got the chance to go to 2.3
If you can't get into download mode through the 3 button way you might need the jig. You got lucky since you're still able to boot up some have perma brick so try the jig and flash back to stock
Sent from my SAMSUNG-SGH-I897 using XDA App
HOLD VOL UP + DOWN
the plug in USB to PC.
keep buttons held until screen comes on!
i asked which gingerbread you were going to do AFTER
What is the build number on your phone, 4 numbers printed under the battery, mine is a 1010 for example, which mean oct. Of 2010 is when it was built. Some phones 1010 and after will not accept the one click odin rom and cause a bootloop like you are having, Try an odin package from TRusselo's sig instead.
my packages dont have the bootloaders. that might be whats screwed up with blinking att boot.
need download first before anything. i do have a GB bootloader package separately
something else:
try removing battery,
plug in USB to PC and Phone
Hold both Volume buttons
put battery back in.
should get you download mode
I really have noidea about what gingerbread i was after, i guess i wanted just the stock android without any custom software from samsung. I am total noob here as far as androids go.
the number on the battery say 2010.12.20 and the last forr nos under the battery at s/n are 11.02.
what is a jig. how do i use it. My phone cannot connect to the computer.
When I try to reset my device by any method, whether usb or power combos, it goes into either a. ATT logo flashing every few secs. or b. battery charging logo with nothing happeining.
Also my phone cannot be seen on my computer
gingerbread isnt for noobs
NOT THE DATE ON the battery
UNDER the battery ON THE PHONE
4 digit number
if you dont know what a jig or gingerbread or any of this stuff is,
you shouldnt have touched your friggin phone!
My apologies. the number is 1102. I understand I have screwed up. Any chance of having a working phone again.
GO GOOGLE A CAPTIVATE JIG AND BUY ONE
you wont be able to make one if you cant follow instructions.
that is your only hope. if not your phone is F'ed up perminantly.
your ONLY HOPE AFTER, is if your phone *somehow stops* turning on *forever*
and you send it back for warranty, and play dumb! ..... ..... ... .. .
PROGRAMMING a phone cant be learned it 5 minutes.
HELL you cant even read the friggin instructions (written for experienced users) in 5 minutes
this was an expensive lesson on researching and learning before doing
hitechchef said:
My apologies. the number is 1102. I understand I have screwed up. Any chance of having a working phone again.
Click to expand...
Click to collapse
Sorry for stepping in..
Yes there is. Might be a little complicated tho. You have some reading to do my friend.
Tru, I'll let you handle it but HiTechChef, you might've to go in for waranty and exchange it saying it did that after you tried to update through Kies. They'll check it and give you another one.
Thanks I will try this method
BWolf56 said:
Sorry for stepping in..
Yes there is. Might be a little complicated tho. You have some reading to do my friend.
Tru, I'll let you handle it but HiTechChef, you might've to go in for waranty and exchange it saying it did that after you tried to update through Kies. They'll check it and give you another one.
Click to expand...
Click to collapse
he's a rogers phone and it boots to ATT screen
it has to *stop* booting to get *warranty*
TRusselo said:
he's a rogers phone and it boots to ATT screen
it has to *stop* booting to get *warranty*
Click to expand...
Click to collapse
Oh right.. Wow..
Yep, go read about a JIG (it's pretty simple to use). You can either build it or buy one from mobiletechvideo or ebay.
TRusselo said:
he's a rogers phone and it boots to ATT screen
it has to *stop* booting to get *warranty*
Click to expand...
Click to collapse
Lol That kind of subtly is lost here... noone is picking up on your suggestion...
and thats how its going to stay,
ive said it before with almost the same words.
ive laid out all the tools....
correction of the original problem is necessary,
research is salvation,
resistance is futile.
there it is... i laughed... all is good again...
Related
hey guys,
i doubt anyone can be of any help. I have bricked my captivate in trying to odin flash the rom back to the stock js6, or whatever. Any help.. wont go into download or recovery mode.
http://forum.xda-developers.com/showthread.php?t=775911
If you don't even know what ROM you're trying to flash to, perhaps you should stick to stock.
rww265 said:
hey guys,
i doubt anyone can be of any help. I have bricked my captivate in trying to odin flash the rom back to the stock js6, or whatever. Any help.. wont go into download or recovery mode.
Click to expand...
Click to collapse
I really like how descriptive you are in telling us what exactly your problem is
Here's a simplified guide to fixing your phone:
1. Press the power button. Does something happen (anything?) If yes, go to step 2, otherwise jump to step 3.
2. Read what Miami_Son posted.
3. Your phone is dead. Mail it back to Samsung. Pray that they don't charge you an arm and a leg to restore the firmware.
Uh-oh
3. Your phone is dead. Mail it back to Samsung. Pray that they don't charge you an arm and a leg to restore the firmware.
Click to expand...
Click to collapse
Do you happen to know how much they may charge for this? I tried to flash back to stock last night and now have no reaction when I press the power button. I talked to Samsung, but couldn't get any good information from them about potential cost without telling them exactly what happened.
Does anyone know what the process involves? Can the tell from a phone that won't power what was done?
Sorry for the n00bish questions.
bmwenger said:
Do you happen to know how much they may charge for this? I tried to flash back to stock last night and now have no reaction when I press the power button. I talked to Samsung, but couldn't get any good information from them about potential cost without telling them exactly what happened.
Does anyone know what the process involves? Can the tell from a phone that won't power what was done?
Sorry for the n00bish questions.
Click to expand...
Click to collapse
Hard bricking with Odin takes some effort. Did you try everything in the thread I posted? If it didn't complete an Odin flash then they probably can't tell what happened or if it has a custom ROM on it. More likely they'll just strip it for repair parts or just reflash it without diagnosing it. Just say that it was suffering from random shutdowns and now it won't turn on.
Miami_Son said:
Hard bricking with Odin takes some effort. Did you try everything in the thread I posted? If it didn't complete an Odin flash then they probably can't tell what happened or if it has a custom ROM on it. More likely they'll just strip it for repair parts or just reflash it without diagnosing it. Just say that it was suffering from random shutdowns and now it won't turn on.
Click to expand...
Click to collapse
About the only thing I haven't tried is a jig, but from what I have read unless you have something happen when you push the power button that won't work. I didn't far enough to really tell where it is in the process. I had a recovery screen (2e I think) show up and then nothing responded to a button press. Next thing I know, it won't let me boot up.
Oh well, we'll see what happens with the phone and Samsung.
Thank you so much for all the help I have gotten over the past few weeks from this site.
I was doing a odin one click restore from continuum rom, and it went through and said successfull but blackscreen brick on reboot...
so after trying every trick in the book, i got it to come on in download mode using a jig but of course odin didnt see it so i had no choice but to try again..
well after days of trying to get it back into DL mode, i contact samsung, and find out my phone is under warantee. so i send it in, and then a week later get an email saying: "Oh hai we r dun with ur phonez and sendin it bak to u"
of course im thinking sweet my phone will work... nope they put on the work order that my phone was beyond repair, and then put a little purple square piece of paper in the box with it that said "=P warantee void for unauthorized updates"
So unfortunately now i have no choice but to use my stupid iphone
att store complain ftw.
att said it was samsungs responsibility
tooloney said:
I was doing a odin one click restore from continuum rom, and it went through and said successfull but blackscreen brick on reboot...
so after trying every trick in the book, i got it to come on in download mode using a jig but of course odin didnt see it so i had no choice but to try again..
well after days of trying to get it back into DL mode, i contact samsung, and find out my phone is under warantee. so i send it in, and then a week later get an email saying: "Oh hai we r dun with ur phonez and sendin it bak to u"
of course im thinking sweet my phone will work... nope they put on the work order that my phone was beyond repair, and then put a little purple square piece of paper in the box with it that said "=P warantee void for unauthorized updates"
So unfortunately now i have no choice but to use my stupid iphone
Click to expand...
Click to collapse
There is a member floating around the forum who might be able to help you out with a JTAG flash for your phone, or you could look into trying your hand at it yourself. Just search for JTAG and I'm sure you'll find some help.
tooloney said:
I was doing a odin one click restore from continuum rom, and it went through and said successfull but blackscreen brick on reboot...
so after trying every trick in the book, i got it to come on in download mode using a jig but of course odin didnt see it so i had no choice but to try again..
well after days of trying to get it back into DL mode, i contact samsung, and find out my phone is under warantee. so i send it in, and then a week later get an email saying: "Oh hai we r dun with ur phonez and sendin it bak to u"
of course im thinking sweet my phone will work... nope they put on the work order that my phone was beyond repair, and then put a little purple square piece of paper in the box with it that said "=P warantee void for unauthorized updates"
So unfortunately now i have no choice but to use my stupid iphone
Click to expand...
Click to collapse
Okay first of all you posted in the wrong section. Next time please post in the Q&A if you have any problems/questions .
Does your phone turn on at all? Like to the Phone+!+PC screen?
my bad it was more of a comment than a question, hence the absence of question marks, I know what needs to be done to fix it, jtag, unless one of these new things theyre discovering with the uart, etc... happens to perform a miracle..
but no its black screen bricked, and that after a "successful" odin flash. The phone does turn on though cuz it gets warm.
Everyone knows flashing voids your warranty. Time to buy a new phone.
yea except for the flash that bricked the phone was a stock rom so i was hoping they wouldnt say it was void because of it
There are a million warnings on this site that flashing voids your warranty and may brick your phone.
When you decided to mess around with flashing you should have known this could happen.
dude im not stupid, i know that flashing voids your warranty. There is also a million people who have gotten new phones from bricks after flashing under warranty replacement.
Trying to get samsung to fix it under warranty is fraud and is illegal. Posting about it on here is evidence of the crime.
If you wanted your phone to have a warranty you shouldn't have flashed it.
I told them i flashed it... as i said, i was flashing it to stock anyway when it died. Either way no fraud was committed, i called them trying to see if i could just buy a new motherboard, theyre the ones that told me the phone was under warranty and to send it in.
So sorry mr lawyerpants for doing what i was told.
Well enjoy your brick just the same.
tooloney said:
I told them i flashed it... as i said, i was flashing it to stock anyway when it died. Either way no fraud was committed, i called them trying to see if i could just buy a new motherboard, theyre the ones that told me the phone was under warranty and to send it in.
So sorry mr lawyerpants for doing what i was told.
Click to expand...
Click to collapse
Why in gods earth would you admit flashing anything?
Sent from my I897 using XDA Premium App
Personally the fun illegal warranty claim on a bricked phone is to open it up loosen the heatsink and take a soldering iron to the CPU well the phone is stuck on boot...
I of course have never done this as my phones CPU exploded for legitimate reasons... ;-P
Sent from my Legend using XDA Premium App
Shouldve just said that your were updating to the offical froyo via kies. And kies told you to put you're phone into download mode (It does say that in the instructions somewhere as a second option.) And that you were doing the offical flash and the phone fell off your table and caused the usb to disconnect. Then the phone wouldn't boot...
mcord11758 said:
Why in gods earth would you admit flashing anything?
Click to expand...
Click to collapse
It might be because
tooloney said:
dude im not stupid
Click to expand...
Click to collapse
I would like you to try something for me. I was having an issue very similar to this. remove your battery and then reinsert it without turning the phone on. plug the phone in as if to charge. Leave it on the charger for several hours. Then try to use odin 3 click, and post your results. May be a lost cause but if it has the slightest chance to save your phone, it deserves a shot.
You fail, should have read the instructions correctly on how to flash.
NascarFastcar said:
Shouldve just said that your were updating to the offical froyo via kies. And kies told you to put you're phone into download mode (It does say that in the instructions somewhere as a second option.) And that you were doing the offical flash and the phone fell off your table and caused the usb to disconnect. Then the phone wouldn't boot...
Click to expand...
Click to collapse
Thats actually what i told them i was flashing, i guess they figured out i was lying since it was the stock odin flash.
or maybe since it was the stock odin flash and we arent supposed to have odin?
xThe Enforcer said:
You fail, should have read the instructions correctly on how to flash.
Click to expand...
Click to collapse
Thanks, I guess I missed the part in the instructions where i was supposed to click more than one button in odin one click to flash my phone to stock. Ill be sure to read more closely next time.
I successfully flashed to att ICS using Jim's method. Then I decided to roll back to 2.3.6 and used Jim's ICS back to 2.3.5 fxz fix zip file. The RSD stopped at 5/19 reboot bootloader for a long time and the screen was off. I hit the power button trying to turn on the screen without thinking. Then I realized that I was flashing! It was too late and I saw FAILED on RSD. My A2 cant turn on anymore. I did not unplug or pull the battery. Any help would be appreciate!
qtqt710 said:
I successfully flashed to att ICS using Jim's method. Then I decided to roll back to 2.3.6 and used Jim's ICS back to 2.3.5 fxz fix zip file. The RSD stopped at 5/19 reboot bootloader for a long time and the screen was off. I hit the power button trying to turn on the screen without thinking. Then I realized that I was flashing! It was too late and I saw FAILED on RSD. My A2 cant turn on anymore. I did not unplug or pull the battery. Any help would be appreciate!
Click to expand...
Click to collapse
DId you replace ALL of the files and then point the RSD to the xml?
Can you boot into fastboot by holding power button and vol down.If can you just reflash it using rsd lite.Tell me more detail about your atrix 2 current rom and which version of rom you are flash with rsdlite.
Sent from my MB865 using xda premium
Exact same problem has occurred to me as well.
I did replaced the files Jim created to FXZ back to 2.3.6 from ICS
My Battery was fully charged at the time of flashing. Flashing stopped at 5/19 reboot bootloader for 15 mins then tried rebooting it manually but it didn't started.
Now I've tried everything but it is not even starting in Fastboot
Please help me with this, I don't want to start any new thread so posted my problem here.
EDIT: I think this is a common problem as the OP here also have the same problem
http://forum.xda-developers.com/showthread.php?t=1781045
http://forum.xda-developers.com/showthread.php?t=1700775
I only flashed ICS when Jim confirmed that it was possible to revert back to 2..3.5
I think there is a problem in reverting back to 2.3.5 once applied ICS update and people should be aware of that.
Everyone should stop flashing ICS leaks otherwise they might end up bricking their phone forever.
100% same to me.
Up to ICS ok, back to Fxz with RSD and stuck at 5/19 reboot-bootloader step, I disconnected cable and phone black forever.
A lot of people they failed when flash with RSD but no problem, just take battery out and return, boot again to fastboot to re-flash. I think wrong file in Fxz not makes this problem, main cause I still don't know ! Maybe we are unlucky man ?
FXZ is not wrong one as I did used it when I had to flash back to stock from lithium Rom last week. I think phone is dead because it is not even booting into fastboot.. I've tried even booting to our stock recovery by pressing 3 buttons but no luck so far.
Its just very bad few hours back I was running ICS and now my phone is not even booting up.
OMG man!! I should have make a thread about this yesterday, but maybe nobody would of paid attention. I didn't really want this to happen to anyone, when flashing from 4.0.4 back to 2.3.5 it will get stuck at 5/20, something like that saying "rebooting loader". Now my phone with a blackscreen is getting hot when I insert the battery and when I plug it without a battery into my laptop or wallcharger and I dont have warranty. I call it white LED of death, when I plug it in to my laptop without a battery hehe , so I guess i'll be paying maybe 200$ dollar for it to be repaired, well if they repair it though, they charge so much here.. But i'm still trying to look what I can do, before I take it to a repair shop.
I heard about this problem when leak ICS for China/HK market 1 month ago, from xda man, and Jim he warned everybody here take care when coming back GB from ICS leak should make your phone bricked.
Now ATT ICS leak was released and all trusted Devs here confirmed that we can turn back to GB without problem, so I thought that it was safe to do with. Next day Jim posted new thread with new patch file. So sad ... I'm too late, we're too late ...
vinamilk said:
I heard about this problem when leak ICS for China/HK market 1 month ago, from xda man, and Jim he warned everybody here take care when coming back GB from ICS leak should make your phone bricked.
Now ATT ICS leak was released and all trusted Devs here confirmed that we can turn back to GB without problem, so I thought that it was safe to do with. Next day Jim posted new thread with new patch file. So sad ... I'm too late, we're too late ...
Click to expand...
Click to collapse
I didn't even flashed ICS leak first day, I did it second day when Jim confirmed and uploaded a link for new replace files.
prasannapmv said:
I didn't even flashed ICS leak first day, I did it second day when Jim confirmed and uploaded a link for new replace files.
Click to expand...
Click to collapse
So this is the point that I'm very confused, I think that even failed flashing phone still powered on normally : wrong boot.img --> just jamed at boot logo, wrong bootloader --> screen turn on and shows errors; need to be flashed again by RSD or script. Some man here even not flashed anything, just root then reboot and phone dead without any reason.
vinamilk said:
So this is the point that I'm very confused, I think that even failed flashing phone still powered on normally : wrong boot.img --> just jamed at boot logo, wrong bootloader --> screen turn on and shows errors; need to be flashed again by RSD or script. Some man here even not flashed anything, just root then reboot and phone dead without any reason.
Click to expand...
Click to collapse
I guess it has something to do with our bootloader, maybe it's stuck or not even working.
darkmixta said:
I guess it has something to do with our bootloader, maybe it's stuck or not even working.
Click to expand...
Click to collapse
I just talked to a Motorola service person he was saying in some rare cases a inbuilt ROM(read only memory) chip which stores bootloader files gets corrupted and in that case it might not even be possible to boot into fastboot.
I don't know how far he is right but one ting we are sure that our hardware was perfectly ok before flashing FXZ.
For me I even made sure that my battery was fully charged before starting FXZ.
prasannapmv said:
I just talked to a Motorola service person he was saying in some rare cases a inbuilt ROM(read only memory) chip which stores bootloader files gets corrupted and in that case it might not even be possible to boot into fastboot.
I don't know how far he is right but one ting we are sure that our hardware was perfectly ok before flashing FXZ.
For me I even made sure that my battery was fully charged before starting FXZ.
Click to expand...
Click to collapse
Same here I had like 90% battery or more, is you're phone becoming hot? When you plug it in or insert the battery?
darkmixta said:
Same here I had like 90% battery or more, is you're phone becoming hot? When you plug it in or insert the battery?
Click to expand...
Click to collapse
yes its getting heated when connected to a wall socket or on a battery.
Did anyone upgrade RSDlite to 5.7 before trying this by any chace?
That might be an issue.
Also, this could be something that was introduced to later model phones. My a2 was able to fxz back, but it ws made in SEPT 2011. Just another thought.
Sent from my SAMSUNG-SGH-I747 using xda premium
prasannapmv said:
yes its getting heated when connected to a wall socket or on a battery.
Click to expand...
Click to collapse
Hahaha, what should we do? Yesterday I felt like throwing my phone into the wall man and just %$#@ Motorola, this is like the biggest failure ever!! Hard bricked without doing something wrong.. Wish I could go back in time sometimes and I don't even have warranty which sucks, what are you gonna do?
Really hard to hard brick? http://forum.xda-developers.com/showpost.php?p=28324515&postcount=10
We hard bricked so easy..
jimbridgman said:
Did anyone upgrade RSDlite to 5.7 before trying this by any chace?
That might be an issue.
Also, this could be something that was introduced to later model phones. My a2 was able to fxz back, but it ws made in SEPT 2011. Just another thought.
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
I was already using RSD 5.7
jimbridgman said:
Did anyone upgrade RSDlite to 5.7 before trying this by any chace?
That might be an issue.
Also, this could be something that was introduced to later model phones. My a2 was able to fxz back, but it ws made in SEPT 2011. Just another thought.
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
I did not. It is 5.6. That may be the reason. I got my A2 from att in Nov 2011, so I guess it is the same earlier version, right?
To those with the issue, can you not get back into ap fast boot? Either hold both volume buttons down with power, then select it from the menu, or i have found that holding up with power will boot you right into fastboot.
Sent from my MB865 using xda premium
Fall of Enosis said:
To those with the issue, can you not get back into ap fast boot? Either hold both volume buttons down with power, then select it from the menu, or i have found that holding up with power will boot you right into fastboot.
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
Nope they can not even power on anymore. This is what we all feared. The hk leak had this same thing in it...
Looks like moto will be warrantying a bunch of phones.
I am just not sure why I can still do it...
We have had way too many of these now for it to be user error or an accident.
Sent from my SAMSUNG-SGH-I747 using xda premium
Hey well, to start things off I was trying to unlock my T-Mobile SGS4G to work with AT&T but it turns out it needs to be rooted first. I have rooted before and this is the first time I have ran into a problem.
What I did first:
I used Heimdall in an attempt to flash CWM Recovery so I can gain root access. For some reason the zImage was bad (?) and my phone could only get to the T-Mobile logo and then freeze.
Recovery and Download DID work
What I did second:
I used odin3 to flash back a stock T-Mobile rom in hope to fix things... and it did everything succesfully but now it's stuck in a real boot loop.
Can't get into Recovery, nor Download. It's really depressing to keep seeing that battery show over and over again.
Any ideas on how to get my computer to detect my phone again?
Thanks.
Edit:
I did every button combination + usb plug combination known to man. I uninstalled and installed the files again.
Did my phone brick because I ticked the partition tab on odin?
PLEASE help.
Our phone IS NOT the Vibrant. Hopefully someone can help you, but... I don't know. If you flashed OUR stock rom, with bootloaders... you're screwed. But, the fact you have images on your screen, should give you some hope.
Yea, I saw that, but the title says he has a vibrant. I don't know....
Head to the vibrant forum there are some un-brick tools over there...you need to get it in download mode use odin to flash stock froyo vibrant rom.. Should get it back up and running
Sent from my SGH-T959V using xda premium
Kingarabian said:
T-Mobile SGS4G
Click to expand...
Click to collapse
Just to verify, pull out your battery and check if you have the SGH-T959V
One of the "download jigs" may help once you are certain which phone you have and what firmware and ROM you need to flash. You can make your own with a resistor and a microUSB plug, I bought one for $8.00, delivered, (I now see they have them on Amazon for $4, Super Saver eligible) and others have had good luck with even cheaper ones on eBay.
Also: http://forum.xda-developers.com/showthread.php?p=9403915
Jigs are cheap and unless you got the right resistor lying around buy a ready made one. Also if the phone shows up in odin you can download something whatever picture shows up on the screen. Raver has a thread about using heimdall to fix the boot files but its about six months old. Worked for me once. It might even be indexed in the bible under development.
Sent from my SGH-T959V using xda premium
My Galaxy S3 will not respond to any combination of button presses, and the device is identified as QHSUSB_DLOAD in Device Manager. If I take out the battery and plug it in, the light turns red for ~10 seconds, and then turns off. (Device Manager is refreshed at this time, but still reads it out as QHSUSB_DLOAD). It does not respond to home+power+vol down or up.
To get to this result, I had booted into recovery mode in order to install a new ROM, but the installation failed. I chose the reboot option and this is how I ended up. Looking back, I probably should've restored the device prior to booting...
x04a said:
My Galaxy S3 will not respond to any combination of button presses, and the device is identified as QHSUSB_DLOAD in Device Manager. If I take out the battery and plug it in, the light turns red for ~10 seconds, and then turns off. (Device Manager is refreshed at this time, but still reads it out as QHSUSB_DLOAD). It does not respond to home+power+vol down or up.
To get to this result, I had booted into recovery mode in order to install a new ROM, but the installation failed. I chose the reboot option and this is how I ended up. Looking back, I probably should've restored the device prior to booting...
Click to expand...
Click to collapse
You most likely need to go into Odin mode and flash back to stock using Odin. Just follow the steps in this guide:
http://forum.xda-developers.com/showthread.php?t=1762709
Also, dumb question, but is your battery dead? I know I had this problem coming from a completely dead battery once, took a bunch of tries to get it to start charging and turn back on. But I wasn't coming off of a bad flash, of course.
dontsayeta said:
You most likely need to go into Odin mode and flash back to stock using Odin. Just follow the steps in this guide:
http://forum.xda-developers.com/showthread.php?t=1762709
Also, dumb question, but is your battery dead? I know I had this problem coming from a completely dead battery once, took a bunch of tries to get it to start charging and turn back on. But I wasn't coming off of a bad flash, of course.
Click to expand...
Click to collapse
The battery was at ~60% when I was flashing.
ALSO: I can't get into ODIN mode as the device doesn't respond to any type of button combination.
Deleted.
dontsayeta said:
Ok. I don't know what steps you have taken so far, but do a battery pull and then try to get into Odin mode.
Click to expand...
Click to collapse
I don't know if you read the OP or not but I did in fact already do what you stated. It does not work. I have: Battery pull+attach to USB, Battery pull+battery back in. Neither work to get back into ODIN mode.
Yeah, sorry, I did read that right after my post, but I couldn't go back and edit it fast enough because I have these new user restrictions on my account.
dontsayeta said:
Yeah, sorry, I did read that right after my post, but I couldn't go back and edit it fast enough because I have these new user restrictions on my account.
Click to expand...
Click to collapse
I understand, I have the same restriction. However, I think that the device is simply bricked and cannot be recovered. If no solution is posted then I will be heading to the VZW store tomorrow I suppose.
x04a said:
My Galaxy S3 will not respond to any combination of button presses, and the device is identified as QHSUSB_DLOAD in Device Manager. If I take out the battery and plug it in, the light turns red for ~10 seconds, and then turns off. (Device Manager is refreshed at this time, but still reads it out as QHSUSB_DLOAD). It does not respond to home+power+vol down or up.
To get to this result, I had booted into recovery mode in order to install a new ROM, but the installation failed. I chose the reboot option and this is how I ended up. Looking back, I probably should've restored the device prior to booting...
Click to expand...
Click to collapse
Your phone is hard bricked. I'm gonna guess you were flashing a non Verizon ROM, probably an international.
The only fix at this point is a JTAG service. Also, unfortunately you would not have been able to restore before leaving recovery anyways. I'll try to find the popular website people use for that service.
Sent from my SGS3 running Eclipse 2.1 build 4
Yep, sounds like you flashed a ROM not made for the Verizon S3. Be a little more careful next time.
Check out mobile tech videos for a JTAG.
Zalithian said:
Yep, sounds like you flashed a ROM not made for the Verizon S3. Be a little more careful next time.
Check out mobile tech videos for a JTAG.
Click to expand...
Click to collapse
Thanks I couldn't remember the site.
Sent from my SGS3 running Eclipse 2.1 build 4
I'm not trying to be a ****, but how/why do people flash roms not made for Verizon GS3? Is it really that easy to make the mistake? Where are they getting the roms from??
Just curious
josh995 said:
I'm not trying to be a ****, but how/why do people flash roms not made for Verizon GS3? Is it really that easy to make the mistake? Where are they getting the roms from??
Just curious
Click to expand...
Click to collapse
Probably just google about flashing roms, find a youtube video and follow instructions. Wonder if a lot of videos don't have a warning, or if people ignore it.
josh995 said:
I'm not trying to be a ****, but how/why do people flash roms not made for Verizon GS3? Is it really that easy to make the mistake? Where are they getting the roms from??
Just curious
Click to expand...
Click to collapse
I'm just an idiot, and jumped the gun on this flash.
josh995 said:
I'm not trying to be a ****, but how/why do people flash roms not made for Verizon GS3? Is it really that easy to make the mistake? Where are they getting the roms from??
Just curious
Click to expand...
Click to collapse
Well, back in the days before quadcore... the roms that were made for the international HTC Desire HD also worked on the us version the HTC Inspire 4G. . . I fell right into the pitfall after getting used to that.