Database Info

[HELP] What do I do now? Captivate dead.

Yessss another dead captivate thread.
I think I'm gonna go die now.
I followed the video guide to install a custom ROM, in the development thread to the letter, and now my phone wont even turn on... (now that im thinking about it, I think I may have left the debugging mode OFF before I went to flash back to stock, maybe thats why?)
I got into download mode, plugged the phone into odin3 JF6 one click, it started and at some point during the process it said "removed" even though I didnt touch anything, and then i got a weird msg saying my device is not recognized, keep in mind the drivers were installed properly, and I had everything double checked before i flashed....
wtf do I do now? Cant boot at all or go back into download mode. this is my third galaxy, got it two days ago ffs.

My only 2 suggestions. Go to the Dev section and in the guides there is a method to make a USB Jig without solder or anything. You're out like $1 if it doesn't work.
Also, what rev is your phone? There's been some threads started saying the newer Rev phones, maybe 1010 and up crap out using normal One-click. Do check your rev level under the battery and do a search of the forums. I know I have seen the threads.
good luck.

1 reboot pc
2 use different usb ports (direct to motherboard)
3 open odin first as administrator
Sent from my GT-I9000 using XDA App

bobbylx said:
My only 2 suggestions. Go to the Dev section and in the guides there is a method to make a USB Jig without solder or anything. You're out like $1 if it doesn't work.
Also, what rev is your phone? There's been some threads started saying the newer Rev phones, maybe 1010 and up crap out using normal One-click. Do check your rev level under the battery and do a search of the forums. I know I have seen the threads.
good luck.
Click to expand...
Click to collapse
I'm not sure if I was looking at the right place, but I think its 10.12. I'll do a search and see what comes up, thanks for your help.
JayPhill89 said:
1 reboot pc
2 use different usb ports (direct to motherboard)
3 open odin first as administrator
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
I'll try that, thanks.

Open Odin first then,
1. Remove your battery for 30 seconds, remove external SD card and SIM card
2. Reinsert battery.
3. Hold down both volume buttons and while holding them down plug the phone in.
It should get into download mode then. I bricked my phone and it wouldn't boot up at all and this worked for me.
On a side note, I have not had much luck flashing or doing much of anything on Windows 7 64 bit. I would suggest trying it on an XP machine if you have access to one.

G.Hook said:
Open Odin first then,
1. Remove your battery for 30 seconds, remove external SD card and SIM card
2. Reinsert battery.
3. Hold down both volume buttons and while holding them down plug the phone in.
It should get into download mode then. I bricked my phone and it wouldn't boot up at all and this worked for me.
On a side note, I have not had much luck flashing or doing much of anything on Windows 7 64 bit. I would suggest trying it on an XP machine if you have access to one.
Click to expand...
Click to collapse
I've tried every possible key combination out there and nothing works. I think my best bet is a Jig, unfortunately the source didnt have any transistors in stock so im SOL for now.

Use JIG ... It will be your last help.

Use it as a paper weight.

If you look up samsung captivate jig on ebay you will find some pre built. I bought one not long ago just to have and it works just fine.
I hope this helps. Best of luck to you.
Sent from my GT-I9000 using XDA App

Sounds like you are a victim of the one size odin fits all debacle. You will indeed need a jig to recover and then you must use odin to flash jh2 or later firmware to your phone. Unfortunately, most guides still direct people to flash jf6 even though your situation comes up on a regular basis.

Check out this link for a jig. And there is a video to show you how to build one. Or mobiletechvideo guy sells them for 17 bucks.
http://forum.xda-developers.com/showthread.php?t=889128&highlight=usb+jig
Sent from my SGH-I897 using XDA App

newter55 said:
Sounds like you are a victim of the one size odin fits all debacle. You will indeed need a jig to recover and then you must use odin to flash jh2 or later firmware to your phone. Unfortunately, most guides still direct people to flash jf6 even though your situation comes up on a regular basis.
Click to expand...
Click to collapse
It seems to me like there's consistent irregularities with the entire process, its not uniform at all, which is very frustrating, every one faces different problems, and the solution is never the same.
Anyways, I went out and bought 3 resistors, turns out they were the wrong ones, I found out the colors werent the same of what I needed, but then that just goes to show you how difficult it is, its partly my fault i got the wrong ones, but someone like me who doesnt know much about hardware hacking, walks into an electronic store, faced with several options, is some times lost.
Oh well, I could've fixed it, had I got the right resistors, but then again, who was going to guarantee I wasn't going to kill it again, for the exact same reason I mentioned in the first post, because I need to consider a few things here, first and foremost, that I have a rogers branded device, and these are the ATT forums.
I called rogers and a replacement has been placed, I should be getting it by friday, or tomorrow if im lucky, with whatever comfort that brings, I still have several concerns, and now that I've basically rendered 3 devices to "almost" none-working condition (this one being an exception because I can "possibly" fix it) I'm not even sure how far I want to go.

