yashsingh1/xdaforums huggingface dataset:
[X Style (Pure) Q&A, Help & Troubleshooting] xdafan15:
If some of the more experienced people here could check my steps for returning to stock, I'd really appreciate it. I have some questions and also want to confirm that I correctly understand how to do some of the others. Thanks.

My XT-1575 is running 6.0 build number MPHS24-49-18-16. I would like to change ROMs (probably to Lineage OS 14.1) but be able to return to the same build at a later time. I do not want to update the Moto firmware to 7.0.

Steps:

1) Use the instructions in the thread: [GUIDE] [XT1575] Return to stock and relock bootloader by [MENTION=2001582]acejavelin[/MENTION]

2) Download the latest 6.0 factory image available (MPHS24.49-18-8) with the link in the thread and place it in the adb platform-tools directory

3) Open a command prompt in the platform-tools directory and issue the commands listed in the thread to flash the firmware. This will not lock the bootloader because this is an earlier build.

4) As shown in the thread, go to [MENTION=4795150]annoyingduck[/MENTION]'s post (post #366) to get the OTA .zip to go from 18-8 to 18-16

5) This needs to be sideloaded.Is TWRP used for this? Will TWRP still be in recovery after running the commands in step 3? Do I need to flash TWRP to recovery? When I flash the OTA, will this replace TWRP with the stock recovery?

6) Is there an additional step(s) to lock the bootloader? The instructions say flashing an older build will fail at locking the bootloader. Instead, the OTA is flashed manually, but how does the bootloader get relocked?

7) Are there any additional steps to return to official status to pass safetynet and get OTAs?
[X Style (Pure) Q&A, Help & Troubleshooting] acejavelin:
All of these questions are answered in the threads you referenced...

1) Yup, that's fine.

2) Same, remember to extract it... Although I would recommend extracting it to a unique directory and add platform-tools to your path

3) Correct, sort of... You cannot use an older firmware to lock, but there are specific commands to attempt a lock and to just flash. When downgrading be aware gpt.bin (partition table) and bootloader.img may fail and that is normal.

4) Yup, good there

5) Sideload in this regard is accomplished through stock recovery, start stock recovery and select "Apply update from ADB" then execute "adb sideload update.zip"

6) Your only option at this time to lock the bootloader is to flash a Nougat firmware image... We do not have a Marshmallow 18-16 image and without one you cannot lock the bootloader, no matter how much you downgrade.

7) "Official" status is not required to pass SafetyNet API check on Marshmallow or Nougat, but you must have a purely stock /boot, /recovery, and /system partition. On Nougat you must also have a locked bootloader. The only way to get back to "Official" status is to flash an official firmware image and then take an official OTA successfully.
[X Style (Pure) Q&A, Help & Troubleshooting] xdafan15:
Thanks for your help, [MENTION=2001582]acejavelin[/MENTION]! Some further clarifying questions-

I assumed I would just copy and paste the commands you provided exactly as listed. Is that OK? Or do I need to substitute the commands you showed at the bottom:

fastboot oem fb_mode_set instead of fastboot oem lock begin

fastboot oem fb_mode_clear instead of fastboot oem lock

Or it doesn't matter?

And the way to do this is to flash NPH25.200-22 from adb fastboot as shown in your other thread, correct? Can I also take the Moto OTA from 18-16 (the one I am currently being offered)?

So you are saying that if I follow the instructions to return to 18-16 I will be able to recieve OTAs and will pass safetynet. Only downside is that my bootloader will remain unlocked?

By flashing the Nougat image, my bootloader can be locked (part of the sequence of commands)

but only by doing this plus accepting a future OTA will the status return to "official"?

[/QUOTE]
[X Style (Pure) Q&A, Help & Troubleshooting] acejavelin:
Using the 'oem lock' commands will fail, and it will get stuck in fb_mode that you have to clear. Better to just use the fb_mode commands up front.

Guess I am confused... if you flash NPH25.200-22 you won't be offered 18-16 OTA, but will likely be offered the NPHS25-201.1 update. If you are on 18-8 and are pure stock you can accept the 18-16 update, and within 24 hours after that is successfully applied you should be offered the Nougat update(s).

You can chose whether to lock the bootloader or not by flashing the Nougat image, the question is which do you want? Just flashing an image won't make your software status "official" in most cases. We have seen some cases where it does, but we don't know why and in most cases it will stay unofficial until you accept an OTA update, then somehow it miraculously becomes official. The key to remember here is once you accept an OTA that is a higher version than the stock images we have, you have no way to lock the bootloader, so if you want to lock your bootloader in your current state the only possible way is to flash the NPH25.200-22 image using the locking commands, because if you don't lock at this point and accept an OTA update you cannot relock the bootloader until (or if) we get a newer factory image.

