[UNOFFICIAL][ROM][A320FL/F/Y] crDroid 6.9 [10.0][64 bits][Treble] - Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re

{
"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"
}
DISCLAIMER
I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. Please do some research if you have any concerns about features included in this ROM before flashing it! YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
FEATURES
A320FL/F/Y supported
Android 10
Arm64 with Treble support
3.18.140 kernel with f2fs support and many more
Enforcing build
VNDK-Full
crDroid features
KNOWN BUGS
Encryption is bugged (dont encrypt phone)
Other inherent bugs from AOSP, LineageOS or crDroid sources
CTS profile can fail in Magisk
Volte (it never will work)
INSTALLATION
Flash the repartition script if you haven't done
Wipe system, data (clean install recommended), vendor, dalvik&cache and cache
Flash rom zip
Flash GAPPS (they can fail at first flash, but flash again)
Reboot
DOWNLOAD
Lastest build: 20/00/2020
GoogleDrive folder
GAPPS
Arm64 gapps
ROOT
Flash Magisk as usual
SUPPORT
Telegram group
SOURCES
My github org
CREDITS
Me, for infinite hours spent with this project
Special thanks to @Valera1978 for bringing this to the exynos7870
@followmsi for the upstream kernel commits
@stricted and 7870 dev team for his work in exynos source code
DONATIONS
I don't need them, I don't need coffees or beers. I really hate see here people with high end devices asking for donations, but you can still donate money to charity. Donate money or simply help people that is really needed. If you like this rom you can make me very happy just pushing THANKS
XDA:DevDB Information
crDroid 6.9, ROM for the Samsung Galaxy A Series 2017 A3, A5, A7
Contributors
Astrako
Source Code: https://github.com/crdroidandroid
ROM OS Version: Android 10
ROM Kernel: Linux 3.x
ROM Firmware Required: Oreo bootloader
Version Information
Status: Beta
Beta Release Date: 2019-12-19
Created 2019-12-19
Last Updated 2020-09-25

Reserved

Is signature spoofing enabled for microG support?

Astrako said:
Reserved
Click to expand...
Click to collapse
Good work, keep it up! ??

Nice job, this is the most stable "first release" I've ever seen!

This is the 2nd day I'm testing this ROM , it is very stable, WiFi, bluetooth, audio, camera.
Everything wotks fine. They only one issue I found a few minutes back its the sound. I was cresting a fullbackup with TWRP to my mSD, then when the phone started again a very very loud sound came from the speaker. It was a notificaction, I tried with músic an found that all kind of sound that cames from the speaker is ver y very lound and broke, even if I put the volumen at minimum.
I think this is a ver y good start for a first realease I really hope this issue gets fixed soon.
If there is a way I can help you to improve this ROM please let us kown. At least I can provide logs or something when this kind of issue happens.
Many thanks for you'r hard work @Astrako. This is one of the best ROM I have tried for this device,

IvannHylian said:
This is the 2nd day I'm testing this ROM , it is very stable, WiFi, bluetooth, audio, camera.
Everything wotks fine. They only one issue I found a few minutes back its the sound. I was cresting a fullbackup with TWRP to my mSD, then when the phone started again a very very loud sound came from the speaker. It was a notificaction, I tried with músic an found that all kind of sound that cames from the speaker is ver y very lound and broke, even if I put the volumen at minimum.
I think this is a ver y good start for a first realease I really hope this issue gets fixed soon.
If there is a way I can help you to improve this ROM please let us kown. At least I can provide logs or something when this kind of issue happens.
Many thanks for you'r hard work @Astrako. This is one of the best ROM I have tried for this device,
Click to expand...
Click to collapse
That is a hardware bug, you only need to shutdown device and will be fixed. It must be a some kind of static remaining in circuits and it happens even with stock. Only way to fix is that.

Very cool to see the phone still getting new roms. Before getting rid of my S9 Port, I was wondering, if the Android 10 iOS style gestures are supported? Since the phone has a home button, they might be disabled but I'd really prefer using gestures over the soft keys (back and recents).
Anyways, thank for the work!

Hello
I have been unable to make the rom work in my phone.
My phone model is A320FL.
The process I have followed to install the rom is the following one:
1. Install this stock A320FLXXS4CSG2_A320FLHUI4CSG1_HUI
2. Install root
3. Install twrp
4. Twrp -> Wipe -> Format data
5. Twrp -> Wipe -> Advanced wipe -> clean davlik, cache, data and system
6. Install rom and google apps open_gapps-arm64-10.0-nano-20191209-BETA.zip
The first time the google apps gave me an error indicating that the sdk version was incorrect; and when I tried to boot without installing it I wasn't able.
I have executed again the steps 5 and 6 and this time I was able to install google apps but the rom didn't boot, the phone only showed the crdroid animation.
This is the logcat of the booting of the rom the 2nd time: https://del.dog/tuzapuckuc
Regards

Looks interesting, can't wait to see if it gets to stable.

jontxo said:
Hello
I have been unable to make the rom work in my phone.
My phone model is A320FL.
The process I have followed to install the rom is the following one:
1. Install this stock A320FLXXS4CSG2_A320FLHUI4CSG1_HUI
2. Install root
3. Install twrp
4. Twrp -> Wipe -> Format data
5. Twrp -> Wipe -> Advanced wipe -> clean davlik, cache, data and system
6. Install rom and google apps open_gapps-arm64-10.0-nano-20191209-BETA.zip
The first time the google apps gave me an error indicating that the sdk version was incorrect; and when I tried to boot without installing it I wasn't able.
I have executed again the steps 5 and 6 and this time I was able to install google apps but the rom didn't boot, the phone only showed the crdroid animation.
This is the logcat of the booting of the rom the 2nd time: https://del.dog/tuzapuckuc
Regards
Click to expand...
Click to collapse
Did you install the repartition script?

Madhias said:
Did you install the repartition script?
Click to expand...
Click to collapse
Hello
Yes I installed the script just after installing TWRP. This is the complete sequence of the setup I did.
1. Install this stock A320FLXXS4CSG2_A320FLHUI4CSG1_HUI
2. Install root
3. Install twrp
4. Run the repartition script
5. Twrp -> Wipe -> Format data
6. Twrp -> Wipe -> Advanced wipe -> clean davlik, cache, data and system
7. Install rom and google apps open_gapps-arm64-10.0-nano-20191209-BETA.zip
The first time the google apps gave me an error indicating that the sdk version was incorrect; and when I tried to boot without installing it I wasn't able.
I have executed again the steps 5 and 6 and this time I was able to install google apps but the rom didn't boot, the phone only showed the crdroid animation.
Regards

jontxo said:
Regards
Click to expand...
Click to collapse
You have done two bad things:
1. Asking for support without having pushing "Thanks" button in first post of this thread. This is something very disrespectful, but I see that is a extremely bad and common behaviour in XDA.
2. You haven't format vendor partition. In the installation instructions in repartition script and this rom threads is written, but you haven't done, I guess because you haven't read the 5 steps of rom installation. Again a very bad and common behaviour in XDA.

