Database Users

[Files Collection]Dev Edition Reset Rom/Firmware/RUU/No red txt[Latest: 7.17.1540.35

Developer Edition Collection
6.07.1540.1
6.07.1540.2
7.17.1540.7
7.17.1540.21
7.17.1540.35
Firmware files, RUU, Recovery, Nand backups, Reset roms and more​
Screenshot:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Just in case:
if you are using files posted below, its because you already know what you are doing. I'm not responsible if you brick your phone using these files (e.g. flashing ota-firmware over the wrong version). All files posted below, (exception: reset roms, nandroid backups and "No red text" hboot) are official HTC files so don't blame me if something goes wrong when flashing, I'm just the uploader. Flash at your own risk! Thanks.​
Click to expand...
Click to collapse
Reset roms/Nand backup:
These roms/nandroid backups are for users with developer edition M7 (or converted to DevEd) that want to reset their phones back to stock version 6.07.1540.1, 6.07.1540.2 or 7.17.1540.7 and be able to receive future ota updates. Reset Roms are flashed using TWRP with the Aroma Installer and like an official Guru Reset Rom, you have the option to flash stock recovery, stock radio and root from the installer.
These reset roms was made using one of crushalot's famous "guru reset" rom package. All credits goes to him for the awesome work he did for us. All I did here was to repack one of his zip with the dev edition system dump, recovery, radio and preload apps (/data/preload) and re-sign it.
I have personally tested these reset roms on my own device using TWRP Recovery 2.6.3.3. Use TWRP 2.8.4.0 to restore the 7.17.1540.7 nandroid backup. Please use ADB push instead of Sideload for better results (sideload might freeze or report "failed") or drag-n-drop to /sdcard if you still have an OS on your phone or if your recovery support MTP!
Basic instructions for Reset Roms:
Click to expand...
Click to collapse
Unlock your bootloader
Flash TWRP recovery 2.6.3.3
Adb push the zip file to your sdcard
Install using TWRP 2.6.3.3
Select stock recovery and radio
Update your firmware so it match the software version (needed for ota support)
Want more detailed (like very very detailed instructions)? Then read FAQ 5) in the post below.
Latest Developer Edition Version: 7.17.1540.35​
Click to expand...
Click to collapse
Lollipop files:
Click to expand...
Click to collapse
General Info:
Firmware and Software version: 7.17.1540.35
stock radio version: 4T.35.3218.16
Android version: 5.0.2
Sense version: 6.0
CID: BS__US001
MID: PN0712000
7.17.1540.35 Files:
7.17.1540.35 RUU.exe
Download link (Official HTC server)
OTA update zip 7.17.1540.35 (thanks to @majmoz for capturing it)
Download link (AFH)
MD5: ca6c1263827943d8ac6be4bbc62a14dc
Stock Firmware patch (firmware package from OTA.zip) 7.17.1540.35
To be flashed incrementally only (from 7.17.1540.21 only)
Download link (AFH)
MD5: 27754f612df99798c51e45c7015aab72
Full stock firmware 7.17.1540.35 untested --> flash at your own risk)
Download link (AFH)
MD5: c8dcff28a23341598110c09ac2c922e8
stock recovery 7.17.1540.35 (parition mmcblk0p34)
Download link (AFH)
MD5: 99a9bc5e2492ca90e3bfecdaa899d2d8
stock bootloader (hboot) 7.17.1540.35 (parition mmcblk0p12)
Download link (AFH)
MD5: 545085ba23e1a2027667c6b66a559856
Modded bootloader (hboot) No red text 7.17.1540.35 (parition mmcblk0p12)
Download link (AFH)
MD5: 842af318e60d0a0b3c030c59cd8b4587
stock kernel 7.17.1540.35 (parition mmcblk0p33)
Download link (AFH)
MD5: fe455af5bee768def555a410d1dcfad7
7.17.1540.21 Files:
7.17.1540.21 Signed RUU.zip
Download link (AFH)
MD5: 93b5999ecbcec8e8e92eb18fb5444de2
OTA update zip 7.17.1540.21
Download link (AFH)
MD5: c36f9e22245524a41d62874232fec526
Stock Firmware patch (firmware package from OTA.zip) 7.17.1540.21
Download link (AFH)
MD5: fd9247fdd994f378a4bc206167ff2d6e
Only flash if your firmware is 7.17.1540.7 firmware or 7.17.1540.21
Full stock firmware 7.17.1540.21 untested --> flash at your own risk)
Download link (AFH)
MD5: abaa10fa65c0a7185751d5b31f406940
stock recovery 7.17.1540.21 (parition mmcblk0p34)
Download link (AFH)
MD5: 1d45cca5a93b1c1da18ba3a757780429
stock bootloader (hboot) 7.17.1540.21 (parition mmcblk0p12)
Download link (AFH)
MD5: fa6c2cc563ffdb76578b1480670805ad
Modded bootloader (hboot) No red text 7.17.1540.21 (parition mmcblk0p12)
Download link (AFH)
MD5: 3031e2488fb137d79495b133ec74ee7c
stock kernel 7.17.1540.21 (parition mmcblk0p33)
Download link (AFH)
MD5: 51dd6c7e01bd5a7391d21e7b519481e7
7.17.1540.7 Files:
7.17.1540.7 Signed RUU.exe
Download link (HTC)
MD5: a1e78219a7d8de0efe2cdbd54e630381
7.17.1540.7 TWRP nandroid backup
Download link (AFH)
MD5: 78d86f33de5c26012c1ca6ecc94e9649
OTA update zip 7.17.1540.7
Download link (AFH)
MD5: f5f67a055460d38d3ca624b8c3f227c4
Stock Firmware patch (firmware package from OTA.zip) 7.17.1540.7
Download link (AFH)
MD5: 55da7c269def8f7853abe7a08c073f6d
Full stock firmware 7.17.1540.7 untested --> flash at your own risk)
Download link (AFH)
MD5: d9a4ff438caad12d11550869ca39e4c7
No red text hboot (modded hboot) 7.17.1540.7
Download link (AFH)
MD5: c5776c29fde6db9780efd3618039f795
Credits to @shinji257 for testing the file on his phone.
/data/preload folder for 7.17.1540.7
Download link (AFH)
MD5: 356c17524f05a64519908c3f38594cdd
stock radio 7.17.1540.7 (parition mmcblk0p31)
Download link (AFH)
MD5: 7402267e194438f7d3100227c64981b8
stock recovery 7.17.1540.7 (parition mmcblk0p34)
Download link (AFH)
MD5: 87a351e9e3b7b11c02d9cbc023a43550
stock bootloader (hboot) 7.17.1540.7 (parition mmcblk0p12)
Download link (AFH)
MD5: c8411bf8e7a66dc3fbaa43653252e50e
stock kernel 7.17.1540.7 (parition mmcblk0p33)
Download link (AFH)
MD5: dd73b73d49c8334ffe33b8b11cea2ba9
Kit Kat files:
Click to expand...
Click to collapse
General Info:
Latest KitKat Firmware/Software version: 6.07.1540.2
stock radio version: 4T.28.3218.04 (both for the .1/.2 version)
Android version: 4.4.3
Sense version: 6.0
CID: BS__US001
MID: PN0712000
6.07.1540.2 Files:
6.07.1540.2 Reset Rom Download:
Download link (AFH):
MD5: df3eebcb55b657905cc4a9f308701471
6.07.1540.2 Signed RUU.exe
Download link (HTCDev.com)
MD5: e5e4f703a6c0d9403ab2b53b982a11c4
6.07.1540.2 OTA update zip file
Download link (AFH)
MD5: e2c41505e640034b89f50cce64630d3e
6.07.1540.2 Firmware patch
Download link (AFH)
MD5: 4fb7ddb299b3f7884274a67fdcd7778e
TO BE FLASHED INCREMENTALLY FROM 6.07.1540.1 VERSION ONLY
6.07.1540.2 stock firmware (full)
Download link (AFH)
MD5: 6b7c3bb3b252115a151aceec61f89f32
CAN BE FLASHED SAFELY FROM ANY VERSION
Stock radio 6.07.1540.2 (partition mmcblk0p31)
Download link (mega.co.nz)
MD5: c4a1864e95548a2c17181b348aa9dbdf
6.07.1540.2 Stock recovery (partition mmcblk0p34)
Download link (AFH)
MD5: bbf256846223a282eb180b8652df888f
6.07.1540.2 Stock Kernel (boot) (partition mmcblk0p33)
Download link (AFH)
MD5: bf7b8c6664baa56180ee5cffcf0f9643
6.07.1540.2 Stock bootloader (hboot) (partition mmcblk0p12)
Download link (AFH)
MD5: 83417611e671d6379379ac6e9ca7f87e
6.07.1540.2 No red text bootloarder (modded hboot) (partition mmcblk0p12
Download link (AFH)
MD5: 6d99221abaf5a0e90e09c2a12439826e
made and tested by @yatindroid, thanks for sharing!
6.07.1540.1 Files:
6.07.1540.1 Reset Rom Download:
Download link (mega.co.nz):
MD5: 21d07939c01d81e840d8068b2b770391
6.07.1540.1 TWRP nandroid backup
Download link (mega.co.nz)
MD5: e54d3783684befb4c8c02b2f26f3c9ad
(Perform a factory reset after restoring this backup)
6.07.1540.1 stock firmware
Download link (AFH)
MD5: 19fbe8b293810e11c62dd1470d412502
Stock recovery 6.07.1540.1 (partition mmcblk0p34)
Download link (mega.co.nz)
MD5: 52e04102121423ee18200f6bad4ad925
Stock radio 6.07.1540.1 (partition mmcblk0p31)
Download link (mega.co.nz)
MD5: c4a1864e95548a2c17181b348aa9dbdf
Stock kernel (boot) 6.07.1540.1 (partition mmcblk0p33)
Download link (AFH)
MD5: 20224c623fbcf3b425762e4212f948a0
Stock bootloader (hboot) 6.07.1540.1 (partition mmcblk0p12)
Download link (AFH)
MD5: 8cf747129d942b58270fd75c0b03ab05
/data/preload 6.07.1540.1 (folder that is wiped when unlocking bootloader)
Download link (AFH)
MD5: a0bbfb0ce1e791713b3ec80f0a3ce4ba
I have personally tested these reset roms on my own device using TWRP Recovery 2.6.3.3. Please use ADB push instead of sideload for better result (sideload might freeze or report "failed") or drag-n-drop to /sdcard if you still have an OS on your phone or if you custom recovery have MPT support!
Click to expand...
Click to collapse
Please do not upload reset roms to other websites or forums without my permission! <--- IR-FILE.COM I'm talking to you...
Click to expand...
Click to collapse
All uploaded files can be found on my AFH account:
Changelog:
Click to expand...
Click to collapse
23rd October 2014: Initial post, uploaded 6.07.1540.1 reset rom, nanadroid backups and other related files.
30th December 2014: Uploaded 6.07.1540.2 ota.zip and related files.
12th January 2015: Uploaded 6.07.1540.2 Reset Rom.
13th January 2015: Uploaded 6.07.1540.2 complete stock firmware.zip, uploaded 6.07.1540.1 complete firmware.zip, uploaded 6.07.1540.1/.2 radio.img.
14th January 2015: Added link to 6.07.1540.2 Signed RUU.exe (thanks to dd98 for sharing).
5th February 2015: Uploaded 7.17.1540.7 Hboot, Radio, Kernel, Recovery and Firmware.
5th February 2015: Uploaded 7.17.1540.7 Ota zip file.
5th February 2015: Uploaded 7.17.1540.7 TWRP Nandroid Backup.
8th February 2015: re-organized OP layout, added FAQ post #2.
11th February 2015: Added link to 7.17.1540.7 ruu.exe, added /data/preload files if you have mistakenly locked/unlocked your bootloader.
06th March 2015: Uploaded 7.17.1540.7 hboot without red warning. Thanks to @shinji257 for testing it.
26th March 2015 : Added 6.07.1540.2 hboot without red warning. Thanks to @yatindroid droid for the file and testing it.
26th May 2015: Uploaded 7.17.1540.21 ota update zip file, stock recovery, stock bootloader, no red text bootloader, stock kernel, ota firmware patch (firmware.zip)
23th June 2015: Uploaded 7.17.1540.21 Signed ruu.zip
11th September 2015: Added 7.17.1540.35 ota.zip thanks to @majmoz for sharing, firmware.zip, stock recovery, stock kernel, stock hboot and no red text hboot.
25th September 2015: Added link to 7.17.1540.35 RUU.exe.

FAQ​
1) Can I flash this reset rom/nandroid with PN071XXXX MID / HTC__XXX CID?
A) Yes but read 2) and 3) below.
2) Will I receive ota update if i'm using HTC__XXX CID?
A) No, you will only receive ota update using BS_US001 CID (also using superCID, thanks to @shinji257 for reporting this)
---> Change CID to BS_US001 (S-OFF needed)
Code:
fastboot oem writecid BS_US001
or to superCID:
Code:
fastboot oem writecid 11111111
3) Can I receive ota update when using PN071XXXX MID?
A) No, only PN0712000 can receive ota updates. If using another MID you'll be able to download the ota update but you'll get the "Variant System Version" error when trying to install it.
---> Change MID to PN0712000 using this tool (S-OFF needed)
---> Or flash OTA update manually from stock recovery (S-OFF needed)
4) After using the 6.07.1540.2 reset rom and selecting "NO" to "install root" I however have SuperSu installed. thanks to @trancemtv for reporting.
A) My bad, I mistakenly built this reset rom using a system dump of a rooted phone. This will not affect ota updates. Fixed in 7.17.1540.7 nandroid backup.
---> Manually delete supersu from /system/app and root files from /system/xbin using TWRP's file manager then re-flash the stock recovery provided in this thread. Or you can use an unroot app like "ota root keeper" to remove root: use "Temp unroot" then "delete SU backup".
5) How can I "adb push" and install a reset roms to my phone:
A)
Originally posted by @alrayHTC ONE M7_U/M7_UL - ADB PUSH & FLASH A ROM - DETAILED INSTRUCTIONS
Prerequisites:
You need ADB and FASTBOOT on your computer,
either by installing the Android SDK or Minimal ADB and FASTBOOT
You need to know how to start a fastboot/adb command prompt:
To open a command window prompt, in Windows go to Start Menu --> ''Run'' then type cmd. Change the directory to the ADB folder on your machine:
If using the default install location for the SDK:
Code:
cd C:\adt-bundle-windows-x86_64-<DATE>\sdk\platform-tools
If using the default install location of Minimal ADB and FASTBOOT:
Code:
cd C:\Program Files (x86)\Minimal ADB and Fastboot
Or hold left shift + right click a blank space inside the folder where adb and fastboot are located and select ''Open command window here'' from the contextual menu.
You need TWRP recovery on your device.
We still recommend to use version 2.6.3.3 for all roms
except if another version is specified in the rom OP.
Use 2.7.1.1+ for roms that require "block:by-name" support (CM11)
Unlock bootloader if not already unlocked:
Thanks to Electroz for the video tutorial
Flash TWRP Recovery:
Make sure the recovery.img file is in the same folder where adb and fastboot are located
(C:\adt-bundle-windows-x86_64-<DATE>\sdk\platform-tools or C:\Program Files (x86)\Minimal ADB and Fastboot)
reboot phone in bootloader mode
Flash the recovery:
Code:
fastboot flash recovery name_of_recovery.img
fastboot erase cache
fastboot reboot-bootloader
You need your HTC drivers correctly installed on your PC:
If not, follow this guide (thanks to nkk71):
originally from @nkk71: [GUIDE] [02-MAR-2014] nkk71's SuperGUIDE to returning 100% back to stock
follow the below instructions to fix
Open "Device Manager" -> select the unknown "One" -> right-click -> "Update Driver Software ..." -> "Browse my computer" -> "Let me pick" -> "Android USB Devices" -> select "My HTC ..." -> install that
just in case, HTC Drivers can be found here: [Drivers] HTC Drivers for Windows - Several Versions (credits to @mdmower)
though you should already have them since you have been using your phone anyways
for those who like a visual guide:
okay so I did a fastboot boot command, and as you can see it didnt install correct driver
Open "Device Manager"
there's the culprit
right click and Update Driver Software
select Browse my computer for driver software
select Let me pick from a list of device drivers on my computer
select Android USB Devices
select My HTC ... (if you have more than one version, choose the latest)
warning, select Yes
successful installation
now it looks better
and can confirm:
Code:
C:\ADB3>[B]adb devices[/B]
List of devices attached
HTxxxxxxxxxx recovery
Click to expand...
Click to collapse
​
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Procedure:
Make sure the ROM you want to flash is in the same folder where ADB and FASTBOOT are.
(C:\adt-bundle-windows-x86_64-<DATE>\sdk\platform-tools or C:\Program Files (x86)\Minimal ADB and Fastboot)
Here is a list of the HTC M7 roms. Some other roms can be found here.
Connect your phone to computer using usb cable
(if not using the official HTC USB calble, make sure
you are using a USB data cable and not only a charging
cable. Data cables have 4 contacts: 5V, GND, DATA+, DATA-.
Charging cable only have 5V and GND contact and will not work)
Reboot phone in recovery mode (TWRP):
If phone is booted in OS:
Code:
adb reboot recovery
if not booted or bootlooping, hold power button + volume down until phone boot in bootloader mode
then select BOOTLOADER then RECOVERY using volume up/down to navigate and power button to select.
Make sure your phone is booted in TWRP main menu:
transfer the rom to your /sdcard folder:
Code:
adb push name_of_rom.zip /sdcard/
Wait for the zip file to transfer, this can take several minutes (5-15) and there is no progress bar, the command prompt will be unresponsive for that duration. When the command prompt is responsive again and display how much bytes transferred in X seconds, the transfer is completed:
In TWRP main menu, select ''INSTALL''
Browse the installation menu and select your rom zip file inside /sdcard folder:
Swipe to confirm you want to flash the rom
Reboot phone
Click to expand...
Click to collapse
Click to expand...
Click to collapse
5) How can I push and restore a nandroid backup to my phone?
B) Boot in twrp and make a backup of boot.img only (this is only to generate a backup path). Then using twrp's files manager navigate to /sdcard/TWRP/BACKUPS/your_serial_number/date_of_backup and delete backup files in this folder and replace them by the files contained in the nandroid backup you want to use. Then select "restore" and restore the backup.
6) How can I flash recovery?
A)
Code:
fastboot flash recovery recovery.img
fastboot erase cache
fastboot reboot-bootloader
7) How can I flash firmware?
A) If you are asking this question, you shouldn't mess with firmware! But however:
Code:
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip
fastboot reboot-bootloader
8) Can I use the 7.17.1540.7 firmware posted here to update my frimware from x.xx.xxx.x version?
A) Strongly not recommended (might brick your phone in QHSUSB-DLOAD mode). The 7.17.1540.7 firmware posted in this thread is a firmware patch to be flashed over the 6.07.1540.2 firmware version. If you want to update to 7.17.1540.7 firmware then flash the 6.07.1540.2 (full) firmware and then the 7.17.1540.7 ota-firmware.
9) I have another question/comment
A) If its related to files posted here, how to use them or to request other files, go ahead and post your questions. Otherwise the HTC One Q&A sub-forum is the place to post your questions, start a thread there and we will help you. Stay on topic, will not answer questions like "How to s-off, how to unlock, how to root, how to install drivers, issues with adb/fastboot" here.

