"Bricked" A100

[kemonine96]

It appears my A100 decided that it wanted to nearly 100% brick itself last night.

I'm stuck with only recovery at the moment and it is reporting that /dev/block/mmcblk0p4 and /dev/block/mmcblk0p8 are not found. I've tried plugging it into usb while in recovery to see about using ADB shell to recover the partitions but I cannot seem to get the USB drivers to recognize the device.

Anyone have ideas on what I can do as a next step?


Thanks to pio_maski and linuxsociety for helping us all out. For those just joining the thread:

For everyone having the missing partitions error in this thread, once it starts its done, it began when the first freeze occurred.

At this point you have 2 choices, neither is fun and both involve Acer.

1 send it now and get charged for repair, they'll know its modded.

2 try to trigger fail safe and just plug it in, turn it on and let it sit and try to boot into android. After a set amount of failed /system or /boot reads it'll go into fail safe mode. Sending it under warranty in this state will have it repaired at no code aside from shipping to Acer.

You'll know fail safe is happening when you turn it on, blue or orange light comes on but the screen is off and there is no vibration on power on.

Both ways:

Get onto the Acer site and start a chat with a rep, tell them what happened. They'll ask you to hard reset after verifying warranty is still in effect time wise. After it fails this, they'll give you the info on sending it in. For me it took 10 days to get it back from sending it out.

Edit: for anyone that can still boot but hangs up, recovery may still be possible but its a very small window.

If you have the brick, then there isn't any options left except to send it in to Acer for repair. They won't say anything about your ROMS/Kernels, however you need to find out if the stock bootloader needs to be re-flashed, and this will pretty much lock them out of recovery and everything when you do. They'll just end up replacing the board in the tablet and sending it back. I'm not 100% sure if anyone has sent their tablet in to acer with the a200 bootloader still intact and received their repaired tablet without a hassle, really that's the main thing you may want to check into.

 

[benpwarner]

I had the same thing happen to me last night.

 

[linuxsociety]

Curious to know if you all were using stock kernels or a custom one? if custom which one?

 

[kemonine96]

Curious to know if you all were using stock kernels or a custom one? if custom which one?

I believe mine was a stock kernel. I was using an unlocked boot loader, clockwork recovery 5.5.0.4 (I believe) and CM9 from 2012/07/08. Unfortunately that is about all the information I can provide. I was unable to use adb with CWR so I couldn't pull up more information on the nature of the problem. I ended up sending it back to Acer for warranty and got it back not 24 hours ago.

 

[linuxsociety]

I believe mine was a stock kernel. I was using an unlocked boot loader, clockwork recovery 5.5.0.4 (I believe) and CM9 from 2012/07/08. Unfortunately that is about all the information I can provide. I was unable to use adb with CWR so I couldn't pull up more information on the nature of the problem. I ended up sending it back to Acer for warranty and got it back not 24 hours ago.

The reason I asked was because I have been working on custom kernels and recoveries for the A100 to help in preventing this from happening, so I just wonder if anyone has had the mmc brick bug to occur while using one of my kernels in combination with my twrp recovery that also has userland mmc brick bug prevention patches.

 

[kemonine96]

The reason I asked was because I have been working on custom kernels and recoveries for the A100 to help in preventing this from happening, so I just wonder if anyone has had the mmc brick bug to occur while using one of my kernels in combination with my twrp recovery that also has userland mmc brick bug prevention patches.

What causes the bug? Is it something preventable in terms of software run? I just got my A100 back from warranty and would prefer it not die in the same spectacular fashion again...

I actually just finished unlocking the bootloader, flashing CWR 5.5.0.4 and re-installing CM9. Would prefer not to do this dance again.

 

[linuxsociety]

What causes the bug? Is it something preventable in terms of software run? I just got my A100 back from warranty and would prefer it not die in the same spectacular fashion again...

I actually just finished unlocking the bootloader, flashing CWR 5.5.0.4 and re-installing CM9. Would prefer not to do this dance again.

The exact cause is unknown, however we do know that parts of the information the GPT partition table contains is wiped. There is no exact cause that we are aware of yet.

