yashsingh1/xdaforums huggingface dataset:
[Moto Maxx Android Development] Guth13:
Thank you very much
[Moto Maxx Android Development] fgl27:
Just in case some one is trying pass safety net app and can't lately is because safety net is reading that the bootloader is unlocked or the android is Modify, but there is a way to avoid that don't know how much time that will last but at least is working.

check iSu thread

http://xdaforums.com/android/apps-g...e-activate-t3478348/post70260918#post70260918
[Moto Maxx Android Development] mrkhigh:
I am still running an older version of RR but the unlocked bootloader did not affect me. I'm guessing the kernel I am in does not allow this check.
[Moto Maxx Android Development] fgl27:
I thinks is the bootloader version...

After some time I had update to Marshmallow I did not manage to pass...

The update also update the bootloader...

what is yours? from lollipop or marshmallow?
[Moto Maxx Android Development] mrkhigh:
It should be lollipop unless one of the roms I flashed included the bootloader, I do not think they did.

I've been itching to upgrade to RR 7.x, but now you have me nervous...

I am unsure how to check bootloader version though.
[Moto Maxx Android Development] fgl27:
on bootloader screen my show.

BL: moto-apq8084-70.94 (sha-d073b93, 2016-06-24 11:45:43)

I assuming a lollipop bootloader must have a date around when lollipop was released or before.

Custom ROM don't update bootloader, is not really need to update it unless your device can't boot, that did not happen ever on quark, but in some others moto devices sometimes is need lollipop bootloader to run lollipop custom ROM, Marshmallow to run Marshmallow etc... but I did not see that behavior in my tests, bootloader may be related to radio version if update radio and can't boot is need to update the bootloader to that same version, but that I did not test running old bootloader and new radio.img...

I did not try to use a old bootlooader to see if I manage to pass without a patch because I believed will not work...

Any way a least there is a patch that is working just in case any one need...
[Moto Maxx Android Development] mrkhigh:
Mine is:

Moto-apq8084-70:86 sha-88bfdfd 2015-04-06

And I am still running a very old version of your isu 1.3

With your original kernel patch you released
[Moto Maxx Android Development] fgl27:
that date it must be from Lollipop and probably is unaffected...

can you share the yours proc/cmdline?

like this

If you some day need to update radio.img try to do without changing the bootloader, if that fails them update only if you can't revert back to a old one...

Analyzing this new patches, unless google do big changes on security they will not find how to get the patch, because the only way to see is using ROOT or special system app privilege and I don't think they will add those to safety net as it need to run from user app, at least I hope they can't tired of have to find a fix, and Moto is not updating MM anymore (probably), but if they do I will stay of it :silly: because they will probably invent something else to block us...
[Moto Maxx Android Development] mrkhigh:
Is this all you need? I changed my serial number, hopefully that didn't affect you.

u0_a139@:/ $ su

root@:/ # cat proc/cmdline

console=null androidboot.hardware=qcom msm_rtb.filter=0x37 ehci-hcd.park=3 vmalloc=400M androidboot.selinux=permissive androidboot.bootdevice=msm_sdcc.1 androidboot.serialno=1234567890 androidboot.baseband=mdm androidboot.mode=normal androidboot.device=quark androidboot.hwrev=0x84A0 androidboot.radio=0x4 androidboot.powerup_reason=0x00100000 androidboot.bootreason=hardware_reset androidboot.write_protect=0 restart.download_mode=0 androidboot.fsg-id= androidboot.secure_hardware=1 androidboot.cid=0x2 mdss_mdp.panel=1:dsi:0:qcom,mdss_dsi_mot_smd_QHD_dualmipi0_cmd_v1 androidboot.bootloader=0x7086 androidboot.carrier= androidboot.hardware.sku=XT1254 androidboot.bl_state=2

root@:/ #
[Moto Maxx Android Development] fgl27:
yes that is all I need... indeed the "flag" androidboot.flash.locked is not there so is a new flag add by Moto for safety and others reason, I will test when I have some time if using old bootloader that disappears need to see if a old one will install over the new, maybe not...

:good:
[Moto Maxx Android Development] Marky__Mark:
You guys see Cynogenmod is done. No more development.
[Moto Maxx Android Development] mrkhigh:
It will live on as lineage os.