rsnt said:
It seems to me like there's consistent irregularities with the entire process, its not uniform at all, which is very frustrating, every one faces different problems, and the solution is never the same.
Anyways, I went out and bought 3 resistors, turns out they were the wrong ones, I found out the colors werent the same of what I needed, but then that just goes to show you how difficult it is, its partly my fault i got the wrong ones, but someone like me who doesnt know much about hardware hacking, walks into an electronic store, faced with several options, is some times lost.
Oh well, I could've fixed it, had I got the right resistors, but then again, who was going to guarantee I wasn't going to kill it again, for the exact same reason I mentioned in the first post, because I need to consider a few things here, first and foremost, that I have a rogers branded device, and these are the ATT forums.
I called rogers and a replacement has been placed, I should be getting it by friday, or tomorrow if im lucky, with whatever comfort that brings, I still have several concerns, and now that I've basically rendered 3 devices to "almost" none-working condition (this one being an exception because I can "possibly" fix it) I'm not even sure how far I want to go.
Click to expand...
Click to collapse
My first captivate went fubar within my 30 days and I damaged the nv_data.bin on my second captivate and was stuck with the test IMEI. Samsung fixed my second one for free. Now I'm at the point where I'm totally sure about what precautions I need to take to keep me out of trouble but I'm not sure if I want to risk it again, heh.
The cheap jig does work. It helped me when I accidentally unplugged my phone during an odin flash.

Yes, you make a good point. You will find that most of the guides are written by people like myself who have an early revision or a phone from the initial release. For most of us, from what I've read and experienced, our phones are really hard to brick, ie, button recovery always works, odin one-click works, etc.
I honestly don't know all the differences now between revs. The first hiccup was the phones missing button recovery/download, and now it seems that people are having issues using the Odin One-click that we have been using for months.
I would recommend with your next phone check the rev or manufacture date, then search the forums for people with similar or same revs that have been successful at flashing and find out what they did.
good luck

@bobby
I wasnt trying to diminish the help that the guides provide. The work that went into creating them is certainly appreciated. The problem arises when so many people just tell newcomers to flash with x version of odin without considering the changes that have occured in the newer builds.
Sent from my Liquid Metal using XDA App

newter55 said:
@bobby
I wasnt trying to diminish the help that the guides provide. The work that went into creating them is certainly appreciated. The problem arises when so many people just tell newcomers to flash with x version of odin without considering the changes that have occured in the newer builds.
Sent from my Liquid Metal using XDA App
Click to expand...
Click to collapse
I agree with you completely. I tend to take it for granted that button recovery works for me and that good old odin one-click does too. It seems we need to start collecting data and making new guides.
Something like,
If you have rev, 1006, 1007,1008 go here,
If you have rev 1009 to 1012 go here,
etc.

latest update,
Two cables, and six resistors later, my phone won't go into download mode, lol, I'm not even sure I did things right, I'm gonna try stripping the same cable, used in one of those videos on how to make a jig, I still have three extra resistors.
I'm starting to think its because of it being with rogers. im gonna search the forums.

A micro usb breakout board is the simplest method for constructing a jig.

Wow, I guess I'm lucky that the used Captivate I picked up for my gf is an older one at 1007. Root procedure for her went without a hitch.
From stock rom, all set up and in daily use, WITHOUT ROOTING first.
Put clockwork update.zip on her sdcard.
Reboot into recovery.
Reinstall packages twice to get into clockwork recovery.
Wipe data/factory reset.
Flash Cognition.
Profit.
She's been using it this way for two weeks and loves it so much more than stock.
What was so complicated about the procedure you followed? Or was it the same as this but it just didn't work?

