Just to add to the list - this is what I had to do to get my Thinkpad to update.
I was rooted, and had CWR installed. I downloaded the ICS update from Lenovo's Website (http://download.lenovo.com/slates/think/tablet1) file was (http://download.lenovo.com/slates/think/tablet1/ThinkPadTablet_A310_03_0069_0130_US.zip). I was getting an indigo check error right away though when trying to flash.
I knew that I had to update the updater-script from META-INF\com\google\android\ in the zip file. Ultimately I totally removed the following lines from it:
assert(file_getprop("/system/build.prop", "ro.build.fingerprint") == "Lenovo/ThinkPadTablet/Indigo:3.1/ThinkPadTablet_A310_02/0039_0089_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");
assert(getprop("ro.product.device") == "Indigo" ||
getprop("ro.build.product") == "Indigo");
I first tried doing this with Notepad++ on windows and ultimately got an error 6 when trying to flash. Luckily I have an Ubuntu (a type of linux) machine laying around and was able to edit the file within the zip using Ubuntu. I copied the ThinkPadTablet_A310_03_0069_0130_US.zip to my network, opened it up in Ubuntu, navigated to META-INF\com\google\android\ and opened updater-script. After removing those lines listed above, I closed out of Gedit and had a prompt asking if it should update the zip. I hit yes and that is the file that worked for me. If you don't have access to a linux machine it may be easy enough for you to make a live CD (https://help.ubuntu.com/community/LiveCD) that will allow you to boot into Ubuntu and not affect the OS of your computer. You could put your update zip file on a thumbdrive, boot the live cd, and edit it that way. Ubuntu is free and everything you need to update your zip should be included on the live CD (zip utility and a text editor).
With my new edited update.zip I started to flash, got much further and then bombed on busybox. I got the busybox file from this post (http://forum.xda-developers.com/showthread.php?t=1741623) file was (http://dl.dropbox.com/u/6846397/Original/busybox). I copied to my thinkpad and moved it to /system/xbin using Root Explorer (I've been an Android user since the G1 and made it this far without Root Explorer but bought it just for this - that App works great and you should get it). If you get an error that you can't write the file hit the Mount R/W at the top (and its always a good idea to rename the original so you have a backup).
At this point I backed up root with Voodoo OTA Rootkeeper, disabled root, rebooted into CWM and flashed my update. Finally things went smooth, i rebooted into ICS and used Voodoo Root Keeper to restore root.
Something else to note is that if you have a root file explorer (and root) you can browse to /cache/recovery and open the last_log file if you are still getting tripped up to see what is failing.
Now I am updated to ICS, restored root, and lost CWM. Hope this helps some of you guys that are stuck. What a pain this was.
karlherr said:
Just to add to the list - this is what I had to do to get my Thinkpad to update.
I was rooted, and had CWR installed. I downloaded the ICS update from Lenovo's Website (http://download.lenovo.com/slates/think/tablet1) file was (http://download.lenovo.com/slates/think/tablet1/ThinkPadTablet_A310_03_0069_0130_US.zip). I was getting an indigo check error right away though when trying to flash.
I knew that I had to update the updater-script from META-INF\com\google\android\ in the zip file. Ultimately I totally removed the following lines from it:
assert(file_getprop("/system/build.prop", "ro.build.fingerprint") == "Lenovo/ThinkPadTablet/Indigo:3.1/ThinkPadTablet_A310_02/0039_0089_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");
assert(getprop("ro.product.device") == "Indigo" ||
getprop("ro.build.product") == "Indigo");
I first tried doing this with Notepad++ on windows and ultimately got an error 6 when trying to flash. Luckily I have an Ubuntu (a type of linux) machine laying around and was able to edit the file within the zip using Ubuntu. I copied the ThinkPadTablet_A310_03_0069_0130_US.zip to my network, opened it up in Ubuntu, navigated to META-INF\com\google\android\ and opened updater-script. After removing those lines listed above, I closed out of Gedit and had a prompt asking if it should update the zip. I hit yes and that is the file that worked for me. If you don't have access to a linux machine it may be easy enough for you to make a live CD (https://help.ubuntu.com/community/LiveCD) that will allow you to boot into Ubuntu and not affect the OS of your computer. You could put your update zip file on a thumbdrive, boot the live cd, and edit it that way. Ubuntu is free and everything you need to update your zip should be included on the live CD (zip utility and a text editor).
With my new edited update.zip I started to flash, got much further and then bombed on busybox. I got the busybox file from this post (http://forum.xda-developers.com/showthread.php?t=1741623) file was (http://dl.dropbox.com/u/6846397/Original/busybox). I copied to my thinkpad and moved it to /system/xbin using Root Explorer (I've been an Android user since the G1 and made it this far without Root Explorer but bought it just for this - that App works great and you should get it). If you get an error that you can't write the file hit the Mount R/W at the top (and its always a good idea to rename the original so you have a backup).
At this point I backed up root with Voodoo OTA Rootkeeper, disabled root, rebooted into CWM and flashed my update. Finally things went smooth, i rebooted into ICS and used Voodoo Root Keeper to restore root.
Something else to note is that if you have a root file explorer (and root) you can browse to /cache/recovery and open the last_log file if you are still getting tripped up to see what is failing.
Now I am updated to ICS, restored root, and lost CWM. Hope this helps some of you guys that are stuck. What a pain this was.
Click to expand...
Click to collapse
At least you have official ICS, we K1 users have been lied to and have been waiting a month for ICS (the 3rd time around) because of some stupid but easy installation of the Play Store.
Thanks karlherr!
karlherr said:
Just to add to the list - this is what I had to do to get my Thinkpad to update.
I was rooted, and had CWR installed. I downloaded the ICS update from Lenovo's Website (http://download.lenovo.com/slates/think/tablet1) file was (http://download.lenovo.com/slates/think/tablet1/ThinkPadTablet_A310_03_0069_0130_US.zip). I was getting an indigo check error right away though when trying to flash.
I knew that I had to update the updater-script from META-INF\com\google\android\ in the zip file. Ultimately I totally removed the following lines from it:
assert(file_getprop("/system/build.prop", "ro.build.fingerprint") == "Lenovo/ThinkPadTablet/Indigo:3.1/ThinkPadTablet_A310_02/0039_0089_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");
assert(getprop("ro.product.device") == "Indigo" ||
getprop("ro.build.product") == "Indigo");
I first tried doing this with Notepad++ on windows and ultimately got an error 6 when trying to flash. Luckily I have an Ubuntu (a type of linux) machine laying around and was able to edit the file within the zip using Ubuntu. I copied the ThinkPadTablet_A310_03_0069_0130_US.zip to my network, opened it up in Ubuntu, navigated to META-INF\com\google\android\ and opened updater-script. After removing those lines listed above, I closed out of Gedit and had a prompt asking if it should update the zip. I hit yes and that is the file that worked for me. If you don't have access to a linux machine it may be easy enough for you to make a live CD (https://help.ubuntu.com/community/LiveCD) that will allow you to boot into Ubuntu and not affect the OS of your computer. You could put your update zip file on a thumbdrive, boot the live cd, and edit it that way. Ubuntu is free and everything you need to update your zip should be included on the live CD (zip utility and a text editor).
With my new edited update.zip I started to flash, got much further and then bombed on busybox. I got the busybox file from this post (http://forum.xda-developers.com/showthread.php?t=1741623) file was (http://dl.dropbox.com/u/6846397/Original/busybox). I copied to my thinkpad and moved it to /system/xbin using Root Explorer (I've been an Android user since the G1 and made it this far without Root Explorer but bought it just for this - that App works great and you should get it). If you get an error that you can't write the file hit the Mount R/W at the top (and its always a good idea to rename the original so you have a backup).
At this point I backed up root with Voodoo OTA Rootkeeper, disabled root, rebooted into CWM and flashed my update. Finally things went smooth, i rebooted into ICS and used Voodoo Root Keeper to restore root.
Something else to note is that if you have a root file explorer (and root) you can browse to /cache/recovery and open the last_log file if you are still getting tripped up to see what is failing.
Now I am updated to ICS, restored root, and lost CWM. Hope this helps some of you guys that are stuck. What a pain this was.
Click to expand...
Click to collapse
Thanks this worked very well! I'm late to the ICS party and spent hours reading through the various forums today before happening upon your post. I followed your advice pretty much to the letter except that I found that I could get the same results in windows 7 without having to go to linux. There is a gedit for windows at http://ftp.gnome.org/pub/gnome/binaries/win32/gedit/ . I used 7Zip, with gedit selected as the editor. I was able to open the ICS update.zip in 7Zip, edit out the indigo entry, and save the zip. Worked except that updater couldn't find notesmobile_len-oem.apk in system\apps though it was installed. Pulled that from http://forum.xda-developers.com/showthread.php?t=1243218 (thanks WyldStyl3) and then the update went through.
Need Help wit CWM Install
I have the US version Thinkpad running 4.0.3. I have successfully rooted the tablet. I have searched endlessly and tried many times to install CWM so I can eventually get Jellybean installed. Can you help with some simple instructions on how to install CWM.
You might want to look at Koshu's threads:
CWM: http://forum.xda-developers.com/showthread.php?t=1831161
CM10: http://forum.xda-developers.com/showthread.php?t=1846044
Thanks
Thanks for the links. Have read hundreds of threads but did not see any instructions on how to activate the PEN ONLY FUNCTION on the Lenovo Thinkpad US Version Running the rooted Jellybean. But I figured it out on my own. Here is how in case anyone else is interested.
1. Make sure your hardware buttons at the bottom edge are turned on.
2. TOggle the second button from the left and it changes from "touch screen off to on.
Then you can use your pen when the touch screen is off.
Thank you very much for this detailed and COMPLETE instruction set
I was crawling threads on various forums for three days now, and finally I am able to run the update.
Good work, u saved my weekend
Greetings from Austria,
norkarnt
Your welcome
Yea I know how frustrating that search was. Glad to help. By the way the 4.1.2 is great and clears all of the Lenovo useless and unsupported apps from the:good: tablet. You will have to purchase the full version of Docs To Go however. And Writepad is a good substitute for Notes Mobile.
Tim
norkarnt said:
Thank you very much for this detailed and COMPLETE instruction set
I was crawling threads on various forums for three days now, and finally I am able to run the update.
Good work, u saved my weekend
Greetings from Austria,
norkarnt
Click to expand...
Click to collapse
Related
I made this for all the people that seem to be having issues with rooting their phone, installing the recovery partition, and installing the new rom.
This is an all-in-one package. It's about 200MB. Includes the original root rom, recovery image, the new rom (2.1OTA rom that was just released today), as well as a few extras. It's a batch script to automate the entire process.
Here's the README file:
Code:
These are automated scripts to root your Eris phone with Android 1.5 (NOT 2.1 LEAK!!!!!)
YOU NEED THE ANDROID SDK IN ORDER FOR THIS TO WORK!
If you don't have the SDK working, visit guide on the forums for instructions.
INSTRUCTIONS:
Unzip this file to your \tools\ directory of your Android SDK. Then run one of the following files:
install_root.bat
------------------------
This script will do the following:
1) Install the root image onto your phone
2) Install the recovery partition onto your phone
3) Install the current rom using the recovery partition
install_extras.bat
------------------------
This script will do the following:
1) Install live wallpapers
2) Install the Nexus Launcher
3) Install the Nexus photo gallery
4) Remove HTC Lockscreen
5) Install wireless tethering
NOTE!
------------------------
1) NOT ALL LIVE WALLPAPERS YOU FIND IN THE MARKET WILL WORK!
2) You cannot use the Nexus photo gallery when in the Nexus Launcher, it will crash
These scripts were put together by GrdLock.
Credit for all of the included files goes to ivan, amon, jcase, and everyone else
who chipped in!
Install this by unzipping it into your \tools\ directory of your Android SDK, then run install_root.bat.
I'm not running Windows so I didn't test this, but I proof read it like 10 times, and I'm 99.99% sure it should work 100%. If anyone gets any errors using it, post and I'll fix them immediately. Make sure USB debugging is turned on before running it.
You can download the whole package here: http://www.multiupload.com/Y7UC8UU2JE
-------------------------------------------------------------------
If you just want the 2.1OTA rooted rom, you can download that here: http://www.multiupload.com/YP1BIUOF60 (this rom includes busybox, the otacert fix, and a few other minor things)
I also put together an update. This will update you to the new 2.1 OTA leak "official" without wiping. Wipe your dalvik and that's it. Do a nand backup first though just incase! http://www.multiupload.com/3OPZCD6NRA
GrdLock said:
I made this for all the people that seem to be having issues with rooting their phone, installing the recovery partition, and installing the new rom.
This is an all-in-one package. It's about 200MB. Includes the original root rom, recovery image, the new rom (2.1OTA rom that was just released today), as well as a few extras. It's a batch script to automate the entire process.
Here's the README file:
Code:
These are automated scripts to root your Eris phone with Android 1.5 (NOT 2.1 LEAK!!!!!)
YOU NEED THE ANDROID SDK IN ORDER FOR THIS TO WORK!
If you don't have the SDK working, visit guide on the forums for instructions.
INSTRUCTIONS:
Unzip this file to your \tools\ directory of your Android SDK. Then run one of the following files:
install_root.bat
------------------------
This script will do the following:
1) Install the root image onto your phone
2) Install the recovery partition onto your phone
3) Install the current rom using the recovery partition
install_extras.bat
------------------------
This script will do the following:
1) Install live wallpapers
2) Install the Nexus Launcher
3) Install the Nexus photo gallery
4) Remove HTC Lockscreen
5) Install wireless tethering
NOTE!
------------------------
1) NOT ALL LIVE WALLPAPERS YOU FIND IN THE MARKET WILL WORK!
2) You cannot use the Nexus photo gallery when in the Nexus Launcher, it will crash
These scripts were put together by GrdLock.
Credit for all of the included files goes to ivan, amon, jcase, and everyone else
who chipped in!
Install this by unzipping it into your \tools\ directory of your Android SDK, then run install_root.bat.
I'm not running Windows so I didn't test this, but I proof read it like 10 times, and I'm 99.99% sure it should work 100%. If anyone gets any errors using it, post and I'll fix them immediately. Make sure USB debugging is turned on before running it.
You can download the whole package here: http://www.multiupload.com/09DM1FI1D1
md5: 535c300411cd47acd319e667fee8cf16
-------------------------------------------------------------------
If you just want the 2.1OTA rooted rom, you can download that here: http://www.multiupload.com/5HH0H1M4T1 (this rom includes busybox, the otacert fix, and a few other minor things)
md5: 6d95e5e8846c6912fda42c54daa0cb34
I also made a kernel-only update that can be flashed without wiping anything: http://www.sendspace.com/file/5ptpmc
md5: cc4e95034dc7e8adaa776483251952bf
Click to expand...
Click to collapse
Thanks....I will be using this on the wifes (soon to be mine) phone tonite as with the new OTA update I now feel my phone is stable enough for her not to freak out over
appreciate your work....
does the script disable OTA's ?
rvpartsguy said:
Thanks....I will be using this on the wifes (soon to be mine) phone tonite as with the new OTA update I now feel my phone is stable enough for her not to freak out over
appreciate your work....
does the script disable OTA's ?
Click to expand...
Click to collapse
Yes, I built the otacert fix into the rom.
Thanks for all your work grid, and all the others that have worked on this. Just got a new refurb the other day and was going to tackle rooting this weekend, gonna make the task so much easier.
Can you please explain what was fixed? Thanks again for your work.
The current rom is a rooted rom using the new 2.1 leak that was just released today, which is SUPPOSEDLY the "official" 2.1 update from Verizon.
What setting should be used for the phone, HTC Sync, USB, Mount SD, or nothing?
Nothing. Just connect it to your USB, and enable USB debugging. Don't mount your sdcard.
Does the market work now?
(I recall hearing that the market wouldn't work because of the test/dev certificate that was in the leaked rom)
The market will work if it doesnt work now, itll work when the OTA comes out.
Grd, this looks fantastic. I've been patient so far, and haven't upgraded to the leaked or original rooted 2.1 builds, but with the news of the latest one (and initial reports saying that it's mostly bug-free), I'm ready to take the plunge. This should be a huge help to me.
A couple of questions:
Does the big package (the 200MB one) include jcase's ROM (bare-bones basic), or yours with the tweaks? I ask because you mentioned removing pdfviewer, which I use.
Also, has anyone else gone through this process yet? Call me timid, but I'm not too keen on being the first one.
K0CAW said:
Grd, this looks fantastic. I've been patient so far, and haven't upgraded to the leaked or original rooted 2.1 builds, but with the news of the latest one (and initial reports saying that it's mostly bug-free), I'm ready to take the plunge. This should be a huge help to me.
A couple of questions:
Does the big package (the 200MB one) include jcase's ROM (bare-bones basic), or yours with the tweaks? I ask because you mentioned removing pdfviewer, which I use.
Also, has anyone else gone through this process yet? Call me timid, but I'm not too keen on being the first one.
Click to expand...
Click to collapse
It includes my rom. You should be able to restore pdfviewer if you need it though. I can post the files in a bit.
Great. I was pretty sure that the apps could be reinstalled if needed, but wanted to confirm. I'm downloading the package now, so I'll keep you updated. I'm pretty excited about this, since I'm still at stock 1.5.
Issues, Well first It copied the PB image fine, it didnt reboot the phone i had to manually do it with vol -, now im on step two installing amons image, it transfers but it cant start files\flash_image, no such file or directory and then it cant chmod it cause its not there.
Could you copy/paste the command prompt text you're seeing? (you gotta right-click the cmd window and select Mark)
Installing Amon's Recovery Image.
1545 KB/s (3926016 bytes in 2.480s)
cannot stat 'files\flash_image': No such file or directory
Unable to chmod /system/bin/flash_image: No such file or directory
flash_image: not found
-
Finished
Your phone will now reboot and test the recovery partition.
Press any key to continue . . .
Ahh, crap...
http://www.sendspace.com/file/obtx2w
Download that file, put it in the \tools\files\ directory, then try again and let me know.
I think I got delete-happy removing some temp files and deleted flash_image by accident.
Worked great
I just went through the install.bat file and everything worked 100% just as promised. I have not installed any of the extras yet. Thanks for the great work!
flash_image was it worked a treat its in amon_ra now was trying manually and came across it missing, went to post it and you had just now
One suggestion before letting adb copy the 2.1 rooted img to the phone have it delete the PB so users dont accidently click on it. Just a lil cleanup to help things out. So far its flashing 2.1 rooted I will let you know about the first error, ill go back through it again and get it to recreate.
FIRST: I know that there are custom ROMs and this has been done via root/etc. I want as vanilla of a gtab as possble (i've tried the TnT Enhancement pack and I have all sorts of issues w/ viewing mp4 files and the device locking up 'Scanning the SD card' that I don't have w/ the OTA updates)
I'm trying to create a custom update.zip that will JUST install the gapps on my gtab. I've got the necessary files from a previous thread: http://forum.xda-developers.com/showthread.php?t=827209
I've created a directory struction w/ update\system (with the files in the gapps zip from the thread) and update\META-INF\com\google\android with an update-script that says:
show_progress 0.1 0
copy_dir PACKAGE:system SYSTEM:
show_progress 0.1 10
I zip it up and sign it:
java -classpath testsign.jar testsign my1stupdate.zip update.zip
then I go to install it, have the \recovery with the command file that says "--update_package=SDCARD2:/update.zip" and it looks like it's installing it fine (get the standard square status screen with the install package icon looking like its going to install) until within a second or two I get the triangle with the exclaimation point in the middle and it reboots (package never gets installed)
what am I missing? anyone provide some insight into how I can figure out what happened to troubleshoot further?
Thanks in advance.
-Deniz
Do you mean something like this which is only the Google apps? No sense in reinventing the wheel.
http://android.d3xt3r01.tk/cyanogen/gapps/gapps-mdpi-tegra-20101020-signed.zip
tullywork;11012789
I'm trying to create a custom update.zip that will JUST install the gapps on my gtab. I've got the necessary files from a previous thread: [url said:
http://forum.xda-developers.com/showthread.php?t=827209[/url]
Click to expand...
Click to collapse
not sure why you are reading an old/closed thread when that thread actually directs you to the currently stickied thread:
http://forum.xda-developers.com/showthread.php?p=9257637
tullywork said:
FIRST: I know that there are custom ROMs and this has been done via root/etc. I want as vanilla of a gtab as possble (i've tried the TnT Enhancement pack and I have all sorts of issues w/ viewing mp4 files and the device locking up 'Scanning the SD card' that I don't have w/ the OTA updates)
I'm trying to create a custom update.zip that will JUST install the gapps on my gtab. I've got the necessary files from a previous thread: http://forum.xda-developers.com/showthread.php?t=827209
I've created a directory struction w/ update\system (with the files in the gapps zip from the thread) and update\META-INF\com\google\android with an update-script that says:
show_progress 0.1 0
copy_dir PACKAGE:system SYSTEM:
show_progress 0.1 10
I zip it up and sign it:
java -classpath testsign.jar testsign my1stupdate.zip update.zip
then I go to install it, have the \recovery with the command file that says "--update_package=SDCARD2:/update.zip" and it looks like it's installing it fine (get the standard square status screen with the install package icon looking like its going to install) until within a second or two I get the triangle with the exclaimation point in the middle and it reboots (package never gets installed)
what am I missing? anyone provide some insight into how I can figure out what happened to troubleshoot further?
Thanks in advance.
-Deniz
Click to expand...
Click to collapse
so what you want is a stock rooted rom with gapps? I wanted the same exact thing, if this is what you wanted let me know and I will let you know how i did it
1st: thanks for the replies.
I looked at the CyanogenMod update.zip and it has 33 different apks that get installed, which again, I don't want all the 'garbage' just gapps (they've got twitter, facebook, carhome, htc email/etc, passion quickoffice...etc..etc).
I've rooted it successfully and installed GApps, so I know how to get it to work successfully....i was just hoping for something easier (eg. load the update.zip on boot after doing a clean NVFlash and all the gapps stuff was there).
I was also hoping to learn a bit more about building my own update.zip and curious what I did wrong (i got pretty far along before it choked), obviously there are probably easier wasy to get this done other than building an update.zip, the learning is half the fun right?!
Thanks again for your replies/help.
-D
I do not have a gtab but a advent vega and believe they are similar.
I made a update.zip from the market_update.zip. Just added the apps i wanted to system/app folder in the zip file, and flash from the software update tool. Not sure if my edited one will work on the gtab because it has the advent vega framework to give a small taskbar.
Original thread: http://forum.xda-developers.com/showthread.php?t=931337
I have posted the original unedited one, hope it helps you out
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 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/
Overview:
This thread is a guide on how to fix the apply_patch_check error message experienced during an upgrade of the Android OS. Specifically, this will detail the steps for an upgrade of Jelly Bean from 4.1.1 to 4.1.2 on the Nexus 7 with CWM Recovery for a user of Windows. I'm sure similar steps will work for other recoveries/upgrades/devices and PC OSes.
You should only bother with this if you don't want to flash the entire system.img file to your phone, which is way easier.
Here is an example of the error message I'm talking about:
Code:
assert failed: apply_patch_check("/system/app/Chrome.apk", "819b34b66335c6faec86404d736a002b8871600", "9d6b55e63b0bf20bea433fb1ee7089f88ab73fb6")
E: Error in /sdcard/03a4eaf95f73.signed-nakasi-JZO54K-from-JRO03D.03a4eaf9.zip
(Status 7)
Installation aborted.
A few notes about the error:
This doesn't have to happen with the Chrome.apk specifically -- it could happen with any app in /system/app or .so in /system/lib.
Those random strings of numbers/letters are SHA-1 hashes of the apk.
The first one is the hash of the apk installed on your device. In my example, this happens to be the version of Chrome that comes with JB 4.1.2.
The second one is the expected hash of the apk that comes with JB 4.1.1.
Cause of the problem:
The reason this error occurs is because the file was somehow modified from its original state. In my case -- and most likely your case -- this was done by Titanium Backup. TB has an option to "Integrate updates of system apps into ROM", which will cause the apk in /system/app (and associated library files in /system/lib, if needed) to be overwritten with the updated apk.
Solution:
Download this zip file which contains the full /system/app and /system/lib directory from the JB 4.1.1 factory image. *
Extract the zip to a location of your choosing on your PC.
In the extracted folder, locate the .apk or .so file referenced in the error message on your device.
Copy this file to your device via your preferred method (USB cable works fine). I put my file in /sdcard/Download.
On your device, use a root file explorer to move the file from /sdcard/Download to /system/app (or /system/lib).
If you don't have a program that can do this, I use ES File Explorer. Be sure to go to Settings > Root Settings and turn on Root Explorer, Up to Root, and Mount File System.
Reboot into your Recovery and try to install the update again.
Repeat steps 3-6 for each subsequent file that produces an error. You will basically need to do this for each app you integrated using TB and maybe a few library files, too. **
* Future updates (above 4.1.2):
Since I won't be keeping the zip file from step #1 up-to-date, here's how to get the directories that I included in the zip for yourself:
Obtain a factory image for your device's current Android version (the version you're updating from).
For JB 4.1.1, this file is called nakasi-jro03d-factory-e102ba72.tgz.
If you're reading this guide at a later date, the JB 4.1.2 file is called nakasi-jzo54k-factory-973f190e.tgz.
You can try your luck at the official Google site, but they seem to only provide the version you're trying to update to, not from.
Extract the .tgz file somewhere on your PC.
Locate the image-naksi-jro03d.zip file and extract that, as well.
In the folder you just extracted from the previous step, located the system.img file.
Download and use a program called sgs2toext4 (View attachment 645320) to convert the system.img to system.ext4.img. ***
Download and use a program called Linux Reader to open system.ext4.img.
Do this by going to Drives > Mount Image > Next > select your file.
It will then be listed under the Hard Disk Drives section in red as "Linux Ext Volume 1".
Navigate to: Linux Ext Volume 1/system.
Right-click on the app (or lib) directory and pick Save > Next > Output to dir of your choice.
You now have the directories that were included with the zip file from Solution step #1, so just follow those steps now.
** How to avoid repeating steps:
If you'd rather not have to try to reinstall after updating only one file, just to find another file that needs updating, try this:
Obtain the /system/app and /system/lib folders from the factory image and save them to your PC.
For the sake of this guide, let's say you save them to C:\factory_app and C:\factory_lib.
Copy the /system/app and /system/lib directories from your phone to your PC.
For the sake of this guide, let's say you saved them to C:\phone_app and C:\phone_lib.
Download the File Checksum Integrity Verifier utility from Microsoft.
Start > Run > cmd
fciv.exe -sha1 -xml factory_app.xml -wp C:\factory_app
fciv.exe -sha1 -xml factory_app.xml -v -bp C:\phone_app
Don't ask me why, but you need to use -bp instead of -wp for the second command.
Don't forget the -v on the second command.
The output of the last command will show you the list of files that are different. These are the files you need to take from C:\factory_app and put into the /system/app directory on your phone.
Do the same for the lib directories (just replace all instances of "_app" with "_lib" in the previous commands).
Summary:
I hope that this post helped some of you who really didn't want to have to flash the system.img or wipe your device just to update. In the future, use TB to back up the original.
I wouldn't normally bother writing up a guide like this (it took almost as long to write as it did to figure out how to do this) but I couldn't find this solution anywhere even though I saw that I wasn't the only person with the problem. Sorry for not posting this guide sooner (update has been out for a while now), but the forum required me to make a bunch of useless spam posts before I could include any links in my guide and I didn't get around to making those posts right away.
*** I would like to thank balamu96m for his guide on extracting data from the system.img file and drphrozen for making the sgs2toext4 program.
Thanks for this. Will try now.
Worked great. Had to copy the apk and odex file.
Good job! It's great to see the steps for Windows users!
Just a heads up that I simply extracted the files I needed from and on my N7 using Root Explorer, without using my PC at all.
Great guide! Method worked perfectly on my Nexus 7 going from 4.1.2 to 4.2, thanks
Please... is there some other way to update the files w/o installing Java on my Windoze PeeCee? I accidentally messed up my YouTube.apk with Titanium Backup... now I can't update from 4.1.2 --> 4.2 JB.
EDIT: JavaPortable FTW... updating (fingers crossed)
EDIT: SUCCESS TY OP!
For anyone who flashed the 4.2 clock/keyboard already
Hey, for anyone who flashed the 4.2 clock and keyboard on their Nexus 7 already and need to roll back to do the 4.2 update, I used OP's method to make a flashable zip that puts the 4.1.2 clock and keyboard back.
Worked perfectly for my Nexus 7 to get me up and running. Hope it helps anyone!
cantthinkofa.com/files/RestoreClockKeyboard.zip
galaxy nexus
Hi can you post a guide for galaxy nexus? Or if it is the same, can you post the link of JB factory image for galaxy nexus? Sorry, I can't find any thread for galaxy nexus, and I don't want to complete flash the stock image since I don't want to wipe my phone.
Thanks in advance!
Nice Guide
perfect, the guide works just fine. Now finally running 4.2.
Awesome guide... Thanks... Happily running 4.2 now aften beeing stuck at libutils.so...
Sent from my Nexus 7 using xda premium
damagno said:
Hi can you post a guide for galaxy nexus? Or if it is the same, can you post the link of JB factory image for galaxy nexus? Sorry, I can't find any thread for galaxy nexus, and I don't want to complete flash the stock image since I don't want to wipe my phone.
Thanks in advance!
Click to expand...
Click to collapse
I don't have a Galazy Nexus, but I think the steps should be the same. Here is a link to the factory images: https://developers.google.com/android/nexus/images#takju . It looks like they now have links for older versions, rather than just the newest images (which is how it was when I made my guide). So that's pretty sweet.
Thanks a lot man, i succeeded to "patch" my system files to update from 4.2 to 4.2.1. I first check what files didn't correspond with fciv (9 files counting both apks and odex) and then replaced them in system/app. In fact they were the apps I previously integrated with tb (learned lesson: never do it if you want to remain stock and receive OTAs). I also noticed many not-matching files in system/lib but i didn't touch them and the update went smooth the same.
Another thing: when in the OP you say it's way easier just to reflash the system.img you mean just run from bootloader "fastboot flash system system.img" (taken from the factory image as usual) or there's some other thing to do in order to fix the system partition in the right way?
GallStones said:
Thanks a lot man, i succeeded to "patch" my system files to update from 4.2 to 4.2.1.
Click to expand...
Click to collapse
I was wondering if you could tell me how you did it? I'm searching a way to install 4.2.1 with no avail as of yet :crying:
GallStones said:
Thanks a lot man, i succeeded to "patch" my system files to update from 4.2 to 4.2.1. I first check what files didn't correspond with fciv (9 files counting both apks and odex) and then replaced them in system/app. In fact they were the apps I previously integrated with tb (learned lesson: never do it if you want to remain stock and receive OTAs). I also noticed many not-matching files in system/lib but i didn't touch them and the update went smooth the same.
Another thing: when in the OP you say it's way easier just to reflash the system.img you mean just run from bootloader "fastboot flash system system.img" (taken from the factory image as usual) or there's some other thing to do in order to fix the system partition in the right way?
Click to expand...
Click to collapse
Yes. I am having the same issue. I cannot update mine from 4.2 to 4.2.1. I wonder to know which original stock image you have used. Can you list a detail procedure?
Thank you very much.
Ric
dev/block/param
legom said:
Overview:
This thread is a guide on how to fix the apply_patch_check error message experienced during an upgrade of the Android OS. Specifically, this will detail the steps for an upgrade of Jelly Bean from 4.1.1 to 4.1.2 on the Nexus 7 with CWM Recovery for a user of Windows. I'm sure similar steps will work for other recoveries/upgrades/devices and PC OSes.
You should only bother with this if you don't want to flash the entire system.img file to your phone, which is way easier.
Here is an example of the error message I'm talking about:
Code:
assert failed: apply_patch_check("/system/app/Chrome.apk", "819b34b66335c6faec86404d736a002b8871600", "9d6b55e63b0bf20bea433fb1ee7089f88ab73fb6")
E: Error in /sdcard/03a4eaf95f73.signed-nakasi-JZO54K-from-JRO03D.03a4eaf9.zip
(Status 7)
Installation aborted.
A few notes about the error:
This doesn't have to happen with the Chrome.apk specifically -- it could happen with any app in /system/app or .so in /system/lib.
Those random strings of numbers/letters are SHA-1 hashes of the apk.
The first one is the hash of the apk installed on your device. In my example, this happens to be the version of Chrome that comes with JB 4.1.2.
The second one is the expected hash of the apk that comes with JB 4.1.1.
Cause of the problem:
The reason this error occurs is because the file was somehow modified from its original state. In my case -- and most likely your case -- this was done by Titanium Backup. TB has an option to "Integrate updates of system apps into ROM", which will cause the apk in /system/app (and associated library files in /system/lib, if needed) to be overwritten with the updated apk.
Solution:
Download this zip file which contains the full /system/app and /system/lib directory from the JB 4.1.1 factory image. *
Extract the zip to a location of your choosing on your PC.
In the extracted folder, locate the .apk or .so file referenced in the error message on your device.
Copy this file to your device via your preferred method (USB cable works fine). I put my file in /sdcard/Download.
On your device, use a root file explorer to move the file from /sdcard/Download to /system/app (or /system/lib).
If you don't have a program that can do this, I use ES File Explorer. Be sure to go to Settings > Root Settings and turn on Root Explorer, Up to Root, and Mount File System.
Reboot into your Recovery and try to install the update again.
Repeat steps 3-6 for each subsequent file that produces an error. You will basically need to do this for each app you integrated using TB and maybe a few library files, too. **
* Future updates (above 4.1.2):
Since I won't be keeping the zip file from step #1 up-to-date, here's how to get the directories that I included in the zip for yourself:
Obtain a factory image for your device's current Android version (the version you're updating from).
For JB 4.1.1, this file is called nakasi-jro03d-factory-e102ba72.tgz.
If you're reading this guide at a later date, the JB 4.1.2 file is called nakasi-jzo54k-factory-973f190e.tgz.
You can try your luck at the official Google site, but they seem to only provide the version you're trying to update to, not from.
Extract the .tgz file somewhere on your PC.
Locate the image-naksi-jro03d.zip file and extract that, as well.
In the folder you just extracted from the previous step, located the system.img file.
Download and use a program called sgs2toext4 (View attachment 645320) to convert the system.img to system.ext4.img. ***
Download and use a program called Linux Reader to open system.ext4.img.
Do this by going to Drives > Mount Image > Next > select your file.
It will then be listed under the Hard Disk Drives section in red as "Linux Ext Volume 1".
Navigate to: Linux Ext Volume 1/system.
Right-click on the app (or lib) directory and pick Save > Next > Output to dir of your choice.
You now have the directories that were included with the zip file from Solution step #1, so just follow those steps now.
** How to avoid repeating steps:
If you'd rather not have to try to reinstall after updating only one file, just to find another file that needs updating, try this:
Obtain the /system/app and /system/lib folders from the factory image and save them to your PC.
For the sake of this guide, let's say you save them to C:\factory_app and C:\factory_lib.
Copy the /system/app and /system/lib directories from your phone to your PC.
For the sake of this guide, let's say you saved them to C:\phone_app and C:\phone_lib.
Download the File Checksum Integrity Verifier utility from Microsoft.
Start > Run > cmd
fciv.exe -sha1 -xml factory_app.xml -wp C:\factory_app
fciv.exe -sha1 -xml factory_app.xml -v -bp C:\phone_app
Don't ask me why, but you need to use -bp instead of -wp for the second command.
Don't forget the -v on the second command.
The output of the last command will show you the list of files that are different. These are the files you need to take from C:\factory_app and put into the /system/app directory on your phone.
Do the same for the lib directories (just replace all instances of "_app" with "_lib" in the previous commands).
Summary:
I hope that this post helped some of you who really didn't want to have to flash the system.img or wipe your device just to update. In the future, use TB to back up the original.
I wouldn't normally bother writing up a guide like this (it took almost as long to write as it did to figure out how to do this) but I couldn't find this solution anywhere even though I saw that I wasn't the only person with the problem. Sorry for not posting this guide sooner (update has been out for a while now), but the forum required me to make a bunch of useless spam posts before I could include any links in my guide and I didn't get around to making those posts right away.
*** I would like to thank balamu96m for his guide on extracting data from the system.img file and drphrozen for making the sgs2toext4 program.
Click to expand...
Click to collapse
my error 7 was generated by emmc: dev/block/mmdblk0p7 (the file is "param" any suggestions?
Thanks. After searching for a lot of time, this post helped me updating my SGS3.:victory: I previously tried to integrate youtube update into rom using titanium backup.
GallStones said:
Another thing: when in the OP you say it's way easier just to reflash the system.img you mean just run from bootloader "fastboot flash system system.img" (taken from the factory image as usual)
Click to expand...
Click to collapse
Yes, that's what I mean. The reason I didn't want to do this on my device is because I had modified some other system files that I wanted to keep the modifications for.
Wow, thanks a lot OP! Your guide helped me fixing an error during the update to 4.2.2 on my Nexus 4.
please include a video ,im getting lost in the details
solved.