#getresurrected
This ROM will not be getting more updates or support
Notes:
- Open GAPPs nano is included with the ROM.
- SU is already included in this ROM, you only need SU manager to manage root access and stuff like that.
- I will not be able to help you with any problems that happen after install magisk modules or stuff like that so you are on your own if you use it xD <3
Instructions :
Download the latest build
Reboot to TWRP
Do a factory reset
Flash the latest build
Flash proximity sensor fix uninstaller (You only need to flash it once and if you flashed Proximity sensor fix before. check here)
Reboot
Downloads :
TWRP
ResurrectionRemix 8.6.7
Proximity sensor fix uninstaller
Known Issues:
VoLTE (samsung Volte support is not ported to AOSP Yet)
Proximity Sensor
SElinux is permissive
FM radio
wifi hotspot doesn't work when mobile data is enabled
did you find any?
Sources:
Device tree
Kernel tree
Special thanks:
- Special thanks to Vary Marvel who provided the build server and helped with much other stuff.
- M51 dev group members for support.
Version Information
Status: Final
ROM OS Version: ResurrectionRemix 8.6.7
Android Security Patch: 5th of February 2021
Vendor Security Patch: 1st of November 2020
Change Log:
5th of March 2021:
- Include open GAPPs nano variant
4th of March 2021:
- Initial release
Reporting Bugs
DO NOT report bugs if you're running a custom kernel or you installed Xposed
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /proc/last_kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues. Any bug not reported in the bug report format below may be ignored.
Code:
What is your--
LineageOS version:
LineageOS Download url:
Gapps version:
Are you using--
a task killer:
a non-stock kernel:
other modifications:
Click to expand...
Click to collapse
F.A.Qs:
How to hide notch?
First, activate developer options by going to settings > about phone > click on build number 7 times
Second, Go to Settings > Advanced > Developer options > Scroll down until you find Display cutout then choose hide
Some info about why I do stuff
Why do you need to flash proximity fix uninstaller?
Because if the screen gets turned off during a call, it won't turn back on until the call ends, in addition to that, it makes the phone stuck on black screen in other ROMs
Thank you so much for this! My favourite ROM makes it to this device! Yay! Lol
First boot is taking forever, is this normal? Never took this long before
CapMothy said:
Thank you so much for this! My favourite ROM makes it to this device! Yay! Lol
First boot is taking forever, is this normal? Never took this long before
Click to expand...
Click to collapse
It usually takes about 2 minutes or less...
did you flash open GAPPs?
LahKeda said:
It usually takes about 2 minutes or less...
did you flash open GAPPs?
Click to expand...
Click to collapse
Nope, no GAPPs or Magisk.
CapMothy said:
Nope, no GAPPs or Magisk.
Click to expand...
Click to collapse
Does it open or still stuck on bootanimation?
Maybe try the latest build
LahKeda said:
Does it open or still stuck on bootanimation?
Maybe try the latest build
Click to expand...
Click to collapse
Latest build worked, thank you.
My god dude woww two rom releases .
Man fking love you
Great work...
Does this rom have 10 bit hevc encoder?
thanks
it was working nice but i flashed proximtry at next boot to twrp then its forever loading on rr logo while restart
thanks bro now using without FLASHING proxymetry .. ITS BETTER THAN STOCK
Shindekrunal1987 said:
it was working nice but i flashed proximtry at next boot to twrp then its forever loading on rr logo while restart
Click to expand...
Click to collapse
Shindekrunal1987 said:
thanks bro now using without FLASHING proxymetry .. ITS BETTER THAN STOCK
Click to expand...
Click to collapse
Lol
This is what you get for not reading the instructions and notes carefully
LehKeda said:
Lol
This is what you get for not reading the instructions and notes carefully
Click to expand...
Click to collapse
Really can u tell me where it is written .. I read only flash it once.. I m blind ..
Awesome ROM using from 3 days
.
Shindekrunal1987 said:
Really can u tell me where it is written .. I read only flash it once.. I m blind ..
Click to expand...
Click to collapse
Here
LehKeda said:
Flash proximity sensor fix uninstaller (You only need to flash it once and if you flashed Proximity sensor fix before. check here)
Click to expand...
Click to collapse
Related
Official Thread will be soon up! Head over there guys.
This thread is dead!
crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features existent today. We're mainly based on CyanogenMod so use custom kernels compatible with them!
A special thanks to @forkbomb444. crDroid is available thanks to him. I'm using his devices, kernel, proprietary vendor and many other repos to build
All the source code for crDroid is available in the Github
repo. And if you would like to contribute feel free to pull a request.
Kernel features beyond CyanogenMod ones (Work in Progress) [Future Release]
• Boeffla Charging Control
• Boeffla Sound.
All this can be initiated through some script knowledge.
INSTALLATION METHOD
First time installing crDroid to your I9300, or coming from another ROM:
- Make sure you're running a proper working Recovery (CWM or TWRP)
- Copy GApps and crDroid zip to your internal SDCard
- Boot into Recovery
- Flash crDroid zip
- Flash GApps zip
-Note: Flash ROM and GApps together or else you'll have a hard time.
- Flash SuperSU (not mandatory. We have
CyanogenMod su access inside)
- DO A DATA WIPE / FACTORY RESET
- Reboot
- Don't restore Apps using Titanium Backup!
Upgrading from earlier version of crDroid:
- Copy crDroid ZIP to your internal SDCard
- Boot into Recovery
- Flash crDroid zip
- Reboot
Download Link:
https://www.androidfilehost.com/?fid=24415232478677728
GApps: opengapps.org
Full support
https://plus.google.com/communities...4243234a-de8a-4262-bd30-68582ebeb472?hl=pt_br
Don't expect any support if you
- are not running stock crDroid-kernel
- have installed any mods such Xposed!
- have modified system files
Special thanks:
- Google
- CyanogenMod
- @forkbomb444
- @temasek
- @Darkened_Sky
- Many others... (if you're feeling upset being out of the thanks list just send a PM )
Source: http://www.github.com/cyanogenmod
https://github.com/crdroidandroid
Reserved 1 (Screenshots)
Someone please share some screenshots!
FAQ
Do read this before asking questions!
1. Q: How do I get root?
A: Enable it in developer options.
2. Q: But can I use SuperSU instead of the built-in SU?
A: Sure. Make sure that the built-in SU is disabled in developer settings. Afterwards flash SuperSU. By default after a clean flash built-in SU is disabled, so you can also directly flash SuperSU after a clean flash
3. Q: Which gapps do I need?
A: This ROM is based on CM13/Android 6.0x/Marshmallow. Therefore choose your gapps accordingly. If you want to use the recommended opengapps, choose the ARM 6.0 version. I highly suggest to use either the pico or the nano package. All other gapps can later still be installed via playstore!
4. Q: Help! I have a problem/issue/bootloop/....?
A: Please follow these steps:
1. Make sure that the problem is not already mentioned in either this thread or in the CM13 thread.
2. Make sure that you can reproduce the problem on your device with absolutely no additional modification and after a clean flash. This includes being on stock kernel, no xposed, no SuperSU, no theme!
3. Try to replicate the problem on official CM13. If it appears there, please ask there.
4. If your problem couldn't be solved with above steps, post here, with an exact description of how to reproduce and if possible with logs.
5. Q: Is xposed working?
A: Yes but make sure to use the latest and the correct version for Marshmallow. Inform yourself in the xposed thread. Everything is clearly explained there which version you need. The version that works for you on official CM13 will also work here.
6. Q: Can I use custom kernels?
A: Yes. Users which use SuperSU frequently report problems with bootloops after flashing a custom kernel. Therefore I'd suggest to use built-in SU.
7. Q: I have added files to my system, but after each ROM update they disappear?
A: Yes during a flash the /system partition is wiped.
yess i'v ben waiting for this rom to get MM
ayoubadri said:
yess i'v ben waiting for this rom to get MM
Click to expand...
Click to collapse
What you waiting for? Give it a try
nice new rom for s3 thinks Dev
spide3 said:
nice new rom for s3 thinks Dev
Click to expand...
Click to collapse
Download and Flash! Enjoy
P.S: I am not the developer of this ROM! I have just created this thread. Though I can do a bit of coding. So, for all bootloops or random reboots I need proper information
sunny1234590 said:
P.S: I am not the developer of this ROM! I have just created this thread. Though I can do a bit of coding. So, for all bootloops or random reboots I need proper information
Click to expand...
Click to collapse
ROM is awesome, but i havenot mobile data... cellular radio working, i have reception but i havenot mobile data. APN is right. GT-I9300
jujuna said:
ROM is awesome, but i havenot mobile data... cellular radio working, i have reception but i havenot mobile data. APN is right. GT-I9300
Click to expand...
Click to collapse
No bug on my device. Using stock kernel?
Are you maintaining this ROM now?
sameer23 said:
Are you maintaining this ROM now?
Click to expand...
Click to collapse
I have opened this thread on the behalf of the original developer but yes, I'll keep it updated with new builds. So, kind of Yes!
sunny1234590 said:
No bug on my device. Using stock kernel?
Click to expand...
Click to collapse
my kernel is 3.0.101-CM-gbe3d845 [email protected] #1 << is it a stock?
jujuna said:
my kernel is 3.0.101-CM-gbe3d845 [email protected] #1 << is it a stock?
Click to expand...
Click to collapse
Yes, it is stock. Try a clean flash and report back!
Do you face this issue on official CM13 also?
sunny1234590 said:
Yes, it is stock. Try a clean flash and report back!
Do you face this issue on official CM13 also?
Click to expand...
Click to collapse
yes, on Official CM13 i had this proble. only AICP marshmallow rom i havenot this problem. crDroid, bliss, an etc i have this problem. my installation was clean 100%.
jujuna said:
yes, on Official CM13 i had this proble. only AICP marshmallow rom i havenot this problem. crDroid, bliss, an etc i have this problem. my installation was clean 100%.
Click to expand...
Click to collapse
I see! Can you tell me which baseband version you have?
And it's strange considering the fact that AICP is also based on Official CM13 just like crDroid!
sunny1234590 said:
I see! Can you tell me which baseband version you have?
And it's strange considering the fact that AICP is also based on Official CM13 just like crDroid!
Click to expand...
Click to collapse
i know, its weird for me too.. my baseband version is I9300XXEMG4 and IP 192.168.0.100 fe80::237:6dff:fef2:c4a0
jujuna said:
i know, its weird for me too.. my baseband version is I9300XXEMG4 and IP 192.168.0.100 fe80::237:6dff:fef2:c4a0
Click to expand...
Click to collapse
That's a slightly older baseband version if I am correct. Just try to flash the latest baseband and see if it makes some difference though I doubt.
Since, I can't reproduce this error so, it's not a bug for me at least. Someone else must confirm about the mobile data thing.
Hi guys,
I can't give root permission to apps.
I've enabled Developer Options, and enabled Root Access to Apps, but when I try to run an app that needs root, it doesn't ask permissions.
Could you give me a hint?
Thanks
sunny1234590 said:
That's a slightly older baseband version if I am correct. Just try to flash the latest baseband and see if it makes some difference though I doubt.
Since, I can't reproduce this error so, it's not a bug for me at least. Someone else must confirm about the mobile data thing.
Click to expand...
Click to collapse
i flashed but no result
OmniROM
[#MARSH]
[#ESPRESSONAME]
[#WHATSOMNI]
[#WARRANTY]
Downloads:
[#DLGITHUBIO]
[#INFOOMNI]
[#DONATETOME]
XDA:DevDB Information
[unified] OmniROM 6.x, ROM for the Samsung Galaxy Tab 2
Contributors
Android-Andi, Ziyan
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.0.x
Version Information
Status: Testing
Created 2016-06-24
Last Updated 2017-04-30
Thanks bro, cant wait to download and test this new omni 6.0
Still testing version, right? Any knowns bugs? Or bugs same with your cm13?
And about the usefull link, I didnt see any changelog for omni 6.0 or am I miss that?
The screen rotation seems to wrong for me. Other than that it seems to work well
Sent from my D5803 using XDA-Developers mobile app
Buleste said:
The screen rotation seems to wrong for me. Other than that it seems to work well
Sent from my D5803 using XDA-Developers mobile app
Click to expand...
Click to collapse
Exactly the same issue. Screen rotation is switched but touch is working fine
Buleste said:
The screen rotation seems to wrong for me. Other than that it seems to work well
Sent from my D5803 using XDA-Developers mobile app
Click to expand...
Click to collapse
I don't have my tab with me, but i can upload a flashable zip later to test. I guess i know the issue.
iks8 said:
Exactly the same issue. Screen rotation is switched but touch is working fine
Click to expand...
Click to collapse
~ All my work, news etc. on http://andi34.github.io ~
Abigail said:
Thanks bro, cant wait to download and test this new omni 6.0
Still testing version, right? Any knowns bugs? Or bugs same with your cm13?
Click to expand...
Click to collapse
Same as on CM 13.
And about the usefull link, I didnt see any changelog for omni 6.0 or am I miss that?
Click to expand...
Click to collapse
looks like omni updated their page and the links not working anymore. You'll see made changes on gerrit.
~ All my work, news etc. on http://andi34.github.io ~
Chromecast should work, but haven't tested myself.
~ All my work, news etc. on http://andi34.github.io ~
I hope attached zip fixes the sensor position to have proper rotation Please let me know if it works
Android-Andi said:
I hope attached zip fixes the sensor position to have proper rotation Please let me know if it works
Click to expand...
Click to collapse
fix is working, thanks
Same here - good to go!
Do I need to have Andy's TWRP? Which gapps are recommended? Do I need to flash supersu if I want root? Thanks
lepa71 said:
Do I need to have Andy's TWRP? Which gapps are recommended? Do I need to flash supersu if I want root? Thanks
Click to expand...
Click to collapse
Idk if older or other recoveries work, i only use the one i shared.
Deltadroid gapps, mentioned on my userpage.
About root... It's mentioned in FAQ too for a good reason....
NOTE:*OmniRom and AOSP aren't pre-rooted, you need to use*SuperSuor the*OpenSource SuperUser*to get rooted.
Click to expand...
Click to collapse
~ All my work, news etc. on http://andi34.github.io ~
now is working fine, thanks...
Android-Andi said:
Idk if older or other recoveries work, i only use the one i shared.
Deltadroid gapps, mentioned on my userpage.
About root... It's mentioned in FAQ too for a good reason....
~ All my work, news etc. on http://andi34.github.io ~
Click to expand...
Click to collapse
Do you recommend basic delta gapps or standard? I usually use nano open gapps.
lepa71 said:
Do you recommend basic delta gapps or standard? I usually use nano open gapps.
Click to expand...
Click to collapse
You can use open gapps too, but they cause trouble for some user if permissions aren't set before sign in.
~ All my work, news etc. on http://andi34.github.io ~
Dear @Android-Andi & Ziyan,
thanks very much for quick updates. is 5521 build perfect?
~Omnivora~
"...stay success and keep tab 2 alive at least till 2020"
Astro Noid said:
Dear @Android-Andi & Ziyan,
thanks very much for quick updates. is 5521 build perfect?
~Omnivora~
"...stay success and keep tab 2 alive at least till 2020"
Click to expand...
Click to collapse
Seems like it doesn't fix simpin which i thought it will fix :/
~ All my work, news etc. on http://andi34.github.io ~
Hello nightly
http://dl.omnirom.org/espressowifi
http://dl.omnirom.org/espresso3g
Note: switching between homemade and nightly builds must be a clean flash!
~ All my work, news etc. on http://andi34.github.io ~
Still I have the same rebooting issue as on every 5.0+ ROM. It works fine for a while and then it soft reboots
Alright, since I resurrected a couple of NAND-bricked 16GB P31x0 ...
Bug 1: Tap on the "User image" in the notification shade - and try to set a avatar image for the "Owner" account - system crashes and reboots once you tap the "Save" button where you can crop the image you selected.
Bug 2: YouTube doesn't work overly well. When you start playing back a video it plays for 2-3 seconds then "stutters" and gives a "playback error". You can retry at which point it will work, but it's annoying (doesn't happen with the July/2 CM13 build). Also, YouTube only shows up to 480p in "Quality" where in CM13 it shows 720p (landscape full-screen).
Bug 3 (not sure if bug or "feature"): You can set the "Recent app" thingy to display "full screen" (no navbar / statusbar), but you cannot enable "extended desktop" anywhere for the UI itself.
Bug 4 (not sure it is a bug): I see a rather strange behavior on system boot...
- When I "shutdown" and have it plugged into the charger it shuts down, then the "charge anim" shows up and the screen is cleared but the backlight isn't turned off.
- When I start the system (from "shutdown" state) it seems as it does a "double boot" ... Galaxy Tab logo screen -> blank -> "reboot" (?) -> Galaxy Tab logo screen -> blank -> Omni boot anim.
All clean flashed with Delta's latest "base" Gapps package and SuperSU 2.65
I'll also slap a post into the CM13 thread as I see two minor problems with the latest build as well.
Omni 9.0 has gone official.
See https://forum.xda-developers.com/xperia-xz/development/rom-omnirom-t3912113
This thread is now closed.
---
These builds are UNOFFICIAL! They do not meet the quality standards of the OmniROM project.
Flash at your own risk! You have been warned.
OmniROM 9.0 builds based on kernel 4.9. The internals are mostly the same as my regular AOSP nightly builds.
SELinux: Enforcing (but lax policies right now)
Priv-app permisisons: Enforcing
Dm-verity: Disabled
Latest downloads: sx.ix5.org
Latest semi-stable will be called "-SEMISTABLE".
Install guide: sx.ix5.org (it should be the same as for AOSP).
Changelogs: TBD
Known bugs: See sx.ix5.org
Read the install guide and post #2 before reporting bugs or asking for help!
DO NOT POST HERE FOR FLASHING HELP OR YOU WILL BE REPORTED. Read everything before posting.
Don't make me ask you for logs every time!
Sources:
https://git.ix5.org/felix/omni-repo-update
https://git.ix5.org/felix/local-manifests-omni-kagura
https://github.com/omnirom/android_kernel_sony_msm
https://github.com/omnirom/android_device_sony_common
https://github.com/omnirom/android_device_sony_tone-common
https://github.com/omnirom/android_device_sony_kagura
XDA:DevDB Information
OmniROM for XZ (unofficial), ROM for the Sony Xperia XZ
Contributors
local__hero, oshmoun, humberos
Source Code: https://git.ix5.org/felix/local-manifests-omni-kagura
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
ROM Firmware Required: .184 or .192 firmware
Based On: OmniROM
Version Information
Status: Nightly
Created 2018-11-30
Last Updated 2018-11-30
Reserved
Reporting bugs
Important: Read the bug list before posting. Anyone can add bugs to the list, just follow the rules.
If you have questions, ask them in this thread: Xperia XZ Pie ROMs Questions and Answers Thread
I will repeat the rules again here:
Rules:
New bugs must include version where error popped up and which oem version you are using
Only reproducible errors
Should include adb logcat (linked in a pastebin service like https://del.dog)
Must include clear description what is wrong
If it is a visual/SystemUI bug, only report it here
If it is an internal bug(e.g. fingerprint crashes device), report it to the Sony bugtracker as well!
Always try to fix the bug yourself first! Then submit a pull request to Sony
Must search if error has already been reported (bug tracker, this document, dev buglist)
If you've reported the issue somewhere else already and just want to track it here as well, add a link
Before reporting a bug, always make sure to isolate it. That means, wipe everything, install only the ROM without GApps and Magisk and see if the problem still exists. Only then report the bug!
Reserved
OH MY GOD... Thanks for the great news.. android 9 omnirom for XZ !! Keep up the great work.. in my country there are alot of ppl using xz and following for this !!!!
rezerved
F8331 cihazımdan Tapatalk kullanılarak gönderildi
Just a question, what version of the OEM I should I use? I know that some of them have a few bugs in then, what would you recommend? Latest OEM or a previous one?
DarkPrinciple said:
Just a question, what version of the OEM I should I use? I know that some of them have a few bugs in then, what would you recommend? Latest OEM or a previous one?
Click to expand...
Click to collapse
I'm using the one from AOSP 9.0 thread and it works fine.
Can't play m4a audio files
I'm using omni_kagura-2018-12-06-UNOFFICIAL_NIGHTLY
successfully flashed it with gapps, magisk 18 etc
it seems that with any audio player i can't play my m4a audio files.
+ is this rom the same as your other aosp 9.0?
Please, please do not abandon development
Omni 9 will have update in the future?
robby.pgn said:
Omni 9 will have update in the future?
Click to expand...
Click to collapse
We can only hope and pray.
Update
New build up, 2019-01-23. This is a "user" build, and as usual, runs enforcing SELinux. Getting very close to an official build.
This release is only compatible with the v5 binaries.
In case you need better battery life over fast screen wake-up, you can turn on Deep Sleep in Settings -> System -> Advanced -> Extended Settings and toggle "Disable Deep Sleep".
Please test thoroughly and report the bugs as described in post #2.
Hi guys
Tranks for your work, Is there a list of known errors in this construction?
Thanks.
Need to get home so I can test this. Been on Omni Oreo for awhile. Been waiting for a good pie rom, especially if it's a omnirom
fallingandroid said:
Need to get home so I can test this. Been on Omni Oreo for awhile. Been waiting for a good pie rom, especially if it's a omnirom
Click to expand...
Click to collapse
Hi bro
The last compilation work fluid, but the camera be continue a bad experince, the rest without problem.
Stronger1101 said:
Hi bro
The last compilation work fluid, but the camera be continue a bad experince, the rest without problem.
Click to expand...
Click to collapse
I'm sure there's other cameras besides stock that can be used. Let's hope lol
fallingandroid said:
I'm sure there's other cameras besides stock that can be used. Let's hope lol
Click to expand...
Click to collapse
I tried use Open camera, a better camera, google camera, and the result dont has been so much diferent.
?
I keep getting the error, failed to mount /oem. WHat am I doing wrong, I follow the instructions right and flash the right binaries. I can't figure this out
fallingandroid said:
I keep getting the error, failed to mount /oem. WHat am I doing wrong, I follow the instructions right and flash the right binaries. I can't figure this out
Click to expand...
Click to collapse
Can seem ridiculus my question, but It happened to me...
You intent flash with flashtool open? This can been the reason of error when youre try flash adb mode.
Stronger1101 said:
Can seem ridiculus my question, but It happened to me...
You intent flash with flashtool open? This can been the reason of error when youre try flash adb mode.
Click to expand...
Click to collapse
I flash with flashtool. Flash the recovery, flash the OEM that's listed for the install. But when I boot into recovery, it says it can't mount /OEM. I don't understand what's happening when I followed the directions step by step.
fallingandroid said:
I flash with flashtool. Flash the recovery, flash the OEM that's listed for the install. But when I boot into recovery, it says it can't mount /OEM. I don't understand what's happening when I followed the directions step by step.
Click to expand...
Click to collapse
Please, you can copy the links files specific you used? To try to see, where is the problem.
A2017X_O_B04_SL!M8
Just for fun....no more no less...
For our dedicated stock users
For those who weren't able to install or obtain the A2017G-O-B04 OTA update, I made a SL!M8 rom (not an AROMA because atm I don't have much time ) that can boot on a working stock Oreo rom.
This version is tested on stock B02 as on my SL!M7 (based on B03). So there should be no problem at all
I hope you'll ENJOY !
Modifications :
* full system r/w
* removed some unwanted apps and the ability to remove more when booted into the rom with a root explorer
* safetynet pass cts will pass when flashing magisk 19.3
* youtube vanced
* adaway 4.2.6
* full working Dolby Atmos
* wifi working...and ofc all the rest
* fastboot working
*.....
Installation : NOTE : for those having trouble installing, flash the twrp 3.2.10 with the universal bootstack (don't forget the modem)
1. unlocked, twrp3218 (non-treble) installed (or compatible one for oreo...)
1.a boot into twrp, format data/factory reset, reboot twrp, wipe system
2. flash A2017GV1.3.0B04_BootStack ( flash your modem type again as this has the latest G-version one )
3. flash A2017X_O_B04_SL!M8
4. flash Magisk 19.3
5. wipe dalvik/cache and boot
6. setup phone
7. you should now have a fully working SL!M8 :cyclops:
Contributors :
@raystef66
Credits :
@totmakina :highfive:
@asderdd
ROM OS Version : OREO 8.0.0
Source : ZTE stock-rom A2017V1.3.0B04
Kernel : ZTE stock
Security Patch : 2019-04-01
Version Information :
Status : Stable
Created : 2019-07-10
Uploaded : 2019-07-10
NEW A2017G-O-B04-MODEM
Good rom for those of us who like stock! I will add Xposed.
I love the stock. I'll test how the battery goes since I put it in a new one a little while ago
Thanks Rays!
totmakina said:
Good rom for those of us who like stock! I will add Xposed.
I love the stock. I'll test how the battery goes since I put it in a new one a little while ago
Thanks Rays!
Click to expand...
Click to collapse
I'm currently running the chinese B23 with TWRP, is it possible to flash this over? Or should I flash other rom first?
Also, a bit offtopic suggestion: You should update your camera2api enabler ZIP, because it somehow changes the build name to A2017GV1.3.0B02 on other roms (this happened to me on european B03 and chinese B23 and should also happen on this new B04)
joaocandeias said:
I'm currently running the chinese B23 with TWRP, is it possible to flash this over? Or should I flash other rom first?
Also, a bit offtopic suggestion: You should update your camera2api enabler ZIP, because it somehow changes the build name to A2017GV1.3.0B02 on other roms (this happened to me on european B03 and chinese B23 and should also happen on this new B04)
Click to expand...
Click to collapse
You can try since it is a stock Oreo rom. So follow instructions furtheron.
Ah yes, you're referring to this one : https://androidfilehost.com/?fid=11410932744536993784
Yeah, it's all in the build.prop...i'll make another one if you want
Thanks so much @raystef66 ! A lot of us have been waiting for this! Hopefully I have better luck flashing this, as B03 Sl!m was giving me encryption issues upon rebooting after flashing.
raystef66 said:
You can try since it is a stock Oreo rom. So follow instructions furtheron.
Ah yes, you're referring to this one : https://androidfilehost.com/?fid=11410932744536993784
Yeah, it's all in the build.prop...i'll make another one if you want
Click to expand...
Click to collapse
Yes, that's the one. I can live with it as long it doesn't affect the ROM usage (I don't think it does though) but it's up to you.
About the new SL!M8, I'll see if I can flash it tomorrow and give feedback
Thanks for your awesome work.
Q: i installed b03 and cant find double tap to wake anymore. Is the Feature gone since Oreo? I wonder if the bugs im having will be gone with this update (gboard constantly crashes when opening settings so i cant change/add languages, SMS bug / can send but not receive, Turn off screen is not installed even tho i choose it in aroma Installer)
Hi, raystef66. Thank you so much for your contribution! I stayed on "ancient" slim B10 (Nougat) until now for Daydream support. Now I upgraded and it works fantastic.
joaocandeias said:
Yes, that's the one. I can live with it as long it doesn't affect the ROM usage (I don't think it does though) but it's up to you.
About the new SL!M8, I'll see if I can flash it tomorrow and give feedback
Thanks for your awesome work.
Click to expand...
Click to collapse
Updating the HDR+ zip again - had to check it over - should work
Here you go : A2017G-V1.30B04_HDR+
boxemall said:
Q: i installed b03 and cant find double tap to wake anymore. Is the Feature gone since Oreo? I wonder if the bugs im having will be gone with this update (gboard constantly crashes when opening settings so i cant change/add languages, SMS bug / can send but not receive, Turn off screen is not installed even tho i choose it in aroma Installer)
Click to expand...
Click to collapse
DT2W is working fine. Up to you to test out the other things.
romitkin said:
Hi, raystef66. Thank you so much for your contribution! I stayed on "ancient" slim B10 (Nougat) until now for Daydream support. Now I upgraded and it works fantastic.
Click to expand...
Click to collapse
Good for you :good:
Nice News in the Morning
Thx for your Efforts Ray. I'm actually on your
B03 Sl!m7. can i download only the b04 sl!m package and flash it over in twrp, or is it better to follow your steps from the beginning ?
Greets from Berlin :good:
Tunox said:
Nice News in the Morning
Thx for your Efforts Ray. I'm actually on your
B03 Sl!m7. can i download only the b04 sl!m package and flash it over in twrp, or is it better to follow your steps from the beginning ?
Greets from Berlin :good:
Click to expand...
Click to collapse
You can flash it when on SLIM7 - I tested it myself.
So backup your stuff, factory reset, reboot twrp, wipe system, flash B04 bootstack, SL!M8 and magisk19.3
You can try a dirty flash but that's up to you to test. I always prefer clean
a2017u
Hello and Ty @raystef66 for this great work.
i have the A2017U version . which modem should i use?
ty
David
le011 said:
Hello and Ty @raystef66 for this great work.
i have the A2017U version . which modem should i use?
ty
David
Click to expand...
Click to collapse
You're welcome.
You can use this one : https://androidfilehost.com/?fid=1395089523397887283
raystef66 said:
You're welcome.
You can use this one : https://androidfilehost.com/?fid=1395089523397887283
Click to expand...
Click to collapse
Ty.....
great day....
raystef66 said:
You can flash it when on SLIM7 - I tested it myself.
So backup your stuff, factory reset, reboot twrp, wipe system, flash B04 bootstack, SL!M8 and magisk19.3
You can try a dirty flash but that's up to you to test. I always prefer clean
Click to expand...
Click to collapse
I also prefer a Clean flash, so i wait until i'm home after Work and then i let the magic begin.
if any other try the diety flash over his b03 slim7 then please let me/us know, if it's work.
Unjustified Dev said:
I built my own kernel from source to remove zte selinux changes that block magisk. I don't think locking the bootloader is necessary. If someone is already on a stock or stock-like Oreo build, without a vendor partition, they only have to flash system and boot.img. This can be done from fastboot.
Click to expand...
Click to collapse
@raystef66
Thanks for your work! Is the Kernel made by U-Dev included in this ROM and if not @Unjustified Dev could you please show us where to get it and thanks a lot
I had a complete crash on b03 this morning. Phone shut down out of nowhere and wouldn't boot anymore. I then saw this as an opportunity to test b04. So far most bugs (Gboard crashing, sms bug) are gone. I just can't find the D2W setting. Where is it?
Regards
boxemall said:
I had a complete crash on b03 this morning. Phone shut down out of nowhere and wouldn't boot anymore. I then saw this as an opportunity to test b04. So far most bugs (Gboard crashing, sms bug) are gone. I just can't find the D2W setting. Where is it?
Regards
Click to expand...
Click to collapse
Go to settings->featured->gesture&motion, under gesture.
silvbm said:
Go to settings->featured->gesture&motion, under gesture.
Click to expand...
Click to collapse
Ty!
that was it. I really didn't think of this. :good:
on a side note: i use HELIX Engine. [https://play.google.com/store/apps/details?id=com.teamhelix.helixengine]
it used to work fine on 7.1.1.
Now i'm getting this (see 1st attachment),
and i still get this shown every time i reboot. can i get rid of it somehow? it's annoying as it can't be sped up and feels way longer than 5 seconds... (see 2nd attachment)
regards
Who are we?YAAP is a project founded by Adhitya Mohan (@poad42) and Ido Ben-Hur (@idoybh) with the goal of staying close to AOSP in design goals, offer a clean interface, do as much as original development as possible and avoid becoming a kitchen sink and cherry picked mess.
Bug reporting:
DO NOT Report bugs if you're running a custom kernel or you installed Xposed
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab dmesg . (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
DownloadsMi A1Flashing ProcedureInstall Latest Custom Recovery (This is recommended)
Coming from a different rom / OS you'll need to clean flash:
1. Wipe data (Factory reset)
(1.1.) If coming from stock OS you may need to format internal storage
2. Flash rom
(2.1.) After Flashing rom Flash Twrp (dont reboot without installing it)
(2.2)After Flashing Twrp go back to main menu and go to Reboot menu and select Reboot to Recovery Again
(2.2)Flash Gapps (This Recommended) For Root We Suggest Use Magisk Canay Builds (check below for download link)
3. Rejoice
For dirty flash just skip step 1, 1.1
and possibly 2.1 if your mods support addon.d (ex: Magisk)
It does not matter when you flash the firmware zip, and you only need to flash it once per firmware version
XDA:DevDB Information
Yet another AOSP project, ROM for the Mi A1
Contributors
murtaza1326
Source Code: [url]https://github.com/yaap[/URL]
Device Tree: [url]https://github.com/yaap/device_xiaomi_tissot[/URL]
Common Device Tree: [url]https://github.com/yaap/device_xiaomi_msm8953-common[/URL]
Vendor Tree: [url]https://github.com/yaap/vendor_xiaomi[/URL]
Kernel Source Code: [url]https://github.com/yaap/kernel_xiaomi_tissot[/URL]
ROM OS Version: Android 11
ROM Kernel: Linux 4.x
ROM Firmware Required: v10.0.24.0 (Pie) (August)
Based On: AOSP
Version Information
Status: Alpha
Created 2020-09-20
Last Updated 2020-10-06
Working:
Camera/Video/Mic
Fingerprint
GPS
IMS (VoLTE)
RIL
Video playback
Wi-Fi
NightLight
CTS
Broken:
WFD
Bubbles
Switching back to wifi after using hotspot
(need to reboot to use wifi again)
Note: The ROM Does Not Include Gapps Feel Free to flash any gapps of your likings Nik Gapps are Recommended
For Root Magisk Canary Build(Compatible with R Only) is Working Fine This Works Perfectly (Do Not Update it)
Here
Credits Section
I am not alone to bring it up to you guys alone there are many many and many people who helped me to achive this
and i would like to mention them
First I would like to thanks
@abhinavagrd_1129 even tho me and him started bringing up trees differently he was always there to guide me
& i would like to tell you that his Aosp Beta 3 Rom Inspired me to try to bringup trees
@poad42 (Our Lead Dev of Project Yaap is the one who helped me alot to fix many bugs including the lags we were facing he pointed out fix to me
@SagarMakhar he is the one who fixed my noobish mistake i made everytime (also helped me to fix ril in the previous version)
@gotenksIN a guy who also stucked with his own bringup as well i was, we disscussed about bugs and different things together
@shivatejapeddi thanks to him VNDK29 issues were solved
@Lostark13 pointing and hinting me out for diffrent smaller things
Vince Device Devs (i picked there fixes thanks alot guys )
my mates in tissot maintainer TG group
also my testers ( i uslly do my own testing but at some point they helped me to too thanks alot guys)
if i miss anyone from the list do let me know :laugh:
New Changelogs :-
Code:
Device Side:-
Enforcing Now
CTS Passes Without Root(Tissot FP No More Pixel Props)
Fixed USB Teathering
Source Side:-
Merged Latest ASB (October)patch r5
Added Q/S Customisations
Added Clocks In Styles & wallpaper app
Added DT2W & DT2Sleep Gestures
Added Brightness Slider Customization
Added Custom Footer Text Support
Old Changelogs :-
Code:
Fixed Night Light
Fixed 3rd Party Apps Not Detecting Fingerprint
Fixed Wifi & Wifi Hotspot Toogle
Fixed CTS (With Root (No More Pixel Props Needed))
Xiaomi Parts Removed Vibration Controls Completly
Xiaomi Parts (New Adaptive Icons will match other android R icons)
Source side features will be added soon
Piru?
Congratulations ??
Harvey_Spectar said:
Piru
Congratulations ??
Click to expand...
Click to collapse
tnq sar
Good to See on 11 too..
Weww.. A11 going lit ??
Pro!!!! Nice work bruh!
Gawd
Sent from my Mi A1 using Tapatalk
What is the mean of "ROM Firmware Required: 10.0.24 (August)"?
Where can I found the ROM firmware?
There is some " must" to install it?
I am sorry if these are silly questions
sergiobh said:
What is the mean of "ROM Firmware Required: 10.0.24 (August)"?
Where can I found the ROM firmware?
There is some " must" to install it?
I am sorry if these are silly questions
Click to expand...
Click to collapse
sorry for inconvenience updated info
edit: i have added links for required firmware there shouldnt be a issue to find it somewhere else
Hi, @murtaza1326, thanks for your great work!
Nice to see that you're working on 11
I flashed YAAP and I found that fingerprint sensor is getting harder to detect fingertips (much less sensible, perhaps?).
Also, I see that if I just flash or update Official Magisk Canary, after device reboots, it goes to Fastboot mode and never boots System. I found that a solution was flashing that "MagiskR" zip, found at the other Android 11 ROM, but once installed, I have to avoid updates... otherwise, problem will appear.
?
KaaMyA said:
Hi, @murtaza1326, thanks for your great work!
Nice to see that you're working on 11
I flashed YAAP and I found that fingerprint sensor is getting harder to detect fingertips (much less sensible, perhaps?).
Also, I see that if I just flash or update Official Magisk Canary, after device reboots, it goes to Fastboot mode and never boots System. I found that a solution was flashing that "MagiskR" zip, found at the other Android 11 ROM, but once installed, I have to avoid updates... otherwise, problem will appear.
Click to expand...
Click to collapse
it could be different sensor like fpc ? i will see and i will fix it thanks for informing about magisk
KaaMyA said:
Hi, @murtaza1326, thanks for your great work!
Nice to see that you're working on 11
I flashed YAAP and I found that fingerprint sensor is getting harder to detect fingertips (much less sensible, perhaps?).
Also, I see that if I just flash or update Official Magisk Canary, after device reboots, it goes to Fastboot mode and never boots System. I found that a solution was flashing that "MagiskR" zip, found at the other Android 11 ROM, but once installed, I have to avoid updates... otherwise, problem will appear.
Click to expand...
Click to collapse
i need more details on your sensor type if you can provide me
check this screenshot it has Fingerprint model stated that can you tell us what it shows there for you because as far as i and my tester tested this has blazing fast Fingerprint sensor
murtaza1326 said:
i need more details on your sensor type if you can provide me
check this screenshot it has Fingerprint model stated that can you tell us what it shows there for you because as far as i and my tester tested this has blazing fast Fingerprint sensor
Click to expand...
Click to collapse
Friend, your screenshot seems to have been deleted
Well, while that, all I could tell is I'm coming from DerpFest, I have changed back to that ROM because I need to use my phone everyday. In that ROM fingerprint if easier to detect fingerprints.
murtaza1326 said:
i need more details on your sensor type if you can provide me
check this screenshot it has Fingerprint model stated that can you tell us what it shows there for you because as far as i and my tester tested this has blazing fast Fingerprint sensor
Click to expand...
Click to collapse
Hello prosur!
KaaMyA said:
Friend, your screenshot seems to have been deleted
Well, while that, all I could tell is I'm coming from DerpFest, I have changed back to that ROM because I need to use my phone everyday. In that ROM fingerprint if easier to detect fingerprints.
Click to expand...
Click to collapse
You can still check which fingerprint sensor your device have
Takeshiro04 said:
You can still check which fingerprint sensor your device have
Click to expand...
Click to collapse
Don't know how. Screenshot would have helped me, but was deleted. Please tell me how to check that.
KaaMyA said:
Don't know how. Screenshot would have helped me, but was deleted. Please tell me how to check that.
Click to expand...
Click to collapse
Install Device info apk and check the fingerprint sensor
murtaza1326 said:
i need more details on your sensor type if you can provide me
Click to expand...
Click to collapse
Mr Magneto said:
Install Device info apk and check the fingerprint sensor
Click to expand...
Click to collapse
I have installed "Device Info HW" app and it tells that my sensor variant is "goodix".