[HOWTO] Manually updating firmware using "dlpkgfile" download via Asus FOTA server

Redefined301 · Jul 29, 2012

[HOWTO] Manually updating firmware using "dlpkgfile" download via Asus FOTA server

FOTA UPDATE version 9.4.5.26-20120720 is known to provide improvements and fixes to address I/O issues, and MicroSD U-1 card compatibility.

Based on the original post here:
http://xdaforums.com/showpost.php?p=29485094&postcount=58
Thanks to Lufterfischer for discovery, and jtrosky for testing it!

Here's the summary of what's needed to manually update using the patch file "dlpkgfile".
This is merely a documentation to help TF700 users to over come their IO problems by manually updating to FOTA version 9.4.5.26-20120720.
A short history of: OTA update happened briefly on 28/7/2012 and became unavailable to owners of TF700 tablet.

Before you start make sure your tablet is charged fully.

Disclaimer: I'm not responsible for whatever you are going to do or did to your tablet.

For those who have unlocked bootloader and custom recovery you can try this method of restoring your stock recovery by copying the blob image back to /staging on device /dev/block/mmcblk0p4
Follow the howto in the following link.
http://xdaforums.com/showthread.php?t=1492887

Prerequisite
1. root
2. a copy of dlpkgfile for correct firmware version
3. a correct firmware installed on the device (9.4.5.22-20120615) for patching
4. unmodified build.prop as some has reported it was the cause for update failure.
5. make sure you don't have any of the existing files under /system modified

Here are the steps:
1. use root explorer to copy "dlpkgfile" into /cache/ directory.
Alternatively you could save the "dlpkgfile" in a microSD then open up a adb shell session.
Type:
su
cat /Removable/MicroSD/dlpkgfile > /cache/dlpkgfile
2. create the file called "command" under /cache/recovery/ directory.
3. write this statement in the file /cache/recovery/command (without qoutes) "--update_package=/cache/dlpkgfile"
Or you can just use the attached file "command" and
cat /Removable/MicroSD/command > /cache/recovery/command

Note: remove MicroSD before this last step.
4. finally reboot into recovery kernel by shutting down first, then press and hold "Volume down" + "Power" once it vibrates release "Power" keep holding "Volume down" until there are some text shown on the boot logo screen. Then press "Volume up" within 5 seconds after releasing "Volume down".
The update process should start... wait for it to complete.
Once it completes, you should have the updated firmware installed on your tablet.

Reference:
US version patch "dlpkgfile" can be found here -> http://xdaforums.com/showthread.php?t=1801756
md5sum for this file is 2ff06463b57226ac910ac642781c5290

If you have received the FOTA update already and haven't updated the firmware and you have root access to your WW, JP, TW, CN version TF700 tablet.
Could you please pull or copy the /cache/dlpkgfile and upload it to your dropbox for backup and please do provide a link for other users to download, Thanks!

********************************************************************************************************
For whatever reason: eg, you disliked the updated firmware
To revert back to firmware version 9.4.5.22-20120615
Extract the blob file from zip within "**epad_user_9_4_5_22_UpdateLauncher.zip" and save
it to a MicroSD
Simply launch the following command under adb shell as root:

Code:

dd if=/Removable/MicroSD/blob of=/dev/block/mmcblk0p4

Then wait patiently for the process to complete once it finish you will see some output as
follows and it returns to the root shell prompt:

1596712+1 records in
1596712+1 records out
817516935 bytes transferred in 383.960 secs (2129172 bytes/sec)
shell@android:/ #

Now reboot the device, the downgrade process should automatically start!
Just do a factory reset after that !!
Note: Camera and Touch panel firmware can't be downgraded and will stay up-to-date.
********************************************************************************************************

tbogunro · Jul 29, 2012

would this work if I have a custom recovery?

Sent from my ASUS Transformer Pad TF700T using Tapatalk 2

newellj79 · Jul 29, 2012

tbogunro said:
would this work if I have a custom recovery?

Sent from my ASUS Transformer Pad TF700T using Tapatalk 2

No...

I'm waiting too.

Sent from my ASUS Transformer Pad TF700T using Tapatalk 2

Redefined301 · Jul 29, 2012

tbogunro said:
would this work if I have a custom recovery?

Sent from my ASUS Transformer Pad TF700T using Tapatalk 2

It's best to flash recovery back to stock, no point having customer recovery installed right now as there isn't any custom ROM available for TF700 yet.

tbogunro · Jul 29, 2012

You're right, but how would I do that?

Sent from my ASUS Transformer Pad TF700T using Tapatalk 2

Redefined301 · Jul 29, 2012

tbogunro said:
You're right, but how would I do that?

Sent from my ASUS Transformer Pad TF700T using Tapatalk 2

