Database Info

One failed update, now? No more OTA?

I'm at wit's end here...
I had to get a replacement TF300, and it came with .26. I downgraded to .17, rooted, OTA Rootkeeper'ed SU, then accepted the OTA update.
The update FAILED (green robot with red ! above). I powered down, rebooted.
Since then, I cannot get my device to find any OTA updates. I tried manually installing .29 - then no update. I installed .30 manually .. no update to JB.
I've force stopped DMClient and CMClient - cleared data/cache and cold booted as directed from some other posts.
Still no OTA.
While I realize I can do manual updates from this point forward, I'd like JB back - and so far, no manual installer of that.
I appreciate any help - this is making me nuts.

darkuni said:
I'm at wit's end here...
I had to get a replacement TF300, and it came with .26. I downgraded to .17, rooted, OTA Rootkeeper'ed SU, then accepted the OTA update.
The update FAILED (green robot with red ! above). I powered down, rebooted.
Since then, I cannot get my device to find any OTA updates. I tried manually installing .29 - then no update. I installed .30 manually .. no update to JB.
I've force stopped DMClient and CMClient - cleared data/cache and cold booted as directed from some other posts.
Still no OTA.
While I realize I can do manual updates from this point forward, I'd like JB back - and so far, no manual installer of that.
I appreciate any help - this is making me nuts.
Click to expand...
Click to collapse
im in the same boat as you i would also like help

joeyman08 said:
im in the same boat as you i would also like help
Click to expand...
Click to collapse
I am also in the same boat as I have an unlocked bootloader and will no longer receive OTA's from ASUS. We just have to be patient for another day or 2 and ASUS will post the JB Firmware on their site here:
http://support.asus.com/download.as...er Pad TF300T&os=32&hashedid=8BmzkQ4yoz5WzBrW
---------- Post added at 10:17 AM ---------- Previous post was at 10:11 AM ----------
But who wants to be patient. THere is always the option of updating manually. Thank krabappel2548 for this one!
http://forum.xda-developers.com/showthread.php?t=1845377

I will give the manual update a go. Thanks!

The manual process requires unlocking the bootloader. Not sure I'm ready to do that.
I'm open to other options.

darkuni said:
The manual process requires unlocking the bootloader. Not sure I'm ready to do that.
I'm open to other options.
Click to expand...
Click to collapse
Don't do all that crap. Do this. I did. Others as well.
Reference: http://forum.xda-developers.com/showthread.php?t=1840540
1) Found the correct OTA file. Someone posted it here for my US MODEL. If your WW or JP or something else, you'll need a different file.
http://forum.xda-developers.com/show...840397&page=11
2) I downloaded that file, named it dlpkgfile and put it in /cache/ (I also kept a copy in /sdcard so I can simply recopy it if/when it failed to update because of some missing app or something again)
3) I created a file called 'command' and put it in /cache/recovery with the contents of that file being as follows(without quotes): "--update_package=/cache/dlpkgfile". (I also kept a copy in /sdcard so I can simply recopy it if/when it failed to update because of some missing app or something again)
4) Now just run the update. To do this, make sure you do all your prep work (Voodoo OTA root keeper, supersu binary installed and run at least once, all original system apps in place. yada yada yada. To run the update shut down your tf300. and then start it holding the POWER and VOLUME DOWN. Keep holding it until you see writing appear. when the writing appears release and press VOLUME UP within 5 seconds of those words appearing.
5) you'll see the normal asus upgrade spin up.... and either complete or fail. If it fails, check your log file in /cache/recovery and see WHY it failed. Fix why it failed, and restart from step 1.

We have a winner! I had the command and dlpkg file ... what I didn't have was the boot process to enact it.
WONDERFUL! I'm safe for one more update

TF700 - Lost OTAs

About the time JB was released I checked for an update not realising that it would go ahead without confirmation. As I didn't want to update just then I cancelled the download by clearing data in CM & DMclient (seemed to be the only way after turning wifi off).
Recently I just rooted (locked) using the debugfs method, after which checking for updates comes back with a zilch.
I tried clearing DM/CMclient data again and removing the update files :
fw_update_progress & isp_fw_progress
These had java errors in them presumably because I had aborted. After trying again they hold "0" and "100" in text format.
Finally on someone's recommendation I did a full factory reset (which worked for him) but I'm still without OTAs.
I'm hoping someone can shed some light on what may be the problem. AFAIK just rooting doesn't kill OTAs yet something has. Does Asus perhaps keep a database record as to what has been downloaded? I somehow doubt it but with a full factory reset I fail to see what's stopping these updates.
Any help , suggestions appreciated.

