Database Info

[Q] TF stuck at Asus boot up screen. Help!

I had my Asus since Wed and everything was good. Last night I decided for the first time completely turn it off for the night. This morning I hit the power button and it will not boot up to the OS. It right stuck at Asus welcome screen. I try several times and its still hangs at the welcome screen. I had no issues with the update from last week (the one where others were bricking their tablet) Last night it had 50% battery life. Any suggestions?

Anyone? I try the recovery mode and it goes into recovery all I get is the little green android robot with triangle....and after five minutes it reboot by itself and then get stuck at the Asus welcome screen

How long in minuted do you let it sit at the Asus screen and did you have a notice about an update?
Sent from my Transformer TF101 using Tapatalk

donatom3 said:
How long in minuted do you let it sit at the Asus screen and did you have a notice about an update?
Sent from my Transformer TF101 using Tapatalk
Click to expand...
Click to collapse
Its been sitting at the welcome screen for the last ten minutes. I am able to turn it off and on..but it does not get past the welcome screen. I did that update (which bricking others tablet) two days ago and everything went fine.....Last night was the first time I completely turned it off..and now this.... I dont know what else to do....I try the recovery mode several time and after five minutes it reboot on its own and then goes back to the welcome screen and sits there...... The only thing that works is the sleep mode for the screen. every 5 minutes screen turn off (sleep mode) Asus support suggest I let the battery drain and then try again.....this completely sucks.

You tried the force power off 10-12secs power button trick yet?

stuntdouble said:
You tried the force power off 10-12secs power button trick yet?
Click to expand...
Click to collapse
I went back and read up on the bricking thread...and instead of trying to go into the recovery mode I did a data wipe and now it working (VOL UP after the prompt) .....I am new to this android thing but just wondering how could this happen? I did install some new softwares yesterday could that have cause this issue? Any way thanks guys for your help

It's pretty rare for an app to make a device need a full reset nowadays, but it can still happen. It's more likely you had some OS bug though to be honest. If your transformer gets into difficulties in the future then try the force power off method as it seems to right quite a few wrongs. Anyways glad you got it working again.

To me it sounds like the update was still actually stored in your memory and ran itself again which is why you saw the android screen with progress bar. Looks like you clearing data got rid of the update file.
Sent from my Transformer TF101 using Tapatalk

donatom3 said:
To me it sounds like the update was still actually stored in your memory and ran itself again which is why you saw the android screen with progress bar. Looks like you clearing data got rid of the update file.
Sent from my Transformer TF101 using Tapatalk
Click to expand...
Click to collapse
I have no idea what happen. Couple of days ago I did drain the battery and it after charging it up it did boot up fine.

This just happened to me......and now my transformer isn't wanting to boot up using volume up+power.
Doh, volume DOWN + power lol. Wiping data, hopefully it fixes it. Hassle though. Gonna have to redownload a bunch of apps now ugh.

Happen again....and it looks like VTL Launcher.1.6.2 is the software that is causing it to not boot up correctly. This is the same app I installed Sat. night and come Sunday after a shutdown it will not boot up. Tried it again today, and its not booting up.....ahhhh
What is this hard boot up you guys talking about? I held onto the power button for 5-6 seconds and I got the Asus EEE pad screen and then get the welcome screen and it just stays there. ahh looks like I have to wipe out the tablet again..not cool at all....... btw after installing VTL Launcher I also set it to default could this be the cause of it not booting up?

Same issue here...
So, I am getting the same problem here...
Wipe works and then it loads the rest of the way, but I cant get it to load without a full wipe.
I do have VTL installed, so that may be the case. I cant imagine that doing it though.
Anyone else have any more information on this?
Thanks!

paultrevino said:
So, I am getting the same problem here...
Wipe works and then it loads the rest of the way, but I cant get it to load without a full wipe.
I do have VTL installed, so that may be the case. I cant imagine that doing it though.
Anyone else have any more information on this?
Thanks!
Click to expand...
Click to collapse
Yeah my advice dont use VTL.... IF VTL is set as default launcher and if you try to reboot it will get stuck at the welcome screen. The issue is VTL. I am using ADW right now and the issue is gone.

