[ROM][10] crDroid 6.27 [begonia/begoniain][OFFICIAL][FINAL] - Redmi Note 8 Pro ROMs, Kernels, Recoveries, & Othe

[ROM][10] crDroid 6.27 [begonia/begoniain][OFFICIAL][FINAL] - Redmi Note 8 Pro ROMs, Kernels, Recoveries, & Othe

{
"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:
*** Disclaimer
I am not responsible for any damage you made to your device
You have been warned
crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features existent today
Features:
https://github.com/crdroidandroid/crdroid_features/blob/10.0/README.mkdn
Instructions:
First time installation:
Carry out the necessary measures to unlock the bootloader.
Connect the phone to the PC with the supplied cord.
Transfer all valuable data from your phone's internal memory to PC. If you make a backup, then the folder with the backup (except if the backup is located on microSD).
Reboot into Fastboot mode (see the header in the F.A.Q. for how to enter it)
Download and unpack on your PC >> this << archive.
In the unpacked archive, go to the folder with your device type (if you have an Indian phone, then in [begoniain], all others in [begonia].
Run !_FLASH_IT_W.bat on Windows or !_FLASH_IT_L.sh on Linux (DO NOT CHANGE THESE SCRIPTS UNLESS YOU WANT TO GET A BRICK!!!)
If something went wrong, check if ADB drivers are installed on Windows, or fastboot packages on Linux.
The necessary images will be flashed and erased, etc., after which the phone itself will reboot into TWRP recovery.
Make the format Data (section Wipe / Wipe, click the Format Data button, then enter "Yes").
Reboot from TWRP to TWRP
Make sure your phone's internal memory is opened in TWRP mode on your PC.
Before starting the ROM installation, it is recommended to take measures to unlock the bootloader and save the critical sections of the phone.
Download and place the archive with the firmware in the internal memory of the phone, as well as Google Apps, if you need them.
Do a Wipe/Cleanup of the "system", "vendor", "cache" and "Dalvik|Art Cache" partitions.
Click Installation / Install and select the archive with the firmware, then click the Add / Add button and select the archive with Google Apps, everything else will be installed and updated automatically.
After installation, reboot again from TWRP to TWRP
Make the format Data (section Wipe / Wipe, click the Format Data button, then enter "Yes").
Reboot into the system and wait for initialization, usually 10 minutes is enough, if the download still fails, reboot forcibly into recovery (long hold volume up + on) and repeat the Format Data operation
After booting the system, perform the initial setup, and then reboot.
TWRP installation:
Before starting the ROM installation, it is recommended to take measures to unlock the bootloader and save the critical sections of the phone.
Save important data, photos, and more.
Download and place the archive with the firmware in the internal memory of the phone, as well as Google Apps if you need them.
Reboot into TWRP if you're not already there (reboot by holding the volume up button).
Wipe/Cleanup the "system", "vendor", "cache" and "Dalvik|Art Cache" partitions.
Click Install/Install and select the firmware archive, then click the Add/Add button and select the Google Apps archive, everything else will be installed and updated automatically.
After installation, reboot from TWRP to TWRP
Do data formatting (section Wipe / Wipe, click the Format Data button, then enter "Yes").
Reboot into the system and wait for initialization, usually 10 minutes is enough, if the download still fails, reboot forcibly into recovery (long hold volume up + on) and repeat the Format Data operation
Once the system has booted, perform the initial setup and then reboot.
Update installation:
USE THESE INSTRUCTION ONLY FOR UPDATING FROM MY PREVIOUS BUILD TO A NEW !!!
Make backups.
Download and place the ROM to the internal memory of the phone
(I do not recommend SD cards, often phones fail because they turn out to be broken)
Reboot in TWRP (vol+ with power button)
Click on Install menu and chose this ROM
After installation click on "Wipe Art/Dalvic" button
Reboot to system
If you have a bootloop, make Format Data in TWRP (all data will be erased).
Rollback to the factory firmware:
Download and unpack any MIUI Fastboot version ROM for begonia or begoniain
Reboot to Fastboot mode (vol- or vol+ with power button)
Run flash_all.bat on Windows or flash_all.sh on Linux
DO NOT USE OTHER ROLLING METHODS IF YOU DO NOT WANT TO GET BRICK !!!
Sources:
ROM: https://github.com/crdroidandroid
Device: https://github.com/TTTT555/device_xiaomi_begonia
Kernel: https://github.com/TTTT555/kernel_xiaomi_begonia
Special thanks:
@FancyPants
@yourdaddy907
@android_lover
@ZIDAN44
@Xakep1993
And other Begonia development team members
Visit official website @ crDroid.net
crDroid Community Telegram
crDroid Device Telegram (links to donations to the author here)
Donate to help crDroid team pay server costs.
XDA:DevDB Information
crDroid, ROM for the Redmi Note 8 Pro
Contributors
TTTT555
ROM OS Version: Android 10
Based On: LineageOS & POTATO project
Version Information
Status: Stable, Final, EOL
Created 2020-06-29
Last Updated 2022-10-19

Build type: Final (EOL)
Support chat (TG): https://t.me/crDroidBegonia
Notes:
- Recomended install fastboot version of MIUI A10 before.
- If you have bootloop after installation, try format data again or to change GAPPS or flash MIUI and try again.
- Reboot after a clean install and initial setup so that the BegoniaParts item appears in the settings.
- GAPPS and Google Photo required for G-Cams. Opengapps recomended [ARM64 Pico or Nano (for OK Google)].
- If you will use Viper FX, then do not forget to enable legacy mode in the application settings.
- If you will use the built-in G-Cams, do not forget to apply configs (three taps between the camshot button and gallery button). If the camera does not find the built-in configs, just reboot the device and try again.
- If you OFF James DSP after ON, reenable Dirac (OFF/ON), if you need it.
- If you OFF G-cam 64 after ON, reboot the device, otherwise bugs are possible.
- ANX cam: If you have problems with a wide angle camera - just turn off the lens distortion correction function, or set the mode to 9/16.
- If you have sound crackles, try ON OFF James DSP.
- You can find additional kernels in the support chat (with ALMK, reduced voltage etc.)
===== 19 October, 2022 =====
- BegoniaParts updates
- Media and audio fixes for game streamers
- Game performance improvements
- Kernel switched to SLMK by default
===== 05 January, 2022 =====
- Fixed playing of system sounds, incl. ringtones.
- The config for the built-in Gcam is now also loaded after format data.
- Fixed definition of wide-angle camera.
BegoniaParts:
- Added additional performance profiles
- Added codec switcher
- Added 80MHz Wi-Fi range switch
- Added Force 64MP switch
- Added V-Sync switch
- Added switch for debug.sf.latch_unsignaled
- Added switch to disable HW overlays
===== 31 December, 2021 =====
- Updates are now downloaded to /sdcard (default folder by TWRP)
- Fixed flickering in Night mode
- Added advanced Night Mode adjustment values
- Wi-Fi Display for non-Chromecast devices
- Fix TTL for advanced operators like red
- Added GCam Mod Burial 8 (the best in terms of color rendition at the moment), the configuration file is unpacked into internal memory, you just need to activate it in the camera
- Unification of Keymaster and TWRP with MIUI
- Additional codecs from MTK
- Integrated Dirac effect instead MiSound
- Changed amplifier mode for external speaker
- Fixes for SafetyNet
- Vertical sync is activated and parameters are selected for better responsiveness of the interface
- Fixed the volume of incoming calls in the headset and small speaker (a script has been written to recalculate the volume levels during a phone call, in the firmware settings you can select up to 60 levels)
- Another tuning ZRAM
- Added new Sepolicy rules
- The installation archive integrates firmwares for the Global and Indian versions of the phone, together with TWRP
- Updated factory libraries and added for a new type of frontal camera, as well as added sound libraries from newer MTK devices
- Thermo profiles from the Indian version of the phone
- Removed Sta2gBw 1 from /vendor/firmware/wifi.cfg which can cause problems (set manually to whoever needs it)
- And many other subtle improvements and additions
Kernel:
- Added driver for new frontal camera
- Enabled KSM support by default
- Added an engine for adjusting the strength of vibration
- Added new schedulers and "sioplus" selected by default
/ Thanks to 7Soldier for help with some features /
BegoniaParts settings app:
- MiSound -> Dirac Sound
- Added performance profiles by adjusting the Schedutil governor downrate (you can edit the parameters yourself or add new ones in the files /vendor/bin/xiaomiparts.sh (chmod 0755) and /vendor/etc/init/hw/init.xiaomi_parts.rc (chmod 0644 )
- Choice of TCP Congestion Algorithm
- FPS sensor
- Additional wake-up gestures
- Vibration strength adjustment

first time installation instructions for miui users or both miui and cfw custom rom users?

adil_muhmd said:
first time installation instructions for miui users or both miui and cfw custom rom users?
Click to expand...
Click to collapse
cfw users may can start by installing the archive (with next wipes, and format data if it was encrypted)

I installed myself, the firmware fire installation is real in 2 clicks).

Sir,
what is HCE mode?

keiyrno said:
Sir,
what is HCE mode?
Click to expand...
Click to collapse
HCE - Android cloud storage technology for card data, with temporary pay tokens on phone, used by G-Pay, etc.
There is also data storage inside the NFC chip - SE (secure element), which can also be used to store e-sim data

TTTT555 said:
HCE - Android cloud storage technology for card data, with temporary pay tokens on phone, used by G-Pay, etc.
There is also data storage inside the NFC chip - SE (secure element), which can also be used to store e-sim data
Click to expand...
Click to collapse
thank you for your explanation sir

Yayy thanks TTTT555 for AOSP

@TTTT555
When using QS- "night light". The screen will flash at a fixed frequency, there seems to be some problems.?
anyway, advance THANKS, Its very very good Begonia ROM!:good::good:

2 buttons navbar gesture error/bug: gesture for recents and chang into open apps. Overall amazing ROM, I love open source plus its lighter for download.

Anyone knows how to solve this? Anytime I restart my phone, I get a notification that my security has been weakened.

eocobby721 said:
Anyone knows how to solve this? Anytime I restart my phone, I get a notification that my security has been weakened.
Click to expand...
Click to collapse
I guess its related with permissive kernel, or disabled SELinux...

KonahZave said:
I guess its related with permissive kernel, or disabled SELinux...
Click to expand...
Click to collapse
Yes it is. Any way to fix that?

eocobby721 said:
Yes it is. Any way to fix that?
Click to expand...
Click to collapse
oooh yeah its you CObby only now I noticed your nick, well anyway I dont know sorry :crying:

KonahZave said:
oooh yeah its you CObby only now I noticed your nick, well anyway I dont know sorry :crying:
Click to expand...
Click to collapse
I was waiting to see if you notice :laugh:
Thanks.

I'm also having lots of reboots with the fingerprint sensor. Looks like it's much slower than the standard one, and you need to keep your finger still for much longer.

@TTTT555 , did you disable the secure element due to the spiread_dma error?

eocobby721 said:
Yes it is. Any way to fix that?
Click to expand...
Click to collapse
Later, but now you may off notice in /Settings/Security/Trust
u8ububu said:
@TTTT555 , did you disable the secure element due to the spiread_dma error?
Click to expand...
Click to collapse
nope, it is not related to this and will be fixed soon
e45cream said:
I'm also having lots of reboots with the fingerprint sensor. Looks like it's much slower than the standard one, and you need to keep your finger still for much longer.
Click to expand...
Click to collapse
you're out of luck, your phone is from a problematic series with a fingerprint for custom firmwares, but we are working on it

Thanks Sir

Related

[ROM][UNOFFICIAL][7.1.2] LineageOS 14.1 [trlte][trlteduos]

Code:
* [B][U]Your warranty is now void.[/U][/B]
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or your 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.
FREQUENTLY ASKED QUESTIONS
(Please read them BEFORE posting anything in the thread!)Q: When will any of the variants receive official builds from LineageOS?
A: Not before all the issues listed under "Bugs" below are fixed.
Note to Junior Members: It is frowned upon in the XDA community to ask for ETA's on builds, features, bug fixes, or other improvements to the code or its functionality.
Q: What will some of the differences be between unofficial and official builds?
A: The following technical changes will take effect:
- Built-in su root will be removed: You will have to download and install the su addon from LineageOS Extras.
- Phone status > LineageOS updates will be activated, allowing for the OTA downloading of official builds.
- The official builds will be digitally signed by Lineage to prove that they do not contain malicious source code and are able to pass the Play Store's SafetyNet check.
Note: Each official build will be cooked and released by LineageOS on their schedule and only if no major unexpected bug is introduced into the source code. The developers will announce if and when their source code will be submitted to Lineage for official support and when we can expect to see the first official builds.
Q: Why is my phone warmer/hotter and the battery noticeably drained after flashing a build?
A: The wipe process that is a part of the installation procedure deletes some important configuration data, ie. BATTERYSTATS, which keep track of the battery's power level. These data ensure a balanced power management profile for all the hardware components of your phone. This is normal and nothing to worry about at all. Your battery drain will return to normal within a day or two.
If, however, you notice increased battery drain over a few days, check your signal. Android automatically re-directs battery power to the antennas to compensate for a weak signal from the tower to which your phone is connected at that time. If your signal is strong, check the following:
1) You missed one of the Wipe steps in the flashing procedure.
2) You are running an old bootloader or modem. Flash the most recent one listed for your variant either under the links below. Note: Use the "AP" button in Odin to flash ripee's combined BL_CP tar files.
3) How old is your battery? Official replacement Samsung batteries typically last around 1 year if you recharge them regularly, ie. once a day. Since the Note 4 is almost 3 years old, it is normal for your original battery to start failing, but official Samsung batteries should not cost more than USD 20 nowadays.
4) If all else fails, start over! Go through the entire installation procedure, including flashing a stock Marshmallow build, and going from there. Do NOT skip any steps this time!
Q. Flashing a build failed with the message "eMMC Write Fail".
A. This is the infamous embedded Multi-Media Controller bug that indicates that your internal flash memory is dead or dying. Do NOT try any tricks or crazy ideas to fix it, as they are all hoaxes! The ONLY way to get rid of it is to open your phone up and replace its logic board.
[Official] Note 4 Verizon Bootloader Unlock
- ryanbg
Odin
- Odin3 v3.13.1
Heimdall
- Glass Echidna
Bootloaders and modems
- ripee
TWRP
- SM-N910F/G/P/R4/T/T3/V/W8: trlte
- SM-N9100ZC/ZH/6W/9W: trlteduos
[THEME][TWRP] TWRP Materialised - Black / Dark / Light / Play [27/01/18]
- z31s1g
BasketBuild Downloader
- daktak
In the app's Settings, change Project to ripee and Device to trlte or trlteduos. Under Base Url, replace s with www.
ROMs
ripee (LineageOS su root included.)
- SM-N910F/G/P/R4/T/T3/V/W8: trlte
- SM-N9100ZC/ZH/6W/9W: trlteduos
_mone
- LineageOS
LineageOS Extras
- addonsu-14.1-arm-signed.zip
- addonsu-remove-14.1-arm-signed.zip
Magisk
OpenGapps Downloader
- daktak
Open GApps
- pico
Aroma-Extras
- Creeper36
The SELinux Switch
- Ibuprophen
SPenCommand
- It is against XDA Developers rules to post links to paid apps and games. Please find this app on your own if you wish to use it.
WipeTelephonyProviderData
- hsbadr
If your currently installed ROM is any version of either: stock Samsung TouchWiz, LineageOS 13.0, CyanogenMod, or any other custom ROM, you must perform a clean install of that LineageOS 14.1 variant, which corresponds to the model of your phone!
How to flash a bootloader and/or modem and TWRP1. If your phone is turned on normally, turn on Advanced reboot in Developer options and select "Download" from the Restart menu,
2. In Odin, import the bootloader.tar file with the "BL" button and the modem.tar file with the "CP" button, or a combined BL_CP.tar file with the "AP" button, for your variant,
3. Download the .tar file of the latest version of TWRP from the link above,
4. Reboot into Download mode again and import the TWRP .tar file with the "AP" button.
How to flash LineageOS, Open GApps, and Aroma-ExtrasFULL WIPE (with external microsd card)
1. Move any files you want to keep to your External MicroSD Card – ! Or you will lose them !
2. Download your LineageOS Rom and GApps Package,
3. Move your LineageOS Rom and GApps Package to the external microsd storage,
4. Boot into Recovery Mode (Hold volume up, Home, and Power button for 1 second after the vibration),
5. Wipe > Advanced Wipe > Select On (enable tick) for Dalvik / Art Cache, System, Data, Internal Storage, Cache,
6. Swipe to Wipe at Bottom of Screen,
7. Back to Main start screen,
8. Wipe > Format Data,
9. Type 'Yes' and press blue checkmark at the bottom-right corner,
10. Go Back to Main Start Screen to Install Rom and GApps and optionally Aroma-Extras,
11. After you have finished installing the Rom and GApps > Wipe Cache/Dalvik > Swipe to Wipe,
12. Reboot System! Enjoy!
FULL WIPE (without external microsd card with NO Home PC access)
1. Move any files you want to keep to a safe folder - ! Or you will lose them !
2. Download your LineageOS Rom and GApps Package,
3. Move your LineageOS Rom and GApps Package to the internal storage,
4. Boot into Recovery Mode (Hold volume up, Home, and Power button for 1 second after the vibration),
5. Wipe > Advanced Wipe > Select On (enable tick) for Dalvik / Art Cache, System, Data, Cache,
6. Swipe to Wipe at Bottom of Screen,
7. Back to Main start screen,
8. Wipe > Format Data,
9. Type 'Yes' and press blue checkmark at the bottom-right corner
10. Go Back to Main Start Screen to Install Rom and GApps and optionally Aroma-Extras,
11. After you have finished installing the Rom and GApps > Wipe Cache/Dalvik > Swipe to Wipe,
12. Reboot System! Enjoy!
FULL WIPE (without external microsd card with Home PC access)
1. Move any files you want to keep to your Home PC - ! Or you will lose them !
2. Download your LineageOS Rom and GApps Package,
3. Move your LineageOS Rom and GApps Package to the internal storage,
4. Boot into Recovery Mode (Hold volume up, Home, and Power button for 1 second after the vibrate),
5. Wipe > Advanced Wipe > Select On (enable tick) for Dalvik / Art Cache, System, Data, Internal Storage, Cache,
6. Swipe to Wipe at Bottom of Screen,
7. Back to Main start screen,
8. Wipe > Format Data,
9. Type 'Yes' and press blue checkmark at the bottom-right corner,
10. Go Back to Main Start Screen to Install Rom and GApps and optionally Aroma-Extras,
11. After you have finished installing the Rom and GApps > Wipe Cache/Dalvik > Swipe to Wipe,
12. Reboot System! Enjoy!
13. Once first boot is completed you can safely move your files back onto your Internal Storage.
How to install SPenCommand1. Install The SELinux Switch and Select SELinux mode as PERMISSIVE,
2. Reboot into System,
3. Install SPenCommand.
Typically if you do not do a Clean Install then you are not allowed to report errors or problems. If you Dirty Install and you do have problems then you will be asked to Wipe All and Clean Install and see if the problems still exist. This is a DAILY changing rom and any bug that you found was not working on the previous day's build may be fixed with todays daily build. On a side note, the code implemented to fix that bug could potentially break something that worked on that previous build. So reporting problems on a day old build that you dirty flashed over whichever build of whichever rom you had flashed previously will not be accepted as a true error.
Problems known to happen after a Dirty Installation
1. A muddled up mess of a system. You are taking a rom and installing a newer rom with changes over the top of your old rom. Between these two periods of time during which you used your phone and created data, changed system options, and used apps. This is absolutely increasing the risk of causing problems somewhere in the system/data partitions. Some people have luck with Dirty Flashing. However, it's always hit-and-miss because of what we mentioned above about bug fixes breaking previously working functions. Dirty flashing doesn't only create problems if the source code of the system data and the system settings of the new build are significantly different from those of your previous build. That's not to say that Clean Installing won't ever create problems, but only bugs present on a Cleanly Installed rom are relevant for development purposes.
* Clean Install: Fully wiping everything and installing the rom onto a fully clean system/data partition of the phone.
* Dirty Install: Installing the rom and GApps or Aroma-Extras over top of the older rom to save time and not have to reinstall all the user apps and tweaking system and app settings that usually take a lot of time to set up as you like.
Important information about stock S Pen functionality!The apps, libraries, and drivers that allow for the advanced S Pen-based functions in stock TouchWiz and TouchWiz-based custom roms WILL NEVER BE INCLUDED IN ANY AOSP-BASED ROMS due to their proprietary nature. The scope of these functions goes beyond simple vendor blobs and enters the realm of 3rd party intellectual property licensed to Samsung. The S Pen does work in all AOSP-based custom roms, however it acts simply as an alternative input device. Various open source 3rd party apps are available that take advantage of the Note 4's stylus (see above), but their functionality is a fraction of that of stock TouchWiz.
Bugs
- The fingerprint scanner works, but you have to go through the finger adding process twice for each finger!
- The built-in camera app is slow and crashes randomly, especially when the flash fires, requiring a reboot to function again.
- Video recording in 4K resolution is not possible with either the built-in camera app or any 3rd party camera/camcorder apps.
- 5GHz hotspot gives an error message when attempting to turn it on.
- If NFC is turned off when the phone is booted up, the NFC toggle will freeze in the "off" position and remain off until the phone is rebooted. If NFC is turned on when the phone is booted up, the NFC toggle will function properly to turn NFC both on and off. However, if NFC is turned off and the phone is rebooted, this bug will reappear.
- The 2nd SIM slot does not work in any trlteduos variant.
- VoLTE is not yet supported.
- You tell us!
Credits
- cvxda, jef_00, lilferraro, and every other open source developer and user who contributes directly or indirectly to the LineageOS community in the development of and in providing feedback for the trlte and trlteduos.
Sources
- _mone
- Corinna Vinschen
- fattire
- LineageOS
- ripee
- samsung-apq8084
XDA:DevDB Information
LineageOS 14.1 , ROM for the Samsung Galaxy Note 4
Contributors
jef_00, _mone, ripee, fattire
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
ROM Firmware Required: Stock Marshmallow for your variant.
Version Information
Status: Stable
Created 2017-04-13
Last Updated 2019-07-13

