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.
Related
I successfully loaded WM6 on my Cingular 8125, but it had some weird issues (today screen didn't fully draw, ringtone screen wouldn't close, etc.) so I decided to go back to the stock ROM. But I thought I'd try a hard reset first and that's where I ran into problems. The screen stays white, but there's a constantly changing series of vertical colored lines that move all over the screen. I can't do a hard reset and can't get into the bootloader. All I get is the shifting white screen and ActiveSync won't see the device, but I get occasional USB bleeps/bloops when i plug the device in.
Any tips on recovering and going back to the original ROM? I've learned my lesson and won't fool with WM6 on my locked G4
Try turning your phone off, and then press and hold the camera button and then press the on button while still holding the camera button and that should put you in to bootloader mode. From there, download and flash the stock ROM from your service provider and see if that works. From your description of what it's doing though, it might actually be a hardware issue that just happened coincidentally at the same time you tried to flash a new ROM. Hopefully it's just software related though for your sake.
restarted my phone at work today and all it does now is go straight to the tri colour boot loader screen. Iv take sím out, SD card out, battry out, nothing works.
Put the USB cable in and it starts on its own straight to the tri colour screen without pushing start button
Any ideas..
Thanks Ahead
Maybe it´s as easy as that the camera-button is stuck? That happened to me with the power button. Now the power button is a bit "loose" in feel but is not active all the time.
yeap
I thought of that, iv pushed the camera button quiet a few times trying to see if its stuck but it didnt help at all, still doing it. If i connect the USB cable with no battery in it starts up on its own as well and goes straight to the boot loader screen.
Its says
WING220 MFG
SPL-0.91.hard
CPLD-7
USB
update
A quick update, if i actually put the USB headphones in the phone and try to start it it works. A restart with them in works to. Take them out and its straight to bootloader again. LOL Also Windows does not recognise the phone when its conected via USB cable when its running. This seems to be a USB problem of some kind. Iv done a hard reset as well, no luck.
Try this: enter bootloader and type "boot". If it again enters bootloader after restarting do the same thing again. Hopefully that fixes it.
hehe
No change. Only way to start the phone is with the headphones connected. When the phone is running and i conect it to the pc i get this " One of the USB devises attached to this computer has malfunctioned, and windows does not recognize it "
NoNco said:
No change. Only way to start the phone is with the headphones connected
Click to expand...
Click to collapse
Try "task 8" in bootloader and then "ResetDevice"
(ps do *not* experiment with other parameters!)
nope
When i used "boot" it made a buzz and went to a white screen, had to remove battry to restart, it didnt help, tried 3 times.
" task 8 " it goes dark for a split second and back to the bootlaoder screen. remove bat. restart back to bootlaoder screen
oh after i type task 8 i get an error that pops up in mtty
wceusbsh004 port read error occured
try Hard resting it but juss to let u kno IF U DO THIS U WILL LOSE a last memory u did even phonebook and all resets like new i had to do it cuz i had a prob i could not text n stuff now it works fine after HARD RESETING
doesnt work
Iv already done the hard reset from within WM when i get the phone to work, it didnt help.
Try the hard reset after re-inserting battery immediately at power on.
(keep left- and right softkey pressed and power on I think is the key combination)
mmm
trying to do it but i must be doing the key combination wrong. Just keeps going to tri colour.
I presume you meen the soft keys on the sides of the s730. Camera key and the Comm Key.
NoNco said:
trying to do it but i must be doing the key combination wrong. Just keeps going to tri colour.
I presume you meen the soft keys on the sides of the s730. Camera key and the Comm Key.
Click to expand...
Click to collapse
No, the softkeys are the two buttons next to the joystick, see here ->IMAGE<-
But I would think your mini-USB connector is kind of broken I'm not sure of course
nope
Iv tried the keys on the side, iv tried the keys on the keypad. i just dont get it to work...
mm
@ Jocky...
I eventually managed to do a hard reset, the problem was it just kept going to the bootscreen so i tried it with the headphones pluged in and then it worked, lol, but on the reboot it just went straight back to the tri colour screen again.. So no help there.
NoNco said:
@ Jocky...
I eventually managed to do a hard reset, the problem was it just kept going to the bootscreen so i tried it with the headphones pluged in and then it worked, lol, but on the reboot it just went straight back to the tri colour screen again.. So no help there.
Click to expand...
Click to collapse
Hmm, looks like a bootflag related to USB is set. The reason could indeed be a physical problem with the usb port of the device. Also it could be related to dirty contacts (both of the UB port and the battery).
I’m having the exact same problem with my S730. Only works with the headphones plugged. I can’t hear nor talk if unplugged the headphones. Does anyone knows how to fix this ???
hi, i have my htc touch diamond flashed with BElite's ROM and this is the first time it happened, and I can't boot the device. It will act like it's starting up, and past the first "htc touch diamond" that shows on the screen, it'll show hte RGB on the bottom right and go black normally, then show it again but with RGB lines all over the screen. sometimes itll make hte htc sound and show hte htc thing then go back to the rgb lines. when i hit reset, the screen is full of different colored lines up and down
Pikeru said:
hi, i have my htc touch diamond flashed with BElite's ROM and this is the first time it happened, and I can't boot the device. It will act like it's starting up, and past the first "htc touch diamond" that shows on the screen, it'll show hte RGB on the bottom right and go black normally, then show it again but with RGB lines all over the screen. sometimes itll make hte htc sound and show hte htc thing then go back to the rgb lines. when i hit reset, the screen is full of different colored lines up and down
Click to expand...
Click to collapse
Hard reset, and if that fails, reflash?
i hit the reset button on the back, but everytime it turns on, it just shows a messed up screen. sometimes white fuzz, sometimes rgb crazy lines, and i think my d-pad and the back is heating up a bit....sometimes itll show hte initial screen.
Pikeru said:
i hit the reset button on the back, but everytime it turns on, it just shows a messed up screen. sometimes white fuzz, sometimes rgb crazy lines, and i think my d-pad and the back is heating up a bit....sometimes itll show hte initial screen.
Click to expand...
Click to collapse
The reset button only does a soft reset, which doesn't sound like it's helping, try hard reset and see what that does.
i tried the hard reset method, but the message that's supposed to pop up doesn't show and no response. maybe its an overheat problem so im letting it sit. but i don't know. The warranty is obviously voided so sending it in is going to cost a lot of...cha-ching.
Hmm... before you flashed, did you do all the things like install HardSPL? If you connect the device to the computer, does it connect (so you can do another flash)?
yeah I have the HardSPL flashed on it. Everything has been working perfectly until this afternooon when i pulled my phone out of my pocket and the screen was fuzzed. I let it sit for hours and it SEEMED to get better because it showed the "device is preparing for first use" screen but the bottom half was crooked and off to a side. and it froze like that. btw thanks for all your help
I let it sit overnight, then this morning when i tried it. EVERYTHING was perfect, i got the date and time setup and the calibration, but when it started to load windows, it frozen, restarted itself and showed rgb dots around the touch diamond initial screen. Thanks for any help.
new symptom: when i plug it in to charge, both pc and ac, it shows that it's charging and it gets warm but, when i unplug it, it keeps showing the center key flashing in the circle it does when it's charging. and it never finishes charging.
Hey all,
I just installed a new digitzer on my Vivid. Everything went fine, and nothing broke as I was taking apart the phone, or putting it back together.
Now that the phone is back together, however, it is having some problems.
First off, When I try to power the phone on, it vibrates like usual, but then doesn't display anything. The phone then proceeds to enter in to a bootloop and keeps vibrating every couple moments. When plugged in to the computer, the orange light comes on for a few seconds, then turns off. Windows will not recognize the phone. All the while, the screen is completely black, and none of the lights come on for the buttons either.
The phone was working fine before replacing broken digitizer.
The phone is NOT rooted, nor has it ever been. I am running stock ICS.
have tried entering Hboot with no avail.
Any advice?
Thank you!
Can you get into any other modes? Try to get to hboot(hold down power button and volume down) while plugged into computer. Should take it to fastboot.
how long for? I tried holding down for a good 30 seconds...nothing happened other than my orange light turning off
I noticed with mine I had to go with:
Remove battery.
Replace battery
hold vol down + power
few seconds later release power
few seconds later in hboot
YMMV due to repair.
You can also try a knoppix boot disc and some tutorial to see if you can find any sign of life off the phone in dmesg.
hope this helps some.
Sounds like a loose connection. Make sure that you've correctly reconnected all internal connections. Especially the connection under the little door with the void sticker on the screw in the battery compartment. If after verifying all connections are made and proper, the problem persists, I'm sorry to say you may have physically damaged the connectors during disassembly. Please visually inspect all connections for damage. A powerful magnifying glass is recommended.
(I have successfully replaced my digitizer twice, and my LCD panel once on this phone...)
Sent from my HTC Dark Raider using XDA.
I have taken it apart twice, checked all connections, and everything is good. Phone cannot enter any boot mode, and computer still doesn't recognize it. The orange light still only stays on for a few seconds when plugged in, then turns off. The phone then proceeds to keep trying to restart itself, but the screen remains pitch black blank
idk.. get a replacement.?
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.