Boot-Up/Factory Reset Problem
- Thread starter Bosco
- Start date
Ricky405jr
Member
- Feb 23, 2013
- 255
- 23
When you type
adb shell
su
do you see $ or a # ?
adb shell
su
do you see $ or a # ?
Ricky405jr
Member
- Feb 23, 2013
- 255
- 23
oki that means you still have a chance fixing it.
So how did you install CWM? Cos as vampirefo ​stated that can fix your problem.
So how did you install CWM? Cos as vampirefo ​stated that can fix your problem.
Bosco
Member
- Oct 12, 2013
- 23
- 3
- Thread starter
- #20
I found a method here;
CWM 6.0.2.8 for Allwinner A10 & A13 Tablets - v2a - xda-developers
Specifically I did this, from the adb shell;
From a Running System: Unzip the file and copy recovery.img and install-recovery.sh to your internal or external SD card.
Next, either run "adb shell" or open the Terminal app, then change the directory to where you stored the files.
If you're using Terminal, start by running "su" to get root access (you may already have it if using adb).
Now, type in "sh install-recovery.sh" then press Enter. Messages will appear telling you whether it succeeded or failed.
CWM 6.0.2.8 for Allwinner A10 & A13 Tablets - v2a - xda-developers
Specifically I did this, from the adb shell;
From a Running System: Unzip the file and copy recovery.img and install-recovery.sh to your internal or external SD card.
Next, either run "adb shell" or open the Terminal app, then change the directory to where you stored the files.
If you're using Terminal, start by running "su" to get root access (you may already have it if using adb).
Now, type in "sh install-recovery.sh" then press Enter. Messages will appear telling you whether it succeeded or failed.
- Nov 8, 2011
- 3,836
- 1,394
Post the output of busybox df -h
Sent from my SPH-D710 using Android Tablet
Sent from my SPH-D710 using Android Tablet
Bosco
Member
- Oct 12, 2013
- 23
- 3
- Thread starter
- #22
Here's the output from the faulty tablet;
busybox df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 407.1M 44.0K 407.1M 0% /dev
tmpfs 407.1M 0 407.1M 0% /mnt/asec
tmpfs 407.1M 0 407.1M 0% /mnt/obb
/dev/block/nandd 252.0M 229.3M 22.7M 91% /system
/dev/block/nandh 126.0M 4.0M 121.9M 3% /cache
/dev/block/vold/179:1
29.8G 24.8G 5.0G 83% /mnt/extsd
/dev/block/vold/93:64
13.2G 4.4G 8.8G 33% /mnt/sdcard
/dev/block/vold/93:64
13.2G 4.4G 8.8G 33% /mnt/secure/asec
And for comparison, here's the output from an identical tablet, (actually this one has only 8GB ram), that's booting correctly.
busybox df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 407.1M 44.0K 407.1M 0% /dev
tmpfs 407.1M 0 407.1M 0% /mnt/asec
tmpfs 407.1M 0 407.1M 0% /mnt/obb
/dev/block/nandd 252.0M 229.3M 22.7M 91% /system
/dev/block/nande 1.2G 358.1M 823.0M 30% /data
/dev/block/nandh 126.0M 4.0M 121.9M 3% /cache
/dev/block/vold/179:1
29.8G 22.0G 7.8G 74% /mnt/extsd
/dev/block/vold/93:64
5.8G 433.7M 5.4G 7% /mnt/sdcard
/dev/block/vold/93:64
5.8G 433.7M 5.4G 7% /mnt/secure/asec
busybox df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 407.1M 44.0K 407.1M 0% /dev
tmpfs 407.1M 0 407.1M 0% /mnt/asec
tmpfs 407.1M 0 407.1M 0% /mnt/obb
/dev/block/nandd 252.0M 229.3M 22.7M 91% /system
/dev/block/nandh 126.0M 4.0M 121.9M 3% /cache
/dev/block/vold/179:1
29.8G 24.8G 5.0G 83% /mnt/extsd
/dev/block/vold/93:64
13.2G 4.4G 8.8G 33% /mnt/sdcard
/dev/block/vold/93:64
13.2G 4.4G 8.8G 33% /mnt/secure/asec
And for comparison, here's the output from an identical tablet, (actually this one has only 8GB ram), that's booting correctly.
busybox df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 407.1M 44.0K 407.1M 0% /dev
tmpfs 407.1M 0 407.1M 0% /mnt/asec
tmpfs 407.1M 0 407.1M 0% /mnt/obb
/dev/block/nandd 252.0M 229.3M 22.7M 91% /system
/dev/block/nande 1.2G 358.1M 823.0M 30% /data
/dev/block/nandh 126.0M 4.0M 121.9M 3% /cache
/dev/block/vold/179:1
29.8G 22.0G 7.8G 74% /mnt/extsd
/dev/block/vold/93:64
5.8G 433.7M 5.4G 7% /mnt/sdcard
/dev/block/vold/93:64
5.8G 433.7M 5.4G 7% /mnt/secure/asec
Last edited:
- Nov 8, 2011
- 3,836
- 1,394
Yes data not mounted, needs factory reset, you need to dump both recoveries, my guess the CWM you Installed isn't for your tablet, so the tablet can't boot into recovery.
Sent from my SPH-D710 using Android Tablet
Sent from my SPH-D710 using Android Tablet
Bosco
Member
- Oct 12, 2013
- 23
- 3
- Thread starter
- #24
I'm using the same version of CWM on the identical tablet and it's working fine. Must be another reason why the faulty tablet can't boot into recovery?
Sounds like I'm running out of options.
Is there any way to perform the necessary factory reset remotely using a PC?
Also, I've discovered Root Explorer will install on the faulty tablet despite the data partition not being mounted. I could try copying the data folder from the healthy tablet onto an ext-sd card then copy it over the data folder on the faulty tablet. Or would this make the tablet freeze and never work again?
Sounds like I'm running out of options.
Is there any way to perform the necessary factory reset remotely using a PC?
Also, I've discovered Root Explorer will install on the faulty tablet despite the data partition not being mounted. I could try copying the data folder from the healthy tablet onto an ext-sd card then copy it over the data folder on the faulty tablet. Or would this make the tablet freeze and never work again?
tpaine
Senior Member
- Aug 18, 2012
- 525
- 130
Did you backup the original recoveries? If so, you could compare the 2. Even though its the same brand, it is a different model. There could be (and it seems likely at this point) different recoveries.
You likely can't copy data using root explorer because the files won't copy until the partition is mounted.
You likely can't copy data using root explorer because the files won't copy until the partition is mounted.
Bosco
Member
- Oct 12, 2013
- 23
- 3
- Thread starter
- #26
No, I don't have any recovery backups. To be honest until my Son's went wrong I was unaware of such things. 
I believe both tablets are the same model. He ordered the same one as me but paid a supplement for an extra 8GB of ram.
Just re-installed Root Explorer on the faulty tablet and was able to copy a folder from within /data to the ext-card.
May work in reverse but would replacing the entire data folder using an app running on the same tablet cause it to freeze?
I believe both tablets are the same model. He ordered the same one as me but paid a supplement for an extra 8GB of ram.
Just re-installed Root Explorer on the faulty tablet and was able to copy a folder from within /data to the ext-card.
May work in reverse but would replacing the entire data folder using an app running on the same tablet cause it to freeze?
Ricky405jr
Member
- Feb 23, 2013
- 255
- 23
well it doesn't mean that when you order a tablet from the same supplier you get the same each time. Looking at the tab's are the same but somethings might be changed in the hardware. You can check that with the build.prop date's on both the tablet's to know for sure.
tpaine
Senior Member
- Aug 18, 2012
- 525
- 130
Yeah, I take your point.
It's weird the data partition doesn't appear to be mounted but I can access the data folder with Root Explorer. Or is that what you'd expect?
You can read it, but can you write to it? ( if its not mounted, you cant)
- Nov 8, 2011
- 3,836
- 1,394
Yeah, I take your point.
It's weird the data partition doesn't appear to be mounted but I can access the data folder with Root Explorer. Or is that what you'd expect?
The tablet is just creating a temp data on each boot, root explorer sees that, but not your real data partition.
Sent from my SPH-D710 using Android Tablet