We're basically going back to the way things were a year or two ago.
[Moto Maxx Android Development] Marky__Mark:
Yea. Still kind of crazy.
[Moto Maxx Android Development] mrkhigh:
What was crazy was cyanogen going corporate without huge corporate backing. Of course they didn't take down Google.
[Moto Maxx Android Development] :
I noticed my backup account is not showing, how do I change this to another account, I can't find a way to change this.
[Moto Maxx Android Development] solidshree:
Hi OP, thanks a lot for a wonderful ROM, am using it as my daily driver, smooth with good battery too. Facing bit odd wifi behavior. My phone is leaving the wifi connection quite frequently even while keeping near the router. I tried everything like restarting my device, re - configuring the wifi connection and also checked in advanced settings, still the same issue. Should I try RR 7.0 naugat(is it stable enough) for a daily use .? and do I have to flash any radio stuff...?Pls advice..., keep up the good work.
[Moto Maxx Android Development] Marky__Mark:
The last CM 6.0.1 snapshot is the most stable rom ive had on this device. If bhb127 is interested in an RR update...
[Moto Maxx Android Development] fgl27:
Snapshot don't have all the update to the date, they have stable to the date with are basically the same on the latest RR I released.

I will released a new ROM in a week or two if it is stable there is very little changes but a lot to update as there is no more CyanogenMod and I have to switch all the repos to LineageOS and that consume a lot of time and internet things I don't have.
[Moto Maxx Android Development] BriCo84:
[MENTION=5747496]bhb27[/MENTION], let me know when you have the new zip ready to test VoLTE Advanced Calling
[Moto Maxx Android Development] ChazzMatt:
Speaking of VoLTE, [MENTION=5747496]bhb27[/MENTION], you've seen this page?

Besides this article, there's also specific ROM download patches on that page.

https://www.gizdev.com/enable-volte-android-n-roms/

This seems to be the XDA thread, but again also read the bottom of that article on the link above.

[UNIVERSAL]VoLTE Patch v2 for All Android N Roms [Updated: 2.1.17]

https://xdaforums.com/redmi-note-3/development/volte-patches-nougat-based-cm-roms-t3509257

Got it from this guy, posting in the Quark AOKP thread:

Yeah, I know this it the Marshmallow RR thread, but the topic is relevant for any non-carrier custom ROM. ;)
[Moto Maxx Android Development] gumbi2647:
Do you know if it works for RR v5.8.0
[Moto Maxx Android Development] ChazzMatt:
Several people said yes, like this guy:

I just went into the XDA thread and did a search for RR 5.8. It's other ROMs like AICP they had to figure out.

But whether it will work on all carriers, I don't know.
[Moto Maxx Android Development] johnjingle:
Ironically, I just posted this on NepoRood's AOKP thread yesterday. I tried it with his ROM and crDROID and couldn't get my phone to boot after applying the patches. I have an XT1254 on Verizon.

If you have any luck, let me know.
[Moto Maxx Android Development] ChazzMatt:
Yeah, I actually quoted your post and gave you credit for the find.
[Moto Maxx Android Development] fgl27:
You can try .zip made for other device but VoLTE is a very specific device thing, unless you use files made for quark it will never work, and odd behavior may happen.
[Moto Maxx Android Development] fgl27:
@ all my two cents about this volte is

For those that wanna VoLTE just keep posting on the right threads like [MENTION=2689772]johnjingle[/MENTION] did, post it here

https://xdaforums.com/droid-turbo/development

There is even some thread there that have VoLTE on the name unfortunately the ROM are not made by Custom ROM developers but are made by Moto and Moto doesn't help us to make Custom ROM or the developers of those thread.

I wish to see a thread there like this

Let's make VoLTE work on Custom ROM :victory::victory::victory:

Then call all of those guys that own a XT1254 and call themselves developer and put them to work on it.

But no, no one even wanna to try there, only that Brazilian dude that live so far from Verizon on a region of the world that LTE didn't even arrived...:silly:

After all VoLTE is possible but unless someone that owns a VoLTE capable device (XT1254) on a VoLTE capable carrier (Verizon) put they mind to make it work it will probably never happens, all those device that have it working have developers that are capable to test it so is way more easier to do...
[Moto Maxx Android Development] ChazzMatt:
I think people look to you [MENTION=5747496]bhb27[/MENTION] because you've accomplished so much, starting with official TWRP for our phones. Then a custom kernel. Several apps, like the Clean Flash Modem, which helped so many people with GPS issues when flashing other ROMs. That's just one, there's others.

