Hello all,
I own a VS995 LG V20, which I rooted a few months back, and it was working fine, until I very recently switched to T-Mobile. I had some issues with the 4G LTE and after doing a lot of research I read the best solution was to flash a US996 ROM, so that's what I did. I flashed the NotSoStock US996 ROM+Kernel
Good news, the phone boots up, everything works, 4G LTE works...yay....
Bad news.... whenever I try to enter TWRP, it loops on the TWRP boot screen until I remove the battery and boot the phone normally...
I guess this is a reverse TWRP boot loop? :s
I discovered this today when I attempted to boot into TWRP to flash a new kernel to stop the ugly static boot screen thing.
I have tried flashing the latest version of TWRP (both VS995 and US996) to no avail, along with attempting to flash my TWRP backup I made when I initially rooted my phone and the one I made before flashing with the 996 rom. :\
This currently isn't a huge dilemma as my phone boots normally just fine, but I am really scared that if something happens, I am unable to enter TWRP to fix any issues. Does anyone know how to fix this? I would really appreciate any insight into the matter.
Related
I do not know if this question has been brought up before, but I am in desperate need of an answer. I recently got my 6P and immediately proceeded to unlock the bootloader and flash TWRP to start loading custom roms. I decided to start use Pure Nexus with it's accompanying gapps package but when I go to reboot the device, I am stuck at the circles boot animation. I decide to try CM13 nightlies and the same problem occurs. After searching online for some time, I realize I needed to flash a SuperSU file from recovery that flashes a custom boot.img. I flash Version 2.66 and restart the device. After 5+ minutes on the boot screen, I decided I am stuck still. What do I need to do, I am unable to boot the device.
Thanks.
I'd use Nexus Root Toolkit to unbrick your phone just so that it is working to start with. Then follow the steps more closely for installing a rom. You'll be doing something wrong, I've had no issues!! Best of luck with this.
hmm I'm not sure. this is happening to me right now as I try to restore my backups... maybe has to do with twrp's system handling/mounting, but I just don't know.
My previous V20 died of a NAND issue and I liked it so much I got another one. I followed the DirtySanta guide, then installed the Alpha Omega Oreo ROM following the directions on the post. After a while, the ROM became very unstable and slow and laggy, so I wanted to go flash the ResurrectionRemix SSDev build that was released recently. I flashed it, only to discover it didn't work. I figured it was because of AO's total flashing of the system, giving it a new bootloader and such. The only way I could think of getting the Nougat aboot back was to flash to stock, do the DirtySanta process again, and install the ROM. I was able to flash the stock image (VS995 12A) and it went fine, until the phone booted. Once it boots, it just says "Settings has stopped" and that message keeps reappearing instantly after dismissing the previous message. I've tried flashing three different VS995 images, and even a US996 image, but they all have this issue. Did I get yet another phone with a NAND issue, or am I just missing something?
It may be necessary to go in to recovery and wipe every thing......no guaranty.
stinka318 said:
It may be necessary to go in to recovery and wipe every thing......no guaranty.
Click to expand...
Click to collapse
For some reason I couldn't enter the recovery on any of the VS995 images, but it worked on the US996 image. I decided to stay with the US996 image, so now my phone is a US996 on VS995 hardware. Oh well, it fixed the obnoxious vibrating on boot. Thanks for the suggestion.
It's been a while since I unlocked my mobile's bootloader, following the steps of a you tube video specifically from the Tecnocat channel. Everything was going well until I thought I did not have any system because whenever I started it it went straight to recovery. Install roms and the same. Until I decided to go directly to the bootloader and start it from there. Of surprise it worked, there was no problem with the system. Everything works fine, but every time I turn off the phone and turn it on it starts in recovery and I have to boot it in fasboot mode and from there start the system. It's tedious, and for example I can not do restarts. I already reprimand the recovery from different sources, and I can not find a solution. Please help
Similar issue
I'm having a similar issue except mine started after mistakenly installing a OTA update (Sept. I think) on a xt1687. Rooted (magisk) with TWRP recovery on stock ROM. Every time I boot it goes into recovery mode, and the only way to get into the phone is through TWRP Reboot > Bootloader, then Start.
I tried flashing the latest stock ROM I could find, but still have the same issue. Only now I'm getting nagged with Install System Update New Version NPNS25.137-93-18. I know better now to follow the OTA update guides, but how do I get the phone back to the way it was before the update? Any help is greatly appreciated. Thanks in advance!
I am puzzled by what's happening...
We got a new Moto G7 for my wife and following the instructions here https://www.the***********.com/install-twrp-root-moto-g7-plus-guide/, I successfully rooted the phone. However, there was a security update that needed to be installed, so with some great advice from ptn107, see https://forum.xda-developers.com/mo...-trying-to-t3977463/post80429619#post80429619, I flashed the updated ROM onto the phone. (Note that I omitted 'fastboot erase userdata'. Also note that the warning message 'is-logical:<partition>: not found' was seen for all flash commands.)
The phone booted properly after the update, so I then went through the exact same rooting steps that had worked previously. However, this time, the phone gets stuck in a boot loop. I reflashed the ROM and can boot successfully, but the phone is no longer rooted. (I have tried this twice, with Magisk 19.3 and 19.4 - same result.)
Any ideas as to what I may be doing incorrectly? More importantly, what is the best way forward?
Thanks.
im dealing with the same issue. you can flash TWRP and go to advanced, fix boot loop, and that should get it to boot, but then you lose Magisk. May be a verity / checksum issue with the stock ROM. probably an easy fix but I dont have it.
EDIT: also you can flash the stock boot.img back and that will do the same thing, but again you lose Magisk/Root.
Hello,
i got a second phone for my GF as i was really happy with this phone and had it flashed without any issues before. This second phone is used and was over a year in use from the guy i've bought it from. It was 100% fine and he always used the shipped Android with it.
So i went on, got the latest TWRP for the phone. Flashed it without any issues and tried to install LineageOS from their website. Flashed it and tried to flash TWRP back as LOS replaces it. I wanted to use TWRP install the backups. But that's where it started to go wrong. Lineage seemed to have been gone from that point on. I couldn't get it to work again, even with reflashing and such. I've downloaded CRDroid and Paranoid and tried them but no luck. Non of them where booting up and TWRP stays showing a warning about "No OS installed".
After some more digging, i've found some posts stating that i would need newest firmware and venders. I've downloaded and flashed them but this made it even worse. The phone started to be stuck in fastboot. I got it working again by flashing latest MIUI version with Xiaomi Flash Tool.
Then i've installed TWRP again but somehow any rom i flash does not boot. The phone starts with the MI logo and flashes once and loads TWRP. There is no message about missing OS or any kind or error when flashing any of these roms.
Anyone able to help me?