Not receiving OTA updates! - Eee Pad Transformer Q&A, Help & Troubleshooting

I downgraded my TFT101 to WW_epad-user-9.2.1.11 in order to root it and update it after that.
It allways worked for me, this is not the first time i do it, but the problem is now that i'm not seeing OTA updates.
What can i do? I've already done factory reset a couple times and forced closed and delete data of CMClient and DMClient but it isn't working.
What can i do???

Well let me play de guessing game .
I think sometimes it has been told that Asus kind of controls every update sent to every tablet. So maybe they could have your tablet listed as updated and so you are not receiving OTA. I don't know if it is that way, just guessing.
Anyway you can DL your desired update from asus web, put it on a SD and manually update your TF. On the same page you have the download you have a PDF that explains how to do it

CalvinH said:
Well let me play de guessing game .
I think sometimes it has been told that Asus kind of controls every update sent to every tablet. So maybe they could have your tablet listed as updated and so you are not receiving OTA. I don't know if it is that way, just guessing.
Anyway you can DL your desired update from asus web, put it on a SD and manually update your TF. On the same page you have the download you have a PDF that explains how to do it
Click to expand...
Click to collapse
make a little bit of sense... since my whole story is:
i saw the newest OTA yesterday and i tried to install it but it got stuck because the tablet wasn't plugged in to AC.
After that i didn't receive anymore OTAs so that's why i downgraded thinkin that would solve it...
But if ASUS controls every update how could i've done this same process without problems in the past?

Related

[Q] Please help me with missing update

I got my Transformer yesterday, and I'm still discovering all its features.
But I'm having a little problem...
My unit when I turned it on for the first time was missing some apps, like MyDesktop.
Also, I was experiencing some issued which I believe were fixed, like MyNet being in Spanish instead of English (I'm Italian but I use English on all my systems)
I thought it wasn't fully updated, went to Settings->About Tablet->System Update, and checked for updates.
The result was (and still is) "There is no update currently available for your device"
Any ideas?
Hi, I have been trying to update my Transformer for the past couple of days with the same results, no update found I can only think that either the server is busy or the update has been removed temporarily.
Neil
bobcollege said:
Hi, I have been trying to update my Transformer for the past couple of days with the same results, no update found I can only think that either the server is busy or the update has been removed temporarily.
Neil
Click to expand...
Click to collapse
Thanks, Neil.
Knowing that I'm not the only one having this issue at least calms a bit the fear that something isn't working on my side.
Let's hope we manage to update as soon as possible - I'd really like to check the new stuff
Have you tried clearing the caches for all the system and Asus apps in the settings, rebooted, and then attempted the update again? Or a full reset?
If i were you two i would seriously consider rooting it and apply the update via the rooted update in the android development thread. Just my .02$
stuntdouble said:
Have you tried clearing the caches for all the system and Asus apps in the settings, rebooted, and then attempted the update again? Or a full reset?
Click to expand...
Click to collapse
Yup, cleared the cache for all the apps, rebooted, and... same result.
I haven't done a complete restore to factory settings yet, but yesterday I tried the update as soon as I turned the thing on, before installing anything, so that should be as close to factory settings as possible.
dcmtnbkr said:
If i were you two i would seriously consider rooting it and apply the update via the rooted update in the android development thread. Just my .02$
Click to expand...
Click to collapse
Actually, I'm a bit scared about rooting the device. I know I won't install alternative OS's and I'll never tamper with the system innards, so rooting is not really a priority for me.
Meanwhile, I've also dropped a note to Asus support, let's see if they can shed some light...
PublicJohnDoe said:
Actually, I'm a bit scared about rooting the device. I know I won't install alternative OS's and I'll never tamper with the system innards, so rooting is not really a priority for me.
Meanwhile, I've also dropped a note to Asus support, let's see if they can shed some light...
Click to expand...
Click to collapse
That's fair, I like to tinker a lot Hopefully asus sheds some light. Enjoy the new device!
dcmtnbkr said:
If i were you two i would seriously consider rooting it and apply the update via the rooted update in the android development thread. Just my .02$
Click to expand...
Click to collapse
I did see the post for the ota rooted stock rom, guess i will have a tinker with that or maybe the one on modaco forums. Lets see how easy it is first
Neil
In the end the update (the new one, Apr 26) did come through!!!

Stop Jellybean Update

Honest ive been searching for an hour, how do i stop the update from happening. Not permanently, hopefully like blocking the update app with Titanium like i did on my Galaxy S3. Also, the location of the already downloaded file so i can delete it. Thanks
Honestly!!?? Is this really that dumb of a question? I honestly still cant find how to block the JB update. Please anybody?
I would love to know that too. I really don't want to hit the update by mistake...
Honestly, just make sure you honestly don't click the update button. Honestly that's all there honestly is to it...honest!:laugh:
Honestly
The update file (dlpkgfile) is in the/cache/ folder.
And I don't know if this will stop the OTA or if this will completely F up your device but the Dmclient (or is it cmclient) system app can probably be disabled. It handles the OTA's
After some research I found that renaming otacerts.zip (in /system/etc/security/) with a .bak at the end could prevent the update to start but the notification is still here.
I tried to stop the Firmware Update Utility in app manager, even by renaming it with a .bak in /system/app/ . The notification is still here, but it seems that the popping window is not showing. Time will tell.
I saw somewhere that renaming the fingerprint line in build.prop woud work, luring the update into thinking the firmware is already up to date, but since I never touched this file (android newbie here!) I will wait for someone more experienced in modifying that kind of things...
If you are rooted, edit your build.prop (back up your original) and then tell the tablet to update. The update will fail (red triangle) and will reboot into ICS. The notification should go away and you will have to update manually.
Ok but what to edit in build.prop?
Gamlus said:
Ok but what to edit in build.prop?
Click to expand...
Click to collapse
Check this thread in the development section. There is a tweaked build.prop that I used before my upgrade. That is what caused my OTA update to fail. BE sure to use the correct file and back up your current build.prop.
http://forum.xda-developers.com/showthread.php?t=1641219
Yes !
I didn't actually changed the whole build.prop, but I downloaded the stock JB build.prop to take the fingerprint line.
So, after a backup of my build.prop, I changed this line :
ro.build.fingerprint=asus/WW_epad/EeePad:4.0.3/IML74K/WW_epad-9.4.3.30-20120604:user/release-keys
With this one :
ro.build.fingerprint=asus/WW_epad/EeePad:4.1.1/JRO03C/WW_epad-10.4.2.9-20120809:user/release-keys
And now, no more notification, after a reboot and a failed install of JB.
Thank you !
turdbogls said:
The update file (dlpkgfile) is in the/cache/ folder.
And I don't know if this will stop the OTA or if this will completely F up your device but the Dmclient (or is it cmclient) system app can probably be disabled. It handles the OTA's
Click to expand...
Click to collapse
ok guys this does work, first remove the update file, then use a root system app freezer and freeze dmclient, reboot, if this does not work, unfreeze dmclient, then change your build.prop to show the blueprint of your asus tf300t or tf300tg tablet on jelly bean, reboot, then freeze dmclient, reboot, and that will remove any chances of getting an OTA or accidentally messing up the device, after this change your build.prop back to original state, reboot, and everything will be gone.
note i have tested the second method, and its working perfectly, no glitches, no FC's
Sent from my ASUS Transformer Pad TF300T using xda app-developers
with my previous returned tf300: after i turned it on the first time it downloaded the ICS .30 firmware and asked me to update, i installed it. then i was curious why it did not download the JB update, so i went to check update manually, it started downloading the jb update and i had to update to jb. after a few days because of hardware problem i returned it.
my new tf300 came yesterday, and the same thing above happened, i updated to ICS .30, now i try to remind myself to not accidentally manually check for update, sounds weird, right? i see cmclient and dmclient always running but it never knows that there's a update lol. and i usually don't go to about tablet so i guess i won't do manual update accidentally.
bige914 said:
ok guys this does work, first remove the update file, then use a root system app freezer and freeze dmclient, reboot, if this does not work, unfreeze dmclient, then change your build.prop to show the blueprint of your asus tf300t or tf300tg tablet on jelly bean, reboot, then freeze dmclient, reboot, and that will remove any chances of getting an OTA or accidentally messing up the device, after this change your build.prop back to original state, reboot, and everything will be gone.
note i have tested the second method, and its working perfectly, no glitches, no FC's
Sent from my ASUS Transformer Pad TF300T using xda app-developers
Click to expand...
Click to collapse
Just wanna say thanks for this. Deleting the update and freezing the dm client with titanium seems to be working. And hasnt caused any other issues as of yet. I think its stupid that we dont have an opt out option if we like the way our tablets are now. We should not be forced to change our tablets that we paid for and OWN!
Gam3r 4 Life said:
Just wanna say thanks for this. Deleting the update and freezing the dm client with titanium seems to be working. And hasnt caused any other issues as of yet. I think its stupid that we dont have an opt out option if we like the way our tablets are now. We should not be forced to change our tablets that we paid for and OWN!
Click to expand...
Click to collapse
Thanks +1
Worked for me too...
neur28 said:
Thanks +1
Worked for me too...
Click to expand...
Click to collapse
Does your stock email app work now? After freezing the DM client the stock email app gets stuck at waiting for sync.
Nevermind. I defrosted the dmclient and email still didnt work. So I rebooted. Saw the update again. So I refroze dmclient, then restored my email app and data in titanium and that fixed it.
I'm glad I helped all of you and enjoy your tablets as I am :3 screw Asus JB update we D block that yo
Sent from my HTC Ruby using xda app-developers app

Moto has apparently released a software update

Per this poster over on S4GRU.com, the new version is 77.8.10.XT897.Sprint.en.US:
http://s4gru.com/index.php?/topic/2507-photon-q-software-update/
Yeah, I had seen someone on the Sprint forums say he got the update last night. He said IM didn't work aterwards, but I wasn't sure if he meant Gtalk, or what.
I am rooted and debloated as well, but from my experience, that shouldn't prevent the device from saying an update is available.... but the update could fail if we try and apply it like this... I always go back to stock unrooted if I wanna install an update.
I think at least one thing they were supposed to address was that VSNCP registratiom error that pops up sometimes, I've seen it pretty much every day, and I've even done the fix of editing my data profile username.
Sent from my XT897 using Xparent ICS Tapatalk 2
Actually, I will be interested to see whether we do receive the update with bootloader unlocked and rooted. I did see Moto say in the FAQs that they are under no obligation to offer updates to unlocked devices. However, that is probably just something they say, and they did also mention the bit about accepting the OTA when rooted/modded causing problems.
Sent from my XT897 using Xparent ICS Tapatalk 2
yogi2010 said:
Actually, I will be interested to see whether we do receive the update with bootloader unlocked and rooted. I did see Moto say in the FAQs that they are under no obligation to offer updates to unlocked devices. However, that is probably just something they say, and they did also mention the bit about accepting the OTA when rooted/modded causing problems.
Sent from my XT897 using Xparent ICS Tapatalk 2
Click to expand...
Click to collapse
any idea is it JB or stil ICS?
Pretty sure its still ICS, I'm sure the guy would have said if it were JB, plus something that significant would have hit the various sites beforehand most likely.
yeah, if it were JB we most probably would have heard about it beforehand. i haven't seen many people with the update yet, today i keep getting 'check for update not available at this time'.
Probably to fix the vsncp error message problem.
i just got off a chat with Sprint, and they said there is no such update currently
unless maybe it was released, then pulled due to bugs?
I woke up to a notification of the update. Size was about 50mb. I pressed 'later' to cancel it, even though it'll fail if I take it since I'm unlocked.
Sent from my XT897 using Tapatalk 2
yogi2010 said:
i just got off a chat with Sprint, and they said there is no such update currently
unless maybe it was released, then pulled due to bugs?
Click to expand...
Click to collapse
The tech was an idiot, I just got the popup notification and was able to click on the link for the release notes.
https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/90757
Yeah, I just got the update notice myself. Thanks!
Gonna install and check it out. Can always revert if it's no good.
Sent from my XT897 using Xparent ICS Tapatalk 2
---------- Post added at 08:11 AM ---------- Previous post was at 08:03 AM ----------
dpwhitty11 said:
I woke up to a notification of the update. Size was about 50mb. I pressed 'later' to cancel it, even though it'll fail if I take it since I'm unlocked.
Sent from my XT897 using Tapatalk 2
Click to expand...
Click to collapse
I'm gonna try restoring the bone-stock backup file, reflashing stock recovery, and then installing the update. From past experience, unlocked bootloader has been ok, it just won't work if your system is rooted/modded.
Sent from my XT897 using Xparent ICS Tapatalk 2
I got the OTA message this morning.
Coming from the shift forum we have learned to never to install OTA updates. However this one looks harmless.
Who knows.. maybe my LTE will start actually working?
Sent from my XT897 using xda app-developers app
anyone do the update with a rooted phone>?
Got the update pushed down around 10:30 am est today.
From the release notes:
Multimedia Texting - Improved MMS texting functionality when the Data Username/NAI has changed to a shorter length
Click to expand...
Click to collapse
This is most likely the data profile extra ".com" fix. I like their wording.
Hey a quick question to everyone. Never really had to deal with Sprint for my epic since XDA had everything I needed but I have gotten very concerned with the information around this and the "VSNCP" stuff. Are the tech's normally this clueless? Is there a quick way to talk to someone that actually knows what they are talking about? They told me I had to get a new phone the other day due to these issues. How could they tell me that if a software update to fix it is going to be release a week later?
ericcire said:
anyone do the update with a rooted phone>?
Click to expand...
Click to collapse
I am rooted and unlocked and the upgrade went through fine. Now I am not rooted anymore, but that shouldnt be hard to fix.
swintec said:
I am rooted and unlocked and the upgrade went through fine. Now I am not rooted anymore, but that shouldnt be hard to fix.
Click to expand...
Click to collapse
I am also rooted (and unlocked, of course you have to be unlocked to be rooted ), but my phone went through a different scenario.
I downloaded the update (was 56MB I believe, somewhere around there. The update is 77.8.10.en.US). Downloaded it via Wi-Fi, then the phone asked if I wanted to install. I pressed Install Now, and it rebooted.
My phone rebooted and went into recovery. I dont remember everything, but it asked if I wanted to install "Unknown.zip", and it had:
No
No
No
No
Yes - Install Unknown.zip
No
No
No
Etc... I clicked No, then it went to the recovery menu (where you have the option to restart the phone, and the other options.. sorry, I've only ever rooted my evo shift so my termoinology is limited). I rebooted the phone via the first option, the phone went through its process, came back up fully, and rebooted by itself! Everything happened again (asking to install the unknown.zip, etc..). Basically, it was in an endless look when I would restart the phone.
First thing I tried was to wipe the Delvik Cache. Did that, rebooted, phone came back up and rebooted by itself again.
Second thing I tried (and I had a feeling I would probably regret this cause it would either brick my phone or unroot it), was to install that Unknown.zip. But that didnt even go through. The install failed (A message appeared at the bottom of the phone along with the other message logs, so I really dont remember exactly what it said. It was just an error message basically).
At this point I didnt know what to do... so I got to the recovery menu (where it said Reboot phone, Advanced, and the other options), and I selected the one that said to Wipe Cache. Not the Delvik cache but the phone cache (I dont think the option said Wipe Cache, but something similar?). Did that, rebooted, and my phone stayed on! The update popped up again, and this time I pressed "Later". Learned my lesson.
I guess the update may be hit or miss for rooted users?
ericcire said:
anyone do the update with a rooted phone>?
Click to expand...
Click to collapse
Yes, clockwork recovery booted up and the update failed.. probably going to flash the stock image..
But my phone says I'm up to date?
Kenneth196 said:
I guess the update may be hit or miss for rooted users?
Click to expand...
Click to collapse
Possibly..I dunno. I used the 2nd method posted only a few weeks ago and a few clicks of the mouse to root...not the first method initially posted when the phone first came out. When I clicked update now it simply rebooted and the android guy came up and did its thing...about 5 minutes later everything was back to normal.
I wiped my phone completely and am not getting a notification about the OTA now.
I'm flashing TWRP and hoping I get notified again.
Is there a way to flash the stock recovery?
I installed this update, all I can confirm is that it's still Android version 4.0.4. Otherwise I've really not noticed anything different or new yet, but I haven't had much of a chance to use it.

Cannot download ota kitkat update

I bought a brand new moto g -stock edition- yesterday.
I am not able to download the kitkat update. It starts at a very slow speed and after an hour it sticks at 37%.
I tried to solve it by factory reseting, but I get the same result.
My wi-fi router works perfectly, as I could restore about 20 apps from Google Play without any delay.
Does anybody have an idea?
Give it some time, maybe the server side is slow.
I'm sure your problem will solve from alone.
If you cannot wait, serach here for the OTA download it put it in internal storage an reboot.
mokkami said:
Give it some time, maybe the server side is slow.
I'm sure your problem will solve from alone.
If you cannot wait, serach here for the OTA download it put it in internal storage an reboot.
Click to expand...
Click to collapse
Ok, I'll be a little patient and wait for now. I thougt it could be me phone's fault.

How to stop lollipop from installing automatically?

I have just noticed my G3 is taking the ota without asking for my approval. How can I stop it from doing it again? Thanks in advance.
Secret Menu
I went to the dialer keypad and typed in 3845#*850#, the 850 is my model number. Change it to your model # and secret menu will appear. Tap on WLAN settings and it will show OTA updates and pick disable. That's it. Worked for me.
Did that but the phone will still try to install. The reason I know is because my phone will be boot looping in twrp. At first I thought I did something crazy until this morning I saw a message saying phone will install update and will reboot in 10 seconds. Good thing is that I have the boot loop fix zip file in my sdcard.
I kept having this happen to me as well, even after disabling the option in the secret menu. I ended up installing the 855 minus 5 ROM.
I actually had that happen as well. My whole system was gone and stuck in twrp. I downloaded the copy of the 10f stock file and the zip fix file. Thought everything was good, then the update popped up again in the notifation bar, so I made a backup in twrp and tried disabling notifications. The next morning it started to auto install and it failed. Stuck in twrp again, ran my backup then disabled notifications again. Haven't seen the update again in the notifications. Hopefully it won't come back.
Using TiBu, I disabled/froze com.leg.lgfota.permission and Software Update and I have not had any issues.
Sent from my LG G3 D850
So I tried Titanium Backup. Couldn't figure out how to do it. I also noticed I couldn't send or receive MMS pics. Did some searching and on Google Play, there is an app called Disable Service. Download the app, open it, click on system at the top, scroll down to Google Play Services and click on it. Scroll down to SystemUpdateService and uncheck the box. I also went down to software update and unchecked all 3 of those boxes. Restart your phone and you're done. I also re enabled the setting in the secret menu. Now my pics come through again and the update disappeared when I restarted the phone.
Can the OTA be undone?
auky said:
I have just noticed my G3 is taking the ota without asking for my approval. How can I stop it from doing it again? Thanks in advance.
Click to expand...
Click to collapse
This may be a dumb question but I had something similar happen and I'm desperately looking for a way to reverse things. My D850 was rooted, still stock but tweaked to PERFECTION, and I was under the false impression that the OTA checked for root and wouldn't proceed, so when I got the notification that the update was available I dismissed it and didn't think about it. Next morning I woke up to find the OTA happened without any action from me and of course I lost root. The phone is now really sluggish with numerous nuisances and I hate it. AT&T really f'd up my perfect G3. I chose not to factory reset or clear the cache as some have suggested to improve performance. I guess I was hoping that with everything still installed there might be some hope to regain root.
I'm reading about people going back back and flashing zip files but I don't get how it's being done. I did not have a custom recovery installed but I did have a backup with Titanium, although I obviously can't get into that now without root. The really odd thing is that Softcard still thinks it's rooted and won't run. Anybody have any ideas?
Thanks,
...Joe K.
jkovacs89 said:
This may be a dumb question but I had something similar happen and I'm desperately looking for a way to reverse things. My D850 was rooted, still stock but tweaked to PERFECTION, and I was under the false impression that the OTA checked for root and wouldn't proceed, so when I got the notification that the update was available I dismissed it and didn't think about it. Next morning I woke up to find the OTA happened without any action from me and of course I lost root. The phone is now really sluggish with numerous nuisances and I hate it. AT&T really f'd up my perfect G3. I chose not to factory reset or clear the cache as some have suggested to improve performance. I guess I was hoping that with everything still installed there might be some hope to regain root.
I'm reading about people going back back and flashing zip files but I don't get how it's being done. I did not have a custom recovery installed but I did have a backup with Titanium, although I obviously can't get into that now without root. The really odd thing is that Softcard still thinks it's rooted and won't run. Anybody have any ideas?
Thanks,
...Joe K.
Click to expand...
Click to collapse
I'm afraid you wont be able to go back to rooted kitkat without having to clean install as there is no root for Lollipop yet.
aybarrap1 said:
Using TiBu, I disabled/froze com.leg.lgfota.permission and Software Update and I have not had any issues.
Sent from my LG G3 D850
Click to expand...
Click to collapse
Hey aybarrap just curious if the TiBu freezing has held up. Took your advice and did the same. Just curious if you've had any issues so I can be on the lookout.
adosin said:
Hey aybarrap just curious if the TiBu freezing has held up. Took your advice and did the same. Just curious if you've had any issues so I can be on the lookout.
Click to expand...
Click to collapse
I have NOT received a single nag or download for OTA. I have had these frozen for over two months without seeing any issues in the phone's operations. In fact I waited 10 days after the 10f was released before installing and had no issues.

Categories

Resources