The multiple ROMs you've maintained are just a baseline. You've gone above and beyond with the other stuff.

I guess people feel if anyone can figure it out, it would be you.

Take it as a compliment. ;)

______

VoLTE for me doesn't matter. I'm on prepaid AT&T on a non-AT&T phone. AT&T only give perks like VoLTE to "postpaid" customers with AT&T-branded phones.

But when on a phone call, I just drop down to HSPA temporarily, and still get simultaneous data + voice.
[Moto Maxx Android Development] ChazzMatt:
ANDROID PAY ON UNLOCKED BOOTLOADERS!

New development for unlocked bootloader, rooted users. Start with this post and go down.

Thanks to [MENTION=5901115]TheSt33v[/MENTION]!

https://xdaforums.com/showpost.php?p=70504607&postcount=4
[Moto Maxx Android Development] fgl27:
I don't think is need...

All my latest ROM's are patch with that already, when I released a NEW Marshmallow here will already have it builtin
[Moto Maxx Android Development] mrkhigh:
[MENTION=5747496]bhb27[/MENTION] is the one who pointed out the failure was in the bootloader, he then asked me to give him some information from my lollipop bootloader since it still worked.

Bhb has a patch that fixes the marshmallow bootloader. I wasn't aware so many people thought this was unattainable? Anybody who never flashed the marshmallow bootloader ( like me) and ran isu already knew safety net still worked and would have understood down grading was all that was needed. I will admit the only thread I am actively following is rr7.

But they isn't needed on bhb27s roms because he included the patch. Brute even realizing it still worked on lollipop.
[Moto Maxx Android Development] ChazzMatt:
Yes, but the mantra has been you can never downgrade Moto bootloader --,which now has been suddenly shown to be false. That is the shock. Even the guy who wrote the Droid Turbo bootloader unlock guide didn't know. I sure didn't.

It's only locked bootloader you can't download? Or will that be proven wrong too?

When people with unlocked bootloader want to downgrade to lower os (lollipop, even Kitkat), the one thing all of us stressed was be sure NOT flash lower bootloader. That can't be touched. And now it can? So, that is the big deal about all this.
[Moto Maxx Android Development] fgl27:
I have downgrade more then once always with bootloader downgrade... I have brick my device more then once and the only thing that really fix all is to flash stock 4.4.4 ROM all partition gpt, system, boot, logo, recovery, bootloader everything, then after a successful boot I upgrade back to latest Moto ROM all partition again, I did that more then once to solve some problem then I go back to Custom.

Like in those tutorial for downgrade I always use this

fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash motoboot bootloader.img
fastboot flash radio radio.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot erase cache
fastboot erase userdata
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot

Lollipop and kitkat have less parts for system so I use less "sparsechunk" on those

But I never try to locked the bootloader and then downgrade that may not be successful, but is possible to locked it after the downgrade of course in XT1225 as we have the unlocked key for those that don't I don't know how it is if those unlock hacks work again after...
[Moto Maxx Android Development] mrkhigh:
Again, didn't realize people thought that.
[Moto Maxx Android Development] ChazzMatt:
16th November 2016, 01:37 PM

[MENTION=5747496]bhb27[/MENTION], you gave me an XT1225 TWRP-flashable radio back in November. I now see you have another XT1225 TWRP-flashable radio in your inventory. I think I know the difference, but I'm asking anyway... I remember something about some minor Marshmallow update Motorola pushed out a while back, which at the time made your kernel incompatible with stock Marshmallow released back in July 2016?

MPG24.107-70.2 (July 2016 Marshmallow release)

[*]MPGS24.107-70.2 (minor December 2016 update)

You even requested Motorola release sources on that newer kernel... which they have NOT yet done.

Kernel Relseased request for latest Quark Moto Maxx (MPGS24.107-70.2-2)

bhb27 opened this issue on Dec 6, 2016

https://github.com/MotorolaMobilityLLC/kernel-msm/issues/96

_________

Anway, this newer radio seems to be from that update?

Have you noticed any quality difference between the two radio/modems? Is it safe for me to flash? I'm also curious why the file size of the newest radio is so different.