alray said:
reserved
Click to expand...
Click to collapse
Great Job ...I'll pack this away for later

Will this ROM with a non dev edition Europe HTC One M7?
==EDIT==
All my device info:
INFOversion: 0.5
INFOversion-bootloader: 1.57.0000
INFOversion-baseband: 4T.28.3218.04
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 6.12.161.8
INFOversion-misc: PVT SHIP S-ON
INFOmeid: 00000000000000
INFOproduct: m7_ul
INFOplatform: HBOOT-8064
INFOmodelid: PN0710000
INFOcidnum: VODAP001
INFObattery-status: good
INFObattery-voltage: 4091mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: dirty-6d8a0b9b
INFOhbootpreupdate: 11
INFOgencheckpt: 0
all: Done!

5H1R42 said:
Will this ROM with a non dev edition Europe HTC One M7?
==EDIT==
All my device info:
INFOversion: 0.5
INFOversion-bootloader: 1.57.0000
INFOversion-baseband: 4T.28.3218.04
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 6.12.161.8
INFOversion-misc: PVT SHIP S-ON
INFOmeid: 00000000000000
INFOproduct: m7_ul
INFOplatform: HBOOT-8064
INFOmodelid: PN0710000
INFOcidnum: VODAP001
INFObattery-status: good
INFObattery-voltage: 4091mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: dirty-6d8a0b9b
INFOhbootpreupdate: 11
INFOgencheckpt: 0
all: Done!
Click to expand...
Click to collapse
Yes, it should but you should S-OFF first to get an update. Otherwise you will be stuck in a weird mode.

