Took my Nexus One off my cradle today to see it was locked up. Thought no biggie, I'll pull battery and restart it.
Now when it boots it comes up with four bars. Red, Green, Blue, White and the 3 skateboarding Droid Bots. I have no clue what to do now.
I was running Cyanogenmod (Forget the version, but it was 2-3 months old. I have not done anything to my phone except add the ebay app to it yesterday.
I can not get my computer to recognize it as a Nexus One anymore so I can not use Fastboot. I tried recovery from HBOOT, but keep coming up the same way.
Please Help
Ray
Picture of my Nexus One from Wifes iPhone...
I can get to FASTBOOT and when connected to USB it says FASTBOOT USB, but my computer fails to recognize the device and it goes back to FASTBOOT.
I can not turn on USB Debuging because it will not boot normal. I do not know what to do.
Weird screen, never seen that before.
Is this screen the only thing you see when you turn on the phone or do you still see the splash screen with the unlocked bootloader image prior? Have you tried booting into recovery? (holding the volume down button while turning the phone on)
Yes its the only thing I see.
I do not see anything Prior.
I have tried to boot to recovery many many times. I have 3 different results.
1. Nexus X with nothing else
2. Nexus X with Unlocked icon below
3. The screen you see
Either way, it does not move forward it just hangs. Is there a way to turn on USB debugging from FASTBOOT or HBOOT?
Ray
Russ T. Nail said:
Weird screen, never seen that before.
Is this screen the only thing you see when you turn on the phone or do you still see the splash screen with the unlocked bootloader image prior? Have you tried booting into recovery? (holding the volume down button while turning the phone on)
Click to expand...
Click to collapse
looks like the bootloader screen, thats what the rainbow screen was on the g1.
havent seen it on the nexus though so it could be something else.
Did you try a factory reset using hardware keys?
I believe you do this by holding vol-down, power and trackball for 5 secs.
That does not seem to do anything but take me to FASTBOOT
There has to be a way to turn on USB Debugging from FASTBOOT?
If you can get fastboot usb to work you could try the following (using latest amon_ra recovery.img):
Code:
fastboot boot c:\path\to\recovery.img
To boot into recovery, then use adb or try nand-ing etc.
if you get that far (recovery)
Code:
adb shell reboot normal
should take you into os.
However, the colored bars look like some pretty serious hardware failure I'd guess...
I can not get FASTBOOT USB to work. Any suggestion on how to get this working again?
Windows just says Unknown Device and uses a standard windows USB driver. I try to update the driver pointing it to android_winusb.inf but windows says no go.
Ray
check this out to help you get fastboot to work http://forum.xda-developers.com/showthread.php?t=613217
i know its titled ADB but it might help you out.
TheQue said:
I can not get FASTBOOT USB to work. Any suggestion on how to get this working again?
Windows just says Unknown Device and uses a standard windows USB driver. I try to update the driver pointing it to android_winusb.inf but windows says no go.
Ray
Click to expand...
Click to collapse
Try to enter to recovery but.... first change your microSD maybe that is the problem ... a faulty card .. Im just guessing
have you tried to contact htc or even google?theyve helped me over the phone even knowing i have an unlocked bootloader.
pvillasuso said:
Try to enter to recovery but.... first change your microSD maybe that is the problem ... a faulty card .. Im just guessing
Click to expand...
Click to collapse
not the sd card if it was a bad card it would just bootloop
if you have SDK you can see what the phone is doing with ddms
I would download SDK and install driver in SDK then you can run ddms and watch what the phone does in the realtime device log as it tries to boot
That pic reminds me of the MDA Win Mobile 5 boot screen, real similar...
Don't know how to help, keep us updated if you figure this one out.
gtrplr71 said:
I would download SDK and install driver in SDK then you can run ddms and watch what the phone does in the realtime device log as it tries to boot
Click to expand...
Click to collapse
I 2nd that. Try using ddms or logcat.
Good luck man!
What happens when you try to flash a rom?
Related
Phone is ATT captivate SGH-I897 1008
Had my phone for 4 months or so, most of the time with cognition 2.x on it. Tried to update to 3.02 yesterday, and it had an error in the middle, left me at a recovery screen of sorts, and I chose to reboot from the possible selections. It got stuck on the ATT worldcom splash screen.
I tried several things. First, I tried to boot into recovery mode (vol up+power, then release) stays on splash screen. However, in this mode, if I connect my phone via USB, an adb devices command shows as connected. From there I tried both an adb reboot recovery, and adb reboot download command. The adb reboot recovery reboots into the worldcom splash screen just like the key combo does. I can't recall what the download option did, though I think it worked.
Secondly, I realized I could reliably get the phone into download mode, so I decided I would try the download mode, and restore to stock. I found an ODIN on the seminal ODIN thread, downloaded it, and started it up. Put the phone into download mode (hold vol + and vol -, plug in the usb) and that worked fine, however, ODIN doesn't see my phone. I left the phone in this mode for a couple hours just to make sure, and tried disconnecting, and reconnecting, and initialized the procedure from the beginning several times -- no go.
So, I am stuck, and coming to the experts. Hopefully, someone has some good suggestions. I was unable to find someone in a similar predicament, so maybe I am SOL.
Thanks in advance for any help.
UPDATE:
I rebooted my laptop (windows XP) and when I plugged in my phone, it saw "new" hardware and the name of the hardware it sees is "gadget serial." This might explain, if it is not initializing the right drivers why ODIN can't see the phone. The only problem is I don't have any clue how to redirect it to see the right hardware now.
Success Update
After reading the seminal ODIN thread a bit more careful, I came across someone who had similar issues with the gadget serial device. Apparently the drivers I got (I think from the Samsung site) are not good enough to cover that aspect of use. I installed with the drivers from links on the ODIN post and my phone was recognized! As I type, I am installing back to stock.
Thanks everyone for their efforts, and I hope my experience could be useful.
Desk top or laptop, have you tried all the ports
I would test to see if adb recognizes your device first during normal operations. I'd that doesn't work, your usb port may not have enough power or you have a bad usb cable. I think adb can also restart right into download mode but check around first.
Sent from my SAMSUNG-SGH-I897 using XDA App
mcord11758 said:
Desk top or laptop, have you tried all the ports
Click to expand...
Click to collapse
I have tried on my laptop mostly. But I did a cursory try on a desktop as well (the desktop has the drivers installed)
trekie86 said:
I would test to see if adb recognizes your device first during normal operations. I'd that doesn't work, your usb port may not have enough power or you have a bad usb cable. I think adb can also restart right into download mode but check around first.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
I tried two differing cables, both of good quality. One was the cable that came with the phone, the other was a mini-usb cable with a micro adapter. Neither worked. I can't do normal operations right now (that I know of), seeing how the phone is in a bad state.
jbwray said:
I have tried on my laptop mostly. But I did a cursory try on a desktop as well (the desktop has the drivers installed)
Click to expand...
Click to collapse
Use rear usb ports on desktop. Make sure you are using original oem cord
Have you used odin before
jbwray said:
I can't do normal operations right now (that I know of), seeing how the phone is in a bad state.
Click to expand...
Click to collapse
Sorry, didn't read your first post close enough. I'm not sure what you can do, someone suggested the battery pull method in another thread, but that was just to get their phone in Download mode. It had nothing to do with ODIN after it was in download mode. Hopefully someone will have a suggestion for you. Good luck.
I'm having a similar issue except that odin sees the phone when booted into the rom, which I find odd.
Would you be so kind as to link the drivers?
So as you may already be aware phones like mine, (orange uk) have the fastboot locked down, and so we cant unlock the bootloader.
I for one believe it can be accessed but needs a little bit of time and research on getting it done.
This thread is aimed for brain-storming for ideas and collecting them for us to try out,
You can de-brand your phone by flashing the software from this thread
http://forum.xda-developers.com/showthread.php?t=1033193
thanks to scott4 for the first upload mirror on page 3
Any ideas on getting the bootloader up and going on locked devices please put them in here
UPDATES
We now have root access thanks to Chainfire's gingerbreak apk which is here
http://forum.xda-developers.com/showthread.php?t=1044765
If your getting "could not extract assets" from gingerbreak
try doing
xperiax10.awesome said:
cool, finally I rooted my xperia ARC
these are very simple steps(copied from different threads):
1. Install the attached apk: Gingerbreak-v1.00
after installing most people getting this error - "could not extract assets".
TO OVERCOME THIS, just copy the attached ADB.zip and extract it on your laptop (windows)
say at
E:\mobile_Xperia\ADB
goto above path in your cmd promt and types these lines (your phone should be connected to laptop in debugging mode)
E:\mobile_Xperia\ADB>adb shell rmdir /data/local/tmp
E:\mobile_Xperia\ADB>adb shell mkdir /data/local/tmp
NOW JUST INSTALL THE apk file again and click on ROOT
Click to expand...
Click to collapse
if that Fails try replacing it with rm -r /data/local/tmp
Update 2
Blagus has kindly opened up this thread here
http://forum.xda-developers.com/showthread.php?t=1063394
We need people with a SIM-FREE phone with a LOCKED bootloader to help us all out, so if thats YOU !!!
Help us poor sods with branded handsets please.
UPDATE 3
Blagus Has come out with his release (As the man who can)
Blagus said:
Omnius for SE v0.23 (30th August 2011)
Added unlocking of S1 MSM7x30 GSM/UMTS phones (testpoint connection to GND is required.)
Added bootloader unlocking for S1 MSM7x30 phones
Anyone who donated (+punk... sorry forgot username, the OP ), contact me for free unlock.
For rest, contact for price (cheaper than at official Omnius resellers).
Click to expand...
Click to collapse
You can contact him here http://forum.xda-developers.com/member.php?u=2645841
Instructions
TESTPOINT INSTRUCTIONS PROVIDED BY mooxie FROM XDA FORUM:
1 turn of the phone
2 take of the backcover
3 remove the battery and sim card
4 take of the plastic covering the test point it's a bit stuck there but the gentle if you can.
5 Find something flexible like a wire or so i used steel wire. Make bend it so you easily can put it on the test point and the ground since you need to hold it there and press the powerbutton in the next step.
6 put in the battery
7 put the wire on the test point and the ground keep it there and press the power button for a few seconds. You wont get any confirmation that it suceeded.
8 Plug in the usb cable in the phone. Windows will now search for a new driver.
If it doesn't install automaticly. Go into the device manager of windows and look up something called SEMC_HUBB think it was that name. Choose update driver and browse to your omnius\driver folder. You will get a warning that the driver isn't signed but press okay and it should install.
9 Now if everything is done right the flashing will start and you should soon have an unlocked phone
Also side note i had problems with
qhsusb_dload driver not installing correctly.
if this is your case right click update and point to the omnius folder and choose update. worked for me.
Have you tried connecting via ADB, and running the command "adb reboot fastboot"?
dh2311 said:
Have you tried connecting via ADB, and running the command "adb reboot fastboot"?
Click to expand...
Click to collapse
What does this command does beside going to the fastboot?
Rithina said:
What does this command does beside going to the fastboot?
Click to expand...
Click to collapse
Well if we can get into fastboot we can unlock the kernal, for the people stuck with not being able to do the normal way
dh2311 said:
Have you tried connecting via ADB, and running the command "adb reboot fastboot"?
Click to expand...
Click to collapse
Reboots back up as normal, also did adb devices and it was there,
Have you tried removing the simlock?
MarylandCookie said:
Have you tried removing the simlock?
Click to expand...
Click to collapse
No not sure how to do it for free, i think someone with a Japaneses version has removed it, i will PM him to ask him
Here's a thought: backup TA. Write random values to security area. If fastboot is disabled/enabled depending on TA simlock info, tampered sec. zone could give you fastboot. Then unlock bootloader and in order to get your phone back to life, restore TA.
Method should be 100% safe as long as you can write TA back.
Sent from my X8 using XDA App
Tampered units wont let the phone boot.
lollylost100 said:
Tampered units wont let the phone boot.
Click to expand...
Click to collapse
But what about flash mode and fastboot? I know they won't boot but that's why in the end TA is restored.
so now all you crazy kids with unlocked phones have root I dont suppose anyone has any more ideas about this problem do they?
I have a few more ieas;
1) I presume you have also tried
adb reboot bootloader
I haven't got my arc yet, Im just saying old ways of getting DHD into bootloader/fastboot
2)
Also, what i think was being mentioned above, Im not too sure what was being said, but on advent vega's and optimus 2x's if you wiped the boot partition, it rebooted into fastboot, because there was no OS installed.
3)
Another one to try is look for market apps that offer reboot into recovery type options and see if they work
have you tried booting your device using the S1 BOOTLOADER method and the S1 DOWNLOAD method? (power off, hold menu + plug battery, then plug cable in pc) you should see a blue LED light. (power off, hold back key + plug battery, then plug cable in pc) you should see a green LED light.
try these two methods and give us a feedback
kazuni said:
have you tried booting your device using the S1 BOOTLOADER method and the S1 DOWNLOAD method? (power off, hold menu + plug battery, then plug cable in pc) you should see a blue LED light. (power off, hold back key + plug battery, then plug cable in pc) you should see a green LED light.
try these two methods and give us a feedback
Click to expand...
Click to collapse
manage to get Green light to come up, and it installs drivers
SEMC Flash Devices installs as the drivers,
After the installation of the new drivers still no blue light
adb reboot bootloader just reboots as normal
Hi !
For me, first method makes my phone booting normaly (no led light).
With the second one, it's OK : green led light appears.
If i can help...
PS : my PC doesn't want to install drivers :-(
punkmonkey1984 said:
manage to get Green light to come up, and it installs drivers
SEMC Flash Devices installs as the drivers,
After the installation of the new drivers still no blue light
Click to expand...
Click to collapse
so that means SEMC Flash is available. Try using Flashtool and flash a UK/Global firmware, and see if it works =)
Skyseb said:
Hi !
For me, first method makes my phone booting normaly (no led light).
With the second one, it's OK : green led light appears.
If i can help...
PS : my PC doesn't want to install drivers :-(
Click to expand...
Click to collapse
Download SEUS. PC Companion doesn't install the right drivers.
kazuni said:
so that means SEMC Flash is available. Try using Flashtool and flash a UK/Global firmware, and see if it works =)
Click to expand...
Click to collapse
Already flashed global firmware,
Still locked,
I guess the lock is actually in the bootloader level, which can't be overridden by writing a ftf package.
Sorry, but no other ideas at the moment =\
??? Have you seen this post ? => http://forum.xda-developers.com/showpost.php?p=13064854&postcount=420
Edit : ok, forget it...
Sorry.
So, pretty much the title. I'm pretty noobish when it comes to phones, and think i messed it up. I'm currently with Rogers, and what i did i unlocked it, and put the Google Play edition onto my phone, because i personally did not like the Blink Feed. So me being awful with phones, after the update came out for the Google Play 4.4 KitKat, I decided to update the firmware... Not realizing that it would mess my phone up... I have no rom to go back too, which would of probably saved this whole problem... Also another huge problem, my Phone does not want to be found by my computer... I would of just easily fixed it by flashing another rom, but i can't because it doesn't want to be recognized. Basically my phone right now boots up half way to the Google Logo, and then goes to a blue/green screen and stays there till i decide to turn it off.. I can get into bootloader, but that's as far much as i can do... Any help would be awesome, because i'm lost as far as it goes and decided to come here to post about it... Considering this is the best website for phones and whatnot... Thanks ahead of time guys!!
BUMP!
You have to fix your driver issues.. without it can't help. Try a different computer, usb port, usb cable, different htc driver package, anything to get your device detected when running
adb devices
or
fastboot devices (in bootloader/fastboot mode)
SaHiLzZ said:
You have to fix your driver issues.. without it can't help. Try a different computer, usb port, usb cable, different htc driver package, anything to get your device detected when running
adb devices
or
fastboot devices (in bootloader/fastboot mode)
Click to expand...
Click to collapse
The thing is, the only time it can recognize it is when it is in fastboot, it says it's connected but it on the phone but doesn't connect to the computer :/
Interesting... what about changing your HTC drivers. There are a few links floating around. Do you have Windows 7 or 8/8.1?
SaHiLzZ said:
Interesting... what about changing your HTC drivers. There are a few links floating around. Do you have Windows 7 or 8/8.1?
Click to expand...
Click to collapse
Sorry for super late reply, fell asleep. Also Windows 7, tried installing different drivers to no avail
Can't help if the phone refuses to respond to fastboot devices in bootloader mode.. or adb devices in custom recovery..
SaHiLzZ said:
Can't help if the phone refuses to respond to fastboot devices in bootloader mode.. or adb devices in custom recovery..
Click to expand...
Click to collapse
Says it's connected, [FastBoot USB] Also says it's connected via Device Manager, http://gyazo.com/f9dfe5d0ab3f184f3b085d776e765d2c But, does not appear in my computer. http://gyazo.com/b23dc0defe0d657a7a4aab8abcc2866e Wish i could get a picture of my phone as well, but you know
I have tried to flash a rom (Android Revolution HD 53.0) for my One. And after I finished flashing, it asked me if I would like to fix root. I pressed yes.
Then the phone go stuck between the boot screen and the recovery screen. It cannot enter the recovery mode (It got a flash of the clockworkmod, but it seems likes some error occurs). And now, I put my phone into Fastboot mode and plug it to my computer. The phone has turned "FASTBOOT USB" but when a use a fastboot command, it says "waiting for device" for a century...
And when my open up the "device manager" on my computer, it can recongnize "my HTC" but it's marked as an unrecongnized device.
I'm using Windows 8.1 on the Lenovo y510p, I think the Win 8.1 is the problem causing this...
I have tried to install the Intel USB 3.0 eXtensible Host Controller Driver as mentioned here, but my USB then goes out of function.
Also, the fastboot won't work even though I manually install the HTC Driver from the device manager.
I have got HTC Sync, ADB and fastboot all installed on the computer. Still got no luck.
Anyway to solve this?
EricLamYP said:
I have tried to flash a rom (Android Revolution HD 53.0) for my One. And after I finished flashing, it asked me if I would like to fix root. I pressed yes.
Then the phone go stuck between the boot screen and the recovery screen. It cannot enter the recovery mode (It got a flash of the clockworkmod, but it seems likes some error occurs). And now, I put my phone into Fastboot mode and plug it to my computer. The phone has turned "FASTBOOT USB" but when a use a fastboot command, it says "waiting for device" for a century...
And when my open up the "device manager" on my computer, it can recongnize "my HTC" but it's marked as an unrecongnized device.
I'm using Windows 8.1 on the Lenovo y510p, I think the Win 8.1 is the problem causing this...
I have tried to install the Intel USB 3.0 eXtensible Host Controller Driver as mentioned here, but my USB then goes out of function.
Also, the fastboot won't work even though I manually install the HTC Driver from the device manager.
I have got HTC Sync, ADB and fastboot all installed on the computer. Still got no luck.
Anyway to solve this?
Click to expand...
Click to collapse
What is your bootloader version? What recovery are you using and what version?
in the meantime I suggest you to use Windows 7 or boot a live ubuntu 12.04 32 bits version cd or bootable flash drive and use fastboot from there.
EricLamYP said:
I have tried to flash a rom (Android Revolution HD 53.0) for my One. And after I finished flashing, it asked me if I would like to fix root. I pressed yes.
Then the phone go stuck between the boot screen and the recovery screen. It cannot enter the recovery mode (It got a flash of the clockworkmod, but it seems likes some error occurs). And now, I put my phone into Fastboot mode and plug it to my computer. The phone has turned "FASTBOOT USB" but when a use a fastboot command, it says "waiting for device" for a century...
And when my open up the "device manager" on my computer, it can recongnize "my HTC" but it's marked as an unrecongnized device.
I'm using Windows 8.1 on the Lenovo y510p, I think the Win 8.1 is the problem causing this...
I have tried to install the Intel USB 3.0 eXtensible Host Controller Driver as mentioned here, but my USB then goes out of function.
Also, the fastboot won't work even though I manually install the HTC Driver from the device manager.
I have got HTC Sync, ADB and fastboot all installed on the computer. Still got no luck.
Anyway to solve this?
Click to expand...
Click to collapse
This fixed fastboot on my windows 8.1 pc
Download this > http://forum.xda-developers.com/attachment.php?attachmentid=2500592&d=1389122072
Easy instructions here > http://forum.xda-developers.com/showthread.php?p=49131915
Use the Old Dirty Solution it works perfectly
clsA said:
This fixed fastboot on my windows 8.1 pc
Download this > http://forum.xda-developers.com/attachment.php?attachmentid=2500592&d=1389122072
Easy instructions here > http://forum.xda-developers.com/showthread.php?p=49131915
Use the Old Dirty Solution it works perfectly
Click to expand...
Click to collapse
so im bout to try this as my phone will not communicate in bootloader. but i have a bigger problem before i get to that. my phone wont stay charged long enough or at all really. i prob dont even have to mess with bootloader if it would charge. so i can plug it in and it flashes red led and empty battery. i can get it into bootloader and then recovery twrp 2.7.0.0 i currently have no os installed but have several on my phone so dont need to mess with adb yet how can i get my phone to stay on long enough to flash a rom ? RUU out of question here because of 30%
i thought twrp was suppose to charge ? but when i get their it wont stay on
alray said:
What is your bootloader version? What recovery are you using and what version?
in the meantime I suggest you to use Windows 7 or boot a live ubuntu 12.04 32 bits version cd or bootable flash drive and use fastboot from there.
Click to expand...
Click to collapse
Get no luck on that... The y510p cannot even boot from a USB /___\
But anyway, I have borrowed my fds computer with Win 7 installed. And all works fine now. Thank you very much~~
ac3kill said:
so im bout to try this as my phone will not communicate in bootloader. but i have a bigger problem before i get to that. my phone wont stay charged long enough or at all really. i prob dont even have to mess with bootloader if it would charge. so i can plug it in and it flashes red led and empty battery. i can get it into bootloader and then recovery twrp 2.7.0.0 i currently have no os installed but have several on my phone so dont need to mess with adb yet how can i get my phone to stay on long enough to flash a rom ? RUU out of question here because of 30%
i thought twrp was suppose to charge ? but when i get their it wont stay on
Click to expand...
Click to collapse
Your Phone is broken send it to HTC or take it to a repair shop
Hello! My LG P880 was Cyannogen CM11 mod, but was a little slow. So I decided to downgrade it to CM 10 I lowered the phone settings, installed it, but when it restarted was giving infinite loop. Now the phone does not go into recovery mode, it is not recognized in the PC USB. When I put the usb cable in pc it tries to recognize but gives blue screen and the pc restarts. Already reinstalled the driver on the PC but not accomplish anything. Trying to install the original rom by LG flash tools but it does not recognize. I tried to get into recovery mode but nothing. Help please !!:crying::crying::crying:
matheusmfn said:
Hello! My LG P880 was Cyannogen CM11 mod, but was a little slow. So I decided to downgrade it to CM 10 I lowered the phone settings, installed it, but when it restarted was giving infinite loop. Now the phone does not go into recovery mode, it is not recognized in the PC USB. When I put the usb cable in pc it tries to recognize but gives blue screen and the pc restarts. Already reinstalled the driver on the PC but not accomplish anything. Trying to install the original rom by LG flash tools but it does not recognize. I tried to get into recovery mode but nothing. Help please !!:crying::crying::crying:
Click to expand...
Click to collapse
Weird how your phone makes you get a blue screen of death.
Can you say what it writes in blue screen? And also try your luck on another PC.My sister's laptop could not recognize my phone no matter what I did.
Blue screen is most likely due to some broken software/hardware on your PC rather than a problem with your phone itself.So do try it on another PC.
Can you also say, how it doesn't go into recovery mode? When you hold vol - plus power, does it make the phone reboot, vibrating but still stuck on LG screen or does it not even vibrate?
matheusmfn said:
Hello! My LG P880 was Cyannogen CM11 mod, but was a little slow. So I decided to downgrade it to CM 10 I lowered the phone settings, installed it, but when it restarted was giving infinite loop. Now the phone does not go into recovery mode, it is not recognized in the PC USB. When I put the usb cable in pc it tries to recognize but gives blue screen and the pc restarts. Already reinstalled the driver on the PC but not accomplish anything. Trying to install the original rom by LG flash tools but it does not recognize. I tried to get into recovery mode but nothing. Help please !!:crying::crying::crying:
Click to expand...
Click to collapse
don't worry, the problem is your PC not your phone
try this 2 fix your pc:
start CMD with administrator privilege -->
chkdsk /f /r -->press enter --> Y
restart the computer, if you lucky it will fix you pc and you will be able 2 fix your phone
(the fix/test take 1-2 hours, depending on how big your HD and if you have errors/bads ectors)
if you r not lucky, you probably have driver collision and it more tricky 2 explain how 2 fix.
anyway, if you in a hurry do it in another computer
ottomanhero said:
Weird how your phone makes you get a blue screen of death.
Can you say what it writes in blue screen? And also try your luck on another PC.My sister's laptop could not recognize my phone no matter what I did.
Blue screen is most likely due to some broken software/hardware on your PC rather than a problem with your phone itself.So do try it on another PC.
Can you also say, how it doesn't go into recovery mode? When you hold vol - plus power, does it make the phone reboot, vibrating but still stuck on LG screen or does it not even vibrate?
Click to expand...
Click to collapse
elad.g said:
don't worry, the problem is your PC not your phone
try this 2 fix your pc:
start CMD with administrator privilege -->
chkdsk /f /r -->press enter --> Y
restart the computer, if you lucky it will fix you pc and you will be able 2 fix your phone
(the fix/test take 1-2 hours, depending on how big your HD and if you have errors/bads ectors)
if you r not lucky, you probably have driver collision and it more tricky 2 explain how 2 fix.
anyway, if you in a hurry do it in another computer
Click to expand...
Click to collapse
Hello, this is the screen error: STOP: 0x0000000A (0x0000000000000000, 0x0000000000000002, 0x0000000000000000,0xFFFFF80003482A56)
- I already tried on another PC, but it is giving blue screen too.
- When I try to go into recovery mode squeeze the volume down and the Power Button, it goes into normal boot.
- I checked the disk, but doesn't work.
matheusmfn said:
Hello, this is the screen error: STOP: 0x0000000A (0x0000000000000000, 0x0000000000000002, 0x0000000000000000,0xFFFFF80003482A56)
- I already tried on another PC, but it is giving blue screen too.
- When I try to go into recovery mode squeeze the volume down and the Power Button, it goes into normal boot.
- I checked the disk, but doesn't work.
Click to expand...
Click to collapse
its very strange that u got blue screens in both computers.....
the error code that u gave usually points that something wrong with mscorsvw.exe and/or NET framework.
i would recommend to update to the latest NET framework or even uninstall it and install it again.
Another good idea is 2 install the Android SDK (it installs a universal usb driver), this might help - ill try this before reinstalling NET frame.
i hope it helps...