Hello Everyone,
New to the rooting Droids, but have an understanding of them. I have jailbroken all Apple products which i got tired of. Now i finally got myself the New DNA phone with verizon. my dilemma is i dont know how to get the bootloader unlocked http://forum.xda-developers.com/showthread.php?t=2109862 i read through this link on how to do so. but it just gives u the link to download the apk file but no idea on what to do next with it? which also ive been reading off this site how to root my phone. http://forum.xda-developers.com/showthread.php?t=2000896
I need of a bit of help if anyone has a min to help me that would be great.
what i dont understand off the first link what to do with the apk file do i put the zip file right on my DNA drive? or run it off the pc?? if so what programs do i need on my computer to unlock my bootloader.
"
What you need:
1.) a Droid DNA
2.) this attached APK
Instructions:
1.) Download apk (attached, cid.apk)
2.) run it (in your app drawer titled HTC DNA SuperCID
3.) reboot to bootloader and confirm you have SuperCID:
a.) fastboot oem readcid
"
that is all the post contains on how to get the supercid?
thanks again!
1. Access XDA from your phone and download the app. (It will show up in your downloads)
2. Install the app by opening it
3. Here's where I believe your main issue/question is. You need Android SDK, if you don't have it installed you can get it Here
4. Follow the instructions and set that up
5. Hold your power button and down on the volume rocker till your phone goes into the bootloader.
6. Plug your phone into your computer
7. While in CMD Prompt type Fastboot oem readcid and hit enter.
8. if you get a response along the lines of 111111 you're good to go.
9. Head over to HTCDev.com and follow the steps they give you
10. After following those steps your bootloader will be Unlocked
11. Flash CWM or TWRP (recoveries) [There are instructions in those threads on how to do that]
12. You should then be good to go and flash ROM's, etc.
access the XDA from the first link? i posted?? on myphone?
ok downloaded to my phone and installed the Apk file
Yes. From your phone go to the link with the apk. Click on the download for that apk, and it will show up on your phone.
ok i now i have it installed and booted to the bootloader screen, which i selected fastboot, and now i have the CMD open but the command you told me to input doesnt work just error message saying "fastboot" is not recongnized. i also have the adt extracted on my desktop.
xd4v3x said:
ok i now i have it installed and booted to the bootloader screen, which i selected fastboot, and now i have the CMD open but the command you told me to input doesnt work just error message saying "fastboot" is not recongnized. i also have the adt extracted on my desktop.
Click to expand...
Click to collapse
Fastboot is an ADB command. Did you install the android SDK to your computer, and follow the guide on how to set it up?
Edit:
Here's a guide on how to setup the SDK Guide
yes it completly installed for the APK software, so i used the "abd" command instead of the word fastboot?
xd4v3x said:
yes it completly installed for the APK software, so i used the "abd" command instead of the word fastboot?
Click to expand...
Click to collapse
Did you set the platform-tools folder to the root of your C: Drive? ADB (my bad, not ABD) uses commands. Fastboot is one of the commands it uses to talk to the phone. If you don't set it up correctly the command: Fastboot will not be recognizable. Double check with the guide I posted, that you have everything correctly setup.
yes i have it in C:\android-sdk-windows
but all i see in the folder is .metadata....
xd4v3x said:
yes i have it in C:\android-sdk-windows
but all i see in the folder is .metadata....
Click to expand...
Click to collapse
Ok, a couple questions...
1. Did you install HTC Sync? That installs the HTC drivers to your computer.
2. What version of Windowns (if you're on windows) are you running?
Yes i install the htc sync and i am running windows 7 x64.
xd4v3x said:
Yes i install the htc sync and i am running windows 7 x64.
Click to expand...
Click to collapse
Ok, go into the sdk folders. There should be a little android icon that says Android SDK or something along those lines. Open that up and it should ask you if you want to install some drivers. You need to install those. Once you do that everything should work.
OverDroid5 said:
Ok, go into the sdk folders. There should be a little android icon that says Android SDK or something along those lines. Open that up and it should ask you if you want to install some drivers. You need to install those. Once you do that everything should work.
Click to expand...
Click to collapse
I have thanked a couple of your posts because the OP hasn't and you have gone out of your way
ok so far what I have setup:
installed phone drivers on the wndows 7 - htc sync.
installed the CID.apk file on my phone.
installed the sdk software on my windows 7 64bit.
I reboot the phone to the bootloader screen.
but cant get the command prompt to work by using the "fast oem readcid"
what am I missing? I keep getting an error when running that command.
thanks again for everyone help so far.
You have to be in a folder that has the fastboot.exe file. Or you need to update your windows path so it recognizes the android sdk folders.
Your best bet is to create a new folder in C:\. For example C:\HTCbootloader. Then copy fastboot.exe, adb.exe, and AdbWinApi.dll into it. Then when you run 'cmd', type 'cd HTCbootloader'. From that point you should be able to type 'fastboot oem readcid'.
thanks I try that when I get home.
betterthancrimzon said:
You have to be in a folder that has the fastboot.exe file. Or you need to update your windows path so it recognizes the android sdk folders.
Your best bet is to create a new folder in C:\. For example C:\HTCbootloader. Then copy fastboot.exe, adb.exe, and AdbWinApi.dll into it. Then when you run 'cmd', type 'cd HTCbootloader'. From that point you should be able to type 'fastboot oem readcid'.
Click to expand...
Click to collapse
This is correct. Also to setup a set path that you can access anywhere.
1. Right click on "Computer"
2. Go to properties
3. Click on Advanced System Settings
4. Click on Environmental Variables
5. In System Variables, Scroll to PATH
6. Select it and hit Edit
7. Do not change anything, in the current string, instead go to the very end
8. No spaces from where it ends. ;C:\(whatever you named the file with fastboot.exe, adb.exe, and AdbWinApi.dll)
9. Click ok, and you have a path setup, so no matter where you access cmd prompt from you can use adb commands.
I apologize by attempting to hijack this thread but the advice in here is superb... Alright gentleman I could use some help, I got my code from HTC and have followed the instructions with the utmost precision including the verification of my paths (using the same folder from the previous CMD during the unlock process) but no matter what I do I get the error...
"cannot load *** bin unknown error". Any ideas?
ok so i finally got the fastboot oem readcid, and it read 11111111 so im in a good spot so far.. but now i dont see any where, on whats the command to get the token. on this forum page. http://forum.xda-developers.com/showthread.php?t=2000896
thanks again!
xd4v3x said:
ok so i finally got the fastboot oem readcid, and it read 11111111 so im in a good spot so far.. but now i dont see any where, on whats the command to get the token. on this forum page. http://forum.xda-developers.com/showthread.php?t=2000896
thanks again!
Click to expand...
Click to collapse
Ok, Now that you have it reading 11111111 head over to HTCdev.com and follow the steps there. You're going to go to unlock bootloader and select other supported devices. It will guide you on how to get the token as well as how to unlock the bootloader.
Related
THIS IS STRICTLY A GUIDE TO PRE-PARE YOU ON HOW TO SET-UP ANDROID SDK AND ADB DEVICES(DRIVERS), IF YOU ALREADY HAVE THAT SET-UP YOU CAN SKIP TO EUGENE'S POST ON HOW TO ROOT MYTOUCH SLIDE.
Last Updated:6/29/2010 at 11:36PM
Any other issues to deal with the actual process to root your mytouch slide should be directed toward his thread. Thank you for reading.
Okay so after about 4 hours of reading and asking questions I finally got my device rooted. My biggest problem doing this was that the guide in this forum was basically showing you how to root the phone if you had previous experience with androids and android SDK which I did not.
Note: If you have SDK installed already on your pc please delete your SDK folder and start from scratch for best results with my guide.
1. download Android SDK.(You will not have to use Android SDK physically but you will need it installed on your pc to root your phone) Save it to your PC where you can find it.
2.Extact the .zip file, do not rename just yet for the sake of my guide you also may delete the .zip file of it to keep clean.
3a. Move android-sdk-windows* out of the android-sdk_r06-windows folder onto the root of your C:/ drive.
*=the name of the folder may be different if you use a different operating system but since I do not own the other systems I cannot really tell you what the folders name.
3b.Now that you have the folder in the correct place you can rename the folder from "SDK-Anroid-Windows" to something easier such as "SDK" "Android" or something else which you will remember has to do with SDK.
This next part is not required, if you do not feel comfortable doing this, then don't, there is other ways around this.
3c.You also have the option to change your the path of your directory on your system. To do this, follow the instrustion here on step 2.( I would like to thank fermunky for his input)
My directory was pointed to the C:/Program files so I switched it to C:/android/tools , for those who do not know what this does it simply makes it so you do not have to change directory in step 7 (CD), you will only have to open your command prompt and then your ready to enter "ADB devices" .
4.Install the correct ADB drivers from pdanet . Select the proper download based on your OS if you do not know what bit you are using click start, right click computer, click properties, the system type will show you the proper file to download. and save it to your computer where you can find it.
5.Start the installation process for the ABD drivers, Follow the on-screen directions to install the drivers ( make sure your phone is not plugged into the pc at this time)
6.Check to see if you did this correctly, plug in your phone and open your comand prompt on your computer and type:
cd C:\android\tools**
**=your file directory might be different than this, it depends what you renamed your folder
then type:
adb devices ( this will now show all the devices connected to an adb devices)
Check to see if your device is listed and connected properly.***
***=If it is correctly connected you will see a device listed and under attached it should say device.
After you have this all set up you are ready to root your phone via the guide from Eugene.****Remember you need to add the contents from his root.zip file into the tools of your SDK folder in order to root your phone.
****=Eugene's guide has changed since I wrote this but you still are ready to follow his steps. I plan on rooting someones slide soon based off his steps and will edit here if I need to add anything)
Thanks for reading.
One thing I did that makes a lot of this a whole lot easier, is to add the directory to your Tools folder to your system's PATH variable, as explained in Step 2 here: http://developer.android.com/sdk/installing.html
What this allows you to do is run the commands with Tools (ADB, fastboot etc) from anywhere within the command prompt, without having to cd to your c:\android-sdk-windows\tools folder. This way, you can put any other update files, into any directory you want.
For example, let say i have update.zip directly on the C drive. I can simply go to command prompt, and just type "cd" and get to the root of the C drive, and then can just run "adb push update.zip /sd/card/". No need to store everything into the tools folder.
fermunky said:
One thing I did that makes a lot of this a whole lot easier, is to add the directory to your Tools folder to your system's PATH variable, as explained in Step 2 here: http://developer.android.com/sdk/installing.html
What this allows you to do is run the commands with Tools (ADB, fastboot etc) from anywhere within the command prompt, without having to cd to your c:\android-sdk-windows\tools folder. This way, you can put any other update files, into any directory you want.
For example, let say i have update.zip directly on the C drive. I can simply go to command prompt, and just type "cd" and get to the root of the C drive, and then can just run "adb push update.zip /sd/card/". No need to store everything into the tools folder.
Click to expand...
Click to collapse
the other guide mentions to create a new variable such as:
For Variable Name type: adb
For Variable Value type: C:\android-sdk-windows\tools
Click to expand...
Click to collapse
so would i follow this? or list that directory under the already-enabled PATH variable?
Yeah just use the existing PATH variable, and only need the path, no need to include variable names.
I think this is a very valuable how-to for the noobs out there and im going to pass this up the chain to get sticky'd. I also posted this in the slide bible. Good job, OP
For the uninitiated, and yes it's common sense
When I was using Windows (as I'm using Ubuntu now), and reading all the adb guides, for ease of use and to prevent people from getting confused, they name the sdk as "android-sdk-windows", which is fine for a newcomer (it's the same for Ubuntu except the "windows" part and the slash direction \ vs. /). However, you can name it whatever you want. You just need to make sure to have the same name in your path. For example, I'm lazy and my typing skills aren't that great. I don't want to type 19 characters (yes, I counted). So I just named it simply "android". 7 characters from 19. Its way more efficient for me. I've contemplated naming it "andy" or something to shorten it further. But, again, you don't even need to name it anything android related. You can choose to name it r2d2 (see what I did there?) if you want! Just my 2 cents. Thanks!
Yeah I could of renamed it something different but I didn't think about that til after it was written, I will fix it as soon as I am on an actual pc. I will also include how to do it via mac and ubuanta(sorry if I miss spelled)
kingofyo1 said:
I think this is a very valuable how-to for the noobs out there and im going to pass this up the chain to get sticky'd. I also posted this in the slide bible. Good job, OP
Click to expand...
Click to collapse
Thanks kingofyo. Glad I could give back to this forum after all it has done for me. And if I find any other helpful tips to help make rooting easier I'll be sure to include it.
Sent from my T-Mobile myTouch 3G Slide using XDA App
fermunky said:
One thing I did that makes a lot of this a whole lot easier, is to add the directory to your Tools folder to your system's PATH variable, as explained in Step 2 here: http://developer.android.com/sdk/installing.html
What this allows you to do is run the commands with Tools (ADB, fastboot etc) from anywhere within the command prompt, without having to cd to your c:\android-sdk-windows\tools folder. This way, you can put any other update files, into any directory you want.
For example, let say i have update.zip directly on the C drive. I can simply go to command prompt, and just type "cd" and get to the root of the C drive, and then can just run "adb push update.zip /sd/card/". No need to store everything into the tools folder.
Click to expand...
Click to collapse
I will leave that as an option for others to pick if they want to do that, as some might not want to change their directory to follow that path.
oo, this cleared up a few things for me! thanks!
eff0rtless said:
oo, this cleared up a few things for me! thanks!
Click to expand...
Click to collapse
ah what pat of seattle do you live in? I live up in mukilteo.
rlacsamana1989 said:
7.Check to see if you did this correctly, plug in your phone and open your comand prompt on your computer and type:
cd C:\android\tools (your file directory might be different than this, it depends what you renamed your folder)
then type:
adb devices ( this will now show all the devices connected to an adb devices)
Check to see if your device is listed and connected properly.
Click to expand...
Click to collapse
when typing in 'adb devices', i get this message:
Code:
adb server is out of date. killing...
* daemon started successfully *
however, it does continue to list my device as attached.
the full message is:
Code:
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
HTxxxxxxxx device
*the x's do represent a valid serial number
-------------------------------------------------------
is this a problem? and will i run into any problems trying to successfully root?
note: i have done a search on this and the results returned as the program DroidExplorer being the culprit, however, i do not have that program installed.
Do you have the most updated Android SDK? And try searching that topic on google and see if you can find people with the same issue.
Sent from my T-Mobile myTouch 3G Slide using XDA App
rlacsamana1989 said:
Do you have the most updated Android SDK? And try searching that topic on google and see if you can find people with the same issue.
Sent from my T-Mobile myTouch 3G Slide using XDA App
Click to expand...
Click to collapse
I believe so. I actually installed of the available packages as per the initial guides instructions. If I needed to uninstall & reinstall the sdk, how would I do that?
As yes I have done a thorough search. I mentioned the results in my original comment.
poetik517 said:
I believe so. I actually installed of the available packages as per the initial guides instructions. If I needed to uninstall & reinstall the sdk, how would I do that?
As yes I have done a thorough search. I mentioned the results in my original comment.
Click to expand...
Click to collapse
You should be able to just delete the folder it downloaded. and make sure you empty your trash. I will look at what the issues can be. and let you know if I find anything. I'm pretty good at that
Edit: Have you seen this post? I'd start from the first thing they say which is going to task manager and ending adb.exe and if that doesn't work go to the next thing they stated to do. If none of those work come back and I will try and figure it out.
Ok so I just got my slide and want root. Im coming from a rooted g1 which has a completely different root process and so I have no experience with sdk and adb sadly. Im running windows 7 and I have followed this guide step-by-step but every time I get to the point where I type "loop" in eugenes guide it says it does not recognize the command... I saw somewhere sdk components are not supported by windows 7. Is this true? And is there a way around it? I also saw somewhere that it could be that I dont have my enviroment variables set correctly. Im not sure by what it means to add the full path to the tools\ directory to the Path variable value. When I double click Path default displays:
%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;%SYSTEMROOT%\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\QuickTime\QTSystem\
Where do I add it?
My tools directory is set in the root of my C drive as
C:\SDK\tools (most people typed android, renamed mine to just SDK, seemed faster)
This is what im trying to figure out at this point. Sorry if it very noobish.. Any help would be greatly appreciated.
cdt82002 said:
Ok so I just got my slide and want root. Im coming from a rooted g1 which has a completely different root process and so I have no experience with sdk and adb sadly. Im running windows 7 and I have followed this guide step-by-step but every time I get to the point where I type "loop" in eugenes guide it says it does not recognize the command... I saw somewhere sdk components are not supported by windows 7. Is this true? And is there a way around it? I also saw somewhere that it could be that I dont have my enviroment variables set correctly. Im not sure by what it means to add the full path to the tools\ directory to the Path variable value. When I double click Path default displays:
%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;%SYSTEMROOT%\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\QuickTime\QTSystem\
Where do I add it?
My tools directory is set in the root of my C drive as
C:\SDK\tools (most people typed android, renamed mine to just SDK, seemed faster)
This is what im trying to figure out at this point. Sorry if it very noobish.. Any help would be greatly appreciated.
Click to expand...
Click to collapse
Okay my guide is to set you up to root, you need to download slideroot.zip from eugene's how to guide. It will download a folder so you need to save it somewhere you will find it. Once you have it saved extract the files and the files within that folder you need to put in the tools of the sdk directory. Do not just drop the folder as that would change the directory even more to another folder. A file in that folder is what actually makes the loop feature work and there are other things you will need from that folder to root.
And to this. %SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;%SYSTEMROOT%\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\QuickTime\QTSystem\
you just need to delete "Program Files (x86)\QuickTime\QTSystem\"
and then replace it with your directory to your C:/
rlacsamana1989 said:
You should be able to just delete the folder it downloaded. and make sure you empty your trash. I will look at what the issues can be. and let you know if I find anything. I'm pretty good at that
Edit: Have you seen this post? I'd start from the first thing they say which is going to task manager and ending adb.exe and if that doesn't work go to the next thing they stated to do. If none of those work come back and I will try and figure it out.
Click to expand...
Click to collapse
a successful uninstall & reinstall of the sdk worked for me. i no longer get the 'adb server is out of date' message when trying to list devices.
when reinstalling all of the packages in sdk, i did note this message:
Code:
'Downloading Usb Driver package, revision 3
Installing Usb Driver package, revision 3
Installed Usb Driver package, revision 3
Updated ADB to support the USB devices declared in the SDK add-ons.
'adb kill-server' succeeded.
ADB: * daemon not running. starting it now *
ADB: * daemon started successfully *
'adb start-server' succeeded.
but its a good thing =]
another note:
when i have sdk all setup, HTC Sync no longer seems to work or recognize my device as connected, even after ending adb.exe in my task manager.
poetik517 said:
another note:
when i have sdk all setup, HTC Sync no longer seems to work or recognize my device as connected, even after ending adb.exe in my task manager.
Click to expand...
Click to collapse
Have you tried re-installing the pdanet drivers again. And make sure you aren't clicking the box that pops up on the bottom of the screen. And if that doesn't work I know there is a program I have installed on my pc that let's me delete drivers I just can't remember the program so ill post it once I get home from work.
Sent from my T-Mobile myTouch 3G Slide using XDA App
usbdeview
rlacsamana1989 said:
Have you tried re-installing the pdanet drivers again. And make sure you aren't clicking the box that pops up on the bottom of the screen. And if that doesn't work I know there is a program I have installed on my pc that let's me delete drivers I just can't remember the program so ill post it once I get home from work.
Sent from my T-Mobile myTouch 3G Slide using XDA App
Click to expand...
Click to collapse
I think the program you're trying to remember may be "usbdeview"? This program allows you to disconnect or uninstall drivers.
I need help rooting my Tb , does anyone have a video or direct me to one that can help! I don't know how to use ADB!
I would take the time to learn ADB or wait until a one click is out. Learning ADB while rooting your phone could easily break it.
what os are you using?
svalle713 said:
I need help rooting my Tb , does anyone have a video or direct me to one that can help! I don't know how to use ADB!
Click to expand...
Click to collapse
Honestly just take the time to read the procedure, other help topics on these forums, and take your time when actually going through the procedure.
I had never used ADB either or rooted an android phone for that matter, and I gotta say, rooting the TBolt was cake.
I just took my time with it ensuring I typed in the commands properly.
But if you need a video, here you go: http://www.droid-life.com/2011/03/22/video-rooting-the-htc-thunderbolt/
what drivers do we need for the process, are they only the htc sync drivers? where can these be found?
Android SDK should be extracted/installed straight onto the C:\ directory to make it easy. Open the android-sdk folder and in it is a program sdkmanager.exe, open that and you can reject all of the downloads but scroll down and install one called the "google usb driver package" which may be necessary, I'm not sure (you should also have the htc sync drivers installed)
The contents from the "exploit.zip" should be extracted into the folder "platform-tools" within the android-sdk folder. Plug in your phone to the usb and open the command prompt. To get started open the command prompt (like a dos prompt) and get the prompt into the folder 'platform-tools' and type "adb devices" then hit enter. If your phone is connected and you have "usb debugging" enabled on your phone from the settings, your phone should appear and you can begin the instructions from jcase
Installed latest version of CWM..made backup of original rom...Rebooted System...No problem...Flashed CM9 per instructions...Full Wipe...Played with it for awhile...Backed it up...tried to restore Stock Rom ...went into CWM loop...Read a lot of threads and I still have drivers and Asus is seen in Device Manager with ADB Interface...So I tried Command prompts for 1a...and what I get is 'adb' is not recognized as an internal or external command,operable program or batch file...
Am I typin the command right ???...I never used ADB before...Came over from Epic Touch 4g Forum here...and I only used Odin...Could someone give me a clue if on on the right path of Unbrickin this thing...
Thanx...
BTW its Unlocked and of course rooted...
Your salvation is at hand:
http://dottech.org/tipsntricks/2153...ows-computer-for-use-with-your-android-phone/
Follow this guide. To the letter, very important you set the path correctly in the environment variables or you'll be going around in circles. Once it's done, you'll have a working ADB and fastboot environment, you will also want the "Universal naked USB driver" which can be found on this site.
Once you've got that up and running, try getting your system into fastboot protocol and type fastboot -i 0x0b05 reboot, if that works, then you've access to ADB and fastboot protocols, follow the commands given in solution 1a then to complete your recovery.
Hope this helps.
Hobbesian said:
Your salvation is at hand:
http://dottech.org/tipsntricks/2153...ows-computer-for-use-with-your-android-phone/
Follow this guide. To the letter, very important you set the path correctly in the environment variables or you'll be going around in circles. Once it's done, you'll have a working ADB and fastboot environment, you will also want the "Universal naked USB driver" which can be found on this site.
Once you've got that up and running, try getting your system into fastboot protocol and type fastboot -i 0x0b05 reboot, if that works, then you've access to ADB and fastboot protocols, follow the commands given in solution 1a then to complete your recovery.
Hope this helps.
Click to expand...
Click to collapse
Yep it was a Nandroid Backup...Im not at all familiar with ADB ...Just Odin which I use Rooting Phones...Ill give it a try...This is drivin me nuts...Just cant get ADB to work for me thru commands...Ill definitely do what you suggest...Thanx a lot Ill let ya know what happens...
Still gettin this when I run a command prompt
adb is not recognized as an internal or external command,operable program or batch file..Says the same for fastboot...Am I typin the commands right...
Installed driver and extracted the files from the download to my c part of the drive...Do I have to open anything in the download folder inorder for it to work or just extract everything like I did...
Didnt have the path of the extracted files in the right spot...Just had to change it...Wurked fine...Up and Runnin...Thanx a lot...Really appreciate it...
Help
ronny71 said:
Didnt have the path of the extracted files in the right spot...Just had to change it...Wurked fine...Up and Runnin...Thanx a lot...Really appreciate it...
Click to expand...
Click to collapse
What did you do? What files? I did literally the EXACT same thing to my prime. Please help. (Idk what to do with this driver download)
chrsbrrss said:
What did you do? What files? I did literally the EXACT same thing to my prime. Please help. (Idk what to do with this driver download)
Click to expand...
Click to collapse
Extract it if you haven't already.... put your prime into recovery .... plug it into the pc... in device manager find the prime and update the driver manually... point windows to the driver and your there...
For adb... you need to download that too I use the one in the nvfashpack... so... you extract the file.. with the window open... press and hold shift then right click in the window (nvflashpack folder, where the adb.exe file is) and select open command prompt here. Now you can use the adb commands... if your trying to push a file...it is best to put it in the same folder (nvflashpack)
I managed to accidentally flash the BLADE boot.img for CM10.1 to my phone before I transferred the ROM across to my SD card.
Didn't think this was a problem.. went into recovery to Mount USB Storage. Didn't work, so I flashed TWRP to see if it worked on there. No luck.
Tried performing a restore of the full working stock sense and wiped caches so I could try to transfer it over the OS. again no luck.
I've even tried pushing the .zip file to the sdcard using adb (run cmd as admin and use 'adb push ROM.zip /sdcard/ROM/') with no luck. It just tells me the device isn't connected. The drivers are definitely installed (fastboot is working).
I'm all out of ideas. If anyone could point me in the right direction, I'd be grateful. Thank you!
Mounting usb storage does not work with MTP devices.
Sent from my HTC One X+ using Tapatalk 2
AndroHero said:
Mounting usb storage does not work with MTP devices.
Sent from my HTC One X+ using Tapatalk 2
Click to expand...
Click to collapse
Is there another way of accessing the SD Card through recovery?
No except adb, but that only works with twrp. Why not flash a stock rom, and copy the rom to the SD Card while booted into android.
Sent from my HTC One X+ using Tapatalk 2
You might not be able to directly access your sd card, but you can most likely use adb sideload to load the CM10.1 ROM onto your device and regain functionality. Check this out for more information: http://teamw.in/ADBSideload
NasaGeek said:
You might not be able to directly access your sd card, but you can most likely use adb sideload to load the CM10.1 ROM onto your device and regain functionality. Check this out for more information: http://teamw.in/ADBSideload
Click to expand...
Click to collapse
Yeah while I was waiting for replies. I did a lot of research into adb sideloading and I pretty much get it now.. Only problem is that I'm running Windows 8 which has a whole bunch load of problems with adb... can't get it to recognise my device even with the correct drivers installed. Followed a few guides on the internet, but to no avail.
Does anyone know of anything that works? Or do I have to install it all on a W7 PC?
petedavison93 said:
Yeah while I was waiting for replies. I did a lot of research into adb sideloading and I pretty much get it now.. Only problem is that I'm running Windows 8 which has a whole bunch load of problems with adb... can't get it to recognise my device even with the correct drivers installed. Followed a few guides on the internet, but to no avail.
Does anyone know of anything that works? Or do I have to install it all on a W7 PC?
Click to expand...
Click to collapse
Do you have the latest SDK downloaded from google? I can confirm on windows 8 sideload through command prompt works fine in the platform tools folder. This is through CWM in my experience. i have not messed with TWRP
Kraizk said:
Do you have the latest SDK downloaded from google? I can confirm on windows 8 sideload through command prompt works fine in the platform tools folder. This is through CWM in my experience. i have not messed with TWRP
Click to expand...
Click to collapse
I downloaded and installed it today.
I'll go through exactly what I've done..
- Installed Java SDK
- Installed Android SDK
- Installed platform tools and usb driver
- Installed HTC Sync
- Opened hasoon's toolkit for the One X+
- Booted into TWRP and selected Advanced > Side Load
- Used the side load button on the toolkit.
I've also tried pushing files using the command line directly and cd-ing to the platform tools folder. This is what brings up the error connecting to device message. I've also started getting messages about starting daemon? No clue what that means.
petedavison93 said:
I downloaded and installed it today.
I'll go through exactly what I've done..
- Installed Java SDK
- Installed Android SDK
- Installed platform tools and usb driver
- Installed HTC Sync
- Opened hasoon's toolkit for the One X+
- Booted into TWRP and selected Advanced > Side Load
- Used the side load button on the toolkit.
I've also tried pushing files using the command line directly and cd-ing to the platform tools folder. This is what brings up the error connecting to device message. I've also started getting messages about starting daemon? No clue what that means.
Click to expand...
Click to collapse
Ignore the toolkit. That thing is less than stellar. Open the platform tools folder in the android SDK directory (default should be C: Android) Place the ZIP file of the rom you wish to flash in this directory. Hold shift and right click in blank space in the android sdk folder. Select "open command window here" (or something along those lines, not at my desk). type "adb kill-server" and then type the command "adb sideload romname.zip"
I recommend using CWM as I know this works on that. I do not use TWRP. You are welcome to try it with TWRP though.
Kraizk said:
Ignore the toolkit. That thing is less than stellar. Open the platform tools folder in the android SDK directory (default should be C: Android) Place the ZIP file of the rom you wish to flash in this directory. Hold shift and right click in blank space in the android sdk folder. Select "open command window here" (or something along those lines, not at my desk). type the command "adb sideload romname.zip"
I recommend using CWM as I know this works on that. I do not use TWRP. You are welcome to try it with TWRP though.
Click to expand...
Click to collapse
I have tried this method before too. It brought up the error message. I'll try it again in a minute and let you know. I'll also try it on CWM, but I read somewhere that CWM didn't support it? TWRP 100% does. It has an option for it in GUI.
EDIT: my android sdk in burried in Users/x/AppData/Local/Android/ .. Should I re-install in C:\Android ?
petedavison93 said:
I have tried this method before too. It brought up the error message. I'll try it again in a minute and let you know. I'll also try it on CWM, but I read somewhere that CWM didn't support it? TWRP 100% does. It has an option for it in GUI.
EDIT: my android sdk in burried in Users/x/AppData/Local/Android/ .. Should I re-install in C:\Android ?
Click to expand...
Click to collapse
That sounds like it is in the wrong place. That is usually a temporary folder. Check your c drive, it may also be labeled adt bundle and may be in program files. Sideload is an option in CWM by lloir by default which can be found in the original development section.
---------- Post added at 04:27 PM ---------- Previous post was at 04:24 PM ----------
Alternatively after rereading your OP. If you have not wiped anything you could just flash your old boot.img
Kraizk said:
That sounds like it is in the wrong place. That is usually a temporary folder. Check your c drive, it may also be labeled adt bundle and may be in program files. Sideload is an option in CWM by lloir by default which can be found in the original development section.
---------- Post added at 04:27 PM ---------- Previous post was at 04:24 PM ----------
Alternatively after rereading your OP. If you have not wiped anything you could just flash your old boot.img
Click to expand...
Click to collapse
About to reinstall the Android SDK (uninstalled and rebooted PC). I should install it to C:\Android ? (This folder doesn't exist currently)
I've also never set the environment variables as the Android SDK installed fine. Should I set these?
Also tried that.. it just hangs
petedavison93 said:
About to reinstall the Android SDK (uninstalled and rebooted PC). I should install it to C:\Android ? (This folder doesn't exist currently)
I've also never set the environment variables as the Android SDK installed fine. Should I set these?
Also tried that.. it just hangs
Click to expand...
Click to collapse
Download the android SDK bundle from google and install to C: Android, if it does not exist let it create it (i would still bet it is somewhere in your C drive but ok). I do not know what comes stock but i typically launch the SDK (NOT ECLIPSE) and allow it download all of the files associated with android (probably not needed). There should be an sdk folder inside the c android folder. in that is the platform tools folder. This is where you will open your command window and run the previously mentioned commands.
Kraizk said:
Download the android SDK bundle from google and install to C: Android, if it does not exist let it create it (i would still bet it is somewhere in your C drive but ok). I do not know what comes stock but i typically launch the SDK (NOT ECLIPSE) and allow it download all of the files associated with android (probably not needed). There should be an sdk folder inside the c android folder. in that is the platform tools folder. This is where you will open your command window and run the previously mentioned commands.
Click to expand...
Click to collapse
Trying the sideload now
petedavison93 said:
Trying the sideload now
Click to expand...
Click to collapse
If it is CWM give it a few minutes (literally like 5). Never used TWRP but it could take some time as well.
Kraizk said:
If it is CWM give it a few minutes (literally like 5). Never used TWRP but it could take some time as well.
Click to expand...
Click to collapse
Nothing came up for the kill-server command but it did pause.. so I'm guessing it did something.
The rest ran pretty quick but the phone hasn't received anything and is just sitting there (using CWM to keep my battery charged)
petedavison93 said:
Nothing came up for the kill-server command but it did pause.. so I'm guessing it did something.
The rest ran pretty quick but the phone hasn't received anything and is just sitting there (using CWM to keep my battery charged)
Click to expand...
Click to collapse
You could flash the stock recovery and run the RUU
Kraizk said:
You could flash the stock recovery and run the RUU
Click to expand...
Click to collapse
Very quick guide? I knew this was a possibility, but I've never had to do it until now. Thank you so much for the help btw
Although this still doesn't solve my problems with adb
petedavison93 said:
Very quick guide? I knew this was a possibility, but I've never had to do it until now. Thank you so much for the help btw
Click to expand...
Click to collapse
Flash the stock recovery (I do not have this as you appear to be on the international variant). Download your RUU (search the forums, I know it is here somehwere but the usual htcruu.com is now down....) boot into your boot loader and run the command "fastboot oem lock" Hit the power button to select hboot from the list and then just run the executable.
Kraizk said:
Flash the stock recovery (I do not have this as you appear to be on the international variant). Download your RUU (search the forums, I know it is here somehwere but the usual htcruu.com is now down....) boot into your boot loader and run the command "fastboot oem lock" Hit the power button to select hboot from the list and then just run the executable.
Click to expand...
Click to collapse
Can't relock the bootloader without working drivers.. this is beyond annoying now ¬.¬
EDIT: Relocked but not enough battery to flash RUU. Do I just run the RUU from the computer while the phone is at the home menu in the bootloader?
I'm using a batch file to charge the device over night. Will try again tomorrow.
I followed the directions here
http://www.htcdev.com/bootloader
on 2 different computer. Installed the 3 links
Google Android SDK zip:
Java Runtime Environment:
HTC Sync (Windows Only):
Made sure fast boot off.
Tried with/without USB debugging on (even tho there is no directions for that)
Typed in Command Prompt: fastboot oem get_identifier_token.
I get same message "fastboot is not recognized as an internal or external command, program or batch file"
Tried to do the rumrunner thing as well but it says i need to get past bootloader 1st.
arrrggg
What do I do I have tried googling with no help.
All my phones in the past i could find rather easy "how to" instructions but not this phone.
crap
Put your device to fastboot mode ( switch off the device volume down and power together)
Else
Usb debugging on and type the command in cmd (adb reboot bootloader)
Sent from my SM-N7505 using XDA Free mobile app
saeroner said:
I followed the directions here
http://www.htcdev.com/bootloader
on 2 different computer. Installed the 3 links
Google Android SDK zip:
Java Runtime Environment:
HTC Sync (Windows Only):
Made sure fast boot off.
Tried with/without USB debugging on (even tho there is no directions for that)
Typed in Command Prompt: fastboot oem get_identifier_token.
I get same message "fastboot is not recognized as an internal or external command, program or batch file"
Tried to do the rumrunner thing as well but it says i need to get past bootloader 1st.
arrrggg
What do I do I have tried googling with no help.
All my phones in the past i could find rather easy "how to" instructions but not this phone.
crap
Click to expand...
Click to collapse
You aren't running the cmd from th correct folder. Browse to the folder where fastboot is. Hold shift key and right click. Select open cmd prompt here. Then run your commands.
dottat said:
You aren't running the cmd from th correct folder. Browse to the folder where fastboot is. Hold shift key and right click. Select open cmd prompt here. Then run your commands.
Click to expand...
Click to collapse
Ok i did that but get this message
"program can't start because AdbWinApi.dll is missing from your computer. Try re-installing"
I reinstalled/downloaded "Google Android SDK zip:"twiceusing to different extraction programs. I placed the folder in the same android folder as the fastboot.
still stuck. any help?
thanks
saeroner said:
Ok i did that but get this message
"program can't start because AdbWinApi.dll is missing from your computer. Try re-installing"
I reinstalled/downloaded "Google Android SDK zip:"twiceusing to different extraction programs. I placed the folder in the same android folder as the fastboot.
still stuck. any help?
thanks
Click to expand...
Click to collapse
Download this. Extract it. Run your command prompt and commands here.
https://www.androidfilehost.com/?fid=23501681358559711
^ Thanks that worked!
saeroner said:
^ Thanks that worked!
Click to expand...
Click to collapse
You are welcome ☺