Database Users

GTab recovery firmware (homebrew and official Viewsonic 1.0.1 & 1.1-based versions)

GTab recovery firmware (homebrew and official Viewsonic 1.0.1 & 1.1-based versions)
TnT 1.1-3588 recovery ROM, dated 01/24 and supplied by Viewsonic / TnT. Link: http://tapntap.http.internapcdn.net/tapntap/viewsonic/update-smb_a1002-3588-user.zip
md5sum: 0f07d710728640ea1e0f4a5d6d3fa72c
TnT 1.1-3389 recovery ROM, dated 12/23 and supplied by Viewsonic / TnT. Link: http://tapntap.http.internapcdn.net/tapntap/viewsonic/update-smb_a1002-3389-user.zip
md5sum: e6c09077f67b29c42643b7ae5f10d6e2
TnT 1.1-3316 recovery ROM, dated 12/19 and supplied by Viewsonic / TnT. Link: http://tapntap.http.internapcdn.net/tapntap/update-smb_a1002-3316-user.zip
Alternate link: http://www.mediafire.com/?p9o52540baa5vfg
md5sum: 1333e22b6d802096d3c63757680777f0
TnT 1.0.1-3053 recovery ROM, dated 12/10 and supplied by Viewsonic / TnT. Link: http://tapntap.http.internapcdn.net/tapntap/update-smb_a1002-3053-user.zip
Alternate link: http://www.mediafire.com/?qy92jzoz8upy8xa
md5sum: 7b800e409b5324f2c69e7ba6f84eab97
TnT 1.0.1-2967 recovery ROM, dated 11/22 and supplied by Viewsonic / TnT. Link: http://tapntap.http.internapcdn.net/tapntap/update-smb_a1002-2967-user.zip
Alternate Link: http://www.mediafire.com/?99eb11cqhvrkkc7
md5sum: 43eb0358db25b492751b1b0a71568c51
These were grabbed from my over-the-air update. They are full recovery images that wipes everything except the user data.
NOTE: These are only for 1.0.1 or 1.1 based stock versions. For 1.2 based stock versions, they will be hosted in the same location as my 1.2-based mods./[/url]
===================================
Instructions for use with the internal memory:
1- Mount your device to your PC
2- Download the ROM you wish you use, and save it to the root of the mounted drive. Rename it to "update.zip"
3- Create a folder on your mounted drive callled "recovery".
4- In that recovery folder, create a file called "command", and add this line to that file:
Code:
--update_package=SDCARD:/update.zip
NOTE to Windows users: If you use notepad, it might name the file "command.txt". That won't work. It cannot have a file extension. I would recommend downloading and using the excellent program "notepad++" as a notepad replacement.
5- Shutdown the device and then boot into recovery (Hold Power button and volume up key for a few seconds). If you are using standard recovery, the install should run automatically. If you are using clockworkmod, you will need to manually choose the update.zip file.
6- Reboot when completed (standard recovery users will be rebooted automatically).
Other note: These stock ROMs WILL flash recovery, as they are designed to do that. If you are using clockworkmod, that recovery tool will most likely be wiped out. Also, if you experience a boot loop post-install, you won't have clockworkmod installed to correct it - there are ways to install a clockworkmod image off your microSD, if necessary, then wipe your user data. Most times, these reboot hangs are due to incompatible data partitions between mods - this is especially true for ROMs like gADAM.

This is not working for me trying to flash from clockwork
i'm getting an error
assert failed: write_raw_image("/tmp/recovery.img", "recovery")
E:Error in /sdcard/update.zip
(Status 7)
Installation Aborted
please help!

nick325i said:
This is not working for me trying to flash from clockwork
i'm getting an error
assert failed: write_raw_image("/tmp/recovery.img", "recovery")
E:Error in /sdcard/update.zip
(Status 7)
Installation Aborted
please help!
Click to expand...
Click to collapse
It's spotty with cwm - I've seen the same thing - cwm probably has an issue being overwritten, for some reason.
You might want to alter the ZIP and just rip out the line that's trying to overwrite recovery.

