ProtonAOSP
Android 12 ROM
ProtonAOSP is a minimal Android fork (custom ROM) focused on UI/UX and performance, with a touch of privacy.
Screenshots
Screenshots of the latest version
Installation
This ROM is currently distributed as flashable ZIPs. Flash it the same way you would flash ROM ZIPs. Don't forget to wipe all data using "fastboot -w" before booting the ROM.
Features
List of current features, with accompanying screenshots and explanations
Downloads
Downloads and changelogs for all versions
Builds with and without minimal Google services (gapps) included are provided for convenience.
Support
If you have questions or concerns, please read the Frequently Asked Questions before asking. It saves time for everyone involved, especially you, and allows us to provide higher-quality answers for all users.
Website with comprehensive documentation
Join the Telegram group for support and extras
Please consider donating to @kdrag0n to support development if you found this helpful: recurring donation to keep the project alive in the long term or buy him a coffee
Kernel source code
ROM source code
Link to AOSP 11: https://github.com/JarlPenguin/rele...001/aosp_montana-ota-retrofit-eng.kiam001.zip
Has the same bugs as LineageOS 18.1.
AOSP 12 has been dropped in favor of ProtonAOSP.
AOSP 11/12 and ProtonAOSP sources are on my GitHub and should be fully buildable. If not, open an issue here.
а можно просто командами рассписать ?
but can you just write down the commands?
JarlPenguin said:
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
Instructions:
Download the latest super images, build, recovery image and GApps (if you need them)
Flash the downloaded super images and recovery image via fastboot
Boot to recovery
Format system and perform a factory reset
Reboot to recovery
Flash the latest build
Flash GApps and any other necessary add-ons
What's working:
WiFi
Camera and Camcorder
Bluetooth
Fingerprint - Oreo firmware required
OTG
Video Playback
Audio
RIL
VoLTE
You tell me
Known issues:
SELinux: Permissive
You tell me
Not tested:
NFC
GPS
USB tethering/audio
Downloads:
Super images: Here
Builds: Here
Recovery: Here
Google Apps: Here
Reporting Bugs
All bugs should be reported here: Issue Tracker
DO NOT Report bugs if you're running a custom kernel or you installed Xposed
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /proc/last_kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues. Any bug not reported in the bug report format below may be ignored.
Code:
What is your--
version:
Download url:
Gapps version:
Did you--
wipe:
restore with titanium backup:
reboot after having the issue:
Are you using--
a task killer:
a non-stock kernel:
other modifications:
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
Thanks to:
@GivFNZ, @Hausemaster, @Rush for testing my builds
@wiktorek140, @karthick mostwanted, @wh0dat, @KalilDev, @AsD Monio, @GoldeneyeS2, @Steve Mathew Joy and @rajatgupta1998 for their hard work on our device sources
LineageOS team
Changelogs:
Code:
2021-10-21:
Fixed Bluetooth.
Fixed FM Radio.
Fixed an issue where the system became unresponsive after enabling and disabling Hotspot and attempting to turn on WiFi.
Fixed GUI glitchiness.
Updated to android-12.0.0_r3 tag.
2021-10-18:
Initial release.
Source code:
Common device tree: https://github.com/JarlPenguin/device_motorola_msm8937-common
Device tree: https://github.com/JarlPenguin/device_motorola_montana
Kernel: https://github.com/LineageOS/android_kernel_motorola_msm8953
Click to expand...
Click to collapse
How to flash super image,,, what is the command?
liony77 said:
а можно просто командами рассписать ?
but can you just write down the commands?
Click to expand...
Click to collapse
SDanger4U said:
How to flash super image,,, what is the command?
Click to expand...
Click to collapse
If you don't understand what and how you need to flash you're better off not installing this ROM. It's not 100% stable either.
everything works wonderfully. does not pass certification
First stable build released. Links and changelog have been updated in the OP.
i did everything in order, but recovery wont boot.
janinetavs said:
i did everything in order, but recovery wont boot.
Click to expand...
Click to collapse
It works only lineage recovery,,,,I tested today,,,but my mobile network not working then I uninstalled it
JarlPenguin said:
First stable build released. Links and changelog have been updated in the OP.
Click to expand...
Click to collapse
Hi,
Hope you are doing well.
Are regular builds (flashable via zip) also planned? For A12
newinnov said:
Hi,
Hope you are doing well.
Are regular builds (flashable via zip) also planned? For A12
Click to expand...
Click to collapse
Once I get time to look into the bugs, yes.
H
Hello everyone, it's been a while since the last update. We've managed to partially fix RIL, while audio is behaving somewhat weirdly. Everything seems to work except for mobile data and VoLTE on the 2nd SIM, while as for audio, system and notification sounds are somewhat delayed. As of right now we don't really know the cause, but we're working on fixing these issues. Also, I've implemented the possibility to relock your bootloader, which is useful for people who would like to run custom ROMs, but with the additional security benefits that a locked bootloader brings.
AOSP 12 has been dropped in favor of ProtonAOSP. First build is available here.
Second build with a quick hotfix is up, I recommend that anyone on version 1 flash this build.
Third release available with some minor fixes and a non-gapps build.
Sorry for saying this But I am a beginner so can you please just explain in a way so that I can understand how to install. P.S. I have already tried via twrp and via adb sideload but it just goes on a loop at the stage where it show the id in yellow colour And yeah I have Latest Lineage os installed.
Sorry again for a silly question
JarlPenguin said:
Third release available with some minor fixes and a non-gapps build.
Click to expand...
Click to collapse
I tried it out, and it worked excellently, except for poor battery life on my device (I'd estimate about half the battery life of stock)
This led me to decide to revert to a backup. (Using the Motorola Software Repair Assistant + backup of data using TWRP)
In doing so, I encountered a major issue: the device can no longer connect to mobile networks (including sms) or gps. Reinstalling the ROM restored this, but even a full reset using the SRA also cannot use these networks.
Any idea what if anything I could do to fix this?
SussyBaka said:
Sorry for saying this But I am a beginner so can you please just explain in a way so that I can understand how to install. P.S. I have already tried via twrp and via adb sideload but it just goes on a loop at the stage where it show the id in yellow colour And yeah I have Latest Lineage os installed.
Sorry again for a silly question
Click to expand...
Click to collapse
I also encountered a fair number of bootloops while installing. I think the installed system should be stock (but I may be wrong), so reinstall stock again first, then flash with TWRP (adb sideload works for me). Then run `fastboot -w` in bootloader before booting the device.
_Kumiho said:
I also encountered a fair number of bootloops while installing. I think the installed system should be stock (but I may be wrong), so reinstall stock again first, then flash with TWRP (adb sideload works for me). Then run `fastboot -w` in bootloader before booting the device.
Click to expand...
Click to collapse
I will give it a try Thanks!!
Related
Announcement: due to life complications in the form of a fire while I was away, all my current development for this phone has ceased until further notice. at some point I will start back up. but I digress;
AEX started messing up on my phone and I was able to use a friends laptop to flash the stock rom and made this verrrrrrry poorly made, yet functional dirty stock flashing zip.
its just a dd of the important partitions for stock rom, with magisk'd boot.img (you need the manager) and @Jleeblanch 's Resurected kernel v3.3
ONLY TESTED ON xt1806 US SINGLE SIM VARIANT. TRY AT YOUR OWN RISK
(but honestly if you can flash the NPS26.116-61 xml.zip from fastboot, this should boot)
known issues:
friggen borked the echo commands. didnt care enough to fix. it still tells you what its doing
doesnt install magisk manager
requires about 5 gb of free space on /sdcard during zip installation
features:
Boots to android
pre-rooted
everything from @Jleeblanch 's stock kernel:
Features
+ Passes SafetyNet
+ Magisk works as intended (including modules)
+ AnyKernel2 format
+ WireGuard support (more info)
+ Disabled CRC's on data blocks (30% increase in performace)
+ Fsync On/Off support
+ Added additional I/O Schedulers (Zen, SIO, FIOPS)
+ Increased zram compression streams
+ Tuned adrenoboost (disabled by default)
+ TCP Advanced Congestion Control
+ KCAL Color Control
+ Sound Control (by @flar2)
+ Linux-stable (wip)
+ CAF updates (wip)
+ Works same as stock (or better?
Click to expand...
Click to collapse
)
TL;DR
DOWNLOAD (1.7gb)(gdrive)
Instructions:
wipe data if coming from another rom
MOUNT DATA
install zip
ignore informative errors
-the ones that say unknown command
-ALSO THE FAULTY ERROR TWRP GIVES ABOUT AN ABSENT OS, ignore that'un too
--others might not need be ignored
download & install magisk manager
hit the thanks button maybe? im not even asking for a beer. and man i need one
enjoy
thank you to @Jleeblanch , if youre not ok with me including your kernel let me know and ill take it down sorry for not pre-checking
rom belongs to lenovorola, flash at your own risk not responsible for your stupidity and ignorance yada yada yada dont sue me
"yada yada yada dont sue me" lmao
Nice one. It's nice to have a option like that. Kudos.
vaporwavie said:
"yada yada yada dont sue me" lmao
Nice one. It's nice to have a option like that. Kudos.
Click to expand...
Click to collapse
thanks, gotta cover your ass yaknow? and yea someone released a "guide" to do it in the general section and didnt even try his own work lol. pretty sure thats called a suggestion not a guide
anywho figured someone else might need it in a pinch like i did.
One Debloated Version is interesting
Without the risk of sounding dumb, can someone please explain to me the difference between NPS26.116-61 and NPS26.116-45-5? I have the XT1806 in the US (3GB\32GB)...How many variants of this phone exist?!
smokinjoe2122 said:
Without the risk of sounding dumb, can someone please explain to me the difference between NPS26.116-61 and NPS26.116-45-5? I have the XT1806 in the US (3GB\32GB)...How many variants of this phone exist?!
Click to expand...
Click to collapse
NPS26.116-61 has December 1 security patch, updated thermal configs, and camera updates, just google the rest of the maintenance release notes.
XT1802 to XT1806
Usually the variations are the GSM bands, which models have NFC / DTV, single / dual sim, etc.
No worries on the kernel, glad to see it put to good use
This worked like a charm, thank you!
Hello,
Thank you for making this ROM.
My Moto somehow lost both the IMEI's and faced no network issues.
After trying everything, your ROM worked for me and had resolved all the issues in it.
NOTE: We didn't had any backup of any kind but this ROM still saved the day.
Thank you!
Continuing to rise and modify the different variants of rom stock? how they did with the moto g older? As a collection of stock ROMs
For example:
https://forum.xda-developers.com/moto-g/4g-development/rom-stock-motorola-4g-lollipop-rom-t3142816
Please kindly upload it on any other cloud storage .
I can't open the zip it's giving me some error
Can this be dirty flashed over stock, rooted NPS26.116-45 in order to get the latest security patch?
I'm computerless at the moment if anyone could mirror for the guy having issues downloading it would be appreciated (all I have is gdrive anyway) sorry man
jp0469 said:
Can this be dirty flashed over stock, rooted NPS26.116-45 in order to get the latest security patch?
Click to expand...
Click to collapse
This only flashes /system /oem /and boot. It shouldn't mess with anything on DATA. It's safe to try, but I'd recommend backing up just in case.
I'm 90% sure it would work, as a dirty update. I've used it to dirty reflashes the whole system and not data and it worked fine. just be aware that magisk is weird ever since v15. Reflashes of it may be necessary.
Lost my IMEI by flashing custom roms too
ekamran said:
Hello,
Thank you for making this ROM.
My Moto somehow lost both the IMEI's and faced no network issues.
After trying everything, your ROM worked for me and had resolved all the issues in it.
NOTE: We didn't had any backup of any kind but this ROM still saved the day.
Thank you!
Click to expand...
Click to collapse
hi, @ekamran
I also experienced you issue, no IMEI so no network, tried everything even this one. Still no IMEI. What are the things you tried prior to this to recover your IMEI? THanks.
gebcruz06 said:
hi, @ekamran
I also experienced you issue, no IMEI so no network, tried everything even this one. Still no IMEI. What are the things you tried prior to this to recover your IMEI? THanks.
Click to expand...
Click to collapse
Hey, This ROM is the only thing that has recovered my IMEI.
Before this, I had been in situation where my phone was stuck in BootLoader Mode only and couldn't even access Recovery Mode.
Then I had tried to flash the official firmware via Fastboot method of which some files installed and some didn't but fortunately, I regained access to Original Recovery Mode.
Then I had flased TWRP again and then flashed this ROM.
Everything sorted.
Thanks for developer
And keep it up
Does it work for the Indian variant
Ae3NerdGod said:
Announcement: due to life complications in the form of a fire while I was away, all my current development for this phone has ceased until further notice. at some point I will start back up. but I digress;
AEX started messing up on my phone and I was able to use a friends laptop to flash the stock rom and made this verrrrrrry poorly made, yet functional dirty stock flashing zip.
its just a dd of the important partitions for stock rom, with magisk'd boot.img (you need the manager) and @Jleeblanch 's Resurected kernel v3.3
ONLY TESTED ON xt1806 US SINGLE SIM VARIANT. TRY AT YOUR OWN RISK
(but honestly if you can flash the NPS26.116-61 xml.zip from fastboot, this should boot)
known issues:
friggen borked the echo commands. didnt care enough to fix. it still tells you what its doing
doesnt install magisk manager
requires about 5 gb of free space on /sdcard during zip installation
features:
Boots to android
pre-rooted
everything from @Jleeblanch 's stock kernel:
)
TL;DR
DOWNLOAD (1.7gb)(gdrive)
Instructions:
wipe data if coming from another rom
MOUNT DATA
install zip
ignore informative errors
-the ones that say unknown command
-ALSO THE FAULTY ERROR TWRP GIVES ABOUT AN ABSENT OS, ignore that'un too
--others might not need be ignored
download & install magisk manager
hit the thanks button maybe? im not even asking for a beer. and man i need one
enjoy
thank you to @Jleeblanch , if youre not ok with me including your kernel let me know and ill take it down sorry for not pre-checking
rom belongs to lenovorola, flash at your own risk not responsible for your stupidity and ignorance yada yada yada dont sue me
Click to expand...
Click to collapse
What is the use of flashing oem.
We only need boot and system . is there any risk in flashing OEM.img
ANDROID O said:
What is the use of flashing oem.
We only need boot and system . is there any risk in flashing OEM.img
Click to expand...
Click to collapse
i had changed the moto stock font. no risk, i think only the stock rom uses it normally. contains moto apps and stuff. when you flash an xml.zip it flashes it. i had originally tried to include the modem partition too but it was giving me issues. this is a stock rom so i included stock files, if you had somehow wiped or corrupted oem, stock rom (and possibly others) might not work correctly so i included it.
INTRODUCTION
I posted my configuration before inside a couple of threads. After that, I have received a lot of questions about the same issues. I have also been asked to create a thread so newbies could have an easy way of having an Oreo system up and running in the Axon 7. So I am doing it. Newbies will have an easy entry point to the world of custom Oreo ROMs and a single point to clarify any question. We have a healthy and active Axon 7 scene here at XDA. This guide provides a path to have a custom Oreo system with the latest features available for this device requiring a minimum effort. It applies to any of the 3 Axon 7 flavors: A2017 (China), A2017G (Europe) and A2017U (Americas) with any memory and storage capacity. At this time there are 3 groups of ROMs depending on the Bootstack and GSI support:
1. B32+B10 ROMs use the reliable Nougat bootstack. They are very stable and battery efficient. On the other hand, none of them support dual SIM or HDR+ camera. However they support HDR and Camera2 API.
2. B12 without GSI support ROMs use the Oreo beta B12 bootstack. Full support for Camera2 API and HDR+ but very poor battery performance and stability issues.
3. B12 with GSI support ROMs also use the same Oreo beta B12 bootstack. They also require a separated vendor partition. They share the same benefits and limitations of the previous group. So far they are experimental and the Treble ROMs don't support yet all the Axon 7 Hardware when using them along with a GSI image. They are examples of a Work-In-Progress that is yet to be finished.
WHAT THE HECK IS TREBLE AND GSI?
Since Oreo, all the new devices must have a separated vendor partition to fulfill Google's Treble project requirements. This way the OS is structured in two parts:
1. Treble ROM: includes all the device drivers and vendor related files in the vendor and boot partitions. The Treble ROM is owned and updated by the device vendor or a custom ROM developer.
2. Generic System Image (GSI): Includes the Android OS, it is controlled by Google and allow generic and frequent security and system feature updates directly from Google. It uses the system partition.
So far, custom Android distributions such as LineageOS, Resurrection Remix, AOKP, Dirty Unicorns, AEX, etc... had to create specific ROMs for each supported device. This was painful and it all was depending on the willingness of a developer to maintain a version for each device. Thanks to Treble project, now Android distributions just release a single GSI able to be installed in any device using a Treble ROM. This way they can properly maintain all the devices with a single GSI image by focusing on frequent updates of a single GSI. These custom distributions will also deliver the security and feature updates by Google. So a fully Treble ROM for the Axon 7 will open the door to virtually all the Android distribution out there.
@NFound in the AEX ROM thread) is the only one working in developing a Treble ROM for our device. He has released some incomplete Treble ROMs coupled with non-generic system images. Others like @Kranoner in the Hellsgate Kernel thread or @OrdenKrieger in the LineageOS 15.1 are building and kindly sharing unofficial releases of several custom Oreo 8.1 ROMs that are used in the EDL packages below.
@Victor13f has also created guides on how to install the leaked Stock Oreo 8.0 Beta B12 ROM. I really advise to upgrade to any of the current Oreo ROMs since the current unofficial releases work way better than the previous Nougat versions. The custom AOSP Oreo 8.1 ROMs offer a wider spectrum for tweaking for better performance and battery. Custom kernels are adding full featured and optimized drivers for custom ROMs. They support almost everything, including backported drivers from the latest Linux 4.xx official kernel sources.
BACKUP:
Please note that a dirty flash won't work when coming from any non Treblerized Axon 7 (Axon 7 without the vendor partition). So, if you want to keep your information, then you should do a backup of your data before continuing with this guide. You can use the file manager to move your Documents, Downloads, Music, Pictures, Videos, etc... from your internal storage to an external SD card. You can upload them to a cloud service such as Google Drive, One Drive, MEGA, DropBox, etc. Or use the USB connection to move your information to your PC.
DEVICE UNLOCK:
Unlocking your bootloader will trigger a factory reset, and will delete the internal storage along with all the information in your phone. If your Axon 7 bootloader is still locked, you have to follow this guide before proceeding to the rest of this guide. It works for Marshmallow and Nougat stock phones. Please use that thread to ask any question related to unlocking your device.
INSTALLATION INSTRUCTIONS:
WARNING, THIS GUIDE WILL WIPE ALL THE DATA IN YOUR DEVICE, INCLUDING THE INTERNAL STORAGE.
IT REQUIRES YOUR DEVICE TO BE UNLOCKED, OTHERWISE YOUR DEVICE COULD BE BRICKED.
!!! Whatever you do, it is at your own risk !!!
In case you get stuck at any point in this guide, do not panic! There is a straightforward way to go back to stock. Just follow this Unbrick/Restore guide. I've tried to make things as easier as possible for everyone, specially newbies not used to deal with the Axon 7. So, I have created stable custom EDL packages. In order to reduce the risk and complexity, this one Stop ROM Shop performs all the following actions in a single flash:
- installs TWRP custom recovery
- installs my customized Bootstack
- removes unlocked bootloader annoying warning message.
- installs custom Oreo ROM.
- installs google apps.
- installs custom kernel.
- installs magisk root
- creates vendor partition to treblerize your phone, this way it will be futureproof.
- formats vendor partition as ext4 filesystem to complete the previous task.
- And the guide also helps you to format data and cache as f2fs in case you haven't done it already. It provides better battery, performance and extends the lifespan of the internal flash.
I provide here 2 basic EDL package options. Both of them include the vendor partition so you won't have to perform any additional formatting and backup when upgrading to treble roms. Both options are this way future proof, just choose one of them:
OPTION 1: B32+B10 based EDL Package if you prefer stability. It includes:
- N+O custom Bootstack (B32+B10)
- TWRP 3.2.1-7 recovery by NFound
- Resurrection Remix Oreo 6.0.0 2018.05.11 ROM By Kranoner
- Google apps (ARM64, 8.1, micro)
- HellsGate v3.0 Kernel by Kranoner
- Magisk root 16.7
OPTION 2: B12 based EDL Package If you require dual SIM or full support for HDR+ camera apps. It includes:
- O custom Bootstack (B12)
- TWRP 3.2.2 recovery
- AEX 5.7 20180711 ROM by NFound
- Google apps (ARM64, 8.1, micro)
- HellsGate X12 GClang Kernel by Kranoner
- Magisk root 16.7
Once you had chosen your preferred option then proceed with these steps:
Download and Un7zip the chosen package to a folder in your computer, ensuring there are no errors. I have an A2017U, so the American modem is the package default. If you have an A2017 or A2017G just copy your modem firmware, from the corresponding provided modem subfolder, to the main folder. Just overwrite the default American modem file.
Install MiFlash in your PC. It includes the Qualcomm Snapdragon SoC drivers, nonetheless you can always install the latest Qualcomm drivers.
Enter EDL mode using one of the following options:
by pressing VolUp+VolDn+Power until the power led flashes briefly
Installing a terminal app and typing reboot edl at the app prompt.
connecting your phone to your PC and typing adb reboot edl at your computer's command prompt.
While your phone is completely off, press VolUp+VolDn while connecting your phone to your PC.
If you haven't done yet, it's time to connect your phone to your computer.
Open MiFlash in your computer.
Click Browse button and select the folder you created with the firmware files.
Click Refresh button and your device will appear listed as virtual COM port.
Click Flash button and wait for a few minutes until it finishes. Note the bottom options are not applicable.
Wait a few seconds until the boot animation begins and press again VolUp+Power until the phone vibrates to enter again into recovery. Go to Advanced > Terminal and now type: reboot "dm-verity enforcing"
Press VolUp+Power until the phone vibrates to enter into recovery, then release both buttons. Go to Advanced > Terminal and type: reboot disemmcwp
Wait a few seconds until the boot animation begins and press again VolUp+Power until the phone vibrates to enter again into recovery for a 3rd time. To ensure everything is clean you should format the DATA partition, including internal storage. Go to settings and ensure "Use rm -rf instead of formatting" option is not selected. Then go to Wipe > Advanced Wipe, select Data partition and tap on Repair_or_Change_File_System button and then on Change_File_System button. Select F2FS and confirm action. Do the same to apply F2FS to the Cache Partition. Now, from the main menu > Wipe, select and clean dalvik.
NOTE: If you receive an error while formatting data, then go to Wipe > Advanced Wipe, select Data partition and tap on Repair_or_Change_File_System button and then on Change_File_System button. Format DATA as EXT4 first and, without leaving TWRP do it again as F2FS. That will fix the issue.
Go to main menu and reboot system.
Complete the setup process so you can continue with the rest of the customizations not included in the basic package:
SOUND EXPERIENCE:
The following steps will provide you with Dolby ATMOS and Viper4Audio pre-processors along with the HiFi DAC output. Please note that the activation of these features will drain your battery faster since both will use your CPU. Nonetheless the benefits are evident. if you want to fully enjoy the audio capabilities of the Axon 7 you should go ahead and use them. The steps are:
Download Mixer_AK4490.zip and Dolby-Oreo.zip to your phone.
Open Magisk Manager app, go to the Download section and Download (do not install yet) Ainur Sauron, Viper4Android FX and Audio Modification Library.
Reboot to recovery the same way you did during System installation, press install, navigate to /sdcard/MagiskManager folder and install Ainur Sauron, Viper4Android (I prefer 2.5.0.5 and traditional interface, however it is all up your personal preference) and Audio Modification Library zip files in that order. Do not reboot after flashing these files, just navigate now to the /sdcard/Download folder and flash Dolby-Oreo.zip and Mixer_AK4490.zip
SCREEN COLOR ENHANCEMENT:
Download and install KCAL Color Calibration/enhancement app. I only modify the Saturation to 62 to get amazing vibrant colors from this AMOLED screen, nonetheless this is a very personal configuration. At the end this has to please your own eyes. . This app optional since Kernel Adiutor and EX Kernel Manager apps can also configure Qualcomm SoC Color Control.
AVOID BATTERY DEGRADATION:
Install Battery charge Limit [ROOT] app. Open it and set Limit charge to 85% and recharge below 79%. Do you want to avoid your battery to wear as the time go by? do not miss this guide to understand why this step is so important for the health of your device.
BETTER CAMERA:
+ Snap Camera App
I am using, and heavily recommend the paid version of Snap Camera HDR. It supports Camera2 API with full manual and HDR support. Find recommended settings here.
Testing now GCAM v4.0. Nonetheless so far I am just starting testing.
Bacon Camera is another Camera I am now actively testing.
The next level of this guide will provide with instructions on how to change recovery, ROM, kernels and all the details and options you have. It is late today so I'll finish it later.
Hope it helps. I will be updating this guide in the future as soon my configuration changes or I find new technologies, apps or patches. If you know about a better option just post your suggestions!
Thanks and credits go to @NFound, @Kranoner, @Infy_AsiX, @roisuke, @Skrem339, @djkuz and you too for bringing up issues and valuable solutions.
Yes! I almost pm'd you like 3 times to ask if you would do exactly this. By far, I am not a noob, but honestly, i can finally take the plunge now knowing i have a place to look back and proper steps. I still have yet to flash TWRP 3.1.1-7 because of the [no bet removing inscription] bit on that thread, but reading over it like a dozen times, im fairly confident the only thing that will not work correctly on my a2017u is removing the warning that my bootloader is unlocked. Correct me if Im wrong on that one. Thank you, @Oki. Many thanks, brother.
kitcostantino said:
Yes! I almost pm'd you like 3 times to ask if you would do exactly this. By far, I am not a noob, but honestly, i can finally take the plunge now knowing i have a place to look back and proper steps. I still have yet to flash TWRP 3.1.1-7 because of the [no bet removing inscription] bit on that thread, but reading over it like a dozen times, im fairly confident the only thing that will not work correctly on my a2017u is removing the warning that my bootloader is unlocked. Correct me if Im wrong on that one. Thank you, @Oki. Many thanks, brother.
Click to expand...
Click to collapse
Removing the message at boot is easy. If you already have TWRP Exclusive v3.2.1-7 and the aforementioned bootloader, then you just have to boot TWRP Advanced menu > More > Del inscription. Easy, Isn't it? It works in my A2017U so It should work for you too.
Oki said:
Removing the message at boot is easy. If you already have TWRP Exclusive v3.2.1-7 and the aforementioned bootloader, then you just have to boot TWRP Advanced menu > More > Del inscription. Easy, Isn't it? It works in my A2017U so It should work for you too.
Click to expand...
Click to collapse
This was actually why:
NFound said:
TWRP Exclusive™
For "U" models pacth cleaning inscriptions bootloader NO BET!
Warning! "Del Inscription" - only for A2017 and A2017G !!!
Click to expand...
Click to collapse
^^^^^^^^This was actually why I thought it didn't work. Honestly, I don't mind the warning. I just had to ascertain if that was the only issue. Nfound had already confirmed it worked on a2017u. And removing that warning hasn't ever mattered to me that much.)
kitcostantino said:
This was actually why:
^^^^^^^^This was actually why I thought it didn't work. Honestly, I don't mind the warning. I just had to ascertain if that was the only issue. Nfound had already confirmed it worked on a2017u. And removing that warning hasn't ever mattered to me that much.)
Click to expand...
Click to collapse
Well NFound just tried to say that his solution was not tested at that time in an A2017U. Actually the 2017U is unbrickable thanks to the hardware EDL mode of the Qualcomm SOC.
By the way, I have updated the OP. Now it matches my current configuration. I have also mentioned my current testing efforts in the battery and camera areas.
Regards
Hi. Any fix for Dual Sim? I read through XDA and it seems dual sim is still not fixed. I am getting tired with nougat ROMs but without dual sim I have to stick with it...
@kitcostantino, there's also another method to get rid of that startup message that might work.
http://forum.xda-developers.com/showthread.php?p=74445757
ZTE Axon 7 A2017U, AospExtended v5.4 ROM, HELLSGATE Kernel, Multiboot, Tapatalk 4.9.3
Hello,
just a little question: Does this guide work on the Axon 7 2017G too? The RR Oreo Rom are for the 2017U....
Thx
Dave_XDA said:
Hello,
just a little question: Does this guide work on the Axon 7 2017G too? The RR Oreo Rom are for the 2017U....
Thx
Click to expand...
Click to collapse
Yes, the guide is valid for any Axon 7 flavor: Chinese, Euro and Americas.
marcdw said:
@kitcostantino, there's also another method to get rid of that startup message that might work.
http://forum.xda-developers.com/showthread.php?p=74445757
ZTE Axon 7 A2017U, AospExtended v5.4 ROM, HELLSGATE Kernel, Multiboot, Tapatalk 4.9.3
Click to expand...
Click to collapse
It is actually the same method. TWRP flashes that aboot image when selecting the option I mentioned. I still see the TWRP method a lot better since it doesn't require any extra download. You can see all the images and add-ons when exploring the filesystem while in TWRP Exclusive.
Thx for your answer.
I got this Axon 7 from my brother with the AEX Oreo Rom install'd. I wanne try out the RR Oreo because i use'd the RR on my old ASUS Phone.
Do i need to install the Bootloader you linke'd in your guide or can i install the RR Oreo with a clean install over the AEX Oreo Rom?
Thx again
Dave_XDA said:
Thx for your answer.
I got this Axon 7 from my brother with the AEX Oreo Rom install'd. I wanne try out the RR Oreo because i use'd the RR on my old ASUS Phone.
Do i need to install the Bootloader you linke'd in your guide or can i install the RR Oreo with a clean install over the AEX Oreo Rom?
Thx again
Click to expand...
Click to collapse
There is no problem as long you have an Oreo Bootloader. Since you are already running a custom Oreo ROM it means you already have a valid bootloader. Thus, you only need to flash the RR-O ROM. Should you find any problem you can just flash the latest bootloader I link in the OP or go back to AEX. It is important to do a clean install when switching Oreo flavors, as you plan, otherwise you will face problems.
Thanks for this. Been running stock since I got the phone, but missing the old phone days where I used to flash something new like once a week. Gonna try this out tonight I think. Really appreciate the concise directions
Are there known issues in returning to B35 Stock, should the RR(O) prove unsatisfactory?
amphi66 said:
Are there known issues in returning to B35 Stock, should the RR(O) prove unsatisfactory?
Click to expand...
Click to collapse
No issues, you can always go back to B35.
Oki said:
It is actually the same method. TWRP flashes that aboot image when selecting the option I mentioned. I still see the TWRP method a lot better since it doesn't require any extra download. You can see all the images and add-ons when exploring the filesystem while in TWRP Exclusive.
Click to expand...
Click to collapse
Thanks for the info.
Never used/explored TWRP Exclusive's extras really. In my environment I might break something [emoji39] but cool that everything is there.
ZTE Axon 7 A2017U, AospExtended v5.4 ROM, HELLSGATE Kernel, Multiboot, Tapatalk 4.9.3
How long does the first boot after flashing the bootloader take? I don't seem to get past the ZTE powered by android screen.
Never mind. Just hold Power + Volume Up at boot.
Thanks !! Oreo AND RR together !!
I will flash it tomorrow on my A2017G !!
(maybe you should write the A2017G compatibility on the first page because this :
RR-O-v6.0.0-20180422-axon7-Unofficial.zip
for the ZTE Axon 7(2017U), by Kranoner
on androidfilehost almost made me missed it )
EDIT : Does this ROM+kernel have the dualsim problem ?
Oki said:
Removing the message at boot is easy. If you already have TWRP Exclusive v3.2.1-7 and the aforementioned bootloader, then you just have to boot TWRP Advanced menu > More > Del inscription. Easy, Isn't it? It works in my A2017U so It should work for you too.
Click to expand...
Click to collapse
After doing this, I can't unlock my phone after restart by entering password. On A2017U and AEX Oreo latest. Any1 had this issue?
If anyone does, here's the fix: https://forum.xda-developers.com/axon-7/help/to-remove-screen-unlock-pattern-t3768575
ashishv said:
After doing this, I can't unlock my phone after restart by entering password. On A2017U and AEX Oreo latest. Any1 had this issue?
If anyone does, here's the fix: https://forum.xda-developers.com/axon-7/help/to-remove-screen-unlock-pattern-t3768575
Click to expand...
Click to collapse
What have you really done my friend? This guide requires a complete cleanup so it is impossible that you had any locksettings after a clean install. If you follow all the steps and follow the guide then you shouldn't have any problem.
The lock settings get corrupted after migrating to f2fs, and you can also find that problem when dirty flashing some roms or kernels. For that reason, to take care of that step, in the f2fs migration link, there is a link to a very detailed way to cleanup the lock settings. You can find that guide here: https://forum.xda-developers.com/axon-7/how-to/guide-access-locked-axon-7-how-to-t3525403 but, it shouldn't happen when following the steps of this guide. By the way, this guide requires RR Oreo ROM, and you mention you are using AEX Oreo...
Update March 23, 2019: I'd like to apologize to everyone. It looks like I am not going to be able to actively keep this thread updated like I used to. I have had too much going on at home an work and it doesn't look like it's going to settle down any time soon. The thread is still usable so I will leave it open for discussion.
Team Win Recovery Project
Code:
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards, fires, rigged elections,
* specks of dusk sitting on cursors, cursors that mock you--waiting for cursor
* revenge, thermonuclear war, or you getting fired because the alarms failed
* and you could not call in.
*
* Please ensure you have an advanced understanding of this device before
* flashing it! YOU are choosing to make these modifications or your own free will.
This is the first official build of TWRP for the Motorola Moto G6 (ALI)!
Notes:
Decryption is finicky: Currently only vold decryption is working. This image must be flashed to properly decrypt. Updates may cause issues with decryption.
If you format data (Not just factory reset) after decrypting you must reboot into recovery and format again.
If you are unable to unlock your phone after restoring a data backup that had a lock code on it (and TWRP is able to decrypt using default password) you'll need remove the '/data/system/locksettings.db' while in TWRP. After that you should be able to reboot into Android and set a lock code. If you cannot then please use this thread as a guide and try again. Bascially you just delete more, however I was able to boot after just deleting the one file with a pattern set (Maybe random luck, maybe not)
If you have any other issues please let me know and I'll work toward fixing them! AS ALWAYS, IT'S YOUR RESPONSIBILITY IF YOU USE THIS SOFTWARE
Known Issues:
I have just noticed some odd behaviour if you input an incorrect decryption password/pattern/etc in twrp. It can cause an issue while entering the lockscreen password/pattern/etc while booting up. Under normal circumstances these two are the same, hence why restoring can also cause a similar issue, though that one is easily fixable. The onIy way to clear the decryption pass is to format. I am unsure at the moment what is causing this, but clearly it has something to do with the decryption. At this time I'd say it'd be best to remove your current lockscreen password/pattern/etc before booting into twrp to avoid this issue. A possible work-around would be to reboot to twrp, enter the correct password, back up your data, format (reboot to twrp and format again), then restore your backup (and possibly need to delete the '/data/system/locksettings.db' file. Your data would still exist that way. I am going to work to fix this asap and maybe see if I can get another build without decryption made for official use for now.
Flashing zips that require BusyBox will not work with the official version right now. I've built an unofficial version to use until a new official build is triggered.
ALI's Changelog: Post #2
Download: twrp.me Download
Unofficial Download (updated more often): twrp-v3.2.3-unofficial-ali-20181110.img
Simple Installation Method:
1) boot to fastboot
2) fastboot flash recovery <twrp-image-name>.img
Other instructions are available on the Official download page. It's up to you to backup your factory recovery first if you wish to have a backup: Post #3
Thanks to the TWRP team and everyone who has put in effort to make these things possible!
@Jleeblanch - Wonderful advice and guidance
@Dadud - testing
@ Everyone at github
@ XDA and the people who provided TWRP compiling threads
If I've forgotten someone who you think needs mention please let me know!
* This page will continue to be edited as more information comes
XDA:DevDB Information
[RECOVERY][OFFICIAL] TWRP v3.2.3 [2018-10-20], Tool/Utility for the Moto G6
Contributors
dejello
Source Code: [url]https://github.com/TeamWin/android_device_motorola_ali[/URL]
Version Information
Status: Stable
Current Stable Version: 3.2.3-0
Stable Release Date: 2018-10-20
Current Beta Version: 3.2.3 Unofficial
Beta Release Date: 2018-11-10
Created 2018-10-21
Last Updated 2018-11-10
Changelogs
TWRP Changelog:
v3.2.3 changelog
ALI's Official Changelog:
v3.2.3-0 (Oct 20, 2018)
- N/A, first build!
ALI's Temp. Unofficial Changelog:
v3.2.3 (Oct 31, 2018) (This log will get moved to official when it gets updated with these changes)
- Stop using toybox (Use busybox!)
- Added vendor image mount point
Factory Backup Information
It's up to you to determine if you want/need a factory recovery image backup before flashing:
To boot twrp first (it will fail decryption, don't worry about it) just do the following while replacing <twrp> with the actual file name.
Code:
fastboot boot <twrp>.img
Then to back up your stock/factory recovery while booted in TWRP do the following.
Code:
adb pull /dev/block/bootdevice/by-name/recovery stockrecovery.img
First [emoji14]
For real tho, nice work and congrats [emoji41]
Woot Woot! Congrats bro?
Lockscreen after restore
Hello, this method (delete lockscreen) after restore backup works for me to ?
Decryption doesn't work for me. XT1925-6 Ali
giant22000 said:
Decryption doesn't work for me. XT1925-6 Ali
Click to expand...
Click to collapse
I'll need more details if I'm to look into it. I also have an xt1925-6. Any logs? What version software are you running? What kind of lock screen are you using (pin, password, pattern, none, etc)? What happened from booting twrp up to the point of decryption failure? The more information I have the better chance I have at rectifying the issue.
[EDIT] I just did some messing around and came across something I hadn't seen before:
I have just noticed some odd behaviour if you input an incorrect decryption password/pattern/etc in twrp. It can cause an issue while entering the lockscreen password/pattern/etc while booting up. Under normal circumstances these two are the same, hence why restoring can also cause a similar issue, though that one is easily fixable. The onIy way to clear the decryption pass is to format. I am unsure at the moment what is causing this, but clearly it has something to do with the decryption. At this time I'd say it'd be best to remove your current lockscreen password/pattern/etc before booting into twrp to avoid this issue. A possible work-around would be to reboot to twrp, enter the correct password, back up your data, format (reboot to twrp and format again), then restore your backup (and possibly need to delete the '/data/system/locksettings.db' file. Your data would still exist that way. I am going to work to fix this asap and maybe see if I can get another build without decryption made for official use for now.
I have added this to the first post.
Damn thanks !
Hi. First thank for the contribution.
I would like to know if someone has the stock twrp, modeled 1925-1. When I modified my stock twrp, I made a back up, but I lost it.
I would like to update my security patch, but I can not because it has modified the twrp.
aaleej0 said:
Hi. First thank for the contribution.
I would like to know if someone has the stock twrp, modeled 1925-1. When I modified my stock twrp, I made a back up, but I lost it.
I would like to update my security patch, but I can not because it has modified the twrp.
Click to expand...
Click to collapse
So I guess I will be the one to say it. I'm giving you one warning about this. It's against forum rules to post on multiple threads with the same subject. I've answered your question on the Ali stock firmware thread also. Please read guides and threads instead of skimming through them because it's been answered multiple times. Next time you do this and post the same thing on multiple threads I will be the one reporting you. Have a good day.
I have added an unofficial build tonight (Oct/31/2018) to fix an issue flashing zips that need busybox (Resurrected Kernel, etc) versus toybox. It also adds a 'vendor image' mount point for use in backups and flashing. Once official gets updated this unofficial build will be removed.
Hello, could you consider supporting the Moto g 6 play xt922-4 I'm welling to help out with logs or anyfile if needed.
jglm4u said:
Hello, could you consider supporting the Moto g 6 play xt922-4 I'm welling to help out with logs or anyfile if needed.
Click to expand...
Click to collapse
There are certain reasons there is no official twrp for our moto g6 play devices yet. Is there issue your having?. Dejello supports the regular g6 and for all intensive purposes I've being doing support for the g6 play.
jglm4u said:
Hello, could you consider supporting the Moto g 6 play xt922-4 I'm welling to help out with logs or anyfile if needed.
Click to expand...
Click to collapse
ninjakira said:
There are certain reasons there is no official twrp for our moto g6 play devices yet. Is there issue your having?. Dejello supports the regular g6 and for all intensive purposes I've being doing support for the g6 play.
Click to expand...
Click to collapse
I don't have access (well, sort of but not really) to a g6 play. My son has one, but it's not unlocked or anything and I won't experiment on his phone without having everything backed up.... Besides, getting the damn thing away from him for extended periods when he isn't in trouble would be something.... I thing it's glued to his face or something.
I am also not up to date on any issues or reasons why twrp isn't official for the g6 play. Be aware that even this version for the g6 has some issues (workarounds are available for everything so you won't lose anything) still.
I've been debating looking into it, but haven't yet for reasons above.
dejello said:
I don't have access (well, sort of but not really) to a g6 play. My son has one, but it's not unlocked or anything and I won't experiment on his phone without having everything backed up.... Besides, getting the damn thing away from him for extended periods when he isn't in trouble would be something.... I thing it's glued to his face or something.
I am also not up to date on any issues or reasons why twrp isn't official for the g6 play. Be aware that even this version for the g6 has some issues (workarounds are available for everything so you won't lose anything) still.
I've been debating looking into it, but haven't yet for reasons above.
Click to expand...
Click to collapse
I just had a good laugh about your son's g6 play being glued to his face ??I could definitely say I don't look at or use my phone as much as the kids now a days and I'm 27 lol I worked ina mall so I seen that alot lmao and what all would you need from someone to attempt an official twrp for it? Ill do my best to provide you with what's needed. The patched twrp for the g6 play should be a good start. I would have already started on it myself but i am not able to get it going because i don't trust my laptop (it came with Vista) and it likes to randomly reboot and all this marvelous stuff lol
ninjakira said:
I just had a good laugh about your son's g6 play being glued to his face ??I could definitely say I don't look at or use my phone as much as the kids now a days and I'm 27 lol I worked ina mall so I seen that alot lmao and what all would you need from someone to attempt an official twrp for it? Ill do my best to provide you with what's needed. The patched twrp for the g6 play should be a good start. I would have already started on it myself but i am not able to get it going because i don't trust my laptop (it came with Vista) and it likes to randomly reboot and all this marvelous stuff lol
Click to expand...
Click to collapse
When I get a chance I can take a look at some things. But looking at github I do see at least one device tree being worked on for jeter
ninjakira said:
I just had a good laugh about your son's g6 play being glued to his face [emoji23][emoji23]I could definitely say I don't look at or use my phone as much as the kids now a days and I'm 27 lol I worked ina mall so I seen that alot lmao and what all would you need from someone to attempt an official twrp for it? Ill do my best to provide you with what's needed. The patched twrp for the g6 play should be a good start. I would have already started on it myself but i am not able to get it going because i don't trust my laptop (it came with Vista) and it likes to randomly reboot and all this marvelous stuff lol
Click to expand...
Click to collapse
I wouldn't trust Windows either. Personally, I'd wipe Windows right off it and run Linux. Linux would breathe new life into a laptop that came with Vista lol.
Jleeblanch said:
I wouldn't trust Windows either. Personally, I'd wipe Windows right off it and run Linux. Linux would breathe new life into a laptop that came with Vista lol.
Click to expand...
Click to collapse
I do have it on dual boot with Ubuntu 18.10 it's Just the the random rebooting is persistent still but yeah I personally use use linux distos over Windows lol. My next paycheck I'm having our local computer store called microcenter help me out with a new laptop at least lol
dejello said:
When I get a chance I can take a look at some things. But looking at github I do see at least one device tree being worked on for jeter
Click to expand...
Click to collapse
I'm not able to send the screenshot of termux so here they are. Recovery is 16 mb
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*
*/
Hi,
here you can find my preview version of LineageOS 19.1 for our Samsung Galaxy Note 8.0 devices.
At first I want to thank @rINanDO and @ChronoMonochrome for all your work which helped me a lot.
This is a BETA build, also on the LineageOS side, so don't install it if you want a completley stable rom and don't report my already listet bugs!
Here you can see how far everything is working for now.
Spoiler: Whats working
Boot
Bluetooth
Audio
Graphics
Cameras
Sensors
Wifi
GPS
USB
Video playback (HW/SW)
Tethering via USB, WIFI and Bluetooth
consumerir transmitter
Stylus
RIL
much more...
Spoiler: Whats not working
Random reboots
Encryption
Maybe more
SD-Card can't be formatted as internal storage, this will cause a bootloop
Spoiler: Links
TWRP
N5100 ROM
N5110 ROM
N5120 ROM
ROM Mega
Magisk zip file
Spoiler: Changelog
26.10.2021
30.11.2021
29.12.2021
09.01.2022
14.02.2022
15.02.2022
18.02.2022
07.03.2022
10.03.2022
17.03.2022
25.03.2022
03.04.2022
12.04.2022
10.05.2022
26.06.2022
23.09.2022
25.01.2023
Spoiler: Don't like my boot picture?
If you don't like it, reboot into recovery and type the following command:
adb shell (or use TWRP's terminal)
bash /data/param_restore.sh
reboot
Uploaded a prepared package to build your own boot picture
download
I would recommend to use microG (much faster experience) or open Gapps as soon they are available.
Do you like my work?
Than you can simply hit the thanks button and consider to spend me a coffee or a beer,
I'm doing this in my free time and it also costs a lot of money to buy hardware.
donate
Wanna improve your sound configs, control your charging current and more?
Now you can use my app to access all boeffla configurations, there will follow more functions.
Exynos4 Kernel Manager - Apps on Google Play
This app provides Boeffla sound control and other kernel + charging tweaks
play.google.com
Spoiler: How to install it?
Instructions
Spoiler: microG instructions
Download Magisk 24.1 and flash it via TWRP (yes, flash the APK file), reboot
Open Magisk and update the App (and do a reboot if it's asking)
Enable Zygisk in Magisk
Download and install microG installer in the Magisk manager, reboot
Download and install safetynet-fix in the Magisk manager, reboot
Check with a safetynet checker app and you should pass
XDA:DevDB Information
[ROM][12.x][N5100/N5110/N5120][BETA] LineageOS 19.1, ROM for the Samsung Galaxy Note 8.0
Contributors
html6405
Source Code: https://github.com/html6405
ROM OS Version: 12.x S
ROM Kernel: Linux 3.x
ROM Firmware Required: TWRP 3.5.2
Based On: LineageOS
Selinux: permissive, this only makes sense as soon the ROM is stable.
Version Information
Status: Beta
Created 2021-11-25
Last Updated 2023-01-25
Update 26.11.2021:
N5120: fixed deep sleep bug
fixed sw decoder issue
This update comes via OTA and don't forget, if you're using BitGapps,
reflash them manually after the flash, otherwise you will face a bootloop...
html6405 said:
Update 26.11.2021:
N5120: fixed deep sleep bug
Click to expand...
Click to collapse
Congrats on getting 19.0 up and running! I did notice the initial build had no deep sleep and I was going to report it, but I see you have resolved it now. Which commit on your github fixed the deep sleep? I want to know for learning purposes. NO RUSH for an answer. Thank you.
html6405N5100 (The firmware does not start)
retiredtab said:
Congrats on getting 19.0 up and running! I did notice the initial build had no deep sleep and I was going to report it, but I see you have resolved it now. Which commit on your github fixed the deep sleep? I want to know for learning purposes. NO RUSH for an answer. Thank you.
Click to expand...
Click to collapse
I will push the commit next week.
But it's only a temporyary solution, because of the not working ril so far, there's no deep sleep.
When we remove the radio entries in the device manifest the device will deep sleep.
The real solution will be to find a way of fixing the RIL on A12.
XdaFoxygen said:
html6405N5100 (The firmware does not start)
Click to expand...
Click to collapse
On my n5100 it run's very well, did you install the ROM clean, are you just facing a bootloop?
html6405 said:
On my n5100 it run's very well, did you install the ROM clean, are you just facing a bootloop?
Click to expand...
Click to collapse
Yes, I ran into the Samsung logo hanging on it.
Accidentally the firmware is not for the project treble?
XdaFoxygen said:
Yes, I ran into the Samsung logo hanging on it.
Accidentally the firmware is not for the project treble?
Click to expand...
Click to collapse
You could try to reboot, sometimes it could be that the device doesn't start the first try,
maybe some kind of timing issue in the mounting process.
Treble is disabled at the moment.
html6405 said:
You could try to reboot, sometimes it could be that the device start's the first boot,
maybe some kind of timing issue in the mounting process.
Treble is disabled at the moment.
Click to expand...
Click to collapse
I'm trying to hang on the logo for about 10 minutes and it doesn't go any further ...
oh yes it started although it took a long time (firmware works)
Can I use Open GApps?
Can I install the version of Open GApps from android 11?
334k said:
Can I use Open GApps?
Can I install the version of Open GApps from android 11?
Click to expand...
Click to collapse
No, you have to use gapps made for Android 12.
Update 30.11.2021:
N5100 & N5110: fixed GPS (N5120 should already work)
Enable default power hal for all
This update comes via OTA and don't forget, if you're using BitGapps,
reflash them manually after the flash, otherwise you will face a bootloop...
html6405Thanks for the update, I'm waiting for you to fix everything else.
I watched the app zoom video backwards through the browser. Can't view, message video media player back aborted
Can I edit it to play?
(N5100,Excellent, Rom is very beautiful)
html6405 said:
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*
*/
Hi,
here you can find my preview version of LineageOS 19.0 for our Samsung Galaxy Note 8.0 devices.
At first I want to thank @rINanDO and @ChronoMonochrome for all your work which helped me a lot.
This is a early ALPHA build, also on the LineageOS side, so don't install it if you want a completley stable rom and don't report my already listet bugs!
When you have BitGapps installed, you have to reflash them after every update!
Here you can see how far everything is working for now.
Spoiler: Whats working
Boot
Bluetooth
Audio
Graphics
Cameras
Sensors
Wifi
GPS on N5120
USB
Video playback (HW/SW)
Tethering via USB, WIFI and Bluetooth
consumerir transmitter
Stylus with gestures and hovering icon
sec keyboard dock
RIL on N8000 (mobile connection)
much more...
Spoiler: Whats not working
Video recording with both cameras
GPS
N5120: RIL
Random reboots
Maybe more
SD-Card can't be formatted as internal storage, this will cause a bootloop
Spoiler: Links
TWRP
N5100 ROM
N5110 ROM
N5120 ROM
Magisk zip file
Spoiler: Changelog
26.10.2021
30.11.2021
Spoiler: Don't like my boot picture?
If you don't like it, reboot into recovery and type the following command:
adb shell (or use TWRP's terminal)
bash /data/param_restore.sh
reboot
Uploaded a prepared package to build your own boot picture
download
If you are going to use BitGapps,
here you can download them:
BitGapps, arm, 12
For the others, you can use microG in future.
If you plan to use a sim card in your device, I would recommend to disable the pin code before with another device.
In some cases the sim card becomes unusable while typing in the code.
Do you like my work?
Than you can simply hit the thanks button and consider to spend me a coffee or a beer,
I'm doing this in my free time and it also costs a lot of money to buy hardware.
donate
Spoiler: How to install it?
Instructions
XDA:DevDB Information
[ROM][12.x][N5100/N5110/N5120][BETA] LineageOS 19.0, ROM for the Samsung Galaxy Note 8.0
Contributors
html6405
Source Code: https://github.com/html6405
ROM OS Version: 12.x R
ROM Kernel: Linux 3.x
ROM Firmware Required: TWRP 3.5.2
Based On: LineageOS
Selinux: permissive, this only makes sense as soon the ROM is stable.
Version Information
Status: Alpha
Created 2021-11-25
Last Updated 2021-11-30
Click to expand...
Click to collapse
Is it a good idea trying to flash the device firmware with your costume ROM
Update 29.12.2021:
Synched with latest LineageOS sources
Signed with dev keys (removes the "signed with public keys" warning)
N5120: Fixed RIL, untested by me, because I don't have my device here, would be great if someone could test and report
N5120: It could be that gps crashes with this version, I would recommend to disable it until next build
Made some fixes for encryption ( but still not finished )
Created workaround to fix shutdown / reboot behaviour with Magisk
Fixed video recording with camera's
Fixed Torch (flashlight)
Fixed hardware button gestures control
Fixed GPS week rollover issue
Set swappiness to 60
Can I run it on a GT-N5105?
ertuncb said:
Can I run it on a GT-N5105?
Click to expand...
Click to collapse
Yes, the n5100 version should be compatible.
html6405 said:
Yes, the n5100 version should be compatible.
Click to expand...
Click to collapse
Flashed the lineage-19.0-20211229-HTML6405-n5100.zip. I've been waiting for 30 minutes with the text 'Samsung GALAXY Note 8.0 GT-N5105' on my screen. Any guesses on how long the first boot might take?
ertuncb said:
Flashed the lineage-19.0-20211229-HTML6405-n5100.zip. I've been waiting for 30 minutes with the text 'Samsung GALAXY Note 8.0 GT-N5105' on my screen. Any guesses on how long the first boot might take?
Click to expand...
Click to collapse
Tired of waiting and restarted by holding down the power button. The animation of LineageOS on initial setup appeared for a short while, then the system booted up. However, while trying to enter the settings and adjust the wireless network settings, the system shut down by itself and booted to TWRP. I've rebooted again and now the see the same boot screen text but with "xdadeveloper html640" in the last two lines. Still waiting, nothing happens. Any suggestions? (In between, I also cleaned dalvik cache and data)
AOSP 13
This is a moto-common project release under the codename borneo
Code:
/*
* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...).
* 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 me for messing up your device, I will laugh at you.
* Your warranty will be void if you tamper with any part of your device / software.
* Same statement for XDA.
*/
What's Moto-Common?
Moto-Common is a set of trees common to every 4.14+ QCOM Motorola device, making it easier to do bringups based on SODP.
What's AOSP?
AOSP is Android as Google publish without other modifications.
Known issues:
You tell me
IF YOU DONT HAVE SLOT B FILLED YOU CAN BRICK
Instructions :
Download the latest build
Reboot to bootloader
Code:
fastboot -w
Code:
fastboot update PACKAGE.zip
You may need to install drivers in device manager after running the last command
Downloads :
Download
Telegram Groups
My chat
Source Code:
https://github.com/moto-common
Changelog:
Jan 25th 2023: Initial release on XDA
Feb 27th 2023: Pushed Feb update
June 19th 2023: Pushed June patch update
Fix fingerprint gestures for egis
Fix color mode listings
Fix aux cameras
Improve memory management
Improve Wi-Fi 5GHz strength
Numerous other changes
Hi I recently installed this as its the only ROM currently available for my phone that I've seen, and I'm just wondering how would someone go about installing gapps?
DefinitelyDetermined said:
Hi I recently installed this as its the only ROM currently available for my phone that I've seen, and I'm just wondering how would someone go about installing gapps?
Click to expand...
Click to collapse
I have no idea , I just build to provide a base for others to work off of mostly.
DefinitelyDetermined said:
Hi I recently installed this as its the only ROM currently available for my phone that I've seen, and I'm just wondering how would someone go about installing gapps?
Click to expand...
Click to collapse
@Electimon
See the following links:
- https://stackoverflow.com/questions/71001696/how-to-include-opengapps-in-aosp-12-build
Use tau instead of sigma for aosp-13 (in the notes at bottom checked answer)\
- https://github.com/opengapps/aosp_build
- https://www.droidwin.com/how-to-download-and-install-android-13-gapps/
Note: Requires a working TWRP
Does this rom bring unlimited google photos???
sdembiske said:
@Electimon
See the following links:
- https://stackoverflow.com/questions/71001696/how-to-include-opengapps-in-aosp-12-build
Use tau instead of sigma for aosp-13 (in the notes at bottom checked answer)\
- https://github.com/opengapps/aosp_build
- https://www.droidwin.com/how-to-download-and-install-android-13-gapps/
Note: Requires a working TWRP
Click to expand...
Click to collapse
Would an outdated twrp version work? There is an unofficial one for Android 11
@Electimon Do you know anything about "range restricted" in Firehose loaders for EDL?
It prevents you from reading (and probably writing?) most partitions in EDL.
If your CID is 0xff or if you have a flag set (which I haven't traced down yet) you can bypass the restriction.
Renate said:
@Electimon Do you know anything about "range restricted" in Firehose loaders for EDL?
It prevents you from reading (and probably writing?) most partitions in EDL.
If your CID is 0xff or if you have a flag set (which I haven't traced down yet) you can bypass the restriction.
Click to expand...
Click to collapse
Yeah thats known, sadly CID partition is signed and the flag is usually burned qfuse in the SoC which is burnt on all retail devices.
Electimon said:
... the flag is usually burned qfuse ...
Click to expand...
Click to collapse
I'm using the Firehose loader size=609,484, MD5=153a904c54963cb21b901b0dd10f0641
I can see that the CID is validated by cert chains.
But I also see lots of stuff like "ssm_flash_cid", "write_cid_store".
I see a bunch of smc (Secure Monitor Calls) and a bunch of SCM (Secure Channel Monitor) calls and functions for reading/writing fuses.
I also see one small function that writes a byte into memory that can disable restrictions.
It seems like a back door, but I haven't seen what activates it.
Would it be possible to use this device tree to make a pixel experience port?
LethalGamer2121 said:
Would it be possible to use this device tree to make a pixel experience port?
Click to expand...
Click to collapse
Yes
Feb 27th 2023: Pushed Feb update
Electimon said:
Feb 27th 2023: Pushed Feb update
Click to expand...
Click to collapse
sound isnt working after update. it started working after i downgraded to the jan release
DefinitelyDetermined said:
sound isnt working after update. it started working after i downgraded to the jan release
Click to expand...
Click to collapse
Thank you for letting me know, it will be fixed soon
DefinitelyDetermined said:
sound isnt working after update. it started working after i downgraded to the jan release
Click to expand...
Click to collapse
Please redownload the same link, ive updated it with the fixed package. Thank you
having an issue where I cant flash it, its saying that it cannot flash
>fastboot update aosp_borneo-img-Feb-Week4.zip-------------------------------- - Pastebin.com
Pastebin.com is the number one paste tool since 2002. Pastebin is a website where you can store text online for a set period of time.
pastebin.com
if you want to reach out to me quickly, DM me on discord, Merith#5829
merith-tk said:
having an issue where I cant flash it, its saying that it cannot flash
>fastboot update aosp_borneo-img-Feb-Week4.zip-------------------------------- - Pastebin.com
Pastebin.com is the number one paste tool since 2002. Pastebin is a website where you can store text online for a set period of time.
pastebin.com
if you want to reach out to me quickly, DM me on discord, Merith#5829
Click to expand...
Click to collapse
Use platform-tools r32, in the latest version google broke fastboot update.
Electimon said:
Use platform-tools r32, in the latest version google broke fastboot update.
Click to expand...
Click to collapse
Small problem, phone has fastbootd, bootloader, recovery, and system (system being rom)
when you tell the phone to boot to fastboot, it goes to fastbootd which does not show up in fastboot.exe's list,
but if I send it to bootloader, it shows up
Edit, Updating drivers fixed it, IOBit Driver notified of out of date driver
Electimon said:
Use platform-tools r32, in the latest version google broke fastboot update.
Click to expand...
Click to collapse
Still broken, just differently
It flashed, rebooted, showed the AOSP android boot animation, rebooted then brought me to stock recovery (TWRP not flashed) saying the system was corrupt and could not boot
Reflashing fixed it but I dont have Cell Service (I have an carrier unlocked device on USC network)
merith-tk said:
Still broken, just differently
It flashed, rebooted, showed the AOSP android boot animation, rebooted then brought me to stock recovery (TWRP not flashed) saying the system was corrupt and could not boot
Reflashing fixed it but I dont have Cell Service (I have an carrier unlocked device on USC network)
Click to expand...
Click to collapse
Wipe data in recovery and let me know if its still an issue