Reserved

Reserved

this build is special for @ripee
changelog:
fixed recent view borders

jef_00 said:
this build is special for @ripee
changelog:
fixed recent view borders
Click to expand...
Click to collapse
Thank you for the mention and of course for your hard work, @jef_00
I'll flash it tomorrow afternoon cuz I have an early morning tomorrow.

Does this work with the 910T? Any support for 10,000mAh battery?

ripee said:
Thank you for the mention and of course for your hard work, @jef_00
I'll flash it tomorrow afternoon cuz I have an early morning tomorrow.
Click to expand...
Click to collapse
No problem mate! @ripee

Rick7C2 said:
Does this work with the 910T? Any support for 10,000mAh battery?
Click to expand...
Click to collapse
Not yet sorry!

Can anyone make data for tmobile N4?
Sent from my SM-G935F using XDA-Developers Legacy app

@jef_00
_mone said:
Clone, fork, rebase, merge, do whatever you want with the repos, but please share it; we are here for that!
Click to expand...
Click to collapse
I don't mind if you copy/paste my thread but, please, add the links to the source that you're using.

Rick7C2 said:
Does this work with the 910T? Any support for 10,000mAh battery?
Click to expand...
Click to collapse
jef_00 said:
Not yet sorry!
Click to expand...
Click to collapse
Is that no on the 910T, or no on the 10 AH battery?
I have a 910T and would love to try this build.
Didn't the trltexx CM build work on the 910T?

