Related
I have put together a little program to allow me to install recovery quicker because I got fed up of it taking so long.
Its dead easy to use!
instructions
download file
unzip
connect vega and make sure usb debugging in enabled
click windows_install, mac_install, or linux_install to flash depending on what your running (u should know that )
wait for that to finish
to boot into recovery click the recovery icon in your app draw
Download v3 clicky - mirror 1
another v3 - mirror 2
For those of you that are having an "error: device not found"
It means that you dont have the adb drivers installed correctly
To check right click on the windows folder and click command prompt here. then type adb devices
If nothing shows up then it means the drivers arent installed
To install them correctly follow this guide
http://android.modaco.com/content/advent-vega-vega-modaco-com/327084/what-to-do-when-your-usb-drivers-are-wrong-win7-64/
Click to expand...
Click to collapse
v1 - windows only
v2 - added mac and linux
v3 - updated to CW 3.0.2.8
thanks go to @mad murdock for making the image and now for fast mirrors
also thanks to @bob1369 who has made a mac and Linux version
i have created mac and linux versions
linux; http://www.megaupload.com/?d=JNEP1GJ5
mac; http://www.megaupload.com/?d=O73B61F0
i suggest creating a small automator app on the mac to further speed installation of clockworkmod just drag run shell script into a work flow and write in the box below the code you would usually use to run the script from terminal e.g.
cd /route/to/script
./install.sh
This worked a treat for me.
I used it to update cwm to the latest version.
Thanks very much for a time saving app.
bob1369 said:
nice little app have a look at this thread though
http://www.villainrom.co.uk/forum/showthread.php/4483-GUIDE-I-think-I-have-bricked-my-vega
restore nandroid through nvflash including cwm of course just a bit quicker thanks to lennyuk for pointing me to it
i have also created mac and linux versions (untested)
linux; http://www.megaupload.com/?d=K79J2BXY
mac; http://www.megaupload.com/?d=QF2YKI4Y
update: i have tested the mac version and discovered the message cannot chmod etc is displayed but script finishes and recovery is installed will rectify soon
Click to expand...
Click to collapse
ahh nice work! i will add to the first post and mention you
i will test linux some time
bob1369 said:
nice little app have a look at this thread though
http://www.villainrom.co.uk/forum/showthread.php/4483-GUIDE-I-think-I-have-bricked-my-vega
restore nandroid through nvflash including cwm of course just a bit quicker thanks to lennyuk for pointing me to it
i have also created mac and linux versions (untested)
linux; http://www.megaupload.com/?d=K79J2BXY
mac; http://www.megaupload.com/?d=QF2YKI4Y
update: i have tested the mac version and discovered the message cannot chmod etc is displayed but script finishes and recovery is installed will rectify soon
Click to expand...
Click to collapse
I have tested the linux version. It works. Same thing with the chmod... I guess you cannot chmod something that is not there.. Just remove the trailing slash. It should work then....
help
my computer cant detect my advent vega
i try xp win7 and vista
help
device no find
after i use install
the word"device no find"
anyone help
fung58745 said:
after i use install
the word"device no find"
anyone help
Click to expand...
Click to collapse
on the vega or pc?
on pc and my vega is in usb debug
same ad "add.thebad " devices not find
my i hav been setup up adb
well done! pretty userfriendly - will link to this post
i mirrored your files - if thats okay with you. at least mirror 1 got gigabit ethernet connection - i download with 2mb/s from it (my local maximum). if you dont wanna use that mirror, tell me, i remove files and links
had to rename file since spaces are no-go the _noflash hopefully keeps "cwm gives error due flashing" on a low degree - people tend to flash every .zip from recovery.
hope that helps...
mirror1: clockwork_recovery_3.0.2.4_vega_noflash.zip size: 73M (76109336 bytes)
mirror2: clockwork_recovery_3.0.2.4_vega_noflash.zip md5sum: 4d8cf9aa85331e8e2673b3406646fbc5
fung58745 said:
on pc and my vega is in usb debug
Click to expand...
Click to collapse
fung58745 said:
same ad "add.thebad " devices not find
my i hav been setup up adb
Click to expand...
Click to collapse
odd, does the vega show up if you do "adb devices"?
mad-murdock said:
i mirrored your files - if thats okay with you. at least mirror 1 got gigabit ethernet connection - i download with 2mb/s from it (my local maximum). if you dont wanna use that mirror, tell me, i remove files and links
had to rename file since spaces are no-go the _noflash hopefully keeps "cwm gives error due flashing" on a low degree - people tend to flash every .zip from recovery.
Click to expand...
Click to collapse
o yeah, that speedy download is nice i will put in first post thanks.
i have merged mac and linux as well attatched to first post
i will pm
same here. device not found.
adb devices output:
Code:
List of devices attached
So device was not found for some reason. Will try adb bundled in android sdk and also reboot device etc etc.
fused#1 said:
same here. device not found.
adb devices output:
Code:
List of devices attached
So device was not found for some reason. Will try adb bundled in android sdk and also reboot device etc etc.
Click to expand...
Click to collapse
It seems like its not using the right driver for some reason....
edit: forgot to say, Windows 7
fused#1 said:
It seems like its not using the right driver for some reason....
edit: forgot to say, Windows 7
Click to expand...
Click to collapse
are you sure you have the vega installed correctly. go to devises and printers > nvidia harmony > hardware and tell me what you see in that list
add.thebad said:
are you sure you have the vega installed correctly. go to devises and printers > nvidia harmony > hardware and tell me what you see in that list
Click to expand...
Click to collapse
This is what I see:
Android Debug Bridge Interface
G:\
Nvidia Tegra 2 USB Device
USB Mass storage
USB Device
(last 2 roughly translated from german)
fused#1 said:
This is what I see:
Android Debug Bridge Interface
G:\
Nvidia Tegra 2 USB Device
USB Mass storage
USB Device
(last 2 roughly translated from german)
Click to expand...
Click to collapse
hmmm, a little confused by this one. mines works correctly and shows up under adb devices but mine shows up as android composite adb interface
try an install like this
http://android.modaco.com/content/advent-vega-vega-modaco-com/327084/what-to-do-when-your-usb-drivers-are-wrong-win7-64/
i think that should set it up right
have you used the vega and adb before?
Thank you. I will try that right now. Used adb with a desire until today.
It appears (and this has been verified by multiple installs by myself and people on #android and #android-dev on freenode) that fastboot has been removed from the R14 release of the Android SDK.
Does anyone know how to get fastboot via another method so I can unlock the boot loader of my Nexus S (my platform is Windows 7 SP1 X64)?
Thank you in advance.
I think I found the answer to my own question:
http://dl.google.com/android/android-sdk_r13-windows.zip
I don't think it's been a part of the Android SDK, at least for a while. I've always had to manually download the binary.
It can also be made in your build environment. Command: make fastboot. It will create the binary.
where to put that command? thx
Here's fastboot.exe: http://www.mediafire.com/?wrgw1erxw71o77a
geo741 said:
where to put that command? thx
Click to expand...
Click to collapse
You have to place it in the same folder containing adb.exe (platform-tools for the last sdk).
JCASE HAS DONE IT GUYS:
http://www.forum.lepanlife.com/showthread.php?tid=322
No luck,
I followed the steps, but when I connected the Lepan2 to the computer, it started to find devices, and finally it got this as I show in this graphic:
imageshack.us/f/838/anydatahsusbdevice.jpg (I cannot post links so I place it like that)
So I tried the 'update driver software" for the one with the yellow question mark under "Other Devices" called ANY_DATA HSUSB Device" and none i386 or amd64 work with that device. I don't know why it shows 2 devices, the other as you can see is under "Portable Devices" and it was recognized by Windows 7 64-bit witch is the OS i'm running. Also if I right-click on that "LePanII" device and select 'update driver software' and point to the unzipped files that you posted above, it says that "The device LepanII already has the best windows drivers"
So when I run SuperOneclick, the one you also posted above, the application became "unresponsive' after clicking on "Root"
I checked on windows task manager and there are 2 adb.exe processes running, and the only way I can terminate the Superoneclick app is by terminating those 2 adb.exe processes. I have tried several times and same result, it becomes unresponsive after starting adb server on port 5037
rocketero said:
No luck,
I followed the steps, but when I connected the Lepan2 to the computer, it started to find devices, and finally it got this as I show in this graphic:
imageshack.us/f/838/anydatahsusbdevice.jpg (I cannot post links so I place it like that)
So I tried the 'update driver software" for the one with the yellow question mark under "Other Devices" called ANY_DATA HSUSB Device" and none i386 or amd64 work with that device. I don't know why it shows 2 devices, the other as you can see is under "Portable Devices" and it was recognized by Windows 7 64-bit witch is the OS i'm running. Also if I right-click on that "LePanII" device and select 'update driver software' and point to the unzipped files that you posted above, it says that "The device LepanII already has the best windows drivers"
So when I run SuperOneclick, the one you also posted above, the application became "unresponsive' after clicking on "Root"
I checked on windows task manager and there are 2 adb.exe processes running, and the only way I can terminate the Superoneclick app is by terminating those 2 adb.exe processes. I have tried several times and same result, it becomes unresponsive after starting adb server on port 5037
Click to expand...
Click to collapse
Yep, Bear was having the same issues when he tried. Adam and I have fixed the drivers partially (they are re-uploaded, so re-download them). When you use the re-up'ped drivers and update the AnyData HSUSB Device it will work now and change it to an Android ADB Composite Interface Device.
However, getting ADB working is another story. Adam and myself have been working on Bear's computer remotely and we've done what we can do from there. When we both get our Le Pan II's this week (Tues/Wednesday, respectively), we are going to push forward full speed ahead in Linux to attempt to get ADB to recognize the device.
It's started to look like the drivers that leaked are not for the LP2, which is disappointing to say the least. In order to root it without the drivers, it's gonna take time and patience and we're going to need to find an unpatched exploit in the HC OS by modifying Gingerbreak or Zerg.
I'll keep you updated as it progresses.
Hey,
Could any of you owners of the Le Pan II (TC979) do a dump of the ROM?
(including the drivers, kernel, etc)
It would be GREATLY beneficial to the XDA / RootzWiki HP TouchPad community since it would assist with the development of Ice Cream Sandwich, given how similar, if not identical the hardware on the Le Pan II is to the HP TouchPad.
Thanks.
PresidentMcCain said:
Hey,
Could any of you owners of the Le Pan II (TC979) do a dump of the ROM?
(including the drivers, kernel, etc)
It would be GREATLY beneficial to the XDA / RootzWiki HP TouchPad community since it would assist with the development of Ice Cream Sandwich, given how similar, if not identical the hardware on the Le Pan II is to the HP TouchPad.
Thanks.
Click to expand...
Click to collapse
As soon as we get this thing rooted, I'd be more than happy too
We have no firmware files, just OTA updates - they do not post firmwares, source code, adb drivers or anything on their site. But we'll get it and when we do, I'll get you that info.
dbaybay said:
As soon as we get this thing rooted, I'd be more than happy too
We have no firmware files, just OTA updates - they do not post firmwares, source code, adb drivers or anything on their site. But we'll get it and when we do, I'll get you that info.
Click to expand...
Click to collapse
Maybe this will help you with ADB drivers:
http://rootzwiki.com/topic/15624-how-tocm9-adb-interface-on-usb/
---------- Post added 24th January 2012 at 12:15 AM ---------- Previous post was 23rd January 2012 at 11:50 PM ----------
If you can at least use Root Explorer to zip up some of it, it'd be helpful
(I believe the drivers are .so files in the lib folder under /)
dbaybay said:
Yep, Bear was having the same issues when he tried. Adam and I have fixed the drivers partially (they are re-uploaded, so re-download them). When you use the re-up'ped drivers and update the AnyData HSUSB Device it will work now and change it to an Android ADB Composite Interface Device.
However, getting ADB working is another story. Adam and myself have been working on Bear's computer remotely and we've done what we can do from there. When we both get our Le Pan II's this week (Tues/Wednesday, respectively), we are going to push forward full speed ahead in Linux to attempt to get ADB to recognize the device.
It's started to look like the drivers that leaked are not for the LP2, which is disappointing to say the least. In order to root it without the drivers, it's gonna take time and patience and we're going to need to find an unpatched exploit in the HC OS by modifying Gingerbreak or Zerg.
I'll keep you updated as it progresses.
Click to expand...
Click to collapse
I just downloaded again the link for "Drivers" and I connected the Lepan2 again to the computer and the same problem as before.
Then I checked the "File hashes" for the files "WdfCoInstaller01009.dll" and the other 2 inside the folder "amd64" and the cr32/md5/sha-1 are identical for the ones I had downloaded before and this ones. So where are the new ones you said you re-uploaded ?
About the ROM, I am also interested on obtaining the "original" ROM that came with the LepanII, as I updated the system with a still-in-development that Lepan tech support had uploaded to the server without even first testing it, and now I can not revert back to the original because they have not provided to me in a support-ticket I opened at their website. I don't know much about ROM extracting or management but I could learn a thing or two about it.
WHOOOOOOOOOOOOOOOOOOOO!!!!
I got ADB working on the Le Pan 2!!! Screw Le Pan and their locked down drivers!
I can't get root access yet, but I got a sysdump and am combing through it. Recovery doesn't show the device being plugged in and I can't figure out how to get into fastboot as of yet, but progress is being MADE!
There is not rush, in the mean time I opened a ticket at lepan.supportsync.com to see if they supply me with this driver. who knows I may get lucky.
rocketero said:
There is not rush, in the mean time I opened a ticket at lepan.supportsync.com to see if they supply me with this driver. who knows I may get lucky.
Click to expand...
Click to collapse
Been there, done that. Hopefully you'll have better luck, but their standard reply is to email two people from HQ if you are a developer, which I've also been there and done that. They don't reply. I'm fairly positive that we are on our own considering they didn't release the ADB drivers for the LP1 or LP2 as of yet and no source code for either, either. They are GPL-violators to the MAX. *puke*
We'll get it tho.
dbaybay said:
WHOOOOOOOOOOOOOOOOOOOO!!!!
I got ADB working on the Le Pan 2!!! Screw Le Pan and their locked down drivers!
I can't get root access yet, but I got a sysdump and am combing through it. Recovery doesn't show the device being plugged in and I can't figure out how to get into fastboot as of yet, but progress is being MADE!
Click to expand...
Click to collapse
Can you please upload somewhere zip with content of /system/lib/? One of the major problems community have with porting of ICS to any Qualcomm platform is absense of userspace video drivers (and inability to run hw-acceleration). TC979 seems to have hw-accel enabled in Honeycomb, which is quite close to ICS in this area.
ghuron said:
Can you please upload somewhere zip with content of /system/lib/? One of the major problems community have with porting of ICS to any Qualcomm platform is absense of userspace video drivers (and inability to run hw-acceleration). TC979 seems to have hw-accel enabled in Honeycomb, which is quite close to ICS in this area.
Click to expand...
Click to collapse
As soon as I can get ADB working in recovery or fastboot and have root access, I will be glad to, as I already said before. ADB is working when the device is running normally, but I do not have SU privileges. I can see the list of files, but can't copy, push, pull, or anything as of right now. My project for today is to get ADB working in fastboot so I can get root permissions.
dbaybay said:
As soon as I can get ADB working in recovery or fastboot and have root access, I will be glad to, as I already said before. ADB is working when the device is running normally, but I do not have SU privileges. I can see the list of files, but can't copy, push, pull, or anything as of right now. My project for today is to get ADB working in fastboot so I can get root permissions.
Click to expand...
Click to collapse
I thought adb pull /system/lib/ does not require root
ghuron said:
I thought adb pull /system/lib/ does not require root
Click to expand...
Click to collapse
Nor did I, but I'm getting permission denied for about everything except adb reboot [recovery / bootloader] or 'ls'. SU, Pull, Push, Root, Remount, etc. etc. etc. are giving me "permission denied" or "can't in manufactor mode" errors.
I'm working on getting it to work in Fastboot, but ADB just won't recognize the device in Fastboot no matter what I do. I'm at a loss right now, so any suggestions would be helpful. I'm gonna keep trying different methods to get ADB to work with root permissions.
Code:
$ pull /system/lib c:\users\admin\desktop
pull /system/lib c:\users\admin\desktop
pull: permission denied
$
A list of the contents is the best I can get for you atm - http://pastebin.com/ZqvXqE0Q
Those files are exactly what the HP Touch pad needs
---------- Post added at 08:03 PM ---------- Previous post was at 08:01 PM ----------
are you sure you can't install superuser ?
PresidentMcCain said:
Those files are exactly what the HP Touch pad needs
---------- Post added at 08:03 PM ---------- Previous post was at 08:01 PM ----------
are you sure you can't install superuser ?
Click to expand...
Click to collapse
110% positive.
I have no permissions to do anything except CD into folders and get a list, or reboot into recovery or bootloader. In bootloader ADB and fastboot do not recognize the device and the modified drivers do not work. We are working on it, but no such luck as of yet. As soon as I can gain SU permissions in ADB, I'll get you the files, don't worry.
dbaybay said:
110% positive.
I have no permissions to do anything except CD into folders and get a list, or reboot into recovery or bootloader. In bootloader ADB and fastboot do not recognize the device and the modified drivers do not work. We are working on it, but no such luck as of yet. As soon as I can gain SU permissions in ADB, I'll get you the files, don't worry.
Click to expand...
Click to collapse
just a simple question: how do you get out of bootloader mode? After I did "adb reboot bootloader", I got to a black screen with the text "Fastboot Mode" and then nothing works, not even the power button. Can't access it via USB either. Guess I can wait till the battery runs down, but there should be a simpler way...
Edit: never mind, the reset button worked
anonguy2 said:
just a simple question: how do you get out of bootloader mode? After I did "adb reboot bootloader", I got to a black screen with the text "Fastboot Mode" and then nothing works, not even the power button. Can't access it via USB either. Guess I can wait till the battery runs down, but there should be a simpler way...
Click to expand...
Click to collapse
Try holding power button + home button at same time for 10 seconds.
Bootloader/fastboot are the same thing from my understanding. When I use adb reboot bootloader, it reboots to my fastboot screen. I use the reset button, as you figured out to get out of it.
I need to get adb or fastboot.exe [platform tools] working in fastboot mode and I should have root access but no such luck.
Any Le Pan II users who managed to get the v116 update - did you get an update.zip placed on your SD Card that you can share? If I can get an properly signed update.zip with the stock ROM inside, I can most likely modify it for with SU access built in.
this may be a stupid question, does this app http://www.androidapps.com/finance/apps/299480-root-explorer-file-manager-speed-software give you root access or do you need to have root permission in order to use that app.
I have a B90 TF101 and I am able to get into recovery mode. I have no ROM on my internal SD card and have wiped and formatted everything. I have read that it is possible to push a file using ADB while in recovery.
However I am not able to see my device when I use the adb devices command. I noticed that the drivers for the transformer are not installed. So I tried to install them and it tells me that windows can't install. I am pointing the installer to the MTP devices driver folder.
How do I get the drivers to work so I can use ADB or can I set up ADB in Linux and not have to worry about the drivers?
edit: I forgot to mention I am running windows vista.
Hi! Search in transformer's support page, you can find the drivers there
Are you saying that the drivers in the MTP folder are not the right ones? I got them right from Asus' website. Which drivers should I be using?
Ageesaman, did you ever get the drivers working? I had the exact same problem (got adb working as far as listing devices, but then it returned with a blank line after "adb devices" in cmd window). I downloaded the ASUS site's USB drivers download as well as every other utility from that site; I also tried external sources; finally, I tried manually updating by pointing to the unzipped MTP folder - nothing worked. I used both 64 and 32 bit Windows 7 machines. I am stuck in the cwm recovery loop so I can't do much troubleshooting. I tried searching dozens of sites for several hours but came up short.
Thanks in advance for any help offered.
Unfortunately I have not found a solution to getting the drivers installed. I was hoping someone would be able to confirm/deny if I can do this in Linux without the drivers before going through with setting it up. However that will be my next step as soon as I have the time to do it.
Ageesaman,
Unfortunately I know nothing about Linux, but what finally got it working for me was starting the installation of PDANet for Android. I saw it look for and install the driver, then I got a ADB confirmation. I then canceled the PDANet install. If you decide to go this route and get error messages in the cmd window, retry "adb devices" up to 3 times. In the meantime, I hope you get your Linux answer. Good luck.
I will give that a try. Is PDAnet something from Asus? I will do a search and see if I can find it.
ageesaman said:
Unfortunately I have not found a solution to getting the drivers installed. I was hoping someone would be able to confirm/deny if I can do this in Linux without the drivers before going through with setting it up. However that will be my next step as soon as I have the time to do it.
Click to expand...
Click to collapse
Yes, I can confirm the TF101 works with ADB without drivers on Ubuntu linux [I am on 11.04]. The current [stable, with 12.04 betas] Ubuntu version is 11.10, and you can download it to a live CD and run it off the CD without installing it.
I just got my tf101 the other day and I tried using adb [and older version], and it did not show up. Then I downloaded the tf101 root.zip file, and tried the adb within that folder, and it worked.
I've uploaded it to mediafire:
adb-1.0.29 http://www.mediafire.com/?hqwxbljs2gbpfxe
md5 64c4afbab6d2f769ddbb229f0247cf8a
update: newest adb is 1.0.31 http://www.mediafire.com/download.php?vcvc4dxkdd57695
md5 ed5c8f9a221cae0cb24d6cdc8b76d396
download, and run
chmod +x ./adb-1.0.29
to make it executable
That worked! I can now connect to my device with ADB. Thanks for that pdanet advice.
Now I just need to figure out how to push the file. Can't seem to get it to work. Here is what I am typing in the cmd line.
adb push rom.zip /sdcard
The rom I am trying to push is in the Platform tools folder that I am using to access adb. Does anybody know what I am doing wrong? Any help would be awesome.
is the rom.zip in the same directory as you are in (cd <path>)?
What does it say when you try to transfer it?
You can also try to push it to the full path (/mnt/sdcard/)
The first issue I had was that Asus sync was on and causing problems. As soon as I shut that off ADB started to work and act normal.
The file is in the same path.
When I try the transfer it looks like it finishes and it just tells me the file size. It actually seems like it works I just can't find the file when it is finished. I tried rebooting recovery but it seems like the file is just not there.
I will try the /mnt/sdcard/ and see if that works.
ageesaman said:
The first issue I had was that Asus sync was on and causing problems. As soon as I shut that off ADB started to work and act normal.
The file is in the same path.
When I try the transfer it looks like it finishes and it just tells me the file size. It actually seems like it works I just can't find the file when it is finished. I tried rebooting recovery but it seems like the file is just not there.
I will try the /mnt/sdcard/ and see if that works.
Click to expand...
Click to collapse
It's probably because /sdcard is a soft link to /mnt/sdcard/
if you did /sdcard/, I think it should probably work.
You sir are the man! Thanks for your time.
To get the process all in the same place for anyone else who may need this here you go. Just to make it clear.... This is what I did on my device and it worked. It may or may not work for you but maybe it's worth a try.
1. Downloaded SDK and Java JDK.
2. Used PDAnet to force windows to install the correct ADB device drivers.
3. When the drivers where installed and ADB was working I used this command to push the .zip file to the internal sd card.
adb push rom.zip /sdcard/
Just a few notes for this.
ADB was not working well at first because I had Asus sync running in the background. Make sure this is off.
Also make sure you put the file you are trying to push in the same directory you are using for ADB. For instance I used C:/android-sdk/platform-tools/ to access ADB so the file had to be in that folder in windows explorer.
To make it easier to type (I had to do this a lot while troubleshooting) I changed the name of the rom I was trying to push to rom.zip. This made typos less of an issue.
Make sure that you put the file extension (.zip in my case) in the ADB command even if it doesn't say it when you look at the file in windows explorer.
I think that is it in a nutshell. I hope this helps anyone else who needs to push a rom.
Good Luck
This method in this post didn't work for me, but this one did: http://forum.xda-developers.com/showthread.php?t=1689193
I set Windows to look for driver in c:. After a while one was installed and worked.
What I did on windows 7
Go to Device manager
Find transformer , right click on faulty marked unit.
Select properties
go to tab driver
update driver
Select browse
select path to the subfolder ANDROID ( containing usb drivers from asus )
include subfolders
Windows will find to alternatives , choose xxxx ADB
Windows will complain, ignore
done
/Claes R
W
Can someone please zip and upload these from the newest SDK with secure USB debugging (4.2) so I don't have to download a full new SDK. [Got these already]
I could also use a new adb binary for use on-device from terminal or script (or is it the same one?).
Thks
[Edit]
That would be 1.0.30 or above for the on-device adb. Can someone on a 4.2 ROM shoot me this file?
Thks
[Edit]
Guess there were too many bricks this week _that demanded attention. No biggy, I just downloaded the new SDK but I still need adb 1.0.30 or newer for on-device use. If someone gets a chance I would appreciate it. I will zip and post the API 17 (4.2.2) versions of adb and fastboot for anyone else that may need them.
Thks