Radio_Flasher_Stock_MPG24.107-70.2_XT1225.zip

38.5MB Nov 16, 2016 | 06:35PM

https://www.androidfilehost.com/?fid=313042859668275536

Radio_Flasher_Stock_MPGS24.107-70.2-2.zip

43MB Dec 13, 2016 | 06:07PM

https://www.androidfilehost.com/?fid=457095661767122577
[Moto Maxx Android Development] kitcostantino:
okay, i cant be the only one here like wth? So....this means that pretty much, as ive always believed, there is a reset fxz for each device (perhaps device tree is a better way to say it considering i bet it applies to Obake and other Motos as well. if anyone has a means to confirm/deny maintance firmware by SU (system update) version, im all ears. i have always maintained it would be ludicrous for Moto to leave themselves no way to go back when fixing devices.

Maybe i am getting this info wrong, [MENTION=5747496]bhb27[/MENTION] . you are saying with your xt1225 you have been able to reverse software version and boot loader version by simply flashing the Kit Kat FXZ? or did you have to wait until you bricked, (qualcomm brick recovery state, i.e.- qhusb mode, etc) and then use the KK fxz to recover? thank you all for what you do.
[Moto Maxx Android Development] fgl27:
I have being using MPGS24.107-70.2-2.zip sense it came out, I did not notice difference or problems is 100%, there is minor updates on that September security patch from Moto so they must have made improves, XT1254 users that update from Lollipop radio to Marshmallow have improves also but that is expected...

I can downgrade any moment, to any version at least I have done it, and to make things easier I have TWRP backups of it OS version just in case I need to test, because the downgrade some times fails via cmdline but the TWRP restore doesn't...

To it not fails I must do this via cmdline... From any version I'm that is newer then the old I wanna to use I flash first KK, then let it boot and ask to revert the sensors firmware and etc, then I flash wherever OS I wanna, this way in the flashing of the files I get always the okay for all partition and it always boot OK, if I try to go back straight to the OS I wanna I get some times errors in bootloader or gpt partitions and it doesn't boots.

I have downgrade many times I only use the cmds + the stock xml.zip or TWRP backups nothing else and some times I only did to test something the device was fine some times it had some problem with partitions or related...

:good:
[Moto Maxx Android Development] kitcostantino:
that is awesome.
[Moto Maxx Android Development] fgl27:
ROM update! ResurrectionRemix-M-v5.7.4-20170117-quark.zip​

Download-ROM

Device Changelog

Source Changelog

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).

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] dwh2o13:
Great timing here with the new update. I've been running RR 5.1.1 and really like it, but have wanted to move into a Marshmallow build for some time now. I haven't really moved around to much with ROM's. I went straight from stock(xt1254 SU4TL-44) to root to RR 5.1.1 so I want to make sure I install correctly. Is there anything to really make sure I do moving from a Lollipop ROM to a Marshmallow version? I always do a clean install, but didn't know if anything other than the ROM and gapps need to be included. Thanks for the great work.

Specific Questions:

1. Open gapps or Banks?

2. when performing wipe in twrp, can I just do factory data reset, or go into advanced and select cache, dalvic cache, system, and data?
[Moto Maxx Android Development] solidshree:
Hi BHB27, was very excited with the new update but had to roll back to the previous version as I lost the cellular service connection, my couldn't detect my sim.
[Moto Maxx Android Development] ChazzMatt:
WRONG THREAD?

EDIT: Everyone ignore this report, please. [MENTION=4460432]solidshree[/MENTION], did you post in the wrong thread? You also posted identical comments in the Nougat RR thread. Until you confirm otherwise, I doubt you flashed both Marshmallow and Nougat ROMs at the same time?

__________

Mine works fine on this RR MARSHMALLOW update. I'm on XT1225 (AT&T). What model Quark and carrier are you using? Also you sure you flashed the Marshmallow RR update?

I also flash [MENTION=5747496]bhb27[/MENTION] Clean Modem Status file as part of any ROM update, along with GAPPS and SuperSu. In TWRP you can stack up to 10 events to flash in successive order.
[Moto Maxx Android Development] kitcostantino:
1) open is what i use bc they are updated frequently

2) the latter is what i wipe. dalvik cache, cache, data, system when updating android version, like RR LP to RR MM.

