Database Users

[HELP]My nexus 4 can not boot even after flash stock image correctly several times!

Hello everyone, I thought I've got a big problem here...
My nexus 4 originally crashed and stuck into a boot loop several days ago, and I flashed stock factory image(4.4.2), then it works again. After that, I imported my backup files into internal storage and using titanium backup restored my apps and data, unfortunately, crashed and boot loop again...So I flashed stock factory image again to find out what reason of this. After several restore from stock factory image, I found that my sms message and many mp3 files could lead to crash, after flash factory image, works fine, use it, reboot it ,fine, but after copy many mp3 files and restore my sms backup(about 2,000+ messages), reboot, stuck into boot loop... Now I try to flash stock image again, however, with no luck to boot my phone...
During my privious several times of flash stock image, it's always hard to boot the machine normally at the first time, I always try to wipe cache, factory reset in recovery even several times to manage to boot the machine normally.
This time when I flash stock image again, I just can't boot my nexus 4 anymore, even wipe cache, factory reset from recovery, whatever other tries...:crying:
Now I even tried several ways to flash stock image(4.4.2, which I used to managed boot up before):
1 Using the newest Nexus Root Toolkit: Boot into bootloader mode and click "Flash Stock+Unroot(soft bricked/boot loop)", everything says OK, however, it just can't boot and stuck in Google logo screen, even after I waited for 2 hours...
2 Using the flash-all.bat: Extract the .tgz image file into a folder which contains adb.exe and fastboot.exe, then execute flash-all.bat, everything reports OK, but just can't boot up, still stuck on Google screen.
3 Manually flash: Extract the .tgz and the .zip, put all files(including boot.zip, system.zip, recovery.zip etc) in one folder, flash bootloader and radio first, then "fastboot flash [partition] *.img", and everything says OK, just can't boot up and stuck on Google screen.
4 Manually flash using 3rd party recovery: Have tried to flash newest CWRP recovery and CMOD recovery separately first, then do manually flash as above.
I even do:
fastboot oem lock
fastboot oem unlock
fastboot reboot-bootloader
fastboot erase system(or fastboot format system)
fastboot erase userdata(or fastboot format userdata)
fastboot erase boot
fastboot erase recovery
fastboot erase cache(or fastboot format cache)
these commands before I try to do the four ways to restore factory image above, but nothing changed.
Now stuck on Google screen, what ever I wipe cache/factory reset how many times, it's just stucked... I even doubt if my flash memory was broken???
PELEASE HELP!

