yashsingh1/xdaforums huggingface dataset:
[Sony Tablet S] jappaj:
Wow. Something is f***ed on your /system/xbin, no wonder you had trobules with root if I remember correctly? su binary does have wrong permissions (that's why it did not work) and all the busybox symlinks are gone but instead of that you have actually those busybox binaries stored as regular files :eek:

Otherwise AiO un-root would clean everything for good (just read it thorugh), but that busybox problem actually will prevent it cleaning your device fully. Thugh, if you don't mind that there are unecessary some files left on your filesystem, then just run AiO un-root and you should be fine.

Please also notices that there are files like this on your filesystem:

-rw-rw-rw- root root 0 2013-04-18 20:11 _custom_update_made_with_S.onyTablet.S_AiO_tool_by_condi_

So flasher did leave some tags to your filesystem and if you sell your device, buyer can easily detect this if she or he roots and checks what files there are...
[Sony Tablet S] SWFlyerUK:
Can I not just delete them?
[Sony Tablet S] jappaj:
Yes you can just delete them. But I would also delete all that busybox stuff... Wait a second, I will try to figure out if there is any fast way to do it.
[Sony Tablet S] condi:
run 'rescue-backdoor', it will give you possibility to reflash jb stock ota. easy in two steps. thats all.
[Sony Tablet S] jappaj:
As you can see from dump he gave us, he already has done that.
[Sony Tablet S] SWFlyerUK:
Just done the rescue back door and was prompted for a system update. Will do that now. See what happens...
[Sony Tablet S] condi:
one stock flash = one system partition flashed. as you can see from dump there is only one "_custom..." file. there was a way to flash twice in a row to get both sys flashed.

with root on current sys he can also overwrite rooted sys with second sys partition via dd.

plenty of ways.
[Sony Tablet S] jappaj:
Ah I see what you mean! Sorry. That could work...

Edit: Just updated xtsdump.zip on first post to dump also sysothers app, bin and xbin to see what files reside on there. Of course, after OTA flash, it won't work as running system is no longer rooted.
[Sony Tablet S] jappaj:
Btw, to flash two times in a row, would you still need to re-root the device after first flash in order to decrease incremental so that device will offer OTA update again? And then flash it again after which both system partitions are flashed to contain proper JB, but then the other system partition still will have those root-related files in place?
[Sony Tablet S] condi:
as far as i remember there was a way to: flash, then after second 'dot' reboot straight into recovery and flash again.
[Sony Tablet S] SWFlyerUK:
Just did a system update, but again it hangs at boot. I can still reboot back into JellyBean though.

I'm selling this device through CeX, so they do some checks before they buy it off me, they then sell it on themselves so if they've not done some checks. Not my fault.
[Sony Tablet S] jappaj:
Dump? :)
[Sony Tablet S] jappaj:
Yeah, it seems everything were flashed properly, but system just won't boot from the freshly flashed partition thus you cannot make second flash to flash your current system... If Sony ever releases new update, this would fix your problem most likely, but currently no. Or whatdo you think [MENTION=422959]condi[/MENTION] ?

I would just manually clean all the stuff from current system. Or rather write script to do it... I could try this evening to make such script...
[Sony Tablet S] SWFlyerUK:
If you have the time, I would much appreciate it jappaj.
[Sony Tablet S] jappaj:
Updated xtsdump.zip, please udpate it...

Also created xtsunroot.zip, which contains unroot script. Now... It is dangerous. It automatically deletes quite a lot of stuff. I tried it on my XTS and it perfectly unrooted and cleaned everything so it seems to work. But still, ALWAYS at own risk...

Next problem is, that how can you verify that you have unrooted :) I have no idea which I couold easily enough exaplain... Perhaps if you unroot, then re-root with motochopper, then run xtsdump and then again unroot, we could see from that dump that is there anyrthing unecessary left and just trust that xtsunroot.bat cleans rest...

Edit: And still it is detectable that you have rooted since you have run rescue-backdoor tweaks and everything. Probably anybody won't notice ever, though...
[Sony Tablet S] SWFlyerUK:
Does anyone have the default build & vendor.prop increment values? As the system update is constantly there.

Your root clean up worked - I've then re-rooted with motochopper and will unroot again when things are clean.
[Sony Tablet S] jappaj:
Well since your vendor1 is flashed from JB OTA zip, it already has correct value:

ro.sony.build.incremental=130329011

