Database Info

Stuck on LG logo

Hi I just rebooted my phone and its stuck on the LG logo anyone got any ideas how to sort it.

Try going into recovery and doing a full wipe
Sent from my SCH-I510 using XDA App

Done it but its still stuck on the lg logo.

Jabbypants said:
Done it but its still stuck on the lg logo.
Click to expand...
Click to collapse
Did you do anything for it to get stuck on the logo..root it..etc

Same problem here...Can someone please ADB PULL /system/bin/sh from a rooted phone and upload here please.I cannot ADB shell my phone after changing some system files on it.It's giving "exec /system/bin/sh Permission Denied (13) error.

Won't turn on now very disappointed wiht this phone now, all the messing I did with the Galaxy S2 and never a hitch and this just goes like this how pathetic.
I rooted the phone 5 days ago and all has been fine never been a problem, I can't even remember what app I had installed now it was something off the market, I rebooted the phone as it went slow and this is the outcome.
This has put me off this phone if I manage to get it replaced it will be sold on.

yep i had same problem twice, was always when I'd filled up internal memory to almost full and tried to uninstall something it would keep saying uninstalling and just hang there so I had to reboot and it would hang on LG. But did three button combo reboot and wiped the phone through that and it rebooted..

I can't seem to get the 3 button wipe to work, I can get in a screen via power and volume down which has factory data reset/wipe etc.
Also the battery is really low now on the last bar, when I plug it in usb for example it starts the phone and stops on the battery screen with it flashing on and off in the red, even if I plug the mains in it doesn't seem to charge.
I have countless times installed the usb drivers again and keep getting LGE Virtual Modem ready to use, but OMAP4430 no driver found.

that was when I had original recovery and not clockwork mod, there was a format partition and recover package option or something along those lines..so maybe doesn't work now with clockwork mod. All I know is I'm not going to fill internal memory up too full and try and uninstall anything as that's when it broke twice for me. Did you backup your phone with clockwork mod?

fraser68 said:
that was when I had original recovery and not clockwork mod, there was a format partition and recover package option or something along those lines..so maybe doesn't work now with clockwork mod. All I know is I'm not going to fill internal memory up too full and try and uninstall anything as that's when it broke twice for me. Did you backup your phone with clockwork mod?
Click to expand...
Click to collapse
Unfortunately not didn't use clockwork mod, I don't even think its charging the battery as it just flashes on the last red bar, I even left it in the charger all night.
I fail to believe this sort of thing can just happen like that, its not even like Samsung where you can pretty much recover anything when this happens seems very limited this phone.
Can't use the updater as it says Disconnected Please connect your phone
Edit> It is charging it must have been very very low as its taken ages just to get one green bar.

this may not work on the o3d but it works on the old droids/milestone.
if you remove the battery and plug it into the wall then insert the battery for a second and remove it again immediately the phone should boot on just mains power.

Just not having anything done the factory reset thing but its the same all the time does the first lg boot then you see the animated part then it just hangs on the lg screen, you get the small vibration it does but just doesn't boot after that.

punctuationmakesthingsaloteasiertounderstandman.

Punctuation is the last thing on my mind , I have a £450 phone that is knackered and hope they will take it back and replace it.
I have spent a day looking around the internet and have come up with nothing and keeping my eye on this forum, forgive me for not caring about what I am writing.

Actually something similiar happened to me.. my phones battery was totally drained and I didn't know. So just try to let it charge fully if you haven't already.
Sent from my LG-P920 using XDA App

largo79 said:
Actually something similiar happened to me.. my phones battery was totally drained and I didn't know. So just try to let it charge fully if you haven't already.
Sent from my LG-P920 using XDA App
Click to expand...
Click to collapse
I am charging it now but its taking ages, its about half full now but has taken a good 2-3 hours to get it there.

surely now the battery has some charge you can just reflash it thusly...
http://forum.xda-developers.com/showthread.php?t=1156549

@jabbypants
I'm in Burton on Trent, if you want to pop over and try my battery in your phone I'd be happy to let you try that.
Think if you've not messed with it you may as well try and get a new phone/refund.
Pete

