Nexus 7 2013 WiFi - WiFi won't turn on after Marshmallow upgrade - bad Mac Address - Nexus 7 (2013) Q&A

Just sideloaded the Mashmallow update from 5.1.1 to 6.0 (downloaded from Google) and the update seemed to go normally - most things work as normal. But the WiFi wouldn't turn on, and it's mac address reports as 02:00:00:00:00:00. That address I know was an issue in the M Preview as a fake address.
I didn't want to hard reset it but in the end relented and loaded a clean new version of 6.0 from Google. When it restarts the second thing it wants to do, after selecting a language, is start the WiFi so it can log on. Of course WiFI won't start, and I can't "skip" so it's stuck. I tried Bad_Boyz fromXDA, and then going back to 5.1.1, and now forward again to 6.0 - same result. I suspect the WiFi mac address has been cleared. I found a little help that if I shell into the tablet, and write the mac address into /persist/wifi/.macaddr I might move forward. I know how to do this, but I can't shell in with adb. I can talk over USB, and run fastboot. When I connect via USB the Nexus mounts (sort of - the storage folder isn't shown when the tablet is at the "Select WiFi network" stage of setup)
When I run "adb devices" - I can't see any, even though I can "fastboot reboot recovery" and the like. I'm sure bluetooth (mac address) is broken too, but I"ll fix that later.
Does anyone have any idea how I can encourage adb to talk, so that I can "adb shell"?

Safe Mode
Just so you know - I started it in safe mode, which I have done before, but anyway - and the WiFi works. Also, USB debugging is presumably switched to off on a hard reset, and I couldn't log in to enable it without working WiFi. Suddenly my mac address is back. Don't really know if safe mode is the answer but it's worth trying...
To get into Safe Mode - long press on the "Power Off" question when you turn it off - it reboots in safe mode.

Related

[Q] I9195 - Unable to connect to WIFI network (Authentication error occurred);

So, here it goes.
My goal is to connect to a network using certain MAC address. Wanted network is marked with "open" and I know that it allows access only to certain devices (according to MAC) on which the administrator have gave a permission to. Once your MAC passes the verification, device gets connected to the network and then I'm asked to enter username and password through WEB browser (well known for me, because it is a procedure that I do on my other device, as well as all my colleagues do).
For example, I was allowed to provide one personal MAC address to administrator to connect to this network. I would like to set the MAC address of my other personal device and set it on my I9195 so that I can access the same network.
So, what have I done so far: I9195 is rooted, it has Android 4.2.2 on it and Busybox installed. I have changed MAC on it using following apps: MacChanger (blue WIFI logo), MAC Address Ghost (green ghost logo), using Android Terminal Emulator commands and via MAC Spoofer (black circle with green text logo). What can I conclude: As soon as superuser has granted the access to these apps, all of them manage to change the MAC. I've done the verification using Terminal Emulator. I also have to add that the MAC remains original if viewed from WIFI advanced menu BUT this shouldn't be an issue because:
1.) Colleague of mine is using his S4 (rooted etc.), while using MAC Address Ghost that does not change the original address (viewed from WIFI advanced menu) but he manages to make a spoof (verified from the Android Terminal Emulator, as all of this apps actually do) and he manages to connect without any problems in the same way as I connect with another device that I have!
2.) I had time to make a small test at home which put a light on the idea that the problem should be focused on the Samsung (and not on the router, especially because I am unable to modify anything on the router on this facility, not even restarting it). My home network works in a similar way as the network that we are discussing about. My S4 Mini has been included in it with his original MAC and it connects to the network without any problems. My other device is also included to the network using its MAC (the one that I am using for spoofing). My other device is turned OFF, router has been reset and I am normally accessing the network with S4 Mini. Then I run the MAC Address Ghost to spoof the MAC on my S4 Mini. In that moment, I have lost the connection that I had which means that the MAC spoofer actually did something. I tried to reconnect to the network but then I am asked to enter the password for my network. I have checked and re-checked it many times, tried to forget the network and doing it all over again but it does not accept the CORRECT password. Changing my MAC back to the original one connects S4 Mini back to the network, while accepting the password immediately.
Problem is represented in a way that it either says “saved” and does not connect to the network or every few times displays a message “Authentication error occurred”.
I have tried I would say every possibility that I’ve seen over the internet. That includes:
1.) Installing WiFi Connection Manager (it provided some info regarding the network that I wish to connect to: IEEE 802.11g standard, 54 Mb link and CH:11). I’ve used its function to fix the WIFI (advanced fix (root required)) but it didn’t help.
2.) All sorts of staying close to the rooter, while enabling and disabling the Power save mode (accessed via *#0011# command) or while having GSM signal.
3.) Browsing through system, data etc. folders to try to find the file that contains the MAC address information (like it did on older android versions in the nvram file). I’ve been unable to find this file or any sort of file that displays my MAC for the purpose to modify it.
I have a plan to upgrade Android to version 4.4.2 later today and make a test.
Please, feel free to suggest anything else! If I do not succeed, I will have to replace my S4 Mini with something else.
Kind regards,
QUICK REPLY: After installing CyanoGEN MOD 4.4.2, the problem remains!
I think there could be a shorter solution! On Sony Xperia Acro S with 4.1.2 Android it was just a matter of changing the MAC address within the file data/etc/wifi/fw! One minute modification...
So, please, if somebody knows the path to the file that contains MAC on CyanoGEN MOD 4.4.2 or on Android 4.2.2, PLEASE HELP!
Kind regards!

