I need to revert back to S-ON for a replacement phone. When I get to fastboot and type "fastboot oem writesecureflag 3", my command prompt tells me that fastboot is not a recognized command. ADB works fine when the phone is on and I used it to get into fastboot. Have I missed a vital step?
Also, YES, I searched quite a bit but couldn't find what I was looking for. Any and all help would be appreciated.
Do you have the actual Fastboot executable in your path? It should be in the same place as the ADB executable within your SDK installation. I guess it could actually be anywhere, but that seems like the most logical place.
Thats an excellent question. I'll have to check when I get home.
Yikes. I feel like that's as close to "is it plugged in?" as I ever want to get.
Also, after running the Tmous RUU, the "Revolutionary" went away from the fastboot screen. Wonder if it now looks like those rare phones that were sent out S-OFF right out of the box...
Sent from my pizza slice using XDA Premium App
Okay, yeah. It was in the tools folder instead of the platform-tools folder where I have adb.exe.
Can I simply move fastboot.exe over to platfrom-tools or is there something else it will need to run?
Nah, you can just move it over. Better yet though, you might want to just add the "tools" folder to your path. I do this on Linux, and my ADB executable and Fastboot executable are both in the "platform-tools" folder. I think I might have just moved Fastboot from its original place in "tools" though. Either way, you can just move it over if you wish.
Sorry for the late reply but thank you very much.
I ended up copying the ones I use most often to the root directory on C:\
This way I don't have to poke around to find what I need. Poking around is strictly reserved for time with the wife...well as of today it's girlfriend when I find one...
Related
EVO 4G with 2.2, I've been trying to root this phone for hour's. Ive got everything downloaded and filed correctly on my computer. Using windows 7. Followed all of the steps as I should. When I get to the command prompt part of the procedure my computer tells me "adb is not recognised as an internal or external command" I've opened the adb in the tools folder and it does not say adb.exe. So I understand why my computer doesnt see it as a command file but why isnt it comming up as a command file. What am I doing wrong? Please help. Scott.
Are you holding the Shift key while right clicking on tools?
No I'm not holding the shift key.
also sounds like you are not in the right directory. Did you first do the cd to the path of the SDK and adk install?
I dont know. I tried to follow the instructions but to some one who doesn't understand command functions and how to use them, this stuff is very intimidiating. If some one could take the time to give me a more detailed step by step of how to move the files and make the folders do what they need to do I would really appreciate it. Kinda like making me a "rooting your evo for dummies" instruction. I realise this sounds silly but I'm just not doing some thing right. Thanks, Scott.
I rooted my hero on 2.1 before on a different computer a while back so im fairly familiar with this process. But i when i type in the file path for the C:\android-sdk-windows\tools and hit enter then type adb devices i get an error message that says
'adb' is not recognized as an internal or external command,
operable program or batch file.
I tried all the troubleshooting i can think of like
making sure its the right path to the tools final
making sure debugging is on
deleting the drivers
reinstalling htc sync
I dont know is this info is relevant but ill share it any way.
Im running windows xp
its an old work pc so idk if i have Admin rights(How do i check??)
If any of you can help thatd be much appreciated
Did u add tools directory to the PATH?
Sent from my HERO200 using XDA App
Hey bird, I had the same problem a few days ago. solution for me was, that adb is not located in the tools folder anymore. its located in another folder.I'm not in front of my pc right now.just check where in the windows sdk folder the adb.exe is located now.
Hope that helps you too.
Greetz ricola
Sent from my HTC HD2 using XDA App
if its the updated sdk you will have to update it. close and restart,and then reopen your run command and type in \platform\tools\. they changed the file path when they updated the new tools.
ricola7 said:
Hey bird, I had the same problem a few days ago. solution for me was, that adb is not located in the tools folder anymore. its located in another folder.I'm not in front of my pc right now.just check where in the windows sdk folder the adb.exe is located now.
Hope that helps you too.
Greetz ricola
Sent from my HTC HD2 using XDA App
Click to expand...
Click to collapse
Thank you very much i searched for adb.exe and found it in the platforms-tools folder thank you.
If any of you can help thatd be much appreciated
Click to expand...
Click to collapse
I'm too tired to read the whole thread right now, so someone has probably answered this, but here goes..
Previous versions of the Android SDK, adb was located in the tools folder, ie: if you installed the android SDK at C:\android-sdk-win, it would be c:\android-sdk-win\tools
The new release of the android sdk, adb has been moved, and is now located in the \platform-tools folder , ie; c:\android-sdk-win\platform-tools
much like the forums, file search is your friend sometimes
take care
So i've got the SDK installed, and i THink i ahve ADB installed correctly (i can run commands and get results evn though i have no idea what to do with them)
But i dont know how to get a screen cap of wht is on my Tablet...is there an app i should be using?or is this not somethingi need to do via ADB?
Darkeyce said:
So i've got the SDK installed, and i THink i ahve ADB installed correctly (i can run commands and get results evn though i have no idea what to do with them)
But i dont know how to get a screen cap of wht is on my Tablet...is there an app i should be using?or is this not somethingi need to do via ADB?
Click to expand...
Click to collapse
You use DDMS to take screenshots. Take a look in your tools folder in the SDK. There should be a file there named ddms.bat... If not it may be in platform-tools. I usually just copy everything in platform-tools to the tools folder anyway.
To take a screenshot make sure you can talk to your tablet. So do a ADB devices from a command line pointed at your tools folder. It should come back and tell you it found your tablet. Then just run ddms.bat and it will open up a window. You need to select your tablet from the list. It will normally be the top line if you only have one device connected. Then from the menu up top select Device, and then screen capture.
Sprdtyf350 said:
You use DDMS to take screenshots. Take a look in your tools folder in the SDK. There should be a file there named ddms.bat... If not it may be in platform-tools. I usually just copy everything in platform-tools to the tools folder anyway.
To take a screenshot make sure you can talk to your tablet. So do a ADB devices from a command line pointed at your tools folder. It should come back and tell you it found your tablet. Then just run ddms.bat and it will open up a window. You need to select your tablet from the list. It will normally be the top line if you only have one device connected. Then from the menu up top select Device, and then screen capture.
Click to expand...
Click to collapse
Oh, That's just SWEET!
Thanks for the assist
Wondering if anyone can help me, I have been following this guide:
http://forum.xda-developers.com/showthread.php?t=1007782
I get upto installing the drivers and connecting the phone to the PC in fastboot mode, then when I type the "fastboot oem unlock" command it says "waiting for device..." and stays stuck on that.
I have done everything the guide says and tried multiple times and still the same outcome.
It seems that the computer doesn't want to recognise the phone at all.
I have i9023 model with S-LCD screen.
Any ideas?
EDIT: if this helps, when I connect the phone in fastboot mode to the PC it says "STANDARD_SET_CONFIGURATION".
Hmm...do you have the fastboot binaries installed on your computer?
mathkid95 said:
Hmm...do you have the fastboot binaries installed on your computer?
Click to expand...
Click to collapse
Hmm, maybe not, how do I install it?
Sent from my Nexus S using XDA Premium App
I had to copy a couple of .dll files to my tools folder from the platform-tools in order for it to work (may have been the other way around, I've had a couple of drinks and it was a month ago now).
I believe they were the AdbWinUSBapi.dll and AdbWinApi.dll files, but I could be mistaken. Once I did this, I was able to connect to the phone. Otherwise, it just hung at the fastboot screen and didn't do anything.
VillainousVivi said:
I had to copy a couple of .dll files to my tools folder from the platform-tools in order for it to work (may have been the other way around, I've had a couple of drinks and it was a month ago now).
I believe they were the AdbWinUSBapi.dll and AdbWinApi.dll files, but I could be mistaken. Once I did this, I was able to connect to the phone. Otherwise, it just hung at the fastboot screen and didn't do anything.
Click to expand...
Click to collapse
Thank you, this worked, I had already transferred the AdbWinApi.dll file, but after also transferring the AdbWinUSBapi.dll file into the tools folder it worked!
Thanks for pointing it out .
Can someone who has webtop tar up thier osh and post a place I can grab it.
I have been working to get a full version of ubuntu going in webtop, and I was working on reverse engineering the way they did it with the bionic and that did not work well
I will buy a beer or coffee for anyone who can do this for me.
Thanks,
Jim
just got home. give me a few minutes
what file format you want?
You rock, does not matter much, a tar or zip or 7zip or bz2... whatever you put it in I can take it and put it back in place from there.
Thanks,
Jim
lol. while it was pulling, i was messing around with my phone and crashed it..
re-pulling
OSH.IMG.TGZ
dd if=/dev/block/webtop of=/mnt/sdcard/osh.img
did you get it?
Yes, I did. I also gave a donation to you.
THANK YOU!
Jim
I was able to get my webtop working again, by whacking tomoyo, that is the Linux FACL that they are using for webtop.
Thanks again for your help.
Jim
I just broke webtop and I was hoping you could explain to me how to restore it using this .img.tar.gz file. I don't have a clue what to do with it. Please help! I messed up my osh file pretty miserably.
matthewsteross said:
I just broke webtop and I was hoping you could explain to me how to restore it using this .img.tar.gz file. I don't have a clue what to do with it. Please help! I messed up my osh file pretty miserably.
Click to expand...
Click to collapse
it think it's a dd image, so just do the reverse;
dd if=osh.img of=/dev/block/webtop
I'm sorry. I'm oblivious as to what you're talking about... I'm am sorry for my ignorance, is that a command prompt thing for windows or is that something I would use adb for? Also, how do I thank you for replying?
matthewsteross said:
I'm sorry. I'm oblivious as to what you're talking about... I'm am sorry for my ignorance, is that a command prompt thing for windows or is that something I would use adb for? Also, how do I thank you for replying?
Click to expand...
Click to collapse
This thread was from before we had the FXZ files to flash from fastboot.
I believe the proper way to restore webtop would be to grab the 55.11.16 release FXZ. Extract it and extract moto-fastboot to the same directory. Run a cmd and cd to the directory.
Put your phone into fastboot mode by holding volume down while you power it on, hook it up via usb, and
(or you can use the two button salute and choose it from the boot menu)
Code:
moto-fastboot.exe flash webtop grfs.img
You can then use motorola's faux-55.13.26 update to reapply the patches to update the webtop partition to the 55.13.25 version.
This tar.gz file would still work, you'd need to decompress it, adb shell into the phone, run su (to get root) and then run the commands from the directory where the img is stored. I don't think you need busybox to run dd... could be wrong
Flashing with fastboot is the more elegant solution.
(note it's probably not a good idea to write the img files from the fxz directly with dd.)DON'T CROSS THE STREAMS!
I got it to work by flashing in fastboot, thanks for all your help! All is well again and I even have Linux unlocked and running the XFCE-4 desktop environment. Thanks for all your help!