hefonthefjords said:
surely now the battery has some charge you can just reflash it thusly...
http://forum.xda-developers.com/showthread.php?t=1156549
Click to expand...
Click to collapse
I did try that but it doesn't get recognised and just says Phone disconnected.
mad_sunday said:
@jabbypants
I'm in Burton on Trent, if you want to pop over and try my battery in your phone I'd be happy to let you try that.
Think if you've not messed with it you may as well try and get a new phone/refund.
Pete
Click to expand...
Click to collapse
Thanks for the offer but I have charged the battery but its the same thing, it hangs on the LG logo and nothing happens.

I phoned up LG and they say it sounds like a software failure so I have sent it back to the place I go it, just have to wait for a replacement.

[FIXED] Stuck at S/W Updater Screen

I was slow around flashing to the latest baseband but finally took the dive today and the program locked up at 5% for like 2 hours before I yanked it. Now it just gets to the "S/W Updater" screen regardless of what I do (NVFlash recoveries, roms, kernels, format, hard reset, etc). When I try to update it again, it just immediately says it's already the latest version. Why won't it just flash over it like most flashing programs.
Tmobile is pinging me $20 for a replacement but I have a really good G2x. Is there anything I can do to revive mine or is it toast? ADB commands or something? I have clockworkmod on there now, but I'm not really getting anywhere.
[Update]
Use this NVFlash method to completely format your phone, re-setup your partition tables, and flash the stock GB rom:
http://forum.xda-developers.com/showthread.php?p=17258229

Dead
It's dead. Same thing happened to me and to many many others. Turn it back to TMo and take the hit--it's not worth the time playing around with it any more.
Call TMo and ask to be forgiven the $20. If you've been a long and loyal customer they might even do it.
Your new phone should come with 2.3.3 installed. Mine did and I've had no trouble with it--it's finally settled down into a very usable and fast phone. Stock ROM. But I won't buy another LG phone again for a very long time--not until they hire a few software engineers who know what they're doing.

No my friend. I got revived!
http://forum.xda-developers.com/showthread.php?p=17258229
It totally erased everything, formatted everything, reset all the partitions, and flashed the GB Stock rom.
Booted up, NVFlashed CWM, Restored my Nandroid backup, viola!
Thought it would be a good thing to make more available. It was in the Android development thread but the title is tricky as its listed as a rom (which I guess it kinda is).

Sent from my LG-P999 using xda premium

i dont understand why people get stuck on this. ok
when i did it. the LG Tool stop responding on half the period % and my phone had the S/W updater screen so what i did i click on closed unpluged my device then open the LG Tool again plug my device and the LG TOOL said that there was a problem if i wish to continue with my update i click yes and it kept doing till it was done and my phone was fine with 2.3.3

The mistake you made was just stopping the update. Mine did the same thing. Instead of listening to the stupid message about removing the battery, etc. I just removed the usb cable, waited for the beep, put the cable back in, waited for the beep and then pressed "restart" on the update. It completed perfectly after that.

Well I've gone through all of those scenerios and it would attempt to reflash it, but the last time it got stuck on 5% for about 2 hours... no error message or anything. After 2 hours at 5% I pulled the plug. When it is in the middle of "flashing" and gets locked up, there is no Cancel button or Restart button like when it errors out.
I had no errors, just a locked up program. Regardless the posted link really fixed me up and got it working again.
I changed the title and updated the OP with the solution.

[Q] Flashed King Runny Rom, now bricked?

I have an Evo 4G revolutionary rooted. Had sinister rom. Flashed the new King Runny and it worked fine starting out. I tried to get into the navigation and it said I needed to download the updates. Then it said I did not have enough memory space and I needed to delete to make space. I then deleted all the pictures off the phone, and that didn't help. So next I went to factory data reset and I believe I pressed on the SD card to be erased too, which may have been an oops on my part. So when it rebooted I got stuck at the boot screen where it is the blue android symbol and it flashes repetitively. I tried multiple things, I have read multiple threads. I tried to flash back the stock ruu. I have been working at it for a couple of days now and I am at a loss. I am on the verge of taking it back to Sprint and eating my $100. Funny thing is, I cannot get into recovery, I can only get into bootloader. Last time I was in recovery, it was saying I could not mount the SD card and I could not mount through usb either. When I try to go to recovery now I get the white evo screen, it goes black, vibrates 5 times and I get a blinking green led. So far the majority of the threads I have read say I have to eat the $100. Others say the battery overheating caused a hardware problem. Just want to see what anyone else thinks. Thanks to all the developers and all the people that can make this stuff happen. I appreciate all the support even if it is to tell me I have to eat the $100.