I wonder why so many people choose to use CWR over twrp? It would make sense to use CWR on devices that don't have TWRP support, but this one does and has for a while. I've never figured that out as the interface is much more trickier and when I have used it in the past i just seem to easily accidentally do the wrong thing with it. I dunno I guess people get accustomed to using one product and just never switch to something else.

 

[kemonine96]

The exact cause is unknown, however we do know that parts of the information the GPT partition table contains is wiped. There is no exact cause that we are aware of yet.

Do the more recent recoveries include a good way to re-write the GPT partition table via an adb shell? Seems like if you can re-write the GPT partition table you'd be able to recover the device from mostly dead. Also, does the bug affect data stored on the various partitions? If so, are there images of the various partitions floating around?

I wonder why so many people choose to use CWR over twrp? It would make sense to use CWR on devices that don't have TWRP support, but this one does and has for a while. I've never figured that out as the interface is much more trickier and when I have used it in the past i just seem to easily accidentally do the wrong thing with it. I dunno I guess people get accustomed to using one product and just never switch to something else.

Speaking for myself, I find that I can mash the hardware keys more efficiently via muscle memory than touch about a touch screen. Probably my old graybeard keyboard ways shining through...

I considered moving over to TWRP but the last I looked the information was a little lean (~1-2 months ago now probably). I planned on looking closer at it once the JB port is further along for the A100. Figured I'd jump to TWRP when I jump over to JB. I am aware the CM9 versions for the A100 are a bit out of date and I'm working on a build to address that (running repo sync while I'm at work).

 

[pio_masaki]

What causes the bug? Is it something preventable in terms of software run? I just got my A100 back from warranty and would prefer it not die in the same spectacular fashion again...

I actually just finished unlocking the bootloader, flashing CWR 5.5.0.4 and re-installing CM9. Would prefer not to do this dance again.

At this point its an unknown trigger, however the research on it shows Samsung and kindle fire devices with the same emmc we have are prone to the same issue.

As it stands now Linux society has patched the issue for Samsung devices in his kernel for Android and his kernel for twrp, its about the best protection we have at this time. While I may not agree to the trigger with him, its still a step taken against it that may well prove to be what prevents future bricks. Better safe then sorry kind of thing and I would suggest his recovery and kernel for this reason. Plus his kernel has a lot of extra goodies to play with

It works with all existing roms from ICS to JB, stock or modified or CM.

Tapatalked from my Galaxy S II.

 

[kemonine96]

At this point its an unknown trigger, however the research on it shows Samsung and kindle fire devices with the same emmc we have are prone to the same issue.

As it stands now Linux society has patched the issue for Samsung devices in his kernel for Android and his kernel for twrp, its about the best protection we have at this time. While I may not agree to the trigger with him, its still a step taken against it that may well prove to be what prevents future bricks. Better safe then sorry kind of thing and I would suggest his recovery and kernel for this reason. Plus his kernel has a lot of extra goodies to play with

It works with all existing roms from ICS to JB, stock or modified or CM.

Tapatalked from my Galaxy S II.

You just had to sweeten the deal.... I will definitely add this higher on my ToDo list than I planned. I really don't want to go through the hassles of another warranty.

If it helps right before my device's GPT table died, I saw a massive CPU spike that caused my device to get quite warm. 2 or 3 hard power-offs and power cycles later my device was going out for warranty. After each boot before it went dead the CPU spike problem was still present and the device wouldn't even unlock from the lockscreen.

 

[pio_masaki]

You just had to sweeten the deal.... I will definitely add this higher on my ToDo list than I planned. I really don't want to go through the hassles of another warranty.

If it helps right before my device's GPT table died, I saw a massive CPU spike that caused my device to get quite warm. 2 or 3 hard power-offs and power cycles later my device was going out for warranty. After each boot before it went dead the CPU spike problem was still present and the device wouldn't even unlock from the lockscreen.

That is actually different from normal for emmc bricks, though makes sense too. If the file system is corrupt or missing then it would hog CPU time trying to find the data or fix the damage, if it even could.

Tapatalked from my Galaxy S II.

 

[icomar]

i think my a100 died just now for the same reason. i was running cm10 preview with 1.5 custom kernel for JB. Is there a way to restore the tablet? any help?

 

[linuxsociety]

i think my a100 died just now for the same reason. i was running cm10 preview with 1.5 custom kernel for JB. Is there a way to restore the tablet? any help?

You need to give more details about what exactly your tablet is doing and what all was you doing when this happened? Can you still get to recovery? When you try to boot does it ever show boot animation? After turning the tablet on does the distorted Acer image still appear? Can you get adb connection at regular boot? Recovery adb? If you can get to recovery can you please give us your recovery.log file also? Thanks


Sent from my A100 using Tapatalk 2

 

[icomar]

You need to give more details about what exactly your tablet is doing and what all was you doing when this happened? Can you still get to recovery? When you try to boot does it ever show boot animation? After turning the tablet on does the distorted Acer image still appear? Can you get adb connection at regular boot? Recovery adb? If you can get to recovery can you please give us your recovery.log file also? Thanks


Sent from my A100 using Tapatalk 2

you are right, so:

1) my tablet was charging, i unlocked it, it freezed. So i pressed the reset button under the tablet. Then it showed boot animation for ever.
2) i can access recovery (clockworkmod recovery) so i flashed cm9 instead of cm10, but the result is always the same, stuck on bootanimation after the distorted acer image that appears. Sometimes the tablet finishes boot, say "upgrading android" but never finishes.

