Not install any firmware - Sony Tablet S

The problem is next. When i install new firmware with custom method i see "error code: 5". When i install any firmware with recovery mode i see
"Verifying update package
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted."
My device is Sony Tablet S with android 3.2.
build.prop
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=THMD01700
ro.build.display.id=THMD01700
ro.build.version.incremental=01700.003
ro.build.version.sdk=13
ro.build.version.codename=REL
ro.build.version.release=3.2
ro.build.date=Fri Aug 5 02:56:50 JST 2011
ro.build.date.utc=1312480610
ro.build.type=user
ro.build.user=integ-build
ro.build.host=build6
ro.build.tags=release-keys
ro.product.model=Sony Tablet S
ro.product.brand=Sony
ro.product.name=nbx03_003
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 is obsolete; use ro.product.device
ro.build.product=nbx03
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=nbx03_043-user 3.2 THMD01700 01700.003 release-keys
ro.build.fingerprint=Sony/nbx03_003/nbx03:3.2/THMD01700/01700.003:user/release-keys
ro.build.characteristics=tablet,nosdcard
# end build properties
ro.opengles.version = 131072
wifi.interface=wlan0
ro.ethernet.interface=eth0
ro.ethernet.autoEnable=yes
rild.libargs=-d /dev/ttyACM0 -i rmnet0
ro.sony.sound.enabled=true
ro.separated.external.storage=true
ro.external.storage.removable=false
ro.tether.denied=true
windowsmgr.max_events_per_sec=120
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.setupwizard.mode=DISABLED
ro.com.google.gmsversion=3.2_r1
ro.config.notification_sound=OnTheHunt.ogg
ro.config.alarm_alert=Alarm_Classic.ogg
ro.com.google.clientidbase=android-sony
ro.sony.wifisleep=0
dalvik.vm.heapstartsize=5m
dalvik.vm.heapgrowthlimit=48m
dalvik.vm.heapsize=256m
rild.libpath=/system/lib/libmbm-ril.so
keyguard.no_require_sim=1
mbm.gps.config.gps_ctrl=/dev/bus/usb/002/049
mbm.gps.config.gps_nmea=/dev/ttyACM2
mbm.gps.config.gps_pref_mode=SUPL
mbm.gps.config.supl.enable_ni=yes
ro.sony.wan.comAtMode=false
ro.sony.wan.warnNwUnavail=false
ro.sony.wan.ignorePushMsg=false
ro.sony.wan.AtnBarType=0
ro.sony.wan.dispMenuNwTyp=true
ro.sony.update.server=info.update.sony.net
ro.sony.update.category_id=ST001
ro.sony.update.service_id=nbx03_043
ro.sony.sku.base=nbx03_043
ro.sony.build.id=FF0.17.001110043
ro.sony.build.incremental=110805005
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.setupwizard.mode=DISABLED
This firmware i tried to install
signed-nbx03_001-ota-0035.001
signed-nbx03_001-ota-120410004
signed-nbx03_001-ota-120914044
signed-nbx03_001-ota-121116036
signed-nbx03_001-ota-incremental-120914044-from120803000
And i can't install root.
[AiO]
It looks that your device is [for now] not rootable...
In your kernel version exploit vulnerability has been locked down...
You need to wait for DEVs to find another way...
Click to expand...
Click to collapse
Soft and hard reset did not help.