[Q] Symptoms of a bricked phone? (related to all skyrocket users)

background info:
I am (or was) running MHX superlite 3.0 rom with romracers stockish 0.3 kernel.
UCLA3 modem and radio.
So today my phone decides to restart itself and never will load past the "first two"
samsung screens.
Once these "two" samsung logos pass by, the screen turns blank (not on)
and starts to vibrate with 1 second intervals.
The only way for it to stop is if I pull the battery.
Heres the weird part.
I tried to ODIN back to stock...once I put my phone into DOWNLOAD MODE.
The little android guy that says DOWNLOADING "dont turn off" will show for a millisecond and then the screen will shut off and start the vibrations. ODIN will not recognize the device either
So what I have is a phone that wont load past the samsung logos if the power button is pressed
AND
Download mode works, but the screen will turn blank and vibrations start buzzing.
My phone is having seizures. The only way to stop the vibrations is by pulling the battery.
I have accepted the fact that the phone may be done for.
It was a great 4 months together. tear*

Well, if you can't get it sorted out there's always this! Unless the hardware is busted, but maybe he can fix that too??
http://www.youtube.com/watch?v=AkJQAbwZjRk

Did you try booting into recovery mode instead of odin?

Is that an overclock kernel? If so sounds like may be set to high. And did u choose set on boot.

silver03wrx said:
Is that an overclock kernel? If so sounds like may be set to high. And did u choose set on boot.
Click to expand...
Click to collapse
No, its not. Can't OC or UV. It can only UC.
Sent from SKYROCKET
NexusMod 4.0
Romracer 0.3

if u can boot into cwm flash darkside

OP... what rom/kernel/modem were you running before MHX-SuperLite? and what wipe process did you use prior to MHX flash?

Can you get into recovery and restore a backup?
If you don't have a backup and can get into recovery, try wiping data/cache, then go into mounts/storage and format system, data, and cache, then go to advanced and wipe Dalvic cache. Then power down and try to Odin back to stock again.
If this doesn't work, try another data cable or usb port on your machine (or another pc if this doesn't work). Maybe communication is getting lost due to bad usb connection...
EDIT: Are you saying you tried to Odin even though Odin wasn't recognizing your phone? That could be part of the problem. Try re-installing the Samsung drivers and see if Odin sees it then.
If you can get into download mode you aren't hard bricked yet...

I think he is saying that Odin recognizes his phone but his phone goes black before he can't start the reflash right?
Sent from my SAMSUNG-SGH-I727

Did we lose the OP'r? I was just getting ready to flash this ROM (MHX) but Jooosty has thrown up a curveball. Hope you get it resolved.

Okay sorry for late response.
But i was running skyice speed before hand.
Ive only used CWM to wipe data.
No OC or UV on this kernel.
Cant get into cwm or recovery. The screen turns blank before i can do anything at all.
Ive concluded its most likely a internal hardware failure maybe...
Going to try to sell for parts

DoctorQMM said:
Did we lose the OP'r? I was just getting ready to flash this ROM (MHX) but Jooosty has thrown up a curveball. Hope you get it resolved.
Click to expand...
Click to collapse
MHX is great. The rom has nothing to do with it i believe

Jooosty said:
Okay sorry for late response.
But i was running skyice speed before hand.
Ive only used CWM to wipe data.
No OC or UV on this kernel.
Cant get into cwm or recovery. The screen turns blank before i can do anything at all.
Ive concluded its most likely a internal hardware failure maybe...
Going to try to sell for parts
Click to expand...
Click to collapse
I wouldn't give up just yet. I have never seen an instance of a hard brick where you could get into download mode. Try using Odin from another machine (preferably not a laptop).
If it's internal hardware failure then you have a defective product that is covered under warranty. Call support and get them to replace it (as a last resort of course--I honestly think you'll be able to get Odin to work if the drivers are properly installed and you have a solid usb connection).
EDIT: If you insist on selling it, please pm me so I can make an offer!

