Related
** UPDATED WITH .BCT saving, include USB as well as NVFLASH just copy in
** 1 dir, run the batch and keep those you may need them one day
** Read the batch file for more info
It is clear for me is that it is not a perfect solution to use nvflash with images that you do not know the source.
The tegra S.O.C. use the information from a file stored in partition#2 to configure some low level setting like flash memory chip speed, total memory installed, video memory installed, flash type etc. As an example, if for some reason a batch of tablet is built with more memory then the .bct files will need to be changed accordingly
It is already confirmed that there's at least 2 different type of hardware. (2 different images by bekit do not use the same .bct configuration)
When flashing after a full wipe after using the create command, nvflash read the .bct configuration files and store it in the partition #2 on the tablet, bct files are created by the manufacturer using a tool from nvdia called buildbct. They are not writen during regular nvflash (where the partition are not re-created)
This also mean it is MUCH safer to NOT replace the partition 2 when nvflashing a device... (the hardware configuration would not be touched).
This batch files will work under windows and will not modify your tablet in anyway
please make sure you use the nvflash tools that is 151K there's an older and smaller one in some package, it will output binary inside the partition.txt instead of plain text. The version 2 include everything you need to backup the device under windows
Thanks to the various poster of thread about nvflash for the correct command THEY did the hard work not me !
To Restore individual partition the command is
"nvflash.exe" --bl bootloader.bin --download X partX.img
where X is the partition number you wish to flash, as stated you can also use your backup from clockwork mod for partition 11 restore.
this will not work for partition below 4
P.S.
I am not trying to start a debate on the validity of the current recovery (thumb-up to the guy who offered those!) They are valid for MOST device however
if you do have a different device this will alleviate any issue that may happen with nvflash restore.
see 2 post below for full restore info
Hi,
I know that the partitiontable shows a partition named "BCT", but is there also something else, perhaps flashed into the SOC itself that is referred to as "the BCT"?
The reason for the question is that nvflash has a setbct and a getbct command, separate from the read and download commands, which work with the partitions.
Jim
Reserved
(will be completed a bit later)
so, we possibly share more internals with the 10s than previously expected? maybe... can we get this thing to dual boot in the future??
10roller said:
so, we possibly share more internals with the 10s than previously expected? maybe... can we get this thing to dual boot in the future??
Click to expand...
Click to collapse
My guess is yes, the platform of the ac100 laptop by toshiba is tegra based and they do it!
P00r said:
The set bct command probably write the 4080 byte to the partition named bct in the cfg, I have yet to test flashing a dummy FF filled partition with the command to confirm the flash.bct get writen there
So in fact when you restore with the nvflash restore images from bekit I think you are actually writing it twice... (it is in the image and you telling the nvflash to create it) but I have not confirmed this yet
Once the bct info is there, the SOC read his configuration there, as well as the ODM info, I have not found a way to use --getbct that reads back the BCT from mass storage yet...
I am not sure either why there's so many section being flashed it should work with only a few of those (I plan to test this) since nvflash is simply puting those one after the other. It make sense only sense for a dual booting unit
Click to expand...
Click to collapse
Hi,
I was able to get --getbct to output a 2048 byte file awhile ago. I think I had posted about it, but, sorry, I don't remember which thread. The only thing I vaguely remember was that I had to use some unobvious combination of parameters. Also, I think that it only worked right after pushing the bootloader.bin. If I find my post, I'll provide a link.
Jim
Thanks OP, I like the idea of being able to back up the partitions directly from my tablet so I know I'm restoring the proper thing should I ever have to resort to that.
Just starting to get into modding this thing after it showed up from Woot yesterday, been planning on buying one for quite some time to compliment my Epic 4g and when the woot sale dropped I had to jump on it. So far all I have done is flash clockwork, and make a nandroid backup with that. Also doing this backup method now.
So have you actually done a successful restore using this method?
so is it possible to back up your original hardware configuration and restore it when you got problems???
Yes and NO, I have error reading partition #11 (system) on my tablet (bad block)
if I use it as is for restore, it doesn't restore and boot, however replacing this partition with clockwork system.img backup give me back a full working tablet.
I can also reboot into recovery and restore from there.
Letters and numbers oh my
I ran the backup on my new replacement GTab yesterday. I had a size mismatch on partition 5, everything else backed up properly. Also, my partition 7 is BLO and partition 6 is MSC. Thanks for the script and capability.
Mike
P00r said:
This also mean it is MUCH safer to NOT replace the partition 2 when nvflashing a device... (the hardware configuration would not be touched). I will post later on how to flash back those if someone request it...
Click to expand...
Click to collapse
Instructions on how to flash back using this would be great. I'd like to have the option to do so if I need to, but haven't gotten familiar enough with nvflash yet to figure it out on my own.
iamchocho said:
Instructions on how to flash back using this would be great. I'd like to have the option to do so if I need to, but haven't gotten familiar enough with nvflash yet to figure it out on my own.
Click to expand...
Click to collapse
You can flash back the partition using
"nvflash.exe" --bl bootloader.bin --download X partX.img
where X is the partition number you wish to flash, as stated you can also use your backup from clockwork mod for partition 11 restore.
If needed you can use the nvflash format kit prior to restoring however it would be better to use your own .bct with that option
Getting stuck at partition 7.
xkwwwx said:
Getting stuck at partition 7.
Click to expand...
Click to collapse
What is the error you are getting ?
stock recovery image
Thank you very much for the sharing this.
Now I have 10 img files (part-2 to part-11)... wich one is the stock recovery image? I did this before installing clockwork mod...
Thanks!
I think this is fantastic. Gives us a chance to backup our gtab before deciding to try a new rom. I tried this today in the hopes to backup and then install the flashback HC rom. But unfortuntaly it stopped on image 7, as xkwwwx has also mentioned. The message seemed to be a issue with the size expected of the image as to what was received. Ill try and copy the message.
"nvflash.exe" -r --read 7 part-7.img
nvflash started
[resume mode]
receiving file: part-7.img, expected size: 16777216 bytes
/ 131072/16777216 bytes received
At that point it stops, and i have to control c to exit the batch file. Id love to be able to backup with this pls, so i can try another rom, and know i can use this to return to this rom if i dont like the new one, any chance this can be resolved pls ?
Was also wondering if some form of GUI maybe of benifit, i know alot of people feel wary of NVFlash, perhaps with a GUI people would feel more comfortable using it. Maybe a simple screen with a backup and restore set of buttons ?
P00r, any chance you can help mate ? Cant use this unfortunatly because of the image size issue.
Icedvoco said:
P00r, any chance you can help mate ? Cant use this unfortunatly because of the image size issue.
Click to expand...
Click to collapse
This mean you probably have a bad block in this section, try skipping it to get the other parts first. this is not a major issue, you may also encounter one in the last data section (my tablet has a few byte less than the regular one)
For the data partition you can substitute the cwm images
Also try using a different bootloader and nvflash this can help even shorter usb cable or a different one can help
The part that you can read is probably usable for a restore anyway
Bad block are not unusual in flash and I have seen a few with this, ideally and usually it's located at the end, you could try using the format image a few time it could be a stuck byte and writing different data can revive it (format write FF all over)
P00r said:
This mean you probably have a bad block in this section, try skipping it to get the other parts first. this is not a major issue, you may also encounter one in the last data section (my tablet has a few byte less than the regular one)
For the data partition you can substitute the cwm images
Also try using a different bootloader and nvflash this can help even shorter usb cable or a different one can help
The part that you can read is probably usable for a restore anyway
Bad block are not unusual in flash and I have seen a few with this, ideally and usually it's located at the end, you could try using the format image a few time it could be a stuck byte and writing different data can revive it (format write FF all over)
Click to expand...
Click to collapse
Bad blocks may be common, but bad blocks in the exact same spot probably not. I get the exact same thing:
"nvflash.exe" -r --read 7 part-7.img
Nvflash started
[resume mode]
receiving file: part-7.img, expected size: 16777216 bytes
/ 131072/16777216 bytes received
Any other thoughts on this?
Maybe someone here knows,
So with NVflashing, I've found only one file that has the alternative BCT (it's a tnt1.0 rom on BL1.1) and no other NVflash file sets work without causing a APX bootloop.
This is the NVflash file set that works for me http://db.tt/FvSeAZj
Ive read it was made when someone was trying to configure for the hardware variations.
Now is it possible to take my backup and insert just the files needed into another NVflash file set?
Well, my Nook appears to be in trouble.
The long and the short of it is that it got wet. Not too wet, but wet.
It boots but whatever I boot to crashes. This includes sdcard installs. The ROM completes the boot, and I can sometimes even open the app drawer, but it crashes before I can interact with it in any meaningful way.
All ROMs complain of "System process" and Wireless issues, with FCs.
I cannot get adb to recognize the device anymore. lsusb does find the Google Inc. entry, though. When I try and run adb devices (ubuntu), it returns ?????? and says insufficient permissions. I have, in response, set up the 99-android.rules in etc/udev/rules.d but it still cannot connect. I have also tried to quickly access the android terminal in the brief period I am allowed before the device crashes with no luck. My goal with this was to try fdisk -l.
The sdcard never mounts while in the ROM, and the emmc storage appears completely wiped.
However, I was able to see I had the correct files in /rom once, so those are there.
Thinking that the wireless chip might be the problem (as when even when I return to stock the set-up fails there, well, until it crashes again...) I tried to just turn off Wifi in 7.2. But as I unchecked the box, right under the setting just displayed "error"
CWM appears to be working EXACTLY as it should, including mounting the sdcard and allowing me to choose update zips.
The uboot and the uboot menu work as well.
I have tried flashing CM7, 9 and stock, as well as booting from sdcard in CM9. All flash and boot normally, but crash.
I have done the 8x reboots, succesully, but when the B&N set-up begins, I cannot connect to wireless. Which would be okay, in the long run, but it then crashes, which is not okay.
I was hesitant to reveal that it got wet, because I can see this being written off as a hardware issue (which it may be, don't get me wrong). But the fact that CWM works and the ROMs boot sure look like software problems to me.
I have tried flashing just about everything that looked promising. I have not dd any images, because I cannot get adb to work, and don't have any idea which partitions are in what shape.
Any suggestions?
Position the unit upside down with the SD flap open. Blowdry it from the bottom up on medium several times over a couple of days. If it's still doing it after that you can probably eliminate moisture as a cause.
old cell phone trick
Fill a bowl with rice (uncooked).....the rice will draw the moisture out.
you can also submerge it in ispropol rubbing alcohol... is what we use to clean electronic components... it will combine with the water... also used for water in gas on a car
Whoa, isopropyl alcohol. I feel like that would take some stones...
I have already put it through a 30 or so hour rice regimen (if that is true, even. It makes some kind of weird intuitive sense, which is usually the kiss of death...)
I have it standing up now and will see about a little air dry method while I investigate where to find the alcohol.
It didn't get submerged, it was lying on a counter and a glass got knocked over. I grabbed it right up, and then left it off like I said.
It boots, CWM works, but since it has been set all the way back to stock and all iterations have the same issue I am fearing the worst...
Thanks for the ideas...any and all welcome!
You can take the back off. I have not done it, but somebody just said they did it to disconnect the battery to reset. Look at that recent thread in q/a. Maybe he can tell you how he did it.
Attempt at your own risk, no support will be provided.
I'm not the battery guy leapinlar was talking about but,
Open the battery flap, remove SD card, remove the tape dots from the T-5 torque screws then remove the screws. Slowly and carefully so as not to break any of the hooky thingies that are holding the back on pry the cover up from that point moving slowly around the unit.
I've only done this once, it was a while back and I ended up breaking two of the little hooky thingies. That's why I suggested providing points for evaporation to escape and attempting to accelerate evaporation. Heck we don't even know if moisture is the issue anymore.
Thanks for the extra suggestions.
I tend to think at this point that whatever water got in there is gone. It's been four days, and it wasn't soaking. I may just go ahead and try and take out the battery, I don't know exactly why that would help, but what have I got to lose?
If I had to guess, I would think that the wifi chip might be shorted, as that is the only thing that doesn't seem to work at least for some period of time.
The FC's sure do look software related though. I fail to see how CWM could read and mount the sdcard while the ROM cannot as being anything other than sotware. Unless they use wildly different methods to do the same thing.
This nagging feeling that I should be able to at least fix that with some software methods keeps me thinking the same or the other problems. I'd be okay with an non-networked tablet, if it came to that. But maybe the thing has to have wifi as an option to work right. I don't know...
Two weeks ago my daughter managed to completely soak her nook.The nook would just constantly reboot with the stock os and system process would repeatedly fc with the cm7 sdcard. I pulled the back cover off and let it stand for a week. Today I pulled the battery and power button cable and it booted up just fine so far. So there is hope.
Malave said:
Two weeks ago my daughter managed to completely soak her nook.The nook would just constantly reboot with the stock os and system process would repeatedly fc with the cm7 sdcard. I pulled the back cover off and let it stand for a week. Today I pulled the battery and power button cable and it booted up just fine so far. So there is hope.
Click to expand...
Click to collapse
Considering that this is basically what is happening to me (but with some additional Wifi setting crashes) this gives me hope.
I had burned a bootable CWM card, from Leapinlar, which was a higher version than I usually used. I think 5.5.0.4 (?)
Anyway, of interest (before I shut it down 2 days ago):
internal sd card is not wiped, it can be explored in CWM.
The /ROM partition is at least somewhat functional, as battery stats can be wiped
When I request a log, I get:
Code:
Battery Stats
Block Groups: 3
reserved block group size: 23
Created filesystem with 11/22608 inodes
and 2883/90357 blocks
warning: wipe_block_device: Discard Failed
W: failed to mount /dev/block/mmcblk1p2 (no such file or dir)
also at one point:
Code:
make_ext4fs failed on /dev/block/mmcblk1p2
(note: both of the above from hastily scrawled notes)
It looks like mmcblk1p2 is related to system mounting, although I am not sure. Maybe that is why I am having trouble with ADB. It just kept saying insufficient permissions and ???????????. I tried setting up android-rules for udev with no luck.
Unless I hear anything else promising, I will go get the proper screwdriver and try the battery thing. It has been sitting off for a couple days now...
Thanks for all the ideas, people.
I'm confused... but trying to help you out... why are you trying that stuff on /dev/block/mmcblk1p2 when /dev/block/mmcblk0p2 is the ROM partition?
Try your edits to /rom... and if you have to try: mount /dev/block/mmcblk0p2 /rom
DizzyDen said:
I'm confused... but trying to help you out... why are you trying that stuff on /dev/block/mmcblk1p2 when /dev/block/mmcblk0p2 is the ROM partition?
Click to expand...
Click to collapse
I actually didn't try to do anything. I just wiped system, cache, davlik, battery stats and asked for a log prior to flashing a new zip in the hopes that the rom would work if provided a blank slate.
I wiped battery stats since the .bin that holds them is in /rom. The log was something I had never done before.
The notes from above were just the CWM output from the log.
edit: I just saw your second paragraph. Don't know how I missed it.
But I don't know what you mean by edits. I haven't been able to get ADB working. I have been able to mount and unmount through CWM that's it. Unless you might know anther way to resolve insufficient permissions with beaucoup question marks instead of device number?
Ok... sorry about my confusion on that... It appears that you are using a CWM that is modifid to work on SD... since it is trying to access /dev/block/mmcblk1p2 since the rom partition is on /dev/mmcblk0.
I would try a different version of recovery.
DizzyDen said:
Ok... sorry about my confusion on that... It appears that you are using a CWM that is modifid to work on SD... since it is trying to access /dev/block/mmcblk1p2 since the rom partition is on /dev/mmcblk0.
I would try a different version of recovery.
Click to expand...
Click to collapse
Which I was. I got it from Leapinlar, and was under the impression, since I had seen him warn that roms flashed from that recovery would go to emmc, that it would work.
I did make a regular 3.2.0.1 bootable, and tried again, but with the same result, so I don't know if that made a difference. But it did seem hopeful, so thanks for the response.
I am going to finally go get the torque screwdriver and take this battery off and give it some days. It's been almost a week already, but you never know.
Thanks a bunch for the reponses, Diz.
mateorod said:
I had burned a bootable CWM card, from Leapinlar, which was a higher version than I usually used. I think 5.5.0.4 (?)
warning: wipe_block_device: Discard Failed
W: failed to mount /dev/block/mmcblk1p2 (no such file or dir)[/CODE]
also at one point:
Code:
make_ext4fs failed on /dev/block/mmcblk1p2
(note: both of the above from hastily scrawled notes)
It looks like mmcblk1p2 is related to system mounting, although I am not sure.
Click to expand...
Click to collapse
Mateorod, if you got that log using my CWM boot SD version 5.5.0.4, the recovery.fstab lists /dev/block/mmcblk1p2 as SD-EXT, which for some devices is the extended partition on SD for storing additional apps to supplement /data. Our implementation of CM does not use that. So when recovery tries to do some wiping, formating, backing up, etc, it always fails when it looks for that partition. It has nothing to do with /system or /rom.
If you told it to do a factory reset, it tries to wipe /SD-EXT as part of that and it fails to wipe that because it cannot find that partition.
Edit: That CWM SD does do its modifications to emmc. It only referenced mmcblk1p2 because of sd-ext.
Here is the filesystem table from my log using it on SD:
0 /tmp ramdisk (null) (null) 0
1 /boot vfat /dev/block/mmcblk0p1 (null) 0
2 /system ext4 /dev/block/mmcblk0p5 (null) 0
3 /data ext4 /dev/block/mmcblk0p6 (null) 0
4 /cache ext4 /dev/block/mmcblk0p7 (null) 0
5 /emmc vfat /dev/block/mmcblk0p8 (null) 0
6 /sdcard vfat /dev/block/mmcblk1p1 (null) 0
7 /sd-ext ext4 /dev/block/mmcblk1p2 (null) 0
The alcohol trick does work, I did it on my old HTC Kaiser. I disassemble it as much as I was comfortable, and then completely submerged it in alcohol until It stopped throwing up air bubbles; Thus showing there was no air left in the unit. I then removed the pieces from the alcohol and put them in a bowl of rice. I let it stand for about a week. Once the time was up a reassembled and turned it on like nothing had happened.
Little note: I was in the possession of a AT&T Go Phone for use as a back up in case this destroyed the unit. If you feel that there might be another way to repair it, I would suggest you explore that option first as I do not know what a significant time in alcohol will do to the inner workings of the Nook. However if you are at the point of already replacing or upgrading to a different tablet, than you have nothing to lose and can only gain a working Tablet or fancy Paper-weight from this.
Okay, a little update.
I had taken apart the Nook and let it sit for almost a week. But upon reconnecting the battery and clearing system/cache/davlik and reflashing anything, it still wouldn't allow in-ROM mounting of sdcard or adb or wireless and I would still get some version of "process System not responding" and "Setting Wireless not responding" toasts and then a crash, either in CM7, CM9 or Stock. Unusable.
What I think I have is a totally borked wifi chip. Which is okay, in the long run, but the Nook kept crashing and I would have liked to use it in some capacity.
What I decided (which was difficult to diagnose with no terminal or no ADB) was that the Nook was crashing upon trying to access the network and the saved network info. (which I know is mad persistent, as the wifi network I used to originally register the device still shows up in the stats, even after many many system wipes and 8x reboots and so forth.)
I had never reset to factory from stock settings and I couldn't now completely erase and deregister because you need wifi to do so.
However, I found this (which I had never heard of, sounds like a boon to thieves everywhere). After skipping out-of-box experience I could boot into stock recovery and finally erase the wireless settings.
Now I have a stable (albeit un-registered) stock nook, where I can at least read the books I have on sdcard.
I will eventually reflash a CM build now that the network settings have been forgotten and see if that is usable, even if there is no wifi.
But I am pretty happy to have some semblance of the Nook back, even if it is just a neutered (literally) stock.
I'll let you know how CM goes one day soon.
Thanks for the help!
Excellent, (and powerful), link.
And by virtue of that link I will find a way to proclaim my absolute geekitude within the company by dropping Kate's name. :good:
Well, I finally tried flashing Cyanogen 7 and 9 to the thing, but as it crashes when it tries to access wifi, I can't get it stable.
Unless anyone knows a code edit (smali maybe? I know there are a bunch of boolean settings in the SystemUI.apk, maybe there) where I can change the default wifi setting, I may just be stuck with stock.
Which is way better than nothing, at least it has use. Skipping OOBE was a life-saver for getting to a place where I could erase the WiFi info.
Okay, here's another shot in the dark, still trying to get this thing to successfully boot in CM...
I am working on a little project for the Nook, which will be infinitely easier to debug if I can actually boot into CM.
Does anyone familiar with the source code know how to modify it so that WiFi is set to off by default? I am thinking about changing the 'true' to 'false' in the /device/bn/encore/overlay/frameworks/base/core/res/res/values/config.xml entry for wifi found here...
Code:
<!-- This string array should be overridden by the device to present a list of network
attributes. This is used by the connectivity manager to decide which networks can coexist
based on the hardware -->
<!-- An Array of "[Connection name],[ConnectivityManager connection type],
[associated radio-type],[priority],[restoral-timer(ms)],[dependencyMet] -->
<!-- the 5th element "resore-time" indicates the number of milliseconds to delay
before automatically restore the default connection. Set -1 if the connection
does not require auto-restore. -->
<!-- the 6th element indicates boot-time dependency-met value. -->
<string-array translatable="false" name="networkAttributes">
<item>"wifi,1,1,1,-1,true"</item>
<item>"bluetooth,7,7,0,-1,true"</item>
<!-- item>"ethernet,9,9,2,-1,true"</item -->
</string-array>
This looks like I am on the right track (this will eventually end up being compiled into the res folder of framework-res.apk) but I may need to track down the ConnectivityManager. Although the cursory look I have given this seems like I may be close to on the right track...
(The wifi being on at boot always crashes my CM installs due to shorted wifi chip, for those of you who may be new to the thread.)
I am asking here just in case someone knows, I may just go ahead and try it if no one chimes in. But better to ask than to blindly shoot in the dark, I figure...
Update: Success. I am back on CM9 (well, a hybrid, actually...HINT), without wifi.
Update 2: Due to the fact that this nook is now in a Cyanogen-usable state, a new rom will be posted in development tomorrow from eyeballer and I. Thanks for the suggestions, everyone. I wish I had dipped it in isopropyl alcohol, just so I could say I did it...
SOLVED the best way.. See post #5
Hello
I have asked this in other threads, but have not gotten an answer that I can manage to make work yet. I'm also hoping that this thread may help the many others out there with this same problem.
I have an Iconia A500 that has the bad sector problem. I cannot get it to format partitions through any of the EUU's out there,or even the Babsector .bat's . Same thing every time-read/write failure. I have seen mention in a thread or two about guys who have used the "rawdeviceread" and "rawdevicewrite" commands in NvFlash to "map out" any bad sectors on the EMMC chip, and create "dummy" partitions over them so that the tablet will function again, at least until more sectors die anyhow.
Can someone please explain this process, including describing the files needed, exact commands, and the rest of the process to make this happen? I have seen member "Yaworski" describe the basis of it, but again his commands are no-go for me. It would also be great if a partition could be created, but not formatted, completely bypassing any possibility of NvFlash failure.
Thanks in advance By helping me I'm sure you wil also help many others. It seems many a500's are starting to suffer form this same exact issue.
Anyone? I have read thru this post: http://forum.xda-developers.com/showthread.php?t=1691729&page=3 , and seen a couple recommendations to it in other threads, but no dice on making it work .. or even being able to map out the bad sector/s. I know this'lll fix me up at least temporarily...
I need help with this as well. There doesn't seem to be a step by step guide anywhere :\
Sent from my SGH-T769 using xda premium
dynospectrum said:
I need help with this as well. There doesn't seem to be a step by step guide anywhere :\
Sent from my SGH-T769 using xda premium
Click to expand...
Click to collapse
I've been asking around about a possible process of mapping out bad sectors, and not just members in here, but engineers and technicians I know as well. First, the NAND has this sort of embedded firmware that directs it to remap or bypass bad sectors “spontaneously,” if you can call it that. When you're stuck with “write errors” or where the NVflash even fails to create and format a partition, it suggests that this part of that firmware is not working. Why the loose fit, or lack thereof, I don't know.
Second, The FCK guys mention that you can write a dummy file and make the device read back so you can see where the data is missing and circumvent it altogether. But they also state that if Sector 0 – which NVFlash is slated to access – is kaputt, then it would hang, as probably in your case and certainly in mine.
Given that the Boot Configuration Table is 4Kb tiny while the NAND is 16Gb large, I can't imagine the latter being damaged so badly as not to have a continuous space of 4Kb to accommodate such partition. As a matter of fact, I did have someone with special equipment probe my NAND “physically” and the initial report indicated that the first half (50%) of it had less than 3% of its sectors that was bad. NVFlash, however, could neither create nor format, let alone write on it.
So, either one must have the appropriate hardware to do a very low level format to restore the NAND in full or in part, or NVFlash has to be hacked to command writing at a Sector different than 0. Until that happens, I doubt it that a step-by-step guide grounded in current programs would be viable.
I know that neither the custom ROMs nor the custom Bootloaders and Recoveries are remotely the cause, because this occurred way before any of it came onto the scene. But in light of the frequency at which this happens to some of us, it seems ironic to term this device bullet-proof. I'd like to think it's not incurable, but what the FCK do I know? (Sigh) Anyone with the essential hardware know-how to tackle this?
SOLVED..well the "easy" way....
I sourced out a broken A500(strangely the screen is fine though lol), re-soldered the power button on it(PITA), and put it into my A500.
I plan on taking it easy with the flashing on this one. A500s seem to have a growing history of EEMC chip failure from over-flashing. My old board had been flashed MANY times by the previous owner, and a few by me before it died. The "new" tab was only flashed enough to get it to Stock ICS. Now it has the V8 bootloader and Civato's Re-Flexx ROM(Best out there IMHO).
So there you have it.. this seems to be the best way to fix this problem on the A500---Replace the Darn motherboard. I'd imagine mapping/skipping sectors is only a temporary fix that will probably lead to the tablet dying when its needed most.
My A500 has a black screen, and no recovery, but I can get to APX mode. My PC is running Windows 7 64 Bit, SP1.
When I run this command from the Babsector tool:
nvflash --bct flash.bct --setbct --configfile flash1.cfg --create --odmdata 0xb00d8011 --bl bootloader.bin --sbk 0x47A21E00 0x0B89F501 0x4BC31103 0xB42F2103 --go
this is the result:
sending file: flash.bct
- 4080/4080 bytes sent
flash.bct sent successfully
odm data: 0xb00d8011
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: bootloader.bin
| 714409/714409 bytes sent
bootloader.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
setting device: 2 3
creating partition: BCT
failed executing command 16 NvError 0x120002
command failure: create failed (bad data)
bootloader status: failed to create the partition (code: 10) message: nverror:0x5 (0x1000005) flags: 0
When the bootloader downloads, the screen lights with "Entering Acer Download Mode" in the upper left, and the Acer logo.
I've tried Afterota, Blackthund3r's tools, root-3.2.1, and all kinds of nvflash scripts. Nothing seems to be able to create the BCT partition.
Key point: this Tab was encrypted prior to all these problems. I do know the encryption password. Anyone have an idea how to recover this tablet?
Any one have an idea?
same as you
I have been in something similar
http://forum.xda-developers.com/showthread.php?t=2123900
and I have stock with HC rom with ICS bootloader !!!!
and stop there because every time I do somthing with the bootloader "babsactor,afterota,EUUs "it takes about a week to get back to the ICS bootloader
and with the ICS bootloader installed and "i think" evrey thing allright i can't flash any ICS rom or JB rom
I can flash only HC roms !!
and when i install HC bootloader i can flash HC roms only even the ICS roms that I used to flash with HC bootloader not work at all.
I hope you fix your problem.
sorry for my bad English.
GotWebs said:
My A500 has a black screen, and no recovery, but I can get to APX mode. My PC is running Windows 7 64 Bit, SP1.
When I run this command from the Babsector tool:
nvflash --bct flash.bct --setbct --configfile flash1.cfg --create --odmdata 0xb00d8011 --bl bootloader.bin --sbk 0x47A21E00 0x0B89F501 0x4BC31103 0xB42F2103 --go
this is the result:
sending file: flash.bct
- 4080/4080 bytes sent
flash.bct sent successfully
odm data: 0xb00d8011
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: bootloader.bin
| 714409/714409 bytes sent
bootloader.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
setting device: 2 3
creating partition: BCT
failed executing command 16 NvError 0x120002
command failure: create failed (bad data)
bootloader status: failed to create the partition (code: 10) message: nverror:0x5 (0x1000005) flags: 0
When the bootloader downloads, the screen lights with "Entering Acer Download Mode" in the upper left, and the Acer logo.
I've tried Afterota, Blackthund3r's tools, root-3.2.1, and all kinds of nvflash scripts. Nothing seems to be able to create the BCT partition.
Key point: this Tab was encrypted prior to all these problems. I do know the encryption password. Anyone have an idea how to recover this tablet?
Click to expand...
Click to collapse
hAVING exact same issue.... no help till now
I may be onto something here... I noticed that babsector A works fine, but babsector B fails every time. so whats the difference?
Maybe it has something to do with the sizing of the BCT... I am still experimenting.
flash1.cfg:
Code:
[partition]
name=BCT
id=2
type=boot_config_table
allocation_policy=sequential
filesystem_type=basic
size=4096
file_system_attribute=0
partition_attribute=0
allocation_attribute=8
percent_reserved=0
flash2.cfg
Code:
[partition]
name=BCT
id=2
type=boot_config_table
allocation_policy=sequential
filesystem_type=basic
size=3145728
file_system_attribute=0
partition_attribute=0
allocation_attribute=8
percent_reserved=0
underscorenorm said:
I may be onto something here... I noticed that babsector A works fine, but babsector B fails every time. so whats the difference?
Maybe it has something to do with the sizing of the BCT... I am still experimenting.
flash1.cfg:
Code:
[partition]
name=BCT
id=2
type=boot_config_table
allocation_policy=sequential
filesystem_type=basic
size=4096
file_system_attribute=0
partition_attribute=0
allocation_attribute=8
percent_reserved=0
flash2.cfg
Code:
[partition]
name=BCT
id=2
type=boot_config_table
allocation_policy=sequential
filesystem_type=basic
size=3145728
file_system_attribute=0
partition_attribute=0
allocation_attribute=8
percent_reserved=0
Click to expand...
Click to collapse
Did you find a solution? I'm having a similar problem.
myers7289 said:
Did you find a solution? I'm having a similar problem.
Click to expand...
Click to collapse
indicates bad storage (cold solder joint on nand chip)
there is a reflow method in the forum that has worked for many users
search or - bake in oven - in forum
Oh, I have a heat gun. It was not my tablet and I was attempting to fix it for a co-worker. I gave up a couple weeks ago.
hi, I've just been busy all afternoon trying to fix one of these tablets, and searching around for information to help, and came across this thread, so I hope nobody minds - I just wanted to mention what I'd found out.
I agree that this is most likely to be dry solder on the RAM chips, which is not easy to sort out on an A500 as they are all so perfectly shielded but I do hope I can still manage that as a test some time - I have 3 of these tablets at the moment, so I don't mind frying one to test it out
From what I've found on my faulty tablet, there is no partitions on its internal memory - none at all, not even faulty or corrupted ones. This would explain why it's so difficult to repair/flash them, because the memory keeps vanishing and it doesn't know how to tell us (except just saying unable to format etc.).
The only way to get any access to my tablets internal files (if there where any) is through Fastboot, but even that cannot identify the tablets ID at all, it only shows a single '?', and ADB can only find things that have a working system so that never even sees the device. I've had mine sometimes respond to Micro-SD cards in it and it can find UPDATE.ZIP files, but only about 1 in 20 attempts, and they never work beyond installing about 20%, so that indicates to me (just my opinion of course) that there's a weak chip or something in there that doesn't always work.
I have a heat station here so I'll be trying that this week some time.
I assume that the tablet can only find the SD card occasionally too, because each time it's internal memory isn't perfectly working, it has to lose some item further down the line. In an actual android OS it would be going nuts finding/losing the memory card, but in just the basic bootloader it's not that acurate.
A thing I've not seen mentioned anywhere that may be of help is, as with most phones and tablets there are secret things in them, secret ways to access menus, and hte A500 is no exception
Try this..... plug in a standard USB keyboard, and turn on into the recovery system (the bit where the big green android appears and then lies down with the warning explamation mark on).
Once he's lay down, press the HOME key on your keyboard, and you'll see text appear saying which files it has been trying to read as it booted up.......
Wait about 30 seconds, and now press the Up or Down arrows and you'l see the familiar blue recovery/bootloading menu.
Makes it so much easier to see what's going on then
I'll be back again soon, hopefully with some soldering that works lol
filesponge said:
From what I've found on my faulty tablet, there is no partitions on its internal memory - none at all, not even faulty or corrupted ones. This would explain why it's so difficult to repair/flash them, because the memory keeps vanishing and it doesn't know how to tell us (except just saying unable to format etc.).
The only way to get any access to my tablets internal files (if there where any) is through Fastboot, but even that cannot identify the tablets ID at all, it only shows a single '?', and ADB can only find things that have a working system so that never even sees the device. I've had mine sometimes respond to Micro-SD cards in it and it can find UPDATE.ZIP files, but only about 1 in 20 attempts, and they never work beyond installing about 20%, so that indicates to me (just my opinion of course) that there's a weak chip or something in there that doesn't always work.
I have a heat station here so I'll be trying that this week some time.
I assume that the tablet can only find the SD card occasionally too, because each time it's internal memory isn't perfectly working, it has to lose some item further down the line. In an actual android OS it would be going nuts finding/losing the memory card, but in just the basic bootloader it's not that acurate
I'll be back again soon, hopefully with some soldering that works lol
Click to expand...
Click to collapse
Did you manage to recover one of your tablets? I have same issue with a friend of mine's Acer A500, can't flash beyond 20-25%....The tablet is more than 3 years old, but all the hardware is ok (battery, screen, touchscreen and so on), except for the internal memory, it seems. Maybe the only thing I could do is to sell this tablet as spare parts, but would anyone be interested? What a waste of hardware....
Iconia A500 RAM repair
omniastrider said:
Did you manage to recover one of your tablets? I have same issue with a friend of mine's Acer A500, can't flash beyond 20-25%....The tablet is more than 3 years old, but all the hardware is ok (battery, screen, touchscreen and so on), except for the internal memory, it seems. Maybe the only thing I could do is to sell this tablet as spare parts, but would anyone be interested? What a waste of hardware....
Click to expand...
Click to collapse
I agree there - I don't like to see such a lot of good hardware going to waste, just the screen on the A500 is an amazing bit of technology, as clear a display as anything I've worked on costing 3 times as much. But anyway, on to what I have managed to find ......
I don't get much time to work on my own projects like this due to being self employed fixing anything & everything around me lol, but as mentioned in my first message i was assuming this was a memory chip fault 'maybe'.... so i powered up my heat station last weekend, and had some success !! But not completely yet.
I removed the RAM chip covers - I wasnt sure which they were but it was the biggest of the covers hid all of the items I needed to see (it wasnt really held down as well as it appeared, I put a small flat bladed screwdriver under one corner, applied very slight pressure, and had the heat gun nearby for about 15 seconds, and it all just lifted off one corner at a time!)
Next, I heated up the RAM chips gently, deliberatly avoiding heating any other part as I wanted to see if this did affect it. I used 300 degrees C for 20-25 seconds, 2 inches away from the chips, as always starting like this to test the theory out. Well guess what happened !!
If I now connect up a USB keyboard as mentioned in my previous posting, and get into the recovery menu from the keyboard, it allowed me to format a couple of extra areas of the internal memory - this is just what I had been hoping for The fact that it changed it to see 'any' extra RAM could show it's a possible working repair.
I've only sent this quick message now just to let people know, but I'm away from my workbench till later this week so it'll have to wait but I was very happy to see the changes it made. I don't have the full details with me as it's written down at home, but I'll return again later in the week when I've got time.
For now, I'm happy with what's happened.
filesponge said:
I don't get much time to work on my own projects like this due to being self employed fixing anything & everything around me lol, but as mentioned in my first message i was assuming this was a memory chip fault 'maybe'.... so i powered up my heat station last weekend, and had some success !! But not completely yet.
I removed the RAM chip covers - I wasnt sure which they were but it was the biggest of the covers hid all of the items I needed to see (it wasnt really held down as well as it appeared, I put a small flat bladed screwdriver under one corner, applied very slight pressure, and had the heat gun nearby for about 15 seconds, and it all just lifted off one corner at a time!)
Next, I heated up the RAM chips gently, deliberatly avoiding heating any other part as I wanted to see if this did affect it. I used 300 degrees C for 20-25 seconds, 2 inches away from the chips, as always starting like this to test the theory out. Well guess what happened !!
If I now connect up a USB keyboard as mentioned in my previous posting, and get into the recovery menu from the keyboard, it allowed me to format a couple of extra areas of the internal memory - this is just what I had been hoping for The fact that it changed it to see 'any' extra RAM could show it's a possible working repair.
I've only sent this quick message now just to let people know, but I'm away from my workbench till later this week so it'll have to wait but I was very happy to see the changes it made. I don't have the full details with me as it's written down at home, but I'll return again later in the week when I've got time.
For now, I'm happy with what's happened.
Click to expand...
Click to collapse
I see...From what I understand it's beyond my ability in repairing electronic devices, sadly. The only thing I could do is to find a similar tablet with broken screen or with a dead battery....Well, we'll see!
Btw, I had some success (for now) by putting the motherboard in the oven, for about 10-15 minutes. So far I was able to reflash Android 3.2.1 using apx mode, and now it works. I wonder, however, how long can this kind of "reflowing" method last. Maybe forever, maybe for a couple of days, who knows!
Holy cow, I think I fried the motherboard... O_O
Maybe it wasn't a great idea to put it in the oven for the second time (after problems with internal memory, again)!! Maybe this time it was too hot, I don't know. You know what they say, "live and learn"!
So, remember, don't cook your board too much!!
I'm having an odd problem with my A500, and while I've seen people with some of the symptoms I'm having, I haven't yet found anyone with all of them. I would appreciate any advice you all may have.
I purchased my A500 on the day it came out, so it's long out of warranty. Everything has been fine with it until two nights ago.
I woke up in the morning to a crashed app alert. I don't get crashed apps often, but it does happen, so I hit ok. A few seconds later I was inundated with crashed app alerts, usually starting with Watchdog (the app killer I use), followed by calendar storage, and then a number of others. At that point, any app I opened would crash. Figuring a good reset would fix it, I turned it off...and it wouldn't turn back on.
I did finally get it to start by holding the volume up and power button.
But that didn't fix the problem. I've discovered that it is somewhat stable if I keep wifi off, but if wifi is on, within minutes everything starts to crash again.
I tried uninstalling some of the apps that crash, but when I restart, the apps are back. It doesn't matter what I uninstall, when I restart, it's back. I tried to factory reset but holding volume up, holding the power button, and continuing to hold volume up while switching the screen lock. The screen gives the "erasing user data" message, but when it loads up, everything is just as I left it. I tried using the android os option to factory reset, but when I hit "erase everything", nothing happens. The button depresses, but nothing happens.
So obviously, I'm a bit perplexed.
I've never rooted it, and I ran an anti-virus scan a few hours before this all happened and it came up clean.
Anyone ever experienced this? Any advice?
Princepapa said:
I'm having an odd problem with my A500, and while I've seen people with some of the symptoms I'm having, I haven't yet found anyone with all of them. I would appreciate any advice you all may have.
I purchased my A500 on the day it came out, so it's long out of warranty. Everything has been fine with it until two nights ago.
I woke up in the morning to a crashed app alert. I don't get crashed apps often, but it does happen, so I hit ok. A few seconds later I was inundated with crashed app alerts, usually starting with Watchdog (the app killer I use), followed by calendar storage, and then a number of others. At that point, any app I opened would crash. Figuring a good reset would fix it, I turned it off...and it wouldn't turn back on.
I did finally get it to start by holding the volume up and power button.
But that didn't fix the problem. I've discovered that it is somewhat stable if I keep wifi off, but if wifi is on, within minutes everything starts to crash again.
I tried uninstalling some of the apps that crash, but when I restart, the apps are back. It doesn't matter what I uninstall, when I restart, it's back. I tried to factory reset but holding volume up, holding the power button, and continuing to hold volume up while switching the screen lock. The screen gives the "erasing user data" message, but when it loads up, everything is just as I left it. I tried using the android os option to factory reset, but when I hit "erase everything", nothing happens. The button depresses, but nothing happens.
So obviously, I'm a bit perplexed.
I've never rooted it, and I ran an anti-virus scan a few hours before this all happened and it came up clean.
Anyone ever experienced this? Any advice?
Click to expand...
Click to collapse
Well, first guess, you have corrupted data somewhere in one of the partitions (/System or /Data). I'm guessing /System as the issue continues after a factory reset, which is "supposed" to wipe the /Data partition.
I'll assume you are stock and un-rooted? Running stock ICS?
The first thing I would do, is while the tab is still running, get your UID number.
First goto Settings/Developer Options, and turn on USB Debugging.
Then go to the Development forum, and check the sticky about how to get your UID number. Should be a simple app you run from your PC while tab is connected. Write it down and save it somewhere (just in case)
Moscow Desire said:
Well, first guess, you have corrupted data somewhere in one of the partitions (/System or /Data). I'm guessing /System as the issue continues after a factory reset, which is "supposed" to wipe the /Data partition.
I'll assume you are stock and un-rooted? Running stock ICS?
The first thing I would do, is while the tab is still running, get your UID number.
First goto Settings/Developer Options, and turn on USB Debugging.
Then go to the Development forum, and check the sticky about how to get your UID number. Should be a simple app you run from your PC while tab is connected. Write it down and save it somewhere (just in case)
Click to expand...
Click to collapse
Thanks for the help!
Yes, I'm running stock, unrooted Android version 4.03.
I've installed blackthund3r's A500 Manager, and it detects my tablet, but it when I try to get my CUPID I get the error "system/bin/sh: su: not found".
I've downloaded "Afterota lite", but hesitate to use it because it says "USE WITH OTA ANDROID SYSTEMS ONLY" and I have no idea if that applies to me or not.
I'm assuming I'm ok to use it, but I don't want to take any chances.
Princepapa said:
Thanks for the help!
Yes, I'm running stock, unrooted Android version 4.03.
I've installed blackthund3r's A500 Manager, and it detects my tablet, but it when I try to get my CUPID I get the error "system/bin/sh: su: not found".
I've downloaded "Afterota lite", but hesitate to use it because it says "USE WITH OTA ANDROID SYSTEMS ONLY" and I have no idea if that applies to me or not.
I'm assuming I'm ok to use it, but I don't want to take any chances.
Click to expand...
Click to collapse
Since the 17th I have exactly all the same problems that you describe!!! I also have the same configuration. Did you may have also the following:
Current Image Version:
Acer_AV041_A500_1.062.00.EMEA_DE?
I did not find a solution so far. But I was able to recover the CUPID - not with the A500 Manager (A500Manager1.1.1) - that did not work. But by retrieving the acer_cpu_id from a file. I did it with adb tools and found it here:
/sys/firmware/fuse/acer_cpu_id
I have been able to get into APX mode (with blackthund3r_A500_APX_Flash_Tool_v0.4.1), but could not flash a new image. I could not get root (with ICS Root 7.2.0), by any method that I tried.
By every operation that I do - it always starts with the same app's and version that I had before. It seems like an "read only" system.
Hope you could solve that problem in the mean time.
Mratlan
Mratlan said:
Since the 17th I have exactly all the same problems that you describe!!! I also have the same configuration. Did you may have also the following:
Current Image Version:
Acer_AV041_A500_1.062.00.EMEA_DE?
I did not find a solution so far. But I was able to recover the CUPID - not with the A500 Manager (A500Manager1.1.1) - that did not work. But by retrieving the acer_cpu_id from a file. I did it with adb tools and found it here:
/sys/firmware/fuse/acer_cpu_id
I have been able to get into APX mode (with blackthund3r_A500_APX_Flash_Tool_v0.4.1), but could not flash a new image. I could not get root (with ICS Root 7.2.0), by any method that I tried.
By every operation that I do - it always starts with the same app's and version that I had before. It seems like an "read only" system.
Hope you could solve that problem in the mean time.
Mratlan
Click to expand...
Click to collapse
I'm sorry to hear that you have the same problem, though I'm kind of glad I'm not alone here.
My Image Version is: Acer_AV041_AA500_RV05RC01_PA_CUS1
"Read only" is a great description of this, in fact, I'm received errors indicating that it's a read only file when trying to resume my previous place in a video that I have saved on my SD card.
So you have not been able to get it to factory reset using external tools either?
Princepapa said:
I'm sorry to hear that you have the same problem, though I'm kind of glad I'm not alone here.
My Image Version is: Acer_AV041_AA500_RV05RC01_PA_CUS1
"Read only" is a great description of this, in fact, I'm received errors indicating that it's a read only file when trying to resume my previous place in a video that I have saved on my SD card.
So you have not been able to get it to factory reset using external tools either?
Click to expand...
Click to collapse
Correct. I could not do:
- a factory reset
- root the tablet
- use recover to make a downgrade
I try to write a new image with blackthund3r_A500_APX_Flash_Tool_v0.4.1. But it is very slow.
Hope we get some good idea's what else we could try.
Mratlan
Mratlan said:
Correct. I could not do:
- a factory reset
- root the tablet
- use recover to make a downgrade
I try to write a new image with blackthund3r_A500_APX_Flash_Tool_v0.4.1. But it is very slow.
Hope we get some good idea's what else we could try.
Mratlan
Click to expand...
Click to collapse
How slow is "very slow"? If it works, I'd be willing for it to take a long time...unless "very slow" means a few percent per day.
Princepapa said:
How slow is "very slow"? If it works, I'd be willing for it to take a long time...unless "very slow" means a few percent per day.
Click to expand...
Click to collapse
Well, I do not know. I had to start again, because I forgot to disable energy saver. Hence during the process there was a stop and I was forced to start again. So my estimation would be several hours (4-8h?).But I’m not sure if it will work.
If you try it again, please let me know how it goes. I probably won't be able to work on mine again until this weekend. I'm also going to continue to research other solutions, though it seems not many people have had this problem, and not many people have ideas for solutions...
Princepapa said:
If you try it again, please let me know how it goes. I probably won't be able to work on mine again until this weekend. I'm also going to continue to research other solutions, though it seems not many people have had this problem, and not many people have ideas for solutions...
Click to expand...
Click to collapse
The flash process (with blackthund3r_A500_APX_Flash_Tool_v0.4.1) did not come to an end.
I tried the following method as descriped here:
http://forum.xda-developers.com/showthread.php?t=2450119&highlight=formatting+partition+bct+failed
But without sucess - but at least I know now a bit more detail about the problem:
****************************************************************
* Before executing, be sure to delete recovery-from-boot.p *
* from /system to ensure recovery will stick *
****************************************************************
****************************************
* Reboot your tablet into APX mode *
****************************************
Generate your SBK with your CPUID from here :
http://vache-android.com/v1/index.php?site=sbk
Enter your SBK:0xCFA21E00 0xA8838901 0x47CA6D03 0xXXXXXXX
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
chip uid: 0x037c6187426094d7
macrovision: disabled
hdcp: enabled
sbk burned: true
dk burned: true
boot device: emmc
operating mode: 4
device config strap: 0
device config fuse: 0
sdram config strap: 0
sending file: flash.bct
- 4080/4080 bytes sent
flash.bct sent successfully
odm data: 0xb00d8011
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: bootloader.bin
| 714409/714409 bytes sent
bootloader.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
setting device: 2 3
creating partition: BCT
creating partition: PT
creating partition: APP
creating partition: EBT
creating partition: GP1
creating partition: SOS
creating partition: LNX
creating partition: CAC
creating partition: MSC
creating partition: FLX
creating partition: AKB
creating partition: UDA
creating partition: GPT
Formatting partition 2 BCT please wait.. FAILED!
command failure: create failed (bad data)
bootloader status: partition table is required for this command (code: 8) messag
e: nverror:0x4 (0x4) flags: 0
Drücken Sie eine beliebige Taste . . .
Maybe you check this on your tablet as well.
HI all,
Sorry to hear that you have problem with your tab!!
happy to hear that you have exactly the same problem than me and others (see this http://forum.xda-developers.com/showthread.php?t=1790958)
I had made all possible test that i can
AFterota, Blackthun3er ,method, badsectros,fastboot, nvflash command......all failed to write the tab!!!!
gerardpuducul said:
HI all,
Sorry to hear that you have problem with your tab!!
happy to hear that you have exactly the same problem than me and others (see this http://forum.xda-developers.com/showthread.php?t=1790958)
I had made all possible test that i can
AFterota, Blackthun3er ,method, badsectros,fastboot, nvflash command......all failed to write the tab!!!!
Click to expand...
Click to collapse
Uhhh, that sounds not very good. At the moment I try EUU tool, but it seems also not working. So, did you give up on the tablet?