ok, here is what happened. im running fulmics rom on lg g3 vs985w, i tried to encrypt my phone for some oddly stupid reason...
well it never got past 0% it sat for hours, so i booted to twrp and wiped everything and flashed fulmics rom
it goes through the whole installation process and when it reboots it goes to right back to the encryption unsuccessful screen
*************************PLEASE*************HELP***************
Related
Hi, I rooted my galaxy s7 from att using this method, https://www.youtube.com/watch?v=GNInTlCpv8E
It worked perfectly and I had my new rooted phone! So a couple of days after the root one of my apps stop working and I cannot get it to start working, it was a pushup workout app, so I restart my phone and it gets into a boot loop stuck on the at&t logo. I was very sad as I did not back anything up so I wiped my phone using the recovery boot and signed in and re-flashed the root rom through odin and re-installed supersu and it worked perfectly again. The next day I have the same problem but this time with snapchat and instagram so I knew what was going to happen and I restarted and it did the same thing. This time when I went into recovery boot I noticed "dm-verity verification failed" in red at the bottom. As of now I am just going to do what I did last time and wipe and re-flash as I made a backup this time and just restore my phone and hope it doesn't happen again. If someone could please explain why this is happening and maybe help me fix it I would be so happy thank you!
UPDATE 7/26/16: I re flashed the ap root file with odin without doing a factory reset and it is still stuck in a boot loop, meaning I have to do a factory reset to get it out.
Mine is doing same thing. I used chain fires root. Everything went perfect. Then couple days later apps started saying they had stopped and phone started freezing. Every app I tired to open would say they had stopped. Then it constantly kept saying Google play services had stopped. I tried to reboot and stuck into bootloop everytime. Rooted again same thing happened again. U ever find a fix or anyone no how to fix this
My G3 recently started having issues with WiFi disconnecting and not showing any available networks. This went on for a few weeks, then the phone started to restart itself occaisionally. Now it will not boot, shows the lg screen for a few seconds and restarts. During all this I tried several different ROMs, original ROM when this all started was XDABBEB's 3.1.1. Also tried XDABBEB's 47a Stock ROM and RR Rom. Nothing has worked so I read it might be the battery, ordered a new one that did not help. Is my phone dead or is there a possible fix, thank you for any suggestions.
So, to begin with, yesterday Mi A1 got the Android 9 update. As I always do, I went to uptade it with Magisk (it worked with 8.0 to 8.1 and with every security patch, so I, as a newbie, thought, "why the h3ll not?"). Obviously, it didn't work and I got into a boot loop. So, here are the [lot] of things I have tried to do.
-Downloaded MiFlash and the latest OS version from Xiaomi site (8.1 witch november patch). Tried flashing a lot of times, I always get the boot loop after installing it. Wiped all data with TWRP and still didn't work. Always the same problem. Tried with different versions as well.
-Downloaded latest AOSP ROM for the device, flashed it, wiped cache and data, instaled TWRP (3.2.3-0), but the system never initiates. Doesn't even restart (20 minutes after my last try and it still is in a black screen).
-I've tried the same thing with Lineage 15.1 as well. Checked with MD5 in both roms. Doesn't work at all. Followed every tutorial I could, step by step, don't know what I'm doing wrong.
Can any one please help me? I don't know what to do anymore.
EDIT 1: So, I thought nothing happened, but after installing AOSP, I rebootet the phone holding the power buton, and during boot, I can see the "Powered by Android" from the custom ROM for a few seconds, but then the screed turns black and nothing more happens.
I woke up with a black screen and unresponsive I soft reset and booted back up just fine, fast forward 2 days, apps are constantly crashing and often seemingly randomly the phone will restart and go into a bootloop anywhere from 1-5 minutes before it finally boots. Sometimes I get lucky and can use my device just fine for a few hours, then apps will crash and stuck back in bootloop.
I have factory reset in recovery, and also flashed latest stock rom via odin, I am new to this and this was my first time I might add, it passed but it hasn't resolved the issue, is there anymore steps with odin or anything else I can do to repair this? The device isn't rooted if that helps.
I think that's a motherboard issue
You could try installing a custom rom
I flashed a Redmi 5 plus with lineage 17 successfully then i rooted it. I wanted to install Revolut and other banking apps but they don't work with root so tried to unroot but was not possible as it got corrupted so reflashed it back to stock rom android 8.1 and worked fine.
I tried again to flash Lineage 17, 16 and also Paranoid Android but each time I boot put the screen turns off. The boot seems to start up but the screen is off.
I reflashed it back to stock rom and it gave me an error on startup saying "Find Device Storage Corrupted, Your Device is Unsafe Now" and keeps rebooting.
Any clues?
berex said:
I flashed a Redmi 5 plus with lineage 17 successfully then i rooted it. I wanted to install Revolut and other banking apps but they don't work with root so tried to unroot but was not possible as it got corrupted so reflashed it back to stock rom android 8.1 and worked fine.
I tried again to flash Lineage 17, 16 and also Paranoid Android but each time I boot put the screen turns off. The boot seems to start up but the screen is off.
I reflashed it back to stock rom and it gave me an error on startup saying "Find Device Storage Corrupted, Your Device is Unsafe Now" and keeps rebooting.
Any clues?
Click to expand...
Click to collapse
Have the same problem with my 5 plus, just keeps rebooting, also when the charger is not plugged it just shutdown before booting to bootanimation. Do you already solve yours? Can you help me?