I had some time to flash build 01/11. The recent tiles are definitely fixed!
I guess now attention can be turned to the fingerprint scanner?
I also noticed that the setting to have the display save power is missing from LiveDisplay, the one usually at the bottom of that submenu.
Thank you @jef_00!

_mone said:
@jef_00
I don't mind if you copy/paste my thread but, please, add the links to the source that you're using.
Click to expand...
Click to collapse
it is done sorry about copy/paste

Just flashed the ROM, wiped cache/dalvik cache and booted.
First impressions:
-Turning the screen on is quite slow like on all non-TouchWiz roms I've tried in the past compared to TW roms (I come from x-rom Note7 port rom). Unlike CM13 on the LG G2
I have no idea why no one talks about this. It takes around 1.4 seconds to show the lockscreen, around 40% more than stock roms.
-Low volume when listening to voice clip recorded by myself on Whatsapp from earpiece
-During the first 15 minutes with the phone I experienced constant freezings (3+ sec. duration) very often while scrolling anywhere. Settings app seems to stop responding too often, perhaps it's related to the freezings. However, right now as I'm writing this I don't seem to be experiencing them anymore...
-After using the phone for 30+ minutes the automatic rotation stops working (only works on camera app).
-Half the translation is in English instead of in Spanish some of which are erratic (Under Gestures: "Proximity wake up: wake up when shaking the phone". Those are two different things.)
- No way to set a different vibration intensity on capacitive buttons (too strong by default IMO).
-Duplicate contacts on DIALER APP (due to having contacts on whatsapp). Went to contacts app-->contacts to show--> set only Google contacts and they stop showing duplicated only on contact app, not on the dialer app. You did it again Google! I saw this stupid behavior back in CM13.
Things I liked/surprised me:
-Built-in option to disable home button from waking up the device.
-Show notifications (black and white screen, ideal for amoled screen phones) when uncovering proximity sensor.
-Speed in general.

The slow lock screen turning on isn't restricted to this rom, as you wrote.
You can link contacts together in the settings of each contact.
The rotation bug is well known throughout 14.1 aosp-based roms for all devices.

ripee said:
The slow lock screen turning on isn't restricted to this rom, as you wrote.
You can link contacts together in the settings of each contact.
The rotation bug is well known throughout 14.1 aosp-based roms for all devices.
Click to expand...
Click to collapse
What is it restricted to?
About the contacts...so if I have 1M contacts I have to spend my whole life doing that task? Haha.

aLexzkter said:
What is it restricted to?
About the contacts...so if I have 1M contacts I have to spend my whole life doing that task? Haha.
Click to expand...
Click to collapse
It's restricted to all 7.1.1 aosp roms.
Only for those who are in multiple accounts. I have 250 and I linked about 75 in total.

ripee said:
It's restricted to all 7.1.1 aosp roms.
Only for those who are in multiple accounts. I have 250 and I linked about 75 in total.
Click to expand...
Click to collapse
I experienced it on all 6.0.1 aosp roms too...

Tanks for this ROM!!!
jef_00 said:
this build is special for @ripee
changelog:
fixed recent view borders
Click to expand...
Click to collapse
Hi jef_00 ! Im back again to Test Your ROMs. Thanksf or this Build. (Sorry that I was a Longer Time "Out"). My PC was Totaly Damaged. So I cant Flash and Testing Your CM13 Builds. Now Im back.

