Database Users

vz 1060 dev &*^()(**^

I am unlocked
fast boot still works
ok I downloaded the OTA
went to root it and everthign went to hell
the recovery dlahed but would nto entere recoivery
tried a couple differnt twrp
tried cwm
tried other 5.1 recovereis after verifying that they had the same sizes
still wont entere recovery
treid to use the kk factoryu image and "most of it flashed
Code:
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'partition' (32 KB)...
OKAY [ 0.249s]
writing 'partition'...
FAILED (remote failure)
finished. total time: 1.114s
C:\Users\Zookeeper\Desktop\android_sdk\XT1060 Moto X\VZW_212.56.26.ghost_verizon.Verizon.en.US>fastboot flash motoboot motoboot.img
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'motoboot' (1604 KB)...
OKAY [ 0.383s]
writing 'motoboot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.137s
flashed a different boot image and moto boot image form 5.1 t mobile
still no joy
there is a brazil 1053 which I am told Mosley works. but I cant find it
no 1060 factory image yet.
so has anybody created a factory type image yet. NOT a flashable zip. unless I can get twrp working that wont help me.
FAST BOOT WORKS

I'm not 100% sure, but you may have to use "mfastboot" which is the motorola version of fastboot. You can find it with a quick search.

So you were on 5.1 and downgraded to Kit Kat? You can't downgrade the bootloader.

dcooterfrog said:
I am unlocked
fast boot still works
ok I downloaded the OTA
went to root it and everthign went to hell
the recovery dlahed but would nto entere recoivery
tried a couple differnt twrp
tried cwm
tried other 5.1 recovereis after verifying that they had the same sizes
still wont entere recovery
Click to expand...
Click to collapse
I'm going to stop you right there,.
To install an OTA, you need STOCK reocvery. If you have a 3rd party recovery like TWRP or CWM, the OTA process might reboot your phone into Recovery but it will fall to install.
If you have 4.4.4 on your phone, you need to get that exact Recovery.img and flash it. You can't use a 5.1 recovery because the pre-flash validation checks that happen as part of the OTA will likely complain that its not the right version.
dcooterfrog said:
treid to use the kk factoryu image and "most of it flashed
Code:
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'partition' (32 KB)...
OKAY [ 0.249s]
writing 'partition'...
FAILED (remote failure)
finished. total time: 1.114s
C:\Users\Zookeeper\Desktop\android_sdk\XT1060 Moto X\VZW_212.56.26.ghost_verizon.Verizon.en.US>fastboot flash motoboot motoboot.img
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'motoboot' (1604 KB)...
OKAY [ 0.383s]
writing 'motoboot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.137s
flashed a different boot image and moto boot image form 5.1 t mobile
still no joy
there is a brazil 1053 which I am told Mosley works. but I cant find it
no 1060 factory image yet.
so has anybody created a factory type image yet. NOT a flashable zip. unless I can get twrp working that wont help me.
FAST BOOT WORKS
Click to expand...
Click to collapse
You can't downgrade from 4.4.4 to 4.4.2 without risking turning your phone into a brick.
What state is your phone in now? WHat bootloader version does it have on it?
If you have bootloader 30.B7, consider downloading the 4.4.4 XT1060 SBF/FXZ moto has on their web site, and visit -> http://forum.xda-developers.com/moto-x/general/faq-how-to-prepare-ota-update-carriers-t3126425 read post 1 and 2... From Post 2, use the Requirements section, then skip to option 5 to get to stock 4.4.4. then try the OTA

ok lest start over
i was rooted with twrp
i returned to stock and flashed system and recovery from
VZW_212.56.26.ghost_verizon.Verizon.en.US
took both OTAs got onto lolipop seemd to be working
went to flash twrp it said flashed OK
but I could not boot into recovery
tried to laod a cuple differnt recoveries.
then tried to restore the whoel thing
VZW_212.56.26.ghost_verizon.Verizon.en.US
gpt failed
recovery failed
then I tried to install a recovery boot and moto boot frfom a different 5.1. ( after verifying that a couple 5.1 roms had the same size moto boot and boot) flashed but gpt is messed up and wont restore.
either I have broke it or I need a factory image from lollipop
i will try to check my boot loader version. but i bet its updated as a resultof th OTA

got twrp working
does any one have a complete nanadroid of verizon lolipop

got twrp working
does any one have a complete nanadroid of verizon lolipop
slowly am getting back up.
i am not at VZW_212.55.26.ghost_verizon.Verizon.en.US
not 56
Blur_Version.212.166.3.ghost_verizon.Verizon.en.US seems to fail.
ill try flashing system and recovery again.
flashd system, revcovery, boot and motoboot
moto boot failed
update unsuccessful so somthing in moto boot muts ba failing the assert. I think I have a NEWER moto boot.

How did you get TWRP working under 5.1? Someone else had similar issues here:
http://forum.xda-developers.com/moto-x/moto-x-qa/xt1060-recovery-5-1-t3201391

Well that was me... Eventually I got twrp working but I don't know what kind of bastard kitkat lolipop Frankenstein thing it was. Phone will not boot. It is on its way back to motorolla
Sent from my Venue 8 7840 using Tapatalk

Hey bud, when you say the phone won't boot do you mean you can't even boot into the bootloader, or do you mean the screen goes black after the boot animation?
If it's the latter the same thing happened to me today and I know how to fix it.

Won't boot. It went back to Motorola yesterday. Love extended warranty. Backup phone droid incredible 1 with KitKat . loving the 3g
Sent from my ADR6300 using Tapatalk

dcooterfrog said:
Won't boot.
Click to expand...
Click to collapse
I was asking you to clarify what you meant by "won't boot" since that could mean multiple things, but it doesn't matter if you already sent the phone back. Glad you have the extended warranty.

yes extended warranty is great.
sorry by wont boot i meant complete brick, not boot loop. no boo tlogo, no motorolla logo, no bootloader unlocked warning screen. just dark dead, as a doornail.
it wold not even get int eh boot loader.
i have never bricked a phone before. i want trying to downgrade. i have been rooting ( the hard way) since eclair on my lg ally, so not a newb.

[Q] How to find correct stock rom for my model?

I'm sorry of this is a noob question, but I found this: http: // www . filefactory . com/folder/c6cdedc45a775d27 <--- which contained a bunch of stock roms. (I'm a new user, so I can't post links; just remove the spaces)
I bricked my phone with an incompatible SuperSU (stuck on Moto boot screen), so I need to flash 6.0.1 for XT1644 (I think it's unlocked/USA variant but idk)
I tried one that I found called "XT1625-XT1644_ATHENE-RETUS_MPJ24.139-48_cid50_subsidy-DEFAULT_CFC.xml_2.zip" which said that it was 6.0.1, but when I tried to flash, it said:
Code:
C:\Users\Mateo\Downloads\Extracted ROM>mfastboot flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.005s]
writing 'partition'...
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.044s
Apparently, I'm flashing the wrong version of the firmware, but there's like 10 pages of downloads on the filefactory link, and it takes about an hour to download each... Can anyone help me out here?
Thanks!

That firmware should be okay, however that error is normal if you're attempting to flash a build older than the build you currently have/had. I'm guessing you had either MPJ24.139-64 or Nougat on your device before? Your updated bootloader and gpt blocks any downgrades (and thus reduces the chances of bricking your device).
You may be able to flash your older firmware (and downgrading in the process) if you do not flash gpt or bootloader, omit:
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
The rest of your flashing commands should be the same. Of course, verify your bootloader is unlocked (which it should be if you were flashing SuperSU), else you won't be able to downgrade.

Thanks for your quick response!! I downgraded without problem! Also rooted with a compatible SuperSU this time... Then disabled the OTA daemon, so it wouldn't​ auto update, and brick myself, since I'm running an earlier version of the bootloader (correct me if I'm wrong...) Thanks again! :good:

matetoes said:
Thanks for your quick response!! I downgraded without problem! Also rooted with a compatible SuperSU this time... Then disabled the OTA daemon, so it wouldn't​ auto update, and brick myself, since I'm running an earlier version of the bootloader (correct me if I'm wrong...) Thanks again! :good:
Click to expand...
Click to collapse
Woo, good to hear you've got your device working I think with the OTA, you should be okay as the bootloader blocked earlier attempts to downgrade and your subsequent flashes won't have affected those partitions, so it's unlikely you'll brick your device!

Bootloop help.

I decided to return my Sprint variant. So i needed to s-on and lock the bootloader. Problem is, now I have a 1 sec bootloop. Here's what I did. No idea how to fix the problem now.
Here's what I did in order to get the phone back to 100% stock to return it.
Changed the CID (incorrectly) to spsc_001 instead of spcs_001 but iddn't notice that.
Managed to get s-on but couldn’t get bootloader locked again.
reinstalled twrp and SU
booted up
installed sunshine and successfully s-off'd & locked
rebooted to download mode
Did a s-on using fastboot oem writesecureflag 3
rebooted and got a 1 sec bootloop
booted back into download mode and tried to factory reset via fastboot but can’t write the partition
tried to flash twrp, but got a security warning BL-unlocked
Now I'm stuck in a super short .5 second bootloop and can’t access stock recovery.
I try to install the ruu.exe and I get a Customer ID error. I try to install RUU.zip and I get a load_file: could not allocate -2146013644 bytes (which I assume means the partition is full but I can't even erase the userdata.) I also get a Security checking failed GT_CONNECT_FAIL on the download mode screen. I'm totally clueless as to how to get out of this situation. Anyone been here before or knows how to deal with this?

u failed to mention that you changed the CID at some point & when you changed it back, u set it wrong...
honestly, I think you're screwed...I don't know how you'll be able to fix this w/o being able to boot up, can't unlock bootloader, can't use fastboot to flash anything, can't flash RUU...somehow u need to get your CID back to SPCS_001...u may just have to return it in that condition & act ignorant.
any ideas @dottat @Captain_Throwback
vijn said:
Now, my vars are:
(bootloader) kernel: lk
(bootloader) product: htc_pmewhl
(bootloader) version: 1.0
(bootloader) max-download-size: 1579200000
(bootloader) serialno: HT64xxxxx6
(bootloader) current-slot:
(bootloader) imei: 99xxxxx1
(bootloader) version-main: 2.42.651.63
(bootloader) boot-mode: download
(bootloader) version-baseband: [email protected]
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 2PS640000
(bootloader) cid: spsc_001
all:
finished. total time: 0.009s
Click to expand...
Click to collapse

OMJ said:
u failed to mention that you changed the CID at some point & when you changed it back, u set it wrong...
Click to expand...
Click to collapse
You're right, but I had created this post before you guys pointed that out to me in the other thread. So, ya for the record i set the CID as spsc_001 instead of spcs_001 and then locked the bootloader. Great job on my part huh? Anyway, I was afraid you were going to say that I was screwed. I have never made a mistake like this before. So stupid, every letter counts. You'd think I'd have learnt that by now. I'm just hoping there's some really obscure and little-known fix for this that some xda angel will send my way. Hehe. Anyway, thanks for the follow-up OMJ.

vijn said:
You're right, but I had created this post before you guys pointed that out to me in the other thread. So, ya for the record i set the CID as spsc_001 instead of spcs_001 and then locked the bootloader. Great job on my part huh? Anyway, I was afraid you were going to say that I was screwed. I have never made a mistake like this before. So stupid, every letter counts. You'd think I'd have learnt that by now. I'm just hoping there's some really obscure and little-known fix for this that some xda angel will send my way. Hehe. Anyway, thanks for the follow-up OMJ.
Click to expand...
Click to collapse
Well did you attempt to see if HTC dev would give you an unlock token at least?
Sent from my SM-G955U using Tapatalk
---------- Post added at 11:29 PM ---------- Previous post was at 11:28 PM ----------
dottat said:
Well did you attempt to see if HTC dev would give you an unlock token at least?
You might be able manually flash the ruu partitions one by one as well. Have you tried that?
Sent from my SM-G955U using Tapatalk
Click to expand...
Click to collapse
Sent from my SM-G955U using Tapatalk

dottat said:
Well did you attempt to see if HTC dev would give you an unlock token at least?
Click to expand...
Click to collapse
Well, I had already unlocked the phone, rooted, installed other ROMs. When I couldn't unlock the GSM bands, I decided to return the phone so I tried to set the phone back to stock Sprint ROM. I did everything necessary except I put in the wrong CID before relocking the bootloader. So, yes, I had been provided the unlock code by HTC dev. The problem is that I now have a locked bootloader with an incorrect CID, which is why flashing RUUs isn't working.
I don't know if I can flash the RUU partitions with a locked bootloader or if that'll work with an incorrect CID but I'll try anything. Just not sure how to go about doing tht. I'd appreciate any help you can provide. Thanks for the recommendation.

vijn said:
Well, I had already unlocked the phone, rooted, installed other ROMs. When I couldn't unlock the GSM bands, I decided to return the phone so I tried to set the phone back to stock Sprint ROM. I did everything necessary except I put in the wrong CID before relocking the bootloader. So, yes, I had been provided the unlock code by HTC dev. The problem is that I now have a locked bootloader with an incorrect CID, which is why flashing RUUs isn't working.
I don't know if I can flash the RUU partitions with a locked bootloader or if that'll work with an incorrect CID but I'll try anything. Just not sure how to go about doing tht. I'd appreciate any help you can provide. Thanks for the recommendation.
Click to expand...
Click to collapse
Attempt to get a new fresh unlock token and tell me what HTC dev says?
Sent from my SM-G955U using Tapatalk

vijn said:
Well, I had already unlocked the phone, rooted, installed other ROMs. When I couldn't unlock the GSM bands, I decided to return the phone so I tried to set the phone back to stock Sprint ROM. I did everything necessary except I put in the wrong CID before relocking the bootloader. So, yes, I had been provided the unlock code by HTC dev. The problem is that I now have a locked bootloader with an incorrect CID, which is why flashing RUUs isn't working.
I don't know if I can flash the RUU partitions with a locked bootloader or if that'll work with an incorrect CID but I'll try anything. Just not sure how to go about doing tht. I'd appreciate any help you can provide. Thanks for the recommendation.
Click to expand...
Click to collapse
try this, grab the stock boot.img from the firmware zip: https://www.androidfilehost.com/?fid=745425885120723715
copy the boot.img into your sdktools folder
boot into download mode & try to manually flash it
fastboot flash boot boot.img
if that doesn't work, then try this
download the signed firmware: https://www.androidfilehost.com/?fid=745425885120723717
then try one or both of the flashing methods (although I suspect it wont work due to bad CID):
Flash Firmware via download mode (requires micro sd card)....
-rename firmware to 2PS6IMG.zip
-copy 2PS6IMG.zip to ext_sd card
-boot into download mode
-it will scan your ext_sd card, then ask if you want to start the update
-press volume up & let it do it's thing...
Flash Firmware via fastboot, no ext sd card needed...
-rename firmware to firmware.zip
-copy firmware.zip to your adb/fastboot/sdk folder
-boot into download mode
-plug in usb
-type fastboot oem rebootRUU
-when u see the black screen w/ HTC, type fastboot flash zip firmware.zip
-when it's done, type fastboot reboot

dottat said:
Attempt to get a new fresh unlock token and tell me what HTC dev says?
Sent from my SM-G955U using Tapatalk
Click to expand...
Click to collapse
Actually I had tried that since this bootloop issue came up and was given a new .bin file without any problems. The problem is when i tried to flash the .bin file i got this:
sending 'unlocktoken' (0 KB)...
OKAY [ 1.024s]
writing 'unlocktoken'...
(bootloader) flash unlocktoken
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X00, disable unlock
(bootloader) [KillSwitch] oem unlock Turn Off!

vijn said:
Actually I had tried that since this bootloop issue came up and was given a new .bin file without any problems. The problem is when i tried to flash the .bin file i got this:
sending 'unlocktoken' (0 KB)...
OKAY [ 1.024s]
writing 'unlocktoken'...
(bootloader) flash unlocktoken
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X00, disable unlock
(bootloader) [KillSwitch] oem unlock Turn Off!
Click to expand...
Click to collapse
Ok. So your only hope would be to get the ruu files extracted and to manually flash each partition by name. Get it to boot and enable oem unlock. Then flash new token and flash twrp and root and S-off via sunshine. Then fix the cid and do the rest the correct way.
Sent from my SM-G955U using Tapatalk

OMJ said:
try this, grab the stock boot.img from the firmware zip: https://www.androidfilehost.com/?fid=745425885120723715
copy the boot.img into your sdktools folder
boot into download mode & try to manually flash it
fastboot flash boot boot.img
if that doesn't work, then try this
download the signed firmware: https://www.androidfilehost.com/?fid=745425885120723717
then try one or both of the flashing methods (although I suspect it wont work due to bad CID):
Flash Firmware via download mode (requires micro sd card)....
-rename firmware to 2PS6IMG.zip
-copy 2PS6IMG.zip to ext_sd card
-boot into download mode
-it will scan your ext_sd card, then ask if you want to start the update
-press volume up & let it do it's thing...
Flash Firmware via fastboot, no ext sd card needed...
-rename firmware to firmware.zip
-copy firmware.zip to your adb/fastboot/sdk folder
-boot into download mode
-plug in usb
-type fastboot oem rebootRUU
-when u see the black screen w/ HTC, type fastboot flash zip firmware.zip
-when it's done, type fastboot reboot
Click to expand...
Click to collapse
Ok well, I tried these.
The sd card method failed due to the CID mismatch.
The stock boot.img from the firmware zip method gave the following:
sending 'boot' (47977 KB)...
OKAY [ 1.606s]
writing 'boot'...
FAILED (remote: cannot flash this partition in s-on state)
finished. total time: 1.656s
The Firmware flash via fastboot, no ext sd card needed gave this:
sending 'zip' (66180 KB)...
OKAY [ 3.269s]
writing 'zip'...
(bootloader) HOSD CL#857212
(bootloader) ERR CID not matched
(bootloader) ERR [SD_UPDATE_ERR] CID NOT ALLOWED
(bootloader) ERR [SD_UPDATE_ERR] sddownload failed: 7
(bootloader) ERR Update zip file failed.
(bootloader) ERR ZIP ERROR, exit read zip loop
(bootloader) ERR ZIP signature checking failed...
(bootloader) Update zip file OK
(bootloader) ERR ZIP ERROR CODE, 7
(bootloader) [email protected]
FAILED (remote: 7 RU_CID_FAIL cid in android-info mismatched )
finished. total time: 6.456s
I'm screwed aren't I?

dottat said:
Ok. So your only hope would be to get the ruu files extracted and to manually flash each partition by name. Get it to boot and enable oem unlock. Then flash new token and flash twrp and root and S-off via sunshine. Then fix the cid and do the rest the correct way.
Sent from my SM-G955U using Tapatalk
Click to expand...
Click to collapse
OK, this is slightly above my pay-grade. While I've read up on it it always seemed too complicated to try in the past, but this is as good a time as any to learn. Any way you can point me in the right direction on this? Not sure how to do this. I assume I should use the original sprint RUU.zip?

vijn said:
OK, this is slightly above my pay-grade. While I've read up on it it always seemed too complicated to try in the past, but this is as good a time as any to learn. Any way you can point me in the right direction on this? Not sure how to do this. I assume I should use the original sprint RUU.zip?
Click to expand...
Click to collapse
Use the original zip and the instructions/tools provided here (https://forum.xda-developers.com/chef-central/android/tool-universal-htc-ruu-rom-decryption-t3382928) to extract your RUU into the basic partition files. Then flash each one using fastboot by name (eg fastboot flash system system_1.img etc)

dottat said:
Use the original zip and the instructions/tools provided here (https://forum.xda-developers.com/chef-central/android/tool-universal-htc-ruu-rom-decryption-t3382928) to extract your RUU into the basic partition files. Then flash each one using fastboot by name (eg fastboot flash system system_1.img etc)
Click to expand...
Click to collapse
Ok, will try that. You wouldn't happen to know where I can find the zip would you? I always used the exe cause that's what was on the htc site. Not sure where the actul RUU.zip file can be found. I assume I can use the one found here: https://forum.xda-developers.com/sprint-htc-10/development/ruu-sprint-htc-10-1-24-651-3-t3379257
And dottat, OMJ, thanks a lot for your help. It's people like you who make this community what it is.

Hey OMJ,
I grabbed one of your RUU.zip files from your repository on xda ( https://forum.xda-developers.com/sprint-htc-10/development/ruu-sprint-htc-10-1-24-651-3-t3379257 ). The zip files, when extracted, turn into like 25 zips. When I extract 0.zip (in order to extract the entire array) I get a file corrupt errors for a few of the files. Am I missing something? I don't think the files are actually corrupt but this is a recurring error I've gotten on a number of different .zip files that have the string of multiple zips within them. Got any ideas?

vijn said:
Hey OMJ,
I grabbed one of your RUU.zip files from your repository on xda ( https://forum.xda-developers.com/sprint-htc-10/development/ruu-sprint-htc-10-1-24-651-3-t3379257 ). The zip files, when extracted, turn into like 25 zips. When I extract 0.zip (in order to extract the entire array) I get a file corrupt errors for a few of the files. Am I missing something? I don't think the files are actually corrupt but this is a recurring error I've gotten on a number of different .zip files that have the string of multiple zips within them. Got any ideas?
Click to expand...
Click to collapse
u download the 2PS6IMG.zip? If so, u can't extract, it's encrypted. You would need to decrypt using the tool that dottat linked u
BUT, don't waste your time, aint gonna work, u already tried manually flashing the boot.img & u got the failed, s-on error
to confirm, from download mode, u used this cmd? fastboot flash boot boot.img if so, I'm fresh out of ideas....
sending 'boot' (47977 KB)...
OKAY [ 1.606s]
writing 'boot'...
FAILED (remote: cannot flash this partition in s-on state)
finished. total time: 1.656s

OMJ said:
u download the 2PS6IMG.zip? If so, u can't extract, it's encrypted. You would need to decrypt using the tool that dottat linked u
BUT, don't waste your time, aint gonna work, u already tried manually flashing the boot.img & u got the failed, s-on error
to confirm, from download mode, u used this cmd? fastboot flash boot boot.img if so, I'm fresh out of ideas....
sending 'boot' (47977 KB)...
OKAY [ 1.606s]
writing 'boot'...
FAILED (remote: cannot flash this partition in s-on state)
finished. total time: 1.656s
Click to expand...
Click to collapse
Ya, that's what I'd done, but strangely this time I got a different error:
sending 'boot' (47977 KB)...
OKAY [ 2.529s]
writing 'boot'...
(bootloader) HOSD CL#857212
FAILED (remote: 9 RU_SECURITY_FAIL boot and bootloader isn't BL_UNLOCKED)
finished. total time: 3.551s

vijn said:
Ya, that's what I'd done, but strangely this time I got a different error:
sending 'boot' (47977 KB)...
OKAY [ 2.529s]
writing 'boot'...
(bootloader) HOSD CL#857212
FAILED (remote: 9 RU_SECURITY_FAIL boot and bootloader isn't BL_UNLOCKED)
finished. total time: 3.551s
Click to expand...
Click to collapse
odd...u can certainly try to flash the system.img but it will probably give the same error...I can the complete single system.img if u want me to upload or u can use the decrypt tool to decrypt the ruu & flash the individual system imgs

OMJ said:
odd...u can certainly try to flash the system.img but it will probably give the same error...I can the complete single system.img if u want me to upload or u can use the decrypt tool to decrypt the ruu & flash the individual system imgs
Click to expand...
Click to collapse
Would you mind sending the system file? I haven't managed to get the decrypt tool working yet.

vijn said:
Would you mind sending the system file? I haven't managed to get the decrypt tool working yet.
Click to expand...
Click to collapse
https://www.androidfilehost.com/?fid=745425885120734364

Saw your post while looking for an sim unlock for my Japanese HTC 10.
Couldn't resist reading more about your problem tho.
First idea but quite dangerous if done incorrectly..
Try and see if you can change the cid in the ruu.exe with a HEX editor?
If that doesn't work, next try and change the cid of the ruu. zip.
Might be a long shot, but if the files cid's aren't encrypted it might work!

I cant' flash the Stock Rom

Good morning everyone, i have a horrible problem with my Moto G5 Plus XT1685.
I had the stock version NPNS25.137-33-11 of the firmware a couple of days ago, and i decided to unlock my bootloader and flash one custom rom.
Well, i did it but i realize i can't use Android Pay and i need it.
I tried to flash a firmware via ADB but i'm getting this error when i write "fastboot fash XXX XXX.img"
Code:
(bootloader) Security version downgrade
(bootloader) Image o failed validation
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.689s
I would RELOCK my bootloader and FLASH the original firmware but i can't because of this problem. Who can help me?
Thanks in advance

Unfortunately, to lock your device, you'd likely need the NPNS25.137-33-11 stock firmware to flash; generally, only stock firmwares of the same build or newer than what you have will be able to re-lock your device. Currently, I can't see that particular firmware having been released/leaked.
If you need Android Pay, you may wish to look into rooting and using magisk to hide your unlocked bootloader status, which may give you SafetyNet and Android Pay. I'm not familiar with rooting and with magisk on G5 Plus devices though.

kombocore said:
Good morning everyone, i have a horrible problem with my Moto G5 Plus XT1685.
I had the stock version NPNS25.137-33-11 of the firmware a couple of days ago, and i decided to unlock my bootloader and flash one custom rom.
Well, i did it but i realize i can't use Android Pay and i need it.
I tried to flash a firmware via ADB but i'm getting this error when i write "fastboot fash XXX XXX.img"
Code:
(bootloader) Security version downgrade
(bootloader) Image o failed validation
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.689s
I would RELOCK my bootloader and FLASH the original firmware but i can't because of this problem. Who can help me?
Thanks in advance
Click to expand...
Click to collapse
You can flash any potter fastboot you want, upgrade/downgrade, whatever; just don't flash the bootloader or gpt.
As long as you skip these, you won't have any issues.
FYI, flashing a stock fastboot file will NOT relock your bootloader.
echo92 said:
If you need Android Pay, you may wish to look into rooting and using magisk to hide your unlocked bootloader status, which may give you SafetyNet and Android Pay. I'm not familiar with rooting and with magisk on G5 Plus devices though.
Click to expand...
Click to collapse
Agreed, magisk is the way to go for root and solutions for rooted devices on the g5.

Thanks both for the replies, very helpful.
But how about relocking the bootloader? There is nothing I can do? I know you reply me yet about this, but I just wanna be sure..thanks again

kombocore said:
Thanks both for the replies, very helpful.
But how about relocking the bootloader? There is nothing I can do? I know you reply me yet about this, but I just wanna be sure..thanks again
Click to expand...
Click to collapse
Until the NPNS25.137-33-11 or newer stock firmware comes out, I think you cannot re-lock your bootloader (and as I mentioned, I see no sign of such stock firmware). Only stock ROM firmware of the same build or newer than the bootloader patch level on your device can re-lock your device.

Many thanks sir, very helpful.
I think we solved the problem.

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.