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.
Related
So I received the OTA Update for my Samsung EPIC 4G stock build Eclair DI18.
Unfortunately it did not install due to missing packages.
I was rooted.
I was not running any custom roms,
I did use the SDX Stock App Remover to remove "nascar",
I have seen other people having problems because they are missing the "Asphalt Demo" apk.
Unfortunately if you remove Nascar or Asphalt you will get that error message when you try to install the OTA EC05 update, as well as if you try the manual method of upgrading by copying the update.zip. This happens because the installer is trying to verify packages for the upgrade (which you no longer have).
I went nuts considering all the different methods I could take to apply this update. I wanted the quickest and easiest method, and one that would leave my data intact.
So if this matches your situation, you don't have to reflash back to stock DI18 to recover a couple of missing stock apps and you don't need Odin or the 255 mb tar ROM that's out there (SPH-D700-DI18-8Gb-REL.tar.md5) etc. with this method.
So here is the method I used to restore my Stock Sprint apps so I could get the installer to run.
Before you start, make sure you know which packages you need to restore back to your /system/app folder. (unfortunately, their is no way of knowing which package(s) you're missing if you don't remember what you removed. You could cross reference what you have with someone who has all the stock apps OR the easiest way is to try to apply the update and write down or remember which apk it is complaining about. Chances are you already know which APK you're missing and that's why you're here. If you removed multiple stock apps, then you might have already guessed that you are going to have to restore each apk one by one, and so you may need to go through this process more than once to discover exactly which apk files are missing.)
These instructions also assume that you've already copied the DI18-EC05 update.zip file found in this thread http://forum.xda-developers.com/showthread.php?t=1005593 to your sdcard.
Download the stock Sprint apk packages from:
http://forum.xda-developers.com/showthread.php?t=987777
The file you are looking for that is linked from that thread is:
http://www.nubecoder.com/files/andro...store_EB13.zip (Even though these are EB13 app's it doesn't matter that you're on DI18, we just need the file to be there so we can trick the installer into running.)
Unzip this file and copy the apk's you need to your sdcard by first mounting your android phone in mass storage mode (usb debugging disabled). After you have copied the apk's to your sdcard, you will need to remount your system folder and copy the apks to that /system/apps location for the update installer to recognize it (simply installing the app to your phone won't cut it).
To continue you will need the Samsung drivers ( I am not providing links because this can be found anywhere on the web. My particular Samsung driver archive is called "usb_drivers_GalaxyS_x64.zip" (reboot your system after installing if necessary).
You will also need the "one click root" zip archive (or any other package that can give you access to the adb shell.) I used the adb shell from the "epic aio one click root" file archive "epic.aio.v1.13.zip".
Enable USB Debugging mode in your phone, and then plug your phone into usb.
Follow the instructions below to remount your /system partition as rw so that you can copy back (to /system/app) the missing apk packages that you've already copied to your sdcard.
Navigate to the location where your adb executable is installed:
1. cd C:\android-sdk-windows\tools> adb shell
2. $ su
3. # mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
4. # cd /system/app
5. # ls (make sure it is mounted)
6. # cd /sdcard
7. # ls *.apk (show the apk package filenames)
8. # cp "apkfilename" /system/app (copy from current working directory [/sdcard] to /system/apps)
On step 8, replace "apkfilename" with apk's you want to copy. Repeat process as many times as necessary to copy back all the default apk's that you removed.
Taken partially from http://androidforums.com/2079717-post6.html
After you have copied all of your stock apk's back, simply unplug your phone, and reboot. Once you have rebooted press and hold volume down, power and camera buttons until the recovery menu pops back up, then simply select install update.zip
This time the installer will not error out on missing packages.
If you want to root your phone after installing the EC05 Stock Update:
http://forum.androidcentral.com/epi...optional-ext4-new-updated-2-a.html#post760733
For those who only need the stock epic asphalt demo here it is.
(Note to mods, this is a 5 minute demo only, not a full game. As such I believe it is ok to post.)
I was looking inside the run.bat file and I used a run.bat file that did not remove asphalt5.apk and freeHDGamesDemo.apk.
Now I don't know if you need the freeHDGamesDemo.apk or where to find it.
I was going to reinstall the asphalt5.apk, but do I erase the /sdcard/gameloft/ folder and if I do will it be recreated again or should I leave it in?
You can get rid of the gameloft folder on sdcard, thats where it puts the file it downloads when you launch the asphalt demo and it prompts to download. Be careful though, if you have other gameloft games they will also use that folder.
I'm not sure on the free hd demo file, if the ota complains about it we should be able to pull it from the eb13 tar file. If it's not posted by time the ota rolls out I'll add it here for ease.
Sent from my SPH-D700 using XDA App
rocket321 said:
You can get rid of the gameloft folder on sdcard, thats where it puts the file it downloads when you launch the asphalt demo and it prompts to download. Be careful though, if you have other gameloft games they will also use that folder.
I'm not sure on the free hd demo file, if the ota complains about it we should be able to pull it from the eb13 tar file. If it's not posted by time the ota rolls out I'll add it here for ease.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Thanks, I am not a big game player so the little asphalt5 demo is about all I need - I never even opened the freeHDDemo file so I don't know what it does, I was only looking for it incase it stopped you from getting any minor updates via OTA's.
I didn't think the Odin EC05 no data loss upgrade version would remove those two apps on Androidcentral.
i did everything but when i went to the system menu to intall the update.zip i dont have that file...
where do i get it from?
Joph said:
i did everything but when i went to the system menu to intall the update.zip i dont have that file...
where do i get it from?
Click to expand...
Click to collapse
Check this thread:
http://forum.xda-developers.com/showthread.php?t=1005593
I have modified several of the updates to be installed in ClockworkMod Recovery so that it will not overwrite CWM Recovery and should also preserve root. I still recommend protecting root using Voodoo OTA Rootkeeper in case something goes wrong and it is always a good idea to make a nandroid backup in ClockworkMod Recovery before installing any update. Also after updating Titanium backup said that my su had the wrong permission and it wanted to correct it (I allowed it to fix it). I am not sure why this happened as I thought I set the permissions properly in the update but go ahead and run Titanium after updating and let it fix it for you if there is a problem. These updates will still check all of your system apps so you need to restore them (copying and pasting them back into the /system/app folder and setting the proper permissions with Root Explorer is one of the easiest ways to do this). You can also make your own modifications to the update and remove the checks if you like (some people have done this with no problems but one guy reported that android wouldn't boot after updating with no checks so I leave it up to you to decide for yourself). I posted instructions for modifying the update here. The changes I made to the update were to remove the Indigo check (because it was giving me an error) commented out the lines that delete the current recovery and install the new recovery, removed the line that deletes Superuser.apk, added an su file to the update so that it reinstalls su after deleting it, and finally added lines to symlink and set permissions for the su file.
Install instructions:
Protect root with Voodoo OTA Rootkeeper (just in case)
Copy the proper update.zip to your external sdcard (if you are US or WE you must install 086 before 089)
Make sure your battery is well charged (having your battery die during the update would be very bad)
Turn off TpT and boot into recovery by turning on and repeatedly pressing the volume up key
Wipe cache partition
Make a nandroid backup (not necessary but highly recommended)
Select install zip from sdcard>choose zip from sdcard then browse to and select the update you downloaded here
Let the install run and then choose reboot system now in the CWR main menu
The first boot will take a long time, don't worry this is normal (if it takes more than 30min you may want to hold power to turn off and reboot again)
ThinkPadTablet_A310_02_0037_0076_WE_CWR.zip
ThinkPadTablet_A310_02_0039_0086_US_CWR.zip
ThinkPadTablet_A310_02_0039_0089_US_CWR.zip
ThinkPadTablet_A310_02_0039_0086_WE_CWR.zip
ThinkPadTablet_A310_02_0039_0089_WE_CWR.zip
ThinkPadTablet_A310_02_0039_0087_UK_CWR.zip
ThinkPadTablet_A310_02_0039_0089_ROW_CWR.zip
ThinkPadTablet_A310_02_0039_0089_SC_CWR.zip
ThinkPadTablet_A310_02_0039_0090_JP_CWR.zip
Flash at your own risk! I am not responsible if this totally bricks your tablet, breaks your root, or creates any other problems for you! Make sure that you install the correct version for your region.
Worked great for me. Thanks!
Is it also necessary to temporarily unroot before applying the update? Thanks again.
I don't believe I needed to do a tempory un-root to apply the updates. I just followed the instructions. I did have to power down during the first installation since it stayed in .. rebooting.. mode for 20 to 25 minutes. After powering down and rebooting, _86 was installed.
I did have to re-install Busybox to get LUKS Manager to work after the installation of 86 and 89.
Thanks, but I got in trouble with OTA2 by not unrooting first, and the OP is the one who helped me with it. I need to make sure before I make a move.
It should not matter, the update deletes and reinstalls su.
Thank you. I'll give it a try later today.
great thanks.
a sticky would be great
I just applied OTA 2.5, now my market consistently force crashes. Anybody else having this issue?
try to download and install new "Play Store"
mandrsn1 said:
I just applied OTA 2.5, now my market consistently force crashes. Anybody else having this issue?
Click to expand...
Click to collapse
My market is working fine on OTA 2.5. Maybe you have two versions of the same app installed after updating (for example if you removed FlexT9 in system and installed the full FlexT9 keyboard from the market and then restored the system app to update). It could also be a problem due to the change over to the new Play Store as quyTam suggested. If all else fails a factory reset would likely fix the problem but then you will have to set everything up again.
jhankinson said:
My market is working fine on OTA 2.5. Maybe you have two versions of the same app installed after updating (for example if you removed FlexT9 in system and installed the full FlexT9 keyboard from the market and then restored the system app to update). It could also be a problem due to the change over to the new Play Store as quyTam suggested. If all else fails a factory reset would likely fix the problem but then you will have to set everything up again.
Click to expand...
Click to collapse
Nope, i unfroze apps before i updates and made sure there were no replaced system apps when I installed.
I have tried stock market, 3.4.4 (honeycomb 3.2 market) and 3.4.6 (Play store) and they all force crash. Sounds like a factory reset may be needed.
mandrsn1 said:
Nope, i unfroze apps before i updates and made sure there were no replaced system apps when I installed.
I have tried stock market, 3.4.4 (honeycomb 3.2 market) and 3.4.6 (Play store) and they all force crash. Sounds like a factory reset may be needed.
Click to expand...
Click to collapse
Something else must be messed up. I factory restored and still am having issues.
I got an error message after trying to install file from SD Card. It said
"Installing: /sdcard/ThinkPadTablet_A310_02_0039_0089_ROW_CWR.zip
Finding update package...
Opening update package...
Installing update...
Verifying Current system...
assert failed: apply_patch_check("/system/app/FlexT9ChineseIME.apk", "222668fd99a68916eb4d6784c3795801ea0698bd" , "8c4feb3af89ec0ff3791c0d5acf30bad168b4600")
E:Error in /sdcard/ThinkPadTablet_A310_02_0039_009_ROW_CWR.zip
(Status 7)
Installation aborted.
I'm currently using 0074ROW
Could someone advise how to fix this?
Put back the system file indicated - FlexT9ChineseIME.apk.
toenail_flicker said:
Put back the system file indicated - FlexT9ChineseIME.apk.
Click to expand...
Click to collapse
Thanks but where can I found it?
That depends on what country you're from. There's a couple of system dumps here on xda.
same here can't ota update coz i deleted some of the apps so can anyone know where can find the dump for the 0074 row dump? or could someone please provide the dump here?
thx for the help!!!
You can also go to the Lenovo download page to find your previous download file, unzip it, and find the file to put back.
toenail_flicker said:
You can also go to the Lenovo download page to find your previous download file, unzip it, and find the file to put back.
Click to expand...
Click to collapse
thx for the help. just asking are you referring to this:
download.lenovo.com/slates/think/tablet1
the worse thing is i deleted the drmprovider.apk and the odex as well which i couldn't see that apps in those zip.
so could anyone help here?
thx!!!
I rooted my TPT with the yet another root exploit method while on version 0089_US, and it worked great. Then I installed RootKeeper and temporarilly unrooted. My TPT is not and never has been modified in any other way, no CWR, no apps deleted, nothing.
When I try to install the OTA ICS update, it will start to install, and then fail with some kind of assert failed error message that mentiones busybox, and then say error in /cache/update.zip.
Anybody know what's going on???
I had the same issues with the ROW update. I followed this thread (thoroughly) and got ICS with root intact.
http://forum.xda-developers.com/showthread.php?t=1723048
I'm confused. The fix was:
"Restored busybox from the same file mentioned before and it worked."
How do I "restore" busybox?
userno69 said:
I'm confused. The fix was:
"Restored busybox from the same file mentioned before and it worked."
How do I "restore" busybox?
Click to expand...
Click to collapse
Here's what I needed to do to get busybox restored and access to my stock recovery again:
1. Downloaded a previous update from Lenovo's site. (had to go two versions prior to find one with a busybox file in it).
2. Extract the Busybox file from the archive (system/xbin Directory)
3. Copy the file to your tablet
4. Using ES File Explorer or Astro, copy this Busybox over to the system/xbin Directory on your device. Note: I had trouble here with permissions that came down to a few settings in ES File Explorer (system access, write permissions, etc).
5. Reboot into recovery by pushing Vol + a few times after Lenovo appears.
Hope this helps.
-A
Both ES File Explorer and File Manager fail when attempting to overwrite the existing busybox.
Any suggestions?
garypen said:
Both ES File Explorer and File Manager fail when attempting to overwrite the existing busybox.
Any suggestions?
Click to expand...
Click to collapse
Can you verify your ES file explorer root settings (Root Explorer and Mount file system enabled). These settings are required to make changes to system files.
EpsilonTheGreat said:
Can you verify your ES file explorer root settings (Root Explorer and Mount file system enabled).These settings are requibe able to overwrite busybox.
Click to expand...
Click to collapse
Thanks! That enabled me to overwrite busybox. Now, I am crossing my fingers that the OTA update works.
It started downloading directly from the "check for update" page, rather than quickly saying an update was available, and asking to reboot and install, as it had been doing. So, perhaps it checks busybox before even DLing the update.
It's taking a while to DL. I'll post results after the next reboot ad install attempt.
garypen said:
Thanks! That enabled me to overwrite busybox. Now, I am crossing my fingers that the OTA update works.
It started downloading directly from the "check for update" page, rather than quickly saying an update was available, and asking to reboot and install, as it had been doing. So, perhaps it checks busybox before even DLing the update.
It's taking a while to DL. I'll post results after the next reboot ad install attempt.
Click to expand...
Click to collapse
I saw the exact same thing after fixing busybox. Glad it worked for you (so far)!
Worked like a champ. Rocking ICS on my TPT with root.
It's really not a huge diff from HC. But, lots of little things that I had become accustomed to on my ICS phone.
The tpt does seem a little faster now. Play store is working better, too.
I just wish I could replace that stupid Lenovo quick app icon with the android app launcher icon, like on my nexus. Why do they locate the apps icon at the very top corner? Makes no sense.
I've tried all the busyboxes that I can find and still no update. Can someone post a working one?
I used the one from the 0086US update.
I found one, I used the OTA update.zip
http://forum.xda-developers.com/showthread.php?t=1507285 OTA Update.zip A310_02_0039_0086_US
Also, I kept root.
assert(file_getprop("/system/build.prop", "ro.build.fingerprint") == "Lenovo/ThinkPadTablet/Indigo:4.0.3/ThinkPadTablet _A400_03/0065_0128_US:user/release-keys" || file_getprop("/system/build.prop", "ro.build.fingerprint") == "Lenovo/ThinkPadTablet/Indigo:4.0.3/ThinkPadTablet _A400_03/0069_0130_US:user/release-keys")
Error in /tmp/sideload/package.zip
Summonabeeeetch!!!! I noticed its the first step of the script... any ideas? Anyone? Maybe Ian not destined for ics :-( any ideas?
daswahnsinn said:
I found one, I used the OTA update.zip
http://forum.xda-developers.com/showthread.php?t=1507285 OTA Update.zip A310_02_0039_0086_US
Click to expand...
Click to collapse
You can get it directly from Lenovo:
http://download.lenovo.com/slates/think/tablet1/ThinkPadTablet_A310_02_0039_0086_US.zip
Busybox is located in the system/xbin folder.
garypen said:
You can get it directly from Lenovo:
http://download.lenovo.com/slates/think/tablet1/ThinkPadTablet_A310_02_0039_0086_US.zip
It's located in the system/xbin folder
Click to expand...
Click to collapse
For some strange reason I couldn't get any of the ones from the lenovo site to work, Thank though this should help someone else for sure.
I was able to update to ICS with CW by editing the updater-script. I commented out the verification check.
ScotchtapeLoser said:
I was able to update to ICS with CW by editing the updater-script. I commented out the verification check.
Click to expand...
Click to collapse
Which ones did you comment out?
Your Tablet may vary....
I started with
Build.prop
Gmail
Anything starting with Google...
MarketUpdater
MediaProvider
Mediauploader
NetworkLocation
I would comment out the line, add the new updater-script to the zip file. Try it. When it threw out an error I would comment out that line... rinse and repeat
After a time I just became annoyed and comment out all of the apply_patch_check (around 450 lines). I do not advise using this shotgun approach.
bigsnack said:
Which ones did you comment out?
Click to expand...
Click to collapse
ICS OTA install busybox error
Hey guys I didn't want to start another thread because this one is very similar to the issue I am having now. My tablet asks me to install an OTA update but once its about half way done in recovery in spits out some kind of error(check attachment). When it comes to tablets Im a noob but I was wondering if you guys can give me some solid instructions on how to get past it?
Thanks in advance.
Reference this thread:
http://www.thinkpadtabletforums.com...ds-and-development/ics-ota-failing-w-busybox/
When apps that ask for root permissions are launched, it doesnt work, example: TI backup says that the device isnt rooted and i might have to check the SU binaries. My N7 was rooted before a update for Superuser was available, now something happen after i updated it. But i dont know what...
That's weird. After you updated your SU, did you go to SU to update its binaries?
i did that twice, and it did say to update binaries...so...
you might need SuperSu instead
What Android version are you running?
Droid_Boi86 said:
i did that twice, and it did say to update binaries...so...
Click to expand...
Click to collapse
I had similar problems with "lightly rooted" stock (4.2.1/JOP40D) using a slightly older version of Superuser. Some apps could get root and others could not. But things have been in flux recently; read on...
I poked around a little bit and it appeared that the 4.2 multi-user stuff was interfering with the way that older versions of (ChainsDD's) Superuser worked, and at that time (only a couple weeks ago) ChainsDD had not released a newer update - things were still in flux.
I switched over to SuperSU, and no problems since... but....
...for me, installation of SuperSU didn't go swimmingly. As I recall the SuperSU install instructions say something like "you need to already have root to install the SuperSU `su' binary". Makes sense as it needs to write it's 'su' binary into /system, which in turn means it needs to get root privilege from a pre-existing su/Superuser installation.
So it poses a chicken-and-egg problem if you have lost root completely which I somehow managed to do... wait, I remember now! I had left the old 'su' binary in place, but had manually uninstalled "Superuser" from /system before I attempted the SuperSU install. Doh!
If you have lost root... you can manually install SuperSU offline inside the recovery via adb & the command line, which means getting both the SuperSU.apk and the 'su' binary ahead of time.
You can get the .apk from the market. You can attempt an install - it will download the 'su' binary and (no kidding) place a copy of it in /data/data/eu.chainfire.supersu/files/superuser.png
If you haven't lost root completely inside the booted OS, I suggest mounting /system in "rw" mode prior to running the SuperSU install and startup.
It looks like I am back a version or two - I have superSU v 0.99
4d7abc0eb5898cdb81bc233dcd16e052 /system/app/SuperSU.apk
0034ec008416b1c3fa7010deb8a3a758 /system/xbin/su
-rwsr-sr-x 1 root root 91992 Jan 10 16:40 /system/xbin/su
note the setuid,setgid bits on /system/xbin/su. Also - no symlink from /system/bin/su to xbin/su.
OK, sorry for the long post. There have been new releases from both chainfire (SuperSU) and chainsDD (Superuser) quite recently. Since I haven't had any troubles since 10 January, I haven't been following it closely - YMMV.
cheers
Hi guys
I am pretty new to android, but i know a lot about pc's.
I have a OP5 and rooted it, but then i had an issue with SuperSU and uninstalled it. What i did not think, is that if i reinstall it, it has no root access, because i can not grant it.
So i tried reinstalling it with TWRP, but it did not get root access.
Does anyone know how to give it root again/reinstall it with root?
(i could reflash the os and reinstall superSU, but i dont want to set uo the phone again)
Also does anyone know the progress on nethunter for OP5?
Thanks and yours
cacciu
Cacciu said:
Hi guys
I am pretty new to android, but i know a lot about pc's.
I have a OP5 and rooted it, but then i had an issue with SuperSU and uninstalled it. What i did not think, is that if i reinstall it, it has no root access, because i can not grant it.
So i tried reinstalling it with TWRP, but it did not get root access.
Does anyone know how to give it root again/reinstall it with root?
(i could reflash the os and reinstall superSU, but i dont want to set uo the phone again)
Also does anyone know the progress on nethunter for OP5?
Thanks and yours
cacciu
Click to expand...
Click to collapse
It's been awhile since I used SuperSU so I might be fuzzy: SuperSU has two components, 1) the .zip portion installed from TWRP and 2) the APK. The zip is like "the framework/service/su" part and the APK is the app that just tracks and loads the DB with which apps or services have been granted SU access.
My question is "Which of these did you uninstall?" : OR: Did you uninstall both? Maybe only uninstalling one or the other causes an 'out of sync' condition.
Anyway: This version of SuperSU https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133 discussed in that thread has the APK in the .zip file. By definition all TWRP recoveries are rooted and can do what they want to like installing SuperSU.
What happens after you boot seems more likely to be about left-over crud from the APK / DB component, (and I'm guessing here), so if the SuperSU APK is still there, I'd clear it's data entirely, perhaps get rid of it entirely if you can and reinstall the .zip that contains all parts of SuperSU (maybe they all do now) from that link ^^. Make sure that link I gave is the one you want (systemless, etc).
TWRP should've done the heavy lifting during SuperSU install since it's already rooted. If it didn't, then keep the log from TWRP and look over it's install steps during the SuperSU install. Post it here maybe.
Thanks for the answer.
I uninstalled the apk.
I already tried to install the apk directly and also installing it from the zip, and there was either a message like "no root detected" or " root is corrupted".
I also deleted the su folder, uninstalled the apk and reinstalled the zip. But it was always the same: the apk did either say it's not rooted or did not install/show in the apps.
Probably i have to unroot and root it, or do you have any other idea?
TWRP Terminal
I found out, that there is a terminal with root access on twrp. So i searched for eu.chainfire.supersu with the find comman and use chown root:root to give each directory root access. But it still did not recognize the root. So i thought about the db you said and maybe it doesnt recognize the db.
So i tried the same with dsploit as it doesnt run without root, but it's the same.
I will try to delete all the supersu directories as well as any su directory and reinstall the zip. Or if there is an apt-get, i will try it to install it by terminal
Cacciu said:
I found out, that there is a terminal with root access on twrp. So i searched for eu.chainfire.supersu with the find comman and use chown root:root to give each directory root access. But it still did not recognize the root. So i thought about the db you said and maybe it doesnt recognize the db.
So i tried the same with dsploit as it doesnt run without root, but it's the same.
I will try to delete all the supersu directories as well as any su directory and reinstall the zip. Or if there is an apt-get, i will try it to install it by terminal
Click to expand...
Click to collapse
You might be out of luck if you deleted the su directory or any other related to binary su code. I'm not sure why you couldn't do a reinstall of the original SuperSU .zip file. You've got that whole 'catch-22' thing going right now.
The only thing I'm wondering about is whether a certain amount of cleanup has to take place before you can just roll SuperSU*.zip over an old mangled version and get it to work. Do you get errors in TWRP when trying to reinstall the entire package?
---------- Post added at 02:48 PM ---------- Previous post was at 02:05 PM ----------
I downloaded this version of SuperSU (which may or may not be what you used, but you of course want the one you used): http://download.chainfire.eu/1114/SuperSU/SR1-SuperSU-v2.82-SR1-20170608224931.zip
Then I unzipped it and the installer script for not only the binary parts but the apk is here .\SR1-SuperSU-v2.82-SR1-20170608224931\META-INF\com\google\android\updater-binary. (updater-script is a dummy). It's kind of old school and is very easy to understand (the shell script that installs it).
All the files that it pushes onto the SD are easy to find and use, although you have to keep SELinux settings in mind.
It's worth taking a look at if you want to try to rebuild the wrecked version or if you want to just reapply the zip and have a better understanding of any errors it spits out.
Good luck.