You are calling an EGLXL102B... which one is that? Ok... been to ematic, it is the 10" version of the 25bl I had...
Do all the buttons work? (gotta ask!)
You say it seemed to do the 'factory reset' correctly?
Do it again but do not touch the DATA this time... see if it behaves the same.
What...
1st off, you should be able to use a USB mouse to connect/move around with...
Once you can get that far, see if you have a Factory reset ability, and start with that...
Hope that helps! :D
You keep saying this...
So, what happened '3 days ago' that has changed the way the wifi/router is operating that could possibly affect Android devices? A power failure that caused it to use 'default' settings that are inconsistent with the original connections? A software update that did...
It is certainly worth a try. I certainly believe the good tablet is going to be the key to fixing the other!
You may want to try doing the mount w/o the -t.. mount /dev/nande /data...
:D
Welcome to the Wonderful World of the Chinese Clone! :p
I have one of these P001s (currently 'brain-dead'), and have multiple others that LOOK the same but are NOT. Included in this variety is a lack of incentive to the manufacturers to create new versions for something that many folk would...
What would ALSO be nice would be for manufacturers to use the same COLOR for these functions...
I have 2 'SuperPAD's, one a vimicro and the other an A10... the vimicro glows GREEN when CHARGING, and NOTHING when done. The A10, on the other hand, has the 'charging display when off' function which...
Sounds like the LIQUID CRYSTAL has leaked out thru the cracks... as it does when the screen gets cracked.
Unfortunately the only thing you can do is replace the screen/tablet or POSSIBLY connect it to an external screen if it is capable...
:(
Just for the record...
Does anyone know what 'error %3' supposedly MEANS?
Now that I have an AllWinner-based (BC1003) tablet, I'd like to KNOW if/when it gets 'worked over', exactly WHAT failed... :cool:
I would like to suggest that you attempt a
fsck /dev/block/nande
on the faulty tablet, and see if it is able to clean it up...
if not, attempt to copy the /dev/block/nandg (recovery partition device) from the good tablet to an external TF card file as I posted before, and then attempt to copy...
Once you're rooted you can delete them yourself w/o risking the install of a ROM that isn't ready.
Do some searching for threads about using Terminal Emulator, SU, remounting /system and you'll be about ready to 'clean house'.
:D
The subject of rooting may be a bit early in the game, but there is a good chance it is rooted already...
Install Terminal Emulator and once running, type 'su'.
If it changes the prompt or otherwise doesn't whine and complain then it already has it.
:D
EDIT:
When you connect it to the PC, does...
Yes... I keep forgetting about 'mount'. :rolleyes:
That is the best place to find what devices are connected to system and data (and recovery)!
(I say that because Ive not used the busybox version of df...)
I suspect that YOUR recovery is as hobbled as mine originally was... but you might be...
You would need to ask them, I'd think. :p
But seriously, as I understand KitKat is not even 'officially' out yet, so it will be a while before even HP gets to play with it.
Whether or not the Slate 7 can upgrade to the newer version(s) will depend upon cpu speed, memory capacity, storage...
So, YOU installed a busybox or it just came with one?
If BOTH of the units are in fact the same, you might want to attempt copying the DATA partition to a file and then load it up on the broken one with ADB...
you may need to 'df' to find out which device the data is on, then 'cat...