Database Users

[Q] stuck at shut down screen after interrupting update

tl;dr: Interrupted update. cant do jack. tried acer tech support. failed
I grew bored with waiting the two minutes for my tablet to install the new update. so i stood up and hit the power button to put it to sleep like a boss. then i cam back later, the lock screen was unresponsive
i figured out be double tapping the pwr button i was able to unlock the tablet to see the powering down screen (see attachment). I can get to the setting menu, but evrytime i try to mess around in it, the window closes itself.
an interesting note is that the time is wrong, and the battery suddenly went from 100% to 15%
I called acer tech support, and with ther guidance...
pressed the reset button to no effect
powered on holding the pwr & vol- buttons down to get an error (see attachment). then the tablet turns off.
Ive dled some "update.zip" files i found online that are supposedly used to unbrick the tab... but i just got the same error picture(see attachment)
one other thing i tried was to hold the power and vol+ buttons. this cleared a chache, but had no other effect.
I am a noob at droid, but not to tech. i would like to avoid perma bricking, and im unsure about mailing this in. waiting is gay. I would like to restore it to factory settings w/o rooting it etc. as ive never done that before. but im not opposed to installing a CFW if it somes to that...
Im looking for ideas guys here guys. wtf is wrong with this thing?

Haha
Lmao "hit the power button to put it to sleep like a boss", funny ****.
Can't help you though sorry

ive been around he web, and have seen this exact series of symptoms happen to a handful of other guys... i haven figured out a solution yet, and it is looking more and more like ill be sending it in via warranty
my best guess at this point is i have corrupted a crucial system file. as to why i can do jack in the factorys recovery mode... idk. but then again, idk what the factorys recovery mode should look like or how it would function. youtube only shows CWR... which i dont have
if i believed i could anything reasonably withing my abilities, i would... but voiding the warranty on a long shot seems dumb.
still ANY ideas would be great

I too faced exactly the same problem today.. Dunno why this is happening... I am too worried now... Kindly post the solution as you find them...
Am sure calling tech-support is just waste of time..
Thanks in advance..

IM GOLDEN...
Ive reflashed to the original factory build. the problem was with the "update.zip" files i have been using. i guess they were corrupt.
multiupload<dot>com/WCT2FYLMQC
this is the file i used. I tried several from other guides, etc... a guy on another board told me to use this one. i put it on the root of my SD card, then held the power and vol- buttons until the loader had started. it took awhile, and it looked like it froze during the process...
DONT TOUCH IT
just let it do its thing, and it will reboot itself and run through the setup process like when it was new.

npena said:
IM GOLDEN...
Ive reflashed to the original factory build. the problem was with the "update.zip" files i have been using. i guess they were corrupt.
multiupload<dot>com/WCT2FYLMQC
this is the file i used. I tried several from other guides, etc... a guy on another board told me to use this one. i put it on the root of my SD card, then held the power and vol- buttons until the loader had started. it took awhile, and it looked like it froze during the process...
DONT TOUCH IT
just let it do its thing, and it will reboot itself and run through the setup process like when it was new.
Click to expand...
Click to collapse
How to put this file on the root folder when am not able to switchon the Tablet itself... and how reliable is this file??

stuck on same screen also!
My friend and i who both purchased this Acer Iconia tab are both having the same problem. We both received a message on the tablets to do the update. We both got stuck and have gone thru tech line and there is no remedy. She was able to return hers within the 15 day period; I on the other hand am a week over that so have to mail it to Acer for repair. I'm thinking this is more than a cooincidence and there is a problem more spread... Acer would neither verify or confirm....

buntzmehta said:
How to put this file on the root folder when am not able to switchon the Tablet itself... and how reliable is this file??
Click to expand...
Click to collapse
He said the root of his SDCARD. You can take out the sdcard and put it in a sd cardreader on a computer and copy the file to it then put it back in the tablet. The file worked for him so it might be worth trying. Just have patience while it is loading as some of these updates take a while to load and sometimes you may not see anything happening but it is. The more patches and roms you load on Android the more you'll learn to just leave it alone and let the updates finish. Its pretty rare for updates to be messed up. Its usually people getting anxious and clicking on stuff.
Good luck
Sent from my A501 using Tapatalk

still stuck on shutdown screen any updates?
Anyone had any luck with a fix? If not --sending it to Acer for warranty repair after the hurricane hits..Sure hope this isn't a wide spreasd Acer issue do to the new download. Wish I could just return the thing all together. Worked well while I had it a whole 3 weeks...... Thanks in advance for any information.

