I have followed the instructions AFTVnews website and blocked the spacific sites preventing it from updating but it is just stuck on the screen saying that it needs to update, any help would be great
kpnavarro said:
I have followed the instructions AFTVnews website and blocked the spacific sites preventing it from updating but it is just stuck on the screen saying that it needs to update, any help would be great
Click to expand...
Click to collapse
Try this: http://www.aftvnews.com/how-to-get-passed-a-forced-software-update-on-the-amazon-fire-tv/
If that doesn't work, and you've confirmed that it has the older software, then most likely it will not update straight to an unrootable version. So let the update go through and then immediatly block updates again.
If its a older software version what is the likely hood that it will still be rootable after a update and is there any video or guides on this so I know the exact time to stop it from updating and block it again
kpnavarro said:
If its a older software version what is the likely hood that it will still be rootable after a update and is there any video or guides on this so I know the exact time to stop it from updating and block it again
Click to expand...
Click to collapse
I just bought one that had the forced update on it because it was the old software. If it's in fact the old software, it will do the forced update to a rootable version. You need to block it when it starts doing the update after it's done downloading.
Related
Check out this link:
http://www.slashgear.com/htc-hero-update-confirmed-imminent-1852644/
Appears as though HTC are gonna address the lagginess expereinced by many (including myself) with an OTA update.
Those with root like me will not get the OTA update as ive read the firmware wont update on rooted phones. Im wondering whether people will put their chef hats on with the new update to create a rom based on it?
You could restore a backup from a point where you had not rooted your phone yet
It basically unroots itself that way.
ammurad said:
Check out this link:
http://www.slashgear.com/htc-hero-update-confirmed-imminent-1852644/
Appears as though HTC are gonna address the lagginess expereinced by many (including myself) with an OTA update.
Click to expand...
Click to collapse
That link makes no mention whatsoever that the update will be OTA - in fact, it says:
“HTC will be providing a software update for the HTC Hero, which will be available via the HTC website in the coming weeks.” HTC statement
Click to expand...
Click to collapse
Via the website almost certainly means download and update manually. Being rooted shouldn't stop you applying the update, though you will probably lose root in the process.
Note that Google pushed OTA updates out for the G1, and the reason they didn't work on most rooted phones was because the procedure used to root the phone specifically switched off the OTA functionality to avoid the phone getting an update and losing root.
Regards,
Dave
It was confirmed prior to release that the Hero would be incapable of receiving OTA updates.
Ok thats useful information. We can just hope now that the update will get rid of the lag.
Someone needs to change the thread topic to
Hero update Iminent, but noT if you have ROOT!
ghoonk said:
Someone needs to change the thread topic to
Hero update Iminent, but noT if you have ROOT!
Click to expand...
Click to collapse
I thought it was only OTA updates that rooted phones couldn't recieve.
Biffert said:
You could restore a backup from a point where you had not rooted your phone yet
It basically unroots itself that way.
Click to expand...
Click to collapse
correct me if i am wrong but even if you back up with nandroid before rooting , running the backup doesnt unroot your phone.
anyway, it is not a problem. all u have to do is just to flash the stock rom posted on this thread and then run the update if this is the case .
I don't think ROOTING is the problem. I think that some people, in the process of rooting, end up changing the recovery.img with test keys which the update may check against and prevent the update.
I updated mine using ADB and used fastboot, so I don't think I actually changed the recovery.img, so future updates will just see my phone as a 'normal' unbranded device (albeit with Superuser.apk and su.apk, and the HTC CIME)
After OTA update, We will get the Custom rom of Hero soon (Like in G1)
I'm in Cincinnati Ohio, and I have a *completely stock and non-rooted* Note 2. I have been trying to get this OTA update since it came out, but no dice so far.
It basically just says that no update is available - the same message everyone else reported. Am I just in an area where it has not been rolled out for *anybody*? Or is there something going on?
I know on my Nexus 7 I had to clear the data on a google service to get it to notice when the Kit Kat update showed up - anything like that for the Note 2?
Thanks.
P.S.
I have searched both XDA and with google, and completely read through the main large thread in this forum relating to the update.
I don't want to load the update in any other way that will wipe my phone. I understand that many of you don't feel like waiting for an OTA, and download these updates and load them manually. I do not want to do that. So, this post is only seeking information as to how I can get the OTA update through the update mechanism in the phone.
Update
Have you tried updating through KIES?
esellerauction said:
Have you tried updating through KIES?
Click to expand...
Click to collapse
No, I don't even have it installed. If I decide to install KIES, does it do the update without wiping the phone - just like the OTA?
I just don't like installing vendor crapware on my computers unless it is absolutely necessary. Which is why I don't own electronics with a "i" prefix.
Ok, I installed KIES and attached is an error message it gives relating to a firmware update
zilla1126 said:
Ok, I installed KIES and attached is an error message it gives relating to a firmware update
Click to expand...
Click to collapse
Crap, nevermind. I got this phone via trade and it turns out that the guy I got it from had rooted it at some time in the past... So no OTA for me. I'll accomplish it the way all the other folks have.
Thanks
Has anyone updated to the new firmware for firetv does kodi still work on this new firmware
Noel30 said:
Has anyone updated to the new firmware for firetv does kodi still work on this new firmware
Click to expand...
Click to collapse
The latest just came out yesterday and changes haven't been posted (that I can see)
Why do you ask? If you're unrooted you have no choice but to take it and if you're rooted you don't have it to install...
I doubt any future updates will break kodi. Even though I always get it from the org, Im pretty sure amazon has it in the app store now (not specifically for aftv) but I still doubt after embracing on other devices they'll kill it for one. I could be dead wrong but like I said up top--what choice do you have?
Early days... but some users on AFTnews are reporting it to be working ok
Code:
aftvnews.com/amazon-fire-tv-update-51-1-5-0-and-fire-tv-stick-update-54-1-1-0-have-been-released/
You don't have to take the updates though. You can block them via your router. Actually thats a good idea until you can be sure everything is okay.
I have them blocked but i will unblock the updates just to get this update as it says ul be able to use usb in this udate hopefully they dont block sideloading as i really like kodi on my firetv so just wondering has anyone updated there firetvs
Hi, hoping I could get some help.
I just got a huawei watch and cannot get it to update. It is on version 1.3xxxx. When I try to update it, it says it's already the latest version. Hopefully I'm just overlooking something very obvious as right now I feel stuck in the mud. Thanks for your help in advance!
Same issue here! Own the watch from 4 days now.
Same for me
An idea ?
Ok, i updated my watch with success. I believe that the OTA don't work because my watch is a refurbished one and the OTA system think that my watch is already up to date.
Here's how to update, it's easy:
You have to do an adb sideload of the OTA files:
Tutorial here:
http://phandroid.com/2016/03/02/huawei-watch-marshmallow/
You have to flash this file first if you are stuck in LCB43B:
http://android.googleapis.com/packa...866b47.signed-sturgeon-MEC23L-from-LCB43B.zip
After the reboot, continue with:
https://android.googleapis.com/pack.../6bae896422cb963c01b479eea9838f1b1b0d705e.zip
After that update the OTA worked normally.
Hope this help.
Thanks for starting this thread! I think all the people stuck on older firmware are Canadians with refurbs from newegg (incl me)? However, I am not sure how being refurb has anything to do with it.
My watch did update once from the version it came with, but kept on saying its up-to-date after that. I guess flashing stock image is the only way to go.
jainanshal said:
Thanks for starting this thread! I think all the people stuck on older firmware are Canadians with refurbs from newegg (incl me)? However, I am not sure how being refurb has anything to do with it.
My watch did update once from the version it came with, but kept on saying its up-to-date after that. I guess flashing stock image is the only way to go.
Click to expand...
Click to collapse
The issue with flashing the stock image is that you have to unlock the bootloader, and after that it seems that you loose the warranty.
Better flashing OTA if you want to stay stock. I bought my refurb from newegg.ca too.
ndompierre said:
Ok, i updated my watch with success. I believe that the OTA don't work because my watch is a refurbished one and the OTA system think that my watch is already up to date.
Here's how to update, it's easy:
You have to do an adb sideload of the OTA files:
Tutorial here:
http://phandroid.com/2016/03/02/huawei-watch-marshmallow/
You have to flash this file first if you are stuck in LCB43B:
http://android.googleapis.com/packa...866b47.signed-sturgeon-MEC23L-from-LCB43B.zip
After the reboot, continue with:
https://android.googleapis.com/pack.../6bae896422cb963c01b479eea9838f1b1b0d705e.zip
After that update the OTA worked normally.
Hope this help.
Click to expand...
Click to collapse
Same problem.
Then I took your advice and it worked out great, and without changing the bootloader, thank you so much ndompierre :good::victory:
I got my newegg refurb yesterday and could not force the OTA despite resetting and checking multiple times. This afternoon it updated to marshmallow.
Each time time it reboots, I check for updates. I am currently receiving my fourth update of the day.
I guess each security patch has to be downloaded separately. I'm up to August so far..
Please,Don't upgrade you device firmware
Similar problem arose like before with initial global releases of Samsung ..
After suspending the update roll out but still some devices are receiving the update with a small code error and unable to communicate properly with PCB results in
Bootloop unable to fix this issue
Though this issue is resulting to a small niche of users
Developer recommend those few users can wait till some official notification is released
Or Users can try manually downgrading SYSTEM
(Keep nand backup since HOME CSC won't work due to encryption except you can restore data later after device is successfully reset)
Direct Link to Stock SM-705G (official only for units manufactured in India)
https://dl2018.sammobile.com/NV9ZRi...ERdVg../A705GMDDU5ATA1_A705GMODM5ATA1_INS.zip
Instruction to Odin Flash (in case)
https://www.sammobile.com/samsung/galaxy-a70/firmware/SM-A705GM/INS/download/A705GMDDU5ATA1/312540/
We already know this
Bugz1 said:
We already know this
Click to expand...
Click to collapse
I knew about this since previous update and this April security patch really f**ked bad
Fair Warning ...
P.S data lost
Abish4i said:
Please,Don't upgrade you device firmware
Similar problem arose like before with initial global releases of Samsung ..
After suspending the update roll out but still some devices are receiving the update with a small code error and unable to communicate properly with PCB results in
Bootloop unable to fix this issue
Though this issue is resulting to a small niche of users
Developer recommend those few users can wait till some official notification is released
Or Users can try manually downgrading SYSTEM
(Keep nand backup since HOME CSC won't work due to encryption except you can restore data later after device is successfully reset)
Direct Link to Stock SM-705G (official only for units manufactured in India)
https://dl2018.sammobile.com/NV9ZRi...ERdVg../A705GMDDU5ATA1_A705GMODM5ATA1_INS.zip
Instruction to Odin Flash (in case)
https://www.sammobile.com/samsung/galaxy-a70/firmware/SM-A705GM/INS/download/A705GMDDU5ATA1/312540/
Click to expand...
Click to collapse
This has already been fixed, updating to stock Android 10. The first release had the battery issue and was hard bricking the a70, samsung suspended the update and rolled out a new fixed android 10 update. Alls good now.
MarvinMod said:
This has already been fixed, updating to stock Android 10, samsung suspended.
Click to expand...
Click to collapse
I am talking abt the update one somewhere around 26-04
it was supposed to be the one with patch but that update corrupted itself ...:good:
[/COLOR]
Abish4i said:
I am talking abt the update one somewhere around 26-04
it was supposed to be the one with patch but that update corrupted itself ...:good:
Click to expand...
Click to collapse
Im saying, the issue with pcb is fixed. Try downloading the update now and flash. Fyi, you cant downgrade from 10 to 9 once you have updated to 10. Samsungs efuse will be triggered. It's been said that a device affected with the PCB bug is hardbricked, however, that is not entirely true.
MarvinMod said:
[/COLOR]
Im saying, the issue with pcb is fixed. however, that is not entirely true.
Click to expand...
Click to collapse
This was for people who might have bricked their devices and are looking for a workaround to successfully fix bootloop boot (same happened to me)
Since due to lookdown a lot of us can't visit customer support for same.
FYI officially you can downgrade without breaking efuse
Abish4i said:
This was for people who might have bricked their devices and are looking for a workaround to successfully fix bootloop boot (same happened to me)
Since due to lookdown a lot of us can't visit customer support for same.
FYI officially you can downloadgrade without breaking efuse
Click to expand...
Click to collapse
Efuse is popped during an update not a downgrade. Idk if ota pops it but i know updating with odin sure does and no, once the efuse is provisioned, there is no going back. If you or anyone else has found a way besides opening the device and making jumpers, please explain or provide links.
Device never went to 10 since the update with 10 has this error to ppl can still switch back to 9 hassle-free.
Thx for heads up!
Overall, Android 10 upgrade was a big disappointment for me, and pushed towards rooting it first, and then to installing LineageOS 17.1.
So, after rooting I disabled auto updates as I knew things can go bad.
But now I'm lucky LOS user!
I flashed my A705MN using Odin to get around the bootloop and it worked but now my wifi and bluetooth doesn't turn on. -_- I'm kinda new at this flashing business. How can I activate them both again?
MarvinMod said:
This has already been fixed, updating to stock Android 10. Alls good now.
Click to expand...
Click to collapse
Not good yet ;
I did some research with certified service centres this problem can't be fixed with software though it can be fixed with as a manual upgradation of PCB board is required
Ultrachamo said:
I flashed my A705MN using Odin to get around kinda new at this flashing business. How can I activate them both again?
Click to expand...
Click to collapse
If still error do following
Are you sure abt manufacturing unit place of origin is India it's fine ... Still if you used HOMECSC and it worked
you need to format it first thing in
If not manufactured in India Search for country origin specific file ... for odin flash
Why does this count as "development"?
DroidGTV said:
Why does this count as "development"?
Click to expand...
Click to collapse
Idk maybe it cuz the bug is related to PCB bridge code error in software which might be fixed with either downgrading FW ver or Hardware upgradation...