[SOLVED] 80070013 error while updating to 7740

[Heathcliff74]

I looked into this. Not 100% sure, but this is what seems to be happening:

- Device starts update procedure WITH BACKUP OPTION.
- Device creates backup and sends it to the PC. Success.
- Device tries to write a record on the device to register that backup and allow it to restore at a later time. -> THAT FAILS!!

This means that even though the backup seems to be successful, you won't be able to restore it to the device, because the NewBackupRecordFile is written to a location on the device that is write-protected. It could be a policy-issue or a corrupt registry setting. I could investigate further and try to find where the location for these files is determined. But at the moment that is not useful, because for 2nd gen HTC devices there is no possibility to alter the policies or the registry. This can probably only be fixed with an update from HTC or Microsoft (and that update can probably only be applied without possibility to backup first).

The error can probably be avoided by skipping the backup-process (send the update without making a backup first), but I strongly advise against that! If something goes wrong, you can't restore!!!

Ciao,
Heathcliff74

 

[Phil_123]

http://forum.xda-developers.com/showthread.php?p=21458192#post21458192
http://forum.xda-developers.com/showthread.php?p=21121496#post21121496

Some users have updated their Titan with no problems. Might there be a batch of Titans that have/don't have this problem with updating?

Here's some info displayed in my Titan's About screen:

Firmware revision number: 1600.2200.20201.708
Hardware revision number: 0002
Radio software version: 16.23.03.17_ 16.27.00.23U
Radio hardware version: 2.122.0.D4
Bootloader version: 2.2.160015.3(134181)
Chip SOC version: 1.6.0.0

---------- Post added at 12:21 AM ---------- Previous post was at 12:19 AM ----------

I looked into this. Not 100% sure, but this is what seems to be happening:

- Device starts update procedure WITH BACKUP OPTION.
- Device creates backup and sends it to the PC. Success.
- Device tries to write a record on the device to register that backup and allow it to restore at a later time. -> THAT FAILS!!

This means that even though the backup seems to be successful, you won't be able to restore it to the device, because the NewBackupRecordFile is written to a location on the device that is write-protected. It could be a policy-issue or a corrupt registry setting. I could investigate further and try to find where the location for these files is determined. But at the moment that is not useful, because for 2nd gen HTC devices there is no possibility to alter the policies or the registry. This can probably only be fixed with an update from HTC or Microsoft (and that update can probably only be applied without possibility to backup first).

The error can probably be avoided by skipping the backup-process (send the update without making a backup first), but I strongly advise against that! If something goes wrong, you can't restore!!!

Ciao,
Heathcliff74

I never made a backup before sending the updates to my Titan, but the errors stayed the same.

 

[kdawg1989]

I looked into this. Not 100% sure, but this is what seems to be happening:

- Device starts update procedure WITH BACKUP OPTION.
- Device creates backup and sends it to the PC. Success.
- Device tries to write a record on the device to register that backup and allow it to restore at a later time. -> THAT FAILS!!

This means that even though the backup seems to be successful, you won't be able to restore it to the device, because the NewBackupRecordFile is written to a location on the device that is write-protected. It could be a policy-issue or a corrupt registry setting. I could investigate further and try to find where the location for these files is determined. But at the moment that is not useful, because for 2nd gen HTC devices there is no possibility to alter the policies or the registry. This can probably only be fixed with an update from HTC or Microsoft (and that update can probably only be applied without possibility to backup first).

The error can probably be avoided by skipping the backup-process (send the update without making a backup first), but I strongly advise against that! If something goes wrong, you can't restore!!!

Ciao,
Heathcliff74

I tried to send the update with out using the backup option and got the same error.. But also you are right there is something wrong with the backups because I tried restore some of my backups as a test before attempting the update and they will not restore they error out at the end.

 

[mmian]

thats weird that some titans have this issue and others dont

 

[Phil_123]

This Chinese guy from wpxap.com is able to update his Taiwan Titan to 8107.
http://www.wpxap.com/thread-259973-1-1.html

Attached is his Titan's About screen and here's some info displayed in there, he seems to have older firmware, radio and bootloader than my Hong Kong Titan:

Firmware revision number: 1600.2200.11001.709
Hardware revision number: 0002
Radio software version: 16.23.02.09_A_ 16.24.00.23U
Radio hardware version: 2.122.0.D4
Bootloader version: 1.10.160015.3(132313)
Chip SOC version: 1.6.0.0

(图片出自 wpxap.com 智机网会员 奇异恩典)
(Photo from wpxap.com member 奇异恩典)

 

[brianmakris]

I sent my Titan back and had a brand new one sent to me ( dead pixel in the corener and this) and guess what it is doing the same exact thing. I am now a little concerned that I am not going to be able to update this if and when ATT decides they want to send it out if Heathcliff is correct. I am wondering also if any body else that can't update their Titans is also having the mic issue and stuttering youtube playback. I wonder if they are related since both brand new ones do the same things.

 

[ROCOAFZ]

My titan updated fine and its on Att no sum locked, only developer unlock

Sent from my PI39100 using XDA Windows Phone 7 App

 

[brianmakris]

Rocoafz what do you mean no sum locked? Also what hardware revision on the about screen?

Sent from my PI39100 using XDA Windows Phone 7 App

 

[JasonWilton]

I tried force update for this on my mozart and now im stuck at the "plug into your computer picture" on my phone... no matter what i do i get it, does it mean my phone is currently bricked?

 

