Hey, has anyone come across this issue? I tried partitioning my SD with recovery-clockwork-4.0.1.5-shooter.img. It appeared to have done its thing. After I hit reboot, the screen went dead... phone doesnt power up any more. Even after pulling the battery, when plugged in to the pc, I get a 'new hardware found' notice. I am thinking it is bricked. Thoughts? Anyone?
dan0412 said:
Hey, has anyone come across this issue? I tried partitioning my SD with recovery-clockwork-4.0.1.5-shooter.img. It appeared to have done its thing. After I hit reboot, the screen went dead... phone doesnt power up any more. Even after pulling the battery, when plugged in to the pc, I get a 'new hardware found' notice. I am thinking it is bricked. Thoughts? Anyone?
Click to expand...
Click to collapse
Weird. It seems someone else had your exact problem.
http://forum.xda-developers.com/showthread.php?t=1199862
Good luck.
Sent from my PG86100 using XDA App
k2buckley said:
Weird. It seems someone else had your exact problem.
http://forum.xda-developers.com/showthread.php?t=1199862
Good luck.
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
Yes, I have seen a couple of these posts. Strangely enough, I flashed Clockwork recovery to allow me partition my SD. The first hint that something was awry (after the partitioning) was when parted->print returned Error: Can't have overlapping partitions.. In any case, I will head over to sprint to ask for a fix (or replacement).
So, I was able to get a replacement for my EVO 3D today. A routine task like partitioning an SD card with a supposedly safe software can turn your phone to paper weight.
Sent from my PG86100 using Tapatalk
Related
Just throwing it out there. As the title states. I attempted the S-off, failed a couple of times, more than likely due to my timing on the wire trick. Then my computer was unable to find device anymore. Long story short, I got my rom to reboot, however the phone will not connect to computer or charge. Tried Pc, Mac, different usb cords. Wiped, reinstalled rom, pulled battery, etc..
This is a risk that I took, and I take full responsibility for that. But just beware that this could affect your hardware and not just your software too, which makes sense because you are messing with the hardware. I am def in the minority here, but I thought I would share. But something to think about. The phone now still functions but I have to take out the battery to charge, and I can't push any files to the phone.
ive never heard of anyone's usb port getting fried with the s-off method but i guess it's possible since your basically grounding your device out.
I know it won't help you with fastboot, but you can still do ADB over wireless. Look for instructions on how to enable it via terminal, or just go the the store and find a widget or app to enable it. At least with functional ADB, you can still push files to your phone using wifi tether or if they are on the same wireless network.
Someone else had the same issue and is testing a possible fix for me. If it works ill post a thread but there is a good chance it is dead.
con247 said:
Someone else had the same issue and is testing a possible fix for me. If it works ill post a thread but there is a good chance it is dead.
Click to expand...
Click to collapse
do you think the wire trick is causing this? if soo that's kinda scary.
fix-this! said:
do you think the wire trick is causing this? if soo that's kinda scary.
Click to expand...
Click to collapse
I had the exact same thing happen to me on my original Rezound, while I was doing all sorts of fastboot stuff to completely wipe it and prepare it to be shipped back to Verizon. In the end, it shipped back to them in a state where it would ONLY boot to hboot, because it had no /boot or /system or /data or /recovery partitions or anything. I don't really know what happened, but before I could run the RUU to complete the job, the USB connection just stopped working and it wouldn't charge. Exactly the same situation, except it was on its way back to Verizon anyway with a dead screen so I didn't bother to investigate any further.
To the people who have had the problem, were you using an uninsulated wire?
tekhna said:
To the people who have had the problem, were you using an uninsulated wire?
Click to expand...
Click to collapse
Or else inadvertantly touched the wrong terminals ? Just trying to figure out how it could happen.
lack of usb function was a product of a corrupted misc image on the HTC Desire. It is possible the same thing happened here so that is being tested. It is worth looking into as a last resort before sending it back.
Yes I was using an insulated wire. I placed the wire exactly where the pictures show. I'm really not sure what happened. But at least I have a backup phone.
Sent from my Galaxy Nexus using XDA
con247 said:
Someone else had the same issue and is testing a possible fix for me. If it works ill post a thread but there is a good chance it is dead.
Click to expand...
Click to collapse
Thanks con
Sent from my Galaxy Nexus using XDA
Knew I didn't wanna do it.
Sent from my ADR6425LVW using xda premium
http://forum.xda-developers.com/showthread.php?t=1620803
Here's a case of fried USB but no s-off. Currently unlocked. Any ideas?
Snuzzo said:
http://forum.xda-developers.com/showthread.php?t=1620803
Here's a case of fried USB but no s-off. Currently unlocked. Any ideas?
Click to expand...
Click to collapse
Sounds like he is in the exact same boat as me. Will be following that thread as well.. Thanks.
Me three
In same Boat.
Please post a cure if you find one.
Another nice option for transferring files is SSHDroidPro used with something like WinSCP.
I know you tried wiping your rom, but did you try an RUU? On the off chance it is a corrupted partition that might be able to fix it. Worth a try anyway.
I didn't do anything out of the ordinary...?
I wiped everything, reflashed a ROM, nothing new.
The only thing I did out of the ordinary was tried to wipe internal storage because it is getting too messy, and anything I care about is on the external storage. It fails when trying to wipe it, so I went to unmount internal storage. I rebooted to take out my sad card just to be safe. When I went to turn it back on, nothing.
Not even an orange light to show it is charging.
Any ideas?
Never had something this close to bricking happen.
I don't think I did anything damaging...?
I guess my question is, does bricking include an unresponsive battery?
Any ideas as to why the battery isnt even charging?
Can you get into recovery?
Sent from my Transformer Prime TF201 using Tapatalk 2
Not unresponsive battery per se but the hardware related to charging could be unresponsive
typhoonikan said:
I guess my question is, does bricking include an unresponsive battery?
Any ideas as to why the battery isnt even charging?
Click to expand...
Click to collapse
Yeah unfortunately or does mine bricked the other day man lol had to rake it to a sprint repair store and got a new one the next day
Sure sounds like its bricked. I really don't think you have any choice except spring replacement. I recently bricked mine and I couldn't find any tools or tricks to help.
Good luck man
Sent from my EVO using xda app-developers app
If you flashed a new Rom based on the latest ota on old firmware you won't boot because of the kernel. Try holding power volume down to get into bootloader and from there recovery
Sent from my EVO using Tapatalk 2
So last night, my phone decided that it would no longer like me to use it. The screen is a full screen of (for lack of a better term) rainbow snow. It is pixelated. I can't see anything except the snow. I have gotten it to show my lock screen by kind of tweaking the phone by bending slightly. When I get the lock screen, the touch screen no longer works. I can hit the power button to turn the screen off, and then again to only get the snow. I am thinking it's probably a hardware issue. I haven't dropped it or gotten it wet. Which leads me to my next question. I am rooted and running CM 10.1. I can't get in to recovery mode to restore to a stock ROM. If I take it in to Sprint for repair/replacement will they have a way of seeing I am running a ROM and decide they wont't work on my phone?
thedanpal said:
So last night, my phone decided that it would no longer like me to use it. The screen is a full screen of (for lack of a better term) rainbow snow. It is pixelated....
Click to expand...
Click to collapse
Is it possible that you CAN get into recovery and you just don't know it because you can't see it? Work with me here.
If you can power down the phone, try powering up into bootloader/fastboot and try to flash an appropriate RUU from fastboot/usb. Just a shot in the dark...
http://forum.xda-developers.com/wiki/index.php?title=Flashing_Guide_-_Android
tmwilsoniv said:
Is it possible that you CAN get into recovery and you just don't know it because you can't see it? Work with me here.
If you can power down the phone, try powering up into bootloader/fastboot and try to flash an appropriate RUU from fastboot/usb. Just a shot in the dark...
http://forum.xda-developers.com/wiki/index.php?title=Flashing_Guide_-_Android
Click to expand...
Click to collapse
That is a very good chance. I will give it a shot tonight. Thanks for the idea.
I pretty much have no idea what to do now. My phone won't mount the SD card on any computer. The phone recognizes the SD card, i just wont mount it. When trying to use RUU i just get the error 170. So, i guess i will be dropping my phone off at sprint and hope for the best.
Same issue. Was running Carbon which is cm based. Tried everything, nothing worked. Took it to the Sprint store yesterday and they got me a refurbished LTE. I'm thinking of getting the HTC one but can't afford it right now. Refurb phone works alright so I'll just keep it for know but I know what you're going through. it sucks and although the ROM worked awesome it may have been the culprit.
Sent from my EVO using xda app-developers app
SiGuy11 said:
Same issue. Was running Carbon which is cm based. Tried everything, nothing worked. Took it to the Sprint store yesterday and they got me a refurbished LTE. I'm thinking of getting the HTC one but can't afford it right now. Refurb phone works alright so I'll just keep it for know but I know what you're going through. it sucks and although the ROM worked awesome it may have been the culprit.
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
The tech thought it was a connection issue with the display, but he couldn't get it fixed and thinks the motherboard went bad. They are replacing the phone with a new one, but they are backordered so I have to wait a week.
Yeah but what caused all of our phones to have the same issue that doesn't exist on sense roms? Kernel overpowering the motherboard causing it to fry?
Sent from my EVO using xda app-developers app
So last night, when going to charge my phone, I notice that turning the screen on wasn't bringing me to my lockscreen. Instead it was a black screen with a line in the middle. It looked like the screen off animation got stuck on the screen. So I rebooted it and it was fine.
Today, I wake up and it won't respond at all. Holding the power button does nothing, it doesn't look like it's charging either. I know that I have it set up to run lagfix at night, could that have been the cause of this? Is there any way to come back from a brick?
shmallow said:
So last night, when going to charge my phone, I notice that turning the screen on wasn't bringing me to my lockscreen. Instead it was a black screen with a line in the middle. It looked like the screen off animation got stuck on the screen. So I rebooted it and it was fine.
Today, I wake up and it won't respond at all. Holding the power button does nothing, it doesn't look like it's charging either. I know that I have it set up to run lagfix at night, could that have been the cause of this? Is there any way to come back from a brick?
Click to expand...
Click to collapse
Yup, there is a way to fix this. Visit your local Sprint store and have it replaced. Hope you have insurance, if not its $50. Gods peed to you.
MeestaAytch said:
Yup, there is a way to fix this. Visit your local Sprint store and have it replaced. Hope you have insurance, if not its $50. Gods peed to you.
Click to expand...
Click to collapse
No insurance. :crying:
After plugging the device into the computer, it says QHSUSB_DLOAD. So I guess that confirms it was from lagfix.
shmallow said:
No insurance. :crying:
After plugging the device into the computer, it says QHSUSB_DLOAD. So I guess that confirms it was from lagfix.
Click to expand...
Click to collapse
Well you're going to have to pay the $50 then. And yea its from the "lagfix". That "lagfix" is really just TRIM. It's disabled off CM10.2 currently for this exact reason. It's been having a grand ole time causing a brickfest.
MeestaAytch said:
Well you're going to have to pay the $50 then. And yea its from the "lagfix". That "lagfix" is really just TRIM. It's disabled off CM10.2 currently for this exact reason. It's been having a grand ole time causing a brickfest.
Click to expand...
Click to collapse
I thought even if you had insurance you had to pay to get a replacement? Isn't only the in-store repair free?
shmallow said:
I thought even if you had insurance you had to pay to get a replacement? Isn't only the in-store repair free?
Click to expand...
Click to collapse
You only pay the deductible if the phone is lost or stolen. For hardware failure, with TEP, there should be no charge for a replacement device.
Jtag might be another alternative, as well. Shoot XDA member Zarboz a PM for more info.
Sent from my EVO using XDA Premium 4 mobile app
PM'd Zarboz. But is there any way for me to unbrick it myself? I'd really like to leave going to sprint or mailing my phone away as a last resort. I've found a few unbricking tutorials, but they say that they're only for bricks that occur when going S-Off. Would it be crazy to try one of those anyway?
shmallow said:
PM'd Zarboz. But is there any way for me to unbrick it myself? I'd really like to leave going to sprint or mailing my phone away as a last resort. I've found a few unbricking tutorials, but they say that they're only for bricks that occur when going S-Off. Would it be crazy to try one of those anyway?
Click to expand...
Click to collapse
It won't work. You're not the first person to have this type of brick. It occurs as a result of faulty hardware, which can only be replaced, or flashed directly with JTAG (and even then, you'd still have the same hardware, and be prone to the same issue again).
I guess you missed the part in the Lagfree app OP that mentions the "brick bug."
Captain_Throwback said:
It won't work. You're not the first person to have this type of brick. It occurs as a result of faulty hardware, which can only be replaced, or flashed directly with JTAG (and even then, you'd still have the same hardware, and be prone to the same issue again).
I guess you missed the part in the Lagfree app OP that mentions the "brick bug."
Click to expand...
Click to collapse
Well, no, I saw it. I thought I would be fine because I only saw the affected devices as samsung ones. Thanks for the input though. I'll just replace it or wait until I can upgrade.
shmallow said:
Well, no, I saw it. I thought I would be fine because I only saw the affected devices as samsung ones. Thanks for the input though. I'll just replace it or wait until I can upgrade.
Click to expand...
Click to collapse
Might help if you go to the thread and mention that this device appears to be affected as well, otherwise more may suffer your fate.
Bricked??
Yesterday I restored a backup that I've been running for mounths, restored fine and no issues. Today I got a text went to unlock the device, had snow like an old tv with no signal. I pressed home and got the lock screen but there was major screen tear and the device was very slow to respond. I managed to get to twrp recovery and there was also screen tear/snow and the middle 2/4 was not there and non responsive, so couldn't wipe, fix perms or restore any thing. Tried that a few times, now the only response I get is I hold the power button for 10-15 seconds, capasitive buttons flash, let go of button, half a second later there is a quick vibration and black screen. I can't get in to the bootloader or recovery. Am I hosed?? tia Also when I charge it the light doesn't go on
I too had this issue, but my phone went white then turned off and never turned
Back on. It was a hardware failure. They replaced mine for free.
Sent from my EVO using xda premium
I plugged the device after a while and the orange light comes on like it is charging?? Is that a good sign?? I try adb commands but it came up device not found. Any suggestions?
robbo10 said:
I plugged the device after a while and the orange light comes on like it is charging?? Is that a good sign?? I try adb commands but it came up device not found. Any suggestions?
Click to expand...
Click to collapse
Let it charge for a good long while, then try to power it up.
Sent from my EVO using XDA Premium 4 mobile app
FinZ28 said:
Let it charge for a good long while, then try to power it up.
Sent from my EVO using XDA Premium 4 mobile app
Click to expand...
Click to collapse
OK i'll try that, the phone was at 90% when all this happened idk??
mammothjojo88 said:
I too had this issue, but my phone went white then turned off and never turned
Back on. It was a hardware failure. They replaced mine for free.
Sent from my EVO using xda premium
Click to expand...
Click to collapse
If I still had insurance I would do this, but I'm not sure a new Evolte is worth $50 to me, especially with my upgrade around the corner. I'll just have to say farewell to this phone. It was a good run.
FinZ28 said:
Let it charge for a good long while, then try to power it up.
Sent from my EVO using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Let charge for a while it booted and got stuck on the splash screen but the coloring was off. I plugged it in to the computer ran "adb devices" and it found it said recovery and a long number. I tried "adb reboot bootloader" black screen and that was it.
Sent from my PC36100 using xda app-developers app
robbo10 said:
Let charge for a while it booted and got stuck on the splash screen but the coloring was off. I plugged it in to the computer ran "adb devices" and it found it said recovery and a long number. I tried "adb reboot bootloader" black screen and that was it.
Sent from my PC36100 using xda app-developers app
Click to expand...
Click to collapse
Looks like an issue with the screen. If you have TEP I'd take it to Sprint and let them look at it. Shouldn't cost you anything to get it replaced.
Sent from my EVO using XDA Premium 4 mobile app
Wow, you guys were right, you do get a free replacement.
At first, I was set on just living with my mother's old SG4G, but I couldn't stand how outdated it was. The screen looked meh, and I couldn't even install Chrome on it. So I was ready to pay the $50 to replace it, went to sprint with my evolte, and the guy there said he could only service active phones. So he changed my active phone back to my evolte, and added insurance to it. So I walked in with a broken phone without insurance, and left with a new phone for free. I'd say that's a lucky day.
Thanks for your advice guys, you guys just got me a new phone for free.
Okay I've never bricked a phone (lucky maybe) ever with all the phones I've owned. However I think my v10 is bricked? How can I tell?
Symptoms for diagnosis for the experts here at XDA, it keeps rebooting -bootloop at LG startup screen and never goes into recovery. Once in a 100 times makes it into TWRP (power button and volume down) but as soon as I click the screen it bootloop again. I can get into fastboot (volume down USB) and have tried sending a boot.img and recovery.img several times so far and still not holding TWRP recovery. ADB also won't show a device only fastboot device command shows the phone.
I had a Samsung phone once that behaved similarly, just kept on rebooting no matter what I did(didn't sit there forever, it would actually keep shutting down and trying to boot, repeatedly). Same in download mode. I sent it in and they replaced the digitizer, I believe. Could be the same, but keep trying everything!
Sent from my LG-H901 using XDA-Developers mobile app
Even though stays on
YrrchSebor said:
I had a Samsung phone once that behaved similarly, just kept on rebooting no matter what I did(didn't sit there forever, it would actually keep shutting down and trying to boot, repeatedly). Same in download mode. I sent it in and they replaced the digitizer, I believe. Could be the same, but keep trying everything!
Sent from my LG-H901 using XDA-Developers mobile app
Click to expand...
Click to collapse
Yeah I thought something like that, but because it doesn't do a reboot when I get into recovery or download (can stay on indefinitely) I thought it might be something else.
How did it get into this condition? Were you flashing something?
Sent from my LG-H901 using XDA-Developers mobile app
Just happened
YrrchSebor said:
How did it get into this condition? Were you flashing something?
Sent from my LG-H901 using XDA-Developers mobile app
Click to expand...
Click to collapse
Nope just happened. Was traveling outside USA and when it registered it did this. Didn't work when came back to the USA so figured maybe try to reinstall software (thinking it might be that) again to fix. So thinking maybe your theory of a hardware failure is possible. and maybe should just try to get an exchange.
webfrm said:
Nope just happened. Was traveling outside USA and when it registered it did this. Didn't work when came back to the USA so figured maybe try to reinstall software (thinking it might be that) again to fix. So thinking maybe your theory of a hardware failure is possible. and maybe should just try to get an exchange.
Click to expand...
Click to collapse
ah ok, sounds like it wasn't your fault, so an exchange should hopefully be in order. keep us posted