Database Users

All I want to do is use nandroid backup.

Ive been reading post after post after post and im confused as all hell.
All I want to do is be able to take a image of my phone once I have everything setup and take new images about once a week in case the phone is ever replaced. I want to be able to get all my ringtone associations apps and app settings like the settings from my k-9 setup etc... phone settings EVERYTHING. I understand the mybackpro and sprite will not do this detailed of a backup. So thats what lead me here.
I have the sprint hero. I have already updated to the newest OTA firmware.
I would like step by step what i need to do. Here is what i think is the correct way from my searches. PLEASE CORRECT ME IF IM WRONG.
1. download ruu from http://forum.xda-developers.com/showthread.php?t=586258 insatll htc sync and run ruu and follow directions. That should bring the phone back to the stock image. Unless I can root from the new OTA firmware which I dont know. Someone lmk if I can.
2. Root the phone following this link http://forum.xda-developers.com/showthread.php?t=583291 or this link http://theunlockr.com/2009/11/18/how-to-root-your-sprint-hero-in-one-click/ or this link http://theunlockr.com/2009/11/07/how-to-root-your-cdma-htc-hero-sprint-verizon/ Which link is best to follow?
3. I setup my phone then turn off then home key power will get to the green menu with nandroid backup as a option. Run that and I have a image of EVERYTHING on my phone?
One last ? Can I ever update to the latest firmware or am I stuck with the stock firmware.
Thank you for your time.

It looks like you have answered your whole question. Yes, you have the process down to a science.
About which links to follow:
Folow the first link to root your phone. That's a thorough, easy to follow, minutes-to-root, fool-proof method. It also contains the download links and everything you need to do EXACTLY what you want.
So yeah,
1. RUU to stock
2. Root by following guide
3. Home/Power and select Make Nandroid Backup
4. (if you want) install rom like fresh .4 (most stable release) that includes the Sprint MR (maintenance release) and application tweaks etc.

Thank you for your response. Though I had it but wanted to make sure
Can I do the OTA update after I have rooted and made my backup? Will this cause any issues with the root or the backup?
also does fresh .4 use the htc sense ui? Ive come to really like that compared to my buddies droid UI.

Actually, if all you want to do is take a nandroid backup, there's no reason to root your phone at all.
Just install the latest flashrec here
Get the Amon-Ra recovery image for the Hero here
Install flashrec, run flashrec, BACKUP RECOVERY IMAGE, then apply the Amon-Ra recovery image.
Now, you can boot to recovery and do a nandroid backup.
If you want to apply the Sprint update, you must restore your backup recovery image (see above in bold) before the update will apply. Once you've rebooted a few times with the Sprint update, you can then apply the Amon-Ra recovery image again (no need to re-backup the recovery image). Reboot into recovery and you can make a nandroid backup.
While it's true that the first link you provided will indeed give you the recovery image to be able to do a nandroid backup, if that is all you want to do, there's really no reason to go through all the steps of rooting your phone (this may change in the future if flashrec stops working with an update from Sprint/HTC - we may even be forced to do a goldcard method at some point in the future if they do something like they did to the gsm Android phones).

jmanley69 said:
Actually, if all you want to do is take a nandroid backup, there's no reason to root your phone at all.
Just install the latest flashrec here
Get the Amon-Ra recovery image for the Hero here
Install flashrec, run flashrec, BACKUP RECOVERY IMAGE, then apply the Amon-Ra recovery image.
Now, you can boot to recovery and do a nandroid backup.
If you want to apply the Sprint update, you must restore your backup recovery image (see above in bold) before the update will apply. Once you've rebooted a few times with the Sprint update, you can then apply the Amon-Ra recovery image again (no need to re-backup the recovery image). Reboot into recovery and you can make a nandroid backup.
While it's true that the first link you provided will indeed give you the recovery image to be able to do a nandroid backup, if that is all you want to do, there's really no reason to go through all the steps of rooting your phone (this may change in the future if flashrec stops working with an update from Sprint/HTC - we may even be forced to do a goldcard method at some point in the future if they do something like they did to the gsm Android phones).
Click to expand...
Click to collapse
So, how do I install flashrec and "apply" the Amon-Ra recovery image? Sorry, but I just got my first Android phone this morning. LOL! And I want to explore all possibilities of what my new toy can do. But I'm not quite sure how to do either of those things.

