Post Reply

One more sony tablet S bricked. Need help

OP Riscas

18th May 2014, 02:06 AM   |  #1  
OP Junior Member
Thanks Meter: 3
 
3 posts
Join Date:Joined: Dec 2011
Hi,

I have a sony tablet s and it froozed in google chrome and never came back to life.
It's stuck in sony logo. I have the most recent firmware installed with condi tool with root.

Here's my recovery log:

Starting recovery on Sun May 18 01:09:57 2014
can't open /dev/tty0: No such file or directory
framebuffer: fd 3 (1280 x 800)
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /configs ext2 /dev/block/mmcblk0p1 (null) 0
2 /system0 ext4 /dev/block/mmcblk0p2 (null) 0
3 /system1 ext4 /dev/block/mmcblk0p3 (null) 0
4 /cache ext4 /dev/block/mmcblk0p4 (null) 0
5 /misc emmc /dev/block/mmcblk0p5 (null) 0
6 /staging ext4 /dev/block/mmcblk0p6 (null) 0
7 /blflags ext4 /dev/block/mmcblk0p7 (null) 0
8 /datapp ext4 /dev/block/mmcblk0p8 (null) 0
9 /log ext4 /dev/block/mmcblk0p9 (null) 0
10 /data ext4 /dev/block/mmcblk0p10 (null) 0
11 /vsdcard vfat /dev/block/mmcblk0p11 (null) 0
12 /sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1 0
13 /boot emmc boot (null) 0
14 /recovery emmc recovery (null) 0
15 /system ext4 system (null) 0
16 /vendor0 ext4 /datapp/vendor/vendor0.img (null) 0
17 /vendor1 ext4 /datapp/vendor/vendor1.img (null) 0

Command: "/sbin/recovery"

ro.secure=1
ro.allow.mock.location=0
ro.debuggable=0
persist.sys.usb.config=mtp
ro.build.id=TISU0077
ro.build.display.id=TISU0077
ro.build.version.incremental=120410009
ro.build.version.sdk=15
ro.build.version.codename=REL
ro.build.version.release=4.0.3
ro.build.date=Tue Apr 10 01:43:14 JST 2012
ro.build.date.utc=1333989794
ro.build.type=user
ro.build.user=integ-build
ro.build.host=build6
ro.build.tags=test-keys
ro.product.model=Sony Tablet S
ro.product.brand=Sony
ro.product.name=SYS_002
ro.product.device=nbx03
ro.product.board=nbx03
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=Sony
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=tegra
ro.build.product=nbx03
ro.build.description=SYS_002-user 4.0.3 TISU0077 120410009 test-keys
ro.build.fingerprint=Sony/SYS_002/nbx03:4.0.3/TISU0077/120410009:user/test-keys
ro.build.characteristics=tablet
ro.opengles.version=131072
wifi.interface=wlan0
ro.ethernet.interface=eth0
ro.ethernet.autoEnable=yes
rild.libargs=-d /dev/ttyACM1 -i rmnet0
windowsmgr.max_events_per_sec=120
ro.tether.denied=true
ro.sony.sound.enabled=true
ro.sony.update.server=info.update.sony.net
ro.sony.update.category_id=ST001
ro.config.notification_sound=OnTheHunt.ogg
ro.config.alarm_alert=Alarm_Classic.ogg
dalvik.vm.heapstartsize=5m
dalvik.vm.heapgrowthlimit=48m
dalvik.vm.heapsize=256m
ro.sony.wifisleep=0
drm.service.enabled=true
ro.setupwizard.mode=DISABLED
ro.com.google.gmsversion=4.0.3_r0
ro.com.google.clientidbase=android-sony
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
net.change=net.bt.name
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.sony.wan.ipv6.enable=false
ro.sony.dlna.dtcp_pext=0
ro.factorytest=0
ro.bootmode=unknown
ro.baseband=unknown
ro.carrier=unknown
ro.bootloader=0x00000008
ro.hardware=nbx03
ro.revision=0
init.svc.recovery=running
init.svc.nfx_daemon=running
init.svc.adbd=running


-- Install /sdcard ...
Finding update package...
I:Update location: /sdcard/signed-nbx03_011-ota-121116066.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 -> 121116066
Not found detailed sku[27550199] in META-INF/com/android/detailedSKU.lst
E:Prohibit update as a result of checking version or base sku
Installation aborted.
Starting recovery on Sun May 18 01:10:52 2014
can't open /dev/tty0: No such file or directory
framebuffer: fd 3 (1280 x 800)
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /configs ext2 /dev/block/mmcblk0p1 (null) 0
2 /system0 ext4 /dev/block/mmcblk0p2 (null) 0
3 /system1 ext4 /dev/block/mmcblk0p3 (null) 0
4 /cache ext4 /dev/block/mmcblk0p4 (null) 0
5 /misc emmc /dev/block/mmcblk0p5 (null) 0
6 /staging ext4 /dev/block/mmcblk0p6 (null) 0
7 /blflags ext4 /dev/block/mmcblk0p7 (null) 0
8 /datapp ext4 /dev/block/mmcblk0p8 (null) 0
9 /log ext4 /dev/block/mmcblk0p9 (null) 0
10 /data ext4 /dev/block/mmcblk0p10 (null) 0
11 /vsdcard vfat /dev/block/mmcblk0p11 (null) 0
12 /sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1 0
13 /boot emmc boot (null) 0
14 /recovery emmc recovery (null) 0
15 /system ext4 system (null) 0
16 /vendor0 ext4 /datapp/vendor/vendor0.img (null) 0
17 /vendor1 ext4 /datapp/vendor/vendor1.img (null) 0

My region is Portugal, and i tried many firmware files out here, but in recovery none of them are installed.
Anyone has a clue what to do?

Thanks
Last edited by Riscas; 18th May 2014 at 02:17 AM.
23rd May 2014, 10:13 PM   |  #2  
Junior Member
Thanks Meter: 1
 
18 posts
Join Date:Joined: Apr 2014
Oi! Tens o firmwire de origem mas o honeycomb para a nossa maquina?pode resolver...nao encontro isso em lado nenhum e ja foi retirado dos servidores da sony

Sent from my ALCATEL ONE TOUCH 997D using XDA Free mobile app
Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes