Hello,
I bricked my phone doing something quite silly... upgrading to stock firmware using OTA from custom ROM. Yes, I used to be an Iphone user, and with Iphones, a recovery would make the phone stock, no matter what state it was in previously.
Anyways, my HTC One Google play edition now has no OS, and no recovery available. I am also unable to use ADB commands to connect to the phone from my Windows 7 PC. However, if I load up my Linux CENTOS through Vmware (VMplayer), the OS recognizes the phone.
Can anyone provide details on the next steps? I don't care what version OS (stock or custom) the phone is fixed to, I just want to fix it and be able to use it again.
On a side note, I am willing to pay $100 USD (via paypal gift), to whoever can guide me through the process successfully. I can also provide remote desktop connection via Teamviewer or Cisco WebEx, if you prefer to just work on it remotely.
Thanks!
J
ca12bon said:
I am ... unable to use ADB commands to connect to the phone from my Windows 7 PC.
...I am willing to pay $100 USD (via paypal gift), to whoever can guide me through the process successfully.
Click to expand...
Click to collapse
You can keep the $100, just see if you can run fastboot getvar all and post the results here and I'm sure plenty of folks will be happy to chime in for free.
If you got adb working on windows 7, presumably you have a working install of the latest android SDK. Also you say you can get into HBOOT.
If so, you're not completely "bricked".
You should still be able to run some fastboot commands. That will be your way out.
Just to spell this out, connect the phone to your PC, boot into the bootloader, select fastboot (on the phone) and try running some of the fastboot commands (from a terminal window in the PC). Start with 'fastboot devices' to see if you are even talking. If your phone's serial number appears, proceed to 'fastboot getvar all' and post the results (edit out your imei and serial number) here.
You can do a lot from fastboot, such as flashing a fresh recovery or even an RUU.
"Brick" is a pretty extreme state. You're not bricked.
Sent from my HTC One using xda app-developers app
NxNW said:
You can keep the $100, just see if you can run fastboot getvar all and post the results here and I'm sure plenty of folks will be happy to chime in for free.
If you got adb working on windows 7, presumably you have a working install of the latest android SDK. Also you say you can get into HBOOT.
If so, you're not completely "bricked".
You should still be able to run some fastboot commands. That will be your way out.
Just to spell this out, connect the phone to your PC, boot into the bootloader, select fastboot (on the phone) and try running some of the fastboot commands (from a terminal window in the PC). Start with 'fastboot devices' to see if you are even talking. If your phone's serial number appears, proceed to 'fastboot getvar all' and post the results (edit out your imei and serial number) here.
You can do a lot from fastboot, such as flashing a fresh recovery or even an RUU.
"Brick" is a pretty extreme state. You're not bricked.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Hey man,
Thanks for the help, really appreciate it. My Windows is unable to recognize the phone via ADB, so I cannot run any fastboot commands. I will go home tonight and try again for the exact readout, but I couldn't perform any commands whatsoever.
However, when using CENTOS (through vmware), the OS recognizes the phone:
[[email protected] Desktop]# lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
Bus 001 Device 003: ID 0bb4:0f91 HTC (High Tech Computer Corp.)
Screenshot of HBOOT:
{
"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"
}
My "main" problem, is I do not know how to get ADB/fastboot installed to my CENTOS mounted on Vmplayer. I think if I can use ADB and fastboot commands, I can push a custom recovery to my phone and install a working ROM.
Regards,
John
Ah, I see, yes it looks like getting the computer to recognize the phone is the main obstacle at this point.
Not an expert on Linux, but I did just run across this reminder about windows 7:
matanlevanon said:
Well, being able to fastboot is crucial... next time you can just install HTC Sync which will update your drivers and then un-install it.
Click to expand...
Click to collapse
Do you have the latest drivers from HTC?
Sent from my HTC One using xda app-developers app
@nkk71's guide has some commands for Ubuntu that may help
Look at step 5
http://forum.xda-developers.com/showthread.php?t=2541082
ca12bon said:
Hey man,
Thanks for the help, really appreciate it. My Windows is unable to recognize the phone via ADB, so I cannot run any fastboot commands. I will go home tonight and try again for the exact readout, but I couldn't perform any commands whatsoever.
However, when using CENTOS (through vmware), the OS recognizes the phone:
[[email protected] Desktop]# lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
Bus 001 Device 003: ID 0bb4:0f91 HTC (High Tech Computer Corp.)
Screenshot of HBOOT:
My "main" problem, is I do not know how to get ADB/fastboot installed to my CENTOS mounted on Vmplayer. I think if I can use ADB and fastboot commands, I can push a custom recovery to my phone and install a working ROM.
Regards,
John
Click to expand...
Click to collapse
Try this first:
1. install HTC Sync on your computer (this will install the latest drivers for you)
2. Create a folder in your C:\ drive naming it 'adb' or something like that.
4. Place the content of this folder (4 files) in your adb folder
5. when in bootloader hit "fastboot" (wait until all the drivers are installed on your PC, give it a good 5 min while the phone is connected and in fastboot mode) you should see at one point "fastboot usb" like in the attached photo:
6. if you don't see it, reboot your computer and try again.
7. your fastboot should work now, use the following guide to flash recovery (Section 3) and you can transfer your ROM and install it.
Use the $100 to buy your phone some nice accessories and remember me by them
I have often heard people recommend adding an additional step between 1) and 2) , let's call it step 1.a) uninstall the actual HTC Sync app (drivers will remain installed)
Is it still necessary?
Sent from my HTC One using xda app-developers app
ca12bon said:
Hello,
I bricked my phone doing something quite silly... upgrading to stock firmware using OTA from custom ROM. Yes, I used to be an Iphone user, and with Iphones, a recovery would make the phone stock, no matter what state it was in previously.
Anyways, my HTC One Google play edition now has no OS, and no recovery available. I am also unable to use ADB commands to connect to the phone from my Windows 7 PC. However, if I load up my Linux CENTOS through Vmware (VMplayer), the OS recognizes the phone.
Can anyone provide details on the next steps? I don't care what version OS (stock or custom) the phone is fixed to, I just want to fix it and be able to use it again.
On a side note, I am willing to pay $100 USD (via paypal gift), to whoever can guide me through the process successfully. I can also provide remote desktop connection via Teamviewer or Cisco WebEx, if you prefer to just work on it remotely.
Thanks!
J
Click to expand...
Click to collapse
uninstall all HTC drivers and software, then try these http://forum.xda-developers.com/showthread.php?t=2261088 drivers
Thanks very much for the input everyone, unfortunately I forgot to bring my phone to work today, I will try out all the suggestions at home tonight.
Hope you all have a great day
Okay I've tried all the methods posted above... but still having the same issue.
Although the phone had USB debugging mode enabled before I bricked it, not really sure if it's on now. Also, I read that I need to have S-OFF, but in order to do that, the phone needs to be recognized by the PC.
Anyone know how to install or download ADB to CENTOS Linux? (or any other Linux)? Since the Linux VMware OS recognizes the phone perfectly, I think that's my only chance at pushing a custom recovery and ROM to the phone.
Are you definitely in fastboot when you try to connect in windows? Also, make sure you disable any antivirus and windows firewall, as I have found them to cause connection issues.
HTC One, Unlocked, S-off, Super CID, ARHD ROM, ElementalX Kernel
Related
Universal Naked Driver 0.73
** Nvidia Shield ADB added (ADB & Fastboot Only)
** Will update with APX asap
Universal Naked Driver 0.72
** HTC One Added (HTC phones are pretty much future proof with my driver)
** Google Nexus 4 Added
** Google Nexus 10 Added
** Google Nexus Q Added
** Google Nexus S Added
32 & 64 Bit Windows 8 / 7 / Vista / XP - Attached to this post!
MD5: 5B9EA9C73066E8F655D14BBA8318C176
I am happy to release my Universal Naked Driver. This is to allow ADB, Fastboot & APX interfaces to work without installing any package much less multiples packages for users with multiple devices. Yes you can just install them and uninstall right away but why bother?
I was annoyed that I couldnt use my Transformer Prime and Galaxy Nexus without having versions and packages trip over each other. My previous post for the Sensation & Galaxy Nexus was helpful so I thought I would bring to XDA the newest Android driver available from source (which they call 4.0) and make it start talking.
Warning: Uninstall any previous driver package's you may have installed and also manually remove drivers by attaching your phone and going to Windows device manager and right click the entry for your phone and select "Uninstall" on the next prompt make sure to select "Delete the driver software for this device" then hit OK and reboot before installing these drivers
Code:
Google Nexus Devices ADB & Fastboot
Samsung Devices ADB & Fastboot
Asus Devices ADB, Fastboot & APX
HTC Devices ADB & Fastboot
Code:
[B]Windows 8 Instructions[/B]
How to Disable Driver Signature Enforcement in Windows 8:
From the Metro Start Screen, open Settings (move your mouse to the bottom-right-corner of the screen and wait for the pop-out bar to appear, then click the Gear icon).
Click ‘More PC Settings’.
Click ‘General’.
Scroll down, and click ‘Restart now’ under ‘Advanced startup’.
Wait a bit.
Click ‘Troubleshoot’.
Click ‘Advanced Options’
Click ‘Windows Startup Settings’
Click Restart.
Enjoy!
Thank you very much! I just used your drivers and successfully unlocked my bootloader on my Nvidia Shield!
jadengore said:
Thank you very much! I just used your drivers and successfully unlocked my bootloader on my Nvidia Shield!
Click to expand...
Click to collapse
You are welcome, glad to know it making things easier.
I will make an auto root batch job once a recovery is made for the device. Shouldn't be too long...
1wayjonny said:
You are welcome, glad to know it making things easier.
I will make an auto root batch job once a recovery is made for the device. Shouldn't be too long...
Click to expand...
Click to collapse
I used to have one (TWRP) but because touch will be much harder (or impossible) on this device, TWRP isn't a viable recovery for SHIELD. Instead, it looks like we'll need to use CWM, the dpad, and the A and B buttons.
agrabren said:
I used to have one (TWRP) but because touch will be much harder (or impossible) on this device, TWRP isn't a viable recovery for SHIELD. Instead, it looks like we'll need to use CWM, the dpad, and the A and B buttons.
Click to expand...
Click to collapse
What's wrong with the touchscreen on the device? Or did you not know it had a multitouch screen? (I can't imagine a modern Android implementation without one, ick)
AndrewNeo said:
What's wrong with the touchscreen on the device? Or did you not know it had a multitouch screen? (I can't imagine a modern Android implementation without one, ick)
Click to expand...
Click to collapse
Nothing is wrong with the touchscreen, but its awkward to use when you have the controller attached to the screen. I'm very scared about the modding community for this device. It looks like the streaming might be broken by custom roms. That being said, I really want to root and put a custom rom on mine. We'll have to see how popular it gets here in the community.
PR0XIDIAN said:
Nothing is wrong with the touchscreen, but its awkward to use when you have the controller attached to the screen. I'm very scared about the modding community for this device. It looks like the streaming might be broken by custom roms. That being said, I really want to root and put a custom rom on mine. We'll have to see how popular it gets here in the community.
Click to expand...
Click to collapse
The issue with the touchscreen is the driver. While it runs great in Android, it doesn't work in recovery, making a touch-based recovery a nightmare. Believe me, I already tried for a few days. I'm sure with enough time, I could get it working, but I didn't want to invest that much time with all the other things on my plate at the moment. I just don't expect recovery to come out this week with touch.
I made a very high quality tutorial (video) on how to do this! Thanks @1wayjonny!
http://www.youtube.com/watch?v=--6OlA4agPo
How To Unlock the Bootloader: http://www.youtube.com/watch?v=7Am5WYRojMs
How To Root the Nvidia Shield: http://www.youtube.com/watch?v=_4-C0CzKoFs
Fix Fastboot issues on Windows 8: http://www.youtube.com/watch?v=XSisjVwcPbE
wwjoshdew said:
I made a very high quality tutorial (video) on how to do this! Thanks @1wayjonny!
http://www.youtube.com/watch?v=--6OlA4agPo
Click to expand...
Click to collapse
Thanks for the video, I was testing something for Nvidia today and did 10 re-install without the SSD RAID 0 i have and it was killing me.
Once you have SSD you cant go back and yes daughters are LOUD! I have one ... =)
I will probably post the video in the OP of all my UNDriver threads.
1wayjonny said:
Thanks for the video, I was testing something for Nvidia today and did 10 re-install without the SSD RAID 0 i have and it was killing me.
Once you have SSD you cant go back and yes daughters are LOUD! I have one ... =)
I will probably post the video in the OP of all my UNDriver threads.
Click to expand...
Click to collapse
haha. She's a trip though. Thanks a lot dude, you don't see to many "screen captures" that show the computer rebooting and everything! lol
Ok I'm clearly doing something wrong. I need to reinstall the fastboot driver. I had it working properly before but need to install them on a different computer.
I plug the shield in and Windows auto installs a driver. The device is identified as the SHIELD but it's an adb driver (but doesn't allow me to send fastboot commands). When I try to update the driver it says it is up to date. If I uninstall that adb driver that gets auto installed by Windows and try to navigate to the universal driver folder and click one of the inf files in there windows says it isn't a compatible and to make sure it is for an x64 system. If I browse to the i386 folder nothing comes up. I'm really getting irritated.
Is there just a normal fastboot driver somewhere that isn't a universal driver? Typically if I have a correct driver and choose "Have Disk" and browse to my driver it will install, but not this time.
I am not sure if I have a previous driver conflicting or something. I don't have like 4 Android devices I used to have any more so uninstalling those drivers isn't possible. I just don't understand why Windows can be so difficult on something so trivial.
I'm using Windows 7.
Evo_Shift said:
Ok I'm clearly doing something wrong. I need to reinstall the fastboot driver. I had it working properly before but need to install them on a different computer.
I plug the shield in and Windows auto installs a driver. The device is identified as the SHIELD but it's an adb driver (but doesn't allow me to send fastboot commands). When I try to update the driver it says it is up to date. If I uninstall that adb driver that gets auto installed by Windows and try to navigate to the universal driver folder and click one of the inf files in there windows says it isn't a compatible and to make sure it is for an x64 system. If I browse to the i386 folder nothing comes up. I'm really getting irritated.
Is there just a normal fastboot driver somewhere that isn't a universal driver? Typically if I have a correct driver and choose "Have Disk" and browse to my driver it will install, but not this time.
I am not sure if I have a previous driver conflicting or something. I don't have like 4 Android devices I used to have any more so uninstalling those drivers isn't possible. I just don't understand why Windows can be so difficult on something so trivial.
I'm using Windows 7.
Click to expand...
Click to collapse
I had the SAME PROBLEM! I uninstalled the drivers, and chose from the list manually! Eventually you choose have disk and there is a long list of things. Find NVIDIA Fastboot from that list.
{
"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 swear I tried that. I think I may have unplugged my device and plugged it back in after uninstalling because I thought I couldn't find it in the device manager after I uninstalled it. I bet it was listed with a yellow exclamation point somewhere in there but I just skipped over it or something.
I wish my work computer didn't lock me out of everything so I didn't have to wait to get home to try it again...
And off topic...I wish I got those kind of speeds in your sig on Sprint. My LTE (Galaxy S3) is hardly faster than 3G in Minneapolis. Though it isn't officially launched yet.
Evo_Shift said:
I swear I tried that. I think I may have unplugged my device and plugged it back in after uninstalling because I thought I couldn't find it in the device manager after I uninstalled it. I bet it was listed with a yellow exclamation point somewhere in there but I just skipped over it or something.
I wish my work computer didn't lock me out of everything so I didn't have to wait to get home to try it again...
And off topic...I wish I got those kind of speeds in your sig on Sprint. My LTE (Galaxy S3) is hardly faster than 3G in Minneapolis. Though it isn't officially launched yet.
Click to expand...
Click to collapse
HERE YOU GO @Evo_Shift! (And others having trouble running fastboot commands on their NVIDIA Shield!)
http://www.youtube.com/watch?v=XSisjVwcPbE
@1wayjonny, (and @agrabren) what do you think?
wwjoshdew said:
HERE YOU GO @Evo_Shift! (And others having trouble running fastboot commands on their NVIDIA Shield!)
http://www.youtube.com/watch?v=XSisjVwcPbE
@1wayjonny, (and @agrabren) what do you think?
Click to expand...
Click to collapse
I have seen this many times if the driver is correct and user is having issues its usually because of the following.
A) Cable is not good, try changing a few cable and all should be well. I have even seen OEM cables give issues with fastboot for some reason on multiple devices.
B) User is trying to use a USB 3.0 port, you can replace the microsoft stack with the intel stack allowing for communication over USB 3.0 - Some other USB 3.0 chipset may have issues as well such as Astek etc.
Its important to remember that not all cables are pinned out the same. For example the Xbox 360 FREE ethernet cable only was 100mbps because they choose to save the money by only using 4 of the 8 available wires to reduce cost.
** UPDATE **
After watching the video it seems like you are forcing the driver which is OK. The driver 0.73 will pick up the shield in adb or fastboot automatically.
If its not the devices is not registering to the computer correct and I would check the cable and avoid USB 3.0 port until you work this out.
Was this a USB 3.0 port? If no go right for the cable and try 3-5 different cables.
I finally got it. I am pretty sure it is because of incorrect adb drivers getting auto installed on me when I plugged in the Shield. I wish you could force Windows not to autoinstall drivers when you plug something in and instead always choose your own location. Once I deleted enough of the incorrect drivers and installed the correct drivers to the SHield again it seems to work.
1wayjonny said:
I have seen this many times if the driver is correct and user is having issues its usually because of the following.
A) Cable is not good, try changing a few cable and all should be well. I have even seen OEM cables give issues with fastboot for some reason on multiple devices.
B) User is trying to use a USB 3.0 port, you can replace the microsoft stack with the intel stack allowing for communication over USB 3.0 - Some other USB 3.0 chipset may have issues as well such as Astek etc.
Its important to remember that not all cables are pinned out the same. For example the Xbox 360 FREE ethernet cable only was 100mbps because they choose to save the money by only using 4 of the 8 available wires to reduce cost.
** UPDATE **
After watching the video it seems like you are forcing the driver which is OK. The driver 0.73 will pick up the shield in adb or fastboot automatically.
If its not the devices is not registering to the computer correct and I would check the cable and avoid USB 3.0 port until you work this out.
Was this a USB 3.0 port? If no go right for the cable and try 3-5 different cables.
Click to expand...
Click to collapse
Nope. A USB 2.0 port. That first video that I made (That you said "I will probably post the video in the OP of all my UNDriver threads."), did it correctly. But for some reason, it would work JUST FINE in ADB mode, but NOT in fastboot. I couldn't get "fastboot oem unlock" to work for the life of me, until forcing it to install after choosing "have disk". After that, it worked fine. Just showing that "manual" method for people that have their Shield working find while in android, but not in fastboot. I'm not saying anyone sole person is responsible for it not working, just showing a manual way around it.
hmm...
I have only "Nvidia Shield" not Nvida Shield ADB in my devices Manager - adb is enabled
Code:
adb devies
List of devices attached
(none)
wwjoshdew said:
Nope. A USB 2.0 port. That first video that I made (That you said "I will probably post the video in the OP of all my UNDriver threads."), did it correctly. But for some reason, it would work JUST FINE in ADB mode, but NOT in fastboot. I couldn't get "fastboot oem unlock" to work for the life of me, until forcing it to install after choosing "have disk". After that, it worked fine. Just showing that "manual" method for people that have their Shield working find while in android, but not in fastboot. I'm not saying anyone sole person is responsible for it not working, just showing a manual way around it.
Click to expand...
Click to collapse
Had this issues so I installed the "manual" way and still commands wont work in fastboot
Edit: followed the video as opposed to the sceenshots above. Good to go now.
1wayjonny said:
Universal Naked Driver 0.73
** Nvidia Shield ADB added (ADB & Fastboot Only)
** Will update with APX asap
Click to expand...
Click to collapse
Is APX mode available on NVIDIA Shield? I've used APX mode before on my Notion Ink Adam (Tegra 2), but I have read that the OUYA (Tegra 3) has APX mode encrypted or something so you would have to know the key to use it.
Would be nice to have APX mode on the Shield, but probably not necessary.
~Troop
Hey there everyone,
Android newbie here.
Just wanted to start off assuring everyone that I've been scouring the internet for answers.
I've been using the following links.
http://forum.xda-developers.com/showthread.php?t=2322220
[Q] Device not found on ADB | TWRP Sideload and CWM mount problems
http://forum.xda-developers.com/showthread.php?t=2345877
help wiped phone and sdcard cant sideload
http://forum.xda-developers.com/showthread.php?t=2325853
[GUIDE] How to ADB Push to fix a formatted /sdcard (Mac + PC)
I'm on a Mac and have an HTC One of course.
At the moment, whenever I switch on the phone it automatically takes me to the TWRP screen.
It looks like there is no system as I cannot boot into the original stock rom (I never installed a customer rom but did have the Kernel which enabled the HTC logo to be functional).
My goal is to get a ROM onto the phone so that I can install it (don't care if the phone is completely wiped).
Issue is that my Mac doesn't detect the phone when plugged in via USB. Neither via the HTC Sync Manager or by Android File Transfer Apps.
When in TWRP, I went to Advance then ADB Sideload. All I get is a the message ADP Sideload Complete Failed.
So the advice was to ADB Push the file onto the phone.
After downloading the Android SDK, extracted everything to desktop, went into the folder called tools, double clicked on the file called Android, made sure that I ticked the right boxes, it downloaded some stuff and then closed the window.
I then opened up terminal and typed in cd Desktop/platform-tools
./adb devices
I get the message saying Daemon started successfully and List of Devices attached (however there are no devices listed).
(At this point I've got the USB cable plugged into the HTC One and it's on the TWRP screen.
I really don't know what to do.
Could someone please help?
Are you using usb port 3.0?
However, boot in fastboot and see if the
Code:
fastboot devices
command work
I'm sorry but I have no clue where you mean I should type in that command.
I've now clicked on reboot in TWRP then it is in the fastboot screen (white screen, with bunch of text and the word fastboot highlighted in red).
I plugged in the USB cable to my mac, open up terminal and typed in.
./adb devices
then
./adb fastboot devices (assuming that's what you had meant) and it did nothing except for load up a screen with commands see attached.
You have only to write:
Code:
./fastboot devices
without adb
hey there,
I typed in cd Desktop/platform-tools
then
./fastboot devices
However it did nothing.
So I typed in
./adb devices after that
And I still get nothing.
Kei$ cd desktop/platform-tools
platform-tools Kei$ ./fastboot devices
platform-tools Kei$ ./adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
platform-tools Kei$
Seems you don't have fastboot into the folder.
However, have you checked that you aren't using a usb 3.0 port?
And driver of phone are installed?
just in case this helps.
When you run the fastboot command, on your phone, what screen are you on. Is it the recovery (twrp) or bootloader?
Also make sure only the phone is connected via usb and nothing else if you have the MacBook air
Sent from my HTC One using xda app-developers app
amnesia said:
just in case this helps.
Click to expand...
Click to collapse
Umh, you're s-on, i will advice you to go to s-off when you've restored it.
akuma24 said:
When you run the fastboot command, on your phone, what screen are you on. Is it the recovery (twrp) or bootloader?
Also make sure only the phone is connected via usb and nothing else if you have the MacBook air
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Yeah, seems he was in recovery, when he have to use the fastboot command in fastboot...
within platform-tools folder I have the following files
adb
api
fastbood
notice.tx
source.properties
systrace
-------
I've installed the HTC Sync (which should install the drivers needed as all threads say)
My iMac is a mid 2010 version and uses USB 2.0 for all four ports.
amnesia said:
within platform-tools folder I have the following files
adb
api
fastbood
notice.tx
source.properties
systrace
-------
I've installed the HTC Sync (which should install the drivers needed as all threads say)
My iMac is a mid 2010 version and uses USB 2.0 for all four ports.
Click to expand...
Click to collapse
So, now, unistall HTC Sync, boot in fastboot and use the command:
Code:
./fastboot devices
after move to the directory.
I had a similar problem last evening, however I am operating on Windows 8.1, thank goodness for dual boot as I had to use Win7 as 8.1 would not recognize adb interface.
However, once in twrp recovery,just the main screen you should be able to use :
adb devices
and it should list your device:
xxxdevicexxx recovery
if so then you use
adb push rom.zip (i tend to rename them to make this easier) /data/media/0
took about 12 minutes for the rom to be placed, then I did an install, I had to do it twice before it took, but after that I was good to go
When in the bootloader, does it say fastboot usb?
Sent from my HTC One using xda app-developers app
Guich said:
So, now, unistall HTC Sync, boot in fastboot and use the command:
Code:
./fastboot devices
after move to the directory.
Click to expand...
Click to collapse
Alright so I uninstalled HTC Sync Manager (Dragging and dropping it to the recycle bin then using Clean My Mac to uninstall it).
Then in terminal I typed in
./fastboot devices
platform-tools Kei$ ./fastboot devices
There was no response at all from the terminal.
Let me know if you would like me to take a video of exactly what I'm doing.
I'm confident that I'm following instructions perfectly.
akuma24 said:
When in the bootloader, does it say fastboot usb?
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Here is a closer image of what I see.
amnesia said:
Alright so I uninstalled HTC Sync Manager (Dragging and dropping it to the recycle bin then using Clean My Mac to uninstall it).
Then in terminal I typed in
./fastboot devices
platform-tools Kei$ ./fastboot devices
There was no response at all from the terminal.
Let me know if you would like me to take a video of exactly what I'm doing.
I'm confident that I'm following instructions perfectly.
Click to expand...
Click to collapse
I don't have a mac, but the command will work like this:
{
"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"
}
So, try to use another cable.
amnesia said:
Here is a closer image of what I see.
Click to expand...
Click to collapse
Your phone isn't connected to the PC.
So, try to use another cable.
Which Mac os are you on and how many usb calls do you have plugged in ?
Sent from my HTC One using xda app-developers app
Oh no, don't say that! I've got windows 8 on my mac (via VMWare fusion) and was going to try that...
I'm on Mac OSX 10.8.4
I have two out of the 4 USB ports plugged in (one is the phone) the other is the printer.
I just went through 3 usb cables and finally the Fastboot screen says
Fastboot USB ! Guess the first two weren't good enough, they were charging the phone though.
I then went into terminal and typed in
./fastboot devices
and now it says
<serial number> fastboot
What's next boss ? What do I type.
Super noob here. I was trying to update my android revolution hd rom and somehow I screwed everything.
Do I have a chance to fix my phone or should I purchase a new one?
My unit is a HTC One m7 (sprint).
I understand that in order to fix this I need to install a new recovery (I have a CWM old version). The phone reboots in regular mode but as ROM is not working it reboots to recovery, but this doesn't work either I just see a 0,5s splash screen and the loop goes on.
I have read the "disaster recovery" thread but they assume Fastboot USB works. My problem is I dont even know how to connect my phone to my computer in order to work from there.
My bootloader is still unlocked (fortunately).
I have Hboot 1.44 should I update it?
A step-by-step dumb proof will be appreciated!
First download a toolkit for the HTC one m7. You can find it in the android development section. With that you can install a new recovery. I recommend twrp. After that push a ROM via adb to the device and flash that Rom. There are hundreds of sprint ROMs and even more threads "how to adb push"
http://forum.xda-developers.com/showthread.php?t=2265618
[GUIDE] Complete Flashing Guide | Rooting | Going Back To Stock | 05.05.2013
Philipp_94 said:
First download a toolkit for the HTC one m7. You can find it in the android development section. With that you can install a new recovery. I recommend twrp. After that push a ROM via adb to the device and flash that Rom. There are hundreds of sprint ROMs and even more threads "how to adb push"
http://forum.xda-developers.com/showthread.php?t=2265618
[GUIDE] Complete Flashing Guide | Rooting | Going Back To Stock | 05.05.2013
Click to expand...
Click to collapse
Thanks, downloaded this tool seems great, but my phone is not getting recognized by the system. Im using Windows 8.1
http://forum.xda-developers.com/showthread.php?t=2727913
{
"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"
}
My drivers are installed, I have "HTC Sync Manager" installed. This is desperating.
Blocked ONE said:
Thanks, downloaded this tool seems great, but my phone is not getting recognized by the system. Im using Windows 8.1
http://forum.xda-developers.com/showthread.php?t=2727913
My drivers are installed, I have "HTC Sync Manager" installed. This is desperating.
Click to expand...
Click to collapse
First off if your running CWM and tried to install ARHD then your gonna have issues as ARHD is only compatible with TWRP recovery 2.6.3.3 or 2.7.1.1
If Windows 8 has stopped recognizing your phone and you can't boot to a Rom unfortunately there's little chance of you getting it working again.
So you have 2 good options. Get/make an otg cable and use it to install a Rom compatible with CWM.
Or create a Linux boot disk to use adb/fastboot. Linux doesn't need drivers for your phone so no detection problems then you can flash recovery or push a Rom whatever you want.
---------- Post added at 03:50 PM ---------- Previous post was at 03:27 PM ----------
Blocked ONE said:
I have read the "disaster recovery" thread but they assume Fastboot USB works. My problem is I dont even know how to connect my phone to my computer in order to work from there.
Click to expand...
Click to collapse
To use Fastboot :- boot the phone to the boot loader and select Fastboot from the menu. Then connect you phone via usb cable and Fastboot should change to fastbootusb.
Open the folder that contains adb and fast boot on your pc then hold Shift and right click on the empty white background space, from the menu that appears select "open command window here"
In the command window type
fastboot devices
If you get an output of your phone's serial no. Fastboot is working.
Danny201281 said:
First off if your running CWM and tried to install ARHD then your gonna have issues as ARHD is only compatible with TWRP recovery 2.6.3.3 or 2.7.1.1
If Windows 8 has stopped recognizing your phone and you can't boot to a Rom unfortunately there's little chance of you getting it working again.
So you have 2 good options. Get/make an otg cable and use it to install a Rom compatible with CWM.
Or create a Linux boot disk to use adb/fastboot. Linux doesn't need drivers for your phone so no detection problems then you can flash recovery or push a Rom whatever you want
To use Fastboot :- boot the phone to the boot loader and select Fastboot from the menu. Then connect you phone via usb cable and Fastboot should change to fastbootusb.
Open the folder that contains adb and fast boot on your pc then hold Shift and right click on the empty white background space, from the menu that appears select "open command window here"
In the command window type
fastboot devices
If you get an output of your phone's serial no. Fastboot is working.
Click to expand...
Click to collapse
I write fastboot devices and nothing happens.
I think I'm trying on a friends computer he has Linux. Hope this is not bricked lol. At least the phone turns ON, it can be charged as well, and bootloader works. But can't fastboot!
Blocked ONE said:
I write fastboot devices and nothing happens.
I think I'm trying on a friends computer he has Linux. Hope this is not bricked lol. At least the phone turns ON, it can be charged as well, and bootloader works. But can't fastboot!
Click to expand...
Click to collapse
Your not even close to being bricked
On Linux you will still need to install adb/fastboot but no drivers for your phone needed. As long as adb is working your on a winner
Also you will need to add sudo at the beginning of each command
E.g "adb devices" becomes " sudo adb devices" or "fastboot flash recovery" becomes " sudo fastboot flash recovery"
Blocked ONE said:
I write fastboot devices and nothing happens.
I think I'm trying on a friends computer he has Linux. Hope this is not bricked lol. At least the phone turns ON, it can be charged as well, and bootloader works. But can't fastboot!
Click to expand...
Click to collapse
Danny201281 said:
Your not even close to being bricked
On Linux you will still need to install adb/fastboot but no drivers for your phone needed. As long as adb is working your on a winner
Also you will need to add sudo at the beginning of each command
E.g "adb devices" becomes " sudo adb devices" or "fastboot flash recovery" becomes " sudo fastboot flash recovery"
Click to expand...
Click to collapse
also Sprint has a different partition structure you CANNOT use files for a GSM phone on yours ...please go to the sprint forums for the files and help you need
Sirs, ubuntu doesnt recognize it either!
While on the bootloop it says system can't mount the Android unit. This means the USB is working.
But on the bootloader/fastboot it doesn't even pop up this message, its like nothing is plugged. WTF I think it is bricked, can't connect anywhere. I feel stupid just trashed my phone for a non important ROM update.
Blocked ONE said:
Sirs, ubuntu doesnt recognize it either!
While on the bootloop it says system can't mount the Android unit. This means the USB is working.
But on the bootloader/fastboot it doesn't even pop up this message, its like nothing is plugged. WTF I think it is bricked, can't connect anywhere. I feel stupid just trashed my phone for a non important ROM update.
Click to expand...
Click to collapse
you need to calm down
first turn the phone off
hold power plus volume down
when the phone goes off keep holding volume down and let go of power
now your in the bootloader
use the volume key to select bootloader then power off
now wait
now hook the phone to the usb and hit power plus volume down
let go of both when you see the bootloader again
now your in fastboot USB
now you can flash the correct recovery to your phone.
next you need this >> http://forum.xda-developers.com/showthread.php?t=2658910
clsA said:
you need to calm down
first turn the phone off
hold power plus volume down
when the phone goes off keep holding volume down and let go of power
now your in the bootloader
use the volume key to select bootloader then power off
now wait
now hook the phone to the usb and hit power plus volume down
let go of both when you see the bootloader again
now your in fastboot USB
now you can flash the correct recovery to your phone.
next you need this >> http://forum.xda-developers.com/showthread.php?t=2658910
Click to expand...
Click to collapse
I followed your instructions but the device doesn't show up in Ubuntu.
But if I try to boot in regular mode, it shows! "Android Phone". The problem is I can't access this, since it just appears for some seconds because this is during the bootloop. Anyway during these seconds, if I click on "Android Phone" it says it cant access it... This is confusing.
I tried both USB 3.0 and 2.0 since I have read 3.0 has problems sometimes.
Should I install any kind of drivers on Ubuntu?
Blocked ONE said:
I followed your instructions but the device doesn't show up in Ubuntu.
But if I try to boot in regular mode, it shows! "Android Phone". The problem is I can't access this, since it just appears for some seconds because this is during the bootloop. Anyway during these seconds, if I click on "Android Phone" it says it cant access it... This is confusing.
I tried both USB 3.0 and 2.0 since I have read 3.0 has problems sometimes.
Should I install any kind of drivers on Ubuntu?
Click to expand...
Click to collapse
From @nkk71 Superguide
5) Q: How do I create a Linux Live USB
Windows users: http://click.xda-developers.com/api...ww.ubuntu.com/download/deskt...ick-on-windows
Mac users: http://www.ubuntu.com/download/deskt...ick-on-mac-osx
Ubuntu 12.04 LTS 32bit ISO from here: http://www.ubuntu.com/download/desktop
Once the Ubuntu Live USB is ready, shutdown your computer and restart from the USB
No need to install, just use the "Try Ubuntu" option
open a terminal
and install adb & fastboot using (copy/paste 1 line at a time into terminal):
Code:
sudo add-apt-repository ppa:nilarimogard/webupd8
sudo apt-get update
sudo apt-get install android-tools-adb android-tools-fastboot
you can then check version, by typing "adb version"
and check connection using "adb devices" in custom recovery or booted phone
and "sudo fastboot devices" in bootloader
you can also check @tobesedated guide for more info: [Guide]Suggestion For S-off On 1.55 HBoot Using Ubuntu---Step by step with pictures
Click to expand...
Click to collapse
OK i think im making some progress!!
I am running this ubuntu from USB, installed adb and fastboot, and I think its connected now. At console I type "fastboot devices" and it says: "HT359W90.... fastboot"
Then I downloaded the TWRP 2.7.1.1 and flashed it. Finally I rebooted the phone and now it enters recovery!!!!!! :good: Im now sure the one is not dead!! Thank you so much guys.
Now what? Should I make a factory reset or just go ahead and flash the ROM I intended to get? Don't want to screw it again...
p.s. Apparently I can't push the ROM from ubuntu to sdcard. It says "no such file or directory". And from phone, the ADB Sideload feature doesnt work either, it gest stuck at "starting ADB sideload feature" even after 15 minutes...
Blocked ONE said:
OK i think im making some progress!!
I am running this ubuntu from USB, installed adb and fastboot, and I think its connected now. At console I type "fastboot devices" and it says: "HT359W90.... fastboot"
Then I downloaded the TWRP 2.7.1.1 and flashed it. Finally I rebooted the phone and now it enters recovery!!!!!! :good: Im now sure the one is not dead!! Thank you so much guys.
Now what? Should I make a factory reset or just go ahead and flash the ROM I intended to get? Don't want to screw it again...
p.s. Apparently I can't push the ROM from ubuntu to sdcard. It says "no such file or directory". And from phone, the ADB Sideload feature doesnt work either, it gest stuck at "starting ADB sideload feature" even after 15 minutes...
Click to expand...
Click to collapse
Ok so you have usb Linux working that's great.
What method did you use to install adb/fastboot? Hopefully it was the Webupd8 repository install as this makes life easy.
Danny201281 said:
Ok so you have usb Linux working that's great.
What method did you use to install adb/fastboot? Hopefully it was the Webupd8 repository install as this makes life easy.
Click to expand...
Click to collapse
Yes I followed the method quoted by clsA
Make sure your Rom is compatible with Sprint then to push it to the phone do this.
Boot your Linux usb stick and select the try ubuntu option. Wait for the desktop to load. Open the Home folder. In the top left you should see other drives connected to your pc. Go into your hdd and copy the Rom to the Home folder of the Linux usb and rename it rom.zip.
Now reboot computer, and Wait for it to return to the try/install ubuntu screen. And press
Control + alt + F1 (this will take you to main Linux terminal)
Boot your phone into recovery and connect with usb and type
adb devices (to check phone is detected if phone is not detected see below)
Then
adb push rom.zip /sdcard
If phone is not detected type the following 3 commands waiting for each to complete there out put. Be patient it may seem stuck at some points and you may see some errors but just wait for the terminal to return to normal after each command I.E ready to accept another command. Once all 3 commands have completed try adb devices again.
sudo add-apt-repository ppa:nilarimogard/webupd8
sudo apt-get update
sudo apt-get install android-tools-adb android-tools-fastboot
Danny201281 said:
Make sure your Rom is compatible with Sprint then to push it to the phone do this.
Boot your Linux usb stick and select the try ubuntu option. Wait for the desktop to load. Open the Home folder. In the top left you should see other drives connected to your pc. Go into your hdd and copy the Rom to the Home folder of the Linux usb and rename it rom.zip.
Now reboot computer, and Wait for it to return to the try/install ubuntu screen. And press
Control + alt + F1 (this will take you to main Linux terminal)
Boot your phone into recovery and connect with usb and type
adb devices (to check phone is detected if phone is not detected see below)
Then
adb push rom.zip /sdcard
If phone is not detected type the following 3 commands waiting for each to complete there out put. Be patient it may seem stuck at some points and you may see some errors but just wait for the terminal to return to normal after each command I.E ready to accept another command. Once all 3 commands have completed try adb devices again.
sudo add-apt-repository ppa:nilarimogard/webupd8
sudo apt-get update
sudo apt-get install android-tools-adb android-tools-fastboot
Click to expand...
Click to collapse
Ubuntu crashes whenever I press Ctrl+Alt+F1, tried twice and had to reboot.
I was using Ctrl+Alt+T for opening a console. Already did all those 3 commands but not working. This seems challenging! I have read something about 32-bits instructions needed for this? Im running under a 64bit computer and 64 bit linux distribution.
By the way a friend has got an OTG cable, would this work to get a ROM inside the SD-Card?
Blocked ONE said:
Ubuntu crashes whenever I press Ctrl+Alt+F1, tried twice and had to reboot.
I was using Ctrl+Alt+T for opening a console. Already did all those 3 commands but not working. This seems challenging! I have read something about 32-bits instructions needed for this? Im running under a 64bit computer and 64 bit linux distribution.
By the way a friend has got an OTG cable, would this work to get a ROM inside the SD-Card?
Click to expand...
Click to collapse
You should be using 32bit Linux it will run ok on a 64bit machine. But with 64bit Linux you will need to install 32bit libs I think.
Yes an otg cable can be used to copy the Rom to the phone
It's weird that you had Fastboot working but adb won't though. Try using adb without the sudo prefix. It should be working if Fastboot is. But remember you must be in recovery to use adb. Not the bootloader.
Fastboot = bootloader
Adb = recovery
Blocked ONE said:
p.s. Apparently I can't push the ROM from ubuntu to sdcard. It says "no such file or directory".
Click to expand...
Click to collapse
Ok slight brain fart on my part lol. The error you got implies that adb is working but your Rom is not in the right place.
You can put the Rom in the home folder and use the adb push command from the terminal as it is when opened.
Or if the Rom is for instance in the downloads folder you must first use
cd Downloads (to take the terminal to the downloads folder)
Then adb push
More problems lol
Apparently I can't flash any ROM because it says I cant mount cache, data nor internal storage.
Im on TWRP 2.7.1.1
Blocked ONE said:
More problems lol
Apparently I can't flash any ROM because it says I cant mount cache, data nor internal storage.
Im on TWRP 2.7.1.1
Click to expand...
Click to collapse
So you've got the Rom on the phone but when go To recovery you can't see the rom because of this error?
It's normal to see these type of errors after using fastboot erase cache. But not normally with internal storage.
If you can see the Rom just flash it it should work.
Unlocking, rooting, relocking and unrooting simplified! (and much more!)
VERSION 2.1.4 - This program will automatically bring together all the files you need to unlock and root your device in a few clicks, or flash it back to stock and re-lock it. You can also use this program to backup/restore all your important data, flash zips, set file permissions, push and pull files, install apps, generate logcats/bugreports, and much more! With the included file association options, you can perform tasks like flashing zips, installing apps, restoring android backup files, and flashing/booting img files with just a double click! The program includes a full featured interface for automating tasks in TWRP, enhanced restore features, an in-built auto-updater/notification system, ‘any build’ mode, advanced restore features,’NRT- Live Log’ for viewing the adb/fastboot cmds that are run in the background, quick tools utilities, and tools for taking screenshots/screen-recordings. All the latest official Android builds and Nexus devices are supported. The program intelligently and selectively downloads the files it needs for your device and makes sure you are using the latest files available. The program can even auto-detect your device and build. This release brings full Marshmallow root support plus all automated features by utilizing a new system that no longer requires modified boot.imgs. Check out the updated changelog for a more comprehensive breakdown of the feature set and changes in this release.
~ my goal for this project is make the entire process as smooth and simple as possible ~
{
"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"
}
Please read the FAQs before posting questions: http://www.wugfresh.com/nrt/faqs/
Looking for a walk-through? >> Excellent Instructional/How-To Videos: http://www.wugfresh.com/videos/
More information & Download Links: http://www.wugfresh.com/nrt/
Changelog: http://www.wugfresh.com/nrt/changelog/
Enjoy! ^_^
{{ WugFresh }}
Hello Nexus Player users. NRT has supported this device for a little while but I never had a dedicated thread.
This device is definitely the most unique of the Nexus lineup - so lets try and keep the posts in this thread specific to this device alone.
Enjoy!
Hello,
Thanks for this great tool.
I tried it last night for a couple of hours and it only seemed to connect to my Nexus Player with the google drivers in step 2.
Also I think it should be noted (sorry if I missed it somewhere) that you need a mouse to complete this root process.
I dont have one and I am now stuck waiting to get one.
I will pick this back up when I get one.
thanks for your effort, Kevin
haeffnkr said:
Hello,
Thanks for this great tool.
I tried it last night for a couple of hours and it only seemed to connect to my Nexus Player with the google drivers in step 2.
Also I think it should be noted (sorry if I missed it somewhere) that you need a mouse to complete this root process.
I dont have one and I am now stuck waiting to get one.
I will pick this back up when I get one.
thanks for your effort, Kevin
Click to expand...
Click to collapse
You don't need a mouse, the root is fully automated in this release.
Sent from my Nexus 5X using Tapatalk
I have installed the drivers , I have unlocked the unit.
I have tried to just root the device and root + flash custom recovery and I get to this screen every time.
Sorry can only link the google pic - https://goo.gl/photos/dCkKYF3j7XpoPojVA
Without a mouse I am stuck and have to repower the nexus player and kill the NRT kit app and start over to no avail.
If I am missing a step please let me know.
(I have seen on other forums that a mouse is needed to get past this step thus my comments and my current experience)
Here is my log where I just ran the root only process again -
Nexus Root Toolkit v2.1.4
Masterlists:
- LatestToolkitFiles.ini 3112
- AndroidDeviceListFull.ini 3112
- AndroidDeviceListFlash.ini 3112
FUGU-FUGU: Android 6.0.1 - Build: MMB29T
Live log initiated [2016-01-19]:
Checking ADB/FASTBOOT Connectivity
adb devices
fastboot devices
Checking ADB/FASTBOOT Connectivity
adb devices
fastboot devices
Checking ADB/FASTBOOT Connectivity
adb devices
85D1781B device
fastboot devices
Connectivity Status: ADB Device Connected
Rebooting your device into bootloader mode...
adb reboot bootloader
Checking Fastboot Connectivity
fastboot devices
85D1781B fastboot
Connectivity Status: Fastboot Device Connected
+ Confirmed: Bootloader Unlocked.
Temporarily Booting TWRP...
fastboot boot "C:\Program Files (x86)\WugFresh Development\Nexus Root Toolkit\data\Recovery_Custom\TWRP\twrp-2.8.7.0-fugu.img"
Checking ADB Recovery Connectivity
adb devices
adb devices
thanks for your help in advance
Kevin
haeffnkr said:
I have installed the drivers , I have unlocked the unit.
I have tried to just root the device and root + flash custom recovery and I get to this screen every time.
Sorry can only link the google pic - https://goo.gl/photos/dCkKYF3j7XpoPojVA
Without a mouse I am stuck and have to repower the nexus player and kill the NRT kit app and start over to no avail.
If I am missing a step please let me know.
(I have seen on other forums that a mouse is needed to get past this step thus my comments and my current experience)
Here is my log where I just ran the root only process again -
Nexus Root Toolkit v2.1.4
Masterlists:
- LatestToolkitFiles.ini 3112
- AndroidDeviceListFull.ini 3112
- AndroidDeviceListFlash.ini 3112
FUGU-FUGU: Android 6.0.1 - Build: MMB29T
Live log initiated [2016-01-19]:
Checking ADB/FASTBOOT Connectivity
adb devices
fastboot devices
Checking ADB/FASTBOOT Connectivity
adb devices
fastboot devices
Checking ADB/FASTBOOT Connectivity
adb devices
85D1781B device
fastboot devices
Connectivity Status: ADB Device Connected
Rebooting your device into bootloader mode...
adb reboot bootloader
Checking Fastboot Connectivity
fastboot devices
85D1781B fastboot
Connectivity Status: Fastboot Device Connected
+ Confirmed: Bootloader Unlocked.
Temporarily Booting TWRP...
fastboot boot "C:\Program Files (x86)\WugFresh Development\Nexus Root Toolkit\data\Recovery_Custom\TWRP\twrp-2.8.7.0-fugu.img"
Checking ADB Recovery Connectivity
adb devices
adb devices
thanks for your help in advance
Kevin
Click to expand...
Click to collapse
Its looking to detect your device while you see that TWRP screen. Your issue is simply driver related. The toolkit should throw you a message at that stage saying it can't find your ADB recovery device - and it provides some tips/suggestions for how to configure it. A simple fix would to be try reinstalling the drivers at this stage, and/or opening your device manager to make sure your device is configured. If nothing is showing up, try unplugging and replugging device.
WugFresh said:
Its looking to detect your device while you see that TWRP screen. Your issue is simply driver related. The toolkit should throw you a message at that stage saying it can't find your ADB recovery device - and it provides some tips/suggestions for how to configure it. A simple fix would to be try reinstalling the drivers at this stage, and/or opening your device manager to make sure your device is configured. If nothing is showing up, try unplugging and replugging device.
Click to expand...
Click to collapse
I have uninstalled drivers and reinstalled 5 times... I can not get it to stay connected.
When I run the driver test and the unit reboots into Fasboot mode then it reboots again and it hangs....the only way I can get it to connect back up again is to go into settings on the nexus and toggle the USB debugging from off to on. The PC then sees the nexus and the script finishes.
I am out of options as to how to get this to connect after it reboots.
EDIT -
I can get the driver script to get to the success without intervention after I have reinstalled the drivers again.
I can not get the past the TWRP screen... as it boots into this screen it disables the ABD connectivity and I am stuck.
Any further help would be appreciated.
thanks for your time
Kevin
haeffnkr said:
I have uninstalled drivers and reinstalled 5 times... I can not get it to stay connected.
When I run the driver test and the unit reboots into Fasboot mode then it reboots again and it hangs....the only way I can get it to connect back up again is to go into settings on the nexus and toggle the USB debugging from off to on. The PC then sees the nexus and the script finishes.
I am out of options as to how to get this to connect after it reboots.
EDIT -
I can get the driver script to get to the success without intervention after I have reinstalled the drivers again.
I can not get the past the TWRP screen... as it boots into this screen it disables the ABD connectivity and I am stuck.
Any further help would be appreciated.
thanks for your time
Kevin
Click to expand...
Click to collapse
Very nice software indeed, thanks WugFresh, had that issue multiple times, when you get the screen that adb doesn't detect device, give it a minute or two and hit continue and it should redetect it. hope it helps. I think installed driver is fine.
confirmed adb doesn't see device once you hit the temporary twrp.
worked really well, thanks for the software!
I had issue initially connecting to the player it took me couple of tries/toggles of adb (developer tools) to get the USB to recognize, and one time of hard boot while unlocking for no reason it just hung there but the device was unlocked.
upsame problem exactly as people above.i can unlock my nexus player but says adb device recovery was not found.and i have android device in device manager working properly.i've tried everything and not new to rooting phones,tablets or any device that can be rooted and romd.
update switched to another pc and worked fine.thanks
Thanks so much for this application! Worked like a charm on Windows 8.1 and Windows 10. Flawlessly installed TWRP after i flashed the purenexus recovery which is bad.. It got stuck after installing the flash for some reason.
twrp 3.0 not available and it wont proceed with out it.. can you help?
yeah, the androidfilehost link for twrp-3.0.0.0-fugu.img is dead, and the official twrp website only goes upto 2.8.7.0
If anyone has downloaded the TWRP v3 fugu img please reup it and share the link
serpentxx said:
yeah, the androidfilehost link for twrp-3.0.0.0-fugu.img is dead, and the official twrp website only goes upto 2.8.7.0
If anyone has downloaded the TWRP v3 fugu img please reup it and share the link
Click to expand...
Click to collapse
Any luck finding the twrp 3.0.0.0 recovery?
unfortunately not, i ended up using SkipSoft toolkit which installed an older TWRP for the latest official rom, seemed to work without issue, and once installed apparantly the twrp recovery can self update itself
Now that twrp is available again, I have a question.
I was having some success using this tool to root when I was interrupted by the lack of recovery image and that's a good thing I think because it gave me time to look into things a bit more. When rooting do I need to be able to navigate the twrp recovery? I ask because the instructions I've seen say a OTG cable and mouse are needed in twrp, which I don't have and I will need to order one online since there don't seem to be any retail stores in my area with one. I'd just hate to get stuck half way through this thing when I'm really just trying to root so I can get my ouya games running on the Nexus player.
EDIT: Have tried again and was unsuccessful. Downloaded the latest TRWP from the other section of the Nexus Player forum and it rejected it as a bad hashcode. Looks like the app will need an overhaul to deal with changes in where files are located before it will continue to be useful. Frustrated. I was under the impression the Nexus line of Android devices were supposed to be easy to root and unlock--so far they've been anything but for me.
Where can I download the file TWRP-3.0.0.0-fugu.img ?
Where can I download the file TWRP-3.0.0.0-fugu.img ?
The file on the twrp site dont work.
I just got it working with the current TWRP-3.0.0.0-fugu.img.
Download "3.0.0-0" from the TWRP site.
Rename the file to "3.0.0.0" (remove that "-").
Copy file to (program path)/Nexus root toolkit/data/Recover_custom/TWRP.
Then run the tool. It'll think it already downloaded the file.
BTW, I had a LOT of issues with the ADB drivers. Easiest fix I found, was delete the driver in device manager, then unplug/plug in device. Didn't think I'd ever get past that first TWRP screen.
Here's the link to download the 3.0 TWRP.img for nexusplayer.
https://dl.twrp.me/fugu/
Hi,
I have the Amazon Fire 7" (not the Fire HD "7!). I did not find any Android ROM for this model, only for the Fire HD 7". Is it possible that such ROM does not exist?
If I'm mistaken, would appreciate if someone could refer me to the proper thread.
moralshixch said:
Hi,
I have the Amazon Fire 7" (not the Fire HD "7!). I did not find any Android ROM for this model, only for the Fire HD 7". Is it possible that such ROM does not exist?
If I'm mistaken, would appreciate if someone could refer me to the proper thread.
Click to expand...
Click to collapse
You need to identify the version of your Kindle. If its the otter2 try these threads over here:
http://forum.xda-developers.com/kindle-fire-hd/fire-2-development
another helpful discussion for you:
http://forum.cyanogenmod.org/topic/90173-otter-or-otter2/
---------- Post added at 02:43 AM ---------- Previous post was at 02:27 AM ----------
If it helps I can attach all the recovery/rom/and gapps that I'm using that seem to work well. I was using pac-rom but switched to slimkat a while ago. I only use this for a bedside alarm clock right now, but I'm thinking of putting it side mounted in my car into my stereo auxiliary running Kodi with the Car Skin they got going on in a thread. I'm not using the latest slimkat rom either I'm using an old version because it works well for me.
How do I identify the version of my Kindle? If it helps, it's the 5th generation that was sold during last December in Amazon for $35
moralshixch said:
How do I identify the version of my Kindle? If it helps, it's the 5th generation that was sold during last December in Amazon for $35
Click to expand...
Click to collapse
You'd need to first install the Kindle drivers, as well as ADB and fastboot, on your PC. Then you would need to completely power off the kindle, type fastboot -i 0x1949 getvar product into a terminal or command prompt, and plug in the Kindle when you see <waiting for device>. Assuming you do this correctly, you should get an output like "jem-pvt-prod-04" in your terminal. The word before the first hyphen in the output (in this example, " jem", which is an example and NOT your particular model's codename) is your device's codename. You should take note of this codename and mention it whenever you're looking for ROMs or device assistance (rooting, flashing a custom recovery, etc.). Once you have the device codename, type fastboot -i 0x1949 reboot to get out of fastboot.
monster1612 said:
You'd need to first install the Kindle drivers, as well as ADB and fastboot, on your PC. Then you would need to completely power off the kindle, type fastboot -i 0x1949 getvar product into a terminal or command prompt, and plug in the Kindle when you see <waiting for device>. Assuming you do this correctly, you should get an output like "jem-pvt-prod-04" in your terminal. The word before the first hyphen in the output (in this example, " jem", which is an example and NOT your particular model's codename) is your device's codename. You should take note of this codename and mention it whenever you're looking for ROMs or device assistance (rooting, flashing a custom recovery, etc.). Once you have the device codename, type fastboot -i 0x1949 reboot to get out of fastboot.
Click to expand...
Click to collapse
I realize this thread is a little old, but I too am trying to get something else on my Kindle Fire other than Fire OS if possible (LineageOS more than likely). Where might I find all of these drivers and utilities, as I have no idea what my Kindle's codename is.
Thanks!
MZGSZM said:
I realize this thread is a little old, but I too am trying to get something else on my Kindle Fire other than Fire OS if possible (LineageOS more than likely). Where might I find all of these drivers and utilities, as I have no idea what my Kindle's codename is.
Thanks!
Click to expand...
Click to collapse
The driver is available on Amazon's developer site, under the "Installing the USB Driver" section. This is assuming you're using Windows, of course.
The ADB binaries can also be downloaded directly from Google as a single .zip file. Once you have both of those downloaded, you should be able to extract the ADB package to an easily accessible directory, right-click on an empty space within the folder view of said directory while holding the shift key down, click "Open command prompt here", and then type the fastboot command I mentioned in the previous reply to identify your kindle.
(Apologies for the late reply!)
Thanks for the information. I got the driver installed and extracted the platform tools. I also enabled ADB from developer options on the Kindle. Problem is, when I run that command you previously mentioned I get this message:
Code:
< waiting for any device >
Nothing else happens, it just keeps waiting.
monster1612 said:
The driver is available on Amazon's developer site, under the "Installing the USB Driver" section. This is assuming you're using Windows, of course.
The ADB binaries can also be downloaded directly from Google as a single .zip file. Once you have both of those downloaded, you should be able to extract the ADB package to an easily accessible directory, right-click on an empty space within the folder view of said directory while holding the shift key down, click "Open command prompt here", and then type the fastboot command I mentioned in the previous reply to identify your kindle.
(Apologies for the late reply!)
Click to expand...
Click to collapse
I realized I never quoted you in my last reply (forums didn't like me quoting links since my account is so new), so you probably wouldn't see my previous reply. Thanks again for your help, I quoted my last post below.
MZGSZM said:
Thanks for the information. I got the driver installed and extracted the platform tools. I also enabled ADB from developer options on the Kindle. Problem is, when I run that command you previously mentioned I get this message:
Code:
< waiting for any device >
Nothing else happens, it just keeps waiting.
Click to expand...
Click to collapse
MZGSZM said:
I realized I never quoted you in my last reply (forums didn't like me quoting links since my account is so new), so you probably wouldn't see my previous reply. Thanks again for your help, I quoted my last post below.
Thanks for the information. I got the driver installed and extracted the platform tools. I also enabled ADB from developer options on the Kindle. Problem is, when I run that command you previously mentioned I get this message:
Click to expand...
Click to collapse
If you go into the device manager within windows and have the Kindle plugged in, does the Kindle show up in its own category? if it doesn't, try giving it a few minutes to install the driver for the device. Also, if you get a prompt on the Kindle asking if you want to "trust" the development computer, you'll want to accept that.
monster1612 said:
If you go into the device manager within windows and have the Kindle plugged in, does the Kindle show up in its own category? if it doesn't, try giving it a few minutes to install the driver for the device. Also, if you get a prompt on the Kindle asking if you want to "trust" the development computer, you'll want to accept that.
Click to expand...
Click to collapse
The device does show up in its own category:
{
"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"
}
Assuming this is the correct one, I'm not sure why I still can't get a readout.
monster1612 said:
If you go into the device manager within windows and have the Kindle plugged in, does the Kindle show up in its own category? if it doesn't, try giving it a few minutes to install the driver for the device. Also, if you get a prompt on the Kindle asking if you want to "trust" the development computer, you'll want to accept that.
Click to expand...
Click to collapse
Hate to sound like a nag, but hoping you saw my last post. Any thoughts on why I'm not getting a readout? Thanks again!
MZGSZM said:
The device does show up in its own category:
Assuming this is the correct one, I'm not sure why I still can't get a readout.
Click to expand...
Click to collapse
That's the right category. Theoretically, the device should be recognized in ADB if you already have it enabled on the Kindle. Try going to the device properties and "updating" the driver by selecting a different one from the list of Fire-specific drivers installed.
My apologies for the extreme lapse in response time - I went through finals earlier this month, and totally forgot about XDA for a while. Anyhow, I haven't worked with the Kindle on Windows in a while - drivers are notoriously finicky, so I tend to use Ubuntu and other Linux OSs for adb and whatnot, seeing as though everything seems to just work without the need for device-specific drivers on that platform.
monster1612 said:
That's the right category. Theoretically, the device should be recognized in ADB if you already have it enabled on the Kindle. Try going to the device properties and "updating" the driver by selecting a different one from the list of Fire-specific drivers installed.
My apologies for the extreme lapse in response time - I went through finals earlier this month, and totally forgot about XDA for a while. Anyhow, I haven't worked with the Kindle on Windows in a while - drivers are notoriously finicky, so I tend to use Ubuntu and other Linux OSs for adb and whatnot, seeing as though everything seems to just work without the need for device-specific drivers on that platform.
Click to expand...
Click to collapse
Hey, no worries. I know how crazy life can get sometimes.
I tried using the different driver versions available without any luck. My laptop currently has a copy of Ubuntu installed, so I could definitely try it on there (with some guidance from you). I'm pretty familiar with how to use the terminal, and would've tried it under Linux had I known it might've been easier.
Thanks again for all of your assistance!
MZGSZM said:
Hey, no worries. I know how crazy life can get sometimes.
I tried using the different driver versions available without any luck. My laptop currently has a copy of Ubuntu installed, so I could definitely try it on there (with some guidance from you). I'm pretty familiar with how to use the terminal, and would've tried it under Linux had I known it might've been easier.
Thanks again for all of your assistance!
Click to expand...
Click to collapse
Nice! I don't know if you need to enable the universe software repo within Ubuntu before you can install the adb programs, but you should be able to type sudo apt-get install android-tools-adb android-tools-fastboot to have them install. After that, you can use the fastboot commands exactly the way you would on Windows, and thus should be able to get the Kindle to boot into fastboot directly from a powered off state. Let me know if you need any other advice or help.
monster1612 said:
Nice! I don't know if you need to enable the universe software repo within Ubuntu before you can install the adb programs, but you should be able to type sudo apt-get install android-tools-adb android-tools-fastboot to have them install. After that, you can use the fastboot commands exactly the way you would on Windows, and thus should be able to get the Kindle to boot into fastboot directly from a powered off state. Let me know if you need any other advice or help.
Click to expand...
Click to collapse
So, I'm still not having any luck. I'm not entirely sure why, I'm guessing maybe I'm missing something?
I've tried getting fastboot to work on three different devices now, two of which were running a Linux OS, the third Windows 7.
I'm running the mentioned fastboot command and then connecting the kindle over USB while it is powered off. ADB is enabled in developer settings.
I've tried running the command with or without the ADB daemon started and with or without the computer in question being authorized as I wasn't sure if that was necessary.
I tried it on my laptop (which is now running Kubuntu) without success but, also read somewhere that fastboot doesn't like USB 3.0. For that reason I tried it also on one of my Raspberry Pi 3s with a fresh install of Raspbian Lite. I didn't have anything else available at the moment running Linux.
I'm guessing I'm probably just missing something small or did one of the steps incorrectly maybe.
MZGSZM said:
So, I'm still not having any luck. I'm not entirely sure why, I'm guessing maybe I'm missing something?
I've tried getting fastboot to work on three different devices now, two of which were running a Linux OS, the third Windows 7.
I'm running the mentioned fastboot command and then connecting the kindle over USB while it is powered off. ADB is enabled in developer settings.
I've tried running the command with or without the ADB daemon started and with or without the computer in question being authorized as I wasn't sure if that was necessary.
I tried it on my laptop (which is now running Kubuntu) without success but, also read somewhere that fastboot doesn't like USB 3.0. For that reason I tried it also on one of my Raspberry Pi 3s with a fresh install of Raspbian Lite. I didn't have anything else available at the moment running Linux.
I'm guessing I'm probably just missing something small or did one of the steps incorrectly maybe.
Click to expand...
Click to collapse
Does your Linux distro recognize the device if you have it plugged in while you're in the Kindle's main OS and you type adb devices? It should work if you have ADB enabled in developer settings.
monster1612 said:
Does your Linux distro recognize the device if you have it plugged in while you're in the Kindle's main OS and you type adb devices? It should work if you have ADB enabled in developer settings.
Click to expand...
Click to collapse
Yep, if I type that a message pops up on screen saying it's unauthorized. The kindle then asks me if it should be authorized.
Try running fastboot as root.
basenjidad said:
Try running fastboot as root.
Click to expand...
Click to collapse
Thanks for the suggestion. I gave that a shot, still no luck getting this Kindle to fastboot.
monster1612 said:
You'd need to first install the Kindle drivers, as well as ADB and fastboot, on your PC. Then you would need to completely power off the kindle, type fastboot -i 0x1949 getvar product into a terminal or command prompt, and plug in the Kindle when you see <waiting for device>. Assuming you do this correctly, you should get an output like "jem-pvt-prod-04" in your terminal. The word before the first hyphen in the output (in this example, " jem", which is an example and NOT your particular model's codename) is your device's codename. You should take note of this codename and mention it whenever you're looking for ROMs or device assistance (rooting, flashing a custom recovery, etc.). Once you have the device codename, type fastboot -i 0x1949 reboot to get out of fastboot.
Click to expand...
Click to collapse
After installing LineageOS on another device, I learned of a command that should force the Kindle to fastboot, and it seemed to work. When I ran the suggested fastboot command I got this output:
Code:
product: AUSTIN
finished. total time: 0.004s
Where might be my next step in finding a compatible ROM?
Many thanks again!