Related
Yes, while I understand there have been many threads in regards to RSD Lite not recognizing phones, hear me out as none of them have been helpful to me. I recently got into the world of rooting and flashing roms, so like a fool yesterday I flashed Eclipse v.1 over 2.3.3. Ever since I have been experience the wifi connectivity issue, so reasonably I tried to use RSD lite to get the 2.3.4 sbf onto my X2. However, using RSD 4.5.3 I kept getting a status message along the lines of "chipset type 53 is not supported." Trying it again also with the 2.3.3 sbf, I tried using RSD v.4.9 and 5.3.1, however neither would recognize my phone. Now I am beginning to encounter other issues with Eclipse (my own fault) and I would greatly appreciate any input. All drivers are up to date for anyone who was going to throw that out again.
Be sure the machine you are running rsd on has plenty of disk space.
I got wierd errors a while back when i was running next to full on the HD RSD makes a temporary file before it flashes.
mastafunk said:
Be sure the machine you are running rsd on has plenty of disk space.
I got wierd errors a while back when i was running next to full on the HD RSD makes a temporary file before it flashes.
Click to expand...
Click to collapse
I have more than enough HD space. When running 4.5.3 it has the chipset error as the device status when paired with any sbf.
Are you running RSD as administrator? Maybe that could be a problem but i dont know.
If you are rooted and have installed system recovery try and flash the 2.3.4 zip aligned update in recovery and see if that works
Sent from my DROID X2 using XDA App
phillyo2 said:
Are you running RSD as administrator? Maybe that could be a problem but i dont know.
Click to expand...
Click to collapse
Just tried both ways in 4.9, neither were successful
It might be quicker if you enumerated, step-by-step, how you last sbf'ed ... that way, the more experienced amongst us can determine where you went wrong.
Oh, and throw in details on your computer's OS, too ... I hear there have been some problems using RSD Lite with Windows 7.
Pj
Phoenix, AZ
pdinphx said:
It might be quicker if you enumerated, step-by-step, how you last sbf'ed ... that way, the more experienced amongst us can determine where you went wrong.
Oh, and throw in details on your computer's OS, too ... I hear there have been some problems using RSD Lite with Windows 7.
Pj
Phoenix, AZ
Click to expand...
Click to collapse
I attempted to sbf based on the standard method from what I've seen in threads: run RSD (various versions were attempted), select the sbf, start the RSD protocol on my phone THEN plug it into the usb, and so on.
brossma1 said:
If you are rooted and have installed system recovery try and flash the 2.3.4 zip aligned update in recovery and see if that works
Sent from my DROID X2 using XDA App
Click to expand...
Click to collapse
Just tried that, 2.3.3 isn't showing up when booting and 2.3.4 gets aborted due to signature verification failure or something along those lines.
I am curious as to what is meant by flash 2.3.4 zip aligned update?
---------- Post added at 10:32 PM ---------- Previous post was at 10:28 PM ----------
Also have u tried a factory reset from STOCK recovery? Not the bootstrap...STOCK...
Then see if rsd works
Aldo what method are u using to get to rsd protocol mode?
do u hold power and volume up? ((This is how I do it))
U can also find it with power and vol down then scroll down after u see dastboot on top...try both ways
I know I have had a couple timed where it took a few minutes for rsdlite to actually see my phone ...think it was trying to auto install drivers....
U try uninstallin moto drivers and reinstall? Something go wacky?
I use rsdlite 5.4.4 by the way
Astrotard Jones said:
Just tried that, 2.3.3 isn't showing up when booting and 2.3.4 gets aborted due to signature verification failure or something along those lines.
Click to expand...
Click to collapse
Signature verification sounds like the file corrupted. Try redownloading the sbf file through Firefox or chrome and unzip the file with 7zip.
Sent from my DROID X2 using XDA App
ashclepdia said:
I am curious as to what is meant by flash 2.3.4 zip aligned update?
---------- Post added at 10:32 PM ---------- Previous post was at 10:28 PM ----------
Also have u tried a factory reset from STOCK recovery? Not the bootstrap...STOCK...
Then see if rsd works
Aldo what method are u using to get to rsd protocol mode?
do u hold power and volume up? ((This is how I do it))
U can also find it with power and vol down then scroll down after u see dastboot on top...try both ways
I know I have had a couple timed where it took a few minutes for rsdlite to actually see my phone ...think it was trying to auto install drivers....
U try uninstallin moto drivers and reinstall? Something go wacky?
I use rsdlite 5.4.4 by the way
Click to expand...
Click to collapse
I have tried both methods of recovery, bootstrap and stock as well as the power+ vol up method and the method of accessing the RSD protocol through the vol down boot method. I have also tried reinstalling drivers as well. I also don't believe time was an issue with RSDlite as I gave each version a good 20 minutes to try to recognize my phone (excluding 4.5).
EvilTim said:
Signature verification sounds like the file corrupted. Try redownloading the sbf file through Firefox or chrome and unzip the file with 7zip.
Sent from my DROID X2 using XDA App
Click to expand...
Click to collapse
I will try that, I have yet to try 7zip. Also when I try to access the 2.3.3 sbf zip file from recovery it does not show up as an option.
The versions of RSD you are using are older, I've been using 5.5 without any issues. If the phone is not being recognized it could be a driver issue on your windows machine. My older computer cannot recognize my phone i think the USB is 1.0.
Use version 5.x.x and higher...
Sent from my DROID BIONIC using xda premium
Astrotard Jones said:
I have tried both methods of recovery, bootstrap and stock as well as the power+ vol up method and the method of accessing the RSD protocol through the vol down boot method. I have also tried reinstalling drivers as well. I also don't believe time was an issue with RSDlite as I gave each version a good 20 minutes to try to recognize my phone (excluding 4.5).
I will try that, I have yet to try 7zip. Also when I try to access the 2.3.3 sbf zip file from recovery it does not show up as an option.
Click to expand...
Click to collapse
U r not supposed to flash the sbf zip from recovery.
u should have all the files on ye computer
Other things to try if still stuck:
try rsd 5.3.1 its what I always use.
Try plugging in to a port in the back of the computer.
Try run as administrator when you start rsd lite
Read the tutorial in the android dev subforum, its in the sticky post.
Sent from my DROID X2 using XDA App
EvilTim said:
Other things to try if still stuck:
try rsd 5.3.1 its what I always use.
Try plugging in to a port in the back of the computer.
Try run as administrator when you start rsd lite
Read the tutorial in the android dev subforum, its in the sticky post.
Sent from my DROID X2 using XDA App
Click to expand...
Click to collapse
Also make sure correct Motorola drivers installed((different ones for 32bit and 64bit computer))
Try uninstall and reinstall drivers.
Kill all internet connection ((saw someone say before this was causing problems somehow...worth a shot..I think it had to do with when installing drivers it was doing something to find other drivers..not to sure but.couldn't hurt to try))
Maybe even just try a different computer all together ..
ashclepdia said:
Maybe even just try a different computer all together ..
Click to expand...
Click to collapse
agreed try another computer
hamburgerman said:
The versions of RSD you are using are older, I've been using 5.5 without any issues. If the phone is not being recognized it could be a driver issue on your windows machine. My older computer cannot recognize my phone i think the USB is 1.0.
Click to expand...
Click to collapse
I just reinstalled the drivers and tried 5.5, it didn't work sadly enough. Also, to every post under the quoted one; please read the thread before you throw out "advice."
Astrotard Jones said:
to every post under the quoted one; please read the thread before you throw out "advice."
Click to expand...
Click to collapse
No one read your whole post because you obviously didn't read the tutorial before you messed with your phone. So next time before you attempt to do something you clearly have no information on, read about it first. And instead of being a tool, thank us for at least TRYING to help you.
Sent from my DROID X2 using XDA App
I have been having data & app issues with my Photon for the last couple of days. And wanted to flash to have a clean slate. When I try to flash any sbf I get the screen below. Pulling the battery and rebooting gets me back into the ROM, but looks like it didn't flash. I have tried different sbf, data cables, versions of RSD Lite. I am stumped, and hope the pic may shed some light on the issue.
Sent from my MB520 using Tapatalk
Never seen that before, are you putting phone in rsd mode and is rsd coming back with an error aside from the norm?
Sent from my MB855 using XDA App
Yep, I put the phone in RSD mode.
This is the message I get after it happens.
budney said:
Yep, I put the phone in RSD mode.
This is the message I get after it happens.
Click to expand...
Click to collapse
I might try to reinstall the latest drivers/motohelper plug in the phone, see if the drivers install on the phone, and then reboot the phone, and then try RSD again...i had some driver issues the other day, so check it out.
KTT16 said:
I might try to reinstall the latest drivers/motohelper plug in the phone, see if the drivers install on the phone, and then reboot the phone, and then try RSD again...i had some driver issues the other day, so check it out.
Click to expand...
Click to collapse
Good thinking, but still not flashing.
looks like it is getting stuck on the BP, it flashes the AP then the device reboots and flashed the BP. Try a stock rom
halfdriven said:
looks like it is getting stuck on the BP, it flashes the AP then the device reboots and flashed the BP. Try a stock rom
Click to expand...
Click to collapse
That is what I always used and have been trying to flash.
budney said:
I have been having data & app issues with my Photon for the last couple of days. And wanted to flash to have a clean slate. When I try to flash any sbf I get the screen below. Pulling the battery and rebooting gets me back into the ROM, but looks like it didn't flash. I have tried different sbf, data cables, versions of RSD Lite. I am stumped, and hope the pic may shed some light on the issue.
Sent from my MB520 using Tapatalk
Click to expand...
Click to collapse
did you work it out? I had the same thing happen me.
budney said:
Good thinking, but still not flashing.
Click to expand...
Click to collapse
Honestly not too sure what to tell you, sure someone will pop in and help out. I personally couldn't for the life of me get the drivers to install correctly on my main desktop to get RSDLite to work right, but I tried it on an old desktop laying around and boom first shot it worked great, if you have easy access to a second comp I would give that a shot because it seems like your missing a driver set somewhere. Have you flashed anything through RSDlite before with this computer onto your Photon or is this your first attempt?
nuxbag said:
did you work it out? I had the same thing happen me.
Click to expand...
Click to collapse
Nope! Did you fix it? If so how?
w0lf215 said:
Honestly not too sure what to tell you, sure someone will pop in and help out. I personally couldn't for the life of me get the drivers to install correctly on my main desktop to get RSDLite to work right, but I tried it on an old desktop laying around and boom first shot it worked great, if you have easy access to a second comp I would give that a shot because it seems like your missing a driver set somewhere. Have you flashed anything through RSDlite before with this computer onto your Photon or is this your first attempt?
Click to expand...
Click to collapse
This is the first time flashing with this Photon. It's a referb I received a few weeks ago. My original Photon flashed fine.
No spare PC or laptop around to try. Could installing XP solve the issue, or win7 32 bit? My PC is running win7 64 bit.
Try 198_7. I had the same issues with 198_6 I believe. Switching to a different sbf fixed my issues. I also had better results on a windows XP box. In pure windows and not a virtual machine.
Sent from my MoPho. All typos are the phones fault.
budney said:
This is the first time flashing with this Photon. It's a referb I received a few weeks ago. My original Photon flashed fine.
No spare PC or laptop around to try. Could installing XP solve the issue, or win7 32 bit? My PC is running win7 64 bit.
Click to expand...
Click to collapse
I did it/do everything with 32bit Win7, but don't want to tell you to go through the hassle of installing an entire OS considering it is just a shot in the dark as to whether it will fix it or not. Only other thing i would think to try would be putting the phone into RSD mode and plugging it into computer and see if Windows installs any drivers that way BEFORE trying to open up and flash through RSDlite.
budney said:
Nope! Did you fix it? If so how?
yes i did get it to work
---------- Post added at 11:15 PM ---------- Previous post was at 11:07 PM ----------
budney said:
Nope! Did you fix it? If so how?
Click to expand...
Click to collapse
can you tell me what rsd lite you are useing and where you got your DL's from. It has noting to do with XP or 7 I have both and i got the screen tare with both
Click to expand...
Click to collapse
nuxbag said:
can you tell me what rsd lite you are useing and where you got your DL's from. It has noting to do with XP or 7 I have both and i got the screen tare with both
Click to expand...
Click to collapse
Using 5.5 and the ROMS are from here: http://forum.xda-developers.com/showpost.php?p=20331570&postcount=3
Well flashing with 198_7 worked! But isn't that a leaked ROM? And where is the best place to download 198_6? Just never had luck with customs, stock + root works for me.
budney said:
Using 5.5 and the ROMS are from here: http://forum.xda-developers.com/showpost.php?p=20331570&postcount=3
Well flashing with 198_7 worked! But isn't that a leaked ROM? And where is the best place to download 198_6? Just never had luck with customs, stock + root works for me.
Click to expand...
Click to collapse
ok if you got working then flash this 1FF-sunfire-user-2.3.4-4.5.1A-1_SUN-154_5-CM-release-keys-signed-Sprint-US in post 3 and use mirror4 then ota update to 1FF-sunfire-user-2.3.4-4.5.1A-1_SUN-198_6-CM.
---------- Post added at 11:47 PM ---------- Previous post was at 11:41 PM ----------
budney said:
Using 5.5 and the ROMS are from here: http://forum.xda-developers.com/showpost.php?p=20331570&postcount=3
Well flashing with 198_7 worked! But isn't that a leaked ROM? And where is the best place to download 198_6? Just never had luck with customs, stock + root works for me.
Click to expand...
Click to collapse
ok if you got working then flash this 1FF-sunfire-user-2.3.4-4.5.1A-1_SUN-154_5-CM-release-keys-signed-Sprint-US in post 3 and use mirror4 then ota update to 1FF-sunfire-user-2.3.4-4.5.1A-1_SUN-198_6-CM. DL rsd lite 5.6 from post 4
nuxbag said:
ok if you got working then flash this 1FF-sunfire-user-2.3.4-4.5.1A-1_SUN-154_5-CM-release-keys-signed-Sprint-US in post 3 and use mirror4 then ota update to 1FF-sunfire-user-2.3.4-4.5.1A-1_SUN-198_6-CM. DL rsd lite 5.6 from post 4
Click to expand...
Click to collapse
Thanks, that sbf worked with out issue. doing the 198_6 OTA now, then root.
Thanks all for the help!
budney said:
Nope! Did you fix it? If so how?
This is the first time flashing with this Photon. It's a referb I received a few weeks ago. My original Photon flashed fine.
No spare PC or laptop around to try. Could installing XP solve the issue, or win7 32 bit? My PC is running win7 64 bit.
Click to expand...
Click to collapse
can somebody help me out my phone is only have rootaccess and i try to do the second step but i always fail so i restore my computer to factory and now i already rooted my phone whats next please help?
---------- Post added at 05:13 AM ---------- Previous post was at 05:12 AM ----------
it really does help read all the problem ppl have so you can learnd from there mistake=]]
RSDlite as administrator
@budney
Are you running RSDlite as an administrator?
HackGerm said:
@budney
Are you running RSDlite as an administrator?
Click to expand...
Click to collapse
Nope, but got it working. Was a problem with the sbf I think.
I've got an issue with Kies here. I connect my phone and open Kies, but it shows 'Connecting...' and doesn't progress. I've tried opening Kies in administrator mode etc, to no avail. I'm using the stock ROM with CWM recovery + root.
I can access the internal storage fine, and Odin obviously worked since I was able to flash the phone with CWM. For this reason I believe the drivers are functional.
The Kies troubleshoot button opens a dialog asking me to unplug the device and hit 'start', but pressing start does absolutely nothing (unless you leave the cable connected, which causes it to complain).
Anyone got any advice?
Edit: Now after a long wait, it tells me that my device is unsupported by Kies 2.0. I downloaded it off the SGSIII support page...
No one has any advice?
Same here! I get "device is unsupported by Kies 2.0" =/
I have this issue and it is to do with the mtp driver failing to install I think. Looking on the internet it only seems to be a problem for people with windows 64 bit operating systems. I have a couple of ideas on how to get it to work if i get it to work I will let you all know. Can i just confirm that both of you are running 64 bit windows 7?
Try installing the drivers via the Toolkit found in the Dev section. That worked for me.
slonn said:
Try installing the drivers via the Toolkit found in the Dev section. That worked for me.
Click to expand...
Click to collapse
Thanks for the suggestion but the MTP driver still won't install hmmmm
---------- Post added at 05:31 PM ---------- Previous post was at 04:49 PM ----------
Well I have fixed it but don't know if this well work for you. Basically when I flashed my firmware through Odin I forgot to flash the kernel as well. So check you have the right kernel for the firmware you have flashed. Hope this helps you
slonn said:
Try installing the drivers via the Toolkit found in the Dev section. That worked for me.
Click to expand...
Click to collapse
Didn't help. :/
Cyb3rGlitch said:
Didn't help. :/
Click to expand...
Click to collapse
Have you got the right kernel flashed or try re-flashing the correct kernel? fixed it for me!
dhendy91 said:
Have you got the right kernel flashed or try re-flashing the correct kernel? fixed it for me!
Click to expand...
Click to collapse
I'm using a stock device. Only thing I've flashed is CF Root, which uses the stock kernel.
might be stupid but try a new cable never know i know with omega 4.2 kies is not supported which i am on but if your still on stock and tried re-installing the drivers as mentioned above buy a new usb cable worth a try for as not expensive
Does anyone have a good downlink for RUU 4.03.605.2? I have searched everywhere to find one. The androidpolice site seems to be down as I get a javascript error when I try to download from there and none of the mirrors work. I tried to download from the dropbox link posted in a different topic but it was corrupted everytime I downloaded. I s-off'd as soon as I could and I haven't updated anything since except changed roms and want to update to the newest update and then go back to my current rom which is viper 1.0.3. Thanks for any help. Once I find the link I just need to flash the ruu twice, factory reset, flash jbear hboot, recovery and rom of my choice is that correct?
I distributed it as a torrent file within a few hours of Android Police posting it. Apparently uTorrent isn't very popular in these forums.
If we had a hundred seeders it would be the fastest way to download the RUU file.
If you like using uTorrent, here is the torrent file
http://db.tt/RsULMvOy
However, I don't think there are many seeders.
regards,
Howard
P.S. After downloading remember to check the MD5 with that published by Android Police
http://www.androidpolice.com/2012/0...ull-ruu-build-4-03-605-2-for-the-htc-rezound/
click the first mirror
works for me
scy1192 said:
http://www.androidpolice.com/2012/0...ull-ruu-build-4-03-605-2-for-the-htc-rezound/
click the first mirror
works for me
Click to expand...
Click to collapse
true the first was pretty fast for me since no one is really using it anymore.
yojoe600 said:
true the first was pretty fast for me since no one is really using it anymore.
Click to expand...
Click to collapse
I tried that one about 8 times yesterday and it never worked so I tried it again and I get the same error as yesterday "{"INFO":"failed posted hashcheck","SOLUTION":"please make sure you have javascript enabled for androidfilehost.com. Hit the back button, enable javascript and try again please. we promise we are probably not doing anything nefarious. maybe. no promises though."}" My javascript is already enabled and I am running Windows 7 Pro 64 bit w/windows explorer 9. I downloaded that bit torrent but it says it is corrupt and it took 4 hours to download.
Edit: I just tried it on Windows XP with explorer 8 and got the same error message.
Edit: Just downloaded Google Chrome and it is working. Internet Explorer is the problem.
Edit: I downloaded 3 different times from the androidfilehost website and from 3 different computers and all 3 times the zip file was corrupt.
BroncoAG said:
I tried that one about 8 times yesterday and it never worked so I tried it again and I get the same error as yesterday "{"INFO":"failed posted hashcheck","SOLUTION":"please make sure you have javascript enabled for androidfilehost.com. Hit the back button, enable javascript and try again please. we promise we are probably not doing anything nefarious. maybe. no promises though."}" My javascript is already enabled and I am running Windows 7 Pro 64 bit w/windows explorer 9. I downloaded that bit torrent but it says it is corrupt and it took 4 hours to download.
Edit: I just tried it on Windows XP with explorer 8 and got the same error message.
Edit: Just downloaded Google Chrome and it is working. Internet Explorer is the problem.
Edit: I downloaded 3 different times from the androidfilehost website and from 3 different computers and all 3 times the zip file was corrupt.
Click to expand...
Click to collapse
Try the download from your phone. I had the same invalid folder message when downloading it from a PC. Once I did it from my phone, the download worked.
vcmstone said:
Try the download from your phone. I had the same invalid folder message when downloading it from a PC. Once I did it from my phone, the download worked.
Click to expand...
Click to collapse
Thanks, I actually just tried that and it downloaded about 10x faster but I had the same error message. I verified the MD5 and then used a zip file repair to recover it and it worked. I just flashed it twice but it did fail on MDM_CUST, TPZ and Radio Cust2 and then I did a factory reset. It just rebooted and appears to be working correctly.
Shipped-roms.com, has it.....downloads fast. Vigor section.
Sent from my HTC Rezound / ADR6425LVW using Tapatalk v2.2.8
manbat said:
Shipped-roms.com, has it.....downloads fast. Vigor section.
Sent from my HTC Rezound / ADR6425LVW using Tapatalk v2.2.8
Click to expand...
Click to collapse
Thanks. there servers appear to be down. I'll try them again later. My phone appears to be working but the last update had 3 things fail on the update so I will probably redo it once I find a good download think. Thanks again.
EDIT: I got the same corrupt error message from shipped-roms as I did from Androidpolice on both my phone and computer. It got me thinking and it ended up being my winzip program was saying it was corrupt when it wasn't. I changed to 7zip and the error message went away and I just reflashed my phone and it went perfect without any errors. Thanks for the all the help.
yojoe600 said:
true the first was pretty fast for me since no one is really using it anymore.
Click to expand...
Click to collapse
how can i use this process. my phone says S-on and its stuck in a bootloop. is there a tool i can use with S-on? i downloaded the android police but my phone isn't being reconginize by my computer. what can i do. i've turned off my phone and hit the power button a few times while the battery was out. that didn't work. i took out the sd card and did it again. that didn't work. right now my phone also says tampered and relocked but i can't get it off the white screen. i did a factory reset and that didn't work i rebooted the bootloader and that didn't work. im totally lost now..
debo19832003 said:
how can i use this process. my phone says S-on and its stuck in a bootloop. is there a tool i can use with S-on? i downloaded the android police but my phone isn't being reconginize by my computer. what can i do. i've turned off my phone and hit the power button a few times while the battery was out. that didn't work. i took out the sd card and did it again. that didn't work. right now my phone also says tampered and relocked but i can't get it off the white screen. i did a factory reset and that didn't work i rebooted the bootloader and that didn't work. im totally lost now..
Click to expand...
Click to collapse
I would love to help but its been so long since I messed around with the Ruu I don't remember what to do (hey that rhymed) but I would ask someone int the Q&A sections they may be able to help you better than I.
yojoe600 said:
I would love to help but its been so long since I messed around with the Ruu I don't remember what to do (hey that rhymed) but I would ask someone int the Q&A sections they may be able to help you better than I.
Click to expand...
Click to collapse
haha. yea that was pretty funny. i did post it in the Q & A but no hits. it has almost 70 views but no one is bitting. i don't know if im giving too much info or not the right info. could you take a look at it and let me know if its something i could add or be more specific. i would have thought by now someone would have it figured out.
debo19832003 said:
haha. yea that was pretty funny. i did post it in the Q & A but no hits. it has almost 70 views but no one is bitting. i don't know if im giving too much info or not the right info. could you take a look at it and let me know if its something i could add or be more specific. i would have thought by now someone would have it figured out.
Click to expand...
Click to collapse
what exactly are you trying to get accomplished? and you are s-on right also did you follow the directions on the site?
yojoe600 said:
what exactly are you trying to get accomplished? and you are s-on right also did you follow the directions on the site?
Click to expand...
Click to collapse
yes im on S-on and yes i followed the instructions and now my phone is stuck. im trying to install the original vzw stock using ph98.img. its stuck in the hboot screen and i can't get it out. and my phone pc isn't recognizing my computer. my problem started when i used hasoon2000 all in one tool kit and locked my bootloader. now i can't get off this white hboot screen. the only opitions i have is fastboot, recovery, factory reset, clear storage ,simlock, image crc..
any suggestions
you may need to get a card reader so put the ph98.img back on the sd not in any files and install it in fastboot again twice
Today I woke up to my phone saying Please insert Sim card, it was inserted. I restarted, no dice, reinstalled cm 10.2, no dice, wiped factory settings, cache, dalvik cache, then installed Paranoid android, still not working. It won't let me get past the activation screen even if I let it time out and hit skip it literally will just go back to the welcome screen and try to activate again.
I searched around and found that RUU-ing back to stock, locking the bootloader and all that would fix it so I locked the bootloader and am trying to use Ruu but half way through Ruu-ing it takes me to a black screen with a silver HTC logo on it and freezes, then Windows 8 tells me that it is not reconized and Ruu says error 171 which is a USB error. I checked under Device manager and it said unknown device so I'm obviously missing the driver so I go to install htc sync to get the driver and no dice, even if I uninstalled HTC sync and kept the driver it still didn't work. My question is which driver am I suppose to be using?
Phone: Droid DNA
Rom: Was running CM10.2 at the time then installed Paranoid Android to see if it would help
OS: Windows 8
iximoronixi said:
Today I woke up to my phone saying Please insert Sim card, it was inserted. I restarted, no dice, reinstalled cm 10.2, no dice, wiped factory settings, cache, dalvik cache, then installed Paranoid android, still not working. It won't let me get past the activation screen even if I let it time out and hit skip it literally will just go back to the welcome screen and try to activate again.
I searched around and found that RUU-ing back to stock, locking the bootloader and all that would fix it so I locked the bootloader and am trying to use Ruu but half way through Ruu-ing it takes me to a black screen with a silver HTC logo on it and freezes, then Windows 8 tells me that it is not reconized and Ruu says error 171 which is a USB error. I checked under Device manager and it said unknown device so I'm obviously missing the driver so I go to install htc sync to get the driver and no dice, even if I uninstalled HTC sync and kept the driver it still didn't work. My question is which driver am I suppose to be using?
Phone: Droid DNA
Rom: Was running CM10.2 at the time then installed Paranoid Android to see if it would help
OS: Windows 8
Click to expand...
Click to collapse
Try change USB port to 2.00, usb v3.00 is causing known issues . Update ADB drivers. also under windows devices manager unknown devices try to updates driver unknown device. Try it on Windows 7 pc.
http://forum.xda-developers.com/showthread.php?t=2293919
finanandroid said:
Try change USB port to 2.00, usb v3.00 is causing known issues . Update ADB drivers. also under windows devices manager unknown devices try to updates driver unknown device. Try it on Windows 7 pc.
http://forum.xda-developers.com/showthread.php?t=2293919
Click to expand...
Click to collapse
Done all of those things except trying on a windows 7 computer, let me see if I can sneak onto my mother's work laptop hah. I also read that installing PDAnet would help me, each time during install it would BSOD me
Edit
Same thing on windows 7
Second edit
O man it is working even though adb devices showed nothing I booted to the welcome screen and started ruu there! Its always windows 8s problem isn't it?
Seriously thank you
iximoronixi said:
Done all of those things except trying on a windows 7 computer, let me see if I can sneak onto my mother's work laptop hah. I also read that installing PDAnet would help me, each time during install it would BSOD me
UPDATE
Same thing on windows 7
Click to expand...
Click to collapse
Did you FLASH THE STOCK HBOOT 1.15 so it matched RUU, when you ran RUU?
---------- Post added at 02:23 AM ---------- Previous post was at 02:05 AM ----------
iximoronixi said:
Done all of those things except trying on a windows 7 computer, let me see if I can sneak onto my mother's work laptop hah. I also read that installing PDAnet would help me, each time during install it would BSOD me
Edit
Same thing on windows 7
Second edit
O man it is working even though adb devices showed nothing I booted to the welcome screen and started ruu there! Its always windows 8s problem isn't it?
Seriously thank you
Click to expand...
Click to collapse
yes I read something about Windows 8 troubles working with adb. Hopes you back in business, but asap RUU finish and you boot in to
out the box Stock, do a Factory or phone reset from Stock Recovery*
finanandroid said:
Did you FLASH THE STOCK HBOOT 1.15 so it matched RUU, when you ran RUU?
---------- Post added at 02:23 AM ---------- Previous post was at 02:05 AM ----------
yes I read something about Windows 8 troubles working with adb. Hopes you back in business, but asap RUU finish and you boot in to
out the box Stock, do a Factory or phone reset from Stock Recovery*
Click to expand...
Click to collapse
I am back on stock but still roaming sadly. Any ideas?
iximoronixi said:
I am back on stock but still roaming sadly. Any ideas?
Click to expand...
Click to collapse
Did you Reset the phone after RUU? are u on VZW, you should receive the OTA 2.04 then 2.06
sometimes that happen, (the roaming s) if you still roaming get it to VZW to exchange SIM Card and be resetting.
finanandroid said:
Did you Reset the phone after RUU? are u on VZW, you should receive the OTA 2.04 then 2.06
sometimes that happen, (the roaming s) if you still roaming get it to VZW to exchange SIM Card and be resetting.
Click to expand...
Click to collapse
Evidently resetting it via recovery was the wrong way to do it. I tried it through fastboot and it worked!!! Thank you for all your help!
I'm on my second dna, about a month in total two phones. First one rooted, s-off from stock rom flashed the latest build of cm10.1. Upon boot up the first screen where it says activating it just sat there after about 5 minutes said it couldn't activate. Odd. On my past nexus devices Samsung gs2 and gs3 it would fly past that screen. I restored my back up same thing it said I had no service. Data worked but couldn't make a call or send a text.. Didn't know what to do and luckily Verizon didn't seem to care and swapped it out. So now I'm re-rooted on this phone but to afraid to flash anything cause of what happened. Seems like the same thing that happened to you happened to me.. I don't know how to do the ruu thing and I guess u can reset the phone from boot loader?? What fixed your issue.? I really want to rock stock android but to scared to flash anything. Let's say something happens again do I just get in boot loader and reset that's it nothing else needed?
Sent from my HTC6435LVW using Tapatalk 2
finanandroid said:
Did you FLASH THE STOCK HBOOT 1.15 so it matched RUU, when you ran RUU?
---------- Post added at 02:23 AM ---------- Previous post was at 02:05 AM ----------
yes I read something about Windows 8 troubles working with adb. Hopes you back in business, but asap RUU finish and you boot in to
out the box Stock, do a Factory or phone reset from Stock Recovery*
Click to expand...
Click to collapse
I can confirm not a windows 8 problem. I've done it several times on 8 pro 64 bit. Must have been something else.
Sent from my HTC6435LVW using xda app-developers app
iximoronixi said:
Evidently resetting it via recovery was the wrong way to do it. I tried it through fastboot and it worked!!! Thank you for all your help!
Click to expand...
Click to collapse
You welcome!
after RUU >Stock Factory Reset, can be done from the phone... Setting>Back up & Reset> Reset Phone ( is exactly the same process when you go to Bootloader, fastboot and apply /Factory Reset. my bad if you misunderstand my concept , I called Stock Recovery to the Factory image and setting of the phone as it came out of the box to differentiate from Custom Stock Recovery like CWR/TWRP. Glad that u figured it out and have your phone back. Next time i will more specific.
cstrife999 said:
I can confirm not a windows 8 problem. I've done it several times on 8 pro 64 bit. Must have been something else.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
Maybe I shouldve mentioned I am on Windows 8.1 (Which is leaps and bounds above 8) but that could have had something to do with it
iximoronixi said:
Maybe I shouldve mentioned I am on Windows 8.1 (Which is leaps and bounds above 8) but that could have had something to do with it
Click to expand...
Click to collapse
yeap it need extra work around windows drivers.
iximoronixi said:
Maybe I shouldve mentioned I am on Windows 8.1 (Which is leaps and bounds above 8) but that could have had something to do with it
Click to expand...
Click to collapse
I actually had to downgrade from 8.1 because it was impossible for me to get adb and fastboot working, because of the drivers. I spent the better part of a whole day trying to, its simply broken because of driver signing.
jake.corey.jacobs said:
I actually had to downgrade from 8.1 because it was impossible for me to get adb and fastboot working, because of the drivers. I spent the better part of a whole day trying to, its simply broken because of driver signing.
Click to expand...
Click to collapse
Yeah it was just easier for me to use my mother's work laptop which has windows 7 on it but now moonshine won't work so there goes my day
Use Ubuntu live CD bro
Sent from my HTC6435LVW using Tapatalk 4
jake.corey.jacobs said:
Use Ubuntu live CD bro
Sent from my HTC6435LVW using Tapatalk 4
Click to expand...
Click to collapse
I was trying to avoid that because I have had issues with ubuntu in the past and I also have gotten s-off before without it but I honestly don't remember what way I used but I guess I'll give ubuntu a shot
There's nothing to mess up. Its a live CD and changes nothing on your HD. And nothing to install outside of Moonshine itself.
Sent from my HTC6435LVW using Tapatalk 4
---------- Post added at 08:08 PM ---------- Previous post was at 08:07 PM ----------
So wait. Are you still s-off?
Sent from my HTC6435LVW using Tapatalk 4
jake.corey.jacobs said:
There's nothing to mess up. Its a live CD and changes nothing on your HD. And nothing to install outside of Moonshine itself.
Sent from my HTC6435LVW using Tapatalk 4
---------- Post added at 08:08 PM ---------- Previous post was at 08:07 PM ----------
So wait. Are you still s-off?
Sent from my HTC6435LVW using Tapatalk 4
Click to expand...
Click to collapse
ah ok sweet thanks and no I am now s-on, tampered, and getting kind of frustrated hah
Edit:
I am still getting the don't drink and shine error on Ubuntu live as I was getting on windows
iximoronixi said:
ah ok sweet thanks and no I am now s-on, tampered, and getting kind of frustrated hah
Edit:
I am still getting the don't drink and shine error on Ubuntu live as I was getting on windows
Click to expand...
Click to collapse
So you went back to s-on?
if so you can try this http://forum.xda-developers.com/showpost.php?p=44796097&postcount=5
jake.corey.jacobs said:
So you went back to s-on?
if so you can try this http://forum.xda-developers.com/showpost.php?p=44796097&postcount=5
Click to expand...
Click to collapse
You are amazing! This worked! thank you so much!