Database Develop

[ROM][EXPERIMENTAL][BOOTLOOPS][XT907][KKBL][LineageOS][Nougat]LineageOS 14.1

THIS ROM BOOTLOOPS. NO NEED TO CONFIRM OR POST SUCH ANYMORE​
Basically this ROM is an experiment at building LineageOS 14.1 (Nougat) specifically for an xt907 KKBL
How I built it:
Set up a virtual Box (on Win7 64b) to build Lineage OS 14.1 (followed their instructions)
Source: https://github.com/LineageOS/
I used an existing xt907 KKBL device tree (https://github.com/LineageOS/android_device_motorola_xt907) it looks old, but I built a JBBL device tree based from this project, and that booted. I also built TWRP using this device tree, and I have been told that it works
Basically, I have done no "magic" here. If this ROM works, I may also be able to build crDroid & ResurrectionRemix Nougat as well. Actually, my JBBL from this device tree worked better for crDoid and RR than LOS
This is an experimental build of LineageOS 14.1, Android version 7.1.2, an experimental build for a non-official device (ie xt907 KKBL).
I personally do not have an xt907 with KKBL, but an xt905 with JBBL, so I can't easily test this KKBL ROM. PLEASE tell me if it works or not.
The good
It's LineageOS
It's Nougat!
It's for KKBL
It's built from a device tree that I hacked into JBBL, and that booted
A TWRP for KKBL was built using the same device tree, and I am told that that works
It Builds
The bad
I have no idea if it boots as I don't have a KKBL installed​
Since I do not own an xt907 KKBL, I cannot test this zip personaly, and hope someone with an xt907 KKBL will try the zip and let me (and others) know if it works?
What I hope is that if this boots and runs, I will try building crDroid Nougat (and maybe ResurrectionRemix) for the xt907 KKBL. If they also work, I personally will up[grade to the KKBL (my JBBL version of crDroid has numerous FC's)
Credits: All credits go to LOS contributors and CM maintainers before them.
Almost forgot, Flash this ZIP at your own risk, the responsibility is all yours, it is provided as-is, with no garantees or whatever and I will not be held resonsible for any damage to your device or its data etc etc etc
Installation:
1) Download the ZIP
2) Boot into TWRP recovery (I wou;d recomend updating to TWRP 3.x (see myh othere thread I have been told trhat it works)
3) Make a nandroid (you should definitely be going back) And remember, a nandroid is NOT 100%! if you don't understand this, maybe trying this is not for you.
4) Wipe system/data/cache/dalvik
5) Flash update package (ie install the zip)
6) Flash GApps (probably Open GApps pico...) if it doesnt work, try a wipe and not flashing GApps (it helps with crDroid for JBBL)
6) Reboot to system
If it falls over, please get some logcats and post them on hastebin/pastebin etc etc NOT HERE, only the links. Hopefully we can fix it and have some highly customisable nougat ROM's for your device. And the steps to make it work may also be helpful for the next Android iteration.
Download Link: https://clicknupload.org/uvu9uknep9ku
And please post how you go with this ROM, either way, I would like to know if it works or not to decide if to build crDroid and/or RR. If it does work and crDroid does not, I may get around to building a non experimental build, with Overclocking enabled.

Cant download from that link

Shmaks said:
Cant download from that link
Click to expand...
Click to collapse
what exactly is the problem? have you tried a different browser? I can directly through chrome and also using TOR browser.

DiamondJohn said:
what exactly is the problem? have you tried a different browser? I can directly through chrome and also using TOR browser.
Click to expand...
Click to collapse
Tried two browsers - chrome and firefox. Click free download - create download link - click here for download - have Error The requested URL could not be retrieved
Fix: downloading with TOR works))

Shmaks said:
Tried two browsers - chrome and firefox. Click free download - create download link - click here for download - have Error The requested URL could not be retrieved
Fix: downloading with TOR works))
Click to expand...
Click to collapse
It may of been a timing thing. I posted the link right after the upload finished.

Just flash it (with and without gapps) - neverended boot animation, bootloop

Shmaks said:
Just flash it (with and without gapps) - neverended boot animation, bootloop
Click to expand...
Click to collapse
how much time did you give it? I have found 8-10 minutes is the norm for the first boot, and I allow 15 before I concede its not going anywhere.
Never mind, I am also just preparing to build crDroid (Nougat) (source is a big and slow download). I found that with the KKBL code altered to JBBL, crDroid booted while LineageOS 14.1 did not. And maybe LOS13 will boot. The fact that LOS14.1 at least showed the animation is a big positive.
Out of interest, did you flash it using TWRP 3.1.1?

