Related
Hello all!
Here's the situation: I dropped my phone yesterday (Samsung Galaxy Nexus - i515) and the screen is destroyed. I can still see the top left corner (maybe 1/4 of the screen), but the digitizer is also hosed and I have a pattern lock. I need to get the data off the phone. When I connect it to my computer, it shows up as an external drive, but there is no file structure. From what I've read... I apparently have to unlock my phone before I can see the files, which as I said before is not possible right now.
Bootloader is locked, not rooted and the best part... USB Debugging is disabled. I've read through tons of information, but most threads either fade away when they get almost to a solution, or they are never fully answered.
I got the Unified Android Toolkit (GNEX V12.1.1.) by SKIPSOFT (which is amazing btw), but since good ole' USB Debugging isn't enabled, I can't use adb commands. I've read you can install a custom recovery and use adb at that point, but my bootloader is locked and I don't want to wipe data to unlock it.
I can get into fastboot, the driver shows up in device manager, serial shows up under 'fastboot devices', etc. but it looks like the only thing I can really do at that point requires a data wipe. I hit recovery (which is stock), the screen goes blank for a few minutes and then boots as normal. I'm guessing I can't use adb with the stock recovery??
I believe my final option here is to use a USB otg cable and use a USB mouse (wired only here? can I use a USB dongle? can I even unlock a pattern lock with a mouse?) to navigate until I can get USB debugging enabled. Since I can see a bit of the screen, I don't think it should be too hard. Even if it does prove too difficult trying to do it blind, there appears to be plenty of small apps that give you the capability to view what's on your phone via your PC. I was initially trying to find something that I could control phone from PC (screencast appears to be the best I've found so far), but without USB Debugging enabled or root, it's a no go.
I would like to hear from some of the smart folks out there about my options. I used to mess around with custom ROMs and all that good stuff, but it's been a few years so I am a little rusty.
TL;DR
Phone: Samsung Galaxy Nexus (i515) - broken screen and digitizer
Bootloader - Locked
Root - No
USB Debugging - Disabled
Phone has pattern lock
What is the best option to get my data backed up/copied?
Thanks in advance for any advice you can share!
buddy008 said:
Hello all!
Here's the situation: I dropped my phone yesterday (Samsung Galaxy Nexus - i515) and the screen is destroyed. I can still see the top left corner (maybe 1/4 of the screen), but the digitizer is also hosed and I have a pattern lock. I need to get the data off the phone. When I connect it to my computer, it shows up as an external drive, but there is no file structure. From what I've read... I apparently have to unlock my phone before I can see the files, which as I said before is not possible right now.
Bootloader is locked, not rooted and the best part... USB Debugging is disabled. I've read through tons of information, but most threads either fade away when they get almost to a solution, or they are never fully answered.
I got the Unified Android Toolkit (GNEX V12.1.1.) by SKIPSOFT (which is amazing btw), but since good ole' USB Debugging isn't enabled, I can't use adb commands. I've read you can install a custom recovery and use adb at that point, but my bootloader is locked and I don't want to wipe data to unlock it.
I can get into fastboot, the driver shows up in device manager, serial shows up under 'fastboot devices', etc. but it looks like the only thing I can really do at that point requires a data wipe. I hit recovery (which is stock), the screen goes blank for a few minutes and then boots as normal. I'm guessing I can't use adb with the stock recovery??
I believe my final option here is to use a USB otg cable and use a USB mouse (wired only here? can I use a USB dongle? can I even unlock a pattern lock with a mouse?) to navigate until I can get USB debugging enabled. Since I can see a bit of the screen, I don't think it should be too hard. Even if it does prove too difficult trying to do it blind, there appears to be plenty of small apps that give you the capability to view what's on your phone via your PC. I was initially trying to find something that I could control phone from PC (screencast appears to be the best I've found so far), but without USB Debugging enabled or root, it's a no go.
I would like to hear from some of the smart folks out there about my options. I used to mess around with custom ROMs and all that good stuff, but it's been a few years so I am a little rusty.
TL;DR
Phone: Samsung Galaxy Nexus (i515) - broken screen and digitizer
Bootloader - Locked
Root - No
USB Debugging - Disabled
Phone has pattern lock
What is the best option to get my data backed up/copied?
Thanks in advance for any advice you can share!
Click to expand...
Click to collapse
Unfortunately without ADB I do not know of any way to retrieve your data, or even clear the pattern lock. I think the easiest route would be to try a corded usb mouse and an otg adapter. You could try a cordless mouse with dongle, as long as it is not Bluetooth as that would most likely require a pairing code, but a standard 2.4GHz wireless mouse may work.
Hakugin said:
Unfortunately without ADB I do not know of any way to retrieve your data, or even clear the pattern lock. I think the easiest route would be to try a corded usb mouse and an otg adapter. You could try a cordless mouse with dongle, as long as it is not Bluetooth as that would most likely require a pairing code, but a standard 2.4GHz wireless mouse may work.
Click to expand...
Click to collapse
Thanks Hakugin.
I wanted to give an update. The USB OTG thing definitely works on the phone, but without being able to see the screen, unlocking the pattern would be extremely difficult. I tried for a little while, but there was just no way of knowing if I was even close.
I ended up getting a new phone via insurance. I took both phones apart and plugged the screen on the new phone into the old phone's motherboard. I was able to get into the phone, disable the pattern lock, enable USB debugging, and everything else I needed to do.
I know it's not the greatest and most available solution, but it definitely allowed me to get where I needed to be. I used MyPhoneExplorer (I think that's what it's called) to backup call logs, texts, etc and then restored to the new phone (once I had them both back together of course).
The USB Debugging is the biggest hurdle to overcome. If someone can find a good answer to solving that problem, we'd be ok. Of course, that would be a huge security issue...
Has anyone successfully got bluetooth debugging to work? My girlfriend bought the G Watch and I bought the 360 today from BestBuy. I was looking into the Minuum keyboard for our watches and so I downloaded the wear version of the app, set up debugging on her watch, pushed and activated the keyboard on her phone, installed Wear Messenger, and voila, it works flawlessly. Granted, I followed the adb instructions listed on the XDA forum post on how to install it. Also, when I was following the instructions to install it on her watch, her phone popped up the "allow adb device" message and I pressed trust. This did not show up when I was doing anything on mine.
However, when I tried to do this with my 360, I had no luck whatsoever. I could not get adb to recognize the watch for the life of me. The G Watch showed up right away under Device Manager, but I couldn't find my 360 anywhere.
I enabled the USB/ADB debugging under the watches, then enabled Bluetooth debugging, then USB debugging on my phone.
It's weird cause when I plugged her watch in, Windows searched and found the drivers right away, but when I plugged mine in, nothing happened (probably because the G Watch has the pogo pins and the 360 has inductive charging).
Basically, I'm just wondering if anyone has successfully found a way to get the 360 connected via adb and actually have it be recognized and showing up as connected when typing in "adb devices".
Follow the instruction found here https://developer.android.com/training/wearables/apps/bt-debugging.html.
I used these same instructions just fine.
wingman_214 said:
Follow the instruction found here https://developer.android.com/training/wearables/apps/bt-debugging.html.
I used these same instructions just fine.
Click to expand...
Click to collapse
Trust me, I did. And I couldn't get the host to connect for the life of me. It worked fine on her G Watch, but not my 360.
I'm having this same issue.
ldemon360 said:
I'm having this same issue.
Click to expand...
Click to collapse
I finally got it last night. For one, my dumb ass never plugged in my phone like I should have so the watch could communicate with the phone. Second, if you use "localhost:4444", you have to put "adb -s localhost:4444" then whatever you want to do.
For me, I installed GLTron to my 360. What I did, was after everything was connected (host and target), I typed in "adb -s localhost:4444 install gltron.apk".
Hope this helps.
Hello all, I've been working on a couple custom apps for my Moto 360, and I'm loving it! After some digging around in the forums, I had a hard time finding DECENT threads that pertained to Bluetooth debugging for your spanky Moto wearable, so here is a quick how-to!
First thing, debugging by Bluetooth is EXTREMELY simple. This does not require you to rip apart your favorite USB cable or perform some electrical engineering Jesus magic to acquire a unique USB connection for ADB. YES, wireless debugging IS possible, and is ONLY ADB capable, NOT FASTBOOT capable!
This means: no, I'm sorry fellow wearabees, you can not root/unlock/or flash partitions through ADB or Bluetooth. It's just not possible, and quite possibly would never be possible due to safe flashing procedures. The chances of bricking a device over a wireless connection is exponentially higher than a cabled connection. This is mostly because of interference, range issues, all together nuclear fallout, or your cat is evil and likes to turn your Bluetooth connections off when you sleep at night (let's pray to Buddha this isn't the case...).
So, let's begin by adjusting a few settings on your 360 and your favorite handheld (that would be your cell phone, dummy):
** Go to your 360 settings and swipe all the way down to the bottom of your semi-circular screen to the About section. Poke your cute little watch face to open About.
**Scroll down in your About section to Build Number and tap that guy 100 times, as fast as possible! (You only need to tap it 7 times, but at least it makes developing fun). This should add a new option in your settings named Developer Options.
**Enter your developer options and enable ADB Debugging, at which point the option below this will become available.
**Select the Debug over Bluetooth option to enable what this whole tutorial is about.
**Now, do the same for your handheld. Tap that Build Number, yeah boy! (Sexual pun intended)
Great! You're one step closer to being Super Sayan! (Not really, I have no affiliation with Dragonball Z)
Ok, now we need to open your terminal/command prompt window and change directory to your ADB executable location. From this location we will need to run ADB:
adb forward tcp:4444 localabstract:/adb-hub
Click to expand...
Click to collapse
then:
adb connect localhost:4444
Click to expand...
Click to collapse
The first command forwards the ADB connection of the phone to the remote connection of the 360 by Bluetooth. The second command simply gets the connection initiated with the remote address.
Now, for safe keeping I will provide two options for giving ADB commands to your 360. The first option should be your preferred option for compatibility reasons:
adb -s localhost:4444 <add you command here>
Click to expand...
Click to collapse
This code directs the command to your specific device. Otherwise, for quick code entry, you may use this:
adb -e <add your command here>
Click to expand...
Click to collapse
This second code is a generic way of connecting to whatever debugging option is available, which doesn't always mean your 360. If you're a developer running debug apps, try not to use this command.
And that's about the basics! Super simple, and all ADB commands are available for your wearable. Don't forget, rebooting into the bootloader through ADB will require a USB connection, at which point also some Jesus magic, and let's hope you're willing to be a god for a day.
Have fun!
**
**
I've tried this and I always get an error "Cannot connect to localhost:4444 no connection could be made because the target machine actively refused it (10061)"
Any solutions? I've tried other ports as well.
I've tried multiple cables, multiple computers, multiple USB ports with no luck. With my original XL, it pops up file explorer and I have to swipe down from phone to select transfer files and can access them. Works with all the same cables, ports and computers I tried with the XL2.
I've also tried to use the included USB-C to USB-C to transfer between XL and XL2. I get the notification on my XL that it's connected to my XL2 and can access the XL2 files, but I can't access my XL files from my XL2. Doesn't even show it's connected. Tried all the pull down options on both phones with no luck.
What am I doing wrong? This should be the easiest thing to do and had been on every phone, but not this one. Please help!
Delete
Did you set the connection type to data transfer?
InfiniteReality said:
I've tried multiple cables, multiple computers, multiple USB ports with no luck. With my original XL, it pops up file explorer and I have to swipe down from phone to select transfer files and can access them. Works with all the same cables, ports and computers I tried with the XL2.
I've also tried to use the included USB-C to USB-C to transfer between XL and XL2. I get the notification on my XL that it's connected to my XL2 and can access the XL2 files, but I can't access my XL files from my XL2. Doesn't even show it's connected. Tried all the pull down options on both phones with no luck.
What am I doing wrong? This should be the easiest thing to do and had been on every phone, but not this one. Please help!
Click to expand...
Click to collapse
I had the same issue and with a little searching I figured it out.. Make sure the phone is set to "Transfer Files" in the notification window drop down and download the Google USB drivers zip and install the driver after unzip. Right click the driver file and select install.
Since this is a new account XDA won't let me link yet so Google search for : Get Google USB Drivers
I'm having a similar issue, and we're not alone. I'll copy what I posted on reddit.
Asus ROG Maximus Hero IX motherboard. Tried with multiple cables. Wifes OG Pixel detects it is plugged in right away, my 2XL has to be screen off and set down for a couple of minutes, then the phone recognizes it is plugged in and starts charging and is available for data transfer.
Seven minutes and twenty seconds before it started charging, and another twenty seconds before the computer recognized it as being attached and ready for data transfer. I'm going to do it a few more times to see if there is a pattern.
Edit: Second time was seven minutes for both, third was three fifty one for both, eleven thirty three on the fourth.
I'm not having this problem at all. Once file transfer is enabled on the Pixel I get a popup in Windows asking how to handle the connection to the Pixel 2 XL.
I is a different story with my Nexus 6P -- I can do adb commands but the Windows does not attempt to access the storage on the device.
-- update on Nexus 6P: if I toggle the setting to PTP mode the Nexus shows up in Windows Explorer. Then when I toggle back to MTP I can see the storage.
Using Windows seems to be the common problem when connecting Android Phones to a PC.
stevemw said:
I'm not having this problem at all. Once file transfer is enabled on the Pixel I get a popup in Windows asking how to handle the connection to the Pixel 2 XL.
I is a different story with my Nexus 6P -- I can do adb commands but the Windows does not attempt to access the storage on the device.
-- update on Nexus 6P: if I toggle the setting to PTP mode the Nexus shows up in Windows Explorer. Then when I toggle back to MTP I can see the storage.
Click to expand...
Click to collapse
dratsablive said:
Using Windows seems to be the common problem when connecting Android Phones to a PC.
Click to expand...
Click to collapse
I don't get any connection option when I connect my XL2. It's like it's not even connected. My XL works perfectly fine with same cords and computers which throws me for a loop.
I'll give the shot about changing to other options and back to file transfer and see what happens.
I may need to wipe the phone and start over or maybe it's see sort of bug. Just kinda sucks, just need to make sure I can access the phone and one of the main reasons I got the 128gb version
InfiniteReality said:
I don't get any connection option when I connect my XL2. It's like it's not even connected. My XL works perfectly fine with same cords and computers which throws me for a loop.
I'll give the shot about changing to other options and back to file transfer and see what happens.
I may need to wipe the phone and start over or maybe it's see sort of bug. Just kinda sucks, just need to make sure I can access the phone and one of the main reasons I got the 128gb version
Click to expand...
Click to collapse
I have encountered similar issues when using Windows, but my laptop dual boots between Windows/Fedora Linux. I only boot to Windows when I have to. Linux has no issues communicating to Android Phones. Maybe find a Linux Bootable DVD and give it a spin
When you look in the Windows device manager do you see an entry for LeMobile Android Device? This caused a problem for me in the past. See this post for a possible solution: https://www.reddit.com/r/Nexus6P/comments/5nc64z/adb_drivers_showing_up_as_lemobile_android_device/
A shortcut to the steps in the article is to simply expand the LeMobile Android Device node, right-mouse click on the Android Composite ADB Interface, click Change settings at the bottom of the General tab, go to the Driver tab, click Update Driver; Select Browse my computer for driver software; browse to the directory where Android Studio (or adb tools downloaded from https://developers.google.com/android/ota) files are located; make sure Include subfolders is check) and replace the LeMobile Android Device driver with the Google driver.
(If you have to do this, more than likely you will have to do it each time you reboot.)
I don't know if this will have any effect but on the pc, plug to the usb ports on the back that are direct to the motherboard instead of usb headers on the top/front of pc.
I have this issue with a TomTom satnav and a Mio miview dash cam. Unless they are plugged in on back pc / with Windows 10 doesn't recognize
Sent from my XT1572 using Tapatalk
Thanks everyone for the suggestions!
dratsablive said:
I have encountered similar issues when using Windows, but my laptop dual boots between Windows/Fedora Linux. I only boot to Windows when I have to. Linux has no issues communicating to Android Phones. Maybe find a Linux Bootable DVD and give it a spin
Click to expand...
Click to collapse
That sounds easy enough, but it's dumb (to me anyways) I should even have to do this to get the computer to recognize my phone when it'll recognize my original XL and of course wife's S7. My phone gets plugged to the computer almost every day to copy files off of, at worst every other day.
stevemw said:
When you look in the Windows device manager do you see an entry for LeMobile Android Device? This caused a problem for me in the past. See this post for a possible solution: https://www.reddit.com/r/Nexus6P/comments/5nc64z/adb_drivers_showing_up_as_lemobile_android_device/
A shortcut to the steps in the article is to simply expand the LeMobile Android Device node, right-mouse click on the Android Composite ADB Interface, click Change settings at the bottom of the General tab, go to the Driver tab, click Update Driver; Select Browse my computer for driver software; browse to the directory where Android Studio (or adb tools downloaded from https://developers.google.com/android/ota) files are located; make sure Include subfolders is check) and replace the LeMobile Android Device driver with the Google driver.
(If you have to do this, more than likely you will have to do it each time you reboot.)
Click to expand...
Click to collapse
I went to the device manager on 2 computers and surprisingly nothing showed up. It's like I'm not even plugging it in, while as soon as I plug in my original XL it pops right up. When I attempt to plug it in, it doesn't even attempt to install any drivers like it sometimes use to. I'm going to install the ADB tools when I get home today and see if that helps any to recognize it.
Just tried it on my work computer which does have ADB on it with no luck or anything in device manager
I literally went through all my USB-C cables I could find yesterday, probably 12-15 at least, and I DID manage to find one that worked..... a 6" cable, lol. I can't figure out why this one works and others don't, very more odd is it's the same brand as other longer cables that don't work. Not sure what to make of it, other than voltage loss with the longer ones....just enough to make it not work.
I do have a 2nd XL2 that should be due in this week, was suppose to ship on 22nd. I was going to return it, but now I'll have to take it out of the box and at least test if it works with the computer. I'll report back.
Open to any other suggestions if anyone has any. Thanks again for the replies!
InfiniteReality said:
That sounds easy enough, but it's dumb (to me anyways) I should even have to do this to get the computer to recognize my phone when it'll recognize my original XL and of course wife's S7. My phone gets plugged to the computer almost every day to copy files off of, at worst every other day.
I went to the device manager on 2 computers and surprisingly nothing showed up. It's like I'm not even plugging it in, while as soon as I plug in my original XL it pops right up. When I attempt to plug it in, it doesn't even attempt to install any drivers like it sometimes use to. I'm going to install the ADB tools when I get home today and see if that helps any to recognize it.
Just tried it on my work computer which does have ADB on it with no luck or anything in device manager
I literally went through all my USB-C cables I could find yesterday, probably 12-15 at least, and I DID manage to find one that worked..... a 6" cable, lol. I can't figure out why this one works and others don't, very more odd is it's the same brand as other longer cables that don't work. Not sure what to make of it, other than voltage loss with the longer ones....just enough to make it not work.
I do have a 2nd XL2 that should be due in this week, was suppose to ship on 22nd. I was going to return it, but now I'll have to take it out of the box and at least test if it works with the computer. I'll report back.
Open to any other suggestions if anyone has any. Thanks again for the replies!
Click to expand...
Click to collapse
Do you see anything in device manager under Android devices or portable devices under USB when the 2XL is connected to the PC?
stevemw said:
Do you see anything in device manager under Android devices or portable devices under USB when the 2XL is connected to the PC?
Click to expand...
Click to collapse
Nothing at all, it's like it's not even connected. Just kind of dumbfounded on why when my XL never has had an issue. Attached a screenshot. The one with the triangle doesn't have anything to do with the phone though, it's always been like that and never bothered to mess with it.
The 2nd XL2 shipped yesterday and due in Thursday, so will be curious on if it has an issue. Hopefully it works as intended and I can just set it up and send this one back. Fingers are crossed for sure.
Are you updated to the latest ADB drivers? Right down to, you might have to remove and reinstall. I'm pretty sure I read that it's required.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
If the Pixel 2 is plugged in your screenshot indicates that it is present on the USB bus. It's like the drivers aren't completely loaded.
I haven't seen it mentioned if you have turned on USB debugging in your phone's Developer options. I'm pretty sure that is required for the computer to see it.
JimSmith94 said:
I haven't seen it mentioned if you have turned on USB debugging in your phone's Developer options. I'm pretty sure that is required for the computer to see it.
Click to expand...
Click to collapse
Yea on my regular pixel I have to enable debugging for mine too work. Sometimes lol
stevemw said:
Do you see anything in device manager under Android devices or portable devices under USB when the 2XL is connected to the PC?
Click to expand...
Click to collapse
JimSmith94 said:
I haven't seen it mentioned if you have turned on USB debugging in your phone's Developer options. I'm pretty sure that is required for the computer to see it.
Click to expand...
Click to collapse
I had it enabled for a while, but no such luck. I'll give it another shot, haven't had it on while at work. Also will uninstall and reinstall ADB as well.
When this has happened to me a few times, reinstalling the Windows MTP drivers has worked. Someone else posted these instructions that worked for me.
1. Go to C:\Windows\INF
2. Find the file "wpdmtp.inf"
3. Right click the file and click 'Install'
4. Once that is done, simply plug your phone and it should work.
So friend gave me a FireTV Stick, brand new (Fire OS 5.2.6.3 (606754020), Fire TV Home Version 6.0.0.6-127).
Little desire to deal with Amazon, need to enable USB Debugging & ADB. Gotten as far as Fire App on Phone to bypass Registration to get to Settings-Device-Options, held Center/Down to Enable X-Ray, Developer Options Hidden Menu etc, but can not find any way to Access USB Debugging or ADB to enable them. When you enable Developer Options, only thing it does is give option clear Recorded Metrics whatever. Enabled it, rebooted, disabled it rebooted, re-enabled etc etc, only option I get is to clear recorded metrics.
Tried several diff ways, nothing can recognize it ADB as I can't enable it, tried USB to PC, it recognizes FireTV Stick, can see whats on the Drive or SD Card, but again, can't send files to it without USB Debugging. Rooted every Android Toy I own, not new to this, but has me stumped.
How do you enable USB Debugging or ADB to a FireTV Stick with latest OS without ever Registering it? As far as Normal stuff, it hooks to Network fine (behind Firewall & VPN), but won't Update, why if you go with the Fire App on phone, you can "pair" and get as far as Option to Access Hidden Developer Options etc, but no USB Debugging or ADB Enable Option is there.
Never messed with one, was more a sort of Gag Gift for a favor he owed me, so said why not, lets see what all the fuss over these things is, I wanna tinker with it.
You can always de-register the device from your Amazon dashboard after setting it up for the first time.
I remember reading in another post, someone describing the exact same situation.
Using the app to skip registration and discovering there was no option to enable adb debugging.
Sounds like they may have fixed that.
I noticed in 5.2.6.3 the same security feature Amazon has implemented to detour people from buying and selling blacklisted devices. I have spent more time than I would like to admit trying to find a loophole, but without the ability to enable abd and unknown sources it seems impossible. I hate to say this but Amazon has it locked down and if anyone could figure it out they would have to someone on xda but no one I know has jad a clue. I don't condone theft one bit, but love a challenge and this one has me stumped.
Well, part of the fun, lol. Voice in my head keeps saying the Fire App, has to be a way, but not seeing it as yet. Did read where someone built a special HDMI setup and over loaded the OS, prompting a a "bootloader" screen and got in that way somehow, but far beyond me and said the parts to build it were like $150, let alone knowing what to solder to what etc, beyond my capabilities.
matafact said:
Well, part of the fun, lol. Voice in my head keeps saying the Fire App, has to be a way, but not seeing it as yet. Did read where someone built a special HDMI setup and over loaded the OS, prompting a a "bootloader" screen and got in that way somehow, but far beyond me and said the parts to build it were like $150, let alone knowing what to solder to what etc, beyond my capabilities.
Click to expand...
Click to collapse
Honestly its fun and has also become consuming trying to find any way to get past each screen lol. I heard the same voice in the past and it worked lol. Now with these 5.2.6.3 2nd gen firesticks I have no way to get to Dev options and with the 4k firesticks it says my login is incorrect to Amazon, and as I previously mentioned I am pretty much out of ideas. Overload HDMI huh? Sounds interesting. Well back to the drawing board for now and If I learn anything I will let you know.
Well, Fire App in my head, dont know why, just keeps coming back to me. Not a programmer, not a Droid, Hacker type, but thinking this way, feel free to tell me Nope, won't work and this is why.
How does it pair with FTV Stick etc? Not Bluetooth etc, so how does it connect? Possible to take Fire App and tinker with code, add some/modify code or a script etc to modify it and get further into FTV OS 5?
Or thinking again, don't know, but seems with a Laptop on say WiFi Network, just like Droid, Iphone, with a Virtual Machine, know Virtual Box you can set up about any Android setup ya want.
So setup a Virtual Machine, tinker with Fire App in some way, and if Laptop can connect to FTV , well, just idea in my head that must be away to get around it, or at least with a Laptop would open many more options to try & beat it. Havent tried this yet, just keeps floating around in my head, may not even connect to a Virtual Machine, maybe over weekend I'll tinker with that a bit.
Somebody who programs etc would know far more on topic, but same idea keeps bouncing around in my mind. Could be dead wrong, maybe they have that locked down to, but guys here, well, how many "can't hack" toys have they already beat, lol.
matafact said:
Well, Fire App in my head, dont know why, just keeps coming back to me. Not a programmer, not a Droid, Hacker type, but thinking this way, feel free to tell me Nope, won't work and this is why.
How does it pair with FTV Stick etc? Not Bluetooth etc, so how does it connect? Possible to take Fire App and tinker with code, add some/modify code or a script etc to modify it and get further into FTV OS 5?
Or thinking again, don't know, but seems with a Laptop on say WiFi Network, just like Droid, Iphone, with a Virtual Machine, know Virtual Box you can set up about any Android setup ya want.
So setup a Virtual Machine, tinker with Fire App in some way, and if Laptop can connect to FTV , well, just idea in my head that must be away to get around it, or at least with a Laptop would open many more options to try & beat it. Havent tried this yet, just keeps floating around in my head, may not even connect to a Virtual Machine, maybe over weekend I'll tinker with that a bit.
Somebody who programs etc would know far more on topic, but same idea keeps bouncing around in my mind. Could be dead wrong, maybe they have that locked down to, but guys here, well, how many "can't hack" toys have they already beat, lol.[/QUOTE=matafact;78395384]
I wish I knew how to use tasker. Im a newbie but your ideas are great and have me thinking the remote app is the key, but it is a task I do not know how to execute.
Click to expand...
Click to collapse