Sony Tablet S Rooted/Updated from Stock Android 3.2 to 4.0.3r1a - My Adventure

[Cat McGowan]

I ordered a Sony Tablet S tablet model SGPT112US/S from Woot.com. I updated and rooted it from its stock Android 3.2 to 4.0.3r1a. Here is my adventure in brief sentences. Keep in mind that I am not telling you what to do, I am just telling you what I did.

Computer running Windows 7 with Android Composite ADB Interface and Sony Tablet S drivers installed.

Links to files used:
Android 3.2.1r2(US) file signed-nbx03_001-ota-0042.001.zip
Android 4.0.3r1a(US) file signed-nbx03_001-ota-120803002.zip
Condi's ALLinONE v4.0 tool file S.onyTablet.S__ALLinONE__v4.0.7z
Android Debug Bridge version 1.0.29 file ADB_v1.0.29.zip


Powered on tablet and did not set up Wi-Fi, accounts, etc.

Went into Settings.
About table read:
- Android version 3.2
- Kernel version 2.6.36.3 [email protected] #1
- Build number 1.10.001100001
Made sure Wi-Fi was turned off.
Turned on (allowed) Unknown sources.
Turned on USB debugging.
Exited Settings.

Opened File Transfer app, went into its settings and selected Do nothing.
Powered off tablet.

Installed SD card in computer.
Copied 3.2.1r2(US) file signed-nbx03_001-ota-0042.001.zip to SD card.
Moved SD card from computer to tablet.

Powered on tablet into recovery mode.
From recovery screen, selected Update system from SD card.
From next screen, selected signed-nbx03_001-ota-0042.001.zip file.
Allowed update to complete.
Tablet rebooted to normal boot.
Went into Settings.
About tablet read:
- Android version 3.2.1 (release2)
- Kernel version 2.6.36.3 [email protected] #1
- Build number THMASU0012400
Exited Settings.

Installed Condi's ALLinONE v4.0 tool.
Added empty file named _offupdates to ALLinONE tool's files directory.
Updated ALLinONE tool's adb files to version 1.0.29.

Connected USB cable between tablet and computer.
Started ALLinONE tool.
From main menu, selected 1 Root device.
Allowed rooting of 3.2.1r2 to complete.
Confirmed root (checked for existence of Superuser). OK!
Powered off table.

Moved SD card from tablet to computer.
Deleted signed-nbx03_001-ota-0042.001.zip file from SD card.
Copied 4.0.3r1a(US) file signed-nbx03_001-ota-120803002.zip to SD card.
Moved SD card from computer to tablet.

Powered on tablet.
Started ALLinONE tool.
From main menu, selected 3 * Custom ROM and Flashing [SUBMENU].
From next menu, selected 1 Create decrypted update.zip [+optional make custom].
Followed ALLinONE prompts.

First problem occurred!
Booted tablet into recovery mode as prompted, but ALLinONE tool stalled at NOW ENTER RECOVERY MODE screen lastly showing 3 dots.
KCCO.
From recovery screen, selected Update system from SD card.
From next screen, selected install.zip file.
Allowed update to complete.
From recovery screen, selected Update system from SD card.
From next screen, selected signed-nbx03_001-ota-120803002.zip file.
Allow update to complete. (Update took several minutes to complete.)
ALLinONE tool continued as expected.
Continued following ALLinONE prompts.

Second problem occurred!
Booted tablet into recovery mode as prompted, but ALLinONE tool stalled at NOW ENTER RECOVERY MODE screen lastly showing 3 dots.
KCCO.
From recovery screen, selected Update system from SD card.
From next screen, selected install.zip file.
Allowed update to complete.
From recovery screen, selected Update system from SD card.
From next screen, selected custom_update_signed.zip file.
Allowed update to complete. (Update took several minutes to complete.)
ALLinONE tool continued as expected.
Tablet rebooted to normal boot.

Went into Settings.
About tablet read:
- Android version 4.0.3 (release1a)
- Kernel version 2.6.39.4 [email protected] #1
- Build number TISU0R0010110
Exited Settings.
Confirmed root (checked for existence of Superuser). OK!
Powered off table.

Booted into recovery mode.
From recovery screen, selected Reset to factory settings.
From next screen, selected Yes -- delete all user data.
Allowed reset to complete.
Tablet rebooted to normal boot.
Set up Wi-Fi, accounts, etc.
Confirmed root (checked for existence of Superuser). OK!
Powered off table.

Successfully updated tablet from stock (unrooted) Android 3.2 to rooted Android 4.0.3r1a.

Wiped sweat off forehead.

 

[stifilz]

Nice post. This will surely help all the Wooters and clear some things up. Glad to see it went well

Stifilz

 