DiamondJohn said:
Out of interest, did you flash it using TWRP 3.1.1?
Click to expand...
Click to collapse
Yes, TWRP 2.8.6 didnt flash it

Shmaks said:
Just flash it (with and without gapps) - never ended boot animation, bootloop
Click to expand...
Click to collapse
DiamondJohn said:
how much time did you give it? I have found 8-10 minutes is the norm for the first boot, and I allow 15 before I concede its not going anywhere.?
Click to expand...
Click to collapse
One difference I have noted between MM and Nougat is that MM will play the boot animation for much shorter a time and go into the "Optimizing app 1 of XX", while Nougat will continue to play the boot animation all through the optimisation (ie a LOOOOONnng time), until it actually loads and displays the launcher. Just a thought, maybe a little hope...

Endless boot screen for me, both with and without GApps. Waited 20 minutes both times. Installed via KKBL TWRP 3.1.1.

I think its safe to say, it will boot loop for everyone.
However, if you wish to possibly see this go further, if someone was to get a log of /proc/kmsg and logcat (and post on hastebin or such, not here), there may be something simple to change. Not that I am going to spend hour and hours on it, but you never know, it may be simple. To know how to get these logs from a non booting computer, you can get the kmsg while TWRP and the logcat maybe using adb over USB. There are plenty of guides on XDA.

DiamondJohn said:
I think its safe to say, it will boot loop for everyone.
However, if you wish to possibly see this go further, if someone was to get a log of /proc/kmsg and logcat (and post on hastebin or such, not here), there may be something simple to change. Not that I am going to spend hour and hours on it, but you never know, it may be simple. To know how to get these logs from a non booting computer, you can get the kmsg while TWRP and the logcat maybe using adb over USB. There are plenty of guides on XDA.
Click to expand...
Click to collapse
Is this still an issue?

DiamondJohn said:
I think its safe to say, it will boot loop for everyone.
However, if you wish to possibly see this go further, if someone was to get a log of /proc/kmsg and logcat (and post on hastebin or such, not here), there may be something simple to change. Not that I am going to spend hour and hours on it, but you never know, it may be simple. To know how to get these logs from a non booting computer, you can get the kmsg while TWRP and the logcat maybe using adb over USB. There are plenty of guides on XDA.
Click to expand...
Click to collapse
Willing to test and post logs. Just not sure how to retrieve the logs.

Not happening
See https://forum.xda-developers.com/showpost.php?p=73567002&postcount=19
Although I would be interested in seeing the last_kmsg log on a KKBL, if anyone has some free time.

As with others, I entered endless bootloop as well. Thank you for making the build to try.

mr3p said:
As with others, I entered endless bootloop as well. Thank you for making the build to try.
Click to expand...
Click to collapse
I am guessing you dont have a log of the last_kmsg :fingers-crossed:?

DiamondJohn said:
I am guessing you dont have a log of the last_kmsg :fingers-crossed:?
Click to expand...
Click to collapse
I apologize for not remembering to save the log. It wouldn't be the end of the world to revert back to KKBL and reload this build to get a log but I'll to find some time to play which is always the challenge.

This wouldn't be a problem so much if Lineage didn't delete perfectly good builds/ROMs for this device when they took over. Why would they do that for this device and not others? That seems a bit too coincidental.

DragonFire1024 said:
This wouldn't be a problem so much if Lineage didn't delete perfectly good builds/ROMs for this device when they took over. Why would they do that for this device and not others? That seems a bit too coincidental.
Click to expand...
Click to collapse
Just curious but if someone wants to run LineageOS, whats the downside of just switching over the to JBBL when builds exist?

mr3p said:
Just curious but if someone wants to run LineageOS, whats the downside of just switching over the to JBBL when builds exist?
Click to expand...
Click to collapse
I can't find working links to downgrade to JBBL

Problem with lockup / display not turning on across various roms, rooted droid

I successfully rooted my droid (that came with lollipop), using this guide
https://forum.xda-developers.com/droid-turbo/general/guide-how-to-unlock-bootloader-install-t3292684
installed twrp backed up the stock OS and installed resurrection remix lollipop rom. I did not install any different modems or radios as I planned to stay on lollipop.
Everything worked great yet after a day or two the display/phone would appear to lock up. I can press power, the display doesn't come on and when (usually) moving the the volume up/down I do hear sounds. Sometimes at this point it will reboot by itself, other times I have to reboot it.
When it comes up it goes through the android is upgrading thing, and sometimes works fine after, sometimes not, regardless eventually this problem repeats.
Thinking it was perhaps RR I tried straight Cyanogenmod, and eventually the rooted stock OS, both have this same problem.
I've tried using it with very minimal installed in the way of apps, same issue.
I've tried saving the log to SD to peer at later, but going through it I don't really see anything obvious to show what the problem is.
I"m wondering if there's a problem with the phone itself (it's a refurb) and am considering unrooting it and returning it.
Anyone seen this or thoughts on what might be the issue?
p.s.
if you happen to have a good link handy to an unrooting guide you might shoot it my way thanks.
thanks in advance!

