Database Develop

Moto G 4G/LTE XT1072 Bricked?

Hi,
i have a Moto G 4G 2015 alias Thea alias Model XT1072 and i cant restore Stock.
I have installed the Downgrade_RETDEALL_XT1068_4.4.4_KXB21.85-14_cid7_CFC and think here i have killed the phone..
i know it is the wrong firmware, i have realized this too late... dont ask why....
so I have downloaded RETDEALL_XT1072_5.0.2_LXB22.46-28_cid7_subsidy-DEFAULT_CFC.xml and RETEUALL_XT1072_5.0.2_LXB22.46-28_cid7_subsidy-DEFAULT_CFC.xml.
But the errors when i try flashing via (m)fastboot are the same
Code:
mfastboot flash partition gpt.bin
fastboot error:
Code:
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
on the display
Code:
version downgraded for primary_gpt
Code:
mfastboot flash motoboot motoboot.img
fastboot error:
Code:
writing 'motoboot'...
(bootloader) Motoboot: Preflash validation for tz
(bootloader) Preflash validation failed
FAILED (remote failure)
on the display
Code:
version downgraded for tz
Code:
mfastboot flash system system.img_sparsechunk.0
fastboot error:
Code:
writing 'system'...
(bootloader) Preflash validation failed
FAILED (remote failure)
on the display
Code:
Image is too large
So why is the Image too large?
getvar all :
(bootloader) version: 0.5
(bootloader) version-bootloader: 4883(*)
(bootloader) product: titan
(bootloader) secure: yes
(bootloader) hwrev: 0x8500
(bootloader) radio: 0x1
(bootloader) emmc: 8GB ID=15 REV=06 PRV=02 TYPE=17
(bootloader) ram: 1024MB Samsung S4 SDRAM DIE=4Gb
(bootloader) cpu: MSM8926
(bootloader) serialno: ZX1C2233HX
(bootloader) cid: 0x0007
(bootloader) channelid: 0x45
(bootloader) uid:
(bootloader) unlocked: yes
(bootloader) securestate: unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) mot_sst: 3
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei:
(bootloader) meid:
(bootloader) date: 03-10-2015
(bootloader) sku: XT1072
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Wed Feb 25 7:52:56 UTC 2015"
(bootloader) ro.build.fingerprint[0]: motorola/titan_retaildsds/titan_um
(bootloader) ro.build.fingerprint[1]: tsds:5.0.2/LXB22.99-16/10:user/rel
(bootloader) ro.build.fingerprint[2]: ease-keys
(bootloader) ro.build.version.full[0]: Blur_Version.22.41.16.titan_retai
(bootloader) ro.build.version.full[1]: ldsds.retaildsdsall.en.03
(bootloader) ro.build.version.qcom[0]: AU_LINUX_ANDROID_LNX.LA.3.5.1_RB1
(bootloader) ro.build.version.qcom[1]: .04.04.02.048.045
(bootloader) version-baseband:
(bootloader) kernel.version[0]: Linux version 3.4.42-g48d3b85 ([email protected]
(bootloader) kernel.version[1]: ilclbld31) (gcc version 4.8 (GCC) ) #1 S
(bootloader) kernel.version[2]: MP PREEMPT Tue Jan 6 10:47:29 CST 2015
(bootloader) sdi.git: git=MBM-NG-V48.83-0-gdc5aeaf
(bootloader) sbl1.git: git=MBM-NG-V48.1D-0-g7e74e90
(bootloader) rpm.git: git=MBM-NG-V48.83-0-g20516c3-dirty
(bootloader) tz.git: git=MBM-NG-V48.83-0-g31cba28
(bootloader) aboot.git: git=MBM-NG-V48.83-0-g67407e2
(bootloader) partition-type: raw
(bootloader) partition-size:
(bootloader) qe: qe 1/1
(bootloader) productid:
(bootloader) sutinfo:
(bootloader) ro.carrier: retde
all: listed above
Is the problem
Code:
(bootloader) product: titan
or any other bootloader settings?
Any ideas?

Hi,
twister_65 said:
i have a Moto G 4G 2015 alias Thea alias Model XT1072 and i cant restore Stock.
I have installed the Downgrade_RETDEALL_XT1068_4.4.4_KXB21.85-14_cid7_CFC and think here i have killed the phone..
i know it is the wrong firmware, i have realized this too late... dont ask why....
so I have downloaded RETDEALL_XT1072_5.0.2_LXB22.46-28_cid7_subsidy-DEFAULT_CFC.xml and RETEUALL_XT1072_5.0.2_LXB22.46-28_cid7_subsidy-DEFAULT_CFC.xml.
But the errors when i try flashing via (m)fastboot are the same
Code:
mfastboot flash partition gpt.bin
fastboot error:
Code:
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
on the display
Code:
version downgraded for primary_gpt
Code:
mfastboot flash motoboot motoboot.img
fastboot error:
Code:
writing 'motoboot'...
(bootloader) Motoboot: Preflash validation for tz
(bootloader) Preflash validation failed
FAILED (remote failure)
on the display
Code:
version downgraded for tz
Code:
mfastboot flash system system.img_sparsechunk.0
fastboot error:
Code:
writing 'system'...
(bootloader) Preflash validation failed
FAILED (remote failure)
on the display
Code:
Image is too large
So why is the Image too large?
getvar all :
(bootloader) version: 0.5
(bootloader) version-bootloader: 4883(*)
(bootloader) product: titan
(bootloader) secure: yes
(bootloader) hwrev: 0x8500
(bootloader) radio: 0x1
(bootloader) emmc: 8GB ID=15 REV=06 PRV=02 TYPE=17
(bootloader) ram: 1024MB Samsung S4 SDRAM DIE=4Gb
(bootloader) cpu: MSM8926
(bootloader) serialno: ZX1C2233HX
(bootloader) cid: 0x0007
(bootloader) channelid: 0x45
(bootloader) uid:
(bootloader) unlocked: yes
(bootloader) securestate: unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) mot_sst: 3
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei:
(bootloader) meid:
(bootloader) date: 03-10-2015
(bootloader) sku: XT1072
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Wed Feb 25 7:52:56 UTC 2015"
(bootloader) ro.build.fingerprint[0]: motorola/titan_retaildsds/titan_um
(bootloader) ro.build.fingerprint[1]: tsds:5.0.2/LXB22.99-16/10:user/rel
(bootloader) ro.build.fingerprint[2]: ease-keys
(bootloader) ro.build.version.full[0]: Blur_Version.22.41.16.titan_retai
(bootloader) ro.build.version.full[1]: ldsds.retaildsdsall.en.03
(bootloader) ro.build.version.qcom[0]: AU_LINUX_ANDROID_LNX.LA.3.5.1_RB1
(bootloader) ro.build.version.qcom[1]: .04.04.02.048.045
(bootloader) version-baseband:
(bootloader) kernel.version[0]: Linux version 3.4.42-g48d3b85 ([email protected]
(bootloader) kernel.version[1]: ilclbld31) (gcc version 4.8 (GCC) ) #1 S
(bootloader) kernel.version[2]: MP PREEMPT Tue Jan 6 10:47:29 CST 2015
(bootloader) sdi.git: git=MBM-NG-V48.83-0-gdc5aeaf
(bootloader) sbl1.git: git=MBM-NG-V48.1D-0-g7e74e90
(bootloader) rpm.git: git=MBM-NG-V48.83-0-g20516c3-dirty
(bootloader) tz.git: git=MBM-NG-V48.83-0-g31cba28
(bootloader) aboot.git: git=MBM-NG-V48.83-0-g67407e2
(bootloader) partition-type: raw
(bootloader) partition-size:
(bootloader) qe: qe 1/1
(bootloader) productid:
(bootloader) sutinfo:
(bootloader) ro.carrier: retde
all: listed above
Is the problem
Code:
(bootloader) product: titan
or any other bootloader settings?
Any ideas?
Click to expand...
Click to collapse
HI,
I have done exactly the same thing as you and facing the same problem while flashing the XT1072 stock firmware.
Could please let me know if you have found any solution.
Thanks

@twister_65 @omarhowlader: U both can now save for a new device, have fun.

LuK1337 said:
@twister_65 @omarhowlader: U both can now save for a new device, have fun.
Click to expand...
Click to collapse
wish you could help with your experience!!!

omarhowlader said:
wish you could help with your experience!!!
Click to expand...
Click to collapse
You can't recover your phone from wrong bootloader

luca020400 said:
You can't recover your phone from wrong bootloader
Click to expand...
Click to collapse
Why not?
I mean, is it a technical limitation? Then why can i install the old one.

twister_65 said:
Why not?
I mean, is it a technical limitation? Then why can i install the old one.
Click to expand...
Click to collapse
Because your device is technically dead xd

luca020400 said:
Because your device is technically dead xd
Click to expand...
Click to collapse
that helps now .......

twister_65 said:
that helps now .......
Click to expand...
Click to collapse
Try to flash motoboot.img from that http://www.filefactory.com/file/2zt...LXB22.99-24_cid12_subsidy-DEFAULT_CFC.xml.zip
It's the only thing that may help you lol.

LuK1337 said:
Try to flash motoboot.img from that http://www.filefactory.com/file/2zt...LXB22.99-24_cid12_subsidy-DEFAULT_CFC.xml.zip
It's the only thing that may help you lol.
Click to expand...
Click to collapse
twister_65 said:
that helps now .......
Click to expand...
Click to collapse
Did it work

Shawn5162 said:
Did it work
Click to expand...
Click to collapse
My device is currently on its way back from a service stadion, but they did not repaired it...

twister_65 said:
My device is currently on its way back from a service stadion, but they did not repaired it...
Click to expand...
Click to collapse
Is that because you broke Motorola's warranty terms of service by unlocking bootloader and flashing? Or is it a lost cause?

Addapp said:
Is that because you broke Motorola's warranty terms of service by unlocking bootloader and flashing? Or is it a lost cause?
Click to expand...
Click to collapse
Did anyone achieved to solve this problem? I am facing exactly the same issue.
The thing is that the Motorola naming is quite confusing and it is very easy to make a mistake between the different Moto Gs, so I flashed the stock ROM of a previous version and when I realized it, it was too late.
I suppose I have the wrong bootloader as it keeps giving me these "image is too large" messages when I try to flash the correct stock rom. I can install CM and other custom roms from TWRP, however at least the camera won't work.
If anyone has found a workaround, please share with us how you do it.

como vc conseguiu pisca? to com o mesmo problema: P

e2_e2 said:
Did anyone achieved to solve this problem? I am facing exactly the same issue.
The thing is that the Motorola naming is quite confusing and it is very easy to make a mistake between the different Moto Gs, so I flashed the stock ROM of a previous version and when I realized it, it was too late.
I suppose I have the wrong bootloader as it keeps giving me these "image is too large" messages when I try to flash the correct stock rom. I can install CM and other custom roms from TWRP, however at least the camera won't work.
If anyone has found a workaround, please share with us how you do it.
Click to expand...
Click to collapse
I've managed to fix my problem, I installed the correct TWRP recovery for my model and managed to install CM THEA and everything is working flawlessly.
The problem is that installing an incorrect recovery will mess the partition, I am sure I can go back to stock now if I use ADB to reflash, but I dont want do go back anymore, there is a bunch of new options avaliable im CM will wont even want the simple stock rom never again. Just Install the correct TWRP for your model and Install a custom rom , it will fix the partition and probably you will be able to reflash to stock using ADB.
This is the correct TWRP for XT1078
https://dl.twrp.me/thea/

