Database Info

Really think it's dead.. ayudame!

So after playing around with ROM manager and getting the new CW recovery to work, I think I legitimately bricked my poor Xoom wifi.
Here's where we are now.
Power button doesn't work. Hard reset doesn't work. Getting to RSD/Fastboot doesn't work. USB connection isn't recognized (windows/linux). No lights work. A/C charger doesn't appear to work. Nothing happens at any direction.
So far, there is zero indication that the device is even powering at all. Yes, it's charged. Just a giant, solid black screen that is mocking me. :[
The last thing I did was partition the SD card. (trying to install new Tia kernel). Rebooted, worked fine. Powered down. Now it won't respond to anything.
Think I'm going to go sacrifice a virgin and see if that helps.
Thoughts? Or should I just go back to Best Buy and beg?
Sorry if this is all over the place. Having one of those "holy $ I have a $600 paperweight!" moments. Heh.
****
THE CHARGING LIGHT WORKS!.. when connected to A/C now. Nothing else does.. but that one light works.. progress is progress..

Hope you're still within your return period. My understanding is the Xooms internal storage is labeled as sdcard and the actual sdcard is sdcard2. So by "formatting the sdcard" you essentially formatted the Xooms 32GB internal memory.

[email protected]$
I partitioned a 4M chunk of it to put the recovery image on it. So.. would that explain it being completely nonresponsive? The only thing I got out of it today is that the charging light was white and then green when it was fully charged. Otherwise nothing works I am within my return period but I'm traveling...until my return period is up. Boy, this is just a bad situation, is it not? Haha

That would explain it being non-responsive.

Anything that can be done? Or do I have to start playing phone and shipping tag with Motorola at this point?
And if I do send it to motorola and they get the OS back on there.. how would they do it?

First off: did you partition the internal storage or are you running Tiamat with sdcard support?
Sent from my Xoom using XDA Premium App

In the recover module, I went to partition SD card, then partitioned it to 4MB. (The image is 3 and change). Whether or not it was internal or external, I couldn't tell you. I don't have an external SD card. So yes, I made a rookie mistake on that one.
I'm glad I wrote this down: Another thing, when I had it hooked up via USB and mounted the USB storage in recovery, a prompt came up in windows saying "you need to format this drive in order to use it." so.. I copied the /sdcard/ contents (cause that's what I thought it was talking about) to my PC and formatted it. I could only format it to 3MB. That's what led me to trying to partition the SD card so I could put the recovery image on whatever drive was there.
Yeah.. the more I think about this the more of a rookie mistake it was. I'm sure I formatted something that had critical operating system files on it and that's why I can't even get the thing to boot. A:LKFJ;-

Stuck at Samsung Logo and no access to download or recovery mode.

Recently I went from Miui to Revelation to check it out and everything seemed fine. I tried to restore something and my phone ended up freezing. I got it back into red recovery and everytime I rebooted (before and after trying restoring) it would just boot back to the CWM that was with each different backup. Miui-Blue and Revelation went to red. Anyway, I used Odin and finally got it back to stock root with one of my stock root files. Now today i was trying to update files again and now I'm stuck at the Samsung Logo and can not access either CWM or Download mode. With the phone off and plugging in cable as if just charging it while off it goes directly to samsung logo. HELP?? I've never seen this before and cant find anything on it.

Pull battery, plugin USB cable, then insert battery. You are now in download mode.
Sent from my SAMSUNG-SGH-I997 using xda premium

bkmo said:
Pull battery, plugin USB cable, then insert battery. You are now in download mode.
Sent from my SAMSUNG-SGH-I997 using xda premium
Click to expand...
Click to collapse
Im not a total newb. I've searched the forums and there isn't anything on it. I've tried all the normal stuff. It has to be something a little more complex than that.

I'm going to try to get it working again when i get home. I tried a few things here at work, but no luck. I don't know if there are any differences between micro usb's, but the one I have here at work is for a LG. Charges my phone fine, but maybe something with that? In the mean time, I have AT&T shipping me another phone just in case I cant figure this one out in the next few days. I would like to get my info off of the internal sd before I ship it back. Any info would be much appreciated.

Wow...it wouldn't let me do the download mode because of the cable. Didn't really see that coming. ***Note--LG cables DO NOT work as data cable on Samsung*** (Charging does)

Try Buying a blackberry torch's Microusb cable. it did wonder s for my phone resetting it to stock

It worked when i got home. everything is good now. Do you all think i should swap with the refurbished one for the hell of it?
Sent from my SAMSUNG-SGH-I997 using XDA Premium App