I dont know if the OTA is operational again, but a lot of people like myself never received any automatic updates for a brand new stock infinity on the 11th. You might might want to try a manual update. Here is my post on the other threads on what I did to manual update to 4.1.1.
"I just returned a prime today that I bought for a friend in exchange for a C8 infinity. Tablet didnt want to update to JB and was stuck on 4.0.3. So I used my laptop and went to the Asus support download site, download 4.1.1 US version, unzipped it and another zipped file came up, Plugged the infinity to the laptop via Asus cable, copied the second zipped file into the main directory I think it was /mnt/sdcard, Rebooted and the exclamation sign came up and installed the new 4.1.1. Then went back and deleted the file that I copied on to the main directory. Dont need an sdcard to manually update. "

junrider said:
I dont know if the OTA is operational again, but a lot of people like myself never received any automatic updates for a brand new stock infinity on the 11th. You might might want to try a manual update. Here is my post on the other threads on what I did to manual update to 4.1.1.
"I just returned a prime today that I bought for a friend in exchange for a C8 infinity. Tablet didnt want to update to JB and was stuck on 4.0.3. So I used my laptop and went to the Asus support download site, download 4.1.1 US version, unzipped it and another zipped file came up, Plugged the infinity to the laptop via Asus cable, copied the second zipped file into the main directory I think it was /mnt/sdcard, Rebooted and the exclamation sign came up and installed the new 4.1.1. Then went back and deleted the file that I copied on to the main directory. Dont need an sdcard to manually update. "
Click to expand...
Click to collapse
Yes I was aware of cases where OTAs never happened from the beginning but they did work for me . I had a pre-JB update and then the JB update itself which I aborted. So I think this is a slightly different case.

louiscar said:
Yes I was aware of cases where OTAs never happened from the beginning but they did work for me . I had a pre-JB update and then the JB update itself which I aborted. So I think this is a slightly different case.
Click to expand...
Click to collapse
I believe after a sucessful download OTA, Asus marked your ID, so you will not able to receive OTA again, the only way now is you have to do it manually.

buhohitr said:
I believe after a sucessful download OTA, Asus marked your ID, so you will not able to receive OTA again, the only way now is you have to do it manually.
Click to expand...
Click to collapse
Right, I've been trying to confirm if this is the case and how Asus do their OTAs. Thing is though, I aborted the download so it should have detected that the OTA was unsuccessful.

louiscar said:
Right, I've been trying to confirm if this is the case and how Asus do their OTAs. Thing is though, I aborted the download so it should have detected that the OTA was unsuccessful.
Click to expand...
Click to collapse
Here is how to update manually when OTA failed to update:
1. Download dlpkgfile.bin (US version)
http://www.mediafire.com/?2ctnjai5b68c7im
2. Rename dlpkgfile.bin to dlpkgfile then copy the dlpkgfile to /cache then set permissions to rw-r-r.
3. Download command file:
http://www.mediafire.com/?yq1bt16mnm7tc8d
4. Unzip and copy the "command" file to /cache/recovery, then set the file's permissions to rw-r-r.
5. Temp-unroot if you want to keep your root with OTA Root Keeper.(skip this if you already done this)
6. Power off.
7. Reboot holding power on and volume down, when you see white text message on the screen release both buttons
8. Press power up to confirm recovery mode.
9. Update will install and upgrade your device.
10. Once done, use OTA root keeper to restore root.
11. If you want to switch to superSU, you can download superSU, launch the app, verify it's working, then you can un install superuser.

buhohitr said:
Here is how to update manually when OTA failed to update:
1. Download dlpkgfile.bin (US version)
http://www.mediafire.com/?2ctnjai5b68c7im
2. Rename dlpkgfile.bin to dlpkgfile then copy the dlpkgfile to /cache then set permissions to rw-r-r.
3. Download command file:
http://www.mediafire.com/?yq1bt16mnm7tc8d
4. Unzip and copy the "command" file to /cache/recovery, then set the file's permissions to rw-r-r.
5. Temp-unroot if you want to keep your root with OTA Root Keeper.(skip this if you already done this)
6. Power off.
7. Reboot holding power on and volume down, when you see white text message on the screen release both buttons
8. Press power up to confirm recovery mode.
9. Update will install and upgrade your device.
10. Once done, use OTA root keeper to restore root.
11. If you want to switch to superSU, you can download superSU, launch the app, verify it's working, then you can un install superuser.
Click to expand...
Click to collapse
Thanks, yes I have already done that. I've also emailed Asus to try to get something sorted for future updates. I'm not sure if updating JB in this way will restore the OTAs. Asus' reply so far has been to tell me to clear DMclient data and I've just replied to tell them I've done that many times already. I'll see what transpires.

