How upgrade the bootloader to 0xC185? - Moto Z Play Questions & Answers

my z play has the bootloader 0xC105 and I want to update it to the latest version, how do I do it ?, I can not find any guide explaining the process well.
I am currently with the XPE rom 12.1.0-20180619

bootloaders come in stock/factory zips. You would have to find a recent version or flash one and let it ota until you get to that point. If that's even possible - does 185 exist???

KrisM22 said:
bootloaders come in stock/factory zips. You would have to find a recent version or flash one and let it ota until you get to that point. If that's even possible - does 185 exist???
Click to expand...
Click to collapse
my bad, key fail, 182 is the correct

Related

HTC M8 Hong Kong Help (No version_main)

Hi everyone!
I recently unlocked my bootloader and rooted my m8.
I tried using firewater to "s-off" my phone and unfortunately, it did not work out. The way I understand it, I cannot install stock ROMs (such as the 5.0.1 GPE) without "s-off." Now, I want to unroot my phone and stick to waiting for the OTAs to roll out instead.
I followed the instructions in the "returning to stock" thread and noticed that I have no version main (see attached image). I looked around the forums and saw that the advice was to flash the latest TWRP version. Since I'm stuck with a phone that I cannot update, I'm trying to be careful now. Can anyone please confirm if flashing the latest TWRP will bring my version main back?
The noob in me also has a few questions/requests as well:
1. Since my phone is rooted, I cannot receive OTA updates and upgrade to lollipop once these updates roll out?
2. Please tell me which files to download to return to stock. Just trying to be really careful this time around.
3. Lastly, is it also true that I can only install custom ROMs once have rooted? As to stock ROMs, I can't install them until I get "s-off"?
Thanks a lot, everyone! Cheers!
panchizzles said:
Hi everyone!
I recently unlocked my bootloader and rooted my m8.
I tried using firewater to "s-off" my phone and unfortunately, it did not work out. The way I understand it, I cannot install stock ROMs (such as the 5.0.1 GPE) without "s-off." Now, I want to unroot my phone and stick to waiting for the OTAs to roll out instead.
I followed the instructions in the "returning to stock" thread and noticed that I have no version main (see attached image). I looked around the forums and saw that the advice was to flash the latest TWRP version. Since I'm stuck with a phone that I cannot update, I'm trying to be careful now. Can anyone please confirm if flashing the latest TWRP will bring my version main back?
The noob in me also has a few questions/requests as well:
1. Since my phone is rooted, I cannot receive OTA updates and upgrade to lollipop once these updates roll out?
2. Please tell me which files to download to return to stock. Just trying to be really careful this time around.
3. Lastly, is it also true that I can only install custom ROMs once have rooted? As to stock ROMs, I can't install them until I get "s-off"?
Thanks a lot, everyone! Cheers!
Click to expand...
Click to collapse
Your firmware version: 3.32.708.4
I got it from your radio (baseband) number.
xunholyx said:
Your firmware version: 3.32.708.4
I got it from your radio (baseband) number.
Click to expand...
Click to collapse
Thanks for the reply!
Do I have to flash the latest TWRP version before proceeding?

[Tool][HTC 10][S-On]Firmware Updater

