So around 2 weeks ago i dropped my phone and the screen broke.
brought it to the store to get the screen replaced but after that it gets stuck on the lineage os logo just looping.
What can i do to fix it, and is it possible to keep my data?
It's been a long time since i installed it so im not quite sure how to do it anymore.
Try to get into recovery and flash again Lineage OS.
If it's not working you can clean flash official ROM and install Lineage again.
For your data you will be able to access to it via TWRP and copy it to SD card
Related
I just installed the bump'd TWRP and CM12 on my G3. I'm trying to encrypt it, since I need it that way for my work email/calendar, but I'm running into a problem with it.
I charge the phone fully and plug it in as required, then go to Settings/Security/Encrypt Phone. I enter my PIN and start the process, but all it does is flash the green android on a black background with what looks like a gear in the middle of it, then goes straight to the Cyanogen boot splash screen, where it sticks until I pull the battery to restart it.
Has anyone else had this problem? Or, does anyone have an idea of what I might be able to try?
jtguf87 said:
I just installed the bump'd TWRP and CM12 on my G3. I'm trying to encrypt it, since I need it that way for my work email/calendar, but I'm running into a problem with it.
I charge the phone fully and plug it in as required, then go to Settings/Security/Encrypt Phone. I enter my PIN and start the process, but all it does is flash the green android on a black background with what looks like a gear in the middle of it, then goes straight to the Cyanogen boot splash screen, where it sticks until I pull the battery to restart it.
Has anyone else had this problem? Or, does anyone have an idea of what I might be able to try?
Click to expand...
Click to collapse
I am having the same problem. Unfortunately, I have not gotten any answer. Sorry I couldn't help, but at least we're not alone.
same here, have had same issue with multiple dailies. do you think this is with twrp or cm12?
I've managed, with the latest CM12.1, to encrypt my LG G3 (d855)....However...TWRP cannot decrypt the partitions so you cannot flash anymore updates until TWRP is updated....
Shakinghead said:
I've managed, with the latest CM12.1, to encrypt my LG G3 (d855)....However...TWRP cannot decrypt the partitions so you cannot flash anymore updates until TWRP is updated....
Click to expand...
Click to collapse
How did you do it? I've tried to encrypt with 27/08/2015 nightly and I couldn't. It said encryption failed and I had to wipe it.
I'm using the 26/08 (UK date format) build - This is the one that broke Chrome. I just encrypted the phone using the settings. I've been trying every couple of weeks for sometime. In the past I get the CM logo and nothing happens. If I remove the battery then the phone boots OK...so clearly the encryption hadn't started. This time I left it and walked away. 30 mins later I went back to the phone and it was prompting for the encryption password after boot....So all good for me....except TWRP cannot decrypt the encrypted partitions...
I am using the D855 model.
I'm having similar issues. I was able to encrypt after installing the Resurrection Remix v5.5.5 but now TWRP shows internal storage as 0mb and throws out a bunch of mount errors. So can't backup or load anything new through TWRP now.
The only way I was able to change ROMs was to flash the stock ROM through the LG flashtool, thereby unrooting the phone and then starting the whole process from scratch. It's a big pain because everytime I do that I need to get admin approval to setup my work email and then need to encrypt again , which locks me into the existing ROM again!
Ughh!! Can't wait for a solution top this problem.
Hi there, I have the above device with unlocked bootloader. It was rooted but I had a problem where the tablet kept rebooting but only after it loaded Android. No amount of following guides fixed it and Recovery and Fastboot were throwing g up problems whenever I tried to flash anything.
Eventually, I managed somehow to switch it on to Chinese update cycle I think and update the ROM with the latest official Chinese EMUI through multiple reboot loops (it downloaded about 10% of the update each time before crashing and getting the next chunk of download next time).
So I'm currently on the latest Chinese ROM running android 5.1.1 and it started working again. However the ROM came without gapps included so I flashed TWRP and installed gapps and I'm back to the reboot cycle. It lasted a long time before restarting again though so I'm guessing it's to do with gapps trying to update.
So I'm back to square one again. Any ideas? Is there any kind of log I can provide to help diagnose? I still have TWRP and have access to that without the bootloop starting again..
How did you rooted it?
Hi all,
I just updated two G Pad 8.3 tablets to the recent weekly update of Lineage 14.1-20180422-NIGHTLY-v500. Both devices are identical to each other in terms of apps and set-up. On one devices the update went flawless and on the other I am stuck on the boot-screen. I can boot into TWRP (3.2.1-0). Is the only way to solve this a factory reset?
I would like to backup before but TWRP tells me there is not enough space even though the SD card would have enough. Weird!
I had a bricked tablet after I installed supersu in twrp...
"secure booting error
cause : boot certification verify"
So the solution was to use LG MOBILE SUPPORT TOOL and upgrade recovery, it installed 4.4.2 but then I put root, twrp and put lineage. So if you go to twrp, why dont you just wipe everything except twrp and then install a new rom, gapps.
So two days before Android Oreo update released (RETEU channel). I tried to flash Magisk cause i needed root access but then i realized that the Bootloader was locked and i unlocked it. Everything was ok until i tried to flash a custom recovery (TWRP) but after that everything was way too complicated. I flashed TWRP but everytime i was trying to restart my phone and get there it was replaced with the stock recovery. I tried to find something online and i did here in XDA. Everything was working and i said that is time to flash Magisk, i rebooted my phone in recovery mode and after that i flashed Magisk, but after that my ROM was destroyed and i didnt even had a backup (yes i know i should have done that, but i totally forgot about it). I said ok, the phone was released almost a year ago and there should be a Stock or Custom ROM online, i did find a couple of them but everytime i tried to flash them i was getting an error, i found the problem, my TWRP was a 32bit version and i changed that to a 64bit, but no other ROM except Lineage 15.1 was working. After flashing Lineage Os I found out that my fingerprint sensor wasn't working, my flashlight too and the camera was awful. I went back online and tried to find a stock ROM but i couldn't find anything, i tried a stock 7.1.1 and stock 8.0 but none of them was working. The last thing that i did was trying to flash it with ADB and after that my phone was working for 10 min until i got a security update that after the installation my phone didnt even boot again, i cant boot it, it isnt showing anything, no vibration, no sound, nothing Please help!
I have the following problem:
A couple of months ago I installed the unofficial Version of lineage os 15.1 on my Galaxy Note s 10.1 LTE because I really wanted to have Android 8. But the S-pen applications werent working properly, so i decided to downgrade to lineage os 14.1. I downloaded the TWRP App, then the wrp.img.tar for my device and tried to flash it via the app, but the file was not flashable, because obviously it was a .tar. I wasnt really thinking about what I was doing so i Just renamed the file to twrp.img so the app would recognice it, which worked out. After I flashed fhe file, I tried to boot into Recovery. But instead of doing so, it booted to Download mode. So I decided to boot into Recovery via quick reboot, which didnt work either and it booted to dowbload mode again. I shut off the device and tried a normal boot, but nothing happend. The screen just stays black. I Hope anyone can help me with that, I really need my tablet.