louiscar said:
Thanks, yes I have already done that. I've also emailed Asus to try to get something sorted for future updates. I'm not sure if updating JB in this way will restore the OTAs. Asus' reply so far has been to tell me to clear DMclient data and I've just replied to tell them I've done that many times already. I'll see what transpires.
Click to expand...
Click to collapse
Thank you for the update. I believe the issue is with their update servers. I had help people with brand new tf700 without receiving update, so it's not the tablet and it's not software or configuration related.

buhohitr said:
Thank you for the update. I believe the issue is with their update servers. I had help people with brand new tf700 without receiving update, so it's not the tablet and it's not software or configuration related.
Click to expand...
Click to collapse
Ok I will report here if I get anywhere with them. I somehow suspect that their support may not even realise or understand the issue but I will persist and see if I can get some kind of acknowledgment about their servers.

Well my OTA resumed after updating to JB so I think that it's as you state, the datebase on their servers. I don't know what the update was but your post in another thread would probably confirm this was JB .18. I guess once they have pushed an OTA, regardless of whether it was successful or not they don't seem to do it again. Which means I need to collect the dlpkgfile for each JB update given that I need to go back to ICS to do a proper factory reset and retain root.

v4.4.4 won't install... gets half way with error!

Trying to install v4.4.4 on my stock --not developer edition-- Droid Ultra. It is currently running v.4.4.2 (19.6.3.obake).
After the download, the phone reboots, gets about half-way through and stops with a message "error!". No other info provided. So far, the MFN doesn't have any answers.
Does anyone have any ideas on how to get this installed?
I have:
-reset to factory specs (via menu with phone booted up) and tried the install
-reset (via vol down, power) to factory specs and tried the install
Always ends with "error!" ..... thanks for any help.

Have you tried to RSD and keep data? I had that problem on the first update and that's what finally fixed it.

beelow319 said:
Have you tried to RSD and keep data? I had that problem on the first update and that's what finally fixed it.
Click to expand...
Click to collapse
Can you offer up the steps to do that? I know how to do a factory reset, but that will wipe the data. Thanks.

Go here: http://forum.xda-developers.com/showthread.php?t=2450702
Super easy to do

newtoncd said:
Trying to install v4.4.4 on my stock --not developer edition-- Droid Ultra. It is currently running v.4.4.2 (19.6.3.obake).
After the download, the phone reboots, gets about half-way through and stops with a message "error!". No other info provided. So far, the MFN doesn't have any answers.
Does anyone have any ideas on how to get this installed?
I have:
-reset to factory specs (via menu with phone booted up) and tried the install
-reset (via vol down, power) to factory specs and tried the install
Always ends with "error!" ..... thanks for any help.
Click to expand...
Click to collapse
Are you, or have you been rooted in the past?

rmjones2006 said:
Are you, or have you been rooted in the past?
Click to expand...
Click to collapse
No, have never been rooted.
The only thing I have ever done is update the radios (adb) ...
for beelow319, am trying the houseofmoto steps now. thanks, will report back.

beelow319 said:
Go here: http://forum.xda-developers.com/showthread.php?t=2450702
Super easy to do
Click to expand...
Click to collapse
May I just say, thank you very much.
That worked ... I am now running v4.4.4 .... and you are right, that was very easy.
Too bad I had already wiped my phone twice ... ugh ... again, thank you!

newtoncd said:
No, have never been rooted.
The only thing I have ever done is update the radios (adb) ...
for beelow319, am trying the houseofmoto steps now. thanks, will report back.
Click to expand...
Click to collapse
Updating the radios is surely what caused your problem.
The OTAs are usually patches to existing files, not replacements. That keeps them smaller.
If you open the OTA file and read through the updater script, you'll see that the first thing it does is run a hash against every file it will be updating. It's making sure that every file is stock, exactly they way the patch needs it to be to be successful. Without a check, it could patch a file with changes that break the file and therefore your phone.
In this OTA, the very last thing checked is the modem (radio). Since your was not the 4.4 radio it was looking for, it stops the update before anything at all is patched.
It took so long to get there because there are about 1000 files it checks, if I counted correctly.
You hadn't even reached the actual update part of the update.