Krassermensch's Firmware Update Tool
My situation:
I'm too young to buy the Sunshine App to set my device S-Off but I want to update my device's firmware every time a firmware update's available. Since I compile ROMs and cannot do that via OTA updates the only acceptable way for me is to install signed firmwares in a locked bootloader. After doing that manually I thought I should write a tool that installs the right firmware for your device automatically. As I'm already running the latest firmware on my device after doing the procedure manually I cannot test if the flash part works correctly. Anyway, I achieved to read out the CID as well as the current firmware version and my tool reports that I'm running the latest firmware version I integrated for my device what's correct. So this part works well.
How the tool works:
The tool asks you if you've already installed the HTC USB drivers on your computer. If you haven't you can install it easily using my tool. After that the tool explains you how to set up your phone to be detected by the computer. Then it checks which device you have and checks which firmware's currently installed on it. Right after that the tool installs all the firmwares newer than the one that's currently installed on your phone one after another until the latest firmware my tool is shiped with runs on your device. The procedure doesn't wipe your data since signed firmware-updates are installed.
Requirements:
- An HTC 10
- A computer running windows
- An internet connection
- An unlocked bootloader
- An installed TWRP
Who is this tool for?
All the people who can't or don't want to set their device S-Off while running a non-stock ROM.
Why should I use this tool?
- It updates your firmware to the latest one available for your device automatically
- It doesn't wipe your storage
- You don't need to be S-Off
Download
https://www.androidfilehost.com/?fid=745425885120704223
When the file is downloaded just extract it on your Windows computer and run the batch file. Everything else will be explained.
Important to know
Your boot and recovery partitions will be replaced by the stock ones so after successfully updating your firmware you need to reflash TWRP as well as your Boot partition.
This process is performed automatically now. No need to do that manually.
Tools using ADB just like mine may interfere with other tools that also use ADB. Make sure all these tools are disabled.
Now I need your feedback to be able to optimize the tool! I'll add new firmwares from time to time. I'm looking forward to your reviews
GitLab
https://gitlab.com/Feulner/Firmware-Update-Tool-HTC10
If you like my work consider a donation to support me in financing computer-components which are meant to replace the defect ones in my broken PC.
If you donate you'll donate to my father who will gimme the money. Thank you really much!
This works with unsigned firmware?
Good job, though irrelevant to me
xunholyx said:
This works with unsigned firmware?
Good job, though irrelevant to me
I would guess that you would have to have matching CID and MID of course.
Click to expand...
Click to collapse
No no, not unsigned firmware. I'll explain it more detailed tomorrow or so. The tool just checks your device's CID as well as your device's current firmware version and updates it to the most current firmware version I integrated in my tool. If your firmware is very old the tool also updates again and again until you have the lässt firmware automatically.But it uses signed firmware packages. The biggest advantage is that it should work fully automatic. Try it out and let me know what you think. I go to bed now...
krassermensch said:
No no, not unsigned firmware. I'll explain it more detailed tomorrow or so. The tool just checks your device's CID as well as your device's current firmware version and updates it to the most current firmware version I integrated in my tool. If your firmware is very old the tool also updates again and again until you have the lässt firmware automatically.But it uses signed firmware packages. The biggest advantage is that it should work fully automatic. Try it out and let me know what you think. I go to bed now...
Click to expand...
Click to collapse
I'm s-off since the day after I got my phone, so.......
It sounds like a great idea. I'm sure lot of people will appreciate this. If it does work like you say, WAY better than going back to stock.
xunholyx said:
I'm s-off since the day after I got my phone, so.......
It sounds like a great idea. I'm sure lot of people will appreciate this. If it does work like you say, WAY better than going back to stock.
Click to expand...
Click to collapse
Since when do you have to go back to stock to "fastboot flash zip some_firmware.zip" (as this tool does)?
--beaups
Hm sounds good, but i wont use it until we have some more information what it actually does.
As far as i know, theres no way to just update your firmware with signed zips without partly wiping your device. I had to reflash Viper10 (or restore a nandroid backup) the last time i updated my firmware, cause boot and recovery partitions got replaced. Not completely sure if this affects stock devices, it may work there, but not for devices which are modified with a custom ROM. For this you need a NoWipe firmware from sneakyghosts thread, but these cant be flashed while s-on.
So please explain in more details what your tool does, of course when youve got your sleep .
It most likely flashes firmware zips from OTA updates since those do not wipe the device. He already said it does that, he said if you're on a very old firmware it will keep updating your firmware progressively until you're on the latest version. So if you've never updated before, and there have been three updates since then, the tool will flash the firmware zip of each OTA one after the other.
Updated the main post, hopefully everything's clear now. I need your reviews now. I'm also thinking about an automatic bootloader lock with backup solution so you don't need to lock your bootloader manually and also don't lose your data partition.
Why it doesn't work with unlocked bootloader?
CroCop18 said:
Why it doesn't work with unlocked bootloader?
Click to expand...
Click to collapse
I didn't try but normally your HTC 10 would block the installation if the bootloader is unlocked. Could you try it out and report. It's a bit hard to try it out by myself currently... It will most probably report that your new firmware's flashed but it actually will not be flashed after that if your bootloader's unlocked. If it's flashed anyway it'd be perfect since I'd not have to make a backup solution in that case. But I guess that the 10 isn't different to the M9 for example when it comes to firmware flashing. I read that you can have an unlocked bootloader if your device is S-Off but those are things I haven't been able to try out so far...
krassermensch said:
I didn't try but normally your HTC 10 would block the installation if the bootloader is unlocked. Could you try it out and report. It's a bit hard to try it out by myself currently... It will most probably report that your new firmware's flashed but it actually will not be flashed after that if your bootloader's unlocked. If it's flashed anyway it'd be perfect since I'd not have to make a backup solution in that case. But I guess that the 10 isn't different to the M9 for example when it comes to firmware flashing. I read that you can have an unlocked bootloader if your device is S-Off but those are things I haven't been able to try out so far...
Click to expand...
Click to collapse
Really? You don't know how to unlock your bootloader? You don't need S-Off for it.
This answers the question I had wondered about. How does this install OTAs with a custom recovery? It doesn't, correct?
You need to be stock for this. The first thing you do after unlocking the bootloader (which pretty much anyone here has done) is to flash a custom recovery.
This tool will only work for users who are still completely on stock.
IO would test myself, but I'm already S-Off/unlocked bootloader/custom recovery/modified firmware/custom ROM|, and I don't want to take the time to go back to stock and incrementally update the steps to see what won't work. I think as soon as you flash custom recovery, you can't use this method.
If you want to unlock your bootloader, HTC provides the method and instructions at htcdev.com
xunholyx said:
Really? You don't know how to unlock your bootloader? You don't need S-Off for it.
This answers the question I had wondered about. How does this install OTAs with a custom recovery? It doesn't, correct?
You need to be stock for this. The first thing you do after unlocking the bootloader (which pretty much anyone here has done) is to flash a custom recovery.
This tool will only work for users who are still completely on stock.
IO would test myself, but I'm already S-Off/unlocked bootloader/custom recovery/modified firmware/custom ROM|, and I don't want to take the time to go back to stock and incrementally update the steps to see what won't work. I think as soon as you flash custom recovery, you can't use this method.
If you want to unlock your bootloader, HTC provides the method and instructions at htcdev.com
Click to expand...
Click to collapse
Sure I know how to unlock a boitloader. If you watch my profile you can see I'm a ROM maintainer. I have to use custom recoveries to do that. People interpret my posts wrongly sometimes. I dunno why. Anyway, I use TWRP but after flashing a recovery or any other image file I lock my bootloader again for safety reasons. You just need to have a locked bootloader to use my tool currently... And no, u don't need to be stock. This tool just requires a locked or relocked bootloader. U can use whatever ROM u like. U just need to have a locked bootloader and my tool installs the latest firmware I integrated for your HTC 10 model. I know what I do. You should just read my posts a bit more carefully to prevent yourself from contending wrong things...
krassermensch said:
Sure I know how to unlock a boitloader. If you watch my profile you can see I'm a ROM maintainer. I have to use custom recoveries to do that. People interpret my posts wrongly sometimes. I dunno why. Anyway, I use TWRP but after flashing a recovery or any other image file I lock my bootloader again for safety reasons. You just need to have a locked bootloader to use my tool currently...
Click to expand...
Click to collapse
" I read that you can have an unlocked bootloader if your device is S-Off" quote from you
I did read it wrong. I was thinking that you meant you needed soff to unlock bootloader.\
And yes, now that I understand what you meant, with S-Off you shouldn't need to re-lock your bootloader.
xunholyx said:
" I read that you can have an unlocked bootloader if your device is S-Off" quote from you
I did read it wrong. I was thinking that you meant you needed soff to unlock bootloader.\
And yes, now that I understand what you meant, with S-Off you shouldn't need to re-lock your bootloader.
Click to expand...
Click to collapse
Yeah, dude, I think I wouldn't be able to write a batch tool with fastboot and adb if I didn't know the whole stuff. My broken Nexus 4 has teached me a lot over the last 3½ years
Just to confirm... and thanks for the tool
I have a HTC 10 and nothing has been done to it since I bought it (Stock everything) will this tool keep it that way but give me the latest OTA?
Milamber said:
Just to confirm... and thanks for the tool
I have a HTC 10 and nothing has been done to it since I bought it (Stock everything) will this tool keep it that way but give me the latest OTA?
Click to expand...
Click to collapse
You do not need this tool if you are Stock everything, unless you unlocked your bootloader.
Milamber said:
Just to confirm... and thanks for the tool
I have a HTC 10 and nothing has been done to it since I bought it (Stock everything) will this tool keep it that way but give me the latest OTA?
Click to expand...
Click to collapse
No, I could write a tool for manual OTA flashing, too, but I don't want to do that since OTAs are for stock devices which are notified about OTA updates automatically. If you want to flash OTAs quicker: there's a thread here on xda where OTA zips are shared with an explaination how to flash it manually... This tool can be used by stock device's owners but it wouldn't be necessary...
krassermensch said:
I didn't try but normally your HTC 10 would block the installation if the bootloader is unlocked. Could you try it out and report. It's a bit hard to try it out by myself currently... It will most probably report that your new firmware's flashed but it actually will not be flashed after that if your bootloader's unlocked. If it's flashed anyway it'd be perfect since I'd not have to make a backup solution in that case. But I guess that the 10 isn't different to the M9 for example when it comes to firmware flashing. I read that you can have an unlocked bootloader if your device is S-Off but those are things I haven't been able to try out so far...
Click to expand...
Click to collapse
Thanks for your explanations, now i understand your tool a bit more.
But if it only works with a locked/relocked bootloader i cant use it. Really no offense and i dont want to sound rude (!), but isnt it already a design problem? You said the tool is designed for people with non-stock ROMS, but that does imply that you have an unlocked bootloader to flash and keep your ROM and recovery up to date. To use your tool you have to relock the bootloader after flashing the ROM. But to update the ROM to a newer version you have to unlock the bootloader again via HTCDev (and loosing your data while doing this)? Sounds a bit weird to me...or did i miss something?
So which adb commands are you using? Didnt have the time to check your script yet (sorry!). Because im S-On with my bootloader unlocked an i COULD flash a signed firmware.zip i extracted from an official OTA via ADB. This wiped my boot and recovery partitions, but not data. Just had to restore the two partitions to get everything working again.
-Vulture- said:
Thanks for your explanations, now i understand your tool a bit more.
But if it only works with a locked/relocked bootloader i cant use it. Really no offense and i dont want to sound rude (!), but isnt it already a design problem? You said the tool is designed for people with non-stock ROMS, but that does imply that you have an unlocked bootloader to flash and keep your ROM and recovery up to date. To use your tool you have to relock the bootloader after flashing the ROM. But to update the ROM to a newer version you have to unlock the bootloader again via HTCDev (and loosing your data while doing this)? Sounds a bit weird to me...or did i miss something?
So which adb commands are you using? Didnt have the time to check your script yet (sorry!). Because im S-On with my bootloader unlocked an i COULD flash a signed firmware.zip i extracted from an official OTA via ADB. This wiped my boot and recovery partitions, but not data. Just had to restore the two partitions to get everything working again.
Click to expand...
Click to collapse
So you could flash the firmware-update.zip from the OTA without relocking your bootloader?
And it was really updated after that?
krassermensch said:
So you could flash the firmware-update.zip from the OTA without relocking your bootloader?
And it was really updated after that?
Click to expand...
Click to collapse
Thats what i did, bootloader was unlocked and flash successfully. I extracted the firmware.zip from an official OTA (TMOB-101) for my device and flashed it via ADB from my PC. Since the firmware.zip is signed, it can be flashed. Doesnt work with modified zips however, like the ones from sneakyghosts thread. He removed unnecessary stuff like the flash command for boot and recovery which my broke my phone initially. Thats why you need TWRP to restore them later.
As you already said with your tool, its also important here to get the right file to flash and not to skip a firmware update in between. You have to go from very old -> old -> current without skipping old.
I used the step-by-step instructions from here:
http://forum.xda-developers.com/htc-10/how-to/2016-05-27-fastboot-flashing-firmware-t3387520

