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.
Related
Q&A for [ROM] **crDroid Lollipop 5.0.1** [vs985][12-3-14]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM] **crDroid Lollipop 5.0.1** [vs985][12-3-14]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Need for Wipe
oadam11 said:
{
"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"
}
crDroid Custom Features:
Dialer Lookup;
Profiles form CyanogenMod;
Call blacklist support;
Protected apps (using trebuchet launcher);
Filter spam notifications;
Clear all button in recent panel;
Privacy guard from CyanogenMod;
Quick settings pull down with one finger in right corner;
Data activity indicators;
Increasing ring tone;
Advanced reboot menu;
Option to hide adb notification;
Screen shot quick delete with confirmation;
Long press back to kill with configurable timeout;
Less frequent notifications sound;
Advanced keyboard features (auto rotation with timeout, disable full screen, selector notification, show enter key, volume key cursor control);
Always Have a full functional Backup. Just in case!
DOWNLOAD
please do not mirror !
pa gapps
screenshots
First time installing crDroid to your vs985, or coming from another ROM:
- Make sure you're running a proper working Recovery (CWM or TWRP)
- Copy GApps and crDroid zip to your internal SDCard
- Boot into Recovery
- Flash crDroid zip
- Flash GApps zip
- DO A DATA WIPE / FACTORY RESET
- Reboot
- Don't restore Apps using Titanium Backup!
Don't expect any support if you:
- are not running stock crDroid-kernel
- have installed any mods such Xposed!
- have modified system files
Thanks to:
Cristiano Matos the developer of this beautiful rom
CM Team
Slim Roms Team
ParanoidAndroid Team
temasek
Omniteam
androidfilesharing for his awesome contribution
invisiblek
manups4e
sooti
And Many More...
if you want to donate please donate to Cristiano Matos who has made this rom PAYPAL
this rom is unofficial so not supported by Cristiano Matos , please don't bother him with questions
kernel source
http://crdroid.org/
crDroid G+ community
https://github.com/crdroidandroid
Click to expand...
Click to collapse
Does flashing this need a wipe if im coming from CM 12 unofficial Lollipop ROM?
New CM Theme App
Pbaird1979 said:
From what I understand, cm team is not beginning themes until 12 is more stable. I may be wrong about this but it's what I understand.
Click to expand...
Click to collapse
The CM Team just announced a new Theme App for anyone running a CM-based ROM that will allow for full customization. From the sounds of it,
it should be out any day and I expect it will work on CM12.
Brandodando said:
Does flashing this need a wipe if im coming from CM 12 unofficial Lollipop ROM?
Click to expand...
Click to collapse
Yea. Clean flash is necessary
I tried to install SuperSU and it sent me into a boot loop, same thing happened to me with the Vanir Comotio build as well, any ideas?
I am getting the "Unfortunately, DSP Manager has stopped" every time I open Play Music and when I skip tracks. Anyone know how to fix this? Also is Wifi Tether working? If not any workarounds?
Does anyone know how to fix the 505 error in play store when trying to DL an app
PA gapps - modular version?
Is the modular version the one to download for this rom? The rest of the versions seem to not have DL links
Bug report:
While playing music and using navigation in the car (using bluetooth), voice directions break in and lower the music volume as it should. Upon returning to music, the volume does not return to its previous level, rather it gets louder, overdriving the phone output and causing distortion. Pressing volume down on the phone once returns volume to normal levels.
Same scenario when SMS notification is received while playing music.
I'm working on a band-aid fix using Tasker, but it would sure be nice to have this fixed more permanently. This is a fantastic ROM, and other than this has been 100% trouble-free. Great work!
Currently running crDroid 12/19 build
This is not a question, but because I'm new, my post came here. I've been lurking around these boards since the HTC rezound, and I must say that the crDroid 12/30 build for the G3 is the fastest and most stable ROM Ive ever used. Great work! I signed in just to say that.
This isn't a question, just a quick note that the 12/30 build is running great so far. The only thing I could even think to add is the option to modify the DPI within your crdroid menu in settings. Other than that, Great Job!
Huge Battery Drain
Folks,
I like the overall look, features, etc. of the Rom so thank you for that. However, it took my battery from 100% to 11% overnight. I'm on the 1/2 version, did the usual wipe/factory reset, wipe cache/dalvik, etc. and then installed the Rom and Gapps.
Any suggestions before I flash back to CM11?
I'd greatly appreciate it.
pressmoon said:
Folks,
I like the overall look, features, etc. of the Rom so thank you for that. However, it took my battery from 100% to 11% overnight. I'm on the 1/2 version, did the usual wipe/factory reset, wipe cache/dalvik, etc. and then installed the Rom and Gapps.
Any suggestions before I flash back to CM11?
I'd greatly appreciate it.
Click to expand...
Click to collapse
Have you checked your battery stats to see if any app or process in particular is the culprit?
Keyboard Chooser Crash
On the newest Jan19 build I can't switch to alternate keyboards. They install but under settings/language&input when I press choose keyboard under current keyboard it crashes. I installed clean with the Jan16 PA Gapps. I just want to know if anyone else has had similar problems.
Not sure if anyone else is having this problem and I did not read it anywhere. But it could be just me but when I'm in a phone call and another call comes in I can transfer over but both people can't hear me and I can't hear them. What do you guys think. In on 1-20 build
flac support?
does this most recent update not support .flac files natively?
Loss of root
I've been using this rom since the very first release with no problem, yesterday I tried to update to the latest build but I wasn't able to reboot into the recovery using the terminal emulator. Then I did a root check and it seems I'm no longer rooted. I attempted to use stump to reroot my phone but it's giving me an unsupported device error. What can I do to install the latest build?
WiFi?
WiFi passwords are not being saved every time I turn the WiFi off the passwords get deleted.
crDroid Lollipop 5.0.1 ROM crashing my LG G3
Using TWRP 2.8.4.0 I ROMed my LG G3 (vs985) with crDroid Lollipop 5.0.1 01/19/2015 build) yesterday and everything worked great. This is the second time ROMing this phone for me - previous running ROM was Cyanogenmod cm-12 which I didn't really care for. My initial impressions was that this is a great ROM.
Not so sure about that now. Before going to bed last night turned off phone; got up this AM, turned on phone and everything turned to s**t. Greeted with a KP right at boot up. Rebooted and appeared to boot ok with my normal home screen appearing but then several seconds later either of two windows started popping up - "Unfortunately, Google Play Store has stopped." or "Unfortunately Google Play Services has stopped." Every time time I do an OK button press on the displayed window either that one or the other window immediately pops up. I can't do any actions to get out of this mess.
So my question is what can I do to get back to normal operation and put my VZW ROM backup back on the phone? Also, is there a bug in the crDroid ROM (at least in this build)?
Thanks.
bmwmcrider said:
Using TWRP 2.8.4.0 I ROMed my LG G3 (vs985) with crDroid Lollipop 5.0.1 01/19/2015 build) yesterday and everything worked great. This is the second time ROMing this phone for me - previous running ROM was Cyanogenmod cm-12 which I didn't really care for. My initial impressions was that this is a great ROM.
Not so sure about that now. Before going to bed last night turned off phone; got up this AM, turned on phone and everything turned to s**t. Greeted with a KP right at boot up. Rebooted and appeared to boot ok with my normal home screen appearing but then several seconds later either of two windows started popping up - "Unfortunately, Google Play Store has stopped." or "Unfortunately Google Play Services has stopped." Every time time I do an OK button press on the displayed window either that one or the other window immediately pops up. I can't do any actions to get out of this mess.
So my question is what can I do to get back to normal operation and put my VZW ROM backup back on the phone? Also, is there a bug in the crDroid ROM (at least in this build)?
Thanks.
Click to expand...
Click to collapse
Edit: managed to reboot into recovery mode and restore from my backup VZW ROM. But my original issue still stands: Why did everything go wonky? Also, the previous poster noted that Stump Root complained about non-compatible phone. Before doing my recovery I managed to launch Stump Root and got the same response. Stump Root doesn't like crDroid?
{
"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
lineage 15.1 oreo builds are now available. See new thread here:
https://forum.xda-developers.com/ne...rom-lineageos-15-1-nexus-5x-bullhead-t3724575
{
"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"
}
LineageOS is a free, community built, aftermarket firmware distribution of android, which is designed to increase performance and reliability over stock android for your device.
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 Wiki.
Important Info
Current lineage 14.1 bullhead nightlies are based on the N2G48C (August 2017) monthly update from google. So you should be using the vendor, radio and bootloader img from that update. They can be extracted from the factory image on google's site here. Or you can use the ones linked below that I already extracted:
Note: The radio and bootloader img is the same as what was in the previous monthly google update, so if you already have it you don't need to flash it.
* vendor-n2g48c.img
* radio-bullhead-m8994f-2.6.37.2.21.img
* bootloader-bullhead-bhz11m.img
The vendor img is flashable with twrp or fastboot. For the radio and bootloader img, use fastboot.
More information and installation instructions can be found on the LineageOS wiki here.
Download Links
LineageOS: https://download.lineageos.org/bullhead
Google apps: Beans GApps (recommend mini)
SU addon zip: Addon Install zip / Addon Removal zip NOTE: LineageOS does not come with root, so this is now provided for those that want it. The install zip is a one time flash, like gapps. Meaning, it persists when updating to a new LineageOS nightly. REF: https://download.lineageos.org/extras
Changelog
https://download.lineageos.org/bullhead/changes/
Stats
https://stats.lineageos.org/
Credits
Many thanks to the LineageOS team and all the contributors out there in the community :good:
Contributors
dcd1182, razorloves
Source Code:
Device tree: https://www.github.com/LineageOS/android_device_lge_bullhead/tree/cm-14.1
Kernel tree: https://www.github.com/LineageOS/android_kernel_lge_bullhead/tree/cm-14.1
ROM OS Version: 7.1.2 Nougat
ROM Kernel: Linux 3.10.73
Status: Nightly
Issues with CM 14.1
Hello, today I tried to flash CM 14.1 but I had some issues like warning that my phone is corrupted or something and I have to contact manufacturer. I wasn't able to setup the device. I'm wondering if this can be flashed over purenexus 7.0 ROM with NBD90Z vendor image...or should I flash some newer vendor image ? Thanks for help community
maof_ke said:
Hello, today I tried to flash CM 14.1 but I had some issues like warning that my phone is corrupted or something and I have to contact manufacturer. I wasn't able to setup the device. I'm wondering if this can be flashed over purenexus 7.0 ROM with NBD90Z vendor image...or should I flash some newer vendor image ? Thanks for help community
Click to expand...
Click to collapse
Do not enable wifi or cellular data during setup, and it will not attempt the device setup part that you can't get past.
Otherwise pretty stable.
I've flashed it, it had some problems booting, but now its working. Here's my guideline:
1-If you do not want to get the VENDOR message at first boot, start flashing last NRD91N factory image
2-Flash TWRP from fastboot, and do a "Fastboot erase cache" and "Fastboot erase userdata"
3-Reboot into TWRP, and do a DATA Format
4-Reboot into TWRP and do a Full Wipe
5-Flash CM14.1 and OpenGapps (i used nano)
6-Reboot. Give it about 5 min, mine got stuck at CM logo. If after 5 min it does not boot, keep power button pressed for a few seconds till it reboots. It should boot properly now.
7-If after booting, entering SIM Pin code DO NOT ENABLE WIFI OR DATA. It will cause a loop on the wizard. Let both be disabled till the end of the config.
8-Reboot and you should have CM14.1 official working.
Here's proof:
Sorry for my english. :angel:
UPDATE:
Ok, i've been doing some more testing with both official 7.0 and dev preview 7.1 and here are my results:
1-If you want, you can use 7.1 dev preview as base, using the same tutorial above. The only difference will be that after every reboot, right before PIN Code, it will tell you the VENDOR.img message. Nothing to worry about.
2-I don't know if it is a placebo effect or not, but I get better performance on the CM14.1 if I use 7.1 as base. I think it is more fluent.
3-Using 7.1 as base definetively changes something, there's a little "glitch" or graphical difference with 7.0. Here's proof:
As you can see, Menu item switch looks different from 7.0.
4-In my experience, I've decided to disable the stock Web Browser and install any other, because the one that comes with the build gives FCs some times, and I think it has some memory leak or something, that makes the OS lag. After disabling it, everything works fine.
Hope this helps to anyone.
Cheers
@razorloves
Thanks for you're contribution to N5x!
I've never used but want to try this out since i'm hearing a lot about it....what I want and need to know is what features comes with this ROM? something tells me i'm really going to like it.
Gallery app freezes and then the phone resets...and ElementalX has dark camera bug
Im unable to complete the initial settings.
After connecting to wifi or data, im prompted to copy data from another device with some error messages and i cant proceed, im always taken back to previous settings screens.
When i try to turn off the wifi and data, the phone tell me that "unable to connect" and im taken back to "choose how to connect" screen. So... any suggestions? I even tried "factory reset" but with no luck.
Im using the newest bootloader from 7.1.1 DP, is this a possible source of the issues? Thanks!
outlawman007 said:
Gallery app freezes and then the phone resets...
Click to expand...
Click to collapse
yep, just heard about that couple hours ago.
already submitted fix, just testing it now.
http://review.cyanogenmod.org/#/q/topic:sdcardfs-fix
EDIT: Thanks to @DeHuMaNiZeD for testing my changes. The fix is now merged and will be in the next nightly.
My impressions so far are exactly as mentioned above by others with the added addition that battery icons dont work when you switch landscape and circle. Hidden and text work. Other than that the rom is pretty stable.
Carach_CZ said:
Im unable to complete the initial settings.
After connecting to wifi or data, im prompted to copy data from another device with some error messages and i cant proceed, im always taken back to previous settings screens.
When i try to turn off the wifi and data, the phone tell me that "unable to connect" and im taken back to "choose how to connect" screen. So... any suggestions? I even tried "factory reset" but with no luck.
Im using the newest bootloader from 7.1.1 DP, is this a possible source of the issues? Thanks!
Click to expand...
Click to collapse
Do not enable wifi or cellular data during setup, and it will not attempt the device setup part that you can't get past.
After first flash, coming encrypting screen, is this normal ?
airtower said:
Do not enable wifi or cellular data during setup, and it will not attempt the device setup part that you can't get past.
Click to expand...
Click to collapse
Couldn´t sign in
You don´t have a network connection.
After pressing next i can either turn on mobile data or connect to wifi.
So.. sorry your advice really didnt helped at all. :crying:
PS: even got "CM stopped working". I even downloaded NRD91N factory image, used its bootloader, radio and vendor. With no luck. Im DEcrypted btw. How the hell you managed to make it work?
PPS: Should i use CM Recovery instead of TWRP? "Sigh" this is frustrating..
Carach_CZ said:
Couldn´t sign in
You don´t have a network connection.
After pressing next i can either turn on mobile data or connect to wifi.
So.. sorry your advice really didnt helped at all. :crying:
PS: even got "CM stopped working". I even downloaded NRD91N factory image, used its bootloader, radio and vendor. With no luck. Im DEcrypted btw. How the hell you managed to make it work?
PPS: Should i use CM Recovery instead of TWRP? "Sigh" this is frustrating..
Click to expand...
Click to collapse
I came from tupac4u's debloated Nought rom, but flashed an unofficial CM14.1 build before this official one. During that process I was prompted to encrypt. I used TWRP 3.0.2-2 throughout. I get warnings during boot, but I clear them with no ill effects.
Not sure what else to tell you. As far as the setup goes, there's instructions a few posts up on how to delete the wizard all together. I didn't need to do this however. Initially I was stuck on the copy from device screen (there's no forward or submit button), but was able to go back, long press and forget the previously saved wifi, uncheck mobile data, and proceed forward skipping the device sync part. When I first opened play store, I was asked for my google credentials and two-factor code.
airtower said:
I came from tupac4u's debloated Nought rom, but flashed an unofficial CM14.1 build before this official one. During that process I was prompted to encrypt. I used TWRP 3.0.2-2 throughout. I get warnings during boot, but I clear them with no ill effects.
Not sure what else to tell you. As far as the setup goes, there's instructions a few posts up on how to delete the wizard all together. I didn't need to do this however. Initially I was stuck on the copy from device screen (there's no forward or submit button), but was able to go back, long press and forget the previously saved wifi, uncheck mobile data, and proceed forward skipping the device sync part. When I first opened play store, I was asked for my google credentials and two-factor code.
Click to expand...
Click to collapse
7-If after booting, entering SIM Pin code and WIFI, it gets stuck at "looking for another terminal" or similar, reboot to TWRP and go: MOUNT-->TICK SYSTEM. Then got to ADVANCED-->FILE MANAGER-->SYSTEM/PRIV-APP/CYANOGENSETUPWIZARD and press option button-->DELETE.
This helped A LOT. I got rid of bugged (i know, first nightly) CM settings wizard and got into AOSP settings wizard which was flawless. Im using the CM 14.1 now! Finally!
Thanks!
maof_ke said:
Hello, today I tried to flash CM 14.1 but I had some issues like warning that my phone is corrupted or something and I have to contact manufacturer. I wasn't able to setup the device. I'm wondering if this can be flashed over purenexus 7.0 ROM with NBD90Z vendor image...or should I flash some newer vendor image ? Thanks for help community
Click to expand...
Click to collapse
What I did to fix this is I did I clean install with no gapps so that you don't have to do Google setup at first boot. booted fine, then I rebooted into twrp and flashed gapps. When I booted back up I just went to settings and added my Google account. I am using mini open gapps
After the registering problems, does the ROM is stable for daily use? I really want to try it, but it is my main phone...
Carach_CZ said:
Im unable to complete the initial settings.
After connecting to wifi or data, im prompted to copy data from another device with some error messages and i cant proceed, im always taken back to previous settings screens.
When i try to turn off the wifi and data, the phone tell me that "unable to connect" and im taken back to "choose how to connect" screen. So... any suggestions? I even tried "factory reset" but with no luck.
Im using the newest bootloader from 7.1.1 DP, is this a possible source of the issues? Thanks!
Click to expand...
Click to collapse
someone posted how to get around the setup solution just a couple of post upwards, I was having that problem to, but followed his instructions and cm14 works fine now
@razorloves. the cm bug report keeps force closing.
Anyone else having problems with clock app? I can't open it at all, tried installing through aroma gapps and through app store, aside from that everything seems stable. Even my fingerprint unlock works again which makes me really happy, it stopped working during marshmallow and even after 7.0 it wouldn't work but somehow it's back and fully functional.
Not booting with F2FS data and cache partitions. Booting fine with jolla kernel. As I see stock kernel that included in ROM also supports F2FS, but I don't know why it's not booting.
{
"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
Havoc-OS 3.x is based on AOSP, inspired by Google Pixel.
Has a refined Material Design 2 UI by @SKULSHADY.
So many features that you probably won't find in any ROM.
All you can dream of and all you'll ever need.
Just flash and enjoy...
Whats working?
Wifi
RIL
Mobile data
Camera
Flashlight
Camcorder
Bluetooth
Lights
Sound / vibration
VoLTE
Known Issues?
You tell me
Links
Rom
Installation
Remove your Google account.
Flash latest firmware with the set of commands attached.
"Fastboot boot" TWRP/OrangeFOX, flash copypartitions.zip and flash ROM.
Boot system..
Optional: boot TWRP/OFOX after the first boot, and flash recovery installer/Magisk/GApps.
Set of commands: https://forum.xda-developers.com/attachment.php?attachmentid=4955977&d=1582350851
If you face any boot loop issue kindly format data and cache.
Contact me on telegram
Credits
LineageOS ([url]https://github.com/LineageOS[/URL])
Crdroid ([url]https://github.com/crdroidandroid[/URL])
Pixel Experience ([url]https://github.com/PixelExperience[/URL])
Nitrogen Project ([url]https://github.com/nitrogen-project[/URL])
Omnirom ([url]https://github.com/omnirom[/URL])
MSM-Xtended Team ([url]https://github.com/Project-Xtended[/URL])
Skydragon ([url]https://gitlab.com/HolyDragonProject[/URL])
Syberia Project ([url]https://github.com/syberia-project[/URL])
And all the other Developers, Testers, Donators and Users.
Team
Lead Developer
SKULSHADY (Anushek Prasal)
ZeNiXxX (Viktor Hermann)
Support Team:
theo.j22 (Tushar Jain)
DankBoi (Apoorva Kr. Srivastava)
Contributors
Electimon
SyberHexen
Jleeblanch
Erfanoabdi
Source Code: [url]https://github.com/Havoc-OS[/URL]
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
ROM Firmware Required: Latest
Based On: Aosp
Version Information
Status: Stable
Created 2020-02-27
Last Updated 2020-04-12
Update Log:
12-March-20: Fixed VoLTE
Add MotoExtras to settings
Added KCAL to kernel and MotoExtras
Fixed a MotoCam Bug
Use Coral Fingerprint
10-March-20:
08-March-20: Update to Havoc OS 3.3 and fix some settings errors
03-March-20: Improve UI performance
29-Feb-20: Fixed calling audio issues, thank @erfanoabdi
You guys are bringing it to the G7 Power!! Awesome work!! [emoji16]
Sent from my mi mix 2 using XDA-Developers Legacy app
intalled from stock rom 9 and it goes great at this moment, thank you, keep the fantastic job
I have been waiting so long, GSI has been working really well on moto g7 power. I figured it wasnt too long before a rom was built.
Any Gapps package working?
toxinburn said:
Any Gapps package working?
Click to expand...
Click to collapse
I use these: https://forum.xda-developers.com/android/software/arm64-nikgapps-t3915866
Edit
toxinburn said:
Any Gapps package working?
Click to expand...
Click to collapse
I just downloaded the micro version off opengapps website its bare min and I am OK with that I just want the Google play store and that's it
So how is this rom Working for people is it good wanna try it but don't wanna have problems
XxRealSaltyxX said:
So how is this rom Working for people is it good wanna try it but don't wanna have problems
Click to expand...
Click to collapse
far as i can tell, everything works except my mic. probably something i did but you might wanna test it after first install. I mostly text so its not a huge issue for me honestly. and i use a bluetooth headset most of the time
UPDATE: fresh installed again and mic is working. must had just been a bug.
I use adaptive storage on my SD card and having issues running apps on the phone I have to switch the location for the apps to work
How to put TWRP on this custom?
eastyx said:
How to put TWRP on this custom?
Click to expand...
Click to collapse
I make this comment assuming that you already have installed factory image and flashed the copy-partition-ab.zip previous to doing anything I say here. I only say that because I wouldn't want you to brick. If you have already done all that then just flash rom and reboot system like it says in the op. Then boot recovery again: fastboot boot twrp.img and install your gapps, magisk, recovery installer zip or whatever because if you try and flash it ALL at once it may not boot. Also as the op says after you install the rom and reboot system your phone may boot into recovery (stock) and prompt you to factory reset. If so select yes and do it otherwise it will not boot. I use a USB stick and keep things on it for my phones just in case. Makes it so much easier!
If you're already using havoc just: sudo fastboot boot twrp.img Then in twrp flash twrp installer zip from twrp site and reboot system.
You should be good then and twrp should then be installed. If it freezes up on you (if touch screen quits working) just boot back into bootloader manually (holding volume down+ power buttons) and boot recovery again through fastboot again... If touch quits working on recovery it will eventually work again, always has for me, but that's what I did and it worked. I actually don't even install recovery now I just use fastboot to boot twrp (or orange fox recovery) when I need to and I don't pull fancy stuff when I'm nowhere near my house. lol. Seems like twrp works better and has no freezes if I don't install it but it does freeze up when I have installed it in the past.. ? Also if you aren't already a member of the Moto G7 Power telegram group definitely check that out. But I recommended using a free app to get another phone # to use for making telegram account because if you use your real one they will spam the ______ outa you! The app named Text Free worked for me for that and telegram accepted the VoIP #..
@Electimon You're awesome! Really appreciate your time spent on this!! Does Havoc have signature spoofing? Seems like i read that somewhere about Havoc having it.. Soon as I make this post I'll check and also see if the patch got updated here on xda for 10/Q to add spoofing if its not. If I find a way to make it spoof if its not spoofing I'll report back. ?? Thanks again!!! :good:
Yes It does
flash713 said:
I use these: https://forum.xda-developers.com/android/software/arm64-nikgapps-t3915866
Edit
Click to expand...
Click to collapse
I wound up going back to latest stock I have nothing but bricks and softbricks anytime i flash twrp permanently on all roms I really wanted to try this also I guess ill wait a lil til things are more stable but i bookmarked the page I think its cause its a/b device so i mean the first thing I flash is the A/b retention zip then i flash the I try to boot to roms and they just send me back to recovery or will show logos for bit before freezing and bootlooping but the link you sent is first time ive seen it say flash roms to both a and b, amd twrp, what about gapps and magisk would they also need to be flashed to both a and b? I am guessing that is why I keep having issues I just figured id ask before I try this again I had thought th ab retention files made it where all things flashed would go to a and b on their own after flashing that but that appears to not be the case I wish I could find step by step instructions for flashing a rom to these ab devices I really want to try something beside stock but I have had nohing but probs last time i got lucky found a single command that put phone in edl mode no other way worked that I had found wish I had not been a bonehead and saved that command because it makes the blank flash work perfectly and was how i finallly revived my device.
I did all the steps and my g7 power is in hardbrick, model XT1955-2
toxinburn said:
I wound up going back to latest stock I have nothing but bricks and softbricks anytime i flash twrp permanently on all roms I really wanted to try this also I guess ill wait a lil til things are more stable but i bookmarked the page I think its cause its a/b device so i mean the first thing I flash is the A/b retention zip then i flash the I try to boot to roms and they just send me back to recovery or will show logos for bit before freezing and bootlooping but the link you sent is first time ive seen it say flash roms to both a and b, amd twrp, what about gapps and magisk would they also need to be flashed to both a and b? I am guessing that is why I keep having issues I just figured id ask before I try this again I had thought th ab retention files made it where all things flashed would go to a and b on their own after flashing that but that appears to not be the case I wish I could find step by step instructions for flashing a rom to these ab devices I really want to try something beside stock but I have had nohing but probs last time i got lucky found a single command that put phone in edl mode no other way worked that I had found wish I had not been a bonehead and saved that command because it makes the blank flash work perfectly and was how i finallly revived my device.
Click to expand...
Click to collapse
I'm not sure whats up but the place to read up and learn or should I say another place to learn is telegram group for G7 power. I go read backwards there from most recent comment up for hours sometimes. I used to immediately rip my phones out the box when I got em and unlock bootloader and flash a Aosp rom but I've learned through killing a few to read everything I can first for a few weeks then operate. I was lucky to bring this one back all the times thanks to blank flash and the guys telling he keep trying it. I believe its all about the USB cable and having steady communication on the blank flash. I have no issues installing recovery but when i have it locks up on me so I just boot it when I need to and works good.
KUSANAGUI said:
I did all the steps and my g7 power is in hardbrick, model XT1955-2
Click to expand...
Click to collapse
I have a 1955 5 aka metro by tmobile g7 power and ever since I joined the Moto G7 power telegram group and learned about how to do things I've not bricked but when this phone came out I immediately grabbed it on day 2 and hard bricked it and bricked it a few more times and brought it back every time using blank flash. Sometimes it took a while to get the blank flash to run atw through but eventually it did and I was able to boot to bootloader and fastboot factory image.. if you aren't already on telegram group it has a TON of information and everyone is really cool and helpful. Best group I've ever been around! The group is @mg7Power
toxinburn said:
Any Gapps package working?
Click to expand...
Click to collapse
toxinburn said:
I wound up going back to latest stock I have nothing but bricks and softbricks anytime i flash twrp permanently on all roms I really wanted to try this also I guess ill wait a lil til things are more stable but i bookmarked the page I think its cause its a/b device so i mean the first thing I flash is the A/b retention zip then i flash the I try to boot to roms and they just send me back to recovery or will show logos for bit before freezing and bootlooping but the link you sent is first time ive seen it say flash roms to both a and b, amd twrp, what about gapps and magisk would they also need to be flashed to both a and b? I am guessing that is why I keep having issues I just figured id ask before I try this again I had thought th ab retention files made it where all things flashed would go to a and b on their own after flashing that but that appears to not be the case I wish I could find step by step instructions for flashing a rom to these ab devices I really want to try something beside stock but I have had nohing but probs last time i got lucky found a single command that put phone in edl mode no other way worked that I had found wish I had not been a bonehead and saved that command because it makes the blank flash work perfectly and was how i finallly revived my device.
Click to expand...
Click to collapse
Try installing everything without a micro SD card I. It was culprit that gave me hours and hours of troubke
I'm interested in this rom to run as a daily driver, have the VoLTE issues been resolved?
flash713 said:
I'm not sure whats up but the place to read up and learn or should I say another place to learn is telegram group for G7 power. I go read backwards there from most recent comment up for hours sometimes. I used to immediately rip my phones out the box when I got em and unlock bootloader and flash a Aosp rom but I've learned through killing a few to read everything I can first for a few weeks then operate. I was lucky to bring this one back all the times thanks to blank flash and the guys telling he keep trying it. I believe its all about the USB cable and having steady communication on the blank flash. I have no issues installing recovery but when i have it locks up on me so I just boot it when I need to and works good.
I have a 1955 5 aka metro by tmobile g7 power and ever since I joined the Moto G7 power telegram group and learned about how to do things I've not bricked but when this phone came out I immediately grabbed it on day 2 and hard bricked it and bricked it a few more times and brought it back every time using blank flash. Sometimes it took a while to get the blank flash to run atw through but eventually it did and I was able to boot to bootloader and fastboot factory image.. if you aren't already on telegram group it has a TON of information and everyone is really cool and helpful. Best group I've ever been around! The group is @mg7Power
Click to expand...
Click to collapse
I sent my smartphone to the technical service because no method of his group served me, I will never root again, install rom, or twrp. To any smartphone that has a / b partitions, my moto x play has not given me headaches like this g7 power.
THANKS
KUSANAGUI said:
I sent my smartphone to the technical service because no method of his group served me, I will never root again, install rom, or twrp. To any smartphone that has a / b partitions, my moto x play has not given me headaches like this g7 power.
THANKS
Click to expand...
Click to collapse
I felt same at first. And not all A/B partitioned phones are like this one. My Pixel XL is A/B and I musta flashed it thousands of times and never bricked. I think with this forum there are a few different models of the same device and it can be confusing AF. Or the fact that my phone is a Metro G7 Power and it uses RETUS, retail US firmware and won't flash the metro firmware. I tried more than once early on. My other device is a xiaomi mi mix 2 I purchased off swappa a while back for $140 and it's a Aonly 64 bit device and flashes just like the last 39 or so phones and tablets I owned in the past. Maybe look at A only devices. There are tons of them. For some reason it took me a while to fully understand the whole A/B partitioning deal even though I read everything known to man on it here and other places. I've had to figure things out a few times through trial and error just because what seems to work for others doesn't for me. As soon as I get a tripod I'm going to throw some videos up on YouTube of how I install roms and flash firmware and things like that. I believe the big thing for this device that throws some people off is the different models idk... I hear you though. I bet money that maybe not all but most people who didn't get the blank flash to work didn't do it enough. It's a tedious mission. While im grateful that we have the blank flashes I'm definitely not trying to do it all again because it was a very long process for me every time I did it. Lol.
{
"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?