What is the firmware version (US?) of your tablet ?
Maybe you can try this -> http://xdaforums.com/showthread.php?t=1492887
Don't do it if you aren't confident enough otherwise you'll risk bricking your device.

tbogunro · Jul 29, 2012

It was originally a US based firmware, but I patched it to a now currently WW 9.4.5.22

Sent from my ASUS Transformer Pad TF700T using Tapatalk 2

teknomanelvis · Jul 29, 2012

When it says tocreate thecommand file, is it a text file what is the file extension?

Sent from my ASUS Transformer Pad TF700T using xda app-developers app

Redefined301 · Jul 29, 2012

teknomanelvis said:
When it says tocreate thecommand file, is it a text file what is the file extension?

Sent from my ASUS Transformer Pad TF700T using xda app-developers app

it's just a file named "command" without any extension.

tbogunro · Jul 29, 2012

Redefined301 said:
What is the firmware version (US?) of your tablet ?
Maybe you can try this -> http://xdaforums.com/showthread.php?t=1492887
Don't do it if you aren't confident enough otherwise you'll risk bricking your device.

Thanks for your help, but I'm not going to risk it lol

Sent from my ASUS Transformer Pad TF700T using Tapatalk 2

newellj79 · Jul 29, 2012

Redefined301 said:
It's best to flash recovery back to stock, no point having customer recovery installed right now as there isn't any custom ROM available for TF700 yet.

To my knowledge u can't go back to stock recovery.

Sent from my ASUS Transformer Pad TF700T using Tapatalk 2

jimmyxxx · Jul 29, 2012

As far as I know from TF201, you can't flash the stock OTA if you unlocked your bootloader.
Althoug I must confess, that I've forgotten the background & reasons for that

eoh7678 · Jul 29, 2012

newellj79 said:
To my knowledge u can't go back to stock recovery.

Sent from my ASUS Transformer Pad TF700T using Tapatalk 2

OK, I took the risk...

Using the info here: http://xdaforums.com/showthread.php?t=1492887

I was able to grab the blob from the .22 update and restore the stock recovery. My device is still unlocked, but has the stock recovery reinstalled. Using the info from the OP, I was able to successfully apply the OTA to .26

I'll write up a quick how to from start to finish.

Redefined301 · Jul 29, 2012

newellj79 said:
To my knowledge u can't go back to stock recovery.

Sent from my ASUS Transformer Pad TF700T using Tapatalk 2

Someone just reverted back to stock recovery.

Redefined301 · Jul 29, 2012

eoh7678 said:
OK, I took the risk...

Using the info here: http://xdaforums.com/showthread.php?t=1492887

I was able to grab the blob from the .22 update and restore the stock recovery. My device is still unlocked, but has the stock recovery reinstalled. Using the info from the OP, I was able to successfully apply the OTA to .26

I'll write up a quick how to from start to finish.

Yeah it will definitely work as long as you don't make a typo doing dd..
So that's interesting ... Did you flashed to stock recovery from customer recovery? Or was it simply unlocked?

GrimSage · Jul 29, 2012

Does anyone have a stock build.prop file, here is mine?

Code:

127|shell@android:/system $ cat build.prop
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=IML74K
ro.build.display.id=IML74K.US_epad-9.4.5.22-20120615
ro.build.version.incremental=US_epad-9.4.5.22-20120615
ro.build.version.sdk=15
ro.build.version.codename=REL
ro.build.version.release=4.0.3
ro.build.date=Fri Jun 15 19:13:51 CST 2012
ro.build.date.utc=1339758831
ro.build.type=user
ro.build.user=
ro.build.host=Mercury
ro.build.tags=release-keys
ro.product.model=EPAD
ro.product.brand=asus
ro.product.name=US_epad
ro.product.device=EeePad
ro.product.board=EeePad
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=asus
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=tegra
# ro.build.product is obsolete; use ro.product.device
ro.build.product=EeePad
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=US_epad-user 4.0.3 IML74K US_epad-9.4.5.22-20120615 release-keys
ro.build.fingerprint=asus/US_epad/EeePad:4.0.3/IML74K/US_epad-9.4.5.22-20120615:user/release-keys
ro.build.characteristics=tablet
# end build properties
ro.opengles.version = 131072
wifi.interface=wlan0
persist.tegra.nvmmlite = 1

#NFC
debug.nfc.fw_download=false
debug.nfc.se=false

