Hi,
I've got an envizen tablet which I accidentally turned the brightness off on completely. This is a serious problem, seeing as this is essentially a write-only device (see the wiki articles since this website is under the impression that I'll spam some links). If this somehow has a fix at all then it will be extremely hard to debug since a) I install many applications, b) I use a custom launcher, c) I have an applock enabled and settings is hard to get to now to enable USB debugging, and d) One of the first things I did to my tablet was disable the Android Device Manager. This is caused by a little program called Dimly, and even though I can successfully log into my tablet, the USB connection isn't set to allow ADB to debug.
This is the application-layer equivalent of a bricked device.
Please help me.
Resolved
This issue has been resolved by a force-shutdown and a viable timing window in which the services start up.
Related
I need a method of completely resetting any and all aspects of Microsoft active sync on the device side without resorting to a hard reset.
i do not care how long this takes or how many registry entries i need to change but i really really really need to get this sync issue fixed and every where else i turn has the same tired 5 step sorry your screwed speech and i have tried it many times.
please someone give me more advanced debugging that can actually help me fix this.
ok now that my pathetic rant is out of the way the issue is one of the classic device is plugged in. all drivers have been reinstalled multiple times and while the phone says it is connected windows mobile device manager says that there are no connected devices and will not display a dialogue to add a new connection. Bluetooth syncing is similarly impaired
steps taken to date.
deleted all current pairings
uninstalled all drivers and windows mobile device center allowed windows update to reinitialize everything.
tried plugging the phone in using active sync with both advanced network functionality and with this option disabled
so that is everything any of the trouble shooting sites have mentioned so far. at this point i believe the issue is at the phone level and has something to do with the network portion of the usb connection process as the network driver for the phone shows that the computer is sending data but receiving no packets from the phone.
all fire walls on my system have already been disabled.
Hey guys,
First off: I searched. Nothing on this specific issue.
My issue: I try to enable USB debugging on my OPO, it works for a few seconds (maybe 4s), then it gets automatically disabled. The notification shows up for about 4s and then disappears, when I go back to the developer menu its disabled.
My OPO: 64GB, 12.0-YNG1TAS2I3, Unlocked, Rooted.
If anyone needs any more info I'll gladly provide it.
Quick video of the issue:
https://www.youtube.com/watch?v=8Je4M0Q9cOM
manichon said:
Hey guys,
First off: I searched. Nothing on this specific issue.
My issue: I try to enable USB debugging on my OPO, it works for a few seconds (maybe 4s), then it gets automatically disabled. The notification shows up for about 4s and then disappears, when I go back to the developer menu its disabled.
My OPO: 64GB, 12.0-YNG1TAS2I3, Unlocked, Rooted.
If anyone needs any more info I'll gladly provide it.
Click to expand...
Click to collapse
Did you manage to come up with a solution? I'm having the same problem.
I had this problem on my Moto G (1st gen) and now on my Xperia Z3 Compact and the exact same thing was happening, which makes me think it could be an app or something affecting it (I just restored nearly everything from Titanium Backup).
Is your ADB working in recovery mode? Mine is so therefore it isn't a computer issue
Ok, turns out I accidentally fixed it somehow so I'm posting here incase anyone else encounters the same issues.
I was having issues with Tasker, TitaniumBackup and ADB and I think it was all inter-related. I re-installed Tasker because tasks weren't automatically triggering. After a couple of reboots due to things being odd, everything started working again. I also ran some TB backups before checking if ADB was working but I'm not sure if that affected it.
TLDR; uninstall Tasker (and maybe disable some device admins?)
Yah, it was an app. Cerberus.
Right then. First things first, I apologize if I don't use the proper lingo associated with everything; I'm as super nooby as can be.
So, here's my problem: My rooted, Samsung Galaxy S3 has had it's screen shattered and its digitizer broken. The screen is completely black and the touchscreen does not respond. It didn't have a password (it was just swipe to open), which I suppose makes things easier, though. The phone itself still turns on, and I receive notifications and all that, but I am completely unable to do anything about. I understand that I am able to view and operate an Android phone through my computer, so I was hoping that'd work. Well, as the title of this topic hinted at, I didn't USB debugging enabled on my phone, which pretty much every program I found requires. So, I searched around, and learned that ADB can activate USB debugging through a usb cable and some tech magic. Unfortunately, I am not a tech magician and the articles I found were hieroglyphics. I spent some time reading, researching, reading researching, but it still doesn't make sense to me. I have ADB installed, but I don't know how to use it at all. I can launch "adb.exe" in administer mode but nothing occurs. I'm wondering if anyone would be able (or want to) explain to me, preferably step-by-step on how to enable USB debugging be it through ADB or some other, miraculous technique.
For anyone interested, these were the articles I looked at:
http://forum.xda-developers.com/showthread.php?t=1725858&page=2
http://android.stackexchange.com/qu...ndroid-if-forgotten-pattern-for-screen-unlock
http://android.stackexchange.com/questions/120394/can-i-enable-usb-debugging-using-adb
http://android.stackexchange.com/qu...bug-mode-was-disabled-how-can-i-re-enable-adb
http://stackoverflow.com/questions/13326806/enable-usb-debugging-through-clockworkmod-with-adb
http://developer.android.com/tools/help/adb.html
http://forum.xda-developers.com/showthread.php?t=2786395
Hey dude, what you are talking that can enable USB Debugging from ADB is possible only on custom ROMs. But on stock ROM this is not possible.
Shield Tablet Bug Fix "missing home button, recent tabs, notification centre" Nougat
Hello Everybody. I have a Shield Tablet running Nougat. I have been experiencing the bug described in the Title a few times, and I finally found a way to solve such bug, at least in my specific scenario. It might not work for everybody but, as I have seen a lot of Users experiencing such bug and being forced to deal with it through a factory reset, I thought posting an easy guide might be helfpful to some. It is not rocket science, but for me it does the trick well. Should you feel there is an easier way to solve the same issue, please, do not hesitate to add it to this post.
I already posted this guide on the official Shield Tablet forum, but I cannot add the link because I am a new User (c'mon dudes, I am not spamming.. just trying to help ). Therefore, I am just gonna copy paste the guide. I apologise if the formatting is not ideal.
Hello Everybody, I know that there is an Android bug that has been creating issues for many years, also on shield tablets. When the bug starts, the home button disappears, it is impossible to open the "recent app" tab, the notification centre cannot be pulled down, and there are many other side effects. Since I started having this issue, I did quite a lot of research. Apparently, all I could find were information regarding how to solve the bug on Lollipop and Marshmallow, but nothing regarding Nougat. The way this bug is usually fixed is by starting the Setup Wizard on the device. Unfortunately though, I was not able to open it due to permission restrictions. Some guides mentioned installing Nova from the appstore, and setting up an action Widget in order to start the Setup Wizard. This did not work for me as well. What I was able to do, instead, was creating and setting up a new User profile, which then fixed the bug on my main User.
I am sure people more experienced and talented than me probably would have been able to find a neater way to make this happen. However, as I am quite a noob with these kind of things, I thought that writing a basic guide might be helpful for others as well.
Before going on, you should know that in my case, the only way to fix the problem is to have "debug settings" enabled on your device BEFORE the bug starts. When I first got the bug, I had not unlocked "debug settings" and I could not do it afterward, as tapping 7 times on the build number did nothing. You also need to have Android Debug Bridge (adb) installed on your computer and configured with the tablet.
Also, the process I will describing now creates a new User and switches to it by using terminal commands and Adb. I am aware that there would be an easier way to achieve the same result by going on "settings>Users" on the tablet. However, if you experience the same bug I was having, you will find out that clicking on the "Users" tab does nothing.
Here is a step by step guide of what I did:
1
Normally boot your tablet and connect it to the computer via usb cable
2
Run a command prompt windows on the computer and run Adb. Even if, due to the bug, you won’t be able to transfer files to the tablet via USB, adb should be able to interact with the shield anyway. To double check this, type the command: adb devices . You should be able to see your device listed.
3
It is now time to create a new User through the command prompt. You can do that by typing the command:
adb shell pm create-user User_Name
Once the new user has been created, the prompt will show you the respective User_ID. You will need to type such number in order to switch to that user, by typing the command:
adb shell am switch-user User_ID
eg. adb shell pm create-user Charlie
Success: created user id 11
adb shell am switch-user 11
4
Your shield should have now switched to the new user just created. At this stage, finish the new user configuration stage on the tablet. Skip all the google services related options, as you do not need them. When the configuration process is finished, the home button, the notification centre, the recent app, etc. should be back. Now that the bug is fixed, it should be possible to go back to your main User profile by simply switching User from the settings menu on the shield: settings>Users. At this stage, if everything went well, you should be logged with your main User, and the bug should have been fixed. It is now possible to go again on settings>Users and delete the new User created on step 3.
This is it. It works well for me and, even if I do not exclude that the bug will present itself again at some point, this is a 5 minutes solution to fix it. I apologise for any english mistake, as English is not by main language. Also, somebody might know of an easier way to solve the issue on Nougat, although I was not able to find any online, and that is why I wrote this short guide. I hope it will be able to help some of you!
Have a nice day!
Alberto
Hello, few days ago my phone's screen stopped working. So I cannot access my phone since its locked behind pattern lock. I tried with ADB but I keep getting ADB Device Unauthorized and I don't know how to fix that.
As far as I know I believe USB Debugging is enabled. I tried a lot of ways with useless one click apps, mirror screen apps but nothing work as I need to unlock phone to give permission to the computer to communicate with the phone, but I cannot do that since the device screen doesn't work and I cannot see anything. I have an OTG cable and tried to unlock with mouse but its easier said than done.
Can someone give me any tutorials.
It requires a couple of your phones internal software switches to be set in order to access your phone via the USB interface. If you have not already set these switches before the screen got broken you may be out of luck.