Bootloop after installing pixelify
Device name: Pixel 7 Pro Rom name: LineageOS Android version: latest Pixelify version: latest
If there is a known problem with installing pixelify on the latest version of Android, why isn't that brought up during the installation script?! Are you kidding me?!
I was coming to check to see if my issue was responded to, seen yours!
I would like to point out that you are installing something custom! When you unlock your bootloader and install a Custom ROM/OS you are entering the BADLANDS, meaning you are 1000% responsible for reading, double checking, and then asking others if they had any issues installing a MOD that hasn't really been updated in 2 years and says nothing about Android 15 which I am assuming you meant by latest.? Not sure, as you did not say, latest is subjective for each phone model, and then you even can get into unofficial & official. You need to not take things lightly if you want to not have to reflash your ROM!
ALWAYS DOUBLE CHECK & ASK OTHERS, Join a telegram group, discord group, or check on XDA before you do anything!
You can really only be mad at yourself, which I have been mad at myself many times! How would you think a install script, written 2 years ago would mention incompatibility with a Custom ROM for Pixel 7 Pro LineageOS (lacking of version above) Android 15 (Guessing myself on version) using Pixelfy 3.0 today when the again last time this MOD was updated was 2 years ago when Android 15 wasn't even made yet?
What I would suggest is you edit above, add missing info, and be respectful to the DEV, he worked incredibly hard to make a Custom MOD for free,
Plus if you look down the issues, there are quite a few Android 15 issues, so again reading before action, trust me it helps a lot!
If you need help, I can point you in the right direction, I see a lot of Pixel groups in Telegram, I am sure they can help you better than I, Because I am not a Pixel Owner, so not sure if it has an EDL mode to reflash LineageOS or not
had no idea I copied the QR code lol, there are lineage groups too
I fixed it by flashing init_boot.img from lineageos
I fixed it by flashing init_boot.img from lineageos
Yeah, that's about the best way, I am guessing pixel flashing is about the same as OnePlus, but remember that everything you do after unlocking your device is on YOU!
Not the Dev's of custom ROM's or custom modules it's on you. To check out what you are going to change, the reason why devices are locked to begin with is because 99% of users don't read and/or look forward to see what files are being modified
Bootloader being unlocked in itself is a huge responsibility to the owner, and I would say 85-95% of unlocked & rooted users have no business being so!!
You could be using a file manager while tired, fall asleep and delete a file! Not even realizing it, the next day you restart your phone and now it won't boot!
It could be that simple of a mistake and not treating your phone as an unprotected child, which it now is!
The install script should fail if the device dosn't support it.
The install script should fail if the device doesn't support it.
I think you are missing my point, once you are doing something outside of the way the phone was manufactured, YOU are responsible, trust me I am not saying that your suggestion isn't a great one, because it is a great idea. I am merely stating that you need to read about what you are installing, double check with others, look at others issues.
I find something I want to install, and sometimes it takes days, perhaps weeks before I have researched it enough that I feel confident that I am willing to take the risk for the reward of having it installed.
You know how many times I have been so worried clicking the reboot button, just hoping I see my boot animation and not a fastboot or recovery screen!
There have been times I felt like a jerk for not reading the issues page, I've been in your shoes, I'm sorry it happened to you. I'm not being a jerk, I wish I was able to have informed you.