Newer version of the reset rom (6.07.1540.2) uploaded. See OP for download link.

alray said:
Newer version of the reset rom (6.07.1540.2) uploaded. See OP for download link.
Click to expand...
Click to collapse
It should be noted that the reset rom (6.07.1540.2) is a Great Way to return to Kit Kat if the Lollipop update was not what you expected / wanted
Great work alray, its a very complete post

You should add this RUU Link also
http://dl3.htc.com/application/RUU_...4_10.33E.1718.01L_release_404528_signed_2.exe

yatindroid said:
You should add this RUU Link also
http://dl3.htc.com/application/RUU_...4_10.33E.1718.01L_release_404528_signed_2.exe
Click to expand...
Click to collapse
Thanks but I already added the link 2 weeks ago in post #1.

Added some 7.17.1540.7 files. Ota zip file, stock twrp nandroid backup and stock reset rom will be uploaded in a few hours.

alray said:
Added some 7.17.1540.7 files. Ota zip file, stock twrp nandroid backup and stock reset rom will be uploaded in a few hours.
Click to expand...
Click to collapse
please upload OTA also?

alray said:
Added some 7.17.1540.7 files. Ota zip file, stock twrp nandroid backup and stock reset rom will be uploaded in a few hours.
Click to expand...
Click to collapse
yatindroid said:
please upload OTA also?
Click to expand...
Click to collapse
Patience Its already uploading but AHF is really slow today. Had to restart the upload twice, hope this time it will work.