No5feratu said:
The problem is next. When i install new firmware with custom method i see "error code: 5". When i install any firmware with recovery mode i see
"Verifying update package
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted."
My device is Sony Tablet S with android 3.2.
build.prop
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=THMD01700
ro.build.display.id=THMD01700
ro.build.version.incremental=01700.003
ro.build.version.sdk=13
ro.build.version.codename=REL
ro.build.version.release=3.2
ro.build.date=Fri Aug 5 02:56:50 JST 2011
ro.build.date.utc=1312480610
ro.build.type=user
ro.build.user=integ-build
ro.build.host=build6
ro.build.tags=release-keys
ro.product.model=Sony Tablet S
ro.product.brand=Sony
ro.product.name=nbx03_003
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 is obsolete; use ro.product.device
ro.build.product=nbx03
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=nbx03_043-user 3.2 THMD01700 01700.003 release-keys
ro.build.fingerprint=Sony/nbx03_003/nbx03:3.2/THMD01700/01700.003:user/release-keys
ro.build.characteristics=tablet,nosdcard
# end build properties
ro.opengles.version = 131072
wifi.interface=wlan0
ro.ethernet.interface=eth0
ro.ethernet.autoEnable=yes
rild.libargs=-d /dev/ttyACM0 -i rmnet0
ro.sony.sound.enabled=true
ro.separated.external.storage=true
ro.external.storage.removable=false
ro.tether.denied=true
windowsmgr.max_events_per_sec=120
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.setupwizard.mode=DISABLED
ro.com.google.gmsversion=3.2_r1
ro.config.notification_sound=OnTheHunt.ogg
ro.config.alarm_alert=Alarm_Classic.ogg
ro.com.google.clientidbase=android-sony
ro.sony.wifisleep=0
dalvik.vm.heapstartsize=5m
dalvik.vm.heapgrowthlimit=48m
dalvik.vm.heapsize=256m
rild.libpath=/system/lib/libmbm-ril.so
keyguard.no_require_sim=1
mbm.gps.config.gps_ctrl=/dev/bus/usb/002/049
mbm.gps.config.gps_nmea=/dev/ttyACM2
mbm.gps.config.gps_pref_mode=SUPL
mbm.gps.config.supl.enable_ni=yes
ro.sony.wan.comAtMode=false
ro.sony.wan.warnNwUnavail=false
ro.sony.wan.ignorePushMsg=false
ro.sony.wan.AtnBarType=0
ro.sony.wan.dispMenuNwTyp=true
ro.sony.update.server=info.update.sony.net
ro.sony.update.category_id=ST001
ro.sony.update.service_id=nbx03_043
ro.sony.sku.base=nbx03_043
ro.sony.build.id=FF0.17.001110043
ro.sony.build.incremental=110805005
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.setupwizard.mode=DISABLED
This firmware i tried to install
signed-nbx03_001-ota-0035.001
signed-nbx03_001-ota-120410004
signed-nbx03_001-ota-120914044
signed-nbx03_001-ota-121116036
signed-nbx03_001-ota-incremental-120914044-from120803000
And i can't install root.
[AiO]
Soft and hard reset did not help.
Click to expand...
Click to collapse
Please try any update twice in a row and then adb pull /tmp/recovery.log from recovery. Then post here

stifilz said:
Please try any update twice in a row and then adb pull /tmp/recovery.log from recovery. Then post here
Click to expand...
Click to collapse
I can't install drivers for recovery mod. In normal mod drivers installed and work good. Id-device is USB\VID_18D1&PID_05B3&REV_0100. And i can't see same id in android_winusb.inf file. My OS is win7 64-bit.

No5feratu said:
I can't install drivers for recovery mod. In normal mod drivers installed and work good. Id-device is USB\VID_18D1&PID_05B3&REV_0100. And i can't see same id in android_winusb.inf file. My OS is win7 64-bit.
Click to expand...
Click to collapse
Ah yes for recovery just change the REV_0999 to REV_0100 as this is the newer recovery's driver. There is a thread somewhere with the update .inf but it is simple enough to edit.
Forgot about that.
Stifilz

stifilz said:
Ah yes for recovery just change the REV_0999 to REV_0100 as this is the newer recovery's driver. There is a thread somewhere with the update .inf but it is simple enough to edit.
Forgot about that.
Stifilz
Click to expand...
Click to collapse
Make your write step by step what i must to do to install drivers for recovery mod? Please.

No5feratu said:
Make your write step by step what i must to do to install drivers for recovery mod? Please.
Click to expand...
Click to collapse
Try drivers from here http://forum.xda-developers.com/showthread.php?t=2429662

stifilz said:
Try drivers from here http://forum.xda-developers.com/showthread.php?t=2429662
Click to expand...
Click to collapse
For normal mod drivers is great. For recovery not work. Trouble is next. Id-device in normal mod - USB\VID_054C&PID_05B4&MI_01. Id-device in recovery USB\VID_18D1&PID_05B3&REV_0100 not same like normal mod and any drivers work on normal mod but not work on recovery. When i tried to rewrite id for recovery mod, drivers installed and work but adb don't see any devices.