What versions of the other ROMs did you use? Lollipop also, or Marshmallow? Nougat? For rooted stock ROM did you upgrade to Marshmallow? None of the Lollipop ROMs are supported anymore, so hard to answer for those.
There are ways to grab logs after a reboot, but here's another suggestion...
I use Auto Reboot app (needs root) to schedule a reboot my phone every day while I'm asleep.
This seems to keep the cobwebs cleared out, so the phone runs better. I know you want to find the issue, but maybe it's an accumulation of apps not releasing RAM orb something. This might help prevent that.

thanks for the reply
ChazzMatt said:
What versions of the other ROMs did you use? Lollipop also, or Marshmallow? Nougat? For rooted stock ROM did you upgrade to Marshmallow? None of the Lollipop ROMs are supported anymore, so hard to answer for those.
Click to expand...
Click to collapse
I tried the last released CM lollipop snapshot, as well as the last nightly.
For RR it was last released, "ROM OS Version: 5.1.x Lollipop"
ChazzMatt said:
There are ways to grab logs after a reboot,
Click to expand...
Click to collapse
Yeh I've been saving it to the SD so I can view it after a reboot, I've looked at 4 or 5 of them after the problem occurred and at least to me nothing really stood out
ChazzMatt said:
but here's another suggestion...
I use Auto Reboot app (needs root) to schedule a reboot my phone every day while I'm asleep.
This seems to keep the cobwebs cleared out, so the phone runs better. I know you want to find the issue, but maybe it's an accumulation of apps not releasing RAM orb something. This might help prevent that.
Click to expand...
Click to collapse
Yeh I expect it might periodically need a reboot but if it's just unpredictiably locking up or rebooting on its own it's not very usable.
I think I'm just going to have to try to unroot and return, maybe I'll go with a LG V20 as I don't want to have pay to re-root another one of these and possibly have same issue. Also the whole pay to have some app do something secret to my phone does leave me a bit uneasy.
Kind of a bummer as I'm actually pretty impressed with this device, fast, good battery, takes nice photos, only drawbacks for me are no removable SD and lack of LED notification, but I was willing to live without those given how good everything else was.
thanks

Same here,
I tried with different Roms 7.X, still blocking and display not turning on.
I'd appreciate some help.
Thanks!
Android Version: 7.1.2
Current Rom: AOKP
Kernel: 3.10.107-Stock-bhb27-nougat-kerneL

MrN00b said:
Same here,
I tried with different Roms 7.X, still blocking and display not turning on.
I'd appreciate some help.
Thanks!
Click to expand...
Click to collapse
FWIW and in case it helps you or someone else, I seem to have fixed mine finally, here's what I did.
First I installed latest twrp (mod 4) https://androidfilehost.com/?w=files&flid=39562 (there's a thread on this twrp if you want tor read on it). That in itself didn't fix the issue but did finally let me format and got rid of an 'mkfs.f2fs: invalid option -- r, ERROR=1' type error I used to get.
I installed this stock zip from twrp as described in thread:
https://forum.xda-developers.com/droid-turbo/development/rom-su4tl-49-100-stock-t3390041
It would never actually boot it would shut my phone off not long after showing the boot screen, and I'm not sure if doing that was necessary or not.
Taking some suggestions from here:
https://forum.xda-developers.com/droid-turbo/help/help-request-custom-rom-phone-unlocked-t3767070
I dug up the last official CM 13 snapshot:
https://www.google.com/search?q=cm-13.0-20161221-SNAPSHOT-ZNH5YAO3Y5-quark.zip
sha1: 9a219dd487c27e51b0c5c4922812838f394099c5
Wipe and installed with no gapps and voilà it would boot consistently. Without reinstalling I tried installing pico gapps and it would still boot though it took maybe 15 mins initially.
I want Nougat so I wiped and installed lineage-14.1-20180612-UNOFFICIAL-quark.zip from https://forum.xda-developers.com/moto-maxx/development/rom-t3494646 again no gapps and it also booted fine, whereas previously it would hang on booting. Without reinstalling ROM I tried installing opengapps nano and it would just hang.
I could then no longer get it to boot again, so I reinstalled CM13 no gapps, which booted fine, wipe and install lineage-14.1-20180612-UNOFFICIAL-quark.zip no gapps, and now it boots fine though currently it's taking a while.
I should perhaps note I took twrp backups inbetween steps whenever I had a working boot, (ex before installing gapps), but once the phone went back to hanging on boot, those restores didn't help. Only reflashing CM13 seemed to clear things up.
My ultimate goal is a LOS ish Nougat/Oreo ROM with no gapps using microg, and running tmobile, I'll see what I end up with.

