Solved - 7" model 51624 won't boot after firmware update

[gcb]

So guess that is that then, just telephoned Storage Options who were no help what so ever, said that would only swap the product out if it was still under warranty, but as it was second hand I don't have the original receipt and guess it is over a year old anyway!

Tablet goes to now being an expensive door stop as unable to connect to it via ADB, it's listed in device manager but I can't connect to it, if debugger mode on the device isn't set will I still see it in device manager and if I do why can't I connect to it?

There might be hope still - Sounds like you might not have the drivers setup right for the tab. You need to see "Android Composite ADB Device" in device manager. Follow the 2nd post in this thread here to set up the drivers correctly.

I have already followed this, I can see the device listed in device manager but I cannot adb shell or adb device to it, says device not found.

[suggsy89]

can you still get to recovery?

No sadly not

Then you will first need to get adb working by following the above post by Charlie

[Charlie]

So guess that is that then, just telephoned Storage Options who were no help what so ever, said that would only swap the product out if it was still under warranty, but as it was second hand I don't have the original receipt and guess it is over a year old anyway!

Tablet goes to now being an expensive door stop as unable to connect to it via ADB, it's listed in device manager but I can't connect to it, if debugger mode on the device isn't set will I still see it in device manager and if I do why can't I connect to it?

There might be hope still - Sounds like you might not have the drivers setup right for the tab. You need to see "Android Composite ADB Device" in device manager. Follow the 2nd post in this thread here to set up the drivers correctly.

I have already followed this, I can see the device listed in device manager but I cannot adb shell or adb device to it, says device not found.

I was just going by one of your earlier posts stating this:-

Well I have tried included downloading the Android SDK and tools and I am stuck, the device is recognised in device manager as Android ADB interface but when I run adb shell all I get is error:device not found - looks as if i've got something wrong?

You need to see "Android Composite ADB Device" in device manager, you say you are seeing "Android ADB interface" - Those of two different things!

[gcb]

I can get both by choosing a range of drivers but still cannot get to the Scroll using ADB, my question is would it still appear in device manager if the debugging had been turned off?

[gcb]

Here's proof in device manager

[Charlie]

So it looks like you have the drivers installed correctly, so that is good.

I can get both by choosing a range of drivers but still cannot get to the Scroll using ADB, my question is would it still appear in device manager if the debugging had been turned off?

No it won't AFAIK, so you won't be able to run ADB commands. I am sure that the scroll you have you can put it into fastboot mode where you could do fastboot flash commands to flash the recovery (but I can not remember how to get it in to fastboot mode (think you have to boot into bootloader), sorry - Maybe someone else knows?)

Example code:

Code: Select all

fastboot flash recovery recovery.img
fastboot boot recovery recovery.img


[gcb]

Interestingly enough the 2nd script which uses fastboots successfully burns the image and reboots the device but it is still stuck at the white storage options screen so maybe I just need the correct image ?

[suggsy89]

Cool clockworkmod here we come

[gcb]

I think that was what I tried downloaded the zip ran the first script which failed the second script worked but after the reboot goes no further tried to get into recovery but still cannot are there any other fastboot scripts I can try ?

[Charlie]

Interestingly enough the 2nd script which uses fastboots successfully burns the image and reboots the device but it is still stuck at the white storage options screen so maybe I just need the correct image ?

Are you talking about the 2nd script by Warpedflash for clockworkmod? - If so you could try a stock recovery.img in that folder and make sure the stock recovery image file is called exactly this => recovery.img and use this 2nd batch file instead --> here - Good luck

P.S. You could flash any recovery image you like with my modified version of the script, as long as you call the image recovery.img - and have it in the same folder as the script.