[bart77]

I too purchased a tablet s from woot and successfully updated to ics using aio4.0. But, i had to manually update the adb driver in device manager while in recovery to resume full auto install during the 3 dots. Apparently it sees the device differently while booted verses in recovery. This was my second attempt, the first ended up with ics and no root. By watching the first video example by bluechip j, i was told not to root when prompted but to add that later. Bad mistake. Luckily i could reflash the 3.2.1 update again and start over. Overall a very trial and error journey through this process. I would have preferred a detailed written procedure but i figured it out in the end. Thanks to everyone involved for all their hard work.

Sent from my DROID RAZR using Tapatalk 2

 

[eduong503]

Good stuff...I could have used this last weekend. Bought my tablet S through Woot as well.

 

[agent0014]

Is that version of ICS you used basically the rooted version of the OTA update? I don't want to lose all the functionality that SONY built in to this thing (the PS games mostly sound pretty cool), but I want to get it rooted while it's still possible (looks like no one has cracked how to root this thing if you take the OTA). I just got mine from woot this afternoon and I'm anxious to get it up and running as a gift for my bf... he's been jealous of my Galaxy Tab 10.1 for a while now

Awesome write-up BTW... I plan to use this for my reference!

 

[stifilz]

Is that version of ICS you used basically the rooted version of the OTA update? I don't want to lose all the functionality that SONY built in to this thing (the PS games mostly sound pretty cool), but I want to get it rooted while it's still possible (looks like no one has cracked how to root this thing if you take the OTA). I just got mine from woot this afternoon and I'm anxious to get it up and running as a gift for my bf... he's been jealous of my Galaxy Tab 10.1 for a while now

Awesome write-up BTW... I plan to use this for my reference!

Yes the method above using AIO will give you a pre-rooted ICS, same as OTA but with root access. If you update OTA there is currently no way to root and no way to go back. Follow this guide and you can't go wrong!

Stifilz

 

[Cat McGowan]

Is that version of ICS you used basically the rooted version of the OTA update?

Yes, the ICS file I rooted was the latest OTA update file that a Sony Tablet S (US region) would download from Sony's servers. Links to all of the files used in my update/root can be found in this forum; however, to assist you better, I am going to edit my original post and add links to all of the files.

 

[jessicaat]

I too purchased a tablet s from woot and successfully updated to ics using aio4.0. But, i had to manually update the adb driver in device manager while in recovery to resume full auto install during the 3 dots. Apparently it sees the device differently while booted verses in recovery. This was my second attempt, the first ended up with ics and no root. By watching the first video example by bluechip j, i was told not to root when prompted but to add that later. Bad mistake. Luckily i could reflash the 3.2.1 update again and start over. Overall a very trial and error journey through this process. I would have preferred a detailed written procedure but i figured it out in the end. Thanks to everyone involved for all their hard work.

Sent from my DROID RAZR using Tapatalk 2

Say "no" to add root but do it later seems to be a really important point in the original instructions by TheHurf which BluechipJ referred to, though that was in AiO V2.7. Really curious about the reason. @@

 

[Cat McGowan]

Say "no" to add root but do it later seems to be a really important point in the original instructions by TheHurf which BluechipJ referred to, though that was in AiO V2.7. Really curious about the reason. @@

The reason for saying no to add root at the time it is said is because (1) the tablet's HC Android 3.2.1 is (must be) already rooted and (2) the rooted and signed ICS Android 4.0.3 update file custom_update_signed.zip has not been created yet.

 

[bart77]

I assume by saying no, you can also customize the ROM more to your liking, then add root and finalize by signing. But, like i said before, i tried that the first time and it didn't work. Maybe i missed a step somewhere. However, I did NOT update the adb to the newer version. Not sure if that had an effect on it or not?
I would also like to note that, while running win7 64bit, or any for that matter, it is critical to start AIO by opening a cmd window, changing to that directory and running the batch file.
Simply double clicking the .bat file to start, usually ended up by closing about halfway through.

Sent from my DROID RAZR using Tapatalk 2

 

[Cat McGowan]

I assume by saying no, you can also customize the ROM more to your liking, then add root and finalize by signing. But, like i said before, i tried that the first time and it didn't work. Maybe i missed a step somewhere. However, I did NOT update the adb to the newer version. Not sure if that had an effect on it or not?
I would also like to note that, while running win7 64bit, or any for that matter, it is critical to start AIO by opening a cmd window, changing to that directory and running the batch file.
Simply double clicking the .bat file to start, usually ended up by closing about halfway through.

