I've been struggling for a week with this.
Trying to unlock the bootloader but whenever I get to the stage of using command prompt I get this message;
'fastboot' is not recognized as an internal or external command,
operable program or batch file
The PC just will not recognise the phone when in fastboot mode although it does when not.
Windows 7
Android 4.3
HTC Sense Version 5.5
Software number 3.62.401.1
HTC SDK API Level 5.65
USB Debugging ticked
Fast boot deticked
HTC cable used
Latest drivers installed
Any help would be appreciated, the only previous experince I have is rooting a Galaxy note and tablet with no trouble whatsoever.
tj
tjpearson said:
I've been struggling for a week with this.
Trying to unlock the bootloader but whenever I get to the stage of using command prompt I get this message;
'fastboot' is not recognized as an internal or external command,
operable program or batch file
The PC just will not recognise the phone when in fastboot mode although it does when not.
Windows 7
Android 4.3
HTC Sense Version 5.5
Software number 3.62.401.1
HTC SDK API Level 5.65
USB Debugging ticked
Fast boot deticked
HTC cable used
Latest drivers installed
Any help would be appreciated, the only previous experince I have is rooting a Galaxy note and tablet with no trouble whatsoever.
tj
Click to expand...
Click to collapse
Do you have fastboot.exe on your computer? It looks like CMD isn't finding fastboot.exe 1-because you don't have it 2- because you have not started your cmd prompt from your fastboot.exe folder
can you post a screenshot of your cmd prompt when you get this error?
ADB Installer
Installed ADB Installer and now been able to copy and been able to submit my token.
Recieved email reply with unlock code and it came as a VLC icon, still put this onto my phone but now get message 'unable to open bin file'
Got one step further but now unable to open file.
Below is the message I get:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\tjpearson>fastboot flash unlocktoken Unlock_code.bin
error: cannot open 'Unlock_code.bin'
C:\Users\tjpearson>
Your help is very much appreciated but my wife fails to understand my pannick and she thinks out tea is more important so may not get back to you straight away.
tj
tjpearson said:
Installed ADB Installer and now been able to copy and been able to submit my token.
Recieved email reply with unlock code and it came as a VLC icon, still put this onto my phone but now get message 'unable to open bin file'
Got one step further but now unable to open file.
Below is the message I get:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\tjpearson>fastboot flash unlocktoken Unlock_code.bin
error: cannot open 'Unlock_code.bin'
C:\Users\tjpearson>
Your help is very much appreciated but my wife fails to understand my pannick and she thinks out tea is more important so may not get back to you straight away.
tj
Click to expand...
Click to collapse
Think you need to open the command prompt in the adb folder, and also have the unlock_code.bin in that same folder.
mb_guy said:
Think you need to open the command prompt in the adb folder, and also have the unlock_code.bin in that same folder.
Click to expand...
Click to collapse
OK, I'll try this tomorrow, thanks for the help.
Originally Posted by mb_guy
Think you need to open the command prompt in the adb folder, and also have the unlock_code.bin in that same folder.
Click to expand...
Click to collapse
OK, I'll try this tomorrow, thanks for the help.
Click to expand...
Click to collapse
Like mb_guy said, you MUST place the bin file in the same folder where adb and fastboot are. Every time you want to flash a file to your phone it must be in that folder, otherwise fastboot won't find it and it will output you that error (can't open file). That rule apply to recovery, unlock code, rom, kernel, ruu, firmware etc etc.
Sent from my HTC One using xda app-developers app
alray said:
Like mb_guy said, you MUST place the bin file in the same folder where adb and fastboot are. Every time you want to flash a file to your phone it must be in that folder, otherwise fastboot won't find it and it will output you that error (can't open file). That rule apply to recovery, unlock code, rom, kernel, ruu, firmware etc etc.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Thanks for the help because at least I've now been able to unlock bootloader.
My problem now is 'fastboot flash recovery openrecovery-twrp-2.6.3.0-m7.img' command line and yet again I'm getting error unable to open as below;
C:\Users\tjpearson>fastboot flash recovery openrecovery-twrp-2.6.3.0-m7.img
error: cannot open 'openrecovery-twrp-2.6.3.0-m7.img'
Even placing zip on root of phone and in adb folder still no joy.
tj
tjpearson said:
Thanks for the help because at least I've now been able to unlock bootloader.
My problem now is 'fastboot flash recovery openrecovery-twrp-2.6.3.0-m7.img' command line and yet again I'm getting error unable to open as below;
C:\Users\tjpearson>fastboot flash recovery openrecovery-twrp-2.6.3.0-m7.img
error: cannot open 'openrecovery-twrp-2.6.3.0-m7.img'
Even placing zip on root of phone and in adb folder still no joy.
tj
Click to expand...
Click to collapse
''error: cannot open'' is caused because fastboot don't find the file. Is the recovery file you are trying to flash is named exactly <openrecovery-twrp-2.6.3.0-m7.img> ?
Btw I'll recommend you to flash twrp 2.6.3.3 not 2.6.3.0 as you could have issur flashing newer 4.4 rom
Code:
fastboot flash recovery <name_of_file.img>
fastboot erase cache
fastboot reboot-bootloader
alray said:
''error: cannot open'' is caused because fastboot don't find the file. Is the recovery file you are trying to flash is named exactly <openrecovery-twrp-2.6.3.0-m7.img> ?
Btw I'll recommend you to flash twrp 2.6.3.3 not 2.6.3.0 as you could have issur flashing newer 4.4 rom
Code:
fastboot flash recovery <name_of_file.img>
fastboot erase cache
fastboot reboot-bootloader
Click to expand...
Click to collapse
Yes, named exactly the same.
It's driving me mad, if the bootloader is now unlocked is there an easier way to flash twrp and then root.
Whats the best way to check adb is actually communicating with the phone
tj
tjpearson said:
Yes, named exactly the same.
It's driving me mad, if the bootloader is now unlocked is there an easier way to flash twrp and then root.
Whats the best way to check adb is actually communicating with the phone
tj
Click to expand...
Click to collapse
Do you have a Sprint phone ? and can you post a screen shot of your adb / fastboot folder containing the files or at least post your results for dir
open command prompt from your adb / fastboot folder (shift+right click - command prompt here)
type
adb devices
your device SN will be here
type
adb reboot bootloader
you should be in fastboot usb
type
fastboot devices
again your serial no should be here
type dir
you should see the contains of the folder your in
now
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
if error change the twrp name to match the one in the dir command above
clsA said:
Do you have a Sprint phone ? and can you post a screen shot of your adb / fastboot folder containing the files or at least post your results for dir
open command prompt from your adb / fastboot folder (shift+right click - command prompt here)
type
adb devices
your device SN will be here
type
adb reboot bootloader
you should be in fastboot usb
type
fastboot devices
again your serial no should be here
type dir
you should see the contains of the folder your in
now
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
if error change the twrp name to match the one in the dir command above
Click to expand...
Click to collapse
I seem to have a problem adb detecting the connected phone, I'll unistall and start again and if I can then get back to you later I'd appreciate it very much.
The phone is UK on 02 Android 4.4 HTC Sense version 5.5
tj
tjpearson said:
I seem to have a problem adb detecting the connected phone, I'll unistall and start again and if I can then get back to you later I'd appreciate it very much.
The phone is UK on 02 Android 4.4 HTC Sense version 5.5
tj
Click to expand...
Click to collapse
can you check my guide under faq #2, if that solves it
Well, think I'll give up with rooting my HTC One, I have never had so much trouble routing a divice as this. My bootloader is now unlocked and that's about as far as I get.
My phone seems to have been detected once through adb that then allowed me to run unlock token but everything else just fails.
In one last attempt I've attached image of ADB folder and below is result from command line.
It must be my age because evertybing seems so complex nowadays
C:\Android>fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
target reported max download size of 1526722560 bytes
error: cannot load 'openrecovery-twrp-2.6.3.3-m7.img': No error
C:\Android>
tjpearson said:
Well, think I'll give up with rooting my HTC One, I have never had so much trouble routing a divice as this. My bootloader is now unlocked and that's about as far as I get.
My phone seems to have been detected once through adb that then allowed me to run unlock token but everything else just fails.
In one last attempt I've attached image of ADB folder and below is result from command line.
It must be my age because evertybing seems so complex nowadays
C:\Android>fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
target reported max download size of 1526722560 bytes
error: cannot load 'openrecovery-twrp-2.6.3.3-m7.img': No error
C:\Android>
Click to expand...
Click to collapse
cannot load = MyFileNameIsWrong
and from the screenshot you posted the filename is: openrecovery-twrp-2.6.3.3-m7.img.img <- yes, double extension, next time do a "dir" in command prompt to see your filenames, not in Windows Explorer.
d -darrrrr
nkk71 said:
cannot load = MyFileNameIsWrong
and from the screenshot you posted the filename is: openrecovery-twrp-2.6.3.3-m7.img.img <- yes, double extension, next time do a "dir" in command prompt to see your filenames, not in Windows Explorer.
Click to expand...
Click to collapse
I love you nkk71, I really can't tell you how much I love you but I do !!!!! :victory:
Did what you said and fumbled through flashing twrp and then adding superuser after to the phones root, did recovery again and installed superuser via twrp and bingo, rooted and confirmed.
Been struggling 2 weeks with this and non stop all weekend, my wife wants a divorce but I don't care cos I'M ROOTED !!
Thanks so much for all the help, nice one :good:
tj
tjpearson said:
I love you nkk71, I really can't tell you how much I love you but I do !!!!! :victory:
Did what you said and fumbled through flashing twrp and then adding superuser after to the phones root, did recovery again and installed superuser via twrp and bingo, rooted and confirmed.
Been struggling 2 weeks with this and non stop all weekend, my wife wants a divorce but I don't care cos I'M ROOTED !!
Thanks so much for all the help, nice one :good:
tj
Click to expand...
Click to collapse
Lol
Now that the phone is good, go spend some time with your better half!!!
No guides on xda, on "how to return my marriage to stock"
Put the phone on the charger or something, and spend time with your significant other.
Sent from my HTC One using Tapatalk
One last question
nkk71,
Can I uninstall Superuser now and install SuperSU instead cos I've already purchased that when had the Note rooted or will it cause me more time away from the mrs with issues.
tj
tjpearson said:
nkk71,
Can I uninstall Superuser now and install SuperSU instead cos I've already purchased that when had the Note rooted or will it cause me more time away from the mrs with issues.
tj
Click to expand...
Click to collapse
Shouldn't be a problem, use the flashable zip from the thread: http://forum.xda-developers.com/showthread.php?t=1538053
Yeah , sorted.
Thanks again for all your help.
tj
Related
Hi guys, I have a problem.
I want to flash my N1 with the Cyanogenmod, but I have a problem with Bootloader unlocking. I do exactly what here is written (in the N1 guide from wiki.cyanogenmod), but when I open CMD (win XP) and write "fastboot oem unlock", it just doesn't works, but "adb devices" works and shows my phone. What can I do ? Any ideas ?
You need to boot into bootloader to work with fastboot. And if "adb devices" shows your phone - you obviously didn't boot.
adb reboot bootloader
Click to expand...
Click to collapse
Also, for a more comprehensive guide, please read the Wiki.
Code:
C:\fastboot>fastboot oem unlock
'fastboot' is not recognized as a
operable program or batch file.
This is what it shows in bootloader mode.
P.S. I have already re-installed my drivers. I have to notice that when I try to reinstall the drivers (in fastboot mode), they always auto-install themselves and when I try to update them, they say that there isn't newer version.
Fastboot executable isn't in the same directory as ADB executable, and isn't in the path you're executing it from (which is C:\fastboot).
Check, what is the actual executable you're trying to run, and if you have one. It might be called fastboot-windows.exe, if you didn't get it from downloading the Android SDK.
There is a executable file named "fastboot-windows.exe", but when I try to run it, it just open and close for 1 second. Any ideas ?
I thought the message would be clear by now... Oh well.
Open command prompt.
Run:
fastboot-windows oem unlock
Click to expand...
Click to collapse
I think It's done but my computer shows this message (see attached) 5 mins and I don't know it's ready or not ? Could I turn on the phone ? (Sry for the easy questions but I'm a real noob, because that's my 1st Android phone.)
The "too many links" message doesn't look good.
Reboot your computer.
Reboot the phone.
Use different USB port in your computer.
Ok well if you want my input try "fastboot devices" this should return your S/N (starting with "HT") if it gives you the same error then I would reinstall the SDK.
After i have put in the Superuser-3.1.3-arm-signed.zip in the phone så did i get the app Superuser.
Type in adb.exe shell and press enter
You should get $ meaning adb has connected to your phone.
This is the problem
The commond promt say that i not are connected to the phone,is this normal
I restart the phone to normal mode with the sim card in.
The problem is now that i can not call with the phone,is this normal
Do i need to put up a new rom ex Lacoste_ModV5Incredible S_03.05
Would need more details.. ROM??? Bootloader?? Etc etc..
Sent from my HTC Incredible S
mafie said:
Would need more details.. ROM??? Bootloader?? Etc etc..
Sent from my HTC Incredible S
Click to expand...
Click to collapse
The phone is unlocked (that did i fix)
Vivo pvt ship s-on
Hboot-2.02.0002
Radio-3831.18.00.11_m
emmc-boot
May 22 2012314,22:08
I have done everything and even 5. Install Superuser and Test Root Access
Is this something i need to do,to get the phone working
"EXTREMELY IMPORTANT IF YOU ARE PLANNING TO STOP GUIDE HERE. LIKE REALLY IMPORTANT!!!!!!!!!!!!!!!!!!!!!!!
At this point you will be able to flash most ROMs. The exceptions are the one that require S-OFF (the ROM requirements in the thread will state so). Also you will have to flash the boot.img manually
To do this download your select ROM. Extract the boot.img to where you have the fastboot.exe, adb.exe, and AdbWinApi.dll (you should have gotten these 3 files when you unlocked the bootloader). Then open the command window (shift, right click, open command window here) and type:
fastboot flash boot boot.img
the boot.img can be renamed to whatever you would like. I keep all my boot images and the fastboot.exe, adb.exe, and AdbWinApi.dll in 1 folder because i download a lot of ROMs. If you do rename the boot.img, i suggest renaming it to the name of the ROM its for. When you type in the fastboot command, just remember to put the .img at the end. This is necessary or it will not work.
If you want to gain S-OFF continue through the guide.
Is this what you want to know"
If i should to that what room are then talking about (it is ex Lacoste that i want to have)
Thanks for the help you are so kind
Factasy said:
After i have put in the Superuser-3.1.3-arm-signed.zip in the phone så did i get the app Superuser.
Type in adb.exe shell and press enter
You should get $ meaning adb has connected to your phone.
This is the problem
The commond promt say that i not are connected to the phone,is this normal
I restart the phone to normal mode with the sim card in.
The problem is now that i can not call with the phone,is this normal
Do i need to put up a new rom ex Lacoste_ModV5Incredible S_03.05
Click to expand...
Click to collapse
It means there is an issue with your ADB drivers.
Did you flash the .zip in recovery?
Did you navigate to the right file in command prompt?
Does your device have Android Debugging enabled?
Is your phone connected to the computer?
Guess u must have not installed the HTC sync drivers..try doing that..
Sent from my HTC Incredible S
mafie said:
Guess u must have not installed the HTC sync drivers..try doing that..
Sent from my HTC Incredible S
Click to expand...
Click to collapse
I took the driver from this page http://forum.xda-developers.com/showthread.php?t=2089508
I have Windows 7
C:\android>adb.exe shell
error: device not found
072665995 said:
It means there is an issue with your ADB drivers.
Did you flash the .zip in recovery?
Did you navigate to the right file in command prompt?
Does your device have Android Debugging enabled?
Is your phone connected to the computer?
Click to expand...
Click to collapse
Yes Debugging enabled
No Did you flash the .zip in recovery?
Yes Did you navigate to the right file in command prompt?
Yes Is your phone connected to the computer?
I did Everything in the guide http://forum.xda-developers.com/showthread.php?t=2118187
And i did 5. Install Superuser and Test Root Access
It is here the problems came
I have solved the
C:\android>adb.exe shel
[email protected]:/ $ su Now
But i cant dail with the phone why
Factasy said:
Yes Debugging enabled
No Did you flash the .zip in recovery?
Yes Did you navigate to the right file in command prompt?
Yes Is your phone connected to the computer?
I did Everything in the guide http://forum.xda-developers.com/showthread.php?t=2118187
And i did 5. Install Superuser and Test Root Access
It is here the problems came
Click to expand...
Click to collapse
Factasy said:
I have solved the
C:\android>adb.exe shel
[email protected]:/ $ su Now
But i cant dail with the phone why
Click to expand...
Click to collapse
The guide says to flash the superuser zip in recovery... Let's start with that first.
As to your dialer not working, reflash the ROM if its custom. If its stock, don't bother with it and just flash a custom ROM later.
072665995 said:
The guide says to flash the superuser zip in recovery... Let's start with that first.
As to your dialer not working, reflash the ROM if its custom. If its stock, don't bother with it and just flash a custom ROM later.
Click to expand...
Click to collapse
I noticed a funny thing.
I only have 3 g on your mobile now no gsm networks
And how do i flash the superuser zip in recovery. Maby i are blind
I have allready the superuser installed in the phone
Ok here is the skinny. I have the Sprint HTC 1. Currently rooted and running Beanstalk 4.3 and TWRP 2.5 ... I have read, re read, and read again how to update my TWRP to 2.6.3 and have no luck.
I have tried Terminal Emulator
I have tired Goo Manager. It actually down loads the file. Runs through the process. Never reboots or updates
I have tried Fastboot. For what ever reason my computer does not pick up and adb devices. It shows Fastboot USB
Any thoughts. I had some unlock this one for me and throw TWRP on. All my others I have done myself.
I love TWRP..but if I cannot fix...what is the easiest way to put Philz or CWM on instead?
Want to update a ROM to 4.4 Kitkat but cannot with out an updated recovery
jaykspokane said:
Ok here is the skinny. I have the Sprint HTC 1. Currently rooted and running Beanstalk 4.3 and TWRP 2.5 ... I have read, re read, and read again how to update my TWRP to 2.6.3 and have no luck.
I have tried Terminal Emulator
I have tired Goo Manager. It actually down loads the file. Runs through the process. Never reboots or updates
I have tried Fastboot. For what ever reason my computer does not pick up and adb devices. It shows Fastboot USB
Any thoughts. I had some unlock this one for me and throw TWRP on. All my others I have done myself.
I love TWRP..but if I cannot fix...what is the easiest way to put Philz or CWM on instead?
Want to update a ROM to 4.4 Kitkat but cannot with out an updated recovery
Click to expand...
Click to collapse
While in fastbootusb check your drivers
Device not recognized? (If you are using Windows 8.1 this will most likely not work)
On your PC go to device manager and find your phone(usually M7WLS), right click and select properties
Select the driver tab
Select update driver
Select browse my comp
Let me pick
Look for ADB USB device or similar should be one of the first couple choices
Select MyHTC install and you should be good
BD619 said:
While in fastbootusb check your drivers
Device not recognized? (If you are using Windows 8.1 this will most likely not work)
On your PC go to device manager and find your phone(usually M7WLS), right click and select properties
Select the driver tab
Select update driver
Select browse my comp
Let me pick
Look for ADB USB device or similar should be one of the first couple choices
Select MyHTC install and you should be good
Click to expand...
Click to collapse
Updated the drives. In Fastboot now. on my cmd prompt c:\user\user wont tried typing and ADB Devices and nothiing
In fastbootusb type fastboot devices
BD619 said:
In fastbootusb type fastboot devices
Click to expand...
Click to collapse
Now I am thinking it it my computer. Just re enstalled the SDK packet. Changed path to all c:/Android-ADB and says not a recognizable internal or external file
At this point I need some sleep. Eyes are going crossed.
jaykspokane said:
Now I am thinking it it my computer. Just re enstalled the SDK packet. Changed path to all c:/Android-ADB and says not a recognizable internal or external file
At this point I need some sleep. Eyes are going crossed.
Click to expand...
Click to collapse
PM me tomorrow and I'll help you out
BD619 said:
PM me tomorrow and I'll help you out
Click to expand...
Click to collapse
Sorry been a crazy new year. Still need help.
So downloaded SDK pack. I have tried ADB shell. Fastboot ... etc etc. When in Fastboot I run ADB Devices and nothing is found. however if i have the phone on it works.
at this point...maybe a new recovery?
jaykspokane said:
Sorry been a crazy new year. Still need help.
So downloaded SDK pack. I have tried ADB shell. Fastboot ... etc etc. When in Fastboot I run ADB Devices and nothing is found. however if i have the phone on it works.
at this point...maybe a new recovery?
Click to expand...
Click to collapse
While in bootloader/fastbootusb type fastboot devices
adb devices =OS and recovery
fastboot devices = bootloader/fastbootusb
BD619 said:
While in bootloader/fastbootusb type fastboot devices
adb devices =OS and recovery
fastboot devices = bootloader/fastbootusb
Click to expand...
Click to collapse
Ok... recognized a device was attached. So type the following
fastboot flash recovery openrecovery-twrp-2.6.3.0-m7wls.img
and I got error cannot open 'openrecovery-twrp-2.6.3.0-m7wls.img'
This is TWRPS guidelines
Download the above file into your platform-tools dir. Turn off your device. Turn on the device and keep holding volume down until a menu shows up. Select fastboot from the menu list. Plug the device into your computer. If you have the right drivers installed, your screen should now say FASTBOOT USB. Run the following command via the command line:
fastboot flash recovery recoveryfilename.img
Note that you will need to change the last part to match the name of the file that you just downloaded. This method requires that you have the drivers installed that come with the HTC Sync software that are available here. You will also need adb and fastboot for your computer.
jaykspokane said:
Ok... recognized a device was attached. So type the following
fastboot flash recovery openrecovery-twrp-2.6.3.0-m7wls.img
and I got error cannot open 'openrecovery-twrp-2.6.3.0-m7wls.img'
This is TWRPS guidelines
Download the above file into your platform-tools dir. Turn off your device. Turn on the device and keep holding volume down until a menu shows up. Select fastboot from the menu list. Plug the device into your computer. If you have the right drivers installed, your screen should now say FASTBOOT USB. Run the following command via the command line:
fastboot flash recovery recoveryfilename.img
Note that you will need to change the last part to match the name of the file that you just downloaded. This method requires that you have the drivers installed that come with the HTC Sync software that are available here. You will also need adb and fastboot for your computer.
Click to expand...
Click to collapse
Try
fastboot erase cache <enter>
then
fastboot flash recovery openrecovery-twrp-2.6.3.0-m7wls.img <enter>
You did install the android sdk right?
BD619 said:
Try
fastboot erase cache <enter>
then
fastboot flash recovery openrecovery-twrp-2.6.3.0-m7wls.img <enter>
You did install the android sdk right?
Click to expand...
Click to collapse
I did. Just to make certain the other night...I down loaded the Android SDK pack. i can run ADB and Fastboot. Pulls all the info etc.
Will try erase cache
jaykspokane said:
I did. Just to make certain the other night...I down loaded the Android SDK pack. i can run ADB and Fastboot. Pulls all the info etc.
Will try erase cache
Click to expand...
Click to collapse
What does this mean?
BD619 said:
What does this mean?
Click to expand...
Click to collapse
Sorry. Meant it just lists all the available command for each respectively...lists the commands etc.
So did the erase and still same error.
All my apps and data are backed up on Titanium. How hard would it be to just have a new recovery installed?
jaykspokane said:
Sorry. Meant it just lists all the available command for each respectively...lists the commands etc.
So did the erase and still same error.
All my apps and data are backed up on Titanium. How hard would it be to just have a new recovery installed?
Click to expand...
Click to collapse
Navigate to the platform tools folder
Press shift and right click inside the folder and choose open cmd here
jaykspokane said:
Sorry. Meant it just lists all the available command for each respectively...lists the commands etc.
So did the erase and still same error.
All my apps and data are backed up on Titanium. How hard would it be to just have a new recovery installed?
Click to expand...
Click to collapse
May be a moot point. I am upgrading to a Team Nocturnal_xR1 which is a 4.4 ROM. So far it has been loading and allowed the file on a TWRP 2.5.0.0 version. I still need to upgrade the TWRP version. Right now looks like it may work.
jaykspokane said:
May be a moot point. I am upgrading to a Team Nocturnal_xR1 which is a 4.4 ROM. So far it has been loading and allowed the file on a TWRP 2.5.0.0 version. I still need to upgrade the TWRP version. Right now looks like it may work.
Click to expand...
Click to collapse
back to square one. LOL.
and no opening cmd from there did not work either
Check PM
I had a similar issue where I needed the updated twrp. I ended up using the original AIO toolkit that I used to root the phone/unlock the phone to begin with.
I found the latest version of the AIO (made by Hasoon: http://www.hasoon2000.info/getdownl...obile,ATT,Sprint)/One_All-In-One_Kit_v3.1.rar) and the latest image of TWRP from here: http://teamw.in/twrp_view_all_devices.
After installing hasoon, stick the downloaded image in the data/recoveries folder w/in the folders from the AIO. Next use the "Your Own Recovery" option under the flash a recovery option and choose that image instead. Worked great for me several times. Hopefully it does for you. Let me know if you have question.
BD619 said:
Check PM
Click to expand...
Click to collapse
When I normally plug my htc one into my laptop that is running win 8.1 64 bit. It shows that my phone is connected and opens files for me to view What is on my phone. When I'm in boot loader and I plug it in (I'm trying to unlock it to root) I hear the notification sound that the phone is connected to computer but the file box doesn't open showing me what's on the phone. Is this normal? If so, how do I open cmd prompt to type in OEM command and what should the command initially say before I type my oem command? Thanks for any help you can give.
dcm1200 said:
When I normally plug my htc one into my laptop that is running win 8.1 64 bit. It shows that my phone is connected and opens files for me to view What is on my phone. When I'm in boot loader and I plug it in (I'm trying to unlock it to root) I hear the notification sound that the phone is connected to computer but the file box doesn't open showing me what's on the phone. Is this normal? If so, how do I open cmd prompt to type in OEM command and what should the command initially say before I type my oem command? Thanks for any help you can give.
Click to expand...
Click to collapse
You will not see you data in bootloader mode. What is your bootloader version? You will not be able to send fastboot commands using windows 8.1 with hboot 1.44.
open the cmd prompt from your adb/fastboot.exe folder and type
Code:
fastboot devices
and see if the device is recognized by your computer
and go see those video guide here: http://forum.xda-developers.com/htc-one#root
Be sure to use the latest htc drivers and latest android sdk (abd/fastboot)
And again, you will not be able to use fastboot with a win8.1 computer if your bootloader is 1.44
dcm1200 said:
When I normally plug my htc one into my laptop that is running win 8.1 64 bit. It shows that my phone is connected and opens files for me to view What is on my phone. When I'm in boot loader and I plug it in (I'm trying to unlock it to root) I hear the notification sound that the phone is connected to computer but the file box doesn't open showing me what's on the phone. Is this normal? If so, how do I open cmd prompt to type in OEM command and what should the command initially say before I type my oem command? Thanks for any help you can give.
Click to expand...
Click to collapse
Sorry mate but I will not troubleshoot via PM because its too much confusing and other members can't help you if you send me pm. Keep posting here it will be much easier. Hope you understand
QUOTE=alray;50379334]Sorry mate but I will not troubleshoot via PM because its too much confusing and other members can't help you if you send me pm. Keep posting here it will be much easier. Hope you understand [/QUOTE
But after flashing twrp recovery and copying supersu to internal storage I erased cache in cms before going into recovery mode then unzipped supersu and rebooted phone. I opened super su and said that there is no binary file or that it is not working. I also dl'ed a root checker and it said that I'm not rooted. Any ideas on what to do now?
dcm1200 said:
QUOTE=alray;50379334]Sorry mate but I will not troubleshoot via PM because its too much confusing and other members can't help you if you send me pm. Keep posting here it will be much easier. Hope you understand [/QUOTE
But after flashing twrp recovery and copying supersu to internal storage I erased cache in cms before going into recovery mode then unzipped supersu and rebooted phone. I opened super su and said that there is no binary file or that it is not working. I also dl'ed a root checker and it said that I'm not rooted. Any ideas on what to do now?
Click to expand...
Click to collapse
install superSU.zip the same as you install a rom in recovery
clsA said:
install superSU.zip the same as you install a rom in recovery
Click to expand...
Click to collapse
Please pardon my ignorance but I'm new to this. How? Is it the same basic way that I flashed twrp to my phone?
hey guys i have a brand new TF701T an im desperately trying to install a custom ROM before i get into using it..
IM trying to install the ROM from http://forum.xda-developers.com/showthread.php?t=2608129&page=30
The first step of manually updating to 10.26.1.18 JB3 is done and I'm now stuck on the CWM step.
I have The ROM and recovery IMG downloaded and im unsure what to do next...Ive googled first and cant really figure it out..
sorry for my newb question but if someone can take pity on me and direct me i will forever be in your debt!!
Put FASTBOOT.EXE and RECOVERY.IMG in the same file.. this i can understand
but........
''Right click + shift on the folder they are in and choose open command prompt here
Boot into the Bootloader by either booting with the Power and Volume Down Buttons held down until you get the 3 icons or by typing the following into the command prompt.
Code:
adb reboot bootloader
Then type the following commands to flash the recovery image:
Code:
fastboot flash recovery recovery.img
fastboot reboot-bootloader''
Is where im lost..
please hgelp..anyone
please..anyone?
Are you unlocked?
Which part is it you don't understand? Opening the cmd prompt?
In Win7 & 8 if you hold the shift key and right click you get a contedt menu with the option to open a command prompt here.
You do have fastboot and adb drivers installed right?
Search XDA for adb fastboot tutorial. Thrre are several very good ones..
Have you managed to get the command prompt open?
sbdags said:
Have you managed to get the command prompt open?
Click to expand...
Click to collapse
In my original post i said i understood 'Have recovery.img & fastboot.exe' in the same file but it turns out i didnt even know what the 'fastboot.exe' was!! I thought it was just another name for the ROM.zip..
SO>> The problem was that i didnt know about the whole android SDK/ platforms tools/ ADB pushing Step..:crying:
after i installed android SDK on my computer and saw the fastboot.exe in the platform tools folder, everything made much more sense
I guess for most guys here it is common knowledge...but not for me. The ROM instructions didnt really specify this clearly nor did the CWM's link instructions.
I wasted 2 days trying to do it but WOW it was worth it..your chromi x ROM is amazing! great job! I've also learned a useful skill for the future so no complaints here