Problem with Cyanogenmod Update - G2 Q&A, Help & Troubleshooting

Well, hi all.
I have been a CyanogenMod user for a while now, and I had CM 12.1 running without any problem in my LG G2 (D802). Today, the notification popped up telling me that I had a software update, which was CM 13.0, so I tapped in download and then install. The phone itself started TWRP and began instalation. When it ended I tapped reboot, and it is not working anymore. I have tried a lot of times to power it on and as soon as the LG logo pops up, it dissappears and the screen goes totally black. I am able to get to do factory reset by pressing Power and - volume, and it leads me to TWRP menu again. I tried to connect the phone to the computer and try to place inside my old CM12.1 so I can install it from the TRWP, but my computer does not recognize my phone and tells me I should format that unit in order to use it again.
I have looked around the forum and the rest of the internet and I just can't find anything, so I'm just starting to get desperate. Any ideas?
Thanks to all

Get an OTG cable and put a rom into a flash drive. Flash it with TWRP.
Don't forget to format the drive as fat32 and mount it in TWRP.
I do this whenever i'm stuck with these kind of situations.
Something similar to this also happened to me. TWRP said "corrupted zip" and did not install cm13.

Related

Emergency help; Stuck at LG logo

Solved!
Please buy hyelton a beer or a damn new phone. He's a hero.
This worked: http://forum.xda-developers.com/showthread.php?t=2432476&highlight=decrypt
Hey guys, but of an emergency here...
I'm stuck at the LG logo after flashing the Pacman ROM with the latest unofficial CWM, and it seems to have failed at Formatting system. All four touch buttons on the bottom were blue, as if they had been pressed and highlighted. No response from anything.
Reboot. Then it got stuck on the LG logo. I can't access CWM anymore, holding power + vol down does nothing, I just go back to the logo. I'm running a D802.
This was a pretty standard flash for me, I have done this many times, so I was confident in it, but now have no way back into a phone I desperately need within hours.
Process went as follows;
Full wipe, format, initialize install, it failed/crashed/whatever, rebooted, now stuck on logo, unable to access CWM, and obviously unable to access ROM.
USB Debugging was on, but as the ROM doesn't exist anymore, not sure how much help that'll be.
I'll gladly go back to either CWM or TWRP, as well as stock ROM or whatever. I can sort all that out later, right now just need things back in running order.
Edit1: I can't even turn it off. It simply boots up again, so now also worried of damaging display or battery.
Edit2: It's not showing after entering "adb devices". List is empty.
ANY help appreciated.
I'm running Windows 8, and no, I will not be able to reinstall to W7 or Ubuntu.
Thank you

[Q] Lg G2 Problems! Help!

So I recently bought a Verzion version of the LG G2 from some guy and it was working fine. After I had it activated Verizon was downloading a Software or System update and after it installed, my phone never booted up to the main screen. Turns out the phone was rooted and had flashed ROMs and what not. I don't really know what it exactly means but I'm starting to understand more and more the more I try to fix it. As of now the only thing my phone does is boot up to the Team Win Recovery Project v2.8.1.9. Not knowing what I was doing, I wiped everything from the phone so the only thing on the SD is the TWRP file. When I go to the reboot option > Power Off I get sent into the screen "Swipe to power off" Above the swipe It says no OS installed. Once I swipe I get put into another Swipe screen but this time it's swipe to install. "Your device does not appear to be rooted. Install SuperSU now?" When I swipe to install, the phone's CMD shows for about a second then it reboots. Note* When I go to the factory reset screen(Holding Vol down and power button) The top left of the screen says rooted. Again nothing besides TWRP files are on the SD card.
What I have downloaded:
LG G2 driver
KitKat_Baseband_VS980
ABD and Android Studio with SDK manager
I was searching on all sorts of forums and they're saying CloudyG3_2.1 is a good way to get the phone working again so I have it downloaded as well.
Also just downloaded ioroot
I tried sideloading it but couldn't really understand how it worked. I couldn't get the files into my phone. ROMs don't really matter as of now because I can't even use my phone, I'm really just trying to get my phone to factory settings as if it was never Flashed/Hacked. If i do manage to recieve help and fix my phone I wouldn't mind added the cool stuff but as of now I just want my phone back.
Please Help!!

