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
Related
Latest update:
I went to Rogers, and the girl suspect that my phone is broken due to physical damage because there are some scratch on my phone. She send the phone back to HTC for diagnosing. It will take 10 - 15 business days. I'm wondering if HTC will find out that I have su and superuser inside T.T
----------------------------------------------------------------------------------------------------------------------------
I bricked my phone. I'll tell you guys what I've done.
When I get my new Evo 3d GSM, the revolutionary for GSM was not released yet.
I used the one for CDMA (HBoot 1.40) to turn my phone to s-off, and yea, it worked. You guys must be blaming me, saying why did you do so? Because at the time when I was rooting my phone, revolutionary did not support GSM yet.
I flashed the recovery at bootloader using fastboot ******* .....
I flashed a root (su/superuser) to my phone. I used the su in this thread
http://forum.xda-developers.com/showthread.php?t=1218969
Yea, that means I have the correct HTC driver and android SDK.
and yea, it's rooted. Everything was totally fine until today...
I saw there's a thread about rooting GSM using new revolutionary which supports GSM.
The thread is http://forum.xda-developers.com/showthread.php?t=1247392
I thought maybe I should turn s-on, and use the revolutionary for GSM (HBoot 1.49.0007) to make it s-off "properly".
I followed most of the the steps on that thread.
Step 1. Download applicable rom from this thread: http://forum.xda-developers.com/show....php?t=1208485
Step 2. Flash rom from attached thread.
I skipped the first and 2nd step, cuz I did not flash my rom to a customer one. I just uninstalled some rogers apps and htc logger. I don't skipping these 2 steps caused the problem at the beginning. But now I think it may caused the problem, because my phone is still in root state!
Step 3. Download and extract android SDK (Already have it)
Step 4. Connect phone in USB debug mode
Step 5. Open an elevated command prompt and cd to the extracted tools folder (Powershell ftw!)
Step 6. type "adb reboot bootloader"
Step 7. type "fastboot oem writesecureflag 3"
Step 8. type "fastboot reboot-bootloader"
Thats it! Bricked!
What's the situation:
I cannot turn it on by any means...The red LED is not on even when I connect it to a charger or my PC.
What I've tried:
---Remove the battery, wait for 10 mins, put the battery back and try to power on,doesn't work.
---Connect to PC, adb and fastboot can't find the device
---Device manager complains "QHSUSB_DLOAD" is not working properly(with a exclamatory mark on the icon). I tried to search this issue, but it seems that none of the similar problems (Device manager complains "QHSUSB_DLOAD") are solved. I also tried to install some driver to let my PC recognize the device (which makes QHSUSB_DLOAD's icon without the exclamatory mark), but adb and fastboot still can't recognize the device.
Please help! Thanks a lot in advance!
Also there is one more question, Rogers gave me a one year's warranty, I bought this phone Aug 2011. My phone is still in warrant, but do they replace my phone due to this kind of problem? I don't know if they can boot up my phone, they'll see s-on or s-off.
Sorry about my broken English, I'm not an arts student
if it won't boot OR communicate with a computer, you should be fine to turn it in for warranty replacement
il Duce said:
if it won't boot OR communicate with a computer, you should be fine to turn it in for warranty replacement
Click to expand...
Click to collapse
What he said
Sent from my HTC EVO 3D X515m using XDA App
Thanks guys, I'll go to rogers tomorrow
updated
snake3276120 said:
updated
Click to expand...
Click to collapse
Sorry to hear that
Lets hope that they cant turn it on...
Sent from my HTC EVO 3D X515m using XDA App
snake3276120 said:
Latest update:
I went to Rogers, and the girl suspect that my phone is broken due to physical damage because there are some scratch on my phone. She send the phone back to HTC for diagnosing. It will take 10 - 15 business days. I'm wondering if HTC will find out that I have su and superuser inside T.T
Click to expand...
Click to collapse
Did you delete any files that had anything to do with rooting from your SD card before sending it in? I heard HTC askes you to send the phone without the memory card, so hopefully you did that. If not, you're screwed.
I don't know what you wanted to "properly unlock" to begin with. If it was already s-off, you can get s more off than off, you know?
Live and learn, I guess.
rugedraw said:
Did you delete any files that had anything to do with rooting from your SD card before sending it in? I heard HTC askes you to send the phone without the memory card, so hopefully you did that. If not, you're screwed.
I don't know what you wanted to "properly unlock" to begin with. If it was already s-off, you can get s more off than off, you know?
Live and learn, I guess.
Click to expand...
Click to collapse
i'm screwed...............................................................................................................sd card inside the phone..................................................
I did the same thing
Step 3. Download and extract android SDK (Already have it)
Step 4. Connect phone in USB debug mode
Step 5. Open an elevated command prompt and cd to the extracted tools folder (Powershell ftw!)
Step 6. type "adb reboot bootloader"
Step 7. type "fastboot oem writesecureflag 3"
Step 8. type "fastboot reboot-bootloader"
Thats it! Bricked!
Did thay fixed it ?
With the signature checking it's important you have a completely stock "SHIP" hboot installed, otherwise your phone will refuse to boot. Why they made it like this I don't really know, since all it does it make it 1000x easier to brick, but they did.
thanks, but any chance to fix it
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
This is the hardest damn thing I have ever done.... trying to root the DNA. It is insane how hard it is, can someone PLEASE do a step by step on how to install Sense 5? Every walkthrough is just not helpful at all and doesn't make any sense.
Theres like 10000 steps and each step has 100 problems and I google the problems and get stuck at every step... I have rooted the S3 so easily w/ in 1 hour but this is just insane....
I know I need to 1) Unlock Bootloader 2) Root 3) S-off
I have tried every one of the above steps and am stuck at one point or another in every point.... Unlocking the bootloader I am stuck because my computer cant recognize my device in bootloader mode. When I type "fastboot oem readcid" it just gets stuck at "waiting for device" I have tried everything and it still doesnt recognize the device....Theres so many people with this problem but no solution.
Is there anyone around San Francisco that will upgrade me to Sense 5 for $20?
ok so first off does you phone have the OTA sofware.. settings>about>software... if your software has 2.04 in it then you won't be able to root at this time..
if your not on the OTA then you should be able to unlock>root>s-off
your obviously having driver issues.. what version of windows are you using?
here are the drivers that I use, i would uninstall all HTC Sync stuff and reboot (basically try and clean out any drivers that could be conflicting)
then try the drivers in this zip file.. I put the phone in bootloader mode first then attach to computer and when i asks about drivers point it to where you unziped the drivers below..
http://db.tt/kr11CT4d
check out the thread I wrote up on how to do this. You can follow all those steps and just use the Sense 5 ROM instead of the ViperDNA ROM I cite. You might have to flash the cubed kernel separately first if it's not packaged with the ROM, but that's not hard to do.
The "waiting for device" means you don't have adb setup correctly. 9 times out of 10 it's because you don't have the drivers. If you have the OTA update you can't unlock the bootloader yet.
Hi Guys,
I do not have the OTA Update, I am running Straight talk and got my phone like 4 months ago, never updated.
I am running Windows 8 on a Samsung Series 9.
I tried the drivers you linked above but I get the same error....see attached photo
I will try your walk though now. I like it a lot... I was about to give up.... nothing is worth this much trouble...Its like problem after problem after problem. lol
Thanks for the help..
irockthebear said:
Hi Guys,
I do not have the OTA Update, I am running Straight talk and got my phone like 4 months ago, never updated.
I am running Windows 8 on a Samsung Series 9.
I tried the drivers you linked above but I get the same error....see attached photo
I will try your walk though now. I like it a lot... I was about to give up.... nothing is worth this much trouble...Its like problem after problem after problem. lol
Thanks for the help..
Click to expand...
Click to collapse
I'm running windows 8 and just had to use a different USB port, 2.0 I think. Do you know how to boot in fastboot? Then did you download adb? There are a few simple commands to get id token, then copy, goto htcdev (google) paste your idtoken after you register. That's step one, unlock the bootloader, in the 1.15 FW
if you need help email me [email protected] Ill check in 5 minutes
SHANENATAS said:
I'm running windows 8 and just had to use a different USB port, 2.0 I think. Do you know how to boot in fastboot? Then did you download adb? There are a few simple commands to get id token, then copy, goto htcdev (google) paste your idtoken after you register. That's step one, unlock the bootloader, in the 1.15 FW
if you need help email me [email protected] Ill check in 5 minutes
Click to expand...
Click to collapse
See attached.
This isnt working.... it says FASTBOOT USB on my phone but on my computer it doesnt recognize the device, I tried every USB port and when I plug it in it just fails and lags at installing device...
irockthebear said:
This isnt working.... it says FASTBOOT USB on my phone but on my computer it doesnt recognize the device, I tried every USB port and when I plug it in it just fails and lags at installing device...
Click to expand...
Click to collapse
1. jump on a windows 7 computer 32 or 64 bit the same as the windows 8 computer
2. download this the htc drivers HTCDriver install them
3. go to C:\Program Files (x86)\HTC\HTC Driver copy the files and put them on the windows 8 computer
4. windows key + r to open the device manager then look under the other devices right click htc than update driver
5. click browse my computer for driver software then browser and find the drivers from the windows 7 computer
6. it well install and work fine
http://forum.xda-developers.com/showthread.php?t=1775870
Try that. I'm going to keep checking this until you get it.
I have to tell ya, if you're on 1.15FW get those drivers to work and unlock the bootloader, then root, and S-off if you like. You will be much happier.
SHANENATAS said:
1. jump on a windows 7 computer 32 or 64 bit the same as the windows 8 computer
2. download this the htc drivers HTCDriver install them
3. go to C:\Program Files (x86)\HTC\HTC Driver copy the files and put them on the windows 8 computer
4. windows key + r to open the device manager then look under the other devices right click htc than update driver
5. click browse my computer for driver software then browser and find the drivers from the windows 7 computer
6. it well install and work fine
http://forum.xda-developers.com/showthread.php?t=1775870
Try that. I'm going to keep checking this until you get it.
I have to tell ya, if you're on 1.15FW get those drivers to work and unlock the bootloader, then root, and S-off if you like. You will be much happier.
Click to expand...
Click to collapse
OMG IT WORKED THX, I will probably get stuck in like 20 seconds on the next step.
Sweet, I'll keep checking here to see if you get stuck or have questions. I'll help if I can, glad you got it!
irockthebear said:
OMG IT WORKED THX, I will probably get stuck in like 20 seconds on the next step.
Click to expand...
Click to collapse
Now I get this....
irockthebear said:
OMG IT WORKED THX, I will probably get stuck in like 20 seconds on the next step.
Click to expand...
Click to collapse
Here are some commands I use. There are great "how to" videos here if you search.
cd c:\fastboot
fastboot oem readcid
fastboot flash recovery recovery.img
adb reboot bootloader
fastboot boot boot.img
fastboot oem lock
fastboot oem get_identifier_token <--------------------- you want this AND
fastboot flash unlocktoken Unlock_code.bin <----------this after you register @htcdev and enter your token
fastboot reboot
irockthebear said:
Now I get this....
Click to expand...
Click to collapse
Im going to try to do this on my HP Envy 4T Windows 7 Device
irockthebear said:
Now I get this....
Click to expand...
Click to collapse
Try switching USB ports, I have only 3 on this laptop, the 2 on the left wont work, but the one on the right does. This is new laptop it has todo with usb version or speed
---------- Post added at 05:31 PM ---------- Previous post was at 05:28 PM ----------
irockthebear said:
Now I get this....
Click to expand...
Click to collapse
Do the same thing on your Envy for the drivers and maybe restart if you get the code 10 again, it might be that simple
http://pcsupport.about.com/od/findbyerrormessage/a/code-10-error.htm
SHANENATAS said:
Try switching USB ports, I have only 3 on this laptop, the 2 on the left wont work, but the one on the right does. This is new laptop it has todo with usb version or speed
---------- Post added at 05:31 PM ---------- Previous post was at 05:28 PM ----------
Do the same thing on your Envy for the drivers and maybe restart if you get the code 10 again, it might be that simple
http://pcsupport.about.com/od/findbyerrormessage/a/code-10-error.htm
Click to expand...
Click to collapse
FML I unlocked the bootloader took like 20 seconds on Windows 7, its because it was windows 8 that everything was buggin out.... wth
Sweet, I'm happy and jealous. Hope everything else goes smooth. For your recovery I like CWMR-6.0.2.8. But to each his own. I'll check here in a little bit, I'm hoping someone figures out a way to unlock the bootloader or downgrade soon so I can be rooted once again.
irockthebear said:
FML I unlocked the bootloader took like 20 seconds on Windows 7, its because it was windows 8 that everything was buggin out.... wth
Click to expand...
Click to collapse
Edit- NM figured it out. Thanks.. wow
irockthebear said:
Hey Guys,
So now when I type the "fastboot flash recovery recovery.img"
It keeps saying "error cannot load 'recovery.img': Unknown error
Click to expand...
Click to collapse
did you put the recovery in the right folder? if the img you're going to use ins't named recovery.img you need to change the name or vise versa in cmd. Get what I'm saying?
Following the TUT is great, but sometimes when we download what we need it might be named different. Like mine is DNA.CWR6.img, so first I put that file in my adb folder, second in the cmd window I type "fastboot flash DNA.CWR6.img" OR do it how you are doing it but rename DNA.CWR6.img to recovery.img
SHANENATAS said:
did you put the recovery in the right folder? if the img you're going to use ins't named recovery.img you need to change the name or vise versa in cmd. Get what I'm saying?
Following the TUT is great, but sometimes when we download what we need it might be named different. Like mine is DNA.CWR6.img, so first I put that file in my adb folder, second in the cmd window I type "fastboot flash DNA.CWR6.img" OR do it how you are doing it but rename DNA.CWR6.img to recovery.img
Click to expand...
Click to collapse
Hi Guys,
Thanks so much for your help in getting me up and running esp you SHANENATAS. I love Sense 5, everything seems to work except MMS. I hope a port comes out for you guys soon!
I honestly think Sense 5 is by far the best rom I have used, it was actually the only one other than cyonogenmod 10 stock android that I considered going to.
The backgrounds are not included, but you can download those easily!
AWSOME upgrade! Funny thing is my windows 7 computer doesn't recognize the DNA now lol... oh well I already did what I had to so I dont need to use fastboot anymore. So in total it took about 30 hours to get this for a total non programmer! Tip to anyone attempting this is to do it on Windows 7, a lot less issues.
Lol havent eaten since 10am it is now 8pm because I have been working non stop on this; going to get dinner now. My girlfriend was wicked pissed off because I was supposed to buy ingredients to make chili with her but I never left the house.
Also guys please note if you are attempting this please install this version of Sense 5 http://forum.xda-developers.com/showthread.php?t=2184706
The previous versions would just crash when connected to wifi....
Thanks Everyone! Awsome walkthrough too, drumz0rz!!
Funny, my Windows 8 Sony Vaio has no problems in Fastboot, ADB etc. All the drivers loaded right up. Glad to hear you got everything going. Me, I'm waiting patiently for an unlock exploit for the OTA 2.04 fw. My replacement phone has the update.
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...
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.