If its just a new version of the same, in example, RR MM v88 to RR MM v99, i wipe cache and dalvik cache, but nothing else. I do the same for kernel updates, just caches.

it is pretty much the same as Lolipop as far as the flashing process is concerned. Also, if you dont have it on your sd card already, download bhb27's clear modem status zip, just in case. my radio (Droid Turbo xt1254) glitches out often when i flash a new rom and that zip makes gps and radio work perfectly for me.

Happy Flashing. :)
[Moto Maxx Android Development] Guth13:
Thank you very much..

I'm send for you the app contacts from cyanogenmod (nexus 5 hammerhead). Can you replace the app contacts that you use from google?

Which kernel do you recommend use with Resurrection Remix M 5.7.4? BHB27-Kernel-V36.zip or BHB27-Kernel-V202-4-M.zip ??
[Moto Maxx Android Development] ChazzMatt:
I just use the kernel that comes with the ROM. I have used [MENTION=5747496]bhb27[/MENTION] kernel in the past, and I admire him as a developer -- but currently I just use the "stock" kernel in RR ROM. I do use Kernel Auditor to set different governors and options.

Others can give you their preferences.
[Moto Maxx Android Development] fgl27:
Way I need to replace the app? I can build the cm contacts app, I don't because it has a major wakelock problem is random and can cause a battery to discharge very fast.

Use the wherever kernel you prefer is all stable, I only support and test the last V.
[Moto Maxx Android Development] fgl27:
There is a minor problem with some CDMA devices on all latest ROM I released yesterday, I'm aware of that is a simple fix but demands a NEW build, as XT1225 is a GSM device I was unable to prevent or see that before releasing it there is no way to me to test it, and it will only affect some VZW/XT1254 users.

Test next V let me know.
[Moto Maxx Android Development] Guth13:
It's for do not update de app contact. The app contact from google always will go update..

I I always replace it when I flash the ROM and it works normally.

But some customizations do not work even by installing only rom and gapp.

Then I flash only the ROM set and then I make wipe caches and install the remaining ".zip" s.

Is it normal for ROM to load slowly ?? Never exceeds 1200 mA.
[Moto Maxx Android Development] fgl27:
I don't understand? what do you mean?
[Moto Maxx Android Development] Guth13:
Que o aplicativo da google vai atualizar sempre.. Eu gosto de evitar de atualizar os aplicativos do sistema personalizado como a RR..

E normal a rom carregar lentamente mesmo no carregador turbo? Nunca passa de 1200mA..

Algum tempo atras fiz um logcat porem esta com xposed.. Espero que isso nao interfira e ajude-o..
[Moto Maxx Android Development] ChazzMatt:
My Google Contacts is updated to latest version. Are you saying it doesn't update?

View attachment 4007915
[Moto Maxx Android Development] fgl27:
Just because you don't like app to get update everyone should have a app that has a problem and will never be update?

Makes no sense if you have a way to fix your problem use but don't ask to create a new one to everyone.

I don't know were you are looking for charging the only way to get the correct value is on the Power and Battery section of KA app, my goes up to 2400mA, when the charge gets close to 80 or 90% the charging rate is lowered automatic so the device can reach 100% (just like any other modern battery).
[Moto Maxx Android Development] ChazzMatt:
Right. I want the latest update.

If I don't, I turn off auto update in Google Play and/or install older version.

For awhile I turned off auto update on Google Search as the newest one broke the Google Assistant xposed module. (Now been fixed.) But I wouldn't ask that be done for everyone!

View attachment 4007928
[Moto Maxx Android Development] dwh2o13:
Are you recommending VZW/XT1254 users wait for the next build, or is this more of an isolated case affecting very few VZW/XT1254 users? Love your RR LP version which I've been running for awhile now. Thanks so much
[Moto Maxx Android Development] aka848:
Has anyone else encountered this bug in the latest build? Hoping it is not hardware.

The screen works fine if I turn the screen off and back on.
[Moto Maxx Android Development] ChazzMatt:
Clean install or dirty install?
[Moto Maxx Android Development] aka848:
Dirty flash. I just realized I posted in 6.x.x I'm on the 7.x.x release.
[Moto Maxx Android Development] ChazzMatt:
Someone else did that too. ;)

You can copy and paste your post over to that thread, then edit this one to remove the information. Just so it doesn't confuse people.