skrambled said:
I wouldn't give up just yet. I have never seen an instance of a hard brick where you could get into download mode. Try using Odin from another machine (preferably not a laptop).
If it's internal hardware failure then you have a defective product that is covered under warranty. Call support and get them to replace it (as a last resort of course--I honestly think you'll be able to get Odin to work if the drivers are properly installed and you have a solid usb connection).
EDIT: If you insist on selling it, please pm me so I can make an offer!
Click to expand...
Click to collapse
He already said Odin/connection isn't the problem. His phone won't stay on long enough for the communication to be made. According to what he said, it has nothing to do with machine/drivers/cable. He needs a way of keep the phone on long enough to make the connection, or somehow communicate with it another way. Unfortunately, I have no ideas. Although, I really hope someone does. That RussianBear guy seems to be onto something with communicating with the emmc without the phone being on... or something like that.

heres a link to a video update!
http://imageshack.us/photo/my-images/254/oww.mp4/

Jooosty said:
heres a link to a video update!
http://imageshack.us/photo/my-images/254/oww.mp4/
Click to expand...
Click to collapse
Man that is so weird. Random, but have you tried leaving it plugged in and charging for a few hours? Haha I just can't think of anything else.

plwalsh88 said:
Man that is so weird. Random, but have you tried leaving it plugged in and charging for a few hours? Haha I just can't think of anything else.
Click to expand...
Click to collapse
Or even a external battery charger maybe there is just enough juice to turn on and then dies
Sent from my SAMSUNG-SGH-I727

The battery is fine. Wouldnt keep rebooting if otherwise. O well.
Just bought a captivate to feed my android in me
Sent from my SAMSUNG-SGH-I897 using XDA

DUDE!!!! mine just started doing the EXACT same issue....SOB....
no cwm, no download, just reboots...i acn see cwm lettering for like 0.1ms then it reboots, and reboots every second...download mode, as soon as I choose continue, it goes into reboot loop.....
this is exactly what happened when it happened to my phone......
I went to hit the power button to lock the screen, was listening ot music on power amp. instead of screen locking, the power menu came up...hit back, and tried ot lock screen again? screen went black, 2 vibrates back to back....then saw sgh-i727r boot logo, then black and 1 second vibrate intervals.....
got it sitting in rice right now in case it got wet...battery litmus paper is good...only thing it may have gotten warm today, was working outside and it was 26° celcius....
I did drop it about 1.5 months ago and changed my screen about 3 weeks ago...unfortunately I broke the old lcd when removing the screen, I guess I didn't heat the glue enough...so I can't pop it back in and test to see if related...
I may take apart my phone in a bit and see if any liquid has leaked in...but I didn't get wet....
i think i'm going to order a gt-i9100 again, as I miss that phone.....

xtechx said:
DUDE!!!! mine just started doing the EXACT same issue....SOB....
no cwm, no download, just reboots...i acn see cwm lettering for like 0.1ms then it reboots, and reboots every second...download mode, as soon as I choose continue, it goes into reboot loop.....
this is exactly what happened when it happened to my phone......
I went to hit the power button to lock the screen, was listening ot music on power amp. instead of screen locking, the power menu came up...hit back, and tried ot lock screen again? screen went black, 2 vibrates back to back....then saw sgh-i727r boot logo, then black and 1 second vibrate intervals.....
got it sitting in rice right now in case it got wet...battery litinus paper is good...only thing it may have gotten warm today, was working outside and it was 26° celcius....
I did drop it about 1.5 months ago and changed my screen about 3 weeks ago...unfortunately I broke the old lcd when removing the screen, I guess I didn't heat the glue enough...so I can't pop it back in and test to see if related...
I may take apart my phone in a bit and see if any liquid has leaked in...but I didn't get wet....
i think i'm going to order a gt-i9100 again, as I miss that phone.....
Click to expand...
Click to collapse
What ROM were you on man?
Sent from SKYROCKET
NexusMod 4.0
Faux 010m

[Q] Nexus S (i9023) won't start. Need help