Any chances of a a5 port? ?

People who can port the Galaxy S10 for our 3 2017? I want 10 but with Samsung chips

ysyp69 said:
People who can port the Galaxy S10 for our 3 2017? I want 10 but with Samsung chips
Click to expand...
Click to collapse
You can always learn how to do that! It's not that hard to learn new things!

Madhias said:
Did you install the repartition script?
Click to expand...
Click to collapse
Astrako said:
You have done two bad things:
1. Asking for support without having pushing "Thanks" button in first post of this thread. This is something very disrespectful, but I see that is a extremely bad and common behaviour in XDA.
2. You haven't format vendor partition. In the installation instructions in repartition script and this rom threads is written, but you haven't done, I guess because you haven't read the 5 steps of rom installation. Again a very bad and common behaviour in XDA.
Click to expand...
Click to collapse
Hello
Thanks for your help, I have managed to install the rom and everything work as expected.
The problem was that I wasn't restarting the phone after using the script to do the repartition. After that I have had also to not to install twrp before reboot.
Regards

deleted

Does this work with the A5 2017? I'm guessing not but this is the only ROM with Android 10, so I thought I'd ask if it supports it. If not, is it possible for this to be ported to the A5?

ImSmatMan said:
Does this work with the A5 2017? I'm guessing not but this is the only ROM with Android 10, so I thought I'd ask if it supports it. If not, is it possible for this to be ported to the A5?
Click to expand...
Click to collapse
It isn't for A5, posible to port? Well ask Dev!??

Related

[ROM][VNS-LX1][6.0.1][UNOFFICIAL] AICP for Huawei P9 Lite

{
"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"
}
AICP is known by everyone as Ice Cold Project that started on Desire HD and since then evolved into a mature ROM with the BEST community you can find!!!
Until Lollipop, the rom has always been AOKP based. Unfortunately, since AOKP either stopped development or will make a comeback later this year, we changed our base to CM when it comes to hardware, drivers and some features.
If there are any bugs, either we will sort them or CM team if it concerns their modifications. This rom isn't CM supported so no need to report errors or bugs to them!!
Click to expand...
Click to collapse
Code:
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*
Flash procedure:
1. Make sure that you are running my CM build or the CM build by Meticulus
2. Remove all registered fingerprints
3. Reboot into TWRP
4. Do a Factory reset
5. Flash the AICP build
6. Flash Gapps (I suggest Open Gapps,use the arm64 packages)
7. Reboot
8. Profit
DOWNLOAD
XDA:DevDB Information
AICP, ROM for the Huawei P9 Lite
Contributors
The Marionette, Meticulus, XePeleato, surdu_petru
Source Code: https://github.com/Meticulus
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.10.x
Based On: CyanogenMod
Version Information
Status: Beta
Created 2016-12-02
Last Updated 2016-12-02
Reserved
WORKING/NOT WORKING
-same as CM
Bugs?
How to delete the fingerprint
Does everything work or are there any bugs?
Raymen03 said:
How to delete the fingerprint
Click to expand...
Click to collapse
Settings > Lockscreen > Fingerprint > *Click on your registered fingerprint in the options* > Delete > *click OK*
Thijs van Hal said:
Does everything work or are there any bugs?
Click to expand...
Click to collapse
Simply put,it has the same bugs as CM(the 2.1MP cam limit and that is that?)
The Marionette said:
Simply put,it has the same bugs as CM(the 2.1MP cam limit and that is that?)
Click to expand...
Click to collapse
How about Bluetooth paring?
Care to elaborate on the difference between this and CM?
Hi,
I have a few questions:
1: Does this work on any P9 Lite variant (i have VNS-L21)?
2: Why is archive so big (almost 700mb)?
3: What Open Gapps package do you recommend to flash?
Tnx
tw1st3d ?
tw1st3d83 said:
Hi,
I have a few questions:
1: Does this work on any P9 Lite variant (i have VNS-L21)?
2: Why is archive so big (almost 700mb)?
3: What Open Gapps package do you recommend to flash?
Tnx
tw1st3d ?
Click to expand...
Click to collapse
1. Yeah,I declared the L"X"1 value to say that it is compatible with both L31 and L21.
2. AICP is "fatter" than CM since it has extra features,so no reason to panic. :silly:
3.I personally use the Pico package and then just install other Google apps which I need. That is the beauty of Open Gapps,you have several options.
Sent from my VNS-LX1 using Tapatalk
The Marionette said:
1. Yeah,I declared the L"X"1 value to say that it is compatible with both L31 and L21.
2. AICP is "fatter" than CM since it has extra features,so no reason to panic. :silly:
3.I personally use the Pico package and then just install other Google apps which I need. That is the beauty of Open Gapps,you have several options.
Click to expand...
Click to collapse
Thanks man for fast answer, the flashing will comence in the morning, i need a straight head for this ?
And sa for archive size i did not panic, just been curious because i had AICP on my galaxy s4 and it was half the size...
AICP rom is one of the best out there and it has sooo much customization options that i almost cry with happyness when i saw this post ?
And one more question: do i use ARM or ARM64 version of gapps?
Huawei P9 Lite have to use ARM64
Potato997 said:
Huawei P9 Lite have to use ARM64
Click to expand...
Click to collapse
Yeah,I thought everyone knew that...
Added it as well to the instructions! xD
@The Marionette thanks for this amazing work. There is some possibility that you can support the VNS-L23 variant? It is practically equal to the L31, with the only differences that do not have NFC support, the bands 4G are different and it has 2GB of RAM. Greetings.
Hey @The Marionette,
I flashed the ROM and i got error that data partition could not be mounted and then when i click to boot in to android the phone boots but it ask for password to start android...
What to do?
EDIT: After rebooting recovery the data partition is mounted again and i did a full wipe then flashed rom and gapps again but after boot in to android it ask for password again...
tw1st3d83 said:
Hey @The Marionette,
I flashed the ROM and i got error that data partition could not be mounted and then when i click to boot in to android the phone boots but it ask for password to start android...
What to do?
EDIT: After rebooting recovery the data partition is mounted again and i did a full wipe then flashed rom and gapps again but after boot in to android it ask for password again...
Click to expand...
Click to collapse
Someone on the question and answer thread had the same problem. See if any of his answers helps.
Sent from my Huawei P9 Lite using XDA Labs
oss_mosis said:
@The Marionette thanks for this amazing work. There is some possibility that you can support the VNS-L23 variant? It is practically equal to the L31, with the only differences that do not have NFC support, the bands 4G are different and it has 2GB of RAM. Greetings.
Click to expand...
Click to collapse
I have the L21 variant and it works fine for me. If CM works on your device,AICP will work as well.
tw1st3d83 said:
Hey @The Marionette,
I flashed the ROM and i got error that data partition could not be mounted and then when i click to boot in to android the phone boots but it ask for password to start android...
What to do?
EDIT: After rebooting recovery the data partition is mounted again and i did a full wipe then flashed rom and gapps again but after boot in to android it ask for password again...
Click to expand...
Click to collapse
Did you follow the instructions or did you do it your own way?
Are you coming from stock?
I think everyone needs to be on CM before flashing.
I flashed it exactly like I described and it booted.
The only downside is that the TWRP goes red(thinks the current ROM is stock) and data can't be mounted. I will look into it.
Sent from my VNS-LX1 using Tapatalk
The Marionette said:
I have the L21 variant and it works fine for me. If CM works on your device,AICP will work as well.
Did you follow the instructions or did you do it your own way?
Are you coming from stock?
I think everyone needs to be on CM before flashing.
I flashed it exactly like I described and it booted.
The only downside is that the TWRP goes red(thinks the current ROM is stock) and data can't be mounted. I will look into it.
Sent from my VNS-LX1 using Tapatalk
Click to expand...
Click to collapse
I followed Meticulus instructions first (did all backups and dump) and then i followed your instructions from OP but i come from stock rom, did not try to install Meticulus CM ROM... So now i managed to get past password screen by formating data partition to FAT and then formating it back to ext4 but now when phone boot i get "Decryption unsuccessful" screen and when i click "reset phone" button it reboots in recovery, wipe cache and then boots up back to "Decryption unsuccessful" screen...
I am downloading now Meticulus build to try with that... Will report back soon...
EDIT: I managed to boot AICP!!! By doing this:
First i updated recovery (did not see that Meticulus pushed V2) then i flashed Meticulus CM build but i got "Decryption failed" screen again but this time when i clicked "reset phone" buton the phone just rebooted to TWRP.
Then i did again full harcore wipe and flashed CM with open gapps and the phone booted in to system without problem, from that point i figure that AICP must work now so i rebooted back to TWRP, did another hardcore full wipe, flashed AICP with Open Gapps micro ARM64 version and the phone finaly booted to AICP :happy: :happy: :happy:
Btw i noticed few thing while doing all this... When i first booted CM my SIM card was not recognized but i figured it needs some time to get the signal or wathever but that never hapend and i cheked camera app and in setting of the app i saw that front and back camera was set to full resolution and the photo i took was really in full (13Mpix) resolution... After checking that and few more things i flashed AICP and at first boot my SIM still not working so i figure i will reboot and after second boot the SIM works again but in this ROM front and back camera are set to 2.1mpix (not a problem for me, just saying for ppl to know)...
Now i am going to play with this awesome ROM!
Thanks @The Marionette
EDIT 2: So after few hours of playing with AICP i been forced to go back to stock because my mobile network gone crazy, every 5-10 minutes it disapear and only reboot helps to get connected again and when network disapears the UI get so much lag that is almost unusable...
I can confirm that other things in ROM work as it should, fingerprint, themes, sound bar, navigation bar customization, lcd density, UI animations customizations etc...
Nice work and keep up the good work! ?
So I am running this ROM on my device since yesterday and I really like it. Seems very stable and allows for a lot of modifications.
It drains a lot of battery while listening to music when the device is locked but I also experienced this on the CM ROM.
I am keeping it on my device for now and am looking forward to new updates
Hello @The Marionette,
May I ask you if you plan to update the AICP ROM with the update from CM? Thank you