You Can Root the New O.T.A. Update manually only.
I have a Sprint Hero and to get the OTA Update I had to get the Original RUU file and install it. Then I did the OTA update but the key thing is Amon Ra image and flashrec WILL NOT WORK.
What Does work is:
1. From the home Screen Go to Settings>Applications>Development Check your USB Debugging Mode and Stay awake boxes
(This is just getting set up to use the Android SDK. Im sorry for all the experience folks Im just going step by step for thoroughness)
2) From the Desktop Computer Get to your command prompt and Follow the steps Below:
3. Open the Command Prompt and type the following (hitting enter at the end of every line):
cd\
cd AndroidSDK\Tools\
adb devices
And make sure your phones’s serial number pops up (if not redo section I).
4. Then type:
adb push asroot2 /data/local/
adb shell chmod 0755 /data/local/asroot2
adb shell
/data/local/asroot2 /system/bin/sh
5. Then type:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
cd /system/bin
cat sh > su
chmod 4775 su
Thats It..After you get the message "ENJOY THE SHELL and get the # sign, IF YOU ENTER EVERYTHING CORRECTLY EXACTLY WHAT YOU TYPED WELL SHOWS UP BELOW WHERE YOU TYPED IT!!)
ROOT USER Programs seem to work but the (PowerButton/ Home Button pressing combination still hangs at "HTC") which is where somehow the Green menu screen is supposed to be. And the NANDROID Backup is supposed to be. If anyone knows how to get this to work or to prevent the Hero from hanging please let us know.

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.

UK CWR Backup needed Desperately (Any Version)

Hi, My UK tablet is stuck on a testing update that was on the FTP and now I cannot update my tablet. My Tablet is stuck on ThinkPadTablet_A310_02_0039_0080_UK_testing but the ThinkPadTablet_A310_02_0039_0086_UK patch only works from 02_0037_0075_UK
My only hope is that I can load on a CWR backup of someones stock tablet from any version. Then I could proceed with standard updates.
Any one who rooted their tablet and had a Nandroid / Clockwork Recovery from a UK tablet and could get that to me would be amazing.
Thanks Steven Richardson

I'm copying my backup now from my sdcard. Will zip it and upload for you in a couple of hours. Its a stock 86 UK backup. Hope that's what you need.

Thats amazing thank you so very much! Cannot wait!

Sorry for the delay. Couldn't find a decent place to upload the file. Haven't used Google drive before but had to upload there as even my dropbox couldn't take it. The file is in a self-extracting archive, just run it and copy the folder "stock.ota2.clean" to your clockworkmod/backup/ folder in your external SD card.
https://docs.google.com/open?id=0B9_U8cZCMA1NS0FHRXRHUTFfWjg
Edit: The file is 401mb.
Edit 2: Finally managed to get it on dropbox. Link: https://www.dropbox.com/s/ohbf1odrvsfzamb/Stock.ota2.Clean.exe
If you don't trust the .exe archive, scan for viruses before running it.

Thanks ever so much. It works great. Have given you Thanks on the forum as well.

I installed your backup. Now i'm not able to update anymore. (Like before )
Does anyone know why?

I just uploaded a clean backup, I dont know if you can update or not. Lenovo always find a way to mess up updates so I haven't tried to update, waiting for positive news from others.

I used it an now am sitting pretty on Ice Cream Sandwich!
Had to install 87 and 89 first
I then rooted it and put in CWR and then updated to ICS and kept root!
Once again thanks

Unfortunately it is not an update to ICS is possible.
Error message every time "failed to verify whole-file signature"
It is probably better to wait for a finished backup of ICS.
I think you must CWM Uninstall before an update is possible.

