Search results

Color me SOL. My Moto Z has been exhibiting a similar issue. It would heat up very easily on even mundane tasks, thermal throttle HARD and stay there until I leave it to cool off before very easily doing do again, at which the phone is already past the point of being uncomfortable to hold. It...

About 4 months since, and HDR+ never fails to amaze. I do wish the app gave exposure compensation controls, though. I often found that it landed too bright at times.

Motorola support has gone downhill ever since the Lenovo takeover. Though from what I've heard, it's also pretty bad before they were Googli-fied.

Sadly, if you either updated to Nougat via OTA or the phone comes with Nougat, there is no way to downgrade to Marshmallow.

It's an issue on NPL25.86-15, as the 2 cores go to sleep completely, causing performance to suffer. In this case, it's more of a reading issue, as the processor works just as intended unless you've tweaked the governor. Another weird anomaly is that the battery gauge seems to go down at a...

I thought I'd say something odd about this kernel. After a while, AIDA64 and CPU-Z can't identify the big cores, identifying them as either "stopped" or "sleeping". However, running benchmarks reveal that the big cores are indeed running, as it gets scores that are typical of other 820 devices...

Stock recovery. I presume it's either because the build I ran was designed for a different region (same model code, though) or that the Marshmallow bootloader was incompatible with the OTA. Regardless, it's been working fine for a bit, although one Busybox installer gave me a small scare when...

Just for background info, at the time it happened, my Z was running NPL25.86-30 from the following thread; https://forum.xda-developers.com/moto-z/development/android-nougat-moto-z-versions-t3506342 It was running perfectly fine, then an OTA thing appeared. Well, I made the single big mistake...

Since you have the kernel, it should be a piece of cake to flash since dm-verity ain't messin' around anymore. Also, can you verify that your 2 high-performance cores are indeed working? I just flashed NPL25.86-30 and it brought back proper functionality of those. Seems to run significantly...

Interesting. Still rather skeptical, though.

I have a feeling that it might also be due to your phone running an older version of the software that the bootloader might not support. Regardless, I'm really glad that your phone is working. Enjoy! ;)

I recommend flashing the kernel first, then flashing SuperSU and Magisk. You need to wipe data before flashing the kernel, btw.

Sweet! Sadly, if the Wells Fargo app uses SafetyNet, unless you use Magisk, it won't work.

Well, if it works, then we'll be golden. But if it doesn't, I think the -30 firmware might help better. Sadly, I'm about to log off for the day, so do keep us updated on how it goes. Fingers crossed that you can get your Z working again.

Try using the TELUS firmware I linked in a thread earlier. https://forum.xda-developers.com/moto-z/development/android-nougat-moto-z-versions-t3506342

I can understand. I freaked out when the Nougat OTA bricked my own Z and I scrambled all-over for help, even heading to a service station even though they can't guarantee a successful repair and I needed to pay a service fee to get it sorted, only to fix it myself via reflash a couple of hours...

Can't hurt to try. Although for 86-15, I don't think it'll work since it's older than what your phone had. You might have a better chance going with 86-30.

Again, there's sadly no TWRP-flashable firmware for 7.0 RETUS. There's only one for TELUS. While it works on other XT1650-03s with unlocked BLs, can't guarantee that it's all stable. https://forum.xda-developers.com/moto-z/development/android-nougat-moto-z-unlocked-versions-t3552210

Hmmm..... Try flashing NPL25.86-30?

Well, this is a last-ditch effort, but you can try this. https://forum.xda-developers.com/moto-z/development/android-nougat-moto-z-unlocked-versions-t3552210 Follow the instructions exactly and see what happens. You also need that custom kernel to make sure it works. I wish I had more I could...

Sadly, no. As of right now, there's only a Marshmallow-based RETUS firmware. It'll take a while for someone to post firmware that's Nougat-based for RETUS.

Well, here's the problem. If you're on the 7.0 GPT and bootloader, you're out-of-luck. Because Moto has changed the rules on those to not accept Marshmallow-based firmware. Trying to flash a MM firmware will result in failure. Trying to downgrade the bootloader may cause your device to be...

Well, to even get Magisk and root to work, you need a working firmware. The fact that your device showed the cyan Moto screen means that the firmware is recognized, and how your PC recognizes the phone means that something is indeed working. But somehow, it's not displaying anything. Sadly...

Yeah. Because the only other fix I can think of is basically flashing the entire firmware including GPT and bootloader via RSD. But that requires firmware that's made exactly for that device and bootloader just to make sure everything is fine. I'm still crossing my fingers in the hopes that...

Try RETUS if it fails? I'm crossing my fingers hoping that the ROGERS firmware can help.

Well, if you want my advice, if you can find it, flash the firmware that your device was last at before you flashed Nougat. An OTA bricked my Z, but flashing the full firmware made exactly for my variant brought it back to life. If you can find it for yours, you might get a lucky break. Also...

