Database Info

[Q] Screen won't stay on for more than an Instant

ok, weird issue.
Yesterday I came back to my TF having left it inmy bag for the day, and it would not turn on at all.
I tried various things and then decided that the battery must be totally dead.
I left it to charge over night, and come the morning was able to watch it booting.
However once It finished boot it goes to black screen. Pressing the power button sometimes gives a flicker of backlight and then goes blank again. sometimes it even gives a glimpse of the screen.
Plugging in the power sometimes gives a longer blink of the booted ROM.
I have tried a cold boot, a full data wipe and I have used NV flash to fully reinstall the ROM (Prime 1.8)
After the full reinstall I go through the Google initial setup process without a problem, as soon as the rom boots I am back to the flicker of screen going off..
Does anyone have any ideas??

Still got the problem, does this sound like hardware to anyone else?

if the screen doesnt work during boot it is hardware problem. flash ur rom again or wipe it

chatch15117 said:
if the screen doesnt work during boot it is hardware problem. flash ur rom again or wipe it
Click to expand...
Click to collapse
Screen works fine during boot
Done both of your suggestions unfortunately, as I stated in my original posting.
I am going to try going back to Stock, and assuming its an app NOT restore any during the rebuild process.

[Q] Stock ROM + Google+ = Rogers logo bootloop

I have the stock 'v10c' ROM on a 'Rogers' LG Optimus 3D.
This morning I was using the Google+ Android client and - without closing the app - pushed the power button to put the phone to sleep and put it in my pocket.
About 15 mins later I pulled the phone out of my pocket and it was dark, but the touch countrols were all lit up. I know that usually isn't good news. The phone was unresponsive.
I pulled the battery and tried to re-boot. It gets to the Rogers screen and then boot-loops, with a flash of the Rogers screen each time it restarts a cycle. Roughly 15 seconds apart.
I did vol+down+Power (guessing based on other phones) and it booted into a recovery (3e) menu that only offered me the chance to wipe all user data. Ok. I moved the cursor down using vol+down and sletected "yes" with Home. The phone then presented a triangle logo and the green android and sat there.
Meanwhile...I Googled. After about 10 mins I pulled the battery again and did the Vol+down+3D button+Power boot to the REAL recovery menu.
I then did a wipe / factory reset from the recovery menu. I have assumed the Home button is the enter button (BTW).
Again the triangle and the green android appear. They are still there 10 mins later.
Not sure what to do now...the phone won't boot and the factory reset won't fix it. But it isn't dead. I can still get to recovery, so in theory this is fixable. I just don't have time for it right now. :-/
I was wondering if maybe the phone had updated OTA in my pocket and I didn't realise it and I may have messed up the process. But I have never seen a phone do an OTA update without first notifying the user and seeking confirmation...so I that probably isn't the case.
Very annoying.
I'm posting this here in case anyone else has the same experience.
Anyone have any advice?
[Update: The Menu button is the enter button...not Home. So I did a real factory reset and the phone now boots to the "Welcome to your new phone" screen. *WHEW!*]

Uhmm... if Menu button is home button that means u have problem with build.prop. I never met with this kind of problem, however I think u just should turn on usb mode in cwm, put a ROM on phone, flash it and see how this will be. Don't forget to backup ur rom.
Sent from my LG-P920 using XDA Premium App

Hi there,
I've got the same problem with my LG P920.
Then I read your thread and now I can tell you how to fix...
The recovery is the right way to fix, but the homebutton is not the menu button.
You have use the Options Button the first from the left side or the 3d-button.
Than you came to factory default and you can restart youre device.
best regreads
Morphix

Anyone know the glitch that is causing this?
Sent from my LG-P925 using xda premium

If've got the boot-loop for the first time and it happend after a reboot comand on the comand app...

I have the same problem and no idea why it happens ..
I had this 2 times in one week! very anoying..

[Q] Touchscreen not responding - stuck TF101 tablet - what can I try?