npena said:
IM GOLDEN...
Ive reflashed to the original factory build. the problem was with the "update.zip" files i have been using. i guess they were corrupt.
multiupload<dot>com/WCT2FYLMQC
this is the file i used. I tried several from other guides, etc... a guy on another board told me to use this one. i put it on the root of my SD card, then held the power and vol- buttons until the loader had started. it took awhile, and it looked like it froze during the process...
DONT TOUCH IT
just let it do its thing, and it will reboot itself and run through the setup process like when it was new.
Click to expand...
Click to collapse
Thanks a lot dear npena.. you are simply great.. i was very anxious initially to try your method as no other member here who face the same problem thanked or recommended your suggestion...
I tried it and it worked... I am really very thankful to you...
Cheers..
you are my hero indeed.. thank once again..
BuntZ

Friends, who face this problem you must try it... it just takes few mins b4 you can get your acer tab to work again beautifully without loosing any settings or installed apps... they remain intact...

Yay!
Glad you got it running again - had a similar problem when doing a ota update myself, was so worried I bricked the tab, went thru about 7 update.zip files until I found one that magically worked, letting me get back into the system and flash the correct rom for my region

hi! i have the same problem with my a500. I write a guide to solve this problem. Problem in firmware. here is the gude http://forum.xda-developers.com/showthread.php?t=1572622

[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] Xoom files doesnt change

Hello guys,
i got a serious and frustrating problem here.
A few days ago my xoom was stuck on the M screen, so I used a thread in the forum and recovered it.
It solved myh problem back then, but since I had 3.2 before this and the solution injected me with Android 3.01 my problems started to show themselves.
the first one is that
<b> Through Fastboot, RecoveryMod, ADB </b> and any other way you can Imagine to install a new ROM or even remove or create a file,
All of them show success message but when I check them out I see no changes.
i tried fastboot and Recovery to install nearly every ROM,Recovery and bootimage in this site but so far it was wild goose chase.
so I want to ask if I'm doing anything wrong or if you need any more information here, but please help me with this

wow I cant believe it, All these masterminds here and no answer to my distress signal??
Guys I am so in trouble and this is the only place I hoped to get answered.
I can provide you with more info if you need, but please dont say I'm on my own here.
all these years this forum was the last hope for me.
i know I'll get my answer here one day

You are not being very clear about what you have done,, but I'm assuming that you reinstalled the stock image that got you back to HC 3.01. Can you see if you are able to get OTA updates to get you back to at least 3.1, or 3.2 if possible?

If that's my problem forgive me please, Ive written that post in 3:00AM
for the sake of clearity I should add some info:
1. I even tried stock ROMs but you see I cant even flash them (Not from Recovery nor Fastboot) the steps seem successful : it opens the package,it installs them and it says everything was a success. But when I restart the device I see nothing has changed.
2. OTA updates are the same, they keep downloading and when the sysem reboots to recovery to install them it cant find them.
3. You dont believe it if I say even files and programs that I remove from device by my hand(Android OS) are back after the first restart.
And you see it's dark magic! everything from a file to a partition are back by one reboot. I dont know what should I call it but I havent seen anything like it on the whole Internet.
So seems like I should make a competition for the xda experts here
Can you publish it so all of them can see it?

Mohfath said:
If that's my problem forgive me please, Ive written that post in 3:00AM
for the sake of clearity I should add some info:
1. I even tried stock ROMs but you see I cant even flash them (Not from Recovery nor Fastboot) the steps seem successful : it opens the package,it installs them and it says everything was a success. But when I restart the device I see nothing has changed.
2. OTA updates are the same, they keep downloading and when the sysem reboots to recovery to install them it cant find them.
3. You dont believe it if I say even files and programs that I remove from device by my hand(Android OS) are back after the first restart.
And you see it's dark magic! everything from a file to a partition are back by one reboot. I dont know what should I call it but I havent seen anything like it on the whole Internet.
So seems like I should make a competition for the xda experts here
Can you publish it so all of them can see it?
Click to expand...
Click to collapse
Actually, I have seen someone with the same problem here on this forum, but I can't recall exactly what the solution was.
Can you describe, step by step what you are doing, what cable you are connecting to your pc with, etc?

okantomi said:
Actually, I have seen someone with the same problem here on this forum, but I can't recall exactly what the solution was.
Can you describe, step by step what you are doing, what cable you are connecting to your pc with, etc?
Click to expand...
Click to collapse
That would be relief to know this could be solvable.
I will look more too.
As for your post I must say:
1. I plug the Xoom to the PC using the included cable
2. I start the xoom and start fastboot
3. on the PC system has the drivers and completely knows it
4. I start with SDK:
I. Fastboot oem unlock (Completing onscreen instructions and reboot device)
II. Fastboot mode again I use Fastboot flash boot boot.img
III. Continuing with Recovery,System
IV. Rebooting the device anything is the same.
My ROM is unchanged by the process and keeeeeeeeps giving the damn error of System process error please submit
5. And with ClockworkrecoveryMod I have the stock ROM on my sd card.
I. I choose install zip from sd card.
II.Choose the correct zip file and start flashing.
III. Choosing Wipe Data/Factory reset will take the device into a complete hang. unless I first use the mount page to mount the System/Data
IV. I reboot the device and ..... you know nothing changed.
so thats my story.
Still hope to find something about it.

Thanks...that was helpful. But now I want to know the following:
Were you rooted before the trouble started?
What did you do to recover?
If rooted, what version of CWM recovery did you have installed? Did you do a nanadroid backup? (I guess the answer is no, because you could have just restored with that).
What recovery are you accessing when trying to flash a zip file?
If you can answer these questions I will continue to wrack my brain trying to recall where I saw that thread.
Edit: please check out this thread http://forum.xda-developers.com/showthread.php?t=1370312
Some of what I said to him may help you .

okantomi said:
Were you rooted before the trouble started?
What did you do to recover?
If rooted, what version of CWM recovery did you have installed? Did you do a nanadroid backup? (I guess the answer is no, because you could have just restored with that).
What recovery are you accessing when trying to flash a zip file?
If you can answer these questions I will continue to wrack my brain trying to recall where I saw that thread.
Edit: please check out this thread http://forum.xda-developers.com/showthread.php?t=1370312
Some of what I said to him may help you .
Click to expand...
Click to collapse
Being rooted? -> Yes, The world is more beautiful with root!
to recover -> I followed this: http://forum.xda-developers.com/showthread.php?t=1097997 Shame it was Android 3.0
I use ClockworkRecovery 3.0.0.28 and I cant upgrade it cause of ... you know
And for your help I must say you are definitely the most caring person I know...
I'm off to check the provided link now

I was thinking of something that might be a reason.
I have this tiny problem:
When I go to CWM and choose Erase userData/Factory Reset Device Hangs
Click to expand...
Click to collapse
I was thinking of may be the userdata partition is corrupted and I gotta find a way to flash it completely.
Somehow I used Fastboot utility to do this and after saying Success, Nothing changed again.
Do you know any other way to physically do this job?

Unresponsive Device

So, I had been using my A500 for the last few days with no problems. Well, yesterday, I got home from work and powered it on. The lockscreen came up, but the screen was unresponsive. I turned it off and then back on, but screen still didn't work. Then I did a hard reset, which still didn't fix the problem. I put it into recovery, then did a wipe that still didn't fix the issue. I flashed the ROM again. Then a different ROM. All it does is is boot up and go to the lock screen, but the screen does not respond.
If I can avoid it, I don't really want to go through the hassle of returning it since I got it online. Hopefully it can be fixed without having to take it back. Thanks in advance for everyone's help.

