Scroll 7" Post firmware update brick [Now Working]

[Trashcooky]

So long as you have a copy of the image you want to flash then copy this to your Ext SDcard, or failing this and if there is room onto the tablet memory space and then flash the image using either CWM or Livesuite.

[Mitre]

Progress! Sort of. Many thanks to Bobmcdermott I downloaded the 102s stock images. Managed to run
fastboot flash boot mtd0.img
fastboot flash recovery mtd6.img

I can now boot into recovery menu. Ya dancer!

Question is, how do I get the rest of the images back onto my scroll?
Device manager has Android Composite ADB Interface and drives F: to J: under portable devices

adb shell mount system returns: - exec '/system/bin/sh' failed: No such file or directory (2) -

I tried setting up droid explorer on my laptop, but the install failed.

Is there a way of extracting the .img files? It may be possible to push the individual files over using adb

have pm'd you a link to some files you look like youre gettin in the swing of it
try "android commander" for you laptop

[Tazmaniandevil]

Thanks for this. I will give these a bash. At least I know I can get back to stock recovery now if it all goes horribly wrong again.

I downloaded an older (standalone) version of droid explorer which fired up no problem. Unfortunately, although it said it was connected to the device it did nothing. Even the reboot command did nowt.

When I tried to send the "system" image to the tablet using adb, it gave an "image too big" type message. I'm assuming that it is able to copy the .img file over, but there is insufficient space available to unpack it too. This happens when flashing from laptop or sdcard.

While I accept this happening is my fault entirely, it would be useful if SO specified on their website that there are different versions of the same tablet. From what I have seen through my research, I'm not the first person this has happened to.

I will continue to plug away at this. If I get mine back up and running, then pretty much anyone can.

I tried renaming the original zip file for system.img to update.zip and applying via recovery, but this gave an error that certain files were missing. On examination of the update.zip file I believe if I can extract the contents of the .img file, I may be able to work out what is required and cook something up.
Nothing ventured, nothing gained.

[Tazmaniandevil]

I've been faffing around during my lunch break looking at extracting the system.img file.
I downloaded unyaffs and tried running it against the image file. Yep, you guessed it, I got an error:
2 [main] unyaffs 7704 _cygtls::handle_exceptions: Exception: STATUS_ACCESS_VIOLATION
1866 [main] unyaffs 7704 open_stackdumpfile: Dumping stack trace to unyaffs.exe.stackdump

(the stack dump file is empty)

Back to the drawing board.
This is turning into an epic saga. Hopefully it will end at some point before someone takes out a contract on me.

[Trashcooky]

Sorry you are still stuck - but it all makes for interesting reading. Hope you get there in the end.

[Tazmaniandevil]

OK, so Android Commander finds the device, then just sits with a repeating scroll bar. Is there another way of accessing the android file system?

When I type adb shell I get: - exec '/system/bin/sh' failed: No such file or directory (2) -
Now I remember reading somewhere there is an issue with the system partition filling up and corrupting the data. I have a funny feeling that this is what has happened here.
I thought that "adb shell -w flash_image system /sdcard/mtd2.img" would wipe the system partition first, but it returns the same error.

The recovery screen allows formatting data and cache. Is there a way to format the system partition either from the device, or from a command shell.

Also, does anyone have a copy of clockwork recovery for 8k scroll?

Also, also.... if anyone needs the 1.02s stock images I have hosted them on my work webspace.

The link is over there --------->

[Trashcooky]

OK, so Android Commander finds the device, then just sits with a repeating scroll bar. Is there another way of accessing the android file system?

When I type adb shell I get: - exec '/system/bin/sh' failed: No such file or directory (2) -
Now I remember reading somewhere there is an issue with the system partition filling up and corrupting the data. I have a funny feeling that this is what has happened here.
I thought that "adb shell -w flash_image system /sdcard/mtd2.img" would wipe the system partition first, but it returns the same error.

The recovery screen allows formatting data and cache. Is there a way to format the system partition either from the device, or from a command shell.

Also, does anyone have a copy of clockwork recovery for 8k scroll?

Also, also.... if anyone needs the 1.02s stock images I have hosted them on my work webspace.

The link is over there --------->

Can't help you with adb but you said in one of your posts that you had sucessfully installed Droid explorer - if you still have this installed it may be interfering with Android commander as they both use the same system processes and this may upset Windows if a process is already running in one package (Droid Explorer runs processes on Windows start-up) try unistalling Droid Explorer if you are going to use Android Commander and see if this helps.
As I asked in a previous post, have you got usb debugging enabled in the tab system settings? you do need this otherwise Android Commander will never see the tablet.

[Tazmaniandevil]

well, debugging was switched on before the update killed the damned thing. I removed droid explorer when it didn't do anything.
Is it possible to check whether debugging is on/off from commandline?

OK Scratch that. Debug mode is on by default in CWM, but apparently not in stock recovery. That will be why nowt works.

So that brings me back to finding an 8k version of cwm, cos the 4k version don't work.

[BobC]

OK, so Android Commander finds the device, then just sits with a repeating scroll bar. Is there another way of accessing the android file system?

When I type adb shell I get: - exec '/system/bin/sh' failed: No such file or directory (2) -
Now I remember reading somewhere there is an issue with the system partition filling up and corrupting the data. I have a funny feeling that this is what has happened here.
I thought that "adb shell -w flash_image system /sdcard/mtd2.img" would wipe the system partition first, but it returns the same error.

The error messages seem to be saying that the Tablet cannot locate the standard shell program. Without this most stuff is going to fail as it is the main command interpreter and what adb is trying to use to execute Android commands. If you can't use adb to talk to the tablet Android Commander and similar GUI front-ends are not going to work either.

BobC

[Tazmaniandevil]

The error messages seem to be saying that the Tablet cannot locate the standard shell program. Without this most stuff is going to fail as it is the main command interpreter and what adb is trying to use to execute Android commands. If you can't use adb to talk to the tablet Android Commander and similar GUI front-ends are not going to work either.

Bum. I thought that might be the case. Looks like getting a version of CWM for the 8k tablet is my only hope. That or "Creating an 8K CWM For Dummies" book, although it can't be in kindle format until I get the scroll back up & running......

Catch 22.