SUREFACE said:
Hi jef_00 ! Im back again to Test Your ROMs. Thanksf or this Build. (Sorry that I was a Longer Time "Out"). My PC was Totaly Damaged. So I cant Flash and Testing Your CM13 Builds. Now Im back.
Click to expand...
Click to collapse
glad you are back!!

[ROM][UNOFFICIAL][8.1.0] LineageOS 15.1 [trlte][tblte][trlteduos]

Code:
* [B][U]Your warranty is now void.[/U][/B]
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or your 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.
FREQUENTLY ASKED QUESTIONS
(Please read them BEFORE posting anything in the thread!)Q: Whenever I try flashing any lineage-15.1 build, I get the following error in TWRP: Updater process ended with ERROR: 7
A: This error appears whenever you try to flash an Oreo-based rom within a version of TWRP older than 3.2. Simply flash the linked below version 3.2 or higher, reboot back into recovery, and flash the rom zip again.
Q: When will any of the variants receive official builds from LineageOS?
A: Not before all the issues listed under "Bugs" below are fixed.
Note to Junior Members: It is frowned upon in the XDA community to ask for ETA's on builds, features, bug fixes, or other improvements to the code or its functionality.
Q: What will some of the differences be between unofficial and official builds?
A: The following technical changes will take effect:
- Built-in su root will be removed: You will have to download and install the su addon from LineageOS Extras.
- Phone status > LineageOS updates will be activated, allowing for the OTA downloading of official builds.
- The official builds will be digitally signed by Lineage to prove that they do not contain malicious source code and are able to pass the Play Store's SafetyNet check.
Note: Each official build will be cooked and released by LineageOS on their schedule and only if no major unexpected bug is introduced into the source code. The developers will announce if and when their source code will be submitted to Lineage for official support and when we can expect to see the first official builds.
Q: Why is my phone warmer/hotter and the battery noticeably drained after flashing a build?
A: The wipe process that is a part of the installation procedure deletes some important configuration data, ie. BATTERYSTATS, which keep track of the battery's power level. These data ensure a balanced power management profile for all the hardware components of your phone. This is normal and nothing to worry about at all. Your battery drain will return to normal within a day or two.
If, however, you notice increased battery drain over a few days, check your signal. Android automatically re-directs battery power to the antennas to compensate for a weak signal from the tower to which your phone is connected at that time. If your signal is strong, check the following:
1) You missed one of the Wipe steps in the flashing procedure.
2) You are running an old bootloader or modem. Flash the most recent one listed for your variant either under the links below. Note: Use the "AP" button in Odin to flash ripee's combined BL_CP tar files.
3) How old is your battery? Official replacement Samsung batteries typically last around 1 year if you recharge them regularly, ie. once a day. Since the Note 4 is almost 4 years old, it is normal for your original battery to start failing, but official Samsung batteries should not cost more than USD 20 nowadays.
4) If all else fails, start over! Go through the entire installation procedure, including flashing a stock Marshmallow build, and going from there. Do NOT skip any steps this time!
Q. Flashing a build failed with the message "eMMC Write Fail".
A. This is the infamous embedded Multi-Media Controller bug that indicates that your internal flash memory is dead or dying. Do NOT try any tricks or crazy ideas to fix it, as they are all hoaxes! The ONLY way to get rid of it is to open your phone up and replace its logic board.
[Official] Note 4 Verizon Bootloader Unlock
- ryanbg
Odin
- Odin3 v3.13.1
Heimdall
- Glass Echidna
Bootloaders and modems
- ripee
TWRP for Samsung Galaxy Note 4 (Qualcomm)
[THEME][TWRP] TWRP Materialised - Black / Dark / Light / Play [27/01/18]
- z31s1g
Open GApps
OFFICIAL !!
I am not building for oreo anymore, devs have moved to pie,
thanks everyone !!
tripLr
Code:
LAST ROM Downloads for Oreo
triplr
Source Code http://www.github.com/tripLr
@kevintm78 kernel development
https://forum.xda-developers.com/note-4/snapdragon-dev/kernel-flashpoint-v3-1-stock-n7-ports-t-t3727407
(LineageOS su root included.)
ROMs Note 4
SM-N910F/G/P/R4/T/T3/V/W8:
click to open trlte drive folder
https://drive.google.com/drive/folders/1XWrdmxHeC0A7zGK-TGOH3XG2VfKYP-IA?usp=sharing
<build date>.zip <flashable zip>
<build date>.zip.md5sum <md5 checksum for build>
<build date>.zip.img <backup kernel image install image in twrp>
ROMs Note 4 Edge
Note 4 Edge Thanks to @micky387 and @ripee
Which device is supported ??
I'm do the best for support multi note edge device so tell me if you see an issue and write it here with you variant
Support SM-N915F SM-N915FY SM-N915G SM-N915T SM-N915P SM-N915V
Click to expand...
Click to collapse
Google Drive Download Folder Click to open and browse to latest
https://drive.google.com/drive/folders/1lD5vLRFYr8XyGIgL2oT9VXFmdcLOWe3F?usp=sharing
file names
<build date>.zip <flashable zip>
<build date>.zip.md5sum <md5 checksum for build>
<build date>.zip.img <backup kernel image install image in twrp>
ROMs Note 4 DUOS
- SM-N9100ZC/ZH/6W/9W:
click to open trlte duos folder
https://drive.google.com/drive/folders/1uibdRnVs9-klbJhtvB5__5B9XFYel1jK?usp=sharing
file names
<build date>.zip <flashable zip>
<build date>.zip.md5sum <md5 checksum for build>
<build date>.zip.img <backup kernel image install image in twrp>
Code:
# Depreciated
[B]ripee[/B] [I]([COLOR="Teal"]LineageOS[/COLOR] su root included.)[/I]
- SM-N910F/G/P/R4/T/T3/V/W8: [URL="https://forum.xda-developers.com/devdb/project/dl/?id=31259"][B]
lineage-15.1-20190218-UNOFFICIAL-trlte.zip[/B][/URL]
- SM-N9100ZC/ZH/6W/9W: [URL="https://forum.xda-developers.com/devdb/project/dl/?id=31260"][B]
lineage-15.1-20190218-UNOFFICIAL-trlteduos.zip[/B][/URL]
[B]_mone[/B]
- [URL="https://androidfilehost.com/?w=files&flid=140308&sort_by=date&sort_dir=DESC"][B]LineageOS[/B][/URL]
[B]micky387[/B]
- SM-N910F/G/P/R4/T/T3/V/W8: [URL="https://androidfilehost.com/?w=files&flid=257279&sort_by=date&sort_dir=DESC"][B]Note 4[/B][/URL]
[/CODE]LineageOS Extras
- addonsu-15.1-arm-signed.zip
- addonsu-remove-15.1-arm-signed.zip
Magisk
The SELinux Switch
- Ibuprophen
SPenCommand
- It is against XDA Developers rules to post links to paid apps and games. Please find this app on your own if you wish to use it.
WipeTelephonyProviderData
- hsbadr
If your currently installed ROM is any version of either: stock Samsung TouchWiz, LineageOS, CyanogenMod, or any other custom ROM, you must perform a clean install of that LineageOS 15.1 variant, which corresponds to the model of your phone!
How to flash a bootloader and/or modem and TWRP1. If your phone is turned on normally, turn on Advanced reboot in Developer options and select "Download" from the Restart menu,
2. In Odin, import the bootloader.tar file with the "BL" button and the modem.tar file with the "CP" button, or a combined BL_CP.tar file with the "AP" button, for your variant,
3. Download the .tar file of the latest version of TWRP from the link above,
4. Reboot into Download mode again and import the TWRP .tar file with the "AP" button.
How to flash LineageOS and Open GAppsFULL WIPE (with external microsd card)
1. Move any files you want to keep to your External MicroSD Card – ! Or you will lose them !
2. Download your LineageOS Rom and GApps Package,
3. Move your LineageOS Rom and GApps Package to the external MicroSD storage,
4. Boot into Recovery Mode (Hold volume up, Home, and Power button for 1 second after the vibration),
5. Wipe > Advanced Wipe > Select On (enable tick) for Dalvik / Art Cache, System, Data, Internal Storage, Cache,
6. Swipe to Wipe at Bottom of Screen,
7. Back to Main start screen,
8. Wipe > Format Data,
9. Type 'Yes' and press blue checkmark at the bottom-right corner,
10. Go Back to Main Start Screen to Install Rom and GApps,
11. After you have finished installing the Rom and GApps > Wipe Cache/Dalvik > Swipe to Wipe,
12. Reboot System! Enjoy!
FULL WIPE (without external microsd card with NO Home PC access)
1. Move any files you want to keep to a safe folder - ! Or you will lose them !
2. Download your LineageOS Rom and GApps Package,
3. Move your LineageOS Rom and GApps Package to the internal storage,
4. Boot into Recovery Mode (Hold volume up, Home, and Power button for 1 second after the vibration),
5. Wipe > Advanced Wipe > Select On (enable tick) for Dalvik / Art Cache, System, Data, Cache,
6. Swipe to Wipe at Bottom of Screen,
7. Back to Main start screen,
8. Wipe > Format Data,
9. Type 'Yes' and press blue checkmark at the bottom-right corner
10. Go Back to Main Start Screen to Install Rom and GApps,
11. After you have finished installing the Rom and GApps > Wipe Cache/Dalvik > Swipe to Wipe,
12. Reboot System! Enjoy!
FULL WIPE (without external microsd card with Home PC access)
1. Move any files you want to keep to your Home PC - ! Or you will lose them !
2. Download your LineageOS Rom and GApps Package,
3. Move your LineageOS Rom and GApps Package to the internal storage,
4. Boot into Recovery Mode (Hold volume up, Home, and Power button for 1 second after the vibrate),
5. Wipe > Advanced Wipe > Select On (enable tick) for Dalvik / Art Cache, System, Data, Internal Storage, Cache,
6. Swipe to Wipe at Bottom of Screen,
7. Back to Main start screen,
8. Wipe > Format Data,
9. Type 'Yes' and press blue checkmark at the bottom-right corner,
10. Go Back to Main Start Screen to Install Rom and GApps,
11. After you have finished installing the Rom and GApps > Wipe Cache/Dalvik > Swipe to Wipe,
12. Reboot System! Enjoy!
13. Once first boot is completed you can safely move your files back onto your Internal Storage.
Important information about stock S Pen functionality!The apps, libraries, and drivers that allow for the advanced S Pen-based functions in stock TouchWiz and TouchWiz-based custom roms WILL NEVER BE INCLUDED IN ANY AOSP-BASED ROMS due to their proprietary nature. The scope of these functions goes beyond simple vendor blobs and enters the realm of 3rd party intellectual property licensed to Samsung. The S Pen does work in all AOSP-based custom roms, however it acts simply as an alternative input device. Various open source 3rd party apps are available that take advantage of the Note 4's stylus (see above), but their functionality is a fraction of that of stock TouchWiz.
How to install SPenCommand1. Install The SELinux Switch and Select SELinux mode as PERMISSIVE,
2. Reboot into System,
3. Install SPenCommand.
Typically if you do not do a Clean Install then you are not allowed to report errors or problems. If you Dirty Install and you do have problems then you will be asked to Wipe All and Clean Install and see if the problems still exist. This is a DAILY changing rom and any bug that you found was not working on the previous day's build may be fixed with todays daily build. On a side note, the code implemented to fix that bug could potentially break something that worked on that previous build. So reporting problems on a day old build that you dirty flashed over whichever build of whichever rom you had flashed previously will not be accepted as a true error.
Problems known to happen after a Dirty Installation1. A muddled up mess of a system. You are taking a rom and installing a newer rom with changes over the top of your old rom. Between these two periods of time during which you used your phone and created data, changed system options, and used apps. This is absolutely increasing the risk of causing problems somewhere in the system/data partitions. Some people have luck with Dirty Flashing. However, it's always hit-and-miss because of what we mentioned above about bug fixes breaking previously working functions. Dirty flashing doesn't only create problems if the source code of the system data and the system settings of the new build are significantly different from those of your previous build. That's not to say that Clean Installing won't ever create problems, but only bugs present on a Cleanly Installed rom are relevant for development purposes.
* Clean Install: Fully wiping everything and installing the rom onto a fully clean system/data partition of the phone.
* Dirty Install: Installing the rom and GApps over top of the older rom to save time and not have to reinstall all the user apps and tweaking system and app settings that usually take a lot of time to set up as you like.
Bugs
- Temporary fix for random SIM death on all trlte variants, courtesy of _mone: boot-1223-trlte.img
- The fingerprint scanner has not yet been integrated into either trlte or trlteduos.
- The front camera force closes, requiring a reboot to work again.
- Bluetooth does not see some wearable devices.
- The built-in camera app is slow and crashes randomly, especially when the flash fires, requiring a reboot to function again.
- Video recording in 4K resolution is not possible with either the built-in camera app or any 3rd party camera/camcorder apps.
- 5GHz hotspot gives an error message when attempting to turn it on.
- If NFC is turned off when the phone is booted up, the NFC toggle will freeze in the "off" position and remain off until the phone is rebooted. If NFC is turned on when the phone is booted up, the NFC toggle will function properly to turn NFC both on and off. However, if NFC is turned off and the phone is rebooted, this bug will reappear.
- The 2nd SIM slot does not work in any trlteduos variant.
- VoLTE is not (yet) supported.
- You tell us!
Changelog
All major features and bug fixes are discussed in detail by the developers in the thread, whenever they are implemented. All builds include the latest upstream Changes for all devices from LineageOS.
Credits
- fattire and every other open source developer and user who contributes directly or indirectly to the LineageOS community in the development of and in providing feedback for the trlte and trlteduos.
Sources
- LineageOS
- triplr-dev
XDA:DevDB Information
LineageOS 15.1, ROM for the Samsung Galaxy Note 4
Contributors
micky387, ripee, tripLr, _mone, cvxda
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.10.x
ROM Firmware Required: Stock Marshmallow for your variant.
Version Information
Status: Snapshot
Current Stable Version: 8.1.0
Created 2018-03-09
Last Updated 2019-07-13