7.17.1540.7 ota zip file uploaded
TWRP nandroid backup and Reset rom are next
 @yatindroid

Zenkiu!
Tanxs
Thanks
Apreciated it!
Gracias!!!!

7.17.1540.7 TWRP Nandroid backup uploaded.

alray said:
7.17.1540.7 ota zip file uploaded
TWRP nandroid backup and Reset rom are next
@yatindroid
Click to expand...
Click to collapse
I'm not gonna flash it until you show green flag "It's Ok battery life is good comparative to 4.4.3 and much bug free"
Thanks for Uploading :good:

My mid is PN0710000 and super cid.
Do I need to switch to PN0712000 and BS_US??

Unable to install lollipop OTA 7.17.1540.7, HTC m7 Dev(Converted)
Hi alray
I had converted my AT&T Unlocked HTC m7 to US Dev edition sometime back and flashed stock recovery on it.
I was able to receive and install OTA updates and current OS version in 6.07.1540.2.
Today i am able to download the lollipop OTA update version 7.17.1540.7 but unable to install the update. It says "i have changed my phone and unable to install new rom".
How can I proceed further , do I need to reset my ROM ?.
Please advise some help.
Thanks
Sudhev

sudevpdas said:
Hi alray
I had converted my AT&T Unlocked HTC m7 to US Dev edition sometime back and flashed stock recovery on it.
I was able to receive and install OTA updates and current OS version in 6.07.1540.2.
Today i am able to download the lollipop OTA update version 7.17.1540.7 but unable to install the update. It says "i have changed my phone and unable to install new rom".
How can I proceed further , do I need to reset my ROM ?.
Please advise some help.
Thanks
Sudhev
Click to expand...
Click to collapse
I had the exact same problem.

Variant version error are caused by using the wrong MID. Correct MID is PN0712000