#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.config.notification_sound=NewMessage.ogg
persist.sys.ringermode=2
ro.config.bootsound=PowerOn.ogg
drm.service.enabled=1
ro.config.alarm_alert=Alarm_Classic.ogg
dalvik.vm.heapstartsize=5m
dalvik.vm.heapgrowthlimit=48m
dalvik.vm.heapsize=256m
wifi.version.driver=V6.1.38
gps.version.driver=V6.9.18
keyguard.no_require_sim=true
ro.kernel.qemu=
bt.version.driver=V9.32
windowsmgr.max_events_per_sec=200
ro.setupwizard.mode=OPTIONAL
ro.com.google.gmsversion=4.0_r2
ro.com.google.clientidbase=android-asus
ro.wifi.country=US
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
tf.enable=y

I have tried doing this and still get the dead android with the following last_log:

Code:

shell@android:/cache/recovery # cat last_log
Starting recovery on Sun Jul 29 12:13:20 2012
can't open /dev/tty0: No such file or directory
framebuffer: fd 3 (1920 x 1200)
recovery filesystem table
=========================
  0 /tmp ramdisk (null) (null) 0
  1 /system ext4 /dev/block/mmcblk0p1 (null) 0
  2 /cache ext4 /dev/block/mmcblk0p2 (null) 0
  3 /misc emmc /dev/block/mmcblk0p3 (null) 0
  4 /boot emmc boot (null) 0
  5 /recovery emmc recovery (null) 0
  6 /staging ext3 /dev/block/mmcblk0p4 (null) 0
  7 /btmac vfat /dev/block/mmcblk0p5 (null) 0
  8 /data ext4 /dev/block/mmcblk0p8 (null) -32768
  9 /sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1 0

I:Got arguments from /cache/recovery/command
Command: "/sbin/recovery" "--update_package=/cache/dlpkgfile"

ro.secure=1
ro.allow.mock.location=0
ro.debuggable=0
persist.sys.usb.config=mtp,adb
ro.build.id=IML74K
ro.build.display.id=IML74K.US_epad-9.4.5.22-20120615
ro.build.version.incremental=US_epad-9.4.5.22-20120615
ro.build.version.sdk=15
ro.build.version.codename=REL
ro.build.version.release=4.0.3
ro.build.date=Fri Jun 15 19:13:51 CST 2012
ro.build.date.utc=1339758831
ro.build.type=user
ro.build.user=
ro.build.host=Mercury
ro.build.tags=release-keys
ro.product.model=EPAD
ro.product.brand=asus
ro.product.name=US_epad
ro.product.device=EeePad
ro.product.board=EeePad
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=asus
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=tegra
ro.build.product=EeePad
ro.build.description=US_epad-user 4.0.3 IML74K US_epad-9.4.5.22-20120615 release-keys
ro.build.fingerprint=asus/US_epad/EeePad:4.0.3/IML74K/US_epad-9.4.5.22-20120615:user/release-keys
ro.build.characteristics=tablet
ro.opengles.version=131072
wifi.interface=wlan0
persist.tegra.nvmmlite=1
debug.nfc.fw_download=false
debug.nfc.se=false
ro.config.notification_sound=NewMessage.ogg
persist.sys.ringermode=2
ro.config.bootsound=PowerOn.ogg
drm.service.enabled=1
ro.config.alarm_alert=Alarm_Classic.ogg
dalvik.vm.heapstartsize=8m
dalvik.vm.heapgrowthlimit=64m
dalvik.vm.heapsize=256m
wifi.version.driver=V6.1.38
gps.version.driver=V6.9.18
keyguard.no_require_sim=true
ro.kernel.qemu=
bt.version.driver=V9.32
windowsmgr.max_events_per_sec=200
ro.setupwizard.mode=OPTIONAL
ro.com.google.gmsversion=4.0_r2
ro.com.google.clientidbase=android-asus
ro.wifi.country=US
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
net.change=net.bt.name
dalvik.vm.stack-trace-file=/data/anr/traces.txt
tf.enable=y
ro.factorytest=0
ro.serialno=C6OKAS105604
ro.bootmode=unknown
ro.baseband=unknown
ro.carrier=wifi-only
ro.bootloader=unknown
ro.hardware=cardhu
ro.revision=0
ro.boot_reason=normal
ro.crypto.fs_type=ext4
ro.crypto.fs_real_blkdev=/dev/block/mmcblk0p8
ro.crypto.fs_mnt_point=/data
ro.crypto.fs_flags=0x00000006
ro.crypto.state=unencrypted
ro.epad.model_id=04
ro.epad.model=TF700T
ro.sf.lcd_density=240
persist.sys.NV_DISPXRES=1920
persist.sys.NV_DISPYRES=1200
persist.sys.NV_STEREOCTRL=0
persist.tegra.NV_FPSLIMIT=0
persist.sys.NV_FPSLIMIT=35
persist.sys.NV_POWERMODE=1
persist.sys.profiler_ms=0
persist.sys.NV_STEREOSEP=20
persist.sys.NV_STEREOSEPCHG=0
persist.sys.NV_PROFVER=20
persist.sys.fw.camera.status=1
persist.sys.language=en
persist.sys.country=US
persist.sys.localevar=
persist.sys.timezone=America/New_York
persist.sys.ui.hw=true
init.svc.recovery=running
init.svc.adbd=running

