[SOLVED] 80070013 error while updating to 7740

pithanks

Member
Mar 6, 2008
17
0
0
My ATT TITAN has failed to update to 7740. UpdateWP returned 80070013.

I googled it and it looks write-protected problem.

interestingly, I can't even unlock my phone permanently.(sim unlock)

It means I have to put my unlock code whenever I turn it off and on to use other carrier's sim card.

Does this mean write-protected partition also prevents to store unlocked state?

Do you any ideas?

Thanks,
wais
 
Last edited:

pithanks

Member
Mar 6, 2008
17
0
0
Hi,

It's solved!

Reserved space should be increased for the first time on zune.

I changed it to 7% on my titan after factory reset.

Then 8170 update succeeded and no more asking for sim unlock code too. =)

Thanks,
wais
 

brianmakris

Member
Feb 19, 2010
31
4
0
Phoenix
I have increased the size all the way up to 10% and i am still unable to update my ATT Titan any other suggestions? I am sick of the disappearing keyboard.

Sent from my PI39100 using XDA Windows Phone 7 App
 

Heathcliff74

Inactive Recognized Developer
Dec 1, 2010
1,646
2,609
0
I have increased the size all the way up to 10% and i am still unable to update my ATT Titan any other suggestions? I am sick of the disappearing keyboard.

Sent from my PI39100 using XDA Windows Phone 7 App
Probably not enough space left on your phone or on your pc.
 

x2beach

Senior Member
Apr 2, 2010
65
3
0
I did a factory Reset. My phone has nothing on it.

---------- Post added at 06:00 AM ---------- Previous post was at 05:52 AM ----------

here is the error i get

 

brianmakris

Member
Feb 19, 2010
31
4
0
Phoenix
Same here just did a factory reset and there is nothing on it at all except the stock stuff. I have even gone in and set the reserved space as high as 20% this just doesn't make sense. I have 50gb now free on the PC and I am still confused.
 

silentP

Senior Member
Mar 22, 2008
531
6
0
Carrier Unlocked?

Are those of you that are having success in updating your AT&T branded Titans carrier unlocked? I, like several others, have been attempting this manual update for quite awhile now, and am having zero success; always ending with the 80070013 error. So I am beginning to believe that it has to do with the SIM lock for AT&T.

Thanks,
 
Last edited:

Phil_123

Senior Member
Sep 7, 2007
148
38
28
Hong Kong
Are those of you that are having success in updating your AT&T branded Titans carrier unlocked? I, like several others, have been attempting this manual update for quite awhile now, and am having zero success; always ending with the 80070013 error. So I am beginning to believe that it has to do with the SIM lock for AT&T.

Thanks,
I have the Asia version of the Titan which is not locked to any carrier. It came with 7740 preinstalled, and I still get the 80070013 error when manually updating it to 8107.
 

Heathcliff74

Inactive Recognized Developer
Dec 1, 2010
1,646
2,609
0
I have the Asia version of the Titan which is not locked to any carrier. It came with 7740 preinstalled, and I still get the 80070013 error when manually updating it to 8107.
To everyone with the 80070013 error.. Please hit L in cabsender and post your log here. Maybe we can see what's going on.

Ciao,
Heathcliff74
 
  • Like
Reactions: silentP

kdawg1989

Member
Jul 13, 2010
6
0
0
Same Problem

I am also getting error 80070013 when trying to update to 7740 I downloaded brianmakris logs and I am getting the exact same errors as him. I didn't download anyone else's logs but I suspect they are the same.
 

mmian

Senior Member
Mar 29, 2011
176
9
0
same error here as well, i responded on both threads, not sure which thread is being followed closer :) I really want the dissapearing keyboard fix! haha
 

LiFePo4

Senior Member
Aug 19, 2011
336
53
0
Oregon
To all getting errors, this may not have anything to do with it but are you using a 32bit or 64bit PC? I thought I read once and I myself ran into weird behavior using the Cab Sender on my 64bit machine but my 32bit works well. I maybe completely off base here...
 

Heathcliff74

Inactive Recognized Developer
Dec 1, 2010
1,646
2,609
0
Most logs are pretty empty. But one of your logs contains this:

Code:
2012-01-12T01:58:14Z:: MESSAGE: Ignore Error DIBR_ERROR_BACKUP_NOT_FOUND (0x80180082) by DibrUspFileManager::FindBackupRecord() 
2012-01-12T01:58:14Z:: Error at function DibrUspFileManager::CommitBackupRecord, line 410, (ahNewBackupRecordFile.valid()) == FALSE, hr=80070013
2012-01-12T01:58:14Z:: Error at function DibrBackup::Commit, line 708, hr=80070013
Not sure what that means.
Will look into it.

Heathcliff74
 
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone