Related
Was running the unofficial lineage 14.1 rom, was getting frustrated with all the gps problems so I decided to try fulmics. Well cell service didn't work on fulmics, so I wanted to switch back and tough out the gps problems until lineage team got things fixed. Recovery seems to be working fine, but any rom I try to install simply endless reboots before every getting to the initial set up. I am at a loss, I am thinking I didn't have the new lg bootloader as I was told to have before trying to install fulmics. How the hell can I fix my phone? I always thought as long as recovery worked I would be fine, but that doesn't seem to be the case. Anyone help before I have to go out and buy a new phone tomorrow?
jamesvmccann said:
Was running the unofficial lineage 14.1 rom, was getting frustrated with all the gps problems so I decided to try fulmics. Well cell service didn't work on fulmics, so I wanted to switch back and tough out the gps problems until lineage team got things fixed. Recovery seems to be working fine, but any rom I try to install simply endless reboots before every getting to the initial set up. I am at a loss, I am thinking I didn't have the new lg bootloader as I was told to have before trying to install fulmics. How the hell can I fix my phone? I always thought as long as recovery worked I would be fine, but that doesn't seem to be the case. Anyone help before I have to go out and buy a new phone tomorrow?
Click to expand...
Click to collapse
PMd you.
I found a fix, I completely wiped everything and first flashed just the stock 7.0 lg bootloader, now everything is working fine. Thanks for the message though!
jamesvmccann said:
I found a fix, I completely wiped everything and first flashed just the stock 7.0 lg bootloader, now everything is working fine. Thanks for the message though!
Click to expand...
Click to collapse
No problem ?
Same Problem
I have the exact same problem. I flashed the LineageOS ROM, then flashed Fulmics ROM, then tried to go back to Lineage—and now every ROM just reboots endlessly, but I can boot into recovery and access TWRP just fine.
It looks like jamesvmccann found a fix, by "completely wiped everything and [then] flash[ing] just the stock 7.0 lg bootloader." I'm afraid I don't know where to download the stock 7.0 lg bootloader. This is a h830, so that may matter as well.
Any additional help would be greatly appreciated.
Managed to fix this problem myself
The stock h830 bootloader was linked in this forum post.
I booted into TWRP and flashed the stock bootloader. It has a different bootflash.
H850 keeps booting into Recovery
Hello everyone, I have a H850 and my phone does not want to boot into the OS. It keeps booting into Recovery mode. I tried flashing only the H850 bootloader and then installing a ROM, and it doesn't work. I've formatted everything except the SD card and still no joy. What else can I do to restore my H850?
Please Help!
KCKitsune said:
Hello everyone, I have a H850 and my phone does not want to boot into the OS. It keeps booting into Recovery mode. I tried flashing only the H850 bootloader and then installing a ROM, and it doesn't work. I've formatted everything except the SD card and still no joy. What else can I do to restore my H850?
Please Help!
Click to expand...
Click to collapse
I had same problem factory reset few times within twrp seem to work after a while. I take it your backup not working? If all else fails flash kdz in lgup
Sent from my LGE LG-H830 using XDA Labs
I am wondering why I can not put a custom rom onto my V30 converted to a US998. Everything I find online is for the H931 and I would like to try out some of these roms. I read that they should work on the phone but when I tried it I did not receive any signal from Verizon. Also when going threw to new phone setup the screen would go black. After I would reboot and go threw the process again it still happened.
danieledwrds2014 said:
I am wondering why I can not put a custom rom onto my V30 converted to a US998. Everything I find online is for the H931 and I would like to try out some of these roms. I read that they should work on the phone but when I tried it I did not receive any signal from Verizon. Also when going threw to new phone setup the screen would go black. After I would reboot and go threw the process again it still happened.
Click to expand...
Click to collapse
You have a exfat sdcard? Kernel driver probably doesnt like it, and eventually crashes the phone (and when youre "too slow", that happens during setup)
The H930 roms work fine on H930(D/DS/G), US998, LS998 and VS996, you would be the first for who it wouldnt work . Its just known that you kinda need to place a call every now and then on Verizon (and only there...) otherwise you wont receive sms/calls but data works fine...
Just (converted) H931 and H933 bootloop (except 1 guy who managed to make it work on his H933... and nobody, not even himself, knows how). No idea of the 3 korean variants now though...
SGCMarkus said:
You have a exfat sdcard? Kernel driver probably doesnt like it, and eventually crashes the phone (and when youre "too slow", that happens during setup)
The H930 roms work fine on H930(D/DS/G), US998, LS998 and VS996, you would be the first for who it wouldnt work . Its just known that you kinda need to place a call every now and then on Verizon (and only there...) otherwise you wont receive sms/calls but data works fine...
Just (converted) H931 and H933 bootloop (except 1 guy who managed to make it work on his H933... and nobody, not even himself, knows how). No idea of the 3 korean variants now though...
Click to expand...
Click to collapse
I do not have any sdcard installed on my phone at all. I don't know how I am being to slow with the setup. When it pops up with the setup I just press on next or fill everything in. Just for some reason the screen goes black. I used the v30 version of resurrection remix. And I used the stock version of Open GApps, I read I should probably try to nano or pico version. Just to verify I should be using the ARM64 version correct?
Please explain the have to make a call to verizon (every once in a while) or I can recieve sms or calls.
danieledwrds2014 said:
I do not have any sdcard installed on my phone at all. I don't know how I am being to slow with the setup. When it pops up with the setup I just press on next or fill everything in. Just for some reason the screen goes black. I used the v30 version of resurrection remix. And I used the stock version of Open GApps, I read I should probably try to nano or pico version. Just to verify I should be using the ARM64 version correct?
Please explain the have to make a call to verizon (every once in a while) or I can recieve sms or calls.
Click to expand...
Click to collapse
Thats a weird behaviour for a VS996
havent heard of that before. Usually it only crashes during setup if the kernel shouldnt like the installed exfat sdcard. Never heard of it happening otherwise
And what i mean with that was that for some reason only verizon users need to place a call after booting (or after some amount of time), otherwise they wont receive any calls or sms, even though data works all the time.
SGCMarkus said:
Thats a weird behaviour for a VS996
havent heard of that before. Usually it only crashes during setup if the kernel shouldnt like the installed exfat sdcard. Never heard of it happening otherwise
And what i mean with that was that for some reason only verizon users need to place a call after booting (or after some amount of time), otherwise they wont receive any calls or sms, even though data works all the time.
Click to expand...
Click to collapse
I don't know if it matters but its a converted VS996 to a US998. I know its weird, is there a version of resurrection remix os that I should try. I tried the unofficial one here. ( https://forum.xda-developers.com/lg-v30/development/rom-resurrectionremix-v6-0-0-t3798443 ) due to not being to find a supported version on Resurrection Remix's website at all. I really want to get this to work just don't want to brick my phone in the process. I understand that is always a risk that everyone takes but when I followed the directions it still didn't work. Maybe I am looking at the wrong place, or doing something wrong.
I am running the 20d of the US998 firmware
Used TWRP format everything execpt the actual system itself.
Used TWRP to install ( RR .zip file and then the GApps file) <-----should i use the micro or pico?
Booted into the phone everything went good during the setup process I chose mobile data and turned off wifi. Then the setup screen went black. I could still see the status bar in the top where it shows battery etc...
(During the setup process I had no connection with verizon) <------Any idea why?
I have the Verizon vs996 as my phone. I have used the Frankenstein method to change it to the us998 version, then unlocked the bootloader and then eventually rooted the phone. I have successfully installed and used at least most, if not all of SGCMarkus' roms, including RR (the version you linked).
I have also used AEX, DotOS, AOSIP, Dirty Unicorns 9.0, twrp flashable vs996 and us998 roms (currently on the twrp vs 996_20f), and maybe others that I am forgetting (it seems like I am forgetting a rom or two)? I have successfully flashed and used all of those I have mentioned. I have successfully flashed and installed Boom box rom, but cannot get the data to work on it. I have not tried to flash or install lineage.
So, I know that it can be done on a Verizon VS996 phone.
So, if you are successfully boot loader unlocked and rooted with twrp installed, it should work.
So, I would download the rom of choice and the suggested gapps (I normally use Nano, and I think v30, does use the arm 64 version. Make sure you have the correct 8.0 or 8.1 download of gapps) and Magisk.
I have used both the data only and also wifi in the setup process successfully. Don't ever recall getting a black screen. I do have an old 32gb SD card that has not given me any trouble (yet).
Hopefully, you can get it worked out and working OK.
I found the reason for all my issues was because I used the Open GApps Stock instead of the nano I switched it out and its working perfectly.
gimpy1 said:
I have the Verizon vs996 as my phone. I have used the Frankenstein method to change it to the us998 version, then unlocked the bootloader and then eventually rooted the phone. I have successfully installed and used at least most, if not all of SGCMarkus' roms, including RR (the version you linked).
I have also used AEX, DotOS, AOSIP, Dirty Unicorns 9.0, twrp flashable vs996 and us998 roms (currently on the twrp vs 996_20f), and maybe others that I am forgetting (it seems like I am forgetting a rom or two)? I have successfully flashed and used all of those I have mentioned. I have successfully flashed and installed Boom box rom, but cannot get the data to work on it. I have not tried to flash or install lineage.
So, I know that it can be done on a Verizon VS996 phone.
So, if you are successfully boot loader unlocked and rooted with twrp installed, it should work.
So, I would download the rom of choice and the suggested gapps (I normally use Nano, and I think v30, does use the arm 64 version. Make sure you have the correct 8.0 or 8.1 download of gapps) and Magisk.
I have used both the data only and also wifi in the setup process successfully. Don't ever recall getting a black screen. I do have an old 32gb SD card that has not given me any trouble (yet).
Hopefully, you can get it worked out and working OK.
Click to expand...
Click to collapse
Hey everyone,
I am very new to the OP7TP, comming from an HTC U11 which is.. old and very different.
Anyhow on to my problem:
When I got my new device I decided to get rooted, and then chose to use reseruction rom.
Which was a pretty nice experience, but I also wanted to see what else was being released, and Havoc came along.
I flashed Havoc according to the instructions on telegram, using fastbootd..
But when I went to boot it just kept rebooting to Bootloader mode
I restored my device using MSM, and triedagain, with the same result
But now, for the real trouble: reseruction rom does the same!
When flashing it, it will just reboot to bootloader every time.
It seems I can't flash custom roms anymore?
The stock OOS rom seems to be fastbootd and MSM flashable and boots without issue.
Has anyone encountered this before? any advice on how to proceed?
I am using the European OP7TP HD1913 with latest stable OOS 10.0.9 HD01BA
Solution:
Well I do feel silly now..
I flashed Reseruction Remix using my Desktop
Flashed Havoc (and all other attempts) using my notebook
And even tho I installed, which I thought were the correct fastboot drivers, evidently they are not..
When I tried flashing Havoc using my desktop it worked instantly..
It was just fastboot.. no errors during flashing, wiping, erasing and such... but it did something wrong..
Giblet-dono said:
Hey everyone,
I am very new to the OP7TP, comming from an HTC U11 which is.. old and very different.
Anyhow on to my problem:
When I got my new device I decided to get rooted, and then chose to use reseruction rom.
Which was a pretty nice experience, but I also wanted to see what else was being released, and Havoc came along.
I flashed Havoc according to the instructions on telegram, using fastbootd..
But when I went to boot it just kept rebooting to Bootloader mode
I restored my device using MSM, and triedagain, with the same result
But now, for the real trouble: reseruction rom does the same!
When flashing it, it will just reboot to bootloader every time.
It seems I can't flash custom roms anymore?
The stock OOS rom seems to be fastbootd and MSM flashable and boots without issue.
Has anyone encountered this before? any advice on how to proceed?
I am using the European OP7TP HD1913 with latest stable OOS 10.0.9 HD01BA
Solution:
Well I do feel silly now..
I flashed Reseruction Remix using my Desktop
Flashed Havoc (and all other attempts) using my notebook
And even tho I installed, which I thought were the correct fastboot drivers, evidently they are not..
When I tried flashing Havoc using my desktop it worked instantly..
It was just fastboot.. no errors during flashing, wiping, erasing and such... but it did something wrong..
Click to expand...
Click to collapse
Everytime I flashed havok I had to wipe data after flashing the ROM when it was in boitloop I held all buttons. Then went to recovery and wiped data then it booted fine
I purchased a LS998 and followed ChazzMatt's guide to convert it to a US998. This worked fine:
https://forum.xda-developers.com/showpost.php?p=76584629&postcount=193
I was able to unlock my bootloader and flash TWRP all OK.
I eventually flashed the latest LGUP firmware "US99820h_00_0318.kdz".
From this I was able to install the latest Magisk 20.4, "AK3_RCTD_Remover", and "Disable_Dm-Verity_ForceEncrypt".
LG's native rom boots fine and everything seems to work; wifi, camera, etc.
Satisfied with this setup, I flashed "lineage-16.0-20200807-UNOFFICIAL-h930.zip" and set everything up as I wanted. Everything worked-- EXCEPT for the camera. Every time the stock AOSP camera (or any other camera app) launched, it would immediately crash.
I flashed "US99820h_00_0318.kdz" back with REFURBISH and confirmed that the camera was fine. Since this removed TWRP as the stock recovery, I had to repeat the same steps from above.
But now every time I boot into LOS 16, it will hang after a short period of time at the setup screen (where it says START). I can click on start while it is still responsive but the "Just a sec..." message and the progress circle will spin and not proceed. The phone will then eventually locks up from there.
I have been unable to figure out how to fix this. I can always revert back to "US99820h_00_0318.kdz" without issue but I can no longer get back onto LOS 16 for some reason.
I did make a TWRP backup of Boot/Data/System but restoring this on top of LOS 16 results in the phone booting up to a progress message "Phone is starting..." which will eventually lead to it too failing to progress and locking up.
I have been flashing roms for years and I have NEVER had this much trouble before. Once a recovery is loaded, flashing a rom, wiping data and doing a factory reset ALWAYS gave me a working system. But it fails here. Why?
Kahenraz said:
I purchased a LS998 and followed ChazzMatt's guide to convert it to a US998. This worked fine:
https://forum.xda-developers.com/showpost.php?p=76584629&postcount=193
I was able to unlock my bootloader and flash TWRP all OK.
I eventually flashed the latest LGUP firmware "US99820h_00_0318.kdz".
From this I was able to install the latest Magisk 20.4, "AK3_RCTD_Remover", and "Disable_Dm-Verity_ForceEncrypt".
LG's native rom boots fine and everything seems to work; wifi, camera, etc.
Satisfied with this setup, I flashed "lineage-16.0-20200807-UNOFFICIAL-h930.zip" and set everything up as I wanted. Everything worked-- EXCEPT for the camera. Every time the stock AOSP camera (or any other camera app) launched, it would immediately crash.
I flashed "US99820h_00_0318.kdz" back with REFURBISH and confirmed that the camera was fine. Since this removed TWRP as the stock recovery, I had to repeat the same steps from above.
But now every time I boot into LOS 16, it will hang after a short period of time at the setup screen (where it says START). I can click on start while it is still responsive but the "Just a sec..." message and the progress circle will spin and not proceed. The phone will then eventually locks up from there.
I have been unable to figure out how to fix this. I can always revert back to "US99820h_00_0318.kdz" without issue but I can no longer get back onto LOS 16 for some reason.
I did make a TWRP backup of Boot/Data/System but restoring this on top of LOS 16 results in the phone booting up to a progress message "Phone is starting..." which will eventually lead to it too failing to progress and locking up.
I have been flashing roms for years and I have NEVER had this much trouble before. Once a recovery is loaded, flashing a rom, wiping data and doing a factory reset ALWAYS gave me a working system. But it fails here. Why?
Click to expand...
Click to collapse
https://forum.xda-developers.com/lg-v30/how-to/detailed-guide-aosp-roms-issues-solution-t4002535
That helps to explain the camera (it doesn't work with anything but GCam) but not how to get LOS 16 working again.
Kahenraz said:
I purchased a LS998 and followed ChazzMatt's guide to convert it to a US998.
This worked fine:
https://forum.xda-developers.com/showpost.php?p=76584629&postcount=193
I was able to unlock my bootloader and flash TWRP all OK.
I eventually flashed the latest LGUP firmware "US99820h_00_0318.kdz".
From this I was able to install the latest Magisk 20.4, "AK3_RCTD_Remover", and "Disable_Dm-Verity_ForceEncrypt".
LG's native rom boots fine and everything seems to work; wifi, camera, etc.
Click to expand...
Click to collapse
You're welcome!
Kahenraz said:
Satisfied with this setup, I flashed "lineage-16.0-20200807-UNOFFICIAL-h930.zip" and set everything up as I wanted. Everything worked-- EXCEPT for the camera. Every time the stock AOSP camera (or any other camera app) launched, it would immediately crash.
Click to expand...
Click to collapse
Some people have had issues with camera on LOS and need different permissive kernel. @tech_infinity is one of the experts and I see he's tried to help.
You were correct in flashing LOS-16 from last stock Oreo. If you had updated to stock Pie, then tried to flash LOS-16, I would have said that was part of your problem.
I do not know why you cannot load LOS-16, but one possible way of fixing it is a little tedious, but you can try if you are willing.
Flash Nougat US998 KDZ via Refurbish mode. This is only temporary stage. You will lose TWRP and root but still have unlocked bootloader. Going back to Nougat cleans out a lot of stuff. Then flash US998 20h KDZ. You will still have unlocked bootloader.
At that point, then, follow WTF Section 6 to reinstall TWRP, encryption disabler, root check disabler, root.
Then, try to install LOS-16 again. But this time perhaps try a different permissive custom kernel, which @tech_infinity can suggest to you. That may solve your camera problems, and hopefully the Nougat-back-to-Oreo will solve the LOS-16 loading issue.
Kahenraz said:
That helps to explain the camera (it doesn't work with anything but GCam) but not how to get LOS 16 working again.
Click to expand...
Click to collapse
You tried going permissive already?
The issue with the boot hang ended up being an issue with the SD card I had inserted. It worked fine in TWRP and LG's Android rom but it would hang for LOS 16.
Before I had done a wipe of my first install of LOS 16, I backed up the rom and copied it over to disk on Windows. But I must have made a mistake on removal that left the FAT32 filesystem in an inconsistent state.
I finally stuck it into my PC where Windows asked that I repair it. LOS 16 worked fine after that; with and without the same SD card.
The camera was fixed by enabling SELinux to Permissive. I'm not a fan of this as I do like the security that SELinux provides. But I also need my camera... and I see no alternative.
Kahenraz said:
The issue with the boot hang ended up being an issue with the SD card I had inserted. It worked fine in TWRP and LG's Android rom but it would hang for LOS 16.
Before I had done a wipe of my first install of LOS 16, I backed up the rom and copied it over to disk on Windows. But I must have made a mistake on removal that left the FAT32 filesystem in an inconsistent state.
I finally stuck it into my PC where Windows asked that I repair it. LOS 16 worked fine after that; with and without the same SD card.
Click to expand...
Click to collapse
Glad you got it figured out.
Kahenraz said:
The camera was fixed by enabling SELinux to Permissive. I'm not a fan of this as I do like the security that SELinux provides. But I also need my camera... and I see no alternative.
Click to expand...
Click to collapse
All V30 LOS-based ROMs need Permissive. Sometimes when reverting from LOS-17 ROMs back to stock Android 9, you then still need to run permissive kernel. Or else camera won't work and other sensors. It's like remnants of LOS-17 still affecting the phone even though you are back on stock. The way people can fix that (most of the time) is to refurbish to Nougat, then go back to newer firmware. That was why I suggested that, but it turned out to be your microSD card.
Are you saying that I could have SELinux Enforcing if I had not flashed stock Pie and then LOS 17?
Kahenraz said:
Are you saying that I could have SELinux Enforcing if I had not flashed stock Pie and then LOS 17?
Click to expand...
Click to collapse
No. I'm saying all V30 LOS ROMs require permissive.
Furthermore, after running LOS ROM 17 if you wish to return to stock you may STILL need permissive mode for camera and other sensors. (LOS-16 doesn't have this after-effect returning to stock.) The fix for the LOS-17 remnants gunk is to refurbish back to Nougat, then update again to newer stock. That often works.
But all V30 LOS ROMs require permissive.
So, I install lineage os every one's and a while to test it and see if it is ok for me, I always revert to stock but that's not the point, one problem that I have is that the phone gets VERY HOT. One day I installed lineage and when I finished the setup process, the phone was so hot I couldn't hold it comfortably, while when I finish the setup on the stock rom the phone is just warm. Is there any way to make the phone run cooler? Is the phone getting hot because the software is too much for the processor? . I haven't installed lineage os for about two months now so I may try it again at some point. Is anyone else having the same problem?
No that's not normal, it's not supposed to heat up much.
Maybe you you didnt flash it properly, it's recommended to install it like this.
forum.xda-developers.com/lg-g5/development/rom-unofficial-lineageos-17-1-g5-t4039807/post81972297#post81972297
Also check before flashing if your camera works on the stock lg rom,
If it doesnt you have to downgrade to stock marshmellow, and then upgrade back to oreo to fix it.
dylank said:
No that's not normal, it's not supposed to heat up much.
Maybe you you didnt flash it properly, it's recommended to install it like this.
forum.xda-developers.com/lg-g5/development/rom-unofficial-lineageos-17-1-g5-t4039807/post81972297#post81972297
Also check before flashing if your camera works on the stock lg rom,
If it doesnt you have to downgrade to stock marshmellow, and then upgrade back to oreo to fix it.
Click to expand...
Click to collapse
Thanks for answering,
This is how I install it. The camera on stock oreo is working normally so I don't need to install stock Marshmallow. So, I firstly unlock the bootloader and then install lineage os 15.1 with no gapps. After that I upgrade to lineage os 16.1 again with no gapps. Now I uninstall lineage 16.1 and I am doing a clean install of official lineage os 17.1 WITH gapps. The reason I do this is because if I install lineage 17.1 instantly the cameras and sensors don't work. Unfortunately I don't remember the temperatures that I got but I remember that one day I woke up with 20 C and after 15 minutes of some web browsing and social media it went up to 40 C (there's a slight chance that I'm wrong since I don't remember the exact temperatures as I said)
Strange i didn't have those problems when flashing properly,
Do you also use nano/pico opengapps?
You could also give crDroid Android 5.12, a try maybe that will work well, but it's android 9 instead of 10.
I think you need to flash it in the same way as lineage.
dylank said:
Strange i didn't have those problems when flashing properly,
Do you also use nano/pico opengapps?
You could also give crDroid Android 5.12, a try maybe that will work well, but it's android 9 instead of 10.
I think you need to flash it in the same way as lineage.
Click to expand...
Click to collapse
I originally used nano opengapps but I started using stock because I use most of the gapps anyway but I will try crdroid 5.12 at some point to see what happens.