rsnt said:
...and now that I've basically rendered 3 devices to "almost" none-working condition (this one being an exception because I can "possibly" fix it) I'm not even sure how far I want to go.
Click to expand...
Click to collapse
I think you may have a good point. Eventually your carrier will stop replacing bricks for you. If you still have the inclination to play with flashing, investing in a jig would definately be a wise investment and if I were in your shoes, I wouldn't flash anything without one. I made a jig for myself before I ever flashed anything but luckily I have never had to use it, probably because I took the time (about a month and a half of trolling around here reading.) to research what all was involved with what I was about to jump into. Just something to consider in case you want to try again. Good luck!

Phone completely Dead

So I lent my brother my nexus s that had cm7 on it. He got into the clockworkmod, went to mounts/storage, and proceeded to format everything (bootloader, boot data, etc. everything in there) he said he thought that would fix the force closes, I figured no biggie, but now I can't even get the phone into download mode and I have no idea what to do, the phone will simply not turn on

wow.... dont even know why he would do that.
rule 1: dont lend people your phone.
and i dont know why you would try and get into download mode, Odin isn't the first thing you want to go to.
1. turn the phone off (if it isnt already)
2. hold volume up + power
... what happens? does bootloader mode pop up?
- plug your phone in your computer's USB
- does the sound for USB plugged in occur?
- does computer detect it?

Can't access fastboot.
Phone sometimes recognizes it and says this device is not recognized and it couldn't install the usb driver, sometimes when i plug it in it does nothing.
Didn't want to lend it to him, had no choice. I told him he should have just fixed the permissions on the phone, but then again he's not exactly android literate.

thats just dumb on his part.. i dont know why he would try and mess with your device. if it has problems, just ask you first.
its probably bricked if you cant access download or bootloader... definitely bricked if the computer is unable to detect it
your only way out of it is to get a replacement

In Device/Drivers of windows under Unspecified there's this:
SEC S5PC110 Test/BD
says drivers are not installed

Anybody out there with a solution?

I think there is more than one driver you can try, though I've never flashed anything in Windows (Linux already comes with the driver ), so I don't know for sure. I think I've seen people mentioned a few drivers before, try search for all the "brick" threads here.

Easiest solution might be to download a Linux live distribution (f.e. ubuntu) and run fastboot from there. No need to install any drivers.

Kicking him in the nuts will probably make you feel better... I don't know if it'll fix your phone though.

jruweaver said:
Kicking him in the nuts will probably make you feel better... I don't know if it'll fix your phone though.
Click to expand...
Click to collapse
lmao!!!!!!!!!!

KryPTiCk0d3 said:
lmao!!!!!!!!!!
Click to expand...
Click to collapse
While funny, it doesn't help one bit.

I would try the various methods to get into download mode and use Odin to fix it ...you might be screwed tho
Sent from my Nexus S using XDA App

SphericalPuma said:
While funny, it doesn't help one bit.
Click to expand...
Click to collapse
Unfortunately with the state your phone is in it is probably going to be the best advice you get.
Sent from my Nexus S using XDA App

http://forum.xda-developers.com/showthread.php?t=1000175
any chance that this could help you?

Ddi you ever get your phone sorted ? I'm now in the same situation !

Yes, hit up http://www.mobiletechvideos.com/blog/?page_id=970 For 50 bucks they'll fix your phone and ship it back to you in no time. They got my phone on a Friday, I got it back on either Monday or Tuesday. Of course they're based in Texas and I'm in STL so it could differ for you, but the point is, they're fast, reliable, and professional.

Thanks for that - I'm based in Ireland but I'll give them a shout and see if we can do business......

Thanks a million for the reference PUMA. Please contact me when you are in need of a brick fix. I fix hundreds of Galaxy S / Samsung / HTC variants and several others in a brick of nearly any scenario. I've devoted a lot of time to providing and almost unseen service to people in need versus parting the phone out or trashing it.

[Q] Should Verizon replace my phone?

I was running cm7 on my phone, and was throwing on the audio fix to get better speaker volume, which sent the phone into a boot loop. I tried to put my phone into hboot (power+volume-) which it does not. It tries to boot every time. I've tried probably 50+ times and same result. I'm guessing it has to deal with the poor built buttons on this phone and the volume down just does not work. My question is despite the fact I'm rooted and running cm7, am I safe to say this is a hardware issue? I just don't want to send in my phone to Verizon and get billed for the fact the phones "tampered" with.

Should verizon replace your phone after you borked it? I think you already know the answer

