Scroll 7" Post firmware update brick [Now Working]

[Tazmaniandevil]

Evening all.
Here's my story.
I was having problems with wifi dropping out on my Scroll 51624, so downloaded a firmware update from Storage Options.
This effectively killed the tablet. Booooooo!

I discovered from this forum how to boot into recovery, which I did.
I downloaded the stock images detailed in this thread.
Downloaded the tools from there, and followed the instructions.
Plugged tablet into laptop and installed drivers. Now have Android Composite ADB Device in device manager.

Strike 1 - adb shell returns error: device not found
Strike 2 - unable to download the Bobmcdermott images to try those. (404 errors)
Strike 3 - yes it gets worse.....
Using fastboot.exe I used the following lines:

fastboot erase boot
fastboot erase recovery
fastboot erase system
fastboot flash recovery mtd6_recovery.img

so far so good.

fastboot flash boot mtd0_boot.img

cool.

fastboot flash system mtd2_system.img

FAILED (remote: data too large)

Now..... Can't get into recovery...... All I get is white screen with Storage Options logo on it.

I would be grateful for any suggestions, other than horse it out the nearest window.

I didn't note any of the details from the working OS, so have no idea which firmware revision it had originally.

[Trashcooky]

Not sure where you go from here but could you possibly tell SO that you applied their firmware update for this tablet and it bricked it, so what are they going to do about it? You never know..... but I won't hold my breath.

Edit I just followed your tracks and as far as I can tell your Scroll was originally 2.1.
I don't know anything about the old post with updates that you found casue they were before I came on this forum but I note that the update files state 1.02 - assuming this is the OS then it looks like you have tried flash a completely wrong ROM for your tablet. Unfortunately, I don't have the skills to help you and it seems most of the Devs are busy elswhere apparently. Lets hope someone with the know-how can tell you if the situation is recoverable and if so how - but I have a suspicion that you now have an expensive paperweight.

[Tazmaniandevil]

I didn't buy it new, so I suspect SO would chase me.

The Android OS version is/was 2.1, but think the firmware version is a different number. Hopefully someone will pop along with a pointer or 2. I'm missing my bedtime reading. I suppose I'll have to resort to council books until I get it figured out.

[Mitre]

the 1.02 is the file for 1st gen scrolls the 102s was for the same tablet with a samsung chipset i woul try to push clockwork mod to the device via adb then instaal cyanogen7 from this forum

[Tazmaniandevil]

I would try this, but can't get adb to connect to the tablet. It returns returns error: device not found.
Would I be correct in my assumption that adb only works in recovery mode?

In device manager, the device is listed as "Android Composite ADB Device"
I tried using fastboot boot recovery-clockwork-scroll.img and I got a white screen with interference. Interestingly, when I tried fastboot boot mtd6_recovery.img it returned an error about the image being incomplete. (or something along those lines)

I'm currently at work, so won't be able to have another bash until after 7PM.

If I can get fastboot to get into recovery, am I correct in assuming adb should work?

Thanks for the replies though. It's possible that I'm just about stupidly dangerous enough to get my head round this stuff after all.

edit: Don't know if it means anything, but it says "Telechips" on one of the labels on the back.

[Trashcooky]

When you connect the Scroll to your PC via usb and get the error "no device found", go to device manager on the PC and see if you have any exclamation marks under portable devices - if you have, then you need to find a suitable windows usb driver for your device.
(also, please forgive if this is patronising, but make sure usb debugging is enabled on your tab)

I have had period of similar problems in not being able to see my device when usb connected. However, during my searches to sort this out I came across a program which although still in beta, seems very powerful as it was able to interrogate my tablet from windows even without my slecting usb connect on the tablet. This may possibly at least give you a window to explore the files on the tablet. You can download it here: https://scrolltabletforum.sevo.uk/site/viewtopic.php?f=20&t=2757&p=23157#p23157

Good luck.

[Tazmaniandevil]

Cheers for this, I will have a go with it later. (I saw the link when I was trawling through stuff yesterday but was a bit scared to try it.)
Not at all patronising Chief, remember I'm a complete Android novice. I checked the device manager for blobs, and installed the drivers from the tools_and_drivers.zip file I downloaded from Evilbobbins. These drivers have worked for others, so I'm kinda assuming they will be OK for mine too.

the 1.02 is the file for 1st gen scrolls the 102s was for the same tablet with a samsung chipset i woul try to push clockwork mod to the device via adb then instaal cyanogen7 from this forum

Is there an alternative location for this? The androtab link on your thread here doesn't appear to be working.

Thanks

Tom

[Mitre]

Aagh fun has i think stopped developing these tablets so i will see if i have it and get you a link no eta

Sent from my GT-I9100 using Tapatalk

[Tazmaniandevil]

Cheers. I'd appreciate that. No rush, I'm using this as a learning curve.

[Tazmaniandevil]

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