[DISCONTINUED] [ROM] Resurrection Remix 6.1.2 (Oreo) - n7000

{
"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"
}
Resurrection Remix 6.1.2 (based on Oreo 8.1.0) for Samsung Galaxy Note N7000
​
DISCLAIMER :
Code:
#include <std/disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
ROM INFO
This is unofficial source-built Resurrection Remix for Galaxy Note (n7000).
....
Yes, just simple as that. Be prepared to #GetResurrected !
*THIS ROM IS STILL IN TESTING PHASE!!!
ROM FEATURES
Probably, RROS should be the only ROM that have sooooo many features! It's too many to be listed here, really
ROM BUGS
Code:
- Display : (sometimes) During power off or reboot, it will freeze for a few seconds. Applies to Recovery Mode, Normal Android and Offline Charging.
- Camera : After every boot, Camera app needs to be launched twice then only it works. (tbc)
- Kernel : Display draining lots of battery (tbc)
This ROM is in testing phase at the moment, thus there might(should) be bugs yet to be found!
ROM INSTALLATION
*NEW USERS: Repartition system first, and install Bauner's TWRP !!!
1. Boot into TWRP (Power + Home + Volume Up)
2. If clean flash, wipe /data, /cache, /system
3. If you'd like to have f2fs, format /data (your internal SD content will be lost!) and /cache to f2fs.
4. Proceed into flashing ROM (install ZIP or sideload)
5. Proceed into flashing other ZIPs if any.
6. Reboot system. First boot takes about 10 minutes. Be patient​
SIDE NOTES
- Device assert check is not removed for the time being. You need to remove the assert checking lines from ZIP file's updater-script so that the file starts with the word ui_print
- Builds are rootless, you have the option to flash SU addon on your own.
- When rebooting from Offline Charging mode/TWRP, sometimes it will freeze (see the above ROM BUGS section). When you noticed it freeze, just let go power button and leave it, it will reboot in a few seconds. (you should able to understand this if you read the ROM BUGS section)
SOURCES
Full credits to @rINanDO (galaxys2), @bauner (n7000), @linusdan (i9100's RROS manifests reference), @benbois (former RR maintainer for n7000), Resurection Remix, LineageOS, long-lived CyanogenMod, and other n7000/i9100/smdk4x10 developers. And also @ChronoMonochrome for his help and guidance!
https://github.com/leewp14/local_manifests/tree/rr-o
XDA:DevDB Information
Resurrection Remix 6 for N7000, ROM for the Samsung Galaxy Note GT-N7000
Contributors
lee.wp14, bauner
ROM OS Version: 8.x Oreo
Version Information
Status: Testing
Created 2018-08-21
Last Updated 2019-01-20
DOWNLOADS
Builds are uploaded to my Google Drive. Click here to access.
Look under directory : n7000 > rr
*DO NOT MIRROR WITHOUT MY PERMISSION. Thank you.
CHANGELOG
Code:
[U][B]20190114[/B][/U]
- smdk4412 : iosched default to noop
- smdk4412 : implement powersuspend, thanks to @ChronoMonochrome
- n7000 : add ro.lineage.version to trick CMSU
- galaxys2-common : reconfigure zRAM
[U][B]20190111[/B][/U]
- initial build
[U][B]20190110[/B][/U]
- Initial build (internal)
I will only write changelog for tested working builds :good: try at your own risk if you want to test it before me :3
Those inside .trash folder are my test builds. Please, avoid this folder and other no changelog written build if you want to play safe. Thanks
SCREENSHOTS
Coming soon :3
Hi @lee.wp14,
Thank you, thank you.... Totally appreciate your efforts dude. I was hoping to catch this rom on some of my old relic devices, HP Touchpad, S2 and N7000. If I didn't use my N7000 as my daily driver MAIN phone, I'd be flashing right away to test and help/feedback....
But I know as soon as my rom starts playing up, and I have to wipe... I shall certainly test this as soon as I can after...
Thank you again for giving your time, and still knocking out roms... Esp, RR roms !!!
Thanks, Lister
Hi @lee.wp14,
Looks like I will be finally be able to get around to testing your rom....
My original N7000 HAS DIED, and so have ordered myself a replacement N7000. So will wipe it of it's current config when it arrives, and dive straight into this rom.... and give you my feedback.
Are you still providing updates/syncs to the latest repo's for this rom...??
Thanks, Lister
Lister Of Smeg said:
Hi @lee.wp14,
Looks like I will be finally be able to get around to testing your rom....
My original N7000 HAS DIED, and so have ordered myself a replacement N7000. So will wipe it of it's current config when it arrives, and dive straight into this rom.... and give you my feedback.
Are you still providing updates/syncs to the latest repo's for this rom...??
Thanks, Lister
Click to expand...
Click to collapse
Hi @Lister Of Smeg
It is sad to hear that.. but anyway just to inform you that I won't be continuing development on this phone anymore, it is kind of hard to develop when I didn't have a n7000 around me. Additionally, I'm quite busy for my public examinations lately. And my knowledge in android development is little to nothing, it will be time consuming to develop on an old device which requires lots of workarounds, cherrypickes and patches.
I thank you for your support in my development! I hope that I will be able to get a n7000 in future, and maybe I will try to develop for this phone if my time allows. Currently I'm using an old Samsung S Advance... quite disappointing, can't even get nougat running properly on this phone. But at least it has an AMOLED screen...
Hi @lee.wp14,
Aye, you're telling me... I'm more annoyed that the death of the Note came out of nowhere... There was no symptoms leading up to it, no strange behaviour. Other than woke one morning to find it had rebooted and stuck on the Splash screen. Thought nothing of it, and rebooted it again as it was stuck on the Samsung N7000 screen. Then after that, it's been no more...
More so, as didn't get chance to back any data stored locally on the device, as it's not detected in Windows. It appears a common issue, affecting a lot of Samsung models... But most talk about it on YouTube, and all fixed theres...
Still, I've ordered myself another N7000 replacement (I hope it's in as good a condition as mine was...) and fully working. I have so many roms for this phone, and wouldn't know which phone to get next if needs be. Purely sentimental reasons, I don't wish to change my Sim or phone number, as it's the original one Ive ever had, since getting my first mobile phone back in the 90's (a long time!!) lol.
I fear if this Note goes (I still have some S2's, that it would work on) I will be forced to move to Micro or Nano Sim.. lol
Anyway, no worries mate... Thank you for letting me know. And much appreciated, all your efforts up till now. You've knocked out and provided some damn good roms... Esp dedication towards the RR roms. You claim your knowledge is little to none, but don't be so hard on yourself. You've managed to release some roms, and patches, and thats MORE THAN ANY OF US CAN DO !!!
Thanks again, for all you done so far... Good luck with your exams !! :good::good: and who knows, hopefully in the future, you maybe back again... with an N7000
Once my replacement arrives, I will be sure to let you know about the Oreo RR rom....
Thanks again, Lister...
lee.wp14 said:
Hi @Lister Of Smeg
It is sad to hear that.. but anyway just to inform you that I won't be continuing development on this phone anymore, it is kind of hard to develop when I didn't have a n7000 around me. Additionally, I'm quite busy for my public examinations lately. And my knowledge in android development is little to nothing, it will be time consuming to develop on an old device which requires lots of workarounds, cherrypickes and patches.
I thank you for your support in my development! I hope that I will be able to get a n7000 in future, and maybe I will try to develop for this phone if my time allows. Currently I'm using an old Samsung S Advance... quite disappointing, can't even get nougat running properly on this phone. But at least it has an AMOLED screen...
Click to expand...
Click to collapse
Hi @lee.wp14,
Do you happen to have a new link for the download, as i cant see that rom on the link provided??
Many thanks, Lister
Thread closed by OP request
Thread re-opened.
Camo.
EDIT : some cleaning works...
EDIT : some cleaning works...
Initial Public Build 20190111
Refer OP for more *detailed* information. Downloads at second post.
*****This is different with the one I uploaded earlier this morning (yes the file names are the same). You can identify by the file size. This latest build has a smaller file size (check the file size in bytes so that you won't get it wrong). This latest build is uploaded around 8PM at UTC+8 while the earlier one is uploaded around 2AM UTC+8 (it is now in the .trash folder).
Build works pretty well as for now, but anything could happen - DO NOT FLASH IF YOU'RE NOT DARE TO RISK.
*you need to remove assert lines to install this build in TWRP, Google search if you don't know how to.
*it is actually the first line inside META-INF/com/google/android/updater-script. Remove it and replace the file inside the one in the zip.
*you need to get some little extra free space for /system if you want to install GAPPS (pico only!). Alternatively, you can repartition your /system to make it larger than 1GB, using REPIT. You can also remove GoogleTTS inside the opengapps pico zip file (edit the installer.sh, remove the line under pico_gapps_list=)
*please do not use your note 1 when charging. by then it is not charging but draining instead.
*button backlights are disabled. Feedback me if you guys need the button lights (I find them ugly tho)
*enable usb functions under Settings > Connected Devices
*camera needs to open twice after every boot. I haven't check into this yet because I'm quite tired today. However this only happens to my current installation, and I don't think I made changes related to camera in this build. So I need someone to confirm this.
EDIT : some cleaning works...
I will flash it too. Currently on Bauners 15.1 v3.
After about one week of testing, here is a fairly usable RR Oreo build for n7000...
Notable changes :
- No more battery drain during deepsleep and Wifi turned on
- Internal SU management working. Flash Lineage's SU addon to get root.
Notes :
- Screenshot uploaded to second post! (Not yet I'm quite busy lately)
- Phone is draining quite a lot of power when screen is on (not sure, as my previous phone has better battery life, and I'm not get used to n7000's power consumption yet)
- To install GAPPS, refer to post #12 for information on how to install. Or, you can repartition your /system to >1GB
Hi lee.wp14,
This rom will have the possibility to autoboot when power is plugged in to the phone?
Thanks
khrisstyan said:
Hi lee.wp14,
This rom will have the possibility to autoboot when power is plugged in to the phone?
Thanks
Click to expand...
Click to collapse
No. If you require this will need modification to the kernel ramdisk.
lee.wp14 said:
No. If you require this will need modification to the kernel ramdisk.
Click to expand...
Click to collapse
Thanks for the quick reply.
Can you patch the rom with this modification?
PS: the rom is 8.0 or 8.1 ? I want to know what version of gapps to download.
Thank you
khrisstyan said:
Can you patch the rom with this modification?
Click to expand...
Click to collapse
Not really, I don't see it necessary.
PS: the rom is 8.0 or 8.1 ? I want to know what version of gapps to download.
Thank you
Click to expand...
Click to collapse
8.1.0
Be noted that even pico gapps is unable to install. You need to exclude GoogleTTS from the installer or resize /system to >1GB
lee.wp14 said:
Not really, I don't see it necessary.
Click to expand...
Click to collapse
That would be nice to have, maybe another rom with this option activated.This is the only thing stoping many of us to use the Note permanently in the car.
lee.wp14 said:
8.1.0
Be noted that even pico gapps is unable to install. You need to exclude GoogleTTS from the installer or resize /system to >1GB
Click to expand...
Click to collapse
System is already resized to 1.5gb , using RR Nougat in this moment.
Maybe I will flash it tomorrow and come with a feedback.

[ROM][J530X] H-ROM S20 PORT V2.0 [10.0][OneUI 2.1][64 bits][Treble]

{
"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"
}
DISCLAIMER
I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. Please do some research if you have any concerns about features included in this ROM before flashing it! YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you
I've put a huge amount of time and effort in this SOLO project (no other dev has been involved), so respect me and respect my work. You are NOT allowed to use this rom, its vendor or any of the other files included as base for your projects. You are only allowed to fix the bugs for your variant and I will post here.
FEATURES
OneUI 2.1 under Android 10, ported from the Samsung Galaxy S20 5G (SM-G981B)
All J530 variants should be supported
Arm64 with Treble support
Fully deodexed
H-KERNEL included. Built permissive and overclocked
Deknoxed, debloated, and removed all samsung useless security stuff in rom and kernel level
S10 CSC with additional features (call recording, etc)
And many more!
COMMON KNOWN BUGS
Updating camera app from Samsung App Store will break it
Light in capacitive buttons
Face unlock (most likely never will work on this port)
Camera on live drawing
Some 3rd camera apps like footej don't work
Back camera video only supports 16:9, others will give errors
Other inherent bugs from OneUI and/or 7870 limitation
You tell me
DOWNLOAD
Current version: 2.0 (14/07/2020)
More info in 2nd post
INSTALLATION
Installer will detect right variant and flash proper files
Vendor partition is required
Wipe system, data (clean install mandatory), vendor, dalvik&cache and cache
Flash rom zip
Reboot
Once set, go to screen settings, set fullhd resolution and set back hd
SCREENSHOTS
https://imgur.com/a/j7Pk3Rd
ROOT
Flash Magisk canary. Stable Magisk will give bootloop.
SUPPORT
Telegram group
CREDITS
Me, for infinite hours spent with this project
Special thanks to @ananjaser1211, @SPARTANICUS and @Valera1978 for their huge contribution to the 7870 development
@topjohnwu for Magisk
DONATIONS
I don't need them, I don't need coffees or beers. I really hate see here people with high end devices asking for donations, but you can still donate money to charity. Donate money or simply help people that is really needed. If you like this rom you can make me very happy just pushing THANKS
XDA:DevDB Information
H-ROM S20 PORT, ROM for the Samsung Galaxy J5
Contributors
Astrako
Source Code: https://gitlab.com/android_samsung_universal7870/common/android_kernel_samsung_exynos7870/-/tree/oneui_q
ROM OS Version: Android 10
ROM Kernel: Linux 3.x
ROM Firmware Required: Oreo bootloader
Version Information
Status: Stable
Current Stable Version: 1.0
Stable Release Date: 2020-07-14
Created 2020-07-14
Last Updated 2020-07-15
H-ROM S20 PORT V2.0 (14/07/2020)
July security patch
Added some new camera modes thanks to @neel0210
Added bloat zip containing several Samsung apps for those with larger system partitions. Feel free to debloat it by yourself according your needs. It will get install by default when flashing the rom zip for the A3 and the J6
GoogleDrive folder
Mega folder
Remember, a lot of time has been put in this project. If you like it and want to support me, no donations at all are required, just pushing thanks buttons.
reserved
mine too
And Here you GO!!!!!!!!!!!!1
Astrako said:
H-ROM S20 PORT V2.0 (14/07/2020)
July security patch
Added some new camera modes thanks to @neel0210
Added bloat zip containing several Samsung apps for those with larger system partitions. Feel free to debloat it by yourself according your needs. It will get install by default when flashing the rom zip for the A3 and the J6
OneDrive folder
GoogleDrive folder
Mega folder
Remember, a lot of time has been put in this project. If you like it and want to support me, no donations at all are required, just pushing thanks buttons.
Click to expand...
Click to collapse
The most awaited moment #stable_ARM64_Q, Another Great Project sar
I was waiting for it, thank you astrako. But i have a big problem, when I install it with the vendor it drops me an error 7 creating symlinks, but if I install it whithout the vendor, the installation finish successfully but instead of booting the system, bootloader screen appears. Please HELP ME ?
Ok I have fix the problem and the system works. But know I have another one, and its that the phone doesn't detect sim card and there's no imei. Please Help.
I already flashed and so far so good!. This is my recipe to flash that it worked for me with no errors.
1.- You must have a Vendor partition, if you don't have it, look for "Project SpagetX" on this thread and follow instructions (you must read and read, that's the key), you must flash (TWRP) "Exynos7870_CreateVendor.zip"
https://forum.xda-developers.com/ga...t/treble-projecttreble-v1-0-jxy17lte-t3929286
2.- Once you have flashed Vendor reboot to Recovery
3.- Wipe Cache, Dalvik, Data, System
4.- Flash the ROM
5.- Enjoy
If you have problems go to the telegram support group that already mentioned in OP
Julfo said:
Ok I have fix the problem and the system works. But know I have another one, and its that the phone doesn't detect sim card and there's no imei. Please Help.
Click to expand...
Click to collapse
You need to have the latest bootloader and modem, for that, use Odin to flash it.
It's ridiculous to ask, but where do I get the files to do it?
---------- Post added at 11:42 AM ---------- Previous post was at 11:39 AM ----------
Andrew666C said:
You need to have the latest bootloader and modem, for that, use Odin to flash it.
Click to expand...
Click to collapse
It's ridiculous to ask, but where do I get the files to do it?
hi, my rom is bootlooping. I have an error 127 in twrp when I install
"Exynos7870_CreateVendor.zip"
"Error installing zip file '/external_sd/Exynos7870_Createvendor.zip'"
I can provide more information if needed
Thank you!
edit:
-phone model j530f/ds, on android pie binary U6 (flashed with odin 1.13.1)
-Developer options->oem unlock enable
-Reboot phone into Download mode
-install "TWRP-3.3.1-j5y17lte-26052020.tar" in ap with odin 1.13.1 (desable auto reboot)
-rebooting in twrp without booting systeme
-flashing "Exynos7870_CreateVendor.zip" with error 127 "Error installing zip file '/external_sd/Exynos7870_Createvendor.zip'"
-rebooting recovery
-flashing "Exynox7870_ProjectSpaget_V3.0.zip" without error
-wiping Dalvik/art cache,System,Data,Cache
-flashing H-ROM_S20_PORT_BLOAT.zip
-rebooting system
-bootloping on samsung j5 logo
Interesting port.
Is the system suitable for everyday work? So for internet browsing, watching movies, instant messaging ...
Hi guys:
I'm using J530 and I have issues with apps that interacts with fingerprint, for example, on playstore if you set "biometric authentication" after set the password the playstore force close, however, there's no problem to unlock the phone and register more fingerprints.
does anyone have that issue?
Notification issue
How to fix notification light up? Because the screen doesn't turned on if there's a notification, especially WhatsApp call. Need to press power button to light up screen and see the caller
---------- Post added at 08:02 AM ---------- Previous post was at 07:58 AM ----------
Henri.P said:
hi, my rom is bootlooping. I have an error 127 in twrp when I install
"Exynos7870_CreateVendor.zip"
"Error installing zip file '/external_sd/Exynos7870_Createvendor.zip'"
I can provide more information if needed
Thank you!
edit:
-phone model j530f/ds, on android pie binary U6 (flashed with odin 1.13.1)
-Developer options->oem unlock enable
-Reboot phone into Download mode
-install "TWRP-3.3.1-j5y17lte-26052020.tar" in ap with odin 1.13.1 (desable auto reboot)
-rebooting in twrp without booting systeme
-flashing "Exynos7870_CreateVendor.zip" with error 127 "Error installing zip file '/external_sd/Exynos7870_Createvendor.zip'"
-rebooting recovery
-flashing "Exynox7870_ProjectSpaget_V3.0.zip" without error
-wiping Dalvik/art cache,System,Data,Cache
-flashing H-ROM_S20_PORT_BLOAT.zip
-rebooting system
-bootloping on samsung j5 logo
Click to expand...
Click to collapse
Don't use TWRP while installing create vendor. Use orangefox
Rahmatyus14 said:
How to fix notification light up? Because the screen doesn't turned on if there's a notification, especially WhatsApp call. Need to press power button to light up screen and see the caller
---------- Post added at 08:02 AM ---------- Previous post was at 07:58 AM ----------
Don't use TWRP while installing create vendor. Use orangefox
Click to expand...
Click to collapse
Thanks! Using SHRP fixed my problem (very nice recovery by the way)
SIM CARD
SIM Card doesn't work in J5 Pro :crying:
Henri.P said:
-flashing H-ROM_S20_PORT_BLOAT.zip
Click to expand...
Click to collapse
This is your problem, it's only the bloatware you install and not the system.
Install H-ROM_S20_PORT_V2.0.zip and you should be OK.
Julfo said:
I was waiting for it, thank you astrako. But i have a big problem, when I install it with the vendor it drops me an error 7 creating symlinks, but if I install it whithout the vendor, the installation finish successfully but instead of booting the system, bootloader screen appears. Please HELP ME
Click to expand...
Click to collapse
how did you fix this? facing the same issue
Thank for the best rom ever
sim not working on j730f
imei 1 and 2 is unknown

[CLOSED][ROM][12][BETA] LineageOS 19.1 for Samsung Galaxy A3 2017 (a3y17lte) (SM-A320F)

{
"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"
}
#include <std_disclaimer.h>
/*
* Your warranty is... still valid?
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
DO NOT USE ORANGEFOX FOR THIS !!! YOU WILL REGERET. ANDROID 12 AND ABOVE BREAK OLD RECOVERYS!!! Due to Platform Changes.
PLS UPGRADE TO TWRP 3.7 before installing the ROM https://drive.google.com/u/0/uc?id=1IDFv-vrfFu0cysHPzXoT8Mf21z4ZLp99&export=download
What works :
-you tell me
Bugs :
Camera 1080p video recording lag
not working codec2: (disabled)
no working gps
no working Bluetooth headset mic in calls
no working fingerprint
vsync is in the future
selinux permissive
broken drm (widevine)
Keep in mind that some LineageOS features have not been completed yet this is not a device bug and please do not report those
in this rom thread, also do not post bug reports for known issues or bug reports without proper
a) Logcat
b) proc/last_kmsg (or proc/kmsg)
c) data/tombstones
d) dmesg
0. [RECOMMENDED] Make sure you have an Oreo bootloader and modem before installing this. (ie : you have been in stock oreo once)
1. [RECOMMENDED] Do a good backup first
2. [ONCE] Make sure you did flash the inital Astrako's repartition script (https://forum.xda-developers.com/t/tool-a320fl-f-y-repartition-script-for-vendor-support.3951105/) to create a vendor partition.
Flashing this script will install (an old) TWRP.
3. Make sure you are using TWRP 3.7.0 (mentionned below)
4. [OPTIONAL/ONCE] Flash my custom repartition script (https://t.me/debieLineageOS/180) to shrink partition sizes, then format data.
6. [CLEAN FLASH] In recovery wipe everything except SD and OTG.
7. Flash LineageOS.
8. [OPTIONAL] Flash MindtheGApps .
9. [OPTIONAL] Flash Magisk.
10. Reboot. Booting should take less than 3 mins.
Generally it's ok to dirty flash, but if you encounter issues a clean flash should be the first thing on your mind.
Note : Flashing a repartition script should only be done once (unless you flash stock or the pit file which revert them) unless a release not say so.
Install gapps right after installing the rom itself don't try to boot to system before that if you want to use gapps (Or wipe data before installing them)
Download :
androidfilehost
Made by : @Flominator Astrako and @GonicTEAM @TheObcd
Device trees : https://github.com/samsungexynos7870/android_device_samsung_a3y17lte/tree/lineage-19.1-oss_bsp-vndk
ROM OS Version : Android 12.1
Kernel : 3.18
Telegram Support Group
Thank you for this work. I have started to test it, and I have 2 feedback. First it does not include fingerprint unlocking. Second, it is a major bug, I cannot enter any more into recovery, it gives a loop on Orangefox screen. Any solution?
Bernique said:
Thank you for this work.
Click to expand...
Click to collapse
that wasn't me
Bernique said:
I have started to test it, and I have 2 feedback. First it does not include fingerprint unlocking. Second, it is a major bug, I cannot enter any more into recovery, it gives a loop on Orangefox screen. Any solution?
Click to expand...
Click to collapse
report bugs to @Flominator
F-Google said:
that wasn't me
Click to expand...
Click to collapse
Why do you create a thread then ? Since it is Flominator work, he could choose to or not to share his work here. What is the goal to share the work of another person without being able to help ?
Bernique said:
I cannot enter any more into recovery, it gives a loop on Orangefox screen.
Click to expand...
Click to collapse
It works fine with TWRP6.X .Flominator told us to use TWRP in telegram .
TheObcd said:
It works fine with TWRP6.X .Flominator told us to use TWRP in telegram .
Click to expand...
Click to collapse
yes, use twrp 3.70 from @Batuhantrkgl
Bernique said:
Thank you for this work. I have started to test it, and I have 2 feedback. First it does not include fingerprint unlocking. Second, it is a major bug, I cannot enter any more into recovery, it gives a loop on Orangefox screen. Any solution?
Click to expand...
Click to collapse
DO NOT USE ORANGEFOX FOR THIS !!! YOU WILL REGERET. ANDROID 12 AND ABOVE BREAK OLD RECOVERYS!!! Due to Platform Changes.
PLS UPGRADE TO TWRP 3.7 before https://drive.google.com/u/0/uc?id=1IDFv-vrfFu0cysHPzXoT8Mf21z4ZLp99&export=download
@F-Google Pls add this as a waring in:
DO NOT USE ORANGEFOX FOR THIS !!! YOU WILL REGERET. ANDROID 12 AND ABOVE BREAK OLD RECOVERYS!!! Due to Platform Changes.
PLS UPGRADE TO TWRP 3.7 before installing the ROM https://drive.google.com/u/0/uc?id=1IDFv-vrfFu0cysHPzXoT8Mf21z4ZLp99&export=download
- put (Beta) in thread title
this build has still a lot of bugs:
Camera 1080p video recording lag
not working codec2: (disabled)
no working gps
no working Bluetooth headset mic in calls
no working fingerprint
vsync is in the future
selinux permissive
broken drm (widevine)
- add bugs to buglist.
Initialy this was the reasone why I didnt post on xda yet.
- add step by step guide install instructions from stock rom to this for newbies like:
1. ...
2. ...
3. ...
as the install process is more way more complex than on other devices.
- provide a link of mindgapps mirror as they are reccomended by LineageOS themselves
-give astrako and gonic credits
best regards Flominator
Bernique said:
Thank you for this work. I have started to test it, and I have 2 feedback. First it does not include fingerprint unlocking. Second, it is a major bug, I cannot enter any more into recovery, it gives a loop on Orangefox screen. Any solution?
Click to expand...
Click to collapse
sorry to you, but the only fix is to reflash the recovery with pc.
Flominator said:
sorry to you, but the only fix is to reflash the recovery with pc.
Click to expand...
Click to collapse
Thank for your thoughts, but I was somehow aware of the risk, especially when there is no comment on the status of the development.
Thanks to all for the new TWRP, I missed this information
@F-Google thx for updateing the thread
F-Google said:
0. [RECOMMENDED] Make sure you have an Oreo bootloader and modem before installing this. (ie : you have been in stock oreo once)
1. [RECOMMENDED] Do a good backup first
2. [ONCE] Make sure you did flash the inital Astrako's repartition script (https://forum.xda-developers.com/t/tool-a320fl-f-y-repartition-script-for-vendor-support.3951105/) to create a vendor partition.
Flashing this script will install (an old) TWRP.
3. Make sure you are using OrangeFox R11.0 (https://forum.xda-developers.com/t/...f-y-orangefox-recovery-project-r11-0.4032121/) (or TWRP 3.6+ (https://t.me/debieLineageOS/1766) in case you use LineageOS18+).
4. Download the Lineage build (https://t.me/debieLineageOS/172), optionally GApps (https://opengapps.org/) and Magisk (https://github.com/topjohnwu/Magisk/releases).
5. [OPTIONAL/ONCE] Flash my custom repartition script (https://t.me/debieLineageOS/180) to shrink partition sizes, then format data.
6. [CLEAN FLASH] In recovery wipe everything except SD and OTG.
7. Flash LineageOS.
8. [OPTIONAL] Flash GApps (arm64, pico or nano only).
9. [OPTIONAL] Flash Magisk.
10. Reboot. Booting should take less than 3 mins.
Generally it's ok to dirty flash, but if you encounter issues a clean flash should be the first thing on your mind.
/!\ OTA builds do NOT guarantee dirty flashing will work fine. (Magisk can cause issues for instance)
Note : Flashing a repartition script should only be done once (unless you flash stock or the pit file which revert them) unless a release not say so.
Click to expand...
Click to collapse
May you not blindly copy past what I wrote in telegram ? This tutorial is about the LineageOS17 releases I share on github/telegram. Some sentences are not appropriated here. I let you correct them. Furthmore you're free to use control + k to insert link .
About OTA, I am not aware of Flominator doing so (but I may be wrong).
TheObcd said:
May you not blindly copy past what I wrote in telegram ? This tutorial is about the LineageOS17 releases I share on github/telegram. Some sentences are not appropriated here. I let you correct them. Furthmore you're free to use control + k to insert link .
About OTA, I am not aware of Flominator doing so (but I may be wrong).
Click to expand...
Click to collapse
corrected wrong and outdated things
F-Google said:
corrected wrong and outdated things
Click to expand...
Click to collapse
Still some work to do...
@roirraW "edor" ehT please can you close the thread, the rom is WIP again @Flominator will post when it's done
F-Google said:
@roirraW "edor" ehT please can you close the thread, the rom is WIP again @Flominator will post when it's done
Click to expand...
Click to collapse
Thread has been closed on request of OP!
@F-Google Just a remark: The best, most efficient and fastest way to get such requests accomplished is to alert the moderators team via the report function instead of posting the request and pinging a moderator. Please be aware, with 75M+ posts in 3.5M+ threads were unable to monitor posts. And moderators are spread all over the globe and due to different timezones pings might not be noticed for many hours or for days/weeks in case of a moderator's absence. Contrary, a report will alert "the moderator on duty".
Regards
Oswald Boelcke
Senior Moderator
CC: @roirraW "edor" ehT

[ROM][13][UNOFFICIAL][BETA] Pixel Experience 13 Plus

{
"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"
}
​Pixel Experience 13 Plus for Galaxy A70​
Code:
/*
* Your warranty is now void.
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
What is this?
PixelExperience is an AOSP based ROM, with Google apps included and all Pixel goodies (launcher, wallpapers, icons, fonts, boot animation)
Our mission is to offer the maximum possible stability and security, along with essential and useful features for the proper functioning of the device
Based on Android 13​What is working:
- WiFi
- DualSIM, including calls on both sims
- Bluetooth
- NFC
- Camera
- Sound
- GPS
- Fingerprint scanner/Face unlock
- Sensors
- SD cards
- Double tap to wake
- Data encryption
- SELinux enforcing
- SafetyNet
- Sound in calls (since that requires clarifying now..)
- Most other basic stuff
Spoiler: Known issues
Known issues:
- VoLTE/VoWiFi, of course
Installation guide:​
Spoiler: Using PE recovery
1. Recommended Samsung firmware version is A705FNXXU5DVK6, but it will work on slightly older versions too.​Make sure that the bootloader is unlocked.​--
2. Boot the phone into download mode. Flash Pixel Experience recovery through AP button in Odin.​Download here.​ Note: TWRP will not work! It does not support new A13 roms with the latest changes.
Use PE recovery for the best experience, otherwise don't complain if your phone bootloops.
--
3. Boot into recovery (Vol+ and Power while USB is plugged into PC)​ Note: Samsung's OneUI wipes the custom recovery partition and possibly vbmeta while booting so try not to reboot into Android.
--
4. Format data and system in the recovery​--
5. Flash the rom in "Apply update" menu.​ There are 2 ways to install:
On the phone: Copy the zip to a FAT32-formatted microSD card and install it in recovery.
With a PC: Use Minimal ADB on Windows. Open "cmd-here" and type
Code:
adb sideload <rom-file>
where <rom-file> is the filename (drag-and-drop the zip file into cmd window).
--
6. (Optional) If you want superuser access, flash Magisk in the same way that you flashed the rom.​We now have a working ramdisk so newest Magisk works fine ^^
--
7. Reboot and enjoy ​
​Downloads:​(Update recovery and clean flash if coming from 2023.01.04!)
ROM: 2023.06.18​Recovery: 2023.06.18​*Please report any bugs that you find before we go official!
Changelog:
Spoiler: Click to open
See here for full changelogs: https://github.com/rtd1250/a70q_OTA/releases
Like my work? Consider donating
Buy rtd1250 a Coffee. ko-fi.com/rtd1250
Become a supporter of rtd1250 today! ❤️ Ko-fi lets you support the creators you love with no fees on donations.
ko-fi.com
Credits:
* @rttxda @ataberkozen @haky 86
* Grarak for the original 17.1 trees
* Simon1511 for his work on Lineage for similar Samsung qcom phones
* All PE devs
Source code:
https://github.com/PixelExperience
https://github.com/rtd1250/android_device_samsung_a70q
https://github.com/rtd1250/android_kernel_samsung_sm6150
https://github.com/rtd1250/proprietary_vendor_samsung_a70q
Other info:
OS version: Android 13
Linux version: 4.14.190
Recommended firmware: A705FNXXU5DVK6
Build date: 18/06/2023
So far so good on the a70(sm-a705mn), I just made the installation without problems, thank you very much for continuing to create roms for the a70q, now only remains to test the pixel experience rom.
Working well on (SM-705GM). No issues except screen gets brighter while unlocking device. Easy and Quick installation. Excellent installation guide. Thanks for this rom.
Came from the crDroid A12 GSI. This is such a lovely ROM. Really impressed, working fine and fingerprint is better than the official Samsung ROM. Great stuff. The hardware on this phone is still great and Samsung ditching it at Android 11 seems like such a waste.
New update is out, fixing a battery drain issue and homescreen stutters.
Unfortunately, it requires a recovery update and a clean flash due to filesystem-related changes, so please back up your data (for example make a google backup) before updating!
Upgrade process is basically: reflash new recovery, wipe data, flash the .zip, like in install guide.
This shouldn't be an issue in the future builds, sorry for the inconvenience.
rttxda said:
New update is out, fixing a battery drain issue and homescreen stutters.
Unfortunately, it requires a recovery update and a clean flash due to filesystem-related changes, so please back up your data (for example make a google backup) before updating!
Upgrade process is basically: reflash new recovery, wipe data, flash the .zip, like in install guide.
This shouldn't be an issue in the future builds, sorry for the inconvenience.
Click to expand...
Click to collapse
Thanks!, I actually installed yesterday and yeah, I feeled the battery drain, so thanks for updating it!
apexRathalos said:
Thanks!, I actually installed yesterday and yeah, I feeled the battery drain, so thanks for updating it!
Click to expand...
Click to collapse
I'm actually impressed with how good the battery is compared to crDroid GSI. No issues on homescreen either (using Nova). Installed only a few days ago!
I can't turn on this settings
Natram1zh said:
I can't turn on this settings
Click to expand...
Click to collapse
yeah that only works on lineage currently, I'll troubleshoot that later.
steford said:
I'm actually impressed with how good the battery is compared to crDroid GSI. No issues on homescreen either (using Nova). Installed only a few days ago!
Click to expand...
Click to collapse
GSIs are pretty terrible from my experience, so I feel like actually porting the rom is worth the effort.
It's crazy how this rom is so smooth. Well done
The ROM is awesome.. very good work
The bugs are:
1- screen of FOD not working
2- vibration on answering and ending calls not working .. I am not sure if it was working on other ROM versions ..
Thumbs up..
Munir.jacob90 said:
The ROM is awesome.. very good work
The bugs are:
1- screen of FOD not working
2- vibration on answering and ending calls not working .. I am not sure if it was working on other ROM versions ..
Thumbs up..
Click to expand...
Click to collapse
1. Answered 2 posts above
2. Didn't know about that (can't test currently..), but there were some vibrator-related changes indeed
rttxda said:
1. Answered 2 posts above
2. Didn't know about that (can't test currently..), but there were some vibrator-related changes indeed
1. Yes I know I just mentioned it
2. Hope it can be fixed..
Click to expand...
Click to collapse
Loving the ROM, works great.
Sorry to be nitpicky but could you fix the aliasing on the rounded corners. Think it's in a file called dimens.xml. Just needs a proper rounded corner value set I think. It'll also make the Google Assistant swipe animation follow the rounded corners.
I can't remember off the top of my head on how I fixed it for the A50 but I believe I removed the separate top and bottom values and replaced them with just rounded_corner_radius.
RandomAJL said:
Loving the ROM, works great.
Sorry to be nitpicky but could you fix the aliasing on the rounded corners. Think it's in a file called dimens.xml. Just needs a proper rounded corner value set I think. It'll also make the Google Assistant swipe animation follow the rounded corners.
I can't remember off the top of my head on how I fixed it for the A50 but I believe I removed the separate top and bottom values and replaced them with just rounded_corner_radius.
View attachment 5806719
Click to expand...
Click to collapse
I did notice that at some point but completely forgot about it. Thanks for reminding me
Android Auto isn't working.
markadrian031 said:
Android Auto isn't working.
Click to expand...
Click to collapse
Oh, unfortunate. Android Auto support on custom roms has always been kind of hit-and-miss anyways, on many devices across many different roms. It's not that high of a priority for rom devs. Either way I can't test that since my stereo doesn't have AA
markadrian031 said:
Android Auto isn't working.
Click to expand...
Click to collapse
Worked fine for me. My car is a wired android auto version. Is yours wireless by any chance? I can't test that.
Random Bootloops Randomly When Restarting The Device So Much ??
Can you please tell me a fix or something for this ,, it's always happening with me since I bought the phone and started to install custom roms on it !!
XxLightAngelXx said:
Random Bootloops Randomly When Restarting The Device So Much ??
Can you please tell me a fix or something for this ,, it's always happening with me since I bought the phone and started to install custom roms on it !!
Click to expand...
Click to collapse
Sounds like either an issue with your phone or the way you install stuff. What's the model? (SM-A705XX)

Categories

Resources