Download mode
You may want to order (or make) a Download Mode jig from Ebay.
They are available for about $2 shipping included. Just snap it into your charge hole, reboot, and it will automatically go to Download Mode. Once there, you remove the jig and snap in your USB cable and you're ready to go. No more taking the case apart, pulling the battery, and holding down the buttons.

My phone isn't recognizing a USB cable is plugged into the computer in fastboot

Hey guys, I have a softbricked Atrix2, I tried making a factory cable the other night, wired it correctly as far as I know, it turned on straight away without a battery into fastboot, but wouldn't recognize that a usb cable was plugged in (So power, but no data). And when I plugged in a normal usb cable with the battery in the phone still wouldn't recognize that a usb cable was plugged in. I am currently charging my battery right now, I wasn't having this problem before and am starting to think this phone is cursed by the devil himself . I'll be really disappointed if I charge this battery up and another problem arises, been waiting weeks for this charger. The phone was recognizing usb data cables without issue, tho of course I couldn't do anything because of the low battery, and suddenly it just stopped. Any ideas? Just don't want to spend all day trying to work this out because I've had a softbricked phone for weeks and only got to use it for all of about an hour .
More info: When I plug a normal USB in without a battery the white LED lights up and stays lit. Everything is pointing to power but no data... What would cause that and is there a fix
More more info: Battery OK
OK to program
Connect USB
Data Cable
Shows in device manager as "Unknown device", trying to force install of the "Mot single ADB interface" drivers just gives the error "The device cannot start (Code10), wont show up in ADB or RSD, and phone WILL NOT change status to USB plugged in. Time to think up a legit reason why my phone would say "Flash failure" and get a replacement?

A little more info maybe
What were you on before soft brick stock 2.3.6,2.3.5 or ICS???
How exactly did you soft brick it??
Have you tried getting the phone to start in the normal mode?(by pressing power+vol up+vol down and choosing boot normally???)
Sent from my MB865 using xda premium

deveshmanish said:
A little more info maybe
What were you on before soft brick stock 2.3.6,2.3.5 or ICS???
How exactly did you soft brick it??
Have you tried getting the phone to start in the normal mode?(by pressing power+vol up+vol down and choosing boot normally???)
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
Went from 2.3.6 to stock 2.3.5 to OTA 2.3.6 to OTA leak to SCV7, phone kept crashing, tried to fxz back to 2.3.5 stock, said completely successfully but just bootlooped so I went to try again but the battery was low, so that's how I softbricked. And me being the impatient person I am I tried to make a moto factory cable with 2 non standard cables (Micro usb end from a mini to micro converter and the other end from something else), I'm sure I wired it correctly but I guess not, it booted into fastboot without a battery, but said connect usb cable, so I tried to plug in a normal usb cable (tried different ones) and it said the same thing. I shorted something out, the damage might just be on the micro usb PCB connector or it might be something worse. Yes I tried normal mode, no go, recovery works. So basically, my phone is now hardbricked because I'm impatient and screwed something up along the way. Now I have a 12 month warranty on the phone, can someone help me come up with a believable story that'll get me a new phone? Keeping in mind the phone boots into fastboot with (flash failure)

Trust me. The folks on the line at AT&T DON'T CARE.
Just BS your way through it. IE: I went to bed, plugged my phone in, woke up and the battery was really hot. Then the phone shut off and won't boot. Just play dumb.
All else fails. Hook that motherboard up to a car battery.
Sent from my SAMSUNG-SGH-I727 using xda premium

Fall of Enosis said:
Trust me. The folks on the line at AT&T DON'T CARE.
Just BS your way through it. IE: I went to bed, plugged my phone in, woke up and the battery was really hot. Then the phone shut off and won't boot. Just play dumb.
All else fails. Hook that motherboard up to a car battery.
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
I bought it from a 3rd party seller (Mobicity.com.au). I think I might just go with "The phone kept crashing every 4-5 minutes, I tried to do the system update to 2.3.6 and the phone crashed halfway through, tried to turn it on again and it showed the Moto logo and something about a fastboot". Wish me luck guys .

Okay shipped it off, wish me luck guys, I'll keep you updated.

"Technicians needed to know which ROM used to update your handset?"
Not liking my chances with this at all. I got my dad to give them a call and act dumb, should be convincing because he honestly doesn't know what he's talking about. The phone says flash failed and he's denying ever flashing anything, I don't think a failed OTA update would give that error message so I don't think they're going to replace it..... .
EDIT: Dad called the technician and the tech said he's gonna fix it and that the motherboard was fried, looking good, phew!.