Question on mismatch of OS version in download mode compared to sw information

Hey everyone,
Apologize if this is something that has been asked before, haven't been able to find much information on it using search. Also still a relative newbie to android, so hope you folks will bear with me. I'm seeing the OS version in download mode showing as OS-3.36.709.3, while the software number in software information shows 4.30.617.12. Is this considered normal, or did I mess something up?
I previously had Marshmallow on my phone, and used TWRP to install the developer edition of Nougat. Was trying to do OTA, which unsurprisingly didn't work with TWRP installed. My plan is to reflash the recovery.img, but I'm unsure whether I should be using the recovery.img for 4.30.617.12, or the one for 3.36.709.3? Is there something I should do to get the versions aligned properly? Trying to make sure I avoid bricking the phone
The easiest solution would be downloading the latest version of the rom that you installed in the past and flashing it via TWRP.
Some advices: Please read the ReadMe thread. It explains why the version numbers differ (e.g. in the RUU section). In addition it will explain to you, that installing OTAs with TWRP actually is possible (c.f. the OTA section) but not in your case. Even with the correct stock recovery for your phone (the 709 one) you wouldn't be able to achieve your goal. You're trying to install an update for a completely different firmware than the current one of your phone. That's not possible. OTAs are incremental. That means you need to be using the firmware that the OTA is supposed to update (4.30.617.12) and not 3.36.709.3. You would need to convert your phone if you want to install that update.
You might want to read the article that I called "the difference between rom and firmware" in the further reading section of the ReadMe thread, as well, after you finished reading the ReadMe thread itself.
Be aware that it's always best to use a system that has the same version (or at least the same mayor version - e.g. 3.x for marshmallow or 4.x for nougat) as your phone. This way you can be sure that system and firmware are optimized for each other. Mismatches can cause unforseen side effects like battery drainage, lags or bugs.
I read the ROM vs. firmware article, and also based on your last comment, I think it would be best to align the firmware and ROM versions. If I'm understanding things correctly, I either need to flash the firmware to a version matching my ROM (4.30.617.12) by following the steps in the 's-off firmware flashing thread', or else I need to go back to a 3.36.709.3 rom and use OTA to update the firmware/ROM. If I use TWRP to update the ROM, I'll still be stuck with an older firmware. Is my understanding on this correct?
I originally go the phone second hand, and am not sure what ROM was on it to begin with. Had previously tried to get it back to stock to update to Nougat via OTA, but kept getting the your device software has been modified regardless of what I did, so ended up using TWRP.
P.S. will make sure to put questions in the right forum in the future.
e1rond said:
I read the ROM vs. firmware article, and also based on your last comment, I think it would be best to align the firmware and ROM versions. If I'm understanding things correctly, I either need to flash the firmware to a version matching my ROM (4.30.617.12) by following the steps in the 's-off firmware flashing thread', or else I need to go back to a 3.36.709.3 rom and use OTA to update the firmware/ROM. If I use TWRP to update the ROM, I'll still be stuck with an older firmware. Is my understanding on this correct?
Click to expand...
Click to collapse
Correct.
e1rond said:
I originally go the phone second hand, and am not sure what ROM was on it to begin with. Had previously tried to get it back to stock to update to Nougat via OTA, but kept getting the your device software has been modified regardless of what I did, so ended up using TWRP.
Click to expand...
Click to collapse
Then the phone had been modified before you got it. Since android 5 google is using block-based OTAs. That means re-flashing the stock recovery isn't sufficent if you want to update your phone and modified it, beforehand. You need to restore a completely untouched system image.
Check the ReadMe thread. The RUU section as well as the TWRP section II should contain the files and instructions that you need for restoring the OTA function of your phone. It's up to you which of the methods you prefer to use.
Appreciate the information and the advice. Decided to RUU back to a 3.x version, and use OTA to upgrade to Nougat. Took a lot of updates to get it to the latest version, but everything is working well now

