★ ☆[ROM][4.4][UNOFFICIAL] CyanogenMod 11 | Alpha.02 | tiKtaK [12-06-13]☆ ★
Unofficial
Cyanogenmod 11
HTC Fireball
I don't usually develop for devices I don't have.
But I saw you guys had no KitKat love over here yet, so I thought I'd give it a shot for you.
Please realize this is completely untested, as I do not have this device.
I have a Thunderbolt, a DNA, and an HTC One.
So just be aware of that and be kind to me, lol.
I hope it boots and is somewhat usable!
I look forward to hearing the results.
It is built using the latest CM sources.
***EDIT: It boots and has working 4G/LTE, wifi, and GPS!
KitKat -- Android 4.4 -- CM11
DISCLAIMER:
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 CANNOT BLAME ME or anyone else for causing harm to your device.
Click to expand...
Click to collapse
CyanogenMod (pronounced sigh-AN-oh-jen-mod), is a customized, aftermarket firmware distribution for several Android devices.
Based on the Android Open Source Project, CyanogenMod is designed to increase performance and reliability over Android-based ROMs released by vendors and carriers such as Google, T-Mobile, HTC, etc.
CyanogenMod also offers a variety of features & enhancements that are not currently found in these versions of Android.
{
"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"
}
While this build is heavily optimized, it is also capable of pushing your phone much harder.
CyanogenMod and it’s team hold no responsibility to any damage caused to your phone, loss of earnings as a result of damaging your phone or anything else that is connected to the development of this rom.
For a list of devices officially supported by CyanogenMod, check out the official devices page.
Such is the craze for CyanogenMod, that devices that aren’t officially supported, still manage to receive ports of the ROM courtesy of enthusiasts and developers.
CyanogenMod offers the most barebone Android experience coupled with some very powerful tweaks.
This whole package by now is not wholly developed by CyanogenMod developers alone, but is a collaborative effort between them and independent developers around the world.
DOWNLOAD:
cm-11-20131206-UNOFFICIAL-fireball
4.4 Gapps
You will likely need an updated recovery.
Assuming that is the case, I will provide the one that compiled with my build.
ClockWorkMod KK compatible recovery image
Old Versions:
cm-11-20131202-UNOFFICIAL-fireball
Source: CM Github
Thanks for trying my build....
Just in case....
I tried to install using TWRP 2.6.3.0. It seemed to mostly work until...
Code:
Creating Symlinks...
ApplyParsedPerms: removexattr of /system/addon.d/50-cm.sh to 0 failed: Operation not supported on transport endpoint
script aborted: set_metadata_recursive: some changes failed
set_metadata_recursive: some changes failed
E:Error executing updater binary in zip '/sdcard/cm-11-20131202-UNOFFICIAL-fireball.zip'
Error flashing zip '/sdcard/cm-11-20131202-UNOFFICIAL-fireball.zip'
After this, the device just bootloops.
I'm going to try again using the recovery.img referenced in the first post.
EDIT: After flasing the CWM recovery from the first, I was able to install. My phone is booting up....
And success! It booted. I made a phone call. I have 4G/LTE. WOW! I'll test some more tonight and report any issues I discover.
EDIT2: The first boot after installing gapps-kk crashed and rebooted the phone. The second boot hung at the "Android is upgrading..." screen with the message "Optimizing app 1 of 21". During this, I checked the CPU usage and found that /system/bin/mpdecision was using 100% of the CPU. After a few minutes I pulled the battery and restarted the phone. This time, with it unplugged (it was connected via USB to my laptop in all previous tests). It completed booting and finished the Android upgrade.
I was able to setup my Google account and download apps over 4G/LTE.
Google Keyboard, Google Search, and Google + were all out-of-date and got updated.
I briefly tested the GPS using "GPS Test" from CHARTCROSS LIMITED. The GPS worked and I got a lock quickly.
I tested WiFi on both 2.4, and 5 GHz both worked reliably for the brief period I tested.
The only thing I find lacking (and it's lacking in ALL non-stock-based ROMs) is the ability for an app to read the secure element of the SIM. This is a requirement for the ISIS contactless payment system - which I use A LOT. So, even though I'd really love to be on KK, I'll be reverting back soon.
-xdadevelopers-user
xdadevelopers-user said:
I tried to install using TWRP 2.6.3.0. It seemed to mostly work until...
Code:
Creating Symlinks...
ApplyParsedPerms: removexattr of /system/addon.d/50-cm.sh to 0 failed: Operation not supported on transport endpoint
script aborted: set_metadata_recursive: some changes failed
set_metadata_recursive: some changes failed
E:Error executing updater binary in zip '/sdcard/cm-11-20131202-UNOFFICIAL-fireball.zip'
Error flashing zip '/sdcard/cm-11-20131202-UNOFFICIAL-fireball.zip'
After this, the device just bootloops.
I'm going to try again using the recovery.img referenced in the first post.
EDIT: After flasing the CWM recovery from the first, I was able to install. My phone is booting up....
And success! It booted. I made a phone call. I have 4G/LTE. WOW! I'll test some more tonight and report any issues I discover.
-xdadevelopers-user
Click to expand...
Click to collapse
Thank you for testing and reporting back! :good:
Can confirm it boots and runs very well after updating recovery. Great job!
Please for HTC Thunderbolt Sir Santod:victory:
wow - great news!
This works very well considering. I haven't experienced any major drawbacks yet. WiFi, GPS, LTE, Bluetooth all work great and I have no problems sending or receiving texts or pictures, the only thing I have really noticed is that the native browser force closed on me. I downloaded chrome and all is good. I did redo the RUU because of a borked radio but that was from the last time I installed 10.2.
Sent from my Incredible 4G LTE using xda app-developers app
I had the same issue with installing, worked flawless when using the specified CWM.
Camera, 4g, calls, wifi, gps everything worked.
1 main issue I ran into is multiple FC when using messaging or hangouts to text
I have not had any fc 's for messages and I don't use hangouts. I forgot to mention the camera works well and it's even oc'd to 1.5 GHz, which works well. This is the best alpha build I've ever ran. I did have to use the CWM recovery provided also, forgot to mention that.
Sent from my Incredible 4G LTE using xda app-developers app
By far the BEST alpha ever..... I did have to use the recovery specified
No fc so far and ran it for the better part of yesterday and overnight ... Will report back on battery life tonight
One question , how do you add home screens
When you go to the widgets page and touch and hold the one you want then you can add it to the left or the right of the home screen and it will add a page for you.
I have noticed that the ear piece volume is pretty low during phone calls, I know this was/is an issue with other CM builds, I don't know of a fix for this. Does anyone else?
About to flash soon reboot back how to works for me! Thanks for you efforts Dev!! Awesome that you are building us cm11 and don't even have the device!
Sent from my LG-G2 using Tapatalk
What are the recommended install steps? I am rooted and S-off. Thanks for your hard work! Currently running Viper.
Sent from my ADR6410LVW using Tapatalk
Flashed CWM, then the zips, wiped davlik
1st boot: restarted during CM splash screen
2nd boot: got to "Optimizing app" but was going extremely slow (this has been happening alot lately with other builds)
3rd boot: seems good
I wish there were a way I could restore a TWRP backup using CWM so I could jump back to 10.2 quickly if needed
EDIT: Oh I guess I could have just down a backup in CWM before flashing CM11. Oh well
j3grizz said:
What are the recommended install steps? I am rooted and S-off. Thanks for your hard work! Currently running Viper.
Sent from my ADR6410LVW using Tapatalk
Click to expand...
Click to collapse
Flash the stock recovery: adb fastboot flash recovery nameoffile.img
Do a factory reset/wipe data in Recovery
Flash the rom and flash Gapps
reboot
enricong said:
Flashed CWM, then the zips, wiped davlik
1st boot: restarted during CM splash screen
2nd boot: got to "Optimizing app" but was going extremely slow (this has been happening alot lately with other builds)
3rd boot: seems good
I wish there were a way I could restore a TWRP backup using CWM so I could jump back to 10.2 quickly if needed
EDIT: Oh I guess I could have just down a backup in CWM before flashing CM11. Oh well
Click to expand...
Click to collapse
There is no need to wipe dalvik after flashing the rom, that creates issues.
As the dalvik hasn't even built yet and now its gonna try and optimize on first boot.
Let me know if you guys want more builds/updates/nightlies?/weeklies?....
Or is there not very many folks left on the device that are interested?
Glad the initial build is working out well.
Great Thx!
---------- Post added at 09:24 PM ---------- Previous post was at 09:10 PM ----------
I would be willing to try weeklies. This looks like it could be a great rom. I will post after I flash it. Thanks again.
OK just finished running for the day and with moderate usage
Dozen or so phone calls....
40+ text/chats
15min of navigation
And various web searches
Took it off the charger at 5:30am
8% at 7:30 pm
About the same or just a touch better than what I had with cm 10 or stock
enricong said:
I wish there were a way I could restore a TWRP backup using CWM so I could jump back to 10.2 quickly if needed
EDIT: Oh I guess I could have just down a backup in CWM before flashing CM11. Oh well
Click to expand...
Click to collapse
Assuming you didn't delete the TWRP backup you could always just reflash TWRP and then restore like normal.
Sent from my XT1060 using xda app-developers app
Related
A flashback to when ROM was first booted ... the good ol' days.
SBF is now available on the Team Black Hat App that can be had from Android Market.
Team DeFuse Presents
Vanilla Android 2.4.3
Only use themes made for 2.4.X if you want to keep lots of new features in Fission!!!
Video Install Guides for Fission ROM Manager can be found HERE. Thank you darkonion for making the vids
Text version of instructions located below.
{
"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"
}
About Us & ROM:
The first generic Android platform for current and future Droid devices. We are a bunch of mad hackers, modders and developers that were not happy with the current model of Droids being "Blurred" so we began a mission to rid our devices from the blurriness of VZW Android systems. It started with a crazy idea of messing with the Droid2 SDK that has turned into a full fledge AOSP generic type of ROM. We have incorporated many features that were only seen in AOSP ROMs before this. Some of the features include Reboot in Power Menu, custom built Framework, vanilla Android GUI, totally blur free app folder and many more AOSP like features to come in the short term future.
Features:
True Vanilla ROM with generic Android feel, not themed to look line one. No blur apps...
Reboot in Power Menu.
Custom Framework - 10% battery increments with display percent number & without.
Overclock ready out of box.
Lots of free memory.
ROM has root and has been deodexed, and zip alligned.
Busybox installed and symlinks have been applied.
Clean base for you to customize how you like.
And many more...
Fission ROM Manager:
Fission ROM Manager (FRM) is a utility we developed to make modifying your Droid phones much easier. It was designed for the new Android user but also very useful for the more advanced user. You can download ROMs, themes, updates add ons and much more. Once your downloads are done you can install everything within Android. No need to go into recovery any more.
HotFix:
Please see download links for new patches.
Team DeFuse Members:
Developers
AngDroid - Team Leader, Project Manager & Developer
braway - Developer
Drod2169 - Developer
Requiem4D - Developer, IT dude & Kernel Specialist
IRC & Forum Support
WalCs - Support Manager - Developer Assistant
Themers
javroch
MJones1052
barracuda
Joe772
tgwaste
StuntinX
draya1986
Web Design & Maintenance
WebKaiser
Jcatt
Web:
Team DeFuse
IRC:
IRC Server - Freenode.net
Chanel #teamdefuse
Twitter:
@Team DeFuse
@AngDroid
Themes:
Check Fission ROM Manager. Many themes are up.
Changelog:
2.4.2 -> 2.4.3
Removed Sound and Speach Recoder
Added new Sound Recorder that can be launched from App Draw
Added 10% Battery Display option to FRM. Will reset current theme back to Stock Fission.
2.4 -> 2.4.2
DX build gets new framework whcih should fix the random USB reboot when plugging in.
All previous fixes are now included
Latest Android Market
More Code Cleaning
Full version ROMs and Upgrades are available. Upgrade will only replace packages. It will not wipe app or framework folder.
No reason to wipe cache or data if coming from Fission ROM for either Full ROM or Upgrade.
2.2.1 -> 2.4
All Devices are now equal. Perform and look the same.
Framework improvements all around. Colors, placement of graphics...lots of little changes.
Almost all apps for each device have been rebuilt from source. Either from AOSP source or Moto source.
Each device now has device specific apps. Will help of future Blur add on. Many people been asking for many different Blur apps so there will be an add on Blur package. Blur package will be heavily modified Blur services and then each app will be an individual add on.
MMS menu compose graphic now fixed.
Phone mute fixed.
Rebuilt Moto Apps (MediaGallery, Cam and Music) are now standard. They work better and will help with Blur add on. Generic Android Apps will be available on FRM.
All devices now use Moto Multi-Touch keyboards. They are themed as Generic Android Keyboards.
More cleaning of code and tweaks...
Few other changes I can not think of right now
Small bug with Global ROM. If you need to activate, slide out keyboard and hit the number key you need to use.
No need to wipe data or cache if coming from previous Fission ROM; however the installer will wipe your system folder so back up any changes you have made to your system folder.
DO NOT USE 2.3.1 Themes. They will work but you will lose lots of changes. Themers are working hard now to update themes.
I must say these are the best Fission ROMs so far. Lots of love and hard work went into them.
Install Instructions:
All install instructions can be found on Team DeFuse Website.
Bug Reporting:
Please use Our Google Code Project Home to report bugs. You can find it HERE.
Search before posting bug. The bug may have been reported and fixed.
Donations:
Thanks to everyone who has donated. If you would like to contribute to our cause you may do so by clicking HERE, thank you very much.
Downloads:
Droid 2, Droid 2 Global, Droid X, Droid Pro & Fission ROM Manager - DOWNLOAD
By clicking the download link and proceeding to download page, you agree to that you have read everything in this post.
Click HERE if you agree.
Thanks!
im getting a 404 error in fission rom manager, ill try manual for now, just a heads up.
edit: oh...its not up yet (?)
re-edit: im super confused now, RC2 never went up that i know of, and now FRM is showing an rc3 that wont download yet either.
botnryan said:
im getting a 404 error in fission rom manager, ill try manual for now, just a heads up.
edit: oh...its not up yet (?)
re-edit: im super confused now, RC2 never went up that i know of, and now FRM is showing an rc3 that wont download yet either.
Click to expand...
Click to collapse
I work fast
RC3 is downloading fine here...you using lite or full?
well i was using lite, but i think my phones bricked now cause i tried to download the stock d2g rom from frm, flashed it, and now i cant get past the motorola M screen, cant get into bootstrap..nothing.
does this rom remove the protection against us carriers?
xryousukex said:
does this rom remove the protection against us carriers?
Click to expand...
Click to collapse
No. That's another problem entirely.
botnryan said:
well i was using lite, but i think my phones bricked now cause i tried to download the stock d2g rom from frm, flashed it, and now i cant get past the motorola M screen, cant get into bootstrap..nothing.
Click to expand...
Click to collapse
Have you tried a battery yank? If so and it didn't work try again but before turning your device back on open the slider and press and holding the 'x' button. Keeping 'x' pressed down press and hold the power button. Keep them both pressed down. You'll get the M screen but it should boot into recovery.
Sent from my DROID2 using XDA App
yyeah i can get it to boot into THAT recovery, but what good does that do?
Sorry about the market issues guys. It worked at first when I was testing and then it crashed on later when I was not home so I could not fix right away.
RC3 was fixed and uploaded again.
You may have to go back to your OEM backup or RC1/2 backup, download RC3 again install it.
My mistake and sorry...just some stuff that happens when doing this sort of thing
RC4 or finall will be on FRM Full at some today/tonight. I am putting the final touches on it now
botnryan said:
yyeah i can get it to boot into THAT recovery, but what good does that do?
Click to expand...
Click to collapse
Did you wipe cache and data from recovery? Stock or clockwork recovery will do...
Pulled RC3...damn new market keeps crashing...
RC4 will be up in a bit...
botnryan said:
yyeah i can get it to boot into THAT recovery, but what good does that do?
Click to expand...
Click to collapse
If all else fails from recovery you can install your backup and get your phone running again.
Sent from my DROID2 using XDA App
yeah about that, i wasnt expecting issues so i didnt make one :\
EDIT: called verizon, they had me load bootloader and wipe data, of course that didnt work so theyre sending me a new one
Angdroid - you mentioned on your twitter about getting it to work on AT&T and needed a Tmo sim to test, so what rom will this work-around be included in? Thanks!
botnryan said:
yeah about that, i wasnt expecting issues so i didnt make one :\
EDIT: called verizon, they had me load bootloader and wipe data, of course that didnt work so theyre sending me a new one
Click to expand...
Click to collapse
Can you get into clockwork recovery? If so I have an OEM image that you can use.
Rule number 1, always make a back up
noope, only stock recovery.
this is my first android device ive rooted and such so i guess ive learned my lesson about backups. sucks i had to do it the hard way but i guess im a little hard headed. at least i can get it replaced :\
Great job guys. Keep up the good work!
Final or RC5 should be out later tonight. I have one more bug to kill and it will be gold
Any find any issues so far with RC4?
Using rc3, only issue i have is the lack of the reboot option on power button press, and in call menu stuff. Idk if those were updated in rc4 or rc5but im just sayin.
Sent from my DROID2 GLOBAL using XDA App
I don't see the normal post from AngDroid but it appears RC5 is on FRM. Running it right now without any initial issues.
{
"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"
}
CyanogenMod is a free, community built, aftermarket firmware distribution of Android, which is designed to increase performance and reliability over stock Android for your device.
Code:
* 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.
*
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. You will need to provide your own Google Applications package (gapps). 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 our Gerrit Code Review. Your changelog is whatever was merged into gerrit.
CyanogenMod 13 Changelogs
Instructions
First time flashing CyanogenMod 13 your device, or coming from another ROM?
Official long version:
Installing CyanogenMod from recovery
Short version:
1. Download the zip(s) from the download section below.
2. Install a compatible Recovery
3. Perform a NANDroid backup of your current ROM (Optional)
4. Perform a Factory reset (wipe data & cache partitions of your device)
5. Flash your CyanogenMod zip file
6. Optional: Install Google Apps
Downloads
Official CM13 Nightlies
TWRP Recovery
Official Open GApps (Choose the nano version or smaller. The other versions won't fit.)
Open GApps XDA-Thread
Note: Some GApps are very basic & will give you only Google app & Google Play Store. The rest of the apps can be downloaded directly from the Play Store as per your need after signing in to the Google. If calender syncing is not working so there is an additional script for that, just flash it & voila it will start working.
Bugreports
On nightlies, you don't have to report bugs here, if you wish to, you can do that here.
Thanks!
The CyanogenMod team would like to thank everyone involved in helping with testing, coding, debugging & documenting! Enjoy.
PS: I have not built this rom, I don't even know if I can post this here, it's mostly a copypaste from another CM thread. If you want me to edit/remove this just tell me.
Current nightly status
I'll use this post for the current nightly build status, wether it has major issues or not. I'll try to keep this updated based on the communities replies, no guarantees though.
Current 20160219 build status: GOOD
20160129 nightly causes bootloops and was removed from get.cm. The build from 20160127 is fine, so use that instead.
Thanks for opening this thread!
Just a little note. From my experience it is quite important to wipe system as well, if you plan flashing a new ROM. Of course this depends on the previous ROM. Most of the times it might not be necessary, but for me it is "best practice".
Might need to get the AOK from mods about this thread, but hopefully will be ok, makes sense to get cm13 one by now.
Hi, thx for this thread. I love Cyanogenmod from version 6 and I was very happy, that came CM13 MM, but with a few last builds I have trouble with lags. After reboot is several hours everything OK, but after that I have several seconds lags when I want run some application (or wake from recent apps).
The same trouble was in last builds CM12.1. Let me know, if exist some solution? Now I must left CM13 (to Chroma and lags are gone), but I want come back, but without lags...
Do you have some of you the same trouble?
Odesláno z mého Nexus 4 pomocí Tapatalk
sigulda1 said:
Thanks for opening this thread!
Just a little note. From my experience it is quite important to wipe system as well, if you plan flashing a new ROM. Of course this depends on the previous ROM. Most of the times it might not be necessary, but for me it is "best practice".
Click to expand...
Click to collapse
Had to research it because I wasn't sure about this part either (I copy pasted it from the old thread..) but apparantly a Factory reset is the way to go as CM installs wipe the system partition anyways. Manually wiping the system partition actually seems to cause some issues. The official instructions don't mention wiping system either. Thanks for the feedback though.
Nilsb7 said:
Manually wiping the system partition actually seems to cause some issues.
Click to expand...
Click to collapse
Huh? Never heard that before, any sources?
Sent from my Nexus 4 using Tapatalk
Nilsb7 said:
Had to research it because I wasn't sure about this part either (I copy pasted it from the old thread..) but apparantly a Factory reset is the way to go as CM installs wipe the system partition anyways. Manually wiping the system partition actually seems to cause some issues. The official instructions don't mention wiping system either. Thanks for the feedback though.
Click to expand...
Click to collapse
bringonblink said:
Huh? Never heard that before, any sources?
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
Manually wiping the system partition causes no problems at all. It simply wipes the ROM, and when flashing a new build, will replace it. Unless you are using CyanDelta, wiping the System should not cause any problems. I, for one has not gone through any problems while wiping my system partition.
bringonblink said:
Huh? Never heard that before, any sources?
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
xWolf13 said:
Manually wiping the system partition causes no problems at all. It simply wipes the ROM, and when flashing a new build, will replace it. Unless you are using CyanDelta, wiping the System should not cause any problems. I, for one has not gone through any problems while wiping my system partition.
Click to expand...
Click to collapse
Had some problems with this myself when trying to update from CM12 to CM13, I tried to only wipe /system though, because I was trying to get rid of a buggy/unkown gapps installation, and this caused error messages to pop up when trying to flash the CM13 version in TWRP. Can't find any sources for this besides this one though, this was the only one I found when searching before so I assumed it was right.
Guess I was wrong? .
Nilsb7 said:
Had some problems with this myself when trying to update from CM12 to CM13, I tried to only wipe /system though, because I was trying to get rid of a buggy/unkown gapps installation, and this caused error messages to pop up when trying to flash the CM13 version in TWRP. Can't find any sources for this besides this one though, this was the only one I found when searching before so I assumed it was right.
Guess I was wrong? .
Click to expand...
Click to collapse
Oh if you're flashing different android versions without doing a full wipe, yeah you're gonna get problems
bringonblink said:
Oh if you're flashing different android versions without doing a full wipe, yeah you're gonna get problems
Click to expand...
Click to collapse
Dirty flashing was approved/recommended officially see here.
Back on topic, anyone tried the 20160201 nightly yet?
Nilsb7 said:
Dirty flashing was approved/recommended officially see here.
Back on topic, anyone tried the 20160201 nightly yet?
Click to expand...
Click to collapse
I'm using it, no problems so far
Edit
Seem to be getting a huge "sns_async_ev and sns_periodic wakelock" wakelock. Actually not letting the device sleep at all. Looks to be related to the hardware sensors.
Can anyone else check if they have this?
Sent from my Nexus 4 using Tapatalk
bringonblink said:
I'm using it, no problems so far
Edit
Seem to be getting a huge "sns_async_ev and sns_periodic wakelock" wakelock. Actually not letting the device sleep at all. Looks to be related to the hardware sensors.
Can anyone else check if they have this?
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
I'm on 20160201 and I don't have that issue. Here's a screenshot of my battery stats, the long wake periods are caused by my audiobook player.
Nilsb7 said:
I'm on 20160201 and I don't have that issue. Here's a screenshot of my battery stats, the long wake periods are caused by my audiobook player.
Click to expand...
Click to collapse
Something strange is going on, just did an hour test, where the phone did not go into deep sleep at all (from the wake lock, however drain seemed good at -1%an hour.
You can see from the pic it stays awake, but no battery drop off :s
Sent from my Nexus 4 using Tapatalk
bringonblink said:
Something strange is going on, just did an hour test, where the phone did not go into deep sleep at all (from the wake lock, however drain seemed good at -1%an hour.
You can see from the pic it stays awake, but no battery drop off :s
View attachment 3631357
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
Have you tried rebooting it at least once after flashing the nightly?
I´m having problems enabling the WIFI after 4 days using the CM13.... it is very strange.
What I have tryed,
-Fly mode on - off
-Flashing the Radio
-Wiping cache with TWRP
Still not working
You can find some screenshots attached....
izuels said:
I´m having problems enabling the WIFI after 4 days using the CM13.... it is very strange.
What I have tryed,
-Fly mode on - off
-Flashing the Radio
-Wiping cache with TWRP
Still not working
You can find some screenshots attached....
Click to expand...
Click to collapse
Try the latest nightly, this might be related.
Nilsb7 said:
Try the latest nightly, this might be related.
Click to expand...
Click to collapse
That was.... now after installing the last Nightly it works :/
I found also that the APP which is giving problems is https://play.google.com/store/apps/details?id=com.ryanamaral.wifi.passwords
im on the 20160202 nightly and everything seems fine except for the user profiles, it looks like they dont do much, i set a profile that toggles from 3g to 2g when connected to wifi but nothing happens. what else... the weather isn't displayed in the status bar and in the clock widget... multiple APN for the same carrier that sometimes disables the whole network until setting up the correct APN... but other than that its flawless. i rather stick to cm13 nightly than going LL or custom MM.
Sent from my Nexus 4 using Tapatalk
I installed nightly 2016-02-06. Everything looks fine since 24hours.
But CM has chosen the wrong APN : Wap.vodafone.de instead of web.vodafone.de
{
"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"
}
Hey how's it goin' guys! This is my first ever ROM I built, so here it is! Introducing AeroROM!
DISCLAIMER: You should bear in mind that flashing this Custom ROM will void your warranty. Therefore, I am not in any way responsible for any damages (Bricks, Fried Accessories, etc.) that may occur from performing these modifications. You are choosing to do this, it's not me forcing you to flash this ROM, lol
FEATURES
Systemless Root w/ SuperSU (Which is why you don't see "KERNEL IS NOT SEANDROID ENFORCING" at boot)
Built In BusyBox
Killed Knox
Obliterated all unnecessary Samsung bloat
DeOdexed apps
DPI Tweak for more screen real-estate
More under-the-hood build.prop tweaks for improved overall performance
Minimal AeroROM breathing boot animation so it doesn't attack your eyes
Lightweight, Fluid, and Snappy
INCLUDED APPS
Viper4Android FX | A feature-packed EQ app For an enhanced audio experience
Nova Launcher | One of the most widely used launchers
ES File Explorer | An advanced file explorer app, includes root browsing
UC Mini | A reliable web browser
SuperSU | Root management
(New with v1.1) AdAway | Blocks Ads
COMPATIBLE DEVICES
Samsung Galaxy Core Prime MetroPCS variant (SM-G360T1)
And *possibly* the T-Mobile variant (SM-G360T), I do not own it so I would definitely appreciate someone confirming that for me.
INSTALLATION
1 Make sure you have the right device, if you do then you may proceed.
2 Install Root and TWRP if you haven't already
3 Copy the ROM and GApps .zip files to your Internal SDCard
4 Now this is the fun part, lol. Reboot into your recovery, swipe to allow modifications if you haven't already. Then perform a factory reset by wiping the Data, Dalvik/ART Cache, Cache, and System. Once that's out of the way, flash the ROM itself first, then the GApps package.
5 Hit Reboot. Then STOP RIGHT THERE! Once the part that says SuperSU doesn't appear to be installed, hit the Do Not Install button. SuperSU does come with this ROM, it's just the method of installation.
6 Proceed with rebooting, and give it a couple of minutes. It takes this long to boot because of the DeOdexed nature of the ROM, but don't worry, this only happens once!
7 Now it's all yours to enjoy!
You can use either TWRP 2.8.70 or 3.0.1, they both work well in flashing this ROM
GAPPS
To keep a minimal file size, GApps were removed as part of the debloat process. You can get some really good GApps packages from Opengapps.org. Be sure to choose ARM as the Platform, 5.1 as the Android Version, then the GApps flavor is all up to you!
DOWNLOAD
v1.1b
https://mega.nz/#!c1AngIqb!_ZD3kHda2EmvrI9tvqgwPPuu7n2w4nCl9SWMTFiF-9U
SPECIAL THANKS
@ShinySide | TrapKernel Root Kernel
@SuperR | For his Kitchen
@Chainfire | For SuperSU
@ViPER520 | For the Viper4Android FX Mod
XDA:DevDB Information
AeroROM, ROM for the Samsung Galaxy Core Prime
Contributors
FazPhantom
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.10.x
ROM Firmware Required: 5.1.1 Stock w/ Root & TWRP
Based On: TouchWiz Stock [AOFA]
Version Information
Status: Stable
Created 2017-05-07
Last Updated 2018-03-31
LATEST
v1.1b - This update reverts the Google WebView debloat which causes some users to stay stuck in the checking info screen. Hopefully this update resolves everything.
KNOWN ISSUES
WiFi Calling + VoLTE unavailable.
PREVIOUS
v1.1 - Fixes broken Mobile Hotspot and adds AdAway Ad blocker
v1.0 - Initial Release
KNOWN ISSUES
Mobile Hotspot doesn't work. Will be fixed ASAP.
EXTRAS
Get the newest emojis on your device!
Samsung's firmware for this phone in particular comes with a set of outdated emojis that may interfere with how you see various emojis, new and old, that may be on your screen. Some new emojis come as black boxes, which isn't really good. Therefore, I'll walk you guys through updating the emojis on this ROM (or whatever ROM you may be using on this device)
Prerequisites: Any root explorer app and root access.
1: Choose your emoji flavor. Some of them are...
EmojiOne (Select emojione-android.ttf)
Android Oreo
You are not limited to these options!
Now, make sure the emoji file you downloaded is a font file (.ttf) and rename it to NotoColorEmoji (That should already be the case if you downloaded the Android Oreo emojis)
Head into system/fonts and back up the existing NotoColorEmoji to somewhere else. Then go back to the new emojis you just downloaded, and move that over to system/fonts.
Lastly, set the permissions of the font file to rw-r-r so the system can detect the new set of emojis. This is important, otherwise it won't work.
Now restart your device, and boom, enjoy your brand new emojis! Use with Gboard for best results.
Any New User Interface? Screen shots please?
Kani08 said:
Any New User Interface? Screen shots please?
Click to expand...
Click to collapse
Screenshots are now in the screenshots tab.
I will try it when I have time however I can say rather confidently that this will work on the SM-G360T. The two phones are exactly the same with different branding.
FazPhantom said:
Screenshots are now in the screenshots tab.
Click to expand...
Click to collapse
OK kool, I am waiting for more users to test before I try it.
Anyone tried it as yet? How's it going so far?
Kani08 said:
Anyone tried it as yet? How's it going so far?
Click to expand...
Click to collapse
I'm personally running my own ROM on my own Core Prime and so far so good! Didn't notice any issues with calling or LTE or WiFi or any of the much needed stuff.
FazPhantom said:
I'm personally running my own ROM on my own Core Prime and so far so good! Didn't notice any issues with calling or LTE or WiFi or any of the much needed stuff.
Click to expand...
Click to collapse
Where is the link to download? If it's that good then share it. Thanks.
Kani08 said:
Where is the link to download? If it's that good then share it. Thanks.
Click to expand...
Click to collapse
Lol it's in the post itself, the link with the mega.co.nz, that's where you can download the ROM
35 Minutes, and still only see AEROROM. Vibrations occur every few seconds, like 15s. Tried first without wiping DATA, and then was taking excruciatingly long, so I went back and wiped everything twice, and then re installed without GAPPS, and 35 minutes so far. Will report any further changes. BUt honestly, this phone bootloops for literally nothing mostly. Haven't had such an unstable Samsung device ever. Kinda hate this phone now, always fixing, never can get calls or anything. Bout to just toss it in the trash. I appreciate the work you've done op, thank you. I've been looking, but is there anyway to port Resurrection Remix 5.7.4 from the 360h over to this phone, It's my personal favorite rom, and on every device since it dropped. I dont mind spending a few hours trying, but I can't build it from source.
Lucairian said:
35 Minutes, and still only see AEROROM. Vibrations occur every few seconds, like 15s. Tried first without wiping DATA, and then was taking excruciatingly long, so I went back and wiped everything twice, and then re installed without GAPPS, and 35 minutes so far. Will report any further changes. BUt honestly, this phone bootloops for literally nothing mostly. Haven't had such an unstable Samsung device ever. Kinda hate this phone now, always fixing, never can get calls or anything. Bout to just toss it in the trash. I appreciate the work you've done op, thank you. I've been looking, but is there anyway to port Resurrection Remix 5.7.4 from the 360h over to this phone, It's my personal favorite rom, and on every device since it dropped. I dont mind spending a few hours trying, but I can't build it from source.
Click to expand...
Click to collapse
That's not good, I think I gotta take this down if it isn't very stable. Weird though, I flashed it on my G360T1 and it booted up just fine. If a few more people report instability in this ROM then I'm taking it down, I've given up hope, CM or lineage won't be built for it at all, I doubt it'll happen at all.
But yeah what I would do is wipe every single thing including internal storage, then turn the phone off, flash stock firmware via Odin, and it should be able to fix things up
FazPhantom said:
That's not good, I think I gotta take this down if it isn't very stable. Weird though, I flashed it on my G360T1 and it booted up just fine. If a few more people report instability in this ROM then I'm taking it down, I've given up hope, CM or lineage won't be built for it at all, I doubt it'll happen at all.
But yeah what I would do is wipe every single thing including internal storage, then turn the phone off, flash stock firmware via Odin, and it should be able to fix things up
Click to expand...
Click to collapse
Went go take a bath, and phone is still on AEROROM, slowly fading in and out. I'm going to put stock and try from there. I'd really like a different rom other than SLIM PICKINS. Effing gravitybox causes bootloop, can't theme it black like every other device, even though I do a bit of **** for TBO, but not offically, I just want evrything to be black, but everything I try crashes and bootloops. Good thing I got this phone for free from a repair job. I appreciate your working on a new rom though, hopefully I can get it to work. I'll see if I could pull a logcat for you. Someone needs to dev a phone emulator so people like us could test on devices. I was all excited to see this, so I'll blow through a few hours, and anything I can devise from it, I'll post for you. Maybe together something might happen. I'd hate to see you have to pull it.:crying:
EDIT: Does the versions of twrp that are available work well on your device? Any twrp3 I put, the touch refuses to work. So I'm stuck on 2.8.7.0. blows dogs for quarters...
Lucairian said:
Went go take a bath, and phone is still on AEROROM, slowly fading in and out. I'm going to put stock and try from there. I'd really like a different rom other than SLIM PICKINS. Effing gravitybox causes bootloop, can't theme it black like every other device, even though I do a bit of **** for TBO, but not offically, I just want evrything to be black, but everything I try crashes and bootloops. Good thing I got this phone for free from a repair job. I appreciate your working on a new rom though, hopefully I can get it to work. I'll see if I could pull a logcat for you. Someone needs to dev a phone emulator so people like us could test on devices. I was all excited to see this, so I'll blow through a few hours, and anything I can devise from it, I'll post for you. Maybe together something might happen. I'd hate to see you have to pull it.:crying:
EDIT: Does the versions of twrp that are available work well on your device? Any twrp3 I put, the touch refuses to work. So I'm stuck on 2.8.7.0. blows dogs for quarters...
Click to expand...
Click to collapse
I'm not necessarily developing a totally AOSP-based ROM as this is a totally different case for me, but I'm getting used to making these stock-firmware based ROMs
And the twrp 3.0.1 I used was made by another dev, not downloaded from the official twrp site so I can give you the link to it if you're interested:
https://www.androidfilehost.com/?fid=24459283995316038
I need a rom for my galaxy core prime that will change the UI and optimize performance. I need more ram free. I have version 360gt1 core prime.. Any Miui roms etc available?
Kani08 said:
I need a rom for my galaxy core prime that will change the UI and optimize performance. I need more ram free. I have version 360gt1 core prime.. Any Miui roms etc available?
Click to expand...
Click to collapse
What's really stupid is that it's 2017, it's been rooted, and there still hasn't been any AOSP ROMs such as Lineage or MiUI made for it yet. Like, has this phone been abandoned?
FazPhantom said:
I'm not necessarily developing a totally AOSP-based ROM as this is a totally different case for me, but I'm getting used to making these stock-firmware based ROMs
And the twrp 3.0.1 I used was made by another dev, not downloaded from the official twrp site so I can give you the link to it if you're interested:
https://www.androidfilehost.com/?fid=24459283995316038
Click to expand...
Click to collapse
Dude, thank you. I had already visited and downloaded that one, but it never worked, until last night. OK, so I tried multiple things, wiped every single partition clean, installed stock, (and didn't on the 2nd try) and tried using my own boot.img, and multiple other files, ended up falling asleep with phone in hand, Woke up to still AEROROM fading in and out.
I have a few jobs (I do pc, cell phone repair) and then gotta go sight in a rifle for my cousin today, so I won't be back and able to continue testing today. So sorry I cannot help further for the day.
I have a favor to ask, although technically, you've done a eff-ton for me by the twrp3 thing, but I would completely understand if you don't have time, or would rather not. You know the themes for twrp, fichl's flashable? If you know them, there's a multitude of colors, and bird333's darker purple theme, is my ****, ya knoso if you could possibly get me a flashable version of your bootanimation of AEROROM, (esp with the O with the slash, as that's how I write mine irl) in that color, I would be frigging ecstatic. And I feel like an ass, but if you would do that, I have a very small request to add to that, if you could possibly add my logo to the bottomof the bootanimation, I would flip out. I custom the **** out of everythingbut have yet to work on sammys, so it would be a massive learning curve for something so "simple" and I only ask because you technically have all the resources available to do so. If it's too much trouble, No problem, I totally totally, understand, but grateful is not strong enough of a word to express how I would feel. It's not that I want to "take" your work, it's just that it's an extra thing that gets people wanting me to do those type of things for them, since I'm unemployed,trying to start a small busisness, but I'm a total recluse, so pimped out phone is a great convo starter for me. Geez, Ik I'm rambling, but just woke up. I'll attach my emblem which is just the matrix font, on a matrix bgrnd, of XIIIMACHINE, because I'm not artistic. Sorry to type your, or rather everyone's head off here. sorry! Hopefully, this Rom can get sorted out, and as soon as I get home tonight, I will jump on it, give a hand wherever possible.
Thank you very much for your work, and effort. Keep it up.
https://drive.google.com/open?id=0B5n3TgqFg-TyWEM1aDdxTVRfN2s
https://drive.google.com/open?id=0B5n3TgqFg-TycGF6cTFReWpaYVU
Please make Lineage OS for Samsung Galaxy Core Prime SM-360T1
Doesn't pass
On the tmobile varient (SM-G360T), it doesn't get passed on the "checking info" transition when setting up the device for the first time.
LineageOS is a free, community built distribution of Android which greatly extends the capabilities of your phone.
{
"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:
#include <std_disclaimer.h>
All information and files — both in source and compiled form —
are provided on an as is basis. No guarantees or warranties are
given or implied. The user assumes all risks of any damages that
may occur, including but not limited to loss of data, damages
to hardware, or loss of business profits. Please use at your
own risk. Note that unless explicitly allowed by the warranty
covering your device, it should be assumed that any warranty
accompanying your device will be voided if you tamper with
either the system software or the hardware.
This is a weekly build (Wednesdays) of LineageOS 14.1 for the Sprint variant of the LG G3 (ls990).
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit our Gerrit Code Review.
If you want to help out follow the building guide and then submit a patch to our Gerrit instance.
Installation Instructions are available on the wiki but the basics are below.
*NOTE*: You must be Bump'd for this to work. This requires flashing via custom recovery *TWRP* for "ls990”.
1. Download the ROM and Open GApps (recommended Open GApps here). You are going to need to use the arm 7.1)
2. Put both on Internal Storage
3. Reboot into recovery
4. BACKUP CURRENT ROM
5. Factory Reset/Wipe if not already on LineageOS 14.1
6. Flash the ROM ***(if installing GApps flash it prior to rebooting or you will have to Factory Reset and start over)
7. Flash GApps 7.1
8. Reboot
9. wait... wait... wait...
10. Profit
To get root/SU, flash the arm su package available in the "Extras" download section or here.
Weekly builds
Working:
Almost everything
Known issues:
None at this time. List any others and I will try to get them working as I have time
@invisiblek deserves most of the credit for this project
LineageOS Blog
LineageOS Wiki
LineageOS Community
LineageOS Status
LineageOS Google+
Best rom ever for this device i came from resurrection remix .. pixel .. fulmics ... crdroid .. this one is better than all of them.
In camera app there is no 4k recrding option but you can use other camera apps and get this option. thermal and performance is just fine but not like stock 6.0 based roms but better than RR rom. Tnx a lot for keeping cyanogenmod alive
this rom have some problems with gapps some of them not install complietly and some of them don't work ...
Beautiful ROM! S'much appreciated.
Settings, More, Cellular Network, Carrier Settings produces the error:com.android.phone has stopped
Open app again. There is a reload/refresh circular button to click on the second line before "Open app again".
Having issues locating where/how to update PRL due to horrid DATA reception which is nothing new to this location.
Freedompop is the carrier.
LS990 running (latest) LineageOS version 14.1-20170611-NIGHTLY-ls990
Since Cell/DATA was not beautiful before the ROM Flash and horrid after, I flashed Modem VFC and although possibly imaginary, the connection is more stable but also still poorly and "apparently" not as good as before.
avibp said:
Beautiful ROM! S'much appreciated.
Settings, More, Cellular Network, Carrier Settings produces the error:com.android.phone has stopped
Open app again.
There is a reload/refresh circular button to click on the second line before "Open app again".
Having issues locating where/how to update PRL due to horrid DATA reception which is nothing new to this location.
Freedompop is the carrier.
LS990 running (latest) LineageOS version 14.1-20170611-NIGHTLY-ls990
Since Cell/DATA was not beautiful before the ROM Flash and horrid after, I flashed Modem VFC and although possibly imaginary, the connection is more stable but also still poorly and "apparently" not as good as before.
Click to expand...
Click to collapse
You need to flash stick to update prl properly but there are other options if you search for them. Carrier settings has always been an issue I'll look at giving that option again.
Flash "stock" STOCK - I was wandering around searching for a "stick" to flash. LOL Thank you very much for the reply. As a side note to this posting however the other options to refresh or update the PRL do not work as in ##72786# or *#*#72786#*#*. The later does seem to want to work but where it should normally prompt for the MSL, instead just goes to a blank screen with a dialer.
Now for the real issue: I'd like to keep as many of my applications on my ext SD card as I can. I can't move any of my applications to the ext SD card. There is an option in developer options that theoretically allows you to move all applications to the SD card, however, when this option is selected, there is still no effect.
This was an issue with marshmallow as well as CyanogenMod 13 I believe but was address appropriately in CyanogenMod 14. Again - I believe, but please don't quote me.
Thanks again for the release
hi ! thx for this rom !
my problem with this rom and others like the RR rom on my LS990 ,my phone stuck in the boot screen ,i wait for an hour but it still stuck :/ :/ :/
plzzz someone helps mee :/
ayouarti said:
hi ! thx for this rom !
my problem with this rom and others like the RR rom on my LS990 ,my phone stuck in the boot screen ,i wait for an hour but it still stuck :/ :/ :/
plzzz someone helps mee :/
Click to expand...
Click to collapse
Make sure you have the latest twrp wipe and install. If you are installing gapps make sure to install prior to reboot.
Last two builds...
Has anyone had any success booting the last two weekly builds? The 8/30 and 9/6 builds both go into a bootloop for me... the Lineage startup logo never appears... tried many things including erasing and clean installing and I get the same. Going back to 8/23, all is good again...
bgabel said:
Has anyone had any success booting the last two weekly builds? The 8/30 and 9/6 builds both go into a bootloop for me... the Lineage startup logo never appears... tried many things including erasing and clean installing and I get the same. Going back to 8/23, all is good again...
Click to expand...
Click to collapse
Try with a custom kernel
Sent from my LG-ls990 using XDA Labs
bgabel said:
Has anyone had any success booting the last two weekly builds? The 8/30 and 9/6 builds both go into a bootloop for me... the Lineage startup logo never appears... tried many things including erasing and clean installing and I get the same. Going back to 8/23, all is good again...
Click to expand...
Click to collapse
I think it was an issue with one of the CVEs that were merged but I haven't had a chance to figure out the exact issue yet. I'll get the build pulled.
[/COLOR]
Kasual52e said:
I think it was an issue with one of the CVEs that were merged but I haven't had a chance to figure out the exact issue yet. I'll get the build pulled.
Click to expand...
Click to collapse
Thanks for your reply! This ROM has been a godsend for an older phone that I am not ready to give up yet... Thanks for your work on this!!
Kasual52e said:
I think it was an issue with one of the CVEs that were merged but I haven't had a chance to figure out the exact issue yet. I'll get the build pulled.
Click to expand...
Click to collapse
I really appreciate the work done on this ROM! What I ended up doing is using a working boot NANDROID and restored that after installing the update. It worked fine for me but looking forward to future offerings with a working kernel.
I think it is this commit https://review.lineageos.org/#/c/189075/ which is causing the problem. I created the revert and I'm going to let some others test before merging. I don't expect it to be an issue and we can probably get it in before this weeks round of builds.
The latest download is available -> https://download.lineageos.org/ls990. Let me know if there are any issues with it.
Kasual52e said:
The latest download is available -> https://download.lineageos.org/ls990. Let me know if there are any issues with it.
Click to expand...
Click to collapse
I installed the latest update without any problem. The system booted up just fine. Tried Magisk this time for root and it also is working fine, passed safe net.
Secure Boot Error
I'm having some small issues with my most recent installation of Lineage OS nightly on my G3 (LS990).
I did the following:
I installed TWRP.
I advanced wiped the cache, system, and data partitions.
I flashed the LineageOS zip (lineage-14.1-20170913-nightly-ls990-signed.zip).
I wiped the dalvik cache.
I flashed the LineageOS su add on zip (addonsu-14.1-arm-signed.zip).
I flashed the GApps zip (open_gapps-arm-7.1-pico_20170914.zip).
I rebooted.
Everything seems to be going ok, but everytime I reboot, I see a "secure boot error, error 1003" at the top of my screen. Is there a way to get rid of that message? Also, is there a way to install SuperSU onto the device, or is the su add-on the root for the device? I enabled apps to have root in the developer options screen. The hash sign in the status bar at the top really bothers me for some reason. Is that something built into LineageOS or is that part of the su add-on? Is there a way to hide that?
Thanks for the help.
ExitusLSU said:
I'm having some small issues with my most recent installation of Lineage OS nightly on my G3 (LS990).
I did the following:
I installed TWRP.
I advanced wiped the cache, system, and data partitions.
I flashed the LineageOS zip (lineage-14.1-20170913-nightly-ls990-signed.zip).
I wiped the dalvik cache.
I flashed the LineageOS su add on zip (addonsu-14.1-arm-signed.zip).
I flashed the GApps zip (open_gapps-arm-7.1-pico_20170914.zip).
I rebooted.
Everything seems to be going ok, but everytime I reboot, I see a "secure boot error, error 1003" at the top of my screen. Is there a way to get rid of that message? Also, is there a way to install SuperSU onto the device, or is the su add-on the root for the device? I enabled apps to have root in the developer options screen. The hash sign in the status bar at the top really bothers me for some reason. Is that something built into LineageOS or is that part of the su add-on? Is there a way to hide that?
Thanks for the help.
Click to expand...
Click to collapse
I can't answer your question about the error message (have never seen that) but you can install Supersu without any problem. I used it on all nightlies until this one, tried Magisk this time and it also works fine.
ExitusLSU said:
I'm having some small issues with my most recent installation of Lineage OS nightly on my G3 (LS990).
I did the following:
I installed TWRP.
I advanced wiped the cache, system, and data partitions.
I flashed the LineageOS zip (lineage-14.1-20170913-nightly-ls990-signed.zip).
I wiped the dalvik cache.
I flashed the LineageOS su add on zip (addonsu-14.1-arm-signed.zip).
I flashed the GApps zip (open_gapps-arm-7.1-pico_20170914.zip).
I rebooted.
Everything seems to be going ok, but everytime I reboot, I see a "secure boot error, error 1003" at the top of my screen. Is there a way to get rid of that message? Also, is there a way to install SuperSU onto the device, or is the su add-on the root for the device? I enabled apps to have root in the developer options screen. The hash sign in the status bar at the top really bothers me for some reason. Is that something built into LineageOS or is that part of the su add-on? Is there a way to hide that?
Thanks for the help.
Click to expand...
Click to collapse
The only way to get rid of that error it's to install an older factory firmware (I think around zvb) and flash from there or go with stock. It isn't an issue but it lets you know that you aren't running a stock image. You should get it booting into TWRP and Lineage but not if you go to fastboot.
SuperSU and magisk both work fine if you don't like the stock implementation
len207 said:
I can't answer your question about the error message (have never seen that) but you can install Supersu without any problem. I used it on all nightlies until this one, tried Magisk this time and it also works fine.
Click to expand...
Click to collapse
Have you run into any issues with the cellular data connection only showing as connecting to 3g? At my house, I get 4g lte, but now LineageOS only ever shows me connected to 3g.
Thanks.
{
"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"
}
Nexus 7 2013 (Wi-Fi & LTE)
Code:
- Your warranty is now void.
- You have been warned.
- Use at your own risk.
Introduction:
This is the Official Lineage OS 18.1 thread for the Nexus 7 (2013, Wi-Fi & LTE).
Downloads:
Please follow the install instructions in your device's Wiki page linked below exactly, and make sure your device's firmware matches the required firmware listed.
Official Builds:
flox - 2013 (Wi-Fi)
debx - 2013 (LTE)
Unofficial - built once a month by me, includes GApps and Pixel goodies:
flox - 2013 (Wi-Fi)
debx - 2013 (LTE)
If you don't follow these instructions, or use 3rd party add-ons (like Magisk) please don't expect support here.
Known Bugs:
None.
Find any? Report them according to this guide.
Notes:
The only supported GApps package at the moment is MindTheGapps, linked on our Wiki page about gapps.
This device _must_ be repartitioned before installation, the only supported repartition package is the one listed in the Wiki linked above - please make sure you followed it before attempting to install!
Kernel Source: https://github.com/LineageOS/android_kernel_google_msm
Thanks for an official version!
Can we possibly get the same for deb? (LTE)
I suppose I mean debx (deb repartitioned)
Edit: oh i see your note about debx, hopefully someone with experience will jump on it.
jb- said:
Thanks for an official version!
Can we possibly get the same for deb? (LTE)
I suppose I mean debx (deb repartitioned)
Edit: oh i see your note about debx, hopefully someone with experience will jump on it.
Click to expand...
Click to collapse
See the last bullet in the "Notes" section ;p
I see followmsi has 18.1 unofficial for flo/deb, maybe he'd be interested in working on official, although don't believe there was much interest in the past.
This is fantastic. except that I can't take the risk of repartition due to broken USB port. but good to see this old device getting the love
I upgraded this device and I can't seem to go through a smooth 17.1 upgrade to 18.1 because I have a lock screen pin/pattern and every time I tried, the lock screen would crash as soon as I entered my pin. I saw that some other users had this problem on other devices, just thought I might want to bring that forward here on the new thread.
NTGDeveloper said:
I upgraded this device and I can't seem to go through a smooth 17.1 upgrade to 18.1 because I have a lock screen pin/pattern and every time I tried, the lock screen would crash as soon as I entered my pin. I saw that some other users had this problem on other devices, just thought I might want to bring that forward here on the new thread.
Click to expand...
Click to collapse
I set it up freshly using the recovery from LOS 18.1 and it worked flawlessly. I first tried TWRP but it couldnt mount /system (MindTheGapps for 18.1), so I tried the recovery built-in and it worked without a hitch.
No issues with pin/encryption using fresh method, IDK about upgrading or dirty flashing, but fresh works as it should.
GROOVYJOSHCLARK said:
I set it up freshly using the recovery from LOS 18.1 and it worked flawlessly. I first tried TWRP but it couldnt mount /system (MindTheGapps for 18.1), so I tried the recovery built-in and it worked without a hitch.
No issues with pin/encryption using fresh method, IDK about upgrading or dirty flashing, but fresh works as it should.
Click to expand...
Click to collapse
Yeah overall it works fine with a clean flash, its just upgrading the device unfortunately doesn't work. Great ROM so far!
NTGDeveloper said:
Yeah overall it works fine with a clean flash, its just upgrading the device unfortunately doesn't work. Great ROM so far!
Click to expand...
Click to collapse
Did you try coming from 10 or earlier LOS and used a dirty flash to the latest? I wouldn't expect that to work without hiccups coming from LOS 10 and dirty upgrading to LOS 11 (even official versions). Normally I have issues with /data and app FCs when I try dirty upgrading a major revision jump like that (I am not saying that's what you did) but if so, I can see it would cause headaches. I normally just backup everything and clean flash a major version jump, especially for my old tablet. I hardly ever use this thing anymore, usually my tablet sits in my work bag powered off. When I saw 18.1 dropped for my Pixels as well, I figured I would test out 18.1 on my nexus before reaching my Pixel 2, 3, or 4 (PX4 is my daily driver) but I have them all still lying around.
NTGDeveloper said:
I upgraded this device and I can't seem to go through a smooth 17.1 upgrade to 18.1 because I have a lock screen pin/pattern and every time I tried, the lock screen would crash as soon as I entered my pin. I saw that some other users had this problem on other devices, just thought I might want to bring that forward here on the new thread.
Click to expand...
Click to collapse
I had the same issue. Wiped and restored from backup.
One issue that I've noticed is that in landscape the wallpaper is distorted (Nova launcher issue?). Other than that, no issues. Thanks so much!
GROOVYJOSHCLARK said:
Did you try coming from 10 or earlier LOS and used a dirty flash to the latest? I wouldn't expect that to work without hiccups coming from LOS 10 and dirty upgrading to LOS 11 (even official versions). Normally I have issues with /data and app FCs when I try dirty upgrading a major revision jump like that (I am not saying that's what you did) but if so, I can see it would cause headaches. I normally just backup everything and clean flash a major version jump, especially for my old tablet. I hardly ever use this thing anymore, usually my tablet sits in my work bag powered off. When I saw 18.1 dropped for my Pixels as well, I figured I would test out 18.1 on my nexus before reaching my Pixel 2, 3, or 4 (PX4 is my daily driver) but I have them all still lying around.
Click to expand...
Click to collapse
They do advertise in the Wiki that dirty flashing from one official version to another is technically supported, but I see why it wouldn't be because Android 11 removed an encryption/lock screen thing that was supposedly obsolete, which I think affected the Nexus 7? But overall idk. Its no big deal anyway for me, I just hope that the same doesn't happen to my phone
Awesome, thanks!
NTGDeveloper said:
I upgraded this device and I can't seem to go through a smooth 17.1 upgrade to 18.1 because I have a lock screen pin/pattern and every time I tried, the lock screen would crash as soon as I entered my pin. I saw that some other users had this problem on other devices, just thought I might want to bring that forward here on the new thread.
Click to expand...
Click to collapse
I didn't have lock screen pin/pattern enabled (just swipe) and dirty flashing 18.1 on top of 17.1 worked just fine. (At least I'm not aware of any problems yet.)
So, if you plan to upgrade from 17.1 to 18.1, I recommend disabling screen lock pin/pattern before the upgrade.
I´m triying to install it for the first time on my nexus 7 (wifi), but when I do:
fastboot boot lineage-18.1-20210401-recovery-flox.img
On console the result is:
Sending 'boot.img' (10880 KB) OKAY [ 1.392s]
Booting OKAY [ 0.000s]
Finished. Total time: 1.438s
And in the nexus I´m getting the text "Booting downloaded image" but nothing else happens and gets stucked there.
Any idea?
Perspective from guy that installed LOS 14 some years ago and was dismayed that official upgrades halted because of partitioning.
It took a couple days. The XP laptop that got me to LOS 14 doesn't seem up to LOS 18. I installed ADB & Fastboot on Win 7 PC that I almost never use after seeing signature error, but of course sig err didn't go away on Win 7. some bonus in that USB connection less flaky.
Sideloads of repartition and MindTheGapps produce signature
errors. In the recovery dialog you need to ignore the error and select "Yes" when asked if you really want to apply the update.
* If you are slow responding (as in researching the messages) the tablet might lose connection and you have to reconnect. PC reboots can help.
* The repartition script and other wipes produce voluminous messages that don't require action. Go do something else for half an hour or maybe more.
* Sideloading gapps requires redoing "Apply Update" and "Apply from ADB"
* Bottom line - It eventually works and is so much better.
Win command session log attached.
* A big thank you to the hard working people who have given my favorite tablet a new future.
NTGDeveloper said:
I upgraded this device and I can't seem to go through a smooth 17.1 upgrade to 18.1 because I have a lock screen pin/pattern and every time I tried, the lock screen would crash as soon as I entered my pin. I saw that some other users had this problem on other devices, just thought I might want to bring that forward here on the new thread.
Click to expand...
Click to collapse
Same. It's a shame I didn't find this advice before trying to upgrade. It's also a shame it isn't mentioned in the Lineageos upgrade wiki for flox...
I ended up doing a wipe from recovery and clean install, after which all seems to be going smoothly
asquartz said:
Same. It's a shame I didn't find this advice before trying to upgrade. It's also a shame it isn't mentioned in the Lineageos upgrade wiki for flox...
I ended up doing a wipe from recovery and clean install, after which all seems to be going smoothly
Click to expand...
Click to collapse
it is now.
Works like a charm after a clean installation. I appreciate your efforts.
I enjoy a bit of sport as well as the next person, but eventually I get tired...
At first I tried a dirty flash over followmsi's unofficial 18.1, and got an "E3004: This package is for device: flox; this device is flo." Ok, no problem, I didn't really expect it to work. But despite all attempts at wiping/formatting/sideloading/repartitioning/modifying/blah blah blah I'm still getting the same E3004 message.
I'm clearly not following a step here, but I don't know which one.
What is it that transforms my flo into a flox?
need some clarification: currently my tablet is on official LOS 17.1 (repartitioned), OpenGApps and has TWRP. How do I install LOS 18.1? Install using TWRP? should I install MindGApps on top?