Update:
Your phone has been deemed unrepairable and as a result will be replaced by your place of purchase. Please contact your place of purchase and quote xxxxxxxx to arrange a replacement handset to be dispatched to you.
Click to expand...
Click to collapse
Wooo .

Really just a paperweight ?

Is there anyway to fix a bricked phone. I mean a seriously completely bricked phone. One that doesn't turn on in anyway. Won't charge. Won't connect to a computer. Never had recovery installed. Nothing. How do they initially flash all that stuff to the phone when they first make it .....
Sent from my PC36100

If you want more help you should probably specify make and model of the phone, also what you were doing when your phone bricked.
I would try getting your phone into download mode, usually some button combinations. If you can do this you're not totally screwed. yet.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

Yeah I should lol. I wasn't cause Im so curious how they flash it all to a phone in the first place. Well its a crappy lg vortex on froyo 2.2.2 and I was messing with themes. And accidently mixed two and it messed it up. Boot loop and all. Then I ended up doing a factory reset which made it not go past the lg screen and I then didn't touch it for a while and so now. It doesn't charge or anything. I don't throw it out cause its not physically broken in anyway. And there's gotta be a way to fix it...cause don't they start of with a lifeless paperweight anyway?
Sent from my PC36100

well if you want to fix it i guess step one is get working battery if it doesnt charge... ?

Well there's no physical damage to it at all. I know the battery should be just fine. But since the screen doesn't turn on or connect to a computer there's no visible way of knowing its charging
Sent from my PC36100

fictitiousexistence said:
Well there's no physical damage to it at all. I know the battery should be just fine. But since the screen doesn't turn on or connect to a computer there's no visible way of knowing its charging
Sent from my PC36100
Click to expand...
Click to collapse
It appears that the vortex is similar to the optimus.
try "removing the battery with the cable unplugged, then plugging in the cable and pressing vol up home and power at the same time."
as quoted from ichihollow at android central.

Is My VZW S3 Dead? (Symptoms in Text)

About three days ago, in the middle of the day, I tried to unlock my Verizon S3 using the power button, but it remained on a black screen. I pulled the battery, replaced it, and tried again. It came on.
Over the next day, it performed this behavior three more times; this time, however, the "black screen, unresponsive" happened while I was using the device (e.g., reading reddit in Reddit Sync when the screen darkens and the device becomes unresponsive and silent). The first two times, a battery pull let me restart the device.
The third time, however, nothing would restart the S3. A different, fully charged (and tested working) S3 battery would not start it. Plugging it into multiple chargers and multiple computers--both with and without a battery--would not start it. Plugging it into a PC fails to install drivers, and the S3 is identified as a "QHSUSB_DLOAD" device by Windows.
Plugging it in sans battery will sometimes briefly illuminate the red charging light, but it eventually turns off on its own, or goes off if I hold the Power button or put a battery in. I cannot access Recovery or Download Mode using the standard button combinations; there is no vibration, no flash on the screen, no change on the LED, and no sound. No input I give the phone appears to have any effect at all.
----------------------------------------------
The phone was running an unlocked, rooted version of 4.1.2, but had no other modifications, and had not had any major system changes in the months prior to this starting. I haven't recently messed with the bootloader, taken the 4.3 update, unrooted, rerooted, or anything else aside from letting apps update naturally and using the phone as always (reading reddit, using Hangouts to chat, listening to music with PowerAmp).
I read about the "Sudden Death Syndrome," but that supposedly applies only to International S3s. I read about hardbricking via screwing up your bootloader or triggering the eFUSE protections, but since I wasn't messing around with any of that for months now and also since I did not take the 4.3 update, I suspect it wasn't the cause.
Reps at the store weren't able to resuscitate the device, but told me I was ineligible for warranty service (I have extended) due to a hairline fracture on the case an inch below the power button (this crack has been there for months).
The device hasn't suffered any water damage or recent drops and was otherwise fully functional before the first blackscreen a few days back. I can't afford an Insurance swap right now, so self-repair is my only hope of having a working phone before my next paycheck hits in a few weeks

