Hello,
Wondering if anyone can help. I have set my AFTV up with XBMC and done everything else. There was an issue with a "Protocol Failure" so I reset it back to Factory Settings using the Alt-Prt Scr-i method and even then when trying to sideload I get the following
connected to 192.......41
protocol failure
-waiting for device-
Does anyone have any ideas how I can get back to sideloading or doing anything else, ADB debugging is ON
edit: It would appear that it is still capable of sideloading smaller files, but maybe times out with some larger ones
Cheers
Just to let anyone else know if you face this problem. It appeared the wireless connection on my network was getting reset. I went wired and all worked well.
Related
Ive got a genuine 3 UK (unbranded) desire and been using it for over a year.
Recently they released a small software update (2.29.405.5). I couldn't install this as not enough space so i thought id do a factory reset to get space, clean up and go from scratch.
Not a problem except after that reset my WiFi has stopped working completely.
It turns on, it shows as on, it scans and it shows WLANs around. However no matter what lan you select the second you enter a key without even trying to connect it says "Unable to connect to the network".
If i try to manually add a network i get "Unable to save the network".
It doesnt even seem to attempt to connect, just errors immediately. It's not a key issue as entering any key either correct or incorrect immediately produces the above error.
After a factory reset failed to get it working i rooted the phone to delete/edit the wpa_supplicant.conf file. This didn't solve the problem.
As a last resort i downloaded the latest RUU, flashed but again this hasn't fixed the problem.
So, does anyone know whats broken or how i can fix this or is it a return on the phone?
Everything else would appear to work perfectly but it just refuses to save any details of wlans or connect to them. It all worked fine before a factory reset!
A couple hours ago, the AFTV wouldn't play any Prime video and would just hang on the Netflix screen with the loading icon. Fairly certain it was on 51.1.1.0_user_511070220. Definitely 51.1.1.0. This was rooted with updates turned off using the adbFire app and a few Amazon URLs blocked in my router's access restrictions. After rebooting the AFTV a couple times, I read that a lot of solutions online were to delete the Prime/Netflix apps' data/cache. That didn't fix it. So then I followed the next common step and deauthorized the account. This is where the AFTV starting going crazy. After putting the user/pass back in, it started very quickly flashing between the "Authorizing Your Device" screen and the "Could not connect screen." A lot of button mashing broke the loop but every time I entered the user/pass, the loop would begin again. Hard and soft rebooting had no effect. Turning off the router (running AdvancedTomato) access restriction didn't help. I even used adbFire to very temporarily re-enable updates. Still no access.
I figured that this was a sign I should protect my root better. It may have been a mistake, but I decided to try and install Clockwork recovery. I left the "pm disable com.amazon.dcp" from adbFire enabled. So Amazon updates were still blocked. I downgraded to 51.1.0.2_user_510058520 kinda not realizing that this would kill my root and maybe also not realizing that Clockwork would need root to install.
I now have the same exact problem as before. I am stuck on the registration page and cannot sign in. It either says that the "sign in failed" or that the "connection was lost." At least on this earlier firmware, it doesn't seem to get stuck on the flashing loop between those two screens. There is some new weirdness where it seems to be pressing buttons on its own somehow. The text entry menu will disappear as if I closed it. And then when I select it again, it's in a broken format with all the keyboard buttons there, but the input field names missing.
I have verified that the current firmware is 51.1.0.2_user_510058520 with "grep fingerprint /system/build.prop".
I am 99% sure that nothing else from amazon is blocked besides "pm disable com.amazon.dcp", which I'm now unable to turn on again as I don't have root. adbFire says that "Amazon updates are off". I thought that this was reset by a downgrade? I can't think of anything else to check. I used to use dnsmasq to block three Amazon URLs before I found AdvancedTomato's Access Restriction but dnsmasq is empty and the rule in Access Restriction is deleted.
I am 99% sure I never edited my AFTV's hosts file. I just did "adb pull /system/etc/hosts" and all it has in it is "127.0.0.1 localhost".
Is there anything else I should check?
Just tried it again this morning. After every "sign in failed," if I let it sit on the failed screen with the keyboard where it wants me to enter user/pass again and touch nothing for 5-10 seconds, it will suddenly close that keyboard pop up and then immediately reopen it -- except it will be broken in that it's missing all the labels for fields like "Enter email here".
?
If you have Amazon.dcp disabled then remove all the blocked sites from the router and boot it up and see if you get connected. Maybe a site you have blocked is the issue
{ParanoiA} said:
If you have Amazon.dcp disabled then remove all the blocked sites from the router and boot it up and see if you get connected. Maybe a site you have blocked is the issue
Click to expand...
Click to collapse
I don't know where the router block could be. The rule in Access Restrictions is deleted and the Dnsmasq field is empty. I'm going to try using a cell phone hot spot to register it. Probably won't change anything but I can at least rule out the router as a problem.
I'm having a huge issue. My Wi-Fi won't work on my 2013 Nexus. I select it. It sees it with a full signal and I put in the password, It just says saved. I tried with a connection without a password, it says the same thing. I tried flashing back to factory multiple times but it does nothing. It was working and just all of a sudden went out on me. Is there a way to flash a driver or something?
lowridincrew said:
I'm having a huge issue. My Wi-Fi won't work on my 2013 Nexus. I select it. It sees it with a full signal and I put in the password, It just says saved. I tried with a connection without a password, it says the same thing. I tried flashing back to factory multiple times but it does nothing. It was working and just all of a sudden went out on me. Is there a way to flash a driver or something?
Click to expand...
Click to collapse
Firstly, just reboot the WiFi access point and try to connect to it again.
Did you change firmware or any settings on the WiFi access point? Do other devices connect to it properly?
Can your Nexus connect to other WiFi access points? Try it with your mobile's WiFi hot spot.
Finally, we need some logs:
turn off N7 wifi
start logcat (I prefer 'time' format: adb logcat -v time > log.txt )
turn on N7 wifi
try to connect
stop logcat
compress and post the log here
Hey guys, I am needing some help. I have a First Gen FireTv box that was rooted previously and is now stuck on the registration screen when you first start up the box.
Here's what I did to get to this place. The box was rooted with CWM recovery installed. I followed this guide and made it back to the registration screen. When I tried to log back into the firetv box I kept getting "The information does not match an Amazon account. If Sign in Approval is enabled, please follow the instructions on your phone." The problem is, that I don't have Sign in Approval enabled (that I know of) and I never received any type of message on my phone... During my sign in attempt, I also kept getting the Critically Low on Storage popup.
After trying to sign in, I tried to connect to the box using ADB again, and it actually worked. That told me that something wasn't quite right with the downgrade process so I re-installed CWM and ran through the guide again and then went in and did a wipe of all user data thinking it would clear up the storage issue. I am pretty sure the storage issue is cleared up, but unfortunately, I now cannot log into my firetv to check the firmware version or enable ADB. Is there anything I can do to fix this issue? Please help before I screw things up even more with this box (if that's even possible)
silverphoenix98 said:
Hey guys, I am needing some help. I have a First Gen FireTv box that was rooted previously and is now stuck on the registration screen when you first start up the box.
Here's what I did to get to this place. The box was rooted with CWM recovery installed. I followed this guide and made it back to the registration screen. When I tried to log back into the firetv box I kept getting "The information does not match an Amazon account. If Sign in Approval is enabled, please follow the instructions on your phone." The problem is, that I don't have Sign in Approval enabled (that I know of) and I never received any type of message on my phone... During my sign in attempt, I also kept getting the Critically Low on Storage popup.
After trying to sign in, I tried to connect to the box using ADB again, and it actually worked. That told me that something wasn't quite right with the downgrade process so I re-installed CWM and ran through the guide again and then went in and did a wipe of all user data thinking it would clear up the storage issue. I am pretty sure the storage issue is cleared up, but unfortunately, I now cannot log into my firetv to check the firmware version or enable ADB. Is there anything I can do to fix this issue? Please help before I screw things up even more with this box (if that's even possible)
Click to expand...
Click to collapse
Use any browser on your PC/Mac to recoup (using the email you used to create it) or create a new Amazon account. Then log in.
You should still look into moving into PreRooted FireOS 5. The low storage will be back quickly. That bug was never fix on FireOS 3. The only true fix is updating to FireOS 5.
I'm trying to setup a brand new firestick 4k since my other one is up to date and I want the launcher changed without using that launch at boot app.
This firestick is currently at 6.2.8.1 (NS6281/3387). It's not rooted.
I kept the internet on for as short as possible while I was setting up the firestick. However, it still started downloading an update.
6.2.8.9 (NS6289/3905) is approx 50% downloaded. I still have it connected to my wifi network, but I killed my actual internet connection.
What do I do now??? I tried removing the files with ADB on my PC but I think I followed the wrong tutorial. The download is still there.
Any ideas??
ThaDraGun said:
I'm trying to setup a brand new firestick 4k since my other one is up to date and I want the launcher changed without using that launch at boot app.
This firestick is currently at 6.2.8.1 (NS6281/3387). It's not rooted.
I kept the internet on for as short as possible while I was setting up the firestick. However, it still started downloading an update.
6.2.8.9 (NS6289/3905) is approx 50% downloaded. I still have it connected to my wifi network, but I killed my actual internet connection.
What do I do now??? I tried removing the files with ADB on my PC but I think I followed the wrong tutorial. The download is still there.
Any ideas??
Click to expand...
Click to collapse
Disable the ota apps then clear settings
Code:
adb shell pm clear com.amazon.tv.settings.v2