crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features existent today. We're mainly based on LineageOS so use custom kernels compatible with them!
{
"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"
}
Features
Click for feature list
Always Have a full functional Backup. Just in case!
DOWNLOAD ROM
GAPPS: DOWNLOAD GAPPS
First time installing crDroid to your Nexus 6P, or coming from another ROM:
** Make sure you're running a proper working Recovery (TWRP)
1) Copy crDroid zip, gapps zip to your device
2) Boot into Recovery
3) Wipe cache, system, & data (or just cache & system for a dirty flash).
4) Flash ROM
8) Flash gapps
9) Boot up
For root, AFTER you boot into the ROM, you can go back to recovery and install Magisk 19.3.
Upgrading from earlier version of crDroid:
The only difference between clean flash as above and upgrading is you just wipe system & cache, leaving data. Everything else is the same. ***Remember to always clean flash before reporting problems. Clean flashing is always the best method of ROM install.
Don't expect any support if you:
- are not running the included kernel
- have installed any mods such as Xposed!
- have modified system files
Thanks to:
- Google
- LineageOS
- SlimRoms
- AOSPA (Paranoid Android)
- OmniRom
- NamelessROM
- Many others... (if you're feeling upset being out of the thanks list just send a PM )
DONATE
XDA:DevDB Information
crDroid 5.7, ROM for the Huawei Nexus 6P
Contributors
PixelBoot
Source Code: https://github.com/crdroidandroid
ROM OS Version: 9.x Pie
Based On: LineageOS
Version Information
Status: Stable
Created 2019-08-19
Last Updated 2019-08-20
A few notes before you proceed:
Before going straight to the download section there’s something we would like to tell you. We have changed the default encryption method for the phone, migrating to File-Based Encryption (you can get more information from the official Google documentation page). In order to get this encryption mode working, you will need to use our custom recovery (compiled from the latest source) which is compatible with this encryption and, just for the first time, you will have to wipe your internal data, so backup your data before proceeding.
Installation Instructions:
Grab our recovery from the peripherals section and install it.
Through TWRP Recovery:
Install Zip > Install Image > Choose ‘recovery.img‘ > Select partition ‘Recovery’ > Swipe to confirm flash
Through Fastboot:
Code:
fastboot flash recovery recovery.img
Install the ROM and then wipe your internal data partition.
Through TWRP Recovery:
Wipe > Format data
Through Fastboot:
Code:
fastboot -w
Reboot into system and wait until the process finishes, it could take a little bit. After the installation is done, I suggest waiting before using the phone because it usually goes into thermal throttling after installing a ROM.
Peripherals:
FBE Recovery: TWRP
@PixelBoot you are one busy little bee. Thanks one more time for all your support. Don't know how you manage so much stuff but I do appreciate all your efforts!
Sent from my Nexus 6P using XDA-Developers Legacy app
Woooow this is amazing ... I love this rom .. thanks ...
doesn´t start well
Have big expectations for this ROM.
As of now, they are on hold for the time being, since it appears, that my phone is stuck booting the system. I am still hoping for the best
DysfunctionalDouche said:
Have big expectations for this ROM.
As of now, they are on hold for the time being, since it appears, that my phone is stuck booting the system. I am still hoping for the best
Click to expand...
Click to collapse
You followed every instructions given above?Like flashing twrp fbe and formating afterwards if you are coming from fde?
Flashing the rom went fine, however Open Gapps is convinced that this rom is SDK23 and is a mismatch... idk why
EDIT: It also thinks my device is not arm64... not sure whats up with all that
DERP, had to read the posts by Pixel... welp all good now
New post because it's been a few hours since flashing
Love the rom, but VoLTE doesn't work on TMO, all advanced calling services appear to be missing(unknown cause) So the device isn't very usable for me now. Sadly
GeTex said:
New post because it's been a few hours since flashing
Love the rom, but VoLTE doesn't work on TMO, all advanced calling services appear to be missing(unknown cause) So the device isn't very usable for me now. Sadly
Click to expand...
Click to collapse
Don't expect volte to work on any 9.0 roms. Not sure that's ever been fixed
Lawlrus said:
Don't expect volte to work on any 9.0 roms. Not sure that's ever been fixed
Click to expand...
Click to collapse
Thanks for the info
Is it working on any 8.1 roms?
GeTex said:
Thanks for the info
Is it working on any 8.1 roms?
Click to expand...
Click to collapse
Afaik It did? Dunno I never gave / don't give a **** about volte. So I never noticed myself. I can say that I didn't see nearly as many people post about it not working when we were on 8.1
Search through the threads.
Lawlrus said:
Afaik It did? Dunno I never gave / don't give a **** about volte. So I never noticed myself. I can say that I didn't see nearly as many people post about it not working when we were on 8.1
Search through the threads.
Click to expand...
Click to collapse
Thanks! it's working in crDroid Oreo. I have to have it working since im in an area with VoLTE service only. there currently isn't any 3G/HSPA bands up due to tower modernization. so it's VoLTE and Wifi calling only in my zone right now
GeTex said:
Thanks! it's working in crDroid Oreo. I have to have it working since im in an area with VoLTE service only. there currently isn't any 3G/HSPA bands up due to tower modernization. so it's VoLTE and Wifi calling only in my zone right now
Click to expand...
Click to collapse
That's really weird and I guess makes sense why people worry about it. I wasn't aware some places offer lte but there's nothing lesser like 3g.
I don't really know much about telecommunications though, and being in the US we had 3g setups years before lte came out
Lawlrus said:
That's really weird and I guess makes sense why people worry about it. I wasn't aware some places offer lte but there's nothing lesser like 3g.
I don't really know much about telecommunications though, and being in the US we had 3g setups years before lte came out
Click to expand...
Click to collapse
Alot of carrier this year are terminating any device that doesn't have advanced calling support by the end of the year to migrate everything to VoLTE, verizon notified me my S3 wouldn't work at the end of Dec because of this, my S5 will(only on the stock rom :'( sadly), and Sprint has already stopped activating any device without at least LTE support since may or something this year.
TMO 1 year ago took down the lower 3G bands here in the area I live and only the LTE bands remain up, however they noted it's band 12 only which as you probably know TMO doesn't allow connections on Band 12 UNLESS a voice and data connection can be established with the device, otherwise you get devices that will roam to Band 12 and all calls will fail outright if it cannot find a 3G connection or 4G HSPA connection.
It's been alot of fun lol.
I have limited understanding of telecommunications but it's not terribly bad
GeTex said:
Alot of carrier this year are terminating any device that doesn't have advanced calling support by the end of the year to migrate everything to VoLTE, verizon notified me my S3 wouldn't work at the end of Dec because of this, my S5 will(only on the stock rom :'( sadly), and Sprint has already stopped activating any device without at least LTE support since may or something this year.
TMO 1 year ago took down the lower 3G bands here in the area I live and only the LTE bands remain up, however they noted it's band 12 only which as you probably know TMO doesn't allow connections on Band 12 UNLESS a voice and data connection can be established with the device, otherwise you get devices that will roam to Band 12 and all calls will fail outright if it cannot find a 3G connection or 4G HSPA connection.
It's been alot of fun lol.
I have limited understanding of telecommunications but it's not terribly bad
Click to expand...
Click to collapse
Wow I wasn't aware that carriers were droping towers that weren't newer. That's kind of ballsy considering in the US there are tons of areas in butt-f nowhere that at best might get 3g. I'll have to look into this. I switched to att a couple years ago because screw vzw, and I haven't heard anything about this.
Lawlrus said:
Wow I wasn't aware that carriers were droping towers that weren't newer. That's kind of ballsy considering in the US there are tons of areas in butt-f nowhere that at best might get 3g. I'll have to look into this. I switched to att a couple years ago because screw vzw, and I haven't heard anything about this.
Click to expand...
Click to collapse
Here's some info regarding it
https://www.fiercewireless.com/wireless/verizon-to-shut-down-2g-cdma-1x-network-by-end-2019
It largely has to do with making room by using the old frequency bands to expand for 4G and upcoming 5G iirc
Another good link
https://www.reddit.com/r/verizon/comments/b5fig5/cdma_shutdown_everything_you_need_to_know/
WCDMA is probably one of the worst offenders though
GeTex said:
Here's some info regarding it
https://www.fiercewireless.com/wireless/verizon-to-shut-down-2g-cdma-1x-network-by-end-2019
It largely has to do with making room by using the old frequency bands to expand for 4G and upcoming 5G iirc
WCDMA is probably one of the worst offenders though
Click to expand...
Click to collapse
Cdma needs nuked. The only reason why Verizon sticks with it is so they can limit what phone choices people have if they don't accept the band.
Lawlrus said:
Cdma needs nuked. The only reason why Verizon sticks with it is so they can limit what phone choices people have if they don't accept the band.
Click to expand...
Click to collapse
WCDMA is actually a GSM band over 3G for data. CDMA tech Verizon originally used was the idea that you didn't need a Simcard but instead the device could identify itself, so new customers, byod, ect had the ability to activate without needing to wait to go to a store for a simcard, and the sim couldn't be removed/stolen. Verizon as of late will basically allow activating any device on the network that has proper support for verizon regardless where it came from(major change, remember upto 2013 when if it wasn't verizon branded, they said no, and you were screwed, sprint still does that sadly). GSM had other advantages such as just swapping Sims to move service and ect. LTE is actually a tech based on the GSM standard if i recall so CDMA is going away it seems
EvDO, 1xRTT, EDGE, WCDMA, GPRS all that stuff looks like its gonna go away to make room for LTE and 5G
Related
CyanogenMod 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>
/*
* Your warranty is now void.
*
* CyanogenMod members or anyone else on this website is
* 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 the products
* you find here 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.
* Your warranty will be void if you tamper with any part
* of your device / software.
*/
This is a nightly build of CM for the LG G3 on Sprint (ls990).
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.
If you want to help out follow the building guide and then submit a patch to our Gerrit instance.
Installation Instructions:
*NOTE*: You must be Bump'd for this to work. This requires flashing via custom recovery *TWRP* for "ls990”.
1. Download this ROM and 6.0 GApps (recommended Open GApps here). You are going to need to use the Marshmallow ones, this is 6.0)
2. Put both on Internal Storage
3. Reboot into recovery
4. BACKUP CURRENT ROM
5. Factory Reset/Wipe if not already on CM13
6. Flash CM13 (no need to wipe System)
7. Flash GApps 6.0
8. Reboot
9. wait... wait... wait...
10. Profit
To get root/SU, enable Developer Options and change "Root Access" options.
Nightly builds *http://get.cm/?device=ls990.*
Working:
Almost everything
Known issues:
Bluetooth for some users
NFC – not working at the moment
??? - list any others and I will try to get them working as I have time
@invisiblek does most of the work for this device series, much more credit goes to him than me, I just focus on the ls990.
CyanogenMod Blog
CyanogenMod Wiki
CyanogenMod Community
CyanogenMod Forums
CyanogenMod Google+
CM Download Page for ls990
Been on this for a month, and it's without a doubt more stable than anything else I've tried on MM. Some things don't work, like NFC, but they don't work on any current rom. It never shuts down randomly like others I've tried and keep up with. Nice job. I'll take stability over glitchy features every time.
Got No SIM Card detected on this build, trust its because of baseband version.
Has anyone got CM13 and CM12 baseband dumps?
Any solution to No SIM Card?
Been trying official build since they came out, cannot get LTE. Only 3G. I am on ringplus if it helps.. I am on newest lollipop baseband from zvc. Tried editing apn.config xml, airplane mode, changing network modes. All I get is 3G. I did find by flashing an apn fix for ringplus I get lte but for carrier it says Digital roaming instead of aprint.. Is it my device or is it the rom?
Lte works fine on stock lg roms. Everytime i flash TOT back to stock i have to do an rtn reset to get lte back though it gets stuck on 3g. Did clean flash btw every nightly wiping internal,system, data dalvik and cache
Disillusioned said:
Got No SIM Card detected on this build, trust its because of baseband version.
Has anyone got CM13 and CM12 baseband dumps?
Any solution to No SIM Card?
Click to expand...
Click to collapse
Try to do a full wipe and flash again. I haven't had any problems with it detecting my SIM. Worst case flash to stock ensure everything works and then flash back to CM.
allanlgz said:
Been trying official build since they came out, cannot get LTE. Only 3G. I am on ringplus if it helps.. I am on newest lollipop baseband from zvc. Tried editing apn.config xml, airplane mode, changing network modes. All I get is 3G. I did find by flashing an apn fix for ringplus I get lte but for carrier it says Digital roaming instead of aprint.. Is it my device or is it the rom?
Lte works fine on stock lg roms. Everytime i flash TOT back to stock i have to do an rtn reset to get lte back though it gets stuck on 3g. Did clean flash btw every nightly wiping internal,system, data dalvik and cache
Click to expand...
Click to collapse
In general mine stays on Domestic Roaming but that depends on how you are connected to the network. Every once in a while mine will show Sprint. Also you don't need to wipe prior to flashing nightlies unless you are experiencing issues.
Been flashing the nightlies since day one of release, and this by far the most stable, fast, overall amazing MM rom I've seen. Smooth as silk even with the stock kernel
flashed last nightly, almost all apps force close, rom is unusable, flashed twice. And no GSM signal
jesus.sea said:
flashed last nightly, almost all apps force close, rom is unusable, flashed twice. And no GSM signal
Click to expand...
Click to collapse
are you sure you have a LS990?
syndre said:
are you sure you have a LS990?
Click to expand...
Click to collapse
Yep!, it was my bad, i was coming from fulmics and had adaptive storage enabled, that was causing the force closes, i guess a problem with teh encryption, just set to forget the storage and everything was OK with the apps.
For the signal issue i had to flash the GSM patch and worked again.
i'm on LS990 using GSM Network on Mexico
Really enjoying the ROM. Thanks for this.
One question... I'm on sprint ls990 and my data speeds have dropped. Considerably. Is there a fix for this, or something I didn't do on my end when flashing? Thanks.
Great ROM! No issues with nightly updates at all. Best ROM I have used on this phone..clean flashed with bumpd TWRP...looking forward to new updates..Thanks!!
Are there any running issue for those using this ROM on the current build besides whats posted? I'm getting horrible dropped calls on RR.
Anyone figure out how to get SuperSU updated?
l_4Fhit_l said:
Are there any running issue for those using this ROM on the current build besides whats posted? I'm getting horrible dropped calls on RR.
Click to expand...
Click to collapse
You might try updating your PRL and see if that helps at all.
gsm sim not working any fix?
Kasual52e said:
You might try updating your PRL and see if that helps at all.
Click to expand...
Click to collapse
I think that might have worked! Thanks man
Anyone else getting a force close with their Clock app when their alarm goes off? My alarm still works, but I'm worried it'll close itself and make me late for work.
Ok, fixed the clock issue by freezing the Clock app and redownloading it from the Play Store.
I've noticed I can't make any in-app purchases with this ROM. I wiped my cache/davlik and flashed a newer version of GApps which didn't work, I then installed a newer apk of Google Play Services and that caused a force close issue, I wiped everything, reflashed the new version of GApps and now I'm back to square one. Not sure what I can do from this points, any ideas?
Edit:Figured it out! Lucky Patcher was messing my store connection up somehow. Froze it via Titanium Backup, cleared the data/cache from the Play Store app, and now everything is working.
Anybody have the issue of their display being too dim?
On lowest brightness, display is barely visible even in complete darkness. Highest brightness is fine for indoor but outdoor its too dim
Yes, adaptive brightness is off. I am on LS990, latest 3/19 nightly. Did not have this problem on stock, brightness was fine both at lowest and highest.
allanlgz said:
Anybody have the issue of their display being too dim?
On lowest brightness, display is barely visible even in complete darkness. Highest brightness is fine for indoor but outdoor its too dim
Yes, adaptive brightness is off. I am on LS990, latest 3/19 nightly. Did not have this problem on stock, brightness was fine both at lowest and highest.
Click to expand...
Click to collapse
Setting > Display & lights > Brightness level is set to what you want
Setting > Display & lights > Adaptive brightness is disabled
Setting > Display & lights > LiveDisplay > Display mode is set to Off
One of those three should do it for you.
{
"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"
}
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?