Ive been using my touchpad with cm9 alpha 1 for a few days now and its been perfect. Went to use it today and I see the screen flash to moboot then everything disappears. The background light is on but no images. It did load into webos and the only reason I knew that was I heard the webos tone. I could increase and lower the volume but nothing would appear on the screen. I can hold power and home to force the reboot and get into usb mode. I ran webos doctor which ran fine to 100%. Screen still doesnt display anything. All I get is a flash of hp logo when it first turns on then nothing. If I hold all the buttons down I do get a blue screen that tells me to release the buttons.
Any Ideas would be appreciated.
Related
Hello All
I did search the forum and still not answer for the stranger reboot loop.
I got a phone call, and answered it. The reception was crappy and hear no voice. I then looked at the phone to see if call had dropped and it was frozed on the incoming call screen. I then pulled the battery and pressed the power button to turn on the phone and It would not power on. After multiple battery pulls and many many power button presses, still nothing. It was like it was out of battery. It was stitting on the home charger before i left the house. Prior to this the phone worked fine. Over the past week or two I had to do a battery pull may be 3 times.
I got to my car and plugged it into the charger and the orange charge led came on, on the front of the device. I then pressed the power button and it vibrate once as normal and then went to the multi-colored nexus "X." he screen went black and then vibrated once again and and was back at the mulit-colored "X." Then the loop starts.
In between the restarts I try to get it to boot into the bootloader by using the "vol down and power" and the "trackball and power button" and the white screen for the boot loader flashed for a milisecond the goes to black. As long as I hold the "vol down" button the while bootloeader or recovery screen flashes every 4-5 sec for a milisecond. As soon as I let go of one of those button, it automatically goes to the full reboot loop.
THis all happens when it is plugged into a power source. As soon as i unplug it, it goes back to the power button not responding. Again it acts as if it has no battery power. But it is in the 90%.
So i am unable to do any other step as in reflashing, and or doing a recovery.
ANY IDEAS any one.
I was running Cyanogen RC3. the latest rom with amon RA 1 7 1, korean radio 5.0.8
It was running perfectly up till today. when it went into its loop.
ANY HELP WOULD BE AWESOME
THanks in advance
DD
Plug it in to the USB, adb reboot recovery, reflash rom. Or even wipe and reflash if needed.
Sounds like it could be hardware the way you have to hold the keys down and you said it wasn't responding to the power button press.
ok thanks, ill give it a try.
here is my only issue. I am not using my original computer Mac. I just sent it out to apple for repair. So i am using my companies computer. I need to set up the AndroidSDK to be able to talk to the nexus. Since the phone will not turn on i can not load the drivers. and ive tried every way and it has not installed and i cant check because it wont stay on. it just goes to the loop. and it wont turn on if its not plugged to a power source.
Any ideas or suggestion.
SOrry I am an noob, so could you please be specific in your instructions.
I as of right now have insalled the Android SDK and i am unable to see the serial number (working on an old dell, running XP sp3) because it wont turn on.
It cant manually install the drivers because I cant turn the phone on to specify the drivers.
and
I using USBDeview, the phone also has to be on to erase all HTC previously installed drivers. i think. but there were none in the usb log...i think becuase they didnt install...agains because it would not power on...:-(
any ideas...please
DD
Also
Sorry excuse me if its a sort of a duhhh question...
even if i am able to load the device bridge, if the phone will not boot can i still flash another rom, or do a recovery. The phone is not getting past the Multi-colored "X" ???
DD
It should still read the commands when it's trying to boot. You don't need to turn the phone on at all to be able to install the ADB drivers, they are independent of each other.
As strange as it started, is a strange as it went.
This morning open the phone to pull the sd and the sim to put it in a throw down phone. I replaced the battery and cover and just hit the power button. The phone does a full boot and it appears to be working properly. the sd card and sim are fine. I the odd thing is i did this multiple times yesterday and last night. I pulled both sim and sd, replaced the battery and tried to boot with the same issues as named above with nothing different.
I left the phone on charge last night and it was charging for close to 8 hours and it was still showing the orange charging light.
So after it booted this morning, and i checked everything. It showed the same amount of charge as yesterday, right before it froze, which was 75%. So that is another strange occurance.
I plan on reflashing the rom and seeing how things go.
I thank you for your assistance and time.
appericate you helping out a clueless noob.
DD
Dear all, I just update my touchpad form CM7 A3.5 to CM9 A0.5.
After updating, comes the switch on problem, the details as blow:
In CM7 A3.5 system, I can shut down and switch on the touchpad with power button as normal, it also means the power button works.
When I update to CM9 A0.5(the updating is successful), I found USB connect problem, so I want to restart touchpad to solve it. As we know, in CM9 system, when press the power button, only shut down selection. So I shut down touchpad. When I press the power button to restart touchpad again, there is no response. the touchpad did nothing. even press main button and power button together. I do not know what happened.
Update: the most probably caused this is I use plustoolbox to change the boot animations.
Is this only a special case? Or could be my failure.
Update information:
After keep my touchpad after 20 hours, I try to switch on it again, the power button works, but just show low battery(by last shut down, it should be 50% battery left), so I charger it. After a while, touchpad started and gone into CM9 system and works.But when I shut down again, the touchpad can not switch on again. I do not know this time I should wait how long time then it can work again.
Last Update: the most probably caused this is I use plustoolbox to change the boot animations.
lunerlee said:
Dear all, I just update my touchpad form CM7 A3.5 to CM9 A0.5.
After updating, comes the switch on problem, the details as blow:
In CM7 A3.5 system, I can shut down and switch on the touchpad with power button as normal, it also means the power button works.
When I update to CM9 A0.5(the updating is successful), I found USB connect problem, so I want to restart touchpad to solve it. As we know, in CM9 system, when press the power button, only shut down selection. So I shut down touchpad. When I press the power button to restart touchpad again, there is no response. the touchpad did nothing. even press main button and power button together. I do not know what happened.
Is this only a special case? Or could be my failure.
Update information:
After keep my touchpad after 20 hours, I try to switch on it again, the power button works, but just show low battery(by last shut down, it should be 50% battery left), so I charger it. After a while, touchpad started and gone into CM9 system and works.But when I shut down again, the touchpad can not switch on again. I do not know this time I should wait how long time then it can work again.
Click to expand...
Click to collapse
You can force a restart by holding the power and center buttons together for 30 seconds.
Thank you for replying.
I have tried but failed.
now the second round is
In shut down status, after 24 hours, the battery can from 100% reduce to low battery.
In this status, I can charger and start touchpad.
lunerlee said:
Thank you for replying.
I have tried but failed.
now the second round is
In shut down status, after 24 hours, the battery can from 100% reduce to low battery.
In this status, I can charger and start touchpad.
Click to expand...
Click to collapse
I'm not currently using the ICS build, but I would then suggest doing a complete reinstall of CM9 through acme installer. Make sure to uninstall the current build that you have on their.
lunerlee said:
Dear all, I just update my touchpad form CM7 A3.5 to CM9 A0.5.
After updating, comes the switch on problem, the details as blow:
In CM7 A3.5 system, I can shut down and switch on the touchpad with power button as normal, it also means the power button works.
When I update to CM9 A0.5(the updating is successful), I found USB connect problem, so I want to restart touchpad to solve it. As we know, in CM9 system, when press the power button, only shut down selection. So I shut down touchpad. When I press the power button to restart touchpad again, there is no response. the touchpad did nothing. even press main button and power button together. I do not know what happened.
Is this only a special case? Or could be my failure.
Update information:
After keep my touchpad after 20 hours, I try to switch on it again, the power button works, but just show low battery(by last shut down, it should be 50% battery left), so I charger it. After a while, touchpad started and gone into CM9 system and works.But when I shut down again, the touchpad can not switch on again. I do not know this time I should wait how long time then it can work again.
Click to expand...
Click to collapse
Can you see Moboot menu when it turns on ? If yes it is working good in Dual booting if not please reinstall moboot,cwm and cm9 using ACME installer 2
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.
I just acquired as P1000 model. I am having 2 problems. 1 I think I fixed, but the other is beyond me.
Problem 1 - When I plug the charger in and I use the USB cord from my 2.1A wall outlet I get a batter logo with a spinning circle and then it flashes dark and starts over again. I think I've tracked this down to the tablet not liking my charger as it charges fine off my laptop.
Problem 2 - After letting it charge for a while, I went to power it up and it gives me the Galaxy Tab logo, but then it goes to a boot animation that is some triangles flipping over each other. It sits on this for a while, then it goes to a black screen and starts the same triangle boot animation all over again.
I've tried searching repeatedly to no avail and I can't seem to find out what I need to do in order to fix this. I welcome any advice, I don't know if it's modded or stock, or what kernel is even on it. When I push the volume down and power buttons I get a note about downloading with a picture of an Android with what looks like a shovel pointed backward.
1stly try factory reset through recovery (by pressing & holding volume up then press power button) to see if it solved your problem.
2ndly if the first method didn't you need to flash the phone with odin using stockrom in download mode (by pressing & holding volume down then press power button).
you can get your stockrom at sammobile or google it.
and also Next time when reporting an issue consider putting Screen shot for better understanding.
Tab s2 8.
Was using practically fully charged tablet one minute, went to use again and screen black.
Back and task switch buttons still light up when press power or home. Plus volume up/down makes the louder/quieter beeps.
Power and volume down gives me the quickest flash of the samsung and android boot logos and then screen black again. Makes the email received notifications you get when restarting the tablet.
Is basically on but just no screen. But screen still functional enough to briefly show boot logos.
Any thoughts?
Update. After about 30 mins of faffing, magically returns to life. Any thoughts on common issues that might have caused? Indicator of something about to go wrong for good?
Put down gently today and the right side of the screen displaying flickering dark/black stripes. Left side of screen perfectly fine. Touch still works over the whole display. Any ideas? Internal cable come loose? Or something more terminal? How easy to check/fix?
Xdaforumposter said:
Tab s2 8.
Was using practically fully charged tablet one minute, went to use again and screen black.
Back and task switch buttons still light up when press power or home. Plus volume up/down makes the louder/quieter beeps.
Power and volume down gives me the quickest flash of the samsung and android boot logos and then screen black again. Makes the email received notifications you get when restarting the tablet.
Is basically on but just no screen. But screen still functional enough to briefly show boot logos.
Any thoughts?
Update. After about 30 mins of faffing, magically returns to life. Any thoughts on common issues that might have caused? Indicator of something about to go wrong for good?
Click to expand...
Click to collapse