Database Info

adb reboot download tutorial(Windows)

Okay this is four newbie that can't get there phone into download mode,or if your phone is stuck on the a&tt screen or whatever reason you need to go into download mode
1st thing you are going to need android-sdk if you do not have. You need to put all the files on your C: drive in a folder called android-sdk.There is the link to the sdk site.
http://developer.android.com/sdk/index.html
Step 1 go to setting then to Application I always select mass storage,but i guess ask on connection will work.Then in applications select Development,and them usb debugging.Then plug your phone into your computer
Step 2 open the start window in windows vista and 7 user type cmd into the search.XP you go to run and then type cmd.
Step 3 once inside cmd type cd\ enter.this will bring you to the c drive and should look like this.Now it should look like this.
C:/>
step 4 next type cd then (space) android-sdk\tools\ enter it should look like this.
C:\>cd android-sdk\tools\
Step 5 type adb (space) devices.Now it should look like this.
C:\android-sdk\tools>adb devices
* daemon not running. starting it now on port whatever *
* daemon started successfully *
whatever # your phone is device.
now if it doesn't say this you probably don't have the proper drivers install,but if your are rooted you should.I will include a zip folder anyways.
Step 6 adb (space) reboot (space) download enter.It should look like this.
C:\android-sdk\tools>adb reboot download
After hitting enter your phone will reboot into download mode.
Here is a link for the drivers.
http://www.sendspace.com/file/dbh299
Make sure that you have ADB in the tool folder if not here it is

Actually step 1 would be to enabled usb debugging in settings/applications/development section otherwise none of this will work.
Theres also the adb reboot recovery command.

peachpuff said:
Actually step 1 would be to enabled usb debugging in settings/applications/development section otherwise none of this will work.
Theres also the adb reboot recovery command.
Click to expand...
Click to collapse
Thank dude I always have my phone in debugging i'll edit now

From my experience if you flash a rom it will no longer have usb debugging enabled so if you get boot loop or something adb wont work. I know you don't specifybut I personally have not heard of a device being stuck unless the person was flashing.
This is my captivate. There are many like it buy this one is mine.

You might also consider adding the instructions for adding the tools folder to PATH for those that would use this frequently.

flashman2002 said:
From my experience if you flash a rom it will no longer have usb debugging enabled so if you get boot loop or something adb wont work. I know you don't specifybut I personally have not heard of a device being stuck unless the person was flashing.
This is my captivate. There are many like it buy this one is mine.
Click to expand...
Click to collapse
I have had my phone,Plus my girls virbrant stuck on the att%t screen\t-mobile screen and this as worked for me.I have had a few boot loops, but that was cuz i was changing the framework-res.apk,but was able to go into download mode via the rom I was on. I will look into this and see if i need to update.

Completely unresponsive
I have a galaxy s7 and my phone is completely dead. It does not show up in list of devices connected. I have tried all key combinations to start my phone but it is completely unresponsive. Can anybody help me out please.

[Q] Windows drivers for Nabi2

I've read a couple dozen of the pages from http://forum.xda-developers.com/showthread.php?t=1905674&page=95 titled
Nabi2 root and Gapps install
Click to expand...
Click to collapse
.
Using Win7 x64. Nabi2 version: 1.9.37 recently updated.
Can't post to above thread because this is my first post (restricted to "General" forums).
In "Jmz Nabi Recovery Installer" window it is always stuck in the "If stuck here drivers are not installed" step.
Prior to installing "PdaNet for Android" from http://junefabrics.com/index.php,
I had 2 devices in Control Panel under "Other devices" with a yellow '!'. One of the looked like the Nabi device. The other is named "MTP".
After installing PdaNet, only MTP remains with the yellow exclamation point.
What should the Nabi look like in the Control Panel if its properly configured with a driver and where would it be?
And what is MTP?
Apparently I'm still having a driver/connection problem from adb.
USB Debugging is on in the Nabi.

Put the nabi in 'fastboot' mode
Open a CMD Prompt and browse to the 'files' folder within 'jmzrootpackage'
Then type:
adb.exe
fastboot devices
It should return a value (fastboot working and drivers are installed)
Let me know how it goes.

