Scroll Tablet PC | Scroll Excel Tablet Forum

Hi all,
My 1st post here, looks like a great forum!

Anyhow really need you help.....
I purchased a scroll excel 7" capacitive for my partners birthday a few days ago and I beleieve it was on OS 2.3.4 but can't remeber any other build numbers. I wanted to gain root acsess and tried z4root as per forum guide, it did say it was already rooted but I believe I couldn't get full rw accsess so decided to uninstall root via z4root and then rerun choosing permenant root, after z4root did its thing it closed by itself and the tablet appeared to be fine...
Shut excel down, rebooted and now stuck at balloon logo, i have tried factory wipe from default recovery mode (power & menu) but its still stuck on balloon
I do have adb accsess but not sure about root permissions now after what happened???
Can anyone provide me with a stock firmware update.zip or maybe a install-recovery.sh file that could be copied back via adb or sdcard, or is there something else that needs to be done or is it curtains for me ???
Anyhow I really hope someone can help as the other halfs birthday is on 11th, damn i wish i could stop fidlling just cant help my self lol!

Thanks

Hi & welcome to the forum,

The Excel, is pre-rooted, so z4root messed up your tab, as that guide is for a different Scroll. Good news is, this should be fixable as you say you have adb access . You will need to flash CWM5 & then a clean backup. (Both available on this forum, just need to make sure you do the right ones.)

I don't have the time tonight, to guide you through it, but can do tomorrow.

Ah m8, brilliant news, yes if u could guide me through that would be great
Thanks for your time look forward to reply....

Hi,

The full 'how to' & files for CWM5 is here -->

viewtopic.php?f=48&t=1800&start=40&hilit=CWM5

The instructions in the 'how to' are for doing it via terminal - so via adb is slightly different: (from what I remember it's this)

Code: Select all


adb remount

adb push install-recovery.sh /data/
adb shell chmod 755 /data/install-recovery.sh
adb push recovery.cpio /data/
adb shell /data/install-recovery.sh


Here is the folder(s) with the files needed (a full clean image) -->

http://dl.dropbox.com/u/18307166/clockworkmod.zip

You need to unzip it and put it on an external sdcard, put this back into the Excel, make sure you keep the folder structure as it is. Like so,

clockworkmod/backup/Excel-2.3-clean/ <here will be the the 6 files needed>

Then once you have CWM5 on the Excel - boot into the new recovery and restore a clean back up - (here just select the folder 'Excel-2.3-clean'

TIP: Make sure you have the power adapter in and on when doing this - as you don't want to lose power when flashing the recovery.

Hi Charlie,
Thanks for the guides, i have downloaded all relevant files and put install-recovery.sh & recovery.cpio into the adb folder, adm remounts fine but trying to push install-recovery.sh and recovery.cpio fails due to read-only file system
Do you know of a command to gain r/w acsess?
I fear z4root and factory resets may have screwed up the tab beyond repair....I really hope not!

doncyp wrote:Hi Charlie,
Thanks for the guides, i have downloaded all relevant files and put install-recovery.sh & recovery.cpio into the adb folder, adm remounts fine but trying to push install-recovery.sh and recovery.cpio fails due to read-only file system
Do you know of a command to gain r/w acsess?
I fear z4root and factory resets may have screwed up the tab beyond repair....I really hope not!

Ok, sounds like you have a similar issue like @blueegale69 had (but we fixed that - in the end!) maybe have a look at the last several pages from this thread. --> viewtopic.php?f=48&t=1978

Basically he use my modified recovery.sh script --> http://dl.dropbox.com/u/18307166/be2/in ... ecovery.sh instead and these new adb instructions (see below) to push the 2 files to get CWM5 on - to the cache partition instead, where there should be no r/w issues. (but his was to do with a bad busybox app install)

Code: Select all


adb remount

adb push install-recovery.sh /cache/
adb shell chmod 755 /cache/install-recovery.sh
adb push recovery.cpio /cache/
adb shell /cache/install-recovery.sh


Hopefully this can get fixed (just not going to be easy), as long as z4root has not done to much damage.

UPDATE: - If you get an error when doing the last line of the above (adb shell /cache/install-recovery.sh) - it depends what the error is, as one type of error, does mean it worked. A different one will mean, we need to do this another way - so report back any error messages at this stage.

Hi charlie,
Thanks for being patient with me, i'm at work right now but will do what u ask and report back tonight.

Thanks

Hi Charlie,
OK I have done what you asked and the result is :

C:\ADB>adb remount
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
remount succeeded

C:\ADB>adb push install-recovery.sh /cache/
25 KB/s (410 bytes in 0.015s)

C:\ADB>adb shell chmod 755 /cache/install-recovery.sh

C:\ADB>adb push recovery.cpio /cache/
5016 KB/s (6411264 bytes in 1.248s)

C:\ADB>adb shell /cache/install-recovery.sh
[: not found
mkdir failed for /cache/recovery, File exists
mke2fs: not found
busybox: not found
busybox: not found
rmdir failed for /cache/recovery, Directory not empty

C:\ADB>

where to go from here?

Ok, you are nearly there.

You could try to boot into recovery, but I doubt that will work at the mo' (try to tho'), otherwise it seems that you need to install busybox (needs to be the correct version), this can be done via adb, but I don't know how to do that, but @blueeagle69 did it some how (see this rather long thread viewtopic.php?f=48&t=1978)

Once you have that - redo, the steps you did - then you should then have CWM5 - then you can do a restore.


UPDATE: I have sent a PM to blueegle69 - to see if he has time to help you get busybox on.

I'm here.
Have you got the Busybox version that is known to work?

If not, get it from here.
http://dl.dropbox.com/u/54025484/busybox first


As already mentioned, using ADB, navigate to /system/bin
Type "ls busybox" to make sure it's there.

Update.

Look in /system/xbin too. It seems to like living there as well