[petersun21]

my experience

I have two att htc titans bought at the same time. I updated mine without backup option and everything worked smoothly.
Installing my wife's titan failed. First it failed in stalling drivers. Phone will not stay in USB mode long enough to allow driver installation. Manually forced usb mode and driver installed successfully. While installing 7440 update and got 80070013 error (without backup option). Tried with backup option and get the same error. However, backup is successful. Tried restore from the backup using zune, failed. As some have described, connecting phone to computer will not start zune either.

I hope someone can come out with a solution. I am also afraid that I will not able to get future official update. I have not done anything unofficial other than this update *FYI

 

[silentP]

I have two att htc titans bought at the same time. I updated mine without backup option and everything worked smoothly.
Installing my wife's titan failed. First it failed in stalling drivers. Phone will not stay in USB mode long enough to allow driver installation. Manually forced usb mode and driver installed successfully. While installing 7440 update and got 80070013 error (without backup option). Tried with backup option and get the same error. However, backup is successful. Tried restore from the backup using zune, failed. As some have described, connecting phone to computer will not start zune either.

I hope someone can come out with a solution. I am also afraid that I will not able to get future official update. I have not done anything unofficial other than this update *FYI

Did you compare the phone details, i.e. bootloader, firmware, radio, etc? When I ordered my Titan they were on backorder due to manufacturing. Maybe some type of change?

 

[petersun21]

Did you compare the phone details, i.e. bootloader, firmware, radio, etc? When I ordered my Titan they were on backorder due to manufacturing. Maybe some type of change?

Other than things that should be different, everything is the same.

 

[Phil_123]

I looked into this. Not 100% sure, but this is what seems to be happening:

- Device starts update procedure WITH BACKUP OPTION.
- Device creates backup and sends it to the PC. Success.
- Device tries to write a record on the device to register that backup and allow it to restore at a later time. -> THAT FAILS!!

This means that even though the backup seems to be successful, you won't be able to restore it to the device, because the NewBackupRecordFile is written to a location on the device that is write-protected. It could be a policy-issue or a corrupt registry setting. I could investigate further and try to find where the location for these files is determined. But at the moment that is not useful, because for 2nd gen HTC devices there is no possibility to alter the policies or the registry. This can probably only be fixed with an update from HTC or Microsoft (and that update can probably only be applied without possibility to backup first).

The error can probably be avoided by skipping the backup-process (send the update without making a backup first), but I strongly advise against that! If something goes wrong, you can't restore!!!

Ciao,
Heathcliff74

I am able to backup my Titan with no errors with WP7 Easy Backup Tool... what gives?
http://forum.xda-developers.com/showthread.php?t=1379571

 

[petersun21]

I am able to backup my Titan with no errors with WP7 Easy Backup Tool... what gives?
http://forum.xda-developers.com/showthread.php?t=1379571

Just want to comment on this. As I stated before, I have two htc titans with identical device information (firmware, etc). One is able to update to 8017 and another is not.
Provide a bit more information for someone to diagnose:

I tried easyBackup on both titans:

The "good" titan successfully backed up fine. The device gave a message after restart "device has been updated". Did not try to restore.

The "bad" titan successfully backed up "fine". However, the device did not give a message after restart. Tried restore and it failed.

Check my earlier posts for references:

 

[Phil_123]

Just want to comment on this. As I stated before, I have two htc titans with identical device information (firmware, etc). One is able to update to 8017 and another is not.
Provide a bit more information for someone to diagnose:

I tried easyBackup on both titans:

The "good" titan successfully backed up fine. The device gave a message after restart "device has been updated". Did not try to restore.

The "bad" titan successfully backed up "fine". However, the device did not give a message after restart. Tried restore and it failed.

Check my earlier posts for references:

I can confirm my Titan is behaving exactly as your bad Titan.

 

[mmian]

so then is it possible to skip the backup process?

 

[Phil_123]

so then is it possible to skip the backup process?

I believe it is not possible, unless HTC releases a ROM flashing tool that does not wipe everything on the Titan and updates only the part responsible for the backup process, or release a fix through the Marketplace as an OEM app that corrects the registry in our Titans.

 

[mmian]

so the problem is that we have corrupt registry values? Looks like we have to wait for the official ATT update...which will hopefully have a fixed registry

 

[Phil_123]

so the problem is that we have corrupt registry values? Looks like we have to wait for the official ATT update...which will hopefully have a fixed registry

The problem is the official update mechanism (sending .cab files to device for installation) always trigger the backup process before installation. If Heathcliff74's hypothesis is correct, we're never going to be able to install any update with Zune unless the corresponding registry data is corrected.

To fix the registry, we could have used a registry editor, but it requires an Interop-Unlock which we do not have. The only remaining option that does not require us to do a factory reset, is to have HTC use their OEM powers to release an app that fixes the problem through the Marketplace.

I've written an support request for HTC regarding this, but their online Customer Service form seems to be down and won't send the message.
http://pastebin.com/NJ76bpBt

 

[brianmakris]

An actual fix

I have finally fixed the problem with both of the phones I have. What it is must be a bad flash from the factory. Thanks to Football I have successfully flashed the following rom and am now running 8107 on my ATT Titan. http://forum.xda-developers.com/showthread.php?t=1334468
It is on page 4 that says Cingular in the name.
Just be sure to follow all the instructions in thus thread. I do have the unfortunate news that you will loose any text messages and game saves, but you will be able to update further in the future.