yashsingh1/xdaforums huggingface dataset:
[X Style (Pure) General] mddunner:
I have a bit of an odd question. What is required to restore a stock nougat backup from TWRP? I installed stock nougat via these steps with no issues, installed TWRP, then backed up the installation. however, when I tried to restore the stock nougat backup, I boot looped. Do I also need to restore stock recovery to load the nougat backup? Thanks!
[X Style (Pure) General] stevejohnson42:
Second edit - fixed so showing certified :

Ideas came from here - but I modified:

https://android-fix.com/google-play-problems/59-device-is-not-certified-by-google.html

1. ; Magisk installed

2. Settings => Application Manager

Clear all data for Google Play Store and Google Play services

3. Go to TWRP

Wipe ( Advanced Wipe) => Cache and Davlik Cache

Reboot device and run Google Play Store --

Go into settings and check the Certification staus

Edit ; ok ; reality is -a basic screwup on my part - I must not have locked bootloader like I thought ; went back to bootloader screen - noted "unlocked" - installed TWRP and rooted ; still shows uncertified ; but suspect it is because I logged into Google without Magisk and an unlocked bootloader. I can used APKPure for now and side load those apps that won't appear in Playstore because of the status

======== original observations / question ==== solved ============

Well I may be screwed with experimenting,

Loaded stock per instructions here...no issues..for the first time this round did without locking boot loader..comes up as uncertified

Started over....this time I used flashboot and installed twrp prior to doing a reboot...rebooted into recovery and flashed Magisk...no issues..Play Store shows certified..all good until I took the update and boots back to twrp..no surprise...wants stock recovery

So started again only this time relocked bootloader ...no root, no twrp...but play store shoows uncertified..took update ...no issues...set up

Went to developer option ...the line to allow unlocking bootloader is greyed out...stuck...never saw that happen before

Any ideas. ? at moment stuck on stock that Google sees as uncertified and not able to unlock bootloader...would like to put twrp and root again
[X Style (Pure) General] acejavelin:
Unfortunately, we have this happen... Unlock, then relock, and it's just gets stuck locked and you can't unlock again.