twister_65 said:
Hi,
i have a Moto G 4G 2015 alias Thea alias Model XT1072 and i cant restore Stock.
I have installed the Downgrade_RETDEALL_XT1068_4.4.4_KXB21.85-14_cid7_CFC and think here i have killed the phone..
i know it is the wrong firmware, i have realized this too late... dont ask why....
so I have downloaded RETDEALL_XT1072_5.0.2_LXB22.46-28_cid7_subsidy-DEFAULT_CFC.xml and RETEUALL_XT1072_5.0.2_LXB22.46-28_cid7_subsidy-DEFAULT_CFC.xml.
But the errors when i try flashing via (m)fastboot are the same
Code:
mfastboot flash partition gpt.bin
fastboot error:
Code:
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
on the display
Code:
version downgraded for primary_gpt
Code:
mfastboot flash motoboot motoboot.img
fastboot error:
Code:
writing 'motoboot'...
(bootloader) Motoboot: Preflash validation for tz
(bootloader) Preflash validation failed
FAILED (remote failure)
on the display
Code:
version downgraded for tz
Code:
mfastboot flash system system.img_sparsechunk.0
fastboot error:
Code:
writing 'system'...
(bootloader) Preflash validation failed
FAILED (remote failure)
on the display
Code:
Image is too large
So why is the Image too large?
getvar all :
(bootloader) version: 0.5
(bootloader) version-bootloader: 4883(*)
(bootloader) product: titan
(bootloader) secure: yes
(bootloader) hwrev: 0x8500
(bootloader) radio: 0x1
(bootloader) emmc: 8GB ID=15 REV=06 PRV=02 TYPE=17
(bootloader) ram: 1024MB Samsung S4 SDRAM DIE=4Gb
(bootloader) cpu: MSM8926
(bootloader) serialno: ZX1C2233HX
(bootloader) cid: 0x0007
(bootloader) channelid: 0x45
(bootloader) uid:
(bootloader) unlocked: yes
(bootloader) securestate: unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) mot_sst: 3
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei:
(bootloader) meid:
(bootloader) date: 03-10-2015
(bootloader) sku: XT1072
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Wed Feb 25 7:52:56 UTC 2015"
(bootloader) ro.build.fingerprint[0]: motorola/titan_retaildsds/titan_um
(bootloader) ro.build.fingerprint[1]: tsds:5.0.2/LXB22.99-16/10:user/rel
(bootloader) ro.build.fingerprint[2]: ease-keys
(bootloader) ro.build.version.full[0]: Blur_Version.22.41.16.titan_retai
(bootloader) ro.build.version.full[1]: ldsds.retaildsdsall.en.03
(bootloader) ro.build.version.qcom[0]: AU_LINUX_ANDROID_LNX.LA.3.5.1_RB1
(bootloader) ro.build.version.qcom[1]: .04.04.02.048.045
(bootloader) version-baseband:
(bootloader) kernel.version[0]: Linux version 3.4.42-g48d3b85 ([email protected]
(bootloader) kernel.version[1]: ilclbld31) (gcc version 4.8 (GCC) ) #1 S
(bootloader) kernel.version[2]: MP PREEMPT Tue Jan 6 10:47:29 CST 2015
(bootloader) sdi.git: git=MBM-NG-V48.83-0-gdc5aeaf
(bootloader) sbl1.git: git=MBM-NG-V48.1D-0-g7e74e90
(bootloader) rpm.git: git=MBM-NG-V48.83-0-g20516c3-dirty
(bootloader) tz.git: git=MBM-NG-V48.83-0-g31cba28
(bootloader) aboot.git: git=MBM-NG-V48.83-0-g67407e2
(bootloader) partition-type: raw
(bootloader) partition-size:
(bootloader) qe: qe 1/1
(bootloader) productid:
(bootloader) sutinfo:
(bootloader) ro.carrier: retde
all: listed above
Is the problem
Code:
(bootloader) product: titan
or any other bootloader settings?
Any ideas?
Click to expand...
Click to collapse
Hello! I spend my same ... first thing you have to do is fix the bootloader using a command
" fastboot oem fb_mode_clear "
takes 10 seconds , once restored the fastboot install the firmware you had of stock again , I recommend unlock booloader for. I hope you serve , Greetings !

mega_vpr said:
Hello! I spend my same ... first thing you have to do is fix the bootloader using a command
" fastboot oem fb_mode_clear "
takes 10 seconds , once restored the fastboot install the firmware you had of stock again , I recommend unlock booloader for. I hope you serve , Greetings !
Click to expand...
Click to collapse
Did not work for me
mihilux said:
it will fix the partition and probably you will be able to reflash to stock using ADB.
Click to expand...
Click to collapse
Not really. I can use an CM AOSP flawlessly as you mention, but if you need to go back to stock (for example, if your phone hardware breaks), you won't be able to flash to the right stock rom unfortunatelly. Is not a 100% bricked phone but is a technically bricked phone, since NAND has been messed up by flashing accidentally with a wrong ROM. As you say this Motorola versioning system is really an issue in terms of deriving to bricked devices

MiSSigNNo said:
Did not work for me
Not really. I can use an CM AOSP flawlessly as you mention, but if you need to go back to stock (for example, if your phone hardware breaks), you won't be able to flash to the right stock rom unfortunatelly. Is not a 100% bricked phone but is a technically bricked phone, since NAND has been messed up by flashing accidentally with a wrong ROM. As you say this Motorola versioning system is really an issue in terms of deriving to bricked devices
Click to expand...
Click to collapse
I've the same problem, but I can go back to Stock Rom 5.0.2 though ADB and bootloader, the problem is that in the Stock Rom or CM13, CM12 my cellphone dont recognize the SIM card and the wifi =/. Someone with the same problem?

moto g 2014 stuck at logo

dear i have moto g 2014 usa
yesterday the battery was dead and after recharging it, the phone stuck at the logo and reboot
and when i boot to fast boot and choose any option like normal powerup, recovery,factory it reboot and stuck again
at the moto logo.
my device is locked and i tried to flash it using the mfastboot v2 with many official rom
XT1063_TITAN_RETLA_5.0.2_LXB22.99-16.3_cid12_CFC.xml
RETLA_XT1063_4.4.4_KXB21.85-23_cid12_CFC_SVC.xml
adb didn't detect my device as connected, but mfastboot did.
mfastboot.exe oem lock begin> run okay
mfastboot.exe flash partition gpt.bin > run okay
mfastboot.exe flash motoboot motoboot.img > run okay
mfastboot.exe flash logo logo.bin > run okay
mfastboot.exe flash boot boot.img > give me this error
target max-sparse-size: 256MB
sending 'boot' (10200 KB)...
OKAY [ 0.341s]
writing 'boot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.793s
and on the phone screen it say hab check failed for boot , failed to verify hab image boot.
i need your help

douha-it said:
writing 'boot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.793s
and on the phone screen it say hab check failed for boot , failed to verify hab image boot.
i need your help
Click to expand...
Click to collapse
If you're trying to install an older version of Android this error can happen.

Danilo-Sanchez said:
If you're trying to install an older version of Android this error can happen.
Click to expand...
Click to collapse
i don't know what was installed on it, is there is any way to know with fastboot, also i tried kit kat and lollipop, and nothing worked, if you have working link for lollipop or newer rom kindly send me the link
here is the details form fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 4883(*)
(bootloader) product: titan
(bootloader) secure: yes
(bootloader) hwrev: 0x8400
(bootloader) radio: 0x1
(bootloader) emmc: 8GB Toshiba REV=06 PRV=51 TYPE=17
(bootloader) ram: 1024MB Elpida S4 SDRAM DIE=4Gb
(bootloader) cpu: MSM8226 CS
(bootloader) serialno: ZX1D323RBX
(bootloader) cid: 0x0009
(bootloader) channelid: 0x8d
(bootloader) uid: 754DBA060F000000000000000000
(bootloader) unlocked: no
(bootloader) securestate: locked
(bootloader) iswarrantyvoid: no
(bootloader) mot_sst: 0
(bootloader) max-download-size: 536870912
(bootloader) reason: UTAG "bootmode" configured as fastboot
(bootloader) imei: 359297052726493
(bootloader) meid:
(bootloader) date: 10-24-2014
(bootloader) sku: XT1063
(bootloader) battid: (null)
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Fri Jun 19 13:11:50 UTC 2015"
(bootloader) ro.build.fingerprint[0]: motorola/titan_retuglb/titan_umts:
(bootloader) ro.build.fingerprint[1]: 4.4.4/KXB21.85-23/21:user/release-
(bootloader) ro.build.fingerprint[2]: keys
(bootloader) ro.build.version.full[0]: Blur_Version.21.11.23.titan_retug
(bootloader) ro.build.version.full[1]: lb.retuglb.en.US
(bootloader) ro.build.version.qcom[0]: AU_LINUX_ANDROID_LNX.LA.3.5.1_RB1
(bootloader) ro.build.version.qcom[1]: .04.04.02.048.045
(bootloader) version-baseband:
(bootloader) kernel.version[0]: Linux version 3.4.42-g668a77b ([email protected]
(bootloader) kernel.version[1]: ilclbld53) (gcc version 4.7 (GCC) ) #1 S
(bootloader) kernel.version[2]: MP PREEMPT Tue Aug 26 20:21:50 CDT 2014
(bootloader) sdi.git: git=MBM-NG-V48.83-0-gdc5aeaf
(bootloader) sbl1.git: git=MBM-NG-V48.83-0-g22c58e4
(bootloader) rpm.git: git=MBM-NG-V48.83-0-g20516c3-dirty
(bootloader) tz.git: git=MBM-NG-V48.83-0-g31cba28
(bootloader) aboot.git: git=MBM-NG-V48.83-0-g67407e2
(bootloader) partition-type: raw
(bootloader) partition-size:
(bootloader) qe: qe 0/0
(bootloader) productid: ZX1D323RBX
(bootloader) sutinfo:
(bootloader) ro.carrier: retus
all: listed above
finished. total time: 0.073s

douha-it said:
i don't know what was installed on it, is there is any way to know with fastboot, also i tried kit kat and lollipop, and nothing worked, if you have working link for lollipop or newer rom kindly send me the link
here is the details form fastboot getvar all
(bootloader) sku: XT1063
Click to expand...
Click to collapse
Try to install this rom: http://forum.xda-developers.com/showpost.php?p=58585477&postcount=2

Danilo-Sanchez said:
Try to install this rom: http://forum.xda-developers.com/showpost.php?p=58585477&postcount=2
Click to expand...
Click to collapse
thanks it did work

