[ROM][UNOFFICIAL][G7 POWER] Havoc OS 3.2 [10] [02/27/2020] - Moto G7 Power ROMs, Kernels, Recoveries, & Other D

{
"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.

Related

[ROM][OFFICIAL] LineageOS 14.1 for Nexus 5X (bullhead)

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.

[ROM] [5.1.1] [G360T/T1] AeroROM v1 | Built for performance

{
"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.

[ROM][LineageOS][14.1][Official] for ls990

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.

[OFFICIAL] LineageOS 18.1 for the Nexus 7 2013 (Wi-Fi & LTE) - Repartition Only (flox/debx)

{
"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?

General [TOOL][AUTOINSTALLER][GSI]SMINORI GSI AUTO INSTALLER FOCO M4 PRO

After i'm search many tutorial and thread about installing clean and optimal GSI and take a lot of time.
So, i decided to make batch auto installer for GSI ROM for help u guys, this is easy way for installing gsi rom WITH JUST PRESS ENTER
SMINORI GSI TOOL RELEASE
{
"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"
}
HOW TO USE:
1. DOWNLOAD & EXTRACT SMINORI GSI AUTO INSTALLER
2. DOWNLOAD YOUR FAVORITE GSI ROM HERE (choose arm64 a/b)
3. EXTRACT GSIROM.IMG TO SAME FOLDER WITH THE TOOL FOLDER
4. RENAME THE GSIROM.IMG TO SYSTEM.IMG
5. REBOOT YOUR PHONE TO FASTBOOT MODE AND CONNECT TO PC
FILE ORDER IN FOLDER SHOULD BE LIKE THIS
6. OPEN SMINORI GSI TOOL.bat
7. FOLLOW THE INSTRUCTION & JUST PRESS ENTER
ENJOY YOUR FOCO WITH GSI ROM​
SOME EVIDENCE:
NEED TO REMEMBER:
I've used this tool several times to install gsi rom and it worked without any problem.
almost all roms from the link above can be installed and can run stable on foco m4 pro.
DON'T FORGET TO HIT THANKS IF I HELPED YOU
NO NEED TO DONATE ME, JUST SAY THANKS TO ENCOURAGE ME ​
Awesome!!!
Please update the post with more info like: whats necessary to make this process (UBL, custom recovery...) And How to revert this to stock state
This is really helpful, thanks! Could you give us a review of how well the GSI you've chosen works for this device? Any particular bugs etc?
nairaldo said:
Awesome!!!
Please update the post with more info like: whats necessary to make this process (UBL, custom recovery...) And How to revert this to stock state
Click to expand...
Click to collapse
because until now there is no stable custom recovery for this device so just use stock recovery. and because this tool requires the process in fastboot mode so it requires unlocking the bootloader.
aricooperdavis said:
This is really helpful, thanks! Could you give us a review of how well the GSI you've chosen works for this device? Any particular bugs etc?
Click to expand...
Click to collapse
later i will make a thread how to install specific gsi rom.
now i'm trying to use pixel experience last update for daily use.
I will tell my experience at least after using it for 2 weeks and create a thread for how to install it.
and about particular bugs, after fixing some bugs at the beginning now what I feel is just a general bug in the camera.
Good tool. Guys, are you satisfied with your GSI installs? (no bugs?). There is echo during phone call (I hear myself) for me and automatic brightness is also broken a bit.. Did you noticed these bugs too?
Are you facing any bugs ?
Like volte , camera , calling , sound , 90 hz display ?
Aj_$tyle$ said:
Are you facing any bugs ?
Like volte , camera , calling , sound , 90 hz display ?
Click to expand...
Click to collapse
volte , camera , calling , sound , 90 hz display it all can be fixed in the phh treble setting.
let me explain what is meant about stable in my thread. what I mean by stable is the installation process. in the script that I made not only to install gsi, the scrit will also disable verification and delete partitions that are not needed by the gsi rom.
for the GSI ROM itself, until now I am still comfortable using it for daily needs.
just a general problem that is not only in the fleur device. but all devices are the same.
common gsi issues : Auto brightness, bluetooth audio(android13) thats only for me. and yaa camera off course is different with stock. but not problem at all.
NOTE: if you want to install gsi with minimum bugs and stable. use vendor from android 11.
because of my experience when using a vendor from android 12 when installing gsi android 13 there was a compatibility problem. like in AOD, Bluetooth, and can't boot in pixel experience.
soutaminori said:
volte , camera , calling , sound , 90 hz display it all can be fixed in the phh treble setting.
let me explain what is meant about stable in my thread. what I mean by stable is the installation process. in the script that I made not only to install gsi, the scrit will also disable verification and delete partitions that are not needed by the gsi rom.
for the GSI ROM itself, until now I am still comfortable using it for daily needs.
just a general problem that is not only in the fleur device. but all devices are the same.
common gsi issues : Auto brightness, bluetooth audio(android13) thats only for me. and yaa camera off course is different with stock. but not problem at all.
NOTE: if you want to install gsi with minimum bugs and stable. use vendor from android 11.
because of my experience when using a vendor from android 12 when installing gsi android 13 there was a compatibility problem. like in AOD, Bluetooth, and can't boot in pixel experience.
Click to expand...
Click to collapse
Can you tell me if you are able to use the camera properly? Like sometimes some lenses don't work in some roms, like the macro or wide.
Is something like that happening or it's all stable.
And installing a android 11 gsi wd be the most stable for daily usage right?
I tried a few gsi's, out of them corvus os (android 12 ver) was the most stable. However, I was unable to make or receive calls on all of the gsi's that I flashed. Also the gcam modules that I tried to install kept crashing everytime I tried to open them. Due to a lack of a stable recovery, I wasn't able to install gapps. Corvus OS didn't have inbuilt gapps. And I cant think of ways to install them.
It's a bummer, really. I really liked how corvus os looked. I guess I have to revert back to old annoying Miui.
If there are ways to fix some if not all the issues, please do post.
Eagerly waiting for the fixes )
warhead1721972 said:
I tried a few gsi's, out of them corvus os (android 12 ver) was the most stable. However, I was unable to make or receive calls on all of the gsi's that I flashed. Also the gcam modules that I tried to install kept crashing everytime I tried to open them. Due to a lack of a stable recovery, I wasn't able to install gapps. Corvus OS didn't have inbuilt gapps. And I cant think of ways to install them.
It's a bummer, really. I really liked how corvus os looked. I guess I have to revert back to old annoying Miui.
If there are ways to fix some if not all the issues, please do post.
Eagerly waiting for the fixes )
Click to expand...
Click to collapse
Hello, I recommend the gsi roms that come with the gapps included. You can also install the gapps with magisk, I use the pixel android 13 on the redmi note 11s. I don't use custom recovery if it's not stock.
post the CherishOS android 13 rom everything works and is very good.
ped1609 said:
Hello, I recommend the gsi roms that come with the gapps included. You can also install the gapps with magisk, I use the pixel android 13 on the redmi note 11s. I don't use custom recovery if it's not stock.
post the CherishOS android 13 rom everything works and is very good.
Click to expand...
Click to collapse
are you able to make calls and recieve them? internet and wifi works fine but i just cant seem to figure out the calling problem
warhead1721972 said:
are you able to make calls and recieve them? internet and wifi works fine but i just cant seem to figure out the calling problem
Click to expand...
Click to collapse
No he tenido problemas,bluetooth conexión con pc funciona para transferir archivos,llamadas funciona,nfc no uso,auriculares tambien,doble toque,led pantalla puedes poner el color que quieras.whasspap se olle bien.
Tried several GSI (almost all of them ) on M4 pro 4G phone. I don't have any specific demands from phone - just calls, internet, so didn't try bluetooth or else.
+ : Everything kinda worked. 90Hz is in Phh's settings. Calls worked (at least with that rom i tried to call), internet also worked. Android 13 is nice, i liked Pixel Experience and, of cource, endless possibility to tweak in some roms.
- : Well, what surprised me was sluggish desktop/menu scrolling, even with 90Hz screen enabled. Not so smooth like in MIUI, and that was maybe the main reason i got back to default OS.
Camera (even didn't try all those cam tweaks, i remember from other phones that you always end up with "not that quality" feeling when using not a propieritary camera). Not that i use it a lot, so it was not really a game changer, but anyway.
Also, if i understand correctly, to install Magisk you have to flash some additional img file (product_gsi.img to logical partition, without deleting it), but i installed GSI roms on top already rooted boot img, so that was not necessary - root was found when i installed magisk manager.
Roms that loaded:
SuperiorOS
crDroid-8.5
SparkOS
PixelExperience
CherishOS
Bootloop:
RD-A13
ArrowOS
crDroid-9.0
Excellent ! IIRC all A13 are bootlooping, while A12 are not, or i missread through the name of the roms you tested ?
Did you come from A12 or A11 ? I'm currently on A11, and i'm wondering if direct use of GSI A12 is working
Thank you !
Graveen said:
Excellent ! IIRC all A13 are bootlooping, while A12 are not, or i missread through the name of the roms you tested ?
Did you come from A12 or A11 ? I'm currently on A11, and i'm wondering if direct use of GSI A12 is working
Thank you !
Click to expand...
Click to collapse
All of listed (except CrDroid 8.5 - it is Android 12) are Android 13 GSI roms. And yes, my MIUI is European, so it's Android 11.
keturidu said:
All of listed (except CrDroid 8.5 - it is Android 12) are Android 13 GSI roms. And yes, my MIUI is European, so it's Android 11.
Click to expand...
Click to collapse
Ok, just starting with M4 Pro, i was not aware EU firmware was implying A11 Thank you
I don't understand the difference between fastboot and fastbootd.
Anyone can help me understand ? Thank you ! i can fastboot flash system with fastbootd, while not under fastboot. Is it similar for boot.img ?
Graveen said:
I don't understand the difference between fastboot and fastbootd.
Anyone can help me understand ? Thank you ! i can fastboot flash system with fastbootd, while not under fastboot. Is it similar for boot.img ?
Click to expand...
Click to collapse
fastbootd flashes in a different partition afaik. dont try flashing anything there unless you know what you're doing. Fastboot generally is the answer.
warhead1721972 said:
fastbootd flashes in a different partition afaik. dont try flashing anything there unless you know what you're doing. Fastboot generally is the answer.
Click to expand...
Click to collapse
Thank you. I can't flash system (no such partition) if i'm not in fastbootd. I think there is virtual partition. The script to go back to stock flash a big bloc superseding everything.
Basically, fastboot is only for boot / vbmeta, and once i switch to fastbootd, i can find the correct A/B partition scheme. This is whati discovered while reading the script, but i'm surprised never see this mentionned here (or i did not read enough, or this is something related to recent updates).
But damn. Stock is so bloated, it would benefit an EvoX or RRemix GSI, but there are nice things on MIUI.
Ok, after really painful week trying to adopt MIUI once again, i gave it up and looked seriously at GSI roms. Luckily, newest updated in list was Evolution X. Pixel with some tweaks options. Gave it a try and this time i tried to configure it better to my needs.
So, sluggish performance (scrolling etc.) is gone by enabling "disable HW overlays". I'm not a power user, so didn't notice of faster battery discharge. Installed "Version Green 5000mah/30W" (to be precise, i don't know if it's necessary). Phh treble settings also lets you to repair backlight. Got google camera from another thread.
All in all, much better experience (and visual feeling) than MIUI, even with all miuizers, debloating and 3rd party apps. Android13, no stupid MIUI intrusions into my space, no battery saving policy, that disables my usable apps by random. Easy way to use FNG gestures.
Latest rage i got was when i changed something with tweaks and screen won't turn off by pressing power off button, except from launcher screen. Could not find for several days, what and where i changed. That was last drop that convinced me to go deeper the rabbit hole.

Categories

Resources