S.onyTablet.S v6.5 [ALLinONE] - new: Update OEM Apps! automatic ICS ROOT!, JB ROOT!

[ObviousMan]

Even though it is fully automati procedure, when you enter recovery you need to install 'install.zip' manually then later on in the process you have to do this again.

Sent from my HTC Desire Z using Tapatalk 2.0

As I said, the video is a bit dated, and the file to install in the recovery mode is named "install.zip"
OM

 

[boxkillor]

prerooted ICS Wifi+3g German is offline,any mirrors available? thx in advance

 

[sapphire88]

my tablet just got an update, 4.0.3 release 2, italy, wifi + 3g, changelog reveal a fix for 3g connection that appears with ics 4.0.3...

PS: i was already on ics 4.0.3

 

[condi]

Even though it is fully automati procedure, when you enter recovery you need to install 'install.zip' manually then later on in the process you have to do this again.

Sent from my HTC Desire Z using Tapatalk 2.0

I was thinking about it today... And I've got some idea.
I think that old recovery 3e from honeycomb doesn't start
automatically install.zip - and new one from ICS does

I will analyze old recovery binary, and make a fix for that.
It should flash fully automatic, without manual choose of install.zip!
Fix for old recoveries coming in next version
I couldnt predict it - all the devices which I had access to,
was already on ICS with new recovery

my tablet just got an update, 4.0.3 release 2, italy, wifi + 3g, changelog reveal a fix for 3g connection that appears with ics 4.0.3...

PS: i was already on ics 4.0.3

Hmm... so Sony removes 1st ICS firmwares,
and releases new one, release2?

Fck... I would already download new firmwares,
decrypt it, and analyze. Don't know what is the situation,
if prerooting will 100% work, all this have to be checked..
But got fckn not rootable dev.. Grrrr that hurts

br
condi

 

[kulen]

Thank you all for help

I'm going to try it again now.

I'm a little afraid because I don't understand this with automatic region change.

I just copied back all from SD card and backups that was created after first attempt (I backed it up) and I hope it'll just continue from where it stopped.

wish me luck

 

[boxkillor]

condi, do u have a solution for the missing file "german ics 3g+wifi" ?

thx in advance

 

[condi]

condi, do u have a solution for the missing file "german ics 3g+wifi" ?

thx in advance

As sapphire88 reported - Sony started pulling second version of ICS firmwares with some bugfixes. When they are releasing new version, in most cases they remove old files. Maybe thats why 4.03 url is not found any more.

Stifilz is an expert in finding correct zip urls
He made full url list for last ICS updates.
Check this thread, and ask there

br
condi

 

[kulen]

thank you condi
and thank you all others that helped me.

I now have rooted ICS on my tablet. I'm just not sure any more which region is it now. but I only care about it so I know which update to download in future.

I just followed procedure AiO 4.0 offered but in 2 occasions when recovery should have started install.zip itself, I started it manually, and after that "failed" I started update (first time update to decrypt, second time custom signed update).

I had to re-install drivers for XP after that.

Good night all - I'm going to play with ICS now

 

[boxkillor]

thx bro

 

[stifilz]

my tablet just got an update, 4.0.3 release 2, italy, wifi + 3g, changelog reveal a fix for 3g connection that appears with ics 4.0.3...

PS: i was already on ics 4.0.3

condi, do u have a solution for the missing file "german ics 3g+wifi" ?

thx in advance

Checked all 3g links on my list. Only Italy and Germany not working for now. Will try to find new link.

Chur

Edit:

Italy Wifi + 3G Same filename different folder from 0003 to 0005.
http://info.update.sony.net/ST003/nbx03_010/contents/0005/signed-nbx03_010-ota-120427022.zip

EDIT EDIT:
Germany Wifi + 3G
http://info.update.sony.net/ST003/nbx03_008/contents/0005/signed-nbx03_008-ota-120612005.zip
Hmmm changed date on this one 12-06-12

 

