[obsolete - use ALLinONE tool] 'rescure-backdoor', ota-autodownloader v1.1 - Sony Tablet S

UPDATE: THIS IS OBSOLETE.
USE S.onyTablet.S [ALLinONE] tool
Below guide/tool use as 'description'
-------------------------------------------------------------------------
Hi again
As I wrote recently - I was working on automatic tool for Sony Tab community,
to get 'rescue-backoor' (in case of bootloop), and get proper OTA update zips.
It took me a lot of effort to get everything to work as it should,
...but I think that it was worth it..... you tell me
OK... let's get to the point - MULTI-TOOL, it has 3 main functions:
build.prop modification - bootloop protection
ota zip autodownloader
disable/enable ota updates and notifications
It does all the things which was described in [GUIDE-IMPORTANT!] "rescue-backdoor" thread.
ALL THE THINGS GOES FULLY AUTOMATIC !!!!!!!!!!!
ROOT and ADB are required.
What exactly does the tool step by step?
[part1: build.prop modification - bootloop protection]
makes backup of current build.prop (to /data/local/tmp/ and PC /backups/)
gets value of sony.build.incremental
reduces sony.build.incremental value by 1
dynamicaly modifies build.prop to correct value(-1)
makes backup of new build.prop (to /data/local/tmp/ and PC /backups/)
reboots and checks if modification is correct
[part2: ota zip autodownloader]
waits for user to click "Download" on ota notification
waits till ota update is fully downloaded
automatically recognizes newly downloaded ota update zip
makes backup of new ota (to /sdcard/ota-updates/ and PC /backups/)
[part3: disable/enable ota updates and notifications]
[optional] it asks if user want to disable ota system updates and notifications
to enable it back just rerun tool - it will ask in the begining of work
Any questions, suggestions - just ask !
Please post results, all the info is much appreciated!
br
condi

---

condi said:
Hi again
As I wrote recently - I was working on automatic tool for Sony Tab community,
to get 'rescue-backoor' (in case of bootloop), and get proper OTA update zips.
It took me a lot of effort to get everything to work as it should,
...but I think that it was worth it..... you tell me
OK... let's get to the point - MULTI-TOOL, it has 3 main functions:
build.prop modification - bootloop protection
ota zip autodownloader
disable/enable ota updates and notifications
It does all the things which was described in [GUIDE-IMPORTANT!] "rescue-backdoor" thread.
ALL THE THINGS GOES FULLY AUTOMATIC !!!!!!!!!!!
ROOT and ADB are required.
What exactly does the tool step by step?
[part1: build.prop modification - bootloop protection]
makes backup of current build.prop (to /data/local/tmp/ and PC /backups/)
gets value of sony.build.incremental
reduces sony.build.incremental value by 1
dynamicaly modifies build.prop to correct value(-1)
makes backup of new build.prop (to /data/local/tmp/ and PC /backups/)
reboots and checks if modification is correct
[part2: ota zip autodownloader]
waits for user to click "Download" on ota notification
waits till ota update is fully downloaded
automatically recognizes newly downloaded ota update zip
makes backup of new ota (to /sdcard/ota-updates/ and PC /backups/)
[part3: disable/enable ota updates and notifications]
[optional] it asks if user want to disable ota system updates and notifications
to enable it back just rerun tool - it will ask in the begining of work
Any questions, suggestions - just ask !
Please post results, all the info is much appreciated!
br
condi
Click to expand...
Click to collapse
Nice! Condi comes through again simplifying the process. I have already made a backup with the manual method but I want to give this a try when I get home so I can turn off the update part. Once I have created this new backup file should I discard the old file because of possible install issues with build.prop? I guess what I am getting at is that since I have already lowered the build.prop once this will lower it again making my download from the manual backup no good? Sorry for the long question. Thanks again!

---