You can install all of the updates. To get 87 on you have to modify the update-script file inside the update and remove the Indigo assert lines. Then use CWR to install the update.
When i installed 87 it over wrote CWR with the stock android revocery so you could continue on from there with stock recovery.
I used stock recovery to install 89 then I re-rooted and put CWR back on so I could fix the busybox error that comes with the ICS update.
I got mine fully working with root and CWR (although havent check CWR since ICS come to think about it)
Steven
EDIT: just checked ICS update puts stock recovery on.

Just got ICS working with this backup
Sent from my ThinkPad Tablet using XDA

folkommen said:
Just got ICS working with this backup
Click to expand...
Click to collapse
Can you post a short tutorial, how did you proceed?
Did you have Root on ICS?

I lost root during the update. Even the OTA Root keeper wasn't able to restore it.
But then I have to try rooting it myself.
Short instruction to get ICS with this backup:
1. Restore the backup with cwr
2. Modify the updater-script in the 0087_UK update
2.1 open updater-script (/META-INF/com/ google/android/updater-script)
2.2 delete the lines 4 and 5
3. install the 0087_UK update using cwr (install zip from SD)
(This is going to overwrite the cwr)
4. Use the normal ota updates (in the settings)
5. Finished

Thats it.
My TPT has now ICS.
Thanks for help.

I'm happy for you guys that have updated to ICS but some people (me for example) still have reservations about updating to ICS. I'd be grateful if you guys could post some feedback about ICS on this thread:http://forum.xda-developers.com/showthread.php?p=26792555#post26792555
It would also help others as well

Clockworkmod not working after ICS update (was not overwritten during update)

I'm not allowed to post in the Development forum, so I will ask my question here:
I updated to ICS successfully by changing the update-script in the update.zip.
I removed the lines which delete the recovery or reinstall it; I deleted the whole recovery folder as well.
But now I can't get back into CWM, it just doesn't start, it stops during "booting into recovery kernel" ( it was not overwritten).
So, is the ICS update changing so much in the system that CWM stops working? (through google I found something about different kernels, but didn't understand it)
I think I'll try to install the original recovery, better than nothing.
(this may also be a warning to people who think that they can roll back to honeycomb with CMW - apparently, once the update was succesfull that's it with honycomb)
daniel

I think it might have to do with the updated bootloader that comes with the ICS OTA.
I just had a look at the "blob"-file in the update.zip and was able to unpack it with the BlobTools for the Asus Transformer (https://github.com/AndroidRoot/BlobTools). Inside it was an EBT-file, which, according to my research, should be an image for the bootloader.
Looking through the strings in the blob, it seems to be one indeed: "Bootloader Start at:%d ms".
So I guess the new bootloader loads the recovery system from a different address or partition than the HC bootloader, which is why CWM won't start.
So adding the lines for flashing the OTA recovery-from-boot.p to the updater-script and re-running the update over HC should theoretically solve the issue. Or, if that doesn't work, flash the recovery image manually and flash the blob via nvflash (I'm not sure, though, if that is possible without the keys).
Maybe then someone with enough reverse-engineering skills could determine what has changed in the update and patch CWM accordingly...

Similar Issue..
In CWM, from [ROM][JB] CM10 for Ideapad K1 [Updated 8/29] (I'm running version 2). Whenever I attempt to use any of the features it asks me to install the recovery (which I know I have, and can boot to it) and asks me to choose my device.. Which it then only gives me the ASUS TRANSFORMER as an option.
So, on Version 1 of this build, some time back. I said, what the heck, why not. Let it do its thing,rebooted.. and the system would not ever boot. Just hung at the CM10 boot animation.
Whatever. I used the NVFlash version, got it back up and running. Rebooted in to CWR, and flashed the [ROM]CM10 for Ideapad K1 version 2 CWM version on it. Id really rather not have to wipe my device again to go to version 3, or 4.. and I don't want to get stuck at a boot animation again.
Any thoughts?

It will work again. Just find the file "k1recovery" from the system/bin folder of a rom that has it. Push it in the device, fix permissions and execute it using ADB. The combination Power Btn & VOL+ doesn't work on some devices.

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.