Lineage OS 16 Shamu (Nexus 6)

Someone is testing LOS 16 on yours Shamu Phone? 15.1 Nightly is a stable build, is it 16 Nightly Build the same?

How should people know this? Lineage-16.0 is out since a few hours.
but since we have this https://github.com/LineageOS/charter/blob/master/device-support-requirements.md you can be shure of a certain quality

Any guidance on moving from 15.1 to 16.0? I assume a clean install is probably a good idea?
Thanks!
-C

First build isn't working properly for me. After flashing it gives me the "Decryption unsuccessful" message. Don't have encryption enabled, and my phone is formatted to ext4. Tried wiping multiple times in different ways. Had been running LOS 15.1 for months with no problems. Clean flash.
Update: Just to see, reinstalled LOS 15 and encrypted my device. Decryption still fails after flashing LOS 16 and trying to boot.

Quade321 said:
First build isn't working properly for me. After flashing it gives me the "Decryption unsuccessful" message. Don't have encryption enabled, and my phone is formatted to ext4. Tried wiping multiple times in different ways. Had been running LOS 15.1 for months with no problems. Clean flash.
Update: Just to see, reinstalled LOS 15 and encrypted my device. Decryption still fails after flashing LOS 16 and trying to boot.
Click to expand...
Click to collapse
I was thinking about flashing back to the last official google release (N6F27M), and then up to 16.0, but was going to wait to see if there was any official recommendation. Kind of a nuke the "site" from orbit approach - "it's the only way to be sure..."
-C

cdaly1970 said:
I was thinking about flashing back to the last official google release (N6F27M), and then up to 16.0, but was going to wait to see if there was any official recommendation. Kind of a nuke the "site" from orbit approach - "it's the only way to be sure..."
-C
Click to expand...
Click to collapse
Yeah, I was thinking about doing that, but just didn't feel like it, and can't imagine how it'd help. Probably just wait a week (probably more) or so for the builds to settle down. They're always pretty unstable at first anyway.

Quade321 said:
First build isn't working properly for me. After flashing it gives me the "Decryption unsuccessful" message. Don't have encryption enabled, and my phone is formatted to ext4. Tried wiping multiple times in different ways. Had been running LOS 15.1 for months with no problems. Clean flash.
Update: Just to see, reinstalled LOS 15 and encrypted my device. Decryption still fails after flashing LOS 16 and trying to boot.
Click to expand...
Click to collapse
Did you follow the instructions on the LOS site? I upgraded from LOS 15.1 to LOS 16 without issues. I wasn't encrypted on LOS 15.1 and still won't because right now that is a headache with TWRP being unable to decrypt.
https://lineageos.org/Changelog-22/

BootloopedMillennials said:
Did you follow the instructions on the LOS site? I upgraded from LOS 15.1 to LOS 16 without issues. I wasn't encrypted on LOS 15.1 and still won't because right now that is a headache with TWRP being unable to decrypt.
https://lineageos.org/Changelog-22/
Click to expand...
Click to collapse
I don't see anything that isn't normal in the instructions. Wipe, flash, done. And also don't know what you mean about TWRP being unable to decrypt. Newest TWRP (been for like 2 years) 3.2.3-0 works fine for me. That's interesting that it works for you though. No clue what's causing my problem.
Also when you say upgrade, do you mean you flashed 16 on top of 15.1? I did a clean flash, wiping everything.

The March 2 build is now booting for me. Noticed some changes to cryptfs in the logs, and sure enough. Now that it's booting, everything actually seems pretty stable.