dazz87 said:
Yeah my advice dont use VTL.... IF VTL is set as default launcher and if you try to reboot it will get stuck at the welcome screen. The issue is VTL. I am using ADW right now and the issue is gone.
Click to expand...
Click to collapse
Gotcha... VERY good to know. Do you have any idea if the problem persists when VTL isnt the default launcher but is still installed?

paultrevino said:
Gotcha... VERY good to know. Do you have any idea if the problem persists when VTL isnt the default launcher but is still installed?
Click to expand...
Click to collapse
If you dont select VTL as a default launcher then you shouldnt have no issues rebooting your TF even if its installled. Its just annoying cause every time I hit the home button the system ask me which launcher do I want to use. So if you want to use VTL as default then make sure you dont reboot. If you need to reboot then remove VTL as default before rebooting your TF

dazz87 said:
If you dont select VTL as a default launcher then you shouldnt have no issues rebooting your TF even if its installled. Its just annoying cause every time I hit the home button the system ask me which launcher do I want to use. So if you want to use VTL as default then make sure you dont reboot. If you need to reboot then remove VTL as default before rebooting your TF
Click to expand...
Click to collapse
sounds plausable - i had a similar problem on my HTC Desire with early releases of SPB Mobile Shell. Fine until reboot and then just looped. luckily i had a nadroid i could recover to.
My advice is always keep at least one backup on your device

Fixed: stuck booting when VTL is set as the default launcher.
Yikes found this thread, Why would ASUS make the default launcher so tightly coupled???
Edit: heres the easy fix using adb to uninstall vtl launcher
Install java/adb
plug in your transformer to your PC using the propritary dock->usb cable. Your transformer should be at the ASUS loading page (stuck indefinitely)
install the usb/adb driver. On windows 7 this was automatically downloaded and installed from windows update. size=8.5MB
open a "cmd" window, run this command: "adb devices"
This is what I get and it verifies that adb is talking to the transformer.
Code:
C:\Users\meeeeee>adb devices
List of devices attached
37c624540e14597 device
run this command at the cmd prompt to uninstall VTL launcher. Root not needed, usb debugging needs to be turned on.
Code:
adb uninstall com.vtlab.launcher
you should see a "success message"
Look at your transformer it should be at the login screen.
tags: stuck transformer TF101 booting VTL launcher adb fix

dazz87 said:
Happen again....and it looks like VTL Launcher.1.6.2 is the software that is causing it to not boot up correctly. This is the same app I installed Sat. night and come Sunday after a shutdown it will not boot up. Tried it again today, and its not booting up.....ahhhh
What is this hard boot up you guys talking about? I held onto the power button for 5-6 seconds and I got the Asus EEE pad screen and then get the welcome screen and it just stays there. ahh looks like I have to wipe out the tablet again..not cool at all....... btw after installing VTL Launcher I also set it to default could this be the cause of it not booting up?
Click to expand...
Click to collapse
Hmm - maybe we should pay attention to the description of the application....
VTL.Launcher - Tablet Optimized - Scrolling Docks - Scrolling Widgets - And More ***NOT FOR HONEYCOMB YET***
Click to expand...
Click to collapse
you'll have to be in Recovery and remove the launcher apk and then reboot.... or wipe data....

[Q] *S.O.S* Stuck in the market with screen ON !FIXED!

So Im running Prime1.5 with clemsyns OC kern..
I go into the market and started dl'n some apps and all of a sudden the screen freezes and it wont turn off no matter what i do..
I tried connect via adb to perform a reboot command, and it wont connect..
So Im stuck with my screen on, almost full battery and Asus TF is froze..
Do i just play the waitin game and let the battery drain and turn off so that i can reboot it? or what are my options??
Has anyone ever ran in to this??
Please help.. I had LG Gslate and this happened once and there was a reset button next to the sim slot.. NOT the case here unfortunately
BTW: I did search first and only came up with "stuck in boot"

It may sound silly...but have you tried to hold the power button for a good 10-15secs (or a little longer) ?

hyperxguy said:
It may sound silly...but have you tried to hold the power button for a good 10-15secs (or a little longer) ?
Click to expand...
Click to collapse
I did hold it for a bit but not quiet long enough
It work, duh moment..
Thanks again!

How to Disable ICS bugfix/bugreport?

Hi, everyone. I always accidentally press my NS' power + volume up buttons, which activates the bugfix/bugreport email window.
Is there any way to safely disable this feature?
Thanks in advance.