Try unlocking with the code anyway... If that fails, try a factory reset in stock recovery, then see if the OEM unlocking option is available. If not, your kinda screwed. :(
[X Style (Pure) General] stevejohnson42:
thanks - in the original post - which was a bit convoluted - figured out ; dang - I really didn't lock it ; installed TWRP, Magisk , then cleared data on the Google play store and something else ( in original post ) - rebooted and all good ; shows as Certified - and , at the moment , on rooted stock

thanks for you inputs --
[X Style (Pure) General] mddunner:
So my current state is:

stock nougat, per this guide

bootloader unlocked

TWRP flashed

Magisk Installed

At this point, can I simply lock the bootloader and clear data on google play store? Thanks for all your detailed info.
[X Style (Pure) General] stevejohnson42:
I never relocked bootloader -- my steps at this point ( you already have done (1) --

Ideas came from here - but I modified:

https://android-fix.com/google-play-...by-google.html

1. ; Magisk installed

2. Settings => Application Manager

Clear all data for Google Play Store and Google Play services

3. Go to TWRP

Wipe ( Advanced Wipe) => Cache and Davlik Cache

Reboot device

To verify :

run Google Play Store --

Go into those settings and check the Certification status; should be "certified "
[X Style (Pure) General] mddunner:
Right on - I misunderstood about re-locking the bootloader. I should have known that Magisk could hide that for us.

I performed the rest of your steps, and my device also shows Certified. Thanks again for sharing your experience and procedure. :good:
[X Style (Pure) General] ShapeShifter499:
I have -23 installed on my phone but I want to reflash everything. Is there a way to reflash and keep -23? Can I flash an older build before the OTA to 23? I have some magisk mods with some other root mods and things seem wonky, I would like just to redo everything. I have T-Mobile so I'd like to keep -23 for that reason.
[X Style (Pure) General] ResistanceIsFutile:
This goes out to anyone knowledgeable - thanks ahead of time !

OP gives the file CLARK_RETUS_7.0_NPH25.200-22_cid9_subsidy-DEFAULT_CFC.xml.zip

In the quote above it states 22 is the Sprint version and 23 is everything else, ok...

But the MXP phone is unlocked and an EVERYTHING or every network phone isn't it ? "both work fine regardless of service provider."

My question is about some images or downloads I've ran across, we're talking about Nougat and there are some DL's being mentioned (in the link) about MM, so omit and disregard those - OK.

So we're all on same page as being Nougat firmware here.

Whats the difference between- a file stating NPH25 and one stating NPHS25 ?

ANYONE KNOW...? Especially OP author [MENTION=2001582]acejavelin[/MENTION]

I'm not sure if XDA will post my link above (in the link) and I'm not trying to disrespect their policy.

I don't know if their valid OS images and being to big for VirusTotal to check - so use care till we know.

I'm only trying to see if these are valid firmware downloads we all could benefit from.

Then to- what are the answers to my questions in pink.

Thank you.

EDITED :)
[X Style (Pure) General] ResistanceIsFutile:
OP file worked in this case

^ Edited above quote for length ^.

[MENTION=8959745]MotoDudeX[/MENTION] did it help to reflash all radio image files as [MENTION=2001582]acejavelin[/MENTION] suggested ?

I'm a NucleaROM user too and for months I've had no problems with calls and texts in network problems. Presently holding a connection to the network has been impossible on Sprint .

I'm just wondering if flashing any and all radio image files helped you MotoDudeX or possibly it's being a mismatch between the kernel used in LOS custom roms and the radio in our MXP's ?

I'm lost I'll admit it after months of no connections problems at all of the Sprint network and now facing them daily to any connectivity.

So I'm stumped as well here.

Thank you

EDITED

Nothing I've tried works - 1. Carrier Reset, 2. Profile Update, 3. PRL Update, 4. *#*#4636#*#* - changed the band to United States, 5. Twrp restore...

Solution

The only fix I've found seems to be ADB/Fastboot flashing back to stock Nougat NPH25.200-22 image from OP.

I chose the complete flash and not just the radio image files (modem stack) to use.

I don't understand the why but the fact it's happened all three times with the NucleaROM in doing the *#*#4636#*#* on Sprint and thereafter it trashes my network connectivity. I've flashed the OP's stock Nougat NPH25.200-22 image three times and come to pin point the hidden code in changing the band to US was my cause to loose calls and SMS ability.

Who knows of what mods in the Lineage OS was already made before the NucleaROM came to being based on it - in turn of making changes to the kernel and/or modem from the stock Nougat which may have caused a mismatch in some way - minor but enough to affect phones on the CDMA networks... If indeed it's not having to do with a custom ROM covering different devices (1572-1575) which have different network bands and frequencies and/or radios to them.

This solution worked when using a custom rom by restoring device back to the stock Nougat OS and getting networks ability again, then proceeding to flashing the custom rom and having my network continue working. Updated; Thanks acejavelin
[X Style (Pure) General] Bill720:
It makes little sense, but that's how it is

This is correct. Both Roms are compatible with all service providers. To reiterate what was said before, there are no known differences (at this time) between 22 and 23, other than that people with Sprint Sim cards started receiving one build through the automated update utility and people with all other Sim cards started receiving the other.
[X Style (Pure) General] ResistanceIsFutile:
Hi and thanks for that info.

One fact on Sprint with the 22 through the (OTA) automated update utility is there are no APN settings made available to the user - more > Cellular networks... I don't have any APN menu or options for a menu on the stock nougat and even to flashing the the OP file here of 22.

Can't speak for others on different networks and knowing if 23 shows an APN menu to them. Would be nice to know and if pulling out a Sprint SIM and doing the 23 Rom would give that APN menu to me.

So unlike the NucleaROM where I had that APN menu with 13 populated APN's listed. Of course it's LOS based but still a Android version 7.1.2_r29.

I had linked to a 23 file earlier as it's said we don't have one yet and in wondering if it would be a good source and valid file to consider?

As I stated earlier "on NucleaROM and for months I've had no problems with calls and texts in network problems" - only my phone number wasn't shown in SIM status, I believe I've pin pointed the problem after months and no problems in before I've made this one change.

I've replicated this three times now to confirm it, I was concerned in seeing the x by the signal wedge with my MXP phone on the NucleaROM as well.

That x stems from my having cellular data turned off - phone number problem still exists in using the NucleaROM.

Read that a *#*#4636#*#* - changing the band to United States might help but, in my case that's where I lost all network contact used with Sprint. Don't understand the why but the fact it's happened all three times with the NucleaROM in doing the *#*#4636#*#* on Sprint and the only fix seems to be ADB/Fastboot flashing the OP's NPH25.200-22. I chose the complete flash and not just the radio image files (modem stack) to use.

A TWRP restore of stock Nougat didn't help as I've seen "if you have in any way modified the partitions that twrp does not backup. For example lineage has a nasty habit of messing with partitions that twrp does not backup..that is why this guide has you flashing original firmware in fastboot vs using a backup that may or may not fix all partitions."

https://xdaforums.com/showpost.php?p=74079560&postcount=441

Tried it and TWRP loops - doesn't go to system, TWRP shut down phone and start up brings you back to recovery again - only when off and going to bootloader can I get into system. So if it's something of LOS writing to unbacked up partitions indeed that's nasty...

No my phone number still doesn't show on NucleaROM, but calls and SMS do work now on the Sprint network and I have cellular data still turned off.

See the screenshots (below) of before in using the NucleaROM where Sprint is recognized as 31000 and the x by the signal wedge #1 & #2 - then latter #3 & #4 SS in the results of doing the *#*#4636#*#* and last #5 SS of NucleaROM APN menu with populated APN's that SS captured.

Thanks for your answers and any thoughts.
[X Style (Pure) General] br0adband:
I purchased a Moto X Pure XT1575 off craigslist yesterday, had some screen issues (black/white spots in one corner but no damage to the glass), and of course it has Google FRP locked down (I presumed I'd be able to get past that at a later time). During my attempts using some methods from YouTube videos I was able to get into Settings - About phone and discovered it has Android 7.0.0 on it (I didn't bother to look at the actual build number, sadly).

And of course, during my attempts to bypass the FRP (multiple methods) the backlight went out completely so I ordered a new display assembly from an eBay reseller, that will probably be here next week. Also ordered a new battery since the whole reason the previous owner was selling it (at least this is what he said) was that it wouldn't work off the charger and of course it didn't, dying within 30 seconds each time it was disconnected from a charger even though the battery status said it was 95% charged.

So while I'm waiting for all those parts to come in I'm doing the typical research into things, here's my question about this ROM featured in the OP in this thread:

Is the ROM in the OP Android 7.0.0, and any OTAs bump it to 7.1 or whatever? I can't seem to find that info anywhere so far and I just wanted to confirm that aspect as I will more than likely do a clean flash of the ROM in the OP when I get it up and running again and then start from there. It's frustrating seeing all the FRP methods fail to do what they seem to do so easily on other devices even considering this device I now have has 7.0.0 on it. I was hoping MotoReaper could help but it seems RootJunky has gone 'commercial' and wants a crazy bit of cash for that tool I'd only need to use one time, so that's a foregone conclusion.

But if anyone could tell me the version number I'd have after flashing the ROM in the OP I'd be grateful. I'm guessing OTAs bump the version as they're released (no idea what the most current one actually is) and I would love to get LineageOS on the device obviously, just not interested in bricking it at all of course.

And with the research I'm doing so far I presume the info that flashing back to stock 6.0 is not a possibility since the stock 7.0.0 is already on the device, so there goes that idea.

Any info is greatly appreciated, thanks.

EDIT:

Just noticed in post #63 in this thread acejavelin stating that FRP cannot be bypassed on any MXPE after the February 2016 update - is that actually true, and this device is basically useless for me now and there is absolutely no possible way to get past FRP on it? Yes, I realize I'm an idiot for not checking on that aspect during the purchase, and the previous owner of course offered me some BS excuse for not wanting to return to log in then let me delete his Gmail account on the device.

But damn, if it's absolutely 100% impossible to get past the FRP now, well, guess I won't be needing the spare parts, if someone can or could confirm that ASAP I'd appreciate knowing that too.
[X Style (Pure) General] acejavelin:
That's what FRP is for... To prevent unauthorized access to the device. What good would it be if you can just bypass it? The answer is no, currently we have no way of bypassing it short of replacement of the mainboard, and at that point it's a different device anyway.

FRP has some bypasses... On specific devices and Software versions, but manufacturers are usually pretty quick at patching FRP security holes.
[X Style (Pure) General] Fobos531:
Moderator information

Please remember to stay on-topic. Don't discuss FRP into too much detail in this topic as it's not a FRP discussion thread, but rather a stock firmware thread. Thread cleaned.

As per rule #15:

Whilst a minor amount of off-topic posting may be overlooked, the general rule is that your posts / threads must be relevant to the Forum / thread in which you are posting.

Thanks.
[X Style (Pure) General] Bill720:
Could get away, but maybe not

It depends on how many times you breach that back cover. I've found that, (if disassembly is done properly) one can probably get there once or twice without destroying the back cover or adhesive beyond repair. If you buy a good battery, I'd recommend just grabbing an extra pad of adhesive to be on the safe side.

That said, after having broken into the device 3 times now, I did need to replace both. I'm not as happy with the replacement back cover as I am with the original, but perhaps it just needs to be broken in.
[X Style (Pure) General] br0adband:
Stock NPHS25.200-22-1 and NPHS25.200-23-1 ROMs

MotoReaper took care of the FRP issue with the XT1575 I recently purchased off craigslist, no issues, no problems. I decided to toy around with LineageOS but because I installed the latest stock ROM directly (which I'll link to below) of course the 14.1 build won't work so I decided to give Hashbang's 15.1 unofficial LOS a shot and wasn't too happy with it (new build posted just a few days ago on July 9th, had some issues I couldn't work with) so now I'm back to pure stock NPHS25.200-23-1.

I was able to locate both stock ROMs and didn't see them posted here at all in any thread anywhere so, I tossed them both up on Mega if anyone finds themselves in a situation where they could prove useful. As I understand it, NPHS25.200-22-1 was the minimum build for any carrier usage either CDMA or GSM, but NPHS25.200-23-1 was more for GSM use. I cannot verify that, it's just something I saw mentioned on another forum that one user pointed out. What I can say for sure is that there are differences in the checksums of the system.img_sparsechunk files and some others as well included in these ROMs so there are differences in there somewhere.

Regardless, here are NPHS25.200-22-1 and NPHS25.200-23-1 stock ROMs if anyone happens to need them so you won't have to deal with or wait for any OTA updates to patch things along the way - considering they still leave the MXPE with the October 1 2017 security patch, I think it's fairly safe to say Lenovo will never release another update for this device and if they do it'll be a small miracle at this point.

NOTE: THESE ARE FOR THE XT1575 ONLY AS I UNDERSTAND IT, I have no way of verifying if they'd be functional on the XT1572 model (Style), so be aware of this fact. I own an XT1575 and I cannot say if these will work on the XT1572 - it's sufficiently say to say "Nope, they are for the XT1575 only..." and be done with it.

CLARK_RETUS_7.0_NPHS25.200-22-1_cid9_subsidy-DEFAULT_CFC.xml.zip

1.39 GB (1,498,747,048 bytes)

SHA1: f6b571435ec158c198990b4a2cdc1124c60de272

flashfile.xml = <software_version version="clark_retus-user 7.0 NPHS25.200-22-1 1 release-keysM8992_1255331.29.01.88.09R"/>

https://mega.nz/#!ZJkkRayT!GkoftKp8J1A3go7Wif0_a8kVI7A6FQBeqmuwk6UKD3s

CLARK_RETUS_7.0_NPHS25.200-23-1_cid9_subsidy-DEFAULT_CFC.xml.zip

1.39 GB (1,498,747,731 bytes)

SHA1: feccf2c71bb5d55cb5405e5698053f6c7332eb13

flashfile.xml = <software_version version="clark_retus-user 7.0 NPHS25.200-23-1 1 release-keysM8992_1255331.29.01.88.09R"/>

https://mega.nz/#!xUsiXI6C!cAyj2HZgoyxUIcnhNtso7nw6lo-0qKeJnmGoNaHQrec
[X Style (Pure) General] ResistanceIsFutile:
Really ?

What about my post #222 (in the link).

Real credit as I find goes to [MENTION=8757735]zi_mo[/MENTION] of the thread created 18th January 2018 found in moto-x-style/general topics.

In the link there of https://yadi.sk/d/MCliEyCPfj7ZZ/MOTO.X3/Style/XT1575/US which at some point updated to offer NPHS25.200-23-1 version.

I only posted my link to seek users input of their being valid official full firmware downloads that we all could benefit from. Not as to some being mere combinations, in addition to OTA's as Security patches added to them - then a dump taken to get the result of a file with NPHS.

That would make since as the "CLARK_RETUS" being the biggest clue ending with "US" and having a connection to the US Pure model (XT1575) of the Moto X.

Then it would be a need to see "CLARK_RETASIA" or "CLARK _RETEU" for the Moto X Style model variants as same logic - to a related file used.

So are any links other than the ones posted by the "Motorola-Firmware-Team on Android File Host" being

OFFICIAL Full Stock ROMs

and to be used ?

I can't say, as I don't see any firmware images offered by "Motorola-Firmware-Team on Android File Host" covered to include any released Security patched version(s) - is there a reason for this ? Does the Security Patch updates need to come from the OTA's system

ONLY !

Especially to insure release keys and every value on device is correct before hand - to add only the correct differential files patch. . .

My original question remains:

Whats the difference between- a Motorola firmware file stating NPH and one stated as NPHS ?

A logical guess would be, only of the added "S" has a meaning to include the latest released Security patch since the prior's Motorola's firmware versions release. I'm guessing for sure - but is it logical to assume this ? Is any Motorola file with NPHS for our Moto X Pure safe to use? Then why are they not found by and offered by the Motorola-Firmware-Team.

UPDATE:

08-06-2018

I've seen acejavelin mentioning this in another Thread-

"Moto OTA's are differential files, so each piece for each file only includes what is different than the known value from the previous build, that is why these OTA's are so dangerous, they do not replace the entire file but patch existing ones with the specific bits that are different only... if it fails or the files are not as expected bad things can and will happen.

BTW, the information to decipher what build you have to be on and what it will go to is inside the OTA zip file, in a file called metadata.json

Your device MUST have the correct values and release keys for it to work."

I'm a noob it's true, but I search and click on links and read to know in what facts I've posted about... If not at first, I don't fully understand it all - I'm always open to an edit of any post I've made.

No disrespect is ever meant to my fellow XDA members - that's not my ground I stand on.

Facts based in written texts only and I hope you'll agree ;)
[X Style (Pure) General] br0adband:
OK, so I didn't SEE those firmware builds, probably because you provided a link to another site where the files happened to be - when I searched for the build numbers I found nothing because you didn't post them by the build numbers, just the link to the other site.

No harm, no foul, nobody is hurt over this, as for credit I don't care at all about such things, I just provided a somewhat easier one-click solution to get the builds if people want 'em.

Geez... really?!?! :confused::p
[X Style (Pure) General] br0adband:
I've used both ROMs, they install without issues - I would not have posted them if that were not the case, which was a presumption but apparently some folks just don't have that level of comprehension and I understand there's a language barrier happening at this point.

Suffice to say, use the firmware, don't use the firmware, whatever.

"And that's all I'm gonna say about that..."
[X Style (Pure) General] ResistanceIsFutile:
I see [MENTION=907867]br0adband[/MENTION] in your assumption for others belief on your reasonable grounds without giving any evidence.

Only answering #1 of the 8 questions, basically going with ""trust me" - "I've use these files".

Without any factual evidence in pro's or con's that inclines the mind to believe or trust but, at the same time leaves to much room for doubt in having more evidence against these downloads than for them as to trust - as it's a gamble we're left with.

The inexperienced user is even gambling for help from you if needed to a helpful understanding in how to proceed - should they have a bad flash.

Nothing defeats the powers of comprehension like the deliberate harm one's left in without using logical reasoning of investigating the principles governing correct and true or a reliable inference by a factual process restricted to the facts at hand.

Thanks but no thanks for your downloads - not enough facts to warrant using them.