You can just copy vendor.prop from vendor1 to vendor0 (be very carefult not to mess permissions etc, use cp -p always, not plain cp etc.)

Just as well as you have JB other system flashed, you can check build.prop values from there. But problem is, your other system is GB while your current system is US... Don't know what happens if you just copy it, will it cause any problems... There are other differences than build number also, you know!

Though, must be quite a buyer to actually found out that your build numbers do not match! I mean, generic Android knowledge will allow you to find out that device was rooted, but to check XTS specific property values and actually understand them!

Couldn't you just try to sell your device as pre-rooted? You may get just as good price like that and it should be now in fully functioning condition so even if buyer checks this thread, he will not demdns his or hers money back...
[Sony Tablet S] SWFlyerUK:
Thanks mate, just changed all the values, the update notification has gone and software is upto date!

I get what you mean about being pre-rooted. I believe this maybe something that is checked by the company first, so I would rather un-root it.

In SuperSU, the binary no updates which is interesting - used to fail. Log attached if required :)

I'm not too bothered about it not being able to update - I'd be suprised if Sony released an update for this tablet again..
[Sony Tablet S] jappaj:
Man, I think you did something wrong... From your dump I can see this:

************ /datapp/vendor/vendor0/vendor.prop ************

ro.sony.build.incremental=111104048

************ /datapp/vendor/vendor1/vendor.prop ************

ro.sony.build.incremental=130329011

So your vendor0 vendor.prop is untouched and indicates thus that you have rooted your device... And also:

************ /system/build.prop ************

ro.build.version.incremental=130329011

************ /data/local/tmp/sysother/build.prop ************

ro.build.version.incremental=130329002

Noooo :) You put value from vendor1 vendor.prop to system build.prop but those values should not be the same! As you can see from sysother's build.prop, correct JB incremental value is:

ro.build.version.incremental=130329002

Also I found something else which can be detected that you had root:

/system/app/su.apk

Hmm what is this??? Disguised Superuser or SuperSU? :eek: Don't know about this, I do not have it, perhaps it's elgitimate, perhaps not...

/system/bin/.ext

I do not know where this is from. I had it also. It has .su file inside if I am correct :eek: Does anybody know wtf this is?

/system/bin/sysinit

Sounds important (I would not have courage to remove, sysinit is quite iportant Linux thing) but yet still I do not have it and date does not match with other system files... Could be some installed AiO tweak like init.d? Which brings me to this:

/system/xbin/run-parts

Yeah, most likely that init.d tweak? Did you install it?

Also, I do not know if that init.d tweak modified any other system file... Geez, quite a hard to remove EVERYTHING :) It would be almost easier to write script, which takes OTA update ZIP and checks everythign against it...
[Sony Tablet S] SWFlyerUK:
So all vendor and build.props should show: ro.build.version.incremental=130329002 ?

Haven't installed any init.d tweak either - su.apk is ChainFire's SU.
[Sony Tablet S] jappaj:
No, different values in build.prop and vendor.prop Look those vendor1 vendor.prop and sysother build.prop values, they are correct ones. Different value in build.prop and vendor.prop.
[Sony Tablet S] jappaj:
I wrote a quick'n'dirty script for you... Attached. It will diff system.img from OTA zip and your current system state. If you wish to run it, please put system.img file from your own region's (GB!!!) JB OTA zip (you need to decrypt if first, but we did it few days ago already with desklunvr, remember?). Then run this script (it should not be dangerous).

You will get file which tell differences (I hope, haven't had much time to test) between that system.img and your current system. It would we very interesting to see, also it will tell what are the differences between US and GB firmwares since you current system is US due to flasher!

Now I am too tired so good night!
[Sony Tablet S] SWFlyerUK:
Sorry it took so long - have been away from my main PC.

Have attached all three text files produced :)
[Sony Tablet S] jappaj:
Hmmm weird, those all files are existing but empty... Could you download xtskit.zip from opening post and run xtsdiff.bat from it? I developed it a lot further. It can also diff other system, if you put systemoth.img to your sdcard (just copy system.img to systemoth.img since you have the same JB on both partitions)...
[Sony Tablet S] SWFlyerUK:
Not sure what you mean by systemoth.img so I took system.img, copied it and renamed it to systemoth.img.

I've attached the new logs.
[Sony Tablet S] jappaj:
That's what I meant.

