yashsingh1/xdaforums huggingface dataset:
[Moto Z ROMs, Kernels, Recoveries, & Other Developm] yanniclord:
Technically, there is no difference if you have the full unlocked Moto Z (International). Even if you have the US version, as long as it is unlocked, it works the same way as all other versions. The minor differences are only OEM/Carrier locks (which make the difference between Single IMEI/SIM and Dual IMEI/SIM). Otherwise there are no differences in firmware (afaik).
[Moto Z ROMs, Kernels, Recoveries, & Other Developm] Tom Conte:
Bummer

Bought an unlocked Moto Z GSM here and unlocked the boot loader.

NONE of your kernels work.

I've tried all of them :crying:
[Moto Z ROMs, Kernels, Recoveries, & Other Developm] janjan:
RUN/double click ADB.bat

adb devices

adb reboot bootloader

fastboot flash logo logo.bin

(I incloude all the necessary files in logo.zip)

https://mega.nz/#!E1YCGZ4A!KOHF6BviL1YYzydx4r_7RD4B5wZqBWrD_BbY1D-P5FY
[Moto Z ROMs, Kernels, Recoveries, & Other Developm] yanniclord:
LOL, i see what you did there. You took the start frame from the boot animation, and placed it above the Warning Text. I can see that, because i can see the little N/A in the lower left corner of the first M of the Moto Logo XD (because the M is opaque). But, it does work, no doubt there. Could you just fix the first M so that it doesn't display the N/A in the background?

In case you want a screenshot, i can provide you with that.
[Moto Z ROMs, Kernels, Recoveries, & Other Developm] Troll amiga:
big thanks

thank you for that
[Moto Z ROMs, Kernels, Recoveries, & Other Developm] reiteravi:
u can use the one from here

http://xdaforums.com/moto-z/themes/logo-bin-file-to-fastboot-unlocked-bl-t3494448

there is light and dark version

with white just where the "n/a" shows so u don't see it

used MotoLogo.v1.1 so u can make your own logo at wish
[Moto Z ROMs, Kernels, Recoveries, & Other Developm] yanniclord:
Link to MotoLogo v1.1? i cannot find it on Google, so that would be nice.

Never mind, found it.
[Moto Z ROMs, Kernels, Recoveries, & Other Developm] reiteravi:
http://xdaforums.com/2015-moto-g/themes-apps/mod-change-splash-screen-various-t3182994

got it from this thread
[Moto Z ROMs, Kernels, Recoveries, & Other Developm] yanniclord:
Ye it doesn't work at all. It requires a "validated" file, and since this is a modified one from janjan, it won't make the "Projects" folder. I found a program called Motorola Boot Logo Maker, but it has stupid size limitations.

EDIT: I can also see that the software janjan used, is the Motorola Boot Logo Maker as well, due to the comments section saying that the one i imported was made in that program.

---------- Post added at 12:18 PM ---------- Previous post was at 11:51 AM ----------

@janjan What picture is the one being displayed in the "Warning" message? Is it logo_boot, logo_unlocked, red, orange or yellow? My logo.bin is 13MB big and i can still flash it, but my image isn't being applied. I tried switching out all of the previous listed images, but that exceeded the size limit (about 31MB large, so i am guessing the partition size is 16MB, or am i wrong?). Anyways, what image do i need to replace so that it gets shown when i start the phone.

EDIT: I am getting a problem, it is saying that "(bootloader) has-slot:logo: not found" when i try to flash my custom logo.bin, same with yours now (though the image is still there). What can i do to fix this?
[Moto Z ROMs, Kernels, Recoveries, & Other Developm] Tom Conte:
nevermind, figured it out. Followed the recommendation here:

http://xdaforums.com/showpost.php?p=69111982&postcount=62
[Moto Z ROMs, Kernels, Recoveries, & Other Developm] reiteravi:
u can take one of the logo.bin i created with motologo and edit.

the logo.bin i edited is the original with only orange.png edited.