xebryus said:
I was running cm7 on my phone, and was throwing on the audio fix to get better speaker volume, which sent the phone into a boot loop. I tried to put my phone into hboot (power+volume-) which it does not. It tries to boot every time. I've tried probably 50+ times and same result. I'm guessing it has to deal with the poor built buttons on this phone and the volume down just does not work. My question is despite the fact I'm rooted and running cm7, am I safe to say this is a hardware issue? I just don't want to send in my phone to Verizon and get billed for the fact the phones "tampered" with.
Click to expand...
Click to collapse
long of it, no they shouldn't. will they? who knows, depends on if you tell them the truth or not.

Should they? Technically no. Will they? Sure. They would be happy to.

but he didnt break it if the loop comes from a hardware defect,all he did was get it to fail sooner than later basically what happened to others,so technically yes they should,or can anyone prove the software killed the hardware.
sent from a screamin' bamfed out tbolt

satseaker said:
but he didnt break it if the loop comes from a hardware defect,all he did was get it to fail sooner than later basically what happened to others,so technically yes they should,or can anyone prove the software killed the hardware.
sent from a screamin' bamfed out tbolt
Click to expand...
Click to collapse
Honestly, it doesn't matter if anyone can prove the software did it or not. He voided his warranty by rooting. But they likely will replace his phone, driving up the costs for future phones.
You rooted your phone. Take it for what it is...a non-warrantied phone.

Touchy
I will start off by saying I don't have a solid answer but being as it is a hardware problem they "should" fix it. Will they? Probably not. They'll take one look, see it's rooted, and tell you that you broke it by tampering with it. All bets are off as soon as the phone is rooted...unless you can unroot and take it in I think you're in trouble but since the button is broken you can't do anything with it. Good luck and let us know what you were able to get done.

I see what you guys are saying from a moral standpoint. I'm just angry cause I know for a fact my buttons are not up to par to what they're supposed to be. I don't want to fraud the companies over something that is my fault, but in this case I'm almost positive it's related to the fact this phone was not built too well. I dunno, do "authorized retailers" handle claims with faulty hardware or just official Verizon wireless stores?

This is why you should have ADB installed and working on your computer. Hook up the phone via USB, get into ADB and reboot into recovery. There are a few threads out there for ADB you should be able to find them using Google, hopefully that will be able to help you.

If you can get into the boot loader with and then you might be able to save your phone.. Maybe, not clear take your as card out and import the rhi, they might work...
Sent from my ThunderBolt using XDA App

if you can prove that the failure was not caused by rooting, then they should fix it for you under warranty. but that is hard to prove.

xebryus said:
I see what you guys are saying from a moral standpoint. I'm just angry cause I know for a fact my buttons are not up to par to what they're supposed to be. I don't want to fraud the companies over something that is my fault, but in this case I'm almost positive it's related to the fact this phone was not built too well. I dunno, do "authorized retailers" handle claims with faulty hardware or just official Verizon wireless stores?[/QUOTE
Did you try BOTH volume buttons at the same time? This got me to bootloader.
Click to expand...
Click to collapse

Just say you tried to install the last update and your phone wont boot now. They won't know the difference.

dpham00 said:
if you can prove that the failure was not caused by rooting, then they should fix it for you under warranty. but that is hard to prove.
Click to expand...
Click to collapse
Caused by rooting or not, there is NO warranty once a phone is rooted. Has nothing to do with what caused the malfunction.
ADB reboot bootloader or recovery should work though, as long as he catches it with the right timing during the loop.
Sent from my ADR6400L using XDA App

Well update on the situation. I called Verizon telling them I can't turn on my because it "freezes" when it tries to boot up every time. He told me to try a hard reset (try to go into hboot) and I told him I tried that at least 30 times and it won't. I said I think there's something wrong with my buttons because they're not very responsive and stick really easily (which they do) and he said they're overnighting a phone to me. That was yesterday, its waiting for me at home. I'm gonna send my old phone back asap.
I'm wondering, if they have a way to find out I'm rooted, will they charge me for the phone? I don't think they'll be able to though because if I can't get into hboot, how will they? I tried adb into bootloader, but as many times as I tried, no devices were found.

you're probably aright since they might just get it and toss it in the "to be refurbed" bin. It costs a lot of money to test every return. Good luck and let us know how it turns out.

xebryus said:
I'm wondering, if they have a way to find out I'm rooted, will they charge me for the phone? I don't think they'll be able to though because if I can't get into hboot, how will they? I tried adb into bootloader, but as many times as I tried, no devices were found.
Click to expand...
Click to collapse
If they do find out, they will charge you. Don't know if they will, but be prepared for the worst.
Sent from my ThunderBolt using Tapatalk

