Finally found the answer in the Nexus forums: http://forum.xda-developers.com/showthread.php?t=1379875
--------------------------
Please tell me I'm not missing the obvious. Here's the deal.
When the phone is booted and running normally, adb works fine. No problems looking around/pulling/pushing/changing permissions/etc...
But when I boot into recovery, it says it has found a new device (Android Samsung SPH-L710 or something like that) and wants to install drivers for it. I have searched thoughly using just about every combination of "adb" "Samsung" "recovery" "Galaxy S3" etc, etc, etc I could think of. They all point to the drivers I already have !!!
I like to make custom icons for things like the title bar, you know, just add a little color to the signal strength, data in/out arrows, things like that. My usual routine with my old EVO was to hook up to the computer, use the batch files I have written to pull framework/SystemUI or whatever, drop in the png I changed, then reboot the phone to recovery and push them back. I don't like using root explorer to put them back while the phone is running normally, but that's what I've had to do so far.
Can someone point me in the right direction? Am I missing the obviuos (wouldn't be the first time ) ?
Nobody? Is adb working for you in recovery?
Related
Ok I don't know where i went wrong but i attempted to flash my sprint optimus s and needless to say. i messed something up. it boots up w/ the sprint/lg logo and it boots into the android os. the odd thing is there is no apps, no menu bar, just the top white strip with the signal gague and the time. can someone help me please????
what did u flash with? sounds like a phone without a homescreen. try going to adb and making it install any kind of homescreen (you need a apk file though.) and try from there. also u can reflash/nandroid restore
well also its frozen and the pull down menu does not work...
I have yet to find an answer to this while searching for the past day, so I'm going to ask about it here.
My LG Optimus V's (just got it a few days ago as a birthday present) screen seems to be permanently blank... In case someone asks... yes, it is activated.
What Happened:
I rooted the phone using Gingerbreak 1.2, installed rom manager/clockwork recovery mod, then attempted to backup my phone in case something went wrong. However, when I started the backup, I noticed that the screen was completely blank. I was kinda freaking out, so I just took a shower while it did it's thing. When I came back, it was done creating the backup and it showed up in Rom Manager. After toying with some of the things I can do with it rooted (I only rooted it to see how much of a difference it would make without changing the kernel), I decided to recover that backup. When my phone restarted to recover the backup, the screen was blank once again. After waiting for over an hour, I concluded that it must have finished (since my HTC Hero would finish restoring and never reboot until I tell it to) and took out the battery. Afterwards, it would show the LG splash screen... then the blank screen.
What I Did:
I was thinking about the android screencast java application a few hours after my problem first developed. I plugged my phone into my computer, got adb working, and android screencast showed me that my phone was actually getting stuck at the clockwork recovery mod screen. I tried many things... I installed a CM7 rom, flashed 3 different recoveries, flashed an overclocked stock rom, etc. Eventually, I flashed the stock rom (no changes whatsoever) and stock recovery. Now I can hear my phone, but cannot see it. However, I should note that while using CM7 the same thing happened. The only difference being that I could use android screencast to see the screen (the phone was actually working) with CM7. Now with the stock rom, adb is disabled and I cannot see the screen or do... anything.
What I Think I Should Do:
I'm thinking about calling Virgin Mobile and telling them that my screen is defected. If they see the issue they'll probably think that it's a hardware issue (for all I know, it could be) and they'll probably give me a replacement. However, if anyone as had the same problem and fixed it, I would love to know.
I would love you hear your opinion on this and, if possible, a fix. Thanks in advance!
(JIC, if I posed in the wrong section, I'm sorry...)
you poor souls reporting the symptoms of getting the newer screen hardware from the optimus s in your v's don't number in the double digits yet, but it's getting closer.
I posted a fix on AndroidCentral, see it:
here
good luck! the fix has worked for everyone I pointed to it so far.
btw, the screencast idea is excellent!
crud. stock recovery, you may be SOL.
you'll probably have to boot into custom recovery to use screencast or adb now.
use the unplug phone -> pull&replace battery -> hold home+volume down -> keep holding, press and hold power until lg screen goes blank to enter recovery. maybe adb will work in stock recovery, I dunno.
Thank you very much for the reply!
Yeah, you're right, I'm probably SOL... I still have one option though! Theoretically, I should be able to turn on ADB without being able to see my screen. I know how to access the settings without seeing it, but navigating myself to the "Applications", "Development", "USB Debugging" may be a little hard. I will attempt to do so. I will report my progress in a bit.
However, if you (or somebody else) could provide screenshots of a step-by-step process to turn on USB Debugging in the stock rom (since it's kinda hard to do remember where everything is and screenshots of different phones is kinda different) then I would appreciate it VERY much!
I shall update this in an hour or so.
UPDATE (9/2/11 - 9 PM):
I'm going to take a break for now. Good thing I give everyone my Google Voice number, I doubt anyone will notice a change. I'm going to flash a stock rom onto my HTC Hero so I can figure out where things are on the LG Optimus V (Same screen size) in an hour or so. I'll update my progress in like 2 hours.
UPDATE (9/3/11 - 8:10 AM):
I have been unable to turn on USB Debugging and it seems to be because I don't know where the confirmation after turning it on is located. However, I should note that when I boot into (I think) recovery, "adb devices" states that the device is attached but offline. If there is a way to make it "online" from stock recovery then I would love to know. For now, I will try everything I can.
UPDATE (9/3/11 - 8:22 AM):
Ok. I plugged my phone into the back of my computer and now when I do "adb devices" it detects the device in recovery mode. However, when I try "adb shell" it says "- exec '/system/bin/sh' failed: No such file or directory <2> -". I'll try some more stuff, but does anyone have any idea of what I can do? Android Screencast doesn't work either, so that's not an option.
UPDATE (9/3/11 - 9:42 AM):
Crap... now it's indefinatly booting into recovery... I had something like this happen before, I'll report my status in an hour or so...
UPDATE (9/3/11 - 12:36 PM):
My friend finally got my phone booting out of recovery again! Now all I have to do is get "USB Debugging" on and it SHOULD work!
I <think> there's a key combination to power up into the bootloader. if you can find it with searching here and android central.
I haven't been able to track that down today. If you can get into the bootloader, you can fix it. Search for asadullah's fastboot root instructions here if you find a way to get into the blue screen (the bootloader, which fastboot talks to.)
otherwise, I'll be done taking the kids to the (ugh) pool in a few hours and I'll search more.
try pulling your battery for a few minutes and see if the reboot cyle stops that way, at least it might get into recovery or the rom.
glad you got back into recovery again, not too sure how to help at this stage though, since I can't find a way to get into the bootloader with a power-on key combo. just emergency mode (useless to the V since the firmware from LG is missing a file) and safe mode. boo.
there is a youtube video for enabling usb debugging on the v, maybe it'll help you find the right spots to press.
http://www.youtube.com/watch?v=nHal0hPNS6s
edit: you can also try to reboot into the bootloader with adb, even though it's missing the shell... it's worth a try, and if it works you can flash xionia recovery with fastboot and things would be a lot easier from that point.
Code:
adb reboot bootloader
if that works but you need more help, a battery pull is the only way to power off with the bootloader except "fastboot reboot" will try to boot your rom.
Awesome, thanks for the replies! I'm going to try your suggestions now. I'll let you know how things work out in a few hours. I would have replied earlier, but to my satisfaction there was a surprise party planned for me, lol. I will defiantly try these out now.
Once again, thank you very much. I honestly did not expect a reply for something that happens to such few people.
bigsupersquid said:
I <think> there's a key combination to power up into the bootloader. if you can find it with searching here and android central.
I haven't been able to track that down today. If you can get into the bootloader, you can fix it. Search for asadullah's fastboot root instructions here if you find a way to get into the blue screen (the bootloader, which fastboot talks to.)
otherwise, I'll be done taking the kids to the (ugh) pool in a few hours and I'll search more.
try pulling your battery for a few minutes and see if the reboot cyle stops that way, at least it might get into recovery or the rom.
Click to expand...
Click to collapse
I'm honestly not sure what my friend did, lol. She was just messing with it while it was, apparently, in recovery and it ended up rebooting and loading the rom. I, honestly, don't want to risk getting stuck in recovery anymore since taking out the battery for an hour didn't do anything... If I'm unable to get adb on using what I know from that video then I'll try booting into the bootloader. Like I said before, I'll report my status in a few hours. I really appreciate your help up to now!
EXTREMELY HAPPY UPDATE!!! (9/4/11 - 1:22 AM)
I was able to turn on ADB! I used what I learned from that video and how turning on ADB works on my HTC Hero to get it working and it's FINALLY ON! Now I can attempt to flash the recovery, kernel, and everything else in order to get it working! Thank you VERY much! I will let you know how everything turn out
Another Wonderful Update! (9/4/11 - 2:03 AM)
I have flashed the recovery.img (the Xionia CWMA one) and can see my screen in recovery! I haven't seen anything on my screen besides the LG splash screen so I'm overwhelmed with joy! I'm flashing a new ROM and the other stuff now!
Final Update! (9/4/11 - 2:09 AM)
2:05 AM - I see the rom's boot screen!
2:06 AM - I see the CM7 Mod boot screen!
2:08 AM - I see the UI on my screen and everything seems to be working! Thank you VERY much!
Quick question though... If I want to install a new ROM, do I need to flash the xionia anykernel one directly afterwards?
ah, excellent! glad it's working now.
you're the most persistent (and maybe technically apt) person I've helped with this so far.
I still think that using screencast was the best new idea I've seen yet.
yes, you'll need to flash the xionia kernel after flashing any rom or rom update.
roms come with their own kernel in the boot.img, and none of them currently out for the v have the video drivers from the newer sprint kernels.
right now, xionia kernel is the only thing that works.
and, you'll need to flash the key swap after changing roms, as well, but at least forgetting to do that won't take out your display.
now that you've got xionia recovery on your phone, it should be a lot easier next time.
Thank you for both the help and the compliment!
I don't like giving up when it's something I know I can do. I figured that if I was able to mount my SD card without being able to see the screen, I should be able to turn on USB Debugging as well. About the Android Screencast... I didn't actually think about it until it until I plugged in my phone while the screen was blank, ran "adb devices", and saw that my device was detected within recovery. I figured that I might as well give it a shot... and it worked.
Alright, that's what I figured. Hopefully someone realizes what's happening with refurbished Optimus V smartphones and ports the newer sprint kernels to the Optimus V. I feel like I got ripped-off though... I bought my phone "new" and got a refurbished one. I can't really do anything though, we're not technically supposed to be rooting our Virgin Mobile phones anyways, lol. I'll be sure to do that everytime now though. For now, I think I'm good with the Bumblebee rom.
Once again, thank you VERY much for your help! I know I would not have been able to fix my phone without your help.
EDIT:
Oh yeah, btw, if the Optimus V ever gets stuck in stock recovery, press the "back" button then "home" button to boot into the rom. Not sure why it works (I was never able to see the screen), but it worked.
There is a key combo!
First time caller long time listener... I bricked my own Optmus V with a bogus ROM. To boot into recovery without adb press (Home)+(Volume Down)+(Power) Now rocking CM7!
I installed CM7 Alpha Final (SD card version) and was working on getting the interface back to how I had it on the previous version. I used CWM to install "transparent status bar icons.zip" from this thread...
http://forum.xda-developers.com/showthread.php?t=1471066
Upon installation I went to reboot and now I'm stuck on the CyanogenMod7 boot screen and looping endlessly.
If anyone has any idea how I can fix this, I'd really appreciate some help.
Thanks!
Retcon:
I just remembered that I did NOT have this installed on the previous version on CM7. On CM7 i had a standard theme dock, so I think I installed something that just wasn't compatible with CM7 at all. What do I do now?
Thanks.
Most likely that transparent icons xip was not built for cm7 and rather was built for stock firmware. They are not compatible. Reinstall cm7.
What method can I use to reinstall? Since I'm in a bootloop I can't get to CWM. Or is there some kind of "safe mode" I can boot into?
Sent from my T-Mobile G2 using xda premium
Turn the unit on, when you get to the n screen, hold the power button until it turns off. Repeat 8 times and you will be forced into CWM.
If you have adb installed on your pc, plug it in, turn it on and check devices. If you are listed, do an adb shell reboot recovery and that will put you into recovery instantly.
I tried the 8-boot method two different ways...
1. Pressed the power button and released. When I saw the N screen, I pressed again and held until the unit powered down.
2. Pressed and HELD the button through it powering on and not releasing until it shut back down again.
Does it matter which of the above ways I do it? I wasn't able to get it to work. Does it have to be exactly 8 times? I don't think I stopped short but I might've done it more than 8...
Regarding the ADB method, I went ahead and installed the SDK but I'm not seeing my devices in ADB DEVICES. Since this is a new computer, I think I just don't have the right drivers installed. I went to Indirect's root thread to get those drivers but his dropbox link is disabled due to high traffic. Is there somewhere else I could get the appropriate driver? And once I have the correct driver and can see my device in ADB DEVICES (I'm assuming I'll be able to see it even though I'm bootlooping the whole time?), what is the code/line to get it into recovery?
Thanks for your help thus far. I really appreciate someone taking the time the time to help me out.
Oh, and a correction to my original post - I used the internal root method, not SD.
I found a working link for the drivers.
http://www.mediafire.com/?w6y5ld1jeuh65i1
I installed them and I can access my tablet now. I can see my device and its responding to commands.
So all I need now is the command to get into CWM. I tried "adb reboot [bootloader:recovery]" which I saw in the cmd window, but it just gave me a standard reboot.
Thanks!
EDIT: I tried "adb reboot recovery" and that did it. I'm back in business! Thanks for the help, Know-Fear. Although in my n00bishness, step-by-step handholding would've been nice, your replies gave me enough for me to at least know what general direction to look in. I still couldn't get the 8-boot method to work, but maybe that's just a dexterity issue. The adb method worked perfectly once I stumbled my way to the command line.
Make sure when you reinstall you do a partition wipe.
Glad you got it working thus far. Hopefully no more problems will arise after the new install.
Hey all, this is my first post on this forum. I registered just to let my voice be heard.
Let me just say that I have done extensive research into these problems but I don't want to brick my phone so I want to know the direct steps for me.
OK my problems are:
Upon turning on the phone the original Motorola logo is gone and is instead replaced by:
"Unlocked. PwrReason: PWR_KEY_PRESS. OS will boot in 5 seconds. Press a key to stop countdown. Avaliable Modes are: " and lists 14 different modes I can choose
This happened after I accidentally deleted my pds folder or something of the sort. I must've partitioned something accidentally and as a result my phone did not boot the next time around. It booted after I did a battery pull but gave me the next problem.
Upon booting into CM10.1 I noticed that the soft keys would not work. The entire screen was recognized as one big touch surface.
I deduced that some file was deleted which makes the screen recognize the soft keys, so I proceeded to do some research into it. The methods I saw to do were doing some sort of pdsfix which is not recommended unless necessary, which in my case is very necessary. I can boot into Romracer's recovery (5.0.2.7 I believe it is) as well as my OS. Everything is working except for those problems I listed. I am not sure if my phone can boot into fastboot but I can try. Please post your answers because I really need to get my phone working perfectly again. At this point, it is only useful for texting and a little music (and settings). I can't go into much else without restarting the phone each time (you must know why).
EDIT 15/04/13
-----------------------------------------------------------
I just flashed pdsfix(gingerbread).zip and I am now able to use my phone at normal speeds and even overclock if necessary. I was running epinter's CM10.1 Rom
Fixed half the problem!
Okay so after many hours of trying, I managed to install the drivers for fastboot on my computer and did the fix for the pds file.
First I downloaded moto-fastboot.zip and extracted to my C:/ drive.
Then I tested if my device was recognized. It didn't recognize it at all, so I went into device manager.
In device manager there was my problem. I saw fastboot with a yellow exclamation sign. I right-clicked it and directed it to where I had previously downloaded fastboot drivers. (Found them here: FASTBOOT DRIVERS
It installed nicely and when I tried the commands listed in Method 2 on this page PDS Partition Fix it worked perfectly!
So I proceeded to restart the phone, no issues. But the Motorola logo at the very beginning is still not there. It says unlocked at the top left and displays the same options as before. The phone is still fully functional without it, but I want to get it back. I will be doing more to fix this though.
But the best part is that, my soft-keys are working perfectly! :laugh: I do notice a little lag in the system but that will be fixed soon. Hope this helped anyone who didn't know what to do.
P.S. If you find a way to restore the Motorola logo on boot, please tell me!
http://forum.xda-developers.com/showthread.php?t=1423763
Logo and animation
Mojar7070 said:
http://forum.xda-developers.com/showthread.php?t=1423763
Logo and animation
Click to expand...
Click to collapse
Perfect! Thanks much for finding that for me. I now have the problems fixed except that my cpu won't clock above 608 mhz even when I put the min clock slider higher than that value.
I suspect that perhaps I flashed the froyo pdsfix instead of gingerbread. Maybe that is causing the problem. I'll try and post my results soon.
My Atrix 4g is fixed!!
Wow I can't believe I finally fixed it! It was as I suspected. After downloading the pdsfix(gingerbread).zip I rebooted my phone into fastboot and proceeded to flash the zip. And who would've guessed it? I am now able to clock at usual speeds including the 1000MHz of old ^_^. I am sooo glad I found this forum. If anyone had similar problems you can try the steps I did.
P.S. For the record I was running epinter's CM10.1 Rom for the Atrix 4g. I may go to Neutrino's in the near future, but I am just glad to have my phone back in working order :laugh::laugh:
Alright. I need some advice one last time, I swear... after this I'm not going to try to do anything.
Phone worked quite well for 2 days. I was enjoying this rom quite a bit. I decided to change the DPI down to 560. I saw that some others in this thread had done so quite easily... so I used this app to change it. Made the change to 560, granted supersu permission and rebooted. Only problem is that... the phone has yet to turn back on. At the moment the only thing I can get it to do is give me a screen that shows a large white empty battery with a cable leading up to it and a hazard exclamation mark in the bottom right when I am trying to put it in download mode. I have tried on multiple computers to restore back to stock following these directions. The best that happens is my computer recognizes an unrecognized device. No luck.
I would love to change the buildprop back or anything, but not even adb recognizes the device.
Otherwise, nothing. I can't get into recovery. I can't get the phone to start at all. All black screen. I can't get any reaction out of it. Any advice would be helpful, I'm on hour two of this. I realize that this is most likely not a problem with the rom, but wanted to see if anyone else had an issue and has advice/let anyone else who's thinking of changing the DPI and shared my troubles reconsider.
Thanks again!
The empty the battery logo is because the phone is dead try charging it for like 30 mins. Also it seems that app you used is 3 years old so it does not support lollipop or even kitkat. After charging it try get it into recovery and restore a backup. If you don't have a backup try wiping your data and cache.
1619415 said:
The empty the battery logo is because the phone is dead try charging it for like 30 mins. Also it seems that app you used is 3 years old so it does not support lollipop or even kitkat. After charging it try get it into recovery and restore a backup. If you don't have a backup try wiping your data and cache.
Click to expand...
Click to collapse
Thanks for the reply!
That emblem only shows up when the battery is removed and I'm trying to put the phone in download mode. So it makes sense. Any other ideas? The battery that I'm using is about 80% full. I still can't find a way to recovery mode.
What other information can I provide to help you out?
Well when your in download mode it does not take any commands can you get the lg powered by android screen? Or just nothing happens? If nothing at all happenes it is most likly bricked. If it boots to the lg screen it is most likly soft bricked.
Bricked- Phone is dead and very very hard to fix if there is a fix
Soft Brick- No OS so you have to reinstall a rom could also be, because of apps.
1619415 said:
Well when your in download mode it does not take any commands can you get the lg powered by android screen? Or just nothing happens? If nothing at all happenes it is most likly bricked. If it boots to the lg screen it is most likly soft bricked.
Bricked- Phone is dead and very very hard to fix if there is a fix
Soft Brick- No OS so you have to reinstall a rom could also be, because of apps.
Click to expand...
Click to collapse
No screen. For anything (other than described).
This is exactly what I was afraid of, but my phone has always been odd. This dead battery screen has always shown up in download mode... even when my phone worked, I've never had the firmware update screen. Which has always been weird to me.
However, the only time my phone shows anything is with the dead battery screen. During such it will show up as an unrecognized device when attached to a computer, again... it's always done this. I was just curious if there was something else or a suggestion that someone more experienced then myself might have.
No that I read it, it sounds like there maybe a very slim chance of getting your device to work. If you mange to get some drivers for the unreconized device driver you maybe able to send adb and fastboot commands. I found this one tool (will limk below) that is call cydia impactor I found in one of rootjunky's toolkit files. I used this one function that was able to make drivers for my sony smartwatch 3 and phone. I will link for the direct download make sure to extract the zip. Inside of the zip you will find another zip called "Impactor_0.9.14.zip" make sure to extract it to it's own folder. If you want you can delete the first folder juat save the impactor folder. Then run the program called "Impactor" can connect your phone to the computer and click on the tab called "USB" then click the button called "Driver Scan". Follow any on screen instructions. It should now generate a driver for your phone if all went well and it will be reconized. Then you should be able to run adb reboot recovery or fastboot reboot-bootloader. The fact that your computer is even seeing the phone tells me that it has so hope of being fixed because your computer see's it. Your device might be in a bootloop of some sort. You may just have no os installed and it may have just glitched.
Download: http://rootjunkysdl.com/getdownload.php?file=Tegra Note 7/ADB root.zip (will immeditly download it)
Worst case scenario, you may try this, or at least read it for general info. I don't think you'll have to go this far though
http://forum.xda-developers.com/showthread.php?t=2582142
[FIX] NO Recovery mode, No download mode, after OTA on rooted LG G2
i changed my dpi once and it bootlooped on me. i was lucky enough to get into recovery and then i restored the data partition from an older nandroid.
i agree with 16. it does sound like the drivers may not be loaded up properly if your computer recognizes a device. have you tried the official lg drivers?
What system are you guys running?
Well, I've found out that for whatever reason... on my phone I have to take out the battery for a period of ~5-10 mins on any change DPI, system rom update, anything. Otherwise, my phone will not turn on. So if someone else find this, give it a try.