Database Users

How to root stock 3.2

Ok, after messing around with 3.2 I decided to fix the rooting issues without downgrading. The problem with downgrading is it requires a SDCard and requires you to install a couple of programs and then to install an update.zip from the sdcard. I could not get half my ACER's to read and mount a sdcard, and some ACER's I have located in a remote office and trying to walk someone through the process was too painful. I tweaked the the downgrade tool's images to install 3.2 with root instead of downgrading it and jumping through hoops. All I did to the stock image is to copy the ash shell over to /system/xbin/su and set the sticky bit. Everything else is stock.
Update posted here, read thead http://forum.xda-developers.com/showpost.php?p=20654298&postcount=129
New version V4
-- The instructions are in a PDF document inside the download --
== Version V4 ==
-- Added /system/subin/su which is a backup (backdoor) root in case an OTA deletes the /system/xbin/su
-- Set permissons on the su root(#) tool so OTA's shouldn't be able to break it.
-- Added drivers for XP
Summary:
Version V4 is the same as V3 with the only difference being that there is a NEW backdoor script which has some additional features to protect root(#) from getting broken when you do an OTA. I also applied these to this flash image so you wouldn't have to add the additional protection yourself. V4 also has the drivers for XP included. However, when taking an OTA you should also install the backdoor for additional protection. However, you cannot leave the backdoor installed as it turns off sound. So having a little more protection just might save your root in case you take an OTA and forget to install the backdoor.
Download it here: http://www.multiupload.com/NS0X5TK4D1
Alternative download location:
http://depositfiles.com/files/c6pr69ri6
http://www.fileserve.com/file/s2wCQpN/root-3.2.1-V4.7z
http://www.filesonic.com/file/jTA7AMN
http://www.filejungle.com/f/vRnfK5/root-3.2.1-V4.7z

Which 3.2 update is it ? Fully working, no issues ? Good job. Is it power + volume down or volume up to go into recovery ? And is it possible to flash a custom kernel like Honeyvillain on this stock ROM ?
Thx

Has anybody ( including OP) tried this method?

It is the 3.2 OTA for WiFi that my Tablet picked up. It is total stock other than making a SU from the ash shell and putting it into /system/xbin.
Fully works, no issues, have used it on 8 ACER 500's with no issues.
To enter recover it is the left side of the volume button which is volume (-) oopps NOT (+) as I indicated.

Hah, saying Vol +/- is not intuitive on this device since when in landscape, Vol + is the "right" side, but in portrait mode Vol + is the "top" side.

no go
Hi, i can see my iconia uid from adb ( already installed in my pc) but
not from test.cmd, in the extracted package. Any ideas?
REPEATED STEPS 1-4 ( PER INSTRUCTIONS) ON 2 PC'S RUNNING W XP. SO FAR "NO GO" TEST.CMD CANNOT FIND PATH.... AND DOTNETDETECTER, THEREFORE, DOES NOT WORK.

will this wipe all the data on the tablet?
---------- Post added at 04:19 PM ---------- Previous post was at 03:40 PM ----------
JUGOMAN said:
Hi, i can see my iconia uid from adb ( already installed in my pc) but
not from test.cmd, in the extracted package. Any ideas?
Click to expand...
Click to collapse
same here i run the setup file and it installs but after i run test.cmd and it cant find it

Sorry about the test.cmd not working. The script just calls adb.exe to make sure it is working and I have it installed in another directory that I did not include. I posted, to the original message an attachment, it is called fix-Test.7z that fixes the test.cmd. You should be able to just unzip it into the directory you created and run the test. The archive includes the adb.exe and dll's so the test.cmd should work. If you have adb.exe working you really don't the test.cmd, but I found out when talking someone through it (over the phone) this made sure that adb.exe was installed and they had the tablet USB Debugging turned on.
And it is a quick and easy way to get the serial number which you need to flash it.
Thanks,
Let me know if you have any more issues.

does anyone know if flashing it this way will delete all your data on the tablet?

NO GO2
The attchment does fix the test.cmd "problem" but the next step, Dotnetdetecter, does not work. It re-installs the driver (?) then error "adb is old" or something like that. All packages in my computer's ADB are up to date. I think that the "target" directory in the DONETDETECTER IS NOT CORRECT. ANY IDEAS? btw GOOD WORK!!!!!

Many thanks for this. It is really easy like this. Keep up the great work.

UPDATE
Installed, booted, but no root. Previous rom( acer update) was3.2 Gen 2, now 3.2 Gen 1. was worth a try.. Thank you... tablet is working just fine, just no root

jimmkd84 said:
does anyone know if flashing it this way will delete all your data on the tablet?
Click to expand...
Click to collapse
Yea. I've never done this before so I'm wondering the same thing.
Also
Idk about this test thing but if u type 'adb devices' it'll show you which devices (if any) are connected. I always use that as a test when i use the adb to install apks.

bad adb
NO GO2 WROTE
The attchment does fix the test.cmd "problem" but the next step, Dotnetdetecter, does not work. It re-installs the driver (?) then error "adb is old" or something like that. All packages in my computer's ADB are up to date. I think that the "target" directory in the DONETDETECTER IS NOT CORRECT. ANY IDEAS? btw GOOD WORK!!!!!
Not sure what that would be. I just use the adb.exe and dlls that are in the fix.zip. Maybe you have a different version loaded?

ROOT IS NOT in the apps. It is in the adb shell.
What this does is allows you to connect to the device using adb.exe shell and you will get the $ prompt.
at the $ prompt type su and press enter. You will get # and be in su mode.
Now you can do whatever you would like. What would that be, you might ask? Well you could do the following:
1. mount system as rw
2. Push your favorite su tools to the device so they are listed in the apps (busybox etc).
Again this gets you to 3.2 with the ability to have a SU when connected via the adb shell. I left the building of the tools and custom CW to you guys to do as you wish. Here's something else you could do.
1. Shell to it, and issue the SU
2. Mount system as rw
3. Push your favorite tools to where you want (busybox etc)
4. Take the recovery.img (in the zip) and dd dump it to the recovery partition. This will put clockwork on the device (1.5).
a. You should probably run itsmagic too.
5. Get everything the way you want it.
6. Reboot to recovery and CW will load.
7. Now with CW 1.5 loaded, you can build and make copies of your ACER and make them available to anyone you like. CW 1.5 does NOT require an external SDCARD.
Sorry, if I did not make it clear that this is just a SU that you have to use from the command line. If someone wants to give me the links to a SU apk, busybox, etc they'd like included I'd do it. It would only take a few minutes as I got hundreds of these ACER's to flash for our company. I just wanted to get SU, but what the heck, I could build it out if someone would like it that way. ACER really pee'd me off with this, and guess what? They left the ability to gain root in the 3.2 100. Why the 'Sam Heck' did they change the 500 3.2 so you cannot get root?
So, anything I can do to help let me know. Also, If you never want ACER to send you another update I can tell you how to fix that too. All you have to do is the following:
1. Get to the adb shell $
2. type su to get the # prompt
3. Now mount system as rw by doing the following:
a. mount -t rfs -o remount,rw system /system
4. Now rename the update tool by doing the following:
a. mv /system/app/FDUpdater.apk /system/app/FDUpdater.apk.old
mv /system/app/FWupdateService.apk /system/app/FWupdateService.apk.old
5. To get OTA then just reverse the process if you ever want ACER and their OTA to break your fleet of ACER Tablets by pushing silly updates that they think you want then you can undo it. The last I knew, I owned these ACER Tablets and I don't take kindly to them changing something that I do NOT WANT CHANGED. They should be sued, matter of fact, I think they are violating federal laws by destroying data on MY tablets. Anyway, off my soapbox.

i have re run the new test.cmd and is working now, and have successfully run dotnetdetector but i dont want to proceed until someone can confirm if doing this will wipe all data on the tablet
appreciate it, great work btw dev!
---------- Post added at 05:05 PM ---------- Previous post was at 04:39 PM ----------
did this wipe the data on it?

Hello, may i use this procedure on my A501?
Thanks

I did NOT test on the 501 so I do not know. If it was me, I would take the 501 stock images and put them in the kitchen and root them and then replace the ones in my zip with those or better yet, use CW to flash it in.
I think the ACER 501 has cell phone data connection doesn't it? I don't think the stock for WiFi only would be a good idea.
What ACER did on the 3.2 update (my opinion) was removed the Gingerbreak exploit and they removed the adb root exploit (they left the adb root exploit in on the 100). This is what many OEM's did, however many allow you to flash your own easier than ACER seems to want to let us. So if you got 3.2 NON-ROOTED loaded then there is no way to 'hack' out a root (just yet).
So how do you root it? You have to make a custom ROM and flash it. Now ASUS/Motorola/Samsung/Toshiba all allow you to flash your own ROM if you know what you are doing.
ACER seems to hide how to put the tablet into flash mode (if someone knows please let me know). Even if you did flash it they do want those ROMS running so they take each partition and calculate the MD5Sum and write it to, I think, partition #7. Therefore, if you do figure out how to flash in a new boot image or system image the tablet will not boot because the MD5Sums will not match (if you brick your tablet this way you are fubar). Fortunately, someone wrote a tool called itsmagic which you can run to tell the tablet to rebuild these. But if you fubar brick it before you get itsmagic run, I don't know how you get into flash mode using the keys so you'd be up a creek.
So, the 411 skinny on rooting an ACER with 3.2 is to get 3.2 off the device. Fortunately, they made an earlier flashing tool to flash in 3.0. I would guess this leaked out as a way for people to reflash to stock when they have issues.
Once you are on 3.0, you now can use Gingerbreak or the adb root exploit to root it. Once rooted, you can get CW loaded. CW allows you to install your own ROM's. Without CW you can only install ROM's signed by ACER and without ROOT you cannot install CW.
So, if you flash to the 3.0 now you are 'back to the future' in 3.0, you can root and install CW so you can now install a custom ROM from your SDCard.
What I would do is go get the STOCK ROM from ACER for your 501 device.
Once you have the stock ROM, you can use the kitchen tools to unzip the ACER ROM and root it to your liking. Now, re-zip it, but you cannot sign it with an ACER certificate so it will only install using CW. No, big deal because you got 3.0 loaded with CW. You boot to recovery CW and then run the update from your SDCard that you built in your kitchen.
This isn't really that hard to do if you're willing to read some documentation.

I have no idea if it wipes it clean totally. It does walk you through the setup again (like it was new out of the box) so I would assume most things would be wiped. I would back it up and not take the chance because it is best to be backed up.

Just a note here. It says fully stock execpt root? i don't think that's entirely accurate. I believe that it's still downgrading the bootloader, otherwise you'd never be able to get CWM to run, as itsmagic doesn't work with the new bootloader. So your left with stock 3.2 ROM with adb/su abilities and pre 3.2 bootloader.
On another note, I believe step 17 is not needed. CWM run's itsmagic automatically on every boot. So just booting CWM and then rebooting to android should suffice.

Restoring Stock Recovery

With the new OTA being released many are asking how to restore stock recovery. I think that the original /system/etc/install-recovery.sh file is required, unfortunately I did not make a backup. Does anyone have a copy of the original version of this file? Please post it here if you have it and anyone who knows how to restore stock recovery please post any helpful instructions here. If I get the file and proper instructions I will update the OP accordingly. Thanks.

I made a backup but have no idea how to extract that file.

You have to write which TPT you have.
US or....?
16, 32 or 64GB?

toenail_flicker said:
I made a backup but have no idea how to extract that file.
Click to expand...
Click to collapse
What did you backup with? If you backed it up after installing CWM then it was probably already gone (which is why I don't have it).
In the ROW instructions they cleverly added this line to the install instructions:
cp /system/etc/install-recovery.sh /system/etc/install-recovery.sh.backup
which creates a backup of the file in /system/etc/
If you did this then you should be able to copy the file install-recovery.sh.backup from /system/etc/ using root explorer or adb.
I have the US 32GB version, I'm not sure if the files are the same but I would guess that they are. Anyway if you can get the file that would be great.

I have 183827U 64GB. Yes, I made a Nandroid backup after installing CMW. I also have Titanium and MyBackup saves, but have no idea if they save the file. I'll go looking for it with RE and let you know what I find.
---------- Post added at 01:47 PM ---------- Previous post was at 01:41 PM ----------
Seems I have install-recovery.sh but the date is recent, so I guess it's from when I rooted. No backup of the same name.

Mine is:
#!/system/bin/sh
if ! applypatch -c EMMC:/dev/block/mmcblk0p1:2048:0a48c18ee1ca32bba5a785d8ea8b6976fc0a190e; then
log -t recovery "Installing new recovery image"
applypatch EMMC:/dev/block/mmcblk0p2:3170304:fa229b8ff37128302094316ea4ced3d68ad5edcf EMMC:/dev/block/mmcblk0p1 53a249cd150c483f9255eba03adccdf6e7c014a6 3524608 fa229b8ff37128302094316ea4ced3d68ad5edcf:/system/recovery-from-boot.p
else
log -t recovery "Recovery image already installed"
fi
WE-TPT-64GB

Modifying the update to keep root

Ok, here is a new version of OTA2 for US tablets that should be flashable in CWR and should keep CWR and root without requiring the use of OTA rootkeeper. I would still protect root with OTA Rootkeeper and temp unroot before updating (you can try it without temp unroot but it has caused some problems for other users). This update will still scan all your system apps so you need to restore or unfreeze any system apps that you deleted or froze using Ti Backup.
Instructions:
This update is for owners of US tablets with root and ClockworkMod Recovery. Make sure your battery is well charged before flashing this, a dead battery mid update can create major problems!
1. Install OTA Rootkeeper and protect root. You should now temp unroot. Users who did not temp un-root have had issues with su access after updating.
2. Download the update below and put it on your external sdcard
3. Restore any system apps that you have removed
4. Reboot into ClockworkMod Recovery (Shutdown Thinkpad, turn on and press vol+ repeatedly until you see booting recovery image)
5. I would also highly recommend making a nandroid backup if you have not previously done so.
6. Select install zip from sdcard>choose zip from sdcard then browse to and select the update you downloaded here
7. update.zip will run, it will check your system apps during the update and may fail if you have changed something, if so the error message should explain why
8. Reboot tablet; it will be a very long reboot. This is normal; it seems to take forever but just let it boot.
9. Use OTA Rootkeeper to restore root.
Flash at your own risk! I am not responsible if this totally bricks your tablet! This is the US update, do not flash if you are using a tablet from another region! Seriously this stuff could cause problems.
ThinkPadTablet_A310_02_0039_0086_US_CWR.zip
-----------------------------------------
Original Message
So I would like to modify the new OTA so I get the updates without losing root and my current recovery. It is my understanding that the file: \META-INF\com\google\android\updater-script contains the instructions for how the update should run. Can I simply modify this script so that it won't delete root or overwrite my recovery or boot and then flash it in CWR? It looks like it would be pretty straight forward but it would be nice to get some information from someone more knowledgeable so that I don't mess something up and brick my TpT. One obvious line to remove would be where it deletes superuser.apk and su. There is also a section where it patches the boot image, I'm not sure what this patch does but I am worried that maybe somehow they might lock the bootloader. EDIT: I updated, and still have CWR so the bootloader didn't get locked. The other lines I would remove are the ones that reference recovery. If someone with knowledge of android would be willing to help me with this then I will upload my modified update.zip (assuming it works) so that others can avoid the hassle.
So I think that the process would be to delete the current \META-INF\ folder, then put in my modified updater script in \META-INF\com\google\android\updater-script and sign the update with SignApk.jar? Is this the correct process? Any help would be greatly appreciated.
Thanks.
I attached the original updater-script below for anyone interested in taking a look.

I appreciate you posting the file. I've never worked with Android code and this was a great intro.

I'm not sure this will work. Although I'm not super knowledgeable in this.
I did find these two threads.
http://forum.xda-developers.com/showthread.php?t=1185881
http://forum.xda-developers.com/showpost.php?p=21351145&postcount=101
Of course, the latter is in respect to the Galaxy Nexus, and I am sure most of those people have unlocked bootloaders, etc. So again, not sure if those shed any more light on it, but am also curious on a process like this.
The update popped up on my tablet last night and I clicked "more info" and from what it lists, does not seem to be very many fixes

So I successfully updated in ClockworkMod Recovery without losing CWR and without deleting my Superuser.apk and su files by modifying the updater-script in the update.zip. Unfortunately it still messed up my superuser permissions somehow and I ended up having to use ADB while booted into CWR to push and symlink the proper files to get su working again (OTA Rootkeeper wasn't functioning properly because the files were there but the permissions were messed up). I have modified the update.zip so that now it deletes the superuser.apk and su files but keeps clockworkmod recovery. With this and OTA Rootkeeper I think you should be able to update while keeping CWR and restoring root. I will also provide directions here for those seeking to make their own modifications and possibly improve upon my efforts, but proceed with caution.
So what I did was open the zip in winrar and extracted the updater-script. I then edited some lines of code using Notepad++, deleting the ones that referred to deleting recovery or installing a new recovery as well as the lines to delete superuser.apk and /system/bin/su and /system/xbin/su. I also commented out a couple lines at the beginning (assert(getprop("ro.product.device") == "Indigo") because I was getting an error code status 7 when it was trying to perform this check while using clockwork mod. I checked my build.prop and it does say Indigo so I don't know why the check failed but just removing the check was easier for me than figuring out the problem (generally it is not good to remove such checks but I was sure I had the right file). In Notepad++ you must select save as and choose type all files then just save it with the same name. Then replace the updater-script in your zip file with the modified one, I used winrar and chose the compression to just be store (ie no compression). Then you need to delete the CERT.RSA, CERT.SF, and MANIFEST.MF files in the META-INF folder of your update.zip and you sign the update.zip using testsign.jar. Then your new modified update.zip is ready to go.
I think that the reason things did not work out for me is that there are a bunch of lines in the updater script about symlinking and setting permissions for stuff in /system and I think /system/bin/su was originally symlinked to /system/xbin/su which is the real file so things got messed up and I had the files still but the symlink and or permissions were messed up. I eventually fixed this by booting into CWR mounting system and using adb to repush /system/xbin/su and setting permissions and making the new symlinked su file in /system/bin just like the last lines of Dan's Thinkpad root bat file did.
Here is a modified update.zip that should delete your Superuser files but keep your ClockworkMod Recovery. I think that with this file you can use OTA Rootkeeper to make a root backup, temp unroot, then boot into CWR and update to the new OTA then you should be able to reboot and use OTA Rootkeeper to restore root and download Superuser from the market, while keeping CWR through the entire process.
Flash at your own risk! I am not responsible if this totally bricks your tablet! This is the US update, do not flash if you are using a tablet from another region! Seriously this stuff could cause problems.
That being said I think it will work. I followed this guide to sign my update.
Original updater-script
Modified updater-script in the update.zip linked above (this one deletes Superuser /system/bin/su and /system/xbin/su but keeps CWR)
Modified updater-script that I flashed on my tablet (this one messed up my su but doesn't delete the files)
If you need a good online file locker join Dropbox here and we'll both get an extra 250mb of space.

Unfortunately that update.zip didn't work for me, game me an error in CWR.
Is the other method, replacing the update scrip in the OTA and trying it ?

freezepop said:
Unfortunately that update.zip didn't work for me, game me an error in CWR.
Is the other method, replacing the update scrip in the OTA and trying it ?
Click to expand...
Click to collapse
Depending on the error you can likely edit the updater-script yourself and successfully installed. Most errors are due to changes in system apps causing them to fail checks. If you remove an app check you should probably remove the corresponding patch for that app in the updater script. What error did you have?

Ok, here is a new version of OTA2 for US tablets that should be flashable in CWR and should keep CWR and root without requiring the use of OTA rootkeeper. I would still protect root with OTA Rootkeeper and temp unroot before updating (you can try it without temp unroot but it has caused some problems for other users). This update will still scan all your system apps so you need to restore or unfreeze any system apps that you deleted or froze using Ti Backup.
Instructions:
This update is for owners of US tablets with root and ClockworkMod Recovery. Make sure your battery is well charged before flashing this, a dead battery mid update can create major problems!
1. Install OTA Rootkeeper and protect root. You should now temp unroot. Users who did not temp un-root have had issues with su access after updating.
2. Download the update below and put it on your external sdcard
3. Restore any system apps that you have removed
4. Reboot into ClockworkMod Recovery (Shutdown Thinkpad, turn on and press vol+ repeatedly until you see booting recovery image)
5. I would also highly recommend making a nandroid backup if you have not previously done so.
6. Select install zip from sdcard>choose zip from sdcard then browse to and select the update you downloaded here
7. update.zip will run, it will check your system apps during the update and may fail if you have changed something, if so the error message should explain why
8. Reboot tablet; it will be a very long reboot. This is normal; it seems to take forever but just let it boot.
9. Use OTA Rootkeeper to restore root.
Flash at your own risk! I am not responsible if this totally bricks your tablet! This is the US update, do not flash if you are using a tablet from another region! Seriously this stuff could cause problems.
ThinkPadTablet_A310_02_0039_0086_US_CWR.zip

jhankinson said:
Ok, here is a new version of OTA2 for US tablets that should be flashable in CWR and should keep CWR and root without requiring the use of OTA rootkeeper. I would still protect root with OTA Rootkeeper just in case something goes wrong but don't temp unroot before updating and see if root still works after the update. This update will still scan all your system apps so you need to restore or unfreeze any system apps that you deleted or froze using Ti Backup.
Instructions:
This update is for owners of US tablets with root and ClockworkMod Recovery. Make sure your battery is well charged before flashing this, a dead battery mid update can create major problems!
1. Install OTA Rootkeeper and protect root (just in case), you shouldn't need to temp unroot though with this update.
2. Download the update below and put it on your external sdcard
3. Restore any system apps that you have removed
4. Reboot into ClockworkMod Recovery (Shutdown Thinkpad, turn on and press vol+ repeatedly until you see booting recovery image)
5. I would also highly recommend making a nandroid backup if you have not previously done so.
6. Select install zip from sdcard>choose zip from sdcard then browse to and select the update you downloaded here
7. update.zip will run, it will check your system apps during the update and may fail if you have changed something, if so the error message should explain why
8. Reboot tablet; it will be a very long reboot. This is normal; it seems to take forever but just let it boot.
Flash at your own risk! I am not responsible if this totally bricks your tablet! This is the US update, do not flash if you are using a tablet from another region! Seriously this stuff could cause problems.
ThinkPadTablet_A310_02_0039_0086_US_CWR.zip
Click to expand...
Click to collapse
Thank you for your work. I have ROW version and waiting OTA2 for that, but still now I know how to modify update-script. I have a question, why not to remove any unneeded software from update and remove check for installed software which are already removed?

redbaron said:
Thank you for your work. I have ROW version and waiting OTA2 for that, but still now I know how to modify update-script. I have a question, why not to remove any unneeded software from update and remove check for installed software which are already removed?
Click to expand...
Click to collapse
Different people have removed different apps so one person may want the patch while another might want it skipped. I was just posting a generic version here that works for stock system apps. If others want to further customize their script then they are welcome improve upon it or customize it for their own system.

jhankinson said:
Ok, here is a new version of OTA2 for US tablets that should be flashable in CWR and should keep CWR and root without requiring the use of OTA rootkeeper. I would still protect root with OTA Rootkeeper just in case something goes wrong but don't temp unroot before updating and see if root still works after the update. This update will still scan all your system apps so you need to restore or unfreeze any system apps that you deleted or froze using Ti Backup.
Instructions:
This update is for owners of US tablets with root and ClockworkMod Recovery. Make sure your battery is well charged before flashing this, a dead battery mid update can create major problems!
1. Install OTA Rootkeeper and protect root (just in case), you shouldn't need to temp unroot though with this update.
2. Download the update below and put it on your external sdcard
3. Restore any system apps that you have removed
4. Reboot into ClockworkMod Recovery (Shutdown Thinkpad, turn on and press vol+ repeatedly until you see booting recovery image)
5. I would also highly recommend making a nandroid backup if you have not previously done so.
6. Select install zip from sdcard>choose zip from sdcard then browse to and select the update you downloaded here
7. update.zip will run, it will check your system apps during the update and may fail if you have changed something, if so the error message should explain why
8. Reboot tablet; it will be a very long reboot. This is normal; it seems to take forever but just let it boot.
Flash at your own risk! I am not responsible if this totally bricks your tablet! This is the US update, do not flash if you are using a tablet from another region! Seriously this stuff could cause problems.
ThinkPadTablet_A310_02_0039_0086_US_CWR.zip
Click to expand...
Click to collapse
I flashed this zip. It didn't delete su or Superuser.apk, yet apps cannot get root access afterward. any suggestions?

mandrsn1 said:
I flashed this zip. It didn't delete su or Superuser.apk, yet apps cannot get root access afterward. any suggestions?
Click to expand...
Click to collapse
That is what happened to me originally, it can be fixed though. Did you make a backup with OTA Rootkeeper? If so open Android Terminal emulator and type:
/system/su-backup
mount -o remount,rw /system
cp -f /system/su-backup /system/xbin/su
ln -s /system/xbin/su /system/bin/su
chown root /system/xbin/su
chmod 6755 /system/xbin/su
Then reboot your tablet. I believe this should fix your root access. If you don't have a backup I think you can also fix it by running adb while booted into CWR. I can give you those instructions if this doesn't work.

Apparently you should temp un-root before installing my update then restore your su backup with OTA Rootkeeper after updating.

You wear the crown
Thanks for posting the fix, too. Waiting for reboot to finish.
Really appreciate all your hard work. The instructions you posted for me in thinkpad forums worked perfectly and I learned a lot in the process.

toenail_flicker said:
Thanks for posting the fix, too. Waiting for reboot to finish.
Really appreciate all your hard work. The instructions you posted for me in thinkpad forums worked perfectly and I learned a lot in the process.
Click to expand...
Click to collapse
Did the fix work for you?

Still waiting for reboot. I waited about 20 minutes and rebooted manually. So far it still hasn't made it in for me to try the fix.
---------- Post added at 09:58 PM ---------- Previous post was at 09:44 PM ----------
jhankinson said:
Did the fix work for you?
Click to expand...
Click to collapse
Fix not yet working. Got this far
/system/su-backup
mount -o remount,rw /system
cp -f /system/su-backup /system/xbin/su
error message
cp: applet not found
Any ideas?

toenail_flicker said:
Still waiting for reboot. I waited about 20 minutes and rebooted manually. So far it still hasn't made it in for me to try the fix.
---------- Post added at 09:58 PM ---------- Previous post was at 09:44 PM ----------
Fix not yet working. Got this far
/system/su-backup
mount -o remount,rw /system
cp -f /system/su-backup /system/xbin/su
error message
cp: applet not found
Any ideas?
Click to expand...
Click to collapse
try
busybox cp -f /system/su-backup /system/xbin/su
may have to type busybox before some of the other commands too if they give an error.

So my line would be
busybox cp -f /system/su-backup /system/xbin/su
cp: applet not found

Just a quick note of thanks for getting me through this. Root is wonderful!

If
cp -f /system/su-backup /system/xbin/su
fails, use
dd if=/system/su-backup of=/system/xbin/su
instead.

jhankinson said:
Ok, here is a new version of OTA2 for US tablets that should be flashable in CWR and should keep CWR and root without requiring the use of OTA rootkeeper. I would still protect root with OTA Rootkeeper just in case something goes wrong but don't temp unroot before updating and see if root still works after the update. This update will still scan all your system apps so you need to restore or unfreeze any system apps that you deleted or froze using Ti Backup.
Instructions:
This update is for owners of US tablets with root and ClockworkMod Recovery. Make sure your battery is well charged before flashing this, a dead battery mid update can create major problems!
1. Install OTA Rootkeeper and protect root. You should now temp unroot. Users who did not temp un-root have had issues with su access after updating.
2. Download the update below and put it on your external sdcard
3. Restore any system apps that you have removed
4. Reboot into ClockworkMod Recovery (Shutdown Thinkpad, turn on and press vol+ repeatedly until you see booting recovery image)
5. I would also highly recommend making a nandroid backup if you have not previously done so.
6. Select install zip from sdcard>choose zip from sdcard then browse to and select the update you downloaded here
7. update.zip will run, it will check your system apps during the update and may fail if you have changed something, if so the error message should explain why
8. Reboot tablet; it will be a very long reboot. This is normal; it seems to take forever but just let it boot.
9. Use OTA Rootkeeper to restore root.
Flash at your own risk! I am not responsible if this totally bricks your tablet! This is the US update, do not flash if you are using a tablet from another region! Seriously this stuff could cause problems.
ThinkPadTablet_A310_02_0039_0086_US_CWR.zip
Click to expand...
Click to collapse
Thx jhankinson, this work for me. my TPT 1838 US.

Stock Netflix.apk needed

I'm trying to upgrade my rooted TF101 to 9.2.1.11 and every zipI use complains on an assert failure for /system/app/Netflix.apk. Oddly, I can't get Ti backup to restore it, so I tried downloading it and putting it in that directory. This doesn't work. Does anyone have the stock Netflix.apk they can post so I can move past this? thx!!

Here ya go!
Title says it all.

Thanks! But no cigar!
I tried that, but it gives me the following error when I attempt to apply the zip from the sd card:
ClockworkMod Recovery v3.2.0.1 roach2010-tf101-r1
-- Installing: /sdcard/ics-us-8.6.5.21-to-9.2.1.11-CWM-rooted.zip
Finding update package...
Opening update package...
Installing update...
Verifying current system...
assert failed: apply_patch_check("/system/app/Netflix.apk", "459b736ea95188dd3500005f621b4fa22291c40c", "58c70e894dfc98166d16c64cb9555a7e83ceb7e4")
E:Error in /sdcard/ics-us-8.6.5.21-to-9.2.1.11-CWM-rooted.zip
(Status 7)
Installation aborted.
Click to expand...
Click to collapse
Any suggestions out there in the development community? I didn't think that uninstalling Netflix would cause such a hassle later on. Is there a different version of the .apk I can try? Or a different way of installing it (I just copied it over after remounting /system/app as rw).
Alternatively, can I unroot, then download the update, then re-root? Anybody have any practice with that, or will the Netflix.apk package.
Thank you! Have a nice day (or evening).

crinis said:
I tried that, but it gives me the following error when I attempt to apply the zip from the sd card:
Any suggestions out there in the development community? I didn't think that uninstalling Netflix would cause such a hassle later on. Is there a different version of the .apk I can try? Or a different way of installing it (I just copied it over after remounting /system/app as rw).
Alternatively, can I unroot, then download the update, then re-root? Anybody have any practice with that, or will the Netflix.apk package.
Thank you! Have a nice day (or evening).
Click to expand...
Click to collapse
That wasn't a zip file, it was an apk. And you don't flash those in recovery. Just put it in /data/app directory, then restart the tablet. Or you can try to execute it, and it will automatically install to the appropriate folder.

I solved it!
Yes, I just copied it over using scp (after remounting /system as rw). I'm no noob!
Here's what I did to get it to work.
I unzipped the rooted zip file, edited the updater-script to remove references to Netflix.apk (three of them), then rezipped it up, copied it to the sdcard , rebooted to recovery, then flashed it. Worked! Here's the exact steps took:
On my linux latop:
mkdir /tmp/ics-us-8.6.5.21-to-9.2.1.11-CWM-rooted
cd /tmp/ics-us-8.6.5.21-to-9.2.1.11-CWM-rooted
unzip ~/Download//tmp/ics-us-8.6.5.21-to-9.2.1.11-CWM-rooted.zip
vi ./META-INF/com/google/android/updater-script
# /Netflix\.apk finds the lines, I deleted two, and modified the third to remove the reference.
zip -r /tmp/ics-us-8.6.5.21-to-9.2.1.11-CWM-rooted.zip *
scp /tmp/ics-us-8.6.5.21-to-9.2.1.11-CWM-rooted [email protected]:/Removable/MicroSD
Click to expand...
Click to collapse
From there it's all Clockwork.
Thanks so much for the help of this forum. I love xda developers!

WARNING Dont use latest twrp-3.2.1-0-s2.img

Alright I have a brand new LE 2 x526. Ran twrp-3.2.1-0-s2.img recovery and format data on user to remove that password thing.
reboot to bootloader and great no more password requirement. Next step is to do a twrp backup.
Just to make sure I rebooted to make sure everything is working. Guess what, it hangs on bootup on the logo.
I found out that twrp-3.2.1-0-s2.img has a bug (its writes the wrong partition size: see below)
Anyway. I used twrp-3.0.2-0-s2.imgto do the format data and everything works again.
Just want to write this just in case someone use this buggy twrp version.
saayantan said:
Just figured this out with the help of another post on a separate thread.
It seems that the latest twrp for x526 (v 3.2.1.0) has a bug such that when you format the data partition - it writes a wrong partition size.
This causes the boot loop with the stock ROM (other custom ROMs seems to be happy living with the error).
An associated side effect of the wrong partition size is that you wont be able to encrypt your phone on the custom ROM (the encryption process simply causes the phone to reboot without doing anything).
To resolve this, downgrade twrp to v 3.0.2. Then format cache/system/data.
Then mount the phone to your PC (enable MTP) and copy the stock ROM of your choice.
You need to update the "updater-script" and comment out the version check - and then you can install the stock ROM using twrp.
This worked for me.
Hope it works for you as well.
PS: Once you install the stock ROM, the data partition gets encrypted and first boot takes a lot of time.
Be patient and also know that twrp will no longer be able to decrypt your data partition (I think either twrp is broken OR the stock ROM uses some other default password to encrypt the data partition and hence decryption fails. I have tried using my screen lock PIN and it doesn't work and "default_password" does not work either.
All the best.
---------- Post added at 06:56 AM ---------- Previous post was at 06:52 AM ----------
Open the update.zip file on your PC and navigate to META-INF/com/google/android.
You will find a file by the name updater-script.
Use your favourite text editor to open this file and then find the following line:
get_device_compatible("le_s2_ww") == "OK" || abort("This package is for "le_s2_ww" devices; this is a "" + getprop("ro.product.device") + "".");
Insert a # at the beginning of the line to get the installer to ignore the version mismatch and you should be good to go.
It should now look like this:
#get_device_compatible("le_s2_ww") == "OK" || abort("This package is for "le_s2_ww" devices; this is a "" + getprop("ro.product.device") + "".");
Now save this file and update the zip file / create a zip file again and then proceed with the installation as usual.
Click to expand...
Click to collapse

Oh I just found a twp that dont have this bug. its in the LineageOS 14.1 for LeEco Le2 by codeworkx thread
https://forum.xda-developers.com/le-2/development/rom-lineageos-leeco-le2-t3541959
twrp-3.2.1-1-codeworkx-s2.img