Fastboot flashing_locked, but system modified?

Hi friends,
I have a new Moto X4 1900-1 that I picked up several weeks ago (standard unlocked version, not Amazon), been working beautifully. Stock aside from magisk flashed/bootloader unlocked, still on stock ROM w/stock recovery.
Been having unrelated hardware trouble with it lately, and was trying to restore it to factory settings prior to sending it in for warranty work...but I fear I've bricked it somehow.
Steps taken:
USB debugging disabled in dev settings
OEM unlock disabled in dev settings
Developer options switched off in dev settings
Magisk completely uninstalled within app
Device rebooted via magisk uninstall
On device reboot, I've got the dreaded "Your device is corrupt. It can't be trusted and will not boot." screen, as if the system is still somehow modified. So, I'm now in a state where the bootloader is locked, but the phone won't boot, not even to recovery.
On trying to boot it to TWRP from fastboot, I get the same "Device is corrupt" screen, and if I try to flash partitions (boot, recovery), I get a "(bootloader) flash permission denied" message. I'm unable to unlock the bootloader again via fastboot oem unlock (unlock code) or fastboot flashing unlock, both of which give me this message: "(bootloader) Check 'OEM unlocking' in Android Settings > Developer Options".
I really did like this phone when it was working, which was for all of a couple weeks. I backed up what I needed before starting all of this, so I don't care about data loss, just want to restore it to factory fresh.

taloras said:
Hi friends,
I have a new Moto X4 1900-1 that I picked up several weeks ago (standard unlocked version, not Amazon), been working beautifully. Stock aside from magisk flashed/bootloader unlocked, still on stock ROM w/stock recovery.
Been having unrelated hardware trouble with it lately, and was trying to restore it to factory settings prior to sending it in for warranty work...but I fear I've bricked it somehow.
Steps taken:
USB debugging disabled in dev settings
OEM unlock disabled in dev settings
Developer options switched off in dev settings
Magisk completely uninstalled within app
Device rebooted via magisk uninstall
On device reboot, I've got the dreaded "Your device is corrupt. It can't be trusted and will not boot." screen, as if the system is still somehow modified. So, I'm now in a state where the bootloader is locked, but the phone won't boot, not even to recovery.
On trying to boot it to TWRP from fastboot, I get the same "Device is corrupt" screen, and if I try to flash partitions (boot, recovery), I get a "(bootloader) flash permission denied" message. I'm unable to unlock the bootloader again via fastboot oem unlock (unlock code) or fastboot flashing unlock, both of which give me this message: "(bootloader) Check 'OEM unlocking' in Android Settings > Developer Options".
I really did like this phone when it was working, which was for all of a couple weeks. I backed up what I needed before starting all of this, so I don't care about data loss, just want to restore it to factory fresh.
Click to expand...
Click to collapse
fastboot flash your factory FW

bcrichster said:
fastboot flash your factory FW
Click to expand...
Click to collapse
That's a negative, ghost rider.
https://forum.xda-developers.com/moto-x4/how-to/guide-how-to-flash-official-factory-t3808348 on following this guide, downloading/extracting the stock image and using the included batch file to flash all, every partition tried returns the following error in Fastboot:
sending 'x'
writing (x)
(bootloader) flash permission denied
FAILED (remote failure)

taloras said:
That's a negative, ghost rider.
https://forum.xda-developers.com/moto-x4/how-to/guide-how-to-flash-official-factory-t3808348 on following this guide, downloading/extracting the stock image and using the included batch file to flash all, every partition tried returns the following error in Fastboot:
sending 'x'
writing (x)
(bootloader) flash permission denied
FAILED (remote failure)
Click to expand...
Click to collapse
Try without Window's batch file thing..?? The new FW may have files of a different name that the cmds may need adjusting for..
Sent from my Moto E (4) Plus using Tapatalk

bcrichster said:
Try without Window's batch file thing..?? The new FW may have files of a different name that the cmds may need adjusting for..
Sent from my Moto E (4) Plus using Tapatalk
Click to expand...
Click to collapse
No joy. The batch file starts with "fastboot flash partition gpt.bin" (which works), but the next one, "fastboot flash bootloader bootloader.img" fails thusly:
target reported max download size of 536870912 bytes
sending 'bootloader' (9520 KB)...
OKAY [ 0.218s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) Cancelling 'bootloader.default.xml'
FAILED (remote failure)
finished. total time: 0.272s

taloras said:
No joy. The batch file starts with "fastboot flash partition gpt.bin" (which works), but the next one, "fastboot flash bootloader bootloader.img" fails thusly:
target reported max download size of 536870912 bytes
sending 'bootloader' (9520 KB)...
OKAY [ 0.218s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) Cancelling 'bootloader.default.xml'
FAILED (remote failure)
finished. total time: 0.272s
Click to expand...
Click to collapse
Can you post a screenshot of the file listing of extracted FW? I'd like to do a file-name comparison, maybe helpful
Sent from my Moto E (4) Plus using Tapatalk

bcrichster said:
Can you post a screenshot of the file listing of extracted FW? I'd like to do a file-name comparison, maybe helpful
Sent from my Moto E (4) Plus using Tapatalk
Click to expand...
Click to collapse
Firmware download: PAYTON_OPW28.46-13_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Files:
boot.img
bootloader.img
BTFM.bin
dspso.bin
flashfile.xml
fsg.mbn
gpt.bin
logo.bin
NON-HLOS.bin
oem.img
PAYTON_OPW28.46-13_subsidy-DEFAULT_regulatory-DEFAULT_CFC.info.txt
regulatory_info_default.png
servicefile.xml
slcf_rev_d_default_v1.0.nvm
system.img_sparsechunk.0
system.img_sparsechunk.1
system.img_sparsechunk.2
system.img_sparsechunk.3
system.img_sparsechunk.4
system.img_sparsechunk.5
system.img_sparsechunk.6
system.img_sparsechunk.7
system_other.img

Strange.. I usually just use Linux & add "sudo" to the beginning of flash cmd for perms issues. They may have changed something else, somewhere
Sent from my Moto E (4) Plus using Tapatalk

bcrichster said:
Strange.. I usually just use Linux & add "sudo" to the beginning of flash cmd for perms issues. They may have changed something else, somewhere
Sent from my Moto E (4) Plus using Tapatalk
Click to expand...
Click to collapse
Let me try this from Linux, then. Though, this does seem to be a permissions issue being squawked back at me from Fastboot and not from Windows...

Definitely not a Windows problem.
{
"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"
}

taloras said:
Definitely not a Windows problem.
Click to expand...
Click to collapse
Any possibility there isn't a bootloader partition or maybe it has different name..??
Sent from my Moto E (4) Plus using Tapatalk

Do you remember your latest installed rom? The bootloader you want to flash has to be newer or at least the same, furthermore you can try it on a older machine with USB 2.0 ports, I had the same problem with "permission denied" on USB 3.0/3.1 ports and new mainboards

bcrichster said:
Any possibility there isn't a bootloader partition or maybe it has different name..??
Sent from my Moto E (4) Plus using Tapatalk
Click to expand...
Click to collapse
How can I check for partitions from Fastboot? As I can't even boot to recovery, I'm limited in what I can do to fastboot commands, which unfortunately doesn't include any adb shell use.