Had this error too
I removed this line from the updater-script file and CWM finished the install succesfully
assert(package_extract_file("recovery.img", "/tmp/recovery.img"), write_raw_image("/tmp/recovery.img", "recovery"), delete("/tmp/recovery.img"));
thanks again roebeet
should I be worried about leaving superuser on this if im returning it?

daCalifa said:
Had this error too
I removed this line from the updater-script file and CWM finished the install succesfully
assert(package_extract_file("recovery.img", "/tmp/recovery.img"), write_raw_image("/tmp/recovery.img", "recovery"), delete("/tmp/recovery.img"));
thanks again roebeet
should I be worried about leaving superuser on this if im returning it?
Click to expand...
Click to collapse
I don't think they'll catch it. Just don't leave your user data intact or anything in the internal memory!

Where can I find the "/recovers/command" file?

deleting that line from the updater-script file worked for me with clockworkmod recovery installed.. if anyone is a noob here's some instructions..
unzip the vanilla recovery rom.. go into the "update-smb_a1002-2967-user\META-INF\com\google\android" folder and edit the updater-script file. I had to use notepad++ to edit it, regular notepad wasn't showing the formatting correctly. then just delete this line "assert(package_extract_file("recovery.img", "/tmp/recovery.img"), write_raw_image("/tmp/recovery.img", "recovery"), delete("/tmp/recovery.img"));" save the file, then zip up the contents of the update-smb_a1002-2967-user folder into an update.zip and copy it to your gtablet. make sure the inside of the update.zip shows the system.img etc files in the root of the zip and that you don't zip it up so those files are one folder deep into the zip. hold down volume + while turning the gtablet on and it should load clockworkmod and let you flash the new update.zip.

Wishmaster2 said:
Where can I find the "/recovers/command" file?
Click to expand...
Click to collapse
It's not in here -- 1.0.1 is a 100% vanilla ROM from Viewsonic so I did not touch it. Viewsonic even calls it 1.0.1.
For the command file, you can grab that in the homebrew 1.0.0 version.

I've flashed my g-tab back to TnT stock dated 11/22. Question: is it possible to get it back to the PRE-updated TnT stock? -- i.e. v.1.0.0 of roebeet's homebrew firmware?
It's a very long story, but I might need to return the g-tab and I need to get it back to the absolute original shape... MANY THANKS!
EDIT: I did tried the flash 1.0.0 on top of 1.0.1 but (not too surprisingly perhaps) nothing happens. I was able to get back to 1.0.1 from TnT Lite 2.0 so I believe I used the correct method.

case-sensitive said:
I've flashed my g-tab back to TnT stock dated 11/22. Question: is it possible to get it back to the PRE-updated TnT stock? -- i.e. v.1.0.0 of roebeet's homebrew firmware?
It's a very long story, but I might need to return the g-tab and I need to get it back to the absolute original shape... MANY THANKS!
Click to expand...
Click to collapse
Tmk, Viewsonic has never supplied a 1.0.0 of their own (technically they never supplied a 1.0.1 either, but we managed to grab it). Why not return it with 1.0.1? That's what I did with my 2nd device - you'll be doing the next owner a favor.

