XZ/KAGURA/F8331 OmniROM BUILDS
PIE 9.0
DOWNLOAD WEEKLY
REQUIREMENTS TO SUCCESSFULLY FLASH OMNIROM:
1. The device has the latest stock ftf
2. The device has an unlocked bootloader
3. The ODM image zip (version 9) has been downloaded from HERE, and the ODM image has been extracted from it
4. The WEEKLY zip file has been downloaded and copied to the device
INSTALLATION INSTRUCTIONS:
1. Reboot device to fastboot mode, and flash the ODM image with this command
Code:
fastboot flash oem <ODM image>
2. Reboot device to TWRP and flash the WEEKLY zip file
3. (If coming from an 8.1 ROM) Fix /dsp SELinux labels with the dsp-label-fixer.zip
4. (Optional) Flash a gapps package
5. Reboot device to system
CURRENT ISSUES ON OFFICIAL:
1. Device wakes up by itself every 5 seconds, reason unknown
2. Camera quality is suboptimal
KERNEL SOURCE: https://github.com/omnirom/android_kernel_sony_msm/tree/android-9.0
BUG REPORTS
REPORT BUGS ONLY:
- AFTER A CLEAN INSTALL
- USING STOCK OMNI KERNEL
- NO MODS OF ANY SORT
OMNI GERRIT REVIEW
https://gerrit.omnirom.org/
DISCLAIMER:
No one is responsible for any damage done to your device but YOU. You've been warned.
XDA:DevDB Information
[ROM][XZ][P][9.0][WEEKLY]OmniROM, ROM for the Sony Xperia XZ
Contributors
oshmoun, humberos, local__hero
Source Code: https://github.com/omnirom
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
ROM Firmware Required: latest stock ftf
Version Information
Status: Beta
Created 2019-03-17
Last Updated 2019-05-31
Thank you for the separate this from the other pie roms.
I will flash it after I arrive home.
Thank you all for the hard work!
Sent from my kagura using XDA Labs
I'm loving the fact Omnipie is official. I will be flashing this right now. Thank you so much.
Finally flashed! been using it for less than an hour, i can say that its definitely good for daily use. Camera seems better and hasnt crashed yet (like it use to), mic actually picks up audio properly, brightness slider is finally proportional to the brightness level, and its pie
however, the stereo speaker seems to muffle at high volumes (especially with the ringtones and less with youtube, but still a little prevelent), app opening times seem a little longer than 8.1, and 120HZ still doesnt work
im also curious why the linked odm isnt the latest one (im pretty sure the latest is 1st march not feb)
anyways, thanks dev! (may be editing this thread after more use for battery etc)
XxperexX said:
however, the stereo speaker seems to muffle at high volumes (especially with the ringtones and less with youtube, but still a little prevelent)
Click to expand...
Click to collapse
Could it be this kernel bug: https://github.com/sonyxperiadev/bug_tracker/issues/336 ? Looks like the sonyxperiadev team is working on it.
XxperexX said:
im also curious why the linked odm isnt the latest one (im pretty sure the latest is 1st march not feb)
Click to expand...
Click to collapse
The March 1 release says "Android 8.1", the linked one looks like the latest for Pie.
sinivalas23 said:
Could it be this kernel bug: https://github.com/sonyxperiadev/bug_tracker/issues/336 ? Looks like the sonyxperiadev team is working on it.
The March 1 release says "Android 8.1", the linked one looks like the latest for Pie.
Click to expand...
Click to collapse
Ah, your correct it does say 8.1 my bad
opps
I saw this version from delta updater (using 8.1 omni) and immediately downloaded flashed oem for pie and downloaded omni 9 but it stucked new omni animated logo. Waited like 10 minutes but nothing happened then rebooted phone but same thing happened. Should i wait more or something went wrong?
Im here with OmniROM freshly flashed trough Open Delta.
I have some problems. First boot never ends, BUT restart worked for me but I have another problem.
Now I need 10 min to unlock the phone when Im lucky.
I unlock with the code and then its instantly relock and it say I cant use fingerprint for first unlock, so I use code again and not work again and still can't use fingerprint.
I do this A LOT OF TIME before I can use my phone. Sometimes it helps sometimes not if I not unlock my phone but use corner dial icon first and then if its ask for code i use it and then I got SystemUI crash error again and again and again.
As I said I try to repeat this methods for like 10 min after every restart. I tried to delete some maybe not compatible apps with this new update but still nothing. Now I will remove some Magisk modules. I will write again.
KikiGames said:
Im here with OmniROM freshly flashed trough Open Delta.
I have some problems. First boot never ends, BUT restart worked for me but I have another problem.
Now I need 10 min to unlock the phone when Im lucky.
I unlock with the code and then its instantly relock and it say I cant use fingerprint for first unlock, so I use code again and not work again and still can't use fingerprint.
I do this A LOT OF TIME before I can use my phone. Sometimes it helps sometimes not if I not unlock my phone but use corner dial icon first and then if its ask for code i use it and then I got SystemUI crash error again and again and again.
As I said I try to repeat this methods for like 10 min after every restart. I tried to delete some maybe not compatible apps with this new update but still nothing. Now I will remove some Magisk modules. I will write again.
Click to expand...
Click to collapse
you need to do a full wipe before upgrading to p
Just as @oshmoun said; before flashing new ROMs, it's imperative to do full wipe (if you don't want to lose all your data, then do a full backup in TWRP), as flashing without full wiping can cause TONS of problems. Don't be lazy and follow the instructions properly.
oshmoun said:
you need to do a full wipe before upgrading to p
Click to expand...
Click to collapse
I used the same rom before but the last update. I updated through OpenDelta.
Hello !
It's cool to see our XZ is alive !
I have some problems with this rom after a full wipe and update to oem V6 :
- no sounds during calls, no mic, no earphone, no sounds on speaker
- Magisk 18.1 not working
- With official camera app, while using the flash, only the autofocus led is lit, the second and much powerful led is never triggered resulting on dark shots
For now that's all
Thx
Performance is somewhat distressed and the camera does not work for the sound is not working after restarting the device is improving
KikiGames said:
I used the same rom before but the last update. I updated through OpenDelta.
Click to expand...
Click to collapse
you cant do that. its pretty misleading having it available on that opendelta ota thingy. you have to follow the instructions in this thread
Flashed data, cache and dalvik, factory reset. And installed latest nightly with gapps and magisk 18.1.
Only reason I did it this way is because I was on a unofficial build on Omni. Everything is working as it should. Very snappy and no lag. Still have to see how the ROM handles after it's settled for a couple day, but right off the bat it's amazing. Thank you very much Dev, and happy to see you back on XDA.
XxperexX said:
you cant do that. its pretty misleading having it available on that opendelta ota thingy. you have to follow the instructions in this thread
Click to expand...
Click to collapse
Why this ROM showed up as an update then?
I just don't understand it.
Nevermind this is my main and only phone and I work 4 days straight before I can use my PC so I need to use this ROM buggy for me. :/
KikiGames said:
Why this ROM showed up as an update then?
I just don't understand it.
Nevermind this is my main and only phone and I work 4 days straight before I can use my PC so I need to use this ROM buggy for me. :/
Click to expand...
Click to collapse
You need a PC to flash this. Follow all steps in order and it'll work. Always remember, unless you have a messaging app that backups texts, you will lose them flashing a cfw. Always always backup anything you don't want to lose.
---------- Post added at 12:56 AM ---------- Previous post was at 12:28 AM ----------
I've had a reoccurring issue on the unofficial and official builds so far. I do not have the option to use my phone when calling unless speaker phone or a Bluetooth headset. I cannot put the phone to my head and use normally. Is there any kind of option to fix this nuisance. Any feedback is truly appreciated
Every 9.0 ROM I ever flash, I always seem to have the same problem. Whether its dirty flashing, or starting with flashtool, to CMD, and then to TWRP, the same problem seems to happen. After the ROM has settled, audio quality through calls becomes a huge problem. I'm not sure if I'm doing something wrong, but it has been a persistent bug, next chance I get for the next nightly ill send a logcat, kinda cant not since back on stock. I need good call quality for work lol. Either way, thank you for bringing OMNI to 9.0 official
anyone having problems with video playback? videos dont play on instagram, youtube or snapchat. using magisk 18.1 and latest omni 9 rom
edit: nvm, found out that the Google camera fix module for magisk was the problem
Related
Summarized Standard Disclaimer: use at your own risk. I use it at mine
*Full wipe recommended if coming from another rom due do the settings database varying and no way to make them compatible*
My personal Omni Rom 5.0 is based on omnirom with the following additions:
CM12 File Manager
CM11 ssh terminal commands
Bash shell
Nano text editor
Koush's full featured open source superuser integrated into settings***(see potential quirk)
Cyanogenmod custom host name
Cyanogenmod screen off volume key long press music control
The list of personal touches isn't very long right now but they include
Battery percent displayed next to battery icon
Battery icon changes color based on percent: 0-15 red, 16-50 yellow, 51-100 green
Disabled lock screen full screen music.
Disabled SELinux at the kernel
Up to 1.6GHz CPU OC
Automatic 400MHz GPU OC
Not Working/Quirky
Bluetooth audio
Mic can be quirky.
Stock camera (not included) would crash on camera change, photo/video change. Try this open source alternative instead. Full featured, nice and fast.
AOSP keyboard swipe doesn't work: google's fault.
Cellular data probably doesn't work. phone call audio doesn't work. The rest is reported ok.
Flashing SuperSU might cause issues since the su daemon is started by the ram disk script since boot scripts apparently don't work.
Plugging in a charger when turned off causes the tablet to turn on with the touch screen disabled.
Everything else not listed as a quirk probably works.
*First Time*
-Read second post FAQ and other important information
-Make titanium backup (highly recommended)
-Flash TWRP 2.8.1.0
-Flash fixed twrp 2.8.0.0 for TMobile users
-Reboot into new recovery
-Make recovery backup (meh, I don't usually do it but you have been warned)
-Full wipe
-Format system
-Install rom
-install gapps (you can use another one if you want. I always provide the most minimum gapps)
-reboot
-TURN ON WIFI IMMEDIATELY AS SOON AS POSSIBLE
*Subsequent flashes*
-TURN ON WIFI BEFORE REBOOT RECOVERY
-Install ROM
-Install gapps
-Reboot into rom
-Reapply any adblocking hosts file.
Downloads
Mediafire folder (discontinued)
Gapps Android File Host
TWRP Android File Host
Wifi ROM Android FIle Host
3G ROM Android FIle Host
TMobile ROM Android File Host
Credits:
-decatf: your patches were vital to the rom
-drewwalton19216801: used your gapps for the minimal gapps package
-kasper_h: I learned a lot from doing kitkat with you last year
-pershoot: original device/vendor base
-omni team: providing rom
-cyanogenmod team: rom extras
Sources https://github.com/AAccount?tab=repositories
Screenshots: a picture is worth 1000 words but a video is worth exactly 30 pictures/second (mostly).
XDA:DevDB Information
Omni 5.0, ROM for the Samsung Galaxy Tab 10.1
Contributors
AAccount
ROM OS Version: 5.0.x Lollipop
ROM Kernel: Linux 3.1.x
Based On: Omni
Version Information
Status: Weekly
Created 2014-11-24
Last Updated 2014-11-23
Delete
FAQ:
OMFFFFFFG: insane boot loop 10 seconds after lock screen: install any rom from the year 2015.
Missing gapps: remember to reflash after every rom.
Adblock hosts stopped working: remember to reapply ad block hosts after ever flash.
Google maps 9+ doesn't work due to an illegal instruction exception. No practical way to fix it. Install google maps 8.4 it works now. Make sure you use the latest google maps.
No keyboard: Settings --> Language & Input --> Current Keyboard --> Hardware (show input method) turn this on.
AOSP swipe doesn't work: apparently google removed these lines of code from aosp keyboard.
Launcher 3 crashes on boot since Feb 8 build: I switched to CM's launcher since it has some customizability. Go to /data/data/com.android.launcher3 FROM RECOVERY and erase this folder.
THIS IS A TEST ROM. PLEASE REMEMBER THAT
For those of you who are itching to try the android 5.1 build I've done some basic quick testing and I like how it's going. The chromium bug I got this afternoon seems to be taken care of with 2 commits. Look at them if you want to know the secret
Installation Instructions (may not be complete as I've installed a lot of zip files. Please try and fill in the missing holes as the rom does install and boot)
Reboot recovery
Wipe data
Format system
RE reboot into recovery
install rom
install my recommended android 5.0 gapps (have heard issues using others but not tried it myself)
try it out
report the bugs
What works: everything thing that worked in 5.0 should continue working.
The camera app has a bit of a "confidence" problem. It will crash on switching to front/back photo/video but if you open it again it will do what you wanted. Sometimes it doesn't crash. Give the camera app patience.
Link: https://www.androidfilehost.com/?fid=95916177934541869
Great news. Downloading asap.
Is just enough to have WiFi on, or it must also connect to some network to avoid bootloop? I'm concerned what happens if I turn it on in the desert where there's no Wi-Fi whatsoever?
Hi.For p4 expected? Thanks.
jaibar said:
Great news. Downloading asap.
Is just enough to have WiFi on, or it must also connect to some network to avoid bootloop? I'm concerned what happens if I turn it on in the desert where there's no Wi-Fi whatsoever?
Click to expand...
Click to collapse
Just on. No connection necessary. You can also feel free to turn it off after a few minutes of just being on. Just remember to turn it back on before a reboot or weekly flash.
@AAccount thanks for bringing omni 5 to the tab was running ur kitkat build, however not sure if anyone else is having install issues, installed twrp 2.8.0.0, factory reset and wiped system, but when trying to install zip i get the following error:
Set_perm: some changes failed
Error excuting binary in zip
Error flashing zip
Any help or info would be appreciated.
Thanks
emu1982 said:
@AAccount thanks for bringing omni 5 to the tab was running ur kitkat build, however not sure if anyone else is having install issues, installed twrp 2.8.0.0, factory reset and wiped system, but when trying to install zip i get the following error:
Set_perm: some changes failed
Error excuting binary in zip
Error flashing zip
Any help or info would be appreciated.
Thanks
Click to expand...
Click to collapse
Well in that case try using the new twrp 2.8.1.0 I just posted. I used that later on in the testing of flashing the rom. It's in the first page instructions under first time flashing. I added a link to the new recovery.
AAccount said:
Well in that case try using the new twrp 2.8.1.0 I just posted. I used that later on in the testing of flashing the rom. It's in the first page instructions under first time flashing. I added a link to the new recovery.
Click to expand...
Click to collapse
Thanks for the reply, but still get the same issue, however if i flash decatf's build first im able to dirty flash your build on top...
emu1982 said:
Thanks for the reply, but still get the same issue, however if i flash decatf's build first im able to dirty flash your build on top...
Click to expand...
Click to collapse
Maybe you should pull a recovery log and post it here so @AAccount can see what's going on.
Can't download twrp2810-wifi.zip from mediafire, always only download 2m then interrupted.
Anybody who can send me a twrp2810-wifi.zip, my email is
[email protected]
Thank you very much!
mediafire failing to download any file I try to download from it
Can't download twrp2810-wifi.zip from mediafire , I am having a problem too with mediafire, each time I click on download , it refreshes loops the download page, no file is able to access, I think it has something to do with our ISP, we moved into a place that you can only use hughesnet to access the web, I can't get DSL from the house my parents got etc.. , I tried the cleaning the cache like this page
http://topkpop.wordpress.com/2010/05/10/solution-for-mediafire-continuous-refresh-download-problem/
it says that removing cookies fixies this but it is not , still failing to access any files off of mediafire, I was able to create a mediafire account , and download their desktop software, but can't get files like from your links to work, it seems , I have tried internet explorer, firefox, and google chrome, each browser doesn't want to let me download etc to save the file, The only thing I have yet to try is use my android tablet to access the links, I don't no if mediafire will work right or not over my android, if my download pc doesn't download it, from my wireless network ,
my android tablet also can't access the files. I just tried to download twrp2810-wifi.zip from mediafire off of browser on android , when you click download it keeps looping and freshing the page, but what it doesn't do is download, I am in US, CA so it shouldn't be blocking me from downloading files, not sure why this seems to be happening, it was not a problem with our old isp before me moved etc..
I don't no if this explains it, but on android , when click download it reloads this page"http://www.mediafire.com/download/6hc9ws7sd96j3nn", instead of this "http://www.mediafire.com/download/6hc9ws7sd96j3nn/twrp2810-wifi.zip" I been tried to click download over and over , even the repair download thing, doesn't do anything , after clicking on download a few, times I got that message.
I am able to use
Downloads
Mediafire folder
Click on the files, and use the copy to my accounts folder option, which sync it to the desktop software, that feature is working for me, just not mediafire download pages
anyway can you give me access to the folder, that has Flash file TWRP 2.8.1.0, since then I could click the copy feature of mediafire, and transfer it to my account on mediafire, and it will download and sync the file to my folder on my computer, thats the only way or simplist way to get passed that looping on download page problem, or maybe copy the file into your mediafire folder if that also possible I hope,
don't have to have the newest version to flash right away , but it would be nice if I was able to access it, to flash anyway, I still got the 2.7 version of twrp, after using android 4.4.4 nameless etc.. before I got problems with mediafire from my web browser problem, and access to cwm boot flash manager too, which I found files on the web for flashing with touch screen option, while browsing the forums here
attached downloads will download no problem, and other websites besides mediafire will also work just fine for me, since it seems to be a mediafire download page problem only bug,
also talking about bugs, does this rom have that power on charging , bug like the rom [AOSP] Android 5.0.0 Lollipop (LRX21V) has?
"Whenever I try to charge the tab while it's turned off, it boots up. Is this a new feature of Android 5.0? Also it doesn't respond to touches. " , on its last page I read that its a new feature of the android 5.0 based on aosp rom, it reads " It turns out there is a new feature in Lollipop to boot from charger but it is not enabled by default. It is only for one specific device at the moment. I reverted the code anyways but the problem still exists. So the issue lies deeper some where." , source information can be found here, http://forum.xda-developers.com/gal...-5-0-0-lollipop-lrx21m-p4wifi-t2938870/page17
if this rom doesn't have that problem, maybe something can be learned from it , to fix the bug in the other rom, since our tablets , don't like that feature, since it locks up our tablets touchscreen from doing anything but hard rebooting them etc.. when plugged into power when in off mode etc...
emu1982 said:
Thanks for the reply, but still get the same issue, however if i flash decatf's build first im able to dirty flash your build on top...
Click to expand...
Click to collapse
Same here, switched from CWM to TWRP 2.8.1.0 and I'm still getting the error D:
AAccount said:
Well in that case try using the new twrp 2.8.1.0 I just posted. I used that later on in the testing of flashing the rom. It's in the first page instructions under first time flashing. I added a link to the new recovery.
Click to expand...
Click to collapse
Was able to download TWRP and gapps just fine but the ReCaptcha you have to complete in order to download the ROM won't load a picture. I have tried on my tablet, phone and computer... Able to pass a ReCaptcha on other pages just fine, clearly an issue with this specific download page. Anyone else having this issue?
L3R0N said:
Maybe you should pull a recovery log and post it here so @AAccount can see what's going on.
Click to expand...
Click to collapse
http://pastebin.com/xSr4TLCY
@AAccount here is a twrp log of the install issue i had trying to install after a full wipe. Hope it helps..
For people with download problems, will it be ok if I register for an account here:
https://www.androidfilehost.com/user/?w=register
Will that be a good file hosting site?
I know its still early development for 5.0 rom versions of android 5.0, do you guys know why scummvm version 1.7.0 release will not download and install, it keeps failing to download for me on android 5.0, from google play website, also the development version 1.8.0 direct from scummvm will install but crashes on play, off of http://scummvm.org/
I know that scummvm app, worked for android 4.4.4 nameless rom, I used it under that android before, never crashed that I can remember, I hope as android 5.0 builds makes progress that whatever causing it to crash gets fixed. I am not sure if its something that needs to be fixed in the android os system of 5.0, or if its something that needs fixing in the scummvm app, that causes it to crash under android 5.0, maybe future development builds of scummvm will fix the crashing under android 5.0.
and below a fix to the charging bug I think its a fix I have yet to test it from this page, since both our based on android 5.0 I am guessing that these files will fix booting on both
source page "http://forum.xda-developers.com/galaxy-tab-10-1/development/rom-android-5-0-0-lollipop-lrx21m-p4wifi-t2938870/page17"
decatf said:
Charging mode should be working now although there are still some issues to be ironed out. Note(!) that ADB is running in while in charger mode. I haven't figured out why yet.
It only requires an update to the boot partition. Flash and reboot.
bootimg-p4-lp-20141125.zip
bootimg-p4wifi-lp-20141125.zip
The problem is that Samsung did not follow the Android method of booting into charger mode. With Android 5.0 this method of booting is not working. So I ported it to work with the Android method. Which means it is booting slightly differently than the old charger mode.
Someone others mentioned issues with overclocking. I have not had a chance to look into this yet.
Click to expand...
Click to collapse
Omni 5.0 p4wifi Nov 23
Re scumm vm... Could it be dalvik vs ART? I have done very little research.. Just know that xposed -framework- (and most modules?) require dalvik.. Put another way, not (yet?) compatible with ART
5.0 has no option for dalvik, whereas 4.4.4 can do both
One possible test: reflash 4.4.4, switch to ART, then see if scumm works?
Or if I am off base, hopefully someone else will chime in...
I never tried the android 4.4.4 under art, so maybe it would of crashed scummvm too , I don't no if its compatable with art maybe thats why, also I did want to note , that unlike the AOSP android 5.0 rom, in this one, google now launcher seems to crash , but I didn't notice crashing in the other android 5.0 , is it because it has had more time to fix the bugs in the os system, since Omni 5.0 p4wifi is a newer rom? I am correct or is their something that needs to be fixed in google now launcher or the build of the rom?
Aosip for Motorola Z2 Force
What is this?
AOSiP is a quality custom ROM based purely on GOOGLE AOSP source since 6.0 release. Twisted with the latest features and blended with stability. We strive for perfection and it shows.
Obligatory Warning: This guide and ROM assumes you know the fundamentals of fastboot, flashing TWRP, and running a flash all. Your warranty is voided because of the unlocked bootloader. This is a Third Party ROM. Things may not work as expected compared to stock (for better or for worse).
Warning 2: If you can't do fastboot commands, do a flash all, root your device or flash TWRP/ROM, please do not ask for help here. If you cannot flash all back to stock, please stay stock for everyone's sake.
Warning 3: if you don't flash the firmware so you are on Oreo on both slots, when you boot after flashing, you'll be on Nougat firmware and have a brick. Try a flash all as that's your only hope on recovering your phone.
How to install
1. Download the latest ROM from here.
2. Prepare your phone for AOSP style ROMs. (download one of the firmwares depending on your model)
Flash the firmware with the .bat file. (See links below or on Post #2)
3. Boot to TWRP
4. Flash TWRP to boot image (with the zip from their website.) Reboot to Newly flashed recovery.
5. Erase oem, data, and system
6. Flash rom like you would any aosp rom, in twrp.
7. Reboot to bootloader
8. run the command "fastboot -w" (this will erase EVERYTHING from your phone, even internal SD, but is needed to have these ROMs work)
9. reboot.
Whats working?
Wifi
RIL
Mobile data
GPS
Camera
Flashlight
Camcorder
Bluetooth
Volte (T-Mobile)
Change quick charge
Fingerprint reader
NFC
Lights
Sound / vibration
Some motomods (soundboost mod doesnt work)
Team Illusion:
Josh Fox (xlxfoxxlx)
Akhil Narang
Sri Harsha (@srisurya95)
Shreesha Murthy
Brett Montague
Known issues
1. WiFi Calling hit and miss
2. Cannot flash Gapps (included temporarily)
3. some Audio recording apps will not have audio recording work (phone functions fine)
4. if you don't fastboot -w, you will not boot.
5. if you don't flash the firmware your bootloader might relock itself and be stuck on Nougat.
6. SElinux is passive (meaning CTS check will always fail until further notice.)
Downloads:
official link(aosiprom.com)
Thanks to everyone at @aosip @mosimchah @moto999999 and @codeworkx for their amazing work
Android OS version: 8.1.0
Security patch level: April 2018
Build author: @Infect_Ed
Source code: https://github.com/AOSiP-Devices/device_motorola_nash - AOSiP source.
https://github.com/InvictrixRom-devices/kernel_motorola_nash - kernel
https://github.com/TheMuppets/proprietary_vendor_motorola - vendor blobs
Contributors
@Infect_Ed @invisiblek @npjohnson @erfanoabdi @joemossjr @jbats @nathanchance
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 4.4.x
Phone Firmware Required: 8.0
T-Mobile
Sprint
Version Information
Status: Stable
Current Stable Version: 1.0
Stable Release Date: 2018-03-28
Created 2018-03-28
Last Updated 2018-04-10
Note: I did not build this. If you want to give thanks for this ROM build, thank @Infect_Ed for building AOSiP, I am just maintaining the support thread for XDA.
Firmware files needed!
T-Mobile:27.1
Sprint: Found em!
Sources Post:
https://github.com/AOSiP-Devices/device_motorola_nash - AOSiP source.
https://github.com/InvictrixRom-devices/kernel_motorola_nash - kernel
https://github.com/TheMuppets/proprietary_vendor_motorola - vendor blobs
Bug reports:
If you don't flash the firmware and your other slot is nougat, after flashing the ROM, you'll brick. (Custom ROM with a locked nougat slot.) Your only hope is attempting an official flash all and try again after flashing the firmware zip in the posts above.
Fair warning and off-topic: I am okay with some off topic questions. If you have a question, please use the search function. If I have addressed the question before, I will not answer and advise to find it in the thread. I will report the post for a mod to delete along with my response to keep the thread tidy. It seems some users think this ROM has international support. It doesn't and won't unless someone with another variant or an unlocked T-Mobile/Sprint model tests, confirms and debugs for that international carrier. Please keep in mind of what I said below regarding this. I posted this on page 20 or so and copying here for better visibility.
Your SIM is locked. You are trying to run a phone off it's intended network. Please don't post those problems here. It isn't ROM related. Like the thread states. It works for T-Mobile and Sprint only on their respective models on their locked networks. Any other tom foolery isn't supported and must be kept out of the thread. After this it will be considered off topic.
Edit: if you have Sprint or T-Mobile service and run into issues with using your (albeit, expensive) international roaming plan, I will assist with that if it works on stock but not AOSP. If you don't have a sprint or T-Mobile sim, I cannot help. Almost all devs on this device won't be able to help. "Almost" all of us are on US carriers.
Click to expand...
Click to collapse
Images posted here
@Uzephi is your device on sprint? Data works but LTE does not? Does the Moto Mods support Hot Swapping? This is great progress and can't wait to see more on this phone.
xDABZx said:
@Uzephi is your device on sprint? Data works but LTE does not? Does the Moto Mods support Hot Swapping? This is great progress and can't wait to see more on this phone.
Click to expand...
Click to collapse
Motomods work with kernel in ROM (hot swapping should as well iirc, I don't use the mods that often where my projector is outdated) LTE doesn't work on Sprint, but 3G and 1xTT works fine.
@Uzephi if we were to flash your kernel, we would lose motomods support?
cervantesjc said:
@Uzephi if we were to flash your kernel, we would lose motomods support?
Click to expand...
Click to collapse
For now, yes. Still trying to get it work. Clang is being a PITA on my build box, having to go to Linaro which can't build the Motorola Greybus driver correctly.
Thanks sir, I appreciate what you've done for the community, finally can go back to my moto from a GS8+
I'm sorry if this is a dumb question but...
Ive never had to install different firmware before on a ROM. If I install this, will it change the process of installing a different ROM in the future?
Thank you.
Sprint varient if it matters by the way.
Edit: I'm sorry for this but is there a way to do this without the .bat file? currently working on OSX
wcain89 said:
I'm sorry if this is a dumb question but...
Ive never had to install different firmware before on a ROM. If I install this, will it change the process of installing a different ROM in the future?
Thank you.
Sprint varient if it matters by the way.
Edit: I'm sorry for this but is there a way to do this without the .bat file? currently working on OSX
Click to expand...
Click to collapse
Open the bat file in a text editor and run each of those commands one by one.
This I'd a dual boot device. Your other slot has the older Nougat bootloader. That firmware flashed the current Oreo firmware to both slots. If you don't do that, and you flash one of these ROMs, you'll reboot to your nougat slot, locked and pretty much screwed without a flash all and luck of being able to flash OEM images in oem mode.
Edit: you won't need to flash this any consecutive times until there is another big firmware update like nougat to Oreo was.
Uzephi said:
Open the bat file in a text editor and run each of those commands one by one.
This I'd a dual boot device. Your other slot has the older Nougat bootloader. That firmware flashed the current Oreo firmware to both slots. If you don't do that, and you flash one of these ROMs, you'll reboot to your nougat slot, locked and pretty much screwed without a flash all and luck of being able to flash OEM images in oem mode.
Edit: you won't need to flash this any consecutive times until there is another big firmware update like nougat to Oreo was.
Click to expand...
Click to collapse
Thank you for the quick reply. I've installed the firmware, but now when I boot to TWRP and try to install the ROM, it instantly fails with ERROR:1. Tried redownloading with a different browser but got the same result. I feel like I'm missing something obvious.
wcain89 said:
Thank you for the quick reply. I've installed the firmware, but now when I boot to TWRP and try to install the ROM, it instantly fails with ERROR:1. Tried redownloading with a different browser but got the same result. I feel like I'm missing something obvious.
Click to expand...
Click to collapse
Flash twrp zip to your phone, reboot to your phone's newly flashed twrp recovery and flash the rom. If I remember right,you need to wipe oem and system before flashing the ROM as well. I'll add that shortly.
Up and running! Thank you!! Still looking around but I do see a built in updater. Will this function 100%? By that I mean, when the Sprint LTE issue is resolved and whatever else is coming will be handled by the updater?
Thanks again very excited to play around.
wcain89 said:
Up and running! Thank you!! Still looking around but I do see a built in updater. Will this function 100%? By that I mean, when the Sprint LTE issue is resolved and whatever else is coming will be handled by the updater?
Thanks again very excited to play around.
Click to expand...
Click to collapse
Yes, since it's official, it checks the link in OP for any new updates.
For anyone using the ROM, are you seeing notification dots, I tried to get them to work, but they're not working for me.
cervantesjc said:
For anyone using the ROM, are you seeing notification dots, I tried to get them to work, but they're not working for me.
Click to expand...
Click to collapse
Working fine for me thru Evie Launcher. Soundboost mod is broken though. My SoundBoost is recognized and the notification says the mod is attached, but the volume steps are reduced to on/off and no sound comes out.
Edited to reflect that only the sound boost mod isn't working AFAIK.
wcain89 said:
Working fine for me thru Evie Launcher. Mods are broken though. My SoundBoost is recognized and the notification says the mod is attached, but the volume steps are reduced to on/off and no sound comes out.
Click to expand...
Click to collapse
Oh, @npjohnson and @invisiblek don't have the sound mod, so they can't get it to work. All of us in the development discord are trying to mail one out, they can't guarantee when it would get fixed.
Edit: added disclaimer to OP. We can only guarantee what we have works. Like when I do my kernel, the only mod I have is the free projector, so that's the only mod I can guarantee works when I do get it working.
I have an extra soundboost I could mail to someone.
Hello everyone. I am opening this thread for the sake of convenience of us users of this ROM so that we stop hijacking the Oreo version thread and have a "clean" place where we can discuss about our experience with this great ROM. So I suggest anything regarding this ROM to be posted here!
You can find the official builds here: https://get.resurrectionremix.com/?dir=hammerhead
DISCLAIMER: I am by no means a developer or maintainer of this ROM, so this cannot be considered an official support thread, just conversation, plain and simple! Moderators can close this thread as soon as an official support thread opens.
Cheers!
I just installed the rom,came from stock. My first impressions are:
-It took 2 reboots to get the camera working. Installed google camera app since the integrated one doesnt show up on app drawer(you can access it from lockscreen though) and it seems to work kinda bad(picture goes black on it sometimes).
-It runs a bit hotter than stock rom. It might be just me though,I have opened the phone a few times to fix the power button which seems to get stuck for me once in a while.
-The default DPI doesn't seem right,everything looks a little bit smaller than it does on stock rom. There is an option to change it though, I set mine to 380 and it looks about right.
I haven't found any other issues yet.
Another note,I think the rom fixed my notification led lol. It didn't work for me on stock rom for some reason.
Pretty good rom overall,I haven't faced any stability issues yet.
edit: Is there any way to lower the resolution?
I upgraded from RR's Oreo build. Before flashing I repartitioned the phone using the method described here and the even more detailed instructions posted by douguluskaien on page 12 of that thread. The flash went very smoothly and although the phone initially ran hot it cooled back to normal after a few hours of what was probably background processing. With the 1.5G system partition I was able to install the micro version of GAPPS. I've had that experience after flashing new ROMs on other phones as well. I also discovered the bundled camera doesn't work and installed Google Camera. After starting up Google Camera, the original camera worked also. I tried connecting bluetooth headphones, and even though I could pair the headset I couldn't get the phone to send audio - it just kept playing through the phone speaker. I also found the default font size a little small, but changing it to Large in the Font Size menu got it back to what seems like normal.
I have one major issue which I realize is not directly related to the ROM. A custom version of TWRP is required to support the non-standard partitions, and that version is based on TWRP 3.2.3 and doesn't support device encryption. Does anyone know if an updated TWRP will be available that will allow me to encrypt the phone and still do recovery-related stuff?
In summary, this is impressively well along for a build that's only been live for a couple of weeks. This isn't my daily driver so I don't need absolute stability, so this is plenty for me for now. I just won't leave the house with it until I can encrypt.
I've been using this ROM for about a month now as a daily driver, so here's my feedback:
ROM is very nice and smooth and feature rich (as expected for RR). I installed it with Opengapps nano, rooted with Magisk. It works very well with the Pixel launcher I grabbed from here.
Some drawbacks I noticed:
Battery life is rather bad. I get 1h30m SOT at best with very mild usage (mostly site browsing and a little bit of social apps and YT video watching) . Then again I am still using the 5yr old battery that came with the phone...
The phone runs very hot (too hot to hold!) after using it for some time. It cools down rather fast if you let it be for a while, though.
Sometimes the camera is crashing (the notorious "can't connect to camera" error). usually a reboot fixes this.
Sometimes it takes a while for the device to wake up after pressing the power button.
I got some soft reboots under device heavy load. Mostly I get them when using the Rocket player music app, and it tries to load a large music folder. Phone freezes, then soft reboots.
SElinux is set to permissive and the build is signed with test keys. Maybe the first thing is caused by the latter, I don't know really....
Overall, it is a good ROM with room for improvement. However, I am concerned about its maintenance status. No update since May 14, so I keep my fingers crossed.
New build (28/07) uploaded!
hammerheadache said:
New build (28/07) uploaded!
Click to expand...
Click to collapse
I am not able to install it giving me ERROR 7
hammerheadache said:
New build (28/07) uploaded!
Click to expand...
Click to collapse
Do you know about change log??
What features added?
I want to update it tonight
As I state at the first post, I am not a developer, neither I have any involvement in this project and the people behind it. So I can't provide any support apart from my experience as a user.
sacmat said:
I am not able to install it giving me ERROR 7
Click to expand...
Click to collapse
I didn't flash this build so I don't know if it works or not. I have switched to a different ROM. However, could you elaborate? Do you come from another ROM? Did you dirty flash? Is your device repartitioned? Usually error 7 in TWRP means there's not enough system space...
m.morcielago said:
Do you know about change log??
What features added?
I want to update it tonight
Click to expand...
Click to collapse
I do not see any changelog file on the download page. Unfortunately with no official support thread, there are no official answers as well...
I flashed this build this morning by dirty way
Unfortunately Bluetooth is not working
It can find the other devices but can not connect to them
1- How can I fix it?
2-How can I downgrade to previous build?
hammerheadache said:
As I state at the first post, I am not a developer, neither I have any involvement in this project and the people behind it. So I can't provide any support apart from my experience as a user.
I didn't flash this build so I don't know if it works or not. I have switched to a different ROM. However, could you elaborate? Do you come from another ROM? Did you dirty flash? Is your device repartitioned? Usually error 7 in TWRP means there's not enough system space...
I do not see any changelog file on the download page. Unfortunately with no official support thread, there are no official answers as well...
Click to expand...
Click to collapse
Thanks for the idea, I had just repartitioned, so I had format my entire phone, (before that i had taken the backup ), and I had successfully installed the rom, I got an strange issue of WIFI connectivity, as I am not able to connect to my wifi which is having Hidden SSID, but i am successfully connected with the hotspot from my another primary phone. i haven't tested the bluetooth yet.
I dirty flashed the new build this morning. Haven't tried bluetooth or camera yet, but Wifi is working fine. As usual, the phone heated up for about a half hour after the flash and then the temp dropped and stabilized. Battery life is not great, like the May build, and there is often a long delay responding to the power button, especially shortly after power-up, but the build seems pretty solid.
Casting isn't finding anything to cast to in the most recent build. Camera worked fine.
New build available (Aug 4) as seen at ROM's dl page.
Bluetooth pairing now working for me on last release
Hi installed this ROM in clean maner but i got intermitent issue with sim card. Not sure if it is only sim issue or reboot but phone ask my pin code.
Looks like @voidz777 is the maintainer for RR Pie as well:
https://github.com/ResurrectionRemix-Devices/api/commit/8388c5df5069cf04df04facbdc22a2bfd8890185
New build (09/08) in case someone missed it... Link in OP
sacmat said:
I am not able to install it giving me ERROR 7
Click to expand...
Click to collapse
okay so to fix this you will have to repartition your system.
This thread will help you. https://forum.xda-developers.com/go...ment/repartition-nexus-5-repartition-t3844395
Repartitioning is the fix to error 70 while flashing gapps as well as error 7.
New build (Sep 16) available! Link in OP.
princeknockouts said:
okay so to fix this you will have to repartition your system.
This thread will help you. https://forum.xda-developers.com/go...ment/repartition-nexus-5-repartition-t3844395
Repartitioning is the fix to error 70 while flashing gapps as well as error 7.
Click to expand...
Click to collapse
Thank you for the tip, I followed the thread and was able to install RR 7 without any trouble. This might not be the right place to ask, but would you have any info on how to install SuperSU on RR 7, or is there perhaps another root method that we must use? Thanks in advance, I can't seem to find information on it anywhere and rather than continuing to bang my head against the wall I thought I'd ask.
** Standard Disclaimer: Unlocking your Bootloader will Void your Warranty. I take no responsibility for this or for any bricked devices. These thing should go without saying at this point, but there they are. If you are here, I assume you are familiar with LineageOS, TWRP, and moving from MIUI to AOSP-based ROMs**
I've built a clean version of LineageOS 17.1 for Mi 9 that includes Signature Spoofing, but no other modifications.
This will allow those who are interested to get full MicroG support without the need of using any sort of Patcher or Magisk/XPosed Module. YOu all may have used my previous LineageOS Clean,Stock ROM and this is just an updated build of that ROM + Signature Spoofing to make life easier for those who want MicroG.
I flashed this and followed the simple steps of installing F-Droid, adding the MicroG Repo, and Installing the necessary packages via F-Droid and confirmed MicroG Self-check passes all the tests (once you finish granting the necessary permissions for each).
I prefer this over the NanoDroid or other patching methods as a much cleaner way to use MicroG with LineageOS.
Proprietary Blobs/Device Tree are DRG-Developer's as referenced in their post: here
Kernel source is by DRG-Developer: here
Xiaomi Hardware package used is the primary LineageOS from their github here
My reason for this is that there does not seem to be an officially-supported build for our device on the LineageOS for MicroG project or a recent, unofficial build.
What Works:
Pretty much everything from what I can tell
Fingerprint Sensor it working like a champ so far.
DT2W/DT2S
NFC Seems to be working but I don't have a device to test against
Known Issues:
You tell me...
Download:
849.98 MB file on MEGA
mega.nz
Prerequisite:
Make sure you are running a current AOSP/MIUI ROM with the latest firmware flashed and TWRP Installed
Install:
From TWRP:
1) Wipe Date (standard wipe)
2) Format Date ---> 'yes'
3) push ROM zip to /sdcard/
4) Flash ROM zip
4b) - OPTIONAL - Flash Magisk Zip for Root
5) Reboot to system
If you want to to install MicroG, just follow the steps outlined here in the "Install" section to get F-Droid installed, add the MicroG Repo, and install the handful of apps needed. No need for any of the patching steps.
DRG-Developer's device trees were last updated on 2020-10-18 so expect this build to reflect that. So far everything seems to function very well.
Does it support GApps too or it's only for MicroG?
Edit:
I test it and It's working well with GApps
Thanks for your build.
Vogie said:
Does it support GApps too or it's only for MicroG?
Edit:
I test it and It's working well with GApps
Thanks for your build.
Click to expand...
Click to collapse
Thanks for testing! If you find any bugs, please post them here. I may not be able to troubleshoot everything but at least other users will be aware.
What changes between your older release of LineageOS 17.1? https://forum.xda-developers.com/t/...ineageos-17-1-clean-stock-2020-07-10.4041523/
ICanTrollU said:
What changes between your older release of LineageOS 17.1? https://forum.xda-developers.com/t/...ineageos-17-1-clean-stock-2020-07-10.4041523/
Click to expand...
Click to collapse
Later/updated device trees and built-in Signature Spoofing that you don't get with stock Lineage.
photonmedia said:
Thanks for testing! If you find any bugs, please post them here. I may not be able to troubleshoot everything but at least other users will be aware.
Click to expand...
Click to collapse
Sure,
I'm using this ROM for daily use since yesterday and seems like very stable since now and battery life is good.
I missed `Internet Band-with Speed indicator` and `three finger swipe screen shot gesture` that I think these features are not available in LineageOS.
Vogie said:
Sure,
I'm using this ROM for daily use since yesterday and seems like very stable since now and battery life is good.
I missed `Internet Band-with Speed indicator` and `three finger swipe screen shot gesture` that I think these features are not available in LineageOS.
Click to expand...
Click to collapse
Yes, I do not believe those are included in stock LineageOS.
photonmedia said:
Yes, I do not believe those are included in stock LineageOS.
Click to expand...
Click to collapse
I didn't find any issue that relate to ROM, it's quite stable
I just have a issue on ANXCamera self camera that force close the ANXCamera that I think is not related to ROM
photonmedia said:
...
What Works:
...
NFC Seems to be working but I don't have a device to test against
Click to expand...
Click to collapse
This morning I checked NFC by sending a picture from my MI 9 to my wife's Mi 9T (also equipped with LOS). The transfer was successfull!
Thank you very much for providing this clean (stock) ROM!
Hi,
I've just unlocked my device and flashed Mauronofrio's TWRP afer that, i've installed this rom. And everytime it seems to be bootlooping. Showing the MI logo and after that it turns off and goes back to the Mi logo again. I've tried flashing it a few times, wiping data / system ETC. At the moment I'm restoring it with flashtool to get it back working. But am I doing something wrong?
nico445 said:
Hi,
I've just unlocked my device and flashed Mauronofrio's TWRP afer that, i've installed this rom. And everytime it seems to be bootlooping. Showing the MI logo and after that it turns off and goes back to the Mi logo again. I've tried flashing it a few times, wiping data / system ETC. At the moment I'm restoring it with flashtool to get it back working. But am I doing something wrong?
Click to expand...
Click to collapse
Did you wipe data AND "Format" Data? When you Format data is asks you to confirm by typing "yes" in the TWRP Recovery. Try Wiping and Formatting data, then push the ROM to the phone and Flash.
Ah that was probably it. ADB Sideload wasn't co-operating so i've flashed the rom first and after that wiped + formatted the data. Thanks! I've just restored the phone but will try this later again.
nico445 said:
Ah that was probably it. ADB Sideload wasn't co-operating so i've flashed the rom first and after that wiped + formatted the data. Thanks! I've just restored the phone but will try this later again.
Click to expand...
Click to collapse
Also, be sure you are coming from an updated ROM running current firmware.
Thank for your build ;-)
Are NFC Payements working on it?
john_matrix said:
Thank for your build ;-)
Are NFC Payements working on it?
Click to expand...
Click to collapse
I have not tested payments. Another user confirmed that file transfer via NFC works. I do not use NFC for payments so cannot test.
Hi, does screen off fod work?
Your rom is really simple stock rom, but there is something that I can't make it work. Waze has been my pain, the map dont load and I cant make it run. Anyway you did a good job. You discovered how can we put updates in the rom?
theandroid02 said:
Hi, does screen off fod work?
Click to expand...
Click to collapse
No, you have to double-tap to wake or hit the power button to wake the screen before you can use the fingerprint scanner.
Vinicius7 said:
Your rom is really simple stock rom, but there is something that I can't make it work. Waze has been my pain, the map dont load and I cant make it run. Anyway you did a good job. You discovered how can we put updates in the rom?
Click to expand...
Click to collapse
After installing, did you Install F-Droid and enable the Magisk repositories to install the necessary Magisk Modules and Location Backends? Then in the MicroG settings ensure all the checkboxes are checked?
Thanks for making this ROM. Really appreciate it.
The only small issue I am noticing is that my finance apps (example: banking apps, stock trading apps) popup an alert saying that my device is rooted (even though it is not) and this could be a security risk. The apps do still function but its a bit annoying to see this alert every time I launch the app.
Is this because the ROM has been signed with public keys? This alert does not appear when I used the iode OS ROM for Mi 9 or when I use the official Lineage OS for MicroG ROM on my Mi 8.
dmahtani said:
Thanks for making this ROM. Really appreciate it.
The only small issue I am noticing is that my finance apps (example: banking apps, stock trading apps) popup an alert saying that my device is rooted (even though it is not) and this could be a security risk. The apps do still function but its a bit annoying to see this alert every time I launch the app.
Is this because the ROM has been signed with public keys? This alert does not appear when I used the iode OS ROM for Mi 9 or when I use the official Lineage OS for MicroG ROM on my Mi 8.
Click to expand...
Click to collapse
I'm not sure. It could be the Signature Spoofing aspect. I don't think iode has that and I know stock LIneage does not.
Do you have Magisk installed?
LineageOS is a free, community built, aftermarket firmware distribution of Android 12, which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. A direct link to kernel sources can be found here. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Instructions:
https://wiki.lineageos.org/devices/sake/install
Download:
https://download.lineageos.org/sake
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.
Thank you for that!!
Pre install of stock android 12 needed?
thanks pro
NisseGurra said:
Pre install of stock android 12 needed?
Click to expand...
Click to collapse
Yes, I'll update description to clarify that. If you try and boot into the LOS 19 recovery with Android 11 firmware it will crashdump.
GMS = Google ? Service?
I'm trying this right now. Hopefully I make it functional before I have to head to bed.
eVen123 said:
GMS = Google ? Service?
I'm trying this right now. Hopefully I make it functional before I have to head to bed.
Click to expand...
Click to collapse
Google Mobile Services, basically google apps and services
Also @ZVNexus, the google drive folder for the build without GMS seems to be empty, has it been removed?
Update:
I had a clean flash of:
WW-ZS590KS-31.0803.0403.54-DEV-2109-M3.13.24.46-SM8350_0000110-1.1.25-user_20210831-release_for_google
I was able too boot to TWRP. It wouldn't allow me to flash your zip. I rebooted to bootloader and flashed vendor_boot. After that, I was unable to get to TWRP recovery. I flashed boot and got to some sort of LOS-like recovery (purple color).
Flashing the image now.
UPDATE: Success. However, I was in a bootloop. Got back to recovery, it suggested to wipe data. It looks like LOS is now performing it's first boot.
UPDATE 2: First boot successful! Got into language and network selection. Seems to be stuck on "Getting your phone ready" step. Scratch that, we got past that! Big success!
UPDATE 3: Got past that bit, it was in "Getting your phone ready" process a long time. Booted now!
AWESOME, thank you for your work!
For anyone else reading, the TLDR:
Installed the above zip (downloaded from official ASUS site). https://www.asus.com/Mobile/Phones/ZenFone/Zenfone-8/HelpDesk_Manual/
Downloaded all the files provided by the author
Flashed boot and vendor_boot
Went to recovery, flashed the ROM zip with "apply update" and "sideload"
Bootloped a couple more times
Recovery suggested I clean data. I did.
...
Works
UPDATE 4: Note - it seems that fingerprint still makes full screen go max brightness + it doesn't work with screen off.
Adaoh said:
Google Mobile Services, basically google apps and services
Also @ZVNexus, the google drive folder for the build without GMS seems to be empty, has it been removed?
Click to expand...
Click to collapse
Nothing was ever uploaded to it. I haven't made a build without GMS yet.
eVen123 said:
Update:
I had a clean flash of:
WW-ZS590KS-31.0803.0403.54-DEV-2109-M3.13.24.46-SM8350_0000110-1.1.25-user_20210831-release_for_google
I was able too boot to TWRP. It wouldn't allow me to flash your zip. I rebooted to bootloader and flashed vendor_boot. After that, I was unable to get to TWRP recovery. I flashed boot and got to some sort of LOS-like recovery (purple color).
Flashing the image now.
UPDATE: Success. However, I was in a bootloop. Got back to recovery, it suggested to wipe data. It looks like LOS is now performing it's first boot.
UPDATE 2: First boot successful! Got into language and network selection. Seems to be stuck on "Getting your phone ready" step. Scratch that, we got past that! Big success!
UPDATE 3: Got past that bit, it was in "Getting your phone ready" process a long time. Booted now!
AWESOME, thank you for your work!
For anyone else reading, the TLDR:
Installed the above zip (downloaded from official ASUS site). https://www.asus.com/Mobile/Phones/ZenFone/Zenfone-8/HelpDesk_Manual/
Downloaded all the files provided by the author
Flashed boot and vendor_boot
Went to recovery, flashed the ROM zip with "apply update" and "sideload"
Bootloped a couple more times
Recovery suggested I clean data. I did.
...
Works
UPDATE 4: Note - it seems that fingerprint still makes full screen go max brightness + it doesn't work with screen off.
Click to expand...
Click to collapse
Updated OP to specify the exact version you need to be on [31.1004.0404.81 (or .71)]. Basically just a public release, not a beta.
What I was able to test now, it's pretty good. Very usable already!
Bugs I notice:
The GMS seems to be a bit slower than expected.
Fingerprint doesn't work with screen off.
Fingerprint request location is not marked.
Fingerprint maxes brightness of whole display.
Task switcher sometimes doesn't work.
Bottom navigation sometimes disappears.
It keeps warning me about SELinux not enforcing issue. Not sure if that's intended/known.
More bugs I noticed after a day of use:
Google account data doesn't want to sync. Perhaps android 11 -> 12 mismatch?
Touch reader stopped working (required forced reboot).
Can't log in certain applications (don't know if it's a ROM issue).
eVen123 said:
What I was able to test now, it's pretty good. Very usable already!
Bugs I notice:
The GMS seems to be a bit slower than expected.
Fingerprint doesn't work with screen off.
Fingerprint request location is not marked.
Fingerprint maxes brightness of whole display.
Task switcher sometimes doesn't work.
Bottom navigation sometimes disappears.
It keeps warning me about SELinux not enforcing issue. Not sure if that's intended/known.
More bugs I noticed after a day of use:
Google account data doesn't want to sync. Perhaps android 11 -> 12 mismatch?
Touch reader stopped working (required forced reboot).
Can't log in certain applications (don't know if it's a ROM issue).
Click to expand...
Click to collapse
SELinux isn't enforcing because it's one of the first builds right after a bringup.
Put up a new build with some things resolved, notably SELinux is now Enforcing.
I also switched from stock's prebuilt NXP NFC stack to the open source stack. Anyone who is able to make payments with Google Pay or something like that, let me know if it works.
Added a vendor_dlkm partition to hold vendor kernel modules so you can flash a different vendor regardless of the kernel situation as the modules are no longer held there.
Enabled automatic brightness by default.
Fixed night light by correct PIxelworks device detection.
Switched from QTI BT to AOSP BT until it gets merged.
Put out a new build.
Upped kernel target level from 5 to 6. The new minimum requirement of level 6 is a minimum kernel version of 5.4.86. To comply with this I updated kernel to LA.UM.9.14.r1-16300-LAHAINA.0.
Also dropped Snapdragon Camera overlays in /vendor as it won't be supported this cycle. Just Camera2 unless I can somehow figure out getting ASUS Camera working.
Automatic brightness is now enabled by default.
Synced with latest lineage-19.0 sources which last I checked now include some theming stuff(?).
Alright, just thought I'd ask here.
I unlocked my BL and disabled some apps. Was running on stock rom!
Just tried to upgrade to Android 12 to be able to flash this rom but it is now stuck on a ramdump screen. Note: it is stuck on this screen with the Official Asus image! I had LOS18 on this device before but was running it for a few months with the stock rom (because of the camera in LOS).
It gets stuck in a loop. When I power down the phone (all 3 buttons for ~10s) it just gets me back to the ramdump.
Even using ASUS recovery RAW image and the instructions from this thread does not work: https://forum.xda-developers.com/t/full-recover-to-stock-if-things-went-really-bad.4337467/ .
After going to fastboot I am NOT able to flash the official ASUS Android 12 image, it just stops on 1/2 and does not give any details.
I am able to flash LOS recovery, LOS18 (latest) and AFTER that I am able to flash back to stock Android 11 (NOT 12, that gives me a ramdump again).
This cost me about half a day to figure out.
Anyone know what is going on and what I can do to get my phone to some kind of normal state when installing roms???
EDIT:
Just got completely stuck on ramdump.
Only thing that helped was: erase vendor_boot, boot_a/b partitions and do fastboot snapshot-update cancel . After that I was able to recover using the link above. Actually got scared there for a sec...
Uploaded a build without GMS for people who don't like using GMS.
Tap to wake functional?, installed "no gms", runs nicely
ZVNexus said:
Put out a new build.
Upped kernel target level from 5 to 6. The new minimum requirement of level 6 is a minimum kernel version of 5.4.86. To comply with this I updated kernel to LA.UM.9.14.r1-16300-LAHAINA.0.
Also dropped Snapdragon Camera overlays in /vendor as it won't be supported this cycle. Just Camera2 unless I can somehow figure out getting ASUS Camera working.
Automatic brightness is now enabled by default.
Synced with latest lineage-19.0 sources which last I checked now include some theming stuff(?).
Click to expand...
Click to collapse
Working great so far. I am having one issue where once I unlock the phone (and the screen gets really bright to read the fingerprint), it stays bright. If I tap the brightness slider, it doesn't move but it adjusts the brightness to what it should be according the slider.
This is the case with and without Adaptive Brightness enabled.
NisseGurra said:
Tap to wake functional?, installed "no gms", runs nicely
Click to expand...
Click to collapse
NisseGurra said:
Tap to wake functional?, installed "no gms", runs nicely
Click to expand...
Click to collapse
No, Tap to Wake does not work.
Mecallie said:
Alright, just thought I'd ask here.
I unlocked my BL and disabled some apps. Was running on stock rom!
Just tried to upgrade to Android 12 to be able to flash this rom but it is now stuck on a ramdump screen. Note: it is stuck on this screen with the Official Asus image! I had LOS18 on this device before but was running it for a few months with the stock rom (because of the camera in LOS).
It gets stuck in a loop. When I power down the phone (all 3 buttons for ~10s) it just gets me back to the ramdump.
Even using ASUS recovery RAW image and the instructions from this thread does not work: https://forum.xda-developers.com/t/full-recover-to-stock-if-things-went-really-bad.4337467/ .
After going to fastboot I am NOT able to flash the official ASUS Android 12 image, it just stops on 1/2 and does not give any details.
I am able to flash LOS recovery, LOS18 (latest) and AFTER that I am able to flash back to stock Android 11 (NOT 12, that gives me a ramdump again).
This cost me about half a day to figure out.
Anyone know what is going on and what I can do to get my phone to some kind of normal state when installing roms???
EDIT:
Just got completely stuck on ramdump.
Only thing that helped was: erase vendor_boot, boot_a/b partitions and do fastboot snapshot-update cancel . After that I was able to recover using the link above. Actually got scared there for a sec...
Click to expand...
Click to collapse
Same happenning here, booting to Android12 ramdumps me... I was able to update before but now it does not work... Also the flash script gives me an error that it did not give me before.
Code:
Project ZS590KS matching success!
Start erase misc
Erasing 'misc' FAILED (remote: 'Erase of misc is not allowed in snapshotted state')
fastboot: error: Command failed
misc flash failed!
Press any key to exit the script.
. I guess I will be staying on Android 11 then...
EDIT: Ran fastboot snapshot-update cancel like you did, and now the raw image file script works to reset the phone. Very weird. Also thank you so much, without your post, I would have never figured a way to make the script work again I am so glad you posted this
EDIT 2: After running the script (And everything working and passing) and getting everything back to normal, I was able to install Android 12 like I normally would without ramdumps