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!!
Related
hi. It was everything fine for me. rooter v20b, cwm installed and working.. but i wanted to reboot my phone and after it, it won't boot up. lg logo shows up and screen goes black for ever. I can't restore or anything but i can load into cwm restore. i can even full wipe to back into phone. any suggestions?
Muphet said:
hi. It was everything fine for me. rooter v20b, cwm installed and working.. but i wanted to reboot my phone and after it, it won't boot up. lg logo shows up and screen goes black for ever. I can't restore or anything but i can load into cwm restore. i can even full wipe to back into phone. any suggestions?
Click to expand...
Click to collapse
Hello Buddy,
Just Factory Reset your device from CWM, it will solve your problem. If it doesn't work then reflash ROM...
before posting please completely read related thread carefully.
Hey guys,
I was just wondering what the general consensus is on which recovery is the most preferred.
I was using TWRP 2.6, but that gave me problems (being stuck on samsung logo everytime my phone rebooted). Reverted back to 2.5.0.2 and it seems to work fine so far. I did try CWM in the past but for some reason my boot loader would get locked and I would have to ODIN back to stock.
So what's your preferred recovery and why?
Thanks.
Exodus885 said:
Hey guys,
I was just wondering what the general consensus is on which recovery is the most preferred.
I was using TWRP 2.6, but that gave me problems (being stuck on samsung logo everytime my phone rebooted). Reverted back to 2.5.0.2 and it seems to work fine so far. I did try CWM in the past but for some reason my boot loader would get locked and I would have to ODIN back to stock.
So what's your preferred recovery and why?
Thanks.
Click to expand...
Click to collapse
I like TWRP. It works well with the new phone and Roms that are coming out plus it is so easy to use. Never liked CWM very much. You did right by reverting to an older version of TWRP I had to do that once.
TWRP... i don't even consider anything else.
Do you guys know why my phone gets stuck on the samsung logo everytime i restart my phone?
Doesn't matter what ROM i use it always happens....
Did you do a factory reset, system wipe, preload wipe, cache wipe, and dalvik wipe? Or try fix permissions from recovery?
If not, go do all of those.
If that doesn't work, something is missing from the system partition that is keeping it from booting. Which means you deleted it. :good:
Dubbsy said:
Did you do a factory reset, system wipe, preload wipe, cache wipe, and dalvik wipe? Or try fix permissions from recovery?
If not, go do all of those.
If that doesn't work, something is missing from the system partition that is keeping it from booting. Which means you deleted it. :good:
Click to expand...
Click to collapse
I did ALL of those, still have the problem.
So.... I just ODIN-ed back to stock and going to root and basically re-do everything -_-
So I have been following the unofficial cm-10.2 ROM. I have dirty flashed probably 3 times without issue. I flash the ROM, a pinlock removal zip and gapps. Then wipe dalvik/cache and reboot. I started doing this with twrp 2.6.
So this morning I grab the latest update, backup, flash.l, reboot.... nothing.
Stuck at LG logo to a black screen. I can get into bootloader, blindly vol down twice and into recovery, now twrp 2.5, so I try to recover by backup, reboot.... black screen.
So I try wiping/factory reset, clean flash, reboot.... black screen...
Now I am a little concerned. I read up and find out about TeenyBin, so I setup my machine to flash the standard zip and that doesn't really work, it flashes fine, reboots but is stuck at LG logo and the tool reports disconnected, so the tool fails kind of. So I try the alternate, same sort of thing, but now it says Google instead of LG and is stuck there. I can get into bootloader, can see text now (nice!) and get into recovery, still 2.5. Tried restoring, wiping/flashing, nothing working..... stuck at Google logo.
So, then I went and formatted internal storage. Bingo! Now I can flash/restore/whatever and I can reboot and get into ROM!
Woah, woah, woah... Not so fast.
So now if I wipe anything, cache/dalvik/system/ANYTHING it soft bricks. I have to again format internal, then flash. That doesn't seem right to me. Sure, I have a functioning phone, but updating is a bigger ***** now that I have to completely format before flashing.
So my question to you all, how do I fix this? Do I need to completely go back to stock image and reroot? I appreciate all your suggestions.
daveerickson said:
So I have been following the unofficial cm-10.2 ROM. I have dirty flashed probably 3 times without issue. I flash the ROM, a pinlock removal zip and gapps. Then wipe dalvik/cache and reboot. I started doing this with twrp 2.6.
So this morning I grab the latest update, backup, flash.l, reboot.... nothing.
Stuck at LG logo to a black screen. I can get into bootloader, blindly vol down twice and into recovery, now twrp 2.5, so I try to recover by backup, reboot.... black screen.
So I try wiping/factory reset, clean flash, reboot.... black screen...
Now I am a little concerned. I read up and find out about tinyrom, so I setup my machine to flash the standard zip and that doesn't really work, it flashes fine, reboots but is stuck at LG logo and the tool reports disconnected, so the tool fails kind of. So I try the alternate, same sort of thing, but now it says Google instead of LG and is stuck there. I can get into bootloader, can see text now (nice!) and get into recovery, still 2.5. Tried restoring, wiping/flashing, nothing working..... stuck at Google logo.
So, then I went and formatted internal storage. Bingo! Now I can flash/restore/whatever and I can reboot and get into ROM!
Woah, woah, woah... Not so fast.
So now if I wipe anything, cache/dalvik/system/ANYTHING it soft bricks. I have to again format internal, then flash. That doesn't seem right to me. Sure, I have a functioning phone, but updating is a bigger ***** now that I have to completely format before flashing.
So my question to you all, how do I fix this? Do I need to completely go back to stock image and reroot? I appreciate all your suggestions.
Click to expand...
Click to collapse
Give CWM a shot and see if it does the same thing?
well I was flashing MIUI V5 UNIVERSAL - v. 3.7.12 for the 3vo and it got stuck in a bootloop. to try and fix it I tried to restore a backup and that rom played a little of the boot animation but then gets stuck in a bootloop. I also tried to wipe/format everything but, that didn't work. If a logcat would help i would appreciate a link on how to do that without being able to boot. I can boot to 4ext recovery. The cause could be that while flashing I selected the file to flash, I selected a file that didn't finish downloading. Thanks in advance for any help
Also if it matters my original rom was negalite blurom.
cdog1213 said:
well I was flashing MIUI V5 UNIVERSAL - v. 3.7.12 for the 3vo and it got stuck in a bootloop. to try and fix it I tried to restore a backup and that rom played a little of the boot animation but then gets stuck in a bootloop. I also tried to wipe/format everything but, that didn't work. If a logcat would help i would appreciate a link on how to do that without being able to boot. I can boot to 4ext recovery. The cause could be that while flashing I selected the file to flash, I selected a file that didn't finish downloading. Thanks in advance for any help
Also if it matters my original rom was negalite blurom.
Click to expand...
Click to collapse
I ran into your same problem today.
At the time my phone was on latest sprint firmware, ICS coolrom (latest rom and kernel) with hboot 1.58 unlocked s-off.
The steps I did preparing to install MIUI was
1) wipe data/factory reset from 4EXT
2) format all (except sdcard)
3) Install MIUI > chose mirage kernal
4) rebooted
after reboot it was stuck at the logo, at least I thought it was, let it sit for about 5 minutes.
Pulled the battery and tried steps 1-4 again.
Kept getting bootloop at that point. Boot splash -> logo -> reboot.
Next I tried flashing the latest mirage kernel from 4ext.
No luck, same issue.
Tried repeating steps 1-4 again.
No luck stuck in bootloop.
At that point I tried to run recovery from a backup I knew was working.
Wiped all data and format all -> selected recovery from 4ext.
Result: still boot loop.
At that point I tried changing bootloader to 1.58.58 jbear. and wiping/formatting all and trying recovery again from known working cool ics backup.
Result: still bootloop.
Switched back to 1.58 bootloader and tried fresh install of CoolICS rom. (I always wipe all data and format all before any rom change.)
Result: still bootloop.
At this point I was getting frustrated but I had an idea that the MIUI install when selecting mirage kernel may have messed up the partition size for the kernel since the mirage kernel states it must be flashed from the flash gui app first to resize the boot partition.
Next I downloaded pacman rom and attempted that install.
result: could not install due to wrong bootloader.
Next I downgraded bootloader to 1.50.50 jbear.
Wiped everything and retried pacman rom.
Install success, before starting the reboot from recovery, I received a message that the boot image has changed and will make a backup/format/flash the new boot image.
upon reboot I was able to successfully boot into pacman rom.
At that point I tried to wipe all again and install CoolICS rom again.
result: bootloop, but probably because of bootloader version. Did not fully test it as at this point I just wanted a working phone again and wanted to try out MIUI.
Rebooted to recovery and wiped everything again.
Installed MIUI using stock kernel option. This time on reboot I let it sit at the rom logo without touching anything. I think it restarted once on its own.
Result: Success. Phone working normally now. such a headache I am just leaving it as is for now.
Jeffjb said:
I ran into your same problem today.
At the time my phone was on latest sprint firmware, ICS coolrom (latest rom and kernel) with hboot 1.58 unlocked s-off.
The steps I did preparing to install MIUI was
1) wipe data/factory reset from 4EXT
2) format all (except sdcard)
3) Install MIUI > chose mirage kernal
4) rebooted
after reboot it was stuck at the logo, at least I thought it was, let it sit for about 5 minutes.
Pulled the battery and tried steps 1-4 again.
Kept getting bootloop at that point. Boot splash -> logo -> reboot.
Next I tried flashing the latest mirage kernel from 4ext.
No luck, same issue.
Tried repeating steps 1-4 again.
No luck stuck in bootloop.
At that point I tried to run recovery from a backup I knew was working.
Wiped all data and format all -> selected recovery from 4ext.
Result: still boot loop.
At that point I tried changing bootloader to 1.58.58 jbear. and wiping/formatting all and trying recovery again from known working cool ics backup.
Result: still bootloop.
Switched back to 1.58 bootloader and tried fresh install of CoolICS rom. (I always wipe all data and format all before any rom change.)
Result: still bootloop.
At this point I was getting frustrated but I had an idea that the MIUI install when selecting mirage kernel may have messed up the partition size for the kernel since the mirage kernel states it must be flashed from the flash gui app first to resize the boot partition.
Next I downloaded pacman rom and attempted that install.
result: could not install due to wrong bootloader.
Next I downgraded bootloader to 1.50.50 jbear.
Wiped everything and retried pacman rom.
Install success, before starting the reboot from recovery, I received a message that the boot image has changed and will make a backup/format/flash the new boot image.
upon reboot I was able to successfully boot into pacman rom.
At that point I tried to wipe all again and install CoolICS rom again.
result: bootloop, but probably because of bootloader version. Did not fully test it as at this point I just wanted a working phone again and wanted to try out MIUI.
Rebooted to recovery and wiped everything again.
Installed MIUI using stock kernel option. This time on reboot I let it sit at the rom logo without touching anything. I think it restarted once on its own.
Result: Success. Phone working normally now. such a headache I am just leaving it as is for now.
Click to expand...
Click to collapse
well I went to go try and boot P.A.C. and my phone just booted normally. So thanks for the help
Phone is a frankensteined LG V30, 931, I installed Lineage on it following the correct steps for prepping the phone for an AOSP rom.
I had some issues with Lineage and decided to restore from backup, but when I restored my phone it hung on the splash screen permanently. I factory data reset, no good, still hung.
Wiped everything in TWRP and flashed US990_H, booted up okay but now I'm bootlooping.
Went back into TWRP and wiped data, restored from my backup, rebooted, still bootlooping.
Went back into TWRP, wiped everything and flashed US998E, F, G, H in order, rebooted, still bootlooping.
I'm out of ideas.
oblivion2k said:
Phone is a frankensteined LG V30, 931, I installed Lineage on it following the correct steps for prepping the phone for an AOSP rom.
I had some issues with Lineage and decided to restore from backup, but when I restored my phone it hung on the splash screen permanently. I factory data reset, no good, still hung.
Wiped everything in TWRP and flashed US990_H, booted up okay but now I'm bootlooping.
Went back into TWRP and wiped data, restored from my backup, rebooted, still bootlooping.
Went back into TWRP, wiped everything and flashed US998E, F, G, H in order, rebooted, still bootlooping.
I'm out of ideas.
Click to expand...
Click to collapse
What TWRP are you running? 3.2.3.7 stable from WTF?
What Magisk are you on? 19.x doesn't work well flashing TWRP flashable zips. Boot back into TWRP, uninstall Magisk and install 18.0 or 18.1.
See if that works.
____
Worst comes to worst, you can go into Download mode, flash 20H in Refurbish mode. You're back on pure stock, but still have unlocked bootloader with fastboot flash commands. Reinstall TWRP, flash the three root files again (no encryption, no root check, Magisk).
But then you'll have to manually install some stuff Johnfawkes puts in his TWRP-flashable zips.
ChazzMatt said:
What TWRP are you running? 3.2.3.7 stable from WTF?
What Magisk are you on? 19.x doesn't work well flashing TWRP flashable zips. Boot back into TWRP, uninstall Magisk and install 18.0 or 18.1.
See if that works.
____
Worst comes to worst, you can go into Download mode, flash 20H in Refurbish mode. You're back on pure stock, but still have unlocked bootloader with fastboot flash commands. Reinstall TWRP, flash the three root files again (no encryption, no root check, Magisk).
But then you'll have to manually install some stuff Johnfawkes puts in his TWRP-flashable zips.
Click to expand...
Click to collapse
I was on 3.2.3.7 from WTF, yes, and 19.x, that must have been my problem. I having the idea to refurbish flash 20H myself, and did that successfully. Going to go ahead and get started on installing the other files now. And doing a full system-image TWRP backup to prevent this from happening in the future.
Out of curiosity, what does Magisk do that causes this to happen? I would have thought that once I wiped the system and data partitions magisk would be gone completely.
i have a similar issue going on here and i'm stuck. bootlooping directly back to TWRP regardless of command (bootloader, power off, system). i believe i took all the right steps in WTF thread (unlocked, rooted, updated to latest H FW) then tried to flash lineageOS. even my sequential (unlock, root, update) TWRPs wont boot (they restore properly it just boots back to TWRP). i tried reflashing E,F,G,H no go.
US998, used proper 3.2.3.7 TWRP, Magisk18.
i've been flashing phones for years and this one has been difficult. any help?
EDIT: it seems the aroma installers of gapps was crashing TWRP. i was finally able to get back into bootloader and upon re-flashing TWRP everything seems back to normal. i can also recreate the problem so its def a gapps/TWRP no likey situation.
I think I ran into that once, and I powered-off fully and booted manually and it worked... you could try that. I may have even tried booting into bootloader or something, and then that fixed it too? I forget exactly, but it wasn't too big of a deal, once I got it solved, of course!