[RECOVERY] Stock recovery from Lollipop 5.0.1

Hello,
I am sending the original recovery from the latest update (2.10.401.2) to Android 5.0.1 Lollipop.
The file comes from Desire 820n.
OTA update name: OTA_A51_UL_L50_DESIRE_SENSE60_MR_HTC_Europe_2.10.401.2_R-1.29.401.5
--------------------------------------------------
Download: https://drive.google.com/file/d/0Byyfu6mA9ye_ejhxU0pFdEFCUlE/
--------------------------------------------------
I hope that is useful

deadpolska said:
Hello,
I am sending the original recovery from the latest update (2.10.401.2) to Android 5.0.1 Lollipop.
The file comes from Desire 820n.
OTA update name: OTA_A51_UL_L50_DESIRE_SENSE60_MR_HTC_Europe_2.10.401.2_R-1.29.401.5
--------------------------------------------------
Download: https://drive.google.com/file/d/0Byyfu6mA9ye_ejhxU0pFdEFCUlE/
--------------------------------------------------
I hope that is useful
Click to expand...
Click to collapse
broken links

It well be blocked by the hboot ; So you well recieve a message that refuse this size (29M) <<<< i think the max recovery size is 16M
BUT its too easy to get back your STOCK recovery.img
** extract the firmware.zip from the OTA zip file and rename the firmware.zip to 0PFJIMG.zip and copy it to your sd card and navigate to you hboot **

bricked my phone... can't boot it normal, stuck in recovery mode. Can't boot hboot.

Can You please upload the update because my phone is telling me there is no update available !!!

Help with june security update - or should I say, how to get it?!

Hi,
I have a complete stock moto g4 plus XT1642, with firmware build number NPJS25.93-14-4 (march security update), retgb.
I didn't get the June security update, and I the phone insists that my software is up to date..
I am not interested in rooting my phone. How can I force it to update?
(I also have the same problem with another retgb moto g4 non-plus..).
Thanks!

Yeah, retgb updates seem to be taking a little while to deploy... Like your experience, I was waiting for updates on the retgb channel too... Then I updated using the captured updates on XDA, which appeared to have worked okay
You've got 2 routes:
1) You can download the June 2017 OTA update from here to your device: https://drive.google.com/drive/folders/0B-GUyOfb8OgzR1VrQ1NHWDVmWE0
This is the same update that was on XDA, just mirrored to my Google Drive as the original link does not appear to work.
File name:Blur_Version.25.201.4.athene.retail.en.US.zip
Size: 56 MB
md5 checksum: 4ce250195b2eb71c960ec3b6579bc9d0
Ensure your device is fully updated to NPJS25.93-14-4 (bootloader should be version B1:05), you have a stock recovery, unmodified system and baseband (baseband version should end in .62R), as this update requires the March 2017 update. If your bootloader is still locked, this should all be applicable. Then:
Boot to stock recovery (notes on how to access stock recovery are here: https://forum.xda-developers.com/showpost.php?p=72981796&postcount=58 )
Select 'apply update from SD card'
Locate the Blur_Version.25.201.4.athene.retail.en.US.zip on your device
Install update.
You may wish to wipe cache before rebooting.
Now, you should be updated to June 2017. There's also the September 2017 OTA (requiring the June 2017 patch) which you can apply in the same fashion: https://forum.xda-developers.com/moto-g4-plus/how-to/captured-ota-september-security-patch-t3680367
I successfully flashed the June 2017 OTA onto my XT1642, retgb (so same as yours) that had previously been running on NPJS25.93-14-4 and have had no issues - my network provider, 3 UK, works well
2) If you want to, you can jump straight to the September 2017 stock build, which is running on my XT1642, and this is the method I chose to update (as I was rooted too, so needed a near clean start). I think it should be suitable for the Moto G4 too that you have, but you may wish to check the following stock ROM thread to confirm.
a) Download the September 2017 stock ROM (NPJS25.93-14-10): https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
b)Set up ADB as directed in the above post. Extract the ROM files in the same folder as your ADB terminal (so you should see files like oem.img and bootloader.img mixed with adb.exe and fastboot.exe)
c)If you wish to keep your data and do not need to re-lock your bootloader (i.e. your bootloader is already locked, or unlocked) and are simply updating, you could use the following fastboot commands to keep your data intact. Back up your data just in case your system becomes unstable and needs a factory reset, though I did not notice any corruption of my data. The initial boot was a little slow (presumably to rebuild caches and update links as necessary):
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot reboot
These commands should update your GPT, bootloader, recovery, system and modem to NPJS25.93-14-10, Sept 2017 patch. Though you could edit one of the flashing scripts - provided in the stock ROM thread - to match the above commands, I preferred to manually copy each command and execute the commands, checking each command flashed. As with anything affecting the firmware of your device, take your time in flashing. Using the September 2017 stock ROM, my XT1642 is still running happily with the September security patch (and seems smoother too )
Bear in mind that with the June and September updates, the bootloader is updated to version B1:06. Thus, it makes downgrading risky. From the sounds of it, you're not interested in rooting/downgrading, so this might not be for you anyway. Just a heads up that downgrading from the June or September 2017 stock ROMs (e.g. by flashing the older stock ROM without flashing GPT/bootloader) and then accepting OTA updates may cause a device to hard brick. We have ways of attempting to rescue a device in this state but I really wouldn't like to try them if at all possible.
Good luck whichever route you choose

Difference with Stock firmwares (npn25.137-92 vs npn25.137-93)

I have two Moto G5 Plus. One has the npn25.137-93 build number and RETUS software channel. On the other one, I installed the stock firmware downloaded from:
https://firmware.center/firmware/Mo...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
and now it displays: npn25.137-92 as build number and RETUS as software channel.
The phone with npn25.137-92 works perfectly, but it is not getting any updates to the the Jannuary 2018 security patch (npn25.137-92-4). The phone with npn25.137-93 has an update notification for the Jannuary 2018 security patch (npn25.137-93-4).
Can anyone explain me what's going on with the update notifications?
What is the different between npn25.137-92 and npn25.137-93?
Thanks!