Sorry to ask, but what? You mean you press them when powering up the phone? If not, could you post a screenshot?
Transmitted from somewhere in space... from my Nexus S... and Tapatalk.

flodb113 said:
Sorry to ask, but what? You mean you press them when powering up the phone? If not, could you post a screenshot?
Transmitted from somewhere in space... from my Nexus S... and Tapatalk.
Click to expand...
Click to collapse
Yes, I accidentally press them when powering on or off my NS. Try holding the power and volume up buttons. Your NS will vibrate and bring up your default email app and compose a bugfix/bugreport email for you.

IIIV said:
Yes, I accidentally press them when powering on or off my NS. Try holding the power and volume up buttons. Your NS will vibrate and bring up your default email app and compose a bugfix/bugreport email for you.
Click to expand...
Click to collapse
Exactly what I am searching online for. I always get the sharing options appear out of nowhere and only realise that it is trying to send a bug report.
After some extended searching, I finally knew how it was activated. By pressing Volume up + Volume down + power button, you will feel a vibration after a second or so, that's when the bug reporting initiated.
http://code.google.com/p/ics-crespo...rc?r=a3b8746ae7e80de2f9db08a9e8094f6587b4b675
However, I have no idea how to disable it. It become very annoying especially when waking up the phone from sleep and you find that your device is lagging because of the bug report generation.
Any help?

ghost_301 said:
Exactly what I am searching online for. I always get the sharing options appear out of nowhere and only realise that it is trying to send a bug report.
After some extended searching, I finally knew how it was activated. By pressing Volume up + Volume down + power button, you will feel a vibration after a second or so, that's when the bug reporting initiated.
http://code.google.com/p/ics-crespo...rc?r=a3b8746ae7e80de2f9db08a9e8094f6587b4b675
However, I have no idea how to disable it. It become very annoying especially when waking up the phone from sleep and you find that your device is lagging because of the bug report generation.
Any help?
Click to expand...
Click to collapse
Turn off USB debugging.

The solution that I've found, without turning off USB debugging, is renaming the file "bugmailer.sh" (to something like "bugmailer.sh-backup"), which is found in /system/bin.
P.S. For me, I need USB debugging turned on, because it is required by Titanium Backup, which I often use. If you don't need USB debugging turned on all the time, you could just turn it off, like Uni7 posted, and it'll also solve this issue.

IIIV said:
The solution that I've found, without turning off USB debugging, is renaming the file "bugmailer.sh" (to something like "bugmailer.sh-backup"), which is found in /system/bin.
P.S. For me, I need USB debugging turned on, because it is required by Titanium Backup, which I often use. If you don't need USB debugging turned on all the time, you could just turn it off, like Uni7 posted, and it'll also solve this issue.
Click to expand...
Click to collapse
You shouldn't need USB debugging for TB on any new rom. From official FAQ:
40. Why does Titanium Backup demand that the Android Debugging Bridge (ADB) be enabled? I don't develop on my phone and don't want this.
The only reason is that on some ROMs, earlier versions of Superuser (the app that grants root privileges) didn't work properly if ADB (USB debugging) was disabled. This is why I added the warning at startup.
Nowadays, on most ROMs you can leave USB debugging disabled in your phone settings and also disable that warning in Titanium Backup. The option is: MENU -> Preferences -> "Warn if no USB debug".
Click to expand...
Click to collapse

Uni7 said:
You shouldn't need USB debugging for TB on any new rom. From official FAQ:
Click to expand...
Click to collapse
Thanks for the info, it works! Never know it's the USB Debugging option, guess I never explore deep enough.
Thanks again!

Uni7 said:
Turn off USB debugging.
Click to expand...
Click to collapse
[CM9 nightly] unluckly this doesn't help

IIIV said:
The solution that I've found, without turning off USB debugging, is renaming the file "bugmailer.sh" (to something like "bugmailer.sh-backup"), which is found in /system/bin.
P.S. For me, I need USB debugging turned on, because it is required by Titanium Backup, which I often use. If you don't need USB debugging turned on all the time, you could just turn it off, like Uni7 posted, and it'll also solve this issue.
Click to expand...
Click to collapse
mcalamelli said:
[CM9 nightly] unluckly this doesn't help
Click to expand...
Click to collapse
Sent from my ice cream powered Nexus S

