Database Info

Need help preparing Xoom for official updates

Hey folks,
I´ve ran my MZ601 xoom on EOS builds over the last 1,5 years.
Obviously its unlocked and rooted. Currently its running CWM Recovery 4.0.0.4
Now I want to go back to stock to install the latest official updates to get the updated drivers for the UMTS radio/modem module.
After that I want to unlock and get root again to use any of the lastest custom Roms again.
Switching to a touch based recovery would be nice too.
I surfed around a bit and I´m rather confused which steps I need to perform in order to do this.
I guess I need to remove root and lock the bootloader again before I can install official updates ?
Could someone please toss me in the right direction? Maybe some step-by step list?

You'll presumably want Build H.6.1-38-1 for Retail Europe from here.
Returning to stock:
Extract the files from the link above to your adb/fastboot directory if you have one. If you don't have one I've uploaded them for you here.
Connect your Xoom to your PC then open command prompt from your adb folder. (Hold shift > right click on adb-fastboot folder > click Open Command Window Here)
Type adb devices and hit enter, if no devices are listed then ensure USB debugging is switched on in Settings > Development > and tick USB Debugging, then try again.
If it still doesn't appear then download Motorola USB drivers here and try again.
If fine then run:
adb reboot bootloader​Then run the following to flash the stock image:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock​
Flashing userdata.img is going to remove all your files so back everything up first.
This should unroot your Xoom anyway, not entirely sure if the lock is required to receive updates, but it's simple to unlock again.
Once booted and through initial setup you should receive several over the air updates. (I believe the stock image is Android 3.2)
Unlock:
Connect your Xoom again and open command window in the adb-fastboot folder as before.
Run:
adb reboot bootloader
fastboot oem unlock
fastboot reboot​You'll now be unlocked.
Install Touch Recovery and Root:
Next download ClockworkMod Touch recovery from here, rename it to just recovery.img for simplicity, and copy the image to the adb-fasboot folder.
Download Xoom Universal Root from here.
Copy that file to your sdcard.
Then run:
adb reboot bootloader
fastboot flash recovery recovery.img​(assuming you renamed it)
Once verified, reboot by holding Volume up and Power. (Keep connected to PC and keep command prompt open)
Important: When you see the Motorola logo wait about 3 seconds and hit volume down. You should see 'Android Recovery' in the top left corner, now press volume up to enter recovery.
From recovery go, Install zip from sdcard > choose zip > and select Xoom-Universal-Root.zip
Important: After the root flashes do not reboot.
Run:
adb remount
adb shell mv /system/recovery-from-boot.p /system/recovery-from-boot.p.old
adb shell mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.old​Then select reboot in ClockworkMod recovery and boot as normal.
If you are unable to use adb in recovery, then you can enable this through Windows by doing the following:
Whilst in recovery and connected to your PC, open Device Manager, find your Xoom, usually under 'Other devices'.
Then right click on your Xoom > Update driver software... > Browse my computer for driver software > Let me pick from a list of device drivers on my computer > Pick your Xoom (either one if there's two shown)
Windows should confirm the driver installed then adb should work in recovery.
Finally, run:
adb reboot recovery​If ClockworkMod touch recovery is still there then all is good!
Hopefully I've made sense! Any questions, just ask.
Repeat of downloads:
Download Motorola USB Drivers (Device Manager) here.
Download ClockworkMod Touch recovery here.
Download Xoom Universal Root here.

Wow, what a detailed guide
Thank you sir

No problem!
Let me know how it goes, hopefully shouldn't have any problems.

Resetting worked great :good:
Right now I´m in an OTA marathon
all that unlock, root and recovery stuff sounds familiar so I don´t expect any problems.
Thanks so far :good:

alecbond said:
From recovery go, Install zip from sdcard > choose zip > and select Xoom-Universal-Root.zip
Important: After the root flashes do not reboot.
Run:
adb remount
adb shell mv /system/recovery-from-boot.p /system/recovery-from-boot.p.old
adb shell mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.old​Then select reboot in ClockworkMod recovery and boot as normal.
Finally, run:
adb reboot recovery​If ClockworkMod touch recovery is still there then all is good!
Click to expand...
Click to collapse
Ok, so this is not working
after I flash touch recovery and do thta reboot thing I can enter touch recovery, thats fine.
Flashing universal root, fine.
THEN,
adb remount
adb shell mv /system/recovery-from-boot.p /system/recovery-from-boot.p.old
adb shell mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.old
gives me error since in recovery mode there ist no adb connection
Whatever when I choose to reboot the system, recovery warns me that it will get overwritten by boot and ask me to disable this.
Shall I do this?
EDIT: Nevermind, I decided to be a little brave and just confirmed that message.
Now touch clockwork seems to be persistent and I´m a happy Xoomer again

Sorry, I had meant to reply during my lunch break.
Edit: Realised the time on the second of your posts, so wouldn't have been much help on my lunch anyway
Well I believe I just learned something new!
Either that or I'd forgotten it asked.
I assume it disables the action rather than deletes those files.
My method was just so you can use the reverse rename in future to re-enable the overwrite on boot.
In future, not that you'll necessarily ever need this information, you can enable adb in recovery through windows by doing the following
When in recovery and connected to your PC, open Device Manager, find your phone, usually under 'Other Devices'.
Then right click > Update driver > Browse my computer > Let me pick from list > Pick your phone (either one if there's two shown)
Should confirm driver installed then adb should work.
I didn't include the above previously as I couldn't remember having to do it personally.
Glad to hear all is well though!

alecbond said:
You'll presumably want Build H.6.1-38-1 for Retail Europe from here.
Returning to stock:
Extract the files from the link above to your adb/fastboot directory if you have one. If you don't have one I've uploaded them for you here.
Connect your Xoom to your PC then open command prompt from your adb folder. (Hold shift > right click on adb-fastboot folder > click Open Command Window Here)
Type adb devices and hit enter, if no devices are listed then ensure USB debugging is switched on in Settings > Development > and tick USB Debugging, then try again.
If it still doesn't appear then download Motorola USB drivers here and try again.
If fine then run:
adb reboot bootloader​Then run the following to flash the stock image:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock​
Flashing userdata.img is going to remove all your files so back everything up first.
This should unroot your Xoom anyway, not entirely sure if the lock is required to receive updates, but it's simple to unlock again.
Once booted and through initial setup you should receive several over the air updates. (I believe the stock image is Android 3.2)
Unlock:
Connect your Xoom again and open command window in the adb-fastboot folder as before.
Run:
adb reboot bootloader
fastboot oem unlock
fastboot reboot​You'll now be unlocked.
Install Touch Recovery and Root:
Next download ClockworkMod Touch recovery from here, rename it to just recovery.img for simplicity, and copy the image to the adb-fasboot folder.
Download Xoom Universal Root from here.
Copy that file to your sdcard.
Then run:
adb reboot bootloader
fastboot flash recovery recovery.img​(assuming you renamed it)
Once verified, reboot by holding Volume up and Power. (Keep connected to PC and keep command prompt open)
Important: When you see the Motorola logo wait about 3 seconds and hit volume down. You should see 'Android Recovery' in the top left corner, now press volume up to enter recovery.
From recovery go, Install zip from sdcard > choose zip > and select Xoom-Universal-Root.zip
Important: After the root flashes do not reboot.
Run:
adb remount
adb shell mv /system/recovery-from-boot.p /system/recovery-from-boot.p.old
adb shell mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.old​Then select reboot in ClockworkMod recovery and boot as normal.
Finally, run:
adb reboot recovery​If ClockworkMod touch recovery is still there then all is good!
Hopefully I've made sense! Any questions, just ask.
Repeat of downloads:
Download Motorola USB Drivers (Device Manager) here.
Download ClockworkMod Touch recovery here.
Download Xoom Universal Root here.
Click to expand...
Click to collapse
Hey, you did a great guide! Would you mind if I put that in the FAQ Thread?
"We think so supersonic and we make our bombs atomic" - Eagle Fly Free (Helloween)
Sent from my Nexus 10 using Tapatalk HD

XxLordxX said:
Hey, you did a great guide! Would you mind if I put that in the FAQ Thread?
Click to expand...
Click to collapse
No problem, I'd be honored!

[TWRP RECOVERY] + [ROOT] Teclast Tbook 11 (E5A6) Android 5.1

Hello,
This is my first post on how to root and install TWRP recovery on the Teclast Tbook 11 (E5A6) android 5.1
The TWRP works with touch and I haven't encounterd any problems with it
I have not created the TWRP, it is made by nik2670
We only flash or boot the recovery, then install SuperSU 2.82- 201705271822. Nothing else !
Sorry for the mirrors. (I will remove them if you're the owner)
Be sure to have ADB drivers v1.4.3 installed before you continue.
Download TWRP 2.8.7.0. Recovery Tbook 11 and ADB and Fastboot and put it in a folder on your desktop
Enable USB debugging on your tablet (Settings->Developers->usb-debugging)
Connect your tablet with your PC
Open up a CMD prompt in the folder you have your ADB. Win+R type CMD, hit enter. Copy the path of ADB and put in the CMD prompt
Code:
cd [path]
Mine was cd "C:\Users\Thermaltake\Desktop\ADB FASTBOOT FILES WINDOWS"
In the CMD prompt, type
Code:
adb devices
If you see your device you good to go.
Type
Code:
adb reboot bootloader
your tablet reboots, select android while it reboots
Now we're in fastboot mode, just to be sure we see the device type
Code:
fastboot devices
. If you can't see your device like me you have to manually install drivers.
Do you have the recovery.img in the same folder as ADB? Good. Type
Code:
fastboot boot recovery.img
OR
Code:
fastboot flash recovery recovery.img
to permanently have the TWRP recovery on your device (I recommand boot)
Your tablet is now in recovery mode! You can acces the internal storage. Add SuperSU-v2.82 on your device.
Hit Install->SuperSU-v2.82-201705271822->Swipe to confirm flash->Wipe dalvik cache->Reboot----> DONE !
Image of succesfully root
Thanks for following my guide, if there are any problems I try to update the tutorial or provide more information to you!
Mathero11
Thanks to nik2670 for the recovery, chainfire for supersu and unpersonally xda developers for other flash/root tutorials

Adb fails to recognise device only when in fastboot

Hi all,
I've seen I haven't been the only one with this problem, but I haven't seen a clear solution yet. My Poco F2 pro miui global gets recognised by adb, and by the unlocking software when in fastboot, but not by adb in fastboot. I am trying to install TWRP. I have tried various drivers (currently running one from the official mi forum), running the command prompt, powershell and terminal with admin rights, killing and starting the adb server, using a windows or linux system to do it, made sure to enable USB debugging, file exchange and permanently accepting fingerprints after connecting. But to no avail. Any suggestions on what to try next?
Thanks in advance.

herkio1 said:
Hi all,
I've seen I haven't been the only one with this problem, but I haven't seen a clear solution yet. My Poco F2 pro miui global gets recognised by adb, and by the unlocking software when in fastboot, but not by adb in fastboot. I am trying to install TWRP. I have tried various drivers (currently running one from the official mi forum), running the command prompt, powershell and terminal with admin rights, killing and starting the adb server, using a windows or linux system to do it, made sure to enable USB debugging, file exchange and permanently accepting fingerprints after connecting. But to no avail. Any suggestions on what to try next?
Thanks in advance.
Click to expand...
Click to collapse
Adb use Adb.exe and fastboot fasboot.exe (differente programs)
For Twrp you must use this command " .\fastboot flash recovery twrp.img "with CMD or Powershell.
download sdk Platform tools https://developer.android.com/studio/releases/platform-tools.
extract platform-tools folder.
Put this twrp https://androidfilehost.com/?fid=17248734326145679747 into platform tools folder
Phone in fastboot mode power and volume - (Obviously the phone must be detected on the pc)
use this command " .\fastboot flash recovery twrp.img "with CMD or Powershell.

Solved thanks, I used fastboot for fastboot mode and adb for in twrp/booted in system. I must have mistyped because I could flash the twrp.img file but it then gave me an error when trying to boot into it.

How to escape TWRP? Activate ADB w/ broken screen?

So my screen broke on my Note 10+, leaving only the top 15% with display and the bottom 60% with touch. I am trying to activate ADB on it so that I can backup my internal storage.
I booted into TWRP so that I could backup the rest of my system, which I did successfully, but because of the bad touch screen I am unable to hit the ADB side load button. I'd like to reboot into the system because I have ADB enabled there, however I also cannot click the reboot to system button, only reboot to download and shutdown. Since I can't see most of the screen, it is also not possible to access the terminal and work from there.
Anybody know how I can escape TWRP or otherwise activate ADB? Thanks for the help.

Once USB Debugging successfully got enabled on Android device, ADB is supported as soon as device successfully booted up.
To turn device into ADB Sideload mode you run commands
Code:
adb devices
adb reboot sideload

jwoegerbauer said:
Once USB Debugging successfully got enabled on Android device, ADB is supported as soon as device successfully booted up.
To turn device into ADB Sideload mode you run commands
Code:
adb devices
adb reboot sideload
Click to expand...
Click to collapse
Like I said, I'm unable to boot into the system right now because I am stuck in TWRP. ADB is not enabled in TWRP upon boot, you have to press the ADB side load button, which I am unable to do.

AllanRSS said:
Like I said, I'm unable to boot into the system right now because I am stuck in TWRP. ADB is not enabled in TWRP upon boot, you have to press the ADB side load button, which I am unable to do.
Click to expand...
Click to collapse
To boot into NORMAL mode ( i.e. ADB mode ) you enter on Windows command prompt these commands, one-by-one
Code:
adb devices
adb reboot

jwoegerbauer said:
To boot into NORMAL mode ( i.e. ADB mode ) you enter on Windows command prompt these commands, one-by-one
Code:
adb devices
adb reboot
Click to expand...
Click to collapse
I can not use ADB. It is for this very reason I am asking how to enable ADB. But thank you for these valuable ADB commands, I'll be sure to reboot my system once I enable ADB

Enable USB Debugging in Recovery Mode

Hi,
during the update the phone got stuck, daughter restarted couple of times but it always got to the 76%, hang there and then restarted itself in the endless loop.
I've tried the the hard reset (Power+VolUP) and it got to the screen saying "No Command". Then I pressed the same combo again to get to the bootloader and tried the wipe / reset. During that process I got the error message "E: Can't send SPI message. Try again" and then it said it was successful, but rebooting did nothing, got stuck in the restart loop.
So I've done the research and wanted to to upload the OTA update, have done that but that didn't do anything.
So I've found some articles on how to upload the stock rom/image but I'm unable to do so as sending adb commands is disabled due to the phone being LOCKED. I've learned that the USB debugging needs to be enabled, however I'm unable to get into the OS to set it up, so found this article:
How to enable USB Debugging in Android using recovery mode?
One million questions, Is it possible to Enable USB Debugging in Android Using Recovery Mode or any other technique? Well, the answer is Yes! It is now
www.isrgrajan.com
which outlines the following steps (in summary):
Download the Stock ROM for your device- Google it, I am dam sure you can find it. [DONE]
Download SuperSU from UPDATE-SuperSU-v1.65.zip [DONE][looks pretty old though]
Steps to Enable USB Debugging Using Recovery Mode
Unzip the stock ROM. [DONE]
Within the extracted folder, you will find the system.img well extract it too using Ext4 Unpacker [DONE but plenty of folder are empty, but eventually plentu of APK along]
Also, extract the Update-SuperSU.v1.65.zip file. [DONE, again, looks pretty old]
Now open the folder where you have extracted the system.img files [DONE]
Grab any .apk file from this folder and change the extension from .apk to .zip [PROBLEM: the apks are all over the shop. Which APK shall I pick up?]
And Copy the RSA Certificated to the Update-SuperSU.v1.65 folder (delete previous files if exist) [PROBLEM: unable to find any "RSA Certificated" like files once I open ANY apk]
Also, copy the build.prop to the system folder located within Update-SuperSU.v1.65 folder [BLOCKED by previous step]
Locate the update-script file within this folder and edit it using Notepad++ [BLOCKED by previous step]
You need to update the build.prop file after adding the following line at the bottom [BLOCKED by previous step]
persist.service.adb.enable=1
Next step is updating SQLite Database [WHERE would I do this step?]
Which can be done by adding the following code to the update-script file
sqlite3 /data/data/com.android.providers.settings/databases/settings.db "UPDATE global SET value=1 WHERE name='adb_enabled'"
What would I do then? How to actually apply the changes back to the phone?
Does anyone know of better / latest step by step process of enabling / unlocking the device or is my device now completely and unrepairably bricked?
Thank you.

Android - Enable ADB from recovery
Android - Enable ADB from recovery. GitHub Gist: instantly share code, notes, and snippets.
gist.github.com

jwoegerbauer said:
https://gist.github.com/varhub/7b9555cdd1e5ad785ffde2300fcfd0bd
Click to expand...
Click to collapse
For a while (since when, I don't know) persistent properties are not shared as individual files in /data/property.
They are all packed inside /data/property/persistent_properties.
Try setprop instead.

jwoegerbauer said:
Android - Enable ADB from recovery
Android - Enable ADB from recovery. GitHub Gist: instantly share code, notes, and snippets.
gist.github.com
Click to expand...
Click to collapse
will give it a go. thank you.

jwoegerbauer said:
Android - Enable ADB from recovery
Android - Enable ADB from recovery. GitHub Gist: instantly share code, notes, and snippets.
gist.github.com
Click to expand...
Click to collapse
I've tried the steps but I'm crashing on sending any commands to the device. While I'm in the recovery, I see the following details and options:
```
Android Recovery
google/blueline/blueline
12/SP1A.210812.016.B2/8602260
user/release-keys
Use volume up/down and power
Warning: Previous installation has failed. Your device may fail to boot if you reboot or power off now
- Reboot system now
- Reboot to bootloader
- Enter Fastboot
- Apply Update from ADB
- Apply update from SD card
- Wipe data/factory reset
- Mount /system
- View recovery logs
- Run Graphics Test
- Run Locale Test
- Power Off
```
where I run the adb command:
`adb shell mount data` I get the `adb.exe: no devices/emulators found`.
when I go to the `Apply update from ADB` and run the command above I get `error: closed`.
Basically I'm unable to run any adb commands as of the first message, and the only place I can it's from within the update. I've noticed that while in the 'Update via ADB', then in the Win Device Manager I can see that the driver is changed to `Android Composite ADB Interface` and only now it's accepting very limited commands. `adb devices` command generates: `<device id number>: sideload`.
When in the fastboot, it switches to `Android Bootloader Interface` in the DEvice manager.
When in recovery, the device is disconnected from the computer. (is not listed in the device manager)
any thoughts. thanks
Note: that phone was never rooted.
Bootloader looks like this at the moment:
```
Fastboot Mode
Product revision: blueline MP1.0(ROW)
Bootloader version: b1c1-0.4-7617406
Basebandversion...
serial number:
secure booth: PRODUCTION
NOS Production: yes
DRAM: 4GB
Device State: Locked
Boot slot: a
```

vajnorcan said:
I've tried the steps but I'm crashing on sending any commands to the device. While I'm in the recovery, I see the following details and options:
```
Android Recovery
google/blueline/blueline
12/SP1A.210812.016.B2/8602260
user/release-keys
Use volume up/down and power
Warning: Previous installation has failed. Your device may fail to boot if you reboot or power off now
- Reboot system now
- Reboot to bootloader
- Enter Fastboot
- Apply Update from ADB
- Apply update from SD card
- Wipe data/factory reset
- Mount /system
- View recovery logs
- Run Graphics Test
- Run Locale Test
- Power Off
```
where I run the adb command:
`adb shell mount data` I get the `adb.exe: no devices/emulators found`.
when I go to the `Apply update from ADB` and run the command above I get `error: closed`.
Basically I'm unable to run any adb commands as of the first message, and the only place I can it's from within the update. I've noticed that while in the 'Update via ADB', then in the Win Device Manager I can see that the driver is changed to `Android Composite ADB Interface` and only now it's accepting very limited commands. `adb devices` command generates: `<device id number>: sideload`.
When in the fastboot, it switches to `Android Bootloader Interface` in the DEvice manager.
When in recovery, the device is disconnected from the computer. (is not listed in the device manager)
any thoughts. thanks
Note: that phone was never rooted.
Bootloader looks like this at the moment:
```
Fastboot Mode
Product revision: blueline MP1.0(ROW)
Bootloader version: b1c1-0.4-7617406
Basebandversion...
serial number:
secure booth: PRODUCTION
NOS Production: yes
DRAM: 4GB
Device State: Locked
Boot slot: a
```
Click to expand...
Click to collapse
On my pixel3, /dev/block/dm-4 is mounted to /data. Try "adb shell mount /dev/block/dm-4 /data".
The instructions you are following are very old, and likely obsolete. SuperSu is also obsolete. Try to find a newer method.

dcarvil said:
On my pixel3, /dev/block/dm-4 is mounted to /data. Try "adb shell mount /dev/block/dm-4 /data".
The instructions you are following are very old, and likely obsolete. SuperSu is also obsolete. Try to find a newer method.
Click to expand...
Click to collapse
the issue is I'm unable to run that command `adb shell mount...` with the `no devices/emulator found` message. I believe it's because the device is not even listed in the device manager (windows) when in recovery mode. When in the update mode, then it's listed in the DM. See my post above, I've updated it few times. Thanks
Btw on that link if you check the posts there are newer ones (1.5y back) claiming it works so might actually work

If you're unable to sideload the OTA via PC, I don't think there's any other option besides paying for a repair, or replacing the device. A locked bootloader definitely makes recovery a lot harder.

V0latyle said:
If you're unable to sideload the OTA via PC, I don't think there's any other option besides paying for a repair, or replacing the device. A locked bootloader definitely makes recovery a lot harder.
Click to expand...
Click to collapse
I'm able to sideload the OTA, but restart goes into start being stuck and back and forth but never gets any further than the first google load screen

vajnorcan said:
I'm able to sideload the OTA, but restart goes into start being stuck and back and forth but never gets any further than the first google load screen
Click to expand...
Click to collapse
Were you using adb/fastboot before this happened? Was the device recognised then? If not, are you sure you have the right drivers?

AlexKarimov said:
Were you using adb/fastboot before this happened? Was the device recognised then? If not, are you sure you have the right drivers?
Click to expand...
Click to collapse
I've used the adb to upload the ota and that went, according the message ok, but the system won't start up. Device is recognized only when I choose the "Apply update from ADB" option in recovery mode. The moment I choose it, it shows up as a device in device manager and "adb devices" lists it ok. In fastboot mode it does list it in device manager, but "adb devices" doesn't list it.
It's the latest driver

vajnorcan said:
I've used the adb to upload the ota and that went, according the message ok, but the system won't start up. Device is recognized only when I choose the "Apply update from ADB" option in recovery mode. The moment I choose it, it shows up as a device in device manager and "adb devices" lists it ok. In fastboot mode it does list it in device manager, but "adb devices" doesn't list it.
It's the latest driver
Click to expand...
Click to collapse
If I understand correctly, you're using "adb devices" when in fastboot mode? You need to use "fastboot devices". If that works and lists the phone then you may be able to use the flash tool on the Google website

AlexKarimov said:
If I understand correctly, you're using "adb devices" when in fastboot mode? You need to use "fastboot devices". If that works and lists the phone then you may be able to use the flash tool on the Google website
Click to expand...
Click to collapse
This requires OEM Unlocking to be enabled so it won't be much help here.
Rescue Mode might work though.
@vajnorcan try this:
Boot to bootloader and select Rescue Mode using the volume buttons, then press Power to enter it.
On your PC, go to pixelrepair.withgoogle.com and connect the USB cable to your device. Select your carrier or select "Other" if device is unlocked.
I don't know whether this will actually work...I haven't heard of anyone using this tool to successfully recover.

AlexKarimov said:
If I understand correctly, you're using "adb devices" when in fastboot mode? You need to use "fastboot devices". If that works and lists the phone then you may be able to use the flash tool on the Google website
Click to expand...
Click to collapse
'fastboot devices' is reading the device, which is good. but trying the online flash tool fails due to the device being locked. :/

V0latyle said:
This requires OEM Unlocking to be enabled so it won't be much help here.
Rescue Mode might work though.
@vajnorcan try this:
Boot to bootloader and select Rescue Mode using the volume buttons, then press Power to enter it.
On your PC, go to pixelrepair.withgoogle.com and connect the USB cable to your device. Select your carrier or select "Other" if device is unlocked.
I don't know whether this will actually work...I haven't heard of anyone using this tool to successfully recover.
Click to expand...
Click to collapse
The google tool has found and connected to the device, but it ends up in an error (on the device) and saying "disconnected", looked promising, but not for long. thanks.