Put the nabi in 'fastboot' mode
Open a CMD Prompt and browse to the 'files' folder within 'jmzrootpackage'
Then type:
adb.exe
Click to expand...
Click to collapse
Part of this command is missing right? Without input parms it just outputs the "uses" message.
fastboot devices
Click to expand...
Click to collapse
Unfortunately this returned nothing for me.
I'm glad you responded. Other suggestions?

Here is how i done it using Windows 8 x64
I done 3 nabi2's this way but had a lot of trouble first so here is what worked for me:
Sadly, i don't have any nabi2 with me now to explain exactly how i done it
1) First boot the Nabi2 normally and turn off usb debugging.
2) When fully booted connect USB cable.
3) Check device manager and drivers should be installed.
4) Unplug USB cable and turn on USB Debugging and Unknown Sources.
5) Reconnect USB Cable.
6) Drivers should install.
7) Install PDA Net on Laptop/PC
8) Select Samsung device from option screen when installing.
9) Wait for install to complete and drivers to install
10) Shut down Nabi2
11) Boot Nabi in fastboot (Hold + and Power buttons)
12) Select fastboot protocol
13) Here i seen Windows 8 take about 60 seconds installing fastboot drivers
To make sure fastboot drivers are installed i went to this thread
Code:
http://forum.xda-developers.com/showthread.php?t=1590800
and download ADB (save it to C:\SDK\platform-tools) and read over the helpful instructions in the thread.
Open command Prompt
Type the following (shown in RED) in the CMD window the opened:
cd\
cd C:\SDK\platform-tools
adb.exe (a list of options should be listed)
fastboot devices (it should list a number after you enter this)
If number displayed then you are good to go.
Reboot Nabi2 and wait to complete
Go to the location you saved jmzrootpackage
Go to files folder inside jmzrootpackage
Double click install.bat
Follow on screen prompts ( I took option 1)
TWRP recovery installs
I had trouble installing GAPPS.zip with an error being displayed about unable to mount /data
I copied GAPPS.zip to a SD Card and inserted to Nabi2
i install zip from EXT-SD Card even though it gives a load of errors about not able to mount /data
Wipe Cache/Dalvik
Reboot Nabi2
Go to daddy/mommy mode and you should have Google Apps installed.
Any problems let me know.

I'm using Windows 7 x64.
Your instructions with selecting "Samsung" for PdaNet install appears
to have done something right. So maybe I'm a little closer.
It completed the PdaNet install successfully and when I reconnect the
Nabi I see a message popup on Windows saying PdaNet connected something.
(It was too quick.)
So maybe I'm not doing the "Fastboot" portion correctly.
On Nabi hold <Power> and <Vol+> down at same time to turn it on.
Resulting Menu:
Boot Normally
Fastboot Protocol
Recovery Kernel
Forced Recovery​
Use <Vol-> to move the selected item.
Moved selected item down to "Fastboot Protocol".
Use <Vol+> to "enter" selected item.
New Menu:
Bootloader
Continue
Reboot-bootloader
Reboot
Poweroff​
Selected "Continue", and entered(<Vol+>).
At this point the Nabi boots up.
On PC in adminstrator mode for command window and with ALL anti-virus
security turned off:
> adb.exe kill-server
> adb.exe start-server
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
> fastboot.exe devices
Nothing. (sigh)

After looking at Victoria Antonio's youtube of this process I'm convinced the driver install is still not correct.
Somehow it gets mucked up when I use PdaNet. Not sure how or why.
To make this picture clearer I posted some screen shots on my website: http <colon, 2 forward slashes>skippyvondrake.com
I hope someone can tell me how to unmuck what I've mucked.

skippyV said:
Selected "Continue", and entered(<Vol+>).)
Click to expand...
Click to collapse
Don't press Continue on the Nabi after selecting fastboot protocol
After selecting fastboot protocol leave it.
skippyV said:
> fastboot.exe devices
Click to expand...
Click to collapse
The command is:
fastboot devices
not
fastboot.exe devices

Thanks for telling me about when I'm in fastboot mode.
I DO get a device number when in fastboot mode and from 'fastboot devices'
But adb still cannot "see" the device. All commands using adb result in:
error: device not found
Regardless of what mode the Nabi is in.