[marinos35]

OK - so, just in case anybody else is suffering the same issues as me, here's the process I went through which (finally) worked.

First-off, for some reason the adb drivers could not detect the tablet in Recovery mode, and it wasn't possible to reinstall them and get that working.

So - I downloaded Virtual PC, and installed a blank version of Windows XP in there. This let me install the adb drivers into the "new" virtual PC, and get to a state where adb could "see" the tablet in both debug and recovery modes. I had to hand-install the drivers in both cases -- the auto install did not find them.

The process then went smoothly - I downloaded the OTA UK version of ICS, ran the decrypt, added root, signed it, and then flashed it successfully.

So in my case the problem was with my PC, not the tablet nor AiO V4, but resolving it was a pain.

Basically, if you can't connect to the tablet via adb in BOTH debug AND recovery modes, then AiO can't work.

-pjc

Thanks to you post I realized what my problem was. The adb driver at the recovery. I tried virtual box and another windows 7 x64 machine, where I managed to install all the drivers, but strangely the adb failed to see the connected device and AIO kept misleading me that I didn't have root 'su'

Anyway I fixed my problem by opening the device manager while in recovery, right clicked the device with the yellow warning and uninstall it (because it was refusing to accept the manual update for the correct driver as it was recognised as an mtp device?!?)

This is the most important part: Check to also uninstall the software for that device.

Then I just selected at the device manager to check for new devices and then I manually installed the correct drivers.

EDIT:
The following part has been modified because my apology to condi was one of the deleted/moderated posts and I wanted to somehow erase any hostility that condi and others felt from my message. Of course I may have failed again to pass my criticism as helpful and with good intentions without any hidden agenda or menace, but at least I have clarified which were my intentions

The AIO may be helpful but it's far from perfect (meaning that its's good but it can get better).

It has some incorrect messages as the script displays

'su' binary not found. You need ROOT to use this function.

even if you had root but you are missing the adb drivers or if for some other reason the device wasn't found by adb.

Also I think the output is missing crucial information for example
(after the *stars* with CAPS is an example of helpful addition)

**************************************************************
  DEVICE POWERED OFF.
  **********************************************************
  NOW ENTER RECOVERY MODE =  hold vol-up, and push power
  _hack_recovery.zip will be automatically done,
  just wait for complete - it will fail - thats ok!
**************************************************************


... IF YOU BOOT IN RECOVERY, THE UPDATE ALREADY FAILED SOME
MINUTES AGO AND YOU ARE STILL STUCK HERE, CHECK THE DEVICE MANAGER
FOR MISSING DRIVERS...

Anyway, thank you for your program (I really mean it as it was helpful even if had in my case a lot of bizarre driver and adb problems)

Your next update, in my opinion should focus to fix the output and making it more troubleshot friendly before adding new features. Just a suggestion, or if you don't like the way I put it: Could you please make the output more troubleshot friendly at the next version?

The reason I found the output so important is because when the root option failed (because the hacked mtp driver that was included in the program's files wasn't automatically installed), AIO still gave the same finishing output as when it succeeds

MTP driver has been enabled back.
Exploit complete!
Press any key to continue.

I think it would be helpful if the message also said to check

if anything failed after persistence then the root failed.
If it did, try to manually install the mtp driver.
You already tried? Seek help ... bla bla"

ORIGINAL UNEDITED MESSAGE

The AIO may be helpful but it's far from perfect, with incorrect messages ("su missing" when adb drivers or just the device wasn't found) and missing crucial information like "reboot your device by holding vol+ etc etc etc IF AFTER A WHILE YOU ARE STILL STUCK HERE, CHECK THE DEVICE MANAGER FOR MISSING DRIVERS

Anyway, thank you for your program, but you should spend your time for the next update to fix the output and making it more troubleshot friendly. I mean, the root failed (because the hacked mtp driver that was included in the program's files wasn't automatically installed) and AIO's output was success?!?!

 