The difference in notifications is likely due to one of your devices having the incorrect build for that software channel.
As far as I recall:
NPN25.137-92 was a build deployed to India, Latin America and possibly other regions.
NPN25.137-93 was deployed to EU, Asia Pacific and the US.
As such, one of your devices, the NPN25.137-93 device, is on the expected build for the retus software channel and is likely recognised by the Motorola servers, hence it's being served an OTA build. However, your other device, on the NPN25.137-92 firmware, is on a build that is not deployed to the retUS channel, and as such, the Motorola servers may not issue an OTA build (else issuing builds to devices on the wrong firmware for that sofware channel may cause a lot of issues), regardless of if the device still functions okay.
I'm not aware of significant differences between -93 and -92, except a different kernel build date and the different deployment of the updates. I'm hoping that you can flash the NPN25.137-93 or NPNS25.137-93-4 firmwares (or newer US specific firmwares) to get you back onto OTA updates, but we've seen that cross flashing firmwares can be risky. It's up to you if you wish to try to crossflash to get back onto the correct firmware, or just manually update the device on NPN25.137-92.
As an aside, this illustrates why it's important to check what firmware build is correct for your device. A useful method is to check reddit (https://www.reddit.com/r/MotoG/ ) or other XDA threads for what OTA updates are being received by a particular region before flashing any firmware (e.g. this thread https://forum.xda-developers.com/g5-plus/how-to/moto-g5-plus-patch-november-npn25-137-92-t3718976 ). If users are receiving a particular latest OTA update for the US, it's a good pointer for what build you should be looking to flash.

Thanks for the detail explanation.
I would definitely like to go back to npn25.137-93. However, I am having a bad time finding that firmware. I checked:
- https://firmware.center/firmware/Motorola/Moto G5 Plus/Stock/
- https://www.getdroidtips.com/moto-g5-plus-stock-firmware-collections-updated/
- https://mirrors.lolinet.com/firmware/moto/potter/official/
but npn25.137-93 or npns25.137-93-4 for XT1687 (retus, carrier unlocked) is not where to be found.
I just noticed that POTTER_NPNS25.137-93-4_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml has been uploaded here: https://forum.xda-developers.com/g5-plus/help/rare-firmware-asia-t3753798
I downloaded it and at a first look it appears to be the complete firmware, so it can be easily flashed with fastboot. However, OP says it's for Asia, so I am not sure...

I am in same boat. Was NPN25.137-93 RETUS but ended up flashing NPN25.137-92 via ADB after trying to update and bricking phone. Now not receiving OTA. I have found some patches but no full firmware for RETUS. Wonder if anyone has TWRP backup that could be restored to get back on track to receive OTA updates?

omino said:
Thanks for the detail explanation.
I would definitely like to go back to npn25.137-93. However, I am having a bad time finding that firmware. I checked:
- https://firmware.center/firmware/Motorola/Moto G5 Plus/Stock/
- https://www.getdroidtips.com/moto-g5-plus-stock-firmware-collections-updated/
- https://mirrors.lolinet.com/firmware/moto/potter/official/
but npn25.137-93 or npns25.137-93-4 for XT1687 (retus, carrier unlocked) is not where to be found.
I just noticed that POTTER_NPNS25.137-93-4_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml has been uploaded here: https://forum.xda-developers.com/g5-plus/help/rare-firmware-asia-t3753798
I downloaded it and at a first look it appears to be the complete firmware, so it can be easily flashed with fastboot. However, OP says it's for Asia, so I am not sure...
Click to expand...
Click to collapse
Yeah, seems that no one has captured the NPN25.137-93 firmware, which is odd given the NPN25.137-92 firmware has been out for a while.
The build numbers for Asia and retUS and retEU appear to be the same (all NPNS25.137-93-4 from the various user reports from each region, e.g. https://forum.xda-developers.com/showpost.php?p=75645812&postcount=34 ) Also, looking at that stock ROM descriptor:
1)Build matches what you need.
2)Baseband matches that for the retUS OTA update for NPNS25.137-93-4 (though the baseband build is the same for NPNS25.137-92-4)
3)Build times for the kernel and this ROM are fairly close ( Tue Jan 23 17:26:00 for the stock ROM, kernel build date for the retUS OTA NPNS25.137-93-4 update is 17:40). Not conclusive, as the NPNS25.137-92-4 kernel got built at 11:31)
4)It's a Blur_Version retail.en.US firmware, which suggests it's for general release.
In summary, it looks like it should work. Of course, the only way to find out is to flash this firmware and hope... At least from the descriptor this looks to be an official firmware from Motorola. Good luck whatever you decide.
Code:
BUILD REQUEST INFO:
SW Version: potter-user 7.0 NPNS25.137-93-4 5 release-keysM8953_37.46.07.47R
MBM Version: C0.8C
Modem Version: M8953_37.46.07.47R
FSG Version: FSG-8953-07.75
Build Fingerprint: motorola/potter/potter:7.0/NPNS25.137-93-4/5:user/release-keys
VERSION INFO FOUND UNDER 'ABOUT PHONE' SCREEN:
System Version: 25.301.5.potter.retail.en.US
Model Number: Moto G (5) Plus
Android Version: 7.0
Baseband Version: M8953_37.46.07.47R
Build Id: NPNS25.137-93-4
SW Display Build ID: NPNS25.137-93-4
Build Date: Tue Jan 23 17:26:00 CST 2018
OTHER MISC VERSION INFO:
Subsidy Lock Config: slcf_rev_d_default_v1.0.nvm
Regulatory Info (eLabel): regulatory_info_default.png
Blur Version: Blur_Version.25.301.5.potter.retail.en.US
Version when read from CPV: potter-user 7.0 NPNS25.137-93-4 5 release-keys
AB Update Enabled: False
Full Treble Enabled: False

