Im trying to unlock my bootloader so I can root my phone. When I get to the step to get my identifier token, it is stuck on <waiting for device>. If anyone can help me, Id greatly appreciate it.
ThatGuyMitch said:
Im trying to unlock my bootloader so I can root my phone. When I get to the step to get my identifier token, it is stuck on <waiting for device>. If anyone can help me, Id greatly appreciate it.
Click to expand...
Click to collapse
Make sure your drivers are installed on the computer and that you are in the fastboot option in hboot, not just the bootloader. I know thats probably a duh, but just making sure. Also when you first connect it to the computer, run adb devices and make sure its seeing the devices.
It also doesn't help that the HTC Dev site is having issues giving up the .bin file after you give them your token identifier. Feel free to tag along here: http://forum.xda-developers.com/showthread.php?t=1475864
clmowers said:
Make sure your drivers are installed on the computer and that you are in the fastboot option in hboot, not just the bootloader. I know thats probably a duh, but just making sure. Also when you first connect it to the computer, run adb devices and make sure its seeing the devices.
Click to expand...
Click to collapse
Should I check to make sure adb can see the device before I pull the battery out to reboot into the bootloader?
You can have it in charge only mode with the rom booted and everything and type "adb devices" and it should spit out the serial number.
Make sure you have USB Debugging checked in settings/developer options. Amd also make sure any antivirus type security business is turned off on your computer.
Sent from my ADR6425LVW using xda premium
Are you using Ubuntu (or any Linux clone) I had a heck of a time setting it up to work on Ubuntu.
Sent from my SCH-I815 using XDA Premium HD app
Related
Hey guys, I just bought a DNA of CL and I'm having some issues that Im hoping I can get resolved here. The DNA is currently rooted running ViperDNA 1.0.1. The issue I'm having is I'm getting no data connections. The only thing I can do is use the phone over wifi. The 4G Lte indicator is not showing up in the notification bar. So Im looking to return my phone to bone stock to see if this helps the issue. My problem is I'm having issues re-locking the boot loader. When I get the phone on fastboot usb( USB debugging is turned on) I go into my command and enter -fastboot oem lock. My command prompt will not recognize the the command, it just tells me"fastboot is not recoginized as a internal or external coomand". Can someone steer me in the right direction and help me out. Thanks
nuttz565 said:
Hey guys, I just bought a DNA of CL and I'm having some issues that Im hoping I can get resolved here. The DNA is currently rooted running ViperDNA 1.0.1. The issue I'm having is I'm getting no data connections. The only thing I can do is use the phone over wifi. The 4G Lte indicator is not showing up in the notification bar. So Im looking to return my phone to bone stock to see if this helps the issue. My problem is I'm having issues re-locking the boot loader. When I get the phone on fastboot usb( USB debugging is turned on) I go into my command and enter -fastboot oem lock. My command prompt will not recognize the the command, it just tells me"fastboot is not recoginized as a internal or external coomand". Can someone steer me in the right direction and help me out. Thanks
Click to expand...
Click to collapse
Assuming you have the adb drivers installed, it sounds like you aren't in the proper directory. You need to execute that command from the directory that fastboot.exe is in. Are you on a windows or Mac/Linux? Of you're using Mac/Linux the correct command is ./fastboot OEM lock
Sent from my DNA using Tapatalk 2
jamiethemorris said:
Assuming you have the adb drivers installed, it sounds like you aren't in the proper directory. You need to execute that command from the directory that fastboot.exe is in. Are you on a windows or Mac/Linux? Of you're using Mac/Linux the correct command is ./fastboot OEM lock
Sent from my DNA using Tapatalk 2
Click to expand...
Click to collapse
Thanks for the quick reply. Im using Windows 7, Im thinking the problem is I dont have the correct drivers. Do you have a link for the adb drivers?
nuttz565 said:
Thanks for the quick reply. Im using Windows 7, Im thinking the problem is I dont have the correct drivers. Do you have a link for the adb drivers?
Click to expand...
Click to collapse
That error means it doesn't know what the command fastboot is, you either don't have it in your path or you aren't in the folder that has it. Drivers will display fast boot messages, not that command error.
Tapatalked from my HTC DNA - ReVolt
Try new SIM card. The same thing sorta happened to me. I couldn't get 4g data. A new SIM fixed it all.
Sent from my HTC6435LVW using xda premium
Also, you are using an extremely outdated version of viper. Upgrade to 1.3 or flash CM/PAC. You probably need a new sim card.
123421342 said:
Also, you are using an extremely outdated version of viper. Upgrade to 1.3 or flash CM/PAC. You probably need a new sim card.
Click to expand...
Click to collapse
I got a new sim card earlier in the day which did not fix the issue. I can not for the life of me figure out how to get it to show up in the command prompt so that I can re-lock my boot loader. I have been dealing with it trying to figure it out all day. Im going to just do what you suggested and try and get 1.3 onto the device. Thanks
nuttz565 said:
I got a new sim card earlier in the day which did not fix the issue. I can not for the life of me figure out how to get it to show up in the command prompt so that I can re-lock my boot loader. I have been dealing with it trying to figure it out all day. Im going to just do what you suggested and try and get 1.3 onto the device. Thanks
Click to expand...
Click to collapse
Did you ever open the prompt in the folder with fastboot.exe? Your error would be gone. At least that one would be, it had nothing to do with the phone and all about your PC not knowing where fastboot is.
Tapatalked from my HTC DNA - ReVolt
Ok, you downloaded the SDK correct? Or at least have the adb and fastboot files somewhere? I'm assuming you do..
Say you have them in a folder named adb on your C drive.
In the command prompt you would type:
cd C:/adb/
That brings the command prompt "into" that folder.
Now run your fastboot oem XXXXX command
Hi folks,
I have a stock phone and I'd like to root it mainly for getting wifi tethering to work. Don't really care about any different roms. Any quick links to what I have to do to have the phone act as a hot spot for my iPad?
Please forgive me if this question wasn't appropriate here.
Crodley
Verizon or Sprint?
Sent from my HTC0P3P7 using xda app-developers app
Root Your HTC One Max
Crodley said:
Hi folks,
I have a stock phone and I'd like to root it mainly for getting wifi tethering to work. Don't really care about any different roms. Any quick links to what I have to do to have the phone act as a hot spot for my iPad?
Please forgive me if this question wasn't appropriate here.
Crodley
Click to expand...
Click to collapse
If your One Max is on Sprint then you can easily unlock bootloader through HTCDev. Then you can Install TWRP 2.6 and use it to flash superSU 1.91 (Google). You will then be rooted and ready to rock and roll. You can follow this Youtube video: http://www.youtube.com/watch?v=qpj6dEMn9dw for procedure if you're unfamiliar. The vid tutorial is for the HTC One but is the same procedure for One Max. You will need to download adb and fastboot (and appropriate drivers if you are using a windows machine). No drivers are needed if you are using a mac or linux box. You can get the necessary files from here: http://developer.android.com/sdk/index.html. Download the appropriate ADT bundle for your platform.
Windows drivers SHOULD be installed by default the 1st time you plug in your phone. They are however installed along with HTC Sync which can cause you connection problems. I would recommend NOT installing HTC Sync as you would most likely have to uninstall it later in order to get these procedures to work. Instead try this link for HTC Drivers: http://forum.xda-developers.com/showthread.php?t=2089508. Make sure drivers are properly installed BEFORE you plug in your phone. Windows can be a PITA so be sure you can disable antivirus, firewall, and any other running processes that may impede your ability to achieve and maintain a solid connection to your device.
You will also need to enable USB Debugging on your One Max. To enable USB Debugging you need to go to Settings > About > Software Information > More > Build number - tap Build number 7 times to enable developer mode. After you get the window saying "developer mode has been enabled" go back to the main menu in Settings and you'll see you now have "Developer Options" added. In there you will have the ability to enable USB Debugging
Create a folder for ALL your development files that you can easily CD your command prompt to. (Ex. "C:/onemax" for windows or "desktop/onemax" mac/linux) Follow video.
If you are using a Verizon One Max, you will be unable to unlock your bootloader through HTCDev. In this case you will need to S-Off your device you can follow this guide if your Hboot is 2.46 or lower: http://forum.xda-developers.com/showthread.php?t=2473644. If your Hboot is 2.47, rumrunner will not work for you. You will need to consult the firewater guide instead: http://forum.xda-developers.com/showthread.php?t=2632385. Once you are S-OFF, you can pretty much do anything you want on your One Max. FYI Hboot is HTC's bootloader. You can find out your version by 1. going into Settings > Power - then untick Fast Boot option. 2. shutting down your phone, then 3. hold the volume - key down firmly, then hold down power button until your device boots into the bootloader. Hboot version will be shown at the top of your screen.
Spend a little time familiarizing yourself with whichever procedure you require. Quadruple check you are using the CORRECT FILES for your One Max. You will need a properly working development environment regardless of which procedure you will follow, so set it up first!
Here's hoping you have a Sprint One Max and a Mac LOL Seeings how you only need a simple root!
Good luck!
neodiver said:
If your One Max is on Sprint then you can easily unlock bootloader through HTCDev. Then you can Install TWRP 2.6 and use it to flash superSU 1.91 (Google). You will then be rooted and ready to rock and roll. You can follow this Youtube video: http://www.youtube.com/watch?v=qpj6dEMn9dw for procedure if you're unfamiliar. The vid tutorial is for the HTC One but is the same procedure for One Max. You will need to download adb and fastboot (and appropriate drivers if you are using a windows machine). No drivers are needed if you are using a mac or linux box. You can get the necessary files from here: http://developer.android.com/sdk/index.html. Download the appropriate ADT bundle for your platform!
Click to expand...
Click to collapse
Yup Sprint, and Windows. Thanks for the replies everyone! I'll attempt this tomorrow.
Crodley said:
Yup Sprint, and Windows. Thanks for the replies everyone! I'll attempt this tomorrow.
Click to expand...
Click to collapse
Well, when I said tomorrow, I meant a month instead.
I checked out the guide Neodiver suggested, and while it was nice, it still had me a bit confused on some of the things. After lots and lots of reading, I started down this path:
http://forum.xda-developers.com/showthread.php?t=2550559
And it worked well, up until between step "F" and step "G" copied here:
f. Boot back into the bootloader, and make sure you're in fastboot. Issue the command fastboot flash boot boot.img. If all is well, the unsecure kernel is now on your phone! Now delete the boot.img from that directory (It'll mess with rumrunner).
g. Unzip the rumrunner contents into the adb/fastboot directory and run the soju.exe. Follow the prompt. If all goes well, you should now have an SOFF television in your hand
It DID flash the boot.img fine, but when I tried to run soju.exe and read the disclaimer it said to make sure the adb saw my device, and sure enough, it does not anymore. ADB WILL see my device when I simply boot up normally, but when I boot to the fastboot usb screen, it no longer sees it.
I'm going to bed and toss and turn with dreams of my phone chasing me down hallways, I'll check for any advice when I wake up.
Again, to be clear, my phone boots fine, all features seem to work and I did all steps up until running rumrunner, at which point in fastboot usb mode, adb won't see my device.
Night, and thanks in advance!
Crodley said:
Well, when I said tomorrow, I meant a month instead.
I checked out the guide Neodiver suggested, and while it was nice, it still had me a bit confused on some of the things. After lots and lots of reading, I started down this path:
http://forum.xda-developers.com/showthread.php?t=2550559
And it worked well, up until between step "F" and step "G" copied here:
f. Boot back into the bootloader, and make sure you're in fastboot. Issue the command fastboot flash boot boot.img. If all is well, the unsecure kernel is now on your phone! Now delete the boot.img from that directory (It'll mess with rumrunner).
g. Unzip the rumrunner contents into the adb/fastboot directory and run the soju.exe. Follow the prompt. If all goes well, you should now have an SOFF television in your hand
It DID flash the boot.img fine, but when I tried to run soju.exe and read the disclaimer it said to make sure the adb saw my device, and sure enough, it does not anymore. ADB WILL see my device when I simply boot up normally, but when I boot to the fastboot usb screen, it no longer sees it.
I'm going to bed and toss and turn with dreams of my phone chasing me down hallways, I'll check for any advice when I wake up.
Again, to be clear, my phone boots fine, all features seem to work and I did all steps up until running rumrunner, at which point in fastboot usb mode, adb won't see my device.
Night, and thanks in advance!
Click to expand...
Click to collapse
I believe you start soju while the phone is booted fully up. With adb enabled. Not at fastboot mode.
Sent from my HTC6600LVW using Tapatalk
dottat said:
I believe you start soju while the phone is booted fully up. With adb enabled. Not at fastboot mode.
Sent from my HTC6600LVW using Tapatalk
Click to expand...
Click to collapse
Yup, that was the one. Funny waiting messages on the Rumrunner program. :good:
Got Sff now!
Thanks to ALL!
Especially Neodiver with the great response with links to everything!
Oh and btw, any particular wifi hotspot app you folks recommend?
I can't for the life of me get adb to recognize my max. It's Verizon, H-boot 2.46. Trying to root and unlock. I've tried everything here....nothing. A little help please.
Only thing I can suggest, because it's happened to me, is to make sure you have the correct, most current device drivers loaded on your PC.
Sent from my HTC6525LVW using Tapatalk
they are correct up to date and most current.
HellRayzer said:
I can't for the life of me get adb to recognize my max. It's Verizon, H-boot 2.46. Trying to root and unlock. I've tried everything here....nothing. A little help please.
Click to expand...
Click to collapse
Are you unlocked, s-off, and rooted? Do you have developer options activated on your phone? Please explain what you´ve done up till now.
What happens when you type adb reboot. Does it start and not find it or come back with command not recognized?
Sent from my HTC6525LVW using xda app-developers app
i was having issues myself. then I found this thread and things worked again. http://forum.xda-developers.com/showthread.php?t=2588979
it doesn't find anything. I haven't been able to root s-off or anything because adb cant find my device. Do I need adb files in rumrunner folder on C drive to make it recognize it and work or what the hell am I doing wrong? I have rooted and s-offed every htc device I have ever owned...this one isn't working out. It's showing as a portable media player not android device. In the past I remember when I connected the usb I had the option to select media storage or connect as android.
HellRayzer said:
it doesn't find anything. I haven't been able to root s-off or anything because adb cant find my device. Do I need adb files in rumrunner folder on C drive to make it recognize it and work or what the hell am I doing wrong? I have rooted and s-offed every htc device I have ever owned...this one isn't working out. It's showing as a portable media player not android device. In the past I remember when I connected the usb I had the option to select media storage or connect as android.
Click to expand...
Click to collapse
my rumrunner folder was still in my downloads folder no where near my adb files and everything worked ok for me. also my Max shows up as a media device also but adb/fastboot still working fine. did you try to reinstall your adb with the link I provided in the above post, its the only thing that helped me when I was having pretty much the same problem as you.
you may also need to unlocked dev tools in your settings... have you done that yet
Where and how do you unlock developer tools...haven't found that under anything in the settings?
HellRayzer said:
Where and how do you unlock developer tools...haven't found that under anything in the settings?
Click to expand...
Click to collapse
Enter Settings, then scroll down to about... pick "Software Information" -- then "More" --- Then press the "Build" 8 times fast. You´ll then have access to the developer tools.
Well thanks for the help. still can't get anything to work, guess this will be the first device I've owned that will never be rooted unless I find something that tells me what to put where and what to do.
HellRayzer said:
Well thanks for the help. still can't get anything to work, guess this will be the first device I've owned that will never be rooted unless I find something that tells me what to put where and what to do.
Click to expand...
Click to collapse
When you type in adb devices, can you see your seriel number?
RayHeath said:
When you type in adb devices, can you see your seriel number?
Click to expand...
Click to collapse
no. it says list of devices, then it's blank.
HellRayzer said:
no. it says list of devices, then it's blank.
Click to expand...
Click to collapse
Ok, I´m not sure what you time zone is, but I can help you tomorrow. It´s 10pm here right now, and I´m gonna hit the hay soon. When you´re online tomorrow, pm me. I´ll log in, and we´ll start.
Hey relax bud, do me a favor and PM and I will help you out with everything and getting your phone to be recognized by dab and fast boot and make sure you properly s-off unlock and root if that's what you are trying to accomplish! Hit me up, I have nothing going on tonight so I can jump right in to it with you right away
HellRayzer said:
no. it says list of devices, then it's blank.
Click to expand...
Click to collapse
Have Win XP or server 2003?!?
This: http://forum.xda-developers.com/showthread.php?p=49045175
Don't know if you guys ever got this issue solved or not. I'm having the same issue S-on, cannot get adb devices command to recognize my t6spr for the life of me. on Hboot 2.46, it will detect the USB device malfunction if I put the device in fastboot mode, but thats about it. Device manager shows Unknown USB (Device Descriptor Request Failed). Tried the KB update for devices that fail enumeration on Windows 8.1 for x64 but the update package said my system is not affected so that never installed. Tried the alternative miniadb pakage previously mentioned but didnt seem to have an affect installing fastboot, adb, and drivers, across the system universally. Just not having any luck apparently. I guess I could just sell the phone Tampered and Unlocked haha with no fingerprint scanner functionality, flash ViperRom or some other stock look alike ROM. Was just really hoping to go back completely stock. At one point it time I was trying different PCs to see if it was just a system issue for me. Occasionally it seemed like if I let it sit in Fastboot AC it would eventually get detected and flip over to Fastboot USB long enough for me to push a couple commands to the phone. I have the right RUU but it dosent do me any good if the computer cant see the phone haha. Now no computer seems to recognize it. It all seemed to happen after I tried to S-Off the device with Firewater's method. Idk if I bricked something because it never worked or changed a CID or some other ID to where the USB isnt recognizable, but all I can get this phone to do is take an electric current from the USB, lol thats about it. I thought I had it fixed enough to where I knew what to do if i absolutely needed to get fastboot to recognize the phone but now, nothing.
Just a curiousity question here....a bad usb cable can produce this also...read through posts didnt see anyone trying a new cable...
Please forgive my ignorance I am very new to this. I just want to flash the new firmware to the nexus 9 manually. I have downloaded minimal adb and fastboot but it doesn't find my device. I have enabled developer mode and allow usb oem ect but nothing when I type the commands it says waiting for device and nothing happens, obviously I am missing something obvious, but if you could please help me out I would be grateful.
Did you let your device RSA footprint be recognised?
Did you run adb commands at the right directory?
AjunNg said:
Did you let your device RSA footprint be recognised?
Did you run adb commands at the right directory?
Click to expand...
Click to collapse
Not sure what the first question means??, I think I ran the adb commands at the right directory??
anobium said:
Not sure what the first question means??, I think I ran the adb commands at the right directory??
Click to expand...
Click to collapse
Means when you connected the device to the PC with USB debugging, there should have been a pop up asking you if you'll let the device blah blah.
You need to press OK.
AjunNg said:
Means when you connected the device to the PC with USB debugging, there should have been a pop up asking you if you'll let the device blah blah.
You need to press OK.
Click to expand...
Click to collapse
No never had a popup, asking me toconfirm???.
Unplug it and replug it until it does.
Uncheck USB debugging and recheck it until it does.
AjunNg said:
Did you let your device RSA footprint be recognised?
Did you run adb commands at the right directory?
Click to expand...
Click to collapse
AjunNg said:
Unplug it and replug it until it does.
Uncheck USB debugging and recheck it until it does.
Click to expand...
Click to collapse
Think ive found my problem in device manager on my computer the android device has a yellow exclamation mark saying no a driver present, were do I get the android driver for windows??
Use Wugfresh's Nexus toolkit, and use the full driver installation.
anobium said:
Think ive found my problem in device manager on my computer the android device has a yellow exclamation mark saying no a driver present, were do I get the android driver for windows??
Click to expand...
Click to collapse
Right click on it. Go to where it lets you pick from a list on your computer. Choose android adb interface driver, or something along those lines
Sent from my Nexus 9 using XDA Free mobile app
AjunNg said:
Use Wugfresh's Nexus toolkit, and use the full driver installation.
Click to expand...
Click to collapse
This program is the bollocks, for a newbie like me, went through the steps and it recognised my device, only 1 question do I need to root to update stock firmware as I cant see option to update without rooting.
By bollocks I mean brilliant.
No root needed to update.
anobium said:
This program is the bollocks, for a newbie like me, went through the steps and it recognised my device, only 1 question do I need to root to update stock firmware as I cant see option to update without rooting.
By bollocks I mean brilliant.
Click to expand...
Click to collapse
oh you silly English person.
the toolkit will get you back to stock. wug is working on a revision that will properly format the data partition to decrypt the tablet. the tool is best for force flashing and renewing your device as if you just unboxed the device with no root. the option to install a recovery and root the device is used after you are happy with the first boot and freshness of your devices. other tools included are just simplified press of the button commands that save you the time of opening a cmd shell.
key things to remember about the n9, absolutely make sure you enable the OEM unlock in developer options. and to my understanding NEVER uncheck it. there is a thread here about that "feature"
Sent from my Nexus 9 using Tapatalk
Migamix said:
oh you silly English person.
the toolkit will get you back to stock. wug is working on a revision that will properly format the data partition to decrypt the tablet. the tool is best for force flashing and renewing your device as if you just unboxed the device with no root. the option to install a recovery and root the device is used after you are happy with the first boot and freshness of your devices. other tools included are just simplified press of the button commands that save you the time of opening a cmd shell.
key things to remember about the n9, absolutely make sure you enable the OEM unlock in developer options. and to my understanding NEVER uncheck it. there is a thread here about that "feature"
Sent from my Nexus 9 using Tapatalk
Click to expand...
Click to collapse
And what's wrong with fastboot? No need for a tool kit
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
And what's wrong with fastboot? No need for a tool kit
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Ok i get to flashing the image and it goes to quick and comes up with errors saying I have different firmware image on my device?, I thought that was the idea im going from lrx21r to lrx22c, do I have to put I already have the 22c in the option list??.
jd1639 said:
And what's wrong with fastboot? No need for a tool kit
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
there is nothing wrong with ADB, or fastboot, if you use it exclusively, good for you.
as the OP title sais, it is not expected for a new user, and even some experienced users, to have such a firm grasp of the ways of the mighty command line, and the fact that the toolkit gathers all of the files in one convenient place, is not without its bonus. i dont know, nor do i really care who started the whole elitist "toolboxes are for lamers", or whatever. toolboxes are nothing more than their name suggests , tool-boxes, to help when we need it. they are nothing more than an interface to commands, much like you running a GUI on top of your OS, or are also running command line only for your primary computer. xda, is designed and expected to be help for all who want to know, not a pond of elitists that would rather brag they have overclocked their device, water cooled it, but can still make a grilled cheese sandwich on their CPU. i have email accounts older than many of the forum members here, so not too much impresses me in that 1337 area. im here to help if i can, and learn if i need to., so since im here alot, im always learning.
ok so im having a few problems with my rooting process. one i have to manually put my device into fastboot since doing it threw my windows 7 CMD just seems to not work since it will say device offline. then once i do get to fastboot i run into my second problem. the recovery.img seems to be frozen during the sending process. in fact its still trying to send it to my device. my device is unloocked. what am i doing wrong? or am i missing something? i followed another titorial on here and im still stuck. mostly on the recovery.img part. it just doesnt seem to send. just sits there saying its sending it.please help if you can.
says S-On . how do i gewt it to say s-off?
LordXombie said:
ok so im having a few problems with my rooting process. one i have to manually put my device into fastboot since doing it threw my windows 7 CMD just seems to not work since it will say device offline. then once i do get to fastboot i run into my second problem. the recovery.img seems to be frozen during the sending process. in fact its still trying to send it to my device. my device is unloocked. what am i doing wrong? or am i missing something? i followed another titorial on here and im still stuck. mostly on the recovery.img part. it just doesnt seem to send. just sits there saying its sending it.please help if you can.
Click to expand...
Click to collapse
Sounds like you need to update to the latest version of ADB/FASTBOOT the "device offline" is usually due to an incomatible older version of ADB. Get the latest version on your PC then make sure that ADB is working before trying fastboot.
LordXombie said:
says S-On . how do i gewt it to say s-off?
Click to expand...
Click to collapse
We don't have an S-off solution for this phone yet but it is not required for root, although you will need to flash jmz's insecure kernel for changes to "/system" to stick after reboot even when rooted,
MiniBlu
i cant seem to get adb to update.
LordXombie said:
i cant seem to get adb to update.
Click to expand...
Click to collapse
Install the latest on your PC from here http://forum.xda-developers.com/showthread.php?t=2317790
MiniBlu
ok so i did that and it is still saying device offline. Now im trying a program i found on here. desire_610_root_v3.exe it was able to reboot the device into bootloader then it brought it into fastboot menu then it started to send the file then it just snags there. the file just keeps saying its sending. i dont know whats going on.
ok it still not getting teh recovery.img on the phone. it just keeps sending it with out doing anything..
ok so this htc is giving me way mopre problems then the htc one vx. i really need help. and now im kind of lost what to do. Currently all i have done is unlocked the device.
ADB says my device is there. Threw cmd i can't get it to fastboot using adb reboot fastboot. all it does it reboot teh device, it wont go to bootloader. I do have bootloader unlocked. when i go and make my device go to bootloader manually i try to do the fastboot flash recovery recovery.img it starts to send the file then fails. unknown error. what am i doing wrong?
ok so it seems changing my usb cord fixed it. i got the file sent and rooted my device. thanks for the help MiniBlu gave me !
LordXombie said:
ok so it seems changing my usb cord fixed it. i got the file sent and rooted my device. thanks for the help MiniBlu gave me !
Click to expand...
Click to collapse
That's info that more people should have. The right usb cord can be difference between failure & success. I remember I went through 6 different usb cables jailbreaking my atv2.
For this phone, however, I just used the one that came with it. But I found the automated process to be sticky (not a tech term) it seemed to freeze a lot during the process.
I wound up plugging and replugging the usb when it froze.
It rooted my phone, installed twrp but needed to flash jmz kernel manually. The root tool works though. And to be honest, until I read this I didn't even think that a different cable might fix those issues in the automated process.
The other night for fun I rooted an old kindle hd and I needed to unplug and replug to get that to work. I was using the same cable that came with HTC desire.
***Anyone ever use a fastboot cable? Apparently u need one to install a 2nd boot loader on kindle hd and I'm wondering if that type of cable would resolve issues like this? That's a question not a go ahead to try it. I know very little about that and don't know if it could possibly cause more serious issues. They're cheap on eBay and I'm getting one for the kfhd.