[nutsymtom]

hi,
-i'm on 4.0.3 prerooted - want to install 4.0.3 r2
-Downloaded 4.0.3 r2 over the air on my TabS
-but when i try to create decrypted update -> AIO 4.0 says my TabS is not rooted, SU binary not found - but it is rooted - where should the SU binary located?

EDIT: oh i see have to check my drivers - a bit confunsing

nutz

 

[condi]

The AIO may be helpful but it's far from perfect, with incorrect messages ("su missing" when adb drivers or just the device wasn't found) and missing crucial information like "reboot your device by holding vol+ etc etc etc IF AFTER A WHILE YOU ARE STILL STUCK HERE, CHECK THE DEVICE MANAGER FOR MISSING DRIVERS"

Nobody force you to use it, you can always do everything manually,
no need of AiO, thats a PERFECT SOLUTION.

I've included a lot of verifications in AiO,
but for God's sake - don't blame AiO&me for that you had incorrect drivers.

Anyway, thank you for your program, but you should spend your time for the next update to fix the output and making it more troubleshot friendly. I mean, the root failed (because the hacked mtp driver that was included in the program's files wasn't automatically installed) and AIO's output was success?!?!

I can't make it more user friendly. It needs some experience,
if its not user friendly for you, then again - don't use it.

And no - I'm not gonna spend my time on fixing what you've suggested.
Most likely I'll spend my time with my wife.

Good night.

 

[nutsymtom]

hello again,
I`m trying to update from a rooted 4.0.3 to a rooted 4.0.3 r2
-adb seems to work now - installed drivers again - everything seems ok
-When starting "create decrypted update" the hackrecovery was created and copyed to sdcard - enter recovery, procedure starts - until here evterything seems to be good - but after "Installation Aborted" on TabS, AIO stucks.
[tried with AIO 4.0 and 3.4 - output is from 3.4 (my latest try)]

Extracting region\region.prop

Everything is Ok

Size: 435
Compressed: 5809
1 Datei(en) kopiert.
12 KB/s (435 bytes in 0.035s)
[*] Region is OK...
[*] HACK zip is already prepared, but not on SD
[*] Pushing _hack_recovery.zip...
1295 KB/s (15155925 bytes in 11.428s)

[*] DONE. Its saved in '/sdcard/_hack_recovery.zip' for future use.

[*] We will use '_hack_recovery.zip'
which is located in external SD!


[*]**************************************************************[*]
[*] DEVICE POWERED OFF. [*]
[*]**************************************************************[*]
[*] NOW ENTER RECOVERY MODE = hold vol-up, and push power [*]
[*] Go to 'Update system from SD Card' and choose: [*]
[*] /sdcard/_hack_recovery.zip [*]
[*] ...and wait for complete - it will fail - thats ok! [*]
[*]**************************************************************[*]


[*] ...

any idea what is going wrong?

nutz

 

[databoy2k]

To go back on topic, I'm having a strange issue. Back around v. 2.7 I flashed the American Rooted ICS onto my Canadian Tablet. Condi pointed out his region-free Play store, and I was off to the races.

I've noticed that I can't buy anything from the Play store, presumably because by tablet is somewhat confused as to its allegiance. I'd like to go back to a Canadian Rooted ICS, but have had difficulties.

It looks like I need to downgrade to Honeycomb, root, and then go back up to ICS, but I can't do the honeycomb update (get "Prohibit update as a result of checking version or base sku").

Can anybody lend me a hand? I'm sure it's not a driver issue, as I've done this once already to go up to rooted ICS.

Thanks!

 

[condi]

hello again,
I`m trying to update from a rooted 4.0.3 to a rooted 4.0.3 r2
-adb seems to work now - installed drivers again - everything seems ok
-When starting "create decrypted update" the hackrecovery was created and copyed to sdcard - enter recovery, procedure starts - until here evterything seems to be good - but after "Installation Aborted" on TabS, AIO stucks.
[tried with AIO 4.0 and 3.4 - output is from 3.4 (my latest try)]


