I bought my TF700T almost a month ago, and I rooted it right away, but postponed updating the firmware (it has .22 on it) because at some point I am going to unlock the bootloader and have some fun with it. Nearly as soon as I went online with it I noticed that a firmware update was available in the notification area, but I ignored it. Well, after a couple of days, I went to the ASUS website and registered my purchase. That same day the firmware notification changed from merely being available to now being ready to download and install, and there was an option to postpone the installation for 10 minutes, 1 hour, or 1 day (I think). I was busy doing something else so I postponed the update for the default 10 minutes without looking and I exited out of the notification, but then I noticed something as I was leaving...there was a number in parenthesis on the postpone button. I went back into the notification area and sure enough, the number was decremented...evidently, you are only allowed 3 postponements, and I had wasted the first one. I looked at the area that allows you to choose how long to postpone the installation, but the maximum was 1 day, so I selected that, then took my tablet offline and found this thread. I renamed CMClient and DMClient, and all update notifications went away...this has been nearly a month ago.
Now I am about ready to unlock the bootloader, and I've read where I should rename those files back to what they were. I assume the tablet needs to be online during the unlocking process, but I am concerned that the firmware update will be back staring me in the face when I do that. I resent the hell out of having the update forced down my throat by ASUS. Do I need to rename those files prior to unlocking, and do I need to be online during the unlocking process?
I bought my TF700T almost a month ago, and I rooted it right away, but postponed updating the firmware (it has .22 on it) because at some point I am going to unlock the bootloader and have some fun with it.
Is this 9.4.5.22? I assume you want to make NVFlash backups before updating.
To unlock, you must be online, and DMClient must be enabled. If there is already an update downloaded and waiting to be installed, it is in /cache/dlkpgfile. Move this file to some other location, e.g. /sdcard. There is another file in /cache (called "command" or so, maybe in a subdirectory) that instructs the recovery to install that dlpkgfile. Move that away too. So it won't install inadvertently.
Also, before you unlock, make a backup of /dev/block/mmcblk0p6, because that partition is deleted by the unlocking process.
Is this 9.4.5.22? I assume you want to make NVFlash backups before updating.
To unlock, you must be online, and DMClient must be enabled. If there is already an update downloaded and waiting to be installed, it is in /cache/dlkpgfile. Move this file to some other location, e.g. /sdcard. There is another file in /cache (called "command" or so, maybe in a subdirectory) that instructs the recovery to install that dlpkgfile. Move that away too. So it won't install inadvertently.
Also, before you unlock, make a backup of /dev/block/mmcblk0p6, because that partition is deleted by the unlocking process.
Great! That's exactly the info I was looking for! Many, many thanks!
Yes, it is 9.4.5.22, from what I little know, the original release software (20120615).
One other thing...is NVFlash safe to use on the TF700T? It's in the list of apps to avoid (NVFlash = softbrick), which is confusing to me...
Yes, it is 9.4.5.22, from what I little know, the original release software (20120615).
One other thing...is NVFlash safe to use on the TF700T? It's in the list of apps to avoid (NVFlash = softbrick), which is confusing to me...
If you follow the guide on androidroot.mobi, it's safe. Since it is a very powerful tool, of course you must be careful, especially with write commands.
...If there is already an update downloaded and waiting to be installed, it is in /cache/dlkpgfile. Move this file to some other location, e.g. /sdcard. There is another file in /cache (called "command" or so, maybe in a subdirectory) that instructs the recovery to install that dlpkgfile. Move that away too. So it won't install inadvertently.
I bought the tab on 3/22/2013, and there is a 45.37MB /cache/dlkpkgfile with a 3/23/2013 datestamp...this was before I registered the product with ASUS, so evidently it wasn't the product registration that triggered the download of the update. There is also a 0B /cache/recovery/last_install file and a 4.61KB /cache/recovery/last_log file, both dated 6/18/2012, but other than the lost+found folder, there are no other files or folders in /cache...
Quote:
Originally Posted by _that
...Also, before you unlock, make a backup of /dev/block/mmcblk0p6, because that partition is deleted by the unlocking process.
Obviously I need to do quite a bit more research...I have no idea what this partition is or why it is important. I don't want to get too far OT, but do I need to restore this partition after unlocking?
I bought the tab on 3/22/2013, and there is a 45.37MB /cache/dlkpkgfile with a 3/23/2013 datestamp...this was before I registered the product with ASUS, so evidently it wasn't the product registration that triggered the download of the update. There is also a 0B /cache/recovery/last_install file and a 4.61KB /cache/recovery/last_log file, both dated 6/18/2012, but other than the lost+found folder, there are no other files or folders in /cache...
OK, maybe the command file is only written when you confirm that you want to apply the update. So it should suffice to remove the dlpkgfile. Of course, DMClient may then start downloading another dlpkgfile (maybe even a huge one that would take you directly from 9.4.5.22 to 10.6.1.14.4), but it won't apply it before asking you.
Quote:
Originally Posted by Fast.Eddie
Obviously I need to do quite a bit more research...I have no idea what this partition is or why it is important. I don't want to get too far OT, but do I need to restore this partition after unlocking?
Unlocking deletes your DRM key. Until now nobody has confirmed if restoring the DRM key restores DRM functionality on an unlocked device, but having a backup of the key doesn't hurt - in the worst case it's useless.
Unlocking deletes your DRM key. Until now nobody has confirmed if restoring the DRM key restores DRM functionality on an unlocked device, but having a backup of the key doesn't hurt - in the worst case it's useless.
I have a very simplistic idea of what DRM is...to the best of my knowledge, I don't have anything that is DRM-protected, so I probably would never notice the deletion. But now I gotta ask myself...why would unlocking my tab trigger deletion of a DRM key? That kinda sucks...I think...if it would cause me to lose a library of books or music that I had paid for.
But I think I am hijacking this thread because I am so far OT so I'll stand down now. Again, thanks for sharing your knowledge...it is much appreciated!
XDA Developers was founded by developers, for developers. It is now a valuable resource for people who want to make the most of their mobile devices, from customizing the look and feel to adding new functionality. Are you a developer?