so i found this: http://ejvyas.blogspot.com/2015/02/cm12aosp-based-rom-gps-fix.html
but for the life of me, I can't seem to enter fastboot modem - my CPU is not recognizing my phone when typing fastboot devices. there has to be another way to clear the modemst1 and modemst2 files via root explorer, right?
jco23 said:
so i found this: http://ejvyas.blogspot.com/2015/02/cm12aosp-based-rom-gps-fix.html
but for the life of me, I can't seem to enter fastboot modem - my CPU is not recognizing my phone when typing fastboot devices. there has to be another way to clear the modemst1 and modemst2 files via root explorer, right?
Click to expand...
Click to collapse
You sure you're opening the command prompt in the directory of your fastboot files.
If not try it.
You have to change the directory of command prompt using cd command
adity said:
You sure you're opening the command prompt in the directory of your fastboot files.
If not try it.
You have to change the directory of command prompt using cd command
Click to expand...
Click to collapse
I'm doing the shift right-click in that directory. for example, if my fastboot files are in c:\temp, I'm opening command prompt in that folder. not sure if it is USB version or not though...
Finally got it to work. I changed lock screen to swipe, used impactor to enter fastboot mode, then enter the command lines via the command prompt. Rebooted, and GPS tracks my movements.
Score!
Sent from my Moto X using XDA Free mobile app
Thanks for the info. I tried It out but when I reboot and try to use GPS by opening maps the phone freezes and reboots.
Never mind found a solution.
sobhambi said:
Never mind found a solution.
Click to expand...
Click to collapse
I have the same issue, what solution did you found?
ososxe said:
I have the same issue, what solution did you found?
Click to expand...
Click to collapse
I reflashed my software and used the GPS Status app. I have changed phones since then so I don't have more detail info on that.
Sent from my Nexus 7 using Tapatalk
Related
Well, Im trying to unroot, however I am having a problem getting into fastboot to remove a second splash screen. When on the "skate boarding" screen, the command prompt on my PC pops up for a second then closes. I'm pretty sure there is something I'm doing wrong, but I just can't figure out what.
Any assistance would be appreciated.
Thanks
CM- 3.9.7
Palm Pre v1.9
So your saying that when you open up command prompt it only stays up for a second and closes.
When I manually open command prompt, it stays open. However, when the PC tries to load fastboot.exe, it opens and closes quickly.
fastboot.exe is a command line utility, running it by itself (without arguments) will produce the behavior you are seeing.
To use it you drop to a command prompt and enter a command such as:
fastboot devices
to see if your phone is being recognized in fastboot mode...
or
fastboot flash system system.img
to flash the system with a backup image.
You get the picture?
uva463 said:
When I manually open command prompt, it stays open. However, when the PC tries to load fastboot.exe, it opens and closes quickly.
Click to expand...
Click to collapse
Your not suppose to open up fastboot.exe
daveid said:
fastboot.exe is a command line utility, running it by itself (without arguments) will produce the behavior you are seeing.
To use it you drop to a command prompt and enter a command such as:
fastboot devices
to see if your phone is being recognized in fastboot mode...
or
fastboot flash system system.img
to flash the system with a backup image.
You get the picture?
Click to expand...
Click to collapse
Thanks for info. After trying to get the phone recognized, I went back and redid everything and found out I had the wrong USB drivers
Thanks again
Not working got to made another one when i be back home.
I have a problem with the computer at work all my zip file are no more working.
I don't know why.
I will make another zip soon
Re: [delete this thread]Flashable zip of Bootloader 4.18 for grouper & tilapia
Yeah works well!
Edit: thought it worked. Stayed on 4.13
Sent from my Nexus 7 using xda premium
[email protected]_OC said:
Not working got to made another one when i be back home.
I have a problem with the computer at work all my zip file are no more working.
I don't know why.
I will make another zip soon
Click to expand...
Click to collapse
Thanks man!
Gave up on fastboot. Dunno why cant get it running!
I tried using fastboot but cant get it to work.
1) Create a folder called fastboot, copy the 4 files + bootloader img into it, and move the folder into C drive.
2) run cmd
3) enter cd C:\fastboot\
4) adb devices. check correct.
5) adb reboot-bootloader
6) fastboot devices. check correct.
7) fastboot flash bootloader bootloader-grouper-4.18.img
8) nth happened.
what went wrong?
o0boiboi0o said:
Thanks man!
Gave up on fastboot. Dunno why cant get it running!
I tried using fastboot but cant get it to work.
1) Create a folder called fastboot, copy the 4 files + bootloader img into it, and move the folder into C drive.
2) run cmd
3) enter cd C:\fastboot\
4) adb devices. check correct.
5) adb reboot-bootloader
6) fastboot devices. check correct.
7) fastboot flash bootloader bootloader-grouper-4.18.img
8) nth happened.
what went wrong?
Click to expand...
Click to collapse
I think you forgot unlock bootloader typing
fastboot oem unlock
Enviado de meu Nexus 7 usando o Tapatalk 2
eric-filth said:
I think you forgot unlock bootloader typing
fastboot oem unlock
Enviado de meu Nexus 7 usando o Tapatalk 2
Click to expand...
Click to collapse
oh! coz i saw there stated unlocked.
is it a must to type that?
o0boiboi0o said:
oh! coz i saw there stated unlocked.
is it a must to type that?
Click to expand...
Click to collapse
No, if are unlocked you dont need
Enviado de meu Nexus 7 usando o Tapatalk 2
o0boiboi0o said:
Thanks man!
Gave up on fastboot. Dunno why cant get it running!
I tried using fastboot but cant get it to work.
1) Create a folder called fastboot, copy the 4 files + bootloader img into it, and move the folder into C drive.
2) run cmd
3) enter cd C:\fastboot\
4) adb devices. check correct.
5) adb reboot-bootloader
6) fastboot devices. check correct.
7) fastboot flash bootloader bootloader-grouper-4.18.img
8) nth happened.
what went wrong?
Click to expand...
Click to collapse
This worked for me fine. How adb devices is working for you? I think when you are in fastboot adb doesnt work.......Maybe i am wrong.
nickporwal said:
This worked for me fine. How adb devices is working for you? I think when you are in fastboot adb doesnt work.......Maybe i am wrong.
Click to expand...
Click to collapse
I think you hit sth!
when tablet is on, adb devices give me return (serial number+device). But, when i adb reboot-bootloader, adb devices give me nth, instead fastboot devices give me return.
When you type in adb devices it returns your device but you'll notice that it says offline next to it.
Therefore you can't send any adb commands to it.
It's a new security measure apparently, the solutions can be found in the forums.
Sent from my Incredible S using xda app-developers app
where are the zips
o0boiboi0o said:
Thanks man!
Gave up on fastboot. Dunno why cant get it running!
I tried using fastboot but cant get it to work.
1) Create a folder called fastboot, copy the 4 files + bootloader img into it, and move the folder into C drive.
2) run cmd
3) enter cd C:\fastboot\
4) adb devices. check correct.
5) adb reboot-bootloader
6) fastboot devices. check correct.
7) fastboot flash bootloader bootloader-grouper-4.18.img
8) nth happened.
what went wrong?
Click to expand...
Click to collapse
You must make sure to put the files you are flashing in the same folder that fastboot is located, and also to cd to that folder in command prompt.
What error were you getting exactly?
[email protected]_OC said:
Not working got to made another one when i be back home.
I have a problem with the computer at work all my zip file are no more working.
I don't know why.
I will make another zip soon
Click to expand...
Click to collapse
I too tried to create a flashable zip from the OTA, but it doesn't stick. I had to use fastboot
Sent from my Nexus 7
o0boiboi0o said:
I think you hit sth!
when tablet is on, adb devices give me return (serial number+device). But, when i adb reboot-bootloader, adb devices give me nth, instead fastboot devices give me return.
Click to expand...
Click to collapse
I am experiencing the same problem. Guess I'll have to wait for the zip version...
I used this guide for the adb: http://forum.xda-developers.com/showthread.php?t=1830108
Adinaky said:
I am experiencing the same problem. Guess I'll have to wait for the zip version...
I used this guide for the adb: http://forum.xda-developers.com/showthread.php?t=1830108
Click to expand...
Click to collapse
I am in the same boat as well. I am having weird adb issues that won't allow me to fastboot either. I am gonna reinstall SDK and see if i can adb working.
Sent from my Nexus 7 using xda premium
Tone_Capone said:
You must make sure to put the files you are flashing in the same folder that fastboot is located, and also to cd to that folder in command prompt.
What error were you getting exactly?
Click to expand...
Click to collapse
Dont think there is any error. It kept stating waiting for device but nth happened on my device side. Seems like the command get thru but nth is done.
Oo more and more ppl are having the same prob as me! :victory: Lol
Lets wait for TS's flashable file!
http://forum.xda-developers.com/showpost.php?p=37989110&postcount=1650
waiting for a linux version, i hate windows
If you don't have a working adb, you should try this guide: http://www.teamandroid.com/2012/07/30/how-to-set-up-adb-fastboot-with-android-sdk/ , it's the only one that worked for me.
Sent from my Nexus 7 using xda premium
weird.
I tried fastboot again. Ok, running smoothly at first, but in the end, i got this error:
writing 'bootloader'...
FAILED <status read failed <too many links>>
So i closed the cmd (bcoz when i tried fastboot devices, it shows ????? devices. Then when i forced closed my device and reboot into bootloader, it showed 4.18 as the bootloader version but under SIGNING, it is not defined yet.
Is this correct?
o0boiboi0o said:
weird.
I tried fastboot again. Ok, running smoothly at first, but in the end, i got this error:
writing 'bootloader'...
FAILED <status read failed <too many links>>
So i closed the cmd (bcoz when i tried fastboot devices, it shows ????? devices. Then when i forced closed my device and reboot into bootloader, it showed 4.18 as the bootloader version but under SIGNING, it is not defined yet.
Is this correct?
Click to expand...
Click to collapse
This happened to me when my adb was not working properly, it showed 4.18, but I fixed the adb and installed the bootloader again, just to be sure.
Sent from my Nexus 7 using xda premium
Anyone an idea, why flashing the bootloader does not work with the zip files?
I am somewhere in nowhere and can not fastboot, have only my Nexus 3G with me. Its on 4.2.2 but bootloader still 4.13. Used this ROM:
[ROM][Factory Image][4.2.2] Nakasig -::- Odex, Deodex, Rooted -::- teshxx (02/14/13)
to update. Worked apart of bootloader and radio.
I've been struggling for a week with this.
Trying to unlock the bootloader but whenever I get to the stage of using command prompt I get this message;
'fastboot' is not recognized as an internal or external command,
operable program or batch file
The PC just will not recognise the phone when in fastboot mode although it does when not.
Windows 7
Android 4.3
HTC Sense Version 5.5
Software number 3.62.401.1
HTC SDK API Level 5.65
USB Debugging ticked
Fast boot deticked
HTC cable used
Latest drivers installed
Any help would be appreciated, the only previous experince I have is rooting a Galaxy note and tablet with no trouble whatsoever.
tj
tjpearson said:
I've been struggling for a week with this.
Trying to unlock the bootloader but whenever I get to the stage of using command prompt I get this message;
'fastboot' is not recognized as an internal or external command,
operable program or batch file
The PC just will not recognise the phone when in fastboot mode although it does when not.
Windows 7
Android 4.3
HTC Sense Version 5.5
Software number 3.62.401.1
HTC SDK API Level 5.65
USB Debugging ticked
Fast boot deticked
HTC cable used
Latest drivers installed
Any help would be appreciated, the only previous experince I have is rooting a Galaxy note and tablet with no trouble whatsoever.
tj
Click to expand...
Click to collapse
Do you have fastboot.exe on your computer? It looks like CMD isn't finding fastboot.exe 1-because you don't have it 2- because you have not started your cmd prompt from your fastboot.exe folder
can you post a screenshot of your cmd prompt when you get this error?
ADB Installer
Installed ADB Installer and now been able to copy and been able to submit my token.
Recieved email reply with unlock code and it came as a VLC icon, still put this onto my phone but now get message 'unable to open bin file'
Got one step further but now unable to open file.
Below is the message I get:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\tjpearson>fastboot flash unlocktoken Unlock_code.bin
error: cannot open 'Unlock_code.bin'
C:\Users\tjpearson>
Your help is very much appreciated but my wife fails to understand my pannick and she thinks out tea is more important so may not get back to you straight away.
tj
tjpearson said:
Installed ADB Installer and now been able to copy and been able to submit my token.
Recieved email reply with unlock code and it came as a VLC icon, still put this onto my phone but now get message 'unable to open bin file'
Got one step further but now unable to open file.
Below is the message I get:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\tjpearson>fastboot flash unlocktoken Unlock_code.bin
error: cannot open 'Unlock_code.bin'
C:\Users\tjpearson>
Your help is very much appreciated but my wife fails to understand my pannick and she thinks out tea is more important so may not get back to you straight away.
tj
Click to expand...
Click to collapse
Think you need to open the command prompt in the adb folder, and also have the unlock_code.bin in that same folder.
mb_guy said:
Think you need to open the command prompt in the adb folder, and also have the unlock_code.bin in that same folder.
Click to expand...
Click to collapse
OK, I'll try this tomorrow, thanks for the help.
Originally Posted by mb_guy
Think you need to open the command prompt in the adb folder, and also have the unlock_code.bin in that same folder.
Click to expand...
Click to collapse
OK, I'll try this tomorrow, thanks for the help.
Click to expand...
Click to collapse
Like mb_guy said, you MUST place the bin file in the same folder where adb and fastboot are. Every time you want to flash a file to your phone it must be in that folder, otherwise fastboot won't find it and it will output you that error (can't open file). That rule apply to recovery, unlock code, rom, kernel, ruu, firmware etc etc.
Sent from my HTC One using xda app-developers app
alray said:
Like mb_guy said, you MUST place the bin file in the same folder where adb and fastboot are. Every time you want to flash a file to your phone it must be in that folder, otherwise fastboot won't find it and it will output you that error (can't open file). That rule apply to recovery, unlock code, rom, kernel, ruu, firmware etc etc.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Thanks for the help because at least I've now been able to unlock bootloader.
My problem now is 'fastboot flash recovery openrecovery-twrp-2.6.3.0-m7.img' command line and yet again I'm getting error unable to open as below;
C:\Users\tjpearson>fastboot flash recovery openrecovery-twrp-2.6.3.0-m7.img
error: cannot open 'openrecovery-twrp-2.6.3.0-m7.img'
Even placing zip on root of phone and in adb folder still no joy.
tj
tjpearson said:
Thanks for the help because at least I've now been able to unlock bootloader.
My problem now is 'fastboot flash recovery openrecovery-twrp-2.6.3.0-m7.img' command line and yet again I'm getting error unable to open as below;
C:\Users\tjpearson>fastboot flash recovery openrecovery-twrp-2.6.3.0-m7.img
error: cannot open 'openrecovery-twrp-2.6.3.0-m7.img'
Even placing zip on root of phone and in adb folder still no joy.
tj
Click to expand...
Click to collapse
''error: cannot open'' is caused because fastboot don't find the file. Is the recovery file you are trying to flash is named exactly <openrecovery-twrp-2.6.3.0-m7.img> ?
Btw I'll recommend you to flash twrp 2.6.3.3 not 2.6.3.0 as you could have issur flashing newer 4.4 rom
Code:
fastboot flash recovery <name_of_file.img>
fastboot erase cache
fastboot reboot-bootloader
alray said:
''error: cannot open'' is caused because fastboot don't find the file. Is the recovery file you are trying to flash is named exactly <openrecovery-twrp-2.6.3.0-m7.img> ?
Btw I'll recommend you to flash twrp 2.6.3.3 not 2.6.3.0 as you could have issur flashing newer 4.4 rom
Code:
fastboot flash recovery <name_of_file.img>
fastboot erase cache
fastboot reboot-bootloader
Click to expand...
Click to collapse
Yes, named exactly the same.
It's driving me mad, if the bootloader is now unlocked is there an easier way to flash twrp and then root.
Whats the best way to check adb is actually communicating with the phone
tj
tjpearson said:
Yes, named exactly the same.
It's driving me mad, if the bootloader is now unlocked is there an easier way to flash twrp and then root.
Whats the best way to check adb is actually communicating with the phone
tj
Click to expand...
Click to collapse
Do you have a Sprint phone ? and can you post a screen shot of your adb / fastboot folder containing the files or at least post your results for dir
open command prompt from your adb / fastboot folder (shift+right click - command prompt here)
type
adb devices
your device SN will be here
type
adb reboot bootloader
you should be in fastboot usb
type
fastboot devices
again your serial no should be here
type dir
you should see the contains of the folder your in
now
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
if error change the twrp name to match the one in the dir command above
clsA said:
Do you have a Sprint phone ? and can you post a screen shot of your adb / fastboot folder containing the files or at least post your results for dir
open command prompt from your adb / fastboot folder (shift+right click - command prompt here)
type
adb devices
your device SN will be here
type
adb reboot bootloader
you should be in fastboot usb
type
fastboot devices
again your serial no should be here
type dir
you should see the contains of the folder your in
now
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
if error change the twrp name to match the one in the dir command above
Click to expand...
Click to collapse
I seem to have a problem adb detecting the connected phone, I'll unistall and start again and if I can then get back to you later I'd appreciate it very much.
The phone is UK on 02 Android 4.4 HTC Sense version 5.5
tj
tjpearson said:
I seem to have a problem adb detecting the connected phone, I'll unistall and start again and if I can then get back to you later I'd appreciate it very much.
The phone is UK on 02 Android 4.4 HTC Sense version 5.5
tj
Click to expand...
Click to collapse
can you check my guide under faq #2, if that solves it
Well, think I'll give up with rooting my HTC One, I have never had so much trouble routing a divice as this. My bootloader is now unlocked and that's about as far as I get.
My phone seems to have been detected once through adb that then allowed me to run unlock token but everything else just fails.
In one last attempt I've attached image of ADB folder and below is result from command line.
It must be my age because evertybing seems so complex nowadays
C:\Android>fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
target reported max download size of 1526722560 bytes
error: cannot load 'openrecovery-twrp-2.6.3.3-m7.img': No error
C:\Android>
tjpearson said:
Well, think I'll give up with rooting my HTC One, I have never had so much trouble routing a divice as this. My bootloader is now unlocked and that's about as far as I get.
My phone seems to have been detected once through adb that then allowed me to run unlock token but everything else just fails.
In one last attempt I've attached image of ADB folder and below is result from command line.
It must be my age because evertybing seems so complex nowadays
C:\Android>fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
target reported max download size of 1526722560 bytes
error: cannot load 'openrecovery-twrp-2.6.3.3-m7.img': No error
C:\Android>
Click to expand...
Click to collapse
cannot load = MyFileNameIsWrong
and from the screenshot you posted the filename is: openrecovery-twrp-2.6.3.3-m7.img.img <- yes, double extension, next time do a "dir" in command prompt to see your filenames, not in Windows Explorer.
d -darrrrr
nkk71 said:
cannot load = MyFileNameIsWrong
and from the screenshot you posted the filename is: openrecovery-twrp-2.6.3.3-m7.img.img <- yes, double extension, next time do a "dir" in command prompt to see your filenames, not in Windows Explorer.
Click to expand...
Click to collapse
I love you nkk71, I really can't tell you how much I love you but I do !!!!! :victory:
Did what you said and fumbled through flashing twrp and then adding superuser after to the phones root, did recovery again and installed superuser via twrp and bingo, rooted and confirmed.
Been struggling 2 weeks with this and non stop all weekend, my wife wants a divorce but I don't care cos I'M ROOTED !!
Thanks so much for all the help, nice one :good:
tj
tjpearson said:
I love you nkk71, I really can't tell you how much I love you but I do !!!!! :victory:
Did what you said and fumbled through flashing twrp and then adding superuser after to the phones root, did recovery again and installed superuser via twrp and bingo, rooted and confirmed.
Been struggling 2 weeks with this and non stop all weekend, my wife wants a divorce but I don't care cos I'M ROOTED !!
Thanks so much for all the help, nice one :good:
tj
Click to expand...
Click to collapse
Lol
Now that the phone is good, go spend some time with your better half!!!
No guides on xda, on "how to return my marriage to stock"
Put the phone on the charger or something, and spend time with your significant other.
Sent from my HTC One using Tapatalk
One last question
nkk71,
Can I uninstall Superuser now and install SuperSU instead cos I've already purchased that when had the Note rooted or will it cause me more time away from the mrs with issues.
tj
tjpearson said:
nkk71,
Can I uninstall Superuser now and install SuperSU instead cos I've already purchased that when had the Note rooted or will it cause me more time away from the mrs with issues.
tj
Click to expand...
Click to collapse
Shouldn't be a problem, use the flashable zip from the thread: http://forum.xda-developers.com/showthread.php?t=1538053
Yeah , sorted.
Thanks again for all your help.
tj
Ok, now we know that fastboot and adb can be troublesome on WIndows, but despite lots of reading, I;m a bit stumped as to what if anything is wrong with my WIN 7 setup.
ADB works fine, I can get into adb from a cmd window, enter commands and get the expected result.
"adb devices" returns the 16 digit serial number, a few spaces and "device"
"adb reboot" reboots as normal
I cannot get into fastboot from adb though. (I can use a factory cable to enter fastboot, no problem, and using the Quick Boot app, I can get into Fastboot no probs.
Once there,
"fastboot -i 0x1949 getvar product" returns -> product: Tate-PVT-08
"fastboot -i 0x1949 devices" returns -> 13EE000200000001 fastboot
"fastboot -i 0x1949 reboot" gets me out into normal mode.
All above leads me (correctly or not) to think that the drivers, system etc are ok and I'm doing something wrong.
eg
" adb reboot-bootloader" (as written in adb help) simply reboots the device as usual
as does
"adb reboot bootloader"
"adb reboot boot loader"
I've seen the various syntax here and elsewhere
It seems as if the command is read as far as "reboot" and everything after that is ignored. So, what am I doing wrong?
You're doing nothing wrong. I believe that command does not work in the later os versions.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Red_81 said:
You're doing nothing wrong. I believe that command does not work in the later os versions.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Oh bum. You know, I thought maybe the drivers were wrong, or my syntax wrong, but I never thought the OS would be wrong!! Lol
Does anyone know when this change was introduced and which was the last OS release that could be booted into fastboot via adb?
If you're rooted you could try the methods in the FAQ post. Otherwise, buy/build a fastboot cable. It makes everything much easier.
Q17: How can I access fastboot mode on 2nd generation Kindle Fires?
There are 3 methods currently used for accessing fastboot mode on the 2nd generation Kindle Fires. Depending on the model, one or more of these methods may not work.
For all devices, entering “reboot bootloader” in the shell as the root user should reboot the device into fastboot mode.
On HD models, entering a fastboot command that waits for a handshake from the device (i.e. <waiting for device>”) such as “fastboot -i 0x1949 getvar product” and rebooting the device will usually enable fastboot mode when the device reboots.
On the KFHD7 and KF2, a factory cable can be used to access fastboot mode by plugging it into the device after it has been powered down.
Thanks Red. The shell command works, but issuing a command that waits for a handshake then rebooting doesn't. I also tried the same command whilst the device was powered down, but in both cases it just booted normally.
Of course my factory cable also works, and I am rooted
Code:
adb shell su -c reboot-bootloader
SafinWasi said:
Code:
adb shell su -c reboot-bootloader
Click to expand...
Click to collapse
thanks safinwasi. I managed ok without needing this option, It was more for reassurance. For the benefit of anyone who might need to do this, I have seen that command without quotes, so try both.
I think you should get a fastboot cable less hassle!
Bao289 said:
I think you should get a fastboot cable less hassle!
Click to expand...
Click to collapse
Hmmm, I think you should read posts properly before making comments.
cecr said:
I can use a factory cable to enter fastboot, no problem, and using the Quick Boot app, I can get into Fastboot no probs.
Click to expand...
Click to collapse
I've had my factory cable since I rooted my first Kindle about 15 months ago.
I've got java and SDK tools properly installed. I've tried several methods. Always gives error command fastboot not found. I'm on crunchbang Linux
If you go to general > sticky roll-up thread....
You'll find my fastboot thread which tells you how to use fastboot correctly.
@NiNJAwitaRaZR,
Did you type ./ before the fastboot command?
cam30era said:
@NiNJAwitaRaZR,
try using sudo ./ before the fastboot command.
Click to expand...
Click to collapse
You don't need sudo for fastboot. But you do need to know where the fastboot binary is.
Or he can use an adb and fastboot installer script which should put it in a known PATH
rootSU said:
You don't need sudo for fastboot. But you do need to know where the fastboot binary is.
Or he can use an adb and fastboot installer script which should put it in a known PATH
Click to expand...
Click to collapse
Aahh, OK.
I still prefer to do things manually, so that I understand how it works.
cam30era said:
Aahh, OK.
I still prefer to do things manually, so that I understand how it works.
Click to expand...
Click to collapse
Me too. Personally I just drop them directly in /usr/bin