One more thing to keep in mind, if you accept an OTA to Nougat or manually upgrade, and decide to downgrade to Marshmallow, it is possible, but once this is done do NOT accept any OTA updates back to Nougat, it will hard brick... and I mean perma-brick such that a mainboard replacement is necessary to fix it, which Moto won't do because you unlocked the bootloader, so basically the phone is trash.
[X Style (Pure) Q&A, Help & Troubleshooting] xdafan15:
[MENTION=2001582]acejavelin[/MENTION], thanks again and sorry for asking so many questions. For those of us who only play around at this stuff, it is hard to keep this all in our heads. Especially since a wrong move can hard brick the phone as you mentioned.

Interesting- You say if I return to stock 18-8, Moto will offer me the 18-16 OTA first, I won't be offered Nougat directly?

Since I would want to relock the bootloader, is there any reason not to just go directly from Lineage OS to NPH25.200-22?

The string of commands to issue (shown in the "return to stock" thread) is the same whether it is a MM or Nougat image that is being flashed, correct?

If I downgrade to MM and then flash the NPH25.200-22 image, at that point is it again OK to take an OTA to NPHS25-201.1 with causing problems?

Does it matter if the Nougat version I was originally on before downgrading was 200-22 vs 201.1?

Thanks again!
[X Style (Pure) Q&A, Help & Troubleshooting] acejavelin:
Yes

No

Yes, except watch the number of sparse chunks

Yes, as long as you flash the full image and not as an OTA.

No

I guess this conversation is going all over the place... are you wanting to return to stock and lock the bootloader or run a custom ROM? You can't really do both. :) If you want to return to stock, that depends on your current version, if you want to run custom there are less constraints. This is a 2 year old device, just pick one and go with it. ;)
[X Style (Pure) Q&A, Help & Troubleshooting] xdafan15:
Thanks for your patience with me, [MENTION=2001582]acejavelin[/MENTION].

My intent is to switch to Lineage OS now, but make sure I understand the correct steps to return to stock in the future if I want to. I wanted to confirm that info before everyone is gone from the Moto X Pure forum. I tend to keep my phones for a long time.

I think I've got it now, but I do want to ask 1 more clarifying question:

I asked "If I downgrade to MM and then flash the NPH25.200-22 image, at that point is it again OK to take an OTA to NPHS25-201.1 with causing problems?"

and you answered

"Yes, as long as you flash the full image and not as an OTA."

Do you mean

(A) as long as I flash the full 25.200-22 image and then take the OTA (which motorola will offer to me at that point to get to 25-201.1),

OR

(B) did you mean after flashing the image to get to 25.200-22, I cannot take the OTA to 25-201.1, but must wait until (if) someone posts the image file for 25-201.1 and flash that?

Sorry for asking so many questions. I really appreciate it
[X Style (Pure) Q&A, Help & Troubleshooting] acejavelin:
Honestly, the smart bet would be to flash the NPH25.200-22 image, then do NOT take any OTA. Then go ahead and flash TWRP and LineageOS. You can always go back to the full image without issues of "downgrading".

At this time the 25.200-22 image is the newest we have and downgrading can never be perfect. If there is no reason to take the OTA (like you are going to just flash Lineage anyway), then don't take it... At least you have an easy out.

The main reason for this is we don't have an image for 25-201.2 and we don't know when, or even if, we ever will. For example, we never did get an image of Marshmallow 18-16 and at this point I doubt we ever will.
[X Style (Pure) Q&A, Help & Troubleshooting] xdafan15:
Thanks for the excellent support, [MENTION=2001582]acejavelin[/MENTION]! That's why I love XDA.
[X Style (Pure) Q&A, Help & Troubleshooting] discovery94:
[MENTION=2001582]acejavelin[/MENTION] I was on official (stock) 7.0, build NPH25.200-23. I installed unofficial LOS 14.1 (by Hashbang) because I have the N modem, and official LOS 14.1 only supports the M modem. I later decided to go back to stock. As we all know the NPH25.200-23 factory images have not yet been (or ever will be) released, so I followed your guide on how to revert to stock, except I flashed the available NPH25.200-22 partitions (the ones that flashed, anyway, minus the ones that gave Preflash Validation Error) without relocking the bootloader, and now I am back to NPH25.200-22. I also immediately received the notification for the -23 OTA but I did not install it. My question is this: Can I accept the -23 OTA or will I risk bricking? I never downgraded to M, I only had unofficial LOS 14.1 builds, and now the stock -22 build.

