[Q] (Tablet S Rooted)System Update Error Code: 7

[Topery Chiang]

Maybe the problem is intractable to Sony Tablet S, because of its 3E recovery.
My S(China 3G model) was repaired, and the version of system backed to factory(3.2.1). I tried to root it with AIO 5.2, but failed. So, I updated it to 4.0.3 R1 with SD, everything is OK.
Then, I rooted it by AIO 5.2, and changed the region to JP. I tried to update it to JP 4.0.3 R1 with SD, everything is going so well, but it stopped in "SONY" interface, unable to go.
A long time later(10 mins), I forced to reboot, system data still, never changed. So I tried it again, and wipe data, the problem still.
There is no way to OTA update, and it was failed, "error code: 7". I tried to OTA it again, it displayed the system is newest, but my system is CH 4.0.3 R1 still!
Who can help me?!
How can I make it to normal?!
Is the BUG of AIO 5.2?!
Thanks for your reply!

Sorry for my poor English!

 

[mikajo]

All I know is that it's not a bug of v 5.2, cause I have the same error. Cannot solve it.
Maybe factory formatting could help... not just a reset. But do not know if it works on Sony Tablet S...

 

[CoolApps]

I get the same error code on my other android device.
Maybe it is the partition sizes.
The device?
The file is too large on one side?
OR maybe the build.prop is gone for good
Bootloops mean that there is a chance that there is a corruption o.o

Sent from my Sony Tablet S using xda premium

 

[Topery Chiang]

All I know is that it's not a bug of v 5.2, cause I have the same error. Cannot solve it.
Maybe factory formatting could help... not just a reset. But do not know if it works on Sony Tablet S...

Thanks, but reset so many times.

 

[Topery Chiang]

I get the same error code on my other android device.
Maybe it is the partition sizes.
The device?
The file is too large on one side?
OR maybe the build.prop is gone for good
Bootloops mean that there is a chance that there is a corruption o.o

Sent from my Sony Tablet S using xda premium

But I restored the build.prop(factory version), and tried it again, rebooting in "SONY" stopped.

 

[CoolApps]

But I restored the build.prop(factory version), and tried it again, rebooting in "SONY" stopped.

What do you mean 'Stopped'?
It is stuck on the Sony screen?

Sent from my Sony Tablet S using xda premium

 

[Topery Chiang]

What do you mean 'Stopped'?
It is stuck on the Sony screen?

Sent from my Sony Tablet S using xda premium

Yes, yes, yes.
It is stuck on the "SONY" interface during the third rebooting.
Can you help me to solve this problem?
Thanks!

 

[CoolApps]

Yes, yes, yes.
It is stuck on the "SONY" interface during the third rebooting.
Can you help me to solve this problem?
Thanks!

Can you access the recovery partition?

Sent from my Sony Tablet S using xda premium

 

[stifilz]

Yes, yes, yes.
It is stuck on the "SONY" interface during the third rebooting.
Can you help me to solve this problem?
Thanks!

OK Do you have adb debugging enabled??

DO NOT FACTORY RESET!!!!!

Try to flash a rom and use adb pull /tmp/recovery.log

Then post here

Stifilz

 

[Topery Chiang]

Can you access the recovery partition?

Sent from my Sony Tablet S using xda premium

Yes.

 

[mikajo]

I learned that this is not just a Sony Tablet S problem but can happen on every device.
Furthermore I learned that the Update is not getting the correct device name from the build.prop.
This is very interesting as I can't remember that I would have changed the name of the tablet in the build.prop. However, maybe it's helpful for someone of you

 

[condi]

Maybe the problem is intractable to Sony Tablet S, because of its 3E recovery.
My S(China 3G model) was repaired, and the version of system backed to factory(3.2.1). I tried to root it with AIO 5.2, but failed. So, I updated it to 4.0.3 R1 with SD, everything is OK.
Then, I rooted it by AIO 5.2, and changed the region to JP. I tried to update it to JP 4.0.3 R1 with SD, everything is going so well, but it stopped in "SONY" interface, unable to go.
A long time later(10 mins), I forced to reboot, system data still, never changed. So I tried it again, and wipe data, the problem still.
There is no way to OTA update, and it was failed, "error code: 7". I tried to OTA it again, it displayed the system is newest, but my system is CH 4.0.3 R1 still!
Who can help me?!
How can I make it to normal?!
Is the BUG of AIO 5.2?!
Thanks for your reply!

Sorry for my poor English!

ok, lets try to solve the problem.
try to flash any update zip, after error 7 wait a minute, and get log from device:

adb pull /tmp/recovery.log

attach it here, let me see.

 

[Topery Chiang]

ok, lets try to solve the problem.
try to flash any update zip, after error 7 wait a minute, and get log from device:

adb pull /tmp/recovery.log

attach it here, let me see.

Mine is JP, I was flashed the JP.
Hello, what the recovery.log(similar) is……

-- Install /sdcard ...
Finding update package...
I:Update location: /sdcard/_hack_recovery.zip
Desklunvr update package...
Opening update package...
I:1 key(s) loaded from /res/keys
Verifying update package...
I:comment is 1465 bytes; signature 1447 bytes from end
I:whole-file signature verified against key 0
I:verify_file returned 0
Checking version is passed, 111104048 -> 111201009
Not found detailed sku[27550199] in META-INF/com/android/detailedSKU.lst
Erohibit update as a result of checking version or base sku
Installation aborted.

 

[condi]

Mine is JP, I was flashed the JP.
Hello, what the recovery.log(similar) is……

-- Install /sdcard ...
Finding update package...
I:Update location: /sdcard/_hack_recovery.zip
Desklunvr update package...
Opening update package...
I:1 key(s) loaded from /res/keys
Verifying update package...
I:comment is 1465 bytes; signature 1447 bytes from end
I:whole-file signature verified against key 0
I:verify_file returned 0
Checking version is passed, 111104048 -> 111201009
Not found detailed sku[27550199] in META-INF/com/android/detailedSKU.lst
Erohibit update as a result of checking version or base sku
Installation aborted.

similar? so thats not your log?

 

[Topery Chiang]

similar? so thats not your log?

This isn't mine, but my log is similar to that(I checked some days ago).
I can't provide mine for you these days, my friend borrowed it.
Mine is similar, the words of "Not found detailed sku[27550199] in META-INF/com/android/detailedSKU.lst" specially!
Please!

 

[condi]

This isn't mine, but my log is similar to that(I checked some days ago).
I can't provide mine for you these days, my friend borrowed it.
Mine is similar, the words of "Not found detailed sku[27550199] in META-INF/com/android/detailedSKU.lst" specially!
Please!

try this fw.

 

[Topery Chiang]

try this fw.

nbx03_016?
What the region is?

 

[Topery Chiang]

try this fw.

Like UK version, if the wifi only and wifi+3G can flash mutually without rescue-backdoor?

 

[stifilz]

nbx03_016?
What the region is?

Have a look and see for yourself. Click Update Links in my signature then search for nbx03_016 on that page.

Stifilz

 

[condi]

This isn't mine, but my log is similar to that(I checked some days ago).
I can't provide mine for you these days, my friend borrowed it.
Mine is similar, the words of "Not found detailed sku[27550199] in META-INF/com/android/detailedSKU.lst" specially!
Please!

ok now try to flash this fw, and post results - if error, post recovery.log just after flashing try.