After a roll back updating ota is no longer possible. Is it possible to flash firmware manually?
You can contact Amazon support to place you back in the regular OTA pool.
Otherwise, you could try doing it manually. You'd want to download the BIN file and place it in the root of the internal storage directory. Then, just go into the menu where you usually check for updates, press the button, and it should say that it's ready to install.
Amazon say once downgraded you can't receive OTA again. Where would I find .BIN files for HDX 7
slugger09 said:
Amazon say once downgraded you can't receive OTA again. Where would I find .BIN files for HDX 7
Click to expand...
Click to collapse
The OTA block is applied on their side; it's based on your device's serial number (FSN). So, they can obviously undo it if you request it.
As for that BIN file, you can find the latest one as of right now here: http://forum.xda-developers.com/kindle-fire-hdx/general/update-1314-4-1-1-probably-sangria-t2901813
It worked with the bin file. However I'm no soon updated until a system update has started downloading. It's 3.2.7 again.
slugger09 said:
It worked with the bin file. However I'm no soon updated until a system update has started downloading. It's 3.2.7 again.
Click to expand...
Click to collapse
You can read here about the OTA verification steps.
There are 3 ways to pass the version check:
1) use a OTA with a higher version number
2) remotely set a flag that disables the version check (guess you can exploit this by using bug 17356824 - poc here)
3) trick the verification system as I did
The problem is actually with the bootloader checks. As the OTA flashes a complete bootloader chain, the SBL1 version number will change. If it goes down, you end up with a brick (as I did).
I suspect the 3.2.7 OTA that Amazon has pushed for downgrading is a special build that has both a higher version number in build.prop and also on the SBL1 stage. This would explain why the 3.2.7 OTA keeps showing up even after upgrading to 4.5.x.
LE
While rooted you could try changing the version number in build.prop to the 4.5.1 one. This should trick the update system into downloading the 3.2.7 OTA. As you have root you could access the OTA bin and upload it. This way people wouldn't have to contact Amazon and request a downgrade.
Actually there is also a flag that disables SSL certificate verification. You could set this flag and then MITM the download.
Related
I have installed 9.4.2.11.1 manually from HoneyCome
I have no issue with freezes or lockups, but I realized It stopped giving me an OTA updates.
While some people are getting .14 update, I am still on 11.1 and even when I check for an update, Prime says there is no update for me.
Is it because I manually updated my prime? If so, how do I get OTA update back?
You are on a beta build of sorts so the actual firm ware updates don't recognize your Build # as one that needs to be updated.
What you need to do is manually up date to a current Build # and get back in the loop. I just did this myself, here are the steps. It's easy and only takes a little time.
Go to the Asus firmware download site.
http://support.asus.com/download.aspx?SLanguage=en&p=20&s=16&m=Eee+Pad+Transformer+Prime+TF201&os=&hashedid=FqCKMQDqgvSncfFM
Download the firmware update for version 13.
Then follow the instructions here to manually update (you probably already know this since you are on 11.1
http://service.asus.com/infopage.aspx?rid=18
You'll update and be on version 13 and your Prime will now "see" OTAs.
Check for firmware updates, it will say there is a new version and it will start to download 14.
ta-da!! You (and I) are back in the loop for OTAs
slugbug2010 said:
You are on a beta build of sorts so the actual firm ware updates don't recognize your Build # as one that needs to be updated.
What you need to do is manually up date to a current Build # and get back in the loop. I just did this myself, here are the steps. It's easy and only takes a little time.
Go to the Asus firmware download site.
http://support.asus.com/download.aspx?SLanguage=en&p=20&s=16&m=Eee+Pad+Transformer+Prime+TF201&os=&hashedid=FqCKMQDqgvSncfFM
Download the firmware update for version 13.
Then follow the instructions here to manually update (you probably already know this since you are on 11.1
http://service.asus.com/infopage.aspx?rid=18
You'll update and be on version 13 and your Prime will now "see" OTAs.
Check for firmware updates, it will say there is a new version and it will start to download 14.
ta-da!! You (and I) are back in the loop for OTAs
Click to expand...
Click to collapse
I will try tomorrow. Thanks!
Ok I have the same problem but .13 update is not available on asus site and trying to manual update to .14 does not work any help ?
PLEASE READ ENTIRE THREAD BEFORE ATTEMPTING!! I AM NOT RESPONSIBLE FOR ANY DAMAGE
FILE WAS DOWNLOAD FROM AT&T VIA OTA UPDATE FROM MY MEGA & EXTRACTED FROM THERE - I527UCUBNE7 CFG FILE OTA UPDATE
I only recommend running adb sideload to install.
ADB SIDELOAD DETAILED INSTRUCTIONS
- Make sure USB debugging is ENABLED
- Reboot device into recovery
- Plug device into computer
- Select adb sideload from your devices recovery screen (drivers might need to install, wait for this and then continue)
- load up command prompt for adb
From here I will give examples (adjust according where your file is stored)
As example say I saved my file in my documents folder this would be the command to sideload
adb sideload c:/users/owner/my documents/ATT OTA 4.4 UPDATE.cfg .............you can rename the file whatever you want but I changed the name for confusion as to what it was.
The file will start to load onto the device and show percentage in adb until upload is complete. Once the file is loaded your device will start the update process. If it fails it will show where it stopped at most likely being that a factory file is missing or changed. Everything must be original from previous mr2 firmware.
AGAIN IF YOU REMOVED, MODIFIED, FROZE APPS LIKE KNOX MOST LIKELY YOUR UPDATE WILL FAIL AFTER 25-30%. FOR BEST RESULTS YOUR ROM MUST HAVE ALL ORIGINAL FILES. THIS UPDATE SCANS YOUR FILE SYSTEM TO ENSURE NOTHING HAS BEEN CHANGED. ANY CHANGE WILL CAUSE A FAILURE.
IF YOU GET AN ERROR DURING UPDATE - INSTALL INSTRUCTIONS IF YOU GET AN ERROR
- Download mr2.tar.md5 file located in my signature under galaxy mega repository
- Install via Odin & make sure "Auto-Reboot" is UN-CHECKED
- Once install is finished reboot device into recovery
- Select adb sideload install then follow the steps above to install update via sideload
THIS UPDATE IS NOT ROOTED OR UNLOCKED. INSTALLING WILL CAUSE YOU TO LOOSE ROOT!!
IF YOURE NOT SURE WHAT YOUR DOING - DONT DO IT - RECOMMEND REMOVING BUSYBOX - ROOT BEFORE INSTALL -
AT&T I527UCUBNE7 OTA UPDATE - CFG FILE - DROPBOX CURRENTLY DOWN DUE TO CONGESTION
- GOOGLE DRIVE LINK - I527UCUBNE7 OTA UPDATE - GOOGLE DRIVE LINK -
- MEGA LINK - I527UCUBNE7 OTA UPDATE - MEGA LINK -
AGAIN USE AT YOUR OWN RISK.
Can I remove apps and flash?
updated no problems but now i have no touch on the screen. no buttons light up or nothing. has anybody else ran into this problem.
thanks
hedgehogmd said:
updated no problems but now i have no touch on the screen. no buttons light up or nothing. has anybody else ran into this problem.
thanks
Click to expand...
Click to collapse
did you run update while your phone was rooted?
KDKobes said:
did you run update while your phone was rooted?
Click to expand...
Click to collapse
No i did a full system reload with Odin then applied the OTA. everything went fine no errors rebooted and no touch.
hedgehogmd said:
No i did a full system reload with Odin then applied the OTA. everything went fine no errors rebooted and no touch.
Click to expand...
Click to collapse
I have seen this happen before. Which "full system reload file" did you use and where was it downloaded? Usually is fixed by re-installing a lower version rom then reapplying the update. I would recommend reinstalling the official rom if thats what you used if you can. This would be the mr2 tar.md5 file in odin. Which way did you install update? Did you try reinstalling the update?
*currently uploading stock official att mr2.tar.md5 to my repository. File should be up shortly*
KDKobes said:
I have seen this happen before. Which "full system reload file" did you use and where was it downloaded? Usually is fixed by re-installing a lower version rom then reapplying the update. I would recommend reinstalling the official rom if thats what you used if you can. This would be the mr2 tar.md5 file in odin. Which way did you install update? Did you try reinstalling the update?
*currently uploading stock official att mr2.tar.md5 to my repository. File should be up shortly*
Click to expand...
Click to collapse
i replaced the screen about 4 months ago with a aftermarket lcd assy and i had to hookup my cracked factory screen boot phone the plug in my aftermarket screen and touch works.
My phone is unlocked. If I do this, what are the chances I lose that unlock?
I updated to 4.2.2 via Kies and didn't lose the unlock, so curious about this.
kwed73 said:
My phone is unlocked. If I do this, what are the chances I lose that unlock?
I updated to 4.2.2 via Kies and didn't lose the unlock, so curious about this.
Click to expand...
Click to collapse
I updates and didn't lose my unlock
Is someone working on a odin version of this update
Great!
Wow..... I have been here and there before I got here. It worked flawlessly!
I got an OTA,
Download and Verified
Rebooted started to install
Then got the Android laying on his back with error under it.
So I held the power button,
the device restarted but no longer offers an OTA update.
My questions are,
Will given time will Google catch on I am running old firmware a offer the OTA again?
Can I force the OTA?
Will it even complete it failed the first time?
or
Should I just give up, find the image, extract it and update manually?
AstroDigital said:
I got an OTA,
Download and Verified
Rebooted started to install
Then got the Android laying on his back with error under it.
So I held the power button,
the device restarted but no longer offers an OTA update.
My questions are,
Will given time will Google catch on I am running old firmware a offer the OTA again?
Can I force the OTA?
Will it even complete it failed the first time?
or
Should I just give up, find the image, extract it and update manually?
Click to expand...
Click to collapse
Install could have failed for a variety of reasons. If you are rooted, or have a custom kernel, or are unencrypted, of there is any modification to the system.
You can sideload the OTA, but really? That's as much work as fastboot flashing the system image.
So, if your bootloader is unlocked, I'd suggest that you just fastboot flash the individual .img files, extracted from the system image.
.... I did a manual install, I have not had much luck with OTAs
I flashed 4.5.2 Apollo on my 8.9 HDX from CM11 now Im stuck it doesnt update just says update failed I removed the recovery didnt fix the problem either. Is there a flashable 4.5.5.1 apollo zip? I tried changing the bin to a zip and flashing didnt work said apollo_full instead of apollo as error. Anyone know how to fix it just downloads the update fully then says update failed...
DroidDogg said:
I flashed 4.5.2 Apollo on my 8.9 HDX from CM11 now Im stuck it doesnt update just says update failed I removed the recovery didnt fix the problem either. Is there a flashable 4.5.5.1 apollo zip? I tried changing the bin to a zip and flashing didnt work said apollo_full instead of apollo as error. Anyone know how to fix it just downloads the update fully then says update failed...
Click to expand...
Click to collapse
Be happy 4.5.5.1 didn't take when SafeStrap recovery was installed; device would have bricked. Assume you used the Safestrap compatible variant of 4.5.2 (here). After flashing that (stock slot only; never use secondary slots in SS v4) reboot device and remove Safestrap recovery via SS app. Power down and boot into stock recovery via <power>+<vol-up> and perform a factory reset (you'll loose all apps/data). Reboot again and initialize FireOS. It should then accept OTA updates.
Be 100% sure Safestrap recovery is uninstalled prior to doing a factory reset.
Curious - why to you want 4.5.5.1? Offers no advantage over 4.5.2 if running custom ROMs. Nor will it automatically update to FireOS v5 as Amazon has no plans to release a v5 update for 3rd gen devices.
Ok I went back to 4.5.2 > installed kingroot > went to safestrap > uninstalled recovery > rebooted to stock recovery and factory reset . Its still doing the same thing it downloads to 100 and doesnt do anything...
I might be selling the device and going to a Nexus 9 so I have to make sure it can update or Im going to lose money on the sale.
DroidDogg said:
Ok I went back to 4.5.2 > installed kingroot > went to safestrap > uninstalled recovery > rebooted to stock recovery and factory reset . Its still doing the same thing it downloads to 100 and doesnt do anything...
Click to expand...
Click to collapse
DroidDogg said:
I might be selling the device and going to a Nexus 9 so I have to make sure it can update or Im going to lose money on the sale.
Click to expand...
Click to collapse
IDK - should work. You can try downloading the latest version of FireOS here; installation instructions here. Also verify OTA apk is installed and properly named (here).
It's likely 4.5.x is the terminal release of FireOS for 3rd gen devices; potential buyers will not be severely disadvantaged on 4.5.2.
OK I tried to update to 4.5.5.1 from 4.5.2 (said it was invalid update) do I need to update sequentially like 4.5.3 first?
Update 1: Tried 4.5.3 said update file not valid again. I'm beginning to think this restore file I found on here that was Safestrap 4.5.2 might be the wrong zip for this device even though it installs...
Update 2: Tried another TWRP 4.5.5, it installed, then I did the same thing again removed SafeStrap. Then factory reset...
Why can't I update to 4.5.5.1 after returning from CM11 this is so frustrating.
DroidDogg said:
OK I tried to update to 4.5.5.1 from 4.5.2 (said it was invalid update) do I need to update sequentially like 4.5.3 first?
Update 1: Tried 4.5.3 said update file not valid again. I'm beginning to think this restore file I found on here that was Safestrap 4.5.2 might be the wrong zip for this device even though it installs...
Update 2: Tried another TWRP 4.5.5, it installed, then I did the same thing again removed SafeStrap. Then factory reset...
Why can't I update to 4.5.5.1 after returning from CM11 this is so frustrating.
Click to expand...
Click to collapse
As previously posted - IDK and I do not think anyone else does either. What I do know is every flash (some which appear questionable) presents another failure opportunity that could yield an unrecoverable device. Keep experimenting and posting results; others will learn from your efforts. Just recognize the risk and know when to say 'good enough'. Pushing from 4.5.2 to 4.5.5.1 buys you no additional capability/functionality/stability at this time.
DroidDogg said:
OK I tried to update to 4.5.5.1 from 4.5.2 (said it was invalid update) do I need to update sequentially like 4.5.3 first?
Update 1: Tried 4.5.3 said update file not valid again. I'm beginning to think this restore file I found on here that was Safestrap 4.5.2 might be the wrong zip for this device even though it installs...
Update 2: Tried another TWRP 4.5.5, it installed, then I did the same thing again removed SafeStrap. Then factory reset...
Why can't I update to 4.5.5.1 after returning from CM11 this is so frustrating.
Click to expand...
Click to collapse
Do you checked if the DeviceSoftwareOTA.apk is there? (which @Davey126 mentioned above).
I was in the same situation and had to rename it back, which I'd renamed before as described in the OTA blocking tutorial. http://forum.xda-developers.com/showpost.php?p=59160158&postcount=1
DroidDogg said:
OK I tried to update to 4.5.5.1 from 4.5.2 (said it was invalid update) do I need to update sequentially like 4.5.3 first?
Update 1: Tried 4.5.3 said update file not valid again. I'm beginning to think this restore file I found on here that was Safestrap 4.5.2 might be the wrong zip for this device even though it installs...
Update 2: Tried another TWRP 4.5.5, it installed, then I did the same thing again removed SafeStrap. Then factory reset...
Why can't I update to 4.5.5.1 after returning from CM11 this is so frustrating.
Click to expand...
Click to collapse
did you ever figure this out? i'm in the same boat right now, except i don't even know how to remove the recovery. i'm running safestrap 4.01 and fire rom 4.5.2. I saw another post here http://forum.xda-developers.com/showpost.php?p=49687774&postcount=9 but i'm not quite sure if it will work ( i just don't want to brick my kindle). I got it unrooted but that is about it
mzk1 said:
did you ever figure this out? i'm in the same boat right now, except i don't even know how to remove the recovery. i'm running safestrap 4.01 and fire rom 4.5.2. I saw another post here http://forum.xda-developers.com/showpost.php?p=49687774&postcount=9 but i'm not quite sure if it will work ( i just don't want to brick my kindle). I got it unrooted but that is about it
Click to expand...
Click to collapse
Ignore that post; dangerous to futz with build.prop on this device. Try the following:
- reroot (yes, this is necessary)
- browse to /system/priv-app/ and search for DeviceSoftwareOTA.???, where '???' is likely 'bak' but could be any series of characters
- rename above file to DeviceSoftwareOTA.apk (this is the app {likely one of several} that handles OTA updates on FireOS v4)
- reboot again
- verify device is registered with Amazon
- check every 10-15 min for availability of OTA update; it will almost certainly be 4.5.5.1; allow the update to proceed
Davey126 said:
Ignore that post; dangerous to futz with build.prop on this device. Try the following:
- reroot (yes, this is necessary)
- browse to /system/priv-app/ and search for DeviceSoftwareOTA.???, where '???' is likely 'bak' but could be any series of characters
- rename above file to DeviceSoftwareOTA.apk (this is the app {likely one of several} that handles OTA updates on FireOS v4)
- reboot again
- verify device is registered with Amazon
- check every 10-15 min for availability of OTA update; it will almost certainly be 4.5.5.1; allow the update to proceed
Click to expand...
Click to collapse
Thanks for the steps but I've tried that already. The kindle does find the update but only to 4.5.3. It downloads it and then does nothing. just stays there. It might give an error after a while and go back to where it checks for updates. I tried to side load the newest rom which I have manually downloaded from amazon, the tablet recognized it at first but then gave me an error. Is it crucial to remove the recovery in order to obtain the update?
mzk1 said:
Thanks for the steps but I've tried that already. The kindle does find the update but only to 4.5.3. It downloads it and then does nothing. just stays there. It might give an error after a while and go back to where it checks for updates. I tried to side load the newest rom which I have manually downloaded from amazon, the tablet recognized it at first but then gave me an error. Is it crucial to remove the recovery in order to obtain the update?
Click to expand...
Click to collapse
If you are referring to Safestrap v4 recovery then absolutely yes. The app itself can stay but recovery must be removed (uninstalled). Lucky you didn't score a brick trying to update FireOS with Safestrap recovery installed.
Davey126 said:
If you are referring to Safestrap v4 recovery then absolutely yes. The app itself can stay but recovery must be removed (uninstalled). Lucky you didn't score a brick trying to update FireOS with Safestrap recovery installed.
Click to expand...
Click to collapse
I got to the step where everything is ready to go. the device has been reset to factory default, safestrap recovery has been uninstalled. the device got registered in amazon store and found an update 4.5.3 but it still can't flash it after downloading. I copied the newest 4.5.5 bin file to the tablet, but when i tried to hit update I got a message: unable to complete update because the update file is not valid. please try downloading file again. Right now I'm on the 13.4.5.2 rom which I got here http://forum.xda-developers.com/kindle-fire-hdx/development/hdx-stock-images-pre-rooted-updates-t2911954. Is there any other ideas on how to make update to work?
should I just edit buildprop for downgrade? i will need root for that. Can you advise, please
mzk1 said:
I got to the step where everything is ready to go. the device has been reset to factory default, safestrap recovery has been uninstalled. the device got registered in amazon store and found an update 4.5.3 but it still can't flash it after downloading. I copied the newest 4.5.5 bin file to the tablet, but when i tried to hit update I got a message: unable to complete update because the update file is not valid. please try downloading file again. Right now I'm on the 13.4.5.2 rom which I got here http://forum.xda-developers.com/kindle-fire-hdx/development/hdx-stock-images-pre-rooted-updates-t2911954. Is there any other ideas on how to make update to work?
should I just edit buildprop for downgrade? i will need root for that. Can you advise, please
Click to expand...
Click to collapse
Four choices:
- Modify build.prop, attempt a downgrade and brick your device. Go ahead, I'll wait ...
tip: relying on uncollaborated guidance in a three year old post is rarely best practice
- Root, reinstall Safestrap v4 + CM/Nexus and leave well enough alone. Your device works. Upgrading is not all it's cracked up to be. Kinda like that sweet looking honey/hunk in the bar on a foggy Saturday night.
- As above but reflash the Safestrap compatible (no other) version of FireOS 13.4.5.2. Possible something didn't go well the first time around which is preventing OTAs from being processed correctly. AFAIK - OTA is the only path to 4.5.5.1 as Amazon only offers 4.5.5 for download.
- Attempt a rollback to 3.2.8 followed by an immediate upgrade to 13.4.5.2 as documented here. This path is both the riskiest and the one most likely to clear whatever is blocking OTA updates. If you choose this option be sure to follow instructions exactly including linked files (not others you may have lying around). It is essential WiFi remain off (airplane/flight mode engaged) during the brief window your device is on 13.3.2.8. If an OTA update arrives on this version the device will hard brick with NO possible recovery.
Davey126 said:
Four choices:
- Modify build.prop, attempt a downgrade and brick your device. Go ahead, I'll wait ...
tip: relying on uncollaborated guidance in a three year old post is rarely best practice
- Root, reinstall Safestrap v4 + CM/Nexus and leave well enough alone. Your device works. Upgrading is not all it's cracked up to be. Kinda like that sweet looking honey/hunk in the bar on a foggy Saturday night.
- As above but reflash the Safestrap compatible (no other) version of FireOS 13.4.5.2. Possible something didn't go well the first time around which is preventing OTAs from being processed correctly. AFAIK - OTA is the only path to 4.5.5.1 as Amazon only offers 4.5.5 for download.
- Attempt a rollback to 3.2.8 followed by an immediate upgrade to 13.4.5.2 as documented here. This path is both the riskiest and the one most likely to clear whatever is blocking OTA updates. If you choose this option be sure to follow instructions exactly including linked files (not others you may have lying around). It is essential WiFi remain off (airplane/flight mode engaged) during the brief window your device is on 13.3.2.8. If an OTA update arrives on this version the device will hard brick with NO possible recovery.
Click to expand...
Click to collapse
thanks for the solutions. I figured since it is such a pain to get it to work I'll just stick with Nexus ROM now.
mzk1 said:
thanks for the solutions. I figured since it is such a pain to get it to work I'll just stick with Nexus ROM now.
Click to expand...
Click to collapse
Yep - that would be my choice too. Take note there are two Nexus builds, one for devices that have a 4.5.5.1 kernel, the other for older kernels. Try the former first as it as actively maintained and has a broader feature set. Links below:
old: http://forum.xda-developers.com/kindle-fire-hdx/development/rom-hdx-nexus-v4-0-1-t3125808
new: http://forum.xda-developers.com/kindle-fire-hdx/orig-development/rom-fire-nexus-rom-ktu84q-t3322931
I picked up a second hand Galaxy S8 over the summer with plans to root it and install a custom ROM. I haven't activated it yet, but I was using it on my home WiFi and was notified that it downloaded an OTA update and it would be installed on the next boot. Since then I haven't touched it because I know that some updates can complicate or nullify the ability to root or install a custom bootloader, ROM, etc. I've done some searches on how to prevent the install, but haven't found anything except for how to disable your phone from downloading it to begin with. Now that the update is downloaded to my phone, is there a way to halt it's installation before I move forward with activation and customization?
I think you can let the OTA install, this because an OTA only affects Android OS and not device's bootloader .
jwoegerbauer said:
I think you can let the OTA install, this because an OTA only affects Android OS and not device's bootloader .
Click to expand...
Click to collapse
Thanks, I've heard different in the past. That OTA updates can lock you out of being able to run certain bootloaders for multiboot and such.
bump for input from others
Downloaded one S8 ota zip and checked. According to install-recovery.sh the command and path to fota package is on cache.
So going into recovery and wiping cache should do it.
edit: then again it might write it back on boot... but does it install it right away? IDK. Factory reset?