My battery is acting all weird, shutting down at about 70%, plugging it again and showing 50%. When I boot, if I unplug it will immediately shut down. Basically it's plugged in the whole time. I have no idea what's causing this, the fact that I flashed unofficial LOS, or because of a faulty battery since I had changed it before flashing LOS), or because of partitions mismatch. So I'm trying to narrow it down and pinpoint the cause. But it seems that every time I try something, it makes the battery worse.
[X Style (Pure) Q&A, Help & Troubleshooting] acejavelin:
The battery is probably reaching the end of it's life...

You can accept the -23 OTA, the risks are minimal if everything you told me is correct.
[X Style (Pure) Q&A, Help & Troubleshooting] discovery94:
Thanks for the reply. Are you sure that taking the OTA on mismatched partitions (bootloader and gpt from -22 and everything else from -23) would not brick? There have been cases like that in the past (https://xdaforums.com/moto-x-2014/general/warning-hard-bricking-downgrading-t3116379) on the Moto X 2nd Gen because the updater script did not have the correct checks to prevent a brick. Maybe it was the case when downgrading to a previous full version i.e. from 5.1 to 4.4.4, or just on older phones/older versions. Do we know if the updater script from -22 to -23 has to correct checks to prevent a brick?
[X Style (Pure) Q&A, Help & Troubleshooting] acejavelin:
Your not downgrading... Either it will work or the checks will fail. The chances of bricking are minimal.
[X Style (Pure) Q&A, Help & Troubleshooting] xdafan15:
The issue of the MM vs. N modems is part of the reason I started this thread. My understanding was that official Lineage OS 14.1 would only work properly if the phone was still running MM firmware because LOS 14.1 was not configured to handle the N modem as written above by [MENTION=4815843]discovery94[/MENTION]. It seems like the unofficial LOS 14 by [MENTION=4630246]Hashbang173[/MENTION] has some problems, so it seemed safer to stay on MM. But [MENTION=2001582]acejavelin[/MENTION]'s advice to me was to upgrade to N before switching ROMS which would seem to severely limit choices of ROMs

I guess the options are stay on MM and have a large selection of ROMS (including official LOS 14.1)

or upgrade to N and only select form Hashbang's LOS, RR by LuisG, and AOSP EX by Obsolete1,

or maybe upgrade to N, then extract the modem from MM stock firmware and flash it to avoid the modem mismatch problem.

Have I summed this up properly?
[X Style (Pure) Q&A, Help & Troubleshooting] discovery94:
So the OTA was unsuccessful. The recovery first showed installing update, then displayed "Error", and then the phone rebooted and displayed an update not successful screen (Images attached). I guess the only way is to use the factory images, but I won't even get my hopes up for that.
[LG G6 Questions and Answers] catalin27:
Hey guys, i've got my lg g6 from Israeli so i tried to unlock bootloader on LG website, they said this phone bootloader cannot be unlocked.

You guys have this problem, you have managed to unlock g6 from Israeli?

BTW sorry for my bad english, if you guys hear something let me know

Thank you
[LG G6 Questions and Answers] Mikes:
As far as I know H870 and US997 are the only unlockable models.
[LG G6 Questions and Answers] Dvivon:
I got the same problem

I thought to re-register to LG developer and change the country of origin.

what u guys think?
[LG G6 Questions and Answers] Killua96:
It won't change anything, if the phone is not european you cannot unlock the bootloader.
[LG G6 Questions and Answers] Dvivon:
The phone is EU h870.

Let say I bought the us977 model and try to unlock it out side from US, Does it work?
[LG G6 Questions and Answers] Killua96:
Yep
[LG G6 Questions and Answers] Dvivon:
So why the LG website, said 'this phone bootloader cannot be unlocked'

My assumption, if I will change my region to... UK or something else in Europe it will send me the unlock code.

Now let say I get the code, do u think I should go for it?

Can I brick the phone?
[LG G6 Questions and Answers] Killua96:
If you get the code it'll be alright, but if the site says that the bootloader cannot be unlocked after inserting device id and IMEI than it's not an European H870
[Verizon Galaxy S 5 Q&A, Help & Troubleshooting] tattmann:
Hi all, I really need some help here. I am reading in some stickied tutorials that mm is not rootable, and on some others it says it may be rootable if your mmc begins with 15 and may be able to unlock bootloader. I don't know which to go by here. My sons phone is a verizon s5, on pd1 and has mmc number beginning with 15. I really want magisk in it as some apps we use simply don't work with straight root. I have scoured the internet in hopes of finding the info needed and came up with too many conflicting reports so I came back to ask the experts here. However, even the search function here still leads me to some conflicts. Can someone please link me to a tutorial that I can use to root his phone? Any help is greatly appreciated. Thank you in advance.
[Verizon Galaxy S 5 Q&A, Help & Troubleshooting] bbsc:
You can only directly root PD1 (or any MM firmware) if the phone's bootloader is unlocked already.

SM-G900V's bootloader is locked by default, CID15 means that it can be unlocked.

In the case if rooting is possible (CID15) for Android 6.0 (PD1 is a 6.0 firmware) you'll need to:

1. Flash a firmware which allows direct rooting. Modern method is to flash COMBINATION firmware. This rooting has nothing to do with the future rooting of your PD1, this rooting is for unlocking the bootloader.

2. Gain root and install SafeStrap recovery.

3. Flash a MM (say, PD1) bootloader and unlock it.

4. Download stock PD1 firmware and remove the bootloader from it.

5. Flash this firmware with Odin.

The result of these operations will be a SM-G900V phone with stock PD1 firmware and unlocked bootloader. Now you can root your PD1.

6. Download TWRP from their site and flash it with Odin.

7. Download Magisk zip-file.

8. Flash Magisk zip-file with TWRP.
[Verizon Galaxy S 5 Q&A, Help & Troubleshooting] tattmann:
ok, lengthy process lol. Is ok, I will start looking for the files to download and get everything set up. Thank you for your time and for replying.

UPDATE: I got it. The phone is now on resurrection remix with twrp and magisk. Thank you for your help!
[Sprint Samsung Galaxy Note5] demetrios3:
I brought my Galaxy Note 5 to a repair shop to have the charging port replaced and the Technician told me that he couldn't do that without also replacing the glass as there was a deep scratch in the digitizer and would probably break during the disassembly.

But after I negotiated a screen replacement along with the charging port replacement I was told that the digitizer on my Note 5 couldn't be replaced without replacing the LCD as well. I asked why and was told that my phone was refurbished and refurbished note 5's don't have separate digitizers and LCDs. I argued that I got the phone new at Best Buy the day it came out and it couldn't be refurbished but he showed me a little "R" on the back of the phone under the glass to prove it. I wasn't about to spend $250 on a Note 5 that I only use for wifi since I upgraded to the Note 8.

But I do use the Note 5 all the time because I can't customize the Note 8 due to the locked bootloader and I'll buy the Digitizer and charging port and replace them myself. I just don't know if the what the Technician told me about the LCD is true.
[Huawei Mate 9 Questions & Answers] suarez1907:
Hi. When I open firmware finder today,i saw Mha-l29 8.0.0.360(C10) firmware and it approved installation for me. But my region code is c432. Can I install it? Do it brick my device?

MHA-L29 cihazımdan Tapatalk kullanılarak gönderildi
[Huawei Mate 9 Questions & Answers] Szilard666:
It bricked my device like that , if no warranty dont do it.
[Huawei Mate 9 Questions & Answers] aureliomilitao:
c432 have oreo, no need c10
[Huawei Mate 9 Questions & Answers] cobraxxx123:
Even if it gets approved is it safe? I have C185
[Huawei Mate 9 Questions & Answers] 5[Strogino]:
Surely, no!

How it can be safe, if you want install it without rebranding?

Huawei approved it to all, that means no imei filter.

You are using FF that points to ROMs on HiCloud instead of waiting official way. So you must be careful and know what you are doing.
[Huawei Mate 9 Questions & Answers] cobraxxx123:
Better hope the C185, thanks
[Huawei Mate 9 Questions & Answers] revjamescarver:
C10 authorized

When it checks by IMEI and shows that it is authorized it checks if the update was authorized by Huawei, since it is a different "brand" I wouldn't suggest installing it but the "update.zip" is pretty much the same across all regions, it is the data and hw zips that contain most of the stuff that is different for different regions, for myself I am waiting on the official c567 Oreo to hit (I'm running the beta right now), with new regions showing up on ff now every few days, it shouldn't be long till the Oreo official updates have rolled out to all the regions.
[Huawei Mate 9 Questions & Answers] cobraxxx123:
Yes, in FF the C185 version is already out, I'm waiting for it to be authorized, I hope it's fast
[Honor 6, 6 Plus Q&A, Help & Troubleshooting] Ownkayjam:
Hello,

I'm looking for an update.app file for the Honor 6A, I put a request there because i can't find it anywhere.

Thank you for reading

I hope your ending year is great,

Ownkay:good:
[Honor 6, 6 Plus Q&A, Help & Troubleshooting] hassanjavaid8181:
Which firmware numberyou are looking for??

---------- Post added at 07:27 PM ---------- Previous post was at 07:27 PM ----------

Your model number and build number?
[Honor 6, 6 Plus Q&A, Help & Troubleshooting] Ownkayjam:
Hello Hassan,

Thank you for you answer,

Unfortunately, the phone doesn't boot and i don't know the build number. The phone model is DLI-L22, it's the only thing i know, I hope it'll be sufficient.

Have a nice day

EDIT : According to DC-Unlocker, the firmware is : Delhi-L22C432B102
[Honor 6, 6 Plus Q&A, Help & Troubleshooting] hassanjavaid8181:
Ok. I will search and post it here..
[Honor 6, 6 Plus Q&A, Help & Troubleshooting] JDR1999:
I am looking honor 6a ( DLI-L22) firmware rom as well.

Thank You.
[Honor 6, 6 Plus Q&A, Help & Troubleshooting] Ownkayjam:
Hello JDR1999,

Thank you for your interest, we just have to wait a bit.

If I got some information, i'll post it there so you can benefit too.

