I updated my Fascinate yesterday OTA to DL09 from Verizon and now when I connect to my laptop I get the big bad blue screen stating that it has stopped to protect my computer from damage. I have rebooted 3 time without any positive result. Anyone else having this issue or know of any fix. Thanks
Try putting the phone into debug then try it.
Z an B son!
Yes, I have the same problem...
and we are not the only one's .... http://forum.xda-developers.com/showthread.php?t=911543
I am not able to connect to my MAC
Tried factory reset .. still didnt work...
The Blue Screen of Death (BSOD) is not the same as the problems that people are having with mounting USB.
I have been all over forums today and this is the first I have heard of a BSOD.
In the BSOD will be an error number. Something like a Fatal Error has occurred at xxxxxxxx in module yyyyyyyy
Google the exact error message and see what you come up with.
Fixed he issue
I got the problem fixed. What I found was that the phone was showing up as a cd rom drive and by doing this my PC automatically started opening up CD rom software on my pc that was totally not compatible with the phone LOL. Isnt it just like Verizon for pushing more of there crap on us to screw up the works.
Thanks for everyone's help.
Related
Welp, Just wanted to start out with a clean slate. Went to RUU my phone and durring the RUU about 70 seconds into "Waiting for Boot Loader" windows pops up and says "The device attached has malfunctioned - blah blah blah".
Ends up coming up with Error 171 USB Connection Failed in the RUU.
Any ideas? HTC bootloader is a Device in the list.
ADB works when the phone is booted.
HTC Sync drivers are there...
Windows 7 x64.
Booted into Fastboot USB and ADB can't seem to find the device which is weird.
I have never had an issue with my phone doing stuff like this till now. I think I bought the golden hero that has no issues at all LOL.
Any ideas fellas...and the few ladies that pass through?
Kcarpenter said:
Welp, Just wanted to start out with a clean slate. Went to RUU my phone and durring the RUU about 70 seconds into "Waiting for Boot Loader" windows pops up and says "The device attached has malfunctioned - blah blah blah".
Ends up coming up with Error 171 USB Connection Failed in the RUU.
Any ideas? HTC bootloader is a Device in the list.
ADB works when the phone is booted.
HTC Sync drivers are there...
Windows 7 x64.
Booted into Fastboot USB and ADB can't seem to find the device which is weird.
I have never had an issue with my phone doing stuff like this till now. I think I bought the golden hero that has no issues at all LOL.
Any ideas fellas...and the few ladies that pass through?
Click to expand...
Click to collapse
I have had problems with my usb port not having a good connection. You can try holding the usb cable in and up towards the screen and see if that helps. That is what I had to do before replacing my Hero.
animal7296 said:
I have had problems with my usb port not having a good connection. You can try holding the usb cable in and up towards the screen and see if that helps. That is what I had to do before replacing my Hero.
Click to expand...
Click to collapse
No Dice.
Phone still works fine, but I figure I'll format it as often as I do my laptop LOL.
Just thought I would also mention that when RUU reboots the phone, it sticks at the HTC screen. And I have to pull the battery to reboot.
-------------------------------------------
I feel like just a noob, I never have problems
-------------------------------------------
Ok so if this happens to anyone else here is what I did to get it fixed.
Run the RUU, and let it fail with Error 171.
The RUU will say the Current Image version (In my case) is FRESH.
Being replaced with 2.56.....
After it fails and it is stuck at the HTC screen, Run the RUU again.
This time it says Image version 1.56....
being replaced with 2.56....
It successfully went through the second time after it was stuck at HTC.
Kcarpenter said:
Ok so if this happens to anyone else here is what I did to get it fixed.
Run the RUU, and let it fail with Error 171.
The RUU will say the Current Image version (In my case) is FRESH.
Being replaced with 2.56.....
After it fails and it is stuck at the HTC screen, Run the RUU again.
This time it says Image version 1.56....
being replaced with 2.56....
It successfully went through the second time after it was stuck at HTC.
Click to expand...
Click to collapse
Glad to see ya got it working.
Kcarpenter said:
Ok so if this happens to anyone else here is what I did to get it fixed.
Run the RUU, and let it fail with Error 171.
The RUU will say the Current Image version (In my case) is FRESH.
Being replaced with 2.56.....
After it fails and it is stuck at the HTC screen, Run the RUU again.
This time it says Image version 1.56....
being replaced with 2.56....
It successfully went through the second time after it was stuck at HTC.
Click to expand...
Click to collapse
Thanks for this! I had tried 4 or 5 times and was starting to get worried!
New to the forums, great stuff here guys!
This is great! I've search for 2 weeks trying to figure this out. Just to clarify, because some things above are implied, not explicit:
1. Run the RUU
2. Get error 171, hit the exit button.
3. Don't do anything to the phone (like remove the battery to unfreeze it or unplug it)
4. Run the RUU again
5. You win!
I'm glad this was covered, I've been getting this BS connection error 171 and have tried at least 10 times without success, I'll have to try it like this.
I think that this problem is common, but yet, I did not managed to find out a solution to solve it. When I press root, (I did ticked the debuging) it just says a few lines, and then it freezes with the ending text saying: Waiting for device...
I choosed "Charge" on my phone.
I used Super One Click 1.7
When it shows Waiting for device... try turn usb debugging off and on
any luck?
Im out of info bout SOC.. now it has version 1.7..
I always did this with v.1.3.. never got a problem
Hi all!
I have a rather major problem.
Today Kies told me that I have a new upgrade for the firmware of my Samsung Galay S i9000. It ran stuck rom with only a few apps installed. I said i want to upgrade so it started to check everything, done a backup of my contacts, started to download the firmware on my PC. So far everything is good.
After that the phone rebooted into an android working logo and said "Downloading..." it stayed like this for a while and after that Kies gave an error. Now the phone is stuck on this screen. Disconecting the device from the usb cable and pluging it back in does't do anything. Kies tries to connect to it but after a couple of minues gives an error that the device is not responding and I should try to rebot the device.
Any idea what to do? This is the work phone so I have to fix this.
Any help is appreciated.
EDIT: Fixed the problem with odin. I know I should get a warning for not searching first...but I panicked.
Easy stuff to fix, start by posting in the right section.
Sent from my GT-I9000 using XDA Premium App
I too have a focus that is stuck in a loop at the Samsung logo. I bought it like that thinking I might be able to resurrect it as another toy. I have had lots of experience with Samsung, HTC and Sony droid phones, this would be the first WP.
It is a I917R on Rogers, there is no hardware revision under battery. I am assuming it is V1.3 as I have only seen software for the that version posted. I do not know how the phone got to its present state. They just said it happened during normal use?
I can get to both download mode and factory reset. I have flashed the stock rogers files without errors, but I never get the screen connecting to pc. The phone just restarts after successfully flashing, only to reboot continuously. I have been able to install MAGLDR and flashed every v1.3 ROM i could download. All without errors, just the same outcome they all just keep displaying Samung logo and then reboot. Only thing I noticed is that when I flash MAGLDR and custom ROMs it takes the phone longer to reboot.
I never get the connect to pc if I hold camera and power, nor do I ever get that screen when I flash a ROM.
Not sure if situation is similar... I am puzzled?
Your situation is very similar with other folks' here, unfortunately. It's not clear what causes it and there's no solution as of yet. For some, re-flashing worked. For others, a new battery. Most are stuck on loop...
When you connect the phone to USB when in download mode, what do you get?
When I boot to download mode I can flash Rom with WP7. I get to the yellow triangle download mode and flashes ok, no errors. Just noticed that it never goes to connect to pc mode.
Same with when I format, no connect to pc mode.
Nothing I try seems to help.
blackangel21 said:
When I boot to download mode I can flash Rom with WP7. I get to the yellow triangle download mode and flashes ok, no errors. Just noticed that it never goes to connect to pc mode.
Same with when I format, no connect to pc mode.
Nothing I try seems to help.
Click to expand...
Click to collapse
I see. What messages do you get when you connect the phone to the PC via USB, in either mode?
No messages, just shows up as Samsung USB composite device, Samsung mobile modem and Samsung mobile modem diagnostic serial port in download mode.
In magldr it shows up add Microsoft USB sync.
The only thing I forgot to mention was that when I flash with WP7 it finished without error in 90 seconds, but on the phone it says it will take 10 minutes.
Not sure what more I can add...
You could try different downloaders. Please see this thread for 7.41 downloader, maybe that helps?
Tried both, same outcome... No errors, just keeps rebooting... No Connect to PC message.
Im having the same problem. And i can see many other people who are having the same issue also. So i think its time to dump those phones, not worth a penny. The one i have in here was actually working, i followed all the directions in order to flash it. And still the phone got stuck into that bootloop. Its ridiculous from what i can see. I think ive read once you put that SDmini in it the phone will use it for the OS. But the one i had was working actually without it, i could turn it off as many times as i wanted and nothing happened. But if i tried a factory reset data would stay and diagnosis mode wasnt working. So i decided to flash it. Big, huge mistake! Hope you have better luck than i did. Because im dumping this one....
Same problem here, ive checked a couple of threads and no solution so far
Hey guys. I tried rooting my LG G4c but after rebootingen it seems that my phone is stuck in a loop, and i can't fix it.
What happens when i turn the phone on:
1. LG logo turn up
2. The following message appears:
[670] --------------------------------------
[670]
[670] Boot verification fail!!
[670] - cause : MISMATCH_SIG_LEN
[670]
[670] --------------------------------------
3. Phone reboots
Using the power button + volume down does NOT work anymore to start recovery mode (although starting the IMEI display still works).
I tried using LG UP to install the original firmware via USB but the device does not show up in the list (probably because the phone keeps rebooting itself). Some website also said to connect the phone with the pc, turn LG UP on, then put out the battery and put it back in to make it work, but that also didn't work.
Anyone know what i can try next? What method can i use to reinstall the firmware? And if it's not possible, does it cost much to repair and who should i ask?
Edit: It seems i can start "Factory data reset" but when this proces starts the phone restarts and continues the loop with the error message.
I also tried connecting the device with LG UP while the phone is stalled on the IMEI screen and the Factory data reset screen. This way the phone does note restart itself and it might appear in the device list of LG UP. But too bad it still didn't work.
I don't know if i'm reaching anyone who can help me, but even a answer from anyone saying that the problem is hard to deal with would already be very relieving I really can't find anything related to this problem on the internet and i'm noobish myself. I'm probably gonna visit a some phone shop down town in the next days because i really don't know what to do.
vanderplate said:
I don't know if i'm reaching anyone who can help me, but even a answer from anyone saying that the problem is hard to deal with would already be very relieving I really can't find anything related to this problem on the internet and i'm noobish myself. I'm probably gonna visit a some phone shop down town in the next days because i really don't know what to do.
Click to expand...
Click to collapse
I had this problem too. I send it to LG and said the phone was unplugged during update process. They flashed it and I gave it to my mom. I have an S4 yet. Much better performance and rom support.
download mode
vanderplate said:
I don't know if i'm reaching anyone who can help me, but even a answer from anyone saying that the problem is hard to deal with would already be very relieving I really can't find anything related to this problem on the internet and i'm noobish myself. I'm probably gonna visit a some phone shop down town in the next days because i really don't know what to do.
Click to expand...
Click to collapse
Can you get it into download mode?