Reserved

Reserved

known bugs?

Rom for note 4 duos N9100???

I am gonna test it now on N910T and will report back.
Thank you.
.
By the way i got some cool amoled wallpapers of lineage os below.

Thx ,keep the note 4 alive ,I will try this weekend

aafranki said:
known bugs?
Click to expand...
Click to collapse
Some camera issue (minor) and ??
merc200k said:
Rom for note 4 duos N9100???
Click to expand...
Click to collapse
Not support
Trex888 said:
I am gonna test it now on N910T and will report back.
Thank you.
Click to expand...
Click to collapse
Perfect ,report after
Becareful read closely OP.
When @ripee or @_mone are ready , they will continue this project

not support N9100??? so I cant test it..
maybe in the future?

Downloading it for the N910F. Gonna test it tonight. Thanks!
edit: ok, installed fine. But no sounds for the speaker, nothing.

Fingerprint dosnt work.No sound too.

Sound is not in this package

nisi3nt said:
Sound is not in this package
Click to expand...
Click to collapse
bt don't work, call sound don't work, speaker sound don't work= phone inusable

petzku said:
Downloading it for the N910F. Gonna test it tonight. Thanks!
edit: ok, installed fine. But no sounds for the speaker, nothing.
Click to expand...
Click to collapse
scpeter1 said:
Fingerprint dosnt work.No sound too.
Click to expand...
Click to collapse
nisi3nt said:
Sound is not in this package
Click to expand...
Click to collapse
aafranki said:
bt don't work, call sound don't work, speaker sound don't work= phone inusable
Click to expand...
Click to collapse
Yes ,error in script.
Upload in progress with new build.
Sorry for this mistake

aafranki said:
bt don't work, call sound don't work, speaker sound don't work= phone inusable
Click to expand...
Click to collapse
That's right but I am jockeying a little the dev well fix this in the next update

nisi3nt said:
That's right but I am jockeying a little the dev well fix this in the next update
Click to expand...
Click to collapse
Yes, Done. New build available in Op
Sorry again

micky387 said:
Yes, Done. New build available in Op
Sorry again
Click to expand...
Click to collapse
download link?

hmm link dosen work error 404

micky387 said:
Yes, Done. New build available in Op
Sorry again
Click to expand...
Click to collapse
Rom dl Link not working.

Fingerprint dosntworking again.Sound is back.

[ROM][EOL][FINAL][8.1.0][i9100] Pixel Experience ASB[AOSP][r65][2019/07/15]

{
"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"
}
PixelExperience ASB for Galaxy S2 [i9100]
What is this?
Pixel Experience ASB is an AOSP ROM based on the original project, with Google apps included and all Pixel goodies (launcher, wallpapers, icons, fonts, bootanimation)
Our mission is to offer the maximum possible stability and security, along with essential features for the proper functioning of the device and latest ASB patches for Android Oreo
Based on Android 8.1
NOTE:
Code:
* Your warranty is now void.
* We are not responsible for anything that may happen to your phone by installing any custom ROMs and/or kernels.
* You do it at your own risk and take the responsibility upon yourself and you are not to blame us or XDA and its respected developers.
Whats working?
Wifi
RIL
Mobile data
GPS
Camera
Flashlight
Camcorder
Bluetooth
FMRadio
Lights
Sound / vibration
Known issues
VSync
DON'T FLASH GAPPS, ALREADY INCLUDED
Download:
AFH: New builds
Old builds without emulated storage

Android OS version: 8.1.0_r65
Security patch level: July 2019 (Lineage ASB)
Build author: linusdan
Source code: https://github.com/PixelExperience
Kernel of device: https://gitlab.com/linusdan/kernel_samsung_smdk4412/tree/oreo
ROM Developer: linusdan
Credits - @rINanDO
Before installing ROM, you need to:
- 1.5 GB of system partition
- Emulated storage (from the April build).
Not sure how? See in this post
If you like my work, do not forget to click the button thanks. It's free!!!
ROM OS Version: 8.1 Oreo
ROM Kernel: Linux 3.0.x
Based On: AOSP
TWRP Required: TWRP 3.3.1-1 EMU
Version Information
Status: Stable. No longer maintained
Created 2018-09-21
Last Updated 2019-07-15