I:Enable RSA key verification.
Installing update...
Finding update package...
I:Update location: /cache/dlpkgfile
Opening update package...
I:1 key(s) loaded from /res/keys
Verifying update package...
I:comment is 1682 bytes; signature 1664 bytes from end
E:failed to verify whole-file signature
I:verify_file returned 1
E:signature verification failed
Installation aborted.
I:result_code: 405
Check and format /storage to vfat if needed...
Mount /btmac successfully
Done.

currently trying to get to stock recovery.
I never unlocked, but did run v6 supercharger, and have since many times factory reset and gone though recovery and manually flashed the .22, and then will try this again...

d14b0ll0s · Jul 29, 2012

Stock build.prop on .26 WW, same number of lines as on .22, haven't diff'ed it yet:

Code:

# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=IML74K
ro.build.display.id=IML74K.WW_epad-9.4.5.26-20120720
ro.build.version.incremental=WW_epad-9.4.5.26-20120720
ro.build.version.sdk=15
ro.build.version.codename=REL
ro.build.version.release=4.0.3
ro.build.date=Fri Jul 20 19:32:57 CST 2012
ro.build.date.utc=1342783977
ro.build.type=user
ro.build.user=
ro.build.host=Mercury
ro.build.tags=release-keys
ro.product.model=EPAD
ro.product.brand=asus
ro.product.name=WW_epad
ro.product.device=EeePad
ro.product.board=EeePad
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=asus
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=tegra
# ro.build.product is obsolete; use ro.product.device
ro.build.product=EeePad
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=WW_epad-user 4.0.3 IML74K WW_epad-9.4.5.26-20120720 release-keys
ro.build.fingerprint=asus/WW_epad/EeePad:4.0.3/IML74K/WW_epad-9.4.5.26-20120720:user/release-keys
ro.build.characteristics=tablet
# end build properties
ro.opengles.version = 131072
wifi.interface=wlan0
persist.tegra.nvmmlite = 1

#NFC
debug.nfc.fw_download=false
debug.nfc.se=false

#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.config.notification_sound=NewMessage.ogg
persist.sys.ringermode=2
ro.config.bootsound=PowerOn.ogg
drm.service.enabled=1
ro.config.alarm_alert=Alarm_Classic.ogg
dalvik.vm.heapstartsize=5m
dalvik.vm.heapgrowthlimit=48m
dalvik.vm.heapsize=256m
wifi.version.driver=V6.1.40
gps.version.driver=V6.9.18
keyguard.no_require_sim=true
ro.kernel.qemu=
bt.version.driver=V9.37
windowsmgr.max_events_per_sec=200
ro.setupwizard.mode=OPTIONAL
ro.com.google.gmsversion=4.0_r3
ro.com.google.clientidbase=android-asus
ro.com.google.mcc_fallback=262
ro.wifi.country=GB
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
tf.enable=y

Edit: OK, I've just compared build.prop from WW .26 with the one from WW .21, no changes apart from the version numbers (which is actually a little disappointing, as they haven't touched it).

Redefined301 · Jul 29, 2012

GrimSage said:
Does anyone have a stock build.prop file?

I have tried doing this and still get the dead android

currently trying to get to stock recovery.
I never unlocked, but did run v6 supercharger, and have since many times factory reset and gone though recovery and manually flashed the .22, and then will try this again...

It seems you have a corrupted dlpkgfile
the correct md5sum for dlpkgfile should be
2ff06463b57226ac910ac642781c5290

Your build.prop is stock. Just got to download "dlpkgfile" again because it won't verify on your tablet.

eoh7678 · Jul 29, 2012

I posted a write up of the process I followed to restore the system image, build.prop, and stock recovery, then update to .26 using dlpkgfile if anyone's interested.

It's here: http://xdaforums.com/showthread.php?t=1803343

GrimSage · Jul 29, 2012

Redefined301 said:
It seems you have a corrupted dlpkgfile
the correct md5sum for dlpkgfile should be
2ff06463b57226ac910ac642781c5290

Your build.prop is stock. Just got to download "dlpkgfile" again because it won't verify on your tablet.

looks like somewhere between restoring the stock recovery and redownloading the dlpkgfile, this has worked.

Currently have

Android is upgrading...
Optimizing application XX of XX.

Thank you to everyone!

[HOWTO] Manually updating firmware using "dlpkgfile" download via Asus FOTA server

Senior Member

Attachments

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Similar threads

Top Liked Posts