OK - since the recent ota upgrade to ICS we've been having a few problems with the table touchscreen freezing - unfortunately now it seems to have got stuck almost all the time. Just at the moment, it is not responding at all to touch - just displays the lock screen when powered on, and then times out a little while later to black. I have to push power to get it back on - but the touch screen simply won't respond to unlock it. So far I have tried:
Holding down power until restarts - no effect - reboots still locked.
Using Vol-Down power on and doing factory reset - no effect - reboots into android setup screen touchscreen not working.
Draining power until it won't turn on. Then recharged. This worked! However...
After going through the setup process, resintalling apps etc., I hit the power button to go into standby. I then thought I'd go straight back in, but as soon as I hit the power button again, it wouldn't respond! Left it charging for a couple of hours, and turned on, this time got in - but same again - hitting the power button and coming straight back in, it's not responding again.
So I'm now back with a fully charged tablet that won't respond to touch at all. - perhaps if I leave it a few hours it might respond again - until it goes into standby!? The device is fully stock with WW_epad-9.2.1.11-20120221 (according to the screen at boot up when you hold down vol-d).
Is this likely to be software or hardware related? Do I need to send it for repair/replacement, or is there something else I can try first? Any help much appreciated. (Oh - I don't have external keyboard btw - so without screen it's pretty limited what i can do!)
Cheers,
Colin.

I have already encountered the same problem but with a cutom rom. to find my touch, I had to do a full wipe and new intallation.

I did full wipe using the Power/Vol-D but the touch screen didn't start working again until I let the battery completely drain.
Then I reinstalled everything (screen was working to begin with), however after I'd set everything up and reinstalled all my apps it stopped again.
Yesterday I managed to get an ota update to 9.2.1.17 (it started working for a short time). But then aftger rebooting again, it stopped again.
This morning it is working again, and I have uninstalled all my apps - just the core stuff on there now. For the moment it appears to be working (which is the longest for a while!) - going to see if it stops again while there aren't any extra apps installed...

[Q] Virus or Bricked it ?

Hey Guys, I'd Like to ask a question , very weird going on about my device... Only one time I got that Lovely Icon (exclamation mark) with a phone sign followed by a computer, yes that means that i am in download mode, i fixed it but once i got passed that small error my phone has been acting up.. I've tried CM10 keeps restarting by itself once in a while, I had tried going COMPLETELY going to stuck by using a Youtube video on how to unbrick it... NO luck. This time it freezes up and all applications become unresponsive, Facebook FORCECLOSE and other apps& and restarts, once is in the home screen i hold the power button and i only get one option "POWER OFF" its very weird because I remeber there was "DATA IS SET "ON" ETC, other settings in the phone had been re-enabled for ex. haptic feedback vibration. i had that turned off and it came back on by itself, second setting is the lock screen i cant set up a lock setting because once i press the unlock button and wait about 5 seconds it would go directly to the home screen W/O asking to enter to any patter. I tried gingerbread 2.3.6, with this rom all apps are UNAVAILABLE.. YES they dont open up.. EVEN facebok.. I took out the battery, turned it back on, and once it gets to the "rethink possible" keeps restarting the att motion until it finally restarts the whole phone and it keeps doing this.. I wanted to ask you guys if my phone is bricked or something because is really annoying. Thanks !

A brick would be where you wouldn't be able to boot up. A virus would be wiped out when flashing a new rom. When installing a new rom, did you also format /system? Sometimes that irons out some bugs. Maybe doing a wipe on your dalvik and cache seperatly could help.
Sent from my MB300 using xda app-developers app

Yea, once i last flashed CM10 yeah i did and the problem persits... Right Now im in stock FROYO 2.2 with no luck... I had to switch to my old Mytouch 3G Slide until i fix this issue...

[Q] Brick / Boot loop problem

I honestly need help.
I'm not sure what to categorize my issue under.
I am stuck in a screen with the green android and the spinning thing in the middle, with a progress bar, but the bar just has a moving animation, looks like it is moving to the left, not getting longer or filling up like usual progress bars.
I am unable to get to the boot loader or recovery.
The issue started after I flashed Cyanogen Mod 10.2 Stable.
it booted fine then, but when I went to use it, it would have a never ending cycle of app not responding at the part where it asks to sign in to cyanogenmod account. I got to settings without signing in by quickly sliding the status bar and clicked on factory reset.
From there it proceded to reboot and now I am stuck in the screen described.
I have tried all the button combinations, reset with pin, nothing will get to bootloader or recovery.
ADB does not find the device, also no devices found when try fastboot devices line.
I have also tried putting the firmware zip on a microsd, but nothing new happens either.
any suggestions appreciated.
** edited ** Issue is resolved. Turns out I just needed to wait longer (about 2 hrs) ... I did turn it off using combo of power and Vol -, left it off overnight, turned it on in the morning and left it alone. I finished whatever it was trying to do, and now CyanogenMod 10.2 stable is working great.