Reserved
NO ETA REQUESTS!
DOWNLOAD LINKS IN OP
Frequent questions
I do not use GAPPS! How can I remove?
R: Unfortunately not. Sorry.
What are the bugs?
R: See Known issues in OP.
How do I get root?
R: Download SuperSU Flashable and install via TWRP. After this, update the application by the Google Play
I found a bug!
Make a logcat and put it in pastebin/hastebin. I'll look when I can
You will need a computer, adb installed, usb debugging enabled on the smartphone and a usb cable.
Here's how to do it here.
1. Open Command Prompt (Windows) or Terminal (Linux/macOS).
2. Type:
Code:
adb logcat -d > logcat-dd-mm-yyyy.txt
This will save the log to logcat-dd-mm-yyyy.txt.
No nonsense questions, please!
Avoid meaningless discussions and help you and the user have useful information on the thread :good:
Dan, when I connect the phone to the PC, I can not access the files because there is no information to authorize the procedure in the notification! Please take a look when you can.
Calm down, Padawan! This is not a bug but google stuff. They have placed the authorization option on development tools. Everyone is trying to understand why this
Do this when you want to have access to them:
Go to System -> developer option -> USB and activate MTP manually.
What will be the frequency of compilations?
Monthly or every two months . I plan to spend $12 per month for the projects.
Praying for the low dollar quote on the Google Cloud Engine :laugh::fingers-crossed::good:

Upgrade from Samsung stock ROM to latest build using ODIN 3.13.1
Also recommended for devices with Android 4.4 - 5+
Back up your files and make a full wipe before the procedure.
Files Required:
Stock ROM
Pit file by-the.gangster
Samsung USB Driver
Odin 3.13.1
Latest Pixel Experience
Pit file with Emulated Storage by rINanDO
TWRP Emulated Storage 3.3.1-1 by rINanDO
0) Install Stock ROM
0.1 After downloading the tools, install the Samsung USB Driver and unzip the file of the rom.
The original rom file is tar.md5
0.2a Boot your phone into Download-mode (Volume down + Power/Standby + Home and hold for 10 seconds).
0.2b Start Odin 3.13.1 in your PC.
0.2c Connect your phone via USB to your PC.
0.2d Press volume up on your phone, Odin should detect your phone.
0.3 In the pit tab on the left side, select the file "i9100_1.5gb-system_6gb-data_512mb-preload_by-the.gangster.pit"
0.4 In AP button, select the tar.md5 file. The Odin app will frozen for a few minutes but do not worry.
After this, select start button. Wait terminate, do not pull the cable
0.5 The device will restart. A message will appear stating that it is encrypted. Turn off your device and enter recovery mode (Volume up + Power/Standby + Home and hold for 10 seconds). Clear Cache and Dalvik / Cache. Restart.
0.6 A warning will appear in the status bar saying that the partition is corrupted. Format the partition. Verify that the partition succeeded in the device settings.
0.7 Charge the phone and follow the next instructions.
1) Prepare your phone
1.1 Copy the ROM to the Micro-SDCard before flashing.
1.2 Boot your phone into Download-mode (Volume down + Power/Standby + Home and hold for 10 seconds).
1.3 Start Odin 3.13.1 in your PC.
1.4 Connect your phone via USB to your PC.
1.5 Press volume up on your phone, Odin should detect your phone.
2) Odin
Auto Reboot : unchecked
Re-Partition: checked
PIT : i9100-LOS-16.0-Emulated-Storage.pit
AP : i9100-LOS-16.0-Emulated-Storage-TWRP-3.3.1-1.tar.md5
Press Start.
3) After successful flash
Reboot phone into Recovery
Press Volume up + Power/Standby + Home and hold for 10 seconds.
The phone shuts down.
Repeat Press Volume up + Power/Standby + Home and hold for 10 seconds
Phone boots in recovery TWRP 3.3.1-1. Swipe to allow modifications.
4) TWRP
In TWRP 3.3.1-1 you need to format partitions
- Wipe -> Format Data -> Type [yes]
- Wipe -> Advanced Wipe -> Select:
Dalvik / ART Cache
Cache
System
Non-emulated Storage
-> Swipe to Wipe
5) Install Pixel Experience and boot system.
P.S: To prevent "Uncryption unsuccessful" error of GAPPS at first start:
- Reboot to recovery and Wipe -> Format Data -> Type [yes] again
Changelog
15072019 [EOL] - FINAL BUILD
* Android 8.1.0_r65
* Fix audio stereo recording
* GApps updated to the latest
* Add dummy keydisabler to allow navbar disabling
* Chromium webview: Updated to 75.0.3770.101 via LOS;
* Added Bluetooth SIM Access Profile support (not tested)
* Using the preload partition for compatibility with the new version of TWRP Emulated Storage by rINanDO
* Applied security updates from LineageOS (July 2019) because Google has not released a new tag for the Oreo
Important:
Update the TWRP before installation!
Files Required:
TWRP EMU 3.3.1-1 by rINanDO
1) Flash TWRP EMU 3.3.1-1 by rINanDO and reboot recovery.
2) Install the new update with dirty flash.
Changelog
04062019 [EOL]
* Android 8.1.0_r65
* GApps updated to the latest
* Fix ADB connection via FunctionFS
* Chromium webview: Updated to 72.0.3626.121 via LOS;
09042019 [EOL]
First PixelExperience ASB build
* Android 8.1.0_r63
* Increased heapsize to 360mb
* Support to multi user added
* GApps updated to the latest
* Performance enhancements
* Emulated storage implemented
* Ported FunctionFS to our kernel (credits goes to @rINanDO)
24112018
* Updated sources;
* GApps updated to the latest
* Fix brightness button;
* Various bug fixes.
07112018
* Updated sources;
* GApps updated to the latest
13102018
* Enabled wifi powersave mode (credits goes to @rINanDO)
* Chromium webview: Updated to 69.0.3497.109 through the lineageos repository;
* GApps updated to the latest
04102018
* Performance optimizations;
* Implementation of auto sleep through (battery drain has improved a lot!);
* GApps updated to the latest

ohh!! i was waiting for this!!
thanks
i'll try and report

thanks alot for share :good:
but if this is a beta, i think it's better add BETA in title

linusdan said:
PixelExperience for Samsung Galaxy SII International (GT-I9100)
DON'T FLASH GAPPS, ALREADY INCLUDED
Download:
GDrive - AFH
Last Updated 2018-09-21
Click to expand...
Click to collapse
Thanks for the ROM. But I don't need and like g-apps. How to uninstall them?

I'm getting error 7 while patching system partition. I have 1GB system partition. how big does it need?
fixed it, system partition had gone dirty, fixe it, could able to flash

guest4711 said:
Thanks for the ROM. But I don't need and like g-apps. How to uninstall them?
Click to expand...
Click to collapse
chhapil said:
I'm getting error 7 while patching system partition. I have 1GB system partition. how big does it need?
fixed it, system partition had gone dirty, fixe it, could able to flash
Click to expand...
Click to collapse
I put this information in the second and third posts. I was going to add before, but I was very sleepy. Take a look, please

linusdan said:
I put this information in the second and third posts. I was going to add before, but I was very sleepy. Take a look, please
Click to expand...
Click to collapse
Sure will help as normally pixel ROMs come with gapps pre packaged it needs bigger system partition.
Also i have seen from Moto G forum, folks have seen better results with Android Go config.
Worth a try for our old device

linusdan said:
INSTRUCTIONS FOR RESIZING THE PARTITION
2) Open the odin. In the pit tab on the left side, select the file "I9100_1.5GB-System_6GB-Data_512MB-Preload_by-
Click to expand...
Click to collapse
Do you recommend that pit files for all yours ROMs? For Nougat too?

Gastozz said:
Do you recommend that pit files for all yours ROMs? For Nougat too?
Click to expand...
Click to collapse
And why not?

Thanks, Feedback as soon as possible

New build is up with Android Go configurations.
Download in OP.

-So far for me:
-Install from jb 4.2.1 after repit get find.
- Phone not recognized by connecting PC câble to windows 7
- Cannot open files from ES explorer apps. Message "SD card formated as internal memory, reboot your phone"
- My files apps works to go to external SD but until now internal SD no chance, maybe a repit problem, going to repit and reinstall to see.
- Camera works great but sending photos by bluetoth or gmail didn't work.
- Don't know anything about call transmition, cose' still have issue regarding, after reboot, ask me for network unlock.
Since i bought it 7 years ago, free from any mobiile operator, i never had this problem before and until now it got thousands "ROM flash".
Maybe because i changed the sim card or imei issue? so long guys