SOLVED
I finally decided to try this with a different computer. Same OS and architecture.
But this computer didn't have various android development "kits" installed previously.
And it worked without a hitch.
The youtube by Victoria Antonio pointed out a few nuances I didn't know.
And you helped too, BBKGTTDi, so giving you "thank you" points.
Chow!

Glad you got it work SkippyV
I just need to figure out now, when i download a game to the Nabi2 from the playstore, how to get it so show in the kids mode

BBKGTTDi said:
Glad you got it work SkippyV
I just need to figure out now, when i download a game to the Nabi2 from the playstore, how to get it so show in the kids mode
Click to expand...
Click to collapse
When I get there - if I figure it out - I'll send you a private email sense that would be a different "thread'. There are other nuances I've noticed too...

show game in Nabi mode after rooting
@BBKGTTDi, I thought there would be a way to send private messages/emails on this forum - but I don't see it.
I ran into the same problem after rooting the Nabi. The "Add Apps" app doesn't work as its supposed to.
It worked prior to rooting.
It does list the newly installed apps, but selecting them for Nabi-Mode, rebooting, and they aren't there.
Only visible in Mommy/Daddy mode.
So if you figure it out please let me know!

The "Add Apps" app is working correctly now. Don't know what happened before.
I must be getting "Nabi-ed out".
Let me know if you're still having troubles.

skippyV said:
I'm using Windows 7 x64.
Your instructions with selecting "Samsung" for PdaNet install appears
to have done something right. So maybe I'm a little closer.
It completed the PdaNet install successfully and when I reconnect the
Nabi I see a message popup on Windows saying PdaNet connected something.
(It was too quick.)
So maybe I'm not doing the "Fastboot" portion correctly.
On Nabi hold <Power> and <Vol+> down at same time to turn it on.
Resulting Menu:
Boot Normally
Fastboot Protocol
Recovery Kernel
Forced Recovery​
Use <Vol-> to move the selected item.
Moved selected item down to "Fastboot Protocol".
Use <Vol+> to "enter" selected item.
New Menu:
Bootloader
Continue
Reboot-bootloader
Reboot
Poweroff​
Selected "Continue", and entered(<Vol+>).
At this point the Nabi boots up.
On PC in adminstrator mode for command window and with ALL anti-virus
security turned off:
> adb.exe kill-server
> adb.exe start-server
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
> fastboot.exe devices
Nothing. (sigh)
Click to expand...
Click to collapse
I ve got the same problem using windows xp, 7 or 8.1 after OTA update to jellybean.
Any ideas of what is going on?

arvati said:
I ve got the same problem using windows xp, 7 or 8.1 after OTA update to jellybean.
Any ideas of what is going on?
Click to expand...
Click to collapse
I did have those problems last year. Still think they were driver related.
I use mehtuus's package now. He has a useful install script.
http://forum.xda-developers.com/showthread.php?t=2172843
And when I want to use adb in "manual" mode I just launch a command prompt from his
'adb' directory (package is named 'mn2ri-v1.5.0-beta2.zip').
Try playing with his installer. And see if anything is displayed using:
Code:
adb devices

Thanks skippyV. I got it in fastboot last week with ubuntu and installed TWRP sucessfully.

Fastboot will not detect my device while rooting

