So, I'm trying to unlock the bootloader. I can't get it to show up on my laptop running Windows 8.1. Just can't figure out how to get my pc to find the device even after typing adb devices or fast boot devices.
try this to put device in fastboot, press and hold button that is located on the bottom of the player, plug in the power cord and hold until led light flashes repeatedly.
eko3484 said:
So, I'm trying to unlock the bootloader. I can't get it to show up on my laptop running Windows 8.1. Just can't figure out how to get my pc to find the device even after typing adb devices or fast boot devices.
Click to expand...
Click to collapse
i had same issue see here
http://forum.xda-developers.com/showpost.php?p=56870580&postcount=6
Still trying. No luck yet.
eko3484 said:
Still trying. No luck yet.
Click to expand...
Click to collapse
Have you unlocked the developer options in the About menu? Then did you enable USB debugging in the developer options? Those two steps are required before your PC will recognize the NP in adb. Also make sure you are on the latest SDK to get the newest platform tools (and drivers).
Elrondolio said:
Have you unlocked the developer options in the About menu? Then did you enable USB debugging in the developer options? Those two steps are required before your PC will recognize the NP in adb. Also make sure you are on the latest SDK to get the newest platform tools (and drivers).
Click to expand...
Click to collapse
Yes I have done all of that. I have the latest sdk but maybe I set it up wrong? It detects my phone, I can run commands through the terminal and everything. It just won't detect the nexus player. My guess was maybe drivers but I'm no expert here lol.
eko3484 said:
Yes I have done all of that. I have the latest sdk but maybe I set it up wrong? It detects my phone, I can run commands through the terminal and everything. It just won't detect the nexus player. My guess was maybe drivers but I'm no expert here lol.
Click to expand...
Click to collapse
Try holding down the button on the bottom of the NP until the white light starts quickly flashing, then let go. This'll put you directly in fastmount mode. Then try "fastmount devices" from your pc to see if it's recognized (assuming you have a normal usb cable between the two, no OTG cable between them of course).
Elrondolio said:
Try holding down the button on the bottom of the NP until the white light starts quickly flashing, then let go. This'll put you directly in fastmount mode. Then try "fastmount devices" from your pc to see if it's recognized (assuming you have a normal usb cable between the two, no OTG cable between them of course).
Click to expand...
Click to collapse
Okay. Do you mean, hold the button as I plug in the power cord? I can get it to fastboot mode just fine.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I have USB Debugging enabled.
The sdk works with my phone.
My pc will not detect when I plug in the nexus player, whether it is fastboot mode or running normally.
Anything else I can try?
eko3484 said:
I have USB Debugging enabled.
The sdk works with my phone.
My pc will not detect when I plug in the nexus player, whether it is fastboot mode or running normally.
Anything else I can try?
Click to expand...
Click to collapse
Sorry, I was typing quickly and mistyped. You can't use adb in fastboot mode (which is what you're in when you manually reboot with the button held down), only fastboot works.
Type "fastboot devices" and see if yours shows up. Its the "fastboot oem unlock" command you'll need to type twice to unlock the bootloader, but "fastboot devices" will tell you if its seeing your NP in the first place. Again, adb won't work in fastboot mode.
Thanks but it's still a no go. Maybe I could try using another pc. Makes no sense because it all works for my note 3.
if windows does not see it in any way ( nothing coming up in "devices" ) , assume you have a bad cable , bad port , or a security block . ( or worse case, a defective usb port on your NP )
bkdg100 said:
if windows does not see it in any way ( nothing coming up in "devices" ) , assume you have a bad cable , bad port , or a security block . ( or worse case, a defective usb port on your NP )
Click to expand...
Click to collapse
Okay. I've tried different cables. USB otg works on it. I've tried all USB ports on my pc. I'll keep trying though. Thanks for helping me try to figure this out.
is the NP showing up under devices ?
eko3484 said:
Okay. I've tried different cables. USB otg works on it. I've tried all USB ports on my pc. I'll keep trying though. Thanks for helping me try to figure this out.
Click to expand...
Click to collapse
If your cables work with your phone on the same usb port, it's probably just misconfigured drivers (very likely) or a bad NP (unlikely).
Go in to your control panel/device manager with the NP plugged in and see if you can find it. If it is under unknown, right click and install driver. If it is there, double click it and select the driver tab then "update driver" button. You can get the correct drivers here:
http://developer.android.com/sdk/win-usb.html
Select "browse my computer" and find wherever you extracted the above drivers, then let it install. Hopefully that'll fix things up for you... if not, you'll have to uninstall the existing drivers and reinstall them. Good luck.
Not at the house right now but I'll try all of this when I can. Thanks.
Related
Nexus 7 is rooted and unlocked.
stupidly hit OK to OTA update, even though clockwork recovery was flashed. Didn't work out so well.
So now there no USB support. Doesn't show up in device manager, doesn't work with fastboot/adb.
Not sure how I can fix this. It seems like the best solution would be to flash a factory image, but I can't without fastboot.
I think maybe its an issue with the kernel, but I don't really know.
Tried searching for the last 3 hours, can't find anything.
Any ideas?
Thanks
After researching more, and trying all sorts of things, I'm starting to think its a problem with the boot loader.
Still same problem, with no usb being recognized anywhere, not sure how to proceed.
Any suggestions greatly appreciated.
Same problem here, did you find a solution?
mine shows in Fastboot mode but not ADB mode....same kinda problem maybe??
have you tried a different usb cable? or if it works with another computer?
Think I might have solved my problem... have you checked USB Debugging is enabled on the tablet?
Mine wasn't and therefore ADB didn't see the device....
I know there are those who advocate manual steps but I just used one of the tool kits to solve this. But my tab was still being recognized by my computer so it was pretty easy. Just flashed root and Recovery in one step.
Sent from my Nexus 7 using xda premium
I cant´t get any USB Connection, even not reinstall the driver, because the Nexus is not shown in the Device Manager.
I tested different Cables on different PCs with no luck.
But OTG with stickmount still works, so i think it can´t be the USB-Port that´s damaged und must be some Software error.
I just flashed the Paranoiddroid in hope that it changes anything, but it did not.
ADB not working, no connection too.
TVeil said:
I cant´t get any USB Connection, even not reinstall the driver, because the Nexus is not shown in the Device Manager.
I tested different Cables on different PCs with no luck.
But OTG with stickmount still works, so i think it can´t be the USB-Port that´s damaged und must be some Software error.
I just flashed the Paranoiddroid in hope that it changes anything, but it did not.
ADB not working, no connection too.
Click to expand...
Click to collapse
Try going into Settings > Developer Options
Make sure USB Debugging is ticked.
Worked for me....
I think your misunderstanding the ops situation.
USB debugging will not help because when he is plugging in, its not been recognized as a device has been plugged in
Even with debugging disabled your PC will detect when you plug it in
Sent from my Nexus 7 using xda app-developers app
taffypride said:
Try going into Settings > Developer Options
Make sure USB Debugging is ticked.
Worked for me....
Click to expand...
Click to collapse
Thank you, but i tried that several times, in different USB-modes too...
bagofcrap24 is right, no recognition at all.
I think i will flash the device back to stock, remove CWM, unroot, lock the bootloader etc., hope that this will change the situation.
The problem is, that there is no USB-Connection at all even in fastboot mode.
Does anyone know if it´s possible to Is it possible to flash a Factory Image with fastboot with ADB over TCP/WIFI ?
bagofcrap24 said:
I think your misunderstanding the ops situation.
USB debugging will not help because when he is plugging in, its not been recognized as a device has been plugged in
Even with debugging disabled your PC will detect when you plug it in
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Just speaking from my own experience....
With USB Debugging set to on, ADB recognises the device as does the Device Manager.
With USB Debugging set to Off, ADB doesn't see the device and neither does the Device Manager.
Only other thing I can think to do is to try a different USB lead and failing that, reinstall the Android SDK/Drivers
taffypride said:
Just speaking from my own experience....
With USB Debugging set to on, ADB recognises the device as does the Device Manager.
With USB Debugging set to Off, ADB doesn't see the device and neither does the Device Manager.
Only other thing I can think to do is to try a different USB lead and failing that, reinstall the Android SDK/Drivers
Click to expand...
Click to collapse
Device Managed Should See your device regardless of weather it has debugging on or not.
please see the attached images to verify
With USB-Debugging On
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
With USB Debugging OFF
As you can see the Nexus 7 is still listed as a portable device regardless of weather debuggin is on or off
the only difference is that with USB debugging off the ADB interface will not work
The only thing i can suggest to the OP is to try a Live Linux CD and pray that you can get it to recognize it in there, if you can then it is possible that you can reflash a completely stock image & bootloader
My Nexus is not recognized by Linux too.
So the problem is not the driver, it´s the tablet´s system.
Does anybody know if it´s possible to flash a factory-image with adb via wifi?
TVeil said:
Thank you, but i tried that several times, in different USB-modes too...
bagofcrap24 is right, no recognition at all.
I think i will flash the device back to stock, remove CWM, unroot, lock the bootloader etc., hope that this will change the situation.
The problem is, that there is no USB-Connection at all even in fastboot mode.
Does anyone know if it´s possible to Is it possible to flash a Factory Image with fastboot with ADB over TCP/WIFI ?
Click to expand...
Click to collapse
Fastboot and adb are two different things and the device is identifying itself with different ids when connected to the PC. Adb over TCP/WIFI is possible (see http://anddisa.blogspot.de/2012/10/remote-debugging-over-tcpip.html, fastboot not.
Sent from my Nexus 7 using xda app-developers app
---------- Post added at 08:55 PM ---------- Previous post was at 08:52 PM ----------
TVeil said:
My Nexus is not recognized by Linux too.
So the problem is not the driver, it´s the tablet´s system.
Does anybody know if it´s possible to flash a factory-image with adb via wifi?
Click to expand...
Click to collapse
You need to add the correct dbus-rules. Have a look at http://anddisa.blogspot.de/2012/10/nexus-7-mtp-automount-on-opensuse-114.html where you can extract the rule-devs you need.
Sent from my Nexus 7 using xda app-developers app
AndDiSa said:
Fastboot and adb are two different things and the device is identifying itself with different ids when connected to the PC. Adb over TCP/WIFI is possible (see http://anddisa.blogspot.de/2012/10/remote-debugging-over-tcpip.html, fastboot not.
Click to expand...
Click to collapse
Got it, thank you. So it´s not possible to flash the Stock image via WIFI - it´s necessary to be in fastboot-mode to do that? Or is there a way to activate the adb-WIFI-Connection in the fastboot-mode?
Is it possible to flash the Factory Image with the Clockwork-Recovery from SD-Card?
Or is there any other way to get back to stock without the need of an USB-Connection?
What version is our boot loader, did ota update also update this? If not you could try to flash this. You can download it from a thread in android dev section of the forum.
Sent from my Nexus 7 using xda app-developers app
My Bootloader Version Number is 3.34, is there a version you can recommend?
-and is it a simple zip-install with clockwork recovery?
The newest boot loader that goes with android 4.1.2 is version 3.41. It is a cwm flash able zip called JZ054K boot loader which you can find in the android (not original) development section of the nexus 7 xda forum. The thread is called [boot loader] JZ054K, or something. Sorry can't post links yet.
Good luck, hope this solves your USB issue.
Sent from my Nexus 7 using xda app-developers app
Thank you very much! I´ll give that a try after work.
For some reason the i cant see the phone connected to the computer, i tried everything i saw in forums, am almost sure that is a hardware issue but i already unlocked the bootloader and void the warranty.
when i connect the phone to the computer the phone charges, in the computer nothing happends, when i connect the phone to wall charges slow like it was connected in usb port, i tried in several OS (XP,7,8). in all forums they mention utilities that works with the computer to relock, but thats not an option for me...
(sorry if i made mistakes, english is not my main language,)
[Toolkit] Wug's Nexus Root Toolkit v1.6.3 [Updated 02/24/13]: Nexus 4 Thread. Read this thread posted in Nexus 4 Original Android Development. Should be on the 2nd page of the thread. Very easy to use and will download necessary drivers.
Buddy3927 said:
[Toolkit] Wug's Nexus Root Toolkit v1.6.3 [Updated 02/24/13]: Nexus 4 Thread. Read this thread posted in Nexus 4 Original Android Development. Should be on the 2nd page of the thread. Very easy to use and will download necessary drivers.
Click to expand...
Click to collapse
The program does not recognize the phone either.
h4r0ld said:
The program does not recognize the phone either.
Click to expand...
Click to collapse
Did you follow the guide within the toolkit to download and install the drivers?
Sent from my Nexus 4 using xda premium
h4r0ld said:
For some reason the i cant see the phone connected to the computer, i tried everything i saw in forums, am almost sure that is a hardware issue but i already unlocked the bootloader and void the warranty.
when i connect the phone to the computer the phone charges, in the computer nothing happends, when i connect the phone to wall charges slow like it was connected in usb port, i tried in several OS (XP,7,8). in all forums they mention utilities that works with the computer to relock, but thats not an option for me...
(sorry if i made mistakes, english is not my main language,)
Click to expand...
Click to collapse
do you have usb debugging turned on in developer options?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
simms22 said:
do you have usb debugging turned on in developer options?
I tried with usb debugging turned on and off, got the same results, i think is a hardware problem, thas why i want to relock the bootloader to claim warranty.
Click to expand...
Click to collapse
h4r0ld said:
I tried with usb debugging turned on and off, got the same results, i think is a hardware problem, thas why i want to relock the bootloader to claim warranty.
Click to expand...
Click to collapse
i dont see how that can be a hardware problem. i bet you its something on your end, like the right drivers not being installed.
simms22 said:
h4r0ld said:
i dont see how that can be a hardware problem. i bet you its something on your end, like the right drivers not being installed.
Click to expand...
Click to collapse
The cellphones not even appears in the device manager of windows, i even tried with linux and nothing happends
Click to expand...
Click to collapse
h4r0ld said:
The cellphones not even appears in the device manager of windows, i even tried with linux and nothing happends
Click to expand...
Click to collapse
In windows it can show up under various device groups depending on how your cpu feels, check them all. On Linux (at least in Ubuntu) you can only access it via fastboot and adb unless you modify some files in addition to the usb rules for your phone.
The one and only time I've had my N4 connected to my computer was to root it. I did notice I had to wiggle the USB cable while plugged in to get a connection. Try that. It worked for me.
Sent from my Nexus 4 using xda premium
Use a high quality USB cord.
Plug it into a good USB port.
Try a different computer.
Uninstall drivers and install drivers and then restart phone and computer.
Put phone into debugging mode.
Viola.
jdcream123 said:
The one and only time I've had my N4 connected to my computer was to root it. I did notice I had to wiggle the USB cable while plugged in to get a connection. Try that. It worked for me.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
meanwhile... cant do anything yer
jdcream123 said:
The one and only time I've had my N4 connected to my computer was to root it. I did notice I had to wiggle the USB cable while plugged in to get a connection. Try that. It worked for me.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
I think ill sell the phone, nothing works!!!
h4r0ld said:
I think ill sell the phone, nothing works!!!
Click to expand...
Click to collapse
I just had my phone repaired under warranty by LG due to a bad USB daughterboard. The phone would charge no problem off of any USB port and with any cable, but it wouldn't sense data at all.
I tried stock, modified, manually set fastcharge off, and I did it on a computer that was originally working with the N4 as I rooted it from there.
Call them, they know of the issue. It was free for me, even though they said because I bought it used, it would cost $40-$100 to repair.
Hello
My phone: LG E400
rom: SDmerge+ miniCM (not sure if the problem is connected with that as everything was fine at the beginning)
All of a sudden my phone didn't show usb connection any more. No connection is shown in the phone or PC, but the phone is charging.
I tried all usb connection options, usb debugging on/off, no result.
Uninstalled all phone drivers in my PC and reinstalled LG driver, nothing.
Tried another usb cable and another PC, the same problem.
Also tried turning off my phone while connected, no help.
Please help me.
Don't know if it helps but I once saw a strange message in Titanium backup while usb was connected (this was after the problem started, so no usb connection was shown, usb debugging was on). It only happened once, so I'm not 100% sure what it said but it was sth about that I should turn on usb debugging.
Bosskardo said:
Hello
My phone: LG E400
rom: SDmerge+ miniCM (not sure if the problem is connected with that as everything was fine at the beginning)
All of a sudden my phone didn't show usb connection any more. No connection is shown in the phone or PC, but the phone is charging.
I tried all usb connection options, usb debugging on/off, no result.
Uninstalled all phone drivers in my PC and reinstalled LG driver, nothing.
Tried another usb cable and another PC, the same problem.
Also tried turning off my phone while connected, no help.
Please help me.
Don't know if it helps but I once saw a strange message in Titanium backup while usb was connected (this was after the problem started, so no usb connection was shown, usb debugging was on). It only happened once, so I'm not 100% sure what it said but it was sth about that I should turn on usb debugging.
Click to expand...
Click to collapse
message is fine thats mode for special apps to control phone from pc or when using adb
there is a program to see if phone fully not detected "Advanced USB Port Monitor" it will show all the requests to usb
seems like you need a flash because usbmanager is part of system and i'm not sure if possible to reinstall
wait a little if not in rush maybe someone else can help @slipsystem @AwesomeSMS
IGGYVIP said:
message is fine thats mode for special apps to control phone from pc or when using adb
there is a program to see if phone fully not detected "Advanced USB Port Monitor" it will show all the requests to usb
seems like you need a flash because usbmanager is part of system and i'm not sure if possible to reinstall
wait a little if not in rush maybe someone else can help @slipsystem @AwesomeSMS
Click to expand...
Click to collapse
I did format and flashed rom again but it didn't solve it. Does this mean its a hardware issue for sure?
Bosskardo said:
I did format and flashed rom again but it didn't solve it. Does this mean its a hardware issue for sure?
Click to expand...
Click to collapse
can you access phone using adb ?
how did you flash ?
IGGYVIP said:
can you access phone using adb ?
how did you flash ?
Click to expand...
Click to collapse
No, phone doesn't show up as adb device
I copied rom files to sd card and flashed from recovery.
Bosskardo said:
No, phone doesn't show up as adb device
I copied rom files to sd card and flashed from recovery.
Click to expand...
Click to collapse
TRY THIS http://forum.xda-developers.com/showthread.php?t=2660144
did you try to access phone using adb in recovery mode ? (not cwm !) does it recognise phone in lgmobile support tool whire in recovery mode
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
?
if you can then try to recovery mode flash new stock firmware
if not leave it because if anything happens to your cwm you will be stuck until you get usb port/controller (i think controller) repaired (yes its most likely hardware damage)
you could also ask if anyone will provide you with .img partition dumps and then adb wifi sideload them (HARD AND DANGEROUS)
IGGYVIP said:
TRY THIS http://forum.xda-developers.com/showthread.php?t=2660144
did you try to access phone using adb in recovery mode ? (not cwm !) does it recognise phone in lgmobile support tool whire in recovery mode
?
if you can then try to recovery mode flash new stock firmware
if not leave it because if anything happens to your cwm you will be stuck until you get usb port/controller (i think controller) repaired (yes its most likely hardware damage)
you could also ask if anyone will provide you with .img partition dumps and then adb wifi sideload them (HARD AND DANGEROUS)
Click to expand...
Click to collapse
No, LG support tool doesn't recognize it. I gave up on usb, just been using bt and wifi transfer (not the best solutions but at least I can transfer data).
But sth happened a few days ago. I plugged it in to my laptop for charging and suddenly it connected. It showed as device in the computer. But then I looked at my phone, it was connected as media device. I don't know why but I changed the connection to usb storage straigth away and lost the connection. Changing back to media device and replugging doesn't connect any more, it still charges.
What could that be about?
Bosskardo said:
No, LG support tool doesn't recognize it. I gave up on usb, just been using bt and wifi transfer (not the best solutions but at least I can transfer data).
But sth happened a few days ago. I plugged it in to my laptop for charging and suddenly it connected. It showed as device in the computer. But then I looked at my phone, it was connected as media device. I don't know why but I changed the connection to usb storage straigth away and lost the connection. Changing back to media device and replugging doesn't connect any more, it still charges.
What could that be about?
Click to expand...
Click to collapse
Actually the problem is on your windows not on your phone.
george brown said:
Actally the problem is on your windows not on your phone.
Click to expand...
Click to collapse
I've tried it on another computer (Vista, mine is win7).
Bosskardo said:
I've tried it on another computer (Vista, mine is win7).
Click to expand...
Click to collapse
If the problem is not from your windows then try to reinstall your cusrom. Or try another cusrom.
Development of this project has ended, @ggow has accomplished tetherless boot!
*Disclaimer* I am not responsible to anything that happens to your device(s)
Fire Mobile Boot Helper
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Fire Mobile Boot Helper allows you to boot custom boot.imgs using another Android device. I assume most XDArs have their android device on them at all times. No more worrying about not being near a PC when you want to reboot or power of your Fire tablet. Right now this is in VERY EARLY stages. I just wanted to share with you what I have come up with so far. Expect to see this all evolved into scripts and even a front end application on your android device. I am using this to gauge interest of a 2 device "safe strap". Would you guys like a one click application that automates this (allows you to just connect a usb cable, click and select a rom let, let it do its magic?)
https://www.youtube.com/watch?v=7o-XLIXfsZ8
Prerequisites
1) A second rooted android device.
2) Terminal Emulator on second device
3) FireBootHelper_current_version.zip
4) OTG adapter and a USB cable
Install Fire Boot Helper on second device
1) Extract FireBootHelper2.zip
2) Run FireMobileBootHelperInstall.bat
3) Binaries and the beginning of the back end are now installed
How to boot custom images
1) Copy your device boot images to wherever you want on your second device
2) Connect your OTG adapter to your second device.
3) Connect your USB cable to the adapter.
4) Boot your Fire into Fastboot using power and volume up. (Or open terminal, su, adb reboot bootloader)
5) Now that your Fire is in Fastboot go back to your second device and open up terminal emulator.
6) Type the following commands
su
fastboot devices (Is your device there, if yes continue)
fastboot boot "/sdcard/location/boot.img"
7) You're now booted using your custom boot img!
If you'd like to see continued development of this let me know! Feel free to donate to support future development.
Thank you Root Junky for helping me with my wonky script.
Note as this grows into its own app it will be moved into another forum.
RESERVED
Update 11/15/15 New installer script installs the necessary binaries as well as prepares for the application back end. This is still super alpha until an application front end stops us from having to manually run commands.
11/16/15 Development has ended, @ggow has accomplished tetherless boot!
nice, will try when I get home
Sent from my XT907 using Tapatalk
Harry44 said:
Update 11/15/15 New installer script installs the necessary binaries as well as prepares for the application back end. This is still super alpha until an application front end stops us from having to manually run commands.
Click to expand...
Click to collapse
I ran the BAT on my Droid RAZR, which has external powered OTG capabilities successfully, but when I type in anything fastboot, it displays "sh: fastboot not found". Any sugestions?
EDIT: I forgot to turn on root permissions for ADB in Developer Options.
---------- Post added at 07:46 AM ---------- Previous post was at 07:04 AM ----------
Now, on my RAZR, it recognizes the Fire in Fastboot mode, but whenever I try to boot up the img, it gets stuck on < waiting for device >
Do you think it is device specific?
Vlasp said:
I ran the BAT on my Droid RAZR, which has external powered OTG capabilities successfully, but when I type in anything fastboot, it displays "sh: fastboot not found". Any sugestions?
EDIT: I forgot to turn on root permissions for ADB in Developer Options.
---------- Post added at 07:46 AM ---------- Previous post was at 07:04 AM ----------
Now, on my RAZR, it recognizes the Fire in Fastboot mode, but whenever I try to boot up the img, it gets stuck on < waiting for device >
Do you think it is device specific?
Click to expand...
Click to collapse
No shouldn't be device specific. Should work cross devices. The binaries were built for arm so it should work for you no issue.
Here are some tips:
-Make sure your RAZR is he host OTG device. Meaning the OTG adapter is plugged into it. Then the USB cable into the Fire. I did that with out realizing it and it didn't work.
-Make sure you're su.
-Reboot the fire into fastboot again.
These are all things I had experienced. If fastboot is up everything is installed correctly and executable. So you shouldn't have issues.
Let know if your issue persists.
Harry44 said:
No shouldn't be device specific. Should work cross devices. The binaries were built for arm so it should work for you no issue.
Here are some tips:
-Make sure your RAZR is he host OTG device. Meaning the OTG adapter is plugged into it. Then the USB cable into the Fire. I did that with out realizing it and it didn't work.
-Make sure you're su.
-Reboot the fire into fastboot again.
These are all things I had experienced. If fastboot is up everything is installed correctly and executable. So you shouldn't have issues.
Let know if your issue persists.
Click to expand...
Click to collapse
The earliest I will be able to test it again is in 7 hours so I will inform you then.
Sent from my XT912 using Tapatalk
Harry44 said:
No shouldn't be device specific. Should work cross devices. The binaries were built for arm so it should work for you no issue.
Here are some tips:
-Make sure your RAZR is he host OTG device. Meaning the OTG adapter is plugged into it. Then the USB cable into the Fire. I did that with out realizing it and it didn't work.
-Make sure you're su.
-Reboot the fire into fastboot again.
These are all things I had experienced. If fastboot is up everything is installed correctly and executable. So you shouldn't have issues.
Let know if your issue persists.
Click to expand...
Click to collapse
So what I did was I shut down my Fire, unplugged it, went to my phone and started terminal emulator and became root, and then I booted to fastboot on my Fire, plugged it in, did fastboot devices and the Fire came up, and lastly I did fastboot boot TWRPFire.img, with TWRPFire.img being on the root of my device's memory. It is stuck on < waiting for device >
I tried on another fastboot command, same problem.
Vlasp said:
So what I did was I shut down my Fire, unplugged it, went to my phone and started terminal emulator and became root, and then I booted to fastboot on my Fire, plugged it in, did fastboot devices and the Fire came up, and lastly I did fastboot boot TWRPFire.img, with TWRPFire.img being on the root of my device's memory. It is stuck on < waiting for device >
I tried on another fastboot command, same problem.
Click to expand...
Click to collapse
Very odd, I have been able to try this on several devices and it hasn't had an issue. I'll recompile the latest binaries for arm and will post back.
Edit, Is this a powered OTG Y adapter?
Harry44 said:
Very odd, I have been able to try this on several devices and it hasn't had an issue. I'll recompile the latest binaries for arm and will post back.
Edit, Is this a powered OTG Y adapter?
Click to expand...
Click to collapse
Yep, it is a homemade Y adapter made of 2 USB Extenders, I cut off one of the female ends and cut off the data lines on the extra male end, so that it is a regular extension cable, but with another power wire. I connect the OTG cable to the Male end with the data lines still intact, and I plug in the Fire to the female end.
Vlasp said:
Yep, it is a homemade Y adapter made of 2 USB Extenders, I cut off one of the female ends and cut off the data lines on the extra male end, so that it is a regular extension cable, but with another power wire. I connect the OTG cable to the Male end with the data lines still intact, and I plug in the Fire to the female end.
Click to expand...
Click to collapse
That may be it. Mine refuses to work with my Y adapter thats why I asked. Just a thought though.
This still could be useful to unbrick without a pc/computer
the stock firmware can be installed in twrp
Unbrick/Restore Stock 2015 Amazon Fire (KFFOWI/Ford) with custom recovery
Hey everyone,
I just got my 6P and am attempting to unlock the bootloader, but I'm running into an issue with Fastboot. I have all necessary drivers installed on my computer (running Windows 10), I've enabled OEM unlocking and USB debugging on my phone, and ADB works perfectly fine. The problem is that once I reboot to Fastboot, the phone displays "connect USB data cable" even though the cable is plugged in and it works fine for ADB functions. I can't get the computer to recognize the phone in Fastboot no matter what I do. Any thoughts?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
EDIT: I tried the exact same process with my 5X and had no such issues. I'm kind of baffled by this.
maxpower7 said:
Hey everyone,
I just got my 6P and am attempting to unlock the bootloader, but I'm running into an issue with Fastboot. I have all necessary drivers installed on my computer (running Windows 10), I've enabled OEM unlocking and USB debugging on my phone, and ADB works perfectly fine. The problem is that once I reboot to Fastboot, the phone displays "connect USB data cable" even though the cable is plugged in and it works fine for ADB functions. I can't get the computer to recognize the phone in Fastboot no matter what I do. Any thoughts?
EDIT: I tried the exact same process with my 5X and had no such issues. I'm kind of baffled by this.
Click to expand...
Click to collapse
Try updating Android SDK. I have the connect USB data cable thing but doesn't affect it [emoji14]
Sent from my Nexus 6P using Tapatalk
JustPlayingHard said:
Try updating Android SDK. I have the connect USB data cable thing but doesn't affect it [emoji14]
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Yeah, I updated the SDK. I also uninstalled and reinstalled the Google USB drivers to no avail. Thanks anyway though!
Sent from my Nexus 6P using Tapatalk
maxpower7 said:
Yeah, I updated the SDK. I also uninstalled and reinstalled the Google USB drivers to no avail. Thanks anyway though!
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Oh. That's weird. I would say try another cable but it's TYPE c and not many people have more than one TYPE C cables at the moment.
maxpower7 said:
Yeah, I updated the SDK. I also uninstalled and reinstalled the Google USB drivers to no avail. Thanks anyway though!
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
First off, try switching ports. If that doesn't work, go to Control Panel > Device Manager, and see if there's anything wrong.