I have been having probplems with my 6515 first it had no sound so I flashed it wilst at .1% it hung then it kept coming up with the boot loader if I removed the battery then put it back in again it would come up with the windows screen then I would configure it time ect it would restart and go back to the boot loader. I then flashed it with SP33246 which was the version it had when I lost the sound and halfway through the flashin it got a error 606 timeout with the USB. Now it won't boot out of the craddle and when its in the craddle it has a red light then every 1min the light turns out it boots to the Windows screen "tap screen to setup" and after 3-4sec it turns off.
I have a feeling it is dead but I thought I might see if anyone else has had this problem.
Related
I am in the process of calibrating my battery. It was full and finally died after a good while. I put it on the charger and waited a couple minutes and tried to boot it up because I needed to make some calls and it goes thru the boot screens and animation and will dim but then it goes black. I press the menu button and end button to turn on the screen but it doesn't work. It will boot into recovery and the buttons work there. I have no idea whats wrong with the phone. Can anybody help me with this problem? Thanks in advance.
Edit: When I plug it in via usb the screen turns on but there is no touch response when I try to slide the unlock tab or sound tab.
I have no idea what caused it or fixed it. Randomly happened and randomly fixed itself.. everything is working fine now.
My N7 was sitting in front of me on my desk, and it made a noise very similar to the USB disconnect noise in Windows 8, which is something i have never heard any android device make. I picked it up, and the backlight was on, but not the screen. The lock button was not responsive, so i proceed to reset it. Also unresponsive. I held down both vol buttons and power for several seconds, and the "Google" splash screen appeared, but it did not enter recovery. The boot logo appeared, and it sat there looping for about 3 minutes (considerably longer than normal), then the screen shut off and individual pixel started flashing, like static cling in the dark. I hooked it up to my comp, i have no adb access. It's unresponsive during boot and while it's doing the flickering thing. I can repeat this cycle of splash screen, boot logo, then wild flickering each time, but cannot get adb regardless.
I was running Franco kernel with stock rom, no overclocking or anything, flashed shortly after i got. It's been faultless for months. I'm almost certain it's toast so i'm not expecting salvation from XDA, but thought i'd get some input if anyone is curious.
tdrussell said:
My N7 was sitting in front of me on my desk, and it made a noise very similar to the USB disconnect noise in Windows 8, which is something i have never heard any android device make. I picked it up, and the backlight was on, but not the screen. The lock button was not responsive, so i proceed to reset it. Also unresponsive. I held down both vol buttons and power for several seconds, and the "Google" splash screen appeared, but it did not enter recovery. The boot logo appeared, and it sat there looping for about 3 minutes (considerably longer than normal), then the screen shut off and individual pixel started flashing, like static cling in the dark. I hooked it up to my comp, i have no adb access. It's unresponsive during boot and while it's doing the flickering thing. I can repeat this cycle of splash screen, boot logo, then wild flickering each time, but cannot get adb regardless.
I was running Franco kernel with stock rom, no overclocking or anything, flashed shortly after i got. It's been faultless for months. I'm almost certain it's toast so i'm not expecting salvation from XDA, but thought i'd get some input if anyone is curious.
Click to expand...
Click to collapse
ask franco if fsync is enabled default and if is barrier=0 in the kernel
Try holding in the power button for 45-60 seconds. If that doesn't work then Plug in the unit, and let it try to charge for an hour or two. Then try holding in the power button for 45-60 seconds again.
There seems to be a glitch where the unit will die when the battery is low. Some people have report something similar when the unit was ~23% battery life.
After I installed the update 3.1 for ViperONE on my HTC One did not drop starts, all I see is the logo VIPER ONE. I'm waiting for 50 minutes, tried to restart my phone (pressed volume up and power button) but it does not help.
Please excuse my poor English.
i just installed this same rom. Everything goes well with installation. First boot shows the first logo with ull brightness, the brightness lowers and comes the second logo and says preparing sim card, 2-3 secs later goes back to first logo and says there. left it for more than 30 minutes. trien installing like 5 times. same result
helpmeplis said:
i just installed this same rom. Everything goes well with installation. First boot shows the first logo with ull brightness, the brightness lowers and comes the second logo and says preparing sim card, 2-3 secs later goes back to first logo and says there. left it for more than 30 minutes. trien installing like 5 times. same result
Click to expand...
Click to collapse
when it does this hold power till phone shuts off then reboot should start up then
Hi,so i replaced LCD in my I9515, I've been doing this with youtube tutorial. Before 1-2 weeks ago my phone boot normally but i couldnt see anything due to broken LCD. In store, guy took my battery and connected it to a naked motherboard and lcd to see if it's working. After replacment when i try to boot it's stuck on Samsung Galaxy S4 logo and wont boot further. I can go into download mode, computer and odin are seeing connected phone, but i cannot boot into recovery it's just showing blue "booting recovery" and nothing happening. When I charging it, the grey battery pops out, but when i unplug it the battery is still there like it's still connected. Sometimes when i try to turn it off when it's stuck on galaxy s4 logo it's turning off then on by itself like 2 or 3 times. Any ideas how to fix it? It's hardware or software problem? In a minutes i'll try to flash stock soft from sammobile. Phone was never rooted and no custom roms were installed.
EDIT Flashing with ODIN not solved the problem
EDIT Now phone doesnt show battery when connected just one vibrate and screen is blank, and when i try to boot it while connected it's just vibrating and still black screen. When it was connected to pc it was vibrating every 2 seconds. When I try to boot it's by itself trying to boot recovery but it's not booting and blue "recovery booting" just hang on top of screen and nothing happening.
Wrong forum ?
Hi, so I got an A2 which has been submerged in water for a while. I was not turning on at all (just showing the white led light blinking), so I bought a new USB part and battery for it, replaced it, and now it seems to react.
However, it keeps switching between the charging logo for a second, then vibrates and shows the Android One logo (this switch goes on and on forever). I have tried the button combo to go into recovery, but as soon as the Android recovery boot logo appears, it'll still timeout into the charging logo.
Does anyone know what may be going on? Or what component to replace? (the phone was only days old when it accidentally got soaked, so everything is new and it's a shame to just throw it away)