Related
LineageOS 14.1 for Galaxy A5 A500xxYou've probably known that cm is "dead", and that there is a new project called "LineageOS" which is a fork on the cyanogenmod project, so this is the "continue" of my cyanogenmod thread. Enjoy
NOTE: this ROM is for any A500 model and will not work for 2016 models (A510)
Disclaimer:
Code:
I'm not responsable for bricked devices :( , dead phone chargers,
nuclear explosions or global warming.
Flash it at YOUR OWN RISK
Downloads1) You need a custom recovery to flash the ROM (zip). You can download TWRP HERE or CTR HERE
2) Optional but recomended: Google Apps (aka gapps). You can download them here: http://opengapps.org/
3) You need marshmallow bootloader and modem. Install latest mm stock ROM to update them
4) You need the ROM obviusly . You can download it here:
LineageOS-14.1: https://www.androidfilehost.com/?w=files&flid=145997
How to InstallIf you have TWRP Recovery:
1) Go to wipe section and wipe: cache, dalvik, system and data (internal storage wipe is not needed!)
2) Go to install box and choose the zip which contains the ROM
3) Flash wifi temporary fix (for first build only)
4) Optional but recomended: flash Google Apps' zip
5) Reboot and enjoy
If you have CTR Recovery:
1) Go to Wipe Menu, tap Wipe ALL - Preflash button and then tap - Yes - Wipe ALL! button
2) Go to Install zip menu and choose the zip which contains the ROM
3) Flash wifi temporary fix (for first build only)
4) Optional but recomended: flash Google Apps' zip
5) Reboot and enjoy
How to Update
If you have TWRP Recovery:
1) Go to install box and choose the zip which contains the ROM
2) Go to wipe section and wipe: cache and dalvik
If you have CTR Recovery:
1) Go to Install zip menu and choose the zip which contains the ROM
2) Go to Wipe Menu, and wipe cache and dalvik
NOTE: For Updating you don't have to wipe data, you only have to wipe data when install different cm version, for example cm-13->cm-14.0 or cm12->12.1
SM-A500XX SECTIONNote1: if you are on SM-A500FU you don't have to follow this section. Just follow the "How to install" one
NOTE2: some device requires some modifications in blobs and/or in device tree in order to get RIL worling
How to install CyanogenMod-14.1 on any SM-A500XX variant:
1) Install the zip of lineageos rom
2) Install RIL fix zip from this thread's attachements
3) Flash gapps (optional but better)
4) Reboot and enjoy
For people running multirom with lineage as secondary ROM:
1) Install the zip of lineageos rom
2) Install gapps (optional but better)
3) Download (from this thread's attachements) and open RIL fix zip for your device
4) Open (inside the zip) /META-INF/com/google/android/updater-script
5) Remove these two lines:
ifelse(is_mounted("/system"), unmount("/system"));
mount("ext4", "EMMC", "/dev/block/bootdevice/by-name/system", "/system");
6) Save the new file and close
7) Go in twrp "Advanced"->"Terminal" and run this command:
ln -s /sdcard/multirom/roms/ROMNAME/system /system
Note: if the output of ln command is "File exists" you made a typo, so, re-run the command without making typos (tab helps); if it gives no output, you typed it correctly, so, you can proceed to the 8th step
8) Flash RIL fix zip
9) Reboot and enjoy
NOTE: If you don't find the RIL fix from your variant and you have RIL problems like sim card not detected, read the section for people with RIL problems and follow the instructions
Knowing Bugs
None for now
Report bugs here, or at https://github.com/DeadSquirrel01/android_device_samsung_a5-common/issues
F2FS Guide
If you want to use F2FS, first you need a twrp that supports F2FS partitions formatting like mine:
https://www.androidfilehost.com/?fid=817550096634793304
Then, reboot in twrp, go in "Wipe"->"Advanced Wipe"->Select "System" box->"Repair or Change File System"->"Change File System"->"F2FS"
Do this also for "Data" and "Cache" partitions
NOTE: Everything in the partitions you turn into F2FS will be deleted!!!
NOTE: If you turn userdata partition (/data), everything in /data/media/0 (/sdcard) will be deleted!!!
Now, open the zip of lineage os and change:
mount("ext4", "EMMC", "/dev/block/bootdevice/by-name/system", "/system");
to
mount("f2fs", "EMMC", "/dev/block/bootdevice/by-name/system", "/system");
Read this if you are having problems with RIL
If you have issue with RIL, post a zip with these libs taken from stock rom, and I'll create a flashable zip:
Code:
/system/lib/libsec-ril.so
/system/lib/libsec-ril-dsds.so (for dual sim variants only)
SOURCES
Device tree: https://github.com/DeadSquirrel01/android_device_samsung_a5ultexx Branch: cm-14.1
Device Config: https://github.com/DeadSquirrel01/android_device_samsung_a5-common Branch: cm-14.1
Kernel: https://github.com/DeadSquirrel01/android_kernel_samsung_msm8916 Branch: cm-14.0
Telegram group: @GalaxyA5dev
Telegram channel for project updates: @ds01news
Note: If you want to contact me for any question which is off topic, just pm me or email me at [email protected]
XDA:DevDB Information
LineageOS-14.1 for Galaxy A5 SM-A500, ROM for the Samsung Galaxy A Series 2017 A3, A5, A7
Contributors
DeadSquirrel01
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
ROM Firmware Required: Lollipop or Marshmallow bootloader/modem (mm suggested)
Version Information
Status: Stable
Created 2017-02-17
Last Updated 2017-02-17
CHANGELOGFifth release (07/09/2017):
Support calls through LTE (VoLTE)
Fix touchscreen freezes on wakeup
Fix GPS: Now it takes about 10 seconds outdoor and 20 seconds outdoor to get the position (these values may change a bit)
Remove NFC button and everything related to NFC. Since it always stucked on turning on, his crashes were slowing down the system a lot
Fourth release (22/08/2017):
Add button to switch data to LTE for variants that support it
Bring CPU core 1 online (active) (improves performance)
Fix touchkey lights
Update some things in ramdisk
Add screencast to record screen
Third release (17/08/2017):
Fix in-call audio
Fix FM radio
Fix LTE (for variants that support it)
Add OMS support for substratum themes (You can download them from google play. See screenshot's dark theme as example)
Add kernel driver to stop touchkey vibration when device is suspended (replaced InputDisabler)
Upgrade kernel to 3.10.106
Lot of other kernel updates and upgrade to LA.BR.1.2.9_rb1.23 (caf)
Upgrade blobs to A500FUXXU1CPG1 (marshmallow)
Add F2FS formatted /data,/system,/cache support. To do it you also need my twrp 3.1.1. (download in first post) or a twrp that supports f2fs formatting
Improved battery life on suspend (fixed doze)
Remove "ANDROID IS NOT SEANDROID ENFORCING" warning on samsung splash screen
Obviously compile ROM on latest lineage sources
Second Release (17/02/2017):
Fix camera that couldn't take videos
Add touch screen gestures
Minor updates to kernel and device tree (see github commits)
First Release (18/01/2017):
Fixed Screen Rotation
Fixed Cellular Data
Lots of minor updates in kernel, device config (see github commits)
NOTE: You can see all changes (github commits) here: https://github.com/DeadSquirrel01/android_device_samsung_a5-common/commits/cm-14.0
and here:https://github.com/DeadSquirrel01/android_device_samsung_a5ultexx/commits/cm-14.0
And for kernel here: https://github.com/DeadSquirrel01/android_kernel_samsung_msm8916/commits/cm-14.1
Excuse me. Why do you put SM-A500 stuff into the A Series (2017) Thread? Or have you misplaced it here and it belongs there?:
https://forum.xda-developers.com/samsung-a-series
saintsimon said:
Excuse me. Why do you put SM-A500 stuff into the A Series (2017) Thread? Is this clutter supposed to look clever? Or have you misplaced it here and it belongs there:
https://forum.xda-developers.com/samsung-a-series
Click to expand...
Click to collapse
Damn, I will ask to a moderator to move it
Good work my friend keeping an eye closely on this thread and wating penalty for audio fix to use it as daily driver
Pls when can we get the audio bug during call fixed? @DeadSquirrel01
---------- Post added at 19:30 ---------- Previous post was at 19:30 ----------
My device is A500H
unimke said:
Pls when can we get the audio bug during call fixed? @DeadSquirrel01
---------- Post added at 19:30 ---------- Previous post was at 19:30 ----------
My device is A500H
Click to expand...
Click to collapse
Please read the thread and follow it:
IMPORTANT: ETA askers: please grow up and make this thread clean; if you ask for ETAs I'll ignore you and your request(s)
Click to expand...
Click to collapse
Ok
Hey, I tried this Rom but was not able to flash it. It showed UNKNOWN ERROR while flashing through TWRP.
Does this error exit or I have done something wrong ?
My device is SM-A500G.
aryan1997 said:
Hey, I tried this Rom but was not able to flash it. It showed UNKNOWN ERROR while flashing through TWRP.
Does this error exit or I have done something wrong ?
My device is SM-A500G.
Click to expand...
Click to collapse
Its only for a500fu variant only...waiting for another variant..cheers man..
leviz0689 said:
Its only for a500fu variant only...waiting for another variant..cheers man..
Click to expand...
Click to collapse
Doh, still don't know why people don't read the full thread (or at least first 4-5 lines also wit "NOTE" in bold) and then cry if it doesn't work
Anyway that's not only for a500fu, when i have time I'll upload A500XX version, too
Sorry man..im only answer that comment too...
leviz0689 said:
Sorry man..im only answer that comment too...
Click to expand...
Click to collapse
You should ignore those comments
leviz0689 said:
Sorry man..im only answer that comment too...[/QUOTE
Dude, if you want to developers continued to work on a project, stop the ETA, wait for a stable version. The developers are people too, they have their own lives, and they do not have to answer stupid questions everyday The Developers works very hard, be patient.
Sorry, if you understand me, i don't speak English. )
Click to expand...
Click to collapse
DeadSquirrel01 said:
You should ignore those comments
Click to expand...
Click to collapse
Sorry, If I offended you in any way. I know that you work very hard and I really appreciate your work. Thanks for all of it.
Its just that there was a section in the post on how to install the Lineage OS on A500xx devices.
So, I just wanted to know that if there is an error or did I do something wrong.
I did not wanted to be rude or anything. Once again SORRY !!!!!!
DeadSquirrel01 said:
LineageOS 14.1 for Galaxy A5 A500xxYou've probably known that cm is "dead", and that there is a new project called "LineageOS" which is a fork on the cyanogenmod project, so this is the "continue" of my cyanogenmod thread. Enjoy
NOTE: this ROM is for any A500 model and will not work for 2016 models (A510)
NOTE2: The First build is for A500FU only!!!
NOTE3: 1st zip is only for SM-A500FU, I'll upload A500XX zip soon, when I have time
Disclaimer:
Code:
I'm not responsable for bricked devices :( , dead phone chargers,
nuclear explosions or global warming.
Flash it at YOUR OWN RISK
Downloads1) You need a custom recovery to flash the ROM (zip). You can download TWRP HERE or CTR HERE
2) Optional but recomended: Google Apps (aka gapps). You can download them here: http://opengapps.org/
3) You need marshmallow bootloader and modem. you can download them HERE (for A500FU only) thanks to @jimbomodder that has uploaded them or you can easily extract them in stock firmware
4) You need the ROM obviusly . You can download it here:
LineageOS-14.1: https://www.androidfilehost.com/?w=files&flid=145997
How to InstallIf you have TWRP Recovery:
1) Go to wipe section and wipe: cache, dalvik, system and data (internal storage wipe is not needed!)
2) Go to install box and choose the zip which contains the ROM
3) Flash wifi temporary fix (for first build only)
4) Optional but recomended: flash Google Apps' zip
5) Reboot and enjoy
If you have CTR Recovery:
1) Go to Wipe Menu, tap Wipe ALL - Preflash button and then tap - Yes - Wipe ALL! button
2) Go to Install zip menu and choose the zip which contains the ROM
3) Flash wifi temporary fix (for first build only)
4) Optional but recomended: flash Google Apps' zip
5) Reboot and enjoy
How to Update
If you have TWRP Recovery:
1) Go to install box and choose the zip which contains the ROM
2) Go to wipe section and wipe: cache and dalvik
If you have CTR Recovery:
1) Go to Install zip menu and choose the zip which contains the ROM
2) Go to Wipe Menu, and wipe cache and dalvik
NOTE: For Updating you don't have to wipe data, you only have to wipe data when install different cm version, for example cm-13->cm-14.0 or cm12->12.1
SM-A500XX SECTIONHow to install CyanogenMod-14.1 on any SM-A500XX variant:
1) Download the sm-a500xx cm-14.1 zip on "Downloads" section"
2) For make "port" process a bit easier do as following:
_1) Delete all files in system/etc/firmware (inside the zip)
_2) Go to META-INF/com/google/android/updater-script (in the zip) and remove all symlinks which start with /firmware and /firmware-modem
2) Use a root browser or adb pull and pull all files located in /firmware/image and /firmware-modem/image in the zip in /system/etc/firmware
2_a) If your device is dualsim, go to stock rom and copy /system/lib/libsecril.so and /system/lib/libsecril-dsds.so in the zip in system/lib/ Then open the system/build.prop in the zip and add:
persist.radio.multisim.config=dsds
3) Flash it and enjoy lineageos on you SM-A500XX variant!!
Knowing Bugs:
_Camera cannot take videos
_Audio during calls bug
Segnale other bugs if u find in bugs section or here https://github.com/DeadSquirrel01/android_device_samsung_a5-common/issues
IMPORTANT: ETA askers: please grow up and make this thread clean; if you ask for ETAs I'll ignore you and your request(s)
SOURCES
Device tree: https://github.com/DeadSquirrel01/android_device_samsung_a5ultexx Branch: cm-14.0
Device Config: https://github.com/DeadSquirrel01/android_device_samsung_a5-common Branch: cm-14.0
Kernel: https://github.com/DeadSquirrel01/android_kernel_samsung_msm8916 Branch: cm-14.1
Note: If you want to contact me for any question which is off topic, just pm me or email me at [email protected]
XDA:DevDB Information
LineageOS-14.1 for Galaxy A5 SM-A500, ROM for the Samsung Galaxy A Series 2017 A3, A5, A7
Contributors
DeadSquirrel01
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
ROM Firmware Required: Lollipop or Marshmallow bootloader/modem (mm suggested)
Version Information
Status: Stable
Created 2017-01-18
Last Updated 2017-01-18
Click to expand...
Click to collapse
1) Delete all files in system/etc/firmware (inside the zip)
_2) Go to META-INF/com/google/android/updater-script (in the zip) and remove all symlinks which start with /firmware and /firmware-modem
2) Use a root browser or adb pull and pull all files located in /firmware/image and /firmware-modem/image in the zip in /system/etc/firmware
cant find those location inside the zip sir sorry noob here and im using a500f sir thank you so much
ian0326 said:
LineageOS 14.1 for Galaxy A5 A500xx
You've probably known that cm is "dead", and that there is a new project called "LineageOS" which is a fork on the cyanogenmod project, so this is the "continue" of my cyanogenmod thread. Enjoy
NOTE: this ROM is for any A500 model and will not work for 2016 models (A510)
NOTE2: The First build is for A500FU only!!!
NOTE3: 1st zip is only for SM-A500FU, I'll upload A500XX zip soon, when I have time
Disclaimer:
1) Delete all files in system/etc/firmware (inside the zip)
_2) Go to META-INF/com/google/android/updater-script (in the zip) and remove all symlinks which start with /firmware and /firmware-modem
2) Use a root browser or adb pull and pull all files located in /firmware/image and /firmware-modem/image in the zip in /system/etc/firmware
cant find those location inside the zip sir sorry noob here and im using a500f sir thank you so much
Click to expand...
Click to collapse
you take /firmware/image and /firmware-modem/image from your stock rom and put them in /system/etc/firmware in the zip
hit thanks if it helped
You can post screenshots of what exactly the device would look like after installing the rom ?
Cannot install on samsung A500F updator error 7
carlossennin56 said:
You can post screenshots of what exactly the device would look like after installing the rom ?
Click to expand...
Click to collapse
Now i have rr on my device, maybe I'll add them later, but they are basically the same as cm14.1
Code:
** Disclaimer
I am not responsible if flashing this recovery bricks your
phone or causes thermonuclear war and ends the
world as we know it. You have been warned.
Recovery Information
Target Devices: Samsung Galaxy Grand Prime SM-G530MU | SM-G530M | SM-G530H | SM-G530FZ | SM-G530P | SM-G530T | SM-G530T1 | SM-G530W
Recovery Status: Stable
Maintainers: [ vince2678 ]
Project GitHub Repositories: https://github.com/Galaxy-MSM8916
Telegram Channel (for ROM build/completion notifications): https://telegram.me/GrandPrimeTWFZ
Telegram Group (for Q&A): https://telegram.me/joinchat/AJrZvz_pGY7Pvfis9kzMwA
Bug reports: http://grandprime.ddns.net/bugs/
Click to expand...
Click to collapse
Device Names
Verify your device codename before downloading any firmwares or recovery images!
Code:
[B]SM-G530MU[/B] - [COLOR="DarkSlateBlue"][B]gprimeltezt[/B][/COLOR]
[B]SM-G530M[/B] - [COLOR="DarkSlateBlue"][B]fortunalteub[/B][/COLOR]
[B]SM-G530FZ[/B] - [COLOR="DarkSlateBlue"][B]gprimeltexx[/B][/COLOR]
[B]SM-G530P/T/T1/W[/B] - [COLOR="DarkSlateBlue"][B]gprimelte[/B][/COLOR]
Click to expand...
Click to collapse
Download
Builds:
Code:
[B]SM-G530MU:[/B] [url]http://grandprime.ddns.net/job/Omni_Builds/job/twrp-3.1-gprimeltezt[/url]
[B]SM-G530M:[/B] [url]http://grandprime.ddns.net/job/Omni_Builds/job/twrp-3.1-fortunalteub[/url]
[B]SM-G530FZ:[/B] [url]http://grandprime.ddns.net/job/Omni_Builds/job/twrp-3.1-gprimeltexx[/url]
[B]SM-G530P/T/T1/W:[/B] [url]http://grandprime.ddns.net/job/Omni_Builds/job/twrp-3.1-gprimelte[/url]
Click to expand...
Click to collapse
Instructions
Installation using Odin
Code:
* [B]Enable Developer Mode on your phone and unlock the bootloader from the
Settings, if not done already. [/B]
* Download a recent [B].tar[/B] archive from the links above for your device.
* Reboot into Download Mode [Press Power+Volume Down+Home].
* Flash the [I][B]tar[/B][/I] archive using ODIN by clicking [I][B]AP[/B][/I] and selecting
the [I][B].tar[/B][/I] file you just downloaded.
Click to expand...
Click to collapse
Changelog
Code:
[B][U]29/05/2017[/U][/B]
* [B][[COLOR="Red"]NOTE[/COLOR]][/B] [B] Updated to 3.1.1-0.[/B]
* [B][[COLOR="Red"]FIX[/COLOR]][/B] [B] F2FS should work completely now.
Updated F2FS code from upstream kernel sources and enabled
security extended attribute support (for SElinux) to fix
android support.[/B]
Code:
[B][U]15/01/2017[/U][/B]
* [B] [ [COLOR="Red"]NOTE[/COLOR] ][/B] [B] Created DevDB project. [/B]
* [B][[COLOR="Red"]NOTE[/COLOR]][/B] [B] Mouse cursor is now hidden from recovery screen.[/B]
* [B][[COLOR="Red"]NOTE[/COLOR]][/B][B] Transitioned to a new kernel based on T560NU and
J500H MM kernel sources (J500HXXU2BPJ9 and T560NUUES1BPL1). [/B]
* [B][[COLOR="Red"]NOTE[/COLOR]][/B][B] Updated kernel and wifi driver to LA.BR.1.2.9_rb1.16[/B]
* [B][[COLOR="Red"]NOTE[/COLOR]][/B] [B] TWRP now has F2FS filesystem support [/B]
* [B][[COLOR="Red"]NOTE[/COLOR]][/B] [B] TWRP has USB OTG support integrated for external usb peripherals
(should work for vfat, exfat, ext4 or f2fs-format peripherals).[/B]
Known Issues
Code:
[COLOR="RoyalBlue"][B]All devices[/B][/COLOR]
[LIST]
[*] [B][[COLOR="Red"]ALL[/COLOR]][/B] [B] None. [/B]
[/LIST]
FAQ
Q: Are you taking device requests?
A: If you're willing to buy me/donate the device for testing, sure.
Click to expand...
Click to collapse
XDA:DevDB Information
[UNOFFICIAL][RECOVERY]TWRP 3.1.x for Grand Prime SM-G530M/MU/FZ/P/T/T1/W, Tool/Utility for the Samsung Galaxy Grand Prime
Contributors
vince2678
Version Information
Status: Stable
Created 2017-05-15
Last Updated 2017-05-29
Vince at the end update it in variant FZ, well for your work, thank you genius
---------- Post added at 06:01 PM ---------- Previous post was at 05:56 PM ----------
Just a question, the backups that I have made with the j6 version serve me now after updating, Thank you very much for the information
Fz: Aroma packages not work
aurelio.9581 said:
Fz: Aroma packages not work
Click to expand...
Click to collapse
Peak and nano if, problem is in device
---------- Post added at 10:00 PM ---------- Previous post was at 09:58 PM ----------
Install rom, backup, root zip
docrates1975 said:
Peak and nano if, problem is in device
Click to expand...
Click to collapse
Nano works for me,only aroma not works
aurelio.9581 said:
Nano works for me,only aroma not works
Click to expand...
Click to collapse
Because putting more garbage on your device, I do not get it
What improvements has the new construction j6?
docrates1975 said:
What improvements has the new construction j6?
Click to expand...
Click to collapse
F2FS, as well as whatever the TWRP 3.1.1-0 comes with (not sure).
vince2678 said:
F2FS, as well as whatever the TWRP 3.1.1-0 comes with (not sure).
Click to expand...
Click to collapse
I already tried, I'm back to building j3 , I commented that it does not start the system from the recovery, directly goes out, and press power twice to start, the first time you press power, it only shows the amount of battery you have, And in the second if you start the system, that's why I went back to building j3.
vince Already corrected in j8 the problem that I comment, Thank you
I tell you, because the j3 is no longer to download
vince, Updated to # 8 or 3.1.1, all good, thanks for your work
Vince, when backing up it is normal to have 2 boxes for system, 2 for data, being 1 external data, 2 system, 1 of start, 2 of cache and this is not the one efc and when making the copy say that external data is included, and since the recovery does not start it only goes off and you have to start from the power button
docrates1975 said:
Vince, when backing up it is normal to have 2 boxes for system, 2 for data, being 1 external data, 2 system, 1 of start, 2 of cache and this is not the one efc and when making the copy say that external data is included, and since the recovery does not start it only goes off and you have to start from the power button
Click to expand...
Click to collapse
Yes, it's completely normal.
vince2678 said:
Yes, it's completely normal.
Click to expand...
Click to collapse
And because the system does not start with recovery? And does not modify the partitions of the mobile when you install a backup with 2 copies of the system, 2 data with the same size? And because there is no option to copy the efs? I think it's an important copy too. And sorry for my maybe silly questions
odin says pass but no twrp recovery
Recovery is not taking, downloaded the right one for my phone which is SM-G530P. ODIN gives a pass but no cigar on the recovery just boot loop, have i missed a step in the process...? Also have root running stock with latest update lolipop, usb debug and bootloader unlocked
kitogh said:
Recovery is not taking, downloaded the right one for my phone which is SM-G530P. ODIN gives a pass but no cigar on the recovery just boot loop, have i missed a step in the process...? Also have root running stock with latest update lolipop, usb debug and bootloader unlocked
Click to expand...
Click to collapse
When installing with odin uncheck the box of auto reboot, And when you say odin pass you remove the battery and start with power button, to see if this works for you
docrates1975 said:
When installing with odin uncheck the box of auto reboot, And when you say odin pass you remove the battery and start with power button, to see if this works for you
Click to expand...
Click to collapse
Took out the battery after pass in Odin, disconnected usb cable reinserted battery and tried button combo for recovery samsung grand prime logo comes up with set warranty bit:recovery in left top corner in yellow and loops until i release button combo... No stock recovery now also but i can boot system and phone works ok no recovery at all.
kitogh said:
Took out the battery after pass in Odin, disconnected usb cable reinserted battery and tried button combo for recovery samsung grand prime logo comes up with set warranty bit:recovery in left top corner in yellow and loops until i release button combo... No stock recovery now also but i can boot system and phone works ok no recovery at all.
Click to expand...
Click to collapse
To ignore the yellow letters, After installing the recovery as I said Start the system and then go to recovery, And must enter by pressing volume more, power and home at the same time Pressing the 3 buttons release when the yellow letters come out, Must install since I did so and with the install lineageos 14.1
docrates1975 said:
To ignore the yellow letters, After installing the recovery as I said Start the system and then go to recovery, And must enter by pressing volume more, power and home at the same time Pressing the 3 buttons release when the yellow letters come out, Must install since I did so and with the install lineageos 14.1
Click to expand...
Click to collapse
OK I'll give it another try...
kitogh said:
OK I'll give it another try...
Click to expand...
Click to collapse
Nope no joy... Tried the recovery for the SM-G530P that's posted on this thread but it will not take to my device which is a sprint phone SM-G530P running lollipop 5.1.1. I also downloaded a twrp recovery from lineage for the grand prime called twrp-3.1.1-0-fortuna3g.img.tar this did take to my phone but I've got no touch or way to control this recovery. What next ? Drop kick it into my neighbors garden... Are these tar files posted here?? Why wont they take to my device and the one from lineageos yes. I might need Sherlock to solve this mystery. If anyone can help out thanks in advance.
Introduction
Hello everyone! In the past few days, I was approached by a few people wanting to know the steps I take to successfully flash a ROM as a secondary ROM in MultiROM. Since there seems to be many people interested in trying out new ROMs while still keeping their daily-driver primary ROM untouched, I decided to make this thread for those interested. The following is a tutorial to modify a TWRP flashable ROM zip to make it compatible with MultiROM and then flashing it as a secondary ROM. Let's get straight to it then!
Compatibility
Device(s)
OnePlus 5
ROM(s)
Mostly All ROMs (in theory, at least, hence mostly)
Android Version(s)
Android Nougat 7.x.x
Android Oreo 8.x.x
Prerequisites
Basic knowledge about TWRP flashing, fastboot flashing, zip editing, MultiROM usage, etc.
A working fastboot interface on your computer
Zip-editor installed on your computer (I prefer Bandizip)
Unlocked bootloader (how-to guide here)
Unencrypted/decrypted system (how-to guide here)
Steps To Follow
Step 1: Create a new folder on desktop (or wherever you prefer) and download the following stuff in it:
The flashable ROM zip that you wish to modify to use a secondary ROM in MultiROM
update-binary.zip (attached at the end of this post)
The latest MultiROM recovery and MultiROM zip (available here)
An updated copy of the latest SuperSU (available here)
Step 2: Extract the update-binary.zip file after which you will get the modified update-binary file that we have to use
Step 3: Open the downloaded ROM zip in the zip program that you use and inside it, navigate to META-INF\com\google\android
Step 4: Delete the existing update-binary that you see there and replace it with the update-binary that you extracted in step 2
Step 5: Save the modified zip (this is now the modified ROM zip that can be flashed as a secondary ROM via MultiROM)
Step 6: Copy the modified ROM zip, the SuperSU zip and the MultiROM zip that you downloaded in step 1 to your phone's internal storage
Step 7: Reboot your phone to the bootloader mode and connect it to your computer
Step 8: Open command prompt and navigate to the folder where you've downloaded the MultiROM TWRP image file
Step 8: Run the following command to flash MultiROM TWRP to your phone's recovery partition:
Code:
fastboot flash recovery TWRP_multirom_cheeseburger_20170919-03.img
Step 10: Once the flashing is successful, reboot to the bootloader mode again using the command:
Code:
fastboot reboot-bootloader
Step 11: Press the volume down button until you see "Recovery mode" on your phone's screen and then press the power button to boot to recovery
Step 12: Once you're in the recovery mode (running MultiROM TWRP), flash the MultiROM zip first and then reboot your phone to recovery
Step 13: Once the phone has rebooted to the recovery mode, open the MultiROM menu (three parallel horizontal lines on the top right of your phone's screen) and click on the "Add ROM" option
Step 14: Select the modified ROM zip and flash it (choose the "internal memory" option if it prompts for a partition to flash the secondary ROM in)
Step 15: Once done, hit back to open the MultiROM menu, then click on the "List ROMs" option and select the ROM that you just installed
Step 16: Once you select the ROM that you just installed, select the "Install Zip" option and flash the SuperSU zip
Step 17: Once the SuperSU zip is flashed, reboot your phone to system and you will notice a new selection menu is now displayed before the phone boots into the system
Step 18: Select the new ROM that you just flashed as the secondary ROM to boot to it
Step 19: The phone will bootloop a couple of times - DON'T WORRY, THIS IS NORMAL AFTER FLASHING SUPERSU - and in between the reboots if you see the ROM selection menu appear again, just select the newly flashed ROM and let it continue
Step 20: It should boot into your secondary ROM after a couple of bootloops/reboots!
Disclaimers
You are doing this at your own risk. 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 are unsure of how to go about something. Also, please don't forget to make a full nandroid backup via TWRP in case anything goes wrong.
The above method works for me 99% of the time, but there are a few ROMs that I wasn't able to boot as secondary no matter what I tried. If a ROM doesn't boot as secondary for you using the tutorial above, I'll try my best to help you, but I may or may not succeed.
I haven't tried the above method with Magisk instead of SuperSU. If you wish to try, feel free to do so at your own risk.
Flashing of the secondary ROM will most probably corrupt your primary ROM's password/pin (if you have one setup). If you can't get into your primary ROM after flashing the secondary ROM using your password/pin, flash this zip in TWRP which will remove your lockscreen security settings (but won't touch your fingerprints, if you have any setup).
Thanks To
@martinusbe for adapting MultiROM (recovery, installer zip, manager application, uninstallation zip) to OnePlus 5
@Chainfire for SUperSU and all the work he's ever done for the community
All of you guys for viewing this thread
Changelog
December 26, 2017 - Initial post
OP Update Information
Created: December 26, 2017
Last Updated: December 26, 2017
@shadowstep This will be very useful to many people. Merry Christmas to you
SlyUK said:
@shadowstep This will be very useful to many people. Merry Christmas to you
Click to expand...
Click to collapse
Thanks! I hope so too. Merry Christmas to you too!
P.S. - I tried the above method with Liquid Remix 8.0 and Dirty Unicorns 12.0, worked fine for me.
shadowstep said:
Thanks! I hope so too. Merry Christmas to you too!
P.S. - I tried the above method with Liquid Remix 8.0 and Dirty Unicorns 12.0, worked fine for me.
Click to expand...
Click to collapse
Nice... speaking of Dirty Unicorns. Here is an update today.
SlyUK said:
Nice... speaking of Dirty Unicorns. Here is an update today.
Click to expand...
Click to collapse
Yes, I follow them on Google+. Read the announcement sometime back. I compile my personal, unofficials builds of DU 12, so have already gotten a sneak peek.
shadowstep said:
Yes, I follow them on Google+. Read the announcement sometime back. I compile my personal, unofficials builds of DU 12, so have already gotten a sneak peek.
Click to expand...
Click to collapse
Oh well thats fantastic. DU Oreo should be amazing once unleashed, i'm sure.
Thanks, but can I have official Oreo in primary rom and an other rom in secondary?
Garfanki said:
Thanks, but can I have official Oreo in primary rom and an other rom in secondary?
Click to expand...
Click to collapse
Should work, yes. I tested the steps with a Nougat primary ROM and an Oreo secondary ROM; worked fine. So the setup you're looking for should also work. Give it a shot!
Ok thanks, I will try!
shadowstep said:
Should work, yes. I tested the steps with a Nougat primary ROM and an Oreo secondary ROM; worked fine. So the setup you're looking for should also work. Give it a shot!
Click to expand...
Click to collapse
can i use magisk instead of supersu ?
kimikim0 said:
can i use magisk instead of supersu ?
Click to expand...
Click to collapse
Already mentioned this in the OP (Point 3 under Disclaimers). I haven't tested the method with Magisk in place of SuperSU.
This is because when I was initially trying to figure all this out, most of the stuff that I was going through pointed out that Magisk wasn't doing too well with the secondary ROM and hence I just chose SuperSU; didn't even bother testing Magisk when SuperSU worked fine.
If you wish to test, go for it. Should do no harm.
kimikim0 said:
can i use magisk instead of supersu ?
Click to expand...
Click to collapse
iirc magisk scripts won't run on secondary rom installation ( twrp multirom or dual boot patcher ) will give you errors and nothing will happen
Sent from my OnePlus 5 using XDA Labs
primary system can't boot when i flash multirom zip file into oos oreo as primary,and for other 8.0 roms as primary,secondary 8.0 roms boot with primary system,same like dual boot patcher,only work with gzosp based 8.0 roms as secondary
billsz said:
primary system can't boot when i flash multirom zip file into oos oreo as primary,and for other 8.0 roms as primary,secondary 8.0 roms boot with primary system,same like dual boot patcher,only work with gzosp based 8.0 roms as secondary
Click to expand...
Click to collapse
I haven't tested the method with OOS 5.0 Oreo as my primary ROM. When I last tested, I was running a custom Nougat based ROM (AOSiP) and with that I tested multiple Oreo based custom ROMs (after modifying them, of course, as mentioned in the tutorial) as secondary ROMs and they all worked fine. Not to mention, of course, that if you don't modify the ROM zip files with the updater-binary file I attached in the OP, then it just won't work.
I would like to have os stable Oreo as primary ROM and other Oreo build as secondary ROM, but the installation of secondary rom fails... Why? Is not possibile have 2 ROMS with Oreo?
Any help?
Garfanki said:
Any help?
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=74636311&postcount=702
Actually, after Oos Oreo 8.0 upgrade, primary via MultiROM.zip won't boot anymore; there were 2 evolutions since OP5 'old' multirom:
1-Magisk support for 2nd roms
2-Encryption support for 2nd roms WITH rebranded data/media/0/multirom directories
I tried rebuilding both : 1) doesn't boot (like 'old'), and 2) boots primary via latest Multirom, BUT 2nd always reboot to recovery, despite working installation files (Magisk/sparse img or not) and decrypted device.
Also, OP5 adbd never worked for MultiROM neither log. So waiting for a skilled (new un-/encryption Oreo status) dev to follow AdrianDC sd820 latest MultiROM : https://github.com/XperiaMultiROM/android_device_sony_dora/tree/master/multirom , considering that there is no working MultiROM for any sd835 yet...
(Kexec-ed kernel would even be better...)
Most powerful is EFIdroid due to our new bootloader edk2, but here: dev/bricks are unrecoverable...
The 'funky' thing is that I got intermediate 1) working 100%, for antic p880 device with Magisk/sparseImg support ok for 2nd roms.
Thank you, so I must wait... Happy New Year!
oF2pks said:
https://forum.xda-developers.com/showpost.php?p=74636311&postcount=702
Actually, after Oos Oreo 8.0 upgrade, primary via MultiROM.zip won't boot anymore; there were 2 evolutions since OP5 'old' multirom:
1-Magisk support for 2nd roms
2-Encryption support for 2nd roms WITH rebranded data/media/0/multirom directories
I tried rebuilding both : 1) doesn't boot (like 'old'), and 2) boots primary via latest Multirom, BUT 2nd always reboot to recovery, despite working installation files (Magisk/sparse img or not) and decrypted device.
Also, OP5 adbd never worked for MultiROM neither log. So waiting for a skilled (new un-/encryption Oreo status) dev to follow AdrianDC sd820 latest MultiROM : https://github.com/XperiaMultiROM/android_device_sony_dora/tree/master/multirom , considering that there is no working MultiROM for any sd835 yet...
(Kexec-ed kernel would even be better...)
Most powerful is EFIdroid due to our new bootloader edk2, but here: dev/bricks are unrecoverable...
The 'funky' thing is that I got intermediate 1) working 100%, for antic p880 device with Magisk/sparseImg support ok for 2nd roms.
Click to expand...
Click to collapse
Good evening, I try to flash flyme rom (downloaded by chinese forum) as secondary rom but the installation fail... Any idea?
Error 7
Can I flash xXx rom as secondary? or does it only work with lineage os based roms?
I am not responsible if you brick your device installing this ROM, you are installing this at your own risk.
Downloads
Mod Edit: DL links removed.
Create device backup first:
1. 1. Boot TWRP/OrangeFox by pressing Bixby+VOL_UP+PWR as you are booting your device.
2. Go tho the backup tab of TWRP/OrangeFox
3. Backup Data, System, Cache, Boot, and System Image
4. Then backup the TWRP/Fox folder on your device to your computer just in case anything goes wrong.
How to install:
1. Boot TWRP/OrangeFox by pressing Bixby+VOL_UP+PWR as you are booting your device.
2. Go do the wipe tab of your recovery of choice, and wipe; DATA, CACHE, SYSTEM, and DALVIK CACHE.
3. Then flash the ROM you copied over to your device, or flash the ROM via ADB, it is up to you.
Reboot and enjoy!
Credits:
Thanks to the arrow-devices github community for the device sources for the S9 series of devices: Their Github Page
Samsung vendor (credit: Synt4x.93 (XDA) Synt4x93 (Github))
Galaxy S9 Plus device tree
Galaxy S9 device tree
Galaxy *9 Series kernel (credit: Synt4x.93 (XDA) Synt4x93 (Github))
Galaxy *9 Series common tree (credit: Synt4x.93 (XDA) Synt4x93 (Github))
Huge thanks to Baddar90 for fixing the battery drain issue this rom was having.
The fix source code: here
His Github: here
Gapps: (credits of the Flame Gapps Team. (Their website)
1.To flash Gapps first download Flame Gapps from here (full gapps package), here (basic gapps package)
2.Then boot TWRP/OrangeFox with the above method.
3. Find the Gapps zip you downloaded, tap on it, and swipe to flash.
4.Reboot and you should have Gapps!
How to get the out of box google setup experience when flashing Gapps (recommended):
1.After flashing the ROM reboot the device once to make sure the ROM boots.
2. On the home screen enter the power menu and then tap on "Reboot" then "Recovery.
3. Once your phone is in the custom recovery of choice, wipe the data partition.
4. Then flash Gapps again.
5. Reboot and you should have access to the the Gapps out of box setup experience!
For those of you who want to use MicroG I will not be covering it here. But the NoGoolag Telegram group as well as r/Privacy on Reddit should be able to help you if you would like to take that route.
r/privacy
NoGoolag Telegram Group
Other Telegram Groups:
(If you would like a Kernel that can help improve battery life you can ask about it here)
P.S Xtended is a great ROM, but it does have a few more bugs than other custom ROMS may have. Not enough to cause any issues but enough for you to notice the occasional hiccup here and there. This ROM is great for people who like A LOT of customizability though. By the way, bur is alos broken to and their is nothing I can do about that sorry. I'd recommend going to Display-Enable Blurs, and toggle it to off. After a device reboot at least you will get some transparency.
I hope you like it!
Also tell me if the ROM works on your S9 Plus as I can then remove that "Untested" badge from it.
Thread closed.
{
"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"
}
Awaken OS for Redmi 7/Y3 [onclite]
#include <std_disclaimer.h>
/*
* Your warranty is void. Or...Valid? Probably?
*
* Project Awaken and its maintainers are not responsible for bricked devices,
* dead SD cards, data loss, thermonuclear war, or economic crisis caused by
* Awaken OS. YOU are choosing to make these modifications, and if you
* point your finger at me for messing up your device, I will laugh at you.
*/
Click to expand...
Click to collapse
Born different, Now Awaken
Awaken OS brings consistent, fluent, and smooth experience with all your must-have customizations, for you, for the community, and everyone.
- Project Awaken -
Saikiran
Ninad Patil [REIGNZ]
Mukul [undead]
- Designers -
Hugwalk
Jagadish
Glitch
Find me on Telegram! @tech_rom
Awaken OS 2.6 Device Changelogs
You may have a login problem in GApps, So that's why I have provided you with Vanilla Build ( ROM Side )
First Time Install / Clean Flash
1. Download the proper flashable ZIP for your device
2. Reboot to Recovery
3. Wipe Cache / Data / System
4. Flash ROM
5. Flash Gapps (optional)
6. Flash Magisk (optional)
7. Reboot to System and #beAwakened
Update / Dirty Flash
1. Download the proper flashable ZIP for your device
2. Reboot to Recovery
3. Flash ROM
4. Wipe Cache
5. Reboot to System and #beAwakened
Download Here / GApps / ScreenShots ( Use Telegram )
Reach Us
Official Channel / Official Discussion
AwakenOS Official
Official Announcement / Official Community
Social Media - Tech Rom
Youtube / Telegram
Awaken Source Code
Rom Source / Github
Changelog:
• Initial Android 12.1 Rebase
• April Security Patch
• Pixel 6 Pro April Build Fingerprint
• Import XiaomiParts from sdm845-common
• Enable F2FS user data
• Enable vibration multiple intensities
• Don't write binary XML files
Redmi 7/Y3 Onclite Project
Device Source / Kernel Source / Vendor Source
ROM Version: Android 12.1 - Eclipse 2.6
ROM Kernel: Linux 4.9.287
Based On: AOSP
Release Type: Stable
I updated your Rom. no matter the pure installation or dirty installation, they are all stuck in the boot screen and can not fully enter the system. Why is this? Would you please teach me?
Also, my red rice 7 works well in your version 2.1!
雪獒2021 said:
I updated your Rom. no matter the pure installation or dirty installation, they are all stuck in the boot screen and can not fully enter the system. Why is this? Would you please teach me?
Click to expand...
Click to collapse
Dude it’s a F2FS format
Just install awaken 2.2 as well you know
Then go to settings and select manage partition
Follow guide
1. Open manage partition
2. Click on data
3. Now change your data partition
4. Select F2FS and swipe
5. After complete, reboot now
Aniket Pro said:
Dude it’s a F2FS format
Just install awaken 2.2 as well you know
Then go to settings and select manage partition
Follow guide
1. Open manage partition
2. Click on data
3. Now change your data partition
4. Select F2FS and swipe
5. After complete, reboot now
Click to expand...
Click to collapse
Hello! Is your version 2.1 and 2.2 in f2fs format? I use the official twrp to install version 2.1 according to your tutorial. Whether it is dirty or pure, it works well. However, version 2.2, whether pure installation or dirty installation based on version 2.1, will be stuck in the boot screen and cannot enter the system!
雪獒2021 said:
Hello! Is your version 2.1 and 2.2 in f2fs format? I use the official twrp to install version 2.1 according to your tutorial. Whether it is dirty or pure, it works well. However, version 2.2, whether pure installation or dirty installation based on version 2.1, will be stuck in the boot screen and cannot enter the system!
Click to expand...
Click to collapse
Join my telegram dude i will give you proper guide
Aniket Pro said:
加入我的电报伙伴，我引导你适当的指导
Click to expand...
Click to collapse
Aniket Pro said:
Join my telegram dude i will give you proper guide
Click to expand...
Click to collapse
Thank you for your invitation. I don't understand English. I communicate with you here with the help of Google translation. The telegram doesn't have Chinese. I can't communicate with you. I'm sorry!
Aniket Pro said:
Join my telegram dude i will give you proper guide
Click to expand...
Click to collapse
Today, I tried other Android 12 threads of Hongmi 7 on XDA, which can run smoothly. Only your version 2.2 can not be installed and run smoothly. What did I do wrong?
雪獒2021 said:
Thank you for your invitation. I don't understand English. I communicate with you here with the help of Google translation. The telegram doesn't have Chinese. I can't communicate with you. I'm sorry!
Click to expand...
Click to collapse
I can understand your problem and I will try to guide you right here
Many people will think that why I have created f2fs build but would like to tell everyone that your recovery encryption problem will be fixed inside this build
First of all you have to follow some steps which is most important for you and can get your rom boot up
1. First of all format your device
2. After that click on advance in which you will see dalvik,cache,system,data,vendor fix all these and swipe to clear
3. After complete reboot your device in recovery again ( reboot - recovery)
4. When your device is in recovery mode again you have to flash Awakener 2.2 rom
5. After completion of flashing you do not have to reboot your device but go to the bag and format your device again by typing yes
6. After completing, you have to go to the recovery settings, where you will see Manage Partition
7. After clicking on manage partition, you will see the data option, after clicking on the data, the last option will be change fs or change format
8. After clicking on that option, there will be an option f2fs, you just have to click on it and swipe, after completing everything, you have to reboot your device and your device will take the boot up
Hope you will get proper knowledge
Bro boot looping after updating rom
Aniket Pro said:
I can understand your problem and I will try to guide you right here
Many people will think that why I have created f2fs build but would like to tell everyone that your recovery encryption problem will be fixed inside this build
First of all you have to follow some steps which is most important for you and can get your rom boot up
1. First of all format your device
2. After that click on advance in which you will see dalvik,cache,system,data,vendor fix all these and swipe to clear
3. After complete reboot your device in recovery again ( reboot - recovery)
4. When your device is in recovery mode again you have to flash Awakener 2.2 rom
5. After completion of flashing you do not have to reboot your device but go to the bag and format your device again by typing yes
6. After completing, you have to go to the recovery settings, where you will see Manage Partition
7. After clicking on manage partition, you will see the data option, after clicking on the data, the last option will be change fs or change format
8. After clicking on that option, there will be an option f2fs, you just have to click on it and swipe, after completing everything, you have to reboot your device and your device will take the boot up
Hope you will get proper knowledge
Click to expand...
Click to collapse
Hello, I'm disturbing you again! I can't do the sixth point you wrote. I can't find the option to manage partitions in my twrp. What should I do? I use twrp3 6.0-9. Does this version not have this option?
雪獒2021 said:
Hello, I'm disturbing you again! I can't do the sixth point you wrote. I can't find the option to manage partitions in my twrp. What should I do? I use twrp3 6.0-9. Does this version not have this option?
Click to expand...
Click to collapse
Try the orange fox recovery link: https://www.mediafire.com/file/qwzicg4vfrijcya/OrangeFox-onclite-beta%40R11.1.zip/file
Rashik lama said:
Bro boot looping after updating rom
Click to expand...
Click to collapse
First of all, you have to follow some steps which are most important for you and can get your rom bootup
1. First of all format your device
2. After that click on advance in which you will see dalvik, cache, system, data, vendor fix all these and swipe to clear
3. After complete reboot your device in recovery again ( reboot - recovery)
4. When your device is in recovery mode again you have to flash Awakener 2.2 rom
5. After completion of flashing you do not have to reboot your device but go to the bag and format your device again by typing yes
6. After completing, you have to go to the recovery settings, where you will see Manage Partition
7. After clicking on manage partition, you will see the data option, after clicking on the data, the last option will change fs or change format
8. After clicking on that option, there will be an option f2fs, you just have to click on it and swipe, after completing everything, you have to reboot your device and your device will take the boot up
Hope you will get proper knowledge
Aniket Pro said:
First of all, you have to follow some steps which are most important for you and can get your rom bootup
1. First of all format your device
2. After that click on advance in which you will see dalvik, cache, system, data, vendor fix all these and swipe to clear
3. After complete reboot your device in recovery again ( reboot - recovery)
4. When your device is in recovery mode again you have to flash Awakener 2.2 rom
5. After completion of flashing you do not have to reboot your device but go to the bag and format your device again by typing yes
6. After completing, you have to go to the recovery settings, where you will see Manage Partition
7. After clicking on manage partition, you will see the data option, after clicking on the data, the last option will change fs or change format
8. After clicking on that option, there will be an option f2fs, you just have to click on it and swipe, after completing everything, you have to reboot your device and your device will take the boot up
Hope you will get proper knowledge
Click to expand...
Click to collapse
Thanks for your help buddy . I am able to use awaken os 2.2 now
Hello, the latest (2.6) version can't log in to Google, and it doesn't work to hang a VPN. Google Suite doesn't run at all. What should I do?
Aniket Pro said:
Awaken OS for Redmi 7/Y3 [onclite]
Born different, Now Awaken
Awaken OS brings consistent, fluent, and smooth experience with all your must-have customizations, for you, for the community, and everyone.
- Project Awaken -
Saikiran
Ninad Patil [REIGNZ]
Mukul [undead]
- Designers -
Hugwalk
Jagadish
Glitch
Find me on Telegram! @tech_rom
Awaken OS 2.6 Device Changelogs
You may have login problem in GApps, So that's why I have provided you with Vanilla Build ( ROM Side )
First Time Install / Clean Flash
1. Download the proper flashable ZIP for your device
2. Reboot to Recovery
3. Wipe Cache / Data / System
4. Flash ROM
5. Flash Gapps (optional)
6. Flash Magisk (optional)
7. Reboot to System and #beAwakened
Update / Dirty Flash
1. Download the proper flashable ZIP for your device
2. Reboot to Recovery
3. Flash ROM
4. Wipe Cache
5. Reboot to System and #beAwakened
Download Here / ScreenShots ( Use Telegram )
Reach Us
Official Channel / Official Discussion
AwakenOS Official
Official Announcement / Official Community
Social Media - Tech Rom
Youtube / Telegram
Awaken Source Code
Rom Source / Github
Redmi 7/Y3 Onclite Project
Device Source / Kernel Source / Vendor Source
ROM Version: Android 12.1 - Eclipse 2.6
ROM Kernel: Linux 4.9.287
Based On: AOSP
Release Type: Stable
Click to expand...
Click to collapse
Changelog:
• Initial Android 12.1 Rebase
• April Security Patch
• Pixel 6 Pro April Build Fingerprint
• Import XiaomiParts from sdm845-common
• Enable F2FS user data
• Enable vibration multiple intensities
• Don't write binary XML files
Bugs:
• You may have a login problem in GApps, So that's why I have provided you with Vanilla Build ( ROM Side )
Changelog:
• Initial Android 12.1 Rebase
• April Security Patch
• Pixel 6 Pro April Build Fingerprint
• Import XiaomiParts from sdm845-common
• Enable F2FS user data
• Enable vibration multiple intensities
• Don't write binary XML files
Bugs:
• You may have a login problem in GApps, So that's why I have provided you with Vanilla Build ( ROM Side )
Dear brother: Is there any plan to adapt to Android 13?
Great rom bro thanks for your updates and hope you will do better again and again .