any idea what is going wrong?

nutz

If AiO stucks - then probably it has no connection with device.
Check = uninstall driver in recovery, and reinstall it again, maybe thats the issue.

To go back on topic, I'm having a strange issue. Back around v. 2.7 I flashed the American Rooted ICS onto my Canadian Tablet. Condi pointed out his region-free Play store, and I was off to the races.

I've noticed that I can't buy anything from the Play store, presumably because by tablet is somewhat confused as to its allegiance. I'd like to go back to a Canadian Rooted ICS, but have had difficulties.

It looks like I need to downgrade to Honeycomb, root, and then go back up to ICS, but I can't do the honeycomb update (get "Prohibit update as a result of checking version or base sku").

Can anybody lend me a hand? I'm sure it's not a driver issue, as I've done this once already to go up to rooted ICS.

Thanks!

You should be able to jump directly from US ICS to CANADIAN ICS,
when I had working prerooted device I've flashed from US ICS to PL ICS without problems. Post details. Do you have canadian prerooted custom zip prepared already?

br
condi

 

[databoy2k]

You should be able to jump directly from US ICS to CANADIAN ICS,
when I had working prerooted device I've flashed from US ICS to PL ICS without problems. Post details. Do you have canadian prerooted custom zip prepared already?

br
condi

I think I got it, or at least somewhat. My hang-up was at the "update.zip" stage - didn't realize that you meant the official ICS update and not "install.zip."

It finished, but it did not reset anything; I had to do a factory reset through recovery to start fresh. How do I tell which region (Canada or US) of ICS is running on this tablet?

 

[nutsymtom]

Hello itz me, nuts again:silly:

If AiO stucks - then probably it has no connection with device.
Check = uninstall driver in recovery, and reinstall it again, maybe thats the issue.

yes ur right!
It was the driver again - but this time it was the driver at the recovery... strange.
In ICS everything ok, but at recovery no driver was found - it works, now!

The funny/bad thing about - i had to read a post few sites above, 3 times to get it... me and my english :silly::cyclops:

The good thing is, until now everything works - if i get any problems with root etc i'll let u know.
German 3G Version from 4.03 to 4.03release2

The new AIO automatic is sweet! Big THX for the work, condi!:good:

btw to Offtopic - nothing is perfect! not u, not me, no programm and no device!:angel:

nuts

 

[condi]

Hello itz me, nuts again:silly:


yes ur right!
It was the driver again - but this time it was the driver at the recovery... strange.
In ICS everything ok, but at recovery no driver was found - it works, now!

The funny/bad thing about - i had to read a post few sites above, 3 times to get it... me and my english :silly::cyclops:

The good thing is, until now everything works - if i get any problems with root etc i'll let u know.
German 3G Version from 4.03 to 4.03release2

The new AIO automatic is sweet! Big THX for the work, condi!:good:

btw to Offtopic - nothing is perfect! not u, not me, no programm and no device!:angel:

nuts

Gooooood
As I read - automatic flashing worked for you
Thats great - it worked because you had already ICS,
on old-honeycomb recovery binary it doesnt work automatically,
thats why some users got to manually choose install.zip, then again install.zip

Because of that I've modified the procedure in case of honeycomb,
to hmm... "semi-automatic" - it will replace recov-binary to 'automatic-one',
got it ready, will be released in v4.1.
But before that I've got to beta-test it somehow

Anyone here got still honeycomb 3.2.1r2 firmware with old recovery,
and want to help/test?

br
condi

 

[xyancompgeek]

Well, if it involves flashing ICS, then thats a big no-no (very happy with hc and i dont have a nandroid backup). But otherwise, yup, i can test it.