Please excuse the newbie questions, I have installed the lineage OS on my Galaxy I9506 phone, together with GApps and the su addon using the instructions on wiki.lineageos.org/devices/ks01lte/install] All the logs suggest all went well but when I boot the phone I get the Galaxy logo plus "secure fail:kernel" in red on the top left of the screen. I am not sue what this means or how I can solve it, I have since reloaded 4.2.2 and started again and had the same result; and loaded CM and had the same result
Should I load a new kernel, if so which one (I prefer a compiled one as I only know win 7)
I would appreciate some advice. Thanks for your time David
Related
Hello fellow devs & modding enthusiasts,
I know that the Note 3 version of the CM is still unofficial, but I decided to give it a go and build it for myself.
However, I bumped into a few strange issues and seeing the number of people who have succeeded in producing a working rom it seemed like the right place to look for some advice.
First of all, my environment setup has been done correctly (as per the instructions on the CM site) and my repo is always synced before each build.
I am planning on installing the rom on my Qualcomm SM-N9005, so I thought that the hltexx version is what I need. I "breakfasted" it, then extracted all prebuilts from the phone. "Brunch" came next, along with the first problem:
The build started normally, but after 30-40 seconds I got a missing library (libtime_genoff.so) error message which aborted the build. After looking in the CM directories and not being able to locate it, I decided to get it from the phone itself, just like the prebuilts. So, I did "make clean" and started the build once again, but this time copied the missing library manually to "out/target/product/hltexx/obj/lib" right after the output directories were created in the beginning of the build.
At this point I was very skeptical for the result, but for my surprise after about 1 hour the build was completed without any errors and I was on my way to Flashingtown.
Yes... But no. After selecting the .zip from CWM, I got a incorrect version error from the first assert line of the updater script. It said "this version is for hltexx only, your version is hlte". Now this is just plain weird to me...
I always thought that the SM-N9005 is actually "hltexx". Am I wrong?
As there is no "hlte" only project in the CM repo and having in mind that everyone is building mainly for the 9005 model, I decided to modify the first line of the updater script so to recognize the "hlte" device.
And so I did, then flashed and... well that's it. The device could not boot beyond the "Galaxy Note 3" logo. I immediately flashed one of the unofficial builds from XDA and everything suddenly worked smoothly and I was rocking a nice clean CM on my Note 3.
What am I missing? Is there anything more to building the CM repo for the Note 3?
Any ideas / suggestions will be immensely appreciated!
Cheers,
Vlad
I've been using Quarx's CyanogenMod 11.0 (KitKat 4.4.2) since its January 20 release. However, my phone starting to become slow with the time (nothing related to the build but the extensive device use & data exchanging). Today i decided to upgrade to most recent build (NIGHTLY 23/03). Of course i wiped everything before. I installed the build directly from TWRP with no big problems, however, i disliked this "new"? recovery interface (this one that shows two options (RECOVERY) and (ANDROID) and this "Press search to load the system" thing. I Would like to disable it and return to the old M logo, where i had the blue led to warn me about the recovery thing. Is this possible? I mean, take this thing out?
Now the most important. As i said, i've been on the development thread since the beginning, but i didn't found any working answer to my situation. After trying both GAPPS 4.4.2, i see a black screen on first boot with the Standard GAPPS and only a "Choose your laguage" with Minimal, after chosen i get a "Launcher stopped working".I cant add the google account without the GAPPS, as some peoples suggested to another on that topic. I remember that i read something related to install the previous working build (20/01) and then upgrade to the newer, after setting the account on the older build. But theres no january 20 on quarxs ftp, what now? HELP PLS
System + data + cache wipe, use core gapps 2-26. If you encounter issues, then again install rom after full wipe, but don't install gapps immediately. Reboot, and delete unwanted system apps to free up space, and then flash gapps and wipe cache
No easy way to backport safestrap (replacement for boot menu)
Sent from my MB526 using Tapatalk
johnaddams83 said:
I've been using Quarx's CyanogenMod 11.0 (KitKat 4.4.2) since its January 20 release. However, my phone starting to become slow with the time (nothing related to the build but the extensive device use & data exchanging). Today i decided to upgrade to most recent build (NIGHTLY 23/03). Of course i wiped everything before. I installed the build directly from TWRP with no big problems, however, i disliked this "new"? recovery interface (this one that shows two options (RECOVERY) and (ANDROID) and this "Press search to load the system" thing. I Would like to disable it and return to the old M logo, where i had the blue led to warn me about the recovery thing. Is this possible? I mean, take this thing out?
Now the most important. As i said, i've been on the development thread since the beginning, but i didn't found any working answer to my situation. After trying both GAPPS 4.4.2, i see a black screen on first boot with the Standard GAPPS and only a "Choose your laguage" with Minimal, after chosen i get a "Launcher stopped working".I cant add the google account without the GAPPS, as some peoples suggested to another on that topic. I remember that i read something related to install the previous working build (20/01) and then upgrade to the newer, after setting the account on the older build. But theres no january 20 on quarxs ftp, what now? HELP PLS
Click to expand...
Click to collapse
do not use standard gapps..system partition not big enough to store standard gapps..install core gapps
Hi, RomSwitcher has been nagging me to update since I installed it. So finally, I clicked Update.
Now my phone doesn't show the boot logo, it just boots into a blank screen. Adb seems to function:
C:\Unified_Android_ToolKit>adb shell
- exec '/system/bin/sh' failed: No such file or directory (2) -
Anyways, if I ODIN any Perseus kernel, then my first ROM boots fine. But if I go into RomSwitcher and install the tools, then reboot boots into blackness again. I've tried to install the tools from the recovery, same thing happens.
I would post this in the Development thread, but I'm not allowed to post there yet. So as I understand it, RomSwitcher boots into it's own environment, changes some directories so one of several ROMS will boot. What seems to happen is that the RomSwitcher environment is just blank. I have no idea where to look, and I can't find the old version of RomSwitcher which worked anymore. I don't really want to reflash everything just to get RomSwitcher functionality back.
There's no information on the internet about how it works or how to fix it. It seems I've probably managed to wipe the configuration when updating it. If anyone can point me to a FAQ or Guide or something about how it works, or summarise it, I'll really appreciate it, as I don't really want to go and dig through the code to figure it out... that might take me several weeks with the little time I have available!
Questions:
What is in the configuration file?
Where is it stored?
Can I re-create it by hand?
What's the simplest way to get RomSwitcher working again, without starting from scratch with all my ROMs?
(I'm just dual booting Phoenix ROM and CM11, which worked fine until I updated RomSwitcher. New RomSwitcher looks good, but doesn't work!)
Thanks
Steps to repeat...
So, I've tried every Perseus kernel: 16, 18, 19
From the main TW based ROM that boots: Phoenix 10.1
RomSwitcher says to install Tools and Reboot before it does anything. Doing that reboots into a black screen, no matter what kernel. I've re-downloaded the main config and the tools several times.
Seems the only thing left to try is re-flash main ROM, re-install RomSwitcher... then it will probably work But that is a 3-4 hour operation I can't afford right now.
Please help me, with the latest versions of Paranoid i'm having issues with the multiboot.. When i update the ROM it goes well, when i boot into multirom and select paranoid a black screen shows a message that says multirom is creating issues.
Every time i have to update the ROM i have to delete and install it, so i'm loosing everything. How can i do?
Ask multirom
Sent from my Nexus 5
Hi, after attempting to enable encryption I get an infinite boot loop animation, and after I force a hard reset (keeping the power button pressed) the phone boots back to normal as if nothing happened. This means that encryption was not even started (otherwise it would be needed to format partition again if the process was interrupted).
What are my options here? On previous Android versions, whenever I came across a Rom that didn't support encryption, I would just flash a stock recovery image alongside the custom rom and try encrypting again, successfully. However, there are no Android 11 stock recovery images for this device (it got abandoned in Android 8.1 I believe), so this isn't an option anymore.
Unfortunately this ROM doesn't seem to have a dedicated thread here on XDA and people on their Telegram channel have not been able to provide guidance so far...
Any tips are appreciated!
ROM: PixelExperience Plus 11 (Android 11) version 2021.05.14
Device: Moto G5 Plus (potter, XT1685)
Recovery image: TWRP 3.5.2_9-0-potter
I have found no v11 or v10 roms which work with encryption (even when they say they do). I have not tried many v9; Your answer is to go back to stock 8.1 and everything will work again (but you'll be on v8):
[Oreo][Stock][Rom] TWRP Flashable Stock Builds
About this project This project provides repackaged Stock Oreo roms that can be flashed by TWRP. Modifications from stock are listed below. As we are now moving into the Oreo world, I've decided that now is a good time to make a few changes...
forum.xda-developers.com
edit: note that i'm on xt1687 (usa) model of potter
edit2: I just tried Arrow v10(official) and it encrypts (after a number of reboots; give it time)
bravo97 said:
edit2: I just tried Arrow v10(official) and it encrypts (after a number of reboots; give it time)
Click to expand...
Click to collapse
hi, in the case of PE+ 11, it just goes to reboot the first time and stays in loading android screen forever (waited a couple hours last time), so I think "giving it more time" wouldn't solve it.
Good to know there's some Rom compatible with encryption though, although it's android 10... I also got a hint that crDroid 11 may be compatible with encryption on potter.