So I just received my new pixel XL 2 and have unlocked the bootloader but not critical and now I can't get anything in fastboot to work any ideas? Should I critical unlock?
ncsuwolfs said:
So I just received my new pixel XL 2 and have unlocked the bootloader but not critical and now I can't get anything in fastboot to work any ideas? Should I critical unlock?
Click to expand...
Click to collapse
1. Are your SDK platform-tools and device drivers up to date??
2. Yes, you should unlock critical once fastboot is responding properly.
3. Are you using a desktop or laptop pc?
4. Are you using a good USB A-USB C cable? Not the one that came with your phone.
5. When in fastboot mode, and you type in fastboot devices, do you see your phone ID# come up? If not, you've got a driver problem. ?
Your number 5 is my number 1. Everytime, lol.
OP, I'd unlock critical. I didn't and then they updated the bootloader. The system wouldn't flash without the updated bootloader and the bootloader wouldn't flash with critical locked.
And... make sure ALL the files you're flashing via fastboot are IN the same platform tools folder WITH the fastboot application
Az Biker said:
And... make sure ALL the files you're flashing via fastboot are IN the same platform tools folder WITH the fastboot application
Click to expand...
Click to collapse
I've always kept my platform tools in C:\platform-tools
Then I add a PATH statement to environment variables. This allows me to use adb and fastboot in any directory.
Can you see any issue doing this? I've never had any problems.
ckarrow2 said:
I've always kept my platform tools in C:\platform-tools
Then I add a PATH statement to environment variables. This allows me to use adb and fastboot in any directory.
Can you see any issue doing this? I've never had any problems.
Click to expand...
Click to collapse
That's how I do it. That way I can open a command window and flash from anywhere
ckarrow2 said:
I've always kept my platform tools in C:\platform-tools
Then I add a PATH statement to environment variables. This allows me to use adb and fastboot in any directory.
Can you see any issue doing this? I've never had any problems.
Click to expand...
Click to collapse
There is no issue doing it this way.
Related
I am trying to unlock the bootloader through HTCdev but my problem is when I open up cmd and type in the command all I get is fastboot access is denied!
I have searched and read for days but cannot find anything to help me out so I have joined up with xda in the hopes someone else out there has had a similar issue or can atleast suggest something.
mrrflagg said:
I am trying to unlock the bootloader through HTCdev but my problem is when I open up cmd and type in the command all I get is fastboot access is denied!
I have searched and read for days but cannot find anything to help me out so I have joined up with xda in the hopes someone else out there has had a similar issue or can atleast suggest something.
Click to expand...
Click to collapse
Try creating a new fastboot folders and updating your HTC drivers. If the need arise, I can share with you my fastboot files
mrrflagg said:
I am trying to unlock the bootloader through HTCdev but my problem is when I open up cmd and type in the command all I get is fastboot access is denied!
I have searched and read for days but cannot find anything to help me out so I have joined up with xda in the hopes someone else out there has had a similar issue or can atleast suggest something.
Click to expand...
Click to collapse
It's probably that the folder is under admin previlage protection.
Try moving fastboot folder.
Didn't work:
-Try extracting fastboot to a new directory again.
Didn't work:
-Run cmd as admin, then use cd command to navigate into fastboot folder
ex: cd c:\fastboot\
convict_moody said:
It's probably that the folder is under admin previlage protection.
Try moving fastboot folder.
Didn't work:
-Try extracting fastboot to a new directory again.
Didn't work:
-Run cmd as admin, then use cd command to navigate into fastboot folder
ex: cd c:\fastboot\
Click to expand...
Click to collapse
Hi convict_moody, I have tried all that you suggested and went as far as removing all traces of my HTC drivers and
fastboot folders from my computer and tried it all from scratch and still no luck.
I recently did a HTC update to 4.2.2 and the Hboot is 1.73 with S on just if that info is of help?
Are the drivers properly installed, you see MYHTC in the windows device manager. If so that's fine.
Maybe download the android sdk bundle and open the command window in the platform tools folder.
Then put there the unlock code.bin file too and flash it
Fastboot flash unlocktoken unlock_code.bin
Mr Hofs said:
Are the drivers properly installed, you see MYHTC in the windows device manager. If so that's fine.
Maybe download the android sdk bundle and open the command window in the platform tools folder.
Then put there the unlock code.bin file too and flash it
Fastboot flash unlocktoken unlock_code.bin
Click to expand...
Click to collapse
Drivers are up to date and I have tried with the sdk bundle, it seems to be so simple and not getting it to work is rather frustrating.
Starting to wonder if it's worth the hassle
mrrflagg said:
Drivers are up to date and I have tried with the sdk bundle, it seems to be so simple and not getting it to work is rather frustrating.
Starting to wonder if it's worth the hassle
Click to expand...
Click to collapse
Sure you logged in as admin on the pc ?
I'm the only user of this computer, got me stumped.
Yeah but when it's not setup as admin you can have trouble
Just want to thank you all for your advice, I tried the process on a different PC and it worked perfectly. Was my laptop the whole time.
Again a big thanks to you all
Dear Exprts
Kindly check this how to fix this problem
when i give a command in CMD (c:\fastboot is not recognized as an internal or external command, oparebale program or batch file)
please give me the procedure as soon as possible ...
i cant unlock the boothloader
Thnks
Deep
I dont get your question. What command u typed? Check if your cmd console working directory is the same as fastboot localization.
Just ctrl rght click in folder where fastboot is and click open command window.
Sent from my One V using xda app-developers app
dipusmart said:
Dear Exprts
Kindly check this how to fix this problem
when i give a command in CMD (c:\fastboot is not recognized as an internal or external command, oparebale program or batch file)
please give me the procedure as soon as possible ...
i cant unlock the boothloader
Thnks
Deep
Click to expand...
Click to collapse
You must have fastboot.exe and the 2 dlls at the same directori, where you are at the moment at console (e.g. you wrote c:\fatsboot, so you need to have fastboot.exe and the 2 dlls at c:\ root to run them.)
I recommend to run fastboot and/or adb from a subdirectory from root, e.g. c:\htc\
I havehave fastboot.exe and the 2 dlls at the same directori (I rote c:\fastboot....but the same result ...
I don't have any root file in c drive
i am attaching the file ...
Ken-Shi_Kun said:
You must have fastboot.exe and the 2 dlls at the same directori, where you are at the moment at console (e.g. you wrote c:\fatsboot, so you need to have fastboot.exe and the 2 dlls at c:\ root to run them.)
I recommend to run fastboot and/or adb from a subdirectory from root, e.g. c:\htc\
Click to expand...
Click to collapse
Check this command in attach file
& told me , whats the problem in command
dipusmart said:
Check this command in attach file
& told me , whats the problem in command
Click to expand...
Click to collapse
don't know what the problem here, but I had errors like this on windows 8.1 and win8, which based on the poor command-line support...
try to move to the folder itself first with cd command, then fastboot as command.
dipusmart said:
Check this command in attach file
& told me , whats the problem in command
Click to expand...
Click to collapse
First, do not place files in the root (system could have some restrictions to run files from here). Place them in any folder and run from there (e.g. c:\fb\fastboot.exe)
Second, usualy you must be in the folder where the running file is. So do this:
cd c:\fb
fastboot ...
---------- Post added at 03:07 PM ---------- Previous post was at 02:59 PM ----------
Btw, are you really sure you want to take the risk with unlocking/rooting/flashing? If you are not quite familiar with a simple computer tasks there is a big chance you will go wrong and the phone will become unuseful. Unless you have many of them and just playing around. =)
Have you tried using the windows AIO tool?
http://forum.xda-developers.com/showthread.php?t=1676686
you may find it easier, but please do read all the instructions carefully especially about making a backup.
thnks guys....
now i don't have warranty ...so i want to upgrade my phone
urgents.....!!!!!
i am already done unlocking/rooting
but i have to install titanium kiss kernal i just stuck in command prompt ..its just waiting for device
what can i do ,,,
dipusmart said:
urgents.....!!!!!
i am already done unlocking/rooting
but i have to install titanium kiss kernal i just stuck in command prompt ..its just waiting for device
what can i do ,,,
Click to expand...
Click to collapse
What exactly the command prompt says?
You have to start your phone in the fastboot mode to accept external commands. So I guess the command prompt is waiting until the phone will get to that mode.
kvestas said:
What exactly the command prompt says?
You have to start your phone in the fastboot mode to accept external commands. So I guess the command prompt is waiting until the phone will get to that mode.
Click to expand...
Click to collapse
In command prompt with your phone connected, and USB debugging turned on in your developer options, and in the folder with your boot.img (you'll need to rename the hellboy kernel file to just boot.img)
type
<adb devices>
you should see a reply showing your phones ID if you get this go for
<adb reboot bootloader>
wait for the phone to reboot to your white bootloader screen then go for
<fastboot flash boot boot.img>
then once the kernel is in
<fastboot reboot>
Again I strongly recommend using an AIO program to make sure you haven't missed a step. Its great to learn all the ways to work with your phone, but its primary use is a phone, if it breaks it won't be able to do that.
Noob again. So I am rooted and I'm currently on build NDE63X on my Verizon 128 gb XL. If i understood the instructions correctly, I have to go back to stock before I can put TWRP on the phone. I know I get the factory images here.
https://developers.google.com/android/images
Do I get the NDE63P image for the phone since that was what was on the phone before I sideloaded the OTA for my current version which is NDE63X or do I just need to download the full image for NDE63X?
Can someone also list the steps needed to accomplish getting phone back to stock? I read Google's instructions and I was a little confused. I understand that I will lose root but should be able to root after installing TWRP since it looks like Chainfire updated the root method for those using TWRP.
Thanks.
It's easy bro. For starters, grab the factory image for the X build. No need to go back to P.
Next, extract the zip. Depending on which OS your computer runs, you'll be running one of the flash-all scripts. the one with the ".bat" extension is for Windows and the one ending with the ".sh" extension is for macOS and Linux. If you don't want it to wipe your device, before running one of those two files I just mentioned, your gonna wanna edit the script file using an application like Notepad++ (on Windows) or Text Wrangler (on macOS.) What you want to do in the script file is remove the wipe command. To do so, delete the following piece from the script: (it's towards the bottom.)
Code:
-w
Save the changes.
Next, copy everything from the factory image folder to where you have adb/fastboot stored. (I suppose you could copy your adb/fastboot files to this folder if you wanted to.)
Assuming that your device is plugged in and USB debugging is enabled, start command prompt (or Terminal.) and type the following commands:
Code:
adb devices (it should return with your devices serial number and say online, if not check your device for a prompt asking to allow or deny.)
adb reboot bootloader
fastboot devices
flash-all.bat (or flash-all.sh)
That should do it. ?
Sent from my Pixel XL
Rydah805 said:
It's easy bro. For starters, grab the factory image for the X build. No need to go back to P.
Next, extract the zip. Depending on which OS your computer runs, you'll be running one of the flash-all scripts. the one with the ".bat" extension is for Windows and the one ending with the ".sh" extension is for macOS and Linux. If you don't want it to wipe your device, before running one of those two files I just mentioned, your gonna wanna edit the script file using an application like Notepad++ (on Windows) or Text Wrangler (on macOS.) What you want to do in the script file is remove the wipe command. To do so, delete the following piece from the script: (it's towards the bottom.)
Code:
-w
Save the changes.
Next, copy everything from the factory image folder to where you have adb/fastboot stored. (I suppose you could copy your adb/fastboot files to this folder if you wanted to.)
Assuming that your device is plugged in and USB debugging is enabled, start command prompt (or Terminal.) and type the following commands:
Code:
adb devices (it should return with your devices serial number and say online, if not check your device for a prompt asking to allow or deny.)
adb reboot bootloader
fastboot devices
flash-all.bat (or flash-all.sh)
That should do it.
Sent from my Pixel XL
Click to expand...
Click to collapse
Thank you. Gonna attempt it this weekend.
Deleted
Rydah805 said:
It's easy bro. For starters, grab the factory image for the X build. No need to go back to P.
Next, extract the zip. Depending on which OS your computer runs, you'll be running one of the flash-all scripts. the one with the ".bat" extension is for Windows and the one ending with the ".sh" extension is for macOS and Linux. If you don't want it to wipe your device, before running one of those two files I just mentioned, your gonna wanna edit the script file using an application like Notepad++ (on Windows) or Text Wrangler (on macOS.) What you want to do in the script file is remove the wipe command. To do so, delete the following piece from the script: (it's towards the bottom.)
Code:
-w
Save the changes.
Next, copy everything from the factory image folder to where you have adb/fastboot stored. (I suppose you could copy your adb/fastboot files to this folder if you wanted to.)
Assuming that your device is plugged in and USB debugging is enabled, start command prompt (or Terminal.) and type the following commands:
Code:
adb devices (it should return with your devices serial number and say online, if not check your device for a prompt asking to allow or deny.)
adb reboot bootloader
fastboot devices
flash-all.bat (or flash-all.sh)
That should do it.
Sent from my Pixel XL
Click to expand...
Click to collapse
im trying to do the same thing but i cant find somewhere to download the factory img from i have a 32 gb xl
Veid71 said:
im trying to do the same thing but i cant find somewhere to download the factory img from i have a 32 gb xl
Click to expand...
Click to collapse
https://developers.google.com/android/images
Sent from my Pixel XL
My command prompt hangs when I try to execute the .bat file
Says "Waiting for any device"
And yes the device is listed when I do ADB devices
Any ideas?
THANKS!!
chipslate said:
My command prompt hangs when I try to execute the .bat file
Says "Waiting for any device"
And yes the device is listed when I do ADB devices
Any ideas?
THANKS!!
Click to expand...
Click to collapse
if you are executing the commands, you are in fastboot, not adb.
try fastboot devices
if it doesnt return anything, your computer is not seeing the device.
you will need the computer to see the device in fastboot before you can proceed.
OK so ADB Devices finds my cellphone but fastboot devices yields nothing.
Any ideas?
chipslate said:
OK so ADB Devices finds my cellphone but fastboot devices yields nothing.
Any ideas?
Click to expand...
Click to collapse
first thing to try is to go into fastboot, then unplug the cable, and then plug it back in.
if it is still not recognized, then its either an outdated adb/fastboot issue, or a driver issue (if you are using windows, if not there may be other possibilities).
chipslate said:
OK so ADB Devices finds my cellphone but fastboot devices yields nothing.
Any ideas?
Click to expand...
Click to collapse
When it finds your phone does it say unauthorized or authorized?
See attached. That is what I get every time. I have had the same thing happen on 2 different Windows 10 boxes. Makes me think it is something on the phone?
chipslate said:
See attached. That is what I get every time. I have had the same thing happen on 2 different Windows 10 boxes. Makes me think it is something on the phone?
Click to expand...
Click to collapse
What happens now when you attempt the next command?
Edit: So after running adb devices, you should be running adb reboot bootloader command next I believe.
Yes, ADB reboot bootloader brings up the fastboot screen on the Pixel XL with the green android thingy.
Also, I have the phone in MTP File Transfer mode and USB Debugging enabled.
chipslate said:
Yes, ADB reboot bootloader brings up the fastboot screen on the Pixel XL with the green android thingy.
Click to expand...
Click to collapse
You should now use the flash-all command but this is going wipe all of your data.
I am fine wiping all my data but running flash-all.bat hangs the CMD window saying "Waiting for any device"
That's my problem.
chipslate said:
I am fine wiping all my data but running flash-all.bat hangs the CMD window saying "Waiting for any device"
That's my problem.
Click to expand...
Click to collapse
Post a picture of when you have that and of your phone at the time you type flash all if you can. Also hit the reply button on my post and itll give my notifications when you reply.
magestic1995 said:
Post a picture of when you have that and of your phone at the time you type flash all if you can. Also hit the reply button on my post and itll give my notifications when you reply.
Click to expand...
Click to collapse
It finally worked!!! Thanks again for your help and going back and forth. I finally installed Android Studio and it inserted the ADB drivers at the top of Device manager. Worked like a charm then. Finally, Android 7.1.1 and unlocked bootloader... Bring it on, world!
Congrats! I've only used Android Studio for all this stuff since Im a developer. Congrats on getting it all figured out!
i have been trying to take my pixel xl back to stock but the flash-all.bat script hangs on the part where it should flash the system img zip. it says the file size is to large
This is bothering me alot, bought an HTC10 thats with o2 and i cant get the final step to work.
I have received the email twice in as a many attempts,used Chrome and IE to download the unlock code. I placed the unlock code in the same folder as fastboot adb and the other adb
all drivers were installed,including the Android studio one thats 1.6gb along htcsync. When i type in adb devices my device sn comes up
Not sure what to make of this, i looked over the web their issues were that they either had a typo or missplaced the code ,is there really no solution for me?
I only saw this once before when I accidentally renamed the unlock file unlock_code.bin.bin. can we see the properties of the unlock_code.bin? Also I couldn't see from the picture if you had run the command prompt as admin?
Cat_On_Droid said:
This is bothering me alot, bought an HTC10 thats with o2 and i cant get the final step to work.
I have received the email twice in as a many attempts,used Chrome and IE to download the unlock code. I placed the unlock code in the same folder as fastboot adb and the other adb
all drivers were installed,including the Android studio one thats 1.6gb along htcsync. When i type in adb devices my device sn comes up
Not sure what to make of this, i looked over the web their issues were that they either had a typo or missplaced the code ,is there really no solution for me?
Click to expand...
Click to collapse
Why don't u uninstall HTC sync and try again.
In folder options for Windows turn on the option to see all file extensions and make sure its labeled "Unlock_code.bin". Also just Shift+Right Click in that folder so you have a Command Prompt that's already loaded in there so all you have to do is type the fastboot commands and not the entire directory. (makes life a little easier)
Tachi91 said:
In folder options for Windows turn on the option to see all file extensions and make sure its labeled "Unlock_code.bin". Also just Shift+Right Click in that folder so you have a Command Prompt that's already loaded in there so all you have to do is type the fastboot commands and not the entire directory. (makes life a little easier)
Click to expand...
Click to collapse
it is a bin file, the pic provided just cuts before it says its a bin file. �ts labaled exactly as in attachment
i updated to latest OTA , enabled USB debugging and still same problem :crying::crying::crying::crying:
attached the Unlock_code for refference
Try just dragging the .bin file onto the command window and then pressing "Enter." This gets rid of any possible path or name issues.
rwallhtc said:
I only saw this once before when I accidentally renamed the unlock file unlock_code.bin.bin. can we see the properties of the unlock_code.bin? Also I couldn't see from the picture if you had run the command prompt as admin?
Click to expand...
Click to collapse
Solved !
You need to run cmd as admin, simple as that haha
Question , OTA updates with unlocked bootloader+root will work or no?
Cat_On_Droid said:
Solved !
You need to run cmd as admin, simple as that haha
Question , OTA updates with unlocked bootloader+root will work or no?
Click to expand...
Click to collapse
Look into Magisk.
http://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Is there any way to get past the device needing -i 0x2c3f to use fastboot? trying to port efidroid and the scripts for finalize_device use fastboot. My machine makes me input that line every fastboot command so basically I'm stuck because it doesn't recognize my device while running the scripts.
Edit: for some reason sudo -s finalize_device device/nextbit/ether worked but have some other issues with building efi droid.
AnierinB said:
Is there any way to get past the device needing -i 0x2c3f to use fastboot? trying to port efidroid and the scripts for finalize_device use fastboot. My machine makes me input that line every fastboot command so basically I'm stuck because it doesn't recognize my device while running the scripts.
Click to expand...
Click to collapse
As far as I know, there isn't a way around it. Only happens on some Robins, mines doesn't need that for fastboot.
VenomMOD said:
As far as I know, there isn't a way around it. Only happens on some Robins, mines doesn't need that for fastboot.
Click to expand...
Click to collapse
Darn it.. it's been getting to me for a few days now and I even got lk.img to boot and configured so alls that needs to be done is the finalize_device and then off to compiling uefi. Oh well, at least I got that close :crying:
Windows it works without it but cant compile jack on that xD
Just got my Robin few days ago, I only have access to Ubuntu machine for a few days. I got adb working and fastboot but have not unlocked yet. My question is will I need to use that Id in command line for all fastboot commands?
bback78901 said:
Just got my Robin few days ago, I only have access to Ubuntu machine for a few days. I got adb working and fastboot but have not unlocked yet. My question is will I need to use that Id in command line for all fastboot commands?
Click to expand...
Click to collapse
from my understanding i believe so but as venom mentioned above he doesn't need to do that but he could be running windows idk he didn't list his machines OS
if it doesn't detect without that cmd extension then you need it
AnierinB said:
from my understanding i believe so but as venom mentioned above he doesn't need to do that but he could be running windows idk he didn't list his machines OS
if it doesn't detect without that cmd extension then you need it
Click to expand...
Click to collapse
Forgot to add, I only use it on Windows 10.
The problem is for whatever reason most device managers - Linux and OSX included do not recognize it as a fastboot device. Therefore that command is instructing the machine to look for that specific vendor and device ID. Something to do with NextBit's implementation of Fastboot cause this. So no. No way around it. You'll see that my guide to reflash the stock ROM also has it
valhallen.282 said:
The problem is for whatever reason most device managers - Linux and OSX included do not recognize it as a fastboot device. Therefore that command is instructing the machine to look for that specific vendor and device ID. Something to do with NextBit's implementation of Fastboot cause this. So no. No way around it. You'll see that my guide to reflash the stock ROM also has it
Click to expand...
Click to collapse
Got it to bypass needing -i 0x2c3f just by typing sudo -s before my fastboot cmd.
Try it