No5feratu said:
For normal mod drivers is great. For recovery not work. Trouble is next. Id-device in normal mod - USB\VID_054C&PID_05B4&MI_01. Id-device in recovery USB\VID_18D1&PID_05B3&REV_0100 not same like normal mod and any drivers work on normal mod but not work on recovery. When i tried to rewrite id for recovery mod, drivers installed and work but adb don't see any devices.
Click to expand...
Click to collapse
Keep trying, drivers can be a mission in windows (you are not Win8 are you??)... Took me a while to. If it helps try my drivers on my 4shared. See sig.

Related

[Q] Tablet S won't upgrade

I bought a Tablet S refurbished almost two months now and since I got it I haven't been able to do the OTA upgrade to 4.0.3, every time I try to update it I either get a failure to download error or it downloads the update and it stops a quarter of the way during the install after reboot and then it starts and gives me an error code 5. I'm pretty much frustrated and I'm this close to selling it, Is this a common occurrence? Is there a simple way I can root the tablet and download and install the update?
PS. Would the fact that I bought the tablet in the US and I'm now in the Caribbean have any bearing on this?
gee_whiz said:
I bought a Tablet S refurbished almost two months now and since I got it I haven't been able to do the OTA upgrade to 4.0.3, every time I try to update it I either get a failure to download error or it downloads the update and it stops a quarter of the way during the install after reboot and then it starts and gives me an error code 5. I'm pretty much frustrated and I'm this close to selling it, Is this a common occurrence? Is there a simple way I can root the tablet and download and install the update?
PS. Would the fact that I bought the tablet in the US and I'm now in the Caribbean have any bearing on this?
Click to expand...
Click to collapse
So I emailed Sony and they say it is a RAM problem and the device has to be serviced...needless to say its outside of warranty. Has anybody ever experienced this?
gee_whiz said:
So I emailed Sony and they say it is a RAM problem and the device has to be serviced...needless to say its outside of warranty. Has anybody ever experienced this?
Click to expand...
Click to collapse
See my FAQ in signature and other link for update zips.
stifilz said:
See my FAQ in signature and other link for update zips.
Click to expand...
Click to collapse
I followed all the instructions exactly but when I try to instal OS 3.2.1 in recovery mode it gives me a signature verification error
gee_whiz said:
I followed all the instructions exactly but when I try to instal OS 3.2.1 in recovery mode it gives me a signature verification error
Click to expand...
Click to collapse
You will need to use 4.0.3 or higher, you can not install 3.2.1 if you are allready on it. Can you please upload your /system/build.prop and tell me the exact model code from the back near charger plug. I will have a lookskey and point you to the right file
stifilz said:
You will need to use 4.0.3 or higher, you can not install 3.2.1 if you are allready on it. Can you please upload your /system/build.prop and tell me the exact model code from the back near charger plug. I will have a lookskey and point you to the right file
Click to expand...
Click to collapse
Hey the model code is SGPT111US/S and here's the build.prop
*START*
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=THMAS11000
ro.build.display.id=THMAS11000
ro.build.version.incremental=11000.001
ro.build.version.sdk=13
ro.build.version.codename=REL
ro.build.version.release=3.2
ro.build.date=Mon Sep 5 00:21:41 JST 2011
ro.build.date.utc=1315149701
ro.build.type=user
ro.build.user=integ-build
ro.build.host=build10
ro.build.tags=release-keys
ro.product.model=Sony Tablet S
ro.product.brand=Sony
ro.product.name=nbx03_001
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 is obsolete; use ro.product.device
ro.build.product=nbx03
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=nbx03_001-user 3.2 THMAS11000 11000.001 release-keys
ro.build.fingerprint=Sony/nbx03_001/nbx03:3.2/THMAS11000/11000.001:user/release-keys
ro.build.characteristics=tablet,nosdcard
# end build properties
ro.opengles.version = 131072
wifi.interface=wlan0
ro.ethernet.interface=eth0
ro.ethernet.autoEnable=yes
rild.libargs=-d /dev/ttyACM0 -i rmnet0
ro.sony.sound.enabled=true
ro.separated.external.storage=true
ro.external.storage.removable=false
ro.tether.denied=true
windowsmgr.max_events_per_sec=120
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.setupwizard.mode=DISABLED
ro.com.google.gmsversion=3.2_r1
ro.config.notification_sound=OnTheHunt.ogg
ro.config.alarm_alert=Alarm_Classic.ogg
ro.com.google.clientidbase=android-sony
ro.sony.wifisleep=0
dalvik.vm.heapstartsize=5m
dalvik.vm.heapgrowthlimit=48m
dalvik.vm.heapsize=256m
ro.sony.update.server=info.update.sony.net
ro.sony.update.category_id=ST001
ro.sony.update.service_id=nbx03_001
ro.sony.sku.base=nbx03_001
ro.sony.build.id=1.10.001100001
ro.sony.build.incremental=110905000
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.setupwizard.mode=DISABLED
*END*
gee_whiz said:
Hey the model code is SGPT111US/S and here's the build.prop
*START*
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=THMAS11000
ro.build.display.id=THMAS11000
ro.build.version.incremental=11000.001
ro.build.version.sdk=13
ro.build.version.codename=REL
ro.build.version.release=3.2
ro.build.date=Mon Sep 5 00:21:41 JST 2011
ro.build.date.utc=1315149701
ro.build.type=user
ro.build.user=integ-build
ro.build.host=build10
ro.build.tags=release-keys
ro.product.model=Sony Tablet S
ro.product.brand=Sony
ro.product.name=nbx03_001
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 is obsolete; use ro.product.device
ro.build.product=nbx03
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=nbx03_001-user 3.2 THMAS11000 11000.001 release-keys
ro.build.fingerprint=Sony/nbx03_001/nbx03:3.2/THMAS11000/11000.001:user/release-keys
ro.build.characteristics=tablet,nosdcard
# end build properties
ro.opengles.version = 131072
wifi.interface=wlan0
ro.ethernet.interface=eth0
ro.ethernet.autoEnable=yes
rild.libargs=-d /dev/ttyACM0 -i rmnet0
ro.sony.sound.enabled=true
ro.separated.external.storage=true
ro.external.storage.removable=false
ro.tether.denied=true
windowsmgr.max_events_per_sec=120
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.setupwizard.mode=DISABLED
ro.com.google.gmsversion=3.2_r1
ro.config.notification_sound=OnTheHunt.ogg
ro.config.alarm_alert=Alarm_Classic.ogg
ro.com.google.clientidbase=android-sony
ro.sony.wifisleep=0
dalvik.vm.heapstartsize=5m
dalvik.vm.heapgrowthlimit=48m
dalvik.vm.heapsize=256m
ro.sony.update.server=info.update.sony.net
ro.sony.update.category_id=ST001
ro.sony.update.service_id=nbx03_001
ro.sony.sku.base=nbx03_001
ro.sony.build.id=1.10.001100001
ro.sony.build.incremental=110905000
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.setupwizard.mode=DISABLED
*END*
Click to expand...
Click to collapse
Oh you are on 3.2. Also you are US region?? Then look here http://www.4shared.com/folder/LwQh2332/SONY.html the file you want aka 3.2.1R2 is 0042.001.zip. NB: If you install ICS R1a or higher (i think) you can not go back to HC. If you like it then stay. also note that this 3.2.1R2 IS ROOTABLE
EDIT: If that does not work then please try 0035 then 0042

