I cant get the update to root. below attachment you can see the screenshot. please tell me wot im doing wrong 
Attachments
-
75.8 KB Views: 301
Many questions, no answer. Condi?Thanks for the replies
I don't think the massive red text saying to not change the region after flashing was there on the first page this morning and I read the last 2 pages of the topic last thing the night before and it didn't say anything about not changing the region.
Then after it didn't work I checked the topic again and saw the massive warning saying not to change the region post-update.
Hoping there is some solution to this. Does anyone know if the tablet will be UK or USA region now?
Assuming the backdoor has lowered the version number then I should be able to flash to a stock ICS rom but every rom I try fails. Is this because there is not yet a rom for Europe and the region did in fact change to UK whilst also corrupting the installed firmware?
Thanks
Robin
Same thing here. Condi, I sent you my recovery.log via PM. Hope that helps.Done but The same problem:
...........
Verifying update package...
Erohibit update as a result of cecking version or base sku
Installation aborted
That's what happened to me. I might've just flashed decrypted ROM instead of custom update. Unfortunately you're stuck without root.US version.
Created custom_update_signed.zip had trouble getting _hack_recovery.zip to work correctly. Once updated USB drivers it worked and I applied the custom update, but now I don't have root and I don't see tempsu or busybox files anywhere on the system.
Is it possible to rollback? Can custom recovery help me here? Can I install signed 3.x rom?
At least I have a working ICS tablet.
My problem is that I did flash the custom_update that I created.That's what happened to me. I might've just flashed decrypted ROM instead of custom update. Unfortunately you're stuck without root.
Sent from my Sony Tablet S using XDA
I think I got that message because I had previously disabled the update messages via the AIO. Then, when I updated to ICS, the original update message from Sony, (that had been AIO blocked) was still resident as a hold-over from the previously installed Sony Honeycomb OS.What did you do to get this message? Did you change some values in build.prop or vendor.prop?
Hi condi, V2 works perfectAttached fix working one, the last one had to be changedunpack to AiO directory, run, done.
Remember to have correct (new) drivers for ICS ADB!
br
condi
Many thanks for your interest in Sony Tab S development obicom.Curious, nobody else (as I know) got this message.
Could you be so kind to post your build.prop and vendor.prop?
I would like to compare it with my own.
That would be great .. thanks in advance.
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=TISU0077
ro.build.display.id=TISU0077
ro.build.version.incremental=120410002
ro.build.version.sdk=15
ro.build.version.codename=REL
ro.build.version.release=4.0.3
ro.build.date=Tue Apr 10 01:08:41 JST 2012
ro.build.date.utc=1333987721
ro.build.type=user
ro.build.user=integ-build
ro.build.host=build9
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 TISU0077 120410002 release-keys
ro.build.fingerprint=Sony/SYS_001/nbx03:4.0.3/TISU0077/120410002: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
#
# ADDITIONAL_BUILD_PROPERTIES
#
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
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.sony.wan.ipv6.enable=false
ro.sony.dlna.dtcp_pext=0
ro.sony.update.service_id=nbx03_001
ro.sony.sku.base=nbx03_001
ro.sony.build.id=TISU0017700
ro.sony.build.incremental=111104048
Thank you very muchThanks Condi. Just donated $10. Get yuor wife a drink.
Had some problems but following suggestions on this forum now have rooted 4.0.3 2.6.39.4 [email protected]#1. TisU0017700. Live in UK.
Followed your script and failed as some others. Did-
install java 64 bit which resoved java errors. initally got 128Mb file so copied decripted file back to PC and run again wgich gave me 240Mb file.
Rooting works fine, Titanium backup has worked on all apps.[...]
You will not loose ADB functionality. Its all ok with ICS and ADB. You should be able to flash with 3G versionCondi I have a 3g tab if you remember. So if I update now without 3g and loose ADB functionality will I be able to flash again when 3g version is available![]()
@bambo
Do you get this update message? I would be happy I get it, but my tablet say I have the newest version (no backdoor and I am a liitle bit afraid about this)
What did you do to get this message? Did you change some values in build.prop or vendor.prop?
'rescue-backdoor' should work just fine.Curious, nobody else (as I know) got this message.
Could you be so kind to post your build.prop and vendor.prop?
DONT USE region changer, because it has only S regions available.im using the tablet p , and i want to know how to change its Region?
just use the same app? allinone?
GoodHi condi, V2 works perfect
Tested wirth Root Check Pro and all is perfect.
(Sorry for late answer !!!)
br
tbzdat00
Thanks friend, I couldn't express it betterPlease give Condi a chance to reply folks. He is newly married and must have spent a lot of time getting us this far. I can appreciate that some of you may have non working devices but its too early to say they are bricked. Let those one here (not including me) who know about these things get to the bottom of this. It may be that condi is working on this now and can only report back when he has something concrete to feed back on.
Thanks to Condi and all thoses that have a working ICS device please donate to him to give him some encouragement.
John
where can I found the ROM you talk about?I have an Italian Device...My problem is now fixed.
Thanks a lot to Condi for giving up his time to get my tablet de-bricked!
ICS is still rooted and working well and I won't change the region again!
The solution involved downgrading back to 3.2.1 using a specific rom and then repeating the process using the AIO tool. I think the specific rom varies depending on the region which is set and the model of the S.
Thanks again.
Robin