So...last night Loki was trying to help me. My Omate wasn't allowing me to flash anything. After Loki's suggestions didn't work, I thought taking my Omate back to stock would hopefully fix the device and allow me to flash something. However, after following Loki's reset to stock guide, now not only will my Omate not turn on, but my computer will not recognize the device nor will Flash Tool.
So, what should I do? What could I have done wrong?
kp12584 said:
So...last night Loki was trying to help me. My Omate wasn't allowing me to flash anything. After Loki's suggestions didn't work, I thought taking my Omate back to stock would hopefully fix the device and allow me to flash something. However, after following Loki's reset to stock guide, now not only will my Omate not turn on, but my computer will not recognize the device nor will Flash Tool.
So, what should I do? What could I have done wrong?
Click to expand...
Click to collapse
Win7 or 8
Sent from my HTC One using Tapatalk
mghtymse007 said:
Win7 or 8
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Update: I removed the battery and now it turns on. However, I still am unable to flash stock (or any other ROM) still.
Win 7
My win7 system requires a reinstall of the flash drivers after a few flashes. Remove the current driver, restart and do a reinstall of the driver. Or do it manually.
Sent from my HTC One using Tapatalk
mghtymse007 said:
My win7 system requires a reinstall of the flash drivers after a few flashes. Remove the current driver, restart and do a reinstall of the driver. Or do it manually.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
I've been knee deep in drivers all day - which drivers are you referring to? The MTK ones (for stock flashing)? Koush?
Sweet baby Cheesus, it just worked.
I don't know why...
kp12584 said:
Sweet baby Cheesus, it just worked.
I don't know why...
Click to expand...
Click to collapse
Good for you. I meant the MTK 65XX VCOM drivers.
Win7 and these drivers, along with the configuration can cause the flash tool and drivers to be touchy at times. Sometimes a restart and reinstall is all is takes.
Sent from my HTC One using Tapatalk
Related
So I rooted my Evo successfully as well as the Evo of one of my good friends. However, a second friend of mine wanted his new Evo rooted so I naturally obliged. However, his phone repeatedly gave me the finger when I tried to root it. Here is what happened:
1. Executed root script via THIS METHOD
2. Script began rooting.
3. Script entered first phone restart phase.
4. Script entered second phone restart phase.
5. When phone turned back on my laptop no longer recognized he device (i.e. Android 1.0 in Device Manager) and so the script could not continue its process.
My attempted solutions:
1. Reset to factory settings and reattempt to root. (Failed)
2. Reset to factory settings and attempted to root using RegawMOD (Failed)
3. Did not try to RUU as I did not have the RUU necessary for his device.
My question here is this....if I RUU his device and reattempt the root is it likely that I will encounter the same issue as I did initially? I do not know whether this was an issue of the rooting process or an issue with the drivers on my laptop. My powers of deduction tell me it is based within the phone since immediately after his phone was unrecognized I was able to plug my phone in, as well as my other friend's Evo, and have my laptop recognize both devices instantly.
Cliff Notes:
My Evo: Rooted Successfully
Friend #1's Evo: Rooted Successfully
Friend #2's Evo: Root Unsuccessful
Personally I would just HTCDev unlock his phone and flash TWRP...then download whatever rom (even the rooted stock if he wants to stay 100% stock) and flash it. Best way to root imho. Hasn't failed me yet!
I would try re updating the htc drivers for your pc
Sent from my EVO using Tapatalk
bhint15 said:
Personally I would just HTCDev unlock his phone and flash TWRP...then download whatever rom (even the rooted stock if he wants to stay 100% stock) and flash it. Best way to root imho. Hasn't failed me yet!
Click to expand...
Click to collapse
RagawMOD root uses the htcDev method. It failed as I stated in the original post.
thicklizard said:
I would try re updating the htc drivers for your pc
Sent from my EVO using Tapatalk
Click to expand...
Click to collapse
I updated my drivers like 10 times. Plus, like I said, my phone a well as my other friend's phone works just fine.
Sent from my EVO using XDA
Concordium said:
RagawMOD root uses the htcDev method. It failed as I stated in the original post.
I updated my drivers like 10 times. Plus, like I said, my phone a well as my other friend's phone works just fine.
Sent from my EVO using XDA
Click to expand...
Click to collapse
If you have the most up to date drivers in device manager it will show "my htc" not android 1.0.
Sent from my EVO using Tapatalk
Concordium said:
RagawMOD root uses the htcDev method. It failed as I stated in the original post.
I updated my drivers like 10 times. Plus, like I said, my phone a well as my other friend's phone works just fine.
Sent from my EVO using XDA
Click to expand...
Click to collapse
Interesting. It definitely sounds like Drivers. The quote below me is right on. I was having this problem as well. The only thing I can think of is that you have a couple sets of drivers on your computer. When you go to update it updates with the old drivers (don't know why). I had this issue with my Kindle Fire.
Have you tried to update the drivers by manually selecting where to find the drivers?
thicklizard said:
If you have the most up to date drivers in device manager it will show "my htc" not android 1.0.
Sent from my EVO using Tapatalk
Click to expand...
Click to collapse
purock said:
Interesting. It definitely sounds like Drivers. The quote below me is right on. I was having this problem as well. The only thing I can think of is that you have a couple sets of drivers on your computer. When you go to update it updates with the old drivers (don't know why). I had this issue with my Kindle Fire.
Have you tried to update the drivers by manually selecting where to find the drivers?
Click to expand...
Click to collapse
I guess I should've added that to the OP. Part of my fix prices was also to completely uninstall all HTC drivers and reinstall them. I used the drivers from PDANet since those were the only ones that managed to work correctly. All of the others wouldn't install correctly.
Sent from my EVO using XDA
After the JB update, I can't seem to get Diagnostic Mode ##3424# to work. I've tried stock with goodies and OMJ build. Diag port doesn't show up in Windows 7. It does show up in Windows XP but driver doesn't install. Previous ICS worked on both XP and Win7. I've gone back to Stock with goodies ICS to confirm it still works. I'm just hoping ot have it available in JB.
Any help appreciated. Thanks.
Diag mode works for my stock rooted JB w/ s-off
Sent from my EVO using xda app-developers app
decayer177 said:
Diag mode works for my stock rooted JB w/ s-off
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
It's enabled but doesn't get installed properly in windows like ICS diag mode. You're still showing up in Windows correctly has diag modem?
supernoman said:
It's enabled but doesn't get installed properly in windows like ICS diag mode. You're still showing up in Windows correctly has diag modem?
Click to expand...
Click to collapse
Having the same problem. I can get into diagnostic mode on the phone but in Windows it won't show up as a modem in device manager or show what port (i was trying to manually change prl). Tried reinstalling HTC diagnostic drivers but it says it's not the right drivers for my device. Which is strange since they worked when I was on ics. I guess something changed on the drivers front with jelly bean.
Sent from my EVO using xda app-developers app
B1GQ1B said:
Having the same problem. I can get into diagnostic mode on the phone but in Windows it won't show up as a modem in device manager or show what port (i was trying to manually change prl). Tried reinstalling HTC diagnostic drivers but it says it's not the right drivers for my device. Which is strange since they worked when I was on ics. I guess something changed on the drivers front with jelly bean.
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
Check this post I just got mine installed running MeanBean
http://forum.xda-developers.com/showpost.php?p=28717758&postcount=8
bigdaddy619 said:
Check this post I just got mine installed running MeanBean
http://forum.xda-developers.com/showpost.php?p=28717758&postcount=8
Click to expand...
Click to collapse
I ended up going back to ice cream to flash a custom prl. Thanks for this tho, I'll definitely bookmark it for next time.
Sent from my EVO using xda app-developers app
B1GQ1B said:
I ended up going back to ice cream to flash a custom prl. Thanks for this tho, I'll definitely bookmark it for next time.
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
Yeah that post is like GOLD haha saved my butt a few times and welcome
Any solution for XP
Tried the above for XP but it does not work...
aankush said:
Any solution for XP
Tried the above for XP but it does not work...
Click to expand...
Click to collapse
Try this to get the drivers installed correctly
http://forum.xda-developers.com/showpost.php?p=28717758&postcount=8
bigdaddy619 said:
Try this to get the drivers installed correctly
http://forum.xda-developers.com/showpost.php?p=28717758&postcount=8
Click to expand...
Click to collapse
My bet is that only works for windows 7. I've that post with both windows xp 32 bit and windows 8 64 bit and on both it tells me the drivers are not designed for my hardware (or something to that effect).
For now those on either of those OS's might just have to nandroid, flash ICS do their PRL update and then restore their JB nandroid.
Unless anyone else has figured out the proper drivers?
supernoman said:
After the JB update, I can't seem to get Diagnostic Mode ##3424# to work. I've tried stock with goodies and OMJ build. Diag port doesn't show up in Windows 7. It does show up in Windows XP but driver doesn't install. Previous ICS worked on both XP and Win7. I've gone back to Stock with goodies ICS to confirm it still works. I'm just hoping ot have it available in JB.
Any help appreciated. Thanks.
Click to expand...
Click to collapse
you need to install the drivers first. look at this page for help http://forum.xda-developers.com/showthread.php?t=1769284&highlight=qpst+make+evo+louder . if you are on windows 7 64 bit like me and are having troubles with the guide that was first provided look here http://forum.xda-developers.com/showpost.php?p=28717758&postcount=8 ask me if you have any questions, i went through the same thing so i probally will know the answer. hope this helped.
P.S. the guide I provided was for use with qpst so if you aren't going to be using that only do steps 1,3,4, and 5. also this person probably meant step 3 not 4 when he says this "Browse to the folder containing the drivers your downloaded in step 4" in step 4
try changing to disk drive instead of HTC Sync Manager option in the phones drop down menu. that should install the diag drivers that you have already.
So I have finally gotten around to unlocking the bootloader so I can install the Atrix-MROM flash to stop having the battery and overheating issues that seem to be present with the latest update. I've been trying to use the procedure outlined in this thread: http://forum.xda-developers.com/showthread.php?t=1182871 , but when I reach the RSD Lite stage the driver cannot be found. I believe this is the flash interface driver going off of what I've seen, but I'm also a little new to all this. I've tried searching the threads and found nothing, and did a little googling. Any info on where I can get the driver or some other fix? And sorry if this has actually been solved, but I couldn't find anything.
onemanwlfpk said:
So I have finally gotten around to unlocking the bootloader so I can install the Atrix-MROM flash to stop having the battery and overheating issues that seem to be present with the latest update. I've been trying to use the procedure outlined in this thread: http://forum.xda-developers.com/showthread.php?t=1182871 , but when I reach the RSD Lite stage the driver cannot be found. I believe this is the flash interface driver going off of what I've seen, but I'm also a little new to all this. I've tried searching the threads and found nothing, and did a little googling. Any info on where I can get the driver or some other fix? And sorry if this has actually been solved, but I couldn't find anything.
Click to expand...
Click to collapse
do you have the proper drivers installed for rsd? there's a 32 bit and a 64 bit version
Sent from my MB860 using xda app-developers app
palmbeach05 said:
do you have the proper drivers installed for rsd? there's a 32 bit and a 64 bit version
Sent from my MB860 using xda app-developers app
Click to expand...
Click to collapse
What I have is the latest Moto drivers from the webpage, and the script that was uploaded unto the thread listed. Are you saying that the source of my problem is that like a noob I missed a set of drivers and that's why when I connect the phone in RSD mode it doesn't work?
onemanwlfpk said:
What I have is the latest Moto drivers from the webpage, and the script that was uploaded unto the thread listed. Are you saying that the source of my problem is that like a noob I missed a set of drivers and that's why when I connect the phone in RSD mode it doesn't work?
Click to expand...
Click to collapse
If you say you do have the latest drivers from Motorola, you should be fine. I'm not sure what RSD version is coming with the automatic bootloader, but I know that there is an updated one, its 5.7. There might be an updated one from that, but that's at least what I have. Try searching and using that and post what happens.
palmbeach05 said:
If you say you do have the latest drivers from Motorola, you should be fine. I'm not sure what RSD version is coming with the automatic bootloader, but I know that there is an updated one, its 5.7. There might be an updated one from that, but that's at least what I have. Try searching and using that and post what happens.
Click to expand...
Click to collapse
Okay, so I found and installed RSD 6.1.4, and double checked my drivers. The moto drivers are version 6.0.0. Attached is a print screen of what happens as I try to connect and use RSD.
Just a hunch. Consider trying to add the drivers manually. Go into the device manager, update driver software, let me pick, then look around. I dunno what they'll be called or, if they will even be there. But it is worth a shot for sure.
If that doesn't work then you might think about trying a different usb cable/usb port/pc/32 or 64bit versions. Sucks, but been there done that one... Hoping that one of those helps you.
Good luck.
JdgM3NT4L said:
Just a hunch. Consider trying to add the drivers manually. Go into the device manager, update driver software, let me pick, then look around. I dunno what they'll be called or, if they will even be there. But it is worth a shot for sure.
If that doesn't work then you might think about trying a different usb cable/usb port/pc/32 or 64bit versions. Sucks, but been there done that one... Hoping that one of those helps you.
Good luck.
Click to expand...
Click to collapse
Yeah I ended up trying the process on my desktop that runs WinXP instead. Worked like a charm so now I've moved on to the rest of the process. Thanks for the advice on that. Must be something wonky with my laptop.
onemanwlfpk said:
Yeah I ended up trying the process on my desktop that runs WinXP instead. Worked like a charm so now I've moved on to the rest of the process. Thanks for the advice on that. Must be something wonky with my laptop.
Click to expand...
Click to collapse
Glad to hear that you got it. Nice work!
It could be a wonky lappy. Myself I think it is because I try to adb and stuff for a lot of different devices on my pc. Seems like if only one device has ever been installed everything is fine. But once I start adding more devices and drivers to the pc it get confused and a lot of things just do not work. I either have to do some serious driver cleanup, or switch machines to be effective. I've moved on to a Samsung phone, but my Wife and Daughter still rock their Atrix(s(?)) So I try to use my lappy for those and my desktop for my Sammys. So far so good here.
So I think I messed up somehow. I tried to flash from Aroma to CWM 10.1. I wiped well but CWN failed to install and somehow it seems the bootloader locked and Odin will not see my Verizon Note 2. How the hell am I supposed to fix this, I dont think the Verizon still will help meh.
R u able to get into recovery mode
ajeteja said:
R u able to get into recovery mode
Click to expand...
Click to collapse
With down+home+power yes. But not sure what I can do. It just laughs at me with the "downloading"
Droidhsv said:
So I think I messed up somehow. I tried to flash from Aroma to CWM 10.1. I wiped well but CWN failed to install and somehow it seems the bootloader locked and Odin will not see my Verizon Note 2. How the hell am I supposed to fix this, I dont think the Verizon still will help meh.
Click to expand...
Click to collapse
If I try to get into my TWRP it get the software message. I cannot start the phone, if I try to I get the boot logo then it shuts off. Really think im screwed here
Let's clarify. You tried to install cwm, it failed and now your phone says unauthorized software take to Verizon? Your post honestly doesn't make sense. Oh and now Odin won't see your phone?
If this is correct then your phone is far from screwed up. Very common it's what happens when you don't unlock the bootloader. So let's get your phone seen by Odin. Are you in download mode? What os is your computer? Have you trired different usb ports? Are drivers installed?
Oh ya Here's A Little reading material for you
http://forum.xda-developers.com/showthread.php?p=39299305
Sent from my SGH-T889 using xda app-developers app
kintwofan said:
Let's clarify. You tried to install cwm, it failed and now your phone says unauthorized software take to Verizon? Your post honestly doesn't make sense. Oh and now Odin won't see your phone?
If this is correct then your phone is far from screwed up. Very common it's what happens when you don't unlock the bootloader. So let's get your phone seen by Odin. Are you in download mode? What os is your computer? Have you trired different usb ports? Are drivers installed?
Oh ya Here's A Little reading material for you
http://forum.xda-developers.com/showthread.php?p=39299305
Sent from my SGH-T889 using xda app-developers app
Click to expand...
Click to collapse
Seeing as when I tried to switch to CWM I was already on Aroma I am confused as to how my bootloader got locked. I have been installing, uninstalling all over the place. in fact im still doing it. to answer your questions: yes,7 and 8,yes,covered.
And believe me I know that article inside and out. If I could get my odin to work Id be in fields of gold. Conveniently I have a new computer arriving today that I will try to get it to work with. It seems that my computer cant figure out how to communicate with it.
It calls it a "Gadget Serial" downloading PC studio didnt seem to help
Droidhsv said:
Seeing as when I tried to switch to CWM I was already on Aroma I am confused as to how my bootloader got locked. I have been installing, uninstalling all over the place. in fact im still doing it. to answer your questions: yes,7 and 8,yes,covered.
And believe me I know that article inside and out. If I could get my odin to work Id be in fields of gold. Conveniently I have a new computer arriving today that I will try to get it to work with. It seems that my computer cant figure out how to communicate with it.
It calls it a "Gadget Serial" downloading PC studio didnt seem to help
Click to expand...
Click to collapse
You can't be on aroma. Aroma is a method used by ROM devs to allow the user to select options during install of their ROM. There are two recoveries, CWM and TWRP.
So you are seeing unauthorized software? Then your bootloader is locked, if it was unlocked then we'll figure that out later.
You should see gadget serial. Is it installing the drivers for that? How did you install drivers, Windows update our manually?
Sent from my SGH-T889 using xda app-developers app
kintwofan said:
Let's clarify. You tried to install cwm, it failed and now your phone says unauthorized software take to Verizon? Your post honestly doesn't make sense. Oh and now Odin won't see your phone?
If this is correct then your phone is far from screwed up. Very common it's what happens when you don't unlock the bootloader. So let's get your phone seen by Odin. Are you in download mode? What os is your computer? Have you trired different usb ports? Are drivers installed?
Oh ya Here's A Little reading material for you
http://forum.xda-developers.com/showthread.php?p=39299305
Sent from my SGH-T889 using xda app-developers app
Click to expand...
Click to collapse
kintwofan said:
You can't be on aroma. Aroma is a method used by ROM devs to allow the user to select options during install of their ROM. There are two recoveries, CWM and TWRP.
So you are seeing unauthorized software? Then your bootloader is locked, if it was unlocked then we'll figure that out later.
You should see gadget serial. Is it installing the drivers for that? How did you install drivers, Windows update our manually?
Sent from my SGH-T889 using xda app-developers app
Click to expand...
Click to collapse
Crud I meant CleanRom 4.8, not Aroma. Not sure what I was thinking.Yeah bootloader locked for sure.When I try to access recovery I get the System software not authorized....etc. I let it automatically install then tried manual install, removed kies,added kies. what do you mean by windows update?
Droidhsv said:
Crud I meant CleanRom 4.8, not Aroma. Not sure what I was thinking.Yeah bootloader locked for sure.When I try to access recovery I get the System software not authorized....etc. I let it automatically install then tried manual install, removed kies,added kies. what do you mean by windows update?
Click to expand...
Click to collapse
Okay, thanks for clarifying. That is a little strange then. I mean did you let Windows download the drivers for you, which you answered. You can try to put phone in download mode and keep plugging and unplugging it (give it time to recognize it first). There was a guy that said it eventually just recognized hos phone after 16 times. You did restart your computer correct?
Sent from my SGH-T889 using xda app-developers app
Yea restarted many times. Ill plug it in and in. not much hope for that though. I dont know what else to try
Droidhsv said:
Yea restarted many times. Ill plug it in and in. not much hope for that though. I dont know what else to try
Click to expand...
Click to collapse
Your new computer that's on the way
Sent from my SGH-T889 using xda app-developers app
kintwofan said:
Your new computer that's on the way
Sent from my SGH-T889 using xda app-developers app
Click to expand...
Click to collapse
-_- na shizz
Well problem solved. Threw a last ditch effort and went to Verizon. BEST SERVICE EVER. no problems free replacement with free overnight shipping. All you win are belong to me naow
Droidhsv said:
So I think I messed up somehow. I tried to flash from Aroma to CWM 10.1. I wiped well but CWN failed to install and somehow it seems the bootloader locked and Odin will not see my Verizon Note 2. How the hell am I supposed to fix this, I dont think the Verizon still will help meh.
Click to expand...
Click to collapse
I cant figure out how to get aroma to launch my aosp lockscreen from download mode while sideloading odin. HELP. Im running jellybam cm-7 beans on my galaxy note 1.5. Please... im stuck.. now i cant boot.
Sorry...had to do it.
Sent from my SCH-I605 using XDA Premium HD app
Chance77 said:
I cant figure out how to get aroma to launch my aosp lockscreen from download mode while sideloading odin. HELP. Im running jellybam cm-7 beans on my galaxy note 1.5. Please... im stuck.. now i cant boot.
Sorry...had to do it.
Sent from my SCH-I605 using XDA Premium HD app
Click to expand...
Click to collapse
Someone woke up on the butthurt side of bed this morning
You're most likely not bricked if it will turn on at ALL! Here's what you need to do:
1. Make sure your computer is setup with the proper drivers/ODIN.
2. Go here and download the stock ODIN image
3. Get a different USB cord you know works or try the most rearest USB port and put your phone in ODIN mode as stated above.
4. If ODIN doesn't recognize your phone, restart the computer with it plugged in and unplug it and replug it...
5. Flash ODIn in the PDA, not the Phone section (Follow the directions given by Imnuts).
That should fix you up, if it doesn't, chances are you missed a step. Good luck:victory:
---------- Post added at 10:29 PM ---------- Previous post was at 10:26 PM ----------
Droidhsv said:
Well problem solved. Threw a last ditch effort and went to Verizon. BEST SERVICE EVER. no problems free replacement with free overnight shipping. All you win are belong to me naow
Click to expand...
Click to collapse
You didn't win, since you don't know what you did wrong. You should read a lot more before you mess up this phone. Give it time and you probably will be in the same place again. Read, read read read read and did I mention read???? Better luck though with your new device
andrewjt19 said:
You're most likely not bricked if it will turn on at ALL! Here's what you need to do:
1. Make sure your computer is setup with the proper drivers/ODIN.
2. Go here and download the stock ODIN image
3. Get a different USB cord you know works or try the most rearest USB port and put your phone in ODIN mode as stated above.
4. If ODIN doesn't recognize your phone, restart the computer with it plugged in and unplug it and replug it...
5. Flash ODIn in the PDA, not the Phone section (Follow the directions given by Imnuts).
That should fix you up, if it doesn't, chances are you missed a step. Good luck:victory:
---------- Post added at 10:29 PM ---------- Previous post was at 10:26 PM ----------
You didn't win, since you don't know what you did wrong. You should read a lot more before you mess up this phone. Give it time and you probably will be in the same place again. Read, read read read read and did I mention read???? Better luck though with your new device
Click to expand...
Click to collapse
Well did ALL that before. Surprise none of it worked. I'm not going to repeat the same process over and over. I'm pretty sure I know why I couldn't get it to work, and I know what went wrong even though I'm not sure how managed it. And getting a new scratch free phone for no cost sounds pretty good.
Droidhsv said:
Well did ALL that before. Surprise none of it worked. I'm not going to repeat the same process over and over. I'm pretty sure I know why I couldn't get it to work, and I know what went wrong even though I'm not sure how managed it. And getting a new scratch free phone for no cost sounds pretty good.
Click to expand...
Click to collapse
Good luck.
Sent from my SCH-I605 using xda premium
Droidhsv said:
Well did ALL that before. Surprise none of it worked. I'm not going to repeat the same process over and over. I'm pretty sure I know why I couldn't get it to work, and I know what went wrong even though I'm not sure how managed it. And getting a new scratch free phone for no cost sounds pretty good.
Click to expand...
Click to collapse
If you went thru VZW and they are shipping you a new phone then it isnt new. They send out refurbished phones as replacements, I think they referr to them as CLN phones.
Sent from my SCH-I605 using XDA Premium HD app
Back in March I was rooted, running a cool sense 5 based custom ROM and happy. But the phone had other ideas. It stopped recognizing the SIM card and the replacement phone Verizon sent was on the latest firmware which we couldn't hack. I couldn't deal with the stock configuration after having the custom ROM so I binned the phone and went back to my old GS3 hoping to someday be able to go back to the DNA.
If I understand things correctly, that day has come and we can root the current firmware equipped phones.....Correct? I've read thru a number of posts and all it has done is left me confused and hesitant to give it a shot.
Can someone help me out with the correct steps, methods and procedures to root my stock, S-on DNA running the latest OTA firmware (2.06)? Any help is greatly appreciated!!
http://forum.xda-developers.com/showthread.php?t=2314771
scheirere said:
Back in March I was rooted, running a cool sense 5 based custom ROM and happy. But the phone had other ideas. It stopped recognizing the SIM card and the replacement phone Verizon sent was on the latest firmware which we couldn't hack. I couldn't deal with the stock configuration after having the custom ROM so I binned the phone and went back to my old GS3 hoping to someday be able to go back to the DNA.
If I understand things correctly, that day has come and we can root the current firmware equipped phones.....Correct? I've read thru a number of posts and all it has done is left me confused and hesitant to give it a shot.
Can someone help me out with the correct steps, methods and procedures to root my stock, S-on DNA running the latest OTA firmware (2.06)? Any help is greatly appreciated!!
Click to expand...
Click to collapse
So I just follow the steps listed in the link above and I'll be ready to flash a custom ROM? No HTC unlock code and such?
Correct.
Sent from my HTC6435LVW using Tapatalk 4 Beta
beaups said:
Correct.
Sent from my HTC6435LVW using Tapatalk 4 Beta
Click to expand...
Click to collapse
Ok, gave it a shot with the windows version and didn't succeed. Followed the instructions and definitely made sure there was no trace of HTC Sync on the computer. When I run the Distiller.exe file, everything seems to run OK for test 1 (rebooting into bootloader) and test 2 (booting device) were the phone reboots like normal. Then the script says rebooting into bootloader (again) and sits there waiting for fastboot. It times out after 60 seconds and says connection failed. usb connection error.
Any ideas on were to go from here?
You need fastboot drivers.
Sent from my HTC6435LVW using Tapatalk 4 Beta
Moonshine works great
Sent from my HTC6435LVW using xda app-developers app
Suggestions on were I can get those fastboot drivers?
Google HTC fastboot drivers. If you are on win8 with usb 3 ports only you can expect issues.
Sent from my HTC6435LVW using Tapatalk 4 Beta
Googled HTC fastboot driver and it looks like I need HTCDriver3.0.0.007.exe . If I google HTC android drivers I can find another file HTCDriver_4.2.0.001.exe. Tried them both on my home windows 7 machine with a USB2 port. Nothing changed. Same results.
So I tried the window XP computer at my office that I originally used to root the old DNA. Got a little further this time. I get a message that temproot has failed. I also get a lot of stuff going on with "other devices" drivers when I watch my device manager. Is this normal during the process?
scheirere said:
Googled HTC fastboot driver and it looks like I need HTCDriver3.0.0.007.exe . If I google HTC android drivers I can find another file HTCDriver_4.2.0.001.exe. Tried them both on my home windows 7 machine with a USB2 port. Nothing changed. Same results.
So I tried the window XP computer at my office that I originally used to root the old DNA. Got a little further this time. I get a message that temproot has failed. I also get a lot of stuff going on with "other devices" drivers when I watch my device manager. Is this normal during the process?
Click to expand...
Click to collapse
Ok temproot failing means factory reset time. You should be good after that.
Sent from my HTC6435LVW using Tapatalk 4 Beta
That did the trick!! Factory reset and the older XP machine. God, how much I missed the custom roms for this phone. It totally transforms the device.
As for the Moonshine process, like I said, it worked for me but I did run into a few more speed bumps. Everytime the phone would reboot, I had to squash the HTCsync install. I guess it's something on the phone as I searched hi and low to find anything like it on the computer, with no luck. Anyhow, I would just cancel out everytime the message appeared on the screen. If I didn't cancel out, the moonshine script would time out and fail.
Just wanted to follow up on this in case someone else has similar issues.
Thanks again, guys!