So as my friends all like to annoy me as they know I'm a bit ocd I recently inherited what I believe is a z1 with problems. Wondered if anyone can shed light as I'm starting to think it's completely duff.
It does not appear to turn on, or charge. I assumed completely zeroed battery however long charge makes no difference. On a software repair, at the stage of hold volume down and connect USB it goes no further. I've tried ensuring it is definitely off multiple ways. However on occasion it has connected to pc companion and it says your device is locked please unlock. Still nothing on device screen.
I've tried vysor but obviously even if it's just a dead screen, USB debug isn't enabled as that's a no go to.
I've tried the yellow off button in sd/sim tray slot multiple times. It makes no audible sound itself at any point eg turning on/off, volume up/down, swiping screen etc.
The only reason I haven't given up so far as a dead screen is that it appears to not want to charge, and that even though pc companion says its on which implies a dead screen there's no sound either.
Any suggestions as I do hate to see a potentially usable phone go to the bin.
Even just data recovery would be a start but can't establish any adb or fastboot connection, again due to debug and not knowing what state the phone is in at any given time
Sent from my CLT-L09 using Tapatalk
Nevermind. Had the battery out....... 2.6v.......good old Sony.
Still, the no screen and dead battery but pc companion advising the phone is on and locked is interesting
Sent from my CLT-L09 using Tapatalk
Related
Hi,
Searched the forum and didn't really find anything like the problem I'm experiencing (even though I might be very wrong on this ).
My device is S-OFF, has clockwork recovery etc. And I was using a custom ICS build (namely this: http://forum.xda-developers.com/showthread.php?t=1424260 )
And earlier today it froze (not super uncommon ). But I had to remove the battery because it was non responsive.
But anyway. Now it's dead!
Nothing happens when I press the power button.
Tried it by removing the battery a couple of times, pushing the button again.
No sound, no buzz, just pitch black screen.
Tried booting into the bootloader with "Vol Down + Power button". Same result here. Just black screen.
Tried connecting it to the PC to boot into bootloader from there. But the PC doesnt even recognize that I have plugged something in
(using dmesg says nothing about a device being connected.. which usually is not so good )
The only sign of "life" I get is when I connect the phone to the charger (or usb cable to the computer) without ever tried booting it with "power button" or "power button + vol down" is that the LED lights up orange.
If I have tried to turn it on it will not light up orange.
I have tried to have it for a few hours (with the light orange) on the charger, then booting it.. But with no luck
I kinda feels like my device has died! I dont really feel it has been bricked? Maybe hardware malfunction? which sucks since my warranty will not be valid because of S-OFF
Anyone have any ideas or tips on what I could possibly try with?
If you were overclocking, the cpu may have overshot. Probably 'hardwear'...
You might take it to a repair facility to diagnose if they can help.
If computer doesn't read it and no boot, nothing you can "do" yourself...
Sounds like brick :what:
sent from xda premium on an Incredible S
Check to see if it responds to any ADB/fastboot commands
cant run any adb commands
Since it's not recognized at all by my computer I cant do any adb commands.
Not list the device, not do fastboot etc.
I still have warranty on the phone, will the repair shop be able to see that I have taken it S-OFF? Or will they most likely just replace the motherboard?
The company I have to leave it to is notorious for being the biggest assholes in the history of this earth
and yeah... I had it overclocked! but only by one step (from oc virtious quattro) or perhaps 2 steps max.
If you cannot see the device on the PC at all, the service centre won't know that you are s-off. If you have a windows install, check in the device manager to see if the phone is detected at all.
Yeah htc has so many repairs they don't have time to mess around dude. They'll try to turn it on, and it won't, so they'll try a fully charged battery and it won't turn on again, they'll throw from anew motherboard in after that and if that doesn't work they'll give you a brand new phone. I'd say you have a 5% chance of them finding out your s-off.
Sent from my anus using xda crap
Hello
Recently i've bought an broken screen Xperia Z, for repair it (i got it like $300 bucks cheaper) and i was ready to buy the screen, but i battery was drained and i could not test it right, when i connected to the charger, it started red light, vibrate, then 3 continuous vibes, read on the internet, OK BATTERY DRAINED, i left it charge THE WHOLE NIGHT, and when i woke up in the morning it was orange (charging), later in the day it was green (charged) but when i disconnect it, it wont turn on anyways, when i connect it to a pc, it goes blue light (wich later i read it was fastboot mode). i read for making a repair with PCC, but it didnt fixed it, then i flashed it with Flashtool, with the latest software (wich had the Sudden death issue fixed) no luck. it wont boot. for it to boot, i have to connect it to PC and with fastboot run "fastboot continue", but most of the time, it reboots and goes redlight and vibrate 3 times then reboot, so i press the power button and it enters fastboot mode (if connected to PC) or loads charging if connected to wall charger, but it reboots again and goes to redlight vibrate reboot, sometimes it stay charging or in fastboot mode, but only "works" if connected in the USB.
when it stays in fastboot, i do "fastboot continue" and it loads the OS, and it works (well, the things i can do with a broken LCD/Touchscreen, i put my sim card and could call it, and it works, but i cant pick up the call). i can explore the phone memory etc. but if it reboots or if i disconnect the USB, it will almost always turn off. i havn't found a solution (or idea) of what can happen, i dont know if its normal since it has broken lcd/touchscreen or it definitely have a huge problem,
any ideas?
thanks in advance!
Maybe the battery is damaged, and the phone knows it and boots into some sort of safe mode to spare internal damage? When the is has booted you can take screenshots with adb if you have usb debugging enabled. Maybe try see if the os says the battery is damaged?
Sent from my HTC Sensation XE with Beats Audio Z715e using Tapatalk 2
heavy_metal_man said:
Maybe the battery is damaged, and the phone knows it and boots into some sort of safe mode to spare internal damage? When the is has booted you can take screenshots with adb if you have usb debugging enabled. Maybe try see if the os says the battery is damaged?
Click to expand...
Click to collapse
Well, actually it doesnt seem the battery is damaged, fisically looks ok and it holds charge, i cant debug because usb debugging comes off by default when flash stock software.
blackknigt said:
Well, actually it doesnt seem the battery is damaged, fisically looks ok and it holds charge, i cant debug because usb debugging comes off by default when flash stock software.
Click to expand...
Click to collapse
Correct me if i am wrong but does the xperia z not support usg-otg and mhl? You could rig the phone up to the tv with a mhl-hdmi cable and maybe use a usb mouse to select things, and enable usb debugging?
Sent from my Nexus 7 using Tapatalk 4
Nice idea, now i need to find who in this country (DR) have that adapter
i ordered the LCD screen assembly for repair it myself, but im still concerned about this, as i dont know if it will boot up anyways
my phone right now isnt booting. but as i cant see images i dont know what is it showing.
i noticed the touch screen is working indeed. (when booted, it plays sounds when tapping)
i will wait till the lcd assembly arrives. any ways, any other ideas on what may happen?
the ex-owner of the phone said it started like that when it fell and broke the lcd.
OK now, i've installed the LCD, the phone works, its ON, BUT the Volume Up button and the Power Button does not work when the phone is ON,
the Vol UP button seems always be pressed cause when i press the power button for some seconds, the Phone restarts and not power off or lock/unlock
Service tests: None of these buttons where recognized.
any ideas on any hardware fixes i could try?
I FIXED IT!!
dissasembled the phone, took out the side button flex cable and the volume up button on the flex was dirty, so it was having a false contact. (wich made the button always be pressed)
I took out the yellow tape and cleaned with alcohol and a needle (its so freakin small) and put the tape again and assembled the phone and voila! IT WORKS OK!!
Yes the vol up button pressed means u get fastboot. Now that you fixed the problem and repaired the phone enjoy. Btw nice job getting it up and running.
[email protected] Z
I'll started off by saying that my bootloader is unlocked and I have flashed the Android 5.0 ROM (503b) from here: http://forum.xda-developers.com/xperia-z/orig-development/exp-lollipop-xperia-z-t2929369
Sorry if this is a bit long but I thought it'd be best to tell you the steps leading up to the potential death of the phone.
As far as I can tell the issue doesn't stem from a software fault as I've been running the ROM solidly for 2 weeks now with no issues apart from not being able to hear a call when I accept with something plugged in the headphone jack.
I wake the phone and go to unlock it and the touchscreen is unresponsive. I have known it to take a second or two to wake up so I gave it a minute then tried again.
No response. Screen hadn't dimmed either so I suspected it had crashed.
Held the power button and the power off prompt appears along with all my previous actions unfolding beneath it. Just for good measure I decide I'll reboot the phone as I sometimes do when it starts to lag.
Powered off fine. Go to turn it on and nothing happens.
Battery was on about 20% when I turned it off so I plugged it in and tried again.
No LED light when I plug it in, still no response to any button combination. No recognition over USB either.
So I'm going to leave it plugged in overnight as I've seen it recommended by a couple of people before. Just wondering if anyone else has had this happen and if you managed to recover the phone?
lukeylad118 said:
I'll started off by saying that my bootloader is unlocked and I have flashed the Android 5.0 ROM (503b) from here: http://forum.xda-developers.com/xperia-z/orig-development/exp-lollipop-xperia-z-t2929369
Sorry if this is a bit long but I thought it'd be best to tell you the steps leading up to the potential death of the phone.
As far as I can tell the issue doesn't stem from a software fault as I've been running the ROM solidly for 2 weeks now with no issues apart from not being able to hear a call when I accept with something plugged in the headphone jack.
I wake the phone and go to unlock it and the touchscreen is unresponsive. I have known it to take a second or two to wake up so I gave it a minute then tried again.
No response. Screen hadn't dimmed either so I suspected it had crashed.
Held the power button and the power off prompt appears along with all my previous actions unfolding beneath it. Just for good measure I decide I'll reboot the phone as I sometimes do when it starts to lag.
Powered off fine. Go to turn it on and nothing happens.
Battery was on about 20% when I turned it off so I plugged it in and tried again.
No LED light when I plug it in, still no response to any button combination. No recognition over USB either.
So I'm going to leave it plugged in overnight as I've seen it recommended by a couple of people before. Just wondering if anyone else has had this happen and if you managed to recover the phone?
Click to expand...
Click to collapse
Do u have flashmode and fastboot and did u try this: http://forum.xda-developers.com/showthread.php?t=2229250
If u can get into flash mode, flash a full ftf with flashtool
langeveld024 said:
Do u have flashmode and fastboot and did u try this: http://forum.xda-developers.com/showthread.php?t=2229250
If u can get into flash mode, flash a full ftf with flashtool
Click to expand...
Click to collapse
Unfortunately no. The phone is doing absolutely nothing when any key combination is pressed and i've tried plugging it in via USB and doing these in case the LED light had developed a fault. Still nothing.
I am posting this update in aid of future Xperia owners:
Problem: I seemed to have experienced the infamous Xperia "Red Light of Death". Phone vibrated 3 times continuously when charged. Screen never came on. Led was only ever RED, and only came on sometimes, sometimes solid, sometimes blinking twice. Computers were not recognizing the Xperia. Neither volume UP or DOWN button presses were ever recognized by any software on either the Win 7 or Win XP installations. However, on a couple of occasions, both computers recognized there was a device on the USB when doing a reset (reset + power). This caused them to try to install drivers. But the drivers, if installed, did not successfully allow any of the software tools to recognize the phone. Nor was the phone recognized in Device Manager, when connected, even when the UP or other buttons were pressed at connection time.
I asked for assistance on 4 or 5 of the net's biggest android forums on this... none came. So I was quickly giving up hope on the Xperia, since it seemed like there was nothing else to do. It might have taken water for all I know, when it was not in my hands, and the mobo might be quiched.
Solution: The phone is charging right now, the screen and color LEDs work fine, the original system is fully intact, and I did not need to reflash a new ROM or anything. However, I'm not exactly sure how I resolved the problem. I'll go through *some* of the steps that preceded this breakthrough. The breakthrough may (or may not) be due Sony's "PC Companion". This is an older version of what Sony now calls "Xperia Companion" (which did nothing good for me, so I went with the older software). "PC Companion" was also useless to me, since it kept insisting on not working unless you allow a connection for it to update itself. But the update always failed, with no clue as to why, despite a/v & firewall disabled. I found a comment where one user said he was able to do a bit more with PCC, once internet was disabled. So I tried that, and yeah, I could at least convince PC Companion to see if it could recognize the phone once the internet was disabled. But just like Flashtools, adb, the Sony Xperia SP drivers and all the other tools, it didn't recognize the phone was plugged in. At least, not the first few times I tried it, using various button combinations. (Up, Down & Reset/Power). Finally, I got a blue light and the PC (Win XP install) started loading drivers for the device.
I'm just not sure what triggered the change. Was it a reset/power combo operation? Was it a slight shift in the motherboard or USB connector that did it? Was it due to (the THIRD install of) PC Companion, or it would have happened with other software eventually? Its hard to say. I think these things contributed to the solution: PC Companion, the reset/power combo press, and just a lot of perseverance, most importantly. (3 days working at it in my case!). If you get this same problem with your Xperia, good luck to you.
(Trust me. You'll need it).
Lent my Sony Xperia SP (C5306) to someone, and it came back in a state where it vibrates 3 times when powering on or charging (it stops vibrating after a while, then starts again). And it won't boot or show anything on the screen, and only a RED led light comes on occasionally. So now I'm stuck on trying to flash a stock ROM on a Win7 system, using Flashtool 0.9.18.6, after installing the Flashtool drivers for "Flashmode" and the SP model, and PC Companion (PC Companion didn't fully install, because it demands updating, and fails on the update -- despite no antivirus installed, and the Windows firewall set to "enable all'). So now my problem is Flashtool won't recognize the phone on the "Please connect your device into flashmode" step, when I press Volume Down before reconnecting the USB cable. I've even tried taking the battery out for a few minutes, no dice.
At a certain point, after hitting the reset button and other buttons, Windows finally recognized there was a phone connected, and automatically installed USB drivers. Yet despite this, Flashtool still wouldn't flash the ROM. I do get 1 error in red saying "ROOT: THIS BUNDLE IS NOT VALID". Presuming this refers to the ROM, I made sure it specified it was for my model (C5306) and its even from the original carrier (Bell). In any case, it still goes beyond that error and proceeds to prepare the files for flashing.
So I'm not entirely sure what's preventing Flashtool from recognizing the phone, since it could be many things. My best guess is the soft or hard brick condition its in: since you can't power down the phone properly, and removing the battery is apparently not the same thing, its not getting to the trigger point that activates Flashtool's flashing. I'm right now trying the "rubberband trick". The idea is to keep the Volume down button depressed with a rubber band, and eventually, the battery wears down and maybe Flashtool recognizes it when it bootloops. I don't get that though, since Flashtool requires you plug the phone in via USB. And if its plugged in via USB, the battery should not ever run down, since its being charged by the USB port.
The phone was rooted, and IIRC, I think my bootloader is locked, so let's assume that. Can anyone help me along on this?
A few days ago, my Sony Xperia SP also could not start up and would keep on vibrating when connected to mains powered charger or USB port of PC. I just wish to record here my experience, hoping it will help some Xperia SP owners facing similar problems.
I tried various suggestions found in various forums but without success, gave up and bought a new phone. The very next day I did a final try. I charged it for around an hour just before I sleep and disconnected it when it was still vibrating. Next morning (yesterday), I pressed the Reset button (marked "OFF" on the back of the set with back cover removed), each lasting about 8-10 seconds. I did not felt any vibration. Anyway, I proceeded to press the power button on the side. And the set turned on! The battery status was shown as 100%. I connected it to my PC just in case drained down battery would cause it to shutdown. I saw a message indicating update was available and proceeded with update which was completed successfully. I downloaded an app and transferred my contacts to my SIM card. (Doing a backup with Xperia Companion will take many hours and I am not sure my contacts could be moved to a non-Sony phone if the Xperia SP fails again later). It has been 24 hours after my SP had revived and it has behaved normally so far.
My thought on this incident is that the problem was not due to battery or some hardware inside the phone. The problem was very likely due to incomplete software updating.
My phone went to an endless bootloop after a botched attempt to install TWRP. I tried hard pressing the power button to no avail, and I can't access fastboot either. That's why I removed the back cover and disconnected the flex cable from the battery on the phone's motherboard.
Later on, I reconnected my phone's battery after my shift ended, then I tried to flash my stock rom through SP Flash Tool + bypass tool python script and it went through with a success. However, this time, my screen seems to be completely dead but my phone is still showing some signs of life (short vibration when pressing the power button, but since then it seems that it takes a few seconds more from pressing the power button to turn it on. ) I reconnected and disconnected everything to see whether or not I missed out something but the issue still persists.
The computer reads the device as "Android ADB interface" and the adb console reads it as *device id* unauthorized when I ran adb devices command. There's no notification light whenever I plug it into the charger.
Is my screen dead, or is my motherboard toast? I need to know as I don't want to spend money to buy a replacement LCD only to know that the motherboard's dead. I don't really care about the IMEI as I'm just going to use it as an authorization device for work. I can just always connect to Wi-Fi. Please advise.
One problem after another, so it seems.
Turns out I already unbricked the phone, but the thing is that my display's backlight got busted for some reason. Unless I shine a flashlight through it, I won't know what's in the screen. I'm currently on the way to get a replacement screen, and a new battery cover.
I guess this will be the last Xiaomi device that I'll ever get. This is the only time that I experienced such flimsy build quality since the LG G4.
Maybe you have destroyed a lil cable or something.