Let me try to explain as comprehensively as possible what happened before I couldn't start my Nexus S again.
Until yesterday, I was running an older CM9 Nightly, together with the Matrix CFS kernel (18.0) and an older reloadedICS mod. Everything was running fine. Well, except for the fact that every time I rebooted, it took 2 or 3 times before it actually started. So 2 or 3 times, while rebooting, my Nexus S rebooted again, or just crashed so that I'd have to pull out the battery. But when my Nexus S finally started, it worked fine. I still had the occasional crash, but everything worked.
Yesterday, I decided it was time for a new nightly. So I downloaded the CM9 nightly from 7 april, the latest gapps, the newest matrix CFS kernel (18.5), and the Reloaded ICS 1.9b2 mod. Before I flashed everything, I wiped cache/dalvik cache, as always. I did flash everything at the same time though.
I didn't like the new icons in the statusbar from the latest Reloaded ICS mod, so I downloaded a different version of the Reloaded ICS 1.9b2 mod that someone had uploaded, with the different icons. That also worked fine. Every icon changed, except for the battery icon.
I used my Nexus S for the day. I listened music, browsed the web, whatsapped with some people... It worked fine. Then I went and watched some TV. After that I went to bed, and I noticed the battery of my Nexus S was empty. Since I wanted to check my mail/facebook before I went to sleep, I put my Nexus S in the charger. I started it, that worked fine. It said the battery had 0% on the statusbar, and because of the new battery icon from the Reloaded ICS mod, you can't see anymore if your Nexus S is charging. But it started, so I guess that's what counts.
So I started facebook (in the browser). Halfway loading, my Nexus S crashed. I experienced crashes before, certainly with CM9 nightlies, so I wasn't really surprised. I pulled out the battery, because the power button wasn't working (again, wasn't surprised, that's normal with that kind of crash).
And that's when things went wrong. My Nexus S wouldn't start again. I tried starting it in fastboot mode. Didn't work.... I put it in the charger for the night, but the charge icon (the white battery icon) didn't show up on the screen. And the next day (today), it still didn't start. I know someone who also has a Nexus S, so I tried his battery. Didn't work. I tried his charger. Didn't work. But when he tried MY battery and charger in HIS Nexus S, it DID work! Well, except for the fact that his Nexus S is still trying to boot up, after half an hour...
So that's two Nexus S's dead. One that won't even charge anymore. The other at least shows signs of life. I have no idea how this is possible. Clearly it has something to do with pulling out batteries, since his Nexus S wouldn't start anymore after he pulled out the battery when it was still turned on, and my Nexus S wouldn't start anymore after I pulled out the battery when it crashed.
By the way, my friend's Nexus S is not rooted. He is using stock ICS.
Thanks a lot in advance!
Edit; i also noticed that my battery was going down exceptionally quick after the 7 april nightly. I don't know if this is relevant.

Try this to see if you can get it up to fastboot. After this you'll want to have fresh ROMs (preferably stock for now) ready to flash. Data/factory reset, format /system and format /boot, then flash the new ROM in recovery.
Hopefully this works for you and possibly your friend. Does his phone enter bootloader (Vol. Up + Power)?

Harbb said:
Try this to see if you can get it up to fastboot. After this you'll want to have fresh ROMs (preferably stock for now) ready to flash. Data/factory reset, format /system and format /boot, then flash the new ROM in recovery.
Hopefully this works for you and possibly your friend. Does his phone enter bootloader (Vol. Up + Power)?
Click to expand...
Click to collapse
Thanks for your help! I'm going to try that.
Yes, his phone can enter bootloader.
I've found some other people on the internet with the same problem as me. First there were problems with rebooting (it would only start after the second or third try). Then the battery drained exceptionally quick. And then, no signs of life at all... http://groups.google.com/a/googlepr...gory-topic/mobile/android-devices/06zm2LENFpc

