{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
AICP
Android Ice Cold Project
AICP is known by everyone as the "Ice Cold Project" that started on a Desire HD years ago (2012) and since then evolved into a mature ROM with the BEST community you can find!!!
Until Lollipop, the Rom has always been based on AOKP. Unfortunately, since AOKP stopped development (but made a comeback later), we changed our base to CM when it comes to hardware, drivers and some features.
With the re-brand of CM to LineageOS (LAOS) we are now actually LAOS based with some tweaks from AOSP.
If there are any bugs, either we will sort them out or the LAOS team will if it concerns their code base. This rom isn't LAOS supported, so no need to report errors/bugs to them!!
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you. Hard & a lot.
*
*/
Feature list (rough Overview)
In the beginning we would like to thank:
LineageOS & CM (R.I.P.) team
@maxwen and the rest of the OmniRom team
DU team
SlimRoms team
Resurrection Remix team
Community
...
@LorD ClockaN
@zipsnet
@eyosen
@semdoc
@Drgravy
@Hashbang173
@SpiritCroc
@wartomato
@eboye
plus the rest of the crazy bunch that we call "team"
...
We are paying for servers that build nightlies/weeklies and everything that comes with it, so EVERY DONATION will really be appreciated and be used to cover those expenses.
Thank you!!
Latest Stable Release Version 13.0
Download link: Preview-AICP-berkeley
Full Changelog link: http://dwnld.aicp-rom.com/
VoLTE
IR Blaster
Let me know if you see any more
FAQ:]
Before using the ROM:
Q. Can I have an ETA for the next build?
A. Yes, just look in the OP to see, if your device is build on a nightly or weekly schedule.
Q. Does this ROM support custom kernels?
A. No. You can still use them (as long as they are LOS based), but discussion should go in the thread of the respective kernel. We don't offer support for bugs you might encounter using them!
Q. Why doesn't this ROM support Xposed?
A. Xposed is a hack that is geared towards AOSP, custom ROM's modify the framework a lot, so Xposed can cause a ton of issues on custom ROM's. Now it might work for you, however it is not to be discussed in this thread, and you should refrain from posting bug reports.
Q. Alright, but I still want to flash Xposed, so which version do I need to install?
A. Xposed is not yet available for Oreo.
Flashing the ROM:
Q. What do I need to know before flashing?
A. Check the install instructions in the first post...
Q. Can the builds be dirty flashed over each other?
A. Yes, however make a nandroid first as there is a chance of getting a bootloop or encountering bugs. Also bugs may only be reported on a clean flash.
Q. How do I dirty flash builds?
A. Wipe the System, Cache and ART/Dalvik cache. Flash the ROM, Gapps (only needed if you wipe the system), your preferred root solution and reboot. Or you might just use the OTA app to preform that task for you.
Q. How do I flash kernel builds?
A1. If it's a .img file boot into TWRP and go to the install page in TWRP, in the bottom right corner select "install image", select the desired kernel, then select "boot", then swipe to flash, then go back to the install screen and install your root method again if you don't want to loose root, and then reboot.
A2. if it's a flashable ZIP You can flash it together with a ROM update or separately. Go to the install page in TWRP, choose the kernel zip (or add it to the flash queue right after the ROM zip). Then add your root method to the queue if you don't want to loose root. Now swipe to flash, and then reboot.
Using the ROM:
Q I installed a bad theme and now I'm getting a bootloop, how do I fix it?
A In TWRP, flash the substratum rescue zip in the substratum folder on the internal storage.
Q I keep losing root with Magisk, how do I fix it?
A Check this out, if that doesn't work for you ask for help in this thread, read or ask in the Magisk thread on XDA or just flash Magisk again!
Q I'm having issues with WhatsApp, how do I fix it?
A Read this
Q. Do I need to provide a logcat if I'm reporting a bug?
A. If you want it to be fixed faster (or at all) then yes, you should definitely provide a logcat. (Note: Please just link the logcat from your GDrive, Dropbox, etc. and do not post the content here. Thanks.
Q. How do I get a logcat, what type should I get and more questions that can conveniently be answered by my pre-determined answer?
A1. Read this thoroughly. Also, here's a good app for getting logs: https://play.google.com/store/apps/details?id=com.tortel.syslog
A2. If you are already rooted, you can use the built-in feature to make a logcat and provide that. Just look into the root section in the AICP Extras menu.
The ROM should contain everything you need to enjoy Android Oreo. You don't need to install any Add-on's, simply download the latest ROM, GApps, flash it and go!
If you want the device to run the ROM "rooted", you can flash a root solution of your choice after the ROM Zipfile.
It is STRONGLY recommended to fully wipe your device before flashing, and if possible avoid restoring system apps and system data with Titanium Backup as this can cause stability issues that are very hard to debug.
If you believe you know what you're doing - then fine, go ahead, but please don't complain if you experience any strange behavior.
How to flash:
(Again: Don't do it if you don't know it!)
1. Download the ROM and GApps and transfer them to your device
2. Boot to recovery (TWRP recommended)
3. Wipe system, Cache, data and ART/Dalvik cache
4. Flash ROM Zipfile
5. Flash/Install GApps (optional, needed for e.g. Google Playstore to work)
6. Reboot to system
The ROM has GApps persistence in between dirty flashes, so you only have to flash them once!
The root solution should be flashed together with every OTA update (= ROM Update)!
Supported Root Solutions:
[COLOR="Dark Red"]Currently SuperSU and Magisk cause the device to reboot every so often.[/COLOR]
PREREQUISITE FOR OTA:
To be able to flash using the buildin OTA app that needs TWRP recovery installed to work.
You can still use LAOS recovery and OTA app, but you will need to download the zip file and flash it manually from within your recovery. Zip gets saved in the "AICP_ota" folder on your internal storage.
Please be sure that you are on the latest TWRP recovery.
If you want to contribute to the AICP or wanna see what is being worked on/merged, feel free to visit our Gerrit review system. (Link is at the bottom!!!)
PLEASE NOTE OTAS ARE CURRENTLY NOT AVAILABLE FOR AICP FOR BERKELEY
ROM & Additional links:
Gerrit Code Review
Github
IceColdJelly AICP G+ community
Contributors
@DarkExistence
LuK1337 (Initial Berkeley tree)
Flex (Fixing fingerprint)
The rest of the Honor Open Source dev community!
And everybody else who contributed to the tree!
You want to see a normal night at the "DEV office", click here!!
XDA:DevDB Information
AICP for Honor View 10, ROM for the Honor View 10
Contributors
DarkExistence
Source Code: https://github.com/AICP
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 4.x
Based On: LineageOS
Version Information
Status: Beta
Created 2018-04-28
Last Updated 2018-04-28
Please note:
- This a flashable zip that must be flashed in TWRP. This is not a GSI
- GAPPS aren't included
- This can only be used on the Honor View 10
Reserved.
This too
One more because why not
are you using unofficial or official twrp?
IcipherPT said:
are you using unofficial or official twrp?
Click to expand...
Click to collapse
Unofficial
Rommco05 said:
FPS gestures like on EMUI are included?
Click to expand...
Click to collapse
Not at the moment, no
DarkExistence said:
Unofficial
Click to expand...
Click to collapse
You can enter recovery mode again after flash your rom?
IcipherPT said:
You can enter recovery mode again after flash your rom?
Click to expand...
Click to collapse
Yeah, I can anyway, but YMMV. Either through the advanced reboot settings in Dev options or from ADB reboot bootloader. Or just from start up without USB cable plugged in.
DarkExistence said:
Yeah, I can anyway, but YMMV. Either through the advanced reboot settings in Dev options or from ADB reboot bootloader. Or just from start up without USB cable plugged in.
Click to expand...
Click to collapse
Yours is a L09 or L04?
@DarkExistence
the next question is, were you able to decrypt your phone with unofficial twrp and aicp on board?
IcipherPT said:
Yours is a L09 or L04?
Click to expand...
Click to collapse
Part of the developer program so L04 . Also on the latest software.
kurvenmeister said:
@DarkExistence
the next question is, were you able to decrypt your phone with unofficial twrp and aicp on board?
Click to expand...
Click to collapse
Yes I could , just had to enter in my screen lock pin and it decrypted. Again though YMMV so if it works for me doesn't necessarily mean it works for you, I'm not a TWRP expert don't see why it wouldn't though
@DarkExistence
thank you for your quick reply. will try it out soon.
you came from stock, flashed twrp, then aicp and then decrypted your device? could you tell me your way? decrypting right after flashing twrp or after flashing aicp?
I think there is a problem with the L09 variant, after flash a custom rom (anyone) I cannot enter anymore in TWRP. I'm not the only one reporting this If I'm not wrong
EDIT: I got an infinite bootloop to enter to recovery xD Had to wait until the eRecovery said "failed to install software"
IcipherPT said:
I think there is a problem with the L09 variant, after flash a custom rom (anyone) I cannot enter anymore in TWRP. I'm not the only one reporting this If I'm not wrong
EDIT: I got an infinite bootloop to enter to recovery xD Had to wait until the eRecovery said "failed to install software"
Click to expand...
Click to collapse
Did you ask in the TWRP thread? Seems more like an issue there vs the actual ROM itself. Hope you get it sorted though , I had a similar issue after updating to the latest stock emui build.
As said in the OP AICP is based on Lineage which from reading the thread you seemed to have issues with before? Most likely a similar case here. Have you tried official twrp maybe?
kurvenmeister said:
@DarkExistence
thank you for your quick reply. will try it out soon.
you came from stock, flashed twrp, then aicp and then decrypted your device? could you tell me your way? decrypting right after flashing twrp or after flashing aicp?
Click to expand...
Click to collapse
I actually came from stock , flashed the unofficial TWRP image, flashed the old lineage system.img (before they switched to the .zip) and then rebooted to TWRP from there and was able to decrypt and flash etc. Waiting for the official TWRP to be updated and will be switching to that then. That's what worked for me anyway but I had glitched my phone with a bad attempt at updating official emui.
DarkExistence said:
Did you ask in the TWRP thread? Seems more like an issue there vs the actual ROM itself. Hope you get it sorted though , I had a similar issue after updating to the latest stock emui build.
As said in the OP AICP is based on Lineage which from reading the thread you seemed to have issues with before? Most likely a similar case here. Have you tried official twrp maybe?
Click to expand...
Click to collapse
Yes ofc, I'm testing as much as I can trying to help every developer, I was asking you to get as much info as I can
I didn't try with offical version because of the encryption =\ (That issue that you are talking about was my fault: frp lock xD)
IcipherPT said:
Yes ofc, I'm testing as much as I can trying to help every developer, I was asking you to get as much info as I can
I didn't try with offical version because of the encryption =\ (That issue that you are talking about was my fault: frp lock xD)
Click to expand...
Click to collapse
Ah, When I was using the official version (unable too now because of my emui version), I used the RemoveEncryption.zip file and it worked pretty well for me, incase you wanted to try it out Just no MTP gotta adb push
DarkExistence said:
Ah, When I was using the official version (unable too now because of my emui version), I used the RemoveEncryption.zip file and it worked pretty well for me, incase you wanted to try it out Just no MTP gotta adb push
Click to expand...
Click to collapse
Not a problem for me! I will test it if you want!
Related
CyanogenMod 13 nightlies started, checkout its thread!
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 5.1.1 Lollipop, which is designed to increase performance and reliability over stock Android for your device.
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*
* Submitting bug reports on nightly builds is the leading
* cause of male impotence.
*/
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit out Gerrit Code Review.
IMPORTANT INFORMATIONS
- Root is now disabled by default on CM12.1. To enable it go to Settings>Developer Options>Root access and set to Apps only or Apps and ADB.
- CyanogenMod 12.1 comes with Cyanogen Recovery by default, if you don't like it you can flash alternative recoveries using IsoRec
I'll not support users and answer questions from users which:
- Are running a custom kernel
- Have flashed mods
- Modified system files
- Didn't follow my instructions
- Are unfriendly
Official CyanogenMod Wiki: http://wiki.cyanogenmod.org/w/I9100_Info
Known Issues: http://wiki.cyanogenmod.org/w/Known_Issues_page_for_i9100
Changelog: http://www.cmxlog.com/12.1/i9100
First time installation instructions:
Download CM-12.1-XXXXXXXX-NIGHTLY-i9100.zip to your sdcard
Make sure you're using a Kitkat Compatible Recovery
Boot into Recovery
Wipe all your data
Flash CM-12.1-XXXXXXXX-NIGHTLY-i9100.zip from sdcard
(Optional)Flash Google Apps.zip from sdcard
Reboot
CM12.1 official nightly builds:
http://download.cyanogenmod.org/?device=i9100
Recommended Google Apps:
http://forum.xda-developers.com/android/software/tk-gapps-t3116347
Choose Pico version to fit in the /system partition.
If you like my work, consider making a small donation
XDA:DevDB Information
CyanogenMod 12.1, ROM for the Samsung Galaxy S II
Contributors
Lysergic Acid
Source Code: https://github.com/CyanogenMod
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.0.x
ROM Firmware Required: Kitkat Compatible Recovery
Based On: AOSP
Version Information
Status: Nightly
Created 2015-07-01
Last Updated 2016-02-04
Reserved
Thank you for the hard work Lysergic and congratulations for the success so far.
...
Update from latest Unofficial to first Official through OTA was unsuccessful. Now flashing from CM Recovery and will flash GAPPS as the Google services are not working after the OTA update.
edit: gapps still not working after flashing official build + gapps from recovery. Any chance to fix it without factory reset?
Solution: "you can clear the play services data to fix that"
---
update: I got better performance with the first official build compared to the latest unofficial.
Reserved
Congratulations LA.
Hope users will provide useful feedbacks and logcats in this thread to help you make this rom even better.
Cheers !
Congratulations
Finally your Hard Work Paid it off.
Congratulations Lysergic Acid!
there is a way to fix the crashing gapps but it will take mashing the screen to get there just wipe the gapps services data and that fixed it for me.
abdulhkeem said:
there is a way to fix the crashing gapps but it will take mashing the screen to get there just wipe the gapps services data and that fixed it for me.
Click to expand...
Click to collapse
Thanks a lot @abdulhkeem, it worked and this saved me a lot of time. :good:
My phone seems very hot under the camera, expecially when leaved attached to AC power... much more than on KK...
I made all the possible wipes/formats and checked with betterbatterystats but I cant find anything strange...
Thanks so much for this @Lysergic Acid!
I have been following since November last year and all I can say is what an amazing achievement!
Congrats to you and all the great devs that helped you get to where you are now.
Can't wait to see what is to come with the official tag on the ROM now.
Regards,
Jleoz.
lost root
Looks like I lost root with the official build. Yes, the root access is enabled in dev options. Tried rebooting, disable-enable, re-flash, still does not have root.
essenov said:
Thank you for the hard work Lysergic and congratulations for the success so far.
...
Update from latest Unofficial to first Official through OTA was unsuccessful. Now flashing from CM Recovery and will flash GAPPS as the Google services are not working after the OTA update.
edit: gapps still not working after flashing official build + gapps from through recovery.
Any chance to fix it without factory reset?
Click to expand...
Click to collapse
As already said, you can clear the play services data to fix that, but I'm working on a fix for the backup tool.
Can't wipe data
I'm unable to wipe data/factory reset from the new cyano recovery. Same thing if i try wiping from settings, is someone having same issue?
@Hazard- Me too, but also I can`t install any *.zip package.
it says unable to open efs/metadata (more or less). I thought efs folder is untouched on wipe, isn't it?
No APN data available so mobile data can't also be enabled.
Nice!
Great work @lysergicacid !! REALLY THANKS!!!
Now I can only hope, that my S3 will also get Official.
I have just written to @JustArchi , would you tell him what you have done to get official? Thanks!
kostelo said:
No APN data available so mobile data can't also be enabled.
Click to expand...
Click to collapse
Same here, but just search for carrier configuration and create an APN yourself, it's easy!
Dr.Fix said:
Same here, but just search for carrier configuration and create an APN yourself, it's easy!
Click to expand...
Click to collapse
I know my man. I already have. I 'm just reporting the bug in case it was missed.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Who's back? We're back.
CarbonROM is an aftermarket firmware based on the Android Open Source Project. We are dedicated to fast, stable, and feature-filled roms, honesty and communication with our users, and openness with our code. We like frequent builds, with the very latest and greatest hardware support and fixes. We strive to not only provide you with the best rom we can build, but also to give back to the Android community and our fellow developers. For us, this is about creating something we can be proud of and hope you will enjoy.
Please feel free to look, build, and use our code at CarbonROM's GitHub... and at CarbonROM Gerrit.
Disclaimer:
While we make every effort to test these builds as much as possible, we are not responsible for anything that may happen to your device, family, pets, or perception of reality. We ask that you do your part to know your device and know how to recover from problems before you flash! If you have questions, ask your fellow users or ask us in #teamcarbon on freenode IRC.
Support:
We spend an astonishing amount of time developing this software. We can't spend much time on XDA as a result, so if you need support, please try the following:
1) Search. Search, search, search. Yes, you. I don't care how unique or important your question is, it's very likely someone has adressed it already. Especially if you're even close to new at this.
2) Read our FAQ, which can be found on our website. Carbon FAQ
3) Ask a question in your device forum. Someone will no doubt try to help you. Warning: this help may come in the form of telling you it's a dumb question that has been asked before. See step 1 - such are the perils of asking questions when you haven't done the research yourself. Android is about helping yourself.
4) Ask a question on our IRC channel. Connect to #teamcarbon on irc.freenode.net or click here. You'll find several other Carbon fans and usually one or more devs as well. Please be polite.
Downloads:
Get CarbonROM
GitHub
Gerrit
Kernel source
Remember, every penny you send to us goes right back into the rom. It's used for hardware, server costs, etc - all the things that help us make Carbon better with every release. Your support means the world to us! If you've enjoyed Carbon, please consider a donation toward this goal. Thank you, and we hope you continue to enjoy Carbon!
XDA:DevDB Information
CarbonROM, ROM for the Google Pixel XL
Contributors
Myself5, CarbonROM
Source Code: https://github.com/CarbonROM
ROM OS Version: 7.x Nougat
Based On: AOSP
Version Information
Status: Nightly
Created 2017-01-08
Last Updated 2018-03-17
Nice to have you around!
Sent from my Pixel XL using Tapatalk
I have e to ask...What all pixel exclusive feature are in carbon now? I used to use carbon back on my sgs3 an missed it in your absence
I'm still using carbon rom on my nexus 5. I'm so happy to see this on Marlin. Can't wait to flash!
I just get "No SIM-Card". Did somebody else tried this ROM?
I haven't tried this rom yet, but thank you so much!!! We had 3 roms drop in less than 24 hours so it will take me a day or two to test.
Nic888 said:
I just get "No SIM-Card". Did somebody else tried this ROM?
Click to expand...
Click to collapse
Hi Nice,
I have been getting that on different roms after flashing, I usually reboot to recovery again, factory reset quickly in twrp, and then reflash the rom, flash twrp again, then from twrp reboot to recovery again, then once you're back in recovery reboot to the system or rom. Hope this helps.
Where are the installation instructions? FAQ section on carbon website is not working. Thanks
I had no clue carbon was about to drop for the pixel xl. This has always been my favorite rom ever. Appreciate the CARBON MARLIN LOVE!
---------- Post added at 07:18 AM ---------- Previous post was at 07:11 AM ----------
dablitzkrieg said:
Where are the download instructions? FAQ section on carbon website is not working. Thanks
Click to expand...
Click to collapse
Download instructions??? Tap "Get CarbonRom" and download for your device. But honestly if you need instructions on how to download a ROM, I would hold off on trying to learn to flash a ROM
skulldreamz said:
I had no clue carbon was about to drop for the pixel xl. This has always been my favorite rom ever. Appreciate the CARBON MARLIN LOVE!
---------- Post added at 07:18 AM ---------- Previous post was at 07:11 AM ----------
Download instructions??? Tap "Get CarbonRom" and download for your device. But honestly if you need instructions on how to download a ROM, I would hold off on trying to learn to flash a ROM
Click to expand...
Click to collapse
Lol, I meant installation instructions
Flashed carbon one of my favorites of all time.
But problems ensued after.
no radio,no clear instructions for gapps.
replaced twrp with carbon recovery in very small font,too small for me to see,no signal etc.
but its a work in progress thanks,will flash again when it gets a little more stable
Restoring from factory image now latest google stock then ill retry.
And before anyone goes on a rant,yes this ROM is free i realize that just saving you some trouble.
Right now its not fully functional in my case ymmv.
Carbon Marlin........ One of my regular dual boots on S3 Great to see support for this device from you guys!
I'm very much looking forward to trying this when I can!
TechBSwift said:
I haven't tried this rom yet, but thank you so much!!! We had 3 roms drop in less than 24 hours so it will take me a day or two to test.
Click to expand...
Click to collapse
That almost screams for the need for MultiROM, huh?
humdrum2009 said:
Flashed carbon one of my favorites of all time.
But problems ensued after.
no radio,no clear instructions for gapps.
replaced twrp with carbon recovery in very small font,too small for me to see,no signal etc.
but its a work in progress thanks,will flash again when it gets a little more stable
Restoring from factory image now latest google stock then ill retry.
And before anyone goes on a rant,yes this ROM is free i realize that just saving you some trouble.
Right now its not fully functional in my case ymmv.
Click to expand...
Click to collapse
Ok, lets see.
I experienced some trouble with the vendor blobs I was using in the past, I made a build overnight with different vendorblob setup, maybe you could test it.
It also includes GApps, as these still have trouble on the Pixel devices. We (the Carbon team) don't want to release builds with included GApps for various reasons, so I will release unofficial builds with included GApps until the GApps issues are solved.
The unofficial builds with GApps can be found here:
https://dl.myself5.de/marlin/CarbonROM/
The TWPR thing is caused by the Recovery setup itself. Recovery is built into the Kernel. This means you need to flash the TWRP installer zip again after flashing a ROM.
@Myself5
Dl in progress. Will test it for you shortly
Flashing in progress
Booting. Didn't saw this animation for a long time
Flashed like this
Rom and twrp
Reboot to twrp
Flashed vendor V
Reboot system
Reboot recovery
Flashed latest su
Reboot system
All fine.
TB is running
Flashed MVK kernel and all fine
Fantastic release for a comeback
Will leave it on for tomorrow to test normal daily usage. So I could say something about battery and overall feeling.
mikaole said:
@Myself5
Dl in progress. Will test it for you shortly
Flashing in progress
Booting. Didn't saw this animation for a long time
Flashed like this
Rom and twrp
Reboot to twrp
Flashed vendor V
Reboot system
Reboot recovery
Flashed latest su
Reboot system
All fine.
TB is running
Flashed MVK kernel and all fine
Fantastic release for a comeback
Will leave it on for tomorrow to test normal daily usage. So I could say something about battery and overall feeling.
Click to expand...
Click to collapse
May I ask what the mvk kernel is?
It's the kernel from the velocity dev. Not on xda. He left xda about 4 years ago.
So one normal day in use and I must say it's damn nice. Battery is fantastic.
All works as it should. Bluetooth, Wlan, mobile etc.
Not one bug comes through my way Fantastic job.
Thx again.
Nice to see you guys back... Now don't leave again.. High5 guys!
Hey guys, I'm one of the core developers of CarbonROM...
...and there is something I would like to address:
I would like to keep our threads clean, and strictly about development and/or related topics. XDA is the place to be helping one another, sharing ideas, bringing each other up in this developer community through contributions. Because of the impulse of certain users, I want to follow a strict policy for postings.
The general idea of what should/should not be posted here is outlined in the XDA forum rules.
MikeChannon said:
Development Forums (ones with the word development in the title) - For Developers to post release threads e.g. ROMs and Kernels including modifications to kernels, bootloaders, ROMs, etc., as well as R&D development discussion threads designed with an end goal
Click to expand...
Click to collapse
Things like...
I love your rom, running great! But, battery life is not as good as XXX rom, please add XXX into the rom.
Click to expand...
Click to collapse
...should not be posted here.
Things like...
"I love your rom, but I'm getting memory issues that are not present in XXX rom that affect battery drainage. XXX rom has a the patch on their gerrit that may potentially solve the memory leak. I'll send a push to your gerrit review server so you guys can check it out!"
Click to expand...
Click to collapse
...are welcomed with open arms (and maybe even kisses, too!)
The only off-topic posts that may happen here may come from a CarbonROM core developer announcing or asking for a certain opinion on XXX feature. Thanks for understanding, this is the way development threads were meant to be in these forums. I invite everyone to stay vigilant to report posts that do not follow the summary by MikeChannon in the XDA rules about what should not be posted. Do not engage users if they don't follow the XDA rules, Forum Moderators exist for the purpose of handling such users . Long live the report button!
Myself5 said:
That almost screams for the need for MultiROM, huh?
Ok, lets see.
I experienced some trouble with the vendor blobs I was using in the past, I made a build overnight with different vendorblob setup, maybe you could test it.
It also includes GApps, as these still have trouble on the Pixel devices. We (the Carbon team) don't want to release builds with included GApps for various reasons, so I will release unofficial builds with included GApps until the GApps issues are solved.
The unofficial builds with GApps can be found here:
https://dl.myself5.de/marlin/CarbonROM/
The TWPR thing is caused by the Recovery setup itself. Recovery is built into the Kernel. This means you need to flash the TWRP installer zip again after flashing a ROM.
Click to expand...
Click to collapse
I get the error:
Could not find 'META-INF/com/google/android/update-binary' in the zip file.
Click to expand...
Click to collapse
LineageOS is a free, community built, aftermarket firmware distribution of Android 7.1 (Nougat), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include "std_disclaimer.h"
/*
* Your warranty is void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit Gerrit Code Review.
Installation
Upgrading from CyanogenMod/unofficial LineageOS without wiping
Download the EXPERIMENTAL and NIGHTLY builds using the download link below
Install the EXPERIMENTAL build, without wiping anything.
Reboot into Android
Reboot back into recovery
Install the NIGHTLY build, without wiping anything.
Enjoy LineageOS!
First time LineageOS 14.1 installation on your Galaxy S IV:
Flash a custom recovery via dd, use this recovery: https://androidfilehost.com/?fid=962157660013071010
Push Lineage OS 14.1 Weekly Zip & (optionally) GApps (arm) & (optionally) addonsu (for root) to your device
Boot into Recovery
Perform factory reset
Flash Lineage OS 14.1 zip from SD card
(optionally)Flash GApps from SD card
(optionally)Flash AddonSU from SD card
Reboot
Upgrading from earlier version of LineageOS:
Update your recovery - https://androidfilehost.com/?fid=962157660013071010
[*]Push the new Lineage OS 14.1 zip to your SD card
[*]Boot into Recovery
[*]Flash the Lineage 14.1 zip from SD card
[*]Flash the most recent GApps for 7.1 if you are upgrading from earlier android version
[*]Reboot
Downloads
Install packages: [URL="https://download.lineageos.org/jfltevzw"]https://download.lineageos.org/jfltevzw
Google Apps (arm): http://wiki.lineageos.org/gapps.html
Root add-on: https://download.lineageos.org/extras
Unofficial TWRP (NEEDED)
Reporting bugs
Bug reports belong on JIRA. See our wiki for more information on using JIRA.
I do not check this thread regularly for bug reports. Using JIRA makes tracking down & debugging bugs a lot easier. Feel free to use this thread to discuss bugs, though
DO NOT report bugs if you're running a custom kernel
DO NOT report bugs if you've modifies system files
DO NOT report bugs if you've installed xposed and/or other mods
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
See how to submit a bug report for the appropriate place to report your bug (NOTE: the majority of bugs need to go in the BUGBASH tracker, which is only open on weekends).
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues or bugs already reported on JIRA. Any bug not reported in the bug report format below may be ignored.
Code:
Phone Informations
* Lineage version
* Gapps version
What you did:
* Wipe data: y/n
* Upgrade from previous official cm build: y/n
* Restore with titanium backup: y/n
You're using (if yes write which one) :
* Task killer
* Phone cleaner / Battery enhancer apps
* Non-stock kernel
* Modified kernel settings
* Other mods
Bug info:
* Last version it worked on
* Repro steps
Getting help
You can ask for help on our subreddit, on IRC: #LineageOS on Freenode
The LineageOS team would like to thank everyone involved in helping with testing, coding, debugging & documenting! Enjoy!
XDA:DevDB Information
LineageOS 14.1 for S4 Verizon, ROM for the Samsung Galaxy S IV S4 Verizon, ROM for the Verizon Samsung Galaxy S4
Contributors
[URL="https://forum.xda-developers.com/member.php?u=5968293"]side, invisiblek, npjohnson
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
Version Information
Status: Nightly
Created 2017-03-15
Last Updated 2017-11-06
XDA:DevDB Information
[OFFICIAL][WEEKLY][7.1.2] LineageOS 14.1, ROM for the Verizon Samsung Galaxy S4
Contributors
npjohnson
ROM OS Version: 2.3.x Gingerbread
Version Information
Status: Testing
Created 2017-11-06
Last Updated 2018-09-21
reserved
@side
Thanks for your contribution!
There is a small typo in the first post - the download URL actually points to jfltexx instead of jfltevzw builds.
Got a question, what root are you using in this? AICP switched to a systemless root magisk and couldn't get it working. Is this is still old school root? Systemless root has to patch the boot.IMG and with the bootloader locked it wont work? Correct? Just trying to understand. Thanks
Would like to switch.
Sent from my Nexus 6 with Pixel XL build.prop
side said:
Flash a custom recovery via Heimdall or Odin
Click to expand...
Click to collapse
Which custom recoveries do work on Verizon variant? Everytime I install TWRP is gives me this message: "System software not authorized by Verizon wireless has been found on your phone "
Alternatively, can this be flashed using Flashify?
Z4K101 said:
Which custom recoveries do work on Verizon variant? Everytime I install TWRP is gives me this message: "System software not authorized by Verizon wireless has been found on your phone "
Alternatively, can this be flashed using Flashify?
Click to expand...
Click to collapse
We don't have an unlocked bootloader. If your bootloader version is MDK, however, there is an exploit known as LOKI. The LOKI exploit allows the bootloader to load 'unsigned' software, if said software has been patched to use the LOKI exploit. If your bootloader is NOT MDK, you're SOL. Don't tamper any more or you risk a brick.
(You can check your bootloader version by typing 'getprop|grep bootloader' in a terminal emulator on your device, or using 'adb shell' and then that from a command line on your computer.)
If you download and install TWRP from the TWRP app or site, it will not be LOKI patched. You need to find a patched recovery and flash that. Check the official TWRP thread. There is a gentleman who was kind enough to throw together a little command script that will flash a LOKI signed TWRP to your phone, if you have ADB enabled and are rooted.
bryantjopplin said:
Got a question, what root are you using in this? AICP switched to a systemless root magisk and couldn't get it working. Is this is still old school root? Systemless root has to patch the boot.IMG and with the bootloader locked it wont work? Correct? Just trying to understand. Thanks
Would like to switch.
Sent from my Nexus 6 with Pixel XL build.prop
Click to expand...
Click to collapse
I would also like to get clarification on this. I want to switch from my OctOS MM ROM to this. I have TWRP 3.1. installed, MDK bootloader.
@side, could you explain how root works on LineageOS 14 on this device?
side said:
LineageOS is a free, community built, aftermarket firmware distribution of Android 7.1 (Nougat), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include "std_disclaimer.h"
/*
* Your warranty is void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit Gerrit Code Review.
Installation
Upgrading from CyanogenMod/unofficial LineageOS without wiping
Download the EXPERIMENTAL and NIGHTLY builds using the download link below
Install the EXPERIMENTAL build, without wiping anything.
Reboot into Android
Reboot back into recovery
Install the NIGHTLY build, without wiping anything.
Enjoy LineageOS!
First time LineageOS 14.1 installation on your Galaxy S IV:
Flash a custom recovery via Heimdall or Odin
Push GApps (arm) and the Lineage 14.1 zip to your device
Boot into Recovery
Perform factory reset
Flash the Lineage 14.1 zip from SD card
Flash GApps from SD card
Reboot
Upgrading from earlier version of LineageOS:
Update your recovery - Lineage Recovery will be done automatically, TWRP can be downloaded from here (NOTE: you need 3.0.2-2 or higher to automatically install updates in Lineage 14.1)
Push the new Lineage 14.1 zip to your SD card
Boot into Recovery
Flash the Lineage 14.1 zip from SD card
Flash the most recent GApps for 7.1 if you are upgrading from earlier android version
Reboot
Downloads
Install packages: https://download.lineageos.org/jfltevzw
Google Apps (arm): http://wiki.lineageos.org/gapps.html
Root add-on: https://download.lineageos.org/extras
Reporting bugs
Bug reports belong on JIRA. See our wiki for more information on using JIRA.
I do not check this thread regularly for bug reports. Using JIRA makes tracking down & debugging bugs a lot easier. Feel free to use this thread to discuss bugs, though
DO NOT report bugs if you're running a custom kernel
DO NOT report bugs if you've modifies system files
DO NOT report bugs if you've installed xposed and/or other mods
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
See how to submit a bug report for the appropriate place to report your bug (NOTE: the majority of bugs need to go in the BUGBASH tracker, which is only open on weekends).
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues or bugs already reported on JIRA. Any bug not reported in the bug report format below may be ignored.
Code:
Phone Informations
* Lineage version
* Gapps version
What you did:
* Wipe data: y/n
* Upgrade from previous official cm build: y/n
* Restore with titanium backup: y/n
You're using (if yes write which one) :
* Task killer
* Phone cleaner / Battery enhancer apps
* Non-stock kernel
* Modified kernel settings
* Other mods
Bug info:
* Last version it worked on
* Repro steps
Getting help
You can ask for help on our subreddit, on IRC: #LineageOS on Freenode
The LineageOS team would like to thank everyone involved in helping with testing, coding, debugging & documenting! Enjoy!
XDA:DevDB Information
LineageOS 14.1 for S4 Verizon, ROM for the Samsung Galaxy S IV S4 Verizon, ROM for the Verizon Samsung Galaxy S4
Contributors
side, invisiblek
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
Version Information
Status: Nightly
Created 2017-03-15
Last Updated 2017-03-15
Click to expand...
Click to collapse
Plz help...... after installing twrp i am unable to boot into recovery mode on my s4 verizon nk1 build . it always says : System software not authorized by Verizon Wireless : ? is there any way to replace stock bootloader or any other way to install custom roms ?
---------- Post added at 04:03 PM ---------- Previous post was at 03:57 PM ----------
I also tried safestrap recovery it installed but not boot
rohailadnan said:
Plz help...... after installing twrp i am unable to boot into recovery mode on my s4 verizon nk1 build . it always says : System software not authorized by Verizon Wireless : ? is there any way to replace stock bootloader or any other way to install custom roms ?
---------- Post added at 04:03 PM ---------- Previous post was at 03:57 PM ----------
I also tried safestrap recovery it installed but not boot
Click to expand...
Click to collapse
This ROM is for MDK bootloaders only. It is not safestrap-compatible. On NK1, you'll need to stick with safestrap-compatible ROMs (TouchWiz-derived).
Also, please don't quote the OP
Has anyone tried this ROM on their jfltevzw yet? If not, I may give it a try anyway (with a bit more caution).
@side @Titokhan @bryantjopplin @uhh186
@flamadiddle
Sorry to disappoint you, but I never have this device.
flamadiddle said:
Has anyone tried this ROM on their jfltevzw yet? If not, I may give it a try anyway (with a bit more caution).
@side @Titokhan @bryantjopplin @uhh186
Click to expand...
Click to collapse
Not yet, not my daily and haven't messed with it again. Still on the aicp. I think I might have tried but had issues with finding root under developer options. That might have also been for the gnex. Lol
Sent from my Pixel XL using Tapatalk
flamadiddle said:
Has anyone tried this ROM on their jfltevzw yet? If not, I may give it a try anyway (with a bit more caution).
@[email protected]@[email protected]
Click to expand...
Click to collapse
Yup. I don't use my jflte much but this ROM works well for all I've seen so far.
Flash it away (if you're on MDK)
uhh186 said:
Yup. I don't use my jflte much but this ROM works well for all I've seen so far.
Flash it away (if you're on MDK)
Click to expand...
Click to collapse
Great! Thanks for the reply. Have you rooted this ROM? If so, which method did you use?
flamadiddle said:
Great! Thanks for the reply. Have you rooted this ROM? If so, which method did you use?
Click to expand...
Click to collapse
SuperSU I believe.
Alright, I'm taking the plunge. Loading 20170412 weekly and trying the SuperSU System-mode installer
Not going great. I was able to flash LineageOS and Pico Gapps, but every attempt I've made to root (system-mode method) so far has ended in boot-loops.
@uhh186 any tips would be appreciated.
flamadiddle said:
Not going great. I was able to flash LineageOS and Pico Gapps, but every attempt I've made to root (system-mode method) so far has ended in boot-loops.
@uhh186 any tips would be appreciated.
Click to expand...
Click to collapse
I'm sorry; I don't use my SG4 anymore, I just play with it every once and a while to see if I can't get the latest software on it. I was wrong/misremembered when I said SuperSU.
We can't use SuperSU because nougat+ requires systemless mode, and we can't do that with a locked bootloader.
My SG4 is rooted, so I went and looked what I had done. It appears I had just flashed the LOS root module.
uhh186 said:
I'm sorry; I don't use my SG4 anymore, I just play with it every once and a while to see if I can't get the latest software on it. I was wrong/misremembered when I said SuperSU.
We can't use SuperSU because nougat+ requires systemless mode, and we can't do that with a locked bootloader.
My SG4 is rooted, so I went and looked what I had done. It appears I had just flashed the LOS root module.
Click to expand...
Click to collapse
No apology necessary. Thanks for the help. It is strange, though. I've completely wiped internal storage, formatted data, installed again, and tried the LOS root addon. I still don't have root. The ChainsDD Superuser app from the Play store thinks I have root, but Titanium Backup and Root Checker can't find it.
flamadiddle said:
No apology necessary. Thanks for the help. It is strange, though. I've completely wiped internal storage, formatted data, installed again, and tried the LOS root addon. I still don't have root. The ChainsDD Superuser app from the Play store thinks I have root, but Titanium Backup and Root Checker can't find it.
Click to expand...
Click to collapse
LOS root requires some weird hoop jumping. Go into your developer options and make sure Root Access is enabled for apps and ADB.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
CarbonROM is an aftermarket firmware based on the Android Open Source Project. We are dedicated to fast, stable, and feature-filled roms, honesty and communication with our users, and openness with our code. We like frequent builds, with the very latest and greatest hardware support and fixes. We strive to not only provide you with the best rom we can build, but also to give back to the Android community and our fellow developers. For us, this is about creating something we can be proud of and hope you will enjoy.
Please feel free to look, build, and use our code at CarbonROM's GitHub... and at CarbonROM Gerrit.
Disclaimer:
While we make every effort to test these builds as much as possible, we are not responsible for anything that may happen to your device, family, pets, or perception of reality. We ask that you do your part to know your device and know how to recover from problems before you flash!
Support:
We spend an astonishing amount of time developing this software. We can't spend much time on XDA as a result, so if you need support, please try the following:
1) Search. Search, search, search. Yes, you. I don't care how unique or important your question is, it's very likely someone has adressed it already. Especially if you're even close to new at this.
2) Read our FAQ, which can be found on our website. Carbon FAQ
3) Ask a question in your device forum. Someone will no doubt try to help you. Warning: this help may come in the form of telling you it's a dumb question that has been asked before. See step 1 - such are the perils of asking questions when you haven't done the research yourself. Android is about helping yourself.
4) Join our Discord server! There, you can connect with other Carbon users and our developers, and you can get quicker responses to your bug reports. The invite link is right below.
5) Please keep bugreports to this thread or Discord. Do NOT create a Jira ticket. This is still in early development so we don't accept any bugreports yet.
Install Instructions:
Flash the newest factory image
Move your ROM + [GApps] to internal storage
Reboot to TWRP
Wipe Data, Dalvik/ART Cache, and cache
Flash the ROM + [GApps]
Reboot to System -> Enjoy CarbonROM
Get CarbonROM
Join the CarbonROM Discord server
Github
Gerrit
Kernel source
Remember, every penny you send to us goes right back into the rom. It's used for hardware, server costs, etc - all the things that help us make Carbon better with every release. Your support means the world to us! If you've enjoyed Carbon, please consider a donation toward this goal. Thank you, and we hope you continue to enjoy Carbon!
XDA:DevDB Information
CarbonROM CR 7.0 OPAL, ROM for the Huawei Nexus 6P
Contributors
PixelBoot
ROM OS Version: 9.x Pie
Version Information
Status: Stable
Created 2019-04-19
Last Updated 2019-07-04
A few notes before you proceed:
Before going straight to the download section there’s something we would like to tell you. We have changed the default encryption method for the phone, migrating to File-Based Encryption (you can get more information from the official Google documentation page). In order to get this encryption mode working, you will need to use our custom recovery (compiled from the latest source) which is compatible with this encryption and, just for the first time, you will have to wipe your internal data, so backup your data before proceeding.
Installation Instructions:
Grab our recovery from the peripherals section and install it.
Through TWRP Recovery:
Install Zip > Install Image > Choose ‘recovery.img‘ > Select partition ‘Recovery’ > Swipe to confirm flash
Through Fastboot:
Code:
fastboot flash recovery recovery.img
Install the ROM and then wipe your internal data partition.
Through TWRP Recovery:
Wipe > Format data
Through Fastboot:
Code:
fastboot -w
Reboot into system and wait until the process finishes, it could take a little bit. After the installation is done, I suggest waiting before using the phone because it usually goes into thermal throttling after installing a ROM.
Peripherals:
FBE Recovery: TWRP
WHAT?!!!! ???????????????????????????????????? I'm really impressed with your HARD WORK ??????? Its amazing the effort you are doing to keep this machine alive. Thank you PixelBoot ?
wow @PixelBoot another ROM from yourself! :good:
Great efforts
You're keeping the Nexus 6P alive
Can i dirty flash this ROM over Pixel Experience?
sufy1000 said:
wow @PixelBoot another ROM from yourself! :good:
Great efforts
You're keeping the Nexus 6P alive
Can i dirty flash this ROM over Pixel Experience?
Click to expand...
Click to collapse
Sadly, a clean flash has to be done.
Thanks for the support! :fingers-crossed:
God daaam another one! :victory: :victory:
You're the best PixelBoot
Thanks from Dominican Republic!
Has been on this rom for a day. Look good and solid. Though I have moved to AOSP Extended because I want a bit more customization.
I am on this ROM since the release, no problems whatsoever
thanks a ton dev
It's very snappy
How did I not notice this! Thanks @PixelBoot
very nice
Installed it, gonna take it for a spin. Just enough additional options, really like the agrresive battery options. So will see how will it pan out. So far so good.
sage of six paths said:
Installed it, gonna take it for a spin. Just enough additional options, really like the agrresive battery options. So will see how will it pan out. So far so good.
Click to expand...
Click to collapse
What kind of settings are there in aggressive options?
sufy1000 said:
What kind of settings are there in aggressive options?
Click to expand...
Click to collapse
Theres agrresive idle and standby ( just toggle on or off ) options in the carbon fibre settings. My phone is still charging to full, but it'll take a day or two till the rom and nfs settle and then i'll have an sot measure. This is kinda the middle point between no extras, and not having too much customization and i like it.
just installing now.
look nice, what kernel for more performance? let me know
I'm not using any kernel per se, i'm using nfs and that's it. However whom ever made the rom made an excellent job since right now after first full charge rom is at 50% battery 2h and 50 mins of sot. So will likely get over 5h of sot for my use which is awesome, and it might even improve slightly in the coming days till the rom and nfs settle properly.
sage of six paths said:
I'm not using any kernel per se, i'm using nfs and that's it. However whom ever made the rom made an excellent job since right now after first full charge rom is at 50% battery 2h and 50 mins of sot. So will likely get over 5h of sot for my use which is awesome, and it might even improve slightly in the coming days till the rom and nfs settle properly.
Click to expand...
Click to collapse
When did you replace your battery?
Sorry for the bonehead questions I'm about to ask, but I need some help here. I tried to find the Carbon FAQ on the website beforehand, but there's like no link to it whatsoever so this is the only place I can ask.
Now mind you I'm no novice at flashing roms, but I've been out of the scene for a long time now. Right now I have an old stock rom on this phone and it's running like absolute crap so I want to erase everything and take a new rom out for a spin in hopes to make things more snappy. This one caught my eye.
Question 1) In the install instructions 1 says to flash the newest factory image. Is this an absolute must? I'm on stock 8.1.0, unlocked bootloader, TWRP installed. I'm sure there's probably nothing newer for this phone than 8.1. Can I just download the rom + gapps, format it all in TWRP, and then install or am I going to royally screw anything up?
Question 2) Can anyone point me to the correct Gapps to use. With so many options these days I really don't want to make the wrong choice, then find the right ones, and have to reinstall.
Thank you in advance.
Raverrevolution said:
Sorry for the bonehead questions I'm about to ask, but I need some help here. I tried to find the Carbon FAQ on the website beforehand, but there's like no link to it whatsoever so this is the only place I can ask.
Now mind you I'm no novice at flashing roms, but I've been out of the scene for a long time now. Right now I have an old stock rom on this phone and it's running like absolute crap so I want to erase everything and take a new rom out for a spin in hopes to make things more snappy. This one caught my eye.
Question 1) In the install instructions 1 says to flash the newest factory image. Is this an absolute must? I'm on stock 8.1.0, unlocked bootloader, TWRP installed. I'm sure there's probably nothing newer for this phone than 8.1. Can I just download the rom + gapps, format it all in TWRP, and then install or am I going to royally screw anything up?
Question 2) Can anyone point me to the correct Gapps to use. With so many options these days I really don't want to make the wrong choice, then find the right ones, and have to reinstall.
Thank you in advance.
Click to expand...
Click to collapse
If your 8.1 is on the december update your good to go, if not flash that one.
If it is you need the fbe recovery for this rom, and all the roms form pixelboot. Aslo for latest lineage 16.
Flash that recovery over the one you have and reboot to recovery, flash rom and gapps, i always have the delete cache and dalvik cache ticked.
After that i go to fastboot and type fastboot -w to delete data, it's probably fine to do the factory format from within twrp.
After that boots i return to twrp to flash magisk, and then download the magisk manager, some roms don't need it, some do.
To use the correct gapps you can just go to open gapps website and pick arm64 9.0 and then the flavour you wish nano, pico or higher.
Make sure you flash open gapps right after rom and then reboot otherwise you might have problems. Just pick the ones with the latest security patch. Thats about it.
You can find an fbe recovery in the pixel experience rom thread, 3rd or 4th post below.
---------- Post added at 09:30 PM ---------- Previous post was at 09:08 PM ----------
sufy1000 said:
When did you replace your battery?
Click to expand...
Click to collapse
Maybe a month ago, two at the very most. In the end after first charge the battery life will round at about 4.30h which is about the same i get on aosp right now.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
LineageOS is a free, community built, aftermarket firmware distribution of Android 10 (Q), which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Introduction:
This is the Official LineageOS 17.1 thread for the Moto G7 Plus, codename lake.
Information:
Official Wiki || https://wiki.lineageos.org/devices/lake
Installation
How-to || https://wiki.lineageos.org/devices/lake/install
Downloads:
Builds || https://download.lineageos.org/lake
XDA:DevDB Information
LineageOS 17.1, ROM for the Moto G7 Plus
Contributors
Jleeblanch
Source Code: https://github.com/LineageOS
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
ROM Firmware Required: Android 10 (Q) Stock Firmware
Version Information
Status: Nightly
Created 2020-04-03
Last Updated 2020-04-03
Reserved
Reserved
many thanks! i couldnt get version 16 to work going from stock android 10 but this works like a charm
Good job bro
Really good job @Jleeblanch!!!!!
The installation instructions don't seem to work for my device. I tried the installation 2 times and both times my GPT got wrecked and I needed to reflash the stock ROM. Can someone who installed the ROM please tell me the steps they've taken so I can try to understand what I did wrong?
I'm on a Moto G7 Plus reteu BTW.
bamless said:
The installation instructions don't seem to work for my device. I tried the installation 2 times and both times my GPT got wrecked and I needed to reflash the stock ROM. Can someone who installed the ROM please tell me the steps they've taken so I can try to understand what I did wrong?
I'm on a Moto G7 Plus reteu BTW.
Click to expand...
Click to collapse
I got stuck also installing lineageos 17.1 on the same device following the steps mentioned in the installation instructions. I came from stock.
The changes that helped:
1. I used copy-partiotions-AB.zip.
2. I did not flash the lineage-recovery, but TWRP for the LineageOS images.
3. I installed GApps Pico. Others would not let me login to Google Services.
For me it seems that there is an issue with the lineage recovery: I flashed lineageos 20200402 and then updated to 20200403 via the built in updater. After the reboot the device was bricked and I had to reflash. This brick was also caused using the lineage recovery in step 2 mentioned above. If there is an issue with using copy-partitions-AB.zip instead of copy-partitions.zip, I cannot tell. I peeked into Jleeblanch's Unofficial Lineage 16 thread thinking there should not be that much of a difference.
Any comments on how to make lineage OTA updates work would help me. Is there a bug in lineageos right now or am I doing something wrong?
Awesome, I just got this device a week ago and was hoping someone would make an official version for it :laugh:
chincheta0815 said:
For me it seems that there is an issue with the lineage recovery: I flashed lineageos 20200402 and then updated to 20200403 via the built in updater. After the reboot the device was bricked and I had to reflash. This brick was also caused using the lineage recovery in step 2 mentioned above. If there is an issue with using copy-partitions-AB.zip instead of copy-partitions.zip, I cannot tell. I peeked into Jleeblanch's Unofficial Lineage 16 thread thinking there should not be that much of a difference.
Click to expand...
Click to collapse
I have to add & correct to myself:
- installing was only possible when I used twrp until lineageos was flashed.
- copy-partitions.zip as mentioned in the lake install instructions did work, but flashing GApps (not matter which) did result in a black screen while going through the wizard, using copy-partitions-AB.zip work well.
Anyone has Android Auto working for this rom? i had it fail with all roms exept the Stock one
rutger465 said:
Anyone has Android Auto working for this rom? i had it fail with all roms exept the Stock one
Click to expand...
Click to collapse
My guess would be no, same probably goes for voice match which has never worked for me on custom Android 10 roms on other devices.
First of all: Thanks a lot for all the effort in making this ROM!
My questions would be:
- does the ROM include some own recovery? I if flash TWRP, then do a sideload of Lineageos, I get into some Lineageos-recovery when rebooting recovery.
- how does rooting the phone work? simply flashing/sideloading latest magisk after flashing Lineageos?
bamless said:
The installation instructions don't seem to work for my device. I tried the installation 2 times and both times my GPT got wrecked and I needed to reflash the stock ROM. Can someone who installed the ROM please tell me the steps they've taken so I can try to understand what I did wrong?
I'm on a Moto G7 Plus reteu BTW.
Click to expand...
Click to collapse
Any build after the 20200405 (so 20200406+) won't have this issue. I apologize for not catching this sooner. With TWRP working as good as it does on this device, I never paid much attention to Lineage Recovery.
chincheta0815 said:
I got stuck also installing lineageos 17.1 on the same device following the steps mentioned in the installation instructions. I came from stock.
The changes that helped:
1. I used copy-partiotions-AB.zip.
2. I did not flash the lineage-recovery, but TWRP for the LineageOS images.
3. I installed GApps Pico. Others would not let me login to Google Services.
For me it seems that there is an issue with the lineage recovery: I flashed lineageos 20200402 and then updated to 20200403 via the built in updater. After the reboot the device was bricked and I had to reflash. This brick was also caused using the lineage recovery in step 2 mentioned above. If there is an issue with using copy-partitions-AB.zip instead of copy-partitions.zip, I cannot tell. I peeked into Jleeblanch's Unofficial Lineage 16 thread thinking there should not be that much of a difference.
Any comments on how to make lineage OTA updates work would help me. Is there a bug in lineageos right now or am I doing something wrong?
Click to expand...
Click to collapse
Nope, you weren't doing anything wrong. Read my reply above. Any build from April 6th on shouldn't have any issues. I spent the last couple days figuring this out lol
jadephyre said:
My guess would be no, same probably goes for voice match which has never worked for me on custom Android 10 roms on other devices.
Click to expand...
Click to collapse
Voice match should work as long as GApps is installed. However, if you're referring to hotword detection when the screen is off, then no. It's currently not fully implemented but I have had it working on Lake during our initial Lineage 17.1 bring up but unfortunately it didn't work on all sdm660 devices at the time. I'll work on decommonizing sound trigger in the near future, so stay tuned.
gerchla said:
First of all: Thanks a lot for all the effort in making this ROM!
My questions would be:
- does the ROM include some own recovery? I if flash TWRP, then do a sideload of Lineageos, I get into some Lineageos-recovery when rebooting recovery.
- how does rooting the phone work? simply flashing/sideloading latest magisk after flashing Lineageos?
Click to expand...
Click to collapse
Yes, Lineage Recovery is included by default (as well as on the official downloads page). The reason you're seeing it after you've flashed twrp to boot and then flashed the lineageos zip is because this device doesn't have an actual recovery partition. The recovery is part of the boot.img, so once you flash lineage, you're essentially overwriting twrp. To keep twrp permanently, you would also need to sideload the twrp-intaller zip from the Official twrp (I recently updated the official thread with newer unofficial version until new official versions are built) AFTER you've installed LineageOS.
If you also want to install GApps and root (Magisk), then reboot recovery and sideload them before rebooting to Lineage.
The new Roms works very well, thank you A LOT for that!
Tried an automatic update yesterday (from system setup menu) and had a short moment of panic: device did not boot anymore. I could save the situation by rewriting GPT and bootloader from the Stock image (10.0), but it was a close call!
The GPT delivered had quite different partition names / tables.
Why replacing bootloader and gpt? afaik if you start installation from scratch using twrp the partition names etc. do not change.
Will keep using twrp (sideloading it) for updates in the future.
Jleeblanch said:
Nope, you weren't doing anything wrong. Read my reply above. Any build from April 6th on shouldn't have any issues. I spent the last couple days figuring this out lol
Click to expand...
Click to collapse
Well, for me it did not took days, but turned me mad the same way I think ;o)
Just a quick quick question:
Will I just have to reflash the respective build you mention or will a simple OTA update do the same?
And very important: Will an OTA update run through and not hang in the bootloader, which was an issue also. (Stucked in a scrambled bootloader causing a stock reflash...)
Thanks a lot!
Moto Gestures?
mmxthorn said:
Moto Gestures?
Click to expand...
Click to collapse
Moto Gestures are not part of AOSP, so no.
chincheta0815 said:
Well, for me it did not took days, but turned me mad the same way I think ;o)
Just a quick quick question:
Will I just have to reflash the respective build you mention or will a simple OTA update do the same?
And very important: Will an OTA update run through and not hang in the bootloader, which was an issue also. (Stucked in a scrambled bootloader causing a stock reflash...)
Thanks a lot!
Click to expand...
Click to collapse
Starting with the next nightly (20200406) you'll be able to OTA update without any issues. Just flash the next build that gets released in twrp and after that you'll be fine. The builds don't flash the bootloader, but bootctrl and gpt-utils do as they are past of what makes the magic of "seamless updates" work, which is why previous builds were wrecking the gpt table.
mmxthorn said:
Moto Gestures?
Click to expand...
Click to collapse
Check > Settings > System > Advanced > Moto Gestures
Also, fingerprint swipe for notifications is include (disabled by default) and also found in the same place as stock (> Settings > System > Gestures)
Can I flash this over an older build of 17.1? I have the March 14th one installed and it can't find the OTA update, so I'm wondering if I can just flash this new one over it, then flash twrp and magisk without losing anything.