Moto g4 xt1622 - twrp bootloop - Moto G4 Plus Questions & Answers

Okay Guys, Here is my problem,
I have a standard MOTO G4 and installed 9.0 Arrow ROM, it randomly started booting off etc. So i flashed my backup from stock rom (which has root and Xposed) and kept getting error 255, this wasnt successful, however i tried every single trick in the book and randomly made it work. The problem is, everytime I shut down my phone and want to start it again, I have to go to bootloader every single time, the power button takes me to TWRP. Can someone give me a solution or at least some feedback on what to do?
Thanks

Related

Moto X Pure stays on the M. No starts, no enters in Recovery Mode. ROM AICP

Hello Folks, I have an issue here. I have a Moto X Pure (XT1575). I'm using ROM AICP. Was running fine, no big bugs but this morning it got frozen so I rebooted by pressing Power Button for some seconds. Now it doesn't start, it stays on the M. Also doesn't enter into Recovery Mode. Any ideas?
Thank you!
Sad to say I had the same thing happen to me yesterday! I tried many things and searched for hours for a fix. I think I was on AICP 5-16. Finally had to restore to stock via fastboot. It wiped internal data and I had to reflash twrp recovery and rom. I was super bummed abut it but didn't have much choice. I hope you find a less invasive fix!
Problem solved
Hey, Folks, I could be able to "fix" my Moto X Pure XT1575 following this post: http://rootmygalaxy.net/how-to-unroot-unbrick-moto-x-pure-edition-2015/
Basically, I restarted all the process from the beginning.
I don't know who is the guy of the posting, but anyway, thanks a lot!

Nexus 6P stopped booting, nothing I do is now working. PLEASE HELP ME.

At this point I have completely run out of options. I AM CALLING UPON THE XDA COMMUNITY TO PLEASE HELP ME. Little bit of background info, nexus 6p was rooted and modified through xposed. Had some modules installed, mostly quality of life and visual/theme modules, as well as the latest version of SuperSU.
These past few days my Nexus 6P has completely stopped responding at times. Extremely laggy and could not do **** with it, systemui kept restarting over and over and over again for no reason. Had to keep force rebooting (holding down the power button for 10 seconds) multiple times over and over again, to the point where it suddenly stopped booting into the OS, it just kept giving me the boot animation loop, i could only access the TWRP recovery i had installed. Before all of this **** went down, I had created a TWRP backup because it would be my safety net if i could somehow miraculously get it to work. Now i have a backup of my TWRP BACKUP FILE on my desktop.
I have wiped caches more times than i can count, have tried factory restoring and formatted the data, and tried flashing the stock google image (the same one that i originally flashed at the time that I got the phone when i started to root) as well as flashed the old TWRP version i had, as well as the current latest version of TWRP, and then transferred the backup i made back onto the phone's internal storage. Tried restoring the old backup from TWRP, and each time it restores, it just reboots without reaching 100% and once it reboots, it still gives me a bootloop, this time, no boot animation, it just gets stuck at the Google text with a little "unlocked" logo at the bottom. I have completely run out of options, and have A LOT of EXTREMELY IMPORTANT information i have saved on the phone.
I will say it again. I am EXTREMELY DESPERATE to get my data back, to the point where i am even willing to offer a cash reward for any help to get my phone working back to the way it used to, or even at least to extract the information through the backup, if at all possible.
Additional information about the files and images I used:
angler-mdb08k is the name of the google image i had back when i had the phone and have flashed again
twrp-2.8.7.2-angler is the TWRP version i had back when i had the phone originally at the time
I had flashed and followed guides online through adb method.

Problems after installing ELEMENTAL V2

Hello . I have a problem with my WAS-LX1. I unlocked the bootloader. I installed the TWRP red version from KingOfMezi. I wipe all the data exactly as in the video. I flashed Elemental V2. I chose the LX1 smell and the rest just like in the movie. I get the OK message. After my restart my phone restarts again, and after the second restart I go into android, I choose the wifi network and after about 1 minute it restarts again. After another minute restart. And so to the end. Right now I have the original WAS-LX1C432B204 software on it. can somebody help me please. :crying:
Elemental V2 ater B204
Do you think it does matter if I install Elemental V2 after B204 or after B182. I still wonder why the phone restarts at approximately 1 minute intervals. I want to abstain from those I do not know for sure, because I've been tired of how many times I've tried with harsh advice.

YU YUREKA AO5510 random bootloop

Hey,
I have been using the ColtOS rom based on Oreo 8.1.0 for quite sometime now. I had it rooted with Magisk too. I have the latest version of TWRP installed (version 3.3.0). I had no problem until now where it just randomly tried to reboot after I ended a call. It did reboot fine once, but it was when i ended a second call that it got stuck in a bootloop.
I have tried everything, clearing the cache/Dalvik , wipe data and system and flashed three different Oreo ROMs, uninstalling Magisk. However, I can only go as far as the set-up screen after the new ROM boots, after which it goes back to rebooting itself endlessly.
I seem to have exhausted all my options, any kind of help to restore my phone will be greatly appreciated.
Thank you.
I have found out that I can flash new ROM and even set up the phone by logging into Google, only when I connect my phone to my laptop. It even installs all the previous apps and data and thats it. It reboots to the lockscreen and when I try to unlock it, it reboots again. And this is all only when I keep the phone connected to my laptop, otherwise,it keeps looping into the bootscreen logo.
AndroGuy18 said:
Hey,
I have been using the ColtOS rom based on Oreo 8.1.0 for quite sometime now. I had it rooted with Magisk too. I have the latest version of TWRP installed (version 3.3.0). I had no problem until now where it just randomly tried to reboot after I ended a call. It did reboot fine once, but it was when i ended a second call that it got stuck in a bootloop.
I have tried everything, clearing the cache/Dalvik , wipe data and system and flashed three different Oreo ROMs, uninstalling Magisk. However, I can only go as far as the set-up screen after the new ROM boots, after which it goes back to rebooting itself endlessly.
I seem to have exhausted all my options, any kind of help to restore my phone will be greatly appreciated.
Thank you.
I have found out that I can flash new ROM and even set up the phone by logging into Google, only when I connect my phone to my laptop. It even installs all the previous apps and data and thats it. It reboots to the lockscreen and when I try to unlock it, it reboots again. And this is all only when I keep the phone connected to my laptop, otherwise,it keeps looping into the bootscreen logo.
Click to expand...
Click to collapse
Flash crdroid nougat

SM-P580 blackscreen problem

So tl;dr version - i was using my tablet, saw an update to magisk, installed it, now it boots to black screen while running sambones rom
[SM-P580] [BQK1] SaMBoNeS
TWRP 3.2.3.0 --> 3.3.1.0
longer story:
i was trying to get a game to run, it wasnt...and realized it has been a while for a restart, so i checked to see if anything needs to be updated and saw magisk needed an update. i didnt note what version it was before but it was a version or two earlier than what it was trying to install.
rebooted to blackscreen no samsung logo
have tried restarting a dozen times, booted to TWRP, tried to force normal system boot through the UI, nothing.
I tried installing a new kernal [SiriKernel], it made it to the samsung logo, waited 15 - 20 minutes and it never made it past. restored a backup using TWRP
updated TWRP to 3.3.1.0, still no luck.
i had this problem a long time ago, and cannot figure out how i fixed it....it may have fixed itself but it isnt this time. any advice would be appreciated. I am trying to avoid wiping and starting again if at all possible because the problem seems familiar. also trying to stick to a rom for use with adaptive storage. if i do have to wipe if that can be done on a newer stock OS that's fine as well but last time i messed with this tablet it wasnt

Categories

Resources