Possibly Bricked? - LG Stylo 2 Plus Questions & Answers

I let a friend of mine borrowed my 2+ a couple weeks ago and he just returned it to me and it will not boot. It was running Lineage 15.1 when I gave it to him and when I try to boot it, it just sits at the boot animation screen but does nothing else. He wiped the memory card so I no longer have a back up to restore and when I try to use LG Bridge, it does not detect the phone and when I try to use LGUP, the phone just shuts itself off after 30 seconds. I've got the 64-bit version of TWRP installed but when I try to connect the phone to my pc to transfer a copy of the Lineage 15.1 zip to the internal memory, the pc says that the device has been disconnected even though I have not touched it and the screen is on. I can't even push the file to the internal memory nor sideload it using the adb sideload feature in TWRP. Is my phone f*cked or is there something I haven't tried that will get the phone back up and running. It's not my daily driver but I would like to get it back up and running if at all possible because it's my play around with phone that I was using to test out different things I've been cooking up.

Related

Is there a way to fix my hero?

After having to take a couple of flights, the phone's various features stopped working. For starters, it doesn't detect an sd card (I've tried a few, and then ones are detected on the computer), nor does it exit from airplane mode.
The phone started freezing whenever I tried to turn off the wifi, so first I tried to restore it from a nandroid backup. That ended up in a failure (it said to run the nand script by hand, but I didn't have my computer where I was), so I went and wiped everything.
Now, I'm left with a wiped ezhero rom, which doesn't exit airplane mode and doesn't detect an sd card. I can't adb to it, as adb doesn't find the device (it had no problem doing that before these problems started happening). Recovery mode starts, but it prints that there's no space left on the device, and since the sd card isn't detected, I can neither restore nor flash a different rom. Adb doesn't find the device when it is in a recovery mode. I have wifi and internet, but no market access (I'm getting connection errors in it).
Is there anything I can do to fix this? There's still a terminal program on the phone itself, and I do have a working 'su'.
UPDATE 1: I can go into the hboot screen, and fastboot at least works. Is it possible to flash the phone to the first original htc hero rom from there? (from ubuntu)

soft bricked vibrant

I have installed a nightly update for Cyanogen 7 and since then the phone is stuck on the Cyanogen logo.
I can get into recovery but since I don't have any firmware files on my SD I can't reinstall the ROM. I just need a way to put the files on my internal SD.
I have tries ADB which didn't detect my phone. I have installed the driver (The phone is found as the Nexus S for some reason) .
I also couldn't get into download mode although I don't have the hardware lock as I can get into recovery.
What can I do in this situation? I am already thinking of opening the phone, swapping out the internal SD and transferring the files through the computer. I would like to know if there's any other way.
Thank you!
romitkin said:
I have installed a nightly update for Cyanogen 7 and since then the phone is stuck on the Cyanogen logo.
I can get into recovery but since I don't have any firmware files on my SD I can't reinstall the ROM. I just need a way to put the files on my internal SD.
I have tries ADB which didn't detect my phone. I have installed the driver (The phone is found as the Nexus S for some reason) .
I also couldn't get into download mode although I don't have the hardware lock as I can get into recovery.
What can I do in this situation? I am already thinking of opening the phone, swapping out the internal SD and transferring the files through the computer. I would like to know if there's any other way.
Thank you!
Click to expand...
Click to collapse
Plug phone into computer and boot in recovery. If still not recognized by adb go to advanced and select reboot recovery. This should get you adb. ADB push "namehere".zip sdcard.
If still having problems Odin back to stock and start over. To get to download mode make sure phone is off, battery pull if necessary. Plug USB to phone press volume up and down and hold and plug USB into computer.
Sent from my GT-I9000 using XDA Premium App
Awesome! Thanks to you I have managed to get into download mode now.
All the guides that I found says I should use the power button. You said only up and down while connecting. That worked.
I am very grateful.

Can no longer connect to phone via laptop

Hi I have been running Android nand 2.2 for some time now and have been increasingly frustrated by the number of people complaining of a high pitched hiss when I call them , I have witnessed this and decided to investigate , my initial indications were that it may be a radio so I decided to do a complete rebuild and go from there.
My problems have a risen as I can no longer connect to the phone via PC , e.g. I was trying to use the Task29 exe to clean the phone and booted the phone into the 3 color band screen and it detected the USB connection , however when I run Task29 (or any rom for that matter ) they eventually come back after "Verifying phone contents screen" and say that the phone could not be detected
I have never had this before usually connects straight away , however I had not attempted to connect since my last rom build , I am bit vague about the details but seem to remember using the clockwork method to deploy it
So I am wondering if somehow I have messed something up or is it simply a drivers issue and if so how would I replace them?
uninstall the drivers and reinstall them
Thx, I got the same result by trying it on a laptop that hadn't seen the phone before , it all worked then, just for ref if I uninstall the drivers won't it simply reinstall the same ones or do I have to delete something on the laptop itself , or is it likely to be a corrupt driver and reinstalling cures?
sometimes it happens, ihad it happen the other day, i had to remove the device from device manager and let it reinstall the drivers for it to be picked up for flashing again
Make sure you have windows mobile device center installed. It has the necessary drivers for detecting a phone in bootloader(tri-color) mode and also when you are flashing Mag or CWM partitions

Please help! I seem to have bricked my G2

So yesterday I installed TWRP alongside CM13.
After that I got some problems with the ROM (rebooting, slow charging) so I decided to return to stock. To flash the stock .kdz I needed to go into download mode, that however did not work my phone just booted normally into CM when I tried to use the method to get into download mode (vol+ & USB). I even tried to force download mode through adb on PC however that also only rebooted the phone.
Then I did a wipe in TWRP (everything except Internal Storage) and shut off the phone.
Now I have the problem that I can not boot (because I obviously have no ROM installed anymore) but I also can't get into recovery anymore.
Also my phone seems to be in "only charge" mode from CM so my PC does not even recognize it correctly. I can't even see it in device manager and neither adb, nor the flash tool nor anything recognizes it.
When I connect my phone to the PC it just shows the CM battery icon that you see when you charge your phone while it's turned off and the LED is glowing yellow.
All of this are things that were new with CM so I guess there is still something left from CM that does prevent my G2 from acting as MTP.
Please tell me there is still hope...

Wiped H1511 - can't transfer files anymore

Hi, looking for some 2nd thoughts on this before I throw this phone away. I got this Nexus 6P a year ago and put purenexus into it along with TWRP, everything was going great. Had an issue with a car charger, the charger port heated up badly and I couldn't charge it. After messing around with it I finally got it to charge but not rapidly (no big deal). Now I tried to upgrade the purenexus version and had some booting issues. So I tried to mess around with the versions and in the process I accidentally wiped the data on the phone. Now the charger port charges but I cannot connect to the PC (as in nothing detected in device manager, no sound of plugnplay or anything). I cannot boot to transfer files with the wifi because there is nothing to boot to. 6P has not ext SD port so I cant put files in. TWRP has also a sideload on the install version but ADB doesnt see the device in any state (obviously if the pc doesnt see it). Finally, I figure I just had to change the charger port so I ordered a new port, put it in and same thing. Phone charges but not detected by any PC. I don't think there's another way to put a rom image on the internal SD but if there is I am all ears.
rbigras said:
Hi, looking for some 2nd thoughts on this before I throw this phone away. I got this Nexus 6P a year ago and put purenexus into it along with TWRP, everything was going great. Had an issue with a car charger, the charger port heated up badly and I couldn't charge it. After messing around with it I finally got it to charge but not rapidly (no big deal). Now I tried to upgrade the purenexus version and had some booting issues. So I tried to mess around with the versions and in the process I accidentally wiped the data on the phone. Now the charger port charges but I cannot connect to the PC (as in nothing detected in device manager, no sound of plugnplay or anything). I cannot boot to transfer files with the wifi because there is nothing to boot to. 6P has not ext SD port so I cant put files in. TWRP has also a sideload on the install version but ADB doesnt see the device in any state (obviously if the pc doesnt see it). Finally, I figure I just had to change the charger port so I ordered a new port, put it in and same thing. Phone charges but not detected by any PC. I don't think there's another way to put a rom image on the internal SD but if there is I am all ears.
Click to expand...
Click to collapse
Hi... Seems like you already tried all the available options. How about bootloader? Is the phone detected? Try to reboot in bootloader and issue: fastboot devices
If your phone is recognized, you can try installing a factory image.
Just in case, download last adb/fastboot version from Google directly:
https://dl.google.com/android/repository/platform-tools-latest-windows.zip

Categories

Resources