Database Users

[Q] Lost root after OTA update.

This is my situation...
I recently rooted for my Wildfire using Unrevoked3, have no installed any custom roms whatsoever.
To install the new firmware (Update 1.25.405.1) i followed a guide which involved renaming it to update.zip and used clockmodrecovery to install update.zip from the SD card.
Update was successful however i lost the root (as expected)
I tried to rerun unrevoked 3 to reroot but all it does is reboot my device and it remains unrooted.
On the HBOOT recovery menu i now get a red triangle with an exclamation mark against a black background. i do power + volume up and it says android system recovery and in yellow 'E: Cant open/cache/recovery command'
How can i reroot my phone so i can use apps such as titanium backup once again? (and yes ive tried to install busybox and i get a failed error message)
I have looked around the forums and made lots of searches some of which address this question but i am yet to find a solution which works... Im sorry if this question is redundant as i am new to this sorta thing.
Thanks.

Did you follow this guide?
Update: What I did to succesfully install the update on a rooted phone
- unplug phone from USB, let it download update (it's about 13 Mb in size)
- phone will ask to reboot -> update will fail, you will be dumped in clockworkmod
- As always, do a Nandroid backup before doing anything that might possibly render your phone unusable.
- Select update from zip/sdcard (or similar), navigate to zip in downloads folder
- the update process will start
- reboot (this can be a longer boot than usual, took 10 minutes on my phone)
- phone will notify you that the update has succeeded! If you've upgraded from your stock ROM (like I did), the phone info screen should look similar to that in the attached image.
- (reflash needed for root)
It doesn't say to rename the file though.
I'm going to do this now (im guessing youre on TM too?)

thanks for the info, i'm just about to do the same thing, after trying [ROM][04/10] WildPuzzleROM v8.0.5; until i realised there are still problems, got scared and restroed nandroid backup Couldn't get marketplace to load?
when phone reboots after downloading the update, i guess its supposed to be installed by the recovery program, but i have clockworkmod, I tried apply sdcard:update; get error back with failed to open update.zip and sig veri failed.
Not sure what to do? Will try booting normally, checking sd theres a file called 'OTA_Buzz_TMO_UK_1.25.110.1_R-1.14.110.1_R_release31o90ome6fwgje76.zip' on the sd card under download folder. will try renaming to update.zip and placing in \sdcard root folder
otherwise i'm thinking rom manager to install, but mobilism is down it seems and can't get hold of it
EDIT: Just rename the update put it in the \sdroot. Boot into recovery and install update.zip. works fine, takes ages, very scarey process.
Will try going back to puzzle when i have more time! Lets hope 1.25 don't crash as frequently!

Yes, i did follow all those instructions and it still didnt work. However i have managed to reroot my wildfire haha so problem is resolved. It was a stupid problem, after i rooted the first time, i reinstalled htc sync to sync some stuff but forgot to uninstall. After uninstalling it again i was able to reroot.
Sorry guys... very silly mistake by me.

[Q] another brick story

I have been working on this for the past few days and for the life of me cannot figure out the problem. I'll start by just laying out a sequence of events.
Bought A500 about a month ago. OTA'd to HC 3.1 4.010.13_com_gen2
Decided not to wait for OTA 3.2 and rooted with iconiabreak.
Did not do a backup (like an idiot, i know)
Flashed Taboonay 2.0 with Thor's 2.1 kernal.
Saw awesome post to get rid of cell standby by deleting phone.apk and telephony.apk....do i did that.
Realize i am an idiot and then run a Nandroid backup.
Was happy for a few weeks when i see that Vache had updated taboonay to 2.1b and decided i wanted to do that.
Downloaded the files and started to flash with CWM. Factory, cache, dalvik wipe. Run Taboonay zip.
Get stuck in bootloop at Taboonay boot screen. $#!t......
Think "it's ok, ill just do an update.zip and go back to 3.1"
Try almost all the files on Vache's full package and update thread.
I put each one on an ext sd card and throw it into recovery boot. The Android guy with gears shows up and it looks like it is going to work.
The progress bar gets about 90-95% of the way when everything just stops. Gears animation, progress, everything.
It then reboots and gets stuck in a bootloop at the android screen. Load a different update.zip and same thing happens each time.
I try to just do a normal recovery boot, but CWM isnt there anymore and i get the ! android.
Normal reboot gives me a bootloop.
So i am stuck and asking if it is the phone and telephony apks that caused everything? if that were the case, how would i be able to load them back up since im totally locked out. I havent tried adb since im out of town for a few days. Thanks for any help that anyone can lend me. Ill try to answer any questions for any information that might be needed.

bumping for great justice~
I've tried decrypting update.zip files and vice versa.
still no luck..

try the fall back to 3.0.1
Check under development section for iconia a500. You'll see a thread for going from 3.2 to 3.0.1.
As i readd about this rom, it seems it's used in difficult cases (it removes the locks created by 3.2 stock), so it could be worth giving it a try.

rorohajj said:
Check under development section for iconia a500. You'll see a thread for going from 3.2 to 3.0.1.
As i readd about this rom, it seems it's used in difficult cases (it removes the locks created by 3.2 stock), so it could be worth giving it a try.
Click to expand...
Click to collapse
Thanks for the reply.
I don't think that will be a viable option for me since i'm not able to get my UID. i've plugged my tablet into the computer and gotten the "hardware found" bubble. It prompts me to look for drivers (which i havent be able to find) and, i assume because it's in a bootloop, wont show up on the computer.
Does anyone know why the update.zip files would fail at 90%? I think that's really the thing that boggles my mind and is most frustrating.

Did you at all have your A500 connected to your computer prior to this happening? If so then you can get the UID from by way of the Windows registry. Then you should contact SC2K and get him your UID he should be able to help you get your A500 back from the dead.

jeffw111 said:
Did you at all have your A500 connected to your computer prior to this happening? If so then you can get the UID from by way of the Windows registry. Then you should contact SC2K and get him your UID he should be able to help you get your A500 back from the dead.
Click to expand...
Click to collapse
Unfortunately, no I never plugged my A500 into my computer.

quick update:
I was able to use a different computer and found something interesting.
While trying to transfer or open a decrypted update.zip file, i get an error message saying, "Please insert the last disk of the Multi-Volume set and click OK to continue". Clicking OK just brings it back and i am forced to click cancel.
Anyone have any idea what that would mean??? It doesnt happen when I open or transfer the non-decrypted file. Only the decrypted file using Thor's Acer Update Decrypter application on HC 3.1 and 3.2 files.
While loading the decrypted update.zip on the A500, it almost instantly shows the ! android guy, while the non-decrypted files go 90-95% and then reboot into bootloop.
Any help would be greatly appreciated!

first off if you can get into recovery to flash anything.You are not bricked.
Take your SD card put in a android phone format it.
Put the card in your computer.copy a full update.zip file from dev section.likes on a post by Thor.put card.back in tab and flash.
If it stall fails repeat with a different SD card.seems smaller ones do best.
Good luck.

erica_renee said:
first off if you can get into recovery to flash anything.You are not bricked.
Take your SD card put in a android phone format it.
Put the card in your computer.copy a full update.zip file from dev section.likes on a post by Thor.put card.back in tab and flash.
If it stall fails repeat with a different SD card.seems smaller ones do best.
Good luck.
Click to expand...
Click to collapse
Thanks for your reply, first off.
I'm sorry I didn't make it clear that I had done all of those things during the events of the first post EXCEPT try a different sd card.
So I went out today and bought a PNY 2GB sd card as opposed to the SanDisk 4GB i was using. I formatted it in my Atrix 4G and threw a full update.zip file in there. The first file I tried (from Vache's http://forum.xda-developers.com/showthread.php?t=1113878 thread) was Acer_A500_4.010.38_COM_GEN1 (HC 3.1). Since I was able to open the .zip without decrypting it I loaded it only the sd card. It did the same thing as before (loaded to about 90% then freeze, reboot) except this time I got a "Boot verification failed..." message in bright red letters up at the top left of the Acer screen. Since it didn't work, I loaded Acer_A500_7.006.03_COM_GEN2 (HC 3.2) onto the sd card. Again, since I was able to open the .zip file, I assumed that there was no need to decrypt it. Loaded the sd card and put the tablet into default recovery (not CWM recovery which I no longer have). The same problem keeps happening: it loads to 90%, freezes then reboots. This time, however, it went into a bootloop at the "android" screen.
I've tried decrypted versions of those files, but I always get an error message while trying to open them and when trying to flash them in default recovery, it almost instantly goes to the ! android guy since I'm assuming those files are already decrypted and decrypting them again is bad.
Hopefully if I try enough files, I'll find the one that works...
Until then, if anyone has any ideas as to what I might be doing wrong or should be doing differently, please let me know!
Thanks.

there is a thread that has instructions on going from the OTA 3.2 to downgrade. To 3.1.look for that tthread and windows software. On that thread it talks about that error your getting.
Since I have not had this issue .can't say for sure if it will help.
Good luck sorry I can not do more to hhelp
Just a dingy blonde here.

erica_renee said:
there is a thread that has instructions on going from the OTA 3.2 to downgrade. To 3.1.look for that tthread and windows software. On that thread it talks about that error your getting.
Since I have not had this issue .can't say for sure if it will help.
Good luck sorry I can not do more to hhelp
Just a dingy blonde here.
Click to expand...
Click to collapse
Thanks for your suggestion.
I was able to find my UID from an old CWM backup file and tried this method. I attempted it last night with no success. I was actually in the middle of making a reply saying how heartbroken I was and that I was basically giving up. I decided to try it one more time and made a slight adjustment from my method last night. In the UID file, I had my UID in there as 0x0blahblahblah and kept getting the incorrect UID error in the program. When I tried taking out the first 0x in the program, it gave me an incorrect format error. That is where I was messing up.
Instead of 0x0, all i needed was 0blahblahblah in the UID file.
Attempted the upgrade utility again, and viola! It worked like a champ.
So thanks again to all that helped out and offered suggestions and to all the Devs for their outstanding work. I've definitely learned a lot from this experience.

[Q] Taboonay 2.1 suddenly unable to connect to WiFi

I flashed Taboonay 2.1 to my Icona Tab A500 last night. Everything was great. I retrieved all my usual apps and previously purchased apps back down from the market, network was working fine. Turned on tab this morning and it is unable to connect to wifi. Keeps trying several times and then says the attempt has been disabled. It sees the Motorola Surfboard but can't connect. I thought I would try to re-flash since the .zip was still on my external SD. I attempted to boot into CWM but it won't come up. It just says loading image and never goes into CWM, that's it. So, I have no ability to connect by Wifi and am unable to download Acer Recovery Installer in order to re-install CWM. Apparently the CWM image is corrupt. The CWM ROM Manager Premium is still on my desktop but it can't do any sort of recovery because if I bring it up and choose "_install .zip from SDCard" it reboots into recovery mode and can't load the recovery image either. Does anyone have any ideas? Taboonay 2.1 is Android 3.2 it has the xda ad hoc wifi patch in it (which has never been quite right) in my opinion. So I found a copy of the 3.1 wpa_supplicant file and installed it into the /system/bin folder using root explorer to set the permission correctly after renaming the one installed by Taboonay to wpa_supplicant.old and re-enabled Wifi. Still it would not connect. The only difference I could see was that it no longer could see ad hoc wifi networks but still would not connect to my infrastructure wifi although it could see it. This particular wpa_supplicant file that I went back to came from Acer 3.1 stock ROM and worked perfectly under 3.1. I'm basically out of business at this point with no network and no way to flash a new ROM or restore a backup. Does anyone have any idea what to do next. Has anyone else had wifi issues with Taboonay 2.1? I did see an update 2.1b for Taboonay 2.1, but I can't get into CWM to apply it. I might as well be totally bricked. I can connect to the tablet and have full access to the 2 SD cards via Windows and a USB cable, but I can't download Acer's Installation Recovery from the market from a Windows browser. I'm sure its not the router because 3 Windows 7 SP2 Computers can connect to it and so can my wireless HP printer. Everything seems to be a Catch 22. Help! Anyone had trouble with Wifi on Taboonay? Does anyone have any ideas or how to get out of this situation? Any suggestion would be appreciated.

Hey gradyzero sorry to see the trouble buddy but the tabooney 2.1b update is made for wifi updates issues and SU perm, im currently running tabooney 2.1b and full with new market and i have no issues. As far as the recovery have you tried new THORS 1.5 cwm can you try using adb to push recovery.img to the tablet, or maybe using terminal emulator theres a new 1.5 cwm update you can try doing that. just extract recovery img to internal sd and go into thors website "google it" and follow every step except for #3
good luck buddy if not hit me up side PM ill see what i can do atleast to try to get recovery back

I don't think I had restored the terminal program back yet let me check. The apk is something I haven't tried. Thanks for the suggestion. I have thor's 1.5 update on my SD card but not quite sure what use it can be until I can get the ability to connect to boot up in recovery. I'll go to his web site and read the instructions there again, overlooking step 3. I have read them once before but didn't have this problem so I just grabbed the download and planned to update it after the Taboonay flash. Figured it would just have to be redone after the flash anyway. Thank for you idea. I should be able get an .apk onto the SD from Windows and should be able to install it. Again, thanks much buddy. I'll post back to this thread what the outcome is.

Restoration of boot image doesn't resolve the problem.
Okay Crashpsycho I download an Acer Install Recovery apk and CWM Launcher 1.0.0.0 apk. Both appeared to install correctly. Acer Install Recovery came up and I was able to choose to install CWM 1.3.4 image. However, when I reboot into recovery I still stop at "Booting recovery kernel image". So reinstalleing the CWM 1.3.4 image that the Acer Install Recovery show as an option didn't fix anything. Any ideas about why recovery might stop when loading the kernel image? When it says "the Kernel Image" is it talking about the base Linux kernel? I seem to recall reading somewhere that Taboonay replaced the Linux kernel with its own version. Is that true? I thought maybe the recovery image was corrupt but assuming the Acer Install Recovery really did reinstall the recovery CWM 1.3.4 image as it said, then something else is wrong. I did manage to get a terminal program installed so I'll try your second suggestion to force the CWM 1.5 image using adb. If Taboonay really did replace the stock Linux kernel, I have no idea how to recover from that. I'm not quit sure exactly where a recovery image goes and so I suspect that adb will ask for the destination. Maybe I'm wrong but do you know? Does adb know automatically where to install a recovery image? If the Linux kernel has to be replaced then I could get bricked if Tabtoonay won't boot up because a different Linux kernel is installed. What is your thinking about all of this? This is getting heavy. Thanks again for your help. Anyone else that has any fresh ideas is encouraged to jump in here and post to this thread. I'll post back here with the results once I try to force the CWM 1.5 image.

Installing other kernel solved issues for me, using thor kernel 3.5

installing 1.5 use terminal emu, extract the recovery.img from zip folder and place on root of sd go to thors website tegraowners and follow all steps except #3 and that will force 1.5 to tablet. have you tried installing stock recovery image using the acer recovery app

So Sector51 are you telling me you had the same issue. Where booting into recovery locked at loading kernel image? I'll try your suggestion. If it doesn't require you to be able to boot into recovery which I can't. Thanks for the tip.

Crashpsycho, I just completed the terminal method you suggested and followed all the instructions except #3 wihch was a mount, if I remember correctly. I extracted the image file from Thor's 1.5 put it on my external SD by copying it from Windows and then went through Thor's instructions step by step. Recovery boot still hangs at loading kernel image. Thor actually says to install itsmagic into /data/local directory both in his adb push and in his terminal emu methodology. There is no copy of itsmagic in his distribution and I can't find such a file on my tablet. BTW, I also tried the adb push from Windows but the recovery image is pushed to the SDCard so I assume he intents for me to then boot into recovery and to install it. So that's not going to work unless I have itsmagic. The Windows adb method also pushes itsmagic out to the /data/local folder but I can't complete that part and I think it is critical to both methods. Any idea where I get this file? Google search returns nothing except that one entry has been removed due to copyright issues. I think that it is the key to installing from the SDcard. I remember seeing that file on my rooted 3.1 but apparently Taboonay removed it. Can you enlighten me on itsmagic? What is it? Where do I get it? I have currently installed the Stock USA 1.31.06_COM_GEN1 recovery in Acer Recovery but reboot into recovery still hangs at loading kernel image.
This is another side issue but do you know if it would be possible to install the Taboonay 2.1b manually. Is it an update zip or a ROM flash? I'm beginning to think that if I could get back my Wifi back I would just forget the recovery reboot as a last resort. I'm going to investigate what is involved in the kernel update suggested by Sector51. But basically I'm not doing anything else until I can fully complete thor's 1.5 update. Man, I've spent 3 entire days trying to resolve this. I'm going bonkers. It certainly gives me a bad taste for Taboonay that probably isn't deserved because I don't see other post about this particular issue. So please educated me on itsmagic and we'll go from there. Thanks dude for all you help.

I found a copy of itsmagic here on xda. Downloaded it and completly went through the terminal emu process exactly as posted on Thoor's Website for 1.5. Everything seemed to work this time including the execution of itsmagic which spit out a nasty message to Acer something about Its Magic. Acer why did you say the bootloader is locked when it isn't? So this tells me that everything should now be good. I rebooted into recovery and this time it acted a bit different. It still said loading boot kernel but then in about 30 seconds rebooted back to Taboonay automatically. So I'm stumped. Does anyone have and new ideas? BTW, the 1.5 recovery image has a date of 29 Feb 2008. Is that right?

Finally suceeded with 1.5 Recovery, Thanks
This message is specifically addressed to Crashpsycho and Sector51. After four attempts I was finally successful at getting Thor's 1.5 recovery booted. I immediately backed up the current version of Taboonay 2.1 and then applied the 2.1b update. Everything in term of recovery is now good. One problem, the update did not fix the the WiFi problem as I am still unable to connect via WiFi. But that's a totally different issue, which I can deal with. Meantime thank to both of you for generously taking you time to help me resolve this recovery boot problem. I would still like to know what I did wrong during the original ROM flash to Taboonay 2.1 to destroy itsmagic. As well as what I did wrong in my first 4 attempts at repairing the recovery. However, I won't dwell on that as I need to proceed on with working on the WiFi issue. Thanks a million to both of you for all your help and suggestions. You are both what makes xda a truly wonderful and unique place for lovers of mobile devices. I am a programer and web developer and I hope I can contribute eventually to the growing Android mania. I personally think it will eventually dominate the table and phone market, if it already hasn't done so retail wise. I'll return to lurker stats for a while and learn more about the SDK while I try to resolve the WiFi issue. One side note, I recently flashed my HTC HD2 phone from Window mobile 6.5 to Widows mobile 7.5. That involved the flashing of 3 ROMs and then upgrading the OS. It runs beautifully and was much more complicated than what should have been a relatively simple task of upgrading to Taboonay 2.1. I'm sure I missed some small detail that caused the problem with the Icona Tab. You guys helped me greatly and I hope to be able to return the favor at some point. So I consider this issue closed and the moderator should feel free to consider it resolve. xda is power to the people.
Final Note: The adb push from Windows was the last attempt and was apparently the one that successfully fixed everything. As a certified Unix Engineer and somewhat of a Linux expert I opted to use the terminal emulator technique since I knew the commands and what they were doing, but typing in a long stream of commands is always more prone to user error. My advice to anyone else with this problem is to install the Windows Android SDK and use adb push to update as it appears the most recent version takes care of most all the permission issues and is almost fool proof. Again thanks to you guys. The Problem is resolved. Mister Moderator consider this thread closed and resolved.

great job man atleast you got the recovery to work. i cant say much for the wifi issue or what happen to recovery i would say if anything the issue must have came from the wifi ad hoc patch/change but im not fully technically skilled to say that it really was but great job hope you get it back up and going

I am enbrased to admit this but I feel it only fair since so many people attempted to help me. I've search around and apparenty no one has run into this here yet, but it needs to be posted for future reference. Most all of my boot recovery issues took place while the tablet was docked in the Acer A500 docking station. When I have trouble in recovery mode, with the image loading message just hanging up, 100% of the time removing the tablet from the docking station resoves the problem. Just thought I should pass this on. I know it is stupid that I didn't realize this before now. If you are docked, don't boot into recovery' not even with1.5 installed. I have no idea why this is true, but it is. If you have the Acer docking station DO NOT BOOT IN TO RECOVERY WHILE DOCKED!

Open up Rom Manager and click "Fix Permissions" let it do its thing then restart. That worked for me.

[Q] Help: A500 bricked?

I tried to upgrade my A500 to Ice Cream Sandwich and ended up with a non-bootable tablet. I uploaded a recovery partition and can boot into it, but every attempt to flash a new ROM after formatting doesn't correct the problem. The flash completes, but it doesn't get past the Acer prompt on startup. I see many web pages promising solutions, but I'm sort of lost here. Can anyone help?
Evan Jones

scoopjones said:
I tried to upgrade my A500 to Ice Cream Sandwich and ended up with a non-bootable tablet. I uploaded a recovery partition and can boot into it, but every attempt to flash a new ROM after formatting doesn't correct the problem. The flash completes, but it doesn't get past the Acer prompt on startup. I see many web pages promising solutions, but I'm sort of lost here. Can anyone help?
Evan Jones
Click to expand...
Click to collapse
Well Evan, this is going to depend on exactly where you were when you started, and where you are now. So a little more info from you is needed.
1. What OS were you running when you started. HC? Stock?
2. Exactly what did you install? Was it an OTA? Or a rooted ICS build?
3. You said you uploaded a recovery partition. How and what did you do?
4. When you boot, do you see text in the upper lt corner about a mod bootloader version?
Note, that if you have an ICS Bootloader, you can no longer run HC Roms in most cases. And keep in mind there are a couple different versions of custom ICS Roms. 1 for HC bootloader tabs, and 1 for ICS UL bootloader tabs.
At this point, without knowing any other info, I would probably do the NVFlash of the unlocked Ver2 ICS Bootloader & Recovery from this thread. Understand you MUST Have your UID number and follow the link to convert it. If you didn't write it down before, you should be able to get it from your Nandroid Recovery backups on your Ext SD card when you did previous recovery backups before.
http://forum.xda-developers.com/showthread.php?t=1522384
Remember, I didn't say to DO this, it's only a suggestion based on a lack of specific information. When you ask for help in this manner, it is better to provide all the information that is relevant. There are different fixes for different problems, and the more info we have, the better able to help you.

Unable to boot
Ok, I'll try to answer your questions. I'm really more familiar with Linux than Android, so I hope I understand what you're asking.
I had a rooted version of Taboonay 2.0 installed before (3.2, I think). I downloaded the Ice Cream Sandwich and tried to flash it. That's when it would no longer boot. I downloaded a recovery image (RA-ICONIA-3.16-getitnowmarketing), and that simply changes the Android system recovery menu. From there, it's possible to format and flash ROMs, but nothing will boot.
Is that close to what you were asking?

Unable to boot
Incidentally, the adb won't connect to my laptop, but I can use the ext SD card to copy files into it if necessary.

scoopjones said:
Incidentally, the adb won't connect to my laptop, but I can use the ext SD card to copy files into it if necessary.
Click to expand...
Click to collapse
you have to get adb working before you can fix anything, see my guide here start from no.3 - hopefully that will do it. sometimes the drvers get a bit screwy after goin into apx mode and require reinstalling but lets just start with the adb

Going crazy! Want ICS, haven't used tablet in long time.

Hi All,
I'm in a bit of a unique pickle. I have a Lenovo ThinkPad Tablet 1838-CTO, it is a US 32GB wifi-only tablet with all stock hardware (with disconnected keyboard folio).
I am running build number ThinkPadTablet_A310_02_0037_0075_US
It is not liking to play more than 5 minutes of a video before saying video cannot be played, video it played fine before. Tried all the standard steps, recopying, rebooting, etc etc. The device also sporadically reboots 20-30 minutes into use, sometimes. I have root, rootprotector, and I have CWR. I have not used my tablet since about a week after the first update from my current version above: my device went loopy, THEN the update failed, and I stuck it in a closet, $%^@%$*&@ed off at it for not working.
I want to either (depending on difficulty, and recommendations here) update my device to the latest Lenovo ICS *OR* Run a custom JB ROM (perhaps http://forum.xda-developers.com/showthread.php?t=1778375 though it is for ROW not US, unsure if that matters). Priority on maintaining root access, could care less about what recovery is used, etc.
OTA updates are failing since I had to get CWR , and I am not sure how to use CWR to manually patch/update.
As for the glitching and all that, I am fairly certain it has something to do with when I rooted it, I was a very early adopter of the first permaroot (I place no blame except myself for any and all issues, and muchly appreciate the efforts of others in allowing me to root my device, whether it bricks it or makes it 10x better). I just want to update my device to ICS and start using it again. I have done some searching but am finding that almost everyone is using 0089 or later with the same issue I have, trying to get back to stock bootloader. Honestly I would like to get it on Lenovo ICS, maintain root, and go from there.
I appreciate any and all advice, it's a personal device so I am fairly lenient on what I am willing to try.
Update: I would most appreciate a stock Lenovo ICS dump flashable from CWR if someone knows where to get one, again though any help at all is appreciated.
Update 2: CWM 5.5.0.4 unable to mount the SD card (/sdcard - not even sure if it is trying to mount internal or external, I have ALWAYS had nothing but issues with the external ALWAYS being write-protected no matter the position of the physical slider switch, though it always reads fine - Sandisk 32GB micro-SDHC with Sandisk MicroSD to SD adaptor), so flashing anything from CWM is a no-go. I want to take this thing and send it on a flying ride out the window, the only thing stopping me is it would probably survive just fine to spite and mock me. Sorry about being long winded, rather give you guys as much as possible info.

Is rooting the tablet all you've done? Did you remove any stock apps? I had the same problem with my TPT when I tried upgrading to ICS(from build 0089_US on wifi only 16GB)but only because I had a corrupt busybox file or something. Try going back to complete stock(NO recovery no root) and try to do an automatic OTA 2, then OTA 3. It should work.

How do I go back to stock recovery/bootloader? I rooted back when you had to swap in ClockworkMod Recovery, so my updates fail consistently when I have to reboot to apply, my guess is that the updater tries to pass calls to the lenovo bootloader that do not exist with CWR.
If there is a way to restore my bootloader then I should be all set, otherwise I think I need to find a good cooked rom

Get Some ICS
Sublime865 said:
...otherwise I think I need to find a good cooked rom
Click to expand...
Click to collapse
I posted an ICS Nandroid from a US 32GB TPT, exactly what you are looking for, here:
http://forum.xda-developers.com/showpost.php?p=28240019&postcount=14
It will return you to stock Restore, losing CWM, but you can reinstall a proper CWM for ICS afterwards. See the Development Forum for the updated CWM version that works in ICS/OTA3.
You will have root, but you must download and use OTA Rootkeeper to bring Superuser back (don't forget to download and open SuperUser from Play store).
Good luck!

pwstein said:
I posted an ICS Nandroid from a US 32GB TPT, exactly what you are looking for, here:
http://forum.xda-developers.com/showpost.php?p=28240019&postcount=14
It will return you to stock Restore, losing CWM, but you can reinstall a proper CWM for ICS afterwards. See the Development Forum for the updated CWM version that works in ICS/OTA3.
You will have root, but you must download and use OTA Rootkeeper to bring Superuser back (don't forget to download and open SuperUser from Play store).
Good luck!
Click to expand...
Click to collapse
Going to try it tonight/tomorrow. Updating my Vivid to a non-corrupt CWR then flashing HolICS 1.3 from 0.9b tonight. Oh the adventures I get myself into... XD
Thanks for the upload, I'll let you know if(when) it works, either way I appreciate the effort!