So my friend broke the screen of her LG Optimus G Pro with pictures on it, I was wondering if it was possible to copy them off of it. From what I remembered I could start it up with Power+VolumeDown into the bootloader, run fastboot boot recovery, then adb away. However, this isn't working. It doesn't have USB debugging enabled and it has a password. I have a few questions.
First, is there any easier way to do this? I googled around and couldn't find anything.
Second, is this possible? I remember using adb in recovery with my Nexus 7, but it has been a year and I might have forgotten, or it might just be impossible on this phone. Also, from what I found on the internet, the power button is on the opposite side of the volume buttons, and the Volume Down is pointed at the home button. Is this correct?
Related
Hi Guys,
My powerbutton works pressing down but it seem that the trigger sensor is stuck on. I cannot turn it on from wake either since its already supposedly pressed. The only way is to take my battery out and reboot. Even when I place the battery back in it would start on its own (yea thats how i figured it was stuck..)
So in my mind, I'll just return my rooted phone to Sprint by unrooting it. Ah, there's a problem I can get into Bootloader but i'm not able to toggle the selection because the power button is still active.
Is there anyway I can use adb to push updates from my computer without having control of the phone itself since it's useless?
As far as returning the phone, the problem is a physical issue not a software issue, what are my chances of getting a replacement? Thanks!
If you are still using the volume buttons, can you try to press [again] the power button to select? Also, likely to get a replacement since its a hardware issue.
it wont let me toggle up and down at all at bootloader.
i'm a little concern what they might say when they see its a rooted phone S-OFF feature (that's if they decided to look into the problem further) but its very evident the button is stuck at ON.
I think you should still be able to unroot by hooking it up to your computer and running an RUU.
50/50 they will look in further, since its a hardware issue. And they won't like it being rooted, they may tel you have to pay 100$ if they see it. And I'm not too sure where to push the files via adb, but I believe it can be done.
I searched a bit around and couldn't find anything like my problem.
Basically, my screen cracked and blanked out. I can power it on, it'll vibrate when the google logo should come up.
I know the security code, but I can't enter it because the touch screen and display is off.. and that means I can't connect it to my PC to pull all the pictures and files off. It is unlocked, but I don't think I rooted it. I've read I may be able to use adb to do it and copy the SDcard off, but I have no idea how to do it without seeing the screen.
The PC does recognize it though, but it will not let me into the files until the security code is entered. Verizon couldn't help, and I only have 10 days as I have my replacement already. Any advice would be greatly appreciated.
J Andersen said:
I searched a bit around and couldn't find anything like my problem.
Basically, my screen cracked and blanked out. I can power it on, it'll vibrate when the google logo should come up.
I know the security code, but I can't enter it because the touch screen and display is off.. and that means I can't connect it to my PC to pull all the pictures and files off. It is unlocked, but I don't think I rooted it. I've read I may be able to use adb to do it and copy the SDcard off, but I have no idea how to do it without seeing the screen.
The PC does recognize it though, but it will not let me into the files until the security code is entered. Verizon couldn't help, and I only have 10 days as I have my replacement already. Any advice would be greatly appreciated.
Click to expand...
Click to collapse
You can use Galaxy nexus toolkit to pull files from phone while in ADB mode.
(Hold volume down and up and the power buttone while booting)
And another thing you can try what sounds funny is:
connenct your phone with HDMI onto an external screen and then you or use a USB mouse to enable data transfer or now where to touch the broken screen.
sounds funny btw XD
A friend brought me a tablet at work today and told me that after he received an update the tablet's screen wouldn't unlock and the battery wouldn't charge past 12%. I got the tablet home and turned it on. it let me unlock the screen but kept going to a blank screen with "android system" in the top left corner. I press the home button and it goes to the home screen but all the icons flash on and off the screen. I tired using the hardware reset switch this did nothing. I tried a factory reset by using the volume+, power and screen lock switch. Factory reset went through okay but now when it boots up (after acer and android logos) it immediately attempts to shut down. it will stay on the shutting down screen indefinitely. to my knowledge this tablet has never been rooted.
I searched the forums but couldn't find any info, everyone had rooted then downgraded to get the updates. I do know that the tablet is under warranty still and that it could be sent in for service.
I would also like to note that before the factory reset the tablet would only let me unlock it once, then after i would reboot I was unable to unlock it again until it had set for some time. After the factory reset the tablet come to the blank screen with android system in the top left. the only function that would work was the screen rotation lock switch. after a reboot it would immediately attempt to shut down.
I would like to know if there is anything I can do so that we don't have to send the tablet off for service. I'm sure that I am overlooking something here. thanks.
It sounds pretty screwed. It seems like a bad flash, try running the ICS "leak" available in the dev section, name it update.zip then place it on your external SD card. Power on holding the volume key closest to the lock switch and report what it does next.
Tapatalked from my Thrive - Kuroikaze B13x
pio_masaki said:
It sounds pretty screwed. It seems like a bad flash, try running the ICS "leak" available in the dev section, name it update.zip then place it on your external SD card. Power on holding the volume key closest to the lock switch and report what it does next.
Tapatalked from my Thrive - Kuroikaze B13x
Click to expand...
Click to collapse
Thanks!
Any update on this? I know it's been forever, but I was just recently given an A100 that's doing the exact same thing (sitting at "Shutting Down).
I've been able to reflash via the update.zip, but with no luck.
Nevermind. I was able to fix mine with "SD_Acer_A100_1.014.08_COM_GEN1_full_user.zip" from this link:
http://www.imeiserver.org/download/index.php?dir=Flash Files /ACER/A100/
I renamned it "update.zip", held the left volume button (in landscape mode) while powering it on. The update ran, then it was stuck on the "Android" screen. I powered it off, then held the right volume button while powering it on and moving the screen lock button. After reboot, it was as if it just came out of the box.
I hope this helps someone else.
touch-aaron said:
Nevermind. I was able to fix mine with "SD_Acer_A100_1.014.08_COM_GEN1_full_user.zip" from this link:
http://www.imeiserver.org/download/index.php?dir=Flash Files /ACER/A100/
I renamned it "update.zip", held the left volume button (in landscape mode) while powering it on. The update ran, then it was stuck on the "Android" screen. I powered it off, then held the right volume button while powering it on and moving the screen lock button. After reboot, it was as if it just came out of the box.
I hope this helps someone else.
Click to expand...
Click to collapse
Actual it should be renamed to just "update" because the system adds the .ZIP so if you rename it update.zip it shows up as "update.zip.zip" and that won't work...
So I rooted my Lg G2 just fine, I've done jailbreaks and such in the past and consider myself tech savvy. However after trying to install a custom ROM on my phone, I got these white lines to where I couldn't see my screen. I found a fix for it and tried to conquer that myself as well. As I proceeded to flash a jdi kernel onto my G2 to get rid of the white lines and lack of display, I got an error and put myself into a boot problem. When I turn my phone on, I get a secure booting error everytime and my screen goes black. I have tried countless times to use the hard reset feature but I cannot get the it to come up with pressing with volume down and power buttons. I can't get into download mode either. My screen goes black within seconds and just sits there. SOMEONE PLEASE HELP IN ANY WAY POSSIBLE.
Please.
I really need any sort of help or direction. I've tried everything I can think of.
How did you try to go into download mode?
Sent from my LG-LS980 using XDA Premium 4 mobile app
RodJeremy said:
So I rooted my Lg G2 just fine, I've done jailbreaks and such in the past and consider myself tech savvy. However after trying to install a custom ROM on my phone, I got these white lines to where I couldn't see my screen. I found a fix for it and tried to conquer that myself as well. As I proceeded to flash a jdi kernel onto my G2 to get rid of the white lines and lack of display, I got an error and put myself into a boot problem. When I turn my phone on, I get a secure booting error everytime and my screen goes black. I have tried countless times to use the hard reset feature but I cannot get the it to come up with pressing with volume down and power buttons. I can't get into download mode either. My screen goes black within seconds and just sits there. SOMEONE PLEASE HELP IN ANY WAY POSSIBLE.
Click to expand...
Click to collapse
Greetings, here's what I did, I booted my phone into download mode by pressing and holding the volume up button, and quickly plugging the usb cable into my phone(make sure it's connected to the computer), wait until the device is charged at 100%(you will know it's fully charged when you see something like this "B100", turn off your phone and hold the power button and volume down button at the same time until you see the LG Logo, once you've seen the LG Logo, QUICKLY press and hold the power button and the volume down button at the same time adain, and you should boot into recovery mode.[emoji4]
If you made a backup of your previous Rom, you can now restore it.[emoji106]
Sent from my G3tized LS980 using Tapatalk
I have a Samsung I9250 which I've unlocked, rooted and loaded with Lineage. The Lineage version is 13.0-20171126-NIGHTLY-maguro. The recovery is TWRP and the root is through SuperSU FREE (CM) v2.79-SR3. The On/Off button doesn't usually work. If the phone is off then pressing On/Off has no effect. Occasionally it works for no reason I can see, it seems to be random, but for the most part it simply doesn't have any effect. If the phone is on then the same is true. Turning it off from the On/Off button is usually impossible. I get round this through Settings>Display & lights>Wake on plug. This means I can activate the phone by connecting it to a PC using its USB cable. This will activate the phone immediately if it is off. It doesn't help with turning it off and I am usually reduced to taking the battery out. The phone is effectively useless although it is clearly NOT bricked. When I can turn it on it works fine.
I don't know if this is a hardware or software problem. If it's a software problem I don't know if the fault is in Lineage or TWRP or SuperSU. I noticed that the problem existed before I installed SuperSU. Has anyone else come across this problem? I'm reluctant to bin the phone because I spent such a long time getting Lineage on to it, but, if I can't turn it on or off it's not really a phone. Any help would be greatly appreciated.
@erich_vogt it's more a hardware problem, you can buy a new button (find link of online stores in accessories section or google.it).
for easyness you don't need to plug charge/usb everytime, you can set volume button waker, find in settings > button (don't remember where correctly, it will be somewhere there) then use volume switches to wake it.
erich_vogt said:
If the phone is off then pressing On/Off has no effect.
Click to expand...
Click to collapse
There have been power button bugs, but only in the OS. If it's not turning on from off, then I think the switch is broken! A common failure in old phones, which is why "volume button to wake" is important, to reduce load on the power button.
Thanks very much for offering to help.
I already had the option for the Volume control buttons to wake the phone turned on. It's here - Settings > Buttons > Volume Buttons > Wake up device. This worked for a while then stopped. I disassembled the phone to look at the On/Off button. I tried turning the phone on directly from the metal contact pad beneath the plastic button. This worked. When the phone had booted I checked to see if there was another nightly update for Lineage. There was the 3rd of Dec update. I downloaded and installed the nightly update using TWRP. It reported a successful install. The phone rebooted and never got past the Google boot-up screen. I waited for a few minutes and the took the battery out and tried turning on again from the metal contact pad. The phone booted but again got stuck (or seemed to) on the Google boot-up screen. I'm afraid that's it for me. This doesn't appear to be related to anything I have done or not done. The phone is just taking up too much time and it will have to go the the local recycler. Life is, as they say, too short. Thanks again for your suggestions.
erich_vogt said:
Thanks very much for offering to help.
I already had the option for the Volume control buttons to wake the phone turned on. It's here - Settings > Buttons > Volume Buttons > Wake up device. This worked for a while then stopped. I disassembled the phone to look at the On/Off button. I tried turning the phone on directly from the metal contact pad beneath the plastic button. This worked. When the phone had booted I checked to see if there was another nightly update for Lineage. There was the 3rd of Dec update. I downloaded and installed the nightly update using TWRP. It reported a successful install. The phone rebooted and never got past the Google boot-up screen. I waited for a few minutes and the took the battery out and tried turning on again from the metal contact pad. The phone booted but again got stuck (or seemed to) on the Google boot-up screen. I'm afraid that's it for me. This doesn't appear to be related to anything I have done or not done. The phone is just taking up too much time and it will have to go the the local recycler. Life is, as they say, too short. Thanks again for your suggestions.
Click to expand...
Click to collapse
3rd dec nightly has problem with booting, get back to older than it.
Reset volume button waker, if it stopped working. I never had problems with volume buttons.
I'd second the idea of it being software. I've had problems with all builds after 20171112. I get the impression there was something overlooked when the developers unified the builds for different GNex variants.
If you still have the phone, try that 20171112 build.
I don't know how to roll back to an earlier build. The phone will not boot. If I try VolumeDown+On/Off to try to get into TWRP Recovery mode nothing happens. The adb bridge option is turned on but if I connect the phone to my PC with a usb cable it does not appear in Device Manager as it used to. If I run ".\adb devices" it is not listed so clearly adb cannot find it. I don't know what else I can do.
erich_vogt said:
The phone will not boot. If I try VolumeDown+On/Off to try to get into TWRP Recovery mode nothing happens. The adb bridge option is turned on but if I connect the phone to my PC with a usb cable it does not appear in Device Manager as it used to. If I run ".\adb devices" it is not listed so clearly adb cannot find it. I don't know what else I can do.
Click to expand...
Click to collapse
Ah, ok. Sorry, I thought you could still do more than that, but it was rebooting and unusable in that sense.
That's well beyond any help I can offer you. I hope you got any data off it.