August 22: Rom Updated to Beta 0.6 (LP 5.1.1 r13). Latest sources.
TWRP 2.8.7 in boot: Manual brightness is fixed by changing horrendously high back light value (18x Sony's high limit) mistakenly put in by Slim team resulting in no manual brightness and overheating. This is fixed now.
Download Link: http://forum.xda-developers.com/devdb/project/dl/?id=14141
Dirty flashing is fine if you are on my previous build.
______________________________________________________________________________________________________________
August 10: Rom Updated. This is Beta 0.4 (LP 5.1.1 r9). Latest Slim changes. Updated M5 kernel with CPU and GPU overclock. Kernel size reduced by 2 mb. Also incorporated latest CM commits into device tree to address some screen flickering. http://review.cyanogenmod.org/#/c/105489/
Download Link: http://forum.xda-developers.com/devdb/project/dl/?id=13920
You can flash dirty if upgrading from the previous build, just keep in mind that if you use Xposed, you must flash it before reboot. This also applies to Supersu. Otherwise, fresh install.
___________________________________________________________________________________________________________
August 6. This is LP 5.1.1 release 9. No heat issues. Also includes M5 hardened kernel with overclocked CPU to 2457 and GPU to 600.
Download: http://forum.xda-developers.com/devdb/project/dl/?id=13858
Kernel Source: https://github.com/AOSPME/android_kernel_sony_msm8974
___________________________________________________________________________________________________________
August 3: Guys. Stay away from July 25 build. It does cause overheating. I had an episode where my phone shut down and refused to boot for an hour. I guess Slimroms still have problems. Pitty. I have removed the download link...
July 29: Update addressing wifi disconnect after 15 min of sleep and excessive battery drain caused by arp packets related wakelocks
Download and description: http://forum.xda-developers.com/showpost.php?p=62102698&postcount=15
No need to wipe anything if you were on my previous build.
_____________________________________________________________________________________________________________
July 25: Rom updated to LP 5.1.1 r8. This is my change, since Slimrom team still uses earlier releases. They have substantially improved the rom sources, so, whatever I said about them in the past no longer applies.
1. Latest Google AOSP changes
2. Latest Slim changes
3. All my regular hardened features including hardened kernel, removed nefarious IPs, full network selection in Network, disabled wifi background scanning are in
4. Modified M5 kernel
5. Twrp 2.8.7 as a Fota image. The reason I put 2.8.7 in fota is that Slimteam still uses version 2.8.6, which has major bugs. In 2.8.7 most were fixed.
Instructions: Note that the boot.img does not include any recovery to prevent a collision with fota recovery
1. In TWRP format Data, then format System/Data/Cache
2. Flash the rom (don't reboot in system unless you already have recovery in fota)
3. Reboot in Bootloader
4. Flash TWRP.img like this: fastboot flash recovery twrp.img
5. Reboot
Download links: Removed
Kernel Source: https://github.com/AOSPME/android_kernel_sony_msm8974
Credit: AOSP, Slimroms, Myself5
__________________________________________________________________________________________________
Rom updated to 5.1 version alpha. All hardened/security features are in. TWRP 2.8.6 is integrated into kernel.
Download link: http://forum.xda-developers.com/devdb/project/dl/?id=12197
Kernel Source: https://github.com/AOSP-Argon/kernel_sony_msm8974/tree/lp5.1
___________________________________________________________________________________________________
Here is the latest Slimrom Lollipop built on February 18.
Main changes:
Disabled creepy Selinux and activated Tomoyo as main security provider
Enabled all ciphers, as opposed 2 or 3 in standard releases
Enabled all hashes, digests and compression modes
Enabled all hashes for random number generation to result in a speedier device
Enabled 256 (as opposed to 128) bit encryption for device encryption
Increased weak 2048 RCA key length to 4096
Changes are implemented on kernel level and in /system/core/vold. As a result, you have a more secure and faster device with real protection for you; whereas Selinux, in my view, apart from being developed by an entity known for spying on people on mass scale, "secures" the device from you - meaning you are prevented from interfering with the constant flow of data from your device to their servers ...
Bugs: up-to-date Slimrom bugs
Credit: Slimroms
Modified Sources:
https://github.com/optimumpr/kernel_sony_msm8974
https://github.com/optimumpr/android_system_vold-1
Install Instructions:
1. Be on Kitkat, have root and recovery
2. Enter recovery, wipe Data/Cache/System
3. Flash the rom
4. Don't reboot yet: for some reason Documents.app does not appear anywhere and there is no file manager to handle app install; therefore
5. Flash Slim file manager from kitkat (see Download links at the bottom of this post), which works on lollipop.
6. Now, reboot and enjoy
Download links for Main rom and Slimfilemanager are at the bottom of this post.
Read about getting recovery on honami here: http://forum.xda-developers.com/xperia-z1/general/recovery-solution-lollypop-roms-t3000822/post58127334#post58127334
TWRP is now integrated, see post #5 for download.
Warning: I am not responsible for the destruction of your device and damage to surrounding areas. You are at your own peril. Also, if you don't care about security, stay away from this thread and get the regular version of this rom, which is available in Original Development or on Slimroms website. Comments or discussion about necessity for security, especially by those who have no idea what they are talking about, won't be tolerated. You have been warned.
DOWNLOAD LINKS:
Rom http://d-h.st/dfo
Slim File Manager http://d-h.st/Aqu0 flash it right after the rom before rebooting
XDA:DevDB Information
Slim Lollipop Hardened Secure, ROM for the Sony Xperia Z1
Contributors
optimumpro
Source Code: https://github.com/SlimRoms/platform_manifest
ROM OS Version: 5.0.x Lollipop
ROM Kernel: Linux 3.4.x
ROM Firmware Required: Unlocked bootloader
Based On: Slimroms
Version Information
Status: Alpha
Created 2015-02-19
Last Updated 2015-08-22
Reserved
screenshoots?? http://cdn3.xda-developers.com/images/smilies/smile.gif
kriswal123 said:
screenshoots?? http://cdn3.xda-developers.com/images/smilies/smile.gif
Click to expand...
Click to collapse
Sorry, I played with the rom for a day and went back to kitkat.
The looks are the same as in the latest Slimrom LP, which is posted on Slimrom website, as well as in the original Android Development thread...
Kernel with integrated TWRP
Here is SlimLP kernel with integrated TWRP recovery. From now and on, you don't need to reflash your device when changing roms, especially from Lillipop to kitkat or deal with the FOTA partition.
Just unzip the attached file and flash it in Fastboot:
fastboot flash boot boot.img
fastboot reboot
For those of you who already have TWRP in FOTA partition, as you know, this recovery collides with the integrated recovery. So, if you have TWRP in FOTA, do this after installing my kernel:
fastboot erase recovery
fastboot reboot
This will get rid of TWRP in FOTA
Do you plan to update this ? (I am sorry I have posted in almost all your threads but all lollipop rom (Except CM12) keeps on freezing for me
and I want to use a rom with selinux disabled (so that i can use xprivacy)
I tried RR hardened and validus. Both freeze...
never saw any freeze in 4.4.4
ggs2 said:
Do you plan to update this ? (I am sorry I have posted in almost all your threads but all lollipop rom (Except CM12) keeps on freezing for me
and I want to use a rom with selinux disabled (so that i can use xprivacy)
I tried RR hardened and validus. Both freeze...
never saw any freeze in 4.4.4
Click to expand...
Click to collapse
I think Slimrom team is no longer updating lollipop 5.0. They are working on 5.1. Nor are they updating kitkat. But you can use any kernel from my lollipop roms, as selinux is disabled there. You can also use my kernel with cm12, although, I am not sure CM12 would work with xprivacy. Out of all lollipops, only SlimLP and RR5.0 work with Xprivacy. RR works straight. Validus works for me with data partition restored from RR5.0. What I did was to first install RR5.0+Xposed+Xprivacy (confirmed it worked), then backed up data, then full wipe, installed Validus , then without reboot xposed, then without reboot restored data from RR5.0 and it works...
optimumpro said:
I think Slimrom team is no longer updating lollipop 5.0. They are working on 5.1. Nor are they updating kitkat. But you can use any kernel from my lollipop roms, as selinux is disabled there. You can also use my kernel with cm12, although, I am not sure CM12 would work with xprivacy. Out of all lollipops, only SlimLP and RR5.0 work with Xprivacy. RR works straight. Validus works for me with data partition restored from RR5.0. What I did was to first install RR5.0+Xposed+Xprivacy (confirmed it worked), then backed up data, then full wipe, installed Validus , then without reboot xposed, then without reboot restored data from RR5.0 and it works...
Click to expand...
Click to collapse
I tried all of your roms.. Xprivacy worked in all of them but i have this screen freeze issue which makes my phone particularly unusable.
I think i would revert to kitkat for now. That was smooth and solid... Thanks....
Rom Updated to 5.1
See OP for SlimLP 5.1.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
my wifi kept dropping out and i cannot turn it on except rebooting, is this a known problem ?
New build is up
Rom updated. See OP for download and description.
@Diewi
I thought we could move our discussion on wifi to this thread. Here is a little dirty secret: that qcom binary file is found in kernel too. So, if you change it in /etc/firmware/, you also have to copy the changed file to your kernel's /drivers/staging/prima/firmware_bin/ directory and then recompile the kernel. As usual, the entries there will go to kernel wifi module, which is actually not a module anymore, but a built-in in kernel. Otherwise, the changes won't work. Hence, there goes your android framework messing up things...
I have done it and am back to Kitkat level of battery drain with no disconnect. Here is my file: I did return to gEnableSuspend = 3 and made some more changes.
optimumpro said:
I thought we could move our discussion on wifi to this thread.
Click to expand...
Click to collapse
Fine with that.
optimumpro said:
Here is a little dirty secret: that qcom binary file is found in kernel too. So, if you change it in /etc/firmware/, you also have to copy the changed file to your kernel's /drivers/staging/prima/firmware_bin/ directory and then recompile the kernel. As usual, the entries there will go to kernel wifi module, which is actually not a module anymore, but a built-in in kernel. Otherwise, the changes won't work. Hence, there goes your android framework messing up things...
I have done it and am back to Kitkat level of battery drain with no disconnect. Here is my file: I did return to gEnableSuspend = 3 and made some more changes.
Click to expand...
Click to collapse
Sorry, I have to disagree. Here, things are a bit different from the android framework. Please have a look at the file "CORE/HDD/src/wlan_hdd_cfg.c" of the prima driver, especially the method "hdd_parse_config_ini". The comment clearly states that the ini-file is parsed:
/*
* This function reads the qcom_cfg.ini file and
* parses each 'Name=Value' pair in the ini file
*/
This also matches my experience that modifying the cfg.ini on the device does indeed have an effect.
Just one more note: By the concept accessing external files), it should not make any difference on reading external file if you compile modules inside the kernel or as "seperate" modules. However, there exist quite a lot device drivers out there which require to be build as modules to load their firmware (due to being depend upon some "external" firmware loader etc.). The prima driver obviously does not belong to these kind drivers.
Nevertheless, those changes should be pushed upstream (cm), then they would reside in the driver directory of the kernel anyways
Regards,
Diewi
Diewi said:
Fine with that.
Sorry, I have to disagree. Here, things are a bit different from the android framework. Please have a look at the file "CORE/HDD/src/wlan_hdd_cfg.c" of the prima driver, especially the method "hdd_parse_config_ini". The comment clearly states that the ini-file is parsed:
/*
* This function reads the qcom_cfg.ini file and
* parses each 'Name=Value' pair in the ini file
*/
This also matches my experience that modifying the cfg.ini on the device does indeed have an effect.
Just one more note: By the concept accessing external files), it should not make any difference on reading external file if you compile modules inside the kernel or as "seperate" modules. However, there exist quite a lot device drivers out there which require to be build as modules to load their firmware (due to being depend upon some "external" firmware loader etc.). The prima driver obviously does not belong to these kind drivers.
Nevertheless, those changes should be pushed upstream (cm), then they would reside in the driver directory of the kernel anyways
Regards,
Diewi
Click to expand...
Click to collapse
I don't dispute that the file is being parsed, my point is that because the same file with different entries is in kernel, we really don't know how they would interact.
Update to fix wifi disconnect and battery drain
Here is a recompiled kernel as well as a separate file to flash. This takes care of wifi disconnect after 15 minutes of sleep as well as excessive battery drain caused by a barrage of arp packets that create wakelocks.
Instructions:
1. Flash WIFI_DRAIN_FIX in Recovery
2. After that reboot in Bootloader and flash kernel (unzip boot.img): fastboot flash boot boot.img
3. If you have fota recovery, don't reboot and erase fota recovery, because this boot.img has twrp: fastboot erase recovery.
TWRP 2.8.7 has a bug preventing backing up roms. So, it is no good, unfortunately. I have returned to an earlier build.
Kernel Source: https://github.com/AOSPME/android_kernel_sony_msm8974
Warning: Don't use this for any other rom, because this kernel is specific to SLimrom.
optimumpro said:
I don't dispute that the file is being parsed, my point is that because the same file with different entries is in kernel, we really don't know how they would interact.
Click to expand...
Click to collapse
I get your point, but please have a look at the Android.mk file in the directory of the prima driver. There it is clearly stated that the files in the firmware_bin sub directory are just copied to the dir "${OUT}/system/etc/firmware/wlan/prima/". Hence, the "same" file does not exist in the kernel. BTW, beware, if you modify the file directly in your kernel folder as it will not be copied to the ${OUT} directory if the file exists there already. This is a serious weakness of the android build system IMHO.
The cfg-file will be parsed when the driver loads.
Sorry, for being that insistent
Diewi said:
I get your point, but please have a look at the Android.mk file in the directory of the prima driver. There it is clearly stated that the files in the firmware_bin sub directory are just copied to the dir "${OUT}/system/etc/firmware/wlan/prima/". Hence, the "same" file does not exist in the kernel. BTW, beware, if you modify the file directly in your kernel folder as it will not be copied to the ${OUT} directory if the file exists there already. This is a serious weakness of the android build system IMHO.
The cfg-file will be parsed when the driver loads.
Sorry, for being that insistent
Click to expand...
Click to collapse
Well. This same file resides in sony_rhine_common overlay. So, what I do is put the changed file in both directories. Anyway, this is the first time on lollipop that I have absolutely no wifi disconnection. And wifi range has increased too (I increased the tx cap to 80).
I have very very strange issue (only on this slim rom)!
My charging sometime stops, and i have to reboot phone to get it back to charging. anyone has same issue?
ggs2 said:
I have very very strange issue (only on this slim rom)!
My charging sometime stops, and i have to reboot phone to get it back to charging. anyone has same issue?
Click to expand...
Click to collapse
I don't think anyone else has it. In case you are talking about charging through usb: some linux distros drop usb connections during sleep and then have trouble reconnecting, because the phone is sleeping. You may have a similar behavior in Windows...
Just a remark, It seems that the file ending is a bit messed up. Or rather missing.
Related
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
MultiROM is a one-of-a-kind multi-boot mod. It can boot any Android ROM as well as other systems like Ubuntu Touch, once they are ported to that device. Besides booting from device's internal memory, MultiROM can boot from USB drive connected to the device via OTG cable. The main part of MultiROM is a boot manager, which appears every time your device starts and lets you choose ROM to boot. You can see how it looks on the left image below and in gallery. ROMs are installed and managed via modified TWRP recovery. You can use standard ZIP files to install secondary Android ROMs and MultiROM even has its own installer system, which can be used to ship other Linux-based systems.
Features:
* Multiboot any number of Android ROMs
* Restore nandroid backup as secondary ROM
* Boot from USB drive attached via OTG cable
You can also watch a video which shows it in action.
WARNING
It is dangerous. This whole thing is basically one giant hack - none of these systems are made with multibooting in mind. It is no longer messing with data partition or boot sector, but it is possible that something goes wrong and you will have to flash factory images again. Make backups. Always.
IMPORTANT
1. I'm not responsible for anything, you do all this on your own risk.
2. Once you have flashed and set up MultiROM, don't flash another boot.img using fastboot or normally. Always go to "Advanced -> MultiROM" to flash ROMs/kernels or other mods.
3. If you want to uninstall MultiROM, just flash the MultiROM uninstaller.
4. I am not certainly sure about the compatibility with stock Roms, I still need to test this yet.
5. Your device must not be encrypted.
6. To all devs maintaing Stock-based ROMs: Feel free to use my patched stock kernels to add MultiROM support to your ROMs.
7. When booting another ROM, you'll notice that in some cases, you can enter the recovery of the boot.img of the ROM. Please don't use it, flash everything using MultiROM TWRP.INSTALLATION
1. Make sure you are on a rom compatible with these kernels.
2. Flash the required kernel zip.
3. Flash MultiROM_TWRP-xx-xx-xxxx.img on fota partition.
4. Flash MultiRom_xx-xx-xxxx-v31x.zip
5. Done1Adding ROMs
Go to recovery, select Advanced -> MultiROM -> Add ROM. Select the ROM's zip file and confirm.Using USB drive
During installation, recovery lets you select install location. Plug in the USB drive, wait a while and press "refresh" so that it shows partitions on the USB drive. You just select the location (extX, NTFS and FAT32 partitions are supported) and proceed with the installation.
If you wanna use other than default FAT32 partition, just format it in PC. If you don't know how/don't know where to find out how, you probably should not try installing MultiROM.
If you are installing to NTFS or FAT32 partition, recovery asks you to set image size for all the partitions - this cannot be easilly changed afterward, so choose carefully. FAT32 is limited to maximum of 4095MB per image - it is limitation of the filesystem, I can do nothing about that.
Installation to USB drives takes a bit longer, because the flash drive is (usually) slower and it needs to create the images, so installation of Ubuntu to 4Gb image on my pretty fast USB drive takes about 20 minutes.
Enumerating USB drive can take a while in MultiROM menu, so when you press the "USB" button in MultiROM, wait a while (max. 30-45s) until it searches the USB drive. It does it by itself, no need to press something, just wait.Updating/changing ROMs
1. Primary ROM (Internal)
Flash ROM's ZIP file as usual, do factory reset if needed (it won't erase secondary ROMs).
Go to Advanced -> MultiROM in recovery and do Inject curr. boot sector.
2. Secondary Android Rom
If you want to change the ROM, delete it and add new one. To update ROM, follow these steps:
Go to Advanced -> MultiROM -> List ROMs and select the ROM you want to update.
Select "Flash ZIP" and flash ROM's ZIP file.
SOURCEs
MultiROM - https://github.com/XperiaMultiROM/multirom/ (branch old)
Modified TWRP - https://github.com/XperiaMultiROM/an...table_recovery (branch master)
Kernel w/ kexec-hardboot patch - https://github.com/aweosomeabhijeet/android_kernel_sony_msm8x27 (cm-Kernel)
CREDITs
Tasssadar
Alvinhochun - without his kexec patch, it would have been impossible for me, kudos to him :highfive:
Xperia Multirom
Myself5
Every other dev behind this
If you think my work is good, please consider a small donation
Donate to me
You might want to consider a Donation to Tasssadar, who is the Mastermind behind all of this, I just ported it to the M
Donate to Tasssadar
XDA:DevDB Information
MultiRom for Xperia M, Tool/Utility for the Sony Xperia M
Contributors
aweosomeabhijeet, alvinhochun, XperiaMultirom
Source Code: https://github.com/XperiaMultiROM/multirom/
Version Information
Status: Stable
Current Stable Version: v31x
Stable Release Date: 2015-08-13
Created 2015-08-07
Last Updated 2015-08-13
BUGs
NO BUGS as of now
LIMITATIONs
1. For MTP to work in TWRP you need to disable and enable it again.
CHANGELOG :
Code:
2015-08-13
Stable release!
Fixed minor touch issues present in the kernel by [email protected] !
2015-08-07
Beta version
Fixed erasing primary rom with secondary
Fixed wifi
2015-08-07
Initial release!
DOWNLOADS
Kernels with kexec-hardboot support :
XMS-stock-Kexec.zip(To be flashed in recovery)(not yet tested)
XMD-stock-Kexec.zip(To be flashed in recovery)(not yet tested)
XM_CM_kexec-08-13-2015.zip(has touch screen issue)
Other kernels with kexec-hardboot support:
1. NUI kernel(kudos to dev.)
Instructions to use NUI kernel
MultiROM TWRP :
recovery.img(To be flashed on fota-partition)
MultiROM-zip :
multirom-20150813-v31x-UNOFFICIAL-nicki.zip(To be flashed in recovery)
Use sdcard class 10 to boot cm11, run very smoothly
Great work, thang's ..
Sent from my waifu
Superb job @aweosomeabhijeet
And u can even add XMD in thread title bcoz it even works on it.. I am XMD user.. It's working well
@aweosomeabhijeet, to prevent compatibility issues that may occur it will be better to use boot image repacking script (e.g. with unpackbootimg and mkbootimg utilities) that will inject new zImage (it is kernel file in your out/target/product/nicki folder) in boot image than flashing raw boot.img, so ramdisk will not be overridden (as far as I understand we don't need changes in ramdisk for kexec, do we? and even if we do, it will be better to replaced only changed files, not the whole ramdisk). Noel Macwan uses that thing in his kernels, I used his script as base for my old injecting CWM/TWRP script.
---------- Post added at 21:26 ---------- Previous post was at 20:57 ----------
BTW, what kernel sources did you use for your kexec-patched kernel? Are they Sony stock ones? Aren't they from CM12.1 repo?
SUCCESS
so today i successfully flashed 3 roms on in XMD which run smoothly..the only problem i faced is patience when flashed through recovery i in usbdisk (which is obvious)..so now i dont need to wipe or format my primary rom in oder to test other builds..fabulous job @aweosomeabhijeet
Now mutlirom thread is active almost after one and half year for our xperia m...
All credits to u...
[deleted]
cucumber09 said:
@aweosomeabhijeet, to prevent compatibility issues that may occur it will be better to use boot image repacking script (e.g. with unpackbootimg and mkbootimg utilities) that will inject new zImage (it is kernel file in your out/target/product/nicki folder) in boot image than flashing raw boot.img, so ramdisk will not be overridden (as far as I understand we don't need changes in ramdisk for kexec, do we? and even if we do, it will be better to replaced only changed files, not the whole ramdisk). Noel Macwan uses that thing in his kernels, I used his script as base for my old injecting CWM/TWRP script.
---------- Post added at 21:26 ---------- Previous post was at 20:57 ----------
BTW, what kernel sources did you use for your kexec-patched kernel? Are they Sony stock ones? Aren't they from CM12.1 repo?
Click to expand...
Click to collapse
Indeed a very good idea, but I am worried about pure stock users. I think the script won't work, though I haven't tried.
They are from CM repo only, I am fixing some issues will push changes to my fork of CM kernel.
aweosomeabhijeet said:
Indeed a very good idea, but I am worried about pure stock users. I think the script won't work, though I haven't tried.
They are from CM repo only, I am fixing some issues will push changes to my fork of CM kernel.
Click to expand...
Click to collapse
We can make different zip for pure stock and for custom ROMs. But is now MR working on stock? Doesn't it have split screen bug? If yes, you should try using custom recovery graphics, and I am not familiar to C, so can't help. And BTW does stock work with CM kernel? I very doubt it. Even if it will work with stock ramdisk and CM zImage (which I doubt too, as CM kernel is built on CAF sources with some changes from stock kernel if I'm not wrong), it surely won't work with full CM boot image, so repacking script will be the best solution (I can even make it for you today if changes in initrd are not needed). And if stock will boot with CM zImage we will not have screen split bug anymore, and script also should work even with stock (as the command line is the same, and even if not, we can read it from unpackbootimg output by using `cat *.img-cmdline` for command line value in script). But building different kernels for stock and custom ROMs (all custom ROMs for our device share the same kernel source, difference is only in ramdisk, you can even boot CM11 with CM12.1 kernel if you will keep CM11's ramdisk) is better solution.
cucumber09 said:
We can make different zip for pure stock and for custom ROMs. But is now MR working on stock? Doesn't it have split screen bug? If yes, you should try using custom recovery graphics, and I am not familiar to C, so can't help. And BTW does stock work with CM kernel? I very doubt it. Even if it will work with stock ramdisk and CM zImage (which I doubt too, as CM kernel is built on CAF sources with some changes from stock kernel if I'm not wrong), it surely won't work with full CM boot image, so repacking script will be the best solution (I can even make it for you today if changes in initrd are not needed). And if stock will boot with CM zImage we will not have screen split bug anymore, and script also should work even with stock (as the command line is the same, and even if not, we can read it from unpackbootimg output by using `cat *.img-cmdline` for command line value in script). But building different kernels for stock and custom ROMs (all custom ROMs for our device share the same kernel source, difference is only in ramdisk, you can even boot CM11 with CM12.1 kernel if you will keep CM11's ramdisk) is better solution.
Click to expand...
Click to collapse
Actually you are getting it wrong!
1. We would not have any screen shift bug
2. Every ROM we boot from multirom can use it's own kernel irrespective of what kernel is installed in the device. (That's the benefit of kexec-hardboot)
3. I have a better idea for maintaing stock and all. Will upload new zip soon. I would like to use parts of your script if you don't mind.
BTW, why didn't you git clone kernel repository (it would save commit history and make your fork git-compatible with original) and then apply your patches? Otherwise, it will be harder to support your patched kernel, as it has another commit history and you if I am not wrong will not be able to merge and cherry-pick commits from CM kernel to your kernel, you will have to do it manually, which is quite annoying, or leave your kernel unupdated in future.
---------- Post added at 15:49 ---------- Previous post was at 15:45 ----------
aweosomeabhijeet said:
Actually you are getting it wrong!
1. We would not have any screen shift bug
2. Every ROM we boot from multirom can use it's own kernel irrespective of what kernel is installed in the device. (That's the benefit of kexec-hardboot)
3. I have a better idea for maintaing stock and all. Will upload new zip soon. I would like to use parts of your script if you don't mind.
Click to expand...
Click to collapse
Seems that we misunderstand each other. I talk about using other ROMs as primary, not only CM. We can do this by using kexec-ed kernel. I just offer you another method installing it, which will keep original ramdisk (if kexec doesn't need changes in it) and only replace kernel itself (zImage only, not boot image).
And I don't mind using parts of this script.
cucumber09 said:
BTW, why didn't you git clone kernel repository (it would save commit history and make your fork git-compatible with original) and then apply your patches? Otherwise, it will be harder to support your patched kernel, as it has another commit history and you if I am not wrong will not be able to merge and cherry-pick commits from CM kernel to your kernel, you will have to do it manually, which is quite annoying, or leave your kernel unupdated in future.
---------- Post added at 15:49 ---------- Previous post was at 15:45 ----------
Seems that we misunderstand each other. I talk about using other ROMs as primary, not only CM. We can do this by using kexec-ed kernel. I just offer you another method installing it, which will keep original ramdisk (if kexec doesn't need changes in it) and only replace kernel itself (zImage only, not boot image).
And I don't mind using parts of this script.
Click to expand...
Click to collapse
I know it. I have forked the repo and currently cloning. It's just in beta status and is just for giving details about the patch. I'll soon be on CM kernel and would merge all its commits and kernel would be updated always.
Don't you worry about it, I have all in mind. It takes time, I am free majorly on weekends so I won't rush on things.
I understand this and I have already made installer zip which does exactly what you are trying to tell, it uses parts of your script to replace just zImage and not whole boot.img. I still have something better coming. Just wait for few days.
aweosomeabhijeet said:
I know it. I have forked the repo and currently cloning. It's just in beta status and is just for giving details about the patch. I'll soon be on CM kernel and would merge all its commits and kernel would be updated always.
Don't you worry about it, I have all in mind. It takes time, I am free majorly on weekends so I won't rush on things.
I understand this and I have already made installer zip which does exactly what you are trying to tell, it uses parts of your script to replace just zImage and not whole boot.img. I still have something better coming. Just wait for few days.
Click to expand...
Click to collapse
Okay, that's nice. Sorry if I was too annoying.
Nice dev discussions
Sent from my waifu
itsnie said:
Nice dev discussions
Sent from my waifu
Click to expand...
Click to collapse
Dev and just-advanced-user discussion as I am not a developer. Just enthusiastic and sometimes full of curiosity user, nothing more. (BTW, we should stop OT not to make a mess in the thread)
It's not a order or request.. A small advice or suggestions.. Can you overclock ur kernel for more smoothness
kjinx01 said:
It's not a order or request.. A small advice or suggestions.. Can you overclock ur kernel for more smoothness
Click to expand...
Click to collapse
Please upload kernel.sin from build 15.5.A.1.5 if anyone here is having ftf of the same so that I can build for XMD stock devices. Thanks
Hey bro why does it take so long time to flash in recovery.. Any rom on sdcard takes abt 10 min to get flashed..??
aweosomeabhijeet said:
Please upload kernel.sin from build 15.5.A.1.5 if anyone here is having ftf of the same so that I can build for XMD stock devices. Thanks
Click to expand...
Click to collapse
here u go for it..i uploaded kernel.sin from 15.5.A.1.5 of XMD ftf stock rom
https://www.mediafire.com/?9dobzi8nu2tqzjy
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
INFORMATION,
First AOSP NOUGAT based builds for Xperia Z2 Tablet.
Disclaimer
We are not responsible for anything that may happen to your device . We ask that you do your part to know your device and know how to recover from problems before you flash!
BUGS
1. Camera Foucs unclear & Dark camera.
All other seems to Work for now.
Please let me know if you find more Bugs!!!
INSTRUCTIONS
Download Rom, Recovery & Gapps First & Unlock Bootloader
1. Download ROM Castor SGP521 (LTE)
--Download ROM Castor-Windy SGP511, SGP512 (WIFI)
2. Download OPENGAPPS
3. Flash the Boot from ROM via fastboot (fastboot flash boot pathTo/boot.img)
4. Flash TWRP Recovery 3.0.0-0 via fastboot too (fastboot flash recovery pathTo/recovery.img)
5. Boot into Recovery by using VOLUME UP when Sony logo comes up with pink notification light.
6. Wipe SYSTEM, DATA, DALVIK, CACHE from recovery.
--- 6.1 If you Update the ROM skip 3,4 & 6.
7. Flash the Rom zip and Open Gapps zip from Recovery.
8. Reboot.
(Optional)
9. Root Direct Download
10. Flash SU zip via recovery.
11. Reboot.
Changelogs :
Build 18/02/2017
- New blobs from sony
- Call Echo Fixed
- Camera crash fixed
- Latest security patch
Build 09/11/2016
- Google release 7.1_r7
- November Security patch
- new charger driver
Build 31/10/2016
-Camera fix (half green is gone)
-Nfc is fixed
-Update interactive gov
-Fix charging bug
-Unify sound Implementation
-Rework panel Implementation
Build 21/10/2016
-Android 7.1.0_r4 release
-Some camera commits
-Removed fm radio (causes deep sleep problems)
-Night display enabled
Sceenshots :
FAQ :
Q- Can i install it on locked bootloader?
A- No.
Q- Which gapps should be used?
A- OpenGapps arm 7.1 Full
Q- How to install this rom?
A- Read first post.
Q- Is camera working?
A-See the bugs listed above.
Q- Something* is not working.
A-Report bugs on github or here when it is not listed above.
Q-Battery draining quickly.
A-There is miscellaneous battery drain.Else no issue with battery.
CREDITS
AOSP/Google
Sonys Open Device Program
Sources
Google
Device Tree (Castor Windy-WIFI)
Device Tree (Castor-LTE)
Kernel tree
Vendor Tree
XDA:DevDB Information
Android Open Source Project [Nougat], ROM for the Sony Xperia Z2 Tablet
Contributors
rcstar6696, akshay2shah
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
ROM Firmware Required: Unlocked Bootloader
Based On: AOSP
Version Information
Status: Alpha
Created 2015-10-29
Last Updated 2017-04-11
reserved
reserved
Recovery Installation
Recovery is only available if your build is v21 or newer!
1. Download the Recovery Image from Mega folder of your device (Recovery Folder)
(Castor=LTE and Castor-windy= Wifi only)
2. Reboot your device to bootloader
3. connect your device with your pc
4.Use fastboot to flash recovery with this commando:
Fastboot flash recovery PATH TO RECOVERY FILE
(Don't forget to press enter )
5. Unplug device
6. Turn on device
7. if the device reaches sony logo the notification Led turns on (pink)
8. press volume up while led is pink (led changes colour to orange if you press correctly)
9. Device should show Recovery now
Enjoy AOSP on Z2 Tablet
V2 is Online
add support for Castor (LTE)
Audio is fixed
Video works now but with wrong colour calibration
Ant*+ Support
Selinux is active
ZIP Package
I uploaded the flashable zip but you can only use it if you upgrade from the first version. if its your first flash use the Images Report back please !!
O-oh, nice! What a treat to try on my tablet
So, a couple of questions prior to installation
1) Right now I have an Android 5.1.1 stock pre-rooted firmware. If I install this - does it overwrite the recovery in the process or does it only touch the system and the kernel partitions? I wouldn't want to lose my XZDualRecovery setup with TWRP
2) by Video not working - do you mean the recording or playing a video? I.E. does it affect apps like Twitch and YouTube video playback?
Fatal1ty_93_RUS said:
O-oh, nice! What a treat to try on my tablet
So, a couple of questions prior to installation
1) Right now I have an Android 5.1.1 stock pre-rooted firmware. If I install this - does it overwrite the recovery in the process or does it only touch the system and the kernel partitions? I wouldn't want to lose my XZDualRecovery setup with TWRP
2) by Video not working - do you mean the recording or playing a video? I.E. does it affect apps like Twitch and YouTube video playback?
Click to expand...
Click to collapse
1) first you need to unlock your boot loader but anyway you will lose xz dual recovery. Recovery will be overwritten and a complete New kernel is needed ( Linux kernel 3.1). The boot.img from aosp build includes this.
2) Sorry i mean video playback, but if you play Videos with MX player or vlc it will work correct if not you will have confuesed colours
Video recording will not work due the camera.
Hmm, okay. So I should be able to get TWRP back via NUT's kernel builder on his website
Another question - you said that optionally I can use the boot.img you linked in the Optional section (instead of the one that comes with the ROM) - does that mean that the ROM-included boot.img does not allow the device to be rooted? (due to SELinux, I suppose)
Fatal1ty_93_RUS said:
Hmm, okay. So I should be able to get TWRP back via NUT's kernel builder on his website
Another question - you said that optionally I can use the boot.img you linked in the Optional section (instead of the one that comes with the ROM) - does that mean that the ROM-included boot.img does not allow the device to be rooted? (due to SELinux, I suppose)
Click to expand...
Click to collapse
This could be possible that it work with his kernel builder i haven't test it
Edit: Kernel build with nuts builder is successfull but you won't have recovery. I tested it
Don't use the optinal boot.img. your device will not Boot.The first image is an old Boot.img Form kit kat which has recovery included. First flash the first image than Boot to recovery than flash Boot.img from rom again
No the kernel supports root but the Problem is that you don't have a recovery. You need it to flash super su.
hey @rcstar6696, Installed the ROM just a few moments ago. Enjoying it so far! Some feedback:
1) The installation went through very smoothly, like I have a Nexus device
The "Flash ROM -> flash KK kernel -> Flash SuperuSU -> Flash MM kernel" went okay as well, no issues, just a little extra step to gain root until we have XZDR for Android 6.0
2) The ROM booted up SUPER FAST for the first time. Sony's firmware usually takes at least 2-3 minutes to boot up fully from a shutdown state, while this ROM booted up in less than like 30 seconds. Very refreshing to see such short booting times!
3) The backup restoration process seemed to not have gone through fully. Only about half of the apps I had were restored. Not really much of an issue, just a personal observation
Also after confirming what apps I wanted to restore, the setup wizard stayed at the "Please wait..." screen, so I had to manually quit to the homescreen via the Home button. Seems like a bug to me? Or maybe it's the built-in GAPPS that's the issue (haven't tried flashing a GAPS package manually though)
4) The system seems to not recognize my SIM-card for some reason. It just tells me "No SIM card installed", which is weird considering that the ROM is for the LTE version. Tried turning on and off the Airplane mode to reset the modem - no result. Tried rebooting the device - also n result.
Maybe try to look at Sony's official binaries for Tab Z2? http://developer.sonymobile.com/downloads/tool/software-binaries-for-aosp-m-android-6-0/
5) Like you said, the video playback is all green/purple artifacted. Wonder if it's the drivers/libraries issue, as I have a Marshmallow based ROM on my Nexus 4 and it doesn't seem to have such issues. Too bad, but hopefully this can be fixed in the future builds! (as I often watch YouTube videos). Any app that uses it's own internal player seems to work fine, though, such as Twitch
6) The multiwindow... kinda works. If you have two apps side by side - seems to function well. Anything beyond that - turns the screen into a mess. Dunno if it's because of the ROM itself or because of the feature, but at least it's kinda available here. Besides, can't really complain about an unfinished feature
Also, the Play Store app looks pretty awful using the Multiwindow, maybe it's not adapted accordingly by Google
7) The sound in this ROM is SUPER LOUD. It's nowhere near this level of volume on the stock ROM. I dunno if the audio balancing is wrong here or if it's supposed to be this way, but it's definitely at least twice as loud as official Sony's 5.1.1 firmware
8) Merging the SD card with the internal storage of the tablet went fine, and I seemed to have no issues transferring the data
9) Minor things:
- The "About this tablet" screen still says "Sony Xperia Z2 Tablet WiFi" despite flashing the ROM on the LTE version
- The text in Bluetooth screen when it's off seems to be aligned to the left, looks weird
10) The SuperSU works fine, apps have no issues requesting permissions nor does SuperSU have any issues granting said permissions to the apps on its own
And I that's it. If anything else surfaces - I'll let you know
Thanks for continuing to build 6.0 AOSP roms for castor_windy ! My computer died so I can't compile anymore atm, I'm glad someone else is doing it !
Fatal1ty_93_RUS said:
hey @rcstar6696, Installed the ROM just a few moments ago. Enjoying it so far! Some feedback:
1) The installation went through very smoothly, like I have a Nexus device
The "Flash ROM -> flash KK kernel -> Flash SuperuSU -> Flash MM kernel" went okay as well, no issues, just a little extra step to gain root until we have XZDR for Android 6.0
2) The ROM booted up SUPER FAST for the first time. Sony's firmware usually takes at least 2-3 minutes to boot up fully from a shutdown state, while this ROM booted up in less than like 30 seconds. Very refreshing to see such short booting times!
3) The backup restoration process seemed to not have gone through fully. Only about half of the apps I had were restored. Not really much of an issue, just a personal observation
Also after confirming what apps I wanted to restore, the setup wizard stayed at the "Please wait..." screen, so I had to manually quit to the homescreen via the Home button. Seems like a bug to me? Or maybe it's the built-in GAPPS that's the issue (haven't tried flashing a GAPS package manually though)
4) The system seems to not recognize my SIM-card for some reason. It just tells me "No SIM card installed", which is weird considering that the ROM is for the LTE version. Tried turning on and off the Airplane mode to reset the modem - no result. Tried rebooting the device - also n result.
Maybe try to look at Sony's official binaries for Tab Z2? http://developer.sonymobile.com/downloads/tool/software-binaries-for-aosp-m-android-6-0/
5) Like you said, the video playback is all green/purple artifacted. Wonder if it's the drivers/libraries issue, as I have a Marshmallow based ROM on my Nexus 4 and it doesn't seem to have such issues. Too bad, but hopefully this can be fixed in the future builds! (as I often watch YouTube videos). Any app that uses it's own internal player seems to work fine, though, such as Twitch
6) The multiwindow... kinda works. If you have two apps side by side - seems to function well. Anything beyond that - turns the screen into a mess. Dunno if it's because of the ROM itself or because of the feature, but at least it's kinda available here. Besides, can't really complain about an unfinished feature
Also, the Play Store app looks pretty awful using the Multiwindow, maybe it's not adapted accordingly by Google
7) The sound in this ROM is SUPER LOUD. It's nowhere near this level of volume on the stock ROM. I dunno if the audio balancing is wrong here or if it's supposed to be this way, but it's definitely at least twice as loud as official Sony's 5.1.1 firmware
8) Merging the SD card with the internal storage of the tablet went fine, and I seemed to have no issues transferring the data
9) Minor things:
- The "About this tablet" screen still says "Sony Xperia Z2 Tablet WiFi" despite flashing the ROM on the LTE version
- The text in Bluetooth screen when it's off seems to be aligned to the left, looks weird
10) The SuperSU works fine, apps have no issues requesting permissions nor does SuperSU have any issues granting said permissions to the apps on its own
And I that's it. If anything else surfaces - I'll let you know
Click to expand...
Click to collapse
1) at the moment we we don't have a change for working recovery i tested some more things
2) same here :good:
3) i have no problem while restoring aps via ti only the google apps i can't restore all other work
4) my fault i forgot to add the castor link sorry i will do it in 5 min than your sim will work but you need to configure your apns by yourself
5) i think this is a driver issue we had the same **** on aosp l and we use the same driver
6) multiwindow is buggy but its not a full feature of android m its only for testing
7) ok never tested it on full loud
8) yes sdcard is a little bit confuesd now due the new encripton from google
9) sorry you need to flash system and boot.img again but the correct one than all will be good i will add the link
Btw v3 is uploading at the moment
The bluetooth text is not our fault this is from google
basic086 said:
Thanks for continuing to build 6.0 AOSP roms for castor_windy ! My computer died so I can't compile anymore atm, I'm glad someone else is doing it !
Click to expand...
Click to collapse
Yes no problem i build it before you released it too but i won't release it with the internal storage bug
V3
Small Update
fixes some small Sensor bugs but the Lightsensor is not fixed :crying:
It should be up in the next half an hour
rcstar6696 said:
Small Update
fixes some small Sensor bugs but the Lightsensor is not fixed :crying:
It should be up in the next half an hour
Click to expand...
Click to collapse
Excellent, pulling now, will report anything interesting found. Is there anything in particular you want battle tested?
NOTE: Mega is pretty slow atm, so it may take awhile..160k over vpn on a 350Mb connection. AFH for future updates maybe? 2hr download to get the 1.2gb file. If not maybe consider zipping up the sparse image files to cut the upload/download times.
Do you think this can work on a z3 tablet? according to gsmarena they have kind of the same specs: same resolution, same cpu (MSM8974AB), 3gb ram, even the cameras (8.1 and 2.2mpx)
dnnz said:
Do you think this can work on a z3 tablet? according to gsmarena they have kind of the same specs: same resolution, same cpu (MSM8974AB), 3gb ram, even the cameras (8.1 and 2.2mpx)
Click to expand...
Click to collapse
I think not z3 tablet uses msm8974AC and has other device configs too. Don't flash it
i fixed the lightsensor now he is working
i think i will make a flashable zip for it
Lightsensor fix
Link to flashable zip https://mega.nz/#!LdBzHaQC!uiZIrU-eoI3Lriczk_em2vCXNNZVQ-tX17kcw5F7LWQ
This package includes older sensor moduls and some files but this will fix light sensor
Next build will include the patch but for now use the fix.
Installation is like super su or root
Flash old kernel
Reboot to recovery
Flash lightsensor fix.zip
Reboot to bootloader
Flash M-Kernel ( boot.im)
Reboot and enjoy
Have you noticed the battery drain during deep sleep ? It's called Miscellaneous in the battery stats, I wonder what it could be ?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
About Resurrection Remix ROM
Changelog
Installation
Downloads and useful linksAbout Resurrection Remix ROM
Resurrection Remix the ROM has been based on CM,slim.omni and original Remix ROM builds, this creates an awesome combination of performance, customization, power and the most new features, brought directly to your Device
[font=Verdana, Arial, Helvetica, sans-serif]Many things that in previous versions were tweaked with mods, are now included by default in the ROM so, please enjoy![/font]
Special thanks to, the CM team,OMNI team ,SLIMROMS and of course to all the supporters
WIPAs this is the 1° released of CM13 for Quark this ROM may have features that are not full working.
So what I have tested and works, data, call, wifi, GPS, bluetooth, USB OTG and MTP, camera, Music/video app, Xposed, Gapps...
Included Main Features
- Check RR changelog and RR M Quark changelog
-ALL cm13.0 Features
-Check 3# and 4# post for screen shot of the features...
This ROM has safetynet verification Support of course when ROOT is disabled:
I develop a simple app to disable and enable SU at will, after disabling SU the user can pass safety net verification without having to remove SU.
I call it iSu XDA thread Click here
It works today only with CM 13 building SU binary it is present in almost all CM Base ROM.
Warning! There is a small implementation that need to be done to the kernel to have this working 100% the app will work on any device running CM base ROM but may loose ROOT support after a reboot if running without my kernel MOD.
Before install read this...
If you are using Any custom ROM that is not RR android Marshmallow 6.0.x you must do a clean install and fallow " Installation Instruction"
If you are using RR android Marshmallow 6.0.x you can do a dirty flash and fallow "Update Instruction" but if encounter problem do a clean install before report bugs...
Installation Instruction
- Download the latest build
- Download Gapps
- Take a TWRP backup
- Demanding - Clean install/Full wipe (Wipe, Dalvik, Data, Cache and System)
- Flash ROM using latest TWRP recovery
- Flash ROM + Gapps (clean install is demanding to flash ROM + gapps at the same time)
- Reboot to system.
- Enjoy!
Update Instruction
- Download the latest build of Resurrection ROM
- Take a TWRP backup
- Flash ROM using latest TWRP recovery
- Flash Gapps + any other zip you have flash before
- Wipe cache
- Wipe dalvik art
- Reboot to system.
- Enjoy!
Installation Files
Download ROM
Gapp's Recommended
Base on the latest users report the most stable is Banks, Opengapps some times is unstable if prefer Opengapps and have problem try a old version check the old Opengapps link
Banks
Opengapps ARM 6.0 Pico latest
Opengapps ARM 6.0 Old releases
TWRP
[url=https://github.com/ResurrectionRemix/android_vendor_resurrection/blob/marshmallow/CHANGELOG.mkdn]Changelog-RR[/url]RR M Quark changelog
Big thanks to:
XDA developers
CM team
Omni team
Slim rom
@Skrilax_CZ for his hard work on building cm-12/12.1/13.0 to this device
AND OF COURSE TO ALL THE SUPPORTERS, DONATORS AND USERS
Big thanks:
A big thank for those ho help me donating to my work.
XDA:DevDB Information
Resurrection Remix for Quark, ROM for the Motorola Quark XT1225, XT1250 and XT1254 -- Moto Maxx, Moto Turbo and DROID TURBO.
Contributors
baybutcher27
Source Code: https://github.com/ResurrectionRemix
Device Tree
Kernel tree
Vendor tree
Mod Kernel Adiutor tree
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.10.x
Based On: CM, slim.omni and original Remix ROM builds
Version Information
Status: Stable
Created 2016-02-16
Last Updated check Download link
I port this help from my 5.x.x thread some things here may not be the same, I will update this with time
Etc App.
Motorola Apps:
I have included on the ROM the motorola-specific play store props and permissions allowing the user to install Moto apps via Playstore…
here the list:
Be Aware some app will not work
I have not tested Gallery because it conflict with theme app (please use another gallery app like QuickPick It gets integrated by camera app just like the default gallery.
Moto email, it install but doesn't let use the app.
Moto voice, it just not install.
All the rest available Moto app seems to be working.
Be aware I will try to fix this app on the future but i don't give any prediction of when, this is not my priority this is a CyanogemMod base ROM not a Motorola or google , any user can use google and search a way to fix this problem, if any one do let me know I will check and made the change so every one can have all available apps working.
My personal Wallpaper folder, to personalized you ROM it contains all most 1000 pics.
BLOATWARE remove List-Script for all Quark
Check my BLOATWARE remove thread to know what app is safe to remove from custom ROM and or stock, for custo I have made a script.
------------------------------------------------
Help:
Device specific bugs:
Below is more a general help then a device bugs because most users will not ever be notice any of this problem reported, so if encounter any problem try to read it all before reporting, if find any new bug or solution please report.
CM12.1/13 Bugs:
- This may have the same bug of CM12.1 or CM13.0 because this share a lot of source's, (if any one found a CM bug please report so i can check, because I may not keep track of reports there), some bugs of CM I have already fix but they may not be fix on CM, so do not expect to find every bug here, and if you are in doubt if one particular bug exist here, ask me I will check...
USB otg and MTP
USB otg and MTP change on Marshmallow if you are new at this please read before post.
After connect to your pc a notification will appear pull down the notification click on it and chose MTP
USB Otg can be read by any file app, but you must find it... It new location is in the root of the device in /mnt/media_rw
My advice is just to make a desktop shortcut from es file explorer to that folder... this way you can put that on a folder or any place of the desktop of the device and access quickly when is need.
Set selinux to permissive
Selinux is the police of the android it will block any service that is not know or allow (of course if the service/app has super su access it will not occur but some times do)
So by default it comes enable (enforcing), if you have a problem with some app service you may try set it to permissive to test.
Selinux can be change via kernel auditor plugin, or via settings>configurations>Miscellaneous.
Led:
-LPThemer Xposed module if enable the option (Enable Notification text color) under Status bar, the led doesn't work. May exist other modules or app that conflict with led notification...
DPI change
- The device will auto reboot when change the DPI that is not a bug.
Radio image
TWRP Flash zip of Moto SOAK XT1225 Radio images.
CM dev share all stock Radio image on CM thread but those need to be flash via bootloader.
GPS OR RADIO related problem:
Changing the ROM may cause GPS lock problem..
To solve is necessary to erase the radio status, that can be achieved via this zip "Clean_modem_status.zip" flash it via TWRP no wipe is need.
If find any problem related lost signal after, re-try the flash of "Clean_modem_status.zip", if the problem persist, flash latest radio.img version fia fastboot (aka via bootloader)
Code:
mfastboot flash radio radio.img
find the radio.img inside the stock ROM xml.zip, some xml.zip and fastboot for windows can be found here (click here)
Gestures/Ambient display:
- Pulse notifications, Wave and Pick-up, work very well, but is necessary to turn it off and on after 1° installation of RR, go to settings>Gestures> un-check and check to enable.
Random FC
- If encounter any FC, before make a report, try to clear data of the FC app, if that doesn't work, try to uninstall/install the app, and if that doesn't help try a clean install of the ROM if you didn't clean install the last update the ROM.
This is old and doesnot happens anymore on RR but I leave for the purpose of consulting.
On screen Navigation bar:
- After first boot you may see on screen navigation buttons, to remove it Settings>configurations>Buttons> un-check Navigation bar buttons....
Web Whatsapp CM bug Fix by CM dev.
Web Whatsapp works but if you try to loging the first time the image may be interlaced, that doesn't block you from loging, just place the device on the front of the screen at the same height of the QR and it will login.
Is possible to set the DPI to 480 ant this bug will not occur at that DPI.
Video apps Netflix HBO etc.
I'm particularly don't have this bug have teste youtube and netflix is all good, but was reported that this apps may not work for one user, the the fix is change a build.prop line:
persist.hwc.mdpcomp.enable
# GLES doesn't support secure display, to allow google play movies netflix
# and other apps that require a secure display we need to enable this
# but this cause screen fragments and glitch , this is a odd bug may not occur always, so is disabled by default
# to enable this change the false to true on the below line in the build.prop and to prevent screen bugs enable
# Disable HW overlays on developer options to not have glitch on the screen
persist.hwc.mdpcomp.enable=false
Waze motogeogence bug
If you use Waze GPS Social, Map... to not have problems is need to freeze a app before run the Waze app, the app to freeze is, MotGeoFenceSvc app or com.motorola.motogeogencesvc 1.0.1 (it has two names) in setting app you can't disable this app, to do that is need to use a root app like titanium backup or similar, or you can just remove the apk folder using a root browser remove the folder system/app/MotGeoFenceSvc.
------------------------------------------------
Changelog and updates:
Change log
! Changelog is inside the device device... Settings > About a phone > About Ressurrection> Changelog
I will be updating this weekly, will post on the thread warning on it update...
-------------------------------------------------
Bug report with in the most accurate description possible, do not spare words, screens and logs, a bug that i can't understand can't reproduce I can't fix.
Screenshots
On the attachment are the RR basic features, the features may change I will try to keep the pics up to date.
Next post more...
Screenshots
On the attachment more of RR basic features.
Currently in class, but I'm downloading now! Excited! I will be flashing it in a few hours. Can't wait.
I'm excited to test this out. Do I flash over my existing RR ROM or clean install?
Downloading now!
--
Moto Maxx - XT1225
Xposed RR Rom 5.1.1
Help
Thanks for the file!
But I have a problem when installing:
7 error error installing zip file
I would like to help me?
---
Moto Maxx - XT1225
Stock ROM
TWRP 3.0
Epic - Downloading...
I have an XT1250 currently running your 5.1.1 rom. I would install this and let you know of any bugs
Installed...running great. Did a clean install, i hate dirty flashing. I have Google 2 Step Verification, it didnt work on the initial setup but worked after the OS started up. I guess thats kinda irrelevant if you ask me. The interface looks a lot smoother than the 5.1.1 rom but mayb its just me. I would keep using and let you know. Ambient screen works great. LED is still broken tho. Ive learnt to live without lol.
Thanks man!!! u are the best
rafaelduim said:
Thanks for the file!
But I have a problem when installing:
7 error error installing zip file
I would like to help me?
---
Moto Maxx - XT1225
Stock ROM
TWRP 3.0
Click to expand...
Click to collapse
Clean install is demanding check 1# post instalation instructions...
Latiken said:
I'm excited to test this out. Do I flash over my existing RR ROM or clean install?
Click to expand...
Click to collapse
Clean install is demanding check 1# post instalation instructions...
kenennaoyeka said:
I have an XT1250 currently running your 5.1.1 rom. I would install this and let you know of any bugs
Installed...running great. Did a clean install, i hate dirty flashing. I have Google 2 Step Verification, it didnt work on the initial setup but worked after the OS started up. I guess thats kinda irrelevant if you ask me. The interface looks a lot smoother than the 5.1.1 rom but mayb its just me. I would keep using and let you know. Ambient screen works great. LED is still broken tho. Ive learnt to live without lol.
Thanks man!!! u are the best
Click to expand...
Click to collapse
Led doesnot work for you on 5.1.1? too.
Because is just fine on my device, I received a notification and the green led light up...
There is the chace that some app is couse that for you with I don't know...
:good:
My bad. Installing now.
baybutcher27 said:
Clean install is demanding check 1# post instalation instructions...
Clean install is demanding check 1# post instalation instructions...
Led doesnot work for you on 5.1.1? too.
Because is just fine on my device, I received a notification and the green led light up...
There is the chace that some app is couse that for you with I don't know...
:good:
Click to expand...
Click to collapse
Yeah it works..but the LED just stays green and doesnt pulse. and it looks like two LEDS with a divider in the middle. It looks a lil weird lol. Since i cant get it to pulsate, i just disabled it.
baybutcher27 said:
Clean install is demanding check 1# post instalation instructions...
Clean install is demanding check 1# post instalation instructions...
Led doesnot work for you on 5.1.1? too.
Because is just fine on my device, I received a notification and the green led light up...
There is the chace that some app is couse that for you with I don't know...
:good:
Click to expand...
Click to collapse
Thank you!
I managed to install. But my Moto 360 does not connect!
It will be a bug?
I installed it and used it for a few minutes before going back to L.
It's a good first test build but I noticed several bugs and things missing such as the Hardware buttons options.
Latiken said:
I installed it and used it for a few minutes before going back to L.
It's a good first test build but I noticed several bugs and things missing such as the Hardware buttons options.
Click to expand...
Click to collapse
you need to report the bugs if you don't I can fix it.
I have none, and my hardware keys are just were they always be, the ROM can't remove any hardware part.
A lot of things on Marshmallow are in different place, if your search for software keys it is call navigation buttons. :good:
made a USB otg and MTP help
USB otg and MTP change on Marshmallow if you are new at this please read before post.
After connect to your pc a notification will appear pull down the notification click on it and chose MTP
USB Otg can be read by any file app, but you must find it... It new location is in the root of the device in /mnt/media_rw
My advice is just to make a desktop shortcut from es file explorer to that folder... this way you can put that on a folder or any place of the desktop of the device and access quickly when is need.
rafaelduim said:
Thank you!
I managed to install. But my Moto 360 does not connect!
It will be a bug?
Click to expand...
Click to collapse
LG G Watch works fine for me...try to restart the phone and try again
kenennaoyeka said:
LG G Watch works fine for me...try to restart the phone and try again
Click to expand...
Click to collapse
Restarted the moto 360
baybutcher27 said:
you need to report the bugs if you don't I can fix it.
I have none, and my hardware keys are just were they always be, the ROM can't remove any hardware part.
A lot of things on Marshmallow are in different place, if your search for software keys it is call navigation buttons. :good:
Click to expand...
Click to collapse
Only thing I'm noticing that's gone regarding the hardware keys is the ability to change the backlight settings. Other than that, I haven't had any issues so far.
Vanilla-ish AOSP 7.1.2_r13 ROM (N2G47X) for WiFi/LTE Nexus 9
This was created by building from N2G47X source, including SuperSU and cherry picking a few commits...
FOR ROOT - SuperSU no longer included!!!
Featuring:
Vanilla AOSP 7.1.2_r13 (N2G47X) for WiFi/LTE Nexus 9
June 5th 2017 security patch level in ROM AND Kernel
SuperSU Free v2.79 SR3 Removed in v1.11.170405
LTE works
NTFS/exFAT file system support (for OTG)
Advanced power menu
Nougat 7.1 boot animation from Pixel XL
Nav bar tuner, night light, brightness slider toggle
System UI Tuner now shows by default in Settings
Removed/sped up some animations for faster/smoother experience
Won't overwrite TWRP with stock recovery
OpenGapps compatibility - stock now working
busybox 1.22.1 removed in v1.11.170405
All future Nougat builds will all be based on this table - https://source.android.com/source/build-numbers.html#source-code-tags-and-builds
AdAway v3.1.2 Removed in v1.11.170405 since no longer including root
Amaze File Manager v3.1.1
You can skip setup wizard (if needed) by tapping all 4 corners in clockwise order starting with top left...
Self-compiled 3.10.103 kernel also from AOSP source (https://android.googlesource.com/kernel/tegra/+/android-tegra-flounder-3.10-nougat):
Current with June 5th 2017 security patch level
Audio issue fix (partial)
healthd charging issue fixed (v0.60)
No forceencrypt
UKSM
Permissive
f2fs supported on /cache
frandom support (added in v0.42)
SIO/FIOPS IO Schedulers (added in v0.42)
Advanced TCP congestion enabled
fsync togglable (added in v0.42)
2.0A charging support (added in v0.42)
Snappy compression library
Defaults
Governor - Interactive
IO Sched - FIOPS
TCP Congestion control - Cubic
UBERTC-4.9.4
Source:
https://github.com/bshiznit
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Please use TWRP 3.0.2-1 PLEASE be at bootloader 3.48.0.0141 and have flashed the latest NMF26F vendor image (linked under downloads)!
You may not need to wipe between versions, if issues please wipe data and both caches (in TWRP got to Wipe --> "Swipe to Factory Reset")
Downloads
Before flashing scroll down and read NOTES!
ROM
DEODEX (for Xposed/GravityBox, theming, etc.):
https://www.androidfilehost.com/?fid=889764386195909301
md5 - 1170234b143704e7202baa72a9ec48f3
No ODEX yet ODEX (faster initial boot and overall performance potentially):
MEGA
Dev-Host
md5
3.50.0.0143 bootloader and N9F27C (N4F27E for LTE model) vendor.img - NOTE there are not 7.1.2 vendor images (Nexus 9 is not officially supported in 7.1.2) so I am pulling the latest 7.1.1 ones from https://developers.google.com/android/nexus/images
WIFI:
https://www.androidfilehost.com/?fid=961840155545575100
md5 - 515f1c328c7a0491f4d3a1e297264053
LTE:
https://www.androidfilehost.com/?fid=817550096634779382
md5 - 5f12990a299d304cdaa8ff843b2ba6c1
NEED fastboot
In fastboot:
WIFI/LTE (be sure you've got the right files!):
Bootloader:
fastboot flash bootloader bootloader-flounder-3.50.0.0143.img
fastboot reboot-bootloader
Vendor image:
fastboot flash vendor vendor.img
OR
Flash vendor.img using new feature in TWRP 3.0.0 (tested using 3.0.2-1) - in recovery's "Install" menu hit the "Install Image" button...
Then ROM
Open GApps (closer to STOCK - choose ARM64 for Platform, 7.1 for Android I pick Stock for Variant
http://opengapps.org/
Direct link:
http://opengapps.org/?download=true&arch=arm64&api=7.1&variant=stock
NOTE takes a WHILE (5-10 minutes) to boot up on first boot! ART is optimizing applications and it is set to EVERYTHING as we have sufficient system partition storage - for SPEED. There is no more dalvik-vm (no REALLY now - not even included in AOSP now)!
If you like it hit thanks! Donations are appreciated but never expected
I do this for a hobby and to keep my tablet running like new
Coming soon:
?
NOTES:
ALWAYS flash GApps even if updating from a prior AOSP 5.1.x/6.0/7.x release! ALL ROMs format the /system partition as part of the installation process and this is where the:silly: GApps are kept!
BACKUP using TWRP and/or Titanium - save those files off the device to a USB stick external HDD or whatnot! Not responsible for lost data!
WIPE Data in recovery
Be sure you are at bootloader 3.48.0.0141 and have flashed latest vendor image (steps in this post)
ONLY TESTED USING TWRP 3.0.2-1
MUST FLASH a GApps zip after the ROM for Play Store, etc.
If you like it consider donating! A nice big solid state hard drive will let me build faster and for more devices! (YAY my build box now has 411GB free even after all this developing - thanks to all who donated)
Thanks:
Nitrogen OS for a lot of things I cherry picked! (@Mr.MEX, @xyyx) - https://github.com/nitrogen-project
Pure Nexus for tons of cherry picks too (@BeansTown106) - https://github.com/PureNexusProject
Team OctOs (@hedwig34) for good SuperSU integration and other custom vendor ideas - http://www.github.com/Team-OctOs
@timduru for some great cherry picks from his TF300T ROM source - https://github.com/timduru
@USBhost - kernel ideas/source - https://github.com/USBhost/FIRE-ICE
@flar2 - kernel ideas/source - https://github.com/flar2/ElementalX-N9
@Beta1440 - kernel ideas/source - https://github.com/Sublime-Development/kernel_flounder
@Snuzzo for github familiarization and being a great dev and resource, as well as introducing me to kernel devving!
@sykopompos for ART build.prop tweaks.
@scrosler great dev and good resource
@Chainfire for SuperSU and keeping it updated!
Google for Android
AOSP for source!
Changelog
N2G47X... v1.11.170405 --> v1.12.170613:
Updated to N4F26X Nougat 7.1.1_r33 (April 5th 2017 security patch level)
Removed included automatically flashed SuperSU (also removed AdAway and busybox)...
N4F26X... v1.11.170306 --> v1.11.170405:
Updated to N4F26X Nougat 7.1.1_r33 (April 5th 2017 security patch level)
Removed included automatically flashed SuperSU (also removed AdAway and busybox)...
N4F26T... v1.11.170207 --> v1.11.170306:
Updated to N4F26T Nougat 7.1.1_r24 (March 5th 2017 security patch level)
Cherry picked partial audio fix into kernel - https://github.com/vartom/android_kernel_flounder/commit/b94b18d897d5d40b0d8fb382855d85d2e3340a71, https://github.com/vartom/android_kernel_flounder/commit/5c4645b56609a305ca147869616af61de578d492
N4F26Q... v1.11.170106 --> v1.11.170207:
Updated to N4F26Q Nougat 7.1.1 (February 5th 2017 security patch level)
N4F26M... v1.11.161206 --> v1.11.170106:
Updated to N4F26M Nougat 7.1.1 (January 1st 2017 security patch level)
NMF26F... v1.10.161117 --> v1.11.161206:
Updated to NMF26F Nougat 7.1.1
NDE63V... v0.71 --> v1.10.161117:
Updated to NDE63V Nougat 7.1!
Sounds and boot animation from the Pixel XL Android 7.1...
NRD91N... v0.70 --> v0.71:
Updated to NRD91N 7.0.0_r15 (November 5th 2016 security baseline)
NOTE - to be fully patched you MUST ALSO update to the vendor partition from NRD91N!!!
NRD91D... v0.60 --> v0.70:
Added ntfs-3g and exfat libraries and utilities (exFAT/NTFS file system support - useful for OTG) - https://github.com/bshiznit/platform_build/commit/269b4fbc1fb4a60db8d4986347b7be52702101b3
Re-added integrated SuperSU - https://github.com/bshiznit/platform_build/commit/ddcb3a0697ee4e904ed8680cdd1181b2129b8af5, https://github.com/Team-OctOS/platform_vendor_to/commit/4f8286815fc8be7c884cf370a6db5054600cd2cb
init.d support fixed (https://github.com/bshiznit/platform_vendor/commit/faa8839c075425831b59b9fd49711832e09a978e)
NRD91D... v0.50 --> v0.60:
healthd fixed in kernel (charging issue) - https://github.com/CyanogenMod/andr...mmit/f63db167706bb651562a262bc3169c0961769fe0
Stock GApps can now be flashed - commits:
https://github.com/AOSPA/android_frameworks_base/commit/d36582165d4694da101cc65755af0841d443c80e
https://github.com/AOSPA/android_frameworks_base/commit/b70f5994464cf6b3b29cedcc4efdd73807a27b0f
Boot animation from Pixel
RAMDisk hacked up (LOL) in kernel to allow SuperSU to flash correctly
Decided NOT to include automatic flashing of SuperSU (see poll - can add back!)
Bionic updates (some arm64, aarch64 stuff - busybox needed this updated for whatever reason in order to compile correctly)
Busybox now compiled in (thanks to Bionic updates)...
MixPlorer replaced with Amaze File Manager
False errors no longer show when flashing in recovery - https://github.com/bshiznit/platfor...mmit/5b1db93c0e05244a087feb6a5970183a75f53770
Thanks a lot man! Any bugs?
Sent from my ONEPLUS A3003 using Tapatalk
jaju123 said:
Thanks a lot man! Any bugs?
Sent from my ONEPLUS A3003 using Tapatalk
Click to expand...
Click to collapse
GApps doesn't seem to stick? SuperSU doesn't seem to flash right either! Still tweaking things but this is a very early build
Congratulations!!
Absolutely awesome my friend!! You are the first dev to get an N9 Nougat ROM up and running!!!
matthewgwilt said:
Absolutely awesome my friend!! You are the first dev to get an N9 Nougat ROM up and running!!!
Click to expand...
Click to collapse
Thanks - wish I had it working better!
IDEA - (still screwing around with builds or I'd try right now) - flash my ROM, Flash ElementalX kernel (N9-5.02 - http://forum.xda-developers.com/nexus-9/orig-development/kernel-elementalx-n9-0-02-alpha-t2931657) - then see if GApps/SuperSU work...
Will try ASAP and get back
EDIT - OK well - no SuperSU but flashing the ElementalX kernel DOES allow the GApps to install (and show up - without the kernel it appears to work but I see nothing when I boot)... Flash kernel, GApps - then got to Settings --> Apps --> Google Play services and click permissions then allow everything allow Location (that's all that is needed to fix)!
Ok, so I goofed...I thought I was on TWRP 3.0.2-1, but I was on 3.0.2-0 I flashed everything, and it boots, however I can't get past the "Google Play services keeps stopping" popup. Every time I try to close it, I'm pushed back to the wifi selection screen, and I can't get to the home screen. I tried going back into TWRP, and TWRP goes into a sort of bootloop where the splash screen will show, but it keeps rebooting to it :/ Any help would be much appreciated! Thx in advance
sabrdawg said:
Ok, so I goofed...I thought I was on TWRP 3.0.2-1, but I was on 3.0.2-0 I flashed everything, and it boots, however I can't get past the "Google Play services keeps stopping" popup. Every time I try to close it, I'm pushed back to the wifi selection screen, and I can't get to the home screen. I tried going back into TWRP, and TWRP goes into a sort of bootloop where the splash screen will show, but it keeps rebooting to it :/ Any help would be much appreciated! Thx in advance
Click to expand...
Click to collapse
Fastboot flash 3.0.2-1, then reflash the ROM.
cam30era said:
Fastboot flash 3.0.2-1, then reflash the ROM.
Click to expand...
Click to collapse
Thx so much! That was going to be my next resort, after mulling it over for a while
sabrdawg said:
Thx so much! That was going to be my next resort, after mulling it over for a while
Click to expand...
Click to collapse
Sounds like you did update the bootloader and vendor partition! In TWRP before 3.0.2-1 the new vendor partition is encrypted and TWRP has no idea how to decrypt it...
RE: the play services crashing (I did add this later to OP) - go to Settings --> Apps --> Google Play services and click permissions then allow Location
bshiznit said:
Sounds like you did update the bootloader and vendor partition! In TWRP before 3.0.2-1 the new vendor partition is encrypted and TWRP has no idea how to decrypt it...
RE: the play services crashing (I did add this later to OP) - go to Settings --> Apps --> Google Play services and click permissions then allow Location
Click to expand...
Click to collapse
Well, I successfully flashed the correct TWRP! The only problem is that the Google Play services error is still persisting I can't go into settings to allow location, because I can't get past the Checking Info screen. It keeps bumping me back to the wifi select screen. Argh Let me make sure I'm on the correct bootloader. I did flash the .img file via TWRP using the boot partition...I wonder if it took?
My bootloader version says
HBOOT-3.48.0.0135
Looks like it is indeed the wrong one. I'll have to figure out how to correctly flash it via TWRP.
sabrdawg said:
Well, I successfully flashed the correct TWRP! The only problem is that the Google Play services error is still persisting I can't go into settings to allow location, because I can't get past the Checking Info screen. It keeps bumping me back to the wifi select screen. Argh Let me make sure I'm on the correct bootloader. I did flash the .img file via TWRP using the boot partition...I wonder if it took?
Click to expand...
Click to collapse
I see - I flashed the PICO Opengapps (which bypasses setup I'm thinking is why the difference) - maybe try that next?
bshiznit said:
I see - I flashed the PICO Opengapps (which bypasses setup I'm thinking is why the difference) - maybe try that next?
Click to expand...
Click to collapse
Will try! Thx for all of your help. It's much appreciated
Well, I restored RR so I could download the Pico Gapps, which worked fine once I flashed the Marshmallow vendor image again. Now TWRP isn't working again. The TWRP splash screen flashed several times before booting into TWRP, and now it's doing that thing where it asks you to enter a password, meaning data is encrypted and it won't recognize any of my files...so now I can't even flash the Nougat files again. Argh Perhaps I need to flash the Nougat vendor image via adb, however TWRP 3.0.2-1 should work on Marshmallow as well, right? Sorry to be such a pain.
EDIT
I finally got it to work! I ended up flashing the previous version of TWRP via Flashify, and it worked without encryption. I went ahead and flashed all files and still kept getting the Google Play services popup, however, this time I was able to get to the home screen and enable all permissions in settings. It worked like a charm What's interesting is that I'm also still on the MM bootloader.
sabrdawg said:
Well, I restored RR so I could download the Pico Gapps, which worked fine once I flashed the Marshmallow vendor image again. Now TWRP isn't working again. The TWRP splash screen flashed several times before booting into TWRP, and now it's doing that thing where it asks you to enter a password, meaning data is encrypted and it won't recognize any of my files...so now I can't even flash the Nougat files again. Argh Perhaps I need to flash the Nougat vendor image via adb, however TWRP 3.0.2-1 should work on Marshmallow as well, right? Sorry to be such a pain.
EDIT
I finally got it to work! I ended up flashing the previous version of TWRP via Flashify, and it worked without encryption. I went ahead and flashed all files and still kept getting the Google Play services popup, however, this time I was able to get to the home screen and enable all permissions in settings. It worked like a charm What's interesting is that I'm also still on the MM bootloader.
Click to expand...
Click to collapse
You aren't being a pain - even though it gets lost A LOT the spirit of this community is to just try stuff - even WIPs - and report back experience
For me I realized very quickly something was wrong with TWRP 3.0.2 after doing:
fastboot flash bootloader bootloader-flounder-3.48.0.0139.img
fastboot reboot-bootloader
fastboot flash vendor vendor.img
So I pretty much checked the TWRP flounder forum here and realized I needed to wait for them to build off Nougat source (aka 3.0.2-1).
Keep me posted and I will try to get more updates going
EDIT - I always keep my tab decrypted - which means when I'm screwing around it invariably gets re-encrypted and I have to wipe it
Anyone using GApps that include the setup wizard (stock for example - ironically the one I direct linked to in OP LOL) - you WILL see FCs until you can get out of that wizard and grant location permissions to Google Play services - to to get off that wizard screen (thanks to @replica102 in N6 forum):
Just tap on the four corners of the screen, starting from top left, clockwise. Do it right, and you'll get sent to home screen
Or use Pico/Nano and grab only the GApps you want
I'm happy to report that the ROM is VERY smooth! Thanks for all your hard work!
bshiznit said:
EDIT - I always keep my tab decrypted - which means when I'm screwing around it invariably gets re-encrypted and I have to wipe it
Click to expand...
Click to collapse
As far as that goes, I just always head to twrp before first boot, and flash fed patcher v8. Never have to worry about it re-encrypting it
SuperSU?
I noticed that SuperSU got crossed out after I got started. Does that mean it isn't rooted yet? I have tried the latest beta but still no good. Any idea's?
wantowan2 said:
I noticed that SuperSU got crossed out after I got started. Does that mean it isn't rooted yet? I have tried the latest beta but still no good. Any idea's?
Click to expand...
Click to collapse
I tried flashing the latest beta and went into a bootloop. I tried fixing contexts, but still no dice. I just wiped and reflashed the ElementalX kernel. I still wish I could get root to work, too!
LineageOS 19.1 for Sony Xperia XZ Premium
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
RELEASE
This is an alternative ROM for the Sony Xperia XZ Premium, offering several privacy features.
Please report any issues you observe apart from the ones listed below. Logs are needed for me to fix anything (preferably dmesg and logcat). I can't test NFC very thoroughly, to please report your findings.
FEATURES
Signed with dev keys
Up-to-date kernel
WireGuard kernel support
Real vendor partition
FBE instead of FDE encryption
DOWNLOAD
You can download the latest releases and TWRP here:
https://androidfilehost.com/?w=files&flid=333825
Check the ChangeLog below for firmware requirements!
INSTALLATION
This build uses a real vendor partition in place for the (now) useless oem partition. You will therefore need the modified TWRP with vendor/FBE support linked above.
Before first install: flash and boot into TWRP, format data, reboot to recovery and wipe all internal partitions.
After above step / any subsequent dirty flashes: Boot into recovery, put the ROM, GApps and root (if needed) on sdcard and flash.
Note: There is not going to be a LOS su addon anymore. If you need root, flash a root manager of your choice. No guaranteed support from LOS for this.
When updating from previous builds, simply dirty flash the ROM, together with any GApps and/or other modifications - addon.d will not work due to currently unavailable TWRP decryption.
Recommended GApps: MindTheGapps-12.1.0
KNOWN ISSUES
Stock camera is not working anymore due to incompatibility of stock library (libimageprocessorjni.so) with new libgui
You tell me...
Contributors
derf elot, modpunk, Rooted_Ansh
Thanks to the yoshino testers (let me know if I forgot to add you)
coin3x, feduss, GiaSen, Gizanagi, hsheemi, kaancaliskan, No1Alien, sohrab1985
Source Code
maple: https://github.com/whatawurst/android_device_sony_maple
maple_dsds: https://github.com/whatawurst/android_device_sony_maple_dsds
kernel: https://github.com/whatawurst/android_kernel_sony_msm8998
Rom Information
ROM OS Version: Android 12.1 / 12L
ROM Kernel: Linux 4.4
Version Information
Status: Stable
Current Stable Version: 1.3
Stable Release Date: 2022-04-20
SECURITY ADVICE
Don't flash ROMs or Magisk modules which set SELinux to permissive or you welcome malware on your device!
How to get root?
As mentioned before, there will not be an official su addon from LOS anymore. If you need root, flash an unofficial solution.
REQUIRED FIRMWARE: 47.2.A.10.107 (47.2.A.11.239 should also work as there isn't any real changes)
CHANGELOG
2022-04-20 | 1.3| 47.2.A.10.107
Initial release
Thanks for your work. And can the kernel support f2fs filesystem？ Does the camera work if i use another gpu driver？
ssdsw said:
Thanks for your work. And can the kernel support f2fs filesystem？ Does the camera work if i use another gpu driver？
Click to expand...
Click to collapse
f2fs is enabled in the kernel ( https://github.com/whatawurst/andro...8998-yoshino-maple_dsds_defconfig#L4632-L4636 ), but that doesn't mean you can use it as is. You would have to adjust the fstab's. No that I would recommend it, seeing as f2fs hasn't really received a lot of updates/(security) fixes for 4.4 kernels in recent times.
And no, you cannot update the gpu drivers. The Sony stock camera blobs are quite dependent on a specific tag.
derf elot said:
f2fs is enabled in the kernel ( https://github.com/whatawurst/andro...8998-yoshino-maple_dsds_defconfig#L4632-L4636 ), but that doesn't mean you can use it as is. You would have to adjust the fstab's. No that I would recommend it, seeing as f2fs hasn't really received a lot of updates/(security) fixes for 4.4 kernels in recent times.
And no, you cannot update the gpu drivers. The Sony stock camera blobs are quite dependent on a specific tag.
Click to expand...
Click to collapse
is there any clues/guide on how to edit the fstab?
so we can use f2fs on data & cache
is signature spoofing (for microg) enabled?
and as i already have installed the ArrowOS build of avl.callista which is based on your work: flash Stock ROM and then install your twrp+rom? or is stock rom step not necessary and it's enough to flash twrp+rom?
m00ns0rr0w said:
is signature spoofing (for microg) enabled?
and as i already have installed the ArrowOS build of avl.callista which is based on your work: flash Stock ROM and then install your twrp+rom? or is stock rom step not necessary and it's enough to flash twrp+rom?
Click to expand...
Click to collapse
no, spoofing is not enabled. I have made builds for 19 before with spoofing enabled, so it works. but rebuilding with spoofing enabled takes a while every time, since it includes changes in fw/b and that's a hefty compile.
as for flashing over another rom: it may or may not work. upgrading from los 18 should work by flashing rom together with 12.1 microg, but no idea about migrating from one rom to another.
derf elot said:
no, spoofing is not enabled. I have made builds for 19 before with spoofing enabled, so it works. but rebuilding with spoofing enabled takes a while every time, since it includes changes in fw/b and that's a hefty compile.
as for flashing over another rom: it may or may not work. upgrading from los 18 should work by flashing rom together with 12.1 microg, but no idea about migrating from one rom to another.
Click to expand...
Click to collapse
hi,
thx for your answer. i was just curious, as the arrowos build is based on your work and has signature spoofing enabled. But if, as you write, that's a lot of work then ... no problem. the arrowos version is stable
And, without signature spoofing, the part with "howto best migrate from rom A to rom B" is obsolete Self-building doesn't seem to be an option, as the hardware requirements seem a bit ... ambitious
Thanks for the great ROM.
I did a few tests today and I couldn't find anything broken.
The only issue I have found so far is when I take a picture or video with Open Camera and try to open it for preview inside the app. It does not work.
Thanks for your working on the ROM.
I found that LOS installed on my G8142 seems to have screen always on when charging, both on 18.1 and 19.1 (which is this one). How to turn it off?
Very nice, THANK YOU for great rom, i am testing it rn, so far so good.
To save someone a troubles i encountered:
I am comming from rooted stock .107, please all do flash correct TWRP!!! , i was slopy but have experience in flashing so i just dirtyflashed it on old TWRP, phone hanged prior to accessing twrp, could not hardreset or annything haha and i had to pull my battery so please just in case FLASH CORRECT TWRP
I like it alot, am switching to daily
stipi69 said:
Very nice, THANK YOU for great rom, i am testing it rn, so far so good.
To save someone a troubles i encountered:
I am comming from rooted stock .107, please all do flash correct TWRP!!! , i was slopy but have experience in flashing so i just dirtyflashed it on old TWRP, phone hanged prior to accessing twrp, could not hardreset or annything haha and i had to pull my battery so please just in case FLASH CORRECT TWRP
I like it alot, am switching to daily
Click to expand...
Click to collapse
Great, yes it needs the twrp I uploaded because of vendor partition and change from fde to fbe.
But just for reference, pulling the battery should not be necessary if it gets stuck. it should be enough to press and hold vol up (or down, I forget because I haven't needed it in a while) + power. it'll vibrate once, but keep holding it until it vibrates twice in quick succession. that should power it off. you can then enter fastboot to flash twrp or flash mode to flash stock.
derf elot said:
Great, yes it needs the twrp I uploaded because of vendor partition and change from fde to fbe.
But just for reference, pulling the battery should not be necessary if it gets stuck. it should be enough to press and hold vol up (or down, I forget because I haven't needed it in a while) + power. it'll vibrate once, but keep holding it until it vibrates twice in quick succession. that should power it off. you can then enter fastboot to flash twrp or flash mode to flash stock.
Click to expand...
Click to collapse
I agree, but i have faulty vol+ key so i was having a hard part sadlly.
Can i ask you something i see this problem 1+ years on all Lineage roms and i am not a developer:
SETTINGS / DISPLAY / LIVE DISPLAY / COLOR PROFILE / VIVID
If i choose this profile i get like 8 bit colors after a while of use, but realy like this profile... i adjusted it manualy now its good looking and stable but wondering if it is XZ P specific or all lineage
short message: my SIM card isn't working with this ROM.
long message: today i installed this ROM. I first flashed stock ROM, booted into it once, and then flashed this ROM. But, as with the ArrowOS ROM, my SIM card isn't working.
More Details: after fresh install of this ROM and during boot i enter the SIM PIN (so that works), but after boot it says: "service not available" (Dienst nicht verfügbar). I'm unable to get it working.
Provider: congstar (telekom daughter). The SIM worked with stock ROM, and it works in an older Samsung S5. Just for curiosity i flashed stock ROM again and
Yeah, i know, no warranty, but... someone had such a problem before?
thx
geee... getting crazy here... after the next (test) flash of this ROM the SIM suddenly works, as well as phone calls, SMS, ...
what's the difference to the first flash? after latest stock ROM flash i left the SIM inside, and the stock ROM (or the telekom software) did some settings, rebooted, and then i started the last flash. Is there something magic that is happening here?
if i had more hair all of it would be bright gray...
OK, after almost a week... no SIM card problems anymore. ROM is running stable.
Just some apps that somehow rely on Google Play Services (or microg maybe) don't run: apps that warn regarding severe weather conditions or catastrophes, like 'DWD Warnwetter', 'NINA KatWarn' etc.. Push notifications...
ROM is stable, and i finally managed the signature spoofing + microg stuff. Thx to @Yokurt815 and his little list in the XZ1C thread - going step by step, writing it all down, finally succeeded.
Am i right that the magisk/lygisk stuff has to be done again after flashing an possibly upcoming ROM update?
Big thanks to @derf elot for this rom
A couple of things though . . .
Anyone got this setting to turn on?
All languages set to English AU
Mind the gapps 12.1 installed
Google set to default assistant
Also, trying to search in settings causes a crash.
shoey63 said:
Big thanks to @derf elot for this rom
A couple of things though . . .
Anyone got this setting to turn on?
All languages set to English AU
Mind the gapps 12.1 installed
Google set to default assistant
Also, trying to search in settings causes a crash.
View attachment 5643169
Click to expand...
Click to collapse
Edited: NVM, seems like it won't work neither.
You need to set Ok Google/Hey Google at first boot; otherwise, it won't work.