Android Advice

Hi, I have a car media system which has android 4.0.4 ICS on it. I need advice please on why my GPS UTC time is 3 hours earlier and the local time is 2 hour earlier than the system when I run an app called GPS Test. I am in the UK.
Here is my build.prop info as I also would like to know if there are any firmware upgrades I can do without flashing the wrong one. The system is rooted.
Does this look right to you??
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=IMM76D
ro.build.display.id=full_m805_8925-eng 4.0.4 IMM76D eng.root.20121022.190818 test-keys
ro.build.version.incremental=eng.root.20121022.190818
ro.build.version.sdk=15
ro.build.version.codename=REL
ro.build.version.release=4.0.4(V2.1 2013-03-21)
ro.build.date=Mon Oct 22 19:12:41 PDT 2012
ro.build.date.utc=1350958361
ro.build.type=eng
ro.build.user=root
ro.build.host=ubuntu
ro.build.tags=test-keys
ro.product.model=Telechips M805S TCC8925 NAND V7 Board
ro.product.brand=Android
ro.product.name=full_m805_892x
ro.product.device=m805_892x
ro.product.board=m805_892x_evm
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=telechips
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=tcc892x
# ro.build.product is obsolete; use ro.product.device
ro.build.product=m805_892x
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=full_m805_892x-eng 4.0.4 IMM76D eng.root.20121022.190818 test-keys
ro.build.fingerprint=Android/full_m805_892x/m805_892x:4.0.4/IMM76D/eng.root.20121022.190818:eng/test-keys
ro.build.characteristics=tablet,sdcard
# end build properties
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.com.android.dateformat=MM-dd-yyyy
ro.config.ringtone=Ring_Synth_04.ogg
ro.config.notification_sound=pixiedust.ogg
ro.config.alarm_alert=Alarm_Classic.ogg
ro.system.hdmi_max_resolution=fullhd
persist.sys.renderer_onthefly=true
ro.system.hdmi_active=true
ro.system.composite_active=true
persist.sys.composite_resize=3
ro.system.component_active=false
tcc.output.component_mode=0
ro.system.hdmi_portable=true
ro.system.osd_active=false
wifi.interface=wlan0
wifi.supplicant_scan_interval=15
debug.egl.hw=1
ro.display.switch=1
ro.system.audio_active=false
persist.sys.strictmode.disable=true
persist.sys.strictmode.visual=false
tcc.video.vsync.support=1
tcc.video.surface.support=1
ro.opengles.version=131072
ro.sf.lcd_density=145
dalvik.vm.heapstartsize=5m
dalvik.vm.heapgrowthlimit=48m
dalvik.vm.heapsize=368m
tcc.all.hdmi.720p.fixed=0
tcc.all.video.call.enable=0
tcc.all.camera.no.display=0
tcc.video.lplayback.mode=0
tcc.all.web.full.video=0
tcc.show.video.fps=0
tcc.hwc.disable=0
tcc.all.output.support.camera=0
tcc.media.rtsp.cusset=1
tcc.media.rtsp.starttime=10
tcc.media.rtsp.autimeout=10
tcc.media.rtsp.eos=1
tcc.media.rtsp.seekend=3
ro.kernel.android.checkjni=0
ro.setupwizard.mode=OPTIONAL
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
How did you root this device ?
Ive got a device with the same info, how did you manage to root this unit ?
BR
It came already rooted.
Sent from my HTC One using XDA Premium HD app
Help
I have the same problem with my chinese RNS system, also the GPS speed displayed is in KM/H but the readout is in knots, so if i drive around 100 km/h it shows 180 ish km/h in IGO...
Please help?? Google play says my device is a:
telechips m805s tcc8925 nand v7 board
Thanks in advance!
Greetings from Holland!