Boot back into recovery.
Wipe your 3 things,
User Data
Cache
Dalvik
Then go to Mounts
Format the same 3 (user data, cache partition and Dalvak.
And Flexrom
Then flash your rom. Try and flash a basic rooted rom. No kernels, no gapps.zip
See what happens.
If you have a file called update.zip, on your sd, I would delete it. And anything else there except for the rom.

sounds like hardware failure. Has the tablet been dropped or banged around. The connector on the digitizer could have came loose.That would mean void warranty and take it apart ..
Send it back is likely your. Best option

Thanks for the quick responses! I'm gonna try these things, hopefully I don't have to take it back.

Guess it is a massive hardware failure. I formatted everything and reset everything I could. All ROM's will flash and boot, but I since the screen does not work, I cannot get past the first screen.
I'm going to have to return it, dammit. So, with no touchscreen, does anyone know how I can remove Clockworkmod Recovery and get the tablet back to stock? I don't want to get any problems during the return. Thanks everyone.

sikkboy626 said:
Guess it is a massive software failure. I formatted everything and reset everything I could. All ROM's will flash and boot, but I since the screen does not work, I cannot get past the first screen.
I'm going to have to return it, dammit. So, with no touchscreen, does anyone know how I can remove Clockworkmod Recovery and get the tablet back to stock? I don't want to get any problems during the return. Thanks everyone.
Click to expand...
Click to collapse
Well, with no touchscreen that makes the easy way out of the question.
Vache has a page with stock roms and updates;
http://forum.xda-developers.com/showthread.php?t=1113878
Now, some people, extracted the update.zip from the update rom, copied it to sd, and booted holding vol+ and PWR. This automatically starts the update flashing.
Others have actually flashed them through CWM and were successful. You can read through the thread and see how they fared.
On a normal basis, we would install AcerRecovery and flash them through there, as that is the preferred method for the full rooms. But this is out of the question for you, as you only have CWM.
With the update.zip, it might work, might not. The update might look for a preinstalled stock rom matching the ComGen numbers. Really don't know.
(I would try the above if the following doesn't work)
Another method, is to use ADB and push a stock image to your device. I've never done this personally, but I know it can be done. Best bet, is to repost the question "how to push a stock image with adb", then explain briefly why. And post it in the Q&A forum. This should hopefully get some folks who use adb to help you out. I rarely use it.

Moscow Desire said:
Well, with no touchscreen that makes the easy way out of the question.
Vache has a page with stock roms and updates;
http://forum.xda-developers.com/showthread.php?t=1113878
Now, some people, extracted the update.zip from the update rom, copied it to sd, and booted holding vol+ and PWR. This automatically starts the update flashing.
Others have actually flashed them through CWM and were successful. You can read through the thread and see how they fared.
On a normal basis, we would install AcerRecovery and flash them through there, as that is the preferred method for the full rooms. But this is out of the question for you, as you only have CWM.
With the update.zip, it might work, might not. The update might look for a preinstalled stock rom matching the ComGen numbers. Really don't know.
(I would try the above if the following doesn't work)
Another method, is to use ADB and push a stock image to your device. I've never done this personally, but I know it can be done. Best bet, is to repost the question "how to push a stock image with adb", then explain briefly why. And post it in the Q&A forum. This should hopefully get some folks who use adb to help you out. I rarely use it.
Click to expand...
Click to collapse
Thanks for all your help. I was able to get it back to stock. The return should go fine. You're awesome and I did not forget to use the thank you button.

have you tried a USB keyboard or mouse to flash it.thou I still think its hardware.
Failure

You can use normal usb mouse with this tablet, you will get mouse pointer on the screen when you connect mouse...

erica_renee said:
have you tried a USB keyboard or mouse to flash it.thou I still think its hardware.
Failure
Click to expand...
Click to collapse
I was able to flash using the physical buttons. I got it all back to factory specs so I can return it. you were correct I believe, it does seem to be a screen hardware failure. Everything else works but the touch response.

Im very sorry for your luck.. But i do believe this is a very well built device. Someone has to get a bad one sometimes.. Boohooooooooo

erica_renee said:
Im very sorry for your luck.. But i do believe this is a very well built device. Someone has to get a bad one sometimes.. Boohooooooooo
Click to expand...
Click to collapse
Guess I had to take one for the team

[Q] Is my tablet beyond hope?

For the last two weeks, I've tried pretty much everything I can think of to get my TPT booted again. Symptoms of its current illness include:
Lots of error messages when booting into CWM recovery ("E:Can't mount /sdcard" for example)
If I attempt to boot normally, I get stuck on the Lenovo logo screen.
Randomly I'll boot into CWM recovery and get its logo on the screen, and a line of text, but no menus.
Other times I'll attempt to boot into CWM recovery, and just get a blank screen
So last night I used nvflash to put a new CWM recovery into partition 6: after which I was able to boot into CWM with no errors. (Yay) However, when I tried to reinstall CynogenMod (whose zip file was sitting on my external sd card), it hung during the installation. I rebooted anyway; this time it got as far as the CyanogenMod spinning logo and hung there. I went to bed, and seven hours later it was still spinning away.
Then I rebooted into CWM (without errors) and managed to install CM ROM this time also with no errors. However, again I can't boot. I get as far as the Lenovo logo, and if I boot into CWM recovery I have all the mount errors again.
Along the way I've erased the cache; done a factory reset, etc.
So: nvflash, new CWM recovery (but still errors), reinstalled CM ROM, but can't boot into it.
Any suggestions? Has this machine packed it in - is its hardware faulty in some way? Or is there something I could try which I haven't already?
Thanks folks - I think I've reached the limits of my fixing ability, and would be very gratefiul of some advice.
Thanks again,
Al

In CWM check to see if your /System folder is mounted with read-write privileges or only with read-only. If the former, then your bootloader may have locked itself. Also, what is your device model? If you have a have a US device then it cannot be unlocked as it has been encrypted by Lenovo...
Sent from my ThinkPad Tablet using Tapatalk

Thanks - it's not a US model (I bought it in Australia, where I live). I thought the bootloader was unlocked because I could use nvflash. When I boot into CWM recovery, I can't mount /system: if I try I get the error "Error mounting /system", along with other errors about not being able to mount or open /cache/recovery/{command, log, last_log}. And since I can't mount anything, I can't install zip files.
I can't remember the device model, although I suppose I could use nvflash to trawl through the partitions somehow. (Since I can't boot the device I can't do the usual thing of checking out the system settings.)
Anyway, at the moment it won't boot beyond the Lenovo logo, even after putting on a new CWM recovery (with nvflash - but as we see above this new recovery is still not working) and reinstalling a ROM (with CWM recovery, which I managed to do on the one occasion I could boot into CWM without mounting errors). It's a right pain, that's what it is.

amca1960 said:
Thanks - it's not a US model (I bought it in Australia, where I live). I thought the bootloader was unlocked because I could use nvflash. When I boot into CWM recovery, I can't mount /system: if I try I get the error "Error mounting /system", along with other errors about not being able to mount or open /cache/recovery/{command, log, last_log}. And since I can't mount anything, I can't install zip files.
I can't remember the device model, although I suppose I could use nvflash to trawl through the partitions somehow. (Since I can't boot the device I can't do the usual thing of checking out the system settings.)
Anyway, at the moment it won't boot beyond the Lenovo logo, even after putting on a new CWM recovery (with nvflash - but as we see above this new recovery is still not working) and reinstalling a ROM (with CWM recovery, which I managed to do on the one occasion I could boot into CWM without mounting errors). It's a right pain, that's what it is.
Click to expand...
Click to collapse
Well there may be hope yet as I understand (not sure) that only the US models shipped with a locked bootloader. My US model locked itself and after some research I eventually replaced the motherboard with one from eBay. There are threads around here regarding the bootloader that might have a few "options" for you to try. On the other hand I read on the Lenovo forums that Lenovo actually replaced motherboards (during the warranty period) due to failures which caused the nand to lock read-only. If the "options" don't work then the latter may be the case and you might want to consider my approach or just move on to a newer device. Good look...

eKeith said:
Well there may be hope yet as I understand (not sure) that only the US models shipped with a locked bootloader. My US model locked itself and after some research I eventually replaced the motherboard with one from eBay. There are threads around here regarding the bootloader that might have a few "options" for you to try. On the other hand I read on the Lenovo forums that Lenovo actually replaced motherboards (during the warranty period) due to failures which caused the nand to lock read-only. If the "options" don't work then the latter may be the case and you might want to consider my approach or just move on to a newer device. Good look...
Click to expand...
Click to collapse
I never thought of replacing the motherboard! I'm happy to try it, though, given instructions, and the correct (ROW; ie non-US) motherboard. Is it hard to do - and where can I find out how to do it? And how do I find out exactly what model I have?
Thanks for this - I'd really like to get this beastie working again.

amca1960 said:
I never thought of replacing the motherboard! I'm happy to try it, though, given instructions, and the correct (ROW; ie non-US) motherboard. Is it hard to do - and where can I find out how to do it? And how do I find out exactly what model I have?
Thanks for this - I'd really like to get this beastie working again.
Click to expand...
Click to collapse
No offense intended but you are somewhat peculiar as you are familiar with NVFlash, can determine which partitions to flash with the correct images but you don't have a record of, or can't find your device's model number? Check on your SD Card port flap (or your invoice). Then check out this page for details.
However if you decide to replace the motherboard then search eBay for "thinkpad tablet motherboard" and choose either of the 1838 or 1839 options. Any will fit and work but you probably won't get your (non-US) choice of replacement motherboard so will probably just have to get what's available.
See here for some basic dis-assembly instructions. Then just take you time and the rest will be obvious. Good luck!

Thanks for that! I tried responding earlier, but my post was blocked by the system. Anyway, I'll check for a new motherboard and have a go installing it. Do you know how I might prevent this from happening again?

amca1960 said:
Thanks for that! I tried responding earlier, but my post was blocked by the system. Anyway, I'll check for a new motherboard and have a go installing it. Do you know how I might prevent this from happening again?
Click to expand...
Click to collapse
No problem at all.
"I'm in the same boat": I replaced my motherboard with another US version about 6 weeks ago, rooted, installed CWM recovery and steady so far... "with fingers crossed"...
Let us know how it goes...