I will try with adb later at home, and if you can tell me how to take the recovery.log i will provide it.
In this case what can i do?

 

[linuxsociety]

you are right, so:

1) my tablet was charging, i unlocked it, it freezed. So i pressed the reset button under the tablet. Then it showed boot animation for ever.
2) i can access recovery (clockworkmod recovery) so i flashed cm9 instead of cm10, but the result is always the same, stuck on bootanimation after the distorted acer image that appears. Sometimes the tablet finishes boot, say "upgrading android" but never finishes.

I will try with adb later at home, and if you can tell me how to take the recovery.log i will provide it.
In this case what can i do?

That's not a brick. backup your apps with titanium backup, reboot wipe data, cache, dalvik, and system. Install your rom, gapps, kernel, etc.. Boot to android and install titanium backup, restore apps + data (only user apps not system!)

Sent from my A100 using Tapatalk 2

 

[icomar]

hello there, i did what you said (except for the titanium backup thing, i dont care about apps) that is the procedure to flash roms. after flashing the recovery freezed after saying "install completed" so i had to reboot manually the tablet from the power button.

still rom does not work (now the boot animation does not even show up).
PLUS if i try to wipe again the recovery says what you see in the attachment.

It is worse than before, am i right?

 

[pio_masaki]

That's not a brick. backup your apps with titanium backup, reboot wipe data, cache, dalvik, and system. Install your rom, gapps, kernel, etc.. Boot to android and install titanium backup, restore apps + data (only user apps not system!)

Sent from my A100 using Tapatalk 2

He's bricking. If he wipes cache then he will finish the job.

Edit: never mind I didn't see his update.

Tapatalked from my Galaxy S II.

 

[icomar]

He's bricking. If he wipes cache then he will finish the job.

Edit: never mind I didn't see his update.

Tapatalked from my Galaxy S II.

now what? too late?

 

[linuxsociety]

hello there, i did what you said (except for the titanium backup thing, i dont care about apps) that is the procedure to flash roms. after flashing the recovery freezed after saying "install completed" so i had to reboot manually the tablet from the power button.

still rom does not work (now the boot animation does not even show up).
PLUS if i try to wipe again the recovery says what you see in the attachment.

It is worse than before, am i right?

Well it definitely doesn't look good now. So the boot animation was appearing before you tried to do all the wipes and install from CWM? I just wanted to verify that this DID in fact take place while booted into recovery. You may want to discuss this with pio_masaki since he had a brick happen to him recently, and he is quiet knowledgeable with the procedures to try to recover from lost partitions or to verify that you are indeed bricked (lost GPT partition info ) .

 

[mordeith]

stock rom

my tablet(a100)is doing much the same, its stock except for crosix swap-mod ,i plug into pc(win 7) and it says apx not installed..last nite it locked up while reading,..and well..i rebooted it and all i saw was the android..