Running basic rom, "LG V10 H901-10c Debranded, Debloated, Deodexed ROM - Clean & Stable"
TWRP 2.8.1, unlocked bootloader, all working well for a while now.
Booted into TWRP to do a backup before I loaded TWRP 3.0.0. Backup successful.
Tried to reboot the phone. I get the LG 'bootloader unlocked' screen. Then I get the LG startup screen but everything hangs there. Phone will not boot into rom.
I only did TWRP backup...nothing else...what could be the problem?? How can I get back to normal.
Thanks!
Have you tried clearing dalvik cache? That happened to me before and simple clearing resolved my issue
Thanks! Just tried that, no joy!
Are you sure you didn't touch the "Fix Contexts" button in TWRP? That will break the ROM.
Just boot into TWRP and flash my ROM again, it should go back to normal.
That did it!! Thanks siraltus!!
Ok... So...
I installed fulmics through TWRP and all worked great
After that, I installed a v30 Rom also with TWRP and that worked great, too, but i decided i like fulmics more and wanted to go back
Retried TWRP and kinda worked, but some errors were popping up all the time, so i decide to reinstall it
Now here i am. When it boots, goes straight in TWRP. I tried a stock zip to flash with TWRP, no luck.
When in TWRP I can see the phone on pc, internal storage in empty.
Fastboot works.
When i load up LGUP, under the version tab, it shows fulmics mod and i can't take any action
How fried is it?
Roti23 said:
Ok... So...
I installed fulmics through TWRP and all worked great
After that, I installed a v30 Rom also with TWRP and that worked great, too, but i decided i like fulmics more and wanted to go back
Retried TWRP and kinda worked, but some errors were popping up all the time, so i decide to reinstall it
Now here i am. When it boots, goes straight in TWRP. I tried a stock zip to flash with TWRP, no luck.
When in TWRP I can see the phone on pc, internal storage in empty.
Fastboot works.
When i load up LGUP, under the version tab, it shows fulmics mod and i can't take any action
How fried is it?
Click to expand...
Click to collapse
Try doing a complete wipe, wipe cache, Dalvik, data, system. Then wipe internal storage via the format data option and reboot recovery. I am guessing that you're on the h850 variant so Flash the 20s complete firmware zip then flash SuperSU or magisk. See if it boots into system.
I do still suggest hooking it up to your PC and flashing stock firmware kdz 20s using uppercut. If if it is recognizing fastboot commands then you should have no issue flashing a new recovery image after you load the stock kdz, you may even be able to flash a new recovery image instead of going through all the other steps that I listed. Which may some your issue. But it's best to format data entirely before flashing anymore ROMs, and use lgup via uppercut to flash stock firmware and let it boot entirely before reflashing fulmics.
But formatting data is key to reset the system folders which were leftover from other ROMs and likely the cause of the issues you experienced.
Hey guys. I've got a us998 with unlocked bootloader and twrp 3.2.1. I recently upgraded to 8.0 using kdz file from ChazzMatt's us998 kdz thread. I got the upgrade done, and booted into system. When I booted into twrp, it told me that data was encrytpted and I probably needed to do a format data which I did. After setting up the phone, I realized that twrp was still giving me the same issue. I tried flashing the no-verity and lg-rctd-disabler, but to no avail. I have tried factory data resetting the phone and it boots back into twrp. When I boot into system it boots to my current system. I tried reflashing twrp and got the same issue with encryption. Is there anything I can do at this point, or am I stuck with an unusable recovery.
I tried reflashing the 8.0 kdz using uppercut like before and it wouldn't have any of that.
Thanks ahead for any help offered.
Does anyone know if I can flash the nougat kdz, and then go back to Oreo? Can we do this on unlocked bootloader?
Ballroomblitz said:
Hey guys. I've got a us998 with unlocked bootloader and twrp 3.2.1. I recently upgraded to 8.0 using kdz file from ChazzMatt's us998 kdz thread. I got the upgrade done, and booted into system. When I booted into twrp, it told me that data was encrytpted and I probably needed to do a format data which I did. After setting up the phone, I realized that twrp was still giving me the same issue. I tried flashing the no-verity and lg-rctd-disabler, but to no avail. I have tried factory data resetting the phone and it boots back into twrp. When I boot into system it boots to my current system. I tried reflashing twrp and got the same issue with encryption. Is there anything I can do at this point, or am I stuck with an unusable recovery.
I tried reflashing the 8.0 kdz using uppercut like before and it wouldn't have any of that.
Thanks ahead for any help offered.
Does anyone know if I can flash the nougat kdz, and then go back to Oreo? Can we do this on unlocked bootloader?
Click to expand...
Click to collapse
Please disregard this thread.
Mod can delete.
Typical disclaimer, etc etc.
You nuke your phone, I'm not paying for it
Thanks to @zefie for converting the kdz to a zip.
The zip
The anti-root removal
I flashed the zip in TWRP, rebooted to the OS, and was unrooted.
Reboot into the bootloader, and flashed TWRP.
Rebooted into recovery, flashed the lucye anti root removal, then rebooted into recovery again, and flashed Magisk.
Phone has been fine since Thursday.
Did you flash this dirty or clean?
I flashed it. Works GREAT. Dirty flashed.
Here's what I did...
-Flashed this zip
-Flashed Eliminator74 twrp image https://forum.xda-developers.com/lg-g6/development/twrp-t3828254 (you'll need to change from .zip to .img in TWRP)
-Rebooted to recovery
-Flashed antiroot removal zip
-rebooted to recovery
-Flashed magisk
-rebooted to system
-be patient
Can you please post a link to eliminator74 twrp build? I'm not sure if I have that one...
Link to his thread
jjohn7293 said:
Can you please post a link to eliminator74 twrp build? I'm not sure if I have that one...
Click to expand...
Click to collapse
Here's a link to his thread https://forum.xda-developers.com/lg-g6/development/twrp-t3828254
monark88 said:
I flashed it. Works GREAT. Dirty flashed.
Here's what I did...
-Flashed this zip
-Flashed Eliminator74 twrp image https://forum.xda-developers.com/lg-g6/development/twrp-t3828254 (you'll need to change from .zip to .img in TWRP)
-Rebooted to recovery
-Flashed antiroot removal zip
-rebooted to recovery
-Flashed magisk
-rebooted to system
-be patient
Click to expand...
Click to collapse
Dirty from 21B worked fine for me
Dirty flash from 20A worked perfectly.
FYI: This ROM has the recovery image removed, so if you already have TWRP, flashing this won't remove TWRP. No need to reinstall TWRP.
I actually started having bad idle drain. Flashed LOS for now, will go back to stock soon. If anyone else notices idle drain, please do let us know.
Thank you!
Only wiped caches
Dirty flashed over 20A
Reboot to recovery
Flashed anti root removal tool
Reboot to recovery
Flashed Magisk 17.3
Wiped caches again
Reboot to system
Showed Android is updating screen
All is well so far!
Still running 17A [rooted]... think dirty flashing this will be alright? Been looking for a good time to update.
Coming from 20A, battery life has been about the same- maybe even a bit better. All's well.
MetalMan2 said:
Still running 17A [rooted]... think dirty flashing this will be alright? Been looking for a good time to update.
Click to expand...
Click to collapse
Go for it. Be sure to install Magisk for root. SuperSU (if you happen to be using it) doesn't work anymore.
gl;hf
BeardKing said:
Coming from 20A, battery life has been about the same- maybe even a bit better. All's well.
Go for it. Be sure to install Magisk for root. SuperSU (if you happen to be using it) doesn't work anymore.
gl;hf
Click to expand...
Click to collapse
Thanks for instilling confidence. It all seems to have worked out just fine. :good:
Time will tell how battery life and what-not compares to 17A.
MetalMan2 said:
Thanks for instilling confidence. It all seems to have worked out just fine. :good:
Time will tell how battery life and what-not compares to 17A.
Click to expand...
Click to collapse
Good to hear. :good:
US997 14a to 21c (Keeping Root)
I'm using the US997 still on 14a (rooted, TWRP installed) would I need to (CLEAN) flash up to 17a and then the 21c? After that flash the anti-root and flash an updated version of Magisk? (currently stuck on v16.4) Can't find my stock boot image to update. Only got the phone back in October and stopped all updates before I unlocked the bootloaded, installed TWRP and used Magisk to get root. I had a hard time finding a version of TWRP with a kernel that worked for my phone (Melina v3.2.1-0) would I have to update that also? Was waiting to see the highest update I could get without losing root. Anyone done this? Any help would be greatly appreciated.
My wife and I both have G6 phones. On mine, I dirty flashed this over 20A with absolutely no problem. My sequence was: flash Eliminator74 TWRP, reboot to recovery, flash 21C zip, reboot to recovery, flash lucye anti-root, reboot to recovery, flash Magisk, wipe cache and Dalvik, reboot to system. I'm guessing I really didn't need those extra reboots but it felt safer. Phone is perfectly stable.
On my wife's phone it was another matter. Her data partition was encrypted, due to the phone having been reimaged by LG during warranty repair. I'd rooted it but never decrypted it. None of the default ways to decrypt it worked, so I was forced to format /data. I thought that would do it, but the resulting installation was unstable, and wouldn't get through setup successfully without continually looping, freezing, and returning to start. Finally I realized it was probably flashing over the LG factory image that caused the problem. I wiped /system and started over, and had much better results.
LPMatt said:
Thank you!
Only wiped caches
Dirty flashed over 20A
Reboot to recovery
Flashed anti root removal tool
Reboot to recovery
Flashed Magisk 17.3
Wiped caches again
Reboot to system
Showed Android is updating screen
All is well so far!
Click to expand...
Click to collapse
MetalMan2 said:
Thanks for instilling confidence. It all seems to have worked out just fine. :good:
Time will tell how battery life and what-not compares to 17A.
Click to expand...
Click to collapse
So I tried this coming from 17A.
When I reboot to recovery on the first go I have the Oreo bootloader screen and it goes into the white reset menu. All encryption is enabled again.
I have to fastboot bootloader, install TWRP recovery, wipe/format and then restore my 17A to recover the phone.
What steps did you take MetalMan2?
Malezar said:
So I tried this coming from 17A.
When I reboot to recovery on the first go I have the Oreo bootloader screen and it goes into the white reset menu. All encryption is enabled again.
I have to fastboot bootloader, install TWRP recovery, wipe/format and then restore my 17A to recover the phone.
What steps did you take MetalMan2?
Click to expand...
Click to collapse
This probably won't help, but are you using this version of TWRP?
BeardKing said:
This probably won't help, but are you using this version of TWRP?
Click to expand...
Click to collapse
Yep. Just downgraded the bootloader back to 17a through it.
Malezar said:
What steps did you take MetalMan2?
Click to expand...
Click to collapse
I exactly followed LPMatt's list which you quoted.
Still no problems. Pretty sure the battery life is less than 17A, but I think we all know that and for me it's "good enough".
How to remove root checker?
Hi all,
So I was happily running the 20190722 PE (Pixel Experience) on beryllium-V10.3.6.0.PEJMIXM-9.0-vendor-firmware with DFE and Magisk 19.3 flashed from TWRP 3.3.0. All files from official sources including the Official Telegram.
I come to discover I am 2 updates behind on PE so I created a NANDROID backup of the boot, system, and restore. I then cleared the dav and cache per usual and dirty flashed the ROM.
I then proceed to reboot the phone and it begins to encrypt itself. Given that I am a brilliant engineer, I proceed to interrupt it and restart the phone into TWRP. It loads and prompts a password. I have forgotten to DFE.
At this point I know that I have completely screwed up so, following the ongoing consensus on these forums, I format in TWRP, rebooting and clearing as instructed. I then go to restore the NANDROID. No go, boot loop.
After reading more, conclude that I need to flash the vendor FW and use it to reset/clear the phone and reinstall TWRP via FASTBOOT then flash the NANDROID. Nope, boot loop.
Going farther I discover that I need to flash the NAN on top of it’s working ROM/FW.
I go and flash the previously working ROM AND FW with dfe. To I double check I boot that and it boots properly to Android Setup.
Great! I use TWRP to flash the NANDROID. It boots to a lighted black screen. Pushing power I can get it to come up with a power/reboot/lock down menu that moves around the screen. This will actually restart or turn it off (didn’t touch the last).
I have tried this in various combinations with both my new NAN as well as a known working one.
Any ideas/thoughts/insults/ (I can take it)?
Try flashing 10.3.7.0 and then PE and immediately after DFE. However, I'm not sure it you won't lose everything. When doing your backup from TWRP, choose everything except System & Vendor. These 2 will be covered by System Image & Vendor Image.
HTH