roebeet said:
Why not return it with 1.0.1? That's what I did with my 2nd device - you'll be doing the next owner a favor.
Click to expand...
Click to collapse
(1) The sears folks actually checked! (2) 1.0.1 is less broken so I have less excuses to return it :-(
This is lame, I know...
Thanks for all your work!

I can't figure out how to remove clockworksmod after I restore the Gtab. Everything else is stock except for the recovery.

+1 on this... gotta get rid of that recovery before I take it back.
ojo8 said:
I can't figure out how to remove clockworksmod after I restore the Gtab. Everything else is stock except for the recovery.
Click to expand...
Click to collapse

Please can someone help me out with this.
ojo8 said:
I can't figure out how to remove clockworksmod after I restore the Gtab. Everything else is stock except for the recovery.
Click to expand...
Click to collapse
Sent from my PC36100 using Tapatalk

How Do I Install: Step by Step, The Recovery ROM
Hi There,
Can you explain in "steps" how to install the recovery ROM to the gTablet? or any other ROM?
I have "rooted" my gTablet, installed the "Flash", installed "Launcher Pro", installed the "Titanium-Full-Market Method" and now my gTablet powers right OFF after the gTablet screen.
Thank You

toddsworld34685 said:
Hi There,
Can you explain in "steps" how to install the recovery ROM to the gTablet? or any other ROM?
I have "rooted" my gTablet, installed the "Flash", installed "Launcher Pro", installed the "Titanium-Full-Market Method" and now my gTablet powers right OFF after the gTablet screen.
Thank You
Click to expand...
Click to collapse
The standard recovery (not clockworkmod) has two components. They can live on the internal /sdcard or on a microSD:
update.zip
/recovery/command
update.zip is pretty standard on Android, so I won't go into it - it's basically the package that actually updates the device.
/recovery/command is like a startup script - it tells recovery where the update.zip package is. This file gets erased after an update, I assume to avoid you from accidentally re-running it. It's a text file that will run /sdcard/update.zip, by default. If you need to change this to the microSD card, you need to edit the file so that "SDCARD" reads "SDCARD2", instead.

I too would like to know how or if its possible to revert from clockworkmod to the vanilla recovery?

jfholijr said:
I too would like to know how or if its possible to revert from clockworkmod to the vanilla recovery?
Click to expand...
Click to collapse
Tmk, the only way to successfully eradicate cwm is to use nvflash. I tried flash_image awhile back and could never get it to work.
This is the reason why I usually say that cwm is for the more tech folks, as it's a one way street unless you know how to use nvflash.

roebeet said:
Tmk, the only way to successfully eradicate cwm is to use nvflash. I tried flash_image awhile back and could never get it to work.
This is the reason why I usually say that cwm is for the more tech folks, as it's a one way street unless you know how to use nvflash.
Click to expand...
Click to collapse
No biggie, I baught this thing to force myself to get my hands dirty. Bumps, cuts and bruises are inevitable. Will future OTA updates work with reverting back to the vanilla rom even if stuck with CWM?

jfholijr said:
No biggie, I baught this thing to force myself to get my hands dirty. Bumps, cuts and bruises are inevitable. Will future OTA updates work with reverting back to the vanilla rom even if stuck with CWM?
Click to expand...
Click to collapse
I don't think so because you have to get to recovery to actually use it, which is cwm.

[Q] Is it possible to switch from leaked 3.1 to official 3.1?

I know that Acer pulled today's update, but will it be possible to switch when it is released again?

Leaked 3.1 to official 3.1
Yes it is, just a little confusing though. You have to know which region your tablet is from http://secure3.tx.acer.com/FindSystem/FindSystem.aspx?title=Information About Your System. And then go about flashing a couple of ROMs to get you ready for the update. Instructions here:
http://forum.xda-developers.com/showthread.php?t=1155664
I am a total noob and wasted my whole day yesterday trying to figure this out. In the end texonex helped me out. Starting with the leaked 3.1 update here's what I did (courtesy texonex):
1. Root the device (http://forum.xda-developers.com/showthread.php?t=1138228). Download Acer Recovery Installer from the market, and from there install the clockwork recovery image. Choose no for a backup of the current recovery.
2. Download the backup file for 1.104.02 here, thanks to camelot1972
dl.dropbox.com/u/34113636/2011-06-24.12.20.13.zip, I guess you could also use the file from here: http://forum.xda-developers.com/showthread.php?t=1113878. This is for the US version.
If your tablet is from another region you would have to find the appropriate "default" version number in the how-to (what firmware is right for my country).
3. Extract the contents from the zip file and put them in the backup folder for clockwork mod on your SD card (take your SD card out of the tablet and connect directly for all the steps), if you do not see the backup folder, I suppose you can make one,e.g. [micro sd]\clockworkmod\backup\2011-06-25.22.14.07. I guess this exact string will still show up in clockwork recovery. I made a backup of the leaked 3.1 and that gave me the folder, and I just replaced the files. The date part is obvious in the name however I wouldn't venture a guess what are the other digits in the folder name.
If you downloaded the file from [OTA] Full Package and Update page, you'll need first to decrypt the file using the decrypter and then extract the contents of the decrypted file. One of the extracted files is update.zip which goes on to the SD card no subfolder in this case.
4. Restore the firmware using CMW using full restore for the US version, or update from the sd card zip if using a full package zip file.
At this point I think you need to save the recovery image for the non-US versions. Follow the instructions in the how-to or just use acer recovery installer to flash the clockword recovery again and this time choose yes to backup the current image.
5. Download 1.104.02 to 1.141.07 update and flash it with CMW.
Or the appropriate latest update file from your region(highest version number).
6. Flash recovery image to 1.141.07, this is option 4 in Acer recovery installer.
For non-us versions restore the recovery image, unroot and restore factory defaults.
7. I stopped here and now am waiting for the OTA. According to the how-to, you roll back to the full defualt package by using the standard ACER recovery (Power + -Vol) after copying the zip file on to the SD card, delete the zip file copied before.
8. Go to settings and trigger update manually. OTA will prompt you the new 3.1 update. I suppose you do not need to unroot.
You can also install the stock ROM from here:
http://forum.xda-developers.com/showthread.php?t=1159443
Thanks to Bec07 (how-to), vache (stock roms) and sc2k (un-rooting) for their contributions or I would have been totally lost in trying to downgrade my tablet from the leaked 3.1. Hope this is helpful, and goes smoothly because if it does not I wouldn't have clue how to fix it.

Sorry for this off-topic post, but you said that acer pulled the update: And I still have it (haven't updated and cant anyway). Is this not right?

What I meant was its not being pushed to more users for now.

Update to 2.3.6 and keep root

If you haven't already done so, install Rom Manager and flash Clockworkmod Recovery. It doesn't replace the actual recovery partition or the files that restore it so it won't affect flashing the update.
If you received an OTA notice don't flash it. You can go into /system/cache and copy it, or download it from the links in other threads. Place the update zip (no need to rename it) on the root of your sd card.
To install the update you must be fully stock (root is okay). That means any changed or deleted system files (including bootanimation.zip) will prevent the update from flashing. You will get a status 7 error. If you used Bloat Freezer you must defrost all before flashing the zip or it will error.
Also, have available whatever zip you used to root your Nexus one (i.e., su.zip or superboot, etc.) and put on the root of your sd card.
Once your system is back to stock reboot into CWM recovery and select flash zip from sd card. Then flash the 2.3.6 update file. Then DO NOT reboot yet. Now flash your root zip. After you have flashed both the udpate and the root zip you can reboot your phone. No need to wipe anything.
When your phone reboots you will have 2.3.6 and it will still be rooted. No bootloader gymnastics necessary.

I am using stock (almost) version of GRJ22 , but unfortunatelly I got the status 7 error when I tried to apply the update via clockworkmod recovery. I guess that's because I have already integrated some system apps into ROM using Titanium Backup.
So, if I flash stock vanilla GRJ22, then SU, then GRK39F (the incremental update) and finally SU again, won't that do the job??
Thanks..

Nikos_s3 said:
I am using stock (almost) version of GRJ22 , but unfortunatelly I got the status 7 error when I tried to apply the update via clockworkmod recovery. I guess that's because I have already integrated some system apps into ROM using Titanium Backup.
So, if I flash stock vanilla GRJ22, then SU, then GRK39F (the incremental update) and finally SU again, won't that do the job??
Thanks..
Click to expand...
Click to collapse
Yes, that will do nicely. Just need to get back to GRJ22 stock before you can flash the udpate. The updater-script does an assert and checks the md5 checksum of every system file before it allows the update to flash. If it doesn't find all stock files or checksums don't match what it is looking for, you get a status 7 error and the line above will show which file it stopped on. So you can look at those messages and keep restoring files it wants (if only a few) without having to flash completely back to stock.

I guess that would take much time, as almost all of my google apps are integrated into ROM...so I will try to follow the procedure I wrote earlier and if that won't work, I will try a ready stock,rooted ROM (Fireb33 has done it already)..
thanks mate..

Why so complicated?
You can update to 2.3.6 AND keep root even much more simple:
1.) Update from OTA to 2.3.6 (and loose root).
2.) Flash Superboot from Madaco and get back root.
Done in 3 minutes.. No need to flash, recover, overwrite and/or whatever, no need for ADB, no messing:
Code:
https://bexton.net/2011/09/24/root-access-for-nexus-one-on-android-2-3-6-grk39f-superboot/

Bexton said:
You can update to 2.3.6 AND keep root even much more simple:
1.) Update from OTA to 2.3.6 (and loose root).
2.) Flash Superboot from Madaco and get back root.
Done in 3 minutes.. No need to flash, recover, overwrite and/or whatever, no need for ADB, no messing:
Code:
https://bexton.net/2011/09/24/root-access-for-nexus-one-on-android-2-3-6-grk39f-superboot/
Click to expand...
Click to collapse
That's only for those who have the bootloader unlocked?