diligentpig said:
Hello everyone, I thought I've got a big problem here...
My nexus 4 originally crashed and stuck into a boot loop several days ago, and I flashed stock factory image(4.4.2), then it works again. After
[Snip]
PELEASE HELP!
Click to expand...
Click to collapse
Flash CWM, wipe the partitions there (But not /boot or /persist, those will hardbrick if you reboot after wiping although I don't think it will let you wipe them), flash the latest radio (.98), and then flash a 4.4 ROM.
If that doesn't work, wait for more responses from others, then try this as a last resort. I suggest that you wait a few days, this can be dangerous
http://forum.xda-developers.com/nexus-4/general/tutorial-how-to-unbrick-n4-t2347060
Follow carefully, and read multiple times before starting. Take it slow and don't panic if the process doesn't go as expected at 85% (Mine wouldn't reboot on its own for some reason, it kept erroring but it was fine and worked itself out)
It should put the phone on a complete clean slate for flashing

Thanks for your reply
lopezk38 said:
Flash CWM, wipe the partitions there (But not /boot or /persist, those will hardbrick if you reboot after wiping although I don't think it will let you wipe them), flash the latest radio (.98), and then flash a 4.4 ROM.
If that doesn't work, wait for more responses from others, then try this as a last resort. I suggest that you wait a few days, this can be dangerous
http://forum.xda-developers.com/nexus-4/general/tutorial-how-to-unbrick-n4-t2347060
Follow carefully, and read multiple times before starting. Take it slow and don't panic if the process doesn't go as expected at 85% (Mine wouldn't reboot on its own for some reason, it kept erroring but it was fine and worked itself out)
It should put the phone on a complete clean slate for flashing
Click to expand...
Click to collapse
Hi lopezk38,
Thanks for your reply! And I do as your instruction:flash newest CWM recovery, then factory rest, wipe cache, and under mouts menu format system/cache/data and firmware(but error), then flash a latest CyanogenMod image for nexus 4, with no luck, everything remains the same
However, I saw the link you provided to unbrick nexus 4, I'll read it carefully several times. At the same time, I'll wait for any other kind help that anyone can provide. If finally there is no other way to repair it, I'll go through with your link.
Thanks again for the tip!

diligentpig said:
Hi lopezk38,
Thanks for your reply! And I do as your instruction:flash newest CWM recovery, then factory rest, wipe cache, and under mouts menu format system/cache/data and firmware(but error), then flash a latest CyanogenMod image for nexus 4, with no luck, everything remains the same
However, I saw the link you provided to unbrick nexus 4, I'll read it carefully several times. At the same time, I'll wait for any other kind help that anyone can provide. If finally there is no other way to repair it, I'll go through with your link.
Thanks again for the tip!
Click to expand...
Click to collapse
Yeah /firmware was another that won't wipe, I just forgot to mention it. Best of luck

It sounds like you have faulty nand block (s). Before no critical parts of the firmware got written to it, so it developed problems when you wrote data to it. Looks like this time you didn't get so lucky, or more failed. If it's under warranty I would RMA it; if it's not, I'm honestly not sure what your best option is. Maybe get one that has broken screen etc, then do a logic board transplant. Good luck.
Sent from my Nexus 4 using Tapatalk

lopezk38 said:
Yeah /firmware was another that won't wipe, I just forgot to mention it. Best of luck
Click to expand...
Click to collapse
I'm going to do the work in the thread you provided now...and will tell you what I've got finally.

consolation said:
It sounds like you have faulty nand block (s). Before no critical parts of the firmware got written to it, so it developed problems when you wrote data to it. Looks like this time you didn't get so lucky, or more failed. If it's under warranty I would RMA it; if it's not, I'm honestly not sure what your best option is. Maybe get one that has broken screen etc, then do a logic board transplant. Good luck.
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
Thanks for your reply. Nexus 4 was not intend to sell to my country, so...Wish me luck

lopezk38 said:
Flash CWM, wipe the partitions there (But not /boot or /persist, those will hardbrick if you reboot after wiping although I don't think it will let you wipe them), flash the latest radio (.98), and then flash a 4.4 ROM.
If that doesn't work, wait for more responses from others, then try this as a last resort. I suggest that you wait a few days, this can be dangerous
http://forum.xda-developers.com/nexus-4/general/tutorial-how-to-unbrick-n4-t2347060
Follow carefully, and read multiple times before starting. Take it slow and don't panic if the process doesn't go as expected at 85% (Mine wouldn't reboot on its own for some reason, it kept erroring but it was fine and worked itself out)
It should put the phone on a complete clean slate for flashing
Click to expand...
Click to collapse
diligentpig said:
Hi lopezk38,
Thanks for your reply! And I do as your instruction:flash newest CWM recovery, then factory rest, wipe cache, and under mouts menu format system/cache/data and firmware(but error), then flash a latest CyanogenMod image for nexus 4, with no luck, everything remains the same
However, I saw the link you provided to unbrick nexus 4, I'll read it carefully several times. At the same time, I'll wait for any other kind help that anyone can provide. If finally there is no other way to repair it, I'll go through with your link.
Thanks again for the tip!
Click to expand...
Click to collapse
Hi, I've carefully read the link several times, and finally go through with it without any problems, and I could flash 4.2.2 stock images and do the 8gb to 16gb part to restore my phone to 16gb storage...However I found that I only can flash 4.2.2 image to make the phone boot up normally, with 4.3 or 4.4.2 image, it fails at boot up. Most important and sad part is, when the phone complete initial setup and install some software, it crash and can not boot again:crying: I've given several tries but the same result.
Finally, I made decision to sold it to buyer who needs only a good glass screen for replacement purpose... Farewell, my nexus4...

[Q] i9505 (jgedlte) fails to boot system after installing ROM

I'm trying to install CM via TWRP.
First I had to unlock the bootloader, so I did, and since then I could not boot to my stock Android (although, correct me if I'm wrong, unlocking the bootloader should NOT delete the OS), it just sent me to recovery.
So I went along, flashed TWRP and got cm 10.2.1 for jfltexx. At first it didn't install well, because my data partition was not formatted correctly. So I formatted it, now TWRP sees it correctly and is able to mount it, enable MTP and everything. When I try to install now, everything seems fine and TWRP's log shows "Updating partition details..." and gives me the "Successful" message, offering to wipe cache/reboot system. (I did wipe cache and dalvik cache before, of course).
If I choose "Reboot System", it just boots back to recovery. The same happens if I power it off and boot normally, even if I pull out the battery and retry that way.
What can I do about it?

Jon-G said:
I'm trying to install CM via TWRP.
First I had to unlock the bootloader, so I did, and since then I could not boot to my stock Android (although, correct me if I'm wrong, unlocking the bootloader should NOT delete the OS), it just sent me to recovery.
So I went along, flashed TWRP and got cm 10.2.1 for jfltexx. At first it didn't install well, because my data partition was not formatted correctly. So I formatted it, now TWRP sees it correctly and is able to mount it, enable MTP and everything. When I try to install now, everything seems fine and TWRP's log shows "Updating partition details..." and gives me the "Successful" message, offering to wipe cache/reboot system. (I did wipe cache and dalvik cache before, of course).
If I choose "Reboot System", it just boots back to recovery. The same happens if I power it off and boot normally, even if I pull out the battery and retry that way.
What can I do about it?
Click to expand...
Click to collapse
First I'd try a newer version of CM. That's an old one. It might not work and play well with a newer version of TWRP. Plus the newer version is a little more polished.
Second, if you must use that CM version, redownload it. You wouldn't be the first person who got a corrupted install file that causes screwball issues like this.
Third, if all else fails use Odin to reset back to stock and start over. Something might have gotten all borked up when you first modified the device that isn't letting the install work. A full restore to stock should correct that.

Skipjacks said:
First I'd try a newer version of CM. That's an old one. It might not work and play well with a newer version of TWRP. Plus the newer version is a little more polished.
Second, if you must use that CM version, redownload it. You wouldn't be the first person who got a corrupted install file that causes screwball issues like this.
Third, if all else fails use Odin to reset back to stock and start over. Something might have gotten all borked up when you first modified the device that isn't letting the install work. A full restore to stock should correct that.
Click to expand...
Click to collapse
Thanks for the reply.
Regarding the versions of CM and TWRP, I deliberately picked these versions due to their high download count (A sign I can trust these builds, being not too buggy). I'll try a newer CM version and another TWRP version if that didn't help.
I will also verify the MD5 for the downloaded file this time.
If I restore to stock via Odin, wouldn't that override the recovery? I've looked on some tutorial on how it's done, and it seems like the stock recovery is flashed, then used to restore the stock. Is there any way to use Odin to flash other ROMs?
EDIT: Nope cm-11-20140210 also failed, and I did verify the MD5 now. My TWRP is the newest available for jgedlte in the download page (2.8.0.1).
I did manage getting into some sort of a boot loop (The initial "Reboot System" brought back the recovery, but after a full power off and a reboot, the screen remains black and the phone vibrates every 4 seconds or so.)
EDIT 2: I tried to flash the stock back, following this tutorial. I downloaded the Open European version, flashed the AP but it failed during the write of system.img.ext4, saying that the image is invalid. I tried again with the PIT file, but it failed too (secure check fail while repartitioning...).

Wifi just quit working, Motorola not helping

OK guys. You are my last hope!
My phone recently stopped detecting wifi networks at all. I've tried to determine what caused it. Tried everything except doing a factory reset.
Then, I called Motorola, and they suggested that very thing. So I tried it. Only problem was that I have TWRP custom recovery installed. My bootloader is unlocked btw. So it went into a bootloop, until I forced it to shutdown and do a normal restart. So factory reset wont work with custom. Lesson learned!
So, I thought that I would use the official factory image (https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a/session/L3RpbWUvMTQ3NDgzMDIyNy9zaWQvUEpTQnd4X20%3D) I got from Motorola a while back. But the instructions were confusing. When that's the case. I usually try and find a second guide that makes it clearer.
So I called Motorola again, asking how to go about flashing the image from fastboot. They said I don't have a developers version of the X Pure Edition! The website doesn't make it clear at all that there's 2 versions of the device (XT1575). Which is total BS. How was I supposed to know? Also he said that unlocking my bootloader voided my warranty. So they wont fix it either!
This is why you guys are my last hope!
Not sure what to try from here. I don't think I'll ever get my wifi working again. But would really like to try.
Vitals:
Non-rooted
Bootloader unlocked/TWRP Recovery
Moto X Pure XT1575
Android 6.0
Kernel version 3.10.84-perf-g6898f68
[email protected] #1 Sat Jan 30 14:35:02 CST 2016
System version 24.201.3.clark_retus.retus.en.US retus
Build number MPHS24.49-18-3

Back up anything you don't want to lose. Boot into TWRP and click wipe. Click 'Format Data'. Once that's done, click on wipe again, then advanced wipe, and select both Cache and ART/Dalvik Cache (and data/internal storage, if you like) and wipe them as well. Reboot. That's how you factory reset with TWRP, for future reference. As for you stock flashing question, see: http://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833 and https://www.youtube.com/watch?v=9ZZy1NvRyOc
There may be a Flash All script in your firmware package which does the heavy lifting for you. Simply extract the files and run the included BAT file. If not, or if you feel like getting your hands dirty, take a look at the 'Useful Commands' section in the thread I linked. Each command corresponds to a file in the firmware package you'll download from Motorola. Flash them one-by-one in the order listed in the thread. Make sure your command prompt is in the directory of the extracted files, or you'll get a file not found error. If you get an error flashing partition gpt.bin, ignore it. Happy flashing.

Odd that a factory reset didn't work with TWRP, it should... All other does is create an Openrecovery script that wipes data and cache, I can't explain why it didn't work.
Although the factory firmware may contain a flashall script, I suggest doing each piece manually via fastboot.
For future reference, the best way to fix the problem you had is to try this first: go to Settings, Backup & Reset, then do a Network Settings Reset, this often fixes WiFi problems.
Sent from my Motorola XT1575 using XDA Labs

Thanks guys! I will look into what you said. Then report back.
Well the network settings reset solved nothing. Guess it'd the hard way now

Dirty Santa and Restoring From Backups - Suck in some kind of limbo?

So I would have asked this question directly in the DirtySanta thread, but apparently I don't have enough posts to actually do anything there yet.
So my device is now in a rather bizzare zombie state. I did manage to get my device fully rooted with TWRP installed. Followed the instructions on how to get everything working with no problems. I ended up wanting to try to flash some audio mods (V4A and such), however they did not install properly, so I went and did what anyone else would do - restored to a full backup I made of the device before I started mucking about.
The restore did complete successfully, and I still have a device that has a working recovery, and an OS with root permission...but I can't flash anything anymore from TWRP. TWRP is unable to mount the /system partition after the restore, and seems convinced that I have no OS installed, even though there is one and the phone boots into it just fine. The restore I'm on now is post-flashing the Konverged Kernel. Attempting to restore to an even earlier backup (one I made just before flashing Konverged) produces similar results - the restore succeeds and produces a bootable phone, but TWRP still can't flash anything.
Just to cover bases I also tried running "fastboot flash recovery twrp-3.0.2-1-us996.img" again in case TWRP got messed up (trying to get the "Swipe to allow system changes" prompt to reappear - it didn't), with no changes - TWRP still works fine, but cant mount and edit /system and still claims I have no OS installed when requesting a reboot.
Any advice on how to get things working again would be greatly appreciated! Thanks!

This may be an issue with TWRP. When I had my Galaxy S3 rooted back in the day I would have this issue, also with a Nexus tablet I rooted as well. It turns out I needed to flash a specific "fixed" version of TWRP to fix the mount/flash issue. That was a long time ago though, so this might not be the problem, but I thought I would at least tell you my experience.
Sent from my LG-LS997 using Tapatalk

biglightbt said:
So I would have asked this question directly in the DirtySanta thread, but apparently I don't have enough posts to actually do anything there yet.
So my device is now in a rather bizzare zombie state. I did manage to get my device fully rooted with TWRP installed. Followed the instructions on how to get everything working with no problems. I ended up wanting to try to flash some audio mods (V4A and such), however they did not install properly, so I went and did what anyone else would do - restored to a full backup I made of the device before I started mucking about.
The restore did complete successfully, and I still have a device that has a working recovery, and an OS with root permission...but I can't flash anything anymore from TWRP. TWRP is unable to mount the /system partition after the restore, and seems convinced that I have no OS installed, even though there is one and the phone boots into it just fine. The restore I'm on now is post-flashing the Konverged Kernel. Attempting to restore to an even earlier backup (one I made just before flashing Konverged) produces similar results - the restore succeeds and produces a bootable phone, but TWRP still can't flash anything.
Just to cover bases I also tried running "fastboot flash recovery twrp-3.0.2-1-us996.img" again in case TWRP got messed up (trying to get the "Swipe to allow system changes" prompt to reappear - it didn't), with no changes - TWRP still works fine, but cant mount and edit /system and still claims I have no OS installed when requesting a reboot.
Any advice on how to get things working again would be greatly appreciated! Thanks!
Click to expand...
Click to collapse
I beleive you have to do Dirty Santa over again....The steps that is.

biglightbt said:
So I would have asked this question directly in the DirtySanta thread, but apparently I don't have enough posts to actually do anything there yet.
So my device is now in a rather bizzare zombie state. I did manage to get my device fully rooted with TWRP installed. Followed the instructions on how to get everything working with no problems. I ended up wanting to try to flash some audio mods (V4A and such), however they did not install properly, so I went and did what anyone else would do - restored to a full backup I made of the device before I started mucking about.
The restore did complete successfully, and I still have a device that has a working recovery, and an OS with root permission...but I can't flash anything anymore from TWRP. TWRP is unable to mount the /system partition after the restore, and seems convinced that I have no OS installed, even though there is one and the phone boots into it just fine. The restore I'm on now is post-flashing the Konverged Kernel. Attempting to restore to an even earlier backup (one I made just before flashing Konverged) produces similar results - the restore succeeds and produces a bootable phone, but TWRP still can't flash anything.
Just to cover bases I also tried running "fastboot flash recovery twrp-3.0.2-1-us996.img" again in case TWRP got messed up (trying to get the "Swipe to allow system changes" prompt to reappear - it didn't), with no changes - TWRP still works fine, but cant mount and edit /system and still claims I have no OS installed when requesting a reboot.
Any advice on how to get things working again would be greatly appreciated! Thanks!
Click to expand...
Click to collapse
So your phone isn't booting beyond TWRP? I'm assuming that's what you are saying. I only want clarification because you mentioned how it won't flash anything.
Try this. Go to "mount" and make sure system is checked. Then power off the device. Then use the button combo to boot back into recovery. It's power + volume down, as soon you see the LG logo let go of the power button and then press it again and hold it (never let go of the volume down button though). If done correctly you'll get a white screen asking you if you want to factory reset. Choose yes for both questions. This will boot you back into recovery. Once in recovery again go back to mount and check system again. Now reboot system. This method got me out of being stuck in TWRP after I had tried every other method I could think of.
PS. Make sure you are on a fully stock version of the ROM that came on your phone. This may work for any backup you have but just incase use the most stock version backup you have.

imucarmen said:
So your phone isn't booting beyond TWRP? I'm assuming that's what you are saying. I only want clarification because you mentioned how it won't flash anything.
Try this. Go to "mount" and make sure system is checked. Then power off the device. Then use the button combo to boot back into recovery. It's power + volume down, as soon you see the LG logo let go of the power button and then press it again and hold it (never let go of the volume down button though). If done correctly you'll get a white screen asking you if you want to factory reset. Choose yes for both questions. This will boot you back into recovery. Once in recovery again go back to mount and check system again. Now reboot system. This method got me out of being stuck in TWRP after I had tried every other method I could think of.
PS. Make sure you are on a fully stock version of the ROM that came on your phone. This may work for any backup you have but just incase use the most stock version backup you have.
Click to expand...
Click to collapse
Sorry if I wasn't clear, its a bit confusing to me also. Normally TWRP saying you have No OS installed is pretty bad news, but it seems to be a bit confused itself, since there IS and OS installed, and the phone boots into it.
The phone basically works exactly as you'd expect after the DirtySanta exploit. It can boot into whatever backup I restore it back to, and works just fine, root included. I can also boot into TWRP just fine also..... Its just that within TWRP, if I try to flash anything at all (apps, zip files, kernels) it comes back with an error just after "Updating Partition Details". The specific error is "failed to mount /system (invalid argument)". If I had to guess I'd think that /system was somehow marked as Read Only after I did the restore. I haven't needed to use the button combos for anything since ADB and Fastboot commands all work just fine too.
If I go into the "Mount" section in TWRP "System" is unchecked, if I tap it to try to check it the phone vibrates as if it accepted the input, but the check never appears. If I select "Mount System as Read Only" I can mount it though. I followed the instructions in the DirtySanta thread to a T, and am using all the recommended software versions.
I also tried restoring back to the backup I made just before flashing Konverged Kernel, with similar results. The restore works, and the phone boots into Android, but if I try to pick up where I left off and flash Konverged again from within TWRP, it fails with the "failed to mount /system (invalid argument)" again.

biglightbt said:
Sorry if I wasn't clear, its a bit confusing to me also. Normally TWRP saying you have No OS installed is pretty bad news, but it seems to be a bit confused itself, since there IS and OS installed, and the phone boots into it.
The phone basically works exactly as you'd expect after the DirtySanta exploit. It can boot into whatever backup I restore it back to, and works just fine, root included. I can also boot into TWRP just fine also..... Its just that within TWRP, if I try to flash anything at all (apps, zip files, kernels) it comes back with an error just after "Updating Partition Details". The specific error is "failed to mount /system (invalid argument)". If I had to guess I'd think that /system was somehow marked as Read Only after I did the restore. I haven't needed to use the button combos for anything since ADB and Fastboot commands all work just fine too.
If I go into the "Mount" section in TWRP "System" is unchecked, if I tap it to try to check it the phone vibrates as if it accepted the input, but the check never appears. If I select "Mount System as Read Only" I can mount it though. I followed the instructions in the DirtySanta thread to a T, and am using all the recommended software versions.
I also tried restoring back to the backup I made just before flashing Konverged Kernel, with similar results. The restore works, and the phone boots into Android, but if I try to pick up where I left off and flash Konverged again from within TWRP, it fails with the "failed to mount /system (invalid argument)" again.
Click to expand...
Click to collapse
I would run the dirtysanta exploit again from the beginning. Your assumption about being stuck in read only seems correct. I'm guessing you might have chosen read only on accident one time when you booted into TWRP and now it's stuck there.
Or you could try using flashfire to flash the TWRP.img

I am having the same issue. I tried doing the DAC mod that enables high impedance as always on. Audio quit working along with the stock music app. Did a restore from after I flashed the konverged kernel. And now no r/w ability and twrp will not mount system unless I check mount as read only. I was able to reinstall supersu from the recovery. But still have the issues.
Only thing I can think of is waiting for a return to stock unrooted method to Come out and re-root.

biglightbt said:
So I would have asked this question directly in the DirtySanta thread, but apparently I don't have enough posts to actually do anything there yet.
So my device is now in a rather bizzare zombie state. I did manage to get my device fully rooted with TWRP installed. Followed the instructions on how to get everything working with no problems. I ended up wanting to try to flash some audio mods (V4A and such), however they did not install properly, so I went and did what anyone else would do - restored to a full backup I made of the device before I started mucking about.
The restore did complete successfully, and I still have a device that has a working recovery, and an OS with root permission...but I can't flash anything anymore from TWRP. TWRP is unable to mount the /system partition after the restore, and seems convinced that I have no OS installed, even though there is one and the phone boots into it just fine. The restore I'm on now is post-flashing the Konverged Kernel. Attempting to restore to an even earlier backup (one I made just before flashing Konverged) produces similar results - the restore succeeds and produces a bootable phone, but TWRP still can't flash anything.
Just to cover bases I also tried running "fastboot flash recovery twrp-3.0.2-1-us996.img" again in case TWRP got messed up (trying to get the "Swipe to allow system changes" prompt to reappear - it didn't), with no changes - TWRP still works fine, but cant mount and edit /system and still claims I have no OS installed when requesting a reboot.
Any advice on how to get things working again would be greatly appreciated! Thanks!
Click to expand...
Click to collapse
Hey I was having the same problem and I fixed it myself messing around with a few things I could think of.
Here it is pasted from another thread.
Dinked around with a few ideas and got my problem fixed! Heres what I did.
1. Made a backup of system in twrp just in case.
2. Formatted system in wipe > advanced > and only checked system.
Panicked because I thought I bricked my device, wouldnt boot farther than the lg logo,
(next steps might be unnecessary but I panicked and tried them lol)
3. still had fastboot access so I repeated step 3 in the root method.
4. Reflashed boot2.img
5. Rebooted to recovery with volume- power, release power while keeping volume- at lg for a second then repress and hold power. Yes twice to get to recovery.
6. Restored system backup. (was able to fully boot now but with lag)
7. Reflashed konverged kernel.
And everything is working perfect now and I have my r/w ability and can mount system in recovery without having to select mount as read only.
---------- Post added at 09:57 AM ---------- Previous post was at 09:10 AM ----------
You can probably just wipe your system like I said in the previous post then Just restore it. I panicked and did a bunch of extra stuff. I realized that when I did my initial backup of my system, or said that its size was about 126247251477482716MB. So I'm guessing when I did my restore (possibly what happened to yours) that it somehow messed up the system.

Won't boot custom ROMs

So far there's only a small sample, but I think there's enough of a pattern to constitute an issue. I've tried to flash the latest of both pixel experience (unofficial) and havoc, and each one sends me directly to either recovery or fastboot, depending on the order which I flash/wipe/factory reset. It's been a couple months since I've flashed anything other than an open beta update, but I never had any issues flashing ROMs.
For both I've tried:
Flash OOS. 9.0.13 (or OB13) in both slots
Flashed Twrp installer
Reboot to recovery
Flash custom ROM
Flash Twrp installer
Factory reset (tried full wipe as well)
It's at this point where I attempt to reboot to recovery to flash gapps (for havoc, not PE) I get sent to recovery or fastboot, depending on whether I reset or wipe data.
I can flash OOS and boot stable or open beta and boot into them with no problems. I've even allowed it to boot to the OOS welcome screen and went back to recovery to flash the custom ROM with the same outcome, doing a factory reset before I flash, after I flash, reboot to recover after flashing to factory reset. I've tried a full wipe in place of factory reset and all different combinations, all with the same result...
What am I missing?

lordcheeto03 said:
What am I missing?
Click to expand...
Click to collapse
I think I've had this issue also--it might be necessary to let the OOS ROM boot up as system--no need to setup the phone, then reboot yourself to TWRP and flash whatever else you want.
It was confusing to me too, and I didn't take notes, so don't know exactly what happened.
Also, maybe don't try to flash things to both partitions--just let the installers do their work as they are made to do without any extra steps.
Since you've already factory reset/wiped, it might help to skip this step also, as a trial.
Did you have Magisk before, and uninstall it first? Might help, as uninstalling restores system images or somesuch.
And, there are some occasions where a ROM flash won't reboot properly without first installing Magisk, but don't recall the incidentals of this either.
Regardless, we'll have a record if you post what steps succeeded in your case.

pbergonzi said:
I think I've had this issue also--it might be necessary to let the OOS ROM boot up as system--no need to setup the phone, then reboot yourself to TWRP and flash whatever else you want.
It was confusing to me too, and I didn't take notes, so don't know exactly what happened.
Also, maybe don't try to flash things to both partitions--just let the installers do their work as they are made to do without any extra steps.
Since you've already factory reset/wiped, it might help to skip this step also, as a trial.
Did you have Magisk before, and uninstall it first? Might help, as uninstalling restores system images or somesuch.
And, there are some occasions where a ROM flash won't reboot properly without first installing Magisk, but don't recall the incidentals of this either.
Regardless, we'll have a record if you post what steps succeeded in your case.
Click to expand...
Click to collapse
Everywhere I've read says to flash OOS to both partitions so if there's an issue with the custom ROM there's a fallback.. I don't flash the custom ROM to both partitions, only OOS. Also, I've tried letting OOS boot to the welcome screen, then back to recovery; I didn't do any setup.
I have magisk installed in OOS, though I haven't tried flashing it when flashing the ROMs. When flashing ROMs I've always flashed the ROM and Twrp, reboot straight to recovery, and flash gapps/Magisk. In my experience, I've been able to skip rebooting back to recovery to flash Magisk and gapps and just boot straight to the barebones ROM.
To reiterate, I use the exact same process to flash OOS and it works flawlessly; can flash the stable or open beta, no issues. It's only non-OOS that refuses to work correctly.
I'm wondering if I need to use the unbrick tool and start from a 100% clean slate .. something may be borked that an unbrick may fix, it's about the only option left that I can think of...

lordcheeto03 said:
Everywhere I've read
Click to expand...
Click to collapse
Good luck whatever you do.

pbergonzi said:
Good luck whatever you do.
Click to expand...
Click to collapse
Thank you for the ideas

I ran the unbrick tool and still encountered the issues, but I did learn something, and also finally got havoc to boot, although I'm still unsure exactly what I did. I'm not saying I figured out exactly what is wrong, and I can't say I know the exact solution, but I CAN say I believe the solution lies somewhere within this wall I'm typing.,..
I noticed this earlier but it didn't actually click until I still got the same error after the unbrick tool... I would always boot correctly to OOS on slot b, so after every successful boot, I'd go into recovery and try flashing.. now taking into account the fact that I flashed OOS in both slots is important because on a successful boot, which would be slot b, I'd go into recovery, still on slot b, so that's the first slot to get OOS. Change slots, flash to slot a, then boot to OOS. If I'm remembering how a/b partitions go, since slot A was the last slot to flash, it would automatically fall back to slot b to boot. Hence the successful boot. Go back to recovery, flash havoc on b, it would attempt to boot from a, and fail.. go back to recovery, I'm back on slot b to start the process over.
After still encountering the problem after the unbrick, I really began paying attention to the boot slots. Once I was paying attention to that, I attempted to manually boot from slot a after flashing OOS to both slots and I got sent to a screen that says Qualcomm crashdump mode. Power +vol up/dn to force a reboot, then volume down until the bootloader unlocked splash screen to go to recovery.
Now this is what I think I did... After figuring out it was the slot, I believe I formatted slot a, and due to the way it fell, slot b then began being the slot to mess up so i made sure to flash havoc/twrp installer in the slot a and it booted right up. Went back to recovery to flash magisk and gapps, and finally a factory reset. Boot from slot a, and here I am.
There were times where I would get stuck in fastboot, boot to recovery or system would just send me to fastboot.. I guess that also meant I was booting from the bad slot. I tried fastboot boot twrp.img, it would send it, but fail to authenticate. Fixed that by doing fastboot --set-active=b then I could restart back to recovery no problem.