I managed to get into developer mode on my new NGP, there's no more "build number" as I've seen in several blog posts with the latest update you click on the Nook icon on the About page it takes you to Developer mode. I've been able to install a few apps, but here's what I'd like to do.
I'd like to plug in a USB keyboard and use it to SSH into another machine through my WiFi hotspot to do some HTML/JS/CSS text editing while I'm outdoors (at the pool, the park, etc) as my other laptops/tablets aren't visible at all outdoors with glare. This would be a nice portable solution if I could get it to work, even editing locally on the device through some editor and sending via SFTP would be just fine.
However, I can get my USB OTG cable and USB keyboard to work on my Samsung J3 phone just fine, but not on my NGP it does nothing when plugged in, keyboard caps lock doesn't activate. Is there a way to get it to work, and does it require rooting the NGP? I haven't rooted the device yet.
JohnnyFriendly said:
However, I can get my USB OTG cable and USB keyboard to work on my Samsung J3 phone just fine, but not on my NGP it does nothing when plugged in, keyboard caps lock doesn't activate. Is there a way to get it to work, and does it require rooting the NGP? I haven't rooted the device yet.
Click to expand...
Click to collapse
As a workaround I put a VNC client on it so I can access my other devices and do the typing from there, that way I can use my RPI3 as the system with a keyboard on battery power and do some Python (Django)/NodeJS/ReactJS from the NGP using it as a monitor outdoors, but if I issue the following commands via adb to rotate into landscape mode I lose input on the NGP and have to reboot:
adb shell settings put system accelerometer_rotation 0
adb shell settings put system user_rotation 1
Any ideas?
I believe I looked at this once.
At least one of the problems is that the ID pin on the micro USB connector is not connected through to the processor.
B&N has never shown any interest in putting Bluetooth in a Nook.
We'll have to see if the latest "Nook Glowlight 3" will have either OTG or BT.
Related
Hey everyone,
Firstly my apologies if this is in the wrong section but it seemed most relavent although I've been pulling my hair out all day/night so I not at my sharpest.
My issue is this:
I have a Google Nexus 7 (pre-2013) that has a cracked screen. I had it rooted originally but I was using TWRP multi-rom loader for Android and Ubuntu. After the screen cracked I couldnt get past the boot loader (even with the OTG cable and mouse). So I restored it to stock awhile back but now I want to re-root it for various reasons, namely to be able to use certain applications that will make controlling it (without OTG cable) far easier and more practical.
I continually get stuck at the RSA Key Check for USB Debugging. (as I am unable to post links I've attached a picture I came accross on the net of the RSA key check I refer to)
This only prompts when I have the USB connected to my PC, but I cant control the Nexus as I have to take the OTG out to connect it to the computer.
I have tried vast array of VNC/Remote applications but still cannot seem to tick that freaking box (or at least just say 'OK' once in order to root the device).
Tablet Remote has gotten me the closest although it doesnt allow me to click "OK" when I pair it with my Samsung S4.
VMLite was promising however its the same deal : I'm required to push 'Start Server' with the USB connection to the PC (of which I cant do, otherwise I would just hit OK on the RSA key check)
Numerous other VNC Server apps or ones of similar nature require root access (of which I am trying to get!)
- I dont have any bluetooth devices in the house (except my old SixAxis controller from PS3 but SixAxis requires root privileges).
- Im not confident of whipping up a home made 'OTG Y Cable' so I can have both USB input to the computer and OTG mouse input
Short of buying either of these (a bluetooth mouse for example or a suitable OTG cable), is there anything I can do? Its so frustrating to not be able to proceed because of 1 stupid box.
Is there a way to disable this RSA check or is there an avenue I havnt explored yet that could solve this for me?
Many thanks in advance!!
TL;DR Smashed phone, need to find a ROM with ADB enabled to use it
Long story short, I smashed my phone last Friday. The LCD screen works and the phone appears to be fully functional except for the digitiser. I had ADB disabled as I frequently plug my phone into computers at university and elsewhere and I don't want to run the risk of ADB commands being run maliciously. Since the Nexus 4 can't do USB OTG without a splitter cable (and, I believe, some configuration) I can't just plug in a mouse to control the phone. Annoyingly, this happened while moving house and I don't have internet at home until tomorrow; I was planning on using USB or WiFi tethering to get my PC online.
I found this page with a suggestion on what I might be able to do. Alternatively, my other plan is to connect an Ouya controller by bluetooth and use the touch pad on that to control the phone. Either way, the plan hinges on using ADB to control the phone to begin with to either configure an app or enable bluetooth.
I've noticed a lot of ROMs (since 4.3.1?) have ADB disabled until the user enables it. Also, whether or not ADB is enabled to begin with isn't something a developer is likely to list in their first post. Does anyone know any ROMs that have ADB enabled on first boot? Any other suggestions on what to do would also be great.
I've been reading various threads and tech posts for hours and feel like I'm going in circles and getting absolutely nowhere, so I'm really hopeful someone can help me out.
I broke the screen and digitizer on my AT&T SGH-I337 Galaxy S4 with stock Android 4.2.2 and ROM, though it is rooted. I was trying to control it via the computer with 'Ultimate Touchscreen Control for Android' or Screencast, but they require ADB which I'm pretty sure is not enabled. I did enable USB debugging before the screen broke, though I can't say with 100% certainty that I didn't later disable it, so I'm not entirely sure what the status of that is. I've been reading about sideloading a kernel with ADB enabled through recovery, or using CWM with Odin to enable it, but I have been absolutely unable to figure out how to do it with a broken screen. It doesn't help that it's been 3.5 years since I really messed with stuff like CWM and custom ROMs, and I've never used Odin, and my knowledge on this stuff is not great. Any help would be greatly appreciated.
I think you're pretty much sol. You say you're on 4.2.2, do you know what bootloader you're on. Mdb, mdl or mf3. If you're on mf3 you won't be able to flash a kennel. Do you have a custom recovery, and if so, which one?
When booted into recovery and adb installed on your pc in a Windows command window type
adb devices
If you're devices serial number shows up you have adb debugging enabled. If it just shows waiting for device, you don't.
Your best bet is to get the screen/digitizer replaced.
Sent from my Nexus 5 using XDA Free mobile app
Not sure what bootloader, but I got the device only a month or two after the S4 came out and immediately rooted it with Motochopper and it hasn't had any updates since, so it has to be an earlier one, probably the first.
After several attempts, 'adb devices' gave me:
"List of devices attached
da916528 unauthorized"
The first several times it would just say "List of devices attached" with nothing following.
'adb shell' resulted in "error: device unauthorized. Please check the confirmation dialog on your device."
Shortly after it does list the phone, the phone shows up in Windows, so I'm thinking it's not going into recovery. My timing must be off because I can't see the screen to know when to release the buttons.
vertigo_2_20 said:
Not sure what bootloader, but I got the device only a month or two after the S4 came out and immediately rooted it with Motochopper and it hasn't had any updates since, so it has to be an earlier one, probably the first.
After several attempts, 'adb devices' gave me:
"List of devices attached
da916528 unauthorized"
The first several times it would just say "List of devices attached" with nothing following.
'adb shell' resulted in "error: device unauthorized. Please check the confirmation dialog on your device."
Shortly after it does list the phone, the phone shows up in Windows, so I'm thinking it's not going into recovery. My timing must be off because I can't see the screen to know when to release the buttons.
Click to expand...
Click to collapse
You're close but unfortunately no cigar. You have usb debugging enabled but it's waiting for you to authorize the device by clicking accept on the touch screen. Which you obviously can't do. If you used motochopper you are on mdb or mdl bootloader which means you could flash a kernel but you'd have to do it in a custom recovery and use the touch screen. I don't have an i337 so I'm not going to be much more help. Sorry.
Sent from my Nexus 9 using XDA Free mobile app
Kinda figured it was something like that. Thanks anyways, at least I know exactly where I stand now. I'm going to try using an MHL and OTG adapter to see if I can click it that way. In the meantime, hopefully somebody with the same phone as me will come along and be able to provide further guidance.
So I was finally able to gain remote access with some crazy wiring and a lot of patience. I'm putting this here so others in my situation might have an easier time at doing it.
First I installed TeamViewer QuickSupport (TVQS) via the Play Store online, then connected a PS/2 mouse to the phone through a OTC cable and a USB to PS/2 adapter (only USB mouse I have is wireless, but good to know you can use such an adapter for this). I blindly swiped the screen to unlock the phone, then connected it to my TV with an MHL adapter and the 5 to 11 pin Samsung-specific adapter. I long-pressed the menu button to activate voice search and said "launch TeamViewer QuickSupport," then when the app opened it showed me the ID to connect to the phone which I entered into my desktop TeamViewer application. I then had to switch back to the mouse to do some more blind clicking to authorize the connection, then again to authorize the remote control, which took several frustrating minutes of switching back and forth between the mouse and the TV. One mistake I made was not installing the remote addon at first, so after I first authorized the connection, I didn't have that option, so I had to install it again through the Play Store online then close and relaunch TeamViewer on the phone and reauthorize the connection before I could start a remote session. Once I was FINALLY in I had full control and was able to get the Ultimate Touchscreen (UTCA) program authorized (which in retrospect would have required the same thing only it would have been significantly easier, since I would have only had to do one blind click) and Mobizen (which I'm currently using to control it as it's the best and fastest of the three, and oddly it's faster through the web interface than the desktop program).
In the end, what would have made this significantly easier (in fact, very easy), would have been to use a combination OTG/MHL adapter that would allow using the mouse and TV at the same time, or possibly a micro-USB OTG Y-cable so I could plug one connector into the phone and one into a power supply, then plugged the MHL Samsung adapter into that so it could get power that way, allowing me to plug the mouse in to it instead of a USB cable for power. Not sure if that would actually work, but it seems like it would. Hopefully somebody finds this info helpful. From now on, I'll be installing and authorizing TVQS, Mobizen, and UTCA on my phones when I get them.
I have the same problem. I cannot access ADB in anyway, even in in Clockworkmod recovery. USB Debugging is off. I am on the original firmware that came with the device, (Pre Knox) and the device is rooted.
My lock screen is just the simple lock, with no password required, but I have an app installed that switches the USB mode to Mass Storage for the external SD only so I cannot see internal storage.
MHL does work, but the touchscreen is not working, so all I can see is the lock screen.
When in recovery, ADB Devices shows the device as unauthorized. If i go to option # 3, (which apparently is Factory Reset) the status changes to "Sideload." But I still cannot do anything.
If no one has any suggestions. I think i'm going to have to purchase one of the Samsung Smart Docks.
I can't post links or pictures until I get 10 posts, but this works;
goo.gl/PR7TCK
Other than getting the dock, the only other way to do it that I know of is how I described above, switching back and forth between video and mouse, which sucks because you're flying blind. It requires a lot of patience.
Hi,
My brothers phone screen is basically unusable.
When I connect the phone to the PC it recognises it in Windows but the phone contains no folders. At first I assumed it was because his screen was locked so I connected a OTG and keyboard and using commands managed to get his phone "unlocked" to the home screen.
However this didnt fix the issue.
Reading around it seems I may need USB Debugging enabled (if he hasn't already) but due to not being able to use the screen how would I do that?
Do I need a MICRO USB to HDMI & USB adapter to use a mouse and TV output?
Or is there a way I can fix this through windows using ADB?
At this point we are willing to try anything as all we are looking for is some family photos off of it then binning the phone and I don't want to put £100-200 into the screen replacement just to attempt this data recovery.
All help is greatly appreciated,
Cheers
ADB is the door to any Android device. As long as ADB has not been activated on the device - and the related RSA keys got created - you have no chance to pull out data from device, IMO.
Ok,
Well see the fact when I connect it to windows it shows the phone but not the folders inside, and I can only assume there will be a popup on the screen mentioning to ALLOW/DECLINE transfer etc..
If I use the OTG adapter I can plug my keyboard in and use the sequence SPACE, SPACE, BKSPACE, BKSPACE, then my PIN and ENTER and it unlocks to the home screen.
But because I would need the phone connected by both PC and KEYBOARD at the same time is it possible to get a splitter on the OTG adapter and this would hopefully let me press RIGHT and ENTER to accept the message?
If not then can the phone be connected via HDMI to see if any message is infact popping up??
Rowan88 said:
Hi,
My brothers phone screen is basically unusable.
When I connect the phone to the PC it recognises it in Windows but the phone contains no folders. At first I assumed it was because his screen was locked so I connected a OTG and keyboard and using commands managed to get his phone "unlocked" to the home screen.
However this didnt fix the issue.
Reading around it seems I may need USB Debugging enabled (if he hasn't already) but due to not being able to use the screen how would I do that?
Do I need a MICRO USB to HDMI & USB adapter to use a mouse and TV output?
Or is there a way I can fix this through windows using ADB?
At this point we are willing to try anything as all we are looking for is some family photos off of it then binning the phone and I don't want to put £100-200 into the screen replacement just to attempt this data recovery.
All help is greatly appreciated,
Cheers
Click to expand...
Click to collapse
OK, new to this. To get usb debugging on, click system. About phone, Software information, build number. Click that several times. (AT least 10). You will see a message that you are in developer mode. Go back to home screen. Click settings icon. Scroll to bottom you should now see { } Developers optiions. Click that. Find the section for ADB, enable ADB. Once ADB is up and running you should be able to pull the files. The screen for an android is the desktop, mouse, and keyboard. (PC analogy). You need something to see your icons, something to click, and a keyboard. If OTG acts as a mouse, and you can see the basic display, and have an external keyboard. I think you can do this. I am not sure what OTG is .
wdtr2002 said:
OK, new to this. To get usb debugging on, click system. About phone, Software information, build number. Click that several times. (AT least 10). You will see a message that you are in developer mode. Go back to home screen. Click settings icon. Scroll to bottom you should now see { } Developers optiions. Click that. Find the section for ADB, enable ADB. Once ADB is up and running you should be able to pull the files. The screen for an android is the desktop, mouse, and keyboard. (PC analogy). You need something to see your icons, something to click, and a keyboard. If OTG acts as a mouse, and you can see the basic display, and have an external keyboard. I think you can do this. I am not sure what OTG is .
Click to expand...
Click to collapse
1. I cant follow that process as the screen is completely destroyed (no display/no touch), thats why I have been blindly using a keyboard to try and find the setting
2. OTG is ON THE GO , its a small adapter that lets you connect USB devices to your phone.
Sorry about that. I think you are stuck. without some visual clues I think you can not put the phone in developer mode. Did you try just a plugin (via usb) into windows and seeing if there is a pictures folder?
It find the phone in Windows, but wont display the folders.
The OTG splitter I purchased to be able to connect it to the PC and KEYBOARD at same time didnt work as it doesnt supply power (should have checked reviews).
Any other solutions? Or is this a new screen for £200 just to get data?
I purchased another OTG splitter that has a OTG/CHARGE switch so this should let me connect it to the PC and KEYBOARD.
Can anyone give me shortcut keys or step by step on how many times I need to press certain buttons to get down to the USB DEBUGGING section please?
Hello.
I've got my mother's Samsung A20. And i need to recover data, but the screen doesn't work.
When power button is pressed, display flashes the lock screen (wallpaper, current time and so on). And then it turns black (backlight stays on for 30 seconds, and then turns off). Pressing the button doesn't guarantee flashing the display, sometimes it goes black immediately. Touch screen gives no input as far as i know (can't hear anything when trying to type pin). Problem still occurs during and after reboots.
I managed to connect a mouse and keyboard with USB OTG, and i was able to unlock. But the phone has no MHL support, so i can't get any image through USB. I'd try pressing the power button repeatedly to get some image and inch my way through the interface, but the lockscreen interferes.
The USB port is set to Charging Only mode, so i can't copy files to my computer. USB Debugging is disabled, bootloader is locked.
Does anybody have a clue, how to get image? Some way to get data? Maybe some keyboard shortcuts, so i can disable lockscreen and make my way easier? And maybe disable 20 alarms in the morning?
damiandbcz said:
I'd try pressing the power button repeatedly to get some image and inch my way through the interface, but the lockscreen interferes.
Click to expand...
Click to collapse
I like to be helpful so I'll try to give you some suggestions but I hope others pitch in who know far more than I do.
I never use the USB cable anymore to operate my phone from my PC (but my screen isn't broken so your situation will be much harder).
I connect to my phone from Windows over Wi-Fi without USB all the time, and I can unlock my screen from the PC, and I can mount my entire Android device as a drive letter on Windows over Wi-Fi, etc., so "maybe" (just maybe though), you can consider using either a WebDav server on Android to access your files and/or adb to bring up and manipulate activities on Android....
damiandbcz said:
The USB port is set to Charging Only mode, so i can't copy files to my computer. USB Debugging is disabled, bootloader is locked.
Click to expand...
Click to collapse
However, I don't know if adb will work for you if you can't turn on USB debugging in the first place... but as of Android 12, adb now works completely over Wi-Fi (see screenshots below) without needing the USB cable to establish the initial connection like it used to be prior to Android 12.
damiandbcz said:
Does anybody have a clue, how to get image? Some way to get data? Maybe some keyboard shortcuts, so i can disable lockscreen and make my way easier? And maybe disable 20 alarms in the morning?
Click to expand...
Click to collapse
If the screen problem is "just" hardware and not software, and if you can turn on Wireless Debugging, you might be able to display your phone over scrcpy or vysor (both of which use adb over Wi-Fi) as shown in the screenshots below on my phone - which never needs the USB cable connection.
Hope this helps, but you seem to need folks who know more than I do as adb/vysor/scrcpy all work for me because I can set up USB Debugging & Wireless Debugging as shown below.
Note that you might have an FTP server or a WebDav Server on your Android phone, and if you do, you might be able to at least transfer important files since they each can mount your entire Android phone as a drive letter on Windows over Wi-Fi (without needing the USB cable).
GalaxyA325G said:
I like to be helpful so I'll try to give you some suggestions but I hope others pitch in who know far more than I do.
I never use the USB cable anymore to operate my phone from my PC (but my screen isn't broken so your situation will be much harder).
I connect to my phone from Windows over Wi-Fi without USB all the time, and I can unlock my screen from the PC, and I can mount my entire Android device as a drive letter on Windows over Wi-Fi, etc., so "maybe" (just maybe though), you can consider using either a WebDav server on Android to access your files and/or adb to bring up and manipulate activities on Android....
However, I don't know if adb will work for you if you can't turn on USB debugging in the first place... but as of Android 12, adb now works completely over Wi-Fi (see screenshots below) without needing the USB cable to establish the initial connection like it used to be prior to Android 12.
If the screen problem is "just" hardware and not software, and if you can turn on Wireless Debugging, you might be able to display your phone over scrcpy or vysor (both of which use adb over Wi-Fi) as shown in the screenshots below on my phone - which never needs the USB cable connection.
Hope this helps, but you seem to need folks who know more than I do as adb/vysor/scrcpy all work for me because I can set up USB Debugging & Wireless Debugging as shown below.
Note that you might have an FTP server or a WebDav Server on your Android phone, and if you do, you might be able to at least transfer important files since they each can mount your entire Android phone as a drive letter on Windows over Wi-Fi (without needing the USB cable).
Click to expand...
Click to collapse
A20 can have only Android 9, 10 or 11, but thanks for ideas anyway.
I didn't even know adb can work over WiFi, I'll look into it. Hopefully this version can do it too.
Now trying blindly to turn on the screen reader…
damiandbcz said:
A20 can have only Android 9, 10 or 11, but thanks for ideas anyway.
I didn't even know adb can work over WiFi, I'll look into it. Hopefully this version can do it too.
Click to expand...
Click to collapse
Ooops. My bad. I apologize. You'll need the USB cable in Android 11 for a moment to establish the connection first. Then you can switch over to Wi-Fi after that (or you can stay on USB).
damiandbcz said:
Now trying blindly to turn on the screen reader…
Click to expand...
Click to collapse
I feel for you. I really do. It hurts me when people can't access their phone remotely to get their data back. I am searching all over the XDA site for a solution for you, where I just moments ago opened this thread to help (I'm still searching for you though).
What is the best XDA solution to control Android on the PC & recover data over Wi-Fi when the user suddenly has an unresponsive broken screen?