Checked your diffs and oh boy... Are you 100% that you used correct system.img? GB JB, right? Because those diffs shows that your systems every single file (well almost) differs from equivalent files from system.img! I really don't think that's possible, could you double check that you used correct syste.img?

For comparision, my diffs shows only su and busybox to differ from system.img (since they do not exist in system.img), nothing else!

- Jari
[Sony Tablet S] SWFlyerUK:
Yep, defo GB JB was used :good:
[Sony Tablet S] jappaj:
Wow... I cannot promise when I have some time, I could manually crosscheck few files to see w*f is going on, but currently I am quite busy...
[Sony Tablet S] SWFlyerUK:
Ah - I was wrong - that system.img is ICS R6B.

Let me download GB JB and decrypt .zip for the system.img.

WIll re-upload the logs!
[Sony Tablet S] jappaj:
That would also explain why it did not work at all when we manually tired to re-flash your current system using JB system.img and after reboot we just saw R6B again which really would not be possible :)
[Sony Tablet S] SWFlyerUK:
This is the correct one!
[Sony Tablet S] jappaj:
Could you copy system.img as sysother.img also? On that diff everyting is still totally different between your system and system.img, but it is quite possible since you are running US system on your GB device...
[Sony Tablet S] jappaj:
My baf, file name should be systemoth.img... I need *oth* files which it produces then...
[Sony Tablet S] SWFlyerUK:
This ok?
[Sony Tablet S] jappaj:
For some reason there is no *oth* files... In your earlier post yesterday there was... You sure you are suing that xtskit.zip from first post, not anything old?

Output you should get to command prompt is something like this:

Initializing...

Your batch ID is: 19146

Waiting for device...

Determining current system partition...

Current system is: /dev/block/mmcblk0p3

Other system is: /dev/block/mmcblk0p4

Trying to find /mnt/sdcard2/system.img...

Mounting /mnt/sdcard2/system.img...

Calculating checksums for /data/local/tmp/systemloop...

Calculating checksums for /system...

Diffing checksum files...

Unmounting system.img...

Done! Now check tmp\sysdiff-19146.txt for results.

Mounting sysother...

Trying to find /mnt/sdcard2/systemoth.img...

Mounting /mnt/sdcard2/systemoth.img...

Calculating checksums for /data/local/tmp/systemloop...

Calculating checksums for /data/local/tmp/sysother...

Diffing checksum files...

Unmounting system.img...

Un-mounting sysother...

Done! Now check tmp\sysothdiff-19146.txt for results.

See tthose systemoth* things?
[Sony Tablet S] SWFlyerUK:
You are right! Sorry. Attached.
[Sony Tablet S] jappaj:
One file is missing, sysimgchecksum, but that probably does not matter.

From those checksums it seems to me, that you actually have US system AND US other system. Also I can see that just about all of the files do differ between regions, so Sony seems to recompile everything for each region.

Which also means, that it is quite hard to "fix" your system. Perhaps manually trying to dd GB firmware in, like we did before... I am not sure though if it's worth the risk... I mean, will nobody ever notice that you are running wrong region... If you still persist that you want to make your device fully GB, I would manually try to dd system.img in...
[Sony Tablet S] SWFlyerUK:
Thanks for your sterling efforts - think I'll sell this tomorrow however. If they pick it up, they pick it up, if not then not my fault!
[Sony Tablet S] giovix84:
guys I have the tablet still stuck. New to unlock it?
[Sony Tablet S] jappaj:
Best to bring it to Sony Service Center, really. They may charge you something, but at least you will end up with working device...
[Sony Tablet S] mgbirder2:
bricked my brand new Xperia Tablet s

Hi, I just bought a an XTS, updated to Android 4.1.1. rooted and then committed the stupidity of installing Chainfire 3d on it... now it’s stuck on the Sony Screen, I tried to rest it following the instructions of the Sony customer service, but it does not enter the recovery menu. I had to fly back to my current residence in Bolivia were i took it to a Sony Service Center, I just got it back with the info that i needed a new main board.. (which is more expensive than the tablet itself..).

My question is: If i get the Sony Screen is it even possible that the main board is damaged? And of course is there any way of restoring my Tablet?
[Sony Tablet S] saf4xdadev:
What kind of warranty did this tablet come with? Is it not still under warranty? and don't mention the word root or rooting to anyone at Sony....