Yes, they get broken down abd only really check for water/physical damage
Sent from the Swag ThunderBolt ADR6400L with some GingerLove (Gingeritis 1.0) using XDA Premium App
Must Watch Before Any Forum Post http://goo.gl/b4IJJ

xebryus said:
Well update on the situation. I called Verizon telling them I can't turn on my because it "freezes" when it tries to boot up every time. He told me to try a hard reset (try to go into hboot) and I told him I tried that at least 30 times and it won't. I said I think there's something wrong with my buttons because they're not very responsive and stick really easily (which they do) and he said they're overnighting a phone to me. That was yesterday, its waiting for me at home. I'm gonna send my old phone back asap.
I'm wondering, if they have a way to find out I'm rooted, will they charge me for the phone? I don't think they'll be able to though because if I can't get into hboot, how will they? I tried adb into bootloader, but as many times as I tried, no devices were found.
Click to expand...
Click to collapse
Congrats on getting a new phone I guess.
I have noticed Verizon has been VERY accomodating with these phones. One call is all that's needed to get a new phone. Im guess they're so generous because they devices have been so finnicky so far and they just want to keep people pleased for now.
I envision them cracking down hard sooner or later though. They're not stupid. They've already come down on tethering and such, so it probably wont be long until they get hardcore on replacements.

My son works for VZ...
and he takes your calls... and this is what he told me. Anything covered under insurance (Asurion), they really don't check/don't care about rooting. VZ, on the other hand, will look pretty extensively if it's covered under the warranty. They will look for rooting or anything else that would break warranty coverage.

Wife's Desire S won't boot, please help!

My wife installed some updates in the market and her phone froze on the Sense home screen. Removed the battery, and it now won't boot past the HTC logo.
It is on the factory/default Sense ROM, never rooted or anything, my wife has like 5 apps on it and still the stock Sense wallpaper
It can boot into HBOOT, we tried the recovery option which showed the black screen with phone+green arrow animation for a few seconds. Then very shortly an image with a red arrow, then a reboot and still stuck on the HTC boot screen.
It does not show up in ADB, USB debugging is not on either.
My next thing to try would be a factory reset, is that likely to work?
Is there any way to get SMS'es and some game save games off the phone before resetting it?
Thanks for all suggestions!

Well if your PC is not recognizing the phone, then there's not much you can try I guess (other then factory reset.) Maybe someone is gonna come up with something.
Aren't the gamesaves on your sd card?
There have been hardware issues associated with multiple downloads from the market and pulling the battery. This might or might not be the case. However you are covered with warranty in case it is.
Sent from my HTC Desire S using XDA App

esbenm said:
My wife installed some updates in the market and her phone froze on the Sense home screen. Removed the battery, and it now won't boot past the HTC logo.
It is on the factory/default Sense ROM, never rooted or anything, my wife has like 5 apps on it and still the stock Sense wallpaper
It can boot into HBOOT, we tried the recovery option which showed the black screen with phone+green arrow animation for a few seconds. Then very shortly an image with a red arrow, then a reboot and still stuck on the HTC boot screen.
It does not show up in ADB, USB debugging is not on either.
My next thing to try would be a factory reset, is that likely to work?
Is there any way to get SMS'es and some game save games off the phone before resetting it?
Thanks for all suggestions!
Click to expand...
Click to collapse
If she created a HTC Sense account and had set it up to sync then her texts would have been saved online.

If no other options download the corresponding to your region RUU (ROM Update Utility) from here. Then reboot to Bootloader (VOL DOWN + POWER Button). Make sure that you have HTC Sync installed. Go to fastboot screen (you should see FASTBOOT USB line). Start RUU.exe. It will handle everything automatically and hopefully you will have a brand new Stock system again.

If hard resetting dies not work, I'm afraid you may have a fries eMMC chip! It's very common when the phone freezes in maker updates and you pull the battery!

olyloh6696 said:
If hard resetting dies not work, I'm afraid you may have a fries eMMC chip! It's very common when the phone freezes in maker updates and you pull the battery!
Click to expand...
Click to collapse
Sorry to be offensive but stop with this crap it only scares people. I have rescued my phone twice already from the bootloop. The fried eMMC is the last consideration to be made after trying some reasonable solutions.