Try to go into recovery and download the Stock 4.0.3 (hopefully he's still on 4.0.3) FULL ROM and flash that (needs to be named update.zip, can flash through stock recovery). If this doesn't work it might need the bootloader unlocked at least and data will most likely be lost at this stage.
There have been some people who have had battery drain issues while the phone is off. I've not heard of anything to suggest anything besides a hardware fault which requires the mainboard to be replaced, unsure if this is related at all.

Harbb said:
Try to go into recovery and download the Stock 4.0.3 (hopefully he's still on 4.0.3) FULL ROM and flash that (needs to be named update.zip, can flash through stock recovery). If this doesn't work it might need the bootloader unlocked at least and data will most likely be lost at this stage.
There have been some people who have had battery drain issues while the phone is off. I've not heard of anything to suggest anything besides a hardware fault which requires the mainboard to be replaced, unsure if this is related at all.
Click to expand...
Click to collapse
My friend can't get into recovery anymore... It shows the green android icon for a flash of a second, and then it shuts down... But at least he can get into bootloader mode... I guess that's something.
I guess it has something to do with my battery, since that is what killed my friends Nexus S. I don't think my problem will ever be fixed though. That ubuntu app is worth a shot, but for that I need a computer that can run ubuntu and windows, and I don't think I have that.
I've also found this: http://mobiletechvideos.mybigcommerce.com/nexus-s-jtag-brick-repair/. Is that worth a shot? I'm willing to pay that kind of money for it. I do a lot of things myself without having too much knowledge, but this goes a little too far...

I personally wouldn't go for a jig, i can't vouch for them at all. I hear it it isn't too difficult to make your own though (3x100kOhm resisters in series or something). Wouldn't be worth $40, closer to $2 if you already have a soldering iron.
Your mate can get into recovery, he just can't see anything because he's on the ICS recovery (it doesn't turn on the SC-LCD's backlight, common problem). Shine a bright lamp on it at an angle and you should be able to make out what's there. Power + Vol. Up to get past the exclamation and android, then shine up the top. If he's happy losing his data (and slightly possibly his warranty) to unlock the bootloader i'd be going for that instead.
Just about any computer can run ubuntu. You might even be able to run it straight off the livecd. This is the first thing i would try.

Harbb said:
I personally wouldn't go for a jig, i can't vouch for them at all. I hear it it isn't too difficult to make your own though (3x100kOhm resisters in series or something). Wouldn't be worth $40, closer to $2 if you already have a soldering iron.
Your mate can get into recovery, he just can't see anything because he's on the ICS recovery (it doesn't turn on the SC-LCD's backlight, common problem). Shine a bright lamp on it at an angle and you should be able to make out what's there. Power + Vol. Up to get past the exclamation and android, then shine up the top. If he's happy losing his data (and slightly possibly his warranty) to unlock the bootloader i'd be going for that instead.
Just about any computer can run ubuntu. You might even be able to run it straight off the livecd. This is the first thing i would try.
Click to expand...
Click to collapse
That tip with the bright lamp really worked! Thanks for that! But the first time he didn't do the factory reset yet, and now he can't even see the recovery menu (not even with a bright lamp), just the exclamation mark...

He needs to press Power + Vol. Up while he can see the exclamation mark. This will exit the splash screen and enter the actual recovery menu.

Thanks! But the factory reset didn't work, unfortunately... He is still stuck in boot...

As a matter of fact, oldblue has written up good instructions to get the phone to factory-stock state and fastboot flashable images. These should overwrite everything that should be overwrited on the phone and throw stock google stuff on there. Definitely something to try out, i would be doing this beyond anything else.
Note that it requires unlocking (and relocking later) the bootloader, and this will also erase all data on the phone and internal sdcard.

My friends phone works again. The factory reset did work after all! Hurray for him, lol
I'm going to try that ubuntu app later today. After that, oldblue's guide might come in handy!
Thanks a lot for all of your help, Harbb!

Happy to help and best of luck. Definitely use AdamOutler's app to the best of it's ability, it can do damn near anything. There is one more thing to try on top of this too if nothing goes to plan but it could be a potential sacrifice (minor hardware mod). Let's just hope this works.
The fastboot images would be, theoretically, a more perfect way to return to stock, so if this is possible to fix by software alone you'd be hard at work trying to find a better alternative. Maybe your phone is recoverable after all.

Androyed said:
My friends phone works again. The factory reset did work after all! Hurray for him, lol
I'm going to try that ubuntu app later today. After that, oldblue's guide might come in handy!
Thanks a lot for all of your help, Harbb!
Click to expand...
Click to collapse
No dont try the ubuntu tool unless it doesnt turn on, you cant boot into bootloader or you cant turn it on, and you see nothing on the screen.
---
die tool is voor echte gebrickte nexussen.. gebruik die aleen als je dus niks meer ermee kan, zoals dat hij nieteens in de bootloader kan booten. (dat was met demijne gebeurd).
succes , als je vragen hebt PM me maar.

Same Problem?
Hey guys, i have a Nexus S (never rooted or anything). I received the update notice for ICS so i duly updated. Right after, my phone was bricked. Doesn't turn on / respond to anything.
I ran the UnbrickableRessurector by Adam and I can get Fastboot Mode to show up this way. I was really hoping that i don't have to unlock it or anything as i don't want to void warranty.
Any thoughts? I tried selecting 'recovery' after which the screen goes dark. Shining a bright light on the display doesn't help - really can't make out anything. Do i have a different problem?
Thanks!