Good luck!
[Sony Tablet S] cons03:
daym, i try to swap my sd to internal using the root system. then im reading here now to find a way to make my xts work again, im also stuck in boot loop =(
[Sony Tablet S] stifilz:
Please do not bump multiple old threads. I have replied to you in the other thread.
[Sony Tablet S] CamachoDjr:
I did that same dumb mistake with "chainfire" a few months ago, wife was so upset... etherway I just claim that it happen after the last update and that its just stuck on the sony logo, turn it in, they replace the mainboard, but now I need to send it back because neither my front or back camera work.

Hotwire: How does he find them?

Prock: I blame Gregslist.

Hotwire: You mean Craigslist?

Prock: No, Gregslist. If you want something even Craig won't touch, you turn to Greg. ....The Awesomes
[Sony Tablet S] stth:
http://xdaforums.com/showthread.php?t=2642436

this worked for me / hung at boot animation due to broken symlinks/removed apk's :good:
[Sony Tablet S] vincenzo929292:
hello guys, unfortunately my tablet does not turn on. It turns on only mode APX. You know help me? not even recognize the driver ADB.
[Sony Tablet S] sfex3best:
I tried posting the problem on the official Sony forums but no 1 helps :(

I miss my tablet :sly:
[Sony Tablet S] dex9mm:
Hold the power button and volume till you get the red flashing light

and leave it boot takes the best part of half an hour If this does not work try the folowing

if you can boot in to recovery flash the latest jb ota offical zip for your device and flash and perform the reset with the volume buttons again try to boot up and leave it for a while
[Sony Tablet S] sfex3best:
Thanks but no luck I kept it on the boot screen all night lol

The problem Is I get that weird error I posted above when I try to flash any official zip file:(
[Sony Tablet S] jappaj:
Sony's official zip files are incapable of recovering bad flash in certain situations. Situtations like we have at hand right now.

I am planning to go to Sony service center and see if they can flash my device. They said that they have everything what is needed to flash, but if that everything is just PC and the same update zips we already have then they cannot do anything. On they other hand they may have better update.zips from Sony...
[Sony Tablet S] sfex3best:
Cool lets hope you can find a way.

Anyway is there any way to contact Sony besides phone because it takes ages to reach them sometimes?

I really did use my tablet alot and miss it now that it's dead...:(
[Sony Tablet S] jappaj:
I contacted my local Sony via E-Mail and they asked my to be in direct contact with authorized Sony service center. I sense this will cost lots of money for me, especially if Sony cannot provide "better" update.zip:s for their service centers and they need to replace the flash chip or something.

Last time I buy any device with locked bootloader. Should it be unlocked there would be no problems at all fixing problems like this (I've been brciked my phones atc. so many times and always I have been able to recover from recovery since bootloader and recovery won't ***** about files about to be flashed).
[Sony Tablet S] mcp001:
Hi. I use flasher do flash JB and brick my device too (region PL). I send it to sony in warranty repair, and is back (for free). :D

What they did?

Typ of part: Plastic - V150 SUB ASSY TOP COVERED FOR SV

Typ of part: Plastic - V150 ADHESIVE TOP COVER

Typ of part: MBX - V150 MB SUB ASSY A1(ELPIDA) (EMMC/16gb)

Tablet back with Android 4.0.3 (release3). System Update writes "The system software is up to date"

Sorry for my poor English.
[Sony Tablet S] jappaj:
Ahaha so they changed flash memory when they could have recovered easily enough just by using proper update.zip. What an amateurs.
[Sony Tablet S] mcp001:
I run recovery and try install JB from zip and:

Installing update...
Write images to system1...
Write files to vendor1...
read_mod_link: failed to readlink "/system0/vendor": No such file or directory
E:Error in /tmp/desklunvr/desklunvr.zip
(Status 7)
Installation aborted.

Im still on 4.0.3 R3
[Sony Tablet S] sfex3best:
I was thinking of this but I bet it takes like 2 to 3 weeks in delivery time right?
[Sony Tablet S] mcp001:
I call to Sony 22 april, today tablet returned. I'm from Poland and service in France.
[Sony Tablet S] saf4xdadev:
So do you know what went wrong with the flasher 3.0 tool then? I was just about to use the flasher when at the same time I was reading the posts right at the point when folks started posting bricks....so I pulled the plug, literally....just after downloading the zip files and before the flash started executing. So lucky!

Anyway, It doesn't sound like something you did wrong since many are having same brick problem using the flasher so I was interested if you knew what is wrong with the flasher or maybe wrong with one of the zip files?
[Sony Tablet S] dex9mm:
Can you do a hard reset then try to root if you an root you can change your back door rescue and then flash the jb zip

It seems like they just changed the flash and didnt do a full wipe of the system ha ha ha sorry not laughing at your misfortune just sonys totally inpet it sounds like they couldnt get past there own recovery lockdown
[Sony Tablet S] jappaj:
No I do not know what is wrong with flasher tool, what exactly went wrong. It is weird because flashing pre-JB firmwares with it worked just fine, but JB causes bricks.

But for me the results seems to be clear; there is ICS bootloader, probably ICS on another system partition and remaining system -partition is corrupted and system tries to boot from corrupted system partition and thus fails. For some reason, system is unable to switch to another system partition when booting fails from another.

NOTHING should be unrecoverable with proper update.zip since we can access recovery and flash partitions. It is just that Sonys update script is poorly made and it will not even try to flash everything, it starts to cry when it sees corrupted partition and aborts immediadly leaving system on corrupted state. That's why I am pissed to Sony - they really should have done better job. Especially if they physically changed flash zip for somebody because they were incompenent enough not to know how to recover via software only. Hell, if Sony would give me their private key to sign update packages, I would be able to fix all bricked devices by myself (disclaimer: I may be wrong of course :)!
[Sony Tablet S] giovix84:
Hi guys! Happy May 1st to all. I feel a significant problem. The tablet will not turn on. It remains to Sony written. Here's what happened. I was updating the tablet to the new version 4.1.1 JB using the application S.onyTablet.S [FLASHER] v3.0 at some point towards the end of the message on the tablet of some program had crashed and involuntarily I click ok and the tablet becomes black lit, this happens while I'm upgrading to JB, the upgrade appears on the screen after a while 'that it has finished and I have to reboot and press enter on the keyboard closes. I do this but the tab remains the same. then I'll turn it off and then power back up and remains so. What do I do? Is there a recovery? If I connect it to the PC recognized the USB icon that appears next to the clock that to maintain safe removal.
[Sony Tablet S] jappaj:
Turn your device off. Push volume up button and keep it pushed while you press power button. Your device should boot into recovery mode. Download correct firmware for your region (links are in somewhere in this forum), prefer version which can be rooted, I think version 6 (not, a not b, just plain old 6) is good choice. Put that firmware to SD-card and SD-card to you tablet and try to flash that firmware.

Let us know how it went.
[Sony Tablet S] giovix84:
how do I put the firmware into the sd? But you're referring to the memory of the tablet or to an external sd-card?

I had the ICS 4.0.3 Release6b root. Where can I find the ICS 4.0.3 Release6?

---------- Post added at 01:24 PM ---------- Previous post was at 12:40 PM ----------

found this firmware from 4shared: signed-txs03_304-ota-121005053.zip you think okay?
[Sony Tablet S] jappaj:
Just copy the zip file to SD-card using your computer and then put that SD-card to your tablet and then reboot to recovery. From there you can choose "Update system from SD card" or something like that I don't remember details and you then hould see all the files from your SD-card. Choose that firmware zip file you placed to SD-card and choose yes.

Correct file depends on your region. That file is for Italian version if I am correct. If your device is from Italy then yes it is ok. Even if you have wrong version, your tablet just refuses to flash it so you can always try.
[Sony Tablet S] giovix84:
thank you very much! But to install JB 4.1.1? I put before ICS 4.0.3 Release6 and then what?

here is the log:

Android system recovery (3e)

System utility(Rev.35. BL: 0x00000006. EC: 0.21. master)

Installing update...

Write images to system1...

Write files to vendor1...

Random offset: 0x109

read_mod_link: failed to readlink "/system0/vendor": No such file or directory

E:Error in /tmp/desklunvr/desklunvr.zip

(Status 7)

Installation aborted.
[Sony Tablet S] jappaj:
Do not worry about JB yet. If your device is not booting, first priority is to get it working again, upgrading to latest version comes second. Why we suggest you to R6 instead of JB is that if you succeed recovering, you can root R6 again but you cannot root JB. And when you have R6, you can always upgrade to JB afterwards. You could also flash JB firmware yes, but no way to root afterwards (until somebody figures out how).

Changes are, that you cannot recover though. There are already few bricked devices with no way to recover. Let's hope yours is not one of them...