echo92 said:
Yeah, seems that no one has captured the NPN25.137-93 firmware, which is odd given the NPN25.137-92 firmware has been out for a while.
The build numbers for Asia and retUS and retEU appear to be the same (all NPNS25.137-93-4 from the various user reports from each region, e.g. https://forum.xda-developers.com/showpost.php?p=75645812&postcount=34 ) Also, looking at that stock ROM descriptor:
1)Build matches what you need.
2)Baseband matches that for the retUS OTA update for NPNS25.137-93-4 (though the baseband build is the same for NPNS25.137-92-4)
3)Build times for the kernel and this ROM are fairly close ( Tue Jan 23 17:26:00 for the stock ROM, kernel build date for the retUS OTA NPNS25.137-93-4 update is 17:40). Not conclusive, as the NPNS25.137-92-4 kernel got built at 11:31)
4)It's a Blur_Version retail.en.US firmware, which suggests it's for general release.
In summary, it looks like it should work. Of course, the only way to find out is to flash this firmware and hope... At least from the descriptor this looks to be an official firmware from Motorola. Good luck whatever you decide.
Code:
BUILD REQUEST INFO:
SW Version: potter-user 7.0 NPNS25.137-93-4 5 release-keysM8953_37.46.07.47R
MBM Version: C0.8C
Modem Version: M8953_37.46.07.47R
FSG Version: FSG-8953-07.75
Build Fingerprint: motorola/potter/potter:7.0/NPNS25.137-93-4/5:user/release-keys
VERSION INFO FOUND UNDER 'ABOUT PHONE' SCREEN:
System Version: 25.301.5.potter.retail.en.US
Model Number: Moto G (5) Plus
Android Version: 7.0
Baseband Version: M8953_37.46.07.47R
Build Id: NPNS25.137-93-4
SW Display Build ID: NPNS25.137-93-4
Build Date: Tue Jan 23 17:26:00 CST 2018
OTHER MISC VERSION INFO:
Subsidy Lock Config: slcf_rev_d_default_v1.0.nvm
Regulatory Info (eLabel): regulatory_info_default.png
Blur Version: Blur_Version.25.301.5.potter.retail.en.US
Version when read from CPV: potter-user 7.0 NPNS25.137-93-4 5 release-keys
AB Update Enabled: False
Full Treble Enabled: False
Click to expand...
Click to collapse
Man, your analysis was helpful and convincing. Thanks a lot!
I decided to pull the trigger and update. I confirm that it works fine on XT1687 on RETUS channel.
In case someone else wants to try, here is the process I followed:
1. Download POTTER_NPNS25.137-93-4_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml from the link in: https://forum.xda-developers.com/g5-...-asia-t3753798
2. Unzip the archive
3. Open a cmd and cd to the POTTER_NPNS25.137-93-4_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml folder
4. Put the phone in bootloader mode (shutdown, then press volume down + power buttons at the same time until the phone turns on)
5. Execute the following fastboot commands (as per flashfile.xml):
Code:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp adspso.bin
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 oem oem.img
fastboot erase cache
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot reboot
I did not erase userdata contrary to what is indicated in flashfile.xml, so I could keep my data. If you want to follow the process as per flashfile.xml, add the following command after erasing cache:
Code:
fastboot erase userdata

After flashing does about phone say RETUS or Asia?

Can confirm it worked for me as well. Thank you both!

Says Europe?

wayne-of3 said:
Says Europe?
Click to expand...
Click to collapse
Looks like the XT1687 has been tested and approved to be sold/used in the EU and the US, at least in terms of radios/electromagnetic radiation and electrical safety. https://www.cnet.com/news/certification-marks-decoded/
I'm not sure if it's important with regards to the firmware, as this build was deployed to the EU and Asia Pacific. All that info shows is that Motorola spent time testing and getting approval from the various safety agencies around the world. On my XT1642 (UK, G4 Plus - just for illustration), I see EU, US, Japan, Malaysia and Australia markings - a combination of where the device was sold and also shows me that I should be okay taking this device to those countries. If I went to the US, my device should not cause radio interference
The important things to look out for with flashing a stock ROM are:
1)Does your device function as expected?
2)Do you get OTA updates and do they install without issue?
If those two apply (we've already seen that 1) is true, 2) will have to wait for another OTA as the firmware is the latest as of writing), then you're likely on the correct build for your device.

Thanks for the clarification. Time will tell when next OTA comes around. Fingers crossed. Still feel better just having latest security.

Someone plz send full rom zip file for indian variant of moto g5 plus for jan security update

wayne-of3 said:
Thanks for the clarification. Time will tell when next OTA comes around. Fingers crossed. Still feel better just having latest security.
Click to expand...
Click to collapse
Have you gotten any OTA security patches since your flash your ROM?

dlong said:
Have you gotten any OTA security patches since your flash your ROM?
Click to expand...
Click to collapse
Yes, that got me back on track. That got me to April sp, but tired of waiting for updates so now on 7.1.2 lineage 14.

wayne-of3 said:
Yes, that got me back on track. That got me to April sp, but tired of waiting for updates so now on 7.1.1 lineage 14.
Click to expand...
Click to collapse
Thanks for the update. I have the same problem with mine which currently stuck on the Nov '17 patch/update/version. I'll have to do what you did. Thanks again.

omino said:
Man, your analysis was helpful and convincing. Thanks a lot!
I decided to pull the trigger and update. I confirm that it works fine on XT1687 on RETUS channel.
In case someone else wants to try, here is the process I followed:
1. Download POTTER_NPNS25.137-93-4_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml from the link in: https://forum.xda-developers.com/g5-...-asia-t3753798
2. Unzip the archive
3. Open a cmd and cd to the POTTER_NPNS25.137-93-4_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml folder
4. Put the phone in bootloader mode (shutdown, then press volume down + power buttons at the same time until the phone turns on)
5. Execute the following fastboot commands (as per flashfile.xml):
Code:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp adspso.bin
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 oem oem.img
fastboot erase cache
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot reboot
I did not erase userdata contrary to what is indicated in flashfile.xml, so I could keep my data. If you want to follow the process as per flashfile.xml, add the following command after erasing cache:
Code:
fastboot erase userdata
Click to expand...
Click to collapse
I had the exact same issue where I relocked my phone with npn25.137-92 and was stuck on Nov 2017 update. Following these steps worked like a charm. After flashing, I received both March and April system updates.

omino,
Thanks for posting the instructions. For others, I also followed the posted instructions and it works. I have a US - Retail, Unlock Moto G5 Plus (from Costco). I had some trouble finding the ROM archive; however, after finding it, the process worked. Note, that when I ran the fastboot commands, for each one, I got an error (or warning?) about "slot-count not found". A google search didn't yield any confirmed information on what it means. However, ignoring it and just continuing with all the commands, the results are fine. After each reboot, every 10 minutes or so it started informing me of new updates (March, then April, then finally June (or July?)). June/July, that's the last one. There doesn't seem to be one after that....
Has anyone else gotten a later security patch June or July for the G5 Plus for the NA RETUS RETAIL ?

I haven't got any update after the June security patch. I think the next one is the 8.1 update. But, as of today, I haven't seen it. Really a shame that Lenovo has not delivered Android 8.1 for NPNS25.137-93-14, RETUS channel.

Lenovo Sucks With Support / Continuing Support (Patches, etc.)
Yeah, pretty crappy of Lenovo. However, when I bought I my phone I wasn't even expecting security patches. Lenovo is very well known for not supporting their products after sale. Like new drivers for a newly released OS. For example, a laptop bought with Win7. But when Win10 comes out, they don't update the drivers so somethings do not work properly. You have to dig around looking at manufacturers and or just try other Lenovo laptop drivers and hope that one works. This phone was sort of a test phone. I would never buy a Lenovo for a daily driver since I don't expect Lenovo to support with security patches or fix bugs in their drivers. For my daily driver, I try to pick to pick LG and Samsung even if it's a entry-level or mid-level phone as I can not justify paying top-dollar for the high-end phones like the S9 or Note 8.

dlong said:
omino,
Has anyone else gotten a later security patch June or July for the G5 Plus for the NA RETUS RETAIL ?
Click to expand...
Click to collapse
Just as an FYI to myself. Today (October 23rd), Lenovo sent out the August security patch (Build number: NPNS25.137-93-18) for Moto G5 plus.

Moto g4 plus hard brick problem

Hello I need immediate help as my Moto G4 plus has hard bricked. Actually yesterday I decided to revert back to stock firmware as I was using a custom Rom on my device. So went into TWRP Recovery. And wiped the system then suddenly the phone turned off, I thought that the battery was dead so plugged in the charger and no screen turned up only the led blinked. So I got to know that it was a hard brick. So I searched on internet and downloaded blankflash . It got flashed then I am trying to flash the partition and boot loader but it is not flash its failing please help me in this matter . Right now I am not able to flash the partition table nor boot loader. And service center is saying to change the motherboard which is costly. And also I forgot to mention I am flashing partition And boot loader from December 2018. Both are failing so please help me in this issue...

What GPT and bootloader are you trying to flash? There are no December 2018 GPT/bootloader files available - the latest available is the April 2018 GPT/bootloader from NPJS25.93-14-18, which you can get from my Google drive: https://drive.google.com/file/d/13AuJkn8eelq-wQ5wp7lNQTf7kT7_lLwI/view
What error are you getting when you flash the GPT/bootloader?

i am already use this April 2018 GPT/bootloader from NPJS25.93-14-18, but didn't work...
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash partition gpt.bin
(bootloader) has-slotartition: not found
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.035s]
writing 'partition'...
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.122s