edit the png as u wish - direct edit pasting any image u want

as i think it will retain the right size - haven't tried otherwise.

remember to leave the area of "n/a" in white so that it won't be seen.
[Moto Z ROMs, Kernels, Recoveries, & Other Developm] H00pyFr00d:
I've tried this ROM a couple of times from a complete wipe and I've experienced the same bug.

Camera probably 1 in 3 times doesn't focus at all. Same with third party camera apps.

Any ideas?
[Moto Z ROMs, Kernels, Recoveries, & Other Developm] yanniclord:
Ye, i also noticed that. I thought that it just cannot focus as deep as i wanted it too (had to take picture of my PC screen, not with Print Screen), but i forgot that it is not an old Camera, and has both OIS and Laser Focus, so why couldn't it take a simple picture with focus.
[Moto Z ROMs, Kernels, Recoveries, & Other Developm] dhingra_vinay_in:
use google camera instead ...all i do is when i face this problem...i swith to google camera and then moto cam works good too !!!
[Moto Z ROMs, Kernels, Recoveries, & Other Developm] H00pyFr00d:
You can just quit and relauch the camera then it works. But by then you've missed the picture you wanted. And I need professional mode as low light photographs come out really badly.
[Moto Z ROMs, Kernels, Recoveries, & Other Developm] yanniclord:
Well i use Camera FV-5 and the Moto Camera, but i need Camera FV-5 for low light pictures and long aperture for pictures like the Northern Lights.
[Moto Z ROMs, Kernels, Recoveries, & Other Developm] erfanoabdi:
OK guys camera focus problem is related to my kernel and Motorola source code

they added missing repo to Motorola LLC GitHub exactly 1 hour ago and I compiled my kernel

Now I'm uploading new version (0.7) with some new features please use new version :cool:
[Moto Z ROMs, Kernels, Recoveries, & Other Developm] H00pyFr00d:
You hero! Thanks.
[Moto Z ROMs, Kernels, Recoveries, & Other Developm] yanniclord:
Yo erfan, did you also add back Infinity Focus? It is missing when i use Camera FV-5, but when i use the Legacy Camera Driver in Camera FV-5, it is there, but Shutter Speed is gone.

Also, i don't seem to find 0.7 on your thread for your KERNEL, only 0.6
[Moto Z ROMs, Kernels, Recoveries, & Other Developm] erfanoabdi:
yeah i fixed them all

check here
[Moto Z ROMs, Kernels, Recoveries, & Other Developm] yanniclord:
You're bonkers, thanks mate!
[Moto Z ROMs, Kernels, Recoveries, & Other Developm] l2icky:
Any chance this works on Verizon 1650-02?
[Moto Z ROMs, Kernels, Recoveries, & Other Developm] vittogn:
I finally have the Z and flashing your rom.

I'm with your recovery and after flashing the 06/11 ROM I'm stuck at unlocked warning for 10+ minutes! I don't see the optimizing app stuff.

I wiped everything but the external sd and wipe cache and dalving after (succesfull) flash.

Fastboot and recovery works.

What can I do? Should U try another recovery?

Tx,
[Moto Z ROMs, Kernels, Recoveries, & Other Developm] janjan:
Try the official twrp. It should work.
[Moto Z ROMs, Kernels, Recoveries, & Other Developm] vittogn:
I'm trying it at the moment. Thanks.
[Moto Z ROMs, Kernels, Recoveries, & Other Developm] regenwurm16:
I'm having the same problem.

Unlocked bootloader, fastboot flashed the latest official TWRP recovery, made a backup, did a factory reset, flashed your ROM, flashed newest TurboZ kernel and am stuck at the bootloader warning/bootanimation (after reflashing it with your two zips).

Then tried to only flash your ROM but same problem still (with wiping everything prior to flashing).

