Related
Hi together!
Since this is a topic where people ask regularly, I try to make a little TUT.
I hope it is helpful.
I am a noob myself, so please don't go on me
Please feel free to correct me if I am wrong or if I missed some important stuff.
What you need:
1.
SDK Tool (type in your browser: developer.android.com/sdk/index.html)
Once you are on that page, download the package and install it.
2.
after the install process has finished, you have to install some packages.
Important is the platform-tools package (there you find the most important commands)
3.
Locate the folder on the harddisk of your PC
4.a)
Push the Windows(Start) Buttom and type: cmd
This opens the command prompt
Now get into the root of the android folder (e.g. cd.. until you get into root of your harddisk)
(on my PC, it looks like this:
cd android
cd platform-tools)
4.b)
Just one thing to make it a little easier to come into the right folder:
Open the folder with the fastbootfiles in a window.
Go to command line and type cmd and the cmd.exe will be shown in the menu.
Drag & Drop the cmd.exe into the opened fastboot folder.
When you now open this cmd, it shows the right folder at the start and you can easily type the commands without navigation through folders.
credits go to Neo XL
5.
Your phone has to be in fastboot-USB mode and connected to PC in order to understand the commands
6.
Once you are in platform-tools folder, you can type commands
Most common commands are:
fastboot erase cache (sometimes helps if phone is in HTC bootloop)
fastboot flash boot (name of boot image / e.g. boot_1.2.3.img) (this is, like the name says, to flash a boot image)
fastboot flash recovery (name of recovery.img
fastboot oem lock ( to relock your phone, in case you have or want to flash a RUU)
fastboot flash unlocktoken Unlock_code.bin (to unlock again, if you already got the unlock key from HTCDev)
Flash firmware.zip using following terminal commands:
Please rename first downloaded .zip package to firmware.zip
fastboot oem rebootRUU
fastboot flash zip firmware.zip
This is almost obsolete, since we have the new Recovery 5.8.3.1 with Mount USB, but it is still good to know
to push ROM to SD card, if you were running superwipe without copying the rom file onto sd
1. You need recovery.img in your fastboot directory
2. Go into bootloader and connect phone
3. Then use: "fastboot boot recovery.img" (thus booting your image from pc and not the installed recovery).
4. When in recovery, you can use the adb commands.
5. You can try with "adb devices" which should show you serial of phone.
6. command: adb push rom_rom.zip /sdcard
credits to broncogr for finding that adb works if you use fastboot boot command and to Jotha for helping me out!
Or try following:
Copy rom to your adb-directory on PC
Switch OFF phone
Connect phone to PC
Wait until you hear the "USB-Connect"-sound on PC
Go into command window in adb-directory
Type "adb push rom.zip /sdcard/"
(where rom.zip is name of rom-file)
pushing is rather slow so it will take a while. Eventually you get an "OK". Then you can go into recovery and flash it.
Credits go to Jotha
Updated link
[TOOL][27/04] Automated Fastboot Commands For HTC One X continued
http://forum.xda-developers.com/showthread.php?t=1634786
credits go to TeAm Hex
For now, this is what I can think of, for sure there are many more commands, but hopefully we don't need them, but like I said, feel free and put them in here
I hope this will help some noobs, like myself!
If this helped you, please push THANKS
thanks! this will stop us noob's, spamming up dev's thread's.
Thanks for you efforts
First time with real android phone, this is good!
Thanks mate
Sent from my HTC One X using xda premium
Can you add the command to push the custom rom to sdcard without mout USB via CWM ?
Just one thing to make it a little easyer to come into the right folder:
Open the folder with the fastbootfiles in a window.
Go to command line and type cmd and the cmd.exe will be shown in the menu. Drag & Drop the cmd.exe into the opened fastboot folder.
When you now open this cmd, it shows the right folder at the start and you can easyly type the commands without navigation through folders.
incident said:
Can you add the command to push the custom rom to sdcard without mout USB via CWM ?
Click to expand...
Click to collapse
Would be great, if this is possible! But as far as I know, it not possible.
Edit:
It is possible now! Updated post!
Sent from my HTC One X using XDA
hello I have problem with loading boot.img in fastboot
sdk is open, phone is conncted to comp on fastboot usb mode , image is on disc c in folder fastboot and still recive this info
c:\fastboot>fastboot flash boot boot.img
'fastboot' is not recognized as an internal or external command,
operable program or batch file.
c:\fastboot>
pls help me with that
ok I fix this, that was problem with missing fastboot.exe and was no connection betwen phone and computer
this link helps fix that
http://dottech.org/tipsntricks/21534/how-to-install-adb-and-fastboot-on-your-windows-computer-for-use-with-your-android-phone/
You have to copy the Boot.img into the folder, where fastboot-, adb commands are situated (c:/andoid/platform-tools)
Then Open cmd. Go to platform-tools folder and from there it should work.
Sent from my HTC One X using XDA
Thanx man, but is fixed now, I did this by follow the instr. in page from my last post, and goes perfect. I just flashed new rom with 1.8 base and iam now on the bright side of life.
PS sorry for my english
@OP, last time I tried fastboot boot command it gave me device not found message(no problem when fastboot flash). What's the correct approach to make it work? I recently updated to 1.28 and I want to stay in stock for the mean time.
Sent either from my Arc or One X using xda premium
You can add the adb and fastboot directory path to the environment path in windows settings. You can then use adb and fastboot outside of the platform tools directory, but still in command prompt of course
Sent from my HTC One X using Tapatalk 2
I'm following your tutorial to the letter but whenever i use fastboot boot recovery.img it refuses to go into recovery. But i can boot into recovery manually and when i do there still isnt any adb devices connected.
Stuart.upton666 said:
I'm following your tutorial to the letter but whenever i use fastboot boot recovery.img it refuses to go into recovery. But i can boot into recovery manually and when i do there still isnt any adb devices connected.
Click to expand...
Click to collapse
3. Then use: "fastboot boot recovery.img" (thus booting your image from pc and not the installed recovery).
4. When in recovery, you can use the adb commands.
5. You can try with "adb devices" which should show you serial of phone.
6. command: adb push rom_rom.zip /sdcard
In point 3, it is not supposed to boot into recovery. Its for booting your recovery.img (e.g. recovery-clockwork-touch-5.8.3.1-endeavoru.img ) from PC. After this step you will automatically boot into Recovery. From there you can use adb commands.
Did you try "adb devices"?
I tried it myself and it works!
This guide is great... Thanks!
Sent from my HTC One X using xda premium
tonyhagger said:
This guide is great... Thanks!
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Thank you, Sir! Some kind of feedback is always appreciated !
Hi about Push to SDCARD command
My questions in Blue
to push ROM to SD card, if you were running superwipe without copying the rom file onto sd
1. You need recovery.img in your fastboot directory - Should i use signed recovery ?
2. Go into bootloader and connect phone
3. Then use: "fastboot boot recovery.img" (thus booting your image from pc and not the installed recovery).
4. When in recovery, you can use the adb commands.
5. You can try with "adb devices" which should show you serial of phone.
6. command: adb push rom_rom.zip /sdcard
incident said:
My questions in Blue
to push ROM to SD card, if you were running superwipe without copying the rom file onto sd
1. You need recovery.img in your fastboot directory - Should i use signed recovery ?
2. Go into bootloader and connect phone
3. Then use: "fastboot boot recovery.img" (thus booting your image from pc and not the installed recovery).
4. When in recovery, you can use the adb commands.
5. You can try with "adb devices" which should show you serial of phone.
6. command: adb push rom_rom.zip /sdcard
Click to expand...
Click to collapse
Take the newest CWM recovery.
Sent from my Desire HD using XDA
incident said:
My questions in Blue
to push ROM to SD card, if you were running superwipe without copying the rom file onto sd
1. You need recovery.img in your fastboot directory - Should i use signed recovery ?
2. Go into bootloader and connect phone
3. Then use: "fastboot boot recovery.img" (thus booting your image from pc and not the installed recovery).
4. When in recovery, you can use the adb commands.
5. You can try with "adb devices" which should show you serial of phone.
6. command: adb push rom_rom.zip /sdcard
Click to expand...
Click to collapse
Asking about number 6,since after push rom into sd card using adb command. How long will it takes rom to place in sd card? My adb command just stuck after push rom without inform is it done or not.
And where did the push file goes? Seems I can't find it in CWM. I'm using latest cwm, but no zip file found in my sd card.
TEKONG84 said:
[/COLOR]
Asking about number 6,since after push rom into sd card using adb command. How long will it takes rom to place in sd card? My adb command just stuck after push rom without inform is it done or not.
And where did the push file goes? Seems I can't find it in CWM. I'm using latest cwm, but no zip file found in my sd card.
Click to expand...
Click to collapse
Rom should be on root of Sd.
If this is not working, you can try to use the command while phone is powered off. I am not a dev, but I read something like that:
"Switch off your phone, connect to pc, wait until it is detected by windows and use: adb push nameofrom.zip /sdcard/" thats what Jotha told someone on ARHD Thread.
Try that and tell us if it worked.
Sent from my Desire HD using XDA
Hi,
I accidentally deleted everything through TWRP. I wanted the kindle fresh for my new ROM, and thought that deleting everything would make for a cleaner install. I was wrong and now all my kindle is good for is TWRP.
When in TWRP, windows doesn't recognize the kindle. Because of this, I cannot mount it. Windows and the kindle fire utility recognizes it as adp when i boot regularly (which is just a black screen) but cannot do anything since it will not enter normal or fast mode.
I don't know what to do, nothing is working. When I restart the kindle it says superuser is not installed, and asks if I would like to install it. I say yes, and it fails. Super user WAS installed before I deleted everything.
Any ideas?
Some more info
1. shell doesn't work
2. it looks like the bootmode is stuck in fastboot, but KFU won't recognize it, even though windows does.
3. Windows does not recognize the kindle when in TWRP recovery mode. If It did i could simply transfer files over and flash it...
4. If I try to boot normally, I get a black screen, but FKU recognizes ADP. It does not recognize what bootmode it's in though.
I believe FFF is working as I have the blue kindle logo and options in the bootloader, but no matter what I do I can't figure it out.
I REALLY need some help from you more experienced guys
thanks for reading
I'm making some progress, I'm in fastboot command prompt and have access. But what do I do from here?
How can I install a system from fastboot? It looks like all the guides say to install twrp and go from there but I have twrp and it wont communicate with my pc!!!
ADB
llmercll said:
Some more info
1. shell doesn't work
2. it looks like the bootmode is stuck in fastboot, but KFU won't recognize it, even though windows does.
3. Windows does not recognize the kindle when in TWRP recovery mode. If It did i could simply transfer files over and flash it...
4. If I try to boot normally, I get a black screen, but FKU recognizes ADP. It does not recognize what bootmode it's in though.
I believe FFF is working as I have the blue kindle logo and options in the bootloader, but no matter what I do I can't figure it out.
I REALLY need some help from you more experienced guys
thanks for reading
Click to expand...
Click to collapse
Do you have adb and fastboot intstalled on your PC??
lj50036 said:
Do you have adb and fastboot intstalled on your PC??
Click to expand...
Click to collapse
Yes, I've been using them at the command level
Feedback
llmercll said:
Yes, I've been using them at the command level
Click to expand...
Click to collapse
Boot into recovery and type
adb devices
copy and paste the output of this so I can see!!!
I went to boot and at the black screen tried to push the stock kindle FW. it failed for some reason
c:\kfu\tools>adb devices
List of devices attached
0123456789ABCDEF device
c:\kfu\tools>adb push C:\update.zip \tmp
failed to copy 'C:\update.zip' to '\tmp': Read-only file system
c:\kfu\tools>
Here is me trying adb devices in recovery mode
c:\kfu\tools>adb reboot recovery
c:\kfu\tools>adb devices
List of devices attached
Interestingly, rebooting into recovery just brought me to the bootloader. it wouldnt boot into recovery by itself, I have to manually do it through the bootloader. Immediately, booting into recovery disconnects my kindle from the pc, and I hear the sound in windows and the kindle dissapears from device manager.
llmercll said:
I went to boot and at the black screen tried to push the stock kindle FW. it failed for some reason
c:\kfu\tools>adb devices
List of devices attached
0123456789ABCDEF device
c:\kfu\tools>adb push C:\update.zip \tmp
failed to copy 'C:\update.zip' to '\tmp': Read-only file system
c:\kfu\tools>
Here is me trying adb devices in recovery mode
c:\kfu\tools>adb reboot recovery
c:\kfu\tools>adb devices
List of devices attached
Interestingly, rebooting into recovery just brought me to the bootloader. it wouldnt boot into recovery by itself, I have to manually do it through the bootloader. Immediately, booting into recovery disconnects my kindle from the pc, and I hear the sound in windows and the kindle dissapears from device manager.
Click to expand...
Click to collapse
So you can boot into recovery yes??
What is this KFU if that some kindle stuff we need to get rid of it and get the fastboot and adb from google... The SDK
make sure you open your CMD window as admin and try putting that file in the /sdcard not the /tmp
lj50036 said:
So you can boot into recovery yes??
What is this KFU if that some kindle stuff we need to get rid of it and get the fastboot and adb from google... The SDK
make sure you open your CMD window as admin and try putting that file in the /sdcard not the /tmp
Click to expand...
Click to collapse
I can boot into recovery, yes. KFU is kindle fire utility. I have the sdk and fastboot and adb.
could putting it in tmp be why the push failed?
Admin
llmercll said:
I can boot into recovery, yes. KFU is kindle fire utility. I have the sdk and fastboot and adb.
could putting it in tmp be why the push failed?
Click to expand...
Click to collapse
Or maybe you did not open you CMD window as admin....but twrp should see your devices in adb and let you push things to the /sdcard for sure... I have one right in front of me, but I am running linux which is much better for these kinds of things... Here is my output of that command and than a push of a zip file
Code:
[email protected] ~ $ adb devices
List of devices attached
0123456789ABCDEF recovery
[email protected] ~ $ adb push cmb_kkgapps_20131209.zip /sdcard
6121 KB/s (126216099 bytes in 20.135s)
I ran it as admin, now I get an error saying /sdcard is a directory
C:\Windows\system32>cd c:/kfu/tools
c:\kfu\tools>adb push C:\update.zip /sdcard
failed to copy 'C:\update.zip' to '/sdcard': Is a directory
c:\kfu\tools>adb devices
List of devices attached
0123456789ABCDEF device
c:\kfu\tools>
feedback
llmercll said:
I ran it as admin, now I get an error saying /sdcard is a directory
C:\Windows\system32>cd c:/kfu/tools
c:\kfu\tools>adb push C:\update.zip /sdcard
failed to copy 'C:\update.zip' to '/sdcard': Is a directory
c:\kfu\tools>adb devices
List of devices attached
0123456789ABCDEF device
c:\kfu\tools>
Click to expand...
Click to collapse
Move everything to the root of your c drive fastboot.exe, adb.exe, update.zip, all of it and than when you open your CMD windowas admin type
cd /
This will move you to the root of your c drive in you CMD window... Than type dir to make sure u can see your fastboot and adb and your update zip
than type
adb push update.zip /sdcard
llmercll said:
I ran it as admin, now I get an error saying /sdcard is a directory
C:\Windows\system32>cd c:/kfu/tools
c:\kfu\tools>adb push C:\update.zip /sdcard
failed to copy 'C:\update.zip' to '/sdcard': Is a directory
c:\kfu\tools>adb devices
List of devices attached
0123456789ABCDEF device
c:\kfu\tools>
Click to expand...
Click to collapse
It's been a long time since I looked at this, but I seem to remember the windows adb client wanting a trailing slash if the push destination is a directory. That is... you want to use "/sdcard/" instead of "/sdcard" in that command to indicate that you want to push a file into that directory rather than replace the directory with a file (which it won't allow). Alternatively, you can use "/sdcard/update.zip" to remove any ambiguity from the command.
The output of your "adb devices" command is also a concern. It doesn't look to me as if you've booted the device into TWRP because it should output "recovery" and not "device" at the end there. One way or another, you'll have to get it to boot into TWRP if you want to flash that update.zip.
I wanna thank you guys for helping me. I'll never be able to figure this out alone.
Still no luck. It either says it's a directory or I lack permission.
C:\>adb devices
List of devices attached
0123456789ABCDEF device
C:\>adb push update.zip /sdcard
failed to copy 'update.zip' to '/sdcard': Is a directory
C:\>adb push update.zip /sdcard/
failed to copy 'update.zip' to '/sdcard//update.zip': Permission denied
C:\>adb push update.zip /sdcard/update.zip
failed to copy 'update.zip' to '/sdcard/update.zip': Permission denied
C:\>
Click to expand...
Click to collapse
I can get into TWRP, but windows will not recognize the kindle while in recovery mode. The only times windows will recognize the devices is if I'm sitting at the boot launcher (it says fastboot) or try and normal boot (and it says "device"). If I could just connect to the PC in TWRP, i could mount it, cut for some reason I can't. Whenever I exit TWRP it also warns me that superuser is not installed, and if I would like to install it. I say yes, and it gives me an error =/
Fastboot works great though, is there anything I can just flash?
llmercll said:
I wanna thank you guys for helping me. I'll never be able to figure this out alone.
Still no luck. It either says it's a directory or I lack permission.
I can get into TWRP, but windows will not recognize the kindle while in recovery mode. The only times windows will recognize the devices is if I'm sitting at the boot launcher (it says fastboot) or try and normal boot (and it says "device"). If I could just connect to the PC in TWRP, i could mount it, cut for some reason I can't. Whenever I exit TWRP it also warns me that superuser is not installed, and if I would like to install it. I say yes, and it gives me an error =/
Fastboot works great though, is there anything I can just flash?
Click to expand...
Click to collapse
Try to use the "mount" function in TWRP to mount the /sdcard partition on your computer. It should work with the generic drivers already on your Windows PC and you can copy the update.zip over to it that way. If you can't get that to work, you are going to have to try reinstalling the drivers to get your PC to recognize TWRP. There are detailed instructions on how to do this in my guide.
The only other thing I can think of is to try reflashing an older version of TWRP. Those directions are available in one of my guides as well.
Recovery
llmercll said:
I wanna thank you guys for helping me. I'll never be able to figure this out alone.
Still no luck. It either says it's a directory or I lack permission.
I can get into TWRP, but windows will not recognize the kindle while in recovery mode. The only times windows will recognize the devices is if I'm sitting at the boot launcher (it says fastboot) or try and normal boot (and it says "device"). If I could just connect to the PC in TWRP, i could mount it, cut for some reason I can't. Whenever I exit TWRP it also warns me that superuser is not installed, and if I would like to install it. I say yes, and it gives me an error =/
Fastboot works great though, is there anything I can just flash?
Click to expand...
Click to collapse
I would if it were me, install a recovery you dont plan on using... Than flash the one you would like to us.... I know it sounds funny but.. Ive be here before and that seems to work everytime... Than flash ROM and Gapps....
Here is the link to TWRP the first gen fire is an 'otter'... Make sure you get the otter.img....Than rename the .img file to twrp.img than put it with fastboot.exe and open CMD window as admin...and type
Code:
fastboot -i 0x1949 flash recovery twrp.img
Than
Code:
fastboot -i 0x1949 reboot
Let me know if that works for you or if you have any questions along the way... Thx as always lj
I didn't see the link for the older TWRP, but I went to the website and tried this one
http://techerrata.com/browse/twrp2/blaze
openrecovery-twrp-2.4.2.0-otter.img
I successfully flashed it and rebooted, but when the kindle went into recovery mode it once again disconnected from the computer. In recovery, which was clearly the older TWRP version, I attempted to mount but nothing happened. Of course it can't happen if it isn't communicating with my pc =/
Can I flash a ROM directly through fastboot? That would probably solve the issue, no?
What about that other recovery program, COTR?
llmercll said:
I didn't see the link for the older TWRP, but I went to the website and tried this one
http://techerrata.com/browse/twrp2/blaze
openrecovery-twrp-2.4.2.0-otter.img
I successfully flashed it and rebooted, but when the kindle went into recovery mode it once again disconnected from the computer. In recovery, which was clearly the older TWRP version, I attempted to mount but nothing happened. Of course it can't happen if it isn't communicating with my pc =/
Can I flash a ROM directly through fastboot? That would probably solve the issue, no?
What about that other recovery program, COTR?
Click to expand...
Click to collapse
2.6.3.1 Give that one a try!!!
I was able to get TWRP recognized by windows by using the earliest blaze edition. I mounted, copied the files, and then flashed back to 2.6.3.1 otter.
Then I wiped whatever data may have been in system data and cache and installed a new rom...
Only problem is it seems to be hanging on "updating partition details.."
I have the option to reboot, but am not sure if I should...
I think I got it!!
I just accidentally wiped my SD card and my system and now I don't know how to get a rom onto my phone due to the lack of an SD card slot. Can anyone help me get a rom on the internal so I can flash? I have TWRP still but I have no clue how to get a rom to my sd card. Am I screwed? Cause I read a forum that had to have usb-debugging on and I have no system lol. Thank you guys so much
You dont need USB debugging tot have adb in recovery. Just use adb sideload. Or adb push.
Sent from my Galaxy Nexus using xda app-developers app
mrgnex said:
You dont need USB debugging tot have adb in recovery. Just use adb sideload. Or adb push.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Could you give me the commands to adb push a rom to the phone? I can't get adb to recognize my device in fastboot either When I use the fastboot devices command no devices show up... it's depressing
jtl_777 said:
Could you give me the commands to adb push a rom to the phone? I can't get adb to recognize my device in fastboot either When I use the fastboot devices command no devices show up... it's depressing
Click to expand...
Click to collapse
First use TWRP not fastboot. Once you are in recovery plug the phone in and type "adb devices" (without the quotes) in command prompt or terminal. If it returns with letters and numbers (can't remember might be a combination of both) your good to go. Type "adb push c:\downloads\Rom.zip /sdcard" type out the directory where the file is instead of downloads change it to where your rom is. If you type adb devices and nothing happens you need to work on your drivers.
jtl_777 said:
Could you give me the commands to adb push a rom to the phone? I can't get adb to recognize my device in fastboot either When I use the fastboot devices command no devices show up... it's depressing
Click to expand...
Click to collapse
I had this issue - I couldn't get the computer to recognise the phone when it was in the Bootloader. I had to uninstall all the android drivers I could find (using this: https://www.topnotchtablets.com/FixUSBproblems) and then plug the handset back into the USB while in bootloader.
Let it detect it as a generic device (or whatever it chooses to see it as, mine was different every time), then in Device Manager, right click it, then select Update Driver Software. Select the option to choose the driver you want to install and navigate to where you have the drivers saved. The actual driver is: android_winusb.inf. Choose the option select the driver yourself from that file, and locate the one that says Bootloader.
After doing all of that I was able to see it all fine, and it was detected in fastboot, and all the toolkits I used.
Someone feel free to correct me anywhere I'm wrong - just going from memory here.
The drivers are here: https://dl-ssl.google.com//android/repository/latest_usb_driver_windows.zip
mickeyflip said:
I had this issue - I couldn't get the computer to recognise the phone when it was in the Bootloader. I had to uninstall all the android drivers I could find (using this: https://www.topnotchtablets.com/FixUSBproblems) and then plug the handset back into the USB while in bootloader.
Let it detect it as a generic device (or whatever it chooses to see it as, mine was different every time), then in Device Manager, right click it, then select Update Driver Software. Select the option to choose the driver you want to install and navigate to where you have the drivers saved. The actual driver is: android_winusb.inf. Choose the option select the driver yourself from that file, and locate the one that says Bootloader.
After doing all of that I was able to see it all fine, and it was detected in fastboot, and all the toolkits I used.
Someone feel free to correct me anywhere I'm wrong - just going from memory here.
The drivers are here: https://dl-ssl.google.com//android/repository/latest_usb_driver_windows.zip
Click to expand...
Click to collapse
Cool story he's trying to use adb not fastboot two totally different things.
DR3W5K1 said:
Cool story he's trying to use adb not fastboot two totally different things.
Click to expand...
Click to collapse
He said he can't get adb to recognize his device - isn't that because the drivers aren't installed properly? I know adb and fastboot are two separate things. If the device isn't showing after he enters "fastboot devices" then my first guess was that the phone, in bootloader (since he has no OS installed), isn't showing up in device manager either because the drivers aren't there.
Excuse me for trying to offer thorough assistance...
mickeyflip said:
He said he can't get adb to recognize his device - isn't that because the drivers aren't installed properly? I know adb and fastboot are two separate things. If the device isn't showing after he enters "fastboot devices" then my first guess was that the phone, in bootloader (since he has no OS installed), isn't showing up in device manager either because the drivers aren't there.
Excuse me for trying to offer thorough assistance...
Click to expand...
Click to collapse
Sorry if I sounded like a Douche. I might be wrong but I thought adb and fastboot had separate driver sets.
DR3W5K1 said:
Sorry if I sounded like a Douche. I might be wrong but I thought adb and fastboot had separate driver sets.
Click to expand...
Click to collapse
No worries - it's possible that they do. But the drivers I linked are the ones that worked for me consistently. The Samsung ones seemed to stop working each time I disconnected the handset and plugged it back in via USB.
In any case, those are the only ones I have installed right now and everything is working great for me connection/recognition wise.
Any luck yet jtl_777?
To push files to the handset, use the command: adb push filename.ext destination-folder
Explained further here: http://developer.android.com/tools/help/adb.html#copyfiles
Just for future reference so people reading these threads don't get super confused, your computer won't recognize your phone through adb commands unless you are in adb sideload through your custom recovery, or if you're booted up and running in an operating system. You could also use adb push commands in your custom recovery. This has nothing to do with drivers or whatnot. If in bootloader your device isn't recognized through adb commands, that's completely normal, because it never would be, but your device should be recognized in bootloader with fastboot commands.
IF your phone is NOT recognized in your booted up phone, or in adb sideload through your custom recovery, or with adb push commands in your custom recovery, with adb commands, then you have driver issues.
ALSO IF your phone is NOT recognized while in bootloader, with fastboot commands, then you have driver issues.
To answer the OP's question:
If you have an unlocked bootloader and you are in TWRP, you can mount your phone onto your computer and copy and paste the rom zip onto the phone and then install it through TWRP once on the phone. If that doesn't work, then you can try using adb push commands while in TWRP (or maybe need to be in adb sideload through TWRP) to push the rom to your sd card and then run it through TWRP. If that doesn't work, you can also try flashing the rom zip through bootloader with fastboot commands, but all these commands might be device specific, that's why I won't tell you the commands I know for the HTC One X, but the processes are the same no matter what. Hope that helps
You don't need to be in sideload mode to use adb in recovery. I use adb in recovery all the time on all my devices to push files
Sent from my Nexus 5
Pirateghost said:
You don't need to be in sideload mode to use adb in recovery. I use adb in recovery all the time on all my devices to push files
Sent from my Nexus 5
Click to expand...
Click to collapse
I believe that's if you're using push commands, no? Other than adb push commands, can you use other adb commands while in a custom recovery, without adb sideload?
For the sake of clarity, you cannot use any adb commands while in stock recovery, but you could if you have a custom recovery.
EsoteRIcalfreaK said:
I believe that's if you're using push commands, no? Other than adb push commands, can you use other adb commands while in a custom recovery, without adb sideload?
For the sake of clarity, you cannot use any adb commands while in stock recovery, but you could if you have a custom recovery.
Click to expand...
Click to collapse
Adb shell as well as numerous other commands work just fine
Sent from my Nexus 5
hi all
I have a problem on getting TWRP to work properly.
I initially used BreakDroid to install TWRP, everything worked fine.
I tried to install the cm-11-20140512.1655-SKANKY-otter.zip OS but I first got the "error 7", fixed that, and then it was stuck at "updating package" (or similar)....
then I saw an updated version of TWRP, without realizing that it was for an asys TF101 tablet (http://forum.xda-developers.com/showthread.php?t=2434422)...I installed that and now twrp doesn't work because the screen is the wrong size and I can't get to various buttons including flash/wipe etc..
I can still mount it tho so I thought about using adb/flashboot...but I can't seem to override that version of TWRP.
...best part...i cannot restore the original amazon OS since I didn't do a backup (...i know...:angel
does anyone have any idea about how I can fix that and install a kitkat rom?
I have nandroid backup of stock in my list.
sd_shadow's collection of links for: Kindle Fire 1
Sent from my Amazon Kindle Fire using Tapatalk
sd_shadow said:
I have nandroid backup of stock in my list.
Click to expand...
Click to collapse
thanks for the reply.
I did look at it but my problem is that I don't need to backup the system, I need to be able to install a recovery tool (twrp or cwmr) that will allow me to flash a rom on my kindle.
my problem now is that I can't seem to be able to do that since the recovery I have is for a different tablet and the screen won't allow me to get to the right buttons...I can only turn the kindle on and off .
SbDROID2012 said:
thanks for the reply.
I did look at it but my problem is that I don't need to backup the system, I need to be able to install a recovery tool (twrp or cwmr) that will allow me to flash a rom on my kindle.
my problem now is that I can't seem to be able to do that since the recovery I have is for a different tablet and the screen won't allow me to get to the right buttons...I can only turn the kindle on and off .
Click to expand...
Click to collapse
you tried
with kindle fire in twrp, connected to mac
adb shell
su
idme bootmode 4002
reboot
# back in your PC shell
fastboot -i 0x1949 flash recovery openrecovery-twrp-2.6.3.1-otter.img
fastboot reboot
I don't have a mac, so commands might not be quite right
may want to read [GUIDE] Set up ADB and Fastboot on a Mac easily
and you will need openrecovery-twrp-2.6.3.1-otter.img
sd_shadow said:
you tried
with kindle fire in twrp, connected to mac
adb shell
su
idme bootmode 4002
reboot
# back in your PC shell
fastboot -i 0x1949 flash recovery openrecovery-twrp-2.6.3.1-otter.img
fastboot reboot
I don't have a mac, so commands might not be quite right
may want to read [GUIDE] Set up ADB and Fastboot on a Mac easily
and you will need openrecovery-twrp-2.6.3.1-otter.img
Click to expand...
Click to collapse
I did try to do that but
1)
adb shell
Click to expand...
Click to collapse
--> doesn't work and I get "error: device not found"
i did the "./android update adb" with "adb kill-server" and "adb start-server" but nothing changed..
2) I installed the img file anyway through
fastboot flash recovery
Click to expand...
Click to collapse
the img file but i still cannot get the twrp with the view for kindle...see attached image. i have NO ACCESS to some of the buttons, therefore I can't do much with it.
I would REALLY like to be able to install a CWM...i tried the one here http://forum.xda-developers.com/showthread.php?t=1454241 using
fastboot flash recovery cwm-file-here.img
Click to expand...
Click to collapse
but it gets to the boot page, I select "recovery" and then it's stuck with the kindle logo and the small "booting..." at the bottom of the screen...so I re-installed twrp even tho i still have that damn "build for Asus TF101 Series Tablets" (see attachment) warning on top!!
any help would be HUGELY appreciated!!
also, using "adb devices" I still can't see it.
Run this command from your computer with your kindle connected when you turn it on:
fastboot getvar product
The FFF bootloader temporarily enables fastboot as the device boots up. When you issue this command, it puts the device into permanent fastboot mode. Just flash the correct recovery after that:
fastboot -i 0x1949 flash recovery your-recovery.img
fastboot reboot
Duchman said:
Run this command from your computer with your kindle connected when you turn it on:
fastboot getvar product
The FFF bootloader temporarily enables fastboot as the device boots up. When you issue this command, it puts the device into permanent fastboot mode. Just flash the correct recovery after that:
fastboot -i 0x1949 flash recovery your-recovery.img
fastboot reboot
Click to expand...
Click to collapse
ok...that doesn't work...
I get the same problem, if I download the correct twrp from here http://teamw.in/project/twrp2/79 I get exactly the same screenshot I posted above..
and the cwm recovery is not available anymore so I don't really know how to fix this...without working recovery I can't install any rom!!
SbDROID2012 said:
ok...that doesn't work...
I get the same problem, if I download the correct twrp from here http://teamw.in/project/twrp2/79 I get exactly the same screenshot I posted above..
and the cwm recovery is not available anymore so I don't really know how to fix this...without working recovery I can't install any rom!!
Click to expand...
Click to collapse
When you are flashing TWRP image in bootloader/fastboot do you see sending ... writing... in command prompt?
like this?
sd_shadow said:
When you are flashing TWRP image in bootloader/fastboot do you see sending ... writing... in command prompt?
like this?
Click to expand...
Click to collapse
When I launch the fastboot flash in fastboot mode I do get nothing but the blank cursor on a new line, although I see the device with "fastboot devices". After a few min that was stuck then I turned it off and the first part came up saying " sending file" but then it gave me an error saying that the connection was lost...which makes sense cause i turned it off..
If instead I launch the command and THEN turn the kindle on it does show me the correct output in a couple of secs as your showed. But then even if I do fastboot reboot, it does reboot it but no correct recovery is loaded...still the wrong screen size... Very very frustrating...
And btw...thanks for bearing with me through this!!!
---edit---
Now that I think about it...the twrp screen, although the wring size, actually reflects the VERSION of twrp that I'm installing through fastboot...it's as if the twrp I got from here ( http://forum.xda-developers.com/showthread.php?t=2434422) controls the size of the screen while I'm able to change the version of twrp...I think that that is a recovery GUI for the Asus tablet, any idea if I can install another GUI?...hopefully this helps...
SbDROID2012 said:
When I launch the fastboot flash in fastboot mode I do get nothing but the blank cursor on a new line, although I see the device with "fastboot devices". After a few min that was stuck then I turned it off and the first part came up saying " sending file" but then it gave me an error saying that the connection was lost...which makes sense cause i turned it off..
If instead I launch the command and THEN turn the kindle on it does show me the correct output in a couple of secs as your showed. But then even if I do fastboot reboot, it does reboot it but no correct recovery is loaded...still the wrong screen size... Very very frustrating...
And btw...thanks for bearing with me through this!!!
---edit---
Now that I think about it...the twrp screen, although the wring size, actually reflects the VERSION of twrp that I'm installing through fastboot...it's as if the twrp I got from here ( http://forum.xda-developers.com/showthread.php?t=2434422) controls the size of the screen while I'm able to change the version of twrp...I think that that is a recovery GUI for the Asus tablet, any idea if I can install another GUI?...hopefully this helps...
Click to expand...
Click to collapse
Your guess is right, installing another TWRP version doesn't affect the theme you are using, unless it has a theme of its own. You could delete the ui.zip from the TWRP folder and that would solve it. The folder should be in sdcard.
Duchman said:
Your guess is right, installing another TWRP version doesn't affect the theme you are using, unless it has a theme of its own. You could delete the ui.zip from the TWRP folder and that would solve it. The folder should be in sdcard.
Click to expand...
Click to collapse
so..the problem with that is that I could not access the sdcard since adb doesn't work...however...as of now I've been able to fix the layout problem by using
fastboot -w
fastboot flash recovery twrp.2.7.0.1.img
fastboot reboot
Click to expand...
Click to collapse
once rebooting I had to re-wipe (advance wipe) sdcard/cache/data since when I tried to mount them I could not check the boxes.
now i STILL cannot mount it and adb does not recognize it.
I'm using mac and I tried
android update adb
Click to expand...
Click to collapse
but still adb can't see the kindle and I can't mount it through twrp
...however, I'm still able to reboot in bootloader and use fastboot
I don't think I can flash a .zip rom from fastboot tho...and I'm not sure how to transfer files on the kindle to flash them from twrp...any idea?
thanks a ton!!
-- edit --
i already modified the ~/.android/adb_usb.ini file adding 0×1949 and then running
adb kill-server
adb devices
but what I get is just
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
and nothing to it...the "adb shell" still gives me "device not found"!!
try flashing Cannibal Open Touch Recovery see http://forum.xda-developers.com/showthread.php?t=2025793
links are bad so uploaded my copy to http://d-h.st/XWy
sd_shadow said:
try flashing Cannibal Open Touch Recovery see http://forum.xda-developers.com/showthread.php?t=2025793
links are bad so uploaded my copy to http://d-h.st/XWy
Click to expand...
Click to collapse
SCORE !!!
dunno why twrp was the problem! the new recovery that you linked worked like magic, adb worked perfectly, I already flashed a rom and it works!!
so...why wouldn't twrp allow me to use adb or mount disks through usb?!
thanks so much for the help!!
Guessing it doesn't use the twrp theme, that was causing trouble.
Sent from my Amazon OtterX using Tapatalk
Hey,
I need some help.
I tried to install LineageOS 14.1 on my Oneplus 3 following this guide, but I think by wiping /data or /system the ROM, which I copied to the phone beforehand, got deleted. Now I don't have any ROM in the storage and also no system installed.
I think fastboot only works in the bootloader mode (I get my phone serial number if I enter the command fastboot devices), but it doesn't work in the recovery mode (because I don't get my serial number then).
If I use the command: C:\adb\SDK\platform-tools>adb push lineage-14.1-20180328-UNOFFICIAL-Sultan-oneplus3.zip /sdcard/ I get the error: adb: error: failed to get feature set: no devices/emulators found while in bootloader mode and also the same error if I am in recovery mode. And if I try ADB Sideload (without wiping Dalvik Cache or Cache) my phone just says Starting ADB sideload features but does nothing else.
Does anyone know what I can do to fix my phone? If it helps I backed up my phone beforehand, but the backup files also got deleted on the phone, but I still have them on my pc.
Not sure if it will help, but make sure you are using the latest ADB downloaded from:
https://developer.android.com/studio/releases/platform-tools
I have had some strange problems with old ADB versions in the past,
good luck hope it helps you.
jeffrey268 said:
Not sure if it will help, but make sure you are using the latest ADB downloaded from: ...
I have had some strange problems with old ADB versions in the past,
good luck hope it helps you.
Click to expand...
Click to collapse
Is this the most recent version?
Code:
C:\adb\SDK\platform-tools>adb version
Android Debug Bridge version 1.0.39
Version 0.0.1-4500957
Installed as C:\adb\SDK\platform-tools\adb.exe
C:\adb\SDK\platform-tools>adb devices
List of devices attached
adb server version (32) doesn't match this client (39); killing...
* daemon started successfully
C:\adb\SDK\platform-tools>adb devices
List of devices attached
C:\adb\SDK\platform-tools>fastboot devices
3d0553dc fastboot
It should be, because I installed the SDK Platform today.
Also most guides which help to get adb working say, that if the phone doesn't get recognized you should get the install the drivers via the device manager, but my phones doesn't show up there, probably because it is in bootloader/recorvery mode.
EDIT: I now discovered that my phone gets recognized as Marshall London Device in the windows device manager and if I click on it it says Google Nexus ADB Interface. Are there any Oneplus 3 drivers which I should install instead?
Flix117 said:
Is this the most recent version?
Code:
C:\adb\SDK\platform-tools>adb version
Android Debug Bridge version 1.0.39
Version 0.0.1-4500957
Installed as C:\adb\SDK\platform-tools\adb.exe
C:\adb\SDK\platform-tools>adb devices
List of devices attached
adb server version (32) doesn't match this client (39); killing...
* daemon started successfully
C:\adb\SDK\platform-tools>adb devices
List of devices attached
C:\adb\SDK\platform-tools>fastboot devices
3d0553dc fastboot
It should be, because I installed the SDK Platform today.
Also most guides which help to get adb working say, that if the phone doesn't get recognized you should get the install the drivers via the device manager, but my phones doesn't show up there, probably because it is in bootloader/recorvery mode.
EDIT: I now discovered that my phone gets recognized as Marshall London Device in the windows device manager and if I click on it it says Google Nexus ADB Interface. Are there any Oneplus 3 drivers which I should install instead?
Click to expand...
Click to collapse
I use this drivers https://androidfilehost.com/?fid=24591020540821930
xGOGI said:
I use this drivers https://androidfilehost.com/?fid=24591020540821930
Click to expand...
Click to collapse
Try this:
Download the stock recovery for your device:
http://oxygenos.oneplus.net.s3.amazonaws.com/recovery_op3.img
Place it in c:\OP3\
Go into cmd and go to c:\OP3\
then type: fastboot flash recovery recovery_op3.img
If you get reboots after this, do the following:
Boot back into fastboot and type:
fastboot format userdata
after that type:
fastboot flash recovery recovery_op3.img
Flix117 said:
Hey,
I need some help.
I tried to install LineageOS 14.1 on my Oneplus 3 following this guide, but I think by wiping /data or /system the ROM, which I copied to the phone beforehand, got deleted. Now I don't have any ROM in the storage and also no system installed.
I think fastboot only works in the bootloader mode (I get my phone serial number if I enter the command fastboot devices), but it doesn't work in the recovery mode (because I don't get my serial number then).
If I use the command: C:\adb\SDK\platform-tools>adb push lineage-14.1-20180328-UNOFFICIAL-Sultan-oneplus3.zip /sdcard/ I get the error: adb: error: failed to get feature set: no devices/emulators found while in bootloader mode and also the same error if I am in recovery mode. And if I try ADB Sideload (without wiping Dalvik Cache or Cache) my phone just says Starting ADB sideload features but does nothing else.
Does anyone know what I can do to fix my phone? If it helps I backed up my phone beforehand, but the backup files also got deleted on the phone, but I still have them on my pc.
Click to expand...
Click to collapse
To clear some things up for you. Fastboot is only used in bootloader mode since that is what it is.
And for the adb sideload, are you initializing the sideload on your phone as well? To use sideload the phone has to be ready on the receiving end, in recovery you have to start adb sideload then launch the process on pc for it to work properly. And if you dont want the whole android SDK to just use ADB and Fastboot i recommend you install the minimal tool https://forum.xda-developers.com/showthread.php?t=2588979 :good: