yashsingh1/xdaforums huggingface dataset:
[Moto Maxx Android Development] rascal9:
So this Doze setting is why i was randomly losing Cell service after 15 minutes? I installed this and bays kernel only to lose service constantly and went back to CM nightlies :(

Xt1254

VZW USA
[Moto Maxx Android Development] Nitefire77:
I don't think its the doze setting making you lose signal. I'm on XT1254 and running the ROM without issue
[Moto Maxx Android Development] quantum tao:
im on verizon and my cell standby is eating battery an cell signal is way lower than normal. do you think i should reflash original L radios?
[Moto Maxx Android Development] Nitefire77:
Reflashing the L radios wouldn't hurt anything, but the cell standby issue comes from being connected to WiFi while Mobile Data is on. If you turn off mobile data when you are connected to WiFi you will not have the cell standby drain. Also, if WiFi is off and you are connected to LTE you will not have cell standby drain.

I run with mobile data off when I'm at home on WiFi and no longer experience the drain
[Moto Maxx Android Development] quantum tao:
That definitely made a difference. Thanks!
[Moto Maxx Android Development] quangv:
What's the theme you use?
[Moto Maxx Android Development] Nitefire77:
Its "Deep Darkness" off the playstore. Its free, and updated constantly
[Moto Maxx Android Development] gimpy1:
I've run into a problem that I haven't had before. I don't think it is rom related? I can not get into twrp recovery. When I reboot into recovery, it takes me to the little green Android on its back (and not into two). When I go to the recovery mode, it will not take me to recovery (twrp). It just flashes to my boot animation and back to the Android. The boot log says "invalid boot image size". I have to go to the "start" button and then it does restart (reboots) the phone back to working.

Yesterday I did upgrade twrp to 3.0.2.0. I don't know if that had anything to do with this or not. After getting that message I was able to reflash back to twrp 3.0.0., but I still cannot get into twrp recovery (I get the same problem/message).

Any help or ideas?
[Moto Maxx Android Development] RLShiftyDoggit:
I would try reflashing twrp w fastboot like when you first put twrp on the phone that should fix it possibly idk it's a toss up but its worth a shot
[Moto Maxx Android Development] gimpy1:
I'm sorry but I don't know how to use fast boot. I'm on the droid turbo and that is not how I did it (I don't think). I used the "Sunshine" method to unlock the bootloader, then used flashify to obtain root.

Do you know what that message means? Invalid image size.
[Moto Maxx Android Development] RLShiftyDoggit:
If you used the droid turbo as I did myself you used had to used fast boot to first flash recovery there's a thread in the Verizon Motorola droid turbo general section that is how to unlock your BL flash twrp and obtain root go to that and it'll walk you thru it also didn't read you used flashify don't use that
[Moto Maxx Android Development] ChazzMatt:
You can use Flashify app to reflash TWRP.
[Moto Maxx Android Development] gimpy1:
Shifty, before I read your last post, I did try flashify. Using Flashify will get me into twrp, but I can only get into it by installing the twrp "image". That opens up twrp for me, but when I reboot the phone, then the problem reoccurs. I cannot reboot back into twrp unless I do an image install from flashify (I did it twice) again. I will check out the Verizon post you mentioned it I can find it.

Thx, for your help. I do need to get this corrected properly.

---------- Post added at 01:10 AM ---------- Previous post was at 01:05 AM ----------

ChazzMatt, just saw your post. As I noted in my above reply to shifty, I did do just that. But, it did not fix the problem, although it does get me into twrp just once, but not again unless I keep reflashing the twrp image.
[Moto Maxx Android Development] RLShiftyDoggit:
Fast boot should correct it fully
[Moto Maxx Android Development] kitcostantino:
personally, in this situation, i would say its time to back up your internal storage on a usb otg card or computer, and do a full fxz. it sucks, but we all end up there eventually. you can use mfastboot to reflash and just delete or omit the line.

im my experiences, it has proved to be better to bite the bullet and erase the internal SD. (erase user data). good luck!!

one other thing...have you tried going back to TWRP 2.8.7.x?
[Moto Maxx Android Development] gimpy1:
I went back to 3.0.0, but have not tried 2.8.7. I will try these later as I am having some testing done today (Dr. Office).

What do you mean by a "full fxz"?
[Moto Maxx Android Development] Nitefire77:
I would look into doing a fastboot install if twrp before erasing user data and see if that fixes it any. There are several guides on YouTube to using fastboot.

I personally use the minimal adb and fastboot program. I download the latest TWRP for quark, rename it to just recovery.IMG and copy/paste it into the minimal adb and fastboot folder and fastboot flash it without issue
[Moto Maxx Android Development] gimpy1:
One more quick question. If I can get back into twrp, I noticed last night that when the "mount" button is pressed and the screen comes up, it shows the "system" box is unchecked. Does it, the system check box, need to be checked?
[Moto Maxx Android Development] Nitefire77:
Nope you don't need to check it. When you flash roms and stuff in twrp it mounts system and flashes the zip. You should see in the logs as it flashes that its mounting system. The only reason you should have to mount manually is if you are using the twrp file manager to move files to system
[Moto Maxx Android Development] gimpy1:
Ok, Thx. My turbo works fine right now, except for not being able to get into twrp, either thru stock recovery or normally. I am trying to be very careful not to do anything that would cause it to boot loop. That is when I won't be able to get into recovery at all.
[Moto Maxx Android Development] gimpy1:
I was able to get back into twrp temporarily using Flashify and installed version 2.8.7. Unfortunately that did not correct the problem. After rebooting I still cannot get back into twrp.

After reading the suggestions from the posters here, there seems to be two suggestions I haven't tried, yet: fastboot or fxz/data erase (even after googling, still not sure what fxz is)?

I assume if I restore a previous backup from twrp, that will not correct my problem?

For the fastboot method I am limited to using my wife's surface pro 3 computer. I'm not real familiar/good with it. I haven't been on it in a few weeks. She does not like for me to mess with her things when I am "playing" with my phone ?.

So, the consensus is to try fastboot? I've never used it and am a little apprehensive.
[Moto Maxx Android Development] rascal9:
You are unlocked with sunshine correct?

See if rashr app works for you and try either CM recovery or TWRP
[Moto Maxx Android Development] gumbi2647:
You do have superSU active and up to date? Also if you don't have a computer then download terminal emulator from the play store and then you can type in the commands as if you had a computer hooked up to it. I can't remember the commands but someone on here can probably help. I had trouble a while back with fastboot and Windows 10. Hopefully it will help you!
[Moto Maxx Android Development] Grynch13:
I would definitely go adb route first but fxz is reinstalling the factory software and earasing everything basically a factory phone with unlocked bootloader but even at that point you will have to use adb to install twrp again or you could use sunshine app till you had temp root then flashify install twrp. But to fxz you download the latest software factory zip install the drivers and unzip the contents of the zip file in your adb minimal folder then click the bat file you unzipped and it will do the rest to get you back to a factory phone
[Moto Maxx Android Development] Nitefire77:
Resurrection Remix has released version 5.6.7 and scanning the changelog shows a bunch of fixes and improvements added that should make things even smoother.

When its updated for quarks we should have smooth sailing
[Moto Maxx Android Development] gumbi2647:
I have been on the latest build and kernel. Zzmove and zbattp with only 1 random reboot in a week. This is the battery life so far.
[Moto Maxx Android Development] gimpy1:
The error message I get when I am in the "log" section of the stock recovery (is that what is referred to as "fast boot"?) is :

" invalid boot image size!

Failed to validate recovery image "

That error message is in pink and

" fastboot reason: fall - through from recovery boot mode "

That error message is in yellow.

I have searched google pretty extensively in doing the adb fast boot method and about have myself talked into trying it.

I did originally unlock the bootloader via Sunshine and get root using Flashify. Would that also be an option, then?
[Moto Maxx Android Development] gumbi2647:
Have you used root checker to make sure that you have proper root?
[Moto Maxx Android Development] gimpy1:
Yes, I just rechecked and it does say I have proper root.
[Moto Maxx Android Development] gumbi2647:
I know that you probably tried it but have you downloaded twrp 3.0.1-0?
[Moto Maxx Android Development] gimpy1:
I just tried it. No luck. Just to make sure I am doing it right. I get into twrp (via flashify), then click on the install button. This opens up all the zips I can flash. In the lower right corner of that screen is a button that says "image". I click on that and I get four, I think, twrp images 2.8.7 thru 3.0.2.0. I click on the one I want to install and two choices then come up. Recovery or boot (I think). I click recovery and then install it (it takes about one second to install), then I reboot the device.

That is the correct way to install it?

After rebooting back to the phone, I'm fine until I try to get back into twrp. I cannot.
[Moto Maxx Android Development] iiWoodstocK:
Yep. That's the correct procedure for updating TWRP within TWRP.

EDIT: try the TWRP manager app to update TWRP. Maybe that'll fix things
[Moto Maxx Android Development] rascal9:
If you have latest drivers installed for Motorola and ADB setup you can try this BAT file from Motorola-Firmware-Team Download HERE It will get you back to 44 Stock. This was recommended to me when to me by Computerfreek274when I soft bricked my XT1254 VZW. Little Extreme in your case, but at least you can have this as a back up plan if all else fails.
[Moto Maxx Android Development] gimpy1:
Rascal, I will check that one out.

iiWoodstock, I have twrp manager installed and I may have used it, can't remember. But, I get this warning when I get ready to install it. Is it ok to check "Yes" to install it?

I may have used this app and checked the yes when I initially installed 3.0.2.0, which was the version I was on when the problem first started.
[Moto Maxx Android Development] iiWoodstocK:
I've actually never used TWRP manager, so I'm not sure. *If* I had to guess, I'd say check yes as that file path appears to be correct looking.
[Moto Maxx Android Development] gimpy1:
Well, it's already broken, so here goes ????
[Moto Maxx Android Development] immadeofpixels27:
BE WARNED: If you don't edit the command to flash the bootloader image out of that .bat file it will lock your bootloader again! Tread carefully when using stock images!
[Moto Maxx Android Development] Nitefire77:
I'm not 100% on this, but I thought once the bootloader is unlocked flashing the bootloader won't relock it. In the official CM12.1 and 13 thread the files with the radio images also have the bootloader images, and instructions for flashing them, including the Verizon SU4 bootloader. I remember flashing the bootloader and radios together when I was running Resurrection Remix 5.5.9 and it didn't relock my bootloader.

I have to reflash the radios to fix my connection issues
[Moto Maxx Android Development] Andrey G.:
You can't relock bootloader that way in any circumstances. Keep calm.
[Moto Maxx Android Development] gimpy1:
Ok, I tried flashing thru twrp manager. I can get into twrp recovery much the same way as when I go thru flashify. And I still have the same problem. Before I flash into twrp in twrp manager I do get the following message/warning.

View attachment 3718225

So, now I am wondering if I could have downloaded and installed the wrong twrp image for my phone, the Droid turbo (xt1254)?

The twrp website does not have a download for the XT1254 specifically. I guess I could have chosen the wrong image? I chose the moto Maxx quark image to download, I'm pretty sure. That would be the correct one?
[Moto Maxx Android Development] quantum tao:
Quark is correct.
[Moto Maxx Android Development] koftheworld:
Exactly. I just fastbooted over all pieces of the turbo stock image (including the bootloader) and had no issues with a relocked bootloader.
[Moto Maxx Android Development] gumbi2647:
Disclaimer I am in no way responsible if you break your phone. Double check everything from other sources.

Just making it easier to find the needed files:

Kingroot: (no longer needed for sunshine)

http://xdaforums.com/android/apps-games/one-click-root-tool-android-2-x-5-0-t3107461

Sunshine (now in official release)

http://theroot.ninja/download.html

TWRP for quark:

http://xdaforums.com/moto-maxx/orig-development/recovery-twrp-2-8-7-0-touch-recovery-t3180308

Chainfires SuperSU:

https://download.chainfire.eu/696/supersu/

(Uninstall old root manager then Simply flash with twrp)

Themes and applications for the Motorola Moto Maxx:

http://xdaforums.com/moto-maxx/themes-apps

Modify your boot logo:

http://xdaforums.com/showthread.php?p=64121852

Cm12.1 for all quark

http://xdaforums.com/showthread.php?p=59577875

Make sure you use a nightly 11/29/15 or later.

xposed installer:

http://xdaforums.com/showthread.php?p=58828974

Flash v78-sdk22-arm.zip in twrp then

Install and run xposedinstaller from the link.

Modified Motorola camera app

(Turns off wavelet noise and more)

http://xdaforums.com/moto-g/themes-apps/app-camera-galery-t3216944

Instructions for bootloader unlock:

Run sunshine

(Kingroot no longer needed)

Instructions for TWRP install:

(Taken straight from the twrp link)

Alternate way:

Install flashify from play store, click recovery image, choose flash file, install twrp for quark. (You may need to use kingroot for temp root)

Fun links:

how the boot loader exploit works

http://theroot.ninja/disclosures/TRUSTNONE_1.0-11282015.pdf

I know its a little dated but you should be able to navigate here to find the one you need. It looks like fastboot is going to be the only option.
[Moto Maxx Android Development] rascal9:
I ran this exact BAT file and my bootloader was still unlocked. It just brought me back to bone stock then i started over with updating and flashing.
[Moto Maxx Android Development] Grynch13:
I have done a clean install on my xt1254 with factory images I can assure you it won't relock your bootloader.
[Moto Maxx Android Development] bubblesd306:
Not able to switch to LTE/CDMA, stays on Global...XT1254
[Moto Maxx Android Development] ruledrbrt1:
I've had reboots while typing as well. Even had one happen while listening to music through Poweramp through Bluetooth. Did not think to get the logs though.
[Moto Maxx Android Development] kenennaoyeka:
I was also listening to music via BT using Google Play tho. I dunno if that's a trend
[Moto Maxx Android Development] ruledrbrt1:
Well the typing reboots happened while I was in class, no music being played. I was using Facebook messenger if that makes a difference.
[Moto Maxx Android Development] kenennaoyeka:
So its fair to isolate the bug to a Keyboard issue
[Moto Maxx Android Development] Nitefire77:
I've typed while playing music via Bluetooth using Poweramp also, bit I didn't get any reboot. It only happened to me once with completely different things I detailed in a different post. Haven't had any reboots at all today and I've used my phone extensively
[Moto Maxx Android Development] kenennaoyeka:
It does not happen all the time. All replies on this thread have been written with my phone. Normally I wouldn't even mention this cos it happens rarely but the dev wants us to test the ROM so I'm just letting him know how it behaves on an XT1250 on T-Mobile US at least. Lol
[Moto Maxx Android Development] immadeofpixels27:
I also had that issue
[Moto Maxx Android Development] mcjonesy:
I'm having the same problem (XT1254, too). It hasn't affected my data connection, though, so that's good.
[Moto Maxx Android Development] quangv:
It always LTE, not able to switch GSM or 3G for me
[Moto Maxx Android Development] bubblesd306:
Anyone able to get VVM working on XT1254 yet.
[Moto Maxx Android Development] Grynch13:
Easter egg

Go to about phone click on android version a bunch then tap the circle and drag your finger around the perimeter of the circle to open a cheesy game
[Moto Maxx Android Development] Nitefire77:
that game has been there since 5.0
[Moto Maxx Android Development] Grynch13:
Cool just got my turbo a week ago so have been burning though all the ROMs so far this one is kicking some major ass just takes a little adjusting to some of the new marshmallow settings anyone have any tips or settings apps that will help with battery life
[Moto Maxx Android Development] fgl27:
ROM update! ResurrectionRemix-M-v5.6.3-20160218-quark.zip​

Download-ROM

If dirty flash and the device don't boot make a clean install (Wipe dalvik cache, cache, system and data) then install the ROM + Gapps (demanding when clean install flash ROM+ Gapps at the same time).

Changes:

Enable HW keys on setting/buttons and in the tiles

Fix Video Rec sound

Clean the ROM remove unneeded not working features and app.

Improve TCP buffers

Improve default network/radio attributes preference

Included all the latest CM13.0 and RR Marshmallow changes and Fix's

This ROM doesn't have my kernel it have Stock-CM-Kernel but you can download and use it, I do this because some people may not need custom kernel or wanna to test without it.

Download BHB27-Kernel

Use only the latest version of my kernel today BHB27-Kernel-V126-CM-RR-Test-05-M.zip please don't report a bug if not using the stock kernel of this ROM or my kernel this version always the last version...

Bug report: make 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.
[Moto Maxx Android Development] fgl27:
This version may fix the wifi problem to some users... So test report...

Other bugs please report torch and some other will be fix on a next version...
[Moto Maxx Android Development] GreaterLesser:
Double Chop for Torch still crashes CMActions and Torch does not stay in my quick settings. Everything else looks fine so far. Will test more and report back.
[Moto Maxx Android Development] RSDamasceno:
Download and report back.

--

Moto Maxx - XT1225

Xposed RR Rom 5.1.1
[Moto Maxx Android Development] blustosa:
I tried the fix for the GPS on the first page but it didnt do it for me. Tried searching through the rest of the post but couldn't find anything else on it.

Any thoughts?
[Moto Maxx Android Development] kitcostantino:
What fixed mine, back on LP was flashing the radio and bootloader package via Fastboot and rolling back to an older version of Maps.

Edit: droid turbo on vzw
[Moto Maxx Android Development] kitcostantino:
sorry i havent been on here, man. FXZ is Motorolas factory software. you install it using RSD LITE, Motorolas firmware flashing software. both your fxz and RSD lite can be found on rootjunky.com (like the plug, [MENTION=4246643]Tomsgt[/MENTION] ? ;) lol )
[Moto Maxx Android Development] fgl27:
ROM update! ResurrectionRemix-M-v5.6.7-20160412-quark.zip​

Download-ROM

If dirty flash and the device don't boot make a clean install (Wipe dalvik cache, cache, system and data) then install the ROM + Gapps (demanding when clean install flash ROM+ Gapps at the same time).

Changelog

This ROM doesn't have my kernel it have Stock-CM-Kernel but you can download and use it, I do this because some people may not need custom kernel or wanna to test without it.

Download BHB27-Kernel

Use only the latest version of my kernel today BHB27-Kernel-V129-2-CM-RR-M.zip please don't report a bug if not using the stock kernel of this ROM or my kernel this version always use the last version...

Bug report: make 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.
[Moto Maxx Android Development] immadeofpixels27:
Thanks to all who corrected me (and there were a lot of you). I've never had to flash radio images so I didn't realize it also flashed bootloader, and when I first rooted and unlocked, the guide I used specifically said to make a new .bat that only flashed system for getting rid of kingroot, then flash SU. I assumed flashing the bootloader would lock it, and I'm still curious as to how it manages to stay unlocked, but thanks again for the info! Always good to know more :)
[Moto Maxx Android Development] Grynch13:
I have no idea why it doesn't either I was scared to **** when I did it the first time. But before I did I asked on the sunshine site and they said I was OK and go ahead, and it worked great. As far as I know the only way to relock is through fastboot commands so it is next to impossible to acidently relock, and even if you do relock it on the droid turbo I have seen at least four or five seperate people have success reunlocking but it's extremely dangerous and could brick you so always be careful
[Moto Maxx Android Development] Nitefire77:
The bootloaders remain unlocked once you unlock them mainly because Motorola officially supports bootloader unlocking for unlocked versions of their phones. and lots of times there is a bootloader update along with official software updates that they only wanna update it and not risk bricking phones. Some phones can have a bootloader locked in a later update when it came factory unlocked, but simply relocking a locked bootloader would risk a ton of bricking claims they would rather avoid.

On Topic: Thanks [MENTION=5747496]baybutcher27[/MENTION] Flashed your latest rom and kernel, all is running great and smooth, and I noticed my phone didnt heat up hardly any when optimizing apps, which was nice. Thank you as always for your continued hard work and support of this rom for us!
[Moto Maxx Android Development] RLShiftyDoggit:
Why would the latest version not boot if dirty flashed? [emoji53] (I haven't tried it just wondering)
[Moto Maxx Android Development] Nitefire77:
I dirty flashed the update and its working fine. He is just saying IF it doesn't boot to do a clean flash. Sometimes there are apps that cause problems when one dirty flashes. Most people won't have a problem.
[Moto Maxx Android Development] RLShiftyDoggit:
Oh OK lol funny part is I just updated to the update before this new one yesterday.... Shows how much I pay attention xD
[Moto Maxx Android Development] gimpy1:
Well, I just tried again and twrp worked this time. ? I didn't do anything but try installing the twrp image thru the app twrp manager this morning. It didn't work, so I forgot about it until now. I tried rebooting into recovery and everything worked as it is supposed to. ?

All good now.

When I went into fast boot, no error messages in the log.
[Moto Maxx Android Development] Nitefire77:
Awesome! Glad its working smooth for you now!
[Moto Maxx Android Development] gimpy1:
I'm not sure. I had left it alone and was showing a coworker and,,,, it worked! I was really surprised. I've checked it three or four times both ways and working now, installed with 3.0.2.0.
[Moto Maxx Android Development] Artnig:
Time to update after two months haha. Just optimizing apps right now, excited for the new version :)
[Moto Maxx Android Development] RLShiftyDoggit:
Updated dirty flash worked :) got BHB27 kernel flashed too looks all good
[Moto Maxx Android Development] affineer:
I am on 12.1, am i good to flash this rom? I don't want to relock my sunshine-unlocked bootloader on xt1254?

What things should I consider to avoid relocking bootloader?