Have a nice day
[Honor 6, 6 Plus Q&A, Help & Troubleshooting] DerEngel:
Hey there, i just unlocked my bootloader. If someone can tell me how, i would try to create a dump and upload it.
[Honor 6, 6 Plus Q&A, Help & Troubleshooting] Ownkayjam:
Hi friends,

there are good news, firmware available ! go take a look there https://xdaforums.com/honor-6/help/huawei-honor-6a-dli-twrp-root-firmwares-t3734018

Cheers:good:

Ownkay'
[LineageOS Questions & Answers] -WhiteHawk-:
Are there any apps out there compatible with 14.1 that allow for customization of the SystemUI?
[E 2015 Q&A, Help & Troubleshooting] supertanno:
After first flashing LineageOS and then ViperOS, my headphone jack has stopped working. The internal speakers still function perfectly fine, but it doesn't detect headphones and just keeps playing sound through its speakers. This was not an issue on stock. Is there any way to solve this?
[G3 General] GamingDevilsCC:
I'm looking for a stable custom ROM as my daily driver on my d852, and out of the crDroid 8.1 or 7.1.2, which one is more stable? What bugs do both of these ROMs have?
[G3 General] wassco:
The older will always be more stable. Just logic really. I don't personally use crdroid. Tried it.. But I like to customize the crap out if my devices. Miui 8 runs pretty well. Lineage 15 I haven't had any issues either.

I test them all for a few days. Make a twrp backup. And test another. Restoring if I don't like the outcome.

I'd suggest 7.1.2 for stability.. but that's just my opinion.
[G3 General] Nikolatas:
Is it true that the 7.1.2 roms kernel makes the cpu not go lower than 1500mhz?
[Elephone P9000 Questions & Answers] Xandaros:
So, after I finally managed to unbrick my phone, I am still left with the problem of the IMEIs being 111111111111111 and 222222222222222.

There are countless threads on this topic on these forums, but I could not get anything to work. Either they use tools with links which aren't available anymore or their solutions just plain don't work.

Something I tried more than others is generating an MP0B_001 file and pushing it over to /data/nvram/md/NVRAM/NVB_IMEI/ (Not entirely sure about the last folder name. I just tab-completed...)

However, using the generated file, changing owner and group to radio:radio and setting permissions to 660, I get no valid IMEI. *#06# is simply blank and the phone info screen says "Unknown".

Now, here's the best thing: Even after moving the original file and fixing ownership and permissions, it still does not restore the IMEI. I'm really not sure what is going on here.

What else can I do? I tried rooting my phone and installing mobile uncle, but that didn't seem to work at all. Engineering mode is missing CDS Information, so that is a no-go. Mtk Droid Tools I haven't found a working download yet. (It's also windows-only. No clue how well that is going to work with wine. I'm on Linux.)

I'm really at a loss. As far as I know, changing your IMEI is illegal in Germany. Using such an obviously fake one is just asking for trouble.