[Q] Sony tablet S boots normally only on second boot, but not on first

Hi,
I have Sony Tablet S with 4.0.3 R5a which was rooted with condi AIO tool, and also i had installed the mods: Install init.d support, Install "rescue-backdoor".
I wanted to return it to stock, so I unrooted it with condi AIO tool, and did a factory reset. After the reset i went in recovery and flashed the latest firmware signed-nbx03_009-ota-121116046.zip for my device, the procedure finished successfully, but on the reboot the tablet was stuck at Sony logo. After a power off with the off button, and powering it on again it boots normally, but from now on on first boot it stays at Sony logo, and on second boot it boots normally.
Is there a fix for this?
What i understand is that there are two system partitions, and one of them is somehow corrupted and that's why it only boots normally on second boot.
build.prop
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=TISU0143
ro.build.display.id=TISU0143
ro.build.version.incremental=121116032
ro.build.version.sdk=15
ro.build.version.codename=REL
ro.build.version.release=4.0.3
ro.build.date=Fri Nov 16 04:09:27 JST 2012
ro.build.date.utc=1353006567
ro.build.type=user
ro.build.user=integ-build
ro.build.host=build8
ro.build.tags=release-keys
ro.product.model=Sony Tablet S
ro.product.brand=Sony
ro.product.name=SYS_001
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 is obsolete; use ro.product.device
ro.build.product=nbx03
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=SYS_001-user 4.0.3 TISU0143 121116032 release-keys
ro.build.fingerprint=Sony/SYS_001/nbx03:4.0.3/TISU0143/121116032:user/release-keys
ro.build.characteristics=tablet
# end build properties
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.display.release=release5a
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.product-res-path=vendor/framework/SemcGenericUxpRes.apk
ro.sony.autovolume.threshold=10
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
drm.service.enabled=true
dalvik.vm.heapstartsize=5m
dalvik.vm.heapgrowthlimit=48m
dalvik.vm.heapsize=256m
ro.sony.wifisleep=0
ro.semc.xloud.supported=true
ro.somc.clearphase.supported=true
ro.setupwizard.mode=DISABLED
ro.com.google.gmsversion=4.0_r3
ro.com.google.clientidbase=android-sony
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.sony.wan.ipv6.enable=false
ro.sony.dlna_dms.enabled=false
ro.somc.social_product_model=PRODUCT_MODEL_TABLET
ro.sony.irremote.protocol_type=1
ro.sony.ols.eula=0
Click to expand...
Click to collapse
vendor.prop
ro.sony.update.service_id=nbx03_009
ro.sony.sku.base=nbx03_009
ro.sony.build.id=TISU0093410
ro.sony.build.incremental=111104048
Click to expand...
Click to collapse
How can i check which system partition is booting from, is it system 0 or system 1?
When it boots up normally i cant find the recovery.log because there is no /tmp partition?
mickeymkd said:
How can i check which system partition is booting from, is it system 0 or system 1?
When it boots up normally i cant find the recovery.log because there is no /tmp partition?
Click to expand...
Click to collapse
/tmp is only available in recovery menu, not on normal boot.
To see what is currently mounted use either
adb shell
mount
from a pc or
mount
from terminal on the device iteself
from there look for system, you will see mmcblk0p2 or 3 (Tablet S) or mmcblk0p3 or 4 (Xperia S)
Let me know if you get stuck
The currently mounted partition is mmcblk0p2. Its the partition when the tablet boots normally.
When i try in recovery to flash the latest firmware from sd, on first boot when the tablet gets stuck on sony logo, the flashing process is successful., but when i try the same procedure on second boot, when it boots normally, it fails when is checking the build version, because is the same with the version installed.
Later i saw the OTA system updates and notifications were disabled, so i rooted the tablet again enabled the notifications, when it restarted, it informed me about new update 4.0.3 r5a which was already installed, so i downloaded and run the update. After it had finished with the update the tablet booted up normally on first but, but when it was booted in the OS i got a message about system update failed, with error code 0. and after that the tablet boots normally but i get the OTA system notifications that there is a new update 4.0.3 r5a, which is strange.
how can i mount the second system partition, and how to copy its content to PC?