Armando Penblade said:
About three days ago, in the middle of the day, I tried to unlock my Verizon S3 using the power button, but it remained on a black screen. I pulled the battery, replaced it, and tried again. It came on.
Over the next day, it performed this behavior three more times; this time, however, the "black screen, unresponsive" happened while I was using the device (e.g., reading reddit in Reddit Sync when the screen darkens and the device becomes unresponsive and silent). The first two times, a battery pull let me restart the device.
The third time, however, nothing would restart the S3. A different, fully charged (and tested working) S3 battery would not start it. Plugging it into multiple chargers and multiple computers--both with and without a battery--would not start it. Plugging it into a PC fails to install drivers, and the S3 is identified as a "QHSUSB_DLOAD" device by Windows.
Plugging it in sans battery will sometimes briefly illuminate the red charging light, but it eventually turns off on its own, or goes off if I hold the Power button or put a battery in. I cannot access Recovery or Download Mode using the standard button combinations; there is no vibration, no flash on the screen, no change on the LED, and no sound. No input I give the phone appears to have any effect at all.
----------------------------------------------
The phone was running an unlocked, rooted version of 4.1.2, but had no other modifications, and had not had any major system changes in the months prior to this starting. I haven't recently messed with the bootloader, taken the 4.3 update, unrooted, rerooted, or anything else aside from letting apps update naturally and using the phone as always (reading reddit, using Hangouts to chat, listening to music with PowerAmp).
I read about the "Sudden Death Syndrome," but that supposedly applies only to International S3s. I read about hardbricking via screwing up your bootloader or triggering the eFUSE protections, but since I wasn't messing around with any of that for months now and also since I did not take the 4.3 update, I suspect it wasn't the cause.
Reps at the store weren't able to resuscitate the device, but told me I was ineligible for warranty service (I have extended) due to a hairline fracture on the case an inch below the power button (this crack has been there for months).
The device hasn't suffered any water damage or recent drops and was otherwise fully functional before the first blackscreen a few days back. I can't afford an Insurance swap right now, so self-repair is my only hope of having a working phone before my next paycheck hits in a few weeks
Click to expand...
Click to collapse
Quite a story, somehow you hard bricked it, This happens sometimes and I can't really explain why, but here's your fix:
http://forum.xda-developers.com/showthread.php?t=2581166
Make sure you have all the necessary equipment and use the 4.1 debrick image in the thread, you should be able to get it working again without a jtag repair.
Sent from my SCH-I535 using Tapatalk 2

BadUsername said:
Quite a story, somehow you hard bricked it, This happens sometimes and I can't really explain why, but here's your fix:
http://forum.xda-developers.com/showthread.php?t=2581166
Make sure you have all the necessary equipment and use the 4.1 debrick image in the thread, you should be able to get it working again without a jtag repair.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
This doesn't seem to have any effect on the proceedings.
I created the recovery IMG SD Card, but after putting it into the S3, pressing the power button on the phone (or plugging it into a PC) still has zero effect. It's like it's not even trying to boot and failing (or failing over to SD Card). Basically, pressing the power button/plugging in has zero effect at all, not just an unsuccessful effect.

Armando Penblade said:
This doesn't seem to have any effect on the proceedings.
I created the recovery IMG SD Card, but after putting it into the S3, pressing the power button on the phone (or plugging it into a PC) still has zero effect. It's like it's not even trying to boot and failing (or failing over to SD Card). Basically, pressing the power button/plugging in has zero effect at all, not just an unsuccessful effect.
Click to expand...
Click to collapse
But that's what it's supposed to look like when it's hard bricked, keep trying to write it then boot with it. Eventually it's going to work, unless you somehow fried your motherboard.
Sent from my SCH-I535 using Tapatalk 2

Is it possible that writing to the SD card via another smartphone (my old Droid 1) would cause the write operation to fail? I don't have any other method of getting the PC to communicate with a microSD card except via cellphones, since I don't have a USB adapter or even a microSD to SD adapter.
Edit: The D1/PC do recognize that something has happened to the SD card after Win32diskimager is done with it, because the D1 reports that it's now a "blank SD card (unsupported file system)" and Windows can't properly mount it anymore in that state. So, W32DI is definitely doing something to it. Tried 3 times now; is there some upper bound on how many to go for before assuming the motherboard died?

Armando Penblade said:
Is it possible that writing to the SD card via another smartphone (my old Droid 1) would cause the write operation to fail? I don't have any other method of getting the PC to communicate with a microSD card except via cellphones, since I don't have a USB adapter or even a microSD to SD adapter.
Edit: The D1/PC do recognize that something has happened to the SD card after Win32diskimager is done with it, because the D1 reports that it's now a "blank SD card (unsupported file system)" and Windows can't properly mount it anymore in that state. So, W32DI is definitely doing something to it. Tried 3 times now; is there some upper bound on how many to go for before assuming the motherboard died?
Click to expand...
Click to collapse
Not really, if you're getting that error message I'm assuming this should work. At the very least you could get a jtag repair and that'll definitely fix it. You could always try the other debrick file available from that thread also.
Sent from my SCH-I535 using Tapatalk 2