islander999 said:
-So far for me:
-Install from jb 4.2.1 after repit get find.
- Phone not recognized by connecting PC câble to windows 7
- Cannot open files from ES explorer apps. Message "SD card formated as internal memory, reboot your phone"
- My files apps works to go to external SD but until now internal SD no chance, maybe a repit problem, going to repit and reinstall to see.
- Camera works great but sending photos by bluetoth or gmail didn't work.
- Don't know anything about call transmition, cose' still have issue regarding, after reboot, ask me for network unlock.
Since i bought it 7 years ago, free from any mobiile operator, i never had this problem before and until now it got thousands "ROM flash".
Maybe because i changed the sim card or imei issue? so long guys
Click to expand...
Click to collapse
I am using ROM for 8 days and have not seen any related issues. I'll consider some things.
Thanks for the feedback!

linusdan said:
I am using ROM for 8 days and have not seen any related issues. I'll consider some things.
Thanks for the feedback!
Click to expand...
Click to collapse
Regarding the unlock network code message, it happens since i tried to install lineage-15.1-20180731-UNOFFICIAL-i9100 i guess, not from your ROM.
But for other bugs i still have issue, even after new reinstall, from repit. Maybe i miss something after the repit process.
I don't remember, should we reconfigure the format of cache, system, etc ?

islander999 said:
Regarding the unlock network code message, it happens since i tried to install lineage-15.1-20180731-UNOFFICIAL-i9100 i guess, not from your ROM.
But for other bugs i still have issue, even after new reinstall, from repit. Maybe i miss something after the repit process.
I don't remember, should we reconfigure the format of cache, system, etc ?
Click to expand...
Click to collapse
Yes! A thorough cleaning is always recommended.

linusdan said:
Yes! A thorough cleaning is always recommended.
Click to expand...
Click to collapse
Thanks for your answer but i did all the wipe.
I was meaning before, do i have to change file system from EXT4 to F2FS for example

islander999 said:
Thanks for your answer but i did all the wipe.
I was meaning before, do i have to change file system from EXT4 to F2FS for example
Click to expand...
Click to collapse
If you wish.

https://forum.xda-developers.com/showthread.php?t=3752664 go apps it works on dotos v2.5 oreo

[ROM][11] crDroid 7.17 [begonia/begoniain][OFFICIAL]