mcalamelli said:
[CM9 nightly] unluckly this doesn't help
Click to expand...
Click to collapse
have you solved this problem ?

ghost_301 said:
Exactly what I am searching online for. I always get the sharing options appear out of nowhere and only realise that it is trying to send a bug report.
After some extended searching, I finally knew how it was activated. By pressing Volume up + Volume down + power button, you will feel a vibration after a second or so, that's when the bug reporting initiated.
http://code.google.com/p/ics-crespo...rc?r=a3b8746ae7e80de2f9db08a9e8094f6587b4b675
However, I have no idea how to disable it. It become very annoying especially when waking up the phone from sleep and you find that your device is lagging because of the bug report generation.
Any help?
Click to expand...
Click to collapse
Same here on my Galaxy Nexus...anyone eager to help us out?

I have the same problem. HELP

This is a manual bug report triggered by pressing both volume keys and the power button at the same time. It will vibrate once when you do it and then it takes a good minute or two for it to compile the report. The phone will then vibrate 3 times quickly when the report is ready, but only if the phone is awake and unlocked. So, for example, if you hit the power button to check the time and happen to press all three buttons or your TPU case (just an example) is holding down your volume buttons, then it will trigger then. You won't actually see the results until the next time you unlock the device. They are addressed to your default email address unless your ROM developer adds an email to them. Obviously being stock this would not be the case.
If you want to get rid of this feature, go to /system/bin and rename bugmailer.sh to bugmailer.sh.bak or delete it. Then reboot and no more bugmailer.

chandradithya said:
This is a manual bug report triggered by pressing both volume keys and the power button at the same time. It will vibrate once when you do it and then it takes a good minute or two for it to compile the report. The phone will then vibrate 3 times quickly when the report is ready, but only if the phone is awake and unlocked. So, for example, if you hit the power button to check the time and happen to press all three buttons or your TPU case (just an example) is holding down your volume buttons, then it will trigger then. You won't actually see the results until the next time you unlock the device. They are addressed to your default email address unless your ROM developer adds an email to them. Obviously being stock this would not be the case.
If you want to get rid of this feature, go to /system/bin and rename bugmailer.sh to bugmailer.sh.bak or delete it. Then reboot and no more bugmailer.
Click to expand...
Click to collapse
While I appreciate the fact that you are helping out, please do not take my responses from another forum and paste them here verbatim as your own.
Source: http://rootzwiki.com/index.php?/topic/18671-Disable-bug-report-error-messaging?#entry488123
I should add that in addition to the way mentioned above that will completely disable it, disabling USB debugging should also disable it in 4.0.4.
Sent from my brain using human to phone transport technology.

Dock Wakeup Issues

Hi All,
Been having this issue for a while now.
Basically with my tablet docked and the option which disabled keyboard wake up in the settings UNTICKED I cannot wake my screen once the screen has been locked for longer than 30seconds.
No matter what I do i.e use the touchpad or press keys the only way to wake the screen is via the power button.
It's extremely frustrating has anyone had the same issue previously?

KinetiClutch said:
Hi All,
Been having this issue for a while now.
Basically with my tablet docked and the option which disabled keyboard wake up in the settings UNTICKED I cannot wake my screen once the screen has been locked for longer than 30seconds.
No matter what I do i.e use the touchpad or press keys the only way to wake the screen is via the power button.
It's extremely frustrating has anyone had the same issue previously?
Click to expand...
Click to collapse
Are you using custom kernel?

buhohitr said:
Are you using custom kernel?
Click to expand...
Click to collapse
Yeah CROMI. Tried both thats and hunds kernels both with same result.

KinetiClutch said:
Yeah CROMI. Tried both thats and hunds kernels both with same result.
Click to expand...
Click to collapse
And you UNCHECKED the MobileDock Battery saving mode located in settings--> Asus customized settings?

buhohitr said:
And you UNCHECKED the MobileDock Battery saving mode located in settings--> Asus customized settings?
Click to expand...
Click to collapse
100% I made sure. I've been through all other options and can't figure out why this is happening. Is been the same across numerous full wipes. I could make a video to show the issue if it helps?