Help regarding unrooting, restoring and accepting 7.1.1 OTA.

Hi. Im new here so please help me.
I have a Moto Z Play XT1635-02 on 7.0 with the 1st May Patch installed.
I unlocked the bootloader to root this device.
I rooted with this:
https://forum.xda-developers.com/moto-z-play/how-to/correct-rooting-moto-z-play-feb-17-t3560268
Now i want to go back to stock firmware to accept the OTA i just recieved for 7.1.1.
My main query is that, i have RETGB device and its on build number NPN25.137-24.3
I can't find any firmware for RETGB software channel.
I did find the OTA for this, which i have downloaded through the moto ota link generator tool by erfanoabdi.
Now, can any one guide me on how to restore stock without messing up my device?
I have downloaded two retail firmwares:
1)XT1635-02_ADDISON_7.0_NPNS25.137-24-1-9_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
2)XT1635-02_ADDISON_7.0_NPNS25.137-24-1-4_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
Is it safe to flash any of these on my May patched device or should i somehow find the may patched firmware?
Waiting for your kind replies! :')
sheri.khan said:
Hi. Im new here so please help me.
I have a Moto Z Play XT1635-02 on 7.0 with the 1st May Patch installed.
I unlocked the bootloader to root this device.
I rooted with this:
https://forum.xda-developers.com/moto-z-play/how-to/correct-rooting-moto-z-play-feb-17-t3560268
Now i want to go back to stock firmware to accept the OTA i just recieved for 7.1.1.
My main query is that, i have RETGB device and its on build number NPN25.137-24.3
I can't find any firmware for RETGB software channel.
I did find the OTA for this, which i have downloaded through the moto ota link generator tool by erfanoabdi.
Now, can any one guide me on how to restore stock without messing up my device?
I have downloaded two retail firmwares:
1)XT1635-02_ADDISON_7.0_NPNS25.137-24-1-9_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
2)XT1635-02_ADDISON_7.0_NPNS25.137-24-1-4_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
Is it safe to flash any of these on my May patched device or should i somehow find the may patched firmware?
Waiting for your kind replies! :')
Click to expand...
Click to collapse
Just flash the below link and you will be on 7.1.1, and yes it is that simple.
https://forum.xda-developers.com/moto-z-play/development/rom-single-dual-sim-t3620551
Jimi Mack said:
Just flash the below link and you will be on 7.1.1, and yes it is that simple.
https://forum.xda-developers.com/moto-z-play/development/rom-single-dual-sim-t3620551
Click to expand...
Click to collapse
Thank you!
I should flash this through TWRP?
Also after flashing this, the future OTA updates(If any) will be installed without any problems on my retgb channel?
sheri.khan said:
Thank you!
I should flash this through TWRP?
Also after flashing this, the future OTA updates(If any) will be installed without any problems on my retgb channel?
Click to expand...
Click to collapse
Yes on TWRP no on future updates.. being there is not official release for you. Plus the next major update if it happens would not be till O is released which we would not see till way after the new year.
Once you unlock bootloader and root, no going back...
Jimi Mack said:
Yes on TWRP no on future updates.. being there is not official release for you. Plus the next major update if it happens would not be till O is released which we would not see till way after the new year.
Once you unlock bootloader and root, no going back...
Click to expand...
Click to collapse
Thanks brother.
I don't seem to get why the RETGB firmware isn't released.
I literally can't find anyone except i guess two or just 3 people who have the same software channel.
Thanks again!
On the Verizon blackberry priv, there was a way to install the ROM with no Verizon bloatware, no rooting or anything.
Same with my T-Mobile s7 edge, is there something for the Verizon moto z play?
jzamalot said:
On the Verizon blackberry priv, there was a way to install the ROM with no Verizon bloatware, no rooting or anything.
Same with my T-Mobile s7 edge, is there something for the Verizon moto z play?
Click to expand...
Click to collapse
I don't think that its possible with the Verizon MZP.
There's no access for anyone to unlock its bootloader as of yet.
So there's no development for it either.
But who knows? Don't lose the hope! :'D
sheri.khan said:
I don't think that its possible with the Verizon MZP.
There's no access for anyone to unlock its bootloader as of yet.
So there's no development for it either.
But who knows? Don't lose the hope! :'D
Click to expand...
Click to collapse
Thanks, just wondering because the blackberry priv bootloader was also never unlocked or ever rooted