An boot loop isn't
an real indicator for fried emmc, most of the times you just somehow messed up part of the software or the partitions, this:
http://forum.xda-developers.com/showthread.php?t=1292730 it's an really fried emmc.
Let's try some solutions before destroying any hope!
Swyped from my Desire S

amidabuddha said:
Sorry to be offensive but stop with this crap it only scares people. I have rescued my phone twice already from the bootloop. The fried eMMC is the last consideration to be made after trying some reasonable solutions.
Click to expand...
Click to collapse
I'm not starting with 'crap' I'm simply saying what might be true.
It is well known that after hitting update all in the market, it leads to a fried emmc chip.
I have also been stuck on a bootloop many times (after flashing wrong kernels etc) and had to pull the battery. I also risked a fried emmc chip. I was just lucky I didn't get it fried, and I hope it doesn't happen again! *touch wood*
Sent from my HTC Desire S using xda premium

esbenm said:
My wife installed some updates in the market and her phone froze on the Sense home screen. Removed the battery, and it now won't boot past the HTC logo.
It is on the factory/default Sense ROM, never rooted or anything, my wife has like 5 apps on it and still the stock Sense wallpaper
It can boot into HBOOT, we tried the recovery option which showed the black screen with phone+green arrow animation for a few seconds. Then very shortly an image with a red arrow, then a reboot and still stuck on the HTC boot screen.
It does not show up in ADB, USB debugging is not on either.
My next thing to try would be a factory reset, is that likely to work?
Is there any way to get SMS'es and some game save games off the phone before resetting it?
Thanks for all suggestions!
Click to expand...
Click to collapse
so, have you tried hard reset/factory reset. let us know what happen than. next time never pull out battery when your phone freeze. just press vol up + vol down + power button (all three hardware button) and the phone will restart. I personally had this problem few times and able to recover my device. start with hard reset your phone.
look at ben_pyett signature. you need the adb+fastboot and htc drivers for your windows pc to detect your device. I'm using linux and I don't need those drivers.

olyloh6696 said:
I'm not starting with 'crap' I'm simply saying what might be true.
It is well known that after hitting update all in the market, it leads to a fried emmc chip.
I have also been stuck on a bootloop many times (after flashing wrong kernels etc) and had to pull the battery. I also risked a fried emmc chip. I was just lucky I didn't get it fried, and I hope it doesn't happen again! *touch wood*
Sent from my HTC Desire S using xda premium
Click to expand...
Click to collapse
Ok to be more specific: I have already rescued my phone from a bootloop with all the indications for a "fried eMMC" described in some threads in this forum. Also me and Tectas assisted several people accross the forum these days to revive their phones from the "fried eMMC" (some successful, some not). Anyway all of these users had the info that they eMMC is fried and were terrified. But a Bricked and Fried phone are totally different stuff. So if you post to help is OK, but when you post to scare this isn't.

Update: thanks for all the suggestions. I couldn't get any of it to work, including factory reset.
We are going to send the phone in for a warranty repair, most of her personal stuff is on her Google account or the SD card, so no major problems.
The HTC Sense website with SMS backup never worked for her, there is no option to log in from the phone.
As much as i love Android I am shocked that hitting "update all" in the market and/or pulling the battery can brick a 400 $ phone. Even buggy old Windows ME was fine if you pulled the pover cord.
My iPhone friends will laugh at me well into 2012 if I tell them this.
Do HTC have more faults than other brands? Both our Desires have had trouble. I am about to upgrade mine, maybe should look at another brand?