Wi-Fi won't connect -Wi-Fi Connection Failure

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

Elephone S7 fix the changing WiFi MAC adress

I have fixed mine.
There was no MAC address programmed to the device at factory. That's an omission. So the WIFI driver when activated after restart or by turning wifi off/on notices that and gives a temporary MAC address.
That address changes in the last bytes.
The solution is to write a WIFI MAC address with an appropriate tool. I did use SN_Writer just be careful to leave the other data alone.
I guess the same happens with the Bluetooth address but did not check that out yet.
0) Choose a valid MAC just look under settings the temporary one that your phone uses that's ok
1) Install VCOM Driver if you don't have it yet
If you use Windows 10 then you have to temporarily disable Driver Signature check since those drivers are not signed
Instructions and download here
http://forum.xda-developers.com/elephone-m2/help/windows-10-mtk-vcom-usb-drivers-32-64-t3267033
2) Download the SN_Writer I did use that one, password is mtk2000
http://mtk2000.ucoz.ru/down18/SN_Writer_Tool_v1.1648.rar
3) Download the right stock rom for your device you need the file which is named like the one I did use
APDB_MT6797_S01_alps-mp-m0.mp9_W16.48
4) Power off phone
5) In SN_Writer hit System Config uncheck everything and check Wifi Adress on the left side
In database file AP_DB use the file from 3)
That should do it.
Hit Start and entry the MAC just the digits no dashes etc.
Connect the phone while holding Volume Down.
That should do it.
Thanks for the write up, I got my S7 WiFi MAC address fixed now too, with your steps !!
Bluetooth appears already fixed/correct. (Also I haven't noticed my paired bluetooth devices loosing pairing..)
FunkiBluDawg said:
Thanks for the write up, I got my S7 WiFi MAC address fixed now too, with your steps !!
Click to expand...
Click to collapse
Great! Also good that Bluetooth is correct. Did not pair anything yet but good to know there won't be similar problems.
Idakis said:
I have fixed mine.
There was no MAC address programmed to the device at factory. That's an omission. So the WIFI driver when activated after restart or by turning wifi off/on notices that and gives a temporary MAC address.
That address changes in the last bytes.
The solution is to write a WIFI MAC address with an appropriate tool. I did use SN_Writer just be careful to leave the other data alone.
I guess the same happens with the Bluetooth address but did not check that out yet.
0) Choose a valid MAC just look under settings the temporary one that your phone uses that's ok
1) Install VCOM Driver if you don't have it yet
If you use Windows 10 then you have to temporarily disable Driver Signature check since those drivers are not signed
Instructions and download here
http://forum.xda-developers.com/elephone-m2/help/windows-10-mtk-vcom-usb-drivers-32-64-t3267033
2) Download the SN_Writer I did use that one, password is mtk2000
http://mtk2000.ucoz.ru/down18/SN_Writer_Tool_v1.1648.rar
3) Download the right stock rom for your device you need the file which is named like the one I did use
APDB_MT6797_S01_alps-mp-m0.mp9_W16.48
4) Power off phone
5) In SN_Writer hit System Config uncheck everything and check Wifi Adress on the left side
In database file AP_DB use the file from 3)
That should do it.
Hit Start and entry the MAC just the digits no dashes etc.
Connect the phone while holding Volume Down.
That should do it.
Click to expand...
Click to collapse
thanks a lot, worked like a charm. I really needed that fix as i put mac control on my router
Meta_maui_db_inconsistent
After:
"Connect the phone while holding Volume Down."
... just a message "META_MAUI_DB_INCONSISTENT" und the process break it
You have an idea what I can still check?
66krieger said:
After:
"Connect the phone while holding Volume Down."
... just a message "META_MAUI_DB_INCONSISTENT" und the process break it
You have an idea what I can still check?
Click to expand...
Click to collapse
Sorry for my late answer.
Double check step 3) you need the correct file from the correct stock rom for your device.
If that still doesn't work I would try reflashing the bootloader preloader (only) from stock ROM and try again.
It should work.
I'm not having any luck with my device on windows 10.
Whenever I try to connect my device to windows via usb, a pop appears - (USB device not recognized-the last USB device you connected to this computer malfunctioned ,and Windows does not recognize it) .
I've also tried to clean up my usb drivers and re-install MTK preloader.
Any advice how I might fix this?
File APDB_MT6797_S01_alps-mp-m0.mp9_W16.48?
Hi,
Where do I find the file "APDB_MT6797_S01_alps-mp-m0.mp9_W16.48"?
It's not available on Google.
Thanks!
Thank q so much .. Fix it.

