i cant find the fastboot option! it is mentioned in htcdev but not present in the phone
htc m9 marshmallow
{
"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 connect the phone in download mode to pc , but the phone is not recognized
You got to use a cmd on PC, having fastboot/adb installed on it, to enter fastboot comands, as well as to activate developer options on the phone itself and check adb debugging and factory unlock option. But I guess you already know this. In addition there is no fastboot mode any longer. Thus you got to perform those commands when the phone is booted to download mode.
Sent from my HUAWEI M2-A01L using XDA Labs
the pc recognize it
http://s14.postimg.org/4fd6gjgb5/screenshot_9.png
but i don't know how to use the cmd
i regret buying an htc phone!
fireheart2008 said:
i regret buying an htc phone!
Click to expand...
Click to collapse
Why'd you do so. You just have to read a little bit of how to use the basics as fastboot. I know other OEM got flashtools, and there are some around for HTC as well. But it can never be wrong to know about all the basics of flashing and rooting a phone.
Go to settings > about. Find the build number entry. Tab it as ling as it states you are a developer now. Head back to settings > developer options. Check mark the USB debugging as well as the bootloader unlock entry.
Install adb/fastboot - minimal adb/fastboit found on XDA will do. Head over to htcdev.com and start unlocking by following the guide.
Sent from my HTC 10 using XDA Labs
Related
I'm using the toolkit, however after I click the 1 Click for all... The bootloader unlocked sucessfully, however on the root part, it got stuck..
It keeps saying waiting for USB debugging to be enabled.... Anyone know a fix?
{
"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"
}
Here's the picture...
It just stays on waiting for USB debugging to be enabled....
With USB Debugging enabled, I don't see my internal drive(the 13.33GB)
When it's disabled I see it..
I installed PDAnet, and when I enable usb debugging, it says Device attached.... So it's detecting something, but the toolkit isn't recognizing...
Help please. D:
Follow this guide Here
I installed the AIO ADB for dummies, than ran the toolkit, still stuck in the waiting for USB debugging...
In fastboot mode, the toolkit reads some serial # on the Fastboot Mode, and on device manager it says Android 1.0.
http://forum.xda-developers.com/showthread.php?t=1529058 - follow this.
nitrogen618 said:
I'm using the toolkit, however after I click the 1 Click for all... The bootloader unlocked sucessfully, however on the root part, it got stuck..
It keeps saying waiting for USB debugging to be enabled.... Anyone know a fix?
Click to expand...
Click to collapse
Srry I didn't see the image above..
Hmm. I found the problem.
Disabled the AVAST! Antivirus, and ran the toolkit again. Wala No problem
Thanks guys!
Don't use a toolkit and follow the guide that XN posted. Its the same guide that I used.
Sent from my Galaxy Nexus using Tapatalk 2
Hello!
Well, I've followed your tutorials and installed android SDK which came in a .zip and I just extracted it to my C:\ directory.
But the phone just doesn't connect! See the image below please.
{
"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 debbuging enabled in my nexus and I am freaking out with this eheh. Little help please xd
Did you boot into the bootloader?
Sent from my Galaxy Nexus using Tapatalk 2
Assuming you've already unlocked the bootloader.
Turn off your cell phone, press Vol+ & Vol- while holding both keys press and hold PowerButton you'll boot into bootloader, now connect your devices to PC and run the command "fastboot devices" if you have all drivers correctly installed you should see something like:
List of Devices
"Devices: xxxxxxxxxx"
Click to expand...
Click to collapse
if you don't see any devices that means either drivers are not installed or you're not booted into the bootloader, but if you see your devices connected use the "fastboot flash recovery recovery.img" once the installation is finished boot into recovery and flash the SuperSU(root).zip
Peace,
L4.1
Rayaxe said:
Hello!
Well, I've followed your tutorials and installed android SDK which came in a .zip and I just extracted it to my C:\ directory.
But the phone just doesn't connect! See the image below please.
I have usb debbuging enabled in my nexus and I am freaking out with this eheh. Little help please xd
Click to expand...
Click to collapse
Try using "fastboot devices" to see if it lists your phone. Fastboot only works when you're in bootloader mode. "adb devices" will list your phone when bored into the os.
Sent from my Galaxy Nexus
thanks guys, it worked ^^
So I got this used HTC One m8 from my friend and there's a weird glitch that happened after I factory reset the phone. The app has the default icon, package name and won't respond when I try to open it. Here is a picture of it.
{
"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"
}
It's the Android app. Is it because there's no sim card in?
I'd love some help
Android version 6.0, not rooted.
Bump I asked here because no one can answer me.
thegamerchunk1 said:
So I got this used HTC One m8 from my friend and there's a weird glitch that happened after I factory reset the phone. The app has the default icon, package name and won't respond when I try to open it. Here is a picture of it.
It's the Android app. Is it because there's no sim card in?
I'd love some help
Android version 6.0, not rooted.
Click to expand...
Click to collapse
try flashing thr RUU does not require root ot TWRP just require a pc and a usb connector get adb on your computer and type in adb fastboot reboot, wait for hone to reboot into bootloader and type fastboot gatvar all and post the result here. https://drive.google.com/file/d/0B2FyBGshXWIxeHdPRy1zWXdwM1E/view?usp=sharing use this link to download adb.zip. extract the zip file and go into the bundle folder, sdk, platform, platform-tool and press shift and right click at the same time and select open command prompt here and you got yourself adb and fastboot. (only works for Windows)
So I have a google pixel c that I think is bricked but I'm not too sure. When I turn the device on it just boots to the bootloader, I can access fastboot and my PC detects the device through the command "fastboot devices", the bootloader is locked and oem unlock was not set in the developer settings. Anything I can do to get the device working again?
{
"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"
}
Can't you unlock it via fastboot ?
rhmanoa said:
Can't you unlock it via fastboot ?
Click to expand...
Click to collapse
I don't believe it's possible to run the OEM unlock command without setting OEM as unlocked in developer setting first
Mike4046 said:
I don't believe it's possible to run the OEM unlock command without setting OEM as unlocked in developer setting first
Click to expand...
Click to collapse
If you are unable to fix it, let me know. I may be interested in buying it.
Mike4046 said:
So I have a google pixel c that I think is bricked but I'm not too sure. When I turn the device on it just boots to the bootloader, I can access fastboot and my PC detects the device through the command "fastboot devices", the bootloader is locked and oem unlock was not set in the developer settings. Anything I can do to get the device working again?
Click to expand...
Click to collapse
You can follow steps in the thread named "helped about pixel C". I think you have the same problem than me .
guys I can not reconnect the phone to the PC I get this error
If you're using type C - type C cable, try a type A - type C.
i am using the classic type c cable
{
"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"
}
What does classic mean? Just make sure there's usb A on the computer side... Do you have USB debugging and OEM unlocking enabled in developer settings?
yes all active
You didn't install a fastboot driver..
I had the same problem i applied this:
[Guide] Fix Device Not Showing Up In Fastboot Mode (Windows 10/11)
You sir are saint...I've been trying to get fastboot to recognize my OP6T for the last 8 hours. Thank you so much!
forum.xda-developers.com
Stef_ said:
I had the same problem i applied this:
[Guide] Fix Device Not Showing Up In Fastboot Mode (Windows 10/11)
You sir are saint...I've been trying to get fastboot to recognize my OP6T for the last 8 hours. Thank you so much!
forum.xda-developers.com
Click to expand...
Click to collapse
This resolved the same issue for me as well. Odd though, because it was working fine for me a couple of months ago.
This is a windows problem, and as others stated downloading the fastboot driver does work, I had to manually install it as an optional update through Windows Update last time it happened, but I prefer to use Linux, as this is one of those "just works" scenarios on there (albeit MSM tool requires Windows, and unaware of a workaround)