ajarif said:
i am already use this April 2018 GPT/bootloader from NPJS25.93-14-18, but didn't work...
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash partition gpt.bin
(bootloader) has-slotartition: not found
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.035s]
writing 'partition'...
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.122s
Click to expand...
Click to collapse
Can you confirm that you've copied the April 2018 GPT/bootloader files to your ADB folder and that you're flashing them? I just would like to check that you're not flashing any other GPT/bootloader files as they all have the same name. If these files don't work, we currently don't have any newer files until the Oreo fastboot stock ROM is released.
Did you update to the soak test Oreo build that's been on XDA?

echo92 said:
Can you confirm that you've copied the April 2018 GPT/bootloader files to your ADB folder and that you're flashing them? I just would like to check that you're not flashing any other GPT/bootloader files as they all have the same name. If these files don't work, we currently don't have any newer files until the Oreo fastboot stock ROM is released.
Did you update to the soak test Oreo build that's been on XDA?
Click to expand...
Click to collapse
yes bro i use soak test Oreo and i have some rebooting problem that's way change stock rom (Moto_G4_Plus_XT1643_ATHENE_MPJ24.139-63) and update to 6.0 to 7.0 OTA official updating..

ajarif said:
yes bro i use soak test Oreo and i have some rebooting problem that's way change stock rom (Moto_G4_Plus_XT1643_ATHENE_MPJ24.139-63) and update to 6.0 to 7.0 OTA official updating..
Click to expand...
Click to collapse
Ah, that's a problem then. You've likely still got the stock Oreo bootloader on your device, which is why the Nougat GPT/bootloader are not working. You'd have to wait for the Oreo fastboot ROM to be released (and hope the GPT/bootloader from that fastboot ROM works) or pay for a motherboard.
This is why downgrading from the soak test is ill-advised. I'm surprised the OTA from 6.0.1 to 7.0 didn't hard brick your device anyway, given you downgraded from 8.1 to 6.0, which is risky as the firmware is not designed to be downgraded. I'm wondering if the OTA corrupted your Oreo bootloader...

echo92 said:
Can you confirm that you've copied the April 2018 GPT/bootloader files to your ADB folder and that you're flashing them? I just would like to check that you're not flashing any other GPT/bootloader files as they all have the same name. If these files don't work, we currently don't have any newer files until the Oreo fastboot stock ROM is released.
Did you update to the soak test Oreo build that's been on XDA?
Click to expand...
Click to collapse
echo92 said:
Ah, that's a problem then. You've likely still got the stock Oreo bootloader on your device, which is why the Nougat GPT/bootloader are not working. You'd have to wait for the Oreo fastboot ROM to be released (and hope the GPT/bootloader from that fastboot ROM works) or pay for a motherboard.
This is why downgrading from the soak test is ill-advised. I'm surprised the OTA from 6.0.1 to 7.0 didn't hard brick your device anyway, given you downgraded from 8.1 to 6.0, which is risky as the firmware is not designed to be downgraded. I'm wondering if the OTA corrupted your Oreo bootloader...
Click to expand...
Click to collapse
Thank you bro...now i waiting for official oreo 8.1 stock rom in my device.