My updating Condi's AiO tool's adb files to version 1.0.29 was done for the sake of caution because of reports that previous versions of adb have not played nice with the Android 4.0.3r1a update. Updating adb may or may not have been necessary, but hey, updating it didn't hurt! Also, I have used Condi's AiO tool severals times to root three different tablets; two tablets three times and one (the one I just rooted) two times. I run Win7x64 and via Windows Explorer have always double-clicked S.onyTablet.S.bat to start it and have never had it close down unexpectedly. Perhaps the problem is unique to your (and maybe others) computer.

 

[stifilz]

I assume by saying no, you can also customize the ROM more to your liking, then add root and finalize by signing. But, like i said before, i tried that the first time and it didn't work. Maybe i missed a step somewhere. However, I did NOT update the adb to the newer version. Not sure if that had an effect on it or not?
I would also like to note that, while running win7 64bit, or any for that matter, it is critical to start AIO by opening a cmd window, changing to that directory and running the batch file.
Simply double clicking the .bat file to start, usually ended up by closing about halfway through.

Sent from my DROID RAZR using Tapatalk 2

Or right click run as admin should do it

 

[Cagedodger]

Thanks for this thread. I'm new to rooting, but I've been following this forum for a while. I picked up a second Sony tab from the Woot sale to replace my 16g and one for my wife.

The steps were a little different for me. The AiO tool (v 4.0 w/ updated adb files) stopped on me as well and in different places. It made it through, just answering "yes" for all options during the custom ROM and flash process.

Here's a few things I noticed that may help others undergoing this process.
I had to manually update the Sony USB driver (see bluechipj's video). After that it worked fine.

Mine was right out of the box. I had not installed hardly any apps on it as I still had my unrooted ICS 16g Sony Tablet that I was using while researching how to root.

I flashed 0035 >>0042 right out of the box then ran the AiO tool. After I finished the 4.0.3.r1a flash, I had myself a freshly rooted ICS tablet. I then went to go to the Play store (I had not updated it from the "Market" version that came with it from the factory. It kept telling me that I needed to associate a Google account to it (already associated) and prompted me to retry. App cache/data both cleared with no change. I did a factory reset and it worked fine after that. No sweat since I had not installed any apps or tied any accounts to it yet.

If you just got this tablet, I would say to try and update to the play store ahead of time. It might save you from having to do a factory reset later on.

Another oddity that I noticed was that AiO (adb) no longer recognized the tablet when I went to disable the OTA notifications. I had to again manually update the tablet USB driver (3rd option: composite) and after that it worked just fine. Not sure if that's because of the flash or factory reset or both. If the AiO tool stops recognizing your tab after the flash, check your driver.

For what it's worth, I'm running Win7 64.

Hope that saves someone a headache.

Thanks again for the run-through and links.

Here's a question for you folks. Can I just take the custom ROM that I created on my tablet and use it to flash my wife's tablet after I flash hers to 0042 and root it or should I go through the whole process again?

Thanks!

 

[Cat McGowan]

Here's a question for you folks. Can I just take the custom ROM that I created on my tablet and use it to flash my wife's tablet after I flash hers to 0042 and root it or should I go through the whole process again?

I do not believe it is possible; however, I've never attempted it, I've always done the complete process on each tablet I've rooted, so I could be wrong. Condi would be the best person to answer your question, but he appears to be MIA right now, probably because of the recent birth of his daughter.

 

[bart77]

If each tablet uses the same nbx number, then yes, you can share.

Sent from my DROID RAZR using Tapatalk 2

 

[stifilz]

If each tablet uses the same nbx number, then yes, you can share.

Sent from my DROID RAZR using Tapatalk 2

But will still have to use AIO process as I believe it tricks the tablet into disabling the signature check or tricking it somehow. If you were to just use the rooted ICS update it would fail due to an error about 'the whole signature did not match'. Otherwise we could decrypt the update add root and part sign etc and the flash that file over a unrootable tab.

Stifilz

 

[olivierkes]

…

Booted into recovery mode.
From recovery screen, selected Reset to factory settings.
From next screen, selected Yes -- delete all user data.
Allowed reset to complete.

…

Noob question: why do you have to reset to factory settings? What does it do?
Thx

 

[Cat McGowan]

Noob question: why do you have to reset to factory settings? What does it do?
Thx

But a good question, eh?

You do not have to reset to factory settings, but doing it clears out residual data and settings from previous installs, thereby creating a clean (but rooted) install.

Keep in mind that in my original post, I am not telling you what to do; instead, I am telling you what I did.

 

[Vinny1967]

It's too late now but are you saying that I could of used the latest update to root my tablet running ics?

 

[Cat McGowan]

It's too late now but are you saying that I could of used the latest update to root my tablet running ics?

If your tablet's previous ICS (or HC) was already rooted, then yes, you could have rooted the ICS 4.0.3r1a update. Otherwise, no.