distortedloop said:
Updating the radios is surely what caused your problem.
The OTAs are usually patches to existing files, not replacements. That keeps them smaller.
If you open the OTA file and read through the updater script, you'll see that the first thing it does is run a hash against every file it will be updating. It's making sure that every file is stock, exactly they way the patch needs it to be to be successful. Without a check, it could patch a file with changes that break the file and therefore your phone.
In this OTA, the very last thing checked is the modem (radio). Since your was not the 4.4 radio it was looking for, it stops the update before anything at all is patched.
It took so long to get there because there are about 1000 files it checks, if I counted correctly.
You hadn't even reached the actual update part of the update.
Click to expand...
Click to collapse
I had replaced the radios with stock before trying to update to v4.4.4 .... when that didn't work, I thought the reset to factory specs would take care of that; no joy.
In the end, I love the HouseofMoto program .... that was really easy.

Need help from the Masters!!! New OTA update!

Hi,
I'm kind of a newbie with phones but good with computers so:
I used the following Fix for the call volume issue on my OPO:
https://forums.oneplus.net/threads/tool-jlouder-v1-0-rc2-makes-your-phone-call-louder.69733/
Seems that because of this Fix I get an error when trying to run the the update OTA or sideloading.
I get following error:
E error in tmp sideload package.zip status 7 installation aborted
Others who have used this fix have same issues. Any easy way out??? I'm not rooted and otherwise stock.
"I think it's the volume fix that changes the md5 checksum on the xml file and therefore kills the update."
Thanks In Advance,
Ken

kenfb1 said:
Hi,
I'm kind of a newbie with phones but good with computers so:
I used the following Fix for the call volume issue on my OPO:
https://forums.oneplus.net/threads/tool-jlouder-v1-0-rc2-makes-your-phone-call-louder.69733/
Seems that because of this Fix I get an error when trying to run the the update OTA or sideloading.
I get following error:
E error in tmp sideload package.zip status 7 installation aborted
Others who have used this fix have same issues. Any easy way out??? I'm not rooted and otherwise stock.
"I think it's the volume fix that changes the md5 checksum on the xml file and therefore kills the update."
Thanks In Advance,
Ken
Click to expand...
Click to collapse
Don't you have a stock backup?
If you don't, have you tried reverting the values?

Wait... if you're not rooted then how did you perform the change in the file in the first place? Did you root, do the change and then unroot?
Like what badjoras said, revert back to the stock file and then apply the OTA.
I haven't followed up on the whole OTA readings, but there are zips out there that will bypass the check of the files. You can try looking into those as well.

zephiK said:
Wait... if you're not rooted then how did you perform the change in the file in the first place? Did you root, do the change and then unroot?
Like what badjoras said, revert back to the stock file and then apply the OTA.
I haven't followed up on the whole OTA readings, but there are zips out there that will bypass the check of the files. You can try looking into those as well.
Click to expand...
Click to collapse
Hi,
Not rooted, I just followed the steps in the fix I posted above.
To revert back to stock file, will that wipe all data? Don't want that.
I'm not great at the phone stuff yet , still learning but trying to be careful.
Can I sideload the previous version without losing data??
Recovery on this phone option is "wipe data factory reset???"
Sorry for being a dummy, it's a big learning curve for me,
Thanks, Ken

Hi
kenfb1 said:
Hi,
Not rooted, I just followed the steps in the fix I posted above.
To revert back to stock file, will that wipe all data? Don't want that.
I'm not great at the phone stuff yet , still learning but trying to be careful.
Can I sideload the previous version without losing data??
Recovery on this phone option is "wipe data factory reset???"
Sorry for being a dummy, it's a big learning curve for me,
Thanks, Ken
Click to expand...
Click to collapse
Hi,
After trying several options, I'm still in Limbo with this.
Can't get the update to install, still looking for ideas.
Ken

Possible Root

Okay so as the fire just updated to 5.4.0.0 and now 5.4.1.0 this means there is an exploit somewhere. If it doesnt have a changelog, Amazon probably increased security.
I would recommend getting No Root Firewall of the play store. Block internet for all amazon apps except Amazon Downloader, and Google play services (this could show as an Amazon app)(This prevents auto updates)
When an update comes out with no changelog DO NOT UPDATE TO IT. AmazonFresh this when they find an error. And an error could mean possible root.
If you did the steps above you shouldn't be receiving updates, there for meaning, you have the possibility of root.

