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
Related
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.
Hello,
I received my Nexus 6P yesterday and got my SIM card activated without any issues at Verizon. I immediately took it home, unlocked the bootloader, installed TWRP, and then flashed CyanogenMod's latest nightly. After booting in, wireless networks weren't detected, and I only had 3G (no 4G LTE as I should). I restored my backup of the stock ROM that I made in TWRP and it hung at the Google logo. I'm not sure why. I then flashed all the latest factory restore images (MTC19X) to get it working again and determined that the issues I had in CyanogenMod might have happened due to the vendor.img I had on my phone at the time not being compatible with that build of CM13.
My questions are:
1) What are the known issues that would likely occur due to vendor.img being a different version than what CM13 was based on? The concept of vendor.img is new to me. I haven't had this, as far as I know, on any of my other phones (granted I'm coming from a locked Samsung Galaxy S5 that I've had for almost 2 years)
2) How can you easily tell which vendor.img CM was based on so you know which one to flash?
3) Is there anything else I should be made aware of before attempting to flash CM13 again?
4) While using CM13, do most people recommend a custom kernel? If so, which one and how stable is it? What are the benefits of switching from the stock kernel, and how simple is it to go back if there's a problem?
Thanks!!
dude...I just got the N6P and ran CM13 within hours. This is what I did...
unlocked the bootloader
downloaded the lastest (MTC19X) image off of https://developers.google.com/android/nexus/images and unpacked it into the C:\Program Files (x86)\Android\android-sdk\platform-tools folder
ran the flash-all.bat
fastbooted TWRP
installed CM13. (didn't wipe internal storage)
installed arm64 open Gapps pico
BAM!!!
right now running stock kernel. it's cool. I'm PrivacyGuard-ing the hell out of all my apps (turned off START AT BOOT and KEEP AWAKE for almost every downloaded app), though, so battery is OK
also using Kernel Adiutor but underclocking values for the CPUs doesn't seem to stick
So it likely worked for you since you had flashed the newest vendor.img first. Apparently there are compatibility issues with certain features that cause them not to work (such as WiFi) if you're using an older one.
chaoticyeshua said:
Hello,
I received my Nexus 6P yesterday and got my SIM card activated without any issues at Verizon. I immediately took it home, unlocked the bootloader, installed TWRP, and then flashed CyanogenMod's latest nightly. After booting in, wireless networks weren't detected, and I only had 3G (no 4G LTE as I should). I restored my backup of the stock ROM that I made in TWRP and it hung at the Google logo. I'm not sure why. I then flashed all the latest factory restore images (MTC19X) to get it working again and determined that the issues I had in CyanogenMod might have happened due to the vendor.img I had on my phone at the time not being compatible with that build of CM13.
My questions are:
1) What are the known issues that would likely occur due to vendor.img being a different version than what CM13 was based on? The concept of vendor.img is new to me. I haven't had this, as far as I know, on any of my other phones (granted I'm coming from a locked Samsung Galaxy S5 that I've had for almost 2 years)
2) How can you easily tell which vendor.img CM was based on so you know which one to flash?
3) Is there anything else I should be made aware of before attempting to flash CM13 again?
4) While using CM13, do most people recommend a custom kernel? If so, which one and how stable is it? What are the benefits of switching from the stock kernel, and how simple is it to go back if there's a problem?
Thanks!!
Click to expand...
Click to collapse
1) Depends on ROM /VENDOR, sometimes nothings happens then an error message, sometimes things doesnt work
2) Just download fresh the latest snapshot, release or nightly (they are much more stable then for a few years!) and vendor image (use these ones which are recommended!)
https://wiki.cyanogenmod.org/w/Install_CM_for_angler (there is a link for the vendor)
3) If you stay close on the tutorials, i dont know what should happen (flashing a rom is normally not critical, installing a recovery can be!)
4) Custom kernels can be great, but its not a must-have. Which kernel you should use depends on your wishes: better battery, more power etc.
Hope i could have help you a little bit!
kaufikauf said:
1) Depends on ROM /VENDOR, sometimes nothings happens then an error message, sometimes things doesnt work
2) Just download fresh the latest snapshot, release or nightly (they are much more stable then for a few years!) and vendor image (use these ones which are recommended!)
https://wiki.cyanogenmod.org/w/Install_CM_for_angler (there is a link for the vendor)
3) If you stay close on the tutorials, i dont know what should happen (flashing a rom is normally not critical, installing a recovery can be!)
4) Custom kernels can be great, but its not a must-have. Which kernel you should use depends on your wishes: better battery, more power etc.
Hope i could have help you a little bit!
Click to expand...
Click to collapse
Very much so. I appreciate it!
Has anyone encountered the constant popup of the Select Sim Card message? I'm using project fi and I am still unable to find a solution to this issue.
"Updater process ended with ERROR: 7" upgrading S5 (klte/G900F) from CM to Lineage
Hi all,
I've finally got around to attempting an upgrade from CyanogenMod 13.0 to LineageOS 14.1 on my Samsung Galaxy S5 (klte/SM-G900F). I have been able to successfully flash lineage-14.1-20170125-experimental-klte-signed.zip and it booted fine, but subsequently attempting to flash the latest nightly (lineage-14.1-20170412-nightly-klte-signed.zip) threw error "updater process ended with ERROR: 7" (something about a file missing from /bin... I think, although I didn't take a copy of the full message ).
After this the phone wouldn't boot (eventually the starting animation froze) and I have ended up reverting to CM13.0 from a backup.
Can anyone tell me what I'm doing wrong? I'm aware the experimental builds have now been removed - is it worth trying to upgrade from the experimental one to an older nightly first? Is this a known issue with this particular nightly? Do I need to try again and actually record the full error message this time?
Thanks for any assistance anyone can provide!
Regards,
Russ
Hi all,
Finally found another bit of free time. I tried again from lineage-14.1-20170125-experimental-klte-signed.zip to lineage-14.1-20170222-nightly-klte-signed.zip (a much smaller jump in version, and within the 2-month supported period of the experimental build) and it worked fine (I did get "E:unknown command [log]" but this seems harmless).
However I tried to go from there to the latest nightly, lineage-14.1-20170426-nightly-klte-signed.zip, and *that* failed:
Code:
assert failed: run_program("/tmp/install/bin/variant_blobs.sh") == 0
Update process ended with ERROR: 7
However, I found the apparent answer via another thread: upgrade to latest TWRP (I'm on 3.0.0). So I will give that a try.
Regards,
Russ
GloomyTrousers said:
However, I found the apparent answer via another thread: upgrade to latest TWRP (I'm on 3.0.0). So I will give that a try.
Click to expand...
Click to collapse
...and it worked Hope this helps someone else.
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