I've been trying for the past couple of days to root my Oneplus One. I started with this tutorial: (http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471) which is featured in the FAQ (which I've read through) and I've gotten stuck at one location.
You can test fastboot by connecting your device to your PC while booted into fastboot mode (power + volume up) and issuing this command:
Code:
fastboot devices
It should return your device serial number, if so, fastboot is working.
Click to expand...
Click to collapse
The ADB command appears to be working, but when I boot into fastboot mode (and when I'm not in it as well), the PC does not detect the phone. I've tried connecting it to multiple USB ports, and I'm using the official Oneplus One cable, so I'm at a bit of a loss of what to do.
However, I feel like I've identified where the source of the error is. If you see here: (http://i.imgur.com/IE1Bxjs.png), you can see that the phone is being detected under Portable Devices. In all of the tutorials I've looked through so far, it's been detected under something like "Android Phone" or "ADB Interface". I've tried various things to fix this, the most common of which is installing drivers onto/for the phone. I've tried the one here: (http://forum.xda-developers.com/showthread.php?t=1413293), which I know is for Archos phones, but should work similarly, as I tried both the Universal ADB driver and the Google one, from the SDK Manager. I kept getting an error telling me that: "the folder you specified doesn't contain a compatible software driver for your device."
I've also tried the one here: (http://www.makeuseof.com/tag/android-wont-connect-windows-adb-fix-it-three-steps/) (let me know if external links aren't allowed and I'll remove it.) This doesn't seem to work either, as I get this error (http://i.imgur.com/CLATXsl.png) when it tells me to:
If you cannot get any driver to work, you will need to force installation. Instead of choosing “Let me pick from a list of device drivers on my computer” in the previous step, you will choose “Browse for driver software on your computer” and manually find the directory where you installed Koush’s drivers.
The location on your hard drive looks something like this:
C:\Program Files (x86)\ClockworkMod\Universal Adb Drivers\
Windows will then install the drivers. From now on, whenever you connect the Android device with debugging enabled, Koush’s drivers will load in place of the ones that failed to work.
Click to expand...
Click to collapse
And now I'm posting here, praying that someone will have some sort of idea what to do. Any help at all would be greatly appreciated,
Fappled
EDIT: Managed to get it working, messing around with the drivers in device manager while in Fastboot mode seemed to work.

Fappled said:
The ADB command appears to be working
Click to expand...
Click to collapse
Feel your pain, I've been thru some pain myself with some weird issue, posted here yesterday. Though, my issue is different from yours, I have some ideas for you.
You say that adb works, so I assume your usb cable & PC are OK here.
I aslo assume that your Device Manager screenshots taken when connected to your phone in device mode (rom running). Don't worry about what you see in Device Manager just yet. Your goal is to make fastboot work, right. Note: Adb works in recovery mode and device mode, but not in fastboot mode. Fastboot works only in fastboot mode.
You could try this, put your phone in fastboot mode, then connect to your PC. Now, see what in your Device Manager. In my case, the phone is under Android Device>Android Bootloader Interface and I use Google driver. Then, try "fastboot devices" to see if your phone is detected.
If not, play with the driver in Device Manager (uninstall, rescan, install another). No need to unplug the phone. After the driver changed, see your Device Manager changed, and then try "fastboot devices".
I played with the driver changing a few time and got fastboot to work. I hope you get it to work too.

Install Adb Drivers For Any Android Phone On Your Pc! [JUST In 2Mins] [Very Easy]

Do You Like To Flash Custom Stuffs On Your Android phone? Or Are You A Developer? But You Can't Able To Do It Because You're Facing Some Problems with Your Adb & fastboot. All Of This Problems Are Only Because Of One Thing And That is Drivers.
And If you agree With Anyone Of This Situations Then You're At The Right Place Because Today I Am Going To Tell You That How You Can Install The Adb Drivers For Your Specific Android Phone On Your Pc.
Adb drivers are necessary if you want to flash a android device through Fastboot mode or if you're a android developer. Usually Our PC installs the adb drivers automatically for the specific android device but sometimes it can't so you have to install it manually.
This will also help you to solve adb errors like Device is offline, USB debugging Authorize pop-up not showing in android And etc adb errors. Make sure that your USB debugging option in developer mode is enabled on your Android device Because without this you can't use adb.
Steps:-
*So first go http://adbdriver.com to and download the "adb driver installer (Universal)". Then extract it.
*Now connect your Android phone to your PC using USB cable. Then Open the application.
*Now you will see something like Adb interface drive and with a red Cross at left side. Make sure to refresh if driver option is not shown.
*Now Just Click On install To install your device adb drivers. Then it will Install the adb drivers for your specific android phone in just under 2 minutes.
*Then Allow The USB debugging On your Android phone. Then the adb drivers will get successfully installed.
*If still adb can't recognize your device then try to connect your phone in PTP Mode instead of MTP or Charging only modes.
*If still it doesn't work for you then Revoke USB debugging Authorizations in developer mode. So that's how you can install the adb drivers for your Android Phone.
Video Tutorial - https://goo.gl/a6QgtH

Un/Official (Windows) USB Drivers/ADB/Fastboot [Essential PH-1/Mata]

Warning if your intent is to Unlock the Bootloader.
At this time 24 Sept 2017
There are no Stock Firmware Images, No Custom Recovery, No Root Method.
Without any of those available Unlocking Bootloader has little Value, and lots of risks.
Official PH-1 windows drivers are up, with Official builds.
https://essential-live.herokuapp.com/developer/current-builds thanks for update @bmg1001 -14 Nov 2017
I haven't seen any Official Windows USB drivers (adb/fastboot) posted any where so i just used Google Pixel Drivers.
Official Google Drivers
Selecting correct drivers in Device manager
Adb seems to work with Windows default drivers, but i had to update ADB.exe version
SDK Platform-Tools for Windows ~3MB
If you have never used ADB
[Index] Setting up and Using ADB/Fastboot
[TOOL]Minimal ADB and Fastboot [1-6-17] by shimp208
Enabling Dev Options
See post #2
ADB Setup/ Troubleshooting
See post #3

Enable Dev Options..
Settings/About phone
Tap on Build number, until you see "You are now Developer"
Back up one screen (Main Settings Page)
tap Developer options
Optional
Toggle on Stay Awake (if you are new to this)
If you are plan on Unlocking Bootloader
Toggle On OEM unlocking
Select Enable (on popup window)
Required
Toggle On USB debugging
Watch for Allow USB debugging popup on Phone
recommended
check box Always allow from this computer
then OK

Testing ADB setup by booting to bootloader
Code:
adb reboot-bootloader
If that code doesn't work you may need to update adb

Fastboot setup
Fastboot commands only work with the device in Fastboot/Bootloader Mode
Boot the Device to Bootloader Options
Code:
adb reboot-bootloader
Power off, Hold Volume Down Button, Power On
Connect To PC via USB
Open PC Device Manager (Settings/Devices/Device Manager)
Look For Mata
Update Driver (Right Click on Mata)
Browse My Computer for Driver Software
Let Me Pick from a List of Available Drivers
Select your Device's Type: ADB
Select the Driver ypu want to Install
Manufacture: Google
Model: ADB Testing (there may be a better one)
Select: Next
PH-1/Mata should look like this
If You don't see adb drivers in available drivers
Try installing l Google Drivers in post #1

I'm using the minimal adb&fastboot, do you think that's the problem?
edit: see attached thumnail, I looked at your photos and followed the instructions. On my windows I get the following options. I tried the two "ADB testing interface" options and neither seem to allow me to perform fastboot commands. If I type fastboot devices nothing happens while the device is in fastboot mode. The ADB commands while the device is powered on do work though.

elsamuraiguapo said:
I'm using the minimal adb&fastboot, do you think that's the problem?
Click to expand...
Click to collapse
no, you need to select the correct driver in Device Manager

Looks like Minimal ADB and Fastboot hasn't been updated since 6th January 2017
So that could be an issue

Updated post #4
to explain images in post #1

sd_shadow said:
no, you need to select the correct driver in Device Manager
Click to expand...
Click to collapse
I did. Check out the picture in my post above. Also I tried to install everything again from the beginning using the [TOOL] [WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.4.3 by*Snoop05 and that didn't work either.
Is yours the Sprint variant?

elsamuraiguapo said:
I did. Check out the picture in my post above. Also I tried to install everything again from the beginning using the [TOOL] [WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.4.3 by*Snoop05 and that didn't work either.
Click to expand...
Click to collapse
Doesn't look like that has been updated since October 2016
i would use the ADB files direct from Google, link in post #1
Is yours the Sprint variant?
Click to expand...
Click to collapse
No, but if bootloader wasn't Unlockable, the OEM unlocking option in Settings should be Greyed out and unselectable

[TOOL] [WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.4.3 by*Snoop05
adb-setup-1.4.3.exe
has adb version Android Debug Bridge version 1.0.32 Revision eac51f2bb6a8-android
and fastboot commands didn't work for me with Mata

ADB version working for me is
Code:
adb version
adb version
Android Debug Bridge version 1.0.39
Revision 3db08f2c6889-android

[TOOL]Minimal ADB and Fastboot [1-6-17] by shimp208
minimal_adb_fastboot_v1.4.2_setup.exe
Android Debug Bridge version 1.0.36
Revision 0e9850346394-android
does appear to be workng

sd_shadow said:
[TOOL]Minimal ADB and Fastboot [1-6-17] by shimp208
minimal_adb_fastboot_v1.4.2_setup.exe
Android Debug Bridge version 1.0.36
Revision 0e9850346394-android
does appear to be workng
Click to expand...
Click to collapse
Okay, I was using an outdated version so I updated to v1.4.2, but still same problem with the fastboot commands. You said to download the google drivers from post #1. I downloaded it and it gives me a ZIP; sorry to sound like a noob but I can't find a .exe in that ZIP to install. I open up the zip and these are the files I see in the usb_driver folder it produces.
Thanks for your quick replies so far by the way.

elsamuraiguapo said:
Okay, I was using an outdated version so I updated to v1.4.2, but still same problem with the fastboot commands. You said to download the google drivers from post #1. I downloaded it and it gives me a ZIP; sorry to sound like a noob but I can't find a .exe in that ZIP to install. I open up the zip and these are the files I see in the usb_driver folder it produces.
Thanks for your quick replies so far by the way.
Click to expand...
Click to collapse
You seem to have the same driver that I have
Adb...1.0.10.0 with 2010 date

sd_shadow said:
You seem to have the same driver that I have
Adb...1.0.10.0 with 2010 date
Click to expand...
Click to collapse
Well I uninstalled all the drivers I could find on my computer to start from scratch. Which should I install? I can't figure out how to install the google usb drivers referenced above

Download latest_usb_driver_windows .zip
Right Click Extract All
Open Folder latest_usb_driver_windows / USB_Driver
Right Click android_winusb.inf
Select Install
Connect Device to PC
adb reboot-bootloader
Select Window menu/Settings/Devices/related Settings/Device Manager
In Device Manager
Right Click Meta/PH-1
Select Update Driver
Browse My Computer for drive Software
Let me Pick From A List of Available drivers
Select Android Device
Select Android ADB Interface
Click Yes at Update driver Warning
Close
Driver selected should be Google 11.0.0.0
If Android ADB Interface is not an option
Uninstall device in Device Manager
Then disconnect and reconnect Device
try again

sd_shadow said:
Download latest_usb_driver_windows .zip
Right Click Extract All
Open Folder latest_usb_driver_windows / USB_Driver
Right Click android_winusb.inf
Select Install
Connect Device to PC
adb reboot-bootloader
Select Window menu/Settings/Devices/related Settings/Device Manager
In Device Manager
Right Click Meta/PH-1
Select Update Driver
Browse My Computer for drive Software
Let me Pick From A List of Available drivers
Select Android Device
Select Android ADB Interface
Click Yes at Update driver Warning
Close
Driver selected should be Google 11.0.0.0
If Android ADB Interface is not an option
Uninstall device in Device Manager
Then disconnect and reconnect Device
try again
Click to expand...
Click to collapse
Okay awesome, I think we're almost done. When I type in fastboot devices I can see the device now. Starts with PM1. What command did you use to unlock the bootloader? I tried fastboot oem unlock and "fastboot flashing unlock" and it failed. (remote: unknown command)
Edit: Never mind it worked now after a few attempts. Weird cause I typed the same command over and over and it kept failing. Anyway looks like it rebooted successfully after the factory reset. Thanks for your help mate. Now I can set up the device to my liking and just wait until we get customer recovery and root.

Hi guys, same issue here with OPENUS version of the MATA PH-1.
I have installed 15 seconds ADB driver 1.43 clean on laptop and can access the phone with ADB and reboot it into bootloader.
However, 'fastboot devices' gives me nothing. I've updated the Mata in device manager first with the options from the 15 seconds ADB, with are 'Android ADB Interface', 'Android Bootloader Interface' and 'Android Composite ADB Interface'. None of them give me any luck when trying 'fastboot devices', nothing found.
Then, uninstalled the ADB driver from device manager so that it showed Mata again, installed Google driver from 1st post, but same thing: version 11.0 of Google drivers (28/08/2014) with same choices, but none of them work.
Does this have to do with the USB A 3.0 --> USB C cable maybe? Or is it just a driver thing?
BTW reason for unlocking is so that I can root later without wiping the device, once root becomes available..

updated post 1 a bit