I had quite the time getting my Netgear Push2tv adapter working and thought I might share what I learned in case anyone else has issues with theirs. My adapter out of the box was on version 1.0.13 and did not work! The S4 would see it but when I would connect it did nothing but continue to connect until I stopped it. I flashed firmware after firmware to the adapter and power cycled the adapter, my tv, and my phone until it finally worked!! Here is what I did, step by step, in detail, to get it working. (trimmed a bit )
First you must upgrade your Netgear Push2tv to the latest firmware. Here is a link to the official firmware and instructions on how to upgrade.
http://support.netgear.com/product/PTV3000
1) Download the latest firmware version (v2.2.16 as I'm writing this)
2) Unzip it and grab the PTV3000_V2.2.16.sbin file.
3) Hold the side button on you netgear adapter for 7 seconds, it will go to upgrade mode.
4) On your pc go to your wireless connections and connect to the push2tv adapter.
5) On your pc open a browser and type http://192.168.3.1 in the url bar.
6) Upload the unzipped file from step 2, and update it.
I am not sure if the following is needed or not but this worked for me after hours of trial and error
7) After the adapter's firmware was updated and rebooted(automatically), I turned the tv off and on again.
8) I was a few updates back on the rom I was running (hyperdrive v5.7, verizon) so I did a complete wipe and flashed the newest version (v7) with the stock kernel. Once settled into the new rom everything was good to go!!! A full wipe and rom flash may not be needed but that's what I did.
I do know that right after you update the firmware on the adapter you will have to reboot your phone at the very least as it seems to hold the old connection to the netgear adapter. If rebooting your phone doesn't work try rebooting to recovery and wiping cache and dalvik cache. If that doesn't work then try suggest a full data wipe.
I have been through multiple firmwares for the adapter, was getting audio but no video, connect then disconnect, not connecting at all, black screens, hdcp errors you name it. After doing exactly what I stated it is now working and mirroring the screen rather well. There is an acceptable minimal lag time between touches on the phone to the mirroring screen. Any type of action/shooter/racing/ game won't perform well but puzzle or rpg games, videos, web browsing are pretty nice !!!
screen mirroring has been disabled - how smart is the PTV3000?
Hello
I have just bought this gadget and the first thing I did was update the firmware to v2.2.16, the phones see's the PTV and connects but after a short while I get the message "screen mirroring has been disabled" and the phone turns screen mirroring off.
My phone is a GS4 i9505 and I have tried multiple rom's and get the same message everytime, so I have to conclude that its not the phone or what ever ROM I happen to be running.
The first test I did was to the PTV3000 without it being connected to a TV/Display - I get the same message about Screen mirroring being disabled.
The second test I did was on a spare commputer monitor with a DVI port, so used a dvi--to-hdmi adapter. But Im not seeing anything being displayed on the screen, but ive seen this before with this screen as I dont think it supports hdmi properly.
Is the PTV3000 smart enough that if it can't display it will disconnect from the phone..? if that is the case why is the phone disabling screen mirroring rather than just saying it cant display of what ever..?
thanks
b.
Related
I have a 4.0.1 device (car stereo actually, I could post to that thread, but here I will probably pass with more attention).
WIFI sometimes works and sometimes doesn't - I simply can't turn it on.
It stucks at "Wifi turning on" and switch goes back to gray.
When it works it works for few days, and when it doesn't I can't turn it on for like a month. Right now that's the case.
WIFI device is an external USB wifi stick. Stick works elsewhere, and I tried with another one, they both work.
I believe the problem is in the software.
On some devices it can be solved via deleting some files in the system. Has anybody got some ideas how to fix it?
Usually when it works stick LED starts flashing right at boot.
Regular data usb stick also works in that port.
So I've been searching Google all day and still can't find a way around all this...
Phone (Nexus 5) got the black screen of death, where a connector on the motherboard gives up due to heat/old age. It only then works by applying pressure to the connection. The digitizer would sometimes play up and I'd have to press on the spot to write emails and texts. My phone got the the point where it became unusable and the digitizer started spazzing out, in that, the flight mode button got pushed, now the screen doesn't work at all.
So heres my dilemma..
Since I flashed Android 7.1 the USB debugging mode has never stayed on through a reboot and is currently off. That ruins my Vysor option to control the phone via usb. Theres a post about a guy who turned on USB debugging via Cerberus which I have, but with flight mode on that rules that out. I've managed to find my way into recovery and ADB works but I have plenty of issues, maybe because I had to use SUhide atc after 7.1 decided to clamp down on rooted devices with banking apps, snapchat etc. My Slimport hdmi adapter isn't working well but I guess thats a cheap fix and will allow me to at least see the screen, (no digitizer though). Other option is to use usb otg to connect a mouse and try things blind.
So are there any other ideas out there? ADB still may work, I got Boot.img onto my computer, but had trouble unpacking it.
Hi guys,
My screen recently died. Before fixing it at a specialized shop, I want to retrieve the data from the phone. Sadly the phone is pattern-locked and until I unlock it I can't access the data when I connect it to my PC. The screen is essentially dead. The image is almost totally black except for small layer in left top corner and the touch sensor is unresponsive, but other than that the phone works and receives notifications and so on.
USB Debugging mode isn't active on the phone and thus I can't replicate the screen of the phone on my PC through software alone, when I connect it via micro-USB. I also didn't think of this problem in advance and I'm not registered on Sony's FindMyMobile or any similar apps.
I tried using a HDMI-MHL adapter and I confirmed that the phone is indeed working because I'm able to get the phone screen's image on my TV. The problem is I can't actually interact with the phone because as I said earlier the touch sensor is not working.
The HDMI-MHL adapter I've used also seems to have a micro-USB port but that seems to work for power only. If I connect a USB-OTG cable on it and connect a USB mouse to it I get image but no mouse. If I connect the USB-OTG and the mouse, alone, I get a mouse cursor but I can't see what I'm doing (phone vibrates as I 'try' and draw the unlock-pattern blindly).
So, Sony Xperia Z3 Compact screen is dead, I wanna connect my Xperia to my TV via HDMI AND use a mouse at the same time to control my phone. Is this possible_
I also thought of another option... go to recovery mode and flash a zip that removes lock. I thought of trying step by step (switch keyboard and TV al the time just to get at point where I can find zip file and flash it). Unfortunately in recovery mode the phone does not allow to stream to TV. It only works when phone is after SIM lock.
Two additions: by removing and re-installing ADB on my laptop my phone is unauthorized. Only a matter of clicking on yes/allow on phone but that's not possible and TWRP 3.1.1-0 is installed.
Anyone any clue? I know I ask a lot but I'm searching the internetz for 2 days now and I'm devistated.
THNX a great bunch!!!
ciao
Valentijm
PS Copy/paste a part of the text from a guy from the internet who had exactly the same problem as I did but his thread ended a few months ago without result.
Just 30 minutes after my post I magically had all the dots correct and that blind!!! So turned on USB debugging and got rid of lock pattern. It was a nice three days of my life Guess there was no solution than getting lucky like I did or screen replacement and getting all your data removed.
ciao
** This post should be in the "Help & Troubleshooting" section of the Nexus Player - ooops. **
My Nexus Player started hanging up at the 4 balls bounce routine last week. After trying a factory reset, the only thing that I've been able to do to get back to Android boot with TV interface is the OTA restore from the latest version 8.0.
This however doesn't stick, as if the device powers off, powering up, the problem returns.
I had the hdmi output connected to a switch that allows the monitor to be shared with a laptop. If the NP device goes to sleep, the switch automatically opens up the feed from the laptop (dual monitor). If I switch back, the wake up mode becomes the 4 balls again.
Someone pointed to the Oreo upgrade as being problematic. Do these symptoms sound like software or hardware?
I did connect the unit without the switch directly to the monitor and got slightly different results. Now the unit tells me that I need to run system restore which formats /data and another partition then partially loads get the Android screen and starts over. Tried to restore from OTA again and it won't pair with the controller saying "Can't play this video" .
Got it running again, let it run overnight with a channel selection and by morning it had died.
Tried loading a different OTA Ver.8 and it is too smart for that. I am reading though from several sites that I'm not the only one with a partial brick since the update to Ver. 8. - Unfortunately, that was "supposed" to be the last update, yet there appears to have been a "zero day" failure built into it.
OK Google (seems as if Asus isn't responsible) the ball is in your court, yet it's going to be difficult to patch when the device is partially bricked.
ggregor said:
My Nexus Player started hanging up at the 4 balls bounce routine last week. After trying a factory reset, the only thing that I've been able to do to get back to Android boot with TV interface is the OTA restore from the latest version 8.0.
This however doesn't stick, as if the device powers off, powering up, the problem returns.
I had the hdmi output connected to a switch that allows the monitor to be shared with a laptop. If the NP device goes to sleep, the switch automatically opens up the feed from the laptop (dual monitor). If I switch back, the wake up mode becomes the 4 balls again.
Someone pointed to the Oreo upgrade as being problematic. Do these symptoms sound like software or hardware?
I did connect the unit without the switch directly to the monitor and got slightly different results. Now the unit tells me that I need to run system restore which formats /data and another partition then partially loads get the Android screen and starts over. Tried to restore from OTA again and it won't pair with the controller saying "Can't play this video" .
Got it running again, let it run overnight with a channel selection and by morning it had died.
Tried loading a different OTA Ver.8 and it is too smart for that. I am reading though from several sites that I'm not the only one with a partial brick since the update to Ver. 8. - Unfortunately, that was "supposed" to be the last update, yet there appears to have been a "zero day" failure built into it.
OK Google (seems as if Asus isn't responsible) the ball is in your court, yet it's going to be difficult to patch when the device is partially bricked.
Click to expand...
Click to collapse
There are a couple threads on this already. Mine is bricked too at the moment.
https://forum.xda-developers.com/nexus-player/help/stuck-google-screen-t3044191
https://forum.xda-developers.com/nexus-player/help/nexus-player-suddenly-dead-t3814519
Try Method 2 only if you're sure your Remote has no problem and is connected properly. First is trying to determine the course of action. If you just bricked it. Then there's nothing you can do unless you take it to the care center or if you had adb enabled then you can force it into fast boot look after connecting it to your pc. That will be in another post. For now troubleshooting it is our concern.
So you have tried to use the TV Box and you can't force it to go into recovery mode neither have you had any luck with the usb stick update.
Method 1:
The problem is Mi TV Box won't boot and will infinitely boot loop unless the paired remote is connected. So most likely the boot loop is caused as the remote and tv box isn't communicating. Your remote may either be damaged or need a change of batteries or may have been unpaired/disconnected after the update.
So grab a USB mouse or USB Keyboard. Try mouse click and there will be a blank screen. Wait for 5-10 minutes. It takes time to load or is simply slower when disconnected from the remote.
Some keyboards don't work. But if they do, keep pressing either Esc or Enter till the Bootloop ends and brings you to a blank screen. Be patient and use a mouse/keyboard arrow keys to navigate to settings and Remote & Accessories. Then select Xiaomi RC and click on Unpair. The Battery % will be shown if it was connected properly. So then re-pair the remote and then restart. You can restart by holding the power button till the power menu pops up. That's it and that's all. Be careful since both Mi TV and Mi TV Boxes will not make it past the boot screen unless the paired or stock remote is connected properly. You can't find a totally working replacement/spare remote since the remote and the tv box are one unit and if either is damaged or has a manufacturing defect, it can't be easily replaced. As both have sort of link. So suppose you buy two Mi TV 4K Boxes and use both at the same time. The remotes will pair up and be forever linked to one particular at the time of set up. You can't randomly change it after that. Exceptions are always there but this is the case for the most part. Or so I believe it to be.
Method 2: If the above method didn't fix it. The issue is software related. You may need to perform a hard reset using either the recovery or get a keyboard with the same or equivalent combination of keys you'll use on the remote. Considering the remote not working or unable to boot into recovery using the remote. If possible get two people to do the recovery sequence on the remote. Since the remote is good quality and sensitivity for button press. Then load up the stable or latest beta update available onto a pen drive. Make sure that the update package is renamed to update.zip. Before installing Wipe/Reset All Data and it'll ask for confirmation. Confirm it and then proceed to install update.zip. The Pen Drive used may also result in success or failure. So use a reliable know good USB 3.0/2.0 stick. SanDisk gave me issues. I had to re-install thrice to get it to work properly. Also don't use sizes above 16 GB. Upto 32 GB is supported. And it may support external harddisk drives but the format is to be kept in mind. Any pendrive larger than 32 GB comes out of the box with either NTFS or exFAT File System Format. So check that before you put the update on it.