I also got the "Decryption unsuccessful" on first boot of an upgrade from lineage 15.1
I was eventually able to boot, but had to do a bunch of random button pushing, and ended up nukeing the phone, but eventually got it to boot... But it has several other issues...
I did an "Advanced Wipe" in TWRP, and turned on every checkbox... Cleared every partition... Then did TWRP sideload of:
lineage-16.0-20190302-nightly-shamu-signed.zip
open_gapps-arm-9.0-nano-20190302.zip
Magisk-v18.1.zip
And it still asked for password on first boot... No way to put away the password entry keyboard BTW, preventing you from getting to the "Emergency Call" button... No 911 for you :'(
So I read somewhere that doing a "Format Data" under the TWRP wipe might help...
So I rebooted, did the above steps again, then tried "Format Data" before leaving TWRP... This failed to mount, and so no format... For some reason, I think on my phone I have TWRP on 2 partitions maybe? For some reason, rebooting from inside TWRP to "Recovery" (so yah, load recovery, then reboot directly to recovery) appeared to fix this unable to mount issue...
So now, I again wiped all paritions, sideloaded everything, got the "Format Data" to mount and work, then rebooted...
This booted and presented the initial setup (YAY!!) Went through that, and attempted to do a Google restore of the phone during setup... This looked like it worked, but NOTHING would download (Everything said it was trying to install, but nothing would...)
I am not super knowledgeable about this stuff, but one of my guess-timations of the issue was that it was a storage permission issue... Rebooted to TWRP again, and under Advanced I found something called "Fix Contents" that claimed it would attempt to repair the SELINUX model or something, which sounded permission issue related to me, so I tried that one...
And it booted, and things installed from Google Play (Double YAY!!)
I attempted to setup multiple users, and logging in a second user apparently seems to kill the Software Home Buttons for all users, and only rebooting brings them back for the primary user, and they disappear again when booting a secondary user... Other than this so far it is very fast, really quick, and looks like it has alot of potential as soon as they work out the kinks
P.S. Now I just wish they would un-discontinue Lineage support for the LG V20... Long live Removable Batteries paired with SDCard slot and IR-Blaster for the win!

Is there a way too root yet

I installed the "stock" version of Gapps that came with the pixel launcher. I can only use the Trebuchet launcher because the Pixel Launcher only crashes. Should I have installed a different Gapps version if it is unsupported? Or is this just a bug? Also, the Android Setup wizard keeps crashing when it is checking for an update at the beginning. It will not complete. Other than those issues, everything else seems to be working fine so far.

girkev said:
Is there a way too root yet
Click to expand...
Click to collapse
Yes. Magisk.
nhasian said:
I installed the "stock" version of Gapps that came with the pixel launcher. I can only use the Trebuchet launcher because the Pixel Launcher only crashes. Should I have installed a different Gapps version if it is unsupported? Or is this just a bug? Also, the Android Setup wizard keeps crashing when it is checking for an update at the beginning. It will not complete. Other than those issues, everything else seems to be working fine so far.
Click to expand...
Click to collapse
I am also seeing this problem, as are several others: https://forum.xda-developers.com/nexus-6/help/pixel-launcher-issue-lineage-16-nexus-6-t3906748

I am also facing the problem of the crash of pixel launcher. Does anybody know whether there is a recovery could decrypt the data of Android Pie?

1997cui said:
I am also facing the problem of the crash of pixel launcher. Does anybody know whether there is a recovery could decrypt the data of Android Pie?
Click to expand...
Click to collapse
Do you have a backup of your data? If you do, don't bother trying to decrypt it. Just wipe format your phone and start fresh.

wipe is not enough, must format encrypted partition
Just wanted to clarify that wiping is not sufficient to remove the encrypted partition. it must be formatted from the advanced wipe settings in TWRP.
David B. said:
Do you have a backup of your data? If you do, don't bother trying to decrypt it. Just wipe your phone and start fresh.
Click to expand...
Click to collapse

nhasian said:
Just wanted to clarify that wiping is not sufficient to remove the encrypted partition. it must be formatted from the advanced wipe settings in TWRP.
Click to expand...
Click to collapse
Yes. Sorry. I am aware of this, but used the incorrect terminology. Format was indeed what I had intended to say.

the 1st 16 release my camera did not work but it did on the 2nd nightly. i did today's [mar 6th] update and the camera does not work. info only.

dr1445 said:
the 1st 16 release my camera did not work but it did on the 2nd nightly. i did today's [mar 6th] update and the camera does not work. info only.
Click to expand...
Click to collapse
Usually, a reboot fixes the camera. It seems that on some boots it works and on some it doesn't.
https://forum.xda-developers.com/ne...geos-16-0-nexus-6-shamu-t3906045/post79053994

ok, i will give it a try.

[ROM][XZ][P][9.0][WEEKLY]OmniROM

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

[Discussion] Resurrection Remix 7 for Hammerhead (Android 9 Pie)

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.