Judah001 said:
Nice! Condi comes through again simplifying the process. I have already made a backup with the manual method but I want to give this a try when I get home so I can turn off the update part. Once I have created this new backup file should I discard the old file because of possible install issues with build.prop? I guess what I am getting at is that since I have already lowered the build.prop once this will lower it again making my download from the manual backup no good? Sorry for the long question. Thanks again!
Click to expand...
Click to collapse
Hi, your 'old copy of ota zip' will work just fine. The tool will decrease your build.prop value by 1, it will work without any issues
Both update zips will have higher value, than one in your device = both will work!
Don't forget to post results

---

condi said:
Hi, your 'old copy of ota zip' will work just fine. The tool will decrease your build.prop value by 1, it will work without any issues
Both update zips will have higher value, than one in your device = both will work!
Don't forget to post results
Click to expand...
Click to collapse
Ok perfect thank you. When I get home tonight I will give it a shot and post my results. I will just edit this post to keep the clutter down in this thread.

---

Judah001 said:
Ok perfect thank you. When I get home tonight I will give it a shot and post my results. I will just edit this post to keep the clutter down in this thread.
Click to expand...
Click to collapse
There was small typo - bad syntax in 1.0, it will make no harm, but will exit when will arrive ota download. Just redownload - v1.1

---

Awesome, condi~! No more worries to root my STS. Gonna try root and install this tonight.

---

I ran two separate tests. Both times build.prop was lowered by one with successful reboot. The issue I had both times was with my wifi after reboot. It stated that my wifi was connected but when checking my browser I was unable to pull up a page. So I disconnected and then reconnected to my wifi. I have been having this issue since rooting already on reboot so I don’t believe it was an issue with Multi-Tool. Once wifi connection was established the first test did not auto populate there was an update so I manually went to system updates to downloaded it. The second test did auto populate after a minute or two. After the update downloaded the script ran and copied all files to both of the correct locations each time. Both the first and second time the updates were successfully turned off. When plugging in on the second test I was prompted to turn the updates back on and it did so with no issues proceeding to download the update. If anyone else is having issues with wifi please let me know. Thanks again Condi for all your hard work!

---

zaynal said:
Awesome, condi~! No more worries to root my STS. Gonna try root and install this tonight.
Click to expand...
Click to collapse
Great happy to kick your worries out
Judah001 said:
I ran two separate tests. Both times build.prop was lowered by one with successful reboot. The issue I had both times was with my wifi after reboot. It stated that my wifi was connected but when checking my browser I was unable to pull up a page. So I disconnected and then reconnected to my wifi. I have been having this issue since rooting already on reboot so I don’t believe it was an issue with Multi-Tool. Once wifi connection was established the first test did not auto populate there was an update so I manually went to system updates to downloaded it. The second test did auto populate after a minute or two. After the update downloaded the script ran and copied all files to both of the correct locations each time. Both the first and second time the updates were successfully turned off. When plugging in on the second test I was prompted to turn the updates back on and it did so with no issues proceeding to download the update. If anyone else is having issues with wifi please let me know. Thanks again Condi for all your hard work!
Click to expand...
Click to collapse
So in summary:
everything works correctly,
WiFi issue IS NOT related to multitool.
Im glad

---

Hi Condi,
I guess a new issue comes up in Germany (only in Germany?).
I heard yesterday evening from a user that he bricked his Tablet S and re-installed his downloaded zip file (~ two weeks old downloaded version 3.2.1R2).
Now he got Kernel build#10 and is now not able to root his device.
(security hole is closed in this version)
Did you tried OTA RootKeeper and did it works after re-install firmware?
Otherwise we running in the risk to lose all opportunities to root the device after re-installation of latest firmware 3.2.1R2.
If OTA RootKeeper works well, we could implement the easy steps in your script for a "second chance for rooting".
Details on German Community:
http://www.android-hilfe.de/root-ha...ablet-s/201625-how_to-root-6.html#post2756883

---

