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.
Related
I used Team win Recovery Project to wipe my phone Galaxy Nexus, and now when I plug the phone in to the lappy it doesn't show the sd card. Freaking out here cause I can't copy over a zip file to flash a ROM... please help...
The GNEX doesn't have an actual sdcard, so when you wiped the phone i'm guessing you wiped the virtual sd card.
You will have to adb push a rom to your phone.
One the top of the first Q&A page jubakuba has a guide that has a panic section in it.
The guide also shows how to install adb/fastboot and gives you the commands.
try flash the stock img via fastboot using the following line to avoid wiping ur sdcard
fastboot update ***.zip
then wipe data via CWM and enjoy
xskordeal said:
try flash the stock img via fastboot using the following line to avoid wiping ur sdcard
fastboot update ***.zip
then wipe data via CWM and enjoy
Click to expand...
Click to collapse
sorry, complete DOLT here. Where would I input the command?
If you don't know about adb/fastboot, do as suggested in first post. All is explained in the guide.
How to get to a MS-DOS prompt or Windows command line
TheDodgey said:
sorry, complete DOLT here. Where would I input the command?
Click to expand...
Click to collapse
Click Start.
Click Run.
Type cmd or command and press enter.
gpfnzl said:
If you don't know about adb/fastboot, do as suggested in first post. All is explained in the guide.
Click to expand...
Click to collapse
ok, following your instructions, and the instructions of the link, I have install ADB and can use cmd, however when I type adb shell, I get an error returning "device not found"
I see a lot of threads stating to make sure usb debugging is on, it was before I wiped the phone, but obviously I cant get to any settings at the moment.
on the verge of crying now, and noone likes to see a grown man cry
FIXED
I ran the push command whilst in recovery and it worked
not sure that it mattered, but I did change the zip file name to ROM.zip, and whilst in recovery, ran the comand "adb push ROM.zip /sdcard/ROM.zip
Just thought I would put that in there for other dopes like me that might come across this problem
Thanks to all for your help!
LOL
Normally if you can't see your device listed you haven't installed the drivers correctly.(or the correct drivers)
Also you have to open a command prompt window in the same folder as fastboot.exe and adb.exe
To do this in Windows 7:
Click the windows start button (bottom left hand corner)
In the search bar at the bottom type: cmd
At the top of the search list you will see the program cmd.exe right click and copy it.
Paste it into the same folder that has fastboot.exe and adb.exe
Now you can open the cmd window and type the command:
adb devices
Hit ENTER and if you have installed drivers correctly, the serial number of your phone will be listed.
If not, uninstall the drivers, download a new set of drivers from jubakuba or efrants guide and reinstall.
---------- Post added at 11:58 AM ---------- Previous post was at 11:53 AM ----------
TheDodgey said:
FIXED
I ran the push command whilst in recovery and it worked
not sure that it mattered, but I did change the zip file name to ROM.zip, and whilst in recovery, ran the comand "adb push ROM.zip /sdcard/ROM.zip
Just thought I would put that in there for other dopes like me that might come across this problem
Thanks to all for your help!
Click to expand...
Click to collapse
didn't need to change the name of the rom zip. Just needed to type the full name of the .zip file.
Good to see it worked, and the tears have stopped
I wrote this guide a while back after fixing a friends phone, it has worked on others too so i decided id post it here for anyone that ran into this issue later down the road and did not want to run a ruu. This also works great if you want to start fresh before flashing roms.
Basically all this does it swap out recovery's and clean the SD, give it a fresh start.
You can find the full guide & Video here http://forums.team-nocturnal.com/showthread.php/1050
This involves unnecessarily deleting the contents of the internal sdcard.
The following method works 99% of the time, albeit in linux only:
1: reboot into recovery & do a mount usb storage (no mount sdcard)
this will just present your internal storage as a mass storage device to the system
2: do a
fsck.vfat /dev/sdX or /dev/ubX (whatever it gets detected as) - you can find out via (dmesg|tail)
Analogically, you can fix your data partition if it got corrupted.
You need to do it from recovery since not all roms have the fsck binaries available:
from recovery (copy - paste, unless you know what you're doing):
umount /cache
for x in {2,3,5}, do fsck.ext4 -fyD /dev/block/mmcblk0p1$x;sync;done;clear;echo done
XsMagical said:
I wrote this guide a while back after fixing a friends phone, it has worked on others too so i decided id post it here for anyone that ran into this issue later down the road and did not want to run a ruu. This also works great if you want to start fresh before flashing roms.
Basically all this does it swap out recovery's and clean the SD, give it a fresh start.
You can find the full guide & Video here http://forums.team-nocturnal.com/showthread.php/1050
Click to expand...
Click to collapse
Hi XsMagical this link no longer works. Can you provide me with the guide I'm having the issue with the corrupted SD card and my htc one x is bricked.
movadoevo8 said:
Hi XsMagical this link no longer works. Can you provide me with the guide I'm having the issue with the corrupted SD card and my htc one x is bricked.
Click to expand...
Click to collapse
what is your base number and hboot ?normally the sdcard thing is fixed long time ago
One-X-master said:
what is your base number and hboot ?normally the sdcard thing is fixed long time ago
Click to expand...
Click to collapse
How do i locate the Hboot number is that the serial# if so here it is HT265W300361
movadoevo8 said:
How do i locate the Hboot number is that the serial# if so here it is HT265W300361
Click to expand...
Click to collapse
no reboot into fastboot and you will see it there.... and base number you can see in settings/about then somewhere there
One-X-master said:
no reboot into fastboot and you will see it there.... and base number you can see in settings/about then somewhere there
Click to expand...
Click to collapse
hboot = 1.14.0002
movadoevo8 said:
hboot = 1.14.0002
Click to expand...
Click to collapse
do you have the one xl? try to update it to latest base
One-X-master said:
do you have the one xl? try to update it to latest base
Click to expand...
Click to collapse
Yes it's an XL, however i can't update, because any zip or file i throw in the SDCARD via twrp recovery after mounting as per my original post it disappears for some reason so i don't know how i would flash anything.
movadoevo8 said:
Yes it's an XL, however i can't update, because any zip or file i throw in the SDCARD via twrp recovery after mounting as per my original post it disappears for some reason so i don't know how i would flash anything.
Click to expand...
Click to collapse
can you not mount adb sideload and flash through that ?
I had yesterday night the problem that I wiped phone because I had some issues...then wanted to put Rom.zip through recovery on sdcard...problem was my pc didn't accepted it...so I tried to find a solution then I found the adb sideload function installed then again the adb and HTC one x driver and then I was able to put the zip on my sdcard...flashed then Rom and yes all is working now
Gesendet von meinem HTC One X mit Tapatalk 2
markb63 said:
can you not mount adb sideload and flash through that ?
Click to expand...
Click to collapse
I'm not sure how to do that and what that means. I know how to flash via TWRP recovery which is not working and flash boot images etc using "FASTBOOT".
---------- Post added at 09:34 AM ---------- Previous post was at 09:31 AM ----------
One-X-master said:
I had yesterday night the problem that I wiped phone because I had some issues...then wanted to put Rom.zip through recovery on sdcard...problem was my pc didn't accepted it...so I tried to find a solution then I found the adb sideload function installed then again the adb and HTC one x driver and then I was able to put the zip on my sdcard...flashed then Rom and yes all is working now
Gesendet von meinem HTC One X mit Tapatalk 2
Click to expand...
Click to collapse
I can put the zip in there even if i remove the USB cable without unmounting and then plug the USB cable again i see the file inside the phone just fine, the problem is when I unmount to get back into TWRP recovery to install a zip then it doesn't show up. Very weird not sure what is going on, but from what i hear it's a corrupted SD CARD. I found a thread, that teaches you how to fix this, but the link is now broken. I have PM the original poster hope he will contact me back.
movadoevo8 said:
I'm not sure how to do that and what that means. I know how to flash via TWRP recovery which is not working and flash boot images etc using "FASTBOOT".
---------- Post added at 09:34 AM ---------- Previous post was at 09:31 AM ----------
I can put the zip in there even if i remove the USB cable without unmounting and then plug the USB cable again i see the file inside the phone just fine, the problem is when I unmount to get back into TWRP recovery to install a zip then it doesn't show up. Very weird not sure what is going on, but from what i hear it's a corrupted SD CARD. I found a thread, that teaches you how to fix this, but the link is now broken. I have PM the original poster hope he will contact me back.
Click to expand...
Click to collapse
http://teamw.in/ADBSideload if you use this you can flash direct from sdk,worth a shot !!
markb63 said:
http://teamw.in/ADBSideload if you use this you can flash direct from sdk,worth a shot !!
Click to expand...
Click to collapse
Thank you so much! I will definitely toy with this later to see if it works.
---------- Post added at 10:07 AM ---------- Previous post was at 09:45 AM ----------
markb63 said:
http://teamw.in/ADBSideload if you use this you can flash direct from sdk,worth a shot !!
Click to expand...
Click to collapse
adb sideload /path/to/rom.zip
this is not working for me instead of just displays all the commands that adb can do.
I have gone and go to advanced>adb sideload in twrp supported version
on my computer i have a folder called c:\fastboot with the adb software and it's the version that supports adb side load according to the instructions so i have met all the requirements. However when i run the command
adb sideload cm.zip
as i am already in the c:\fastboot folder via command prompt all i get is a display of all the commands i can use with adb as if i just typed "adb" and it displays all the commands.
I also tried typing
adb sideload c:\fastboot\cm.zip
this did not work either same result. FYI cm.zip is the name of the rom file.
I also tried typing
adb sideload /fastboot/cm.zip
Any thoughts?
movadoevo8 said:
Thank you so much! I will definitely toy with this later to see if it works.
---------- Post added at 10:07 AM ---------- Previous post was at 09:45 AM ----------
adb sideload /path/to/rom.zip
this is not working for me instead of just displays all the commands that adb can do.
I have gone and go to advanced>adb sideload in twrp supported version
on my computer i have a folder called c:\fastboot with the adb software and it's the version that supports adb side load according to the instructions so i have met all the requirements. However when i run the command
adb sideload cm.zip
as i am already in the c:\fastboot folder via command prompt all i get is a display of all the commands i can use with adb as if i just typed "adb" and it displays all the commands.
I also tried typing
adb sideload c:\fastboot\cm.zip
this did not work either same result. FYI cm.zip is the name of the rom file.
I also tried typing
adb sideload /fastboot/cm.zip
Any thoughts?
Click to expand...
Click to collapse
do you have sdk on your desktop ? ... if so reboot your phone into recovery and connect to your pc via usb-open up sdk\platform tools-enter into adb sideload in recovery,then put your curser in the platform tools folder-press and hold the shift key and right click mouse,you should see open command window here-click.then enter adb devices-your device should show as ********* sideload in the command adb window.your device should now be asking for you to flash ?
markb63 said:
do you have sdk on your desktop ? ... if so reboot your phone into recovery and connect to your pc via usb-open up sdk\platform tools-enter into adb sideload in recovery,then put your curser in the platform tools folder-press and hold the shift key and right click mouse,you should see open command window here-click.then enter adb devices-your device should show as ********* sideload in the command adb window.your device should now be asking for you to flash ?
Click to expand...
Click to collapse
okay i followed your instructions and when i type "adb devices" i get the following output
C:\fastboot>adb devices
List of devices attached
HT2AHW300413 host
However my phone does say "now send the package you want to apply to the device with "adb sideload <filename>"
but when i goto advance>sideload from twrp that is what displays on the phone from the get go even before i run the command. SDK i have ADB version 1.0.29
When you say to make sure i have SDK please see the following screen shot i have attached and let me know if you are referring to those files under my fastboot folder and/or if i'm actually missing something.
movadoevo8 said:
okay i followed your instructions and when i type "adb devices" i get the following output
C:\fastboot>adb devices
List of devices attached
HT2AHW300413 host
However my phone does say "now send the package you want to apply to the device with "adb sideload <filename>"
but when i goto advance>sideload from twrp that is what displays on the phone from the get go even before i run the command. SDK i have ADB version 1.0.29
When you say to make sure i have SDK please see the following screen shot i have attached and let me know if you are referring to those files under my fastboot folder and/or if i'm actually missing something.
Click to expand...
Click to collapse
I think your in fastbboot folder ? you need to be in platform tools .my platform tools has a lot more inside than yours
movadoevo8 said:
okay i followed your instructions and when i type "adb devices" i get the following output
C:\fastboot>adb devices
List of devices attached
HT2AHW300413 host
However my phone does say "now send the package you want to apply to the device with "adb sideload <filename>"
but when i goto advance>sideload from twrp that is what displays on the phone from the get go even before i run the command. SDK i have ADB version 1.0.29
When you say to make sure i have SDK please see the following screen shot i have attached and let me know if you are referring to those files under my fastboot folder and/or if i'm actually missing something.
Click to expand...
Click to collapse
You don't need whole sdk ...if you activate adb sideload in recovery go to device manager on pc there should be something with android device or so ...then right click on it then update drivers or so then something with from computer and download at first the adb drivers for windows 8 extract to a folder a then in the driver update thing select this folder and update it or so...sorry am atm to stupid to write in English but you can sideload because adb drivers aren't working properly...you should also install HTC sync manager etc so it should be fixed then ...if not Google HTC one x adb driver windows 8 many instructions to get all working properlY
Gesendet von meinem HTC One X mit Tapatalk 2
One-X-master said:
You don't need whole sdk ...if you activate adb sideload in recovery go to device manager on pc there should be something with android device or so ...then right click on it then update drivers or so then something with from computer and download at first the adb drivers for windows 8 extract to a folder a then in the driver update thing select this folder and update it or so...sorry am atm to stupid to write in English but you can sideload because adb drivers aren't working properly...you should also install HTC sync manager etc so it should be fixed then ...if not Google HTC one x adb driver windows 8 many instructions to get all working properlY
Gesendet von meinem HTC One X mit Tapatalk 2
Click to expand...
Click to collapse
I'm setting this up on my windows 7 machine, now I think i had an issue once on win 8. Updates to follow, thanks.
markb63 said:
I think your in fastbboot folder ? you need to be in platform tools .my platform tools has a lot more inside than yours
Click to expand...
Click to collapse
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
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