_raz_ said:
That's only for those who have the bootloader unlocked?
Click to expand...
Click to collapse
Well, yep. That method indicates your (phones) bootloader is unlocked. But as it's the N1, unlocking the bootloader is just 19 (up to 25) characters away -> "fastboot(-linux) oem unlock".
Edit: By the way, i looked up that post from an android platform engineer:
Code:
groups.google.com/group/android-platform/msg/b7d83992dd92accb?dmode=source
The N1 is just made for that.

tried superboot but wifi down
I flashed the update for 2.3.6 and then superboot but my wifi gives an error when I try to turn it on.

New Superboot file for GRK39F?
Is there a new Superboot file for the new OTA update?

jboxer said:
If you haven't already done so, install Rom Manager and flash Clockworkmod Recovery. It doesn't replace the actual recovery partition or the files that restore it so it won't affect flashing the update.
If you received an OTA notice don't flash it. You can go into /system/cache and copy it, or download it from the links in other threads. Place the update zip (no need to rename it) on the root of your sd card.
To install the update you must be fully stock (root is okay). That means any changed or deleted system files (including bootanimation.zip) will prevent the update from flashing. You will get a status 7 error. If you used Bloat Freezer you must defrost all before flashing the zip or it will error.
Also, have available whatever zip you used to root your Nexus one (i.e., su.zip or superboot, etc.) and put on the root of your sd card.
Once your system is back to stock reboot into CWM recovery and select flash zip from sd card. Then flash the 2.3.6 update file. Then DO NOT reboot yet. Now flash your root zip. After you have flashed both the udpate and the root zip you can reboot your phone. No need to wipe anything.
When your phone reboots you will have 2.3.6 and it will still be rooted. No bootloader gymnastics necessary.
Click to expand...
Click to collapse
I want to update to gingerbread and looking for the proper guidance going forward. I've done some looking around the forums but i'm still unclear if i need to unroot or install a stock build, etc. What i know is the phone is rooted and sim unlocked. How can i check to see if the bootloader is open/locked?
Current specs:
android version 2.2.1
Baseband 32.41.00.32U_5.08.00.04
Kernal Version 2.6.35.9-cyanogenmod
Mod Version: Cyanogenmod-6.1.1-N1
Build: FRG83D
edit:
Please treat me like an idiot and walk me through this process. It's be utterly frustrating and I'm a stone's throw away from busting out my Nokia 3390 (equipped with led disco keypad).

