Hi Everyone,
Since LG was shutting down their developper tools on the 31st of December, I decided it was time for me to finally install Lineage OS. Unfortunately there occured some problems however. I was hoping some of you could help me troubleshooting and possibly fixing it!
The version I wanted to install is the following version, LineageOS 18: https://www.cyanogenmods.org/lg-v30-lineageos-18/
The guide refers to the following guide to install TWRP, this was done succesfully: https://www.cyanogenmods.org/forums/topic/how-to-install-twrp-and-root-lg-v30/ . I did however lose my phone's data, but I've accepted that already.
I then proceeded to following step, the flashing LineageOS step, in the guide: https://www.cyanogenmods.org/forums/topic/flash-install-custom-rom-twrp-recovery/
In this step a problem occured. It stated that the drive I tried to flash to was encrypted. I could flash LineageOS however I could not boot into it. I needed a password to unencrypt the data. I did not have this password (it was not my phones PIN, SIM PIN or Google account). I wanted to try the flashing process again but format the drive first (since I lost my data anyway, I didn't really care). After formatting the system needed a reboot.
The reboot however is stuck. It always goes instantly to the 1st time boot of Lineage OS (while I haven't reflashed yet). It just gets stuck there (I left it on overnight, still no signs of progress). I tried force rebooting using the powerkey+volumedown, that still works, but I can't turn it completely off. Some googling shows that people suggest reflashing the Lineage OS, but that clearly doesn't work because I can't get into TWRP.
I am currently trying to let Lineage OS drain the battery completely and then upon fresh start up try to boot into the TWRP menu and refresh.
The model I have is the LG V30 H930 (no T-Mobile variants or whatsoever).
Some questions that I have:
1. Did I screw up my phone?
2. If 1. is "No not yet", what are some possible solutions?
Kind regards,
Hidde
Related
Hi!
I got some major problems with my G3. I was on stock Android 6 (rooted). Worked fine for some months. Then I decided to encrypt the phone and activated this option in the normal android settings. After some time the phone restarted and I got the "Encryption unsucccessful" page and cannot do anything anymore.
After reading through the help forums I tried the following steps to solve it:
- factory reset
- wipe eveything in twrp and flashed system, boot, modem manually to Android 6 again
- repaired all filesystem partitions in twrp
- many many more factory resets
All didn't help. The only thing that changed is that when coming to the "Encryption unsucccessful" page now the phone hangs up after the next option I choose (shut down or restart or factory reset) so I have to take out the battery to restart or shut down.
Any suggestions how to solve it and maybe also any suggestions what might have gone wrong? Don't want to kill the next phone the same way by just enabling encryption!?
I haven't tried full device encryption before, so I thought I'd give it a try with my old i9100. It was running twrp-3.1, Lineage 14.1 (specifically the OctOS flavour) and had OpenGapps and Lineage Root installed. I proceeded to set up a pin, enable full device encryption, it rebooted and I began to wait. Several hours later it was still spinning with the boot animation. One post online suggested a rooted phone could give it issues. No worries, there was nothing of value on there anyway. Rebooted back to twrp, reinstalled the OS, OpenGapps, factory reset, let it reboot and I was back to the launcher. Set a pin, tried to click on the "Encrypt Phone" entry in settings and nothing happens. The encrypt phone window just won't come up. From there I proceeded to try several things. Various combinations of pins and passwords in different lengths. Reinstalled the OS a few more times with and without OpenGapps. Downgraded to Lineage 13. Nothing. Never again have I got the encrypt phone window to come up.
Is there some sort of prereq that I'm missing that I haphazardly had on my first install that I haven't repeated?
Thanks
Same problem here, well, not really, mine reboot and nothing happens except that i don't have network anymore, i have to reboot the phone again to have network operational.
But the phone isn't encrypted, tried everything without success.
I can see post on forum from the beginning of the year with this issue, too bad for us, encryption is a really important feature for a lot of users.
So, to begin with, yesterday Mi A1 got the Android 9 update. As I always do, I went to uptade it with Magisk (it worked with 8.0 to 8.1 and with every security patch, so I, as a newbie, thought, "why the h3ll not?"). Obviously, it didn't work and I got into a boot loop. So, here are the [lot] of things I have tried to do.
-Downloaded MiFlash and the latest OS version from Xiaomi site (8.1 witch november patch). Tried flashing a lot of times, I always get the boot loop after installing it. Wiped all data with TWRP and still didn't work. Always the same problem. Tried with different versions as well.
-Downloaded latest AOSP ROM for the device, flashed it, wiped cache and data, instaled TWRP (3.2.3-0), but the system never initiates. Doesn't even restart (20 minutes after my last try and it still is in a black screen).
-I've tried the same thing with Lineage 15.1 as well. Checked with MD5 in both roms. Doesn't work at all. Followed every tutorial I could, step by step, don't know what I'm doing wrong.
Can any one please help me? I don't know what to do anymore.
EDIT 1: So, I thought nothing happened, but after installing AOSP, I rebootet the phone holding the power buton, and during boot, I can see the "Powered by Android" from the custom ROM for a few seconds, but then the screed turns black and nothing more happens.
I am facing strange problem on my Redmi Note 4. Custom Roms are getting stuck after language selection screen on first boot. I had been using Resurrection Remix (Official) – Pie Rom on this phone earlier. Due to some reasons, I had to flash the stock MIUI rom. Thereafter, I flashed the latest TWRP 3.3.1 in fastboot mode and installed the latest build of Resurrection Remix (Official) – Pie (7 July 2019) via TWRP. The Rom installed successfully without facing any encryption problem because I had formatted my data partition prior to flashing Rom.
After flashing Rom, the System boots and Set Up Wizard initiates with the screen giving me option to select language. After I select language and press next…the phone goes to next screen ‘Just a Sec…’ and thereafter remains there forever. The screen blinks after some time and goes blank, then it comes back to ‘Just a Sec…’. It simply doesn’t let me go beyond that.
I tried two more builds of Resurrection Remix – Pie, but again the same story.
I tried to flash Pixel Experience (Official) – Pie, but the same story.
I believe, Set Up Wizard is stuck with some thing and doesn’t let me through. The Resurrection Remix (Official) – Pie (20 January 2019) build came to my rescue as this rom doesn’t initiate Set Up Wizard at first boot and simply goes to desktop. Thereafter, Set Up can be completed any time and doesn’t create any problem.
As 20 January 2019 build works fine, I tried to dirty flash the latest build over it with the hope that Set Up Wizard won’t come up. The dirty flash goes without error and phone boots to system. But this time, phone gets stuck while trying to get to desktop screen and message keeps showing forever on the screen ‘Phone is Starting’. I can see the desktop image in the background. The screen goes blank in between and then message keeps showing again. It simply doesn’t let me pass through. In this scenario, I can access the pulldown and go to settings. I did check, phone wasn’t encrypted because I had not used any pin, fingerprint etc. on the working rom prior to dirty flash of latest build.
Can anyone help me as I simply cannot install any Custom Rom due to this problem. I have been left with only two options, either to stick with 20 January 2019 build of Resurrection Remix, which doesn’t initiate Set Up Wizard at first boot or to bloatware loaded MIUI stock rom.
What I tried :
1. Tried to rename the SetupWizard.apk file to SetupWizard.apk.bak in TWRP to evade first time Set Up Wizard but in this case, screen doesn’t show any thing and goes blank at the time just before going to desktop. It didn’t work.
2. I tried TWRP backup of another Redmi Note 4 having latest build and restored backup of four partitions of that phone (vendor, boot, system and data) on my trouble creating phone. The system booted but it also got stuck at ‘Phone is Starting’ Screen while showing me desktop in the background. I could enter the settings through quick pulldown in this scenario.
Please help me resolve this problem.
I have obtained catlog files through adb while my phone was booting after dirty flashing latest RR build (August 2019). Please note that I can't go beyond Just a Second screen, in case I go for clean flash after data format. Therefore, I flashed RR January build first, which works without any problem. Then settled my phone and thereafter updated it with latest RR (August 2019) build by dirty flashing. Phone accepted my pin on startup screen and then went ahead with showing 'Phone is Starting'. The phone never passed through that screen.
I have obtained two files, one with Error option and other is complete log. Please help me understand the problem, so that I may update my phone with latest RR build, else I may remain stuck with January build only.
https://drive.google.com/open?id=1zVXYxdQ5epImYTOiXSs1tIFB8uTwNV2p (Complete Log File)
https://drive.google.com/open?id=1YYXbdq7csCwskCtgtn2uWYG4rXWng4em (Log File with Error Tag only)
I kept trying Rom after Rom and finally, the AOSiP Official Rom is working great on my phone. Every thing went smooth with this Rom.
Moderator, please close this thread.
Thread closed at Op's Request.
Thanks
SacredDeviL666.
I have used the search function, but to no avail. Also, sorry for no log files – cant access them (see below).
I used a work around „Error 7 – Assert failed“ while trying to flash Lineage OS (lineage-16.0-20200104-nightly-kiwi-signed.zip) for my honor 5x (this work around: https://forum.xda-developers.com/showthread.php?t=2522762). I was positive that the .zip i used was for my specific phone and that the twrp was the current one. Even after updating to most recent twrp, the error 7 persisted (I did perform the corrext wipes of storage). After „forcing“ the phone to install the .zip anyway (overriding the assert check with the workaround) , my phone is now bootlooped, or worse (stupid me, i guess). During the first restart after flashing, things seemed fine for a few seconds, the lineage logo started to appear for a short while, but disappeared and now only the honor logo appears. It mostly bootloops. I can still access fastboot mode and, with a little luck, also recovery, but touch screen isnt working. Some fastboot commands work, but some do not seem to work, although i am not very experienced with fastboot and cant tell for sure. I have a nandroid backup available.
My questions: How to save the phone? I would be happy to return to stock for now, just to sort things out from there. I couldnt execute most guides to return to stock, since i have no access to twrp (touchscreen no longer reactive). I‘m happy for all ideas.
My firmware KIW-L21C432B160