There is some hope!
amidabuddha said:
Ok to be more specific: I have already rescued my phone from a bootloop with all the indications for a "fried eMMC" described in some threads in this forum. Also me and Tectas assisted several people accross the forum these days to revive their phones from the "fried eMMC" (some successful, some not). Anyway all of these users had the info that they eMMC is fried and were terrified. But a Bricked and Fried phone are totally different stuff. So if you post to help is OK, but when you post to scare this isn't.
Click to expand...
Click to collapse
+1
I'm afraid that I must agree.
In the early days of this problem, I too was probably guilty of announcing too early to users "that's you've fried your eMMC chip - that's a warranty return" where as over time we've now come to believe that this still a chance of hope, albeit not great or guaranteed, but none the less, fortunately several people have managed to recover from this situation, by a variety of means.
So even though the possible outcome might not be likely, I think that we should attempt to always suggest that there might be hope at least until we've tried all the possible solutions and now luckily the various users have compiled guides of the suggested options so this isn't that difficult.
The only time when I'd suggest that a user should probably instantly return a device, is if they are completely non technical or have a brand new device which is still S-ON. In which case they may as well return the device under warranty and get a replacement device or motherboard which will at least contain the non dubious/faulty chip, and will remove the possibility of future occurrence completely - so they'll actually be better off for the future!
esbenm said:
Update: thanks for all the suggestions.
Click to expand...
Click to collapse
Sorry to hear this. You were just unfortunate and what happened to you is rare, also it's not a fault of Android but, a HTC eMMC chip hardware issue caused by a particular dodgy version of the eMMC chip that comes on some of these phones.
I believe that HTC realised the fault and replaced the chip with another make after a fashion. So hopefully you'll get the different chip on your replacement device/motherboard.
I also think that they've changed the market application so that it downloads one application after rather than all the applications together, which was known to cause a device freeze, which often was followed by a battery user battery pull - which then led to this problem.
Next time... Never pull the battery! there are always other options.
Take care and good luck.

[Q] QHSUSB_BULK help?

Hey guys I was trying to unlock my bootloader, and when I booted into fastboot, my phone shut off and my phone was detected as QHSUSB_BULK on my PC and will not respond to anything. Any help would be appreciated. Thanks.

AFAIK (personal experience on other devices) it's dead. Until someone comes up with a JTAG, you're gonna have to try your luck with OPO customer service.

Thanks
rani9990 said:
AFAIK (personal experience on other devices) it's dead. Until someone comes up with a JTAG, you're gonna have to try your luck with OPO customer service.
Click to expand...
Click to collapse
Thanks for responding. Do you know specifically what causes this issue (For future reference)?

Man, anything to do with QHUSB is never good from pretty much everything I've read about it here on XDA. We can't help you on this issue. QHUSB is the very definition of a hard brick. My friend, you're going to have to suffer through the agony that it OnePlus Customer Service. Best of luck.
Can you tell us exactly what you did so other people don't end up with the same outcome as you? Really sorry to hear this, man.

When I have seen this on other devices it often is due to loss of or corruption of firmware that has to do with the boot sequence such as bad bootloader or radio. I was messing with LOGO partition and nearly bricked my OPO the other day, got the same driver coming up. But luckily it rebooted back to os on its own and I just had to dd the partition back to stock in order to get bootloader back and functioning.
So other than JTAG you most likely can't do anything without shell commands available to you

Eshraq said:
Thanks for responding. Do you know specifically what causes this issue (For future reference)?
Click to expand...
Click to collapse
Typically, bootloader corruption is the cause of a phone entering QHUSB (Qualcomm High-Speed USB) mode. QHUSB is a very low level, extremely basic level of functionality that your phone can have with your computer; hell, it's so low-level, no one has been able to find the significance of it or how to reverse this mode yet (with the exception of a few people with a few legacy HTC device, and having some very lucky breaks, like Demkantor above me). Think of it as your phone being brain-dead. All of the things that made your phone yours (data, pictures, apps, pretty much everything having to do with data) is gone. Only the basic functions (USB connectivity through QHUSB, battery) are still functioning.
This is truly the worst-case scenario of development. Very sorry to hear.

treChoy said:
Man, anything to do with QHUSB is never good from pretty much everything I've read about it here on XDA. We can't help you on this issue. QHUSB is the very definition of a hard brick. My friend, you're going to have to suffer through the agony that it OnePlus Customer Service. Best of luck.
Can you tell us exactly what you did so other people don't end up with the same outcome as you? Really sorry to hear this, man.
Click to expand...
Click to collapse
What I said is what literally what happened. I booted into fastboot. Crashed and the end result is there. I'm not sure what else to say. I'm definitely going to try to return it and just get the next nexus. Whatever.

demkantor said:
When I have seen this on other devices it often is due to loss of or corruption of firmware that has to do with the boot sequence such as bad bootloader or radio. I was messing with LOGO partition and nearly bricked my OPO the other day, got the same driver coming up. But luckily it rebooted back to os on its own and I just had to dd the partition back to stock in order to get bootloader back and functioning.
So other than JTAG you most likely can't do anything without shell commands available to you
Click to expand...
Click to collapse
Wait what do you mean it rebooted back on its own?
Alright I long pressed the power and it turned on

Nice People of OPO Channel
So I went into the OPO channel. They told me to long press power. It worked. I think I might be lucky. Or something else maybe.