{
"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:
*** Disclaimer
I am not responsible for any damage you made to your device
You have been warned
crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features existent today
Features:
https://github.com/crdroidandroid/crdroid_features/blob/11.0/README.mkdn
Instructions:
First time installation:
Carry out the necessary measures to unlock the bootloader.
Connect the phone to the PC with the supplied cord.
Transfer all valuable data from your phone's internal memory to PC. If you make a backup, then the folder with the backup (except if the backup is located on microSD).
Reboot into Fastboot mode (see the header in the F.A.Q. for how to enter it)
Download and unpack on your PC >> this << archive.
In the unpacked archive, go to the folder with your device type (if you have an Indian phone, then in [begoniain], all others in [begonia].
Run !_FLASH_IT_W.bat on Windows or !_FLASH_IT_L.sh on Linux (DO NOT CHANGE THESE SCRIPTS UNLESS YOU WANT TO GET A BRICK!!!)
If something went wrong, check if ADB drivers are installed on Windows, or fastboot packages on Linux.
The necessary images will be flashed and erased, etc., after which the phone itself will reboot into TWRP recovery.
Make the format Data (section Wipe / Wipe, click the Format Data button, then enter "Yes").
Reboot from TWRP to TWRP
Make sure your phone's internal memory is opened in TWRP mode on your PC.
Before starting the ROM installation, it is recommended to take measures to unlock the bootloader and save the critical sections of the phone.
Download and place the archive with the firmware in the internal memory of the phone, as well as Google Apps, if you need them.
Do a Wipe/Cleanup of the "system", "vendor", "cache" and "Dalvik|Art Cache" partitions.
Click Installation / Install and select the archive with the firmware, then click the Add / Add button and select the archive with Google Apps, everything else will be installed and updated automatically.
After installation, reboot again from TWRP to TWRP
Make the format Data (section Wipe / Wipe, click the Format Data button, then enter "Yes").
Reboot into the system and wait for initialization, usually 10 minutes is enough, if the download still fails, reboot forcibly into recovery (long hold volume up + on) and repeat the Format Data operation
After booting the system, perform the initial setup, and then reboot.
TWRP installation:
Before starting the ROM installation, it is recommended to take measures to unlock the bootloader and save the critical sections of the phone.
Save important data, photos, and more.
Download and place the archive with the firmware in the internal memory of the phone, as well as Google Apps if you need them.
Reboot into TWRP if you're not already there (reboot by holding the volume up button).
Wipe/Cleanup the "system", "vendor", "cache" and "Dalvik|Art Cache" partitions.
Click Install/Install and select the firmware archive, then click the Add/Add button and select the Google Apps archive, everything else will be installed and updated automatically.
After installation, reboot from TWRP to TWRP
Do data formatting (section Wipe / Wipe, click the Format Data button, then enter "Yes").
Reboot into the system and wait for initialization, usually 10 minutes is enough, if the download still fails, reboot forcibly into recovery (long hold volume up + on) and repeat the Format Data operation
Once the system has booted, perform the initial setup and then reboot.
Update installation:
USE THESE INSTRUCTION ONLY FOR UPDATING FROM MY PREVIOUS BUILD TO A NEW !!!
Make backups.
Download and place the ROM to the internal memory of the phone
(I do not recommend SD cards, often phones fail because they turn out to be broken)
Reboot in TWRP (vol+ with power button)
Click on Install menu and chose this ROM
After installation click on "Wipe Art/Dalvic" button
Reboot to system
If you have a bootloop, make Format Data in TWRP (all data will be erased).
Rollback to the factory firmware:
Download and unpack any MIUI Fastboot version ROM for begonia or begoniain
Reboot to Fastboot mode (vol- or vol+ with power button)
Run flash_all.bat on Windows or flash_all.sh on Linux
DO NOT USE OTHER ROLLING METHODS IF YOU DO NOT WANT TO GET BRICK !!!
Sources:
ROM: https://github.com/crdroidandroid
Device: https://github.com/TTTT555/device_xiaomi_begonia
Kernel: https://github.com/TTTT555/kernel_xiaomi_begonia
Credits and Thanks:
@DarkJoker360Dev
@SoldatSempai
And to all begonia devs, who is working on an open tree for our device.
Visit official website @ crDroid.net
crDroid Community Telegram
crDroid Device Telegram (links to donations to the author here)
crDroid Device Telegram RU zone
My Telegram
Donate to help crDroid team pay server costs.
XDA:DevDB Information
crDroid, ROM for the Redmi Note 8 Pro
Contributors
TTTT555
ROM OS Version: Android 11
Based On: crDroid 6.x / crDroid 8.x
Version Information
Status: Stable

Notes:
- If you have bootloop after installation, try format data again or to change GAPPS.
- Reboot after a clean install and initial setup so that the BegoniaParts item appears in the settings.
- GAPPS and Google Photo required for G-Cams.
- If you will use Viper FX, then do not forget to enable legacy mode in the application settings.
- If you will use the built-in G-Cams, do not forget to apply configs (three taps between the camshot button and gallery button). If the camera does not find the built-in configs, just reboot the device and try again.
- If you OFF James DSP after ON, reenable Dirac (OFF/ON), if you need it.
- If you OFF G-cam 64 after ON, reboot the device, otherwise bugs are possible.
- ANX cam: If you have problems with a wide angle camera - just turn off the lens distortion correction function, or set the mode to 9/16.
===== 11 May, 2022 =====
* Device tree:
- Based on A-11/12 device trees (R-OSS) by @DarkJoker360
- Packed required firmwares with TWRP into the ROM archive
- Added in-call volumes fix via script
- Rewrote display props
- Rewrote overlays to such as on crDroid v.6.25
- ZRAM fixes and tweaks
- Perfomance and battery optimizations
- Added lost sepolicy denies
- BegoniaParts: Fixed Vibrator's Strenght restore after reboot
- Add G-photo unlim
- MTK Wi-Fi Display injection
- Enable privapp permissions control
- Added MTK Engineer Mode app
- Additions for manifest and compatibility matrix
- Inbuild configs for inbuild G-cams
- Some audio optimizations
- Some init optimizations
- And something else
* Kernel:
- Based on R-OSS kernel tree by @DarkJoker360
- Declare CocoLite kernel
- Add xt_HL module (TTL)
- Add "sioplus" I\O scheduler and make it by default
- Add ALMK
- Some performance improovements
- Some tweaks for support BegoniaParts
- Enforce selinux via cmdline
* BegoniaParts:
- Dirac sound instead MI sound
- Viper with on/off switch (audio)
- James DSP with on/off switch (audio)
- DB FX with on/off switch (audio)
- Switch for some EAS Governors
- Switch for Governor's ratio
- Codec switch
- TCP congestion switch
- Wi-Fi MTK Sta2 mode switch
- Switch for enabling 900 mA via USB
- Switch for disabling MI thermal (if you want)
- Camera switch (ANX, G-cam Burial 8, G-cam true 64 MP)
- V-Sync disabler (if you want)
- Switch for activating debug.sf.latch_unsignaled (if you want)
- Switch for disabling HW overlays (if you want)
- True FPS Info switch
- Gestures section
- 10 point vibration strenght switch
/ Thanks to @7Soldier for help with some features /

i dit a first install of android 11 crdroid. works perfectbut now my twrp is decrypted, ow do i decrypt?

@TTTT555
Is it similar to Rom of VNDK30?
Just that needs the TWRP metadat version to flash , right?

gadmei.tw said:
@TTTT555
Is it similar to Rom of VNDK30?
Just that needs the TWRP metadat version to flash , right?
Click to expand...
Click to collapse
I downloaded the correct metadata and i flashed it with fastboot. Now i can decrypt

Hi.
Does call recording work on this ROM?

reist said:
I downloaded the correct metadata and i flashed it with fastboot. Now i can decrypt
Click to expand...
Click to collapse
i have the same problem. where did u find metadata ?

ariber14 said:
i have the same problem. where did u find metadata ?
Click to expand...
Click to collapse
Go here. And download the 3.4.0.4 metadata and flash it.

How i fix the low quality in videos of instagram???

*edited
Nevermind, thanks

Hi all, anyone using this as their daily driver? Keen to hear how is going. Thanks

Thanks

Thank you for your Work.
Trcamera doesnt Work for me.
In Anx also my front cam doesnt Work.
Any solutions?

The ROM is fast!
NikGApps is working fine to me (I don't know if Google Auto and Google Assistant work because I don't use them).
Trcamera crashes when going to gallery. This fixed when I flashed the omni version of NikGApps. Turns out that the default app for gallery must be Google Photos (AOSP Gallery not working for trcamera)
I don't know about the charging... It says it's it's slowly charging even if I'm using the original fast charger of my phone.
This ROM is awesome nonetheless and thank you devs for keeping up the good work!

Akira10 said:
Trcamera doesnt Work for me.
Click to expand...
Click to collapse
I uninstalled the pre-installed trcamera and installed this version.
Before doing that, flash this buffer fix in Magisk.

d4dave said:
Hi all, anyone using this as their daily driver? Keen to hear how is going. Thanks
Click to expand...
Click to collapse
I've been using this for quite a while now...
mostly stable in everything. Both the Cameras are fine. All features functional. Charging and battery performance all good. The pixel launcher feels buggy with the recents tray so using the crdoid home app. Pretty good.
jeane_uglypish said:
The ROM is fast!
NikGApps is working fine to me (I don't know if Google Auto and Google Assistant work because I don't use them).
Trcamera crashes when going to gallery. This fixed when I flashed the omni version of NikGApps. Turns out that the default app for gallery must be Google Photos (AOSP Gallery not working for trcamera)
I don't know about the charging... It says it's it's slowly charging even if I'm using the original fast charger of my phone.
This ROM is awesome nonetheless and thank you devs for keeping up the good work!
Click to expand...
Click to collapse
The assistant is working fine with full functional voice recognition. But changing the device fingerprint to something else creates a problem with Ok google because The assistant 2.0 or later gets installed and something happens. ( I haven't used android auto too so no comment).
I also flashed nikgapps full package and everything is fine.
The slow charging problem that u have is not happening with me. What happens is that at the starting it shows charging slowly. Then after a few seconds or a minute it starts charging rapidly.

@TTTT555 do you really need to wipe the internal storage ? It's kinda lame to have to copy everything, couldn't you just wipe data ?

Shafin2315 said:
I've been using this for quite a while now...
mostly stable in everything. Both the Cameras are fine. All features functional. Charging and battery performance all good. The pixel launcher feels buggy with the recents tray so using the crdoid home app. Pretty good.
Click to expand...
Click to collapse
You mentioned "both the cameras are fine", do you mean the rear and front camera?

thank you very much

kirinin said:
You mentioned "both the cameras are fine", do you mean the rear and front camera?
Click to expand...
Click to collapse
Oh, no no. I meant trCam and AnXcam app...both are working pretty fine so far. My rear and front cam works fine anyways. I have the old device. I am not on the new one.. I think I know what ur trying to say. Ur front cam probably doesn't work ri8? I'm pretty sure in most of the threads people said that the new device kernel hasn't been released and new cam isn't responding in many roms because of that. Honestly i don't think there's any workaround for that unless the kernel is officially released.

[ROM][11][Lake][OFFICIAL] RevengeOS 4.0

CHANGES
04/11/21:
- RevengeUI is here!
- Dropped MotoClock.
- Update display config to 1.9.
- Increased status bar height for notch.
- Drop QS height in favor of the new interface.
Notes:
- Dirty flash is possible!
- For temporary fix blur lag, go to t.me/FraaxiusGrp and type #fix-blur.
04/04/21:
- Initial official build.
- Added Moto Live Wallpapers.
- RevengeUI release in the next build... Stay tuned!
03/12/21:
- Initial build.
- Added MotoClock.
- Added MotoCam2.
- Improved rounded corners.

Reserved 2

Reserved 3

Does this ROM support signature spoofing? Thx.

Playing with this a little. Wasn't sure which version (11). AFWall plays well with this, and the firewall log works so far.

Fraaxius said:
INSTALLATION- Boot TWRP img
- Flash Copy-Partitions-ab. (Only if you install from Stock ROM)
- Make backups of EFS, Persist, Persist 2, Modem, FSG & DSP. (Only if you install from Stock ROM)
- Wipe > Format Data > Yes
- Flash RevengeOS build
- Flash TWRP Installer
- Reboot.
After...
- Optional: Reboot in recovery
- Optional: flash FlameGApps
- Wipe > Format data > Yes
- Reboot system
U need Magisk?
- Reboot to recovery
- Optional: flash Magisk (if you want to root your device as well) (it's recommended to flash Magisk post first boot)
- Reboot system.
Click to expand...
Click to collapse
I currently use LineageOS 18 on my Moto G7 Plus, which I successfully installed myself using the official instructions. Never used TWRP.
Lineage is OK. Nothing great. Android itself just gets worse with ever generation it seems. And some things don't work at all on mine (like voicemail).
So, I want to try this Revenge OS. Questions:
1) I don't understand what all these install directions actually mean. Sorry, I'm just not that experienced. How do I learn what they all mean so I don't brick my phone?
2) How do I know I can trust Revenge as an OS that doesn't have extra malicious code in it (key/screen loggers, etc) that will get my data, passwords, crypto, etc?
Thx.

synrgii said:
So, I want to try this Revenge OS. Questions:
1) I don't understand what all these install directions actually mean. Sorry, I'm just not that experienced. How do I learn what they all mean so I don't brick my phone?
2) How do I know I can trust Revenge as an OS that doesn't have extra malicious code in it (key/screen loggers, etc) that will get my data, passwords, crypto, etc?
Thx.
Click to expand...
Click to collapse
1) That's something that you could look into. You should be able to google and learn what the terms mean or look at the instructions for other custom ROMs here and see if there's a better explanation as generally the procedures are quite similar.
2) The source code IS available at https://github.com/revengeos so you can audit it yourself but most people aren't going to know what to look for. You could check Revenge's Telegram or other connections and see what others are experiencing and saying.

srshamblen said:
Does this ROM support signature spoofing? Thx.
Click to expand...
Click to collapse
yes

Thank you for the OS. I installed it and started testing on my G7 plus. It gave me a feeling of a very snappy system, letting fast apps functioning. Great! The only issue I discovered is the aborting wallpaper app which prevents me from changing the main screen appearence. But I could live with it. So I proceeded to enable rooted apps, like AWFirewall, via Magisk. For this I needed to install TWRP via recovery mode.
And here I knocked into a true problem... The recovery boot disappeared! Trying to reset to Recovery mode I only fall into a screen with dead android icon saying "No Command". I can alternatively enter the bootloader, but when I opt for Recovery Mode or other options, the device enters into bootloop. I can only launch back the OS which works without root.
I tried to lauch TWRP via fastboot command: fastboot boot twrp-3.5.2_9-0-lake.img. TWRP runs but the touchscreen remains unresponsive. So no chance that way either for installing Magisk. Flashing TWRP does not work, it says "no partitition found".
I tried some advices proposed in forums and found out that remounting /system and /cache fail via "adb mount -o rw,remount -t yaffs2", only /data is detected. I presume that the OS installation procedure in some way blocked access to system partititions.
Could you please suggest a solution of the issue. I'd like to take back control over root and recovery partititions.
Thanks for your advice and help

This ROM is all about open source APPS : Kudos!
Maybe some folks could not like the replacement of the originals AOSP apps
Except for few things (buttons and gestures) not costumizable , its a shame
Screenshot are from me ...

BEWARE : TWRP touchscreen totally unresponsive , its true
After install this ROM , when wanted to to install other ROM thru TWRP the touchscreen totally unresponsive...
SOLUTION: install another ROM from "ADB sideload" to regain TWRP touchscreen, worked for me
Regards

Thank you for reviewing this rom!

Hello i think download link is not working, i would like to test this rom

Better Mobile App

welcome