If your bootloader is unlocked you will see an unlocked padlock on the boot up screen...

Useful Files if You are Having Problems Updating to ICS

A lot of people seem to have the same broken files so I figured I would post a few here. These are all from a US 32GB TpT on OTA2.5 but should work for any US TpT:
Original generic.kl
Original wpa_supplicant
Original gps.conf
Original busybox
My US OTA2 clean nandroid backup (not completely clean, you will need to replace Generic.kl and wpa_supplicant with the files provided above) If you are totally screwed up you can restore this in CWR, replace the two files mentioned, and then proceed to update normally (OTA2.5 then ICS). For US Tablets only!!!
A bunch of system files (I think this was copied when I was still on OTA1 but maybe some files will still be useful if they weren't patched).
The update.zip I flashed to restore stock recovery before updating to ICS. Use at your own risk, it has only been tested once by me. This should not be necessary but may help if you are getting the indigo failure message as I got that message in CWR but not with stock recovery.
Don't change any system files in ICS until someone gets CWR working: if you break your system without CWR you're gonna have a bad time.

I think you should mention which location each file is located at.

bigsnack said:
I think you should mention which location each file is located at.
Click to expand...
Click to collapse
I agree. I need to try this method but need help with the locations of the files that need to be streamlined into the nandroid backup provided.
Hope someone could help out.
Update:
1. Replace generic.kl @ this location: /system/usr/keylayout/
2. Replace wpa_supplicant @ this location: /system/bin/

Getting some MD5 mismatch when I try to restore your backup x.x

yahoowizard said:
Getting some MD5 mismatch when I try to restore your backup x.x
Click to expand...
Click to collapse
Redownload the file. I restored from the nandroid backup posted without MD5 chechsum error. Sometimes files get corrupt while downloading.

Blanco954 said:
Redownload the file. I restored from the nandroid backup posted without MD5 chechsum error. Sometimes files get corrupt while downloading.
Click to expand...
Click to collapse
Nope, happening again x.x

yahoowizard said:
Nope, happening again x.x
Click to expand...
Click to collapse
I've seen this happen before on different Android phones I owned that had CWR installed. I could not restore my backup due to MD5 checksum mismatch. It might be attributed to the version of CWR you have and the version used to create it.
What exactly is happening in your case? I didn't necessarily had to load this restore, the only problem with my upgrade was the "Indigo" error. I went thus route cause I was anxious and didn't research my problem. Need to practice some more self control before I hose my TPT. Maybe we can pitch in and help you figure something out.
Sent from my DROID RAZR using xda premium

E: failed to verify whole-file signature
E: signature verification failed
Then it aborts. It's not as specific as busybox or Indigo or any of the other errors people have been getting, so not sure what I'm supposed to be fixing.

yahoowizard said:
E: failed to verify whole-file signature
E: signature verification failed
Then it aborts. It's not as specific as busybox or Indigo or any of the other errors people have been getting, so not sure what I'm supposed to be fixing.
Click to expand...
Click to collapse
I assume your attempting to install the OTA that was downloaded to the tablet. I am not an expert but this error your getting is due to not having the stock recovery installed. There's a post on this forum where you can download the Lenovo ICS update files. Make sure you are stock with bloat. Download that pair of files and place them on the root of your SD card.. If you made a nandroid backup of stock OS when you rooted your tablet restore that backup. Temp unroot with OTA rootkeeper. Reboot to recovery and choose to install the update from SD card via CWR. Make sure its the large file first. You might get an assert check error "Indigo" if so you will need to restore the stock recovery using the file GodfatherIP linked in OP. Once you have restored stock recovery the update should install without a problem and you can enjoy ICS on TPT. It is way better than broken GB.
Sent from my DROID RAZR using xda premium

jhankinson said:
A lot of people seem to have the same broken files so I figured I would post a few here. These are all from a US 32GB TpT on OTA2.5 but should work for any US TpT:
Original generic.kl
Original wpa_supplicant
Original gps.conf
Original busybox
My US OTA2 clean nandroid backup (not completely clean, you will need to replace Generic.kl and wpa_supplicant with the files provided above) If you are totally screwed up you can restore this in CWR, replace the two files mentioned, and then proceed to update normally (OTA2.5 then ICS). For US Tablets only!!!
A bunch of system files (I think this was copied when I was still on OTA1 but maybe some files will still be useful if they weren't patched).
The update.zip I flashed to restore stock recovery before updating to ICS. Use at your own risk, it has only been tested once by me. This should not be necessary but may help if you are getting the indigo failure message as I got that message in CWR but not with stock recovery.
Don't change any system files in ICS until someone gets CWR working: if you break your system without CWR you're gonna have a bad time.
Click to expand...
Click to collapse
i have just restored your nandroid and also put hte two files you mentioned in place (Original generic.kl and Original wpa_supplicant). i am using a 64GB USA TPT too. i plan to make an updated nandroid before i try ota 2 and then ics and if all goes well, i'll post the updated nandroid in this thread.
update1:
after doing the above, i then:
-restored the stock recovery after your nandroid, rebooted twice still on cwr recovery
-did not seem to work at first however i then reran an custom update.zip for 0089US_CWR
-did a check for updates and noticed it went to the stock recovery update
-now am updating to ics!! hopefully that will go through smoothly.
update2:
-getting busybox assert error, putting busybox file in play next. used voodoo rootkeeper to make backup to keep root on ics too. temp unrooted, trying update again. :fingers-crossed:
update3:
ICS!!!!!!!!!!!!!!!!!! i'll post nandroid later today and can confirm these files combined w/a cwr update to 0089 got me out of my failed update funk. thanks again all!
My Contribution/Files:
note: i have a 64GB USA TPT (1839-27U). was running CWR and was rooted.
-USA, OTA2 Nandroid w/Original generic.kl and Original wpa_supplicant in place. You will still need to add back the busybox file after you update to 0089
nandroid zip
-0089 CWR update zip (not made by me, found somewhere on xda)
cwr update zip

seamonkey420 said:
i have just restored your nandroid and also put hte two files you mentioned in place (Original generic.kl and Original wpa_supplicant). i am using a 64GB USA TPT too. i plan to make an updated nandroid before i try ota 2 and then ics and if all goes well, i'll post the updated nandroid in this thread.
update1:
after doing the above, i then:
-restored the stock recovery after your nandroid, rebooted twice still on cwr recovery
-did not seem to work at first however i then reran an custom update.zip for 0089US_CWR
-did a check for updates and noticed it went to the stock recovery update
-now am updating to ics!! hopefully that will go through smoothly.
update2:
-getting busybox assert error, putting busybox file in play next. used voodoo rootkeeper to make backup to keep root on ics too. temp unrooted, trying update again. :fingers-crossed:
update3:
ICS!!!!!!!!!!!!!!!!!! i'll post nandroid later today and can confirm these files combined w/a cwr update to 0089 got me out of my failed update funk. thanks again all!
My Contribution/Files:
note: i have a 64GB USA TPT (1839-27U). was running CWR and was rooted.
-USA, OTA2 Nandroid w/Original generic.kl and Original wpa_supplicant in place. You will still need to add back the busybox file after you update to 0089
nandroid zip
-0089 CWR update zip (not made by me, found somewhere on xda)
cwr update zip
Click to expand...
Click to collapse
Excellent post. Thanks for your contribution, these files will come in handy for other members that are in a pinch.
Sent from my DROID RAZR using xda premium

seamonkey420 said:
update3:
ICS!!!!!!!!!!!!!!!!!! i'll post nandroid later today and can confirm these files combined w/a cwr update to 0089 got me out of my failed update funk. thanks again all!
My Contribution/Files:
note: i have a 64GB USA TPT (1839-27U). was running CWR and was rooted.
-USA, OTA2 Nandroid w/Original generic.kl and Original wpa_supplicant in place. You will still need to add back the busybox file after you update to 0089
nandroid zip
-0089 CWR update zip (not made by me, found somewhere on xda)
cwr update zip
Click to expand...
Click to collapse
Is there a version for 16gb US models, because I am getting MD5 mismatch.

bigsnack said:
Is there a version for 16gb US models, because I am getting MD5 mismatch.
Click to expand...
Click to collapse
i wonder if you can re-generate the MD5 checksum for the nandroid?
i'll find that post and link to it below:
http://forum.xda-developers.com/showthread.php?t=976453&page=2
For anyone who has had the Clockwork-mod Recovery MD5 mismatch! error.
Update: thanks Exca
If you have androids SDK ( ADB installed) try this easer method by Exca
This is a much easier way:
adb shell
# cd /sdcard/clockworkmod/backup/2010-06-29.20.22.53
# rm nandroid.md5
# md5sum *img > nandroid.md5
usually does the trick

This thread may save me. I'll try it and post back.

[Solved] OTA update fails on Yoga Tab 2 1050F

Hi,
i have the Yoga Tab2 1050F. The last OTA update fails to install.
I am currently on S100067_1507101258 and the update is for S100196_1511230539.
All earlier OTA's installed fine. I had my Tab rooted, but i unrooted it before installing the OTA update.
I also did a factory reset, the update still fails.
I only get an "Error" on the display with the tilted android avatar.
I saved the last OTA file, which is around 50MB large.
I also tried an update via the internal sd and the external sd card. None of these helped.
Can anyone help find the cause and help me install the latest update?
Regards
Jay

jayp57 said:
Hi,
i have the Yoga Tab2 1050F. The last OTA update fails to install.
I am currently on S100067_1507101258 and the update is for S100196_1511230539.
All earlier OTA's installed fine. I had my Tab rooted, but i unrooted it before installing the OTA update.
I also did a factory reset, the update still fails.
I only get an "Error" on the display with the tilted android avatar.
I saved the last OTA file, which is around 50MB large.
I also tried an update via the internal sd and the external sd card. None of these helped.
Can anyone help find the cause and help me install the latest update?
Regards
Jay
Click to expand...
Click to collapse
the thing is that not always the 'unroot' works for doing a system update, the unroot (have you performed the full one?) could leave behind modified binaries or maybe apps you installed have did that (for eg if you installed busybox it will leave the new binary) and the first step of the OTA update is to do a check of all the files that are going to be updated (patched) and if one of them doesn't match the sha1 checksum the update will abort (will not change anything on your tab when aborting). you can fix it by:
1. (complicated) restore the orginal files (you can check the recovery log on your cache partition to see where it failed)
2. (recommended) flash a stock rom matching your existing Android (you are on lollipop so you can use this for a stock lollipop install)
ps. factory reset doesn't save, that one just erases 'data' partition, has nothing to do with the ota (that usually updates files on the 'system' one or the 'boot/recovery/fastboot' partitions)

Thanks ionioni for your answer.
I don't want to flash a stock rom, that is not OTA. Just for security reasons. This would be my last resort.
I prefer to "repair" it. I am familiar with your tmp-root tool.
Do i have to mount something when i am in tmp-root, to search the su root files?
I think they reside in /system/lib and /system/bin.
Regards
Jay

jayp57 said:
Thanks ionioni for your answer.
I don't want to flash a stock rom, that is not OTA. Just for security reasons. This would be my last resort.
I prefer to "repair" it. I am familiar with your tmp-root tool.
Do i have to mount something when i am in tmp-root, to search the su root files?
I think they reside in /system/lib and /system/bin.
Regards
Jay
Click to expand...
Click to collapse
if you start with tmp_root it will open an early adb shell as root (regardless of whether your tab was or not rooted)
check after you shell in to see if the /cache is mounted (input a simple mount) and if it is not you need to mount it
afterwards you will need to go and do an adb pull on your recovery log (if i recall is on /cach/recovery ) and check inside to find on what did the ota failed
however this is cumbersome and even if you find on what it fails you still will have to find the original files (and after you try to OTA again it can fail many more times on other files as the OTA is aborted on the first non matching file and if there are many you will need to repeat these steps over again). i never did this, i am just saying that it could be done, but why would one waset maybe hours just so he can bring his system back to the same state it could bring in 3 minutes by flashing a stock rom? but if you want the complicated way feel free
if i were you i would just flash the stock rom in 3 minutes (that is how long it takes) and move along
what security reasons you are talking about?

I am just carefull. The images might be tampered.
But i get your point. It might get cumbersome to fix each file.
I'll try your method and flash the lollipop image.

jayp57 said:
I am just carefull. The images might be tampered.
But i get your point. It might get cumbersome to fix each file.
I'll try your method and flash the lollipop image.
Click to expand...
Click to collapse
oh, i see... i doubt they are tampered by anyone (except Lenovo of course ) the files i provide have already been used by others (and if they were to be tampered they would have failed future OTA's, the boot image is checked and it won't load if modified etc)
as a personal thought, to tamper a stock rom (to whatever purpose one would want) so that they cannot be detected by a future ota requires a level of knowledge that i think keeps us safe (i think one who is able to do such a thing would not 'waste' his time and resources on doing it to a normal/casual user like we are), so if you are able to take ota's you can safely assume that the files are the ones Lenovo put in there (not to say that Lenovo could not do funny things tho)
i wish you to become so important that one day this could be a real concern

yeah you are right.
thanks for your support. i managed to update my tablet.

Hi. I have the same problem. Did you have flash lollipop firmware again ? the ota works ?
Do you know where to get lollipop firmware for 1050F ? in all-in-one subject there is only kitkat firmware for 1050F.
Thank you.

saupiquet said:
Hi. I have the same problem. Did you have flash lollipop firmware again ? the ota works ?
Do you know where to get lollipop firmware for 1050F ? in all-in-one subject there is only kitkat firmware for 1050F.
Thank you.
Click to expand...
Click to collapse
the link is in my first reply here