I think your best bet is to try that RETLA firmware. I'm not sure how it does with Moto phones, but some variants are kinda picky with their software channels. Factory images designed for retail ("RETxx") devices might have a better chance since my RETAPAC model is on a RETMX build of Nougat...

The TELUS or the RETMX build? I've been using the RETMX build since January. Little to complain about. Only real issue is that the 2 HP cores park after a while and stubbornly refuse to unpark until the device is rebooted. Not much of a performance hit, but my OCD hates that. Kinda skeptical...

I'm assuming you tried to flash the stock ROM via fastboot? If so, I'm a little at a loss here. Although since you have TWRP, try flashing the stock ROM along with its recovery following the guide linked below...

I don't recommend it. RSD will flash the entire package including the bootloader. It's more than likely that it'll flash the new bootloader, causing you to lose your downgrade chance. Worst case scenario, because the software was designed for a different region, you may experience some issues...

Sweet! Can't wait.

I believe it's more of a reading error. When under a proper full-load, all 4 cores work as they should, as evident during benchmark performance and general gaming performance as well.

Did you do a TWRP system backup and restored it? If so, dm-verity may have been tripped. You will have to reinstall the firmware if you don't plan to be using a custom kernel. The full list is here. https://firmware.center/firmware/Motorola/Moto%20Z/Stock/XT1650-03/ Given that your device may...

Note that when you enable TWRP system write access, dm-verity will be tripped and you will be unable to boot unless you reflash the firmware or flash a custom kernel.

Thanks! Guess I won't have to worry too much when I decide to flash a ROM the moment support winds down for this device, which, knowing Motorola, will be pretty soon. Was kinda weary with mine, after getting a "System partition failed to recover" error in the stock recovery, but after a...

How's the included kernel? I presume it disables both forced-encryption and dm-verity, right?

So you tried to reflash the firmware via fastboot and your device is still dead? I had the same issue but flashing via RSDLite fixed it. In your case, I may have to throw in the towel and assume that a critical block on your system partition is corrupted beyond recovery, possibly caused by a...

If anyone asks why the kernel is necessary when mounting system as R/W. This is because by default, dm-verity is enabled, and will prevent the phone from booting if it detects an unauthorized change in the system partition. Flashing the kernel will disable dm-verity, which makes it a must if...

You will have to wait until either the Lineage Theming Engine is finished or OMS support is added. You can still use Substratum Legacy, but be warned that because OMS is not yet fully baked into the ROM, you can break the SystemUI, especially on 7.1.1, so make a NANDroid.

Anyone flashed this while their stock ROM is encrypted? Or does it require the stock ROM to be unencrypted? Sorry for the barrage of questions. This is the first Android I've used that has all these security checks (forced encryption, dm-verity and whatnot) while the phones which I tinkered...

A'ight. And I assume it also disables dm-verity or does it in a way that will not trip it? Just kinda confused because a OnePlus 3T will go into a bootloop when TWRP gets write access to the /system partition due to dm-verity unless one flashes a zip that will disable it along with forced...

Does this require the /system partition to be mounted as RW? I asked because I did have the Ramdisk error (not surprising as it was already rooted) and was curious on whether such installations require TWRP to have access to writing on the /system partition. And also because an increasing...

Sounds great. I assume one needs to mount system as R/W and either flash a different kernel (if not included) or just use the one included in the ROM itself to avoid dm-verity tripping and putting the device in the bootloop, requiring a factory image reflash, right? Curious if the stock ROM...

Does everything work perfectly, especially YouTube playback? If that's the case, then I'm very interested in how ROM development will pick up. Hopefully more ROMs spring up soon. Motorola themselves aren't great at updates these days and it would be nice to see the XDA Dev community give this...

Would this work fine if I were to flash it on a device that's running Nougat but on an MM bootloader? I asked because somebody else asked the same thing and the reply was that it might but may not be as stable. Would like to get some more word on this.

Are you on Windows 10? If so, that's the problem. RSDLite and Windows 10 don't play nicely with each other as of right now.

I've got a question. What method did you use to downgrade? Did you use RSDLite or ADB? And if you used ADB, exactly what did you flash? Furthermore, what was your software channel for both your phone and firmware? I asked because since ROM development for the Moto Z seems to be picking up, I...

It's me again. I've been seeing the development community of the Moto Z starting to pick up after the release of the Nougat source code, evident by the release of an unofficial build of LineageOS 14.1 and the rather quick pace of updates. However, that ROM was built on the Nougat source code...

The better choice is obviously the newer phone, especially in its unlocked form. But if flashing custom firmware is your thing, the Moto X is actually the better bet as there's an active dev community for it. The Moto Z's dev community is still rather quiet.

You know, I wonder if this works with the Hasselblad mod. I've always thought that the issues with the Hasselblad camera are software-related since the sensor is likely the same one from the 6P. If HDR+ and better processing can save it, color me impressed.