Hi all
I was wondering if anyone can help or suggest a way around this.
See image below. I was updating lineage 17.1 to latest as I've done numerous times before and this happened. I always used twrp so I don't know how this happened.
Thanks
Related
Hey guys,
I was running a old version of android (6.0.1) and wanted to upgrade my rooted phone today. Decided to try out Oreo, followed a guide that involved using fastbooting various files (bootloader, radio, boot, system, vendor). I got no errors along the way. My phone went past the android logo once and "optimized" my apps, restarted and was stuck loading the android logo. It now just keeps trying to load the android logo and reboots into TWRP recovery. After recovering, I am now stuck on the Google image while booting up.
Does anyone have any tips? Can I just try flashing a older version of android? Or is there a better way to fix this problem. Any help is appreciated and thanks in advance!
Edit: Was able to fix my issue. For anyone who is having similar problems, follow step 9 from Heisenberg's guide. Since I was updating from such an old version, a lot of the programs were incompatible with the newer android version and causing issues.
Hello,
I have an odd problem I need to iron out. . . Recently I installed the NeculaROM mostly without a hitch, however I was having issues not being able to make outgoing calls, so I wanted to switch back to my old Rom. Normally this wouldn't be an issue however when attempting to wipe anything on the phone, it starts vibrating and shuts off in TWRP. I can flash things fine still, back things up, yada yada. I tried reflashing TWRP, and that didn't help either.
So now I am stuck on this rom, and I can't do anything in TWRP. Is there any way to fix this? I can't seem to find much information on this particular issue. Any help would be great.
Thanks!
I believe this is caused by f2fs changes with rebasing this device to nougat.
Have you tried using the TWRP linked to the OP of the NucleaROM thread? You might have to format internal storage to get things working right again.
If that doesn't work out for you I'd recommend searching around more recent discussions in the TWRP thread and LineageOS thread. These issues with wiping and differences between unofficial TWRP, official TWRP, and what works with what ROM/firmware combinations have been covered in both.
Sorry I'm not more help on exactly what to do. I've just stuck with marshmallow firmware and custom roms based on it. I'm waiting for the dust to settle on this nougat rebase business.
Had same issue. I ended up just reflashing all the firmware images. Fixed my problem (for the most part.)
Hey everybody, I need help. I have a J320P that is stuck in a boot loop, when it was found like this by my friend they came to me and asked if I could help. I have no information on how this happened other than they took a shower and when they came back it was like this. I have tried installing stock firmware 3 times to no luck. I might have an sd card somewhere with the backup for this phone but finding it would take some time so in the mean time I am turning to the forums. If anyone could help that would be amazing. I will provide more information and answer questions as they come.
Steps I have taken:
1. dirty flash of stock latest firmware
1. wiping the phone completely
2. Installing latest stock firmware
3. Still bootlooped
Not solved
So after triple wiping through TWRP and installing the stock firmware again it was still looping so i left to run to the store quickly and when I returned I tried powering it on and it loaded normally and I am still setting it back up.
Leaving the original comment. After coming home from work my friend said it had started doing it again, and it is. This time there was no root and no system anything messed with, does this mean there is a hardware problem?
Posting this because I spent 2 days trying to get my phone back up and running after I changed some system setting that caused an endless bootloop. Marking is solved as the issue is solved and maybe it will show in the searches.
I followed the instructions on the guides i found on this site. I had all sorts of problems. ROM not installing, TWRP not sticking, TWPR not flashing modules, error messages all along the way. I have flashed this phone several times already without issues, other than the 1st run.
I stumbled across a random post on an Xiomi forum somewhere where the guy was having similar issues. The solution was DON"T use "the latest version" of TWRP.
All the guides insist you use the latest version. That's what I was doing to TWO days. I went back about 3 versions and BOOM, phone was set up, flashed OOS 10.3.3, Magisk flashed, new kernel flashed, xxxNoLimits flashed and everything working in under an hour.
This may have been specific to my Tmobile, international conversion, but I doubt it as I was already running OOS 10.3.3. Nowhere on this site, at least from the searches I did could I find this suggestion that turned out to be my solution so I am posting in hopes it might help someone else and save the frustration I went through.
For those that are going to post search results that didn't show up when I searched( which seems to happen when you say you couldn't find something here).....cool....the extra info may help someone.
Thanks for posting! I've been having issues flashing Xtended! The phone shuts off right in the middle of the boot animation. Fastboot recovering to oos worked fine though.
Is that similar to what you experienced?
Hi Everyone,
I have been on a rooted Android 10 build for the past 2 years, but found the battery was starting to drain quickly, so decided to upgrade to the latest version 11.
I have rooted phones many times, however im a bit stummped.
Initially when i rooted by flashing with Odin, my patched AP file, it would boot loop the start screen, however today i have got further and it boots to "android starting", but after 3 hours it hasnt moved from that point. I cant imagine this is normal\expected? I have tried to reflash a few times and wiped\factory reset before hand, using the main CSC instead of home_csc, but still the same result.
Any ideas? Am i missing something?
Cheers!
If anyone wants to reply with a potential fix for others, then please do, however for now i have managed to obtain root using a method someone else did on XDA.
Basically, i managed to install and run TWRP, then flashed a kernel in that. Now have an up to date phone with root.
Thanks for anyone who looks at this however.