I'm having the same problem even after restoring my backup. When restoring TWRP said it can't delete "fsg" so I had to exclude it from the restore but it's still stuck at the boot warning.
[Moto Z ROMs, Kernels, Recoveries, & Other Developm] Troll amiga:
try using his twrp works for me all the time and the 1st boot wait 10 mins
[Moto Z ROMs, Kernels, Recoveries, & Other Developm] regenwurm16:
Troll Amiga, I did as you write but there was no difference.

Strange thing is even when restoring the backup I did right after bootloader unlock and flashing official TWRP it won't boot. It only boots the backup when I'm flashing the TurboZ kernel so something's not right.

Can maybe someone help me?
[Moto Z ROMs, Kernels, Recoveries, & Other Developm] Troll amiga:
cache

try advanced wipe dalvik/art cache and cache
[Moto Z ROMs, Kernels, Recoveries, & Other Developm] regenwurm16:
I do that pretty much always when doing such things.

I think maybe because I did a factory reset in TWRP before creating the first backup and the original boot.img not being able to handle unencrypted data partitions this could be the reason why they phone only would boot with TurboZ kernel installed.

On the other side I just restored my backup and installed the custom kernel and under security the phone is still stated as "encrypted" and not "encryptable" so I'm a little confused to why it won't start right after restoring the backup. Is it because the recovery partition is changed?

By the way I tried to install the deodexed version of the ROM.

I know tried the odexed version aswell but no luck there either.

I'm a bit frustrated, I thought that flashing and development on this phone is easier than on the ZTE Axon 7.

I just experimented a bit with my original backup.

When using the anykernel force encryption disabler zip on the original boot.img the backup boots up fine.

I then tried to install the SuperSU zip bundled with the deodexed ROM and it was stuck at the first boot logo.

Furthermore I noticed that in the two variants odexed/deodexed two different SuperSU zips are packed in.

The deodexed one just says installing and the odexed one is modified by "AlphaEva" and shows the normal routine of what patched at the moment 2 times strangely.

When using the official 2.78 zip it tries to install as systemless and fails at extracting the ram disk.

So as far as I could find out the SuperSU zip is the culprit to my boot problems which renders the whole bootloader unlock useless.
[Moto Z ROMs, Kernels, Recoveries, & Other Developm] regenwurm16:
Hello janjan

first thanks for the custom rom.

I managed to get it up and running after removing SuperSU from it because it was causing boot freeze problem.

I saw that you really deleted almost all apps possible (a bit too many in my taste)

I'm missing attentive display (at least the Moto app is crashing when I click the "exercise" button to test the function), color mode changer app, in camera when swiping left it says "activity missing" I suppose it's linked to Google photos and maybe some other stock apps that would be nice to have.

Can you maybe provide a zip with all the removed stuff or something? Because these special Motorola apps/functions are not available on Play Store (apart from Google photos)

It wouldn't be a problem to debloat the stock rom myself but all your tweaks sound very nice and I can't simply add them on my own.

Attentive display is working but it's always saying "Moto Actions force closed" when the timeout is up.
[Moto Z ROMs, Kernels, Recoveries, & Other Developm] enetec:
It was my fear... I've asked a LOT of times what could happen having an unencrypted phone and flashing back original kernel, BUT nobody answered me until today... :rolleyes:

This is a GREAT news.... I was going to hint you about it... It seems to be a "must have" in our SD for every emergency.... :p

Since you are going with tests... why don't you try to root with Magisk v.8 and its phh's SU?

I'm particularly curious about this combination in both encrypted and unencrypted situations... I've already opened a specific thread about it... we could continue there... ;)
[Moto Z ROMs, Kernels, Recoveries, & Other Developm] erfanoabdi:
Because data partition is (force) encrypted after any flashing from stock

You should wipe data partition(data and user data)
[Moto Z ROMs, Kernels, Recoveries, & Other Developm] regenwurm16:
I just tried restoring my backup and wiping ART cache, cache, data & internal storage after restoring the backup and it's still stuck at the boot warning. In the data manager of TWRP I saw that there are still files and folders under /data even though I did a full data wipe so I manually deleted them, restarted recovery and did a wipe again but still my stock backup won't boot if I'm not installing the force encryption disable zip.