[ROM] zaizado gt-i9152 final

OFFICIAL ROM GT-I9152​
BUILD.PROP​
Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=JDQ39
ro.build.display.id=JDQ39.I9152XWUAML3.ZAIZADO
ro.build.version.incremental=I9152XWUAML3
ro.build.version.sdk=17
ro.build.version.codename=REL
ro.build.version.release=4.2.2
ro.build.date=Mon Dec 23 17:42:08 KST 2013
ro.build.date.utc=1387788128
ro.build.type=user
ro.build.user=se.infra
ro.build.host=SEP-112
ro.build.tags=release-keys
ro.product.model=GT-I9152
ro.product.brand=samsung
ro.product.name=craterxx
ro.product.device=crater
ro.product.board=capri
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=samsung
ro.product.locale.language=en
ro.product.locale.region=GB
ro.wifi.channels=
ro.board.platform=capri
# ro.build.product is obsolete; use ro.product.device
ro.build.product=crater
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=craterxx-user 4.2.2 JDQ39 I9152XWUAML3 release-keys
ro.build.fingerprint=samsung/craterxx/crater:4.2.2/JDQ39/I9152XWUAML3:user/release-keys
ro.build.characteristics=phone
# Samsung Specific Properties
ro.build.PDA=I9152XWUAML3
ro.build.hidden_ver=I9152XWUAML3
ro.build.changelist=1963860
ro.product_ship=true
ro.chipname=capri
# end build properties
#
# system.prop for capri
#
rild.libpath=/system/lib/libbrcm_ril.so
#rild.libargs=-d /dev/ttyS0
ro.sf.lcd_density=240
ro.lcd_brightness=123
ro.lcd_min_brightness=20
# MultiTouch support
ro.product.multi_touch_enabled=true
ro.product.max_num_touch=2
ro.kernel.qemu=0
ro.tvout.enable=true
persist.sys.storage_preload=1
net.streaming.rtsp.uaprof=http://wap.samsungmobile.com/uaprof/
# Multimedia property for Smart View
media.enable-commonsource=true
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.opengles.version=131072
debug.hwui.render_dirty_regions=false
brcm.graphics.async_errors=true
brcm.hwc.no-hdmi-trans=1
ro.error.receiver.default=com.samsung.receiver.error
dalvik.vm.heapstartsize=8m
dalvik.vm.heapgrowthlimit=64m
dalvik.vm.heapsize=256m
drm.service.enabled=true
ro.sf.lcd_density=240
ro.sec.fle.encryption=true
ro.crypto.support=recovery_mount|others
ro.config.ringtone=S_Over_the_horizon.ogg
ro.config.ringtone_2=02_Fog_on_the_water.ogg
ro.config.notification_sound=S_Whistle.ogg
ro.config.notification_sound_2=S_On_time.ogg
ro.config.alarm_alert=Walk_in_the_forest.ogg
ro.config.media_sound=Media_preview_Touch_the_light.ogg
ro.url.legal=http://www.google.com/intl/%s/mobile/android/basic/phone-legal.html
ro.url.legal.android_privacy=http://www.google.com/intl/%s/mobile/android/basic/privacy.html
keyguard.no_require_sim=true
ro.com.android.dateformat=MM-dd-yyyy
ro.carrier=unknown
ro.com.google.clientidbase=android-samsung
ro.ril.hsxpa=1
ro.ril.gprsclass=10
ro.adb.qemud=1
ro.com.google.gmsversion=4.2_r3
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
FEATURE
- DEODEX
- SLIM
- ORIGINAL WITHOUT MODIFICATION
- NO TWEAK
- INCLUDE BOOT.IMG​
HOW TO INSTALL​
1. Sure you have custom recovery (recomended using twrp)
2. Copy download file to sd card
3. Now go to twrp (shutdown your device – press home – vol up - power)
4. Backup your phone
5. Go wipe tab (WIPE DATA, WIPE CACHE, WIPE DALVIK)
6. Go back to home and install the rom ( select from sdcard)
7. Your just waiting up to all installation proses done.
8. Clear dalvik and chace
9. Reboot
DOWNLOAD ROM​https://drive.google.com/uc?id=0ByRCPLfevAtdQXYteVFvbGVMTTA&export=download
install google crack if you have problem with google play service
DOWNLOAD CRACK GOOGLE PLAY SERVICE
Screenshots pls
Sent from my GT-I9152 using XDA Premium 4 mobile app
thanks,bro. would like to have a try,but fail to download from drive.goole.com. Would you please upload it to Dev-Host,if possible.thanks again.
Thanks for the effort for this ROM. I wanted to try but it is based on a quite old firmware version. My mega now on ANA6 and that is not even the latest which is ANC2.
Will wait for an updated version based on latest firmware.,
ini gak ada SS-nya gan ?
isn't any SS of this ROM yet bro ?