[solved] Note 3 bricked for good? No ADB interface to reflash manually.

Hi everybody.
TL;DR
Recovery hangs upon booting and fastboot mode doesn't show up ADB interface on my PC. How to flash the phone?
Long version:
I wonder if you can help me. My old faithful Note 3 is badly misbehaving. Yesterday I filled almost all its internal memory with some movies before heading out on a trip, but some time later when I reset the phone after unusually long boot all user settings were lost. Well, something went wrong, couple of hours later there was reset after reset so I wanted to restore previous backup... but couldn't. TWRP was showing error messages (TAR something something, 255) very shortly into restoring process. It couldn't restore backup but also couldn't make new one as well (similar error with TAR and code 255 when trying to backup user data).
Something was very wrong, so I thought maybe I will flash newer TWRP 3.0 and give it a try but suddenly after next reset I couldn't even get into recovery anymore - TWRP gives me black screen after several seconds into booting it. No icons, no reaction to key presses, nothing. Even holding power button does nothing.
Ooooookay, it's time to enter fastboot mode then and flash new recovery manually. So I enter it, connect phone to my laptop and... nothing! No ADB interface. Some kind of samsung driver is installing, but the most important one, for ADB, just doesn't show up. It's really weird. Reinstalling drivers doesn't help, only the same one device that shows up gets different names, but that's it - no ADB interface, and, effectively, I can't flash anything because fastbot and ADB can't see any device. Odin can't see the phone too.
What's going on? Is the internal flash dying or what? But if so what does it have to do with ADB not showing up? Do you have any ideas that I can try out in this situation? I checked my laptop with a tablet that I have on hand and it shows up its ADB interface without problem in fastboot mode even though it's the first time I connect it to this laptop, so laptop and it's system are fine.
If nothing helps then, well, One+ 3, here I come.
EDIT: Problem solved. Turns out f2fs on data partition crashed and therefore TWRP couldn't start at all. I managed to flash Philz CWM via Odin somehow (after messing with drivers for some more time) which told me there is something wrong with /data because it couldn't mount it at all. It couldn't format it either. Fortunately SlimLP managed to start and after throwing up some errors I managed to do factory reset which formatted the internal memory back to ext4. Then flashing TWRP, formatting data back to f2fs, restoring backup and voila! It works again. Good, I'll wait until Note 8 if there ever will be one.

Help Exposed Installation gone wrong

Hey, so I have had my phone rooted for a long time. I have a Galaxy S5 6.0.1 Marshmallow.
I decided I wanted to get Framework installed so I downloaded the right files and flashed it in TWRP.
My phone took way longer than 10 min to reboot into system so I thought I was stuck in a bootloop and decided to run my phone through TWRP again.
I tried rebooting but that didn't work. I have my phone's backup saved onto a micro SD so I did a factory reset and then tried rebooting.
I got past the rebooting logo and actually got to my lock screen where it asks for my password.
From there, I've been getting spammed with 3 different messages, one saying that IMS service is down, com.sec.vsimservice is down, and WfcService is down.
After I press ok to all 3 of the messages, my phone is still in the lock screen asking for my password but the phone doesn't recognize that im touching the screen to type. After letting the phone stay like that for a few minutes, the lock screen that asks for my password goes away and all I can see is my wallpaper background (no notification panel either) but now the phone recognizes me touching the screen ( I know that because the LED lights up for the windows button and back button )
So basically I decided to go into TWRP and flash my recovery that I had saved on the microSD.
After that didn't work, I've just been going through a series of factory resetting my phone and wiping Dalvik files and then flashing my recovery. My phone is getting unrealistically hot too.
Btw I never downloaded the Exposed Uninstaller from the forum so I tried downloading it onto my pc and then sending the file over to my phone through download mode using Odin so that I could flash the uninstaller through my TWRP but that didn't work because the PDA in Odin does not recognize the uninstaller file.
Please, I really need help and thanks to anyone who tries, it would mean a lot if someone could figure out what I can do. Thanks.
Since you've tried restoring your backup and everything seems to have failed (it sucks, I know) you should try to install a completely stock firmware which you can download from here: http://live.samsung-updates.com/index.php?device=SM-G900I Just make sure you select your exact phone model from the dropdown menu at the top right side as you didn't mentioned which of the 40 S5s you have lol. And after you flash stock firmware and successfully boot up try to restore your backup. If it's still bugged - flash stock again and start off fresh. Let me know how it turns out. I'll help with installing xposed later as well, first let's get your phone running again

