I accidentally dropped my s730 today. After doing so the screen froze and the phone didn't respond in any way so I turned it off by removing the battery. After trying to turn it on all i get is a split second fail message that says "No Image Found" and then i get a red, green, blue and white screen which says "WING220 SPL-1.31.0000 CPLD-7.
In the white portion it says "Serial" and when I connect with a USB cable it switches to "USB" other than that it doesn't respond in any way shape or form I've been able to figure out yet. A hard-reset using the soft buttons and on button hasn't worked either.
Any advice on how to fix this or am I screwed?
Just flash a rom
Have you put HardSPL or something on? Wouldnt have expected the phone to allow you into that screen without changes. I also wouldnt see it wiping your OS from the phone since its an SSD not a standard disc drive. In the drop you could have damaged the intnernal memory and now its showing the default screen from the chipset?
Give what Sh1n1 said a try and see if flashing a rom will take. Otherwise you might have something broken internally that needs to be repaired.
I haven't installed hardspl or anything like that. Guess I'll try flashing a rom.
What you are seeing is the Tri-Color-Boot screen. Accessed by pressing the camera button and powering on at the same time.
Sounds like the drop made the camera-button defect. Try prying it out carefully (don't pull it out of the shell) and powercycle the phone, or try pushing it some times with the power off. The power on the device.
Hi everyone ...
I recently disassembled my G1 to fix the touch screen. I acknowledge that I took the phone's fate into my hands when I decided to open it up, but I had done this twice before with no problems whatsoever. If these symptoms sound familiar to you, please let me know if you were able to fix your phone.
I put it back together, and now when I power it on, I get the short vibration that confirms the power-on ... but I get no screen image, no keyboard lights. So when this first happened I pulled the whole thing apart again to be absolutely sure I hooked up all the flex cables and ribbon cables. Yes, everything is connected. Everything. I've triple-checked it now.
What I did next was a couple of tests to see how "awake" or functional the phone actually is behind that blank screen. When I power it on and let it sit a couple minutes, so that I know it has finished booting ....
I CAN:
- boot the phone in normal or recovery mode. both modes produce the blank screen and no key lights.
- view the phone in ADB. (ADB tells me "device" or "recovery" mode)
- execute commands and view files on the phone with ADB shell.
- pull files off the phone with ADB.
- make the LED light up by plugging in the wall charger or USB cable when the phone is off.
I CANNOT:
- make any of the backlit keys turn on by pressing them.
- make the phone receive a call or a text.
- make the LED light up by a missed call, text, or plugging in the charger/USB when the phone is on.
My first impression is that I've done something terrible to the mainboard so the phone is somehow in this "semi-booted" state, where it won't run the screen. Is it possible that a bad cable to the screen could cause this? Thanks so much for your help.
Come on, no one can help me with this? I know I'm not the only one who has taken a G1 apart and met with disappointment.
Long story short, I've got a fairly new (~few months) totally stock Captivate that I can't get warrantied. So I dismantled it to clean the lock button out (I had done this to another Captivate maybe half an hour before and it now works just fine) because it wasn't working, but now the screen on this one won't turn on. I can hear the boot-up sounds (wooshing and whatnot from the Galaxy S screen), and the touch buttons at the bottom light up when touched, but the screen never comes on. When plugged into a computer, it isn't recognized. When plugged into the wall, there's no indication that it was charging at all, though I suppose it did since it now turns on and didn't before. I've tried holding the volume buttons and the power button to hard reset it, but that seemed to be totally ineffectual (screen didn't come on, no additional/different sounds).
Is there anything I can do to fix this phone for my mom before I leave the country for 5 months?
It sounds like one of the connectors isn't full engaged. Carefully take it back apart and ensure any cables coming from the screen are properly attached.
I hear this a lot. People dismantle their phones and when putting it all back together their ribbon wire to the screen isn't properly secured to its original state.
Sent from my SGH-I897 using xda premium
Thanks, that did the trick for the screen. Turns out the lock button still doesn't work, after cleaning it several times (I used CRC QD Electronic Cleaner). At least it's back to being mostly functional.
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
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.