Zokhii said:
Do you remember your latest installed rom? The bootloader you want to flash has to be newer or at least the same, furthermore you can try it on a older machine with USB 2.0 ports, I had the same problem with "permission denied" on USB 3.0/3.1 ports and new mainboards
Click to expand...
Click to collapse
I've never touched the ROMS on the device beyond what it came with out of the box, it's using whatever the latest October OTA version is (there was an 11/1 OTA update which I saw a notification for but didn't apply).
fastboot getvar all gives me the following:
Code:
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-uefi-2d29a27-181010
(bootloader) product: payton
(bootloader) board: payton
(bootloader) secure: yes
(bootloader) hwrev: P4
(bootloader) radio: NA
(bootloader) storage-type: eMMC
(bootloader) emmc: 32GB MICRON S0J97Y RV=08 PV=10 FV=4E5630304D483333
(bootloader) ufs: N/A
(bootloader) ram: 3GB MICRON LP4 DIE=12Gb M5=FF M6=02 M7=10 M8=0C
(bootloader) cpu: SDM630 1.0 (2)
(bootloader) serialno: ZY2257LBZP
(bootloader) cid: 0x0032
(bootloader) channelid: 0x8d
(bootloader) uid: 662200ED
(bootloader) securestate: flashing_locked
(bootloader) verity-state: logging (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: xxxxxxxxxxxx
(bootloader) meid:
(bootloader) date: 09-19-2018
(bootloader) sku: XT1900-1
(bootloader) carrier_sku: XT1900-1
(bootloader) battid: SNN5994A
(bootloader) battery-voltage: 4284
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/payton/payton:8.1.0/OPWS2
(bootloader) ro.build.fingerprint[1]: 8.46-21-15/ec37:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.28.261.23.payton.ret
(bootloader) ro.build.version.full[1]: ail.en.US
(bootloader) ro.build.version.qcom: LA.UM.6.4.r1-06900-8x98.0
(bootloader) version-baseband: M660_7042.27.01.74.02R PAYTON_NA_CUST
(bootloader) kernel.version[0]: Linux version 4.4.78-perf-gf993b65 (huds
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x 20150
(bootloader) kernel.version[2]: 123 (prerelease) (GCC) ) #1 SMP PREEMPT
(bootloader) kernel.version[3]: Wed Oct 10 02:52:24 CDT 2018
(bootloader) git:abl: MBM-3.0-uefi-2d29a27-181010
(bootloader) git:xbl: MBM-3.0-uefi-455afa3-181010
(bootloader) git:pmic: MBM-3.0-uefi-455afa3-181010
(bootloader) git:rpm: MBM-3.0-uefi-f14962c-181010
(bootloader) git:tz: MBM-3.0-uefi-9a58d2e-dirty-181010
(bootloader) git:hyp: MBM-3.0-uefi-9a58d2e-dirty-181010
(bootloader) git:devcfg: MBM-3.0-uefi-9a58d2e-dirty-181010
(bootloader) git:cmnlib: MBM-3.0-uefi-9a58d2e-dirty-181010
(bootloader) git:cmnlib64: MBM-3.0-uefi-9a58d2e-dirty-181010
(bootloader) git:keymaster: MBM-3.0-uefi-9a58d2e-dirty-181010
(bootloader) git:prov: MBM-3.0-uefi-9a58d2e-dirty-181010
(bootloader) git:storsec: MBM-3.0-uefi-9a58d2e-dirty-181010
(bootloader) frp-state: protected (77)
(bootloader) ro.carrier: retus
(bootloader) current-slot: _a
(bootloader) running-bl-slot: _a/_a
(bootloader) running-boot-lun: 0
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: no
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 5
(bootloader) slot-retry-count:_b: 0
all: listed above
28.261.23 and 8.46-21-15 look sort of like build numbers; that plus a pretty recent Oct 10th kernel build date leads me to think I'm looking for a 28.46-21-15 or later firmware download, which I'll try to track down. Know of anywhere I could find firmwares that recent?
I have an older desktop with a bunch of usb 2.0 ports on it, I'll give that a whirl too.

taloras said:
I've never touched the ROMS on the device beyond what it came with out of the box, it's using whatever the latest October OTA version is (there was an 11/1 OTA update which I saw a notification for but didn't apply).
fastboot getvar all gives me the following:
Code:
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-uefi-2d29a27-181010
(bootloader) product: payton
(bootloader) board: payton
(bootloader) secure: yes
(bootloader) hwrev: P4
(bootloader) radio: NA
(bootloader) storage-type: eMMC
(bootloader) emmc: 32GB MICRON S0J97Y RV=08 PV=10 FV=4E5630304D483333
(bootloader) ufs: N/A
(bootloader) ram: 3GB MICRON LP4 DIE=12Gb M5=FF M6=02 M7=10 M8=0C
(bootloader) cpu: SDM630 1.0 (2)
(bootloader) serialno: ZY2257LBZP
(bootloader) cid: 0x0032
(bootloader) channelid: 0x8d
(bootloader) uid: 662200ED
(bootloader) securestate: flashing_locked
(bootloader) verity-state: logging (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: xxxxxxxxxxxx
(bootloader) meid:
(bootloader) date: 09-19-2018
(bootloader) sku: XT1900-1
(bootloader) carrier_sku: XT1900-1
(bootloader) battid: SNN5994A
(bootloader) battery-voltage: 4284
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) ro.build.fingerprint[0]: motorola/payton/payton:8.1.0/OPWS2
(bootloader) ro.build.fingerprint[1]: 8.46-21-15/ec37:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.28.261.23.payton.ret
(bootloader) ro.build.version.full[1]: ail.en.US
(bootloader) ro.build.version.qcom: LA.UM.6.4.r1-06900-8x98.0
(bootloader) version-baseband: M660_7042.27.01.74.02R PAYTON_NA_CUST
(bootloader) kernel.version[0]: Linux version 4.4.78-perf-gf993b65 (huds
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x 20150
(bootloader) kernel.version[2]: 123 (prerelease) (GCC) ) #1 SMP PREEMPT
(bootloader) kernel.version[3]: Wed Oct 10 02:52:24 CDT 2018
(bootloader) git:abl: MBM-3.0-uefi-2d29a27-181010
(bootloader) git:xbl: MBM-3.0-uefi-455afa3-181010
(bootloader) git:pmic: MBM-3.0-uefi-455afa3-181010
(bootloader) git:rpm: MBM-3.0-uefi-f14962c-181010
(bootloader) git:tz: MBM-3.0-uefi-9a58d2e-dirty-181010
(bootloader) git:hyp: MBM-3.0-uefi-9a58d2e-dirty-181010
(bootloader) git:devcfg: MBM-3.0-uefi-9a58d2e-dirty-181010
(bootloader) git:cmnlib: MBM-3.0-uefi-9a58d2e-dirty-181010
(bootloader) git:cmnlib64: MBM-3.0-uefi-9a58d2e-dirty-181010
(bootloader) git:keymaster: MBM-3.0-uefi-9a58d2e-dirty-181010
(bootloader) git:prov: MBM-3.0-uefi-9a58d2e-dirty-181010
(bootloader) git:storsec: MBM-3.0-uefi-9a58d2e-dirty-181010
(bootloader) frp-state: protected (77)
(bootloader) ro.carrier: retus
(bootloader) current-slot: _a
(bootloader) running-bl-slot: _a/_a
(bootloader) running-boot-lun: 0
(bootloader) slot-suffixes: _a,_b
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: no
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: no
(bootloader) slot-retry-count:_a: 5
(bootloader) slot-retry-count:_b: 0
all: listed above
28.261.23 and 8.46-21-15 look sort of like build numbers; that plus a pretty recent Oct 10th kernel build date leads me to think I'm looking for a 28.46-21-15 or later firmware download, which I'll try to track down. Know of anywhere I could find firmwares that recent?
I have an older desktop with a bunch of usb 2.0 ports on it, I'll give that a whirl too.
Click to expand...
Click to collapse
Firmwares can be found here (but unfortunately I can't find a 28.46-21-15 build):
https://mirrors.lolinet.com/firmware/moto/payton/official/RETAIL/
https://androidfilehost.com/?w=files&flid=229118&sort_by=date&sort_dir=DESC (official motorola account)
Use these commands:
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 bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.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 system_b system_other.img
fastboot flash oem oem.img
fastboot erase carrier
fastboot erase userdata
fastboot erase ddr
fastboot oem fb_mode_clear
If you get an error with something like "partition not found", change the "fastboot flash modem NON-HLOS.bin" command to "fastboot flash modem_a NON-HLOS.bin" for all commands where you get this error.

Zokhii said:
Firmwares can be found here:
https://mirrors.lolinet.com/firmware/moto/payton/official/RETAIL/
https://androidfilehost.com/?w=files&flid=229118&sort_by=date&sort_dir=DESC (official motorola account)
Hmm but unfortunately I can't find a 28.46-21-15 build...
Click to expand...
Click to collapse
Yeah, the most recent I see is 21-12, with a 10-09 upload date on androidfilehost (earlier than the kernel build date of whatever firmware I'm currently running). Might have to wait a few days until some kind soul uploads something more recent. I'll try this one on that other PC, just to dot my Is and cross my Ts.

taloras said:
Yeah, the most recent I see is 21-12, with a 10-09 upload date on androidfilehost (earlier than the kernel build date of whatever firmware I'm currently running). Might have to wait a few days until some kind soul uploads something more recent. I'll try this one on that other PC, just to dot my Is and cross my Ts.
Click to expand...
Click to collapse
Good luck man, I hope it works

Zokhii said:
Good luck man, I hope it works
Click to expand...
Click to collapse
No luck. flash partition gpt.bin works, but flashing anything after that fails with either "invalid partition name" or "permission denied".
Code:
C:\Users\Paul\Desktop\Peyton>fastboot flash partition gpt.bin
Sending 'partition' (37 KB) OKAY [ 0.000s]
Writing 'partition' (bootloader) Validating 'gpt.default.xml'
(bootloader) Committing 'gpt.default.xml'
(bootloader) - flashing 'gpt_main0.bin' to 'partition:0'
OKAY [ 0.141s]
Finished. Total time: 0.281s
C:\Users\Paul\Desktop\Peyton>fastboot flash bootloader bootloader.img
Sending 'bootloader' (9520 KB) OKAY [ 0.687s]
Writing 'bootloader' (bootloader) Validating 'bootloader.default.xml'
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) Cancelling 'bootloader.default.xml'
FAILED (remote: '')
Finished. Total time: 0.766s
C:\Users\Paul\Desktop\Peyton>fastboot flash modem NON-HLOS.bin
Sending 'modem__a' (94843 KB) OKAY [ 4.970s]
Writing 'modem__a' (bootloader) Invalid partition name modem__a
FAILED (remote: '')
Finished. Total time: 5.157s
C:\Users\Paul\Desktop\Peyton>fastboot flash modem_a NON-HLOS.bin
Sending 'modem_a' (94843 KB) OKAY [ 2.612s]
Writing 'modem_a' (bootloader) flash permission denied
FAILED (remote: '')
Finished. Total time: 2.643s

taloras said:
No luck. flash partition gpt.bin works, but flashing anything after that fails with either "invalid partition name" or "permission denied".
Code:
C:\Users\Paul\Desktop\Peyton>fastboot flash partition gpt.bin
Sending 'partition' (37 KB) OKAY [ 0.000s]
Writing 'partition' (bootloader) Validating 'gpt.default.xml'
(bootloader) Committing 'gpt.default.xml'
(bootloader) - flashing 'gpt_main0.bin' to 'partition:0'
OKAY [ 0.141s]
Finished. Total time: 0.281s
C:\Users\Paul\Desktop\Peyton>fastboot flash bootloader bootloader.img
Sending 'bootloader' (9520 KB) OKAY [ 0.687s]
Writing 'bootloader' (bootloader) Validating 'bootloader.default.xml'
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) flash permission denied
(bootloader) Cancelling 'bootloader.default.xml'
FAILED (remote: '')
Finished. Total time: 0.766s
C:\Users\Paul\Desktop\Peyton>fastboot flash modem NON-HLOS.bin
Sending 'modem__a' (94843 KB) OKAY [ 4.970s]
Writing 'modem__a' (bootloader) Invalid partition name modem__a
FAILED (remote: '')
Finished. Total time: 5.157s
C:\Users\Paul\Desktop\Peyton>fastboot flash modem_a NON-HLOS.bin
Sending 'modem_a' (94843 KB) OKAY [ 2.612s]
Writing 'modem_a' (bootloader) flash permission denied
FAILED (remote: '')
Finished. Total time: 2.643s
Click to expand...
Click to collapse
Damn.. well then let's wait till someone uploads a newer fw and hope that it will work, I am running out of ideas for now..

Are you using the latest version of fastboot?
https://developer.android.com/studio/releases/platform-tools
latest build PAYTON_OPWS28.46-21-16:
https://moto.netlib.re/payton/

Moto G5s Plus no service after 8.1 update

Hello guys, i have a sad new to share, at least for me, i updated via ota my moto g5s plus (XT1802), Brazil, security patch is now 1st december 2018, Android 8.1. Everything works on my phone, except i can not get service, sim chip is recognized but no service bar. My bootloader is locked and i want to flash a stock rom that is viable for my phone. I am afraid to brick it so i wish if any of you could point the rom i should flash here. I already tried many methods, fastboot + restart bootloader, factory reset, nothing works. My last hope, i am not sure of it, is flash the entire stock rom.
My output getvar data is:
C:\Users\asb\Desktop\Moto g5 plu\BOOTLOADER\adb+fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8953-C2.12
(bootloader) product: sanders
(bootloader) board: sanders
(bootloader) secure: yes
(bootloader) hwrev: P4
(bootloader) radio: 4
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG RX1BMB RV=08 PV=07 FV=0000000000000007
(bootloader) ram: 3GB SAMSUNG LP3 DIE=6Gb M5=01 M6=05 M7=00 M8=7B
(bootloader) cpu: MSM8953
(bootloader) serialno: 0040329610
(bootloader) cid: 0x0000
(bootloader) channelid: 0x1b
(bootloader) uid: 2897250500000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 534773760
(bootloader) reason: Volume down key pressed
(bootloader) imei: 359521094360387
(bootloader) meid:
(bootloader) date: 01-22-2019
(bootloader) sku: XT1601
(bootloader) carrier_sku:
(bootloader) battid: SB18C18457
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Tue Feb 10 18: 7:35 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/sanders_nt/sanders_nt:8.1
(bootloader) ro.build.fingerprint[1]: .0/OPSS28.65-36-6/05c0:user/releas
(bootloader) ro.build.fingerprint[2]: e-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.28.211.6.sanders.ret
(bootloader) ro.build.version.full[1]: ail.en.US
(bootloader) ro.build.version.qcom: LA.UM.6.6.r1-08600-89xx.0
(bootloader) version-baseband[0]: M8953_41.50.07.79.01R SANDERS_BRAZILDS
(bootloader) version-baseband[1]: DS_CUST
(bootloader) kernel.version[0]: Linux version 3.18.71-perf-gaeae168 (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x 2015
(bootloader) kernel.version[2]: 0123 (prerelease) (GCC) ) #1 SMP PREEMPT
(bootloader) kernel.version[3]: Wed Dec 5 11:29:59 CST 2018
(bootloader) sbl1.git: git=MBM-NG-VC2.12-0-g698fb2f
(bootloader) rpm.git: git=92e5e21-dirty
(bootloader) tz.git: git=c5fe23f
(bootloader) devcfg.git: git=c5fe23f
(bootloader) keymaster.git: git=c5fe23f
(bootloader) cmnlib.git: git=c5fe23f
(bootloader) cmnlib64.git: git=c5fe23f
(bootloader) prov.git: git=c5fe23f
(bootloader) aboot.git: git=MBM-NG-VC2.12-0-g07ff23c
(bootloader) frp-state: no protection (77)
(bootloader) ro.carrier: retla
(bootloader) current-slot:
(bootloader) slot-suffixes: _a
(bootloader) slot-count: 1
(bootloader) slot-successful:_a: INVALID
(bootloader) slot-successful:_b: INVALID
(bootloader) slot-bootable:_a: INVALID
(bootloader) slot-bootable:_b: INVALID
(bootloader) slot-retry-count:_a: unknown
(bootloader) slot-retry-count:_b: unknown
all: listed above
finished. total time: 0.192s
Thansk in advance

Fire_GT said:
Hello guys, i have a sad new to share, at least for me, i updated via ota my moto g5s plus (XT1802), Brazil, security patch is now 1st december 2018, Android 8.1. Everything works on my phone, except i can not get service, sim chip is recognized but no service bar. My bootloader is locked and i want to flash a stock rom that is viable for my phone. I am afraid to brick it so i wish if any of you could point the rom i should flash here. I already tried many methods, fastboot + restart bootloader, factory reset, nothing works. My last hope, i am not sure of it, is flash the entire stock rom.
My output getvar data is:
C:\Users\asb\Desktop\Moto g5 plu\BOOTLOADER\adb+fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8953-C2.12
(bootloader) product: sanders
(bootloader) board: sanders
(bootloader) secure: yes
(bootloader) hwrev: P4
(bootloader) radio: 4
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG RX1BMB RV=08 PV=07 FV=0000000000000007
(bootloader) ram: 3GB SAMSUNG LP3 DIE=6Gb M5=01 M6=05 M7=00 M8=7B
(bootloader) cpu: MSM8953
(bootloader) serialno: 0040329610
(bootloader) cid: 0x0000
(bootloader) channelid: 0x1b
(bootloader) uid: 2897250500000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 534773760
(bootloader) reason: Volume down key pressed
(bootloader) imei: 359521094360387
(bootloader) meid:
(bootloader) date: 01-22-2019
(bootloader) sku: XT1601
(bootloader) carrier_sku:
(bootloader) battid: SB18C18457
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Tue Feb 10 18: 7:35 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/sanders_nt/sanders_nt:8.1
(bootloader) ro.build.fingerprint[1]: .0/OPSS28.65-36-6/05c0:user/releas
(bootloader) ro.build.fingerprint[2]: e-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.28.211.6.sanders.ret
(bootloader) ro.build.version.full[1]: ail.en.US
(bootloader) ro.build.version.qcom: LA.UM.6.6.r1-08600-89xx.0
(bootloader) version-baseband[0]: M8953_41.50.07.79.01R SANDERS_BRAZILDS
(bootloader) version-baseband[1]: DS_CUST
(bootloader) kernel.version[0]: Linux version 3.18.71-perf-gaeae168 (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x 2015
(bootloader) kernel.version[2]: 0123 (prerelease) (GCC) ) #1 SMP PREEMPT
(bootloader) kernel.version[3]: Wed Dec 5 11:29:59 CST 2018
(bootloader) sbl1.git: git=MBM-NG-VC2.12-0-g698fb2f
(bootloader) rpm.git: git=92e5e21-dirty
(bootloader) tz.git: git=c5fe23f
(bootloader) devcfg.git: git=c5fe23f
(bootloader) keymaster.git: git=c5fe23f
(bootloader) cmnlib.git: git=c5fe23f
(bootloader) cmnlib64.git: git=c5fe23f
(bootloader) prov.git: git=c5fe23f
(bootloader) aboot.git: git=MBM-NG-VC2.12-0-g07ff23c
(bootloader) frp-state: no protection (77)
(bootloader) ro.carrier: retla
(bootloader) current-slot:
(bootloader) slot-suffixes: _a
(bootloader) slot-count: 1
(bootloader) slot-successful:_a: INVALID
(bootloader) slot-successful:_b: INVALID
(bootloader) slot-bootable:_a: INVALID
(bootloader) slot-bootable:_b: INVALID
(bootloader) slot-retry-count:_a: unknown
(bootloader) slot-retry-count:_b: unknown
all: listed above
finished. total time: 0.192s
Thansk in advance
Click to expand...
Click to collapse
Amigo, conseguiu resolver ?

I have the some problem. Any solution?

I just updated to the latest 8.1 OTA, security patches dated april 1 2019 and kernel dated april 26 2019, and have the same problem - SIM detected but no service, can't see any operators if try to select network manually.
Have tried: rebooting, power cycle, change network to 2G then power cycle then change back to 4G.
Anyone know if this can be easily fixed, or if it will do any good to complain to Lenovo?

Fixed it!
Ok I fixed the problem on my phone. I had a hunch that the problem was the "radio ROM" (actually "modem" ROM) wasn't updated correctly, due to the nature of the problem, and the fact that 99% of Moto G5S Plus owners didn't have the same problem. My hunch was correct.
Here's the TL;DR version of the fix:
1. get a copy of the firmware update and extract the file "NON-HLOS.bin"
2. reboot to fastboot mode (hold volume down button while phone turns on or reboots) and connect USB cable
3. do
Code:
fastboot flash modem NON-HLOS.bin
Long version:
1. download and install the Lenovo MOTO Smart Assistant app (I can't post URLs with this new account, and can't remember my original XDA login details from back in the day, and the reset password form is still giving me problems with the image verification (and I'm probably not an AI, I think!))
Now, all I really needed this app for in the end was to download the ROM for me (and fastboot.exe) and if you already have fastboot set up (or if you're not running Windows!) then you'll find it easier to Google for the filename of the ROM: SANDERS_OPS28.65_36_11_cid50_subsidy_DEFAULT_regulatory_DEFAULT_CFC.xml.zip
The app's not bad, though, and I used it to take another backup just in case (originally I thought I'd have to wipe my phone)
2. If you use the app, then go to the Flash section (there's a horizontal navigation bar along the top) and select your Moto G model using the dropdowns, then download the latest ROM.
(The app will guide you into fastboot mode before it will begin the download)
Close the app once it's downloaded and extracted the firmware for you. Don't click the button to begin the recovery process or you'll lose your data unnecessarily.
3. Once downloaded and extracted, I opened a command prompt and:
Code:
C:\ProgramData\LMSA\Download\RomFiles\SANDERS_OPS28.65_36_11_cid50_subsidy_DEFAULT_regulatory_DEFAULT_CFC.xml>..\..\ToolFiles\Fastboot\Fastboot\fastboot.exe flash modem NON-HLOS.bin
target max-download-size: 510MB
sending 'modem' (71941 KB)...
OKAY [ 1.946s]
writing 'modem'...
OKAY [ 2.221s]
finished. total time: 4.169s
C:\ProgramData\LMSA\Download\RomFiles\SANDERS_OPS28.65_36_11_cid50_subsidy_DEFAULT_regulatory_DEFAULT_CFC.xml>..\..\ToolFiles\Fastboot\Fastboot\fastboot.exe erase cache
erasing 'cache'...
OKAY [ 0.031s]
finished. total time: 0.032s
C:\ProgramData\LMSA\Download\RomFiles\SANDERS_OPS28.65_36_11_cid50_subsidy_DEFAULT_regulatory_DEFAULT_CFC.xml>..\..\ToolFiles\Fastboot\Fastboot\fastboot.exe reboot
rebooting...
finished. total time: 0.001s
Now, to me it's pretty clear that there was a problem during the original update, and the modem file wasn't flashed properly for whatever reason.
In my case, I only needed to flash that modem partition, but in your case you might need to flash more partitions. A full list of the commands that an official firmware update runs behind the scenes can be found here by searching, because I can't post links.
I found I didn't need to erase anything (except cache, which I did out of habit)
Hope this helps others with the same problem.

same problem in moto g5 plus after rooting
AaronSpain said:
Ok I fixed the problem on my phone. I had a hunch that the problem was the "radio ROM" (actually "modem" ROM) wasn't updated correctly, due to the nature of the problem, and the fact that 99% of Moto G5S Plus owners didn't have the same problem. My hunch was correct.
Here's the TL;DR version of the fix:
1. get a copy of the firmware update and extract the file "NON-HLOS.bin"
2. reboot to fastboot mode (hold volume down button while phone turns on or reboots) and connect USB cable
3. do
Code:
fastboot flash modem NON-HLOS.bin
Long version:
1. download and install the Lenovo MOTO Smart Assistant app (I can't post URLs with this new account, and can't remember my original XDA login details from back in the day, and the reset password form is still giving me problems with the image verification (and I'm probably not an AI, I think!))
Now, all I really needed this app for in the end was to download the ROM for me (and fastboot.exe) and if you already have fastboot set up (or if you're not running Windows!) then you'll find it easier to Google for the filename of the ROM: SANDERS_OPS28.65_36_11_cid50_subsidy_DEFAULT_regulatory_DEFAULT_CFC.xml.zip
The app's not bad, though, and I used it to take another backup just in case (originally I thought I'd have to wipe my phone)
2. If you use the app, then go to the Flash section (there's a horizontal navigation bar along the top) and select your Moto G model using the dropdowns, then download the latest ROM.
(The app will guide you into fastboot mode before it will begin the download)
Close the app once it's downloaded and extracted the firmware for you. Don't click the button to begin the recovery process or you'll lose your data unnecessarily.
3. Once downloaded and extracted, I opened a command prompt and:
Code:
C:\ProgramData\LMSA\Download\RomFiles\SANDERS_OPS28.65_36_11_cid50_subsidy_DEFAULT_regulatory_DEFAULT_CFC.xml>..\..\ToolFiles\Fastboot\Fastboot\fastboot.exe flash modem NON-HLOS.bin
target max-download-size: 510MB
sending 'modem' (71941 KB)...
OKAY [ 1.946s]
writing 'modem'...
OKAY [ 2.221s]
finished. total time: 4.169s
C:\ProgramData\LMSA\Download\RomFiles\SANDERS_OPS28.65_36_11_cid50_subsidy_DEFAULT_regulatory_DEFAULT_CFC.xml>..\..\ToolFiles\Fastboot\Fastboot\fastboot.exe erase cache
erasing 'cache'...
OKAY [ 0.031s]
finished. total time: 0.032s
C:\ProgramData\LMSA\Download\RomFiles\SANDERS_OPS28.65_36_11_cid50_subsidy_DEFAULT_regulatory_DEFAULT_CFC.xml>..\..\ToolFiles\Fastboot\Fastboot\fastboot.exe reboot
rebooting...
finished. total time: 0.001s
Now, to me it's pretty clear that there was a problem during the original update, and the modem file wasn't flashed properly for whatever reason.
In my case, I only needed to flash that modem partition, but in your case you might need to flash more partitions. A full list of the commands that an official firmware update runs behind the scenes can be found here by searching, because I can't post links.
I found I didn't need to erase anything (except cache, which I did out of habit)
Hope this helps others with the same problem.
Click to expand...
Click to collapse
In my case the fastboot.exe is in romfiles folder only, but I am unable to run fastboot.exe from there, though I can flash that file from adb command. I am having the same issue with my moto g5 plus ie no signal, only my LTE sim works in both sim slots, I have tried flashing before using these command
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
let me try with only non-hlos.bin.. will post result if it work

Not working
I Tried flashing modem from stock rom of oreo and nougat. still no success....

I just replied to your PM, but I'll post publicly here as well:
I no longer have the Moto G5S Plus.
What happened is that after I fixed the problem by flashing the modem file, Motorola release another system update.
I thought "there's no way that TWO system updates can break my phone, is there?" and applied the update.
How wrong I was: broken again. And this time my "flash the modem" fix didn't do anything. Neither did anything else I tried.
Motorola support said to return it to a service centre for repair, but it was going to cost me a fair bit of money to do that, because the phone was just out of its two year warranty period.
So here's how I 'fixed' my problem:
I bought a Realme 5 with 128GB of storage for €160
And this is also a story of how Motorola and Lenovo have missed out on any future business from me and the people whom I buy technology for:
After initially being happy with my Moto G5S Plus, a year later I bought my girlfriend a Moto G6. Her next phone will not be a Motorola.
My girlfriend's mother needed a new phone a couple of months ago. I bought her a Realme 5 as well. If I hadn't had such a bad experience with Motorola, their so-called support, and their habit of breaking phones with system updates then I would have bought a Moto G7.
My girlfriend needed a new laptop last month. I definitely didn't buy her a Lenovo.
I'm going to need a new laptop next year. Guess which brand I'm going to stay away from?
Friends and family turn to me for advice when purchasing technology. Lenovo/Motorola have lost out on approximately €1500 of revenue in less than a year. Over the next ten years I estimate they will miss out on at least €10,000, probably more, due to me bad-mouthing them to everyone I know.
It's a shame, I remembered when Motorola were a good company - a friend of mine in the UK worked for them back in the late 1990s and early 2000s and had great things to say about them.
My Milestone 2 was one of my all-time favourite phones - a wonderful portable SSH terminal.
Rant over. Good luck with your Moto G phone. It's good while it works. Just don't apply any updates, and remember the saying "If it ain't broke, don't fix it".

I figured out the problem, actually its something to with the pairing between my particular sim(airtel) and my mobile. Other sim (including airtel's) works fine in my mobile both at 2g and 4g network. And also my sim works well in other mobile. Only solution in my case is to get a new sim, or airtel fix it from there end. Getting new sim is difficult in this lockdown as most stores are closed. I called customer care and they said they have transferred my case to the technical team. Let's see if they fix the problem. I regret not checking my mobile network with other sims, unnecessarily flashed and resetted my mobile multiple times. Thanks for the reply

AaronSpain said:
Fixed it!
Ok I fixed the problem on my phone. I had a hunch that the problem was the "radio ROM" (actually "modem" ROM) wasn't updated correctly, due to the nature of the problem, and the fact that 99% of Moto G5S Plus owners didn't have the same problem. My hunch was correct.
Here's the TL;DR version of the fix:
1. get a copy of the firmware update and extract the file "NON-HLOS.bin"
2. reboot to fastboot mode (hold volume down button while phone turns on or reboots) and connect USB cable
3. do
Code:
fastboot flash modem NON-HLOS.bin
Long version:
1. download and install the Lenovo MOTO Smart Assistant app (I can't post URLs with this new account, and can't remember my original XDA login details from back in the day, and the reset password form is still giving me problems with the image verification (and I'm probably not an AI, I think!))
Now, all I really needed this app for in the end was to download the ROM for me (and fastboot.exe) and if you already have fastboot set up (or if you're not running Windows!) then you'll find it easier to Google for the filename of the ROM: SANDERS_OPS28.65_36_11_cid50_subsidy_DEFAULT_regulatory_DEFAULT_CFC.xml.zip
The app's not bad, though, and I used it to take another backup just in case (originally I thought I'd have to wipe my phone)
2. If you use the app, then go to the Flash section (there's a horizontal navigation bar along the top) and select your Moto G model using the dropdowns, then download the latest ROM.
(The app will guide you into fastboot mode before it will begin the download)
Close the app once it's downloaded and extracted the firmware for you. Don't click the button to begin the recovery process or you'll lose your data unnecessarily.
3. Once downloaded and extracted, I opened a command prompt and:
Code:
C:\ProgramData\LMSA\Download\RomFiles\SANDERS_OPS28.65_36_11_cid50_subsidy_DEFAULT_regulatory_DEFAULT_CFC.xml>..\..\ToolFiles\Fastboot\Fastboot\fastboot.exe flash modem NON-HLOS.bin
target max-download-size: 510MB
sending 'modem' (71941 KB)...
OKAY [ 1.946s]
writing 'modem'...
OKAY [ 2.221s]
finished. total time: 4.169s
C:\ProgramData\LMSA\Download\RomFiles\SANDERS_OPS28.65_36_11_cid50_subsidy_DEFAULT_regulatory_DEFAULT_CFC.xml>..\..\ToolFiles\Fastboot\Fastboot\fastboot.exe erase cache
erasing 'cache'...
OKAY [ 0.031s]
finished. total time: 0.032s
C:\ProgramData\LMSA\Download\RomFiles\SANDERS_OPS28.65_36_11_cid50_subsidy_DEFAULT_regulatory_DEFAULT_CFC.xml>..\..\ToolFiles\Fastboot\Fastboot\fastboot.exe reboot
rebooting...
finished. total time: 0.001s
Now, to me it's pretty clear that there was a problem during the original update, and the modem file wasn't flashed properly for whatever reason.
In my case, I only needed to flash that modem partition, but in your case you might need to flash more partitions. A full list of the commands that an official firmware update runs behind the scenes can be found here by searching, because I can't post links.
I found I didn't need to erase anything (except cache, which I did out of habit)
Hope this helps others with the same problem.
Click to expand...
Click to collapse
P:\Xperia\Mi\Redmi note 5\Tools>fastboot flash modem NON-HLOS.bin
target reported max download size of 534773760 bytes
sending 'modem' (108209 KB)...
OKAY [ 2.818s]
writing 'modem'...
FAILED (remote: size too large)
finished. total time: 2.840s

i softbricked moto g6 :(

so here i am, after 2 days of scrutinizing every corner of the internet, looking for solution. i had my moto g6 on pie but out of curiosity i wanted try out different roms and here is what happened:
- after ive successfully unlocked the oem lock, installed twrp and tried to install different roms just to run into error 255 and such i gave up and thought **** it lets go back to original rom, so i fired up fastboot and put back oreo that i downloaded from here, the splashscreen however was still bearing the 'device has been unlocked and cant be trusted' message, so i thought i would put back the oem lock and then formatted the device... ooops and thats when i started having these problems.
- since then i cant install any rom - stock or mod (i was however successful in flashing twrp back on the phone)
- fastboot says FLASHING_LOCKED and having tried maybe 6 different stock roms i noticed that i can flash these two lines without problems:
./fastboot flash partition gpt.bin
./fastboot flash bootloader bootloader.img
but anything after that is giving me (bootloader) flash permission denied FAILED (remote failure) in powershell
so to sum it up: i can boot into fastboot or twrp but i cant do much anything else
ive seemed to exhaust every remote advice out there and really dont know what to do anymore
any of you guys could point me in the right direction? or is the phone done and done?
here is the fastboot var list
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-ali_retail-e4c1135-190306
(bootloader) product: ali
(bootloader) board: ali
(bootloader) secure: yes
(bootloader) hwrev: PVT2
(bootloader) radio: 4
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SKHYNIX HBG4a2 RV=08 PV=A5 FV=00000000000000A5
(bootloader) ram: 3GB SKHYNIX LP3 DIE=8Gb M5=06 M6=04 M7=00 M8=5F
(bootloader) cpu: SDM450
(bootloader) cid: 0x0032
(bootloader) channelid: 0x00
(bootloader) uid: 1A46B50700000000000000000000
(bootloader) securestate: flashing_locked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 534773760
(bootloader) reason: UTAG "bootmode" configured as fastboot
(bootloader) meid:
(bootloader) date: 11-26-2018
(bootloader) sku: XT1925-4
(bootloader) carrier_sku: XT1925-4
(bootloader) battid: SB18C15119
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Sun May 26 14: 4:32 UTC 2019"
(bootloader) ro.build.fingerprint[0]: motorola/ali_n/ali_n:8.0.0/OPS27.8
(bootloader) ro.build.fingerprint[1]: 2-19-4/a37fd:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.27.21.a37fd.ali.reta
(bootloader) ro.build.version.full[1]: il.en.US
(bootloader) ro.build.version.qcom: LA.UM.6.6.r1-04400-89xx.0
(bootloader) version-baseband: M450_14.640.10.36R ALI_EMEA_CUST
(bootloader) kernel.version[0]: Linux version 3.18.71-perf-g5870245 (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x 2015
(bootloader) kernel.version[2]: 0123 (prerelease) (GCC) ) #1 SMP PREEMPT
(bootloader) kernel.version[3]: Fri Mar 9 11:12:11 CST 2018
(bootloader) sbl1.git: MBM-2.1-ali_retail-0d2031d-190306
(bootloader) rpm.git: MBM-2.1-ali_retail-576a4d4-190306
(bootloader) tz.git: MBM-2.1-ali_retail-4636043-190306
(bootloader) devcfg.git: MBM-2.1-ali_retail-4636043-190306
(bootloader) keymaster.git: MBM-2.1-ali_retail-4636043-190306
(bootloader) cmnlib.git: MBM-2.1-ali_retail-4636043-190306
(bootloader) cmnlib64.git: MBM-2.1-ali_retail-4636043-190306
(bootloader) prov.git: MBM-2.1-ali_retail-4636043-190306
(bootloader) aboot.git: MBM-2.1-ali_retail-e4c1135-190306
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: retgb
(bootloader) current-slot:
(bootloader) slot-suffixes: _a
(bootloader) slot-count: 1
(bootloader) slot-successful:_a: INVALID
(bootloader) slot-successful:_b: INVALID
(bootloader) slot-bootable:_a: INVALID
(bootloader) slot-bootable:_b: INVALID
(bootloader) slot-retry-count:_a: unknown
(bootloader) slot-retry-count:_b: unknown
all: listed above
thx
Peter

You have locked bootloader you cant flash anything ....unlock it, flash rom (optionaly flash stock rom and lock booloader)
mybea you can try "fastboot flashing unlock"

najjannajS650 said:
You have locked bootloader you cant flash anything ....unlock it, flash rom (optionaly flash stock rom and lock booloader)
mybea you can try "fastboot flashing unlock"
Click to expand...
Click to collapse
thanks, i think ive already tried that already before,
here is a recap of what happens when i type in fastboot flashing unlock
- (bootloader) WARNING: This command erases all user data. (bootloader) Please re-run this command to continue.
- (bootloader) Check 'Allow OEM Unlock' in Android Settings > Developer (bootloader) Options.
i dont have any rom installed so i cant get into developers options and allow OEM unlock
edited: and if i try ./fastboot oem unlock
i get
... (bootloader) invalid boot state
:crying:

nobody has solution to this? really????

delosanto said:
nobody has solution to this? really????
Click to expand...
Click to collapse
You don't need to unlock the bootloader to flash the stock firmware. The reason gpt.bin and the bootloader won't flash is because you're attempting to downgrade them. Flash everything in your firmware in order and if something fails to flash, then just skip it and go to the next item in line. It should still work.

Spaceminer said:
You don't need to unlock the bootloader to flash the stock firmware. The reason gpt.bin and the bootloader won't flash is because you're attempting to downgrade them. Flash everything in your firmware in order and if something fails to flash, then just skip it and go to the next item in line. It should still work.
Click to expand...
Click to collapse
thanks man but those two files are the only files that seem to flash.. the rest is giving flashing denied error
after digging around xda even more ive realized im in the same situation as the guy: https://forum.xda-developers.com/moto-x4/help/fastboot-flashinglocked-modified-t3872215
ive managed to brick it real good this time, quoting a nice chap who tried to help him: "You DID lock the keys... not so much in a car with bulletproof windows... but in a nuclear-resistant TANK"
im really sad at this point, i didnt even have the phone for a week and even being it a budget phone i really really liked it..
RIP moto g6 you were my first... bricked... phone :crying:

delosanto said:
thanks man but those two files are the only files that seem to flash.. the rest is giving flashing denied error
after digging around xda even more ive realized im in the same situation as the guy: https://forum.xda-developers.com/moto-x4/help/fastboot-flashinglocked-modified-t3872215
ive managed to brick it real good this time, quoting a nice chap who tried to help him: "You DID lock the keys... not so much in a car with bulletproof windows... but in a nuclear-resistant TANK"
im really sad at this point, i didnt even have the phone for a week and even being it a budget phone i really really liked it..
RIP moto g6 you were my first... bricked... phone :crying:
Click to expand...
Click to collapse
I don't think you're bricked just yet. From fastboot try the following commands;
fastboot oem fb_mode_set
fastboot format -w
fastboot erase userdata
fastboot erase cache
fastboot erase DRR
Then try flashing your firmware again. Also, something would help is running the command;
fastboot getvar all
And posting what that says. DO NOT include your MEID number. I don't need it and it should never be given out.

Spaceminer said:
I don't think you're bricked just yet. From fastboot try the following commands;
fastboot oem fb_mode_set
fastboot format -w
fastboot erase userdata
fastboot erase cache
fastboot erase DRR
Then try flashing your firmware again. Also, something would help is running the command;
fastboot getvar all
And posting what that says. DO NOT include your MEID number. I don't need it and it should never be given out.
Click to expand...
Click to collapse
ok, here goes nothing
fastboot oem fb_mode_set returns OKAY [ 0.002s] finished. total time: 0.003s
fastboot format -w returns fastboot: usage: expected argument
fastboot erase userdata returns (bootloader) Permission denied FAILED (remote failure) finished. total time: 0.004s
fastboot erase cache returns (bootloader) Permission denied FAILED (remote failure)
fastboot erase DRR returns (bootloader) Permission denied FAILED (remote failure)
getvarall info:
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-ali_retail-e4c1135-190306
(bootloader) product: ali
(bootloader) board: ali
(bootloader) secure: yes
(bootloader) hwrev: PVT2
(bootloader) radio: 4
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SKHYNIX HBG4a2 RV=08 PV=A5 FV=00000000000000A5
(bootloader) ram: 3GB SKHYNIX LP3 DIE=8Gb M5=06 M6=04 M7=00 M8=5F
(bootloader) cpu: SDM450
(bootloader) cid: 0x0032
(bootloader) channelid: 0x00
(bootloader) uid: 1A46B50700000000000000000000
(bootloader) securestate: flashing_locked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 534773760
(bootloader) reason: Fall-through from charger boot mode
(bootloader) date: 11-26-2018
(bootloader) sku: XT1925-4
(bootloader) carrier_sku: XT1925-4
(bootloader) battid: SB18C15119
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Tue Jan 22 19:25:37 UTC 2019"
(bootloader) ro.build.fingerprint[0]: motorola/ali_n/ali_n:8.0.0/OPS27.8
(bootloader) ro.build.fingerprint[1]: 2-19-4/a37fd:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.27.21.a37fd.ali.reta
(bootloader) ro.build.version.full[1]: il.en.US
(bootloader) ro.build.version.qcom: LA.UM.6.6.r1-04400-89xx.0
(bootloader) version-baseband: M450_14.640.10.36R ALI_EMEA_CUST
(bootloader) kernel.version[0]: Linux version 3.18.71-perf-g5870245 (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x 2015
(bootloader) kernel.version[2]: 0123 (prerelease) (GCC) ) #1 SMP PREEMPT
(bootloader) kernel.version[3]: Fri Mar 9 11:12:11 CST 2018
(bootloader) sbl1.git: MBM-2.1-ali_retail-0d2031d-190306
(bootloader) rpm.git: MBM-2.1-ali_retail-576a4d4-190306
(bootloader) tz.git: MBM-2.1-ali_retail-4636043-190306
(bootloader) devcfg.git: MBM-2.1-ali_retail-4636043-190306
(bootloader) keymaster.git: MBM-2.1-ali_retail-4636043-190306
(bootloader) cmnlib.git: MBM-2.1-ali_retail-4636043-190306
(bootloader) cmnlib64.git: MBM-2.1-ali_retail-4636043-190306
(bootloader) prov.git: MBM-2.1-ali_retail-4636043-190306
(bootloader) aboot.git: MBM-2.1-ali_retail-e4c1135-190306
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: retgb
(bootloader) current-slot:
(bootloader) slot-suffixes: _a
(bootloader) slot-count: 1
(bootloader) slot-successful:_a: INVALID
(bootloader) slot-successful:_b: INVALID
(bootloader) slot-bootable:_a: INVALID
(bootloader) slot-bootable:_b: INVALID
(bootloader) slot-retry-count:_a: unknown
(bootloader) slot-retry-count:_b: unknown
all: listed above

delosanto said:
ok, here goes nothing
fastboot oem fb_mode_set returns OKAY [ 0.002s] finished. total time: 0.003s
fastboot format -w returns fastboot: usage: expected argument
fastboot erase userdata returns (bootloader) Permission denied FAILED (remote failure) finished. total time: 0.004s
fastboot erase cache returns (bootloader) Permission denied FAILED (remote failure)
fastboot erase DRR returns (bootloader) Permission denied FAILED (remote failure)
getvarall info:
(bootloader) version: 0.5
(bootloader) version-bootloader: MBM-2.1-ali_retail-e4c1135-190306
(bootloader) product: ali
(bootloader) board: ali
(bootloader) secure: yes
(bootloader) hwrev: PVT2
(bootloader) radio: 4
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SKHYNIX HBG4a2 RV=08 PV=A5 FV=00000000000000A5
(bootloader) ram: 3GB SKHYNIX LP3 DIE=8Gb M5=06 M6=04 M7=00 M8=5F
(bootloader) cpu: SDM450
(bootloader) cid: 0x0032
(bootloader) channelid: 0x00
(bootloader) uid: 1A46B50700000000000000000000
(bootloader) securestate: flashing_locked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 534773760
(bootloader) reason: Fall-through from charger boot mode
(bootloader) date: 11-26-2018
(bootloader) sku: XT1925-4
(bootloader) carrier_sku: XT1925-4
(bootloader) battid: SB18C15119
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Tue Jan 22 19:25:37 UTC 2019"
(bootloader) ro.build.fingerprint[0]: motorola/ali_n/ali_n:8.0.0/OPS27.8
(bootloader) ro.build.fingerprint[1]: 2-19-4/a37fd:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.27.21.a37fd.ali.reta
(bootloader) ro.build.version.full[1]: il.en.US
(bootloader) ro.build.version.qcom: LA.UM.6.6.r1-04400-89xx.0
(bootloader) version-baseband: M450_14.640.10.36R ALI_EMEA_CUST
(bootloader) kernel.version[0]: Linux version 3.18.71-perf-g5870245 (hud
(bootloader) kernel.version[1]: son[email protected]) (gcc version 4.9.x 2015
(bootloader) kernel.version[2]: 0123 (prerelease) (GCC) ) #1 SMP PREEMPT
(bootloader) kernel.version[3]: Fri Mar 9 11:12:11 CST 2018
(bootloader) sbl1.git: MBM-2.1-ali_retail-0d2031d-190306
(bootloader) rpm.git: MBM-2.1-ali_retail-576a4d4-190306
(bootloader) tz.git: MBM-2.1-ali_retail-4636043-190306
(bootloader) devcfg.git: MBM-2.1-ali_retail-4636043-190306
(bootloader) keymaster.git: MBM-2.1-ali_retail-4636043-190306
(bootloader) cmnlib.git: MBM-2.1-ali_retail-4636043-190306
(bootloader) cmnlib64.git: MBM-2.1-ali_retail-4636043-190306
(bootloader) prov.git: MBM-2.1-ali_retail-4636043-190306
(bootloader) aboot.git: MBM-2.1-ali_retail-e4c1135-190306
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: retgb
(bootloader) current-slot:
(bootloader) slot-suffixes: _a
(bootloader) slot-count: 1
(bootloader) slot-successful:_a: INVALID
(bootloader) slot-successful:_b: INVALID
(bootloader) slot-bootable:_a: INVALID
(bootloader) slot-bootable:_b: INVALID
(bootloader) slot-retry-count:_a: unknown
(bootloader) slot-retry-count:_b: unknown
all: listed above
Click to expand...
Click to collapse
What country are you in? You have a software mismatch going on. It says your carrier is RETGB which is Great Britain, but your Blur version is saying Retail US.

Spaceminer said:
What country are you in? You have a software mismatch going on. It says your carrier is RETGB which is Great Britain, but your Blur version is saying Retail US.
Click to expand...
Click to collapse
im in the uk, please dont say there is still hope

delosanto said:
im in the uk, please dont say there is still hope
Click to expand...
Click to collapse
Yes there is! I think you need this firmware. https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
If that doesn't work, try this one.
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Special note: Do not use any scripts, batch files, or rsdlite to flash it. Use adb/fastboot and enter everything manually. Read the flash file carefully, and be sure to use the command fastboot oem fb_mode_set before starting, and when you finish flashing, enter the commands, fastboot oem fb_mode_clear then fastboot reboot after. Wait and it should start to encrypt then reboot and finish encrypting.

Spaceminer said:
Yes there is! I think you need this firmware. https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
If that doesn't work, try this one.
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Special note: Do not use any scripts, batch files, or rsdlite to flash it. Use adb/fastboot and enter everything manually. Read the flash file carefully, and be sure to use the command fastboot oem fb_mode_set before starting, and when you finish flashing, enter the commands, fastboot oem fb_mode_clear then fastboot reboot after. Wait and it should start to encrypt then reboot and finish encrypting.
Click to expand...
Click to collapse
i did exactly as you said, getting the same results as before
the first two files gpt and bootloader seem to flash fine but the rest is giving me the same error (bootloader) flash permission denied FAILED (remote failure)
PS C:\Users\okratio\Desktop\platform-tools> ./fastboot oem fb_mode_set
...
OKAY [ 0.003s]
finished. total time: 0.003s
PS C:\Users\okratio\Desktop\platform-tools> ./fastboot flash partition gpt.bin
target reported max download size of 534773760 bytes
sending 'partition' (45 KB)...
OKAY [ 0.000s]
writing 'partition'...
(bootloader) Validating 'gpt.default.xml'
(bootloader) Committing 'gpt.default.xml'
(bootloader) - flashing 'gpt_main0.bin' to 'partition:0'
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
OKAY [ 0.078s]
finished. total time: 0.078s
PS C:\Users\okratio\Desktop\platform-tools> ./fastboot flash bootloader bootloader.img
target reported max download size of 534773760 bytes
sending 'bootloader' (7419 KB)...
OKAY [ 0.212s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) Committing 'bootloader.default.xml'
(bootloader) - flashing 'emmc_appsboot.mbn' to 'aboot'
(bootloader) - flashing 'rpm.mbn' to 'rpm'
(bootloader) - flashing 'tz.mbn' to 'tz'
(bootloader) - flashing 'devcfg.mbn' to 'devcfg'
(bootloader) - flashing 'cmnlib.mbn' to 'cmnlib'
(bootloader) - flashing 'cmnlib64.mbn' to 'cmnlib64'
(bootloader) - flashing 'keymaster.mbn' to 'keymaster'
(bootloader) - flashing 'prov.mbn' to 'prov'
(bootloader) - flashing 'sbl1.mbn' to 'sbl1'
OKAY [ 0.417s]
finished. total time: 0.630s
PS C:\Users\okratio\Desktop\platform-tools> ./fastboot flash modem NON-HLOS.bin
target reported max download size of 534773760 bytes
sending 'modem' (62664 KB)...
OKAY [ 1.660s]
writing 'modem'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 1.665s
PS C:\Users\okratio\Desktop\platform-tools> ./fastboot flash fsg fsg.mbn
target reported max download size of 534773760 bytes
sending 'fsg' (7972 KB)...
OKAY [ 0.219s]
writing 'fsg'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 0.219s
i tried to flashed the files exactly in the order they appear in .info file
./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 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 system system.img_sparsechunk.5
./fastboot flash system system.img_sparsechunk.6
./fastboot flash system system.img_sparsechunk.7
./fastboot flash system system.img_sparsechunk.8
./fastboot flash system system.img_sparsechunk.9
./fastboot flash vendor vendor.img_sparsechunk.0
./fastboot flash vendor vendor.img_sparsechunk.1
./fastboot flash oem oem.img
./fastboot erase cache
./fastboot erase userdata
./fastboot erase ddr
./fastboot oem fb_mode_clear
./fastboot reboot

delosanto said:
i did exactly as you said, getting the same results as before
the first two files gpt and bootloader seem to flash fine but the rest is giving me the same error (bootloader) flash permission denied FAILED (remote failure)
PS C:\Users\okratio\Desktop\platform-tools> ./fastboot oem fb_mode_set
...
OKAY [ 0.003s]
finished. total time: 0.003s
PS C:\Users\okratio\Desktop\platform-tools> ./fastboot flash partition gpt.bin
target reported max download size of 534773760 bytes
sending 'partition' (45 KB)...
OKAY [ 0.000s]
writing 'partition'...
(bootloader) Validating 'gpt.default.xml'
(bootloader) Committing 'gpt.default.xml'
(bootloader) - flashing 'gpt_main0.bin' to 'partition:0'
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
OKAY [ 0.078s]
finished. total time: 0.078s
PS C:\Users\okratio\Desktop\platform-tools> ./fastboot flash bootloader bootloader.img
target reported max download size of 534773760 bytes
sending 'bootloader' (7419 KB)...
OKAY [ 0.212s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) Committing 'bootloader.default.xml'
(bootloader) - flashing 'emmc_appsboot.mbn' to 'aboot'
(bootloader) - flashing 'rpm.mbn' to 'rpm'
(bootloader) - flashing 'tz.mbn' to 'tz'
(bootloader) - flashing 'devcfg.mbn' to 'devcfg'
(bootloader) - flashing 'cmnlib.mbn' to 'cmnlib'
(bootloader) - flashing 'cmnlib64.mbn' to 'cmnlib64'
(bootloader) - flashing 'keymaster.mbn' to 'keymaster'
(bootloader) - flashing 'prov.mbn' to 'prov'
(bootloader) - flashing 'sbl1.mbn' to 'sbl1'
OKAY [ 0.417s]
finished. total time: 0.630s
PS C:\Users\okratio\Desktop\platform-tools> ./fastboot flash modem NON-HLOS.bin
target reported max download size of 534773760 bytes
sending 'modem' (62664 KB)...
OKAY [ 1.660s]
writing 'modem'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 1.665s
PS C:\Users\okratio\Desktop\platform-tools> ./fastboot flash fsg fsg.mbn
target reported max download size of 534773760 bytes
sending 'fsg' (7972 KB)...
OKAY [ 0.219s]
writing 'fsg'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 0.219s
Click to expand...
Click to collapse
It looks like you have the correct firmware. If you didn't then the bootloader shouldn't be able to flash. You aren't being blocked by frp either, so that's not the problem. I'll do some research and see if I can find a way to fix this. It should allow you to flash stock firmware since it's signed by Motorola. This is a tough one.
If you're using Windows and have not tried this already, try opening the command prompt with administrator privileges. If you happen to be using Windows 10, make sure that you're using the older cmd and not powershell. If you have not tried using a different usb port, this might be worth a shot. I'd try ports that are directly connected to the motherboard. Try USB 2.0 and 3.0 if you have both. Also be sure to use the original USB cord that it came with if you have it. I'll see what I can dig up in the meantime.
---------- Post added at 07:09 PM ---------- Previous post was at 06:57 PM ----------
@delosanto
Are you able to boot or flash twrp?

Spaceminer said:
It looks like you have the correct firmware. If you didn't then the bootloader shouldn't be able to flash. You aren't being blocked by frp either, so that's not the problem. I'll do some research and see if I can find a way to fix this. It should allow you to flash stock firmware since it's signed by Motorola. This is a tough one.
If you're using Windows and have not tried this already, try opening the command prompt with administrator privileges. If you happen to be using Windows 10, make sure that you're using the older cmd and not powershell. If you have not tried using a different usb port, this might be worth a shot. I'd try ports that are directly connected to the motherboard. Try USB 2.0 and 3.0 if you have both. Also be sure to use the original USB cord that it came with if you have it. I'll see what I can dig up in the meantime.
Click to expand...
Click to collapse
thank you! i think i must have read and tried everything there is out there trying to bring the poor little fella back to life.. ive tried different ports, methods, ROMs, different cables, tomorrow im gonna try what youre suggesting - the older cmd but i doubt it will make any difference, since i was able to flash and re-flash this phone just fine before i somehow managed to **** up the oem lock with no possibility to unlock it since there is no OS.
yes, im able to totally erase twrp (pic of android with red triangle and NO COMMAND) and then bring it back by booting twrp and consequently flashing twrp so it's there back under recovery mode

Spaceminer said:
Yes there is! I think you need this firmware. https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
If that doesn't work, try this one.
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Special note: Do not use any scripts, batch files, or rsdlite to flash it. Use adb/fastboot and enter everything manually. Read the flash file carefully, and be sure to use the command fastboot oem fb_mode_set before starting, and when you finish flashing, enter the commands, fastboot oem fb_mode_clear then fastboot reboot after. Wait and it should start to encrypt then reboot and finish encrypting.
Click to expand...
Click to collapse
I haven't seen the encrypting screen on Pie... I've only seen it on Oreo.

Ragarianok said:
I haven't seen the encrypting screen on Pie... I've only seen it on Oreo.
Click to expand...
Click to collapse
the last OS that was successfully flashed was Oreo

delosanto said:
the last OS that was successfully flashed was Oreo
Click to expand...
Click to collapse
I'm not sure if I was reading that correctly, but are you able to boot twrp? If so, try formatting /data and running fix permissions. If you can only boot the stock recovery (red triangle), try factory resetting. You can pull up the menu in stock recovery by pressing Power+Volume Up at the "no command" screen. If you can reset the phone through either method, then try flashing the firmware again. Maybe a stupid question, but have you tried flashing the last Oreo RETGB xt1925-4 firmware already? (There's a few different RETGB firmwares.)

Spaceminer said:
I'm not sure if I was reading that correctly, but are you able to boot twrp? If so, try formatting /data and running fix permissions. If you can only boot the stock recovery (red triangle), try factory resetting. You can pull up the menu in stock recovery by pressing Power+Volume Up at the "no command" screen. If you can reset the phone through either method, then try flashing the firmware again. Maybe a stupid question, but have you tried flashing the last Oreo RETGB xt1925-4 firmware already? (There's a few different RETGB firmwares.)
Click to expand...
Click to collapse
twrp runs fine, what i cant get rid of is the flashing_locked message in fastboot..
this i think prevents flashing ANYTHING onto the phone except two files:
./fastboot flash partition gpt.bin
./fastboot flash bootloader bootloader.img
flashing any other file returns permission denied
and ive tried at least 6 different roms

delosanto said:
twrp runs fine, what i cant get rid of is the flashing_locked message in fastboot..
this i think prevents flashing ANYTHING onto the phone except two files:
./fastboot flash partition gpt.bin
./fastboot flash bootloader bootloader.img
flashing any other file returns permission denied
and ive tried at least 6 different roms
Click to expand...
Click to collapse
Try flashing this boot.img in fastboot. If it fails, try using TWRP.

Spaceminer said:
Try flashing this boot.img in fastboot. If it fails, try using TWRP.
Click to expand...
Click to collapse
but when i try to flash the stock rom, again i get past the first two files gpt.bin and bootloader.bit but the rest is giving me the same error
(bootloader) flash permission denied
FAILED (remote failure)
but then it crashes back to fastboot
and i even did a clean windows installation today