Hard Brick P10 Lite - need help

Hello everyone, just wanted to say a quick thanks, after successfully rooting and installing custom roms on two phones thanks to the information on these forums, third time turns out to be a charm and I managed to hard brick my new P10 lite.
The situation right now:
no charge light, no combination of buttons will do anything, phone is dead and will not boot or vibrate.
my computer will recognize that a phone is connected, for example Hisuite will pop up when i connect the phone, and in device manager, it shows Lemobile android device and the submenu says Android bootloader interface.
how i got here:
i was trying to install lineage 14.1 from this haky86
https://forum.xda-developers.com/p8...m-lineageos-14-1-huawei-p8-lite-2017-t3649292
but before i did that, i used this guide to install twrp and supersu:
https://forum.xda-developers.com/p10/how-to/twrp-how-to-root-p10-lite-t3617418
everything went fine, on the stock operating system i had root and system was running.
when i installed lineage, i lost root and couldnt figure out how to get it back. so i used this guide to restore the stock system and was going to try again from the beginning.
https://forum.xda-developers.com/p10-lite/help/original-service-rom-huawei-p10-lite-t3688097
however, when i tried to reinstall lineage for the second, third and fourth time, i kept getting stuck in a bootloop with the lineage animation. it seemed to me that i needed to flash the vendor image, and i found a guide on xda how to do it, but it wouldnt let me flash to the vendor partition. (sorry, i dont recall the exact error and i cant get there anymore :/)
so in massive frustration and desperation, i tried to use this method:
https://forum.xda-developers.com/p8...uide-unbrick-huawei-p8-lite-2017-pra-t3713574
which i know is for a p8 and i never should have tried to install it, but it went through the whole download process and at about 50-60% on the recovery the phone went black and never turned on again.
i have read that perhaps disconnecting the battery for a few minutes might help? or is this something that dc unlocker can help with?
any advice would be greatly appreciated. if more information is needed, please let me know.
Hi,
Have you tried completely turning off your phone (pressing on/off button for roughly 20 seconds) and then booting into recovery (pressing Volume Up and Power key simultaneously for rouhgly 10 seconds)?
Best,
Kenny
Thanks for the reply, but as I said, no button combinations elicit any response. The only sign that the phone is not completely dead is that it will be recognized by my computer as an android phone, but adb (for example) says no device is connected.
lineage gives you bootloop due to wrong data partition format
bricked my p10 lite several times same ending
only way that always gets the phone back to life is flashing lineage, i took haazan's one
BUT BEFORE flashing the lineage 14.1 zip check partition format is ext4
when back on lineage and stock ROM is wanted boot into twrp and re change format to f2ts or how it is named and flash the stock zip
unbricked
edit:
saw your second post too late
if the phone does not response on any button(s) maybe adb sideload command for change partition format and then sideloading the lineage zip is a way?
I have a similar problem, I have a custom rom (Elemental) but I flash another custom rom, it was normal, in the reboot it not turn on, only is in fastboot mode, i flash original system, cust, boot, and another but it is the same, help me please

Categories

Resources