[Q] help i have a soft bricked rca tablet

Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=JRO03H
ro.build.display.id=JRO03H
ro.build.version.incremental=V1.00-20130809.001225
ro.build.version.sdk=16
ro.build.version.codename=REL
ro.build.version.release=4.1.1
ro.build.date=Fri Aug 9 00:13:05 HKT 2013
ro.build.date.utc=1375978385
ro.build.type=user
ro.build.user=pf
ro.build.host=server70
ro.build.tags=release-keys
ro.product.model=RCT6077W2
ro.product.brand=RCA
ro.product.name=RCT6077W2
ro.product.device=RCT6077W2
ro.product.board=rk2928sdk
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=Foxconn International Holdings Limited
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=rk2928
# ro.build.product is obsolete; use ro.product.device
ro.build.product=rk2928sdk
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=rk2928sdk-user 4.1.1 JRO03H 20130809.001225 release-keys
ro.build.fingerprint=RCA/RCT6077W2/RCT6077W2:4.1.1/JRO03H/V1.00-20130809.001225:user/release-keys
ro.build.characteristics=tablet
# end build properties
#
# system.prop
#
#rild.libpath=/system/lib/libreference-ril-23d.so
#rild.libpath=/system/lib/libreference-ril.so
#rild.libargs=-d /dev/ttyUSB2
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.com.android.dateformat=MM-dd-yyyy
ro.config.ringtone=Ring_Synth_04.ogg
ro.config.notification_sound=pixiedust.ogg
ro.carrier=wifi-only
ro.config.alarm_alert=Alarm_Classic.ogg
dalvik.vm.heapstartsize=5m
dalvik.vm.heapgrowthlimit=64m
dalvik.vm.heapsize=256m
ro.config.facelock=enable_facelock
persist.facelock.detect_cutoff=5000
persist.facelock.recog_cutoff=5000
persist.sys.usb.config=mtp
persist.sys.strictmode.visual=false
dalvik.vm.jniopts=warnonly
ro.rksdk.version=RCT6077W2-ANDROID4.1.1-v1.0.3
sys.hwc.compose_policy=6
sf.power.control=2073600
ro.sf.fakerotation=true
ro.sf.hwrotation=270
ro.rk.MassStorage=false
wifi.interface=wlan0
ro.sf.lcd_density=120
ro.rk.screenoff_time=300000
ro.rk.def_brightness=178
ro.rk.homepage_base=http://www.google.com/webhp?client={CID}&source=android-home
ro.rk.install_non_market_apps=false
ro.rk.wifi_on=false
ro.default.size=100
persist.sys.timezone=America/New_York
ro.product.usbfactory=RCA_usb
wifi.supplicant_scan_interval=15
ro.opengles.version=131072
ro.rk.systembar.voiceicon=false
testing.mediascanner.skiplist=/mnt/sdcard/Android/
ro.kernel.android.checkjni=0
ro.eboda.modem=false
ro.rk.ethernet_enable=false
ro.com.google.clientidbase=android-fih
ro.com.google.gmsversion=4.1_r5
ro.setupwizard.mode=OPTIONAL
ro.com.widevine.cachesize=16777216
ro.rk.bt_enable=false
rild.libargs=-d_/dev/ttyUSB1
ril.pppchannel=/dev/ttyUSB2
rild.libpath=/system/lib/libril-rk29-dataonly.so
ril.function.dataonly=1
ro.product.version=1.0.3
ro.product.ota.host=tablet2.gyrodock.com:2300
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
Model Id: Rct6077w2
i have 2 tablets.. one in working order and the other is bricked....but the working tablet has a crack accross screen...is there a way i can making a bottable ROM from my working tablet? and if so can someone tell me how thanks...and it seems as if i never get help on this forum..........very freaking sad that neither this forum or rca wants to help me
added more details of uild prop ...can someone help me......swear you guys are never gonna help me but for why? atm it wont boot past RCA logo..i tried to change the DPI of my now bricked tablet ....and i unrooted it like a dumb ass ...now idk what to do..is there a way i can make a boot image or something i can fix my bricked tablet with? i have access to one tablet in full but everywhere i go says i need root access for both tablets which is freaking annoying..please help me guys and stop just viewing this forum thank you!!!
Search for "CREATE OWN ROM FOR ANY ANDROID DEVICE" in this forum, I cannot provide the link as I am a new user
Maybe you can make a ROM out of your working tablet to flash on the bricked one...
Good luck
el-figurin said:
Search for "CREATE OWN ROM FOR ANY ANDROID DEVICE" in this forum, I cannot provide the link as I am a new user
Maybe you can make a ROM out of your working tablet to flash on the bricked one...
Good luck
Click to expand...
Click to collapse
i respect everything uve ried to do but still wont work atm...ive tried

Categories

Resources