Mi A2 Lite Bluetooth Audio Problems? Back To Oreo?

Hi There,
Just bought my GF a Mi A2 Lite a few weeks ago and she is loving it compared to her old iPhone 5s but one major issue atm is that her bluetooth headphones seem to be giving her issues!
The audio stutters a LOT even when right next to the phone. Tried resetting the Bluetooth connection but to no avail.
I had a quick scan through the forums and seen that people recommend going back to Oreo to solve the issues.
Is there any clear guides or links on how to do this? I know my way around tech so should have any issues following a guide.
Thanks in advance!
Yes, it's a very annoying bug.... I have it too, but didn't find a solution
That's the reason why I downgraded to Oreo!
If you want to downgrade,
1. you must unlock the bootloader, but this will erase all of your data. So, don't forget to make a backup of your internal storage. https://forum.xda-developers.com/mi-a2-lite/how-to/guide-how-to-unlock-bootloader-official-t3885578
2. Install MiFlash and ADB on your computer: https://www.xiaomiflash.com/download/ https://forum.xda-developers.com/showthread.php?t=2317790
3. Download an oreo stock rom and unzip it: https://forum.xda-developers.com/mi-a2-lite/how-to/fastboot-xiaomi-mi-a2-fastboot-images-t3824871
4. Boot your phone into bootloader
-> Connect your phone with your computer and enable ADB in developer settings
-> Shutdown your phone and hold Volume Down and Power-Button to boot your phone into fastboot/bootloader
5. Open the MiFlash-Tool on your computer and select the Oreo-Stock-Rom which you want to install.
6. At the bottom of the MiFlash window you must choose clean all, this will erase all of your data!
7. If your phone gets recognized from your computer and the programm, then you can hit the button flash on the top of the window
8. This procedure takes a while, so be patient.
9. If everything works, it will reboot your phone automatically.
10. Maybe you will have the bug of swapped SIMs. You must install TWRP: https://forum.xda-developers.com/mi-a2-lite/development/official-twrp-daisy-t3855396
and flash this file to fix it: https://forum.xda-developers.com/attachment.php?attachmentid=4704476&stc=1&d=1550012435
11. Perfect! You downgraded to Oreo!
I hope this little guide could help you, and sorry if it's a bit complicated
If it's any consolation, I had this issue on Oreo and Pie!
I'm now upgrading to a Pixel 3a, but keeping this phone for development. Might try porting Ubuntu Touch some time. ?
iforgotmylogin said:
If it's any consolation, I had this issue on Oreo and Pie!
I'm now upgrading to a Pixel 3a, but keeping this phone for development. Might try porting Ubuntu Touch some time. ?
Click to expand...
Click to collapse
Okay, that's weird ?
Maybe there was a problem with your Bluetooth headset?
00norman00 said:
Okay, that's weird ?
Maybe there was a problem with your Bluetooth headset?
Click to expand...
Click to collapse
If so, it was a problem with every one I tried!
I tried on a generic Bluetooth speaker, two different generations of Echo Dot, and on a current gen regular Echo.
It is channels problem. Bluetooth and WiFi are on 2.4GHz. Some frequencies are busy and it stutters. Turn off WiFi and Bluetooth. Turn Bluetooth on and connect your Bluetooth device. Wait 10 seconds and turn on WiFi. After this WiFi will avoid frequency where is Bluetooth device and use free frequencies.
LotR656 said:
It is channels problem. Bluetooth and WiFi are on 2.4GHz. Some frequencies are busy and it stutters. Turn off WiFi and Bluetooth. Turn Bluetooth on and connect your Bluetooth device. Wait 10 seconds and turn on WiFi. After this WiFi will avoid frequency where is Bluetooth device and use free frequencies.
Click to expand...
Click to collapse
Interesting... sounds like a pain in the ass, but I'll try this next time I get chance.
Thanks!
LotR656 said:
It is channels problem. Bluetooth and WiFi are on 2.4GHz. Some frequencies are busy and it stutters. Turn off WiFi and Bluetooth. Turn Bluetooth on and connect your Bluetooth device. Wait 10 seconds and turn on WiFi. After this WiFi will avoid frequency where is Bluetooth device and use free frequencies.
Click to expand...
Click to collapse
But it stutters also when wifi is offline. And on Android 8 I don't have this frequency-problem
00norman00 said:
But it stutters also when wifi is offline. And on Android 8 I don't have this frequency-problem
Click to expand...
Click to collapse
You can solve by adding the the missing codecs, all the routes are still there, xiaomi removed licensed codecs
Downgrade helped as of 30.05.2019
Mi A2 lite
Bought Galaxy Buds. Stuttered and eventually lost connection.
NOTE:What comes ahead is my personal experience (with some software errors that doesnt seem to have effect on our goal) downgrading my MI A2 lite to Oreo.
Downloaded Android Oreo 9.6.11 , ADB and Fastboot, Miflash(latest from site) from links in the beginning of the thread.
Very few proper video tutorials (Indian mostlyXD).
Enabled developer options on my phone (tapping 7 times on build number). In developer options enabled allow OEM unlock and turned on usb debug mode.
Turned off phone and launched it it fastboot mode (hold "volume down" and power button simultaneously). Connect phone to PC via usb.
Open folder on PC where you installed ADB and fastboot software. Launch cmd.exe or smth. In black window type "fastboot oem unlock" Enter. The phone reboots (takes a lot of time dont be alert) and wipes data from your phone. You will see a scary message/warning (disappear s after few sec) that asks you to lock bootloader back.
NOTE: somehow my device did not ask for any confirmations for enabling unlocked bootloader.
NOTE 2: I was trying to do this whole process by video and text guides. Some ppl type commands in cmd "fastboot flashing unlock" and then "fastboot flashing unlock_critical" BUT for some reason this commands did nothing. So all I did is oem unlock command.
After OEM unlock command rebooted phone skip all phone setups and open developer mode again (if it is locked) and in dev options check if "allow oem unlock" and usb debug mode is turned on. Turn off your phone and load it in fastboot mode (volume down+power).
On PC unpack Android Oreo files. It should look like a long name folder with some .bat files and folder (avoid unpacking in place with strange name paths).
Launch MiFlash tool. NOTE: it gave me a prompt for installing drivers and after i pressed it gave an error. It is fixed by creating inside MiFlash tool folder a new folder and naming it "log". Then launch the tool again and press install drivers.
Once you are in MiFlash program there is a ling space where you can insert a file path. You need to copy a file path that leads to your unpacked Android Oreo files (the path should lead inside where the .bat files located). Paste this copied path into MiFlash path bar and press refresh button. If there is no error you can proceed by pressing in the bottom right corner a "clear all" option and in the top right "flash" button. This will install Android Oreo on your mi a2 lite.
After the process is done i had an error in MiFlash program BUT the phone reboots on its own with downgraded Android version. Turn the phone off, load it in fastboot mode, connect via usb and run in ADB folder CMD.exe and run "fastboot oem lock" command. The phone reboots, takes a while.
!!!
After it reboots immediately skip all phone setup menus especially wifi and account options and go straight in settings to unlock developer mode. In developer options TURN OFF AUTOMATIC SYSTEM UPDATES! After it you can finish phone setup process ,accounts, networks and everything else.
An Android message "update available" can pop up. To get rid of it for good simply swipe it slowly A BIT (not all the way) till you see a cog sign (options icon) and there turn of this notification.
Now you can go smoke a cigar. Android 8.1.0 Oreo installed AND it wont update automaticlly to PIE. You can use your bluetooth devices properly (or whatever problems you had).
Have a nice day. Gonna probably go buy Samsung A30. This **** is unacceptable. Pie update rolled out long time ago (Android Q is releasing in 3 months from now) and this stuff is still not fixed. Wtf
Solution
I did a simple step to fix pair
Reboot into safe mode, pair the select device, after pair reboot out the safe mode and you see the device paired.
Cheers
---------- Post added at 10:15 PM ---------- Previous post was at 10:14 PM ----------
I did a simple step to fix pair
Reboot into safe mode, pair the select device, after pair reboot out the safe mode and you see the device paired.
Cheers