KinetiClutch said:
100% I made sure. I've been through all other options and can't figure out why this is happening. Is been the same across numerous full wipes. I could make a video to show the issue if it helps?
Click to expand...
Click to collapse
try the key with the lock see if that works.(top right handside of the keyboard).

buhohitr said:
try the key with the lock see if that works.(top right handside of the keyboard).
Click to expand...
Click to collapse
Tried it only works to unlock when the screen is on. Then it works. The issue is turning the screen on via the keyboard.

I don't think ths has worked since JB came in. The behaviour you are describing is default I believe. If the screen self locks then you don't get much time to use the touchpad to unlock it.
On mine when I open the lid it unlocks the screen. Does yours do this?

KinetiClutch said:
Tried it only works to unlock when the screen is on. Then it works. The issue is turning the screen on via the keyboard.
Click to expand...
Click to collapse
OK, last try, disabled the screen lock (no lock screen) and see if it wakes.

sbdags said:
I don't think ths has worked since JB came in. The behaviour you are describing is default I believe. If the screen self locks then you don't get much time to use the touchpad to unlock it.
On mine when I open the lid it unlocks the screen. Does yours do this?
Click to expand...
Click to collapse
Yeah when I open the lid this does wake the screen.
I guess this must be it, weird is it even worth the bother of emailing ASUS?
It's weid that when THAT tried it for me he had no issues with it, unless he wasn't leaving it for long enough. Noticed that tonite i've had no issues with using the trackpad to wake the screen however, spotify is running so maybe that interferes with the locking process?
Thanks for the help Buh, but don't think it's worth disabling the lock screen completely just to get this working!

KinetiClutch said:
It's weid that when THAT tried it for me he had no issues with it, unless he wasn't leaving it for long enough.
Click to expand...
Click to collapse
I tried it this morning (after 6 hours sleep time), and it still worked - I hit the lock key, and the tablet was awake instantly - how unfair, I was still sleepy.

_that said:
I tried it this morning (after 6 hours sleep time), and it still worked - I hit the lock key, and the tablet was awake instantly - how unfair, I was still sleepy.
Click to expand...
Click to collapse
I hate you
I guess this is my tablet punishing me for using such poor stock ROM's on it for so long

I also have this problem when I use Cromi. I found that I can "fix" it by clicking and unclicking "MobileDock Battery saving mode" whenever I reboot the tablet-doing so allows me to wake the screen using the keyboard. Also, see if you have the same problem with Cromi-X. I recently upgraded to Cromi-X and the keyboarding waking screen problem went away.

I had the same issue, and fixed it with a clean wipe and install...

[Q] Phone won't wake sometimes - 5.02

Hey guys,
I flashed my OnePlus One to 5.02 (TimOs) and it has been working alright for now (ignoring the somewhat reduced internet speed) but now I've noticed that every 15-20 unlocks, it just won't unlock. I can hold down the power button and eventually it will reboot or wait for around 30-60s and eventually the screen will turn on.
I have tap to wake enabled but neither the power button nor the double tap wakes the phone.
Anyone got any suggestions as to why this might be happening?
Thanks

Cheesus182 said:
Hey guys,
I flashed my OnePlus One to 5.02 (TimOs) and it has been working alright for now (ignoring the somewhat reduced internet speed) but now I've noticed that every 15-20 unlocks, it just won't unlock. I can hold down the power button and eventually it will reboot or wait for around 30-60s and eventually the screen will turn on.
I have tap to wake enabled but neither the power button nor the double tap wakes the phone.
Anyone got any suggestions as to why this might be happening?
Thanks
Click to expand...
Click to collapse
This happens in some specific ROMs,flash another and it should be gone.

I've tried 2 ROMs, it always happens, only on lollipop though.

Cheesus182 said:
I've tried 2 ROMs, it always happens, only on lollipop though.
Click to expand...
Click to collapse
Did you try from official CMmod webpage?
How did you flashed your ROMs,dirty install or clean?

I havent tried official one yet no, might give that a try later.
Clean install, wiped everything.
I heard that it could be something to do with the proximity sensor?

Cheesus182 said:
I havent tried official one yet no, might give that a try later.
Clean install, wiped everything.
I heard that it could be something to do with the proximity sensor?
Click to expand...
Click to collapse
It`s a bul**** i had the same issue and tried another rom that fixed it. But now i`m on official nightly and it`s fine. Give it a go