Brand New Firestick, I blocked the first update and it wont start, since at soon It connect it want to update and of Course failed telling me to contact customer support and consequently cannot access the menu - settings - system – developer, in order to load kingroot
I blocked the update with open DNS
1. amzdigital-a.akamaihd.net
2. amzdigitaldownloads.edgesuite.net
3. softwareupdates.amazon.com
4. updates.amazon.com
http://www.aftvnews.com/how-to-block-software-updates-on-the-amazon-fire-tv-or-fire-tv-stick/?
is there a way to start and prevent update at least up to 5.05 and root?
guliver365 said:
Brand New Firestick, I blocked the first update and it wont start, since at soon It connect it want to update and of Course failed telling me to contact customer support and consequently cannot access the menu - settings - system – developer, in order to load kingroot
I blocked the update with open DNS
1. amzdigital-a.akamaihd.net
2. amzdigitaldownloads.edgesuite.net
3. softwareupdates.amazon.com
4. updates.amazon.com
http://www.aftvnews.com/how-to-block-software-updates-on-the-amazon-fire-tv-or-fire-tv-stick/?
is there a way to start and prevent update at least up to 5.05 and root?
Click to expand...
Click to collapse
Follow these instructions to get through the initial setup without updating:
http://www.aftvnews.com/how-to-complete-the-fire-tv-initial-setup-without-updating/
Then you can briefly unblock updates just long enough to see which one it's going to try to download. If it's 5.0.5 (537174420) then let it through, but if it's 5.0.5.1 (537175520) kill the power. There's no way to force it to take 5.0.5 if it tries to download 5.0.5.1. If it tries to download 5.0.5.1, all you can do is hope that rbox is able to release TWRP for the Stick and hope he releases a 5.0.5 ROM.
I am in it system 5.0.5 (537174420) but not sure why the 5.0.5.1 (537175520 has been downloaded but not installed yet waiting for the stick to be not in use, so I need a step by step to delete the download file in the cache before It got installed!
guliver365 said:
I am in it system 5.0.5 (537174420) but not sure why the 5.0.5.1 (537175520 has been downloaded but not installed yet waiting for the stick to be not in use, so I need a step by step to delete the download file in the cache before It got installed!
Click to expand...
Click to collapse
http://www.aftvnews.com/how-to-stop...rom-installing-on-a-fire-tv-or-fire-tv-stick/
AFTVnews.com said:
Follow these instructions to get through the initial setup without updating:
http://www.aftvnews.com/how-to-complete-the-fire-tv-initial-setup-without-updating/
Then you can briefly unblock updates just long enough to see which one it's going to try to download. If it's 5.0.5 (537174420) then let it through, but if it's 5.0.5.1 (537175520) kill the power. There's no way to force it to take 5.0.5 if it tries to download 5.0.5.1. If it tries to download 5.0.5.1, all you can do is hope that rbox is able to release TWRP for the Stick and hope he releases a 5.0.5 ROM.
Click to expand...
Click to collapse
that guide and video are ancient, have you ever even attempted this specifically on a fire tv stick anytime in the past 2 years or even remotly recently? the video is from 2014 , i think it needs to be updated because it does not work at all any more
my fire TV stick says manufactured in mid march 2016 according to the serial #
also in the wifi password menu screen the cancel, advanced ,connect buttons are at the bottom not at the top like in the video
the guide doesn't work , the fire tv stick will not go past the error screen and get to the registration screen, there is no way to get to the registration screen using that guide
i do everything the guide says exactly, when it says connection successful i pull the ethernet cable from the back of my router going to my modem and before it gets to the checking for updates screen
then it just hangs at checking for updates for like an hour and finally goes back to the error message screen, i hit the back button like you said,i re enter the wifi information like you said and hit connect again , pull the cable once it says connection successful and before checking for updates
same thing happens every time, one giant loop
hangs at checking for updates, goes to error screen ,hit back , re enter wifi settings ,hit connect, pull cable at connection successful ,hangs at checking for updates , goes back to error screen ,hit back, infinity
your guide is old and doesn't work any more
obviously it has not been tested anytime recently and they changed something hardware of software wise in the mean time
your guide says it was "updated" but what does that even mean? yeah you update your guides but do you actually retest them with new hardware for all 3 products 1 ,2 and stick?, i highly doubt it
i highly doubt that this guide was ever re tested recently with a fire stick ,one manufactured recently with a new fw like the one before the latest or whatever fw they were shipping with in mid march
go take a ride down to best buy and pick up a new fire stick and retest it then return it see if it still works, check the SN to see if it's made in 2016 ,i bet it won't work
The way I did it :
you cannot register the stick without the update downloading, at this point you are still in 5.05 make sure you do not restart the device I was not able to find the bin file with ES so I put King root in there with adbfire succeed to root it although it start to say fail but before I start the rooting again it says root so from this I used the regular adb guide from http://www.aftvnews.com/how-to-block-software-updates-on-the-amazon-fire-tv-or-fire-tv-stick/#root method 1 even after restart still at 5.05. I checked system update it give me error not still blocked by the open Dns I do not dare to remove it yet, firestarter is installing Kodi so I guess I am in business the only minor problem with fire starter the regular amazon home menu is truncated 3/4 of the screen maybe because of 4k TV and I do not have this issue with the rest of the links like your videos tv shows etc !
Related
Hi,
There is a patch on Acer support site for wifi problems since 3.1 update.
Here's the link for anyone not able to see it on the support site.
http://global-download.acer.com/GDF...AB&Step3=A500&OS=a07&LC=en&BC=Acer&SC=EMEA_27
http://global-download.acer.com/GDF... TAB&Step3=A500&OS=a07&LC=en&BC=Acer&SC=AAP_7
How do you install that?
Thank you for this
Here is the official instructions straight from the PDF file in the patch:
"Acer ICONIA TAB A500 ‘connect Wi-Fi unsuccessfully’ patch notification
To check the version of the operating system (OS) on your tablet:
Please go to Settings > About tablet > Build number.
Supported OS version(s): Please refer to the information below to verify if your
A500 is affected by the ‘connect Wi-Fi unsuccessfully’ issue.
Affected countries and OS
A. Countries: UK/France/Italy/Spain
- Affected OS versions:
Acer_A500_4.010.22_COM_GEN1
Acer_A500_4.010.30_COM_GEN1
- After installing the update, you are advised to update your tablet’s operating system to:
Acer_A500_4.010.38_COM_GEN1
B. Country: USA
- Affected OS versions:
Acer_A500_4.010.07_COM_GEN2
Acer_A500_4.010.08_COM_GEN2
Acer_A500_4.010.09_COM_GEN2
- After installing the update, you are advised to update your tablet’s operating system to:
Acer_A500_4.010.10_COM_GEN2
C. Countries: Singapore/Malaysia/Thailand/Philippines/India/Vietnam/
Indonesia/Australia/New Zealand
- Affected OS versions:
Acer_A500_4.010.12_COM_GEN1
Acer_A500_4.010.24_COM_GEN1
- After installing the update, you are advised update your tablet’s operating system to:
Acer_A500_4.010.40_COM_GEN1
Acer ICONIA TAB A500 ‘connect Wi-Fi unsuccessfully’ patch notification
D. Countries: Taiwan/Hong Kong
- Affected OS version:
Acer_A500_4.010.23_COM_GEN1
- After installing the update, you are advised to update your tablet’s operating system to:
Acer_A500_4.010.39_COM_GEN1
Installing the patch:
• Preparation
- Prepare a microSD card using FAT or FAT32 format
- Copy ‘update.zip’ to the root of the microSD card
- Ensure the tablet’s battery is fully charged
• Steps
1. Turn off the device (press and hold the power key)
2. Insert the microSD card in the tablet’s microSD slot
3. Press and hold the power button and volume down key (the volume key nearest
the power button)
4. After the tablet vibrates ONCE, keep holding the keys.
5. Wait until you see "Erasing caches before SD update..." in the top left-hand side of
the screen.
6. Release the power and volume keys.
7. Device shows the Android Robot and a progress bar.
8. Wait until the progress bar reaches 100% then restart the tablet.
9. Wait until the update process finishes.
10. Turn off Wi-Fi and turn it on again to complete the patch installation process."
personally i found it easier to statically assign the IP configuration information for the 2 networks I use, plus my version wasn't listed for the patch anyway. I also renamed the files in /data/misc/dhcp/ to correct the issue where stuck on assigning IP address in wireless connection (where it basically repeatedly attempts to get an IP address)
*edit*
Here you go BatPenguin. This is the PDF file that comes with the zip for how to properly install the patch
***EDIT***
I was beat to it lol.
bmathison said:
Here is the official instructions straight from the PDF file in the patch
personally i found it easier to statically assign the IP configuration information for the 2 networks I use, plus my version wasn't listed for the patch anyway. I also renamed the files in /data/misc/dhcp/ to correct the issue where stuck on assigning IP address in wireless connection (where it basically repeatedly attempts to get an IP address)
Click to expand...
Click to collapse
Omg I'm an idiot. I didn't even see that my version isn't even listed -_-
So thenfact I installed it shouldn't mess my tab up right? Ugh such an idiot.
*edit* I just uninstalled the patch lol. No sense in keeping it if its not for my device anyway. I keep forgetting my tab is not my computer and downloads, zips, etc should be done there first.
........................................
I got the 3.1 OTA update today. Could not connect to WiFi after installation. Did the paperclip reset routine a few times but no luck.
Considered installing this patch but noticed it was not for my build and had second thoughts. But I installed it anyway and after a reboot, my WiFi was working again.
I'm guessing that Acer's list of supported builds is not all-inclusive. If your Wifi stopped working after the HC 3.1 update try using the patch posted above.
Well, I'm in the boat as many of you. The download came in at just after midnight local and after 90% of the install messed up the wifi. I downloaded the patch and tried to install it multiple times with no change in the ability to connect. The tab will see all the networks in my area but it gets into a loop cycle trying to connect and after a minute or so will disable the wifi. I even went so far as to go through the factory reset process and install the patch afterwards with no luck.
At this point it's nothing more than a fancy color reader. Is there a way to re-flash the entire OS with the original Acer version? I have been rooted but don't have a desire to flash any custom ROMs yet. If this is not possible it'll have to go back to Acer and who knows how long that will take....just in time for my trip next month.
Just to err on the safe side it is a US tablet living the Middle East, not that it should matter.
There are plenty of stock ROM's in the dev section you can flash with. Their threads are clearly labelled as such.
Well, I went through the level 1 gauntlet at Acer and they have passed me off to a level 2. I don't have high expectations but it will be a PITA to call considering my hours and my location.
"Australia/New Zealand
- Affected OS versions:
Acer_A500_4.010.12_COM_GEN1
Acer_A500_4.010.24_COM_GEN1
- After installing the update, you are advised update your tablet’s operating system to:
Acer_A500_4.010.40_COM_GEN1"
I already have the update "Acer_A500_4.010.40_COM_GEN1" showing for download.
Does this one include the wifi fix?
(I have no interest in updating from 3.01 to 3.1 becasue of the wifi problem, so if it's not fixed, I'll stay as I am.)
Yes, it does.
Thanks for that - I might let it update now..
ibcrusn said:
Well, I'm in the boat as many of you. The download came in at just after midnight local and after 90% of the install messed up the wifi. I downloaded the patch and tried to install it multiple times with no change in the ability to connect. The tab will see all the networks in my area but it gets into a loop cycle trying to connect and after a minute or so will disable the wifi. I even went so far as to go through the factory reset process and install the patch afterwards with no luck.
At this point it's nothing more than a fancy color reader. Is there a way to re-flash the entire OS with the original Acer version? I have been rooted but don't have a desire to flash any custom ROMs yet. If this is not possible it'll have to go back to Acer and who knows how long that will take....just in time for my trip next month.
Just to err on the safe side it is a US tablet living the Middle East, not that it should matter.
Click to expand...
Click to collapse
fist of all this is not the problem that's supposed to be fixed by the patch. your problem is more simple, check or reenter the wifi password. because it is normal for wifi connection to be removed if it cannot connect to it because of the luck of the password. also make sure your router is supporting wpa/tsk or wpa2/tsk.
because i think that has changed since 3.01 wich also supported WEP, which might not be the case anymore.
the problem people have is that the dhcp is not working after the password is entered. i.e. it dispalys waiting for IP, and never gets it, but it does not remove any networks from the list.
I've been down that path and reentered the password at least a half a dozen times. Up until the most recent update that was pushed was 90% installed and then stalled out out I have had no issues on this network or others.
Your second statement more closely matches the issue that I'm having.
Not happy with Acer. Those of us who use this forum may be able to apply patches to correct problems caused by their upgrades, but think how many people have lost all connectivity when they applied the 3.1 update.
How is it possible that Acer, which has been working on update issues for a month or more, pushes an update that takes out our wireless connection? And why do the users have to assume the burden of solving the problem, locating the patch and applying it?
Doesn't the company test their upgrade before pushing it out? Were they not aware of the havoc it caused?
I like my tablet a lot, but the Acer customer experience is frustrating and hard to understand.
I was able to speak with Karen a level 2 tech rep and we went through a few easy steps and it seems ot have fixed my issue.
begin with the tablet turned off
- press and hold the volume up button (I assume it must be in landscape because she stated it was the button closest the rotation lock)
- press and hold the power button until the light comes on, continue holding the volume button
- as soon as the tablet vibrates begin flipping the rotation lock back and forth as quickly as you can until you see small words in the upper left corner. I had to do this twice because I didn't flip it fast enough.
- once the words appear (erasing cache and such) you can stop switching the rotation lock and let off the volume button.
- It will do its thing and reboot to the original home screen
I had already tried a factory reset but she made it sound as though this would completely reset the tablet and wipe everything. At any rate it seems to have worked. I'm going to try and re-download 4.010.10, root it, re-install Titanium Pro and re-install all my apps and I'm back in business
Give it a try and see if it works.
Hi sorry running into some problem once again
Device is not rooted, trying to update it seem
keep downloading the 387mb and give me "invalid update "the system update is invalid and has been canceled.
the cycle repeat itself, getting pretty annoying.
Model number A500
android version 3.0.1
Knerl version 26.36.3
build number: Acer_A500_1.139.05_COM_GEN1
Country:Ontario, Canada
trying to system update 4.010.38
I am not technical at all, don't want to root nor manual update.
Also i keep getting lock up whenever after i wall charged, once i use the open power to pop the screen up, the multi-touch fail to respond i can't unlock the screen until i force reset but it will rotate as normal.
Is it me or this thing is already broken ?
Thanks.
i had the same problem with mine, same build number, same update. I had to do a factory data reset and then it worked prefectly
I had the same problem tonight.
Fixing the "Invalid Update" Problem .......
I recently had exactly this problem when the 3.2 OTA upgrade was released. After two failed attempts at downloading and installing the 3.2 update, I gave in and contacted Acer Telephone Support. The support person kindly emailed me the following instructions. My A500 was using a standard 3.1 ROm, but had been rooted. I did not need to un-root it to install the 3.2 OTA update - however, I did of course loose root access after the upgrade.
Invalid Update Problem solved !!!!
Dear Customer,
Please try to download the update again after performing the following:
1. Please go to Settings > Application > Development > enable Stay Awake.
2. Please go to Settings > Screen > Timeout > set the value to 30 Minutes.
3. Plug in your charger.
4. Proceed to download the update either via restarting the tablet or check System Update under About Tablet.
Please also ensure the tablet has more than enough power and good wifi signal strength during the updating process.
This should enable you to download and install the patch as normal.
If you are still unable to install the update after the steps above, please provide all the following details so I can assist you further
1. The SNID of the tablet.
2. The build number of the tablet(you can find this in the About Tablet Section)
3. The size of the update file.
Thank you for your cooperation in this matter, I look forward to your reply.
Best regards,
First Level Technical Support
Acer Computer Australia
8 Baywater Drive
Wentworth Point NSW 2127
Telephone: 1300 365 100
Fax: (02) 8762 3730
Thanks for the information. I was able to get my A500 updated by following the instructions above.
Sent from my A500 using xda premium
Thank you for sharing this! I had the same problem with updates, but following these instructions I updated my honeycomb 3.0 Iconia tab a500 to Honeycomb 3.2.1
In order to update to ICS, you need to install an updater app from official Acer website. Then simply run update check and you will see your ICS update.
Downloading right now, hope everything will work fine
People don't seem to realise, you need to have the acer tab attached to the wall charger or it won't do the OTA updates...
I bet the few who have the updates fail and brick their device have had them plugged in and disconnect them part way through the flash...
Not sure why Acer requires the power plugged in as the tabs aren't(or so I've been told) actually charging...
Just a quirk of Acer perhaps...
Root MethodAmazon has just released a new firmware update, blocking the fastboot commands necessary for root/custom ROMs (fastboot boot). We need more information about this update. If people could update their tablet to this latest version without getting it stuck in the botloop, we could see the information regarding the update and get root out for this ROM ASAP. Thanks to anyone who sacrifices root/ROMs for development.
List of things you can't do:
Downgrade to an earlier release
Boot a .img from Fastboot
List of things you can do:
Install and use the Google Play Framework and Services
Root
Install Custom ROMS via FlashFire
Remove Lockscreen Ads
Remove Amazon Bloatware
Feel free to comments things that worked/didn't work on your device.
ANYONE WHO IS ON 5.0.x AND WANTS TO GO TO 5.1.1 WITHOUT ANY COMPLICATIONS AND KEEPING TWRP, GO TO THIS LINK: http://forum.xda-developers.com/showthread.php?t=3265594
Can anyone test if the Google Framework Install tutorial works on this update?
It does.
However, DON'T TRY TO DOWNGRADE BACK TO THE 5.0.1 FIRMWARE. IT WILL BRICK YOUR DEVICE. I found that out the hard way. It's stuck in a preloader reboot-loop.
Added list of what you are able to do on the update.
Can someone with a brand new Fire & an open wifi network within range, confirm that it will not automatically connect to wifi? I would appreciate it greatly.
Yes, I do believe that you should have to agree to connect to wifi. And that's what I vaguely recall from my Fire. But I'd like to be 100% sure. Don't want to take the slightest chance. My friend has a new fire in the box & has an open wifi network within range of their place.
blueberry.sky said:
Can someone with a brand new Fire & an open wifi network within range, confirm that it will not automatically connect to wifi? I would appreciate it greatly.
Yes, I do believe that you should have to agree to connect to wifi. And that's what I vaguely recall from my Fire. But I'd like to be 100% sure. Don't want to take the slightest chance. My friend has a new fire in the box & has an open wifi network within range of their place.
Click to expand...
Click to collapse
You have to go through the setup, but originally I just skipped that part, even though I was next to a Starbucks, and it didn't connect.
Doesn't Starbucks wifi require you to click to agree to their terms of use before you can freely browse or download? So Internet would not actually be available initially to the update script.
Pretty much, I trust amazon on this issue, as far as I can throw them. I don't want to presume that a OTA proccess won't silently connect, while the Fire otherwise appears to be waiting for the ok to connect to wifi.
Bloat removal
Hi just to add this thread it looks like you cannot remove any of the bloat as I was able to do on 5.01
craigs23 said:
Hi just to add this thread it looks like you cannot remove any of the bloat as I was able to do on 5.01
Click to expand...
Click to collapse
Thanks, added.
This is bullsh!t. the ENTIRE reason about 5,000 people bought this tab last week is because of root, fastboot and CM. If I get my tab soon I can offer any assistance you need. I'm not sure if it will be possible to dump any part of the system, boot, etc. without fastboot or twrp, but I'm sure we could figure something out.
blueberry.sky said:
Can someone with a brand new Fire & an open wifi network within range, confirm that it will not automatically connect to wifi? I would appreciate it greatly.
Yes, I do believe that you should have to agree to connect to wifi. And that's what I vaguely recall from my Fire. But I'd like to be 100% sure. Don't want to take the slightest chance. My friend has a new fire in the box & has an open wifi network within range of their place.
Click to expand...
Click to collapse
When I setup mine it asked to turn on wifi I skipped it and said later.
Sent from my SM-N910T3 using Tapatalk
Has anyone tried kingroot on 5.1.1?
Experts please take a look at this
What was changed in OS 5.1.1?
If anyone can get the frimware update or capture it id like to test it out
running 5.1.1 & all I could manage to load was Google Account manager. The rest (Framework Services, etc) says something like "App not installed" & nothing else, every time I try.
scratch that..... found found a couple that did load for me.
Damn! I did this (tried to downgrade, got bricked) a day before you posted this. I should probably replace mine...
My unrooted Fire upgraded to 5.1.1 last night before I had any idea it was coming. I'm willing to try whatever is needed to assist with further research if I could be of any help.
unlikely it would work, but did anyone on 5.1.1 try
Code:
fastboot -i 0x1949 boot twrpfilename
Sent from my KFFOWI using Tapatalk
5.1.1 update file
Here is the 5.1.1 update file
snap42.com/update-kindle-full_ford-37.5.4.1_user_541112720.bin.zip
Root Fire 7"- 5th Gen-2015 FireOS 5.1.3, 5.1.4 (New Shipments Summer, Fall 2016)
I bought my Fire 7" shortly after it came out. Not too many weeks went by and folks had posted instructions to get rid of the ads, load Google Play Store, get rid of Amazon's horrible home screen(s) (a.k.a Launcher) and a month or so later how to root it.
A friend of mine just ordered one on my recommendation. And boy have things changed! It would appear that as folks came up with ways to do the things mentioned above, Amazon simply issues OS updates to stop them. Everything I am about to write about is, I'm sure, found somewhere else here on XDA. My intent is to save you the time it took me to figure this out this past afternoon.
FIRST - DON'T LET YOUR NEW FIRE TABLET UPDATE! What I'm going to explain applies to FireOS 5.1.3, 5.1.4 (and 5.1.2.1)
Right now today, early Oct 2016, it appears that there isn't a root tool for FireOS numbered above 5.1.2. But you easily downgrade the ones shipping today (FireOS 5.1.3, 5.1.4 and 5.1.2.1) to FireOS 5.1.2. And then existing tools work.
You'll need to download and extract:
AmazonFire5thGenSuperTool.zip
Firmware-Downgrade-to-Fire-OS-5.1.2-Supertool.zip
Steps:
Run the Firmware-Downgrade-Supertool, you don't need to start adb or anything first, just double-click the "1-Start-Firmware-Downgrade-to-5.1.2.bat"
NOTE1: You'll need to allow unknown sources (In the Security Settings) and allow adb (In Developer Options. You add Developer Options by tapping Serial Number 7 times (In Device Options) see Developer Options
NOTE2: Watch the Fire Screen closely. There will be multiple popup screens/boxes. You'll need to approve adb several times. Just tap "OK"
NOTE3: When I ran it the text in the Windows cmd.exe box said it failed. But wait and a menu will appear on the fire's screen. Use the volume keys to select the 2nd item listed "from ADB" and the on/off/power button to select it. Go back to the Windows cmd.exe box and hit any key. Then the bin file for the downgrade will start transfering
When it completes, run the AmazonFire5thGenSupertool. It has a menu that will let you do everything I listed in my opening paragraph
In the AmazonFire5thGenSupertool menu pay attention to those selections that require root first. In FireOS 5.1.2 it will intall a rooting app. PAY ATTENTION to the NOTE in the cmd.exe screen that says if it fails to root you may need to shut the Fire all the way down and run tha app again. For me it was running it again after a full shutdown that completed the root.
You've just spent a good amount of time downgrading to 5.1.2 so you could get rid of the Amazon crud. IT SHOULD GO WITHOUT SAYING, but I'll say it anyway. In the AmazonFire5thGenSupertool be sure to shut off updates!
MANY, MANY THANKS to RootJunky for the tools!!!
I used this method, but when you restart the tablet does not appear among the options to update the firmware, it appears only option (I forget the name) and select not let.
Got myself a Fire tablet 16gb, which came with ver 5.1.3 and auto updated to 5.1.4 (which i didn't want it to), used this guide and followed the steps. Kingroot took maybe 6-7 tries, but it finally worked. Achieved root, got rid of of lockscreen ads, uninstalled FireOS launcher, and installed nova launcher. Now it feels like stock android (also got playstore) while keeping the FireOS features (useful for my 2 yr old son who loves the shows on the Amazon firestick). Win-Win. Thank you OP
mstrakt said:
Got myself a Fire tablet 16gb, which came with ver 5.1.3 and auto updated to 5.1.4 (which i didn't want it to), used this guide and followed the steps. Kingroot took maybe 6-7 tries, but it finally worked. Achieved root, got rid of of lockscreen ads, uninstalled FireOS launcher, and installed nova launcher. Now it feels like stock android (also got playstore) while keeping the FireOS features (useful for my 2 yr old son who loves the shows on the Amazon firestick). Win-Win. Thank you OP
Click to expand...
Click to collapse
Don't forget to disable OTA updates. If you used an automated method make sure system\priv-app\DeviceSoftwareOTA.apk got renamed.
Davey126 said:
Don't forget to disable OTA updates. If you used an automated method make sure system\priv-app\DeviceSoftwareOTA.apk got renamed.
Click to expand...
Click to collapse
Yup did that too. It hasn't bugged me to update since, so I'm guessing it worked! Thanks.
mstrakt said:
Got myself a Fire tablet 16gb, which came with ver 5.1.3 and auto updated to 5.1.4 (which i didn't want it to), used this guide and followed the steps. Kingroot took maybe 6-7 tries, but it finally worked. Achieved root, got rid of of lockscreen ads, uninstalled FireOS launcher, and installed nova launcher. Now it feels like stock android (also got playstore) while keeping the FireOS features (useful for my 2 yr old son who loves the shows on the Amazon firestick). Win-Win. Thank you OP
Click to expand...
Click to collapse
I had rooted my kindle out of the box and turned off auto updates. However overnight it updated..... I am having a heck of a time getting access to the kindle again even after authorizing USB debugging. I have tried the downgrade supertool, I've tried command window method, the main supertool and everything else I can think of.
When I get to the point to load the firmware via adb sideload <filename> it says it cannot find the device. I have authorized debugging and allowed unknown source app downloading.
Please tell me how you were able to get back out of 5.1.4. Thank you in advance.
Dano
So ... received a 5.1.3 device (5th gen, with special offers) yesterday. Successfully downgraded to 5.1.2 using the method on this thread. Before even connecting to Wifi - downgraded straight out of the box.
However, the kingroot method from this thread just fails (using 4.9.2 apk version) with the supertool method. Tried several times, even reflashing 5.1.2. gets stuck at Verify Root Status (left it there for several hours).
Decided to manually install kingroot 3.5 to PC (from XDA thread). That fails too. Says Failed to Root. Root request recieved. KFFOWI Android 5.1.1.
So now, I got a 5.1.2 device that cannot be rooted using the methods at my disposal.
Hope something comes up soon.
siftekhar said:
So ... received a 5.1.3 device (5th gen, with special offers) yesterday. Successfully downgraded to 5.1.2 using the method on this thread. Before even connecting to Wifi - downgraded straight out of the box.
However, the kingroot method from this thread just fails (using 4.9.2 apk version) with the supertool method. Tried several times, even reflashing 5.1.2. gets stuck at Verify Root Status (left it there for several hours).
Decided to manually install kingroot 3.5 to PC (from XDA thread). That fails too. Says Failed to Root. Root request recieved. KFFOWI Android 5.1.1.
So now, I got a 5.1.2 device that cannot be rooted using the methods at my disposal.
Hope something comes up soon.
Click to expand...
Click to collapse
Keep trying; KingRoot can be stubborn as countless others before you have learned. Try a factory reset; don't register device w/Amazon on restart. WiFi must be enabled during first 30-60 sec of KingRoot run; otherwise failure is certain.
---------- Post added at 04:09 PM ---------- Previous post was at 04:07 PM ----------
AkDano said:
I had rooted my kindle out of the box and turned off auto updates. However overnight it updated..... I am having a heck of a time getting access to the kindle again even after authorizing USB debugging. I have tried the downgrade supertool, I've tried command window method, the main supertool and everything else I can think of.
When I get to the point to load the firmware via adb sideload <filename> it says it cannot find the device. I have authorized debugging and allowed unknown source app downloading.
Please tell me how you were able to get back out of 5.1.4. Thank you in advance.
Dano
Click to expand...
Click to collapse
Updated to what? KingRoot is now capable of rooting all builds of FireOS 5.1.x. No downgrade needed if on 5.1.4.
Hey! This is my first time here, sorry if I'm doing smth wrong, I just really need help. My fossil gen 6 is kinda useless at this point after updating to Wear OS 3 and I would like to flash it back to Wear OS 2, since I don't get any notifications & I can't even sync my notes at this point without connecting to wifi (not even through mobile data, which is pretty annoying -> my phone & watch doesn't connect to each other through bluetooth)
thanks, for any guides in advance!
night
You will have to perform a factory reset and repair the watch and phone again. Only option at the moment.
edwin270 said:
You will have to perform a factory reset and repair the watch and phone again. Only option at the moment.
Click to expand...
Click to collapse
Did that 3 times already, nothing changed. Thanks for your answer though!
Did you get anywhere with this? I also want to go back to wear os 2. I hate the fossil app
I'd like to know too. I just came back to Android with the S23 Ultra and wanted to pair my Razer x Fossil watch to it. But I decided to update since I was doing a factory reset/disconnect anyways. Big big BIG mistake.
There has to be a way to flash wear OS 2.3 back to the watch and re partition it as stock. I'm able to see my watch as a USB perhp on my machine without BT or wifi connection.
Anyone have the old firmware for these watches? Short of buying another Razer watch for $600
I do have all the required files to go back to wearOS 2, but wont suggest it might brick your device. Have a partition backup first.
For OTA add the hash in the placeholder.
Main URL: https://redirector.gvt1.com/packages/data/ota-api/package/<hash_with_extension_here>
v2.30: 230d380c72f87f94cbd4e43b944afd70700d6ffd.zip (Apply updates from playstore regarding wearOS to get it upto 2.38)
Minor Update: 4e201fee66e76ed4694e77eaa589f7767f93beea needs to applied after flashing the above package.
V3: a569fe07dfdcb4edea85f9535d592b9af4621cd1.zip
Malvik said:
I do have all the required files to go back to wearOS 2, but wont suggest it might brick your device. Have a partition backup first.
For OTA add the hash in the placeholder.
Main URL: https://redirector.gvt1.com/packages/data/ota-api/package/<hash_with_extension_here>
v2.30: 230d380c72f87f94cbd4e43b944afd70700d6ffd.zip (Apply updates from playstore regarding wearOS to get it upto 2.38)
Minor Update: 4e201fee66e76ed4694e77eaa589f7767f93beea needs to applied after flashing the above package.
V3: a569fe07dfdcb4edea85f9535d592b9af4621cd1.zip
Click to expand...
Click to collapse
Hey ! Thanks for the file. I'll take the risk to brick my watch.
Do you know how I can flash the archive ?
MiamKebab said:
Hey ! Thanks for the file. I'll take the risk to brick my watch.
Do you know how I can flash the archive ?
Click to expand...
Click to collapse
I'm also looking to be able to flash my watch between WearOS 2 and 3. Have you figured anything out by chance? All the things I normally do aren't working, with and without TWRP.
Malvik said:
I do have all the required files to go back to wearOS 2, but wont suggest it might brick your device. Have a partition backup first.
For OTA add the hash in the placeholder.
Main URL: https://redirector.gvt1.com/packages/data/ota-api/package/<hash_with_extension_here>
v2.30: 230d380c72f87f94cbd4e43b944afd70700d6ffd.zip (Apply updates from playstore regarding wearOS to get it upto 2.38)
Minor Update: 4e201fee66e76ed4694e77eaa589f7767f93beea needs to applied after flashing the above package.
V3: a569fe07dfdcb4edea85f9535d592b9af4621cd1.zip
Click to expand...
Click to collapse
Or would you be able to provide some guidance on how to proceed?
Arkbird1000 said:
I'm also looking to be able to flash my watch between WearOS 2 and 3. Have you figured anything out by chance? All the things I normally do aren't working, with and without TWRP.
Click to expand...
Click to collapse
From what I found, the original cable with 4 spins (2 on each side) should be used to connect your watch to a PC and use the USB debugging.
So I bought one but nothing happened. I'm just able to use Bluetooth or WiFi debugging and these can't be used to unlock the bootloader as WiFi and Bluetooth are disabled on bootloader mode. So fastboot can't detect the watch.
So I'm stuck and that sucks, my duck.
Another way is to remove the watch's back and tweak the USB connectors but I'll not do that...
MiamKebab said:
From what I found, the original cable with 4 spins (2 on each side) should be used to connect your watch to a PC and use the USB debugging.
So I bought one but nothing happened. I'm just able to use Bluetooth or WiFi debugging and these can't be used to unlock the bootloader as WiFi and Bluetooth are disabled on bootloader mode. So fastboot can't detect the watch.
So I'm stuck and that sucks, my duck.
Another way is to remove the watch's back and tweak the USB connectors but I'll not do that...
Click to expand...
Click to collapse
I see. I have been able to make it farther, but I also was running into problems getting the USB connection to work. Most of what I did was under Linux instead of Windows but I found that after enabling USB debugging I often had to remove the watch from the cradle, put it back on, then run 'adb devices' from the connected computer to get the daemon going. That usually got the adb popup on the watch to show, then I can select the 'always allow' option.
All that said, at the moment I'm not currently able to boot my watch unless I have the bootloader unlocked. I have restored the stock recovery after using TWRP and unsuccessfully flashing anything via that adb shell or from the bootloader with fastboot. Even worse, some things are not working properly, such as automatic brightness and some of the wireless capabilities. I might need to see if I can work something out with Fossil if I'm unable to resolve these issues.
You guys seems way ahead on me in the downgrade process...
I made Wear OS 3 update but the Fossil app used to pair the watch won't work with Oneplus 8 Pro (Android 13), gotta go back but i have no idea how...
Yet i flashed a lot of custom roms and stuff in the past, but now.. kinda lost
Im looking forward to see news here
Good luck guys, i'll keep updated if i somehow manage to flash the OTA posted ahead
Edit : well i was on Apkmirror to try an older apk of the app, and found out their app targets android 12 but not android 13..........
Arkbird1000 said:
I see. I have been able to make it farther, but I also was running into problems getting the USB connection to work. Most of what I did was under Linux instead of Windows but I found that after enabling USB debugging I often had to remove the watch from the cradle, put it back on, then run 'adb devices' from the connected computer to get the daemon going. That usually got the adb popup on the watch to show, then I can select the 'always allow' option.
All that said, at the moment I'm not currently able to boot my watch unless I have the bootloader unlocked. I have restored the stock recovery after using TWRP and unsuccessfully flashing anything via that adb shell or from the bootloader with fastboot. Even worse, some things are not working properly, such as automatic brightness and some of the wireless capabilities. I might need to see if I can work something out with Fossil if I'm unable to resolve these issues.
Click to expand...
Click to collapse
I do have the TWRP but need to find it, took some tweaks from Ticwatch 3 pro. I didnt pushed it on the repo tho. I didnt what made me do it, but I wiped my system partitions and had to rebuilt from the OTA only. But after getting the watch working again, I had few functionalities broke, including the OTA updates. If you can social enginner your way thru fossil to get files such as stock rom and other files for qualcomm software like rawprogrammer and firehose files it can be great help.