[Q]

Please when i receved update OREO for my moto G5 Xt 1676 dual ? Thanks in advance ,,??
mednazim said:
Please when i receved update OREO for my moto G5 Xt 1676 dual ? Thanks in advance ,,
Click to expand...
Click to collapse
Most probably, you will receive it in this century.. I think. :laugh:
I'll be serious now. Nobody knows when you will receive an update. It depends on your region mostly, but there are also few other factors which can delay it. However, if you don't want to wait anymore and have knowledge of flashing fastboot firmwares, full fastboot Oreo firmware (step-by-step tutorial included) for Moto G5 is already available here: https://forum.xda-developers.com/g5/how-to/official-oreo-8-1-0-opp28-85-16-t3849244. Of course, nobody is responsible for any damage you make by flashing it.
it is necessary to unlock bootloader and install recovery for install update OREO ?
mednazim said:
it is necessary to unlock bootloader and install recovery for install update OREO ?
Click to expand...
Click to collapse
No, it isn't. According to posts in the other threads, there are at least 2 requirements to successfully update to Oreo through OTA (https://forum.xda-developers.com/g5...ase-opp28-t3849273/post77771786)#post77771786).
The first one is that system, boot and recovery partitions must be 100% unmodified - restoring doesn't help. If it's once modified, only a full reflash of stock firmware (with equal or newer build) will revert it to completely unmodified state. If you decide to install an update with one of these partitions modified - in the better case, update will refuse to install. In the worse one, it will install, but you will end up with hardbrick.
The second one, your build number must be NPPS25.137-93-2-5 (install script do the checking of the build number in the beginning of the OTA install. If it finds different value, installation will be stopped with some error showing up, but nothing happens, because the whole process of updating didn't start at all).
Thanks bro i will try

Categories

Resources