How to disable OTA on new Firestick being setup?

Amazon is pushing a new version for the Firestick 4K (not max) running fire OS 6.2.x.x.
This update prevents you from using your own launcher.
So, to prevent updates, you can disable a few of the OTA system modules, however if running a version higher than 6.2.8.1 (xxx/40xx) (for example /4812 is higher than /4061 and /4812 wont work), then you can NOT disable the OTA modules because they are now "protected" files.
So, I have two Amazon firesticks 4k that come with a version of fire os that you CAN disable the OTA files, but I can't fugure out a way to do it because part of the process of setting up a new stick will check for the "latest" firmware and install it - which will install the version that you can NOT disable the OTA files.
So, is there a way to use ADB or some other method to disable these files when setting up a new firestick?
com.amazon.device.software.ota
com.amazon.tv.forceotaupdater.v2
com.amazon.device.software.ota.override
(and this is assuming that the setup process will continue it the check for the latest firmware fails if these files are disabled).
i been trying the same but firestick setup will not continue if you block the updates......i dont know if anyone will find away to set up a new stick without downloading the new updates
GRAM333 said:
i been trying the same but firestick setup will not continue if you block the updates......i dont know if anyone will find away to set up a new stick without downloading the new updates
Click to expand...
Click to collapse
Follo my post .
[APP][FIRETV][NOROOT] Launcher Manager (Change Launcher without Root)
LAUNCHER MANAGER (FOS 6+) STEPS TO ENABLE CUSTOM LAUNCHER: Before installing version 1.1.8 uninstall any previous version. 1. Download Launcher Manager by clicking or by using short link and install on your FireTV. (Latest: 1.1.8) 2. Install a...
forum.xda-developers.com
2 options:
Unplug the rj11/rj45 cable from your router so you still have wifi but it has no internet access. Try setup your firetv and see if it allows you to get to the dashboard. If it does enable adb and disable the update packages:
Code:
pm disable-user com.amazon.tv.forcedotaupdater.v2
pm disable-user com.amazon.device.software.ota
pm disable-user com.amazon.device.software.ota.override
pm clear com.amazon.device.software.ota
reboot
Another option is to first change the DNS value on your router's DHCP config to push out the DNS entry of 104.155.28.90 and 104.154.51.7 before you power on your devices. Then setup your devices as per usual and your devices shouldn't be able to pull the new updates down.
roligov said:
2 options:
Unplug the rj11/rj45 cable from your router so you still have wifi but it has no internet access. Try setup your firetv and see if it allows you to get to the dashboard. If it does enable adb and disable the update packages:
Code:
pm disable-user com.amazon.tv.forcedotaupdater.v2
pm disable-user com.amazon.device.software.ota
pm disable-user com.amazon.device.software.ota.override
pm clear com.amazon.device.software.ota
reboot
Another option is to first change the DNS value on your router's DHCP config to push out the DNS entry of 104.155.28.90 and 104.154.51.7 before you power on your devices. Then setup your devices as per usual and your devices shouldn't be able to pull the new updates down.
Click to expand...
Click to collapse
i set up opendns on my laptop.....blocked the updates.....set up mobile hotspot on the laptop and connected firestick to that.....the set up on new stick will not complete because the firestick cannot connect to the blocked updates,,,.........Unplugging the rj11/rj45 cable does not work either as same thing....firestick cannot connect to updates
Why don't they just follow the instructions in my link?
Original Source ->> https://troypointinsider.com/t/block-amazon-system-updates/43814/45
The goal is to enter the VoiceView mode.
See point 4-7
1. Turn on your mobile hotspot on your phone.
2. Get to the part where you connect to a network and connect to your hotspot.
3. As soon as it says “getting updates” disconnect your hotspot.
4. On the next page that says network error, hold down the back and menu buttons at the same time for a couple seconds to enter VoiceView mode.
5. Push the back button to exit VoiceView mode (with your hotspot still disconnected).
6. You should now be at the registration page. Go ahead and enter your Amazon credentials and turn your hotspot back on to connect.
7. As soon as your account registers and you get to the home page, proceed to use your preferred method of blocking system updates.
fire_cuber said:
Why don't they just follow the instructions in my link?
Original Source ->> https://troypointinsider.com/t/block-amazon-system-updates/43814/45
The goal is to enter the VoiceView mode.
See point 4-7
1. Turn on your mobile hotspot on your phone.
2. Get to the part where you connect to a network and connect to your hotspot.
3. As soon as it says “getting updates” disconnect your hotspot.
4. On the next page that says network error, hold down the back and menu buttons at the same time for a couple seconds to enter VoiceView mode.
5. Push the back button to exit VoiceView mode (with your hotspot still disconnected).
6. You should now be at the registration page. Go ahead and enter your Amazon credentials and turn your hotspot back on to connect.
7. As soon as your account registers and you get to the home page, proceed to use your preferred method of blocking system updates.
Click to expand...
Click to collapse
ok thanks....i will give that a try
Note to 6.2.8.1/4812 on which I am also.
com.amazon.device.software.ota (can no longer be disabled via ADB)
com.amazon.tv.forceotaupdater.v2 (can still be disabled via ADB)
com.amazon.device.software.ota.override (can no longer be disabled by ADB)
So the updates have to be blocked via DNS or in the router or via Blockada APP.
But the Wolf Launcher still works via home button.
This no longer works from the Fire OS 6.2.8.7 NS6287/3768.
GRAM333 said:
ok thanks....i will give that a try
Click to expand...
Click to collapse
Let us know if it works.
fire_cuber said:
Why don't they just follow the instructions in my link?
Original Source ->> https://troypointinsider.com/t/block-amazon-system-updates/43814/45
The goal is to enter the VoiceView mode.
See point 4-7
1. Turn on your mobile hotspot on your phone.
2. Get to the part where you connect to a network and connect to your hotspot.
3. As soon as it says “getting updates” disconnect your hotspot.
4. On the next page that says network error, hold down the back and menu buttons at the same time for a couple seconds to enter VoiceView mode.
5. Push the back button to exit VoiceView mode (with your hotspot still disconnected).
6. You should now be at the registration page. Go ahead and enter your Amazon credentials and turn your hotspot back on to connect.
7. As soon as your account registers and you get to the home page, proceed to use your preferred method of blocking system updates.
Click to expand...
Click to collapse
worked great....thanks for the help
GRAM333 said:
worked great....thanks for the help
Click to expand...
Click to collapse
@GRAM333
What version and build did your device have after the factory reset?
Were you able to successfully disable updates using both commands?
linuxlad said:
@GRAM333
What version and build did your device have after the factory reset?
Were you able to successfully disable updates using both commands?
Click to expand...
Click to collapse
used a new firestick lite. version 7.2.4.2....then i installed update blocker and wolf launcher
GRAM333 said:
used a new firestick lite. version 7.2.4.2....then i installed update blocker and wolf launcher
Click to expand...
Click to collapse
@GRAM333
What version was it before you did the factory reset?
linuxlad said:
@GRAM333
What version was it before you did the factory reset?
Click to expand...
Click to collapse
I think he did NOT do a factory reset - he simply "setup" a brand new stick and used that special process to prevent it from downloading the latest version during the setup process.
And his stick probably had version 7.2.4.2 on it out-of-the-box, and since he was able to skip the update process during setup - so it stayed a 7.2.4.2, he was then able to disable those two OTA files, so now it won't ever do an update.
JohnC said:
I think he did NOT do a factory reset - he simply "setup" a brand new stick and used that special process to prevent it from downloading the latest version during the setup process.
And his stick probably had version 7.2.4.2 on it out-of-the-box, and since he was able to skip the update process during setup - so it stayed a 7.2.4.2, he was then able to disable those two OTA files, so now it won't ever do an update.
Click to expand...
Click to collapse
yes ....i think amazon is still sending out sticks without the latest software so if you get a new stick it is still possible to do....
fire_cuber said:
Why don't they just follow the instructions in my link?
Original Source ->> https://troypointinsider.com/t/block-amazon-system-updates/43814/45
The goal is to enter the VoiceView mode.
See point 4-7
1. Turn on your mobile hotspot on your phone.
2. Get to the part where you connect to a network and connect to your hotspot.
3. As soon as it says “getting updates” disconnect your hotspot.
4. On the next page that says network error, hold down the back and menu buttons at the same time for a couple seconds to enter VoiceView mode.
5. Push the back button to exit VoiceView mode (with your hotspot still disconnected).
6. You should now be at the registration page. Go ahead and enter your Amazon credentials and turn your hotspot back on to connect.
7. As soon as your account registers and you get to the home page, proceed to use your preferred method of blocking system updates.
Click to expand...
Click to collapse
hi,,,,,did all this and all fine and registered but as soon as i connect to internet again brand new firestick lite begins download update ...then when update is download it automatically restarts so i have no time to block updates or remove the update.....what can i do...is there any way to prevent the restart ....this is the first time i have seen the automatic restart,,,is this a new update......thanks
fire_cuber said:
Why don't they just follow the instructions in my link?
Original Source ->> https://troypointinsider.com/t/block-amazon-system-updates/43814/45
The goal is to enter the VoiceView mode.
See point 4-7
1. Turn on your mobile hotspot on your phone.
2. Get to the part where you connect to a network and connect to your hotspot.
3. As soon as it says “getting updates” disconnect your hotspot.
4. On the next page that says network error, hold down the back and menu buttons at the same time for a couple seconds to enter VoiceView mode.
5. Push the back button to exit VoiceView mode (with your hotspot still disconnected).
6. You should now be at the registration page. Go ahead and enter your Amazon credentials and turn your hotspot back on to connect.
7. As soon as your account registers and you get to the home page, proceed to use your preferred method of blocking system updates.
Click to expand...
Click to collapse
Disconnecting internet method (fire_cuber linked above, Thank You!) worked to not auto update at initial set up on a new fire TV stick 4k and able to register just now.
I disconnected it soon after fire tv home screen and checking what Fire OS it has. Looks like Amazon is currently shipping the 4K with Fire OS 6.2.9.2 (NS6292/4226). Is this a bad one? Can I not put Wolf that others have mentioned as a better interface/launcher?
I have not connected it back on until I know how to disable the auto update completely? Can someone direct me to how to disable it? I read a few adb methods but don't know if they still work. Anyone has done it recently? Will it start downloading updates immediately when I connect it back on? Thanks guys.
I think that these versions are when it started that you could no longer easily install a third party launcher:
Fire OS 6.2.8.1+
Fire OS 7.2.5.6+
And at some version prior to the above versions is when they started to prevent the ability to disable OTA.
A bit late but.......
I disabled OTA by blocking the servers that provide the updates on my router's /etc/hosts file and then verified they were blocked by pinging them on my PC. You should be able to block the sites in your router GUI.
Block the following.
amzdigitaldownloads.edgesuite.net
softwareupdates.amazon.com
updates.amazon.com
Code:
[email protected]# cat /etc/hosts
127.0.0.1 localhost
127.0.0.1 amzdigitaldownloads.edgesuite.net
127.0.0.1 softwareupdates.amazon.com
127.0.0.1 updates.amazon.com
I got the server info from here fwiw.
a screen will appear, which will say "Unable to check for updates, retry or reboot the stick"
Press and hold the BACK and MENU buttons simultaneously on the remote for a few seconds, until the VoiceView accessibility feature turns on. Then, once the VoiceView feature is on the screen, press the BACK button on the remote to exit VoiceView.
Now it will ask for an account, log-in.
Note: If you connect to another network later then you won't be protected. Sideloading and configuring an app like DNS66 or AdAway after initial setup will enable you to continue blocking the sites on your device. Good luck!

Categories

Resources