Related
Hi to all I have a provlem I need help with.While trying to unlock my bootloader using rsd and fastboot.I get as far as the cmd line entries and have problems basically I cant seem to get my command line to use the fastboot command and or any other fastboot command I can find.What seems to happen all the time is that the command line responds with "this is not an internal or external command" or similar.
Any help appreciated Windows 7 64bit all latest drivers installed
scotty7910 said:
Hi to all I have a provlem I need help with.While trying to unlock my bootloader using rsd and fastboot.I get as far as the cmd line entries and have problems basically I cant seem to get my command line to use the fastboot command and or any other fastboot command I can find.What seems to happen all the time is that the command line responds with "this is not an internal or external command" or similar.
Any help appreciated Windows 7 64bit all latest drivers installed
Click to expand...
Click to collapse
are you in the same folder that the FASTBOOT.EXE is in when you run the command???
Make sure your running CMD as administrator. You can tell by the path that shows when cmd is launched. If its a regular user account it will path to something like: c:\users\"your username"\
If your running as admin it will path to something like: c:\windows\system32
Sent from my MB860 using XDA Premium App
Take your fastboot files and images and put them in a folder on the root of your C: drive... I use one named phone
Then you should be able to open your Command line and type
cd c:\phone
That will change you to the Phone directory you made in the root of C: earlier
If you want to make sure you can type DIR and it should list all the files you have in there.
At this time you can start using your fastboot commands and it will recognize them.
beatphreek said:
Take your fastboot files and images and put them in a folder on the root of your C: drive... I use one named phone
Then you should be able to open your Command line and type
cd c:\phone
That will change you to the Phone directory you made in the root of C: earlier
If you want to make sure you can type DIR and it should list all the files you have in there.
At this time you can start using your fastboot commands and it will recognize them.
Click to expand...
Click to collapse
Another handy thing is to open the folder then hold the shift key and then right click. You'll have an "Open command window here" option.
Yep I use that all the time...
used both the suggestions in here and still having trouble,can do the root of c folder,use the dir command see it is all there but the cd C:\fastbootpackage brings the same response again.Can anyone see where I am going wrong?Once the command line changes to fastboot what do I need to command?Phone is still attached (as per the guide I am following?)showing 100% phone needs manually rebooted.
I have all latest drivers on win 7 64bit and I am definetely running cmd as an administrator
Also as the third suggestion suggests if I open the cmd box from the folder what is the exact command to use from there?Is there an alternative to doing this as I am beginning to struggle?
Unlock your Bootloader
1. You need to download and install RDS lite on your PC:http://forum.xda-developers.com/attachment.php?attachmentid=634879&d=1308872277
2. Download and extract IHOP_Bell.rarhttp://api.viglink.com/api/click?format=go&drKey=1359&loc=http%3A%2F%2Fforum.xda-developers.com%2Fshowthread.php%3Ft%3D1136261&v=1&libid=1311795928774&out=http%3A%2F%2Fdiamantephoto.com%2FIHOP_Bell.rar&ref=http%3A%2F%2Fforum.xda-developers.com%2Fforumdisplay.php%3Ff%3D997&title=%5BPUDDING%5D%20International%20House%20of%20Pudding!%20(Unlock%2Froot%20thread)%20Updated%20July%2023%202011%20-%20xda-developers&txt=http%3A%2F%2Fdiamantephoto.com%2FIHOP_Bell.rar
3. Download and extract Fastboot tools http://gititbit.ch/FAST
4. Power down your Motorola Atrix
5. Take out your microSD card and SIM*card*for the flashing process
6. While turning the phone on, hold the Volume Up button until it acknowledges RSD
7. Your device will say “Starting RSD protocol support”
8. Run “RSD Lite” on your computer
9. Press the “. . .” button next to the box labeled “Filename”
10. Load up the SBF file – IHOP_Bell.sbf
11. Plug your device into your computer
12. RSD Lite should recognize your device and say “Model: NS Flash Olympus” and “Connected…”
13. Press the “Start” button
14. Be patient while the phone*reboots. It will take a long time.
15. Open and extract the Fastboot package from above
16. Open a command prompt window
a.On Windows, press Start and type “cmd” then press the enter button
17.Type the following command. Your directory will be the folder where you extracted the Fastboot package.
(Example:* cd C:\Users\Kenneth\Desktop\fastboot-package)
a.cd*your directory here
18. Power down your Atrix device
19. Hold the power button and the downward volume button until you see “Fastboot”
20. Let go of the buttons and press the upward volume button once
21. You will now see “Starting Fastboot protocol support”
22. Plug your device into a USB port in the back slot of your computer
a.Front slots sometimes do not have enough power to stay connected to the device.
23. Type the following command:
a.fastboot oem unlock
24. You will now receive a warning along with a unique device ID
25. Type the following commands using your unique device ID in place of the ####:
a.fastboot oem unlock ####
b.fastboot reboot
26. Wait for your device to reboot. Congratulations! You now have an unlocked bootloader!
This is the guide I have been using, thanks again
scotty7910 said:
"this is not an internal or external command"
Click to expand...
Click to collapse
This msg will only show if you are in different folder than your fastboot. You don't need to run cmd as administrator. The best thing to do is:
copy those 3 files (AdbWinApi.dll, AdbWinUsbApi.dll, fastboot.exe) to your main c:\ (do not put to the folder)
Run cmd and type "cd \" this will move you to c:\
Now type fastboot and press enter - you should see various commands that can be used. (your mobile doesn't need to be connect to your pc to see this)
Now you can continue with unlocking. If you applied ihop.sbf already then startt from step 18.
I'm 99% sure that you were in the wrong folder.
Thanks very much that last post got it.In fact I would say that is the simplest way I have read so far as far as fastbooting goes.Many thanks.I have been having problems installing tenfars cwm so I will be using the rom manager "official cwm,will using the fastboot-w command be a problem for me do you think?
scotty7910 said:
Thanks very much that last post got it.In fact I would say that is the simplest way I have read so far as far as fastbooting goes.Many thanks.I have been having problems installing tenfars cwm so I will be using the rom manager "official cwm,will using the fastboot-w command be a problem for me do you think?
Click to expand...
Click to collapse
Don't use the Rom Manager app. It sucks and doesn't work properly. Do things properly.
With XDA forum members there's no reason to do things half assed. Use your hole ass, dammit.
scotty7910 said:
Thanks very much that last post got it.In fact I would say that is the simplest way I have read so far as far as fastbooting goes.Many thanks.I have been having problems installing tenfars cwm so I will be using the rom manager "official cwm,will using the fastboot-w command be a problem for me do you think?
Click to expand...
Click to collapse
Well if you came that far then try to install tenfar's recovery, download this file :recovery-en-goapk-0630-1029.zip Unzip and move recovery-en-goapk-0630-1029.img to your c:\....Now reboot your phone and enter to fastboot mode. In cmd go to c:\ and type "fastboot flash recovery recovery-en-goapk-0630-1029.img" and then "fastboot reboot" DONE
If you have any problems try to download moto-fastboot (http://forum.xda-developers.com/attachment.php?attachmentid=635584&d=1308928440). It's kind of the same thing as fastboot and to be honest I don't know what's the different between both (I think moto-fastboot is designed for 2.3.4 firmware). Extract zip and move moto-fastboot to c:\ and type the same command but instead of fastboot type moto-fastboot. I hope this make sense.
Also it's recommended to delete "install_recovery.sh" which apparently is in /system/etc/ BUT I never managed to find this file and I just ignored this step.
thanks foka, but I have already tried and tried again unsuccessfully to use tenfars cwm.I can install the recovery and delete the sh file all as normal using fastboot and astro.However for some reason there seems to be no way I can get into cwm having flashed it.when I attempt it I dont see the same menu I could scroll through as before.Then I tried a cwm of tenfars that was supposed to flash through rom manager.Again the flash went fine but could not seem to enter recovery mode.I see you installed aura 1.1 didi you flash a radio afterwards?My signal is comnstantly 1 bar.Could you reccomend a uk radio?
Well Ive flashed at&t radio N_01.77.30p which solved battery draining and 1 bar issue. I'm not sure why you can't use cwm recovery...
Sent from Motorola Atrix
What do you mean you don't see the same menu as before? When you hold volume down, power up phone, fastboot, scroll through the list and none of them say Android Recovery?
i'm VERY new to all of this, and i promise i tried my hardest to find an answer in existing threads and google, but haven't found anything to help with my prob:
I tried (?) to root kindle fire [android police thingy], not sure if I succeeded or not (had a lot of "device not found" at the beginning) and tried to install RTL languages support at the same time.
I haven't installed any "TWRP" or "firefirefire" or anything like it.
after the reboot at the end of the RTL, the kindle got stuck on "kindle fire". I tried 20 second power button for several times, on and off power.
kindle fire utlity ("run") says:
adb status: online
adb rooted: no
boot status: 4000
when trying to root through this (temp root), i get: adbd cannot run as root in production builds.
I get the same phrase trying to do anything on the utiility.
Can I do anything to save this from being a 200$ coaster?
THANKS!
you can try to install fff and twrp with kfu (option 5)
then copy one of the prerooted stock images to sdcard:
http://forum.xda-developers.com/showthread.php?t=1402440
would recommend the secure one
and install with twrp:
http://forum.xda-developers.com/showpost.php?p=20543289&postcount=47
imageshack. us/photo/my-images/515/brickc.jpg/
(delete spaces)
i get about the same thing for every option i choose.
any other option?
(and THANK YOU for answering so quickly)
open an (elevated) command prompt in the tools directory of kfu and type in:
adb shell
copy and paste what you get back
b63 said:
open an (elevated) command prompt in the tools directory of kfu and type in:
adb shell
copy and paste what you get back
Click to expand...
Click to collapse
$ sign.. (waiting does nothing, "enter" produces yet another $ sign :X )
that is very good - you did not mess up your shell !!!
ok - what version of kfu do you have ?
would recommend the newest one - 0.9.2 - extract it to c:\ and rename the folder to "kfu" so that it looks c:\kfu
then give it a retry with option 3 and then 5
please copy and paste the output that i can see what it is doing
b63 said:
that is very good - you did not mess up your shell !!!
ok - what version of kfu do you have ?
would recommend the newest one - 0.9.2 - extract it to c:\ and rename the folder to "kfu" so that it looks c:\kfu
then give it a retry with option 3 and then 5
please copy and paste the output that i can see what it is doing
Click to expand...
Click to collapse
the kf is on 6.2.1 and the kfu is 0.9.2.
img521.imageshack .us/slideshow/webplayer.php?id=brick2m.jpg
(again, delete space)
on the first attempt with no. 5, it started downloading something but my internet went bad and the dl stayed on 52%. I manually downloaded the file and named it "recovery" (in the correct folder). after that, i got the message in "brick 3"
and another thing - even though i keep getting "adb rooted: no", after each time i "root", the device reboots, but it doesn't reboot after the "installation" of the twrp.
that with the recovery was right - it has to be recovery\recovery.img
the file should be ~10mb - maybe we have to do it manually
the problem is that burritoroot is allready installed and kfu can't gain root
you did not install burritoroot with kfu ? (kfu has a special version)
therefor we get the message "... can not run on production builds"
now we can look where the file is located and install with kfu or
install fff and twrp manually
i think in this case it will be easier to install manually:
first fff 1.2 manuell:
•download from here:
http://forum.xda-developers.com/attachment.php?attachmentid=850008&d=1326179460
•extract to the folder where adb.exe & fastboot.exe is located
•"adb shell idme bootmode 4002" & "adb reboot"
•flash with "fastboot -i 0x1949 flash bootloader u-boot.bin"
second twrp manuell:
•copy recovery.img which you downloaded and renamed to the folder where adb.exe & fastboot.exe is located
•install with "fastboot -i 0x1949 boot recovery.img"
now we reboot into recovery:
•"fastboot -i 0x1949 oem idme bootmode 5001"
•"fastboot -i 0x1949 reboot"
now we should have the recovery system installed ...
b63 said:
i think in this case it will be easier to install manually:
first fff 1.2 manuell:
•download from here:
http://forum.xda-developers.com/attachment.php?attachmentid=850008&d=1326179460
•extract to the folder where adb.exe & fastboot.exe is located
•"adb shell idme bootmode 4002" & "adb reboot"
•flash with "fastboot -i 0x1949 flash bootloader u-boot.bin"
Click to expand...
Click to collapse
itmw,
"adb shell idme bootmode 4002" (in c:\KFU\tools)
gave me:
"<idme> invalid permission"
(and thank you again for all the help)
RYuval said:
itmw,
"adb shell idme bootmode 4002" (in c:\KFU\tools)
gave me:
"<idme> invalid permission"
(and thank you again for all the help)
Click to expand...
Click to collapse
looks like you have messed up the permissions !
ok - then we use this to get into fastboot:
download this and extract in the tools folder:
http://forum.xda-developers.com/attachment.php?attachmentid=833582&d=1325144494
then:
adb push fbmode /data/local/tmp
adb shell chmod 755 /data/local/tmp/fbmode
adb shell /data/local/tmp/fbmode
adb reboot
now we should continue the steps above
b63 said:
looks like you have messed up the permissions !
ok - then we use this to get into fastboot:
download this and extract in the tools folder:
http://forum.xda-developers.com/attachment.php?attachmentid=833582&d=1325144494
then:
adb push fbmode /data/local/tmp
adb shell chmod 755 /data/local/tmp/fbmode
adb shell /data/local/tmp/fbmode
adb reboot
now we should continue the steps above
Click to expand...
Click to collapse
those steps went fine.
but now we're back to "error: device not found"
reinstalled the drivers, shut down, restarted and reinstalling again to see if it helps. (maybe it's just me, but it feels like anything that can go bad, does. )
RYuval said:
those steps went fine.
but now we're back to "error: device not found"
reinstalled the drivers, shut down, restarted and reinstalling again to see if it helps. (maybe it's just me, but it feels like anything that can go bad, does. )
Click to expand...
Click to collapse
that's quite normal
what say your device manager about adb or kindle ?
b63 said:
that's quite normal
what say your device manager about adb or kindle ?
Click to expand...
Click to collapse
until recently, "adb android device" or something like that..
now it says the driver does not suit 64bit... (currently: unknown USB device)
it should say "android adb interface"
update the driver with the one from c:\kfu\drivers - they can 64bit
if it does'nt work you can run install_drivers.bat from c:\kfu - maybe 2 times
for information in device manager:
normal boot (4000) -> android composite adb interface
fastboot (4002) -> android adb interface
b63 said:
it should say "android adb interface"
update the driver with the one from c:\kfu\drivers - they can 64bit
if it does'nt work you can run install_drivers.bat from c:\kfu - maybe 2 times
Click to expand...
Click to collapse
for some reason, that still doesn't work..
and the driver was properly installed earlier..
RYuval said:
for some reason, that still doesn't work..
and the driver was properly installed earlier..
Click to expand...
Click to collapse
for normal boot - have you ever been/worked in/with fastboot mode ?
we have to get the right drivers for every mode working
i just switched my kf to fastboot and return to normal boot to verify
try to update the driver manually (select manually)
alternately you can delete every driver with kindle or adb and then unplug and replug the kf
that' only a loose description that you see how it is done:
if you' asked
-choose browse my computer for driver software
-Then select have disk
-Then select browse
-direct to where you downloaded the usb driver
-Select okay and okay
just in case you'r not asked:
-Go to device manager
-right click on the exclamation mark kindle
-Choose update driver software
-choose browse my computer for driver software
-choose let me pick from a list of devices on my computer
-Then select have disk
-Then select browse
-direct to where you downloaded the usb driver
-Select okay and okay
will be updated (drivers installed.) the name's without "composite"
if you have a 32 bit pc - that's the better choice
what os is it ? xp 7 or ?
on the 32 bit you can try an alternate set
download it from this post:
http://forum.xda-developers.com/showpost.php?p=20855280&postcount=54
and run the included batch and then install the driver
b63 said:
if you have a 32 bit pc - that's the better choice
what os is it ? xp 7 or ?
on the 32 bit you can try an alternate set
download it from this post:
http://forum.xda-developers.com/showpost.php?p=20855280&postcount=54
and run the included batch and then install the driver
Click to expand...
Click to collapse
i have 32bit win7 (and 64 on win7)
it identified as an "adb interface device" but still "device not found" on cmd..
RYuval said:
i have 32bit win7 (and 64 on win7)
it identified as an "adb interface device" but still "device not found" on cmd..
Click to expand...
Click to collapse
device not found on what command ?
your on an elevated command prompt (as administrator) ?
fastboot -i 0x1949 getvar product
it should return "kindle"
First of all, i would like to thank alot Mr. "b63" without him my kf stuck and bricked forever.
I Initially putted the following question/problem:
.I have a problem with kindle fire, as i installed TWRIP program to try to install android 4.0 ice cream sandwich, but i failed, and screen remain to TWRIP software every time i try to boot the fire, at this step i am able to mount kindle fire, and what i did also is flashing KF (i made every kind of flash), i noticed that when i mounted KF all system files are deleted!, i tried to return back to my old software by downloading KF firmware update 6.2.1 and transfer it to kf, then install it, after that, and from this time the KF stuck at KF logo every time i start it, also it can't be mounted anymore, when i plug KF into the pc, it show me removable device but not accessible, i tried kindle fire utility and KindleUnbrickUtilityV1.0.zip but every order the software is waiting for the device and remain as it is, it seems that my KF bricked forever because i tried everything and it is now a challenge to return KF to it's original state or install android and make it workable again, can any one help me please?
i tried to make the following:
1. download the kindle fire utility
2. I used fastboot without rooting rooting (thanks to pokey9000 )
3. I used
Code:
fastboot -i 0x1949 getvar product
to search my kindle fire
4. I downloaded the fastboot file HERE then extract the files into the kindle fire utility folder
5. then we use this code
Code:
fastboot -i 0x1949 boot twrp-blaze-2.0.0RC0.img
to install fastboot mode
6. then the screen will display the "install complete" word and button called reboot now click it after rebooting you should find the yellow triangle
7. Now use thee commands
Code:
fastboot -i 0x1949 oem idme bootmode 5001
fastboot -i 0x1949 reboot
if it cannot find a device and the locate driver window opens define the kf again
8. Now you can download the rom hat ever you want
9. click the mount button from the recovery mode
10. copy the rom into it
11. install the rom and i the install screen click the mall button have "X md5" or something like that(if you don't do this the kf will not install the rom)
12. clear the dalvik/cache
13. run thee commands
Code:
adb shell idme bootmode 4000
adb reboot
but unfortunately can't be done because there was some system shell files deleted, so i made factory cable and repeated the previous steps, it worked and i successed to install twrp s/w.
Also i downloaded modaco custom rom and installed it but it did not work for me.
Then i installed preroted unsecure rom from the following link:
http://www.multiupload.com/ZQ065JFSMR
Transferred it to kf, installed it and it works fine except the Android market icon
Also i made the following command before turning on the wifi:
adb shell rm /system/etc/security/otacerts.zip
to delete ocacerts.zip file to overcome amazone delete for the fff and twrp software.
to solve the problem of android market i did the following:
download from this post:
http://forum.xda-developers.com/show...42&postcount=8
and
http://www.xageek.com/software/FileE...9_GKWeb_EN.apk
and
http://61.145.124.93/soft/3GHeart/go...r_EX_V2.77.apk
and place all files in the tools directory of kfu
then some commands:
adb install GO_Launcher_EX_V2.77.apk
adb install FileExpertSigned_4.0.9_GKWeb_EN.apk
On My device (either click disconnect or unplug it temporarily) go to Apps and run the File Expert application we installed earlier. Click the Menu button at the bottom of the screen → More → Settings → File Explorer Settings and check “Root Explorer”, clicking “Allow” to the access dialogue. After this, back out to the Home screen of File Expert. From here click My Files → Phone Internal Storage → sdcard, then tap Menu → More → Mount → Mount as Read Write. Now do this for one more location, so tap the back arrow, then go to system → app and tap menu → More → Mount → Mount as Read Write.
adb push GoogleServicesFramework.apk /sdcard/
adb push Vending.apk /system/app
adb shell chmod 644 /system/app/Vending.apk
On My device, open File Expert (if you closed it) and go to My Files → Phone Internal Storage → sdcard and tap GoogleServicesFramework.apk (if you don't see it, back up a directory and come back). Tap Install. Once it finishes, click “Done”. Now tap back, then system → app. From here tap Vending.apk and Install it. Choose OK to Replace Application. Once finished click “Done”.
Reboot My Kindle Fire.
Go to Apps and launch Go Launcher. From inside of Go Launcher I should be able to visit and use the Android Market. Now when you press the Home Key you'll be prompted to choose either the Amazon launcher or the Go Launcher. They both have their uses.
but mounting for read & write failed for unknown reason.
I overcome this by doing the following:
issued "adb remount" and resume with the next 3 adb commands above
it works very nice for me, i tried to install from android market and it worked very nice, i enjoy my kf, thanks again to b63 and XDA-developer forum.
I've rooted my kindle fire before but I lost root access so I rooted it again last night via kindlewater (for mac) or some such name like that.
Then I tried to install TWRP via my vmware windows emulator. At some point during the process my kindle fire disconnected from windows and reconnected to my mac and I'm assuming that's where things went tragically wrong.
It looks as if it's stuck in fastboot but windows isn't recognizing it. My drivers are installed and have uninstalled and reinstalled a few times.
I've tried the Kindle Fire Utility 0.9.3 and the Kindle Fire Unbricking Utility. Neither of them have done anything since the only way windows recognizes the KF is as a corrupted USB device.
I've tried boosting it into normal mode but all it gives me is "waiting on device" as it does with any selection in the KF Utility or KF Unbricking Utility.
I've been in web design/computer technology classes for four years (top of my class) but at some point I must have missed the command prompt classes because I can't seem to ever get commands working nor do I have any idea on how to which is why I've been reliant on those two programs which haven't done anything.
I've seen somebody say they forced the correct fastboot with some command line like fastboot oem blablabla and I tried that once or twice or 8 times and it never recognized the command then again though all I typed was the command and hit enter...
I've never seen a yellow triangle when booting I've always been stuck on a static (no animation) kindle fire screen and no matter what I can't get it recognized as anything other than a corrupt usb device.
What makes this all harder is working on a macbook pro with a windows emulator. -_-
I really need some advice here...I'm about ready to say screw it and use my warranty to have the device replaced in a staples store. If I can't figure out how to boot it i'm sure they wouldn't be able to and would just replace it right?
P.S. I'd rather have it replaced then buy a fastboot cord and have to wait a week to have it shipped lol.
Please help a girl out
try this
Symberlei said:
I've rooted my kindle fire before but I lost root access so I rooted it again last night via kindlewater (for mac) or some such name like that.
Then I tried to install TWRP via my vmware windows emulator. At some point during the process my kindle fire disconnected from windows and reconnected to my mac and I'm assuming that's where things went tragically wrong.
It looks as if it's stuck in fastboot but windows isn't recognizing it. My drivers are installed and have uninstalled and reinstalled a few times.
I've tried the Kindle Fire Utility 0.9.3 and the Kindle Fire Unbricking Utility. Neither of them have done anything since the only way windows recognizes the KF is as a corrupted USB device.
I've tried boosting it into normal mode but all it gives me is "waiting on device" as it does with any selection in the KF Utility or KF Unbricking Utility.
I've been in web design/computer technology classes for four years (top of my class) but at some point I must have missed the command prompt classes because I can't seem to ever get commands working nor do I have any idea on how to which is why I've been reliant on those two programs which haven't done anything.
I've seen somebody say they forced the correct fastboot with some command line like fastboot oem blablabla and I tried that once or twice or 8 times and it never recognized the command then again though all I typed was the command and hit enter...
I've never seen a yellow triangle when booting I've always been stuck on a static (no animation) kindle fire screen and no matter what I can't get it recognized as anything other than a corrupt usb device.
What makes this all harder is working on a macbook pro with a windows emulator. -_-
I really need some advice here...I'm about ready to say screw it and use my warranty to have the device replaced in a staples store. If I can't figure out how to boot it i'm sure they wouldn't be able to and would just replace it right?
P.S. I'd rather have it replaced then buy a fastboot cord and have to wait a week to have it shipped lol.
Please help a girl out
Click to expand...
Click to collapse
I had the same thing happen to me (do not use Fastboot in recovery). This worked for me give it a try ; Kindle Fire Unbrick posted on liliputing. You'll need a PC with Windows. Just be sure you have the Kindle Drivers available, otherwise your USB may not see the Kindle.
Good luck
Why were you using Windows emulator to begin with?
Just use terminal and cd to your android sdk tools folder where adb and fast boot are and type: (with device plugged in and turned on)
./fastboot -i 0x1949 oem idme bootmode 4000
./fastboot reboot
Chances are that it will hang at "rebooting". If so just hold the power button down until it shuts off then turn it back on. It should start normally.
Sent from my Amazon Kindle Fire using xda premium
CD?
How do I CD to something?
I know this sounds stupid and totally noobish but like I said terminal and I don't get together a whole lot XD
Can I just pay somebody to come to my house and do it for me? D=
(Joking of course)
Okay I think I directed myself to fastboot in terminal and I copied and pasted
./fastboot -i 0x1949 oem idme bootmode 4000
./fastboot reboot
but then it said "-bash: ./fastboot: No such file or directory
mac-users-macbook-pro-1634:~ macuser$ ./fastboot reboot
-bash: ./fastboot: No such file or directory"
Symberlei said:
How do I CD to something?
I know this sounds stupid and totally noobish but like I said terminal and I don't get together a whole lot XD
Can I just pay somebody to come to my house and do it for me? D=
(Joking of course)
Okay I think I directed myself to fastboot in terminal and I copied and pasted
./fastboot -i 0x1949 oem idme bootmode 4000
./fastboot reboot
but then it said "-bash: ./fastboot: No such file or directory
mac-users-macbook-pro-1634:~ macuser$ ./fastboot reboot
-bash: ./fastboot: No such file or directory"
Click to expand...
Click to collapse
A quick intro:
cd is "change directory"
pwd is "present working directory"
ls is "list directory contents"
What you see in the prompt above is...
mac-users-macbook-pro-1634 - the name of your mac
~ - your pwd
macuser - your username
~ is shorthand for your home directory. i.e. '/Users/macuser'
e.g. If you type 'pwd' you'll get '/Users/macuser'
cd will change your pwd to what you specify
e.g. type 'cd Documents' and you'll change to that directory. This is analogous to opening up your Documents folder in the Finder.
If you then type 'pwd' at the next prompt you'll get '/Users/macuser/Documents'
If you then type 'ls' at the next prompt, you'll get the contents of your Documents folder listed
What the previous poster wants you to do is change directories to wherever you have the fastboot program so you can run it in the terminal. You can do this on the mac by typing "cd " (that's cd followed by a space) and then dragging the folder that contains the fastboot program into the terminal window. The terminal will automatically paste in the complete path (directory location) of the folder for you.
I suggest doing some more reading...
http://osxdaily.com/2007/02/07/basic-command-line-utilities-tips-commands/
Thank you but
Thank you so much that was incredibly helpful =D
it brought up the fastboot program and it says the following
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
reboot reboot device normally
reboot-bootloader reboot device into bootloader
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
mac-users-macbook-pro-1634:~ macuser$
What should I do after this?
*Bump* I still need help D=
I still don't know what to do after that last step or even if I'm in the wrong place. I'd like to have my kindle fire back up and unbricked before the weekends over. Please and thank you
OK so assuming you have terminal open and your current directory is your Android SDK tools folder...
it should read something like iMac-HD~ platform-tools "yourUsername"$
...all you need to do is type:
./fastboot -i 0x1949 oem idme bootmode 4000
Hit enter, then:
./fastboot reboot
It will say "rebooting". If it doesn't reboot right away just hold down the power button until it shuts off, then restart.
If you aren't sure you are in the right directory to start off in, type:
ls
That's "Ls" not "is"...you should see, among other things, adb and fastboot. If you are not in the right directory (edit: type cd in the terminal) find the Android SDK folder and drag it to your terminal window hit enter and type:
cd platform-tools
That should get you going in the right direction
Sent from my Amazon Kindle Fire using xda premium
ERROR:could not get pipe properties
Okay well I finally got all my directories sorted out so those are fine and I entered in your commands which worked fine (THANK YOU SO MUCH) but now I'm getting this error
mac-users-macbook-pro-1634:tools macuser$ ./fastboot-mac -i 0x1949 oem idme bootmode 4000
./fasERROR: could not get pipe properties
< waiting for device >
^R
./ERROR: could not get pipe properties
ERROR: could not get pipe properties
ERROR: could not get pipe properties
ERROR: could not get pipe properties
ERROR: could not get pipe properties
ERROR: could not get pipe properties
ERROR: could not get pipe properties
ERROR: could not get pipe properties
ERROR: could not get pipe properties
ERROR: could not get pipe properties
ERROR: could not get pipe properties
ERROR: could not get pipe properties
_____________
I've tried it again and now I'm just getting "..." and it's not doing anything. :/
mac-users-macbook-pro-1634:~ macuser$ cd /Users/macuser/android-sdk-macosx/tools
mac-users-macbook-pro-1634:tools macuser$ ./fastboot-mac -i 0x1949 oem idme bootmode 4000
...
Success wooooo
OMG THANK YOU SO MUCH! I LOVE YOU! I seriously don't know what in the world I would have done without your help! I'm so happy right now! =D
If you ever need anything digitally designed hit me up at [email protected] I owe you one
Exact same problem resolved, my issue and solution
I've spent the past several hours banging my head against this problem. MBP and an iMac both running OS X 10.7.3 and VM Fusion 4.1. This thread seemed like the best place to share what I learned in case anyone else has a similar issue.
NOTE: I try and run everything inside vms to keep my base OS clean and just revert to snapshots frequently. Also I've rooted/modded a couple android phones with both these vms recently without incident.
Fought with two different XP Pro vms to get the ADB/Fastboot drivers installed. Kept getting an error about unsigned drivers. At some point the SDK drivers did install and I rooted successfully with KFU 0.9.3. Then I tried the TWRP install and had the same issue as the op. Stuck at the static Kindle Fire image. XP refused to recognize my KF and the drivers would not reinstall properly. Fastboot would remain at the "<waiting for device>" prompt when I used the fastboot -i 0x1949... bootmode command. I tried another route and booted a new OS X 10.7.3 vm and installed ADB/Fastboot. The same "<waiting for device>" prompt.
The problem had to do with the vmware usb implementation. I installed ADB/Fastboot to a non-vm install of 10.6.8 and my KF immediately responded to the bootmode command.
So if you're having a problem with the ADB/Fastboot drivers take a hard look at your usb setup.
In Windows 10,Powershell Command prompt doesn't recognize the command..."Fastboot Boot Recovery"
Can't TWRP at all...
What about the command "fastboot flash recovery.img"???
Can i brick my device if i flash directly? (without boot in it before)
andrexp31 said:
In Windows 10,Powershell Command prompt doesn't recognize the command..."Fastboot Boot Recovery"
Can't TWRP at all...
What about the command "fastboot flash recovery.img"???
Can i brick my device if i flash directly? (without boot in it before)
Click to expand...
Click to collapse
Command must hav adb written first
Use cmd on w10 not Powershell.
Quoting Microsoft:
It (PowerShell) replaces Command Prompt (aka, “cmd.exe”) in the WIN + X menu, in File Explorer’s File menu, and in the context menu that appears when you shift-right-click the whitespace in File Explorer. Typing “cmd” (or “powershell”) in File Explorer’s address bar will remain a quick way to launch the command shell at that location. For those who prefer to use Command Prompt, you can opt out of the WIN + X change by opening Settings > Personalization > Taskbar, and turning “Replace Command Prompt with Windows PowerShell in the menu when I right-click the Start button or press Windows key+X” to “Off”.
andrexp31 said:
In Windows 10,Powershell Command prompt doesn't recognize the command..."Fastboot Boot Recovery"
Can't TWRP at all...
What about the command "fastboot flash recovery.img"???
Can i brick my device if i flash directly? (without boot in it before)
Click to expand...
Click to collapse
Is your phone in fastboot mode with correct drivers installed? Do you have fastboot folder in Windows PATH variable? Is your recovery image called "Recovery"? What exactly does error say?
Knox1 said:
Command must hav adb written first
Click to expand...
Click to collapse
If is adb...is adb...if is Fastboot,is fastboot... adb is with the phone power on and fastboot...is with the phone in fastboot mode...for the only thing that i have to put adb first... is for"adb fastboot reboot" i think