obicom said:
Hi Condi,
I guess a new issue comes up in Germany (only in Germany?).
I heard yesterday evening from a user that he bricked his Tablet S and re-installed his downloaded zip file (~ two weeks old downloaded version 3.2.1R2).
Now he got Kernel build#10 and is now not able to root his device.
(security hole is closed in this version)
Did you tried OTA RootKeeper and did it works after re-install firmware?
Otherwise we running in the risk to lose all opportunities to root the device after re-installation of latest firmware 3.2.1R2.
If OTA RootKeeper works well, we could implement the easy steps in your script for a "second chance for rooting".
Details on German Community:
http://www.android-hilfe.de/root-ha...ablet-s/201625-how_to-root-6.html#post2756883
Click to expand...
Click to collapse
hi friend,
thanks for posting this info - its very important to stay rootable..
about OTA RootKeeper - i've got it installed and got 'protected root'.
Got to check if it works ok in details.
As far as I remember - it worked, but not from the beginning.
I've already reflashed with rootkeeper,
su-backup stays, after reflash you need to reinstall Superuser app.
Will try that when I get back home later evening.
BTW - I think I could get some other, 'extra rootkeeper' for us,
as far as I remember - with some proper permissions we could get
unwritable build.prop - then we could have opportunity to reflash
older 'rootable' zip, if another ota would lock the exploit vulnerability.
I had this one time - reflashed new ota, and build.prop remained untouched
br
condi

---

My friend,
I guess the magic command should be 'chattri +i'.
This is the way how Root Keeper works.
It should be possible to use the same to protect the build.prop too.
But please consider, to install an older version of update.zip, we need a much lower value in the build.prob. I have two files on my sd card (update.zip) ..
For example .. if my build.prop = 123456789, I got the last version with
123456788 and a older one (e.g. 3.2) with 103456789
Therefore we should increase build.prop for the first step (download latest version) with one and should increase a higher digit for protection as a backup.

---

Hi Condi:
I have boot Loop, I run the bootloop protection, but still having bootloops, Any sugestion?
Thank you

---

What do you mean with "I run the bootloop protection"?
Did you reinstall the ota firmware zip via recovery menu?
If yes and if it was successful the boot loop should be gone.
If you try do start boot loop protection script after getting boot loop ...
its to late ... :-(

---

rfreeman said:
Hi Condi:
I have boot Loop, I run the bootloop protection, but still having bootloops, Any sugestion?
Thank you
Click to expand...
Click to collapse
Code:
pro·tec·tion   [pruh-tek-shuhn]
noun
1.
the act of protecting or the state of being protected; preservation from injury or harm.
You get 1000 of viruses, hard disk damaged. And then you buy antivirus software and want pc to work?
You cant protect something, that has already been done.
Now you can FIX, REPAIR, not protect!

---

I used your "all in one" "Install "rescue-backdoor" - anti-bootloop protection, gives opportunity to reflash current firmware
if something goes wrong with modifying system things."
But after the first step I tried to download the system update, but bootloop come again.
please tell me What can I do?.
Thank you and sorry for my english.

---

rfreeman said:
I used your "all in one" "Install "rescue-backdoor" - anti-bootloop protection, gives opportunity to reflash current firmware
if something goes wrong with modifying system things."
But after the first step I tried to download the system update, but bootloop come again.
please tell me What can I do?.
Thank you and sorry for my english.
Click to expand...
Click to collapse
Hello,
Bootloop can't come after trying to download ota zip.
Bootloop can't come after using rescue-backdoor thing.
Its made to protect, not to damage. Its just one value change.
Describe all the things you've done before using multitool,
there you should search for the mistake.
Do you have adb access?

---

condi said:
Hello,
Bootloop can't come after trying to download ota zip.
Bootloop can't come after using rescue-backdoor thing.
Its made to protect, not to damage. Its just one value change.
Describe all the things you've done before using multitool,
there you should search for the mistake.
Do you have adb access?
Click to expand...
Click to collapse
I think your first assessment was correct. It sounds like he already had a bootloop and is now trying to use protection to fix it....
BTW Thanks for the awesome tool. I've had my tablet for about a week but haven't gotten up the nerve to try and root it yet lol =D