Cancel Update?
Hi,
I installed Netguard and blocked System Update and some Alex services.
At first that kept system updates from connecting and it said: "can't check update" or something.
10 Minutes later suddenly the 5.6.0.0 update shows up and it says it will install when inactive.
What can I do to prevent it from updating?
Running 5.4.0.1
P.S.
Kingroot still not working,
"rm -f /sdcard/Android/data/com.amazon.device.software.ota/files/*.bin" did nothing (no files)
"rm -rf /cache/*" gives 'Permission denied'
using adb shell

Has anyone tried the root yet?
https://forum.xda-developers.com/apps/framaroot/root-framaroot-one-click-apk-to-root-t2130276

0v3rdr1v3 said:
Has anyone tried the root yet?
https://forum.xda-developers.com/apps/framaroot/root-framaroot-one-click-apk-to-root-t2130276
Click to expand...
Click to collapse
The last comment on that post is from 2016. It says:
"This root method is no longer supported and does not work on recent devices. Thread closed."

lehnin said:
Hi,
I installed Netguard and blocked System Update and some Alex services.
At first that kept system updates from connecting and it said: "can't check update" or something.
10 Minutes later suddenly the 5.6.0.0 update shows up and it says it will install when inactive.
What can I do to prevent it from updating?
Running 5.4.0.1
P.S.
Kingroot still not working,
"rm -f /sdcard/Android/data/com.amazon.device.software.ota/files/*.bin" did nothing (no files)
"rm -rf /cache/*" gives 'Permission denied'
using adb shell
Click to expand...
Click to collapse
Hmm, maybe PM clear <packagename>

sorry new guy here...
thefanum said:
The last comment on that post is from 2016. It says:
"This root method is no longer supported and does not work on recent devices. Thread closed."
Click to expand...
Click to collapse
Does this mean that rooting these is NEVER going to be a possibility? Or a new method is being developed and is not out yet? Also I have 2 HD 8's, one is on 5.6 and the other is on 5.4.0.1. Does the factory reset bring it back to 5.4.0.1?

Aethernoob said:
Does this mean that rooting these is NEVER going to be a possibility? Or a new method is being developed and is not out yet? Also I have 2 HD 8's, one is on 5.6 and the other is on 5.4.0.1. Does the factory reset bring it back to 5.4.0.1?
Click to expand...
Click to collapse
These have been out for months without a root solution. I would guess it could easily be months more before we find a solution. Or longer, if at all.
Factory resetting will not downgrade your firmware ever on any device. Do not attempt to downgrade manually, as it would brick it.
If you factory reset, it will try to auto update as soon as you connect to WiFi. If you set it up without network access, and then remote the OTA feature, it may not upgrade the firmware. I just did exactly this, and it went fine. But there's no room for error.
Your best bet for root is to block OTA's and wait. As far as we know, there is no root method even under development currently. Although, if I were working on one, I sure wouldn't tell anyone, and get "ETA'd" to death.

[QUOTE="thefanum, post: 74729008, member: 4404866"]These have been out for months without a root solution. I wo
thefanum said:
These have been out for months without a root solution. I would guess it could easily be months more before we find a solution. Or longer, if at all.
Factory resetting will not downgrade your firmware ever on any device. Do not attempt to downgrade manually, as it would brick it.
If you factory reset, it will try to auto update as soon as you connect to WiFi. If you set it up without network access, and then remote the OTA feature, it may not upgrade the firmware. I just did exactly this, and it went fine. But there's no room for error.
Your best bet for root is to block OTA's and wait. As far as we know, there is no root method even under development currently. Although, if I were working on one, I sure wouldn't tell anyone, and get "ETA'd" to death.
Click to expand...
Click to collapse
Being super green in this field if you "brick" it and then "unbrick" it will that just fastboot it back to factory set points? Also is there a glossary for all these acronyms... it would be glorious if there was!!!

Aethernoob said:
Being super green in this field if you "brick" it and then "unbrick" it will that just fastboot it back to factory set points? Also is there a glossary for all these acronyms... it would be glorious if there was!!!
Click to expand...
Click to collapse
Brick means physically broken, usually forever. As in, your tablet is now as useful as a brick. There are soft bricks where just the firmware is broken, but can be fixed by reflashing (still won't downgrade). But we're taking about a full brick. As in, you destroy your tablet and have to buy a new one.