After looking through the wipe options again I think I just selected the wrong option all the time. I went to advanced wipe and wiped data and internal storage but there's also a button named format data which actually formats data partition completely (deleting encryption aswell).

So I thought maybe that's the reason it's not working but I tried that aswell just now and the backup still won't boot without a modified boot image.

What would I have to do to get my backup running again. If it's always force encrypting the data partition shouldn't it work now?

I tried it with the deodexed ROM aswell now to format data and wipe all the other options and then flash the rom but it's only booting when I delete SuperSU from the ROM.

This seems to have been the problem from the beginning that SuperSU causes the freeze at boot.

I installed the ROM without SuperSU just now and booted it up and then went to recovery to install the SuperSU that came bundled with the ROM.

The phone just shut off after a few seconds showing the boot logo.
[Moto Z ROMs, Kernels, Recoveries, & Other Developm] erfanoabdi:
Oh bro I don't know were you went wrong but as you said it should work :confused:

Sorry I can't help maybe other guys, have more experience than me can help you

:silly:
[Moto Z ROMs, Kernels, Recoveries, & Other Developm] regenwurm16:
After extensive testing I can say that it's not SuperSU's fault but with the boot image

There's no problem when using my original boot image with encryption disabled or using TurboZ kernel without root.

As soon as I install root it gets stuck at boot (tried several SuperSU variants like the two bundled with de/odexed ROM, system mode ones from here http://xdaforums.com/apps/supersu/v2-64-2-66-supersu-mode-t3286120, or even the newest SR3 in systemless (which failed at ramdisk extraction))

The only way I could use root was when I flashed the boot image from here http://xdaforums.com/moto-z/development/recovery-twrp-3-0-2-0-test-beta1-t3467131 which is from a previous update of the software.

Here I had no problem flashing the systemmode SuperSU zip SR1 or SR3. To be on the safe side I still applied the encryption disabler zip.

I could use either the stock kernel or the TurboZ kernel with root without problems here.

So could somebody provide me/us with a boot image from the latest update modified in the same as done by JackyGreen?

I suppose it's not enough to simply flash the newest TurboZ kernel over this outdated kernel and it's like it was the latest image already?

Thanks in advance
[Moto Z ROMs, Kernels, Recoveries, & Other Developm] vittogn:
I finally got to to a successful install using the official recovery. Not at first attempt.

During installation process (a lot of stuff) the phone was lagging as hell but I guess it is normal. Now it's all good. Tomorrow during a normal day of use I'll be able to report performance and battery.

Tx for the great rom.

I noticed that battery stats report SOT that is lower than the actual usage. Any one else. Can't say yet if it is random or with a specific factor.
[Moto Z ROMs, Kernels, Recoveries, & Other Developm] enetec:
Sometimes I ask myself if people read my posts or what... :confused:

We have people having some issues, I've provided a working solution, they don't apply it... and then they return here with new questions... :rolleyes:

Why don't you simply listen what is told to you?

Magisk + SuperSU and (probably...) Magisk + phh's SU are known working solutions...
[Moto Z ROMs, Kernels, Recoveries, & Other Developm] vittogn:
Who and what do you refer to?
[Moto Z ROMs, Kernels, Recoveries, & Other Developm] enetec:
http://xdaforums.com/showpost.php?p=69593522&postcount=274 ;)

Magisk is known to be able to make SuperSU working on Moto Z when in normal condition it is unable to... e.g.
[Moto Z ROMs, Kernels, Recoveries, & Other Developm] H00pyFr00d:
I had the same experience with this ROM I'm afraid. Never got past the 'your phone is unlocked and cannot be trusted' screen. Odex and Deodex. Both from clean flash.

I flashed the boot.img and it worked fine straight after that.

The only other issue I have is a I can't get into battery stats. FCs the Settings. Anyone else?
[Moto Z ROMs, Kernels, Recoveries, & Other Developm] vittogn:
Battery stats work but SOT is underestimated I think.
[Moto Z ROMs, Kernels, Recoveries, & Other Developm] regenwurm16:
I'm not very familiar with Magisk, can you still flash SuperSU in system mode with it because with systemless installations I'm always having difficulties in titanium backup.
[Moto Z ROMs, Kernels, Recoveries, & Other Developm] enetec:
What sort of exactly? :confused:
[Moto Z ROMs, Kernels, Recoveries, & Other Developm] regenwurm16:
Whenever I wanted to delete a system app it would act like it deleted it but after refreshing the app list it was still there.

The only way was to got into root explorer mount system as r/w and switch to titanium backup then it would work.

I flashed the SuperSU 2.78 SR1 system mode right after flashing magisk zip, then TurboZ kernel and everything worked as expected so thanks again.

Your first message just looked like a suggestion to try magisk if it maybe helps and not like do this it's the solution to my problem.
[Moto Z ROMs, Kernels, Recoveries, & Other Developm] vittogn:
I need an advice. This issue is unrelated to this great ROM.

If I change the DPI setting e.g. from 640 (default) to 540 the stock camera does not work properly (shutter button does not work and other menu settings cannot be changed). It is the only app that does not work correctly. Any suggestion with a lower than 640 dpi setting that fully works?

Thanks in advance.
[Moto Z ROMs, Kernels, Recoveries, & Other Developm] vittogn:
I don't know if my issue (or feature??!!) is ROM and/or kernel related, but I noticed that when the battery mod is connected and it is charging (I'm in efficiency mode, so every time it get to reach 80% of phone battery) the SOT time does not increase.

Any other with the same issue/feature!!

tx
[Moto Z ROMs, Kernels, Recoveries, & Other Developm] H00pyFr00d:
Use App Settings Xposed module and change the Camera app to use the proper DPI. Moto haven't rendered their app to work in different DPIs
[Moto Z ROMs, Kernels, Recoveries, & Other Developm] vittogn:
Doesn't work! I applied and restarted the phone with no luck.

Any other suggestion? Tx.
[Moto Z ROMs, Kernels, Recoveries, & Other Developm] innit:
camera won't work with lower dpi. unfortunately you have to put stock values (640dpi) in appsettings, save and it will work.

Sent from my MOTO Z (XT1650-03) with Tapatalk
[Moto Z ROMs, Kernels, Recoveries, & Other Developm] vittogn:
Great.

It works now. Thanks for the help.

After setting 640 in appsetting a phone restart is needed.

Thanks a lot.
[Moto Z ROMs, Kernels, Recoveries, & Other Developm] H00pyFr00d:
I think we were saying the same thing in different ways.
[Moto Z ROMs, Kernels, Recoveries, & Other Developm] enetec:
Thank you for your explanation... it seems more a Titanium backup issue or a compatibility problem between systemless SuperSU and Titanium Backup... It could be interesting to know if this will happen with phh's SU (systemless) too...

Anyway it has some sense... systemless installations of SU/Xposed/etc, are done to not modify system partition to have it "untouched" for the various reasons we know... if it (SuperSU) then leaves every app to easily modify system partition (like file managers or Titanium Backup ...) using a systemless installation would not have a reason anymore... don't you think?

Magisk (which on other Motorola has shown some compatibility issues in past), seems to be very "Moto Z friendly": not only works fine with it, but (for some unknown reason... at least to me!) it seems to "stabilize" system installed apps too... apparently by solving issues with enabled encryption.

I'm pressing developers to add directly in kernel for this reason too... Eventually with phh's SU if this would show to work fine... ;)
[Moto Z ROMs, Kernels, Recoveries, & Other Developm] enetec:
Look what I've found...

;)
[Moto Z ROMs, Kernels, Recoveries, & Other Developm] regenwurm16:
Now the question is how long it takes to encrypt an empty data partition? Because I left it for 10 minutes and nothing happend. I was also irritated that it wouldn't go beyond the bootloader unlocked warning.
[Moto Z ROMs, Kernels, Recoveries, & Other Developm] enetec:
Good observation... but for security reasons encryption could include free space too (read: unallocated space containing deleted data...) :confused:

Anyway the Moto Z is full of strange behaviour to be investigated... look @ my post about WiFi/DHCP e.g... :rolleyes:
[Moto Z ROMs, Kernels, Recoveries, & Other Developm] benson1118:
Great work! And any person tried under clock the Moto z to 307MHz for longer battery life?
[Moto Z ROMs, Kernels, Recoveries, & Other Developm] vittogn:
Is this 246-45 the latest official Motorola available?
[Moto Z ROMs, Kernels, Recoveries, & Other Developm] erfanoabdi:
Yeah it's really amazing for battery life
[Moto Z ROMs, Kernels, Recoveries, & Other Developm] enetec:
My Italian Z think so... ;)
[Moto Z ROMs, Kernels, Recoveries, & Other Developm] Turbojugend:
Is there a fix yet for when it won't boot? Everything I have tried it just hangs at the first screen.
[Moto Z ROMs, Kernels, Recoveries, & Other Developm] H00pyFr00d:
Download and flash the other rom on this forum then boot it. Once that's done, flash this rom. That seemed to add all the missing bits for me and it booted fine. You'll need to obviously install TWRP after flashing the first rom though.
[Moto Z ROMs, Kernels, Recoveries, & Other Developm] vittogn:
I had similar issues.

I fixed it flashing first 16 OCT and then the latest odexed 6 NOV.

Don't ask me why but it worked!
[Moto Z ROMs, Kernels, Recoveries, & Other Developm] vittogn:
http://www.tuttoandroid.net/lenovo/...-iniziano-ricevere-android-7-0-nougat-431442/

Nougat is landing!
[Moto Z ROMs, Kernels, Recoveries, & Other Developm] Manish54:
Whats the difference between Odexed and Deodexed ?
[Moto Z ROMs, Kernels, Recoveries, & Other Developm] bmwh0r3:
odex is standard file system so to speak. Deodexed is optimized to modify for use with viper or xposed or blah blah blah. That's the basic gist of it. Search xda as this has been explained multiple times in a lot more detail. Enough detail that may leave you more confused than originally.
[Moto Z ROMs, Kernels, Recoveries, & Other Developm] Manish54:
Exactly, the explanations i saw were more complicated, thanks mate :)

One more question, will i still get the Nougat OTA update if i flash this ?
[Moto Z ROMs, Kernels, Recoveries, & Other Developm] bmwh0r3:
No... Otas will always fail on non stock(even if stock based) roms. There are ways around it using apps like FlashFire but I myself haven't used them. I myself find it easier to backup everything to external sd or otg drive and then use a pc to flash stock for clean installs of updates. Then root again and restore the backups. I came from nexus devices so I'm learning all over again how to use a non nexus device lol
[Moto Z ROMs, Kernels, Recoveries, & Other Developm] Manish54:
Haha.. same here. Never even tried any custom rom for last 3 years on my Nexus 5 :D
[Moto Z ROMs, Kernels, Recoveries, & Other Developm] silvercat:
Color Mod in display setting is not working, it says color manager not available.
[Moto Z ROMs, Kernels, Recoveries, & Other Developm] Troll amiga:
does any one kown when Nougat is coming to eu for moto z ?
[Moto Z ROMs, Kernels, Recoveries, & Other Developm] iron maiden:
Hello, I have the moto z retue version xt1560-03. Will you continue to update future versions? The warranty issue is lost to the bootloader unlocker? Some say that if others do not thank you very much

I feel my english

Thank you
[Moto Z ROMs, Kernels, Recoveries, & Other Developm] Troll amiga:
does any one have the update yet in the eu ????????
[Moto Z ROMs, Kernels, Recoveries, & Other Developm] silvercat:
Hi [MENTION=490110]janjan[/MENTION], since you moved to pixel will you be providing an nougat update for moto z?