Related
Hello All
First post here.
I bought a refurbished TF101 with dock from the Netherlands a week ago and updated to WW 8.6.5.7 OTA right after setting the device up. Then rooted it and used the ad hoc guide by qwer23 (thank you!) from this tutorial (via adb) in order to tether my Nokia N9 with the Joiku wifi hotspot app...
I got the notification yesterday that I could update to 8.6.5.9 OTA but after it checks firmware integrity and reboots, it shows an icon of the android robot with an exclamation mark after it tries to install the installation file.
I did a hard reset to the whole device, and again, OTA notification saying i could update and still shows the same error message when i press on install and it shuts the device down.
possible to get some help regarding this situation? any advice?
cheers
I've got the same problem.
I rooted 3.1 to get AdHoc tethering.
I got the 3.2 ww 8.6.5.7-20110730 OTA update and it installed without losing root or the modified wpasupplicant.
I just got the 8.6.5.9. notification, tried to update and got the android ! warning.
Rebooted/restarted and back to 8.6.5.7. but now no update available.
Can somebody point us to a restoration thread please?
Thanks
so far as I am aware this update wont work on rooted devices so you will have to un root to get it. There are a number of posts stating this on here.
v8code said:
so far as I am aware this update wont work on rooted devices so you will have to un root to get it. There are a number of posts stating this on here.
Click to expand...
Click to collapse
Yes, I know that, I'm perfectly capable of un-rooting.
As I pointed out, the previous 3.2 update installed while rooted, and I remained rooted, so I didn't suspect that this one might not.
There are also posts stating that the update won't show again once it's been downloaded once and the install has failed.
It's not on the Asus firmware downloads page.
So, once I've un-rooted, is the update still stored on the machine or do we have to wait for or find a ww zipfile somewhere?
cozzykim said:
So, once I've un-rooted, is the update still stored on the machine or do we have to wait for or find a ww zipfile somewhere?
Click to expand...
Click to collapse
As far as I know - since I'm in your same situation - there's nothing left to do but:
- bring the device back to stock;
- wait for the update to become available on Asus site, because we will not get any other notification for 8.6.5.9.
Well, this seems merely a question of time and also, some geeky dude out there could dump 8.6.5.9 stock ROM for easy Nvflash flashing
If you've downloaded the update and your TF101 is asking you to check notifications but you no longer have a update notification then you'll need to clear the DMClient cache in order to reactivate the update.
Check this this thread.
http://forum.xda-developers.com/archive/index.php/t-1106054.html
juscoll said:
If you've downloaded the update and your TF101 is asking you to check notifications but you no longer have a update notification then you'll need to clear the DMClient cache in order to reactivate the update.
Check this this thread.
http://forum.xda-developers.com/archive/index.php/t-1106054.html
Click to expand...
Click to collapse
Not my case, unfortunately. I received the FOTA notification, made the update process start and then something's gone wrong (green android with an exclamation mark). Now no more update notification is shown; actually searching for an update manually from the tablet returns a message saying that no update is available for my device.
KaylordTheuZ said:
Not my case, unfortunately. I received the FOTA notification, made the update process start and then something's gone wrong (green android with an exclamation mark). Now no more update notification is shown; actually searching for an update manually from the tablet returns a message saying that no update is available for my device.
Click to expand...
Click to collapse
Same here, I had already tried clearing the DMClient Data and Cache.
Somebody must have the downloaded WW file available in their cache, pretty please
i've unrooted my phone, did a full system reset and the update notification appeared. it was showing the android robot with the cogs working in its belly then again i got the exclamation error screen.
i looked at this thread: http://forum.xda-developers.com/showthread.php?t=1232810 where it says to check what the updater script checks for. have es explorer installed and it showed that the wpa supplicant and wpa supplicant.original is still in there. should i overwrite the wpa supplicant file with the original one? shouldn't this already happen when i do a full system reset?
aSIMULAtor said:
i've unrooted my phone, did a full system reset and the update notification appeared. it was showing the android robot with the cogs working in its belly then again i got the exclamation error screen.
i looked at this thread: http://forum.xda-developers.com/showthread.php?t=1232810 where it says to check what the updater script checks for. have es explorer installed and it showed that the wpa supplicant and wpa supplicant.original is still in there. should i overwrite the wpa supplicant file with the original one? shouldn't this already happen when i do a full system reset?
Click to expand...
Click to collapse
My answer is being based of your post and my assumptions.
I'm guessing that when you rooted, you changed other things after that were located in /system?
If so, then you didn't change it back when you unrooted.
All factory resetting does is make your tablet /look/ like it just came out the box. Users that aren't tech savvy do not modify /system files. So when they reset, it /looks/ like it's just out of the box.
In short, factory reset will clear your /data but it will not reset everything back to factory settings in /system.
You will need to re-root, replace the file with the original, then unroot again.
Just my thought process.
Hello
You are right
Yes it was the wpa supplicant file that i had replaced, i have the original (i think) which i copied over in the same directory...but, is there a way to download the original wpa supplicant file for 8.6.5.7 somewhere off the net just in case?
Going to try that now...
Also, just a question, if i download WW 8.6.5.7 from the ASUS website and install that would it completely overwrite and reset everything in /system?
aSIMULAtor said:
Hello
You are right
Yes it was the wpa supplicant file that i had replaced, i have the original (i think) which i copied over in the same directory...but, is there a way to download the original wpa supplicant file for 8.6.5.7 somewhere off the net just in case?
Going to try that now...
Also, just a question, if i download WW 8.6.5.7 from the ASUS website and install that would it completely overwrite and reset everything in /system?
Click to expand...
Click to collapse
This thread http://forum.xda-developers.com/showthread.php?t=1093778 has the original in the OP, just choose the 3.1 original.
aSIMULAtor said:
Hello
You are right
Yes it was the wpa supplicant file that i had replaced, i have the original (i think) which i copied over in the same directory...but, is there a way to download the original wpa supplicant file for 8.6.5.7 somewhere off the net just in case?
Going to try that now...
Also, just a question, if i download WW 8.6.5.7 from the ASUS website and install that would it completely overwrite and reset everything in /system?
Click to expand...
Click to collapse
You could just copy the file into your external sdcard.
I believe you could do that. Apparently the new update doesn't require that fix anymore.
I believe that is correct.
I just look at them as a complete update.zip where everything is included in /system.
alex5790 said:
This thread http://forum.xda-developers.com/showthread.php?t=1093778 has the original in the OP, just choose the 3.1 original.
Click to expand...
Click to collapse
I've done all this, exchanged the AdHoc wpa_supplicant for the original (which I kept on a removable microsd), unrooted, rebooted (though not factory reset) and manually searched for the update......nothing.
The wpa_supplicant was the only change I had made, to connect to my HD2 Wm6.5
So, I still need the update package, unless I really do need to hard reset?
cozzykim said:
I've done all this, exchanged the AdHoc wpa_supplicant for the original (which I kept on a removable microsd), unrooted, rebooted (though not factory reset) and manually searched for the update......nothing.
The wpa_supplicant was the only change I had made, to connect to my HD2 Wm6.5
So, I still need the update package, unless I really do need to hard reset?
Click to expand...
Click to collapse
From what I have seen during my research, it looks like you will need to flash the NVFlash, update to a offical firmware provided by Asus on their website, and THEN check if you can recieve the update.
I'm just hoping.
Thanks, that might be the way, I'll check it out
did the same thing as you...before my device notified me of the update, then it almost updated, but now i'm just not getting any notifications anymore.
will try what The Dark Lestat suggests and will report back when it's done.
aSIMULAtor said:
did the same thing as you...before my device notified me of the update, then it almost updated, but now i'm just not getting any notifications anymore.
will try what The Dark Lestat suggests and will report back when it's done.
Click to expand...
Click to collapse
please help, I will not reveal more.
I tried to wipe data and hard reset, but nothing.
balls!!!!!
well, updating to the 3.6.5.7 via the zip file worked...but, still not receiving any notifications of 3.6.5.9 update AT ALL.
I guess, have to wait till someone uploads the WW 3.6.5.9 zip file and will try to install it that way...
(i hope someone does this! )
i've the same problem here. update failed, wiped everything, installed stock hc3.2 but no update available anymore.
It's possible that ASUS blacklists pad's with modified system files? how coul this be done? with gmail account? with wifi mac address? or this sounds too stupid to be true.
Okay guys. I've searched and searched and found nothing, almost found something but wasn't definitive enough, and wasn't going to risk bricking my device.
Acer Iconia A500 Wifi Version
Current OS Version: HC 3.0.1
FLEX Version: 04_COM_GEN1
Kernel Version: 2.6.36.3
Build Number: ACER_A500_1.145.04_COM_GEN1
Now, notice I only bought this end of December-ish 2011 but this device has been out for quite some time. I don't know what is going on with Acer right now but this thing will not update through the system update no matter how many times I click on it. (tap on it you know what I mean)
Now, I wanted to do it manually, since I was able to do so on my Nexus S with ICS. But there are so many version out there and most of those forums say that if you don't use the correct region you'll brick your device.
Also, I searched my build number and only 1 person on 1 forum here on XDA Devs had the same build number and even then was only saying it to share. I cannot find anything regarding this build number, or what build to use to upgrade to 3.2.1, or all the way up to even if it takes multiple updates.
I know that Acer A500s are supposed to be getting ICS 4.0 sometime this month in Jan, but I'd like to be able to be updated to 3.2 at least while I'm here.
NOTE: I DO NOT WANT TO ROOT ANYTHING (That is not what she said)
Can someone take a look at my build number and current versions and what not, and please point me in a direction to get this thing upgrade to 3.2?
Thanks. A lot. In advanced. And stuff.
-B00mer
I'm actually facing the same problem too. Same build number, and no updates found. I checked Acer's website and say a document for updating to 3.2. The document mentions certain build numbers from different countries that are eligible for an update, and ours is not in the list. I wonder what Acer is up to?
Does it download the update?
mrtoken said:
Does it download the update?
Click to expand...
Click to collapse
It won't even see any of the updates. It just keeps saying "No Update: Your device is up to date."
Did a bit of googling for you
Someone had the same problem until they used the acer registration widget and waited a couple of days.
will keep looking
mrtoken said:
Did a bit of googling for you
Someone had the same problem until they used the acer registration widget and waited a couple of days.
will keep looking
Click to expand...
Click to collapse
Hey mate,
Thanks for doing that. However I've used that widget and registered when I got it and its been 2 weeks now. I guess I wasn't able to find that on google mostly because I've been looking under the assumption that because this is an android OS there would be a more technical way of updating the device. Lol.
Not giving up though.
b00mtastik said:
Hey mate,
Thanks for doing that. However I've used that widget and registered when I got it and its been 2 weeks now. I guess I wasn't able to find that on google mostly because I've been looking under the assumption that because this is an android OS there would be a more technical way of updating the device. Lol.
Not giving up though.
Click to expand...
Click to collapse
Some people are reporting that updates come in waves, I know the latest update is doing the rounds now so you might have to wait till that has finished and then you might get a catch up one.
I would just give acer nz a call and ask them
Try and get a date for ICS as well
mrtoken said:
Some people are reporting that updates come in waves, I know the latest update is doing the rounds now so you might have to wait till that has finished and then you might get a catch up one.
I would just give acer nz a call and ask them
Try and get a date for ICS as well
Click to expand...
Click to collapse
Would the update mean much to me since I am still on 3.0.1? I cant even get any of the other ones to even get to the latest update.
If I get a date for ICS, ill be sure to post it.
Just root it, then update. After that you can install a none rooted updated 3.2.1 stock rom
Hi b00mtastik,
I had the same problem with an iconia a couple of days ago. I tried different things and managed to fix it.
I'll try to give you step by step how to fix it (not sure if it will work for you).
I thought that the people from the shop i got the tablet played with it and put some custom rom and so i tried to get it to stock.
I used stuff from this thread.
1. You have to root your tablet - Click here
2. You have to install Clockwork Recovery.
- install from market "Acer Recovery"
- run it and give it root permission
- choose ClockworkMod Recovery rev1.3.4 by thor2002ro
- click Install Recovery Image
3. Download this. It is a backup made with clockworkmod. It will give you an android with version 1.139.02. In the zip is also a update.zip which will update your 1.139.02 to 1.139.05.
4. unzip it and put it on your external sd card (if you do not have one, find one, you need ~ 500 mb free)
5. put the files directly on sd card (e.g. update.zip goes to root, clockworkmod folder goes to root)
6. After that you have to boot in recovery.
- power device off
- keep VOL- button pressed and press and hold power button. Keep holding both button until you get to the menu.
7. Navigate using volume keys and enter a menu using the power button.
8. Navigate to backup/restore and then full backup and full restore (might be a little different). You choose full restore and navigate to restore a backup made on 25.06.
9. Wait until it is done.
10. Reboot and wait for the tablet to boot.
11. Open Acer Recovery and choose to install Stock USA recovery image. install.
12. Again you have to boot in recovery.
- power device off
- keep VOL- button pressed and press and hold power button. Keep holding both button until you see the update installing (An android robot).
13. After the update installs and the tablet boots check for updates.
This has worked for me. I did try other stuff but with no success.
I hope it was helpful for you and you can fix your device.
What you are most likely running into is ACER has not released an OTA for your region. What people are telling you might not be what you want. For example, if someone in the USA is telling you to flash or update, they are often referring to experiences that relate to the USA. NZ might have a different configuration, digital rights, contracts, language, etc etc that ACER just hasn't upgraded yet. Or might not ever upgrade.
If you are totally stock and have never rooted, then CALL ACER TECH SUPPORT and get the correct answer for you make and model for your country. If not, then following directions here might void your warranty. So, just give them a call and see what they tell you first. Then let us know what your find out.
TD
Of course you should first make sure there IS a higher version in your region. And rooting will void warranty.
Although as I spoke with Acer Support about the tablet mentioned in my post, they told me that 3.0.1 is the newest version, which is not true since I have two other a500 tablets both up to 3.2.
Just shared what did it for me.
Hope you can fix your problem the easy way.
Current for NZ is
3.2.1
Kernel version 2.6.36.3+
Build Acer_A500_7.014.15_Com_gen1
Is your current firmware stable? Is everything working OK?
New Zealand and Australia are typically the first countries to get the updates. But they are rolled out by google due to some number to do with your tablet. I'm in the south island and have had 3.2 for quite a while. When I brought my father an A500, it took about a week before the update was available for it. basically if you have any problems just go to the acer ANZ facebook fanpage, one of their acer people are always very good there with question. firmware is stable, and android 4 is meant to be released to NZ/Aussie shortly.
i forgot to mention before you get the big android updates there is a smaller update, i can't remember the size of it, but your tablet has to take that update before it will take the 3.1 or 3.2 update, cannot remember if you need 3.1 before 3.2
I know for a fact that NZ/AUS are supposed to be at 3.2 atleast, as I've seen some of the store A500's with 3.2 running. Also, Acer states NZ/AUS are supposed to be getting ICS 4.0 by the end of Jan.
I'm hoping this will be very soon. I'm thinking that they might have removed the updates from their servers for 3.1 and 3.2 and 3.2.1 and my tablet will just get a OTA for 4.0.
I'm hoping not to have to root anything, but I suppose that'll depend on my patience by the end of this month. Lol.
I should be able to update manually to 3.2 I know this much, but I can't seem to write to my SD Card which is why the manual updating via boot is not working, because it won't let me write to external_sd.
If someone can at least give me ideas on external_sd and write permissions for it WITHOUT rooting. Would be helpful.
Mean while I shall try and get a hold of support and see what they say.
-b00mer
b00mtastik said:
I know for a fact that NZ/AUS are supposed to be at 3.2 atleast, as I've seen some of the store A500's with 3.2 running. Also, Acer states NZ/AUS are supposed to be getting ICS 4.0 by the end of Jan.
I'm hoping this will be very soon. I'm thinking that they might have removed the updates from their servers for 3.1 and 3.2 and 3.2.1 and my tablet will just get a OTA for 4.0.
I'm hoping not to have to root anything, but I suppose that'll depend on my patience by the end of this month. Lol.
I should be able to update manually to 3.2 I know this much, but I can't seem to write to my SD Card which is why the manual updating via boot is not working, because it won't let me write to external_sd.
If someone can at least give me ideas on external_sd and write permissions for it WITHOUT rooting. Would be helpful.
Mean while I shall try and get a hold of support and see what they say.
-b00mer
Click to expand...
Click to collapse
Download the 3.2.x you want on your PC and put the sdcard in your PC, copy the file to the sdcard on your PC. Now take the sdcard out of the PC and put it into your tablet. Works every time.
Lastly, if you're still under warranty, why not just call ACER for help?
timmyDean said:
Download the 3.2.x you want on your PC and put the sdcard in your PC, copy the file to the sdcard on your PC. Now take the sdcard out of the PC and put it into your tablet. Works every time.
Lastly, if you're still under warranty, why not just call ACER for help?
Click to expand...
Click to collapse
The last thing I want to do is give it back to them and wait for about 2 weeks for the retail store to get their asses into gear and send it off, then wait another week for Acer to do fix things, which should just not have happened in the first place.
I've tried the idea you gave me mate. I took out the SD Card, and used an old phone that allowed me to access it as a Mass Storage Device because I didn't have a card reader, and formatted it both to FAT first then FAT32 and still no go. The tablet just cannot seem to be recognizing that it even has an External SD Card in it.
Its looking more and more like I'm going to HAVE to go in and get it sorted somehow. Thanks everyone for your input and help. I've also contacted Acer Support. Lets see what they have to say, which I will post here. I'll also fiercely be practicing my Google-Fu to see what else I can find.
-b00mer
I would suggest that you wait for the ICS to start coming out, I can let you know when I get it.
They may have removed the 3.1 and 3.2 from the OTA update sever to get ready for ICS.
If you don't have ICS in a week after it rolls then I would be taking it back to the retailer and telling them that it does not update, they will send it away to get it loaded etc.
mrtoken said:
I would suggest that you wait for the ICS to start coming out, I can let you know when I get it.
They may have removed the 3.1 and 3.2 from the OTA update sever to get ready for ICS.
If you don't have ICS in a week after it rolls then I would be taking it back to the retailer and telling them that it does not update, they will send it away to get it loaded etc.
Click to expand...
Click to collapse
Its kind of the only choice I have while I'm unable to do anything else.
Thanks mate, that'll be good to know. And yeah, I was thinking they removed it from their servers to get it ready, but I'm hoping they don't cut it out and stop it either like they did with Nexus S. I had to manually update that as well, but that worked seemlessly, while I was JUST getting drunk, during a party. You know something is good when you can do that.
I'm dreading letting it go away, but if they can load it up, I technically should be able to getting it loaded somehow as well?
-b00mer
Hi all. In advance, please don't flame me. I am new to Android, and don't understand all of the technical jargon. I have a problem that I hope will be a simple fix - if there is an answer already on the forums perhaps someone can point me in the right direction.
I was given a Samsung S4 by a friend that works for Samsung. Apparently it was some kind of demo model or something - typically given out for promotional purposes (which may or may not be relevant). The phone is factory unlocked. It is running on the AT&T version of the firmware. Here is the "About Device" info:
Model #: Samsung-SGH-I337
Android version: 4.2.2
Baseband ver: I337UCUAMDB
Kernal ver: 3.4.0-440216
My problem: I cannot update firmware. I tried OTA and via Samsung Kies. When I try OTA, it searches for an update (and finds one available), but then says that the update was interrupted and I there is no update available - try again in 24 hours (GRRR!). When I try to update via Kies, it finds the update and goes through a lengthy download process. Once it begins to install it (my screen goes black and green characters flash on the screen - so apparently it is trying to install the new firmware) - it hangs. Eventually I get a message stating that the update failed (or something along those lines) and I need to do emergency recovery. When I start emergency recovery it just hangs....eventually I just restart the phone and it is right back to normal.
I have tried this process 6 or 7 times-no luck. I really want the recent update, which allows moving apps to SD. Again - I am new to Android-everything. I understand that I likely need to manually install a ROM package - if someone could point me toward some step by step directions I would REALLY appreciate it. Thanks in advance for your help!
-TJ
To try to update more often, try moving the time and date of the phone ahead and try again. If you want to flash ROMS, don't update, because there is no bootloader unlock for it yet
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4
r8revealed said:
To try to update more often, try moving the time and date of the phone ahead and try again. If you want to flash ROMS, don't update, because there is no bootloader unlock for it yet
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4
Click to expand...
Click to collapse
Thx for the reply...and for the tip about adjusting the date/time. :good: I am fine with the stock AT&T ROM - but for whatever reason, my phone simply will not update. I tried resetting it - still no dice. If anyone could help me to reinstall the stock or newer AT&T rom manually, I think that would be ideal. Any ideas?
I don't know much about this, but maybe you could flash the stock AT&T firmware again via ODIN. It's basically "unooting" the device, even though your device isn't rooted. it'll wipe all your data and reinstall everything again. I did this often on my S3 but I'm not sure if it's the same for the S4. Maybe someone else would know better because I don't know the .tar files needed for unrooting the S4.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4
antjefferson said:
Hi all. In advance, please don't flame me. I am new to Android, and don't understand all of the technical jargon. I have a problem that I hope will be a simple fix - if there is an answer already on the forums perhaps someone can point me in the right direction.
I was given a Samsung S4 by a friend that works for Samsung. Apparently it was some kind of demo model or something - typically given out for promotional purposes (which may or may not be relevant). The phone is factory unlocked. It is running on the AT&T version of the firmware. Here is the "About Device" info:
Model #: Samsung-SGH-I337
Android version: 4.2.2
Baseband ver: I337UCUAMDB
Kernal ver: 3.4.0-440216
My problem: I cannot update firmware. I tried OTA and via Samsung Kies. When I try OTA, it searches for an update (and finds one available), but then says that the update was interrupted and I there is no update available - try again in 24 hours (GRRR!). When I try to update via Kies, it finds the update and goes through a lengthy download process. Once it begins to install it (my screen goes black and green characters flash on the screen - so apparently it is trying to install the new firmware) - it hangs. Eventually I get a message stating that the update failed (or something along those lines) and I need to do emergency recovery. When I start emergency recovery it just hangs....eventually I just restart the phone and it is right back to normal.
I have tried this process 6 or 7 times-no luck. I really want the recent update, which allows moving apps to SD. Again - I am new to Android-everything. I understand that I likely need to manually install a ROM package - if someone could point me toward some step by step directions I would REALLY appreciate it. Thanks in advance for your help!
-TJ
Click to expand...
Click to collapse
I'm not flaming you, I am giving you advice that will help you. Try to use the search function to find answers before posting a question that has already been posted several times. It is possible, the help you need has already been posted in those other threads several times. Also, did you see "similar" threads appear while you were posting your question? Take the time to read those first. It couldn't be easier because they are listed for you. You should also read the "pinned" threads in the "general" section. There is a lot of information there that will help you understand things, if you take the time to read it. If you don't understand the "technical jargon" take some time to learn about it before you do anything to your phone or you are guaranteed to mess it up. If you really don't want future flaming, follow the XDA rules and search for answers first. Good luck.
I have successfully blocked 10 or so FireTVs using DNSMasq. They got to the "Checking for updates" screen then continued fine to login.
I have a new batch of FireTVs though, and the same method leaves it stuck at an "Update available" screen, didn't even go to a "Checking for updates" message. Finally it times out and says it couldn't contact the servers.
Not sure on the method to block the updates in this case. Has anyone else experienced this?
Thanks heaps.
modstore said:
I have successfully blocked 10 or so FireTVs using DNSMasq. They got to the "Checking for updates" screen then continued fine to login.
I have a new batch of FireTVs though, and the same method leaves it stuck at an "Update available" screen, didn't even go to a "Checking for updates" message. Finally it times out and says it couldn't contact the servers.
Not sure on the method to block the updates in this case. Has anyone else experienced this?
Thanks heaps.
Click to expand...
Click to collapse
Depending on the version it comes with, it might have a forced update.
rbox said:
Depending on the version it comes with, it might have a forced update.
Click to expand...
Click to collapse
Ahh ok, so there's no way to stop this update happening? What's the best method to hopefully still get root, just let it install this update, and hope it hasn't gone to the latest. Then re-enable DNSMasq rules again after this update? Thanks!
modstore said:
Ahh ok, so there's no way to stop this update happening? What's the best method to hopefully still get root, just let it install this update, and hope it hasn't gone to the latest. Then re-enable DNSMasq rules again after this update? Thanks!
Click to expand...
Click to collapse
Sure, but at this point I think they are pushing out 51.1.3.0 out to everyone.
rbox said:
Sure, but at this point I think they are pushing out 51.1.3.0 out to everyone.
Click to expand...
Click to collapse
Ok, I'll just let it run and see what happens.
I assume there's no way to imitate the update server on localhost? Eg redirect to localhost and have the same XML file or whatever they request, and return an earlier update locally? Not really sure how it works, and I imagine it couldn't be this easy.
modstore said:
Ok, I'll just let it run and see what happens.
I assume there's no way to imitate the update server on localhost? Eg redirect to localhost and have the same XML file or whatever they request, and return an earlier update locally? Not really sure how it works, and I imagine it couldn't be this easy.
Click to expand...
Click to collapse
Various experiments have been done. If you MITM the update and replace it with a different version it will fail because it knows what the checksum should be. Although I don't think anyone has tried to see what happens if the checksum fails for a forced update. If it fails for a normal update it'll just fail and go on with life and try again later. I would assume if a forced update fails it'll just try to download it again. It will try to download a URL from http://amzdigitaldownloads.edgesuite.net. If you stick wireshark on it, see what it's trying to download, and then point the DNS to a local server which is serving up a garbage file at the location, it will download it and see the checksum failed. At that point it *might* keep booting and try to download it later, or it might be stubborn and try to download it again.
rbox said:
Various experiments have been done. If you MITM the update and replace it with a different version it will fail because it knows what the checksum should be. Although I don't think anyone has tried to see what happens if the checksum fails for a forced update. If it fails for a normal update it'll just fail and go on with life and try again later. I would assume if a forced update fails it'll just try to download it again. It will try to download a URL from http://amzdigitaldownloads.edgesuite.net. If you stick wireshark on it, see what it's trying to download, and then point the DNS to a local server which is serving up a garbage file at the location, it will download it and see the checksum failed. At that point it *might* keep booting and try to download it later, or it might be stubborn and try to download it again.
Click to expand...
Click to collapse
I unblocked the urls and allowed the update to run. Once it finished I put the block back in place, and after installing the updates, it proceeded to the "Checking for updates" step, which was successfully bypassed, and my system was only updated to 51.1.0.2 Thanks heaps for the info.
rbox said:
Various experiments have been done. If you MITM the update and replace it with a different version it will fail because it knows what the checksum should be. Although I don't think anyone has tried to see what happens if the checksum fails for a forced update. If it fails for a normal update it'll just fail and go on with life and try again later. I would assume if a forced update fails it'll just try to download it again. It will try to download a URL from http://amzdigitaldownloads.edgesuite.net. If you stick wireshark on it, see what it's trying to download, and then point the DNS to a local server which is serving up a garbage file at the location, it will download it and see the checksum failed. At that point it *might* keep booting and try to download it later, or it might be stubborn and try to download it again.
Click to expand...
Click to collapse
I will be testing this theory, among a few others, soon. One of my readers is shipping me his "refusing to proceed" Fire TV. It's currently in the mail. This is the first time I'll have one of these Fire TVs that won't proceed past the update check, so hopefully I'll be able to figure out a way to get to the home screen without taking an update. Stay tuned.
rbox said:
Various experiments have been done. If you MITM the update and replace it with a different version it will fail because it knows what the checksum should be. Although I don't think anyone has tried to see what happens if the checksum fails for a forced update. If it fails for a normal update it'll just fail and go on with life and try again later. I would assume if a forced update fails it'll just try to download it again. It will try to download a URL from http://amzdigitaldownloads.edgesuite.net. If you stick wireshark on it, see what it's trying to download, and then point the DNS to a local server which is serving up a garbage file at the location, it will download it and see the checksum failed. At that point it *might* keep booting and try to download it later, or it might be stubborn and try to download it again.
Click to expand...
Click to collapse
Wonder if the checksum is something that can be known & then injected while still loading a downgrading FW? When connected to a local server via Cat 5e cable?
You could use keyword blocking and just block every update that isn't rootable so it can only try to update to a version that is rootable
modstore said:
I unblocked the urls and allowed the update to run. Once it finished I put the block back in place, and after installing the updates, it proceeded to the "Checking for updates" step, which was successfully bypassed, and my system was only updated to 51.1.0.2 Thanks heaps for the info.
Click to expand...
Click to collapse
This is interesting. This shows that in some instances it doesn't flash the latest right away.
Y314K said:
Wonder if the checksum is something that can be known & then injected while still loading a downgrading FW? When connected to a local server via Cat 5e cable?
Click to expand...
Click to collapse
The problem is the firetv talks to an HTTPS server initially. It sends a huge JSON payload including encrypted data. And receives a huge JSON payload also including encrypted data. The Fire TV does certificate validation, so the HTTPS server it is presented has to have a valid certificate. It doesn't necessarily check that it's Amazon's certificate, just that it is a valid certificate (signed by a valid CA). But regardless, there are encrypted parts and plaintext parts of the payload and I suspect modifying anything in it would make it fail. Also I suspect the serial number is encoded in there somewhere too, so capturing the result of a "here, flash 51.1.0.2" payload might not work. But I didn't do too much experimentation on that front.
{ParanoiA} said:
You could use keyword blocking and just block every update that isn't rootable so it can only try to update to a version that is rootable
Click to expand...
Click to collapse
Yes, that is assuming it doesn't do a forced update to a non rootable version.
rbox said:
This is interesting. This shows that in some instances it doesn't flash the latest right away.
Click to expand...
Click to collapse
I assume if the forced update compares the checksum, it already knows which update it will be getting. So if an update is released after that, it couldn't be sent to it on it's first update, is that correct?
modstore said:
I assume if the forced update compares the checksum, it already knows which update it will be getting. So if an update is released after that, it couldn't be sent to it on it's first update, is that correct?
Click to expand...
Click to collapse
The way it works is the Fire TV talks to the update server and it says "hey, hows it going. My serial number is XYZ and i am running software version 123. Do you got anything for me?" And then the server will respond with either no or an update url along with the checksum.
So in theory, if the update server is configured to give out only old versions to really old boxes, and then give it the latest after that, that would explain the behavior being seen.
AFTVnews.com said:
I will be testing this theory, among a few others, soon. One of my readers is shipping me his "refusing to proceed" Fire TV. It's currently in the mail. This is the first time I'll have one of these Fire TVs that won't proceed past the update check, so hopefully I'll be able to figure out a way to get to the home screen without taking an update. Stay tuned.
Click to expand...
Click to collapse
Any updates... Have you even received the AFTV ?
Y314K said:
Any updates... Have you even received the AFTV ?
Click to expand...
Click to collapse
I did receive it. I haven't had too much time to mess with it yet. So far, no amount of URL blocking will get past the forced update. I'm pretty sure it puts up the "an update is available" screen before it even checks to see if there actually is an update. I've blocked nearly every domain it's trying to access, so either it permanently remembers there is an update (yes I've cleared /cache and /data) or it tries to update no matter what.
It will not proceed if it doesn't get an expected response from softwareupdates.amazon.com. A spoofed response is not good enough. It needs to be the encrypted response it expects. Since the softwareupdates.amazon.com responce tells it to start download ing the update, my next step is to try feeding it various versions of the update file and see how it reacts.
AFTVnews.com said:
I did receive it. I haven't had too much time to mess with it yet. So far, no amount of URL blocking will get past the forced update. I'm pretty sure it puts up the "an update is available" screen before it even checks to see if there actually is an update. I've blocked nearly every domain it's trying to access, so either it permanently remembers there is an update (yes I've cleared /cache and /data) or it tries to update no matter what.
It will not proceed if it doesn't get an expected response from softwareupdates.amazon.com. A spoofed response is not good enough. It needs to be the encrypted response it expects. Since the softwareupdates.amazon.com responce tells it to start download ing the update, my next step is to try feeding it various versions of the update file and see how it reacts.
Click to expand...
Click to collapse
Great to hear your throwing the kitchen sink at it. I am waiting for my 2nd unit from Staples. Seems all the ones they are shipping are on the new unrootable FW (Amazon must of sent out only new FW as restock). But with coupons you can't beat Staples price (Under $60) Will have to decide what I want to do with it. My 1st unit is already rooted. Heard any rumors about a new root ?
Y314K said:
Great to hear your throwing the kitchen sink at it. I am waiting for my 2nd unit from Staples. Seems all the ones they are shipping are on the new unrootable FW (Amazon must of sent out only new FW as restock). But with coupons you can't beat Staples price (Under $60) Will have to decide what I want to do with it. My 1st unit is already rooted. Heard any rumors about a new root ?
Click to expand...
Click to collapse
No rumors on a new root. A new root will likely come from an Android phone root and not a Fire TV specific root.
{ParanoiA} said:
You could use keyword blocking and just block every update that isn't rootable so it can only try to update to a version that is rootable
Click to expand...
Click to collapse
Well if you have CWM & the latest PreRooted FW then your super protected & don't have to worry about things. CWM will block AutoUpdates. One of a the many benefits of a rooted AFTV + CWM.
AFTVnews.com said:
No rumors on a new root. A new root will likely come from an Android phone root and not a Fire TV specific root.
Click to expand...
Click to collapse
At least the base for root possibilities is much broader if you include Android Phones...
AFTVNews... You might want to take a look at this post over at SlickDeals...
Also, just a heads up. Bought one on Amazon yesterday, came today, still had everything blocked. Booted up, stuck on Downloading Updates screen. Waited 10 min, pulled the power, plugged it back in. Again Downloading Updates. 10 min, pulled the power. This time, disconnected the ethernet cable before powering up. Showed downloading updates for a split second then went in to the Fire TV UI. Successfully rooted and got everything installed.
Click to expand...
Click to collapse
Hope this helps... Come on over to SlickDeals or let me know if you have any more ?'s for MSK2982....
I'm still trying different things with no luck. I've tried killing and/or blocking the update download at various points with no luck. I've also tried making it download a dummy update file by redirecting the download request to my own server. Everything ends up with the same result: an update failed message with no option but to pull the power and try again.
I've only got a few more ideas and then I'm spent. Ideas for things to try are welcome.
Side note: I've found that if the update file download returns a "404 - File Not Found", the Fire TV will retry the download about every 3 minutes forever. I let it go for a full hour and it never gave up. This doesn't really change anything, but I thought it was worth mentioning since it's the only thing that has changed the routine so far.
AFTVnews.com said:
I'm still trying different things with no luck. I've tried killing and/or blocking the update download at various points with no luck. I've also tried making it download a dummy update file by redirecting the download request to my own server. Everything ends up with the same result: an update failed message with no option but to pull the power and try again.
I've only got a few more ideas and then I'm spent. Ideas for things to try are welcome.
Side note: I've found that if the update file download returns a "404 - File Not Found", the Fire TV will retry the download about every 3 minutes forever. I let it go for a full hour and it never gave up. This doesn't really change anything, but I thought it was worth mentioning since it's the only thing that has changed the routine so far.
Click to expand...
Click to collapse
What about a 403 forbidden?
I'm about to jump of a ledge over here. So, I've read about this online as well.
I try to install 11.0.2.2.1N11AA and, by the numbers, this is what happens:
1. It says "Installation will continue when device isn't being used. To install now, tap Resume."
2. I tap resume.
3. It says: "Couldn't update
Installation problem"
4. I see and tap "Try again".
5. Loopback to step 1 -- ad infinitum.
How can I update this thing? Anyone have any luck?
And, on another note, at what point is my device not being used exactly? What is using my device that makes this update unworkable? I searched online, others have problems, no one seems to have solutions.
Others noticed this problem on XDA, nobody said anything so far. I found this thread through Google: https://forum.xda-developers.com/t/...-dumper-magisk_patched-guides.4175033/page-13 The Nov 23, 2020 at 10:44 AM reply. That man is in a similar situation as I!
I went through the remainder of the thread, searching for the username "raashnal" in each page until the end of the thread. The logic being, if anyone addressed his concern they would reply to it and he would presumably reply to thank that person. So, I figure the name must come up; it did not; so I assume this thread does not have an answer.
reilus said:
I'm about to jump of a ledge over here. So, I've read about this online as well.
I try to install 11.0.2.2.1N11AA and, by the numbers, this is what happens:
1. It says "Installation will continue when device isn't being used. To install now, tap Resume."
2. I tap resume.
3. It says: "Couldn't update
Installation problem"
4. I see and tap "Try again".
5. Loopback to step 1 -- ad infinitum.
How can I update this thing? Anyone have any luck?
And, on another note, at what point is my device not being used exactly? What is using my device that makes this update unworkable? I searched online, others have problems, no one seems to have solutions.
Others noticed this problem on XDA, nobody said anything so far. I found this thread through Google: https://forum.xda-developers.com/t/...-dumper-magisk_patched-guides.4175033/page-13 The Nov 23, 2020 at 10:44 AM reply. That man is in a similar situation as I!
I went through the remainder of the thread, searching for the username "raashnal" in each page until the end of the thread. The logic being, if anyone addressed his concern they would reply to it and he would presumably reply to thank that person. So, I figure the name must come up; it did not; so I assume this thread does not have an answer.
Click to expand...
Click to collapse
Hello again
So are you rooted at the moment? Do you have oxygen updater installed?
If you are rooted then please disable any and all active modules then reboot your phone.
Then open oxygen updater.
Accept the agreement and provide it any rights it needs then take the update (a full update)
It'll push it to your phone.
Go to settings /system updates / local upgrade.
Choose the zip downloaded by oxygen updater.
Do not reboot when it's complete.
Press home then reopen magisk and click install, then click install to inactive slot after OTA.
Let they install then click reboot, that should be it.
If you're not rooted then let me know.
PS: that's my thread btw, your rationale doesn't quite make sense, an answer could have been given and thanks provided or not. Meaning their name doesn't necessarily have to come up again at all.
It's not that long a thread tbh. The amount of responses I've had and issues addressed and resolved I would say that pretty much any issue to do with payload dumper, root has been addressed
Thank you! I was just about to say, I ended up using Oxygen updater and then doing a local install.
I cannot do an incremental update, but I can do a full update.
I did have an interesting problem, which I also solved. I could not do the OTA install of Magisk! So, I swiped the Oxygen Updater off the recents. Then I tried again and it worked! So, if anyone else has that issue, maybe that will help them !
And I understand that my rationale is flawed, any rational position is flawed. In fact, you won't find any epistemic approach -- even science -- without flaws. I declared my biases and methods to show that I feel I put in a reasonable effort before asking for help. I hope that was part of your understanding. =)
reilus said:
Thank you! I was just about to say, I ended up using Oxygen updater and then doing a local install.
I cannot do an incremental update, but I can do a full update.
I did have an interesting problem, which I also solved. I could not do the OTA install of Magisk! So, I swiped the Oxygen Updater off the recents. Then I tried again and it worked! So, if anyone else has that issue, maybe that will help them !
And I understand that my rationale is flawed, any rational position is flawed. In fact, you won't find any epistemic approach -- even science -- without flaws. I declared my biases and methods to show that I feel I put in a reasonable effort before asking for help. I hope that was part of your understanding. =)
Click to expand...
Click to collapse
If you are rooted then you're certainly not meant to do an incremental OTA as it needs to be a full update.
Haha and no need to prove your efforts to me pal, it's all good.
Just glad you're sorted.
PS: I've actually just updated the thread as 11.0.3.3 just arrived.
I've provided a patched boot img and have updated the guide already
reilus said:
I'm about to jump of a ledge over here. So, I've read about this online as well.
I try to install 11.0.2.2.1N11AA and, by the numbers, this is what happens:
1. It says "Installation will continue when device isn't being used. To install now, tap Resume."
2. I tap resume.
3. It says: "Couldn't update
Installation problem"
4. I see and tap "Try again".
5. Loopback to step 1 -- ad infinitum.
How can I update this thing? Anyone have any luck?
And, on another note, at what point is my device not being used exactly? What is using my device that makes this update unworkable? I searched online, others have problems, no one seems to have solutions.
Others noticed this problem on XDA, nobody said anything so far. I found this thread through Google: https://forum.xda-developers.com/t/...-dumper-magisk_patched-guides.4175033/page-13 The Nov 23, 2020 at 10:44 AM reply. That man is in a similar situation as I!
I went through the remainder of the thread, searching for the username "raashnal" in each page until the end of the thread. The logic being, if anyone addressed his concern they would reply to it and he would presumably reply to thank that person. So, I figure the name must come up; it did not; so I assume this thread does not have an answer.
Click to expand...
Click to collapse
I always have the same problem when I try to update. For whatever reason before I update I have to flash boot the "stock" boot.img and then my phone will accept the update.
State.of.mind said:
I always have the same problem when I try to update. For whatever reason before I update I have to flash boot the "stock" boot.img and then my phone will accept the update.
Click to expand...
Click to collapse
That's not true mate, if you're rooted there is simply no need to change the boot.img, use magisk to install to inactive slot before rebooting, that is it.
The update method you use whilst rooted is oxygen updater and it's a full OTA
dladz said:
That's not true mate, if you're rooted there is simply no need to change the boot.img, use magisk to install to inactive slot before rebooting, that is it.
The update method you use whilst rooted is oxygen updater and it's a full OTA
Click to expand...
Click to collapse
dladz said:
That's not true mate, if you're rooted there is simply no need to change the boot.img, use magisk to install to inactive slot before rebooting, that is it.
The update method you use whilst rooted is oxygen updater and it's a full OTA
Click to expand...
Click to collapse
I was sharing my experience with updates. Regardless of the update platform Oxygen Updater or One Plus I ALWAYS have to flash the stock boot.img prior to receiving an update.
I think the problem could be that when I flash the patched magisk boot image I flash it to both slots and not one single slot. I'll try the newer method when another update is released.
State.of.mind said:
I was sharing my experience with updates. Regardless of the update platform Oxygen Updater or One Plus I ALWAYS have to flash the stock boot.img prior to receiving an update.
I think the problem could be that when I flash the patched magisk boot image I flash it to both slots and not one single slot. I'll try the newer method when another update is released.
Click to expand...
Click to collapse
Yep again mate you don't need to do that, regardless where you download the update from provided it is in fact a full update