Database Users

(XT1572) SIM Card not recognized

Hi there! I'm new in this forum. Yesterday I had the chance to buy this good looking phone and I am pretty glad. Unfortunately, I soft bricked trying to flash rom just because i am very impatient. Luckily, I could solved it by flashing stock, and i am actually using ACIP Rom. The thing is that after all this process I don't have my SIM Card recognized by the phone. I am not used to Motorola phones but I see that modem drivers is a thing and I don't know if it has something to do with.
Please, any help is appreciated.
btw, this is what i wrote in the command prompt when flashed stock
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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
Click to expand...
Click to collapse

This is not the proper flashing method... The proper method using the latest firmware is:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash 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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash bluetooth BTFM.bin
fastboot erase cache
fastboot erase userdata
fastboot oem fb_mode_clear
fastboot reboot
They key is to use the latest image, and verify OKAY response after each step, if you don't get that then repeat the step up to 3 times. If it still fails there is more going on than it appears.
Your symptoms indicate an invalid radio stack (bold italicized above) or incorrect radio version. Remember that firmware images are region specific, a firmware from India and one from Brazil or the EU are different even though all are for XT1572, you must use the correct one for your device.

acejavelin said:
This is not the proper flashing method... The proper method using the latest firmware is:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash 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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash bluetooth BTFM.bin
fastboot erase cache
fastboot erase userdata
fastboot oem fb_mode_clear
fastboot reboot
They key is to use the latest image, and verify OKAY response after each step, if you don't get that then repeat the step up to 3 times. If it still fails there is more going on than it appears.
Your symptoms indicate an invalid radio stack (bold italicized above) or incorrect radio version. Remember that firmware images are region specific, a firmware from India and one from Brazil or the EU are different even though all are for XT1572, you must use the correct one for your device.
Click to expand...
Click to collapse
I will trying flashing again via fastboot but i am seeking the latest firm so I found this web:
https://firmware.center/firmware/Motorola/Moto X Style/Stock/XT1572/
How may I know which is the last one AND which is for my device?

C:\xxx\xxx\Desktop\Nueva carpeta (2)>fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.005s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.367s
Click to expand...
Click to collapse
This is where always fail

papo_blue7 said:
This is where always fail
Click to expand...
Click to collapse
Well documented... You are trying to downgrade which isn't really supported.
Still, you can skip bootloader and gpt.bin if you have to, but my answer still holds, it's a modem issue.
Add your screen shot of bottom of About phone (scroll to bottom and screen shot) and output of "fastboot getvar all" in bootloader in order to help more.

acejavelin said:
Well documented... You are trying to downgrade which isn't really supported.
Still, you can skip bootloader and gpt.bin if you have to, but my answer still holds, it's a modem issue.
Add your screen shot of bottom of About phone (scroll to bottom and screen shot) and output of "fastboot getvar all" in bootloader in order to help more.
Click to expand...
Click to collapse
I think I bricked the phone again after flashing XT1572_CLARK_RETLA_6.0_MPH24.49-18_cid12_subsidy-DEFAULT_CFC.xml. It's stucked in the bootloader unlocked warning. Previously I flashed:
XT1572_CLARK_RETLA-MSTLA_6.0_MPH24.49-18_cid12_subsidy-MOVSTLA_CFC.xml
XT1572_CLARK_RETLA-MSTCL_6.0_MPHS24.49-18-4_cid12_subsidy-MOVSTLA_CFC.xml
I will post the screens right away.
btw, is this useful?
https://forum.xda-developers.com/showpost.php?p=62819858&postcount=15

HELP!
Well, it's stucked in this screen. What can I do!? I freak out

papo_blue7 said:
HELP!
Well, it's stucked in this screen. What can I do!? I freak out
Click to expand...
Click to collapse
Remember, first boot is 15+ minutes... Factory reset in recovery and try again. Those are pretty old versions, give me a bit and I'll get you a newer link.
---------- Post added at 06:18 PM ---------- Previous post was at 06:06 PM ----------
Latest available stock firmware is here
Without seeing the output of 'fastboot getvar all' I can't really say for certain which is the right version, there is a retail single SIM (18-4) and dual SIM version (18-8), and a Movistar subsidized version (18-4).

acejavelin said:
Remember, first boot is 15+ minutes... Factory reset in recovery and try again. Those are pretty old versions, give me a bit and I'll get you a newer link.
---------- Post added at 06:18 PM ---------- Previous post was at 06:06 PM ----------
Latest available stock firmware is here
Without seeing the output of 'fastboot getvar all' I can't really say for certain which is the right version, there is a retail single SIM (18-4) and dual SIM version (18-8), and a Movistar subsidized version (18-4).
Click to expand...
Click to collapse
Here it is
C:\Users\Pablo\Desktop\Nueva carpeta (2)>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8992-A0.48
(bootloader) product: clark
(bootloader) board: clark
(bootloader) secure: yes
(bootloader) hwrev: 0x83C0
(bootloader) radio: 0x1
(bootloader) emmc: 32GB Samsung REV=07 PRV=02 TYPE=57 PNM=BWBD3R
(bootloader) ram[0]: 3072MB Micron S8 SDRAM DIE=6Gb M5=x3 M6=x0 M7=x0 M8
(bootloader) ram[1]: =x3B
(bootloader) cpu: MSM8992
(bootloader) serialno: ZY223T4GRZ
(bootloader) cid: 0x0007
(bootloader) channelid: 0x40
(bootloader) uid: 82796F011E000000000000000000
(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: 358209070447326
(bootloader) meid:
(bootloader) date: 12-15-2016
(bootloader) sku: XT1572
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Thu Apr 21 4:57:14 UTC 2016"
(bootloader) ro.build.fingerprint[0]: motorola/clark_retla/clark:6.0/MPH
(bootloader) ro.build.fingerprint[1]: S24.49-18-4/1:user/release-keys
(bootloader) ro.build.version.full[0]: Blur_Version.24.221.5.clark_retla
(bootloader) ro.build.version.full[1]: .retla.en.01
(bootloader) ro.build.version.qcom: <not found>
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 3.10.84-perf-g329ac5f (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x-goog
(bootloader) kernel.version[2]: le 20140827 (prerelease) (GCC) ) #1 SMP
(bootloader) kernel.version[3]: PREEMPT Thu Apr 21 03:51:14 CDT 2016
(bootloader) sbl1.git: git=MBM-NG-VA0.48-0-g86c6f70
(bootloader) rpm.git: git=90a41be
(bootloader) tz.git: git=5fa1c0c-dirty
(bootloader) hyp.git: git=5fa1c0c-dirty
(bootloader) sdi.git: git=52a3f93
(bootloader) pmic.git: git=MBM-NG-VA0.48-0-g86c6f70
(bootloader) aboot.git: git=MBM-NG-VA0.48-0-g8c942c6
(bootloader) qe: qe 0/0
(bootloader) frp-state: no protection (75)
(bootloader) ro.carrier: reteu
all: listed above
finished. total time: 0.116s
Click to expand...
Click to collapse

acejavelin said:
Remember, first boot is 15+ minutes... Factory reset in recovery and try again. Those are pretty old versions, give me a bit and I'll get you a newer link.
---------- Post added at 06:18 PM ---------- Previous post was at 06:06 PM ----------
Latest available stock firmware is here
Without seeing the output of 'fastboot getvar all' I can't really say for certain which is the right version, there is a retail single SIM (18-4) and dual SIM version (18-8), and a Movistar subsidized version (18-4).
Click to expand...
Click to collapse
Here it is
C:\Users\Pablo\Desktop\Nueva carpeta (2)>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8992-A0.48
(bootloader) product: clark
(bootloader) board: clark
(bootloader) secure: yes
(bootloader) hwrev: 0x83C0
(bootloader) radio: 0x1
(bootloader) emmc: 32GB Samsung REV=07 PRV=02 TYPE=57 PNM=BWBD3R
(bootloader) ram[0]: 3072MB Micron S8 SDRAM DIE=6Gb M5=x3 M6=x0 M7=x0 M8
(bootloader) ram[1]: =x3B
(bootloader) cpu: MSM8992
(bootloader) serialno: ZY223T4GRZ
(bootloader) cid: 0x0007
(bootloader) channelid: 0x40
(bootloader) uid: 82796F011E000000000000000000
(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: 358209070447326
(bootloader) meid:
(bootloader) date: 12-15-2016
(bootloader) sku: XT1572
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Thu Apr 21 4:57:14 UTC 2016"
(bootloader) ro.build.fingerprint[0]: motorola/clark_retla/clark:6.0/MPH
(bootloader) ro.build.fingerprint[1]: S24.49-18-4/1:user/release-keys
(bootloader) ro.build.version.full[0]: Blur_Version.24.221.5.clark_retla
(bootloader) ro.build.version.full[1]: .retla.en.01
(bootloader) ro.build.version.qcom: <not found>
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 3.10.84-perf-g329ac5f (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x-goog
(bootloader) kernel.version[2]: le 20140827 (prerelease) (GCC) ) #1 SMP
(bootloader) kernel.version[3]: PREEMPT Thu Apr 21 03:51:14 CDT 2016
(bootloader) sbl1.git: git=MBM-NG-VA0.48-0-g86c6f70
(bootloader) rpm.git: git=90a41be
(bootloader) tz.git: git=5fa1c0c-dirty
(bootloader) hyp.git: git=5fa1c0c-dirty
(bootloader) sdi.git: git=52a3f93
(bootloader) pmic.git: git=MBM-NG-VA0.48-0-g86c6f70
(bootloader) aboot.git: git=MBM-NG-VA0.48-0-g8c942c6
(bootloader) qe: qe 0/0
(bootloader) frp-state: no protection (75)
(bootloader) ro.carrier: reteu
all: listed above
finished. total time: 0.116s
Click to expand...
Click to collapse
btw, my carrier is Movistar
Also, if I try to get Recovery Mode it says No command and a "dead" android.

papo_blue7 said:
Here it is
Click to expand...
Click to collapse
So is this a Latin American variant or a European variant?
The firmware you are flashing is for Latin America, but the device seems to be the European variant (note: ro.carrier: reteu entry)
Is this an original LA or EU device?
Although your carrier is Movistar, that doesn't mean you need to use a Movistar specific ROM unless it is a carrier branded device.
From "Dead Andy" to get to the recovery menu, hold POWER and tap Vol Up quickly.

acejavelin said:
So is this a Latin American variant or a European variant?
The firmware you are flashing is for Latin America, but the device seems to be the European variant (note: ro.carrier: reteu entry)
Is this an original LA or EU device?
Although your carrier is Movistar, that doesn't mean you need to use a Movistar specific ROM unless it is a carrier branded device.
From "Dead Andy" to get to the recovery menu, hold POWER and tap Vol Up quickly.
Click to expand...
Click to collapse
Ok, it may be european but I bought it here in Argentina. And I am not sure but is not carrier branded so it's ok.
I could get recovery mode now!

papo_blue7 said:
Ok, it may be european. I bought it here in Argentina. And I am not sure but is not carrier branded so it's ok.
I could get recovery mode now!
Click to expand...
Click to collapse
Did you purchase it new or used?
It is kind of important we determine what the original version of this is... if you flash a LA ROM to an EU device, it could very well give you the issues you see, where the SIM is not recognized, because the radio firmware doesn't match the radio hardware. I am pretty sure that ro.carrier gives it away and we need an EU ROM, but let me check something... Give me a couple hours if you can.
Is this a single or dual SIM model?

acejavelin said:
Did you purchase it new or used?
It is kind of important we determine what the original version of this is... if you flash a LA ROM to an EU device, it could very well give you the issues you see, where the SIM is not recognized, because the radio firmware doesn't match the radio hardware. I am pretty sure that ro.carrier gives it away and we need an EU ROM, but let me check something... Give me a couple hours if you can.
Is this a single or dual SIM model?
Click to expand...
Click to collapse
Bought it new! Single sim

papo_blue7 said:
Bought it new! Single sim
Click to expand...
Click to collapse
OK, well I am going to have to go with you might have accidentally flashed an EU ROM at some point maybe?
I would try XT1572_CLARK_RETLA_6.0_MPHS24.49-18-4_cid12_subsidy-DEFAULT_CFC.xml, or your Movistar variant if the phone was purchased from Movistar, and flash each step manually, then attach the terminal log output please.

acejavelin said:
OK, well I am going to have to go with you might have accidentally flashed an EU ROM at some point maybe?
I would try XT1572_CLARK_RETLA_6.0_MPHS24.49-18-4_cid12_subsidy-DEFAULT_CFC.xml, or your Movistar variant if the phone was purchased from Movistar, and flash each step manually, then attach the terminal log output please.
Click to expand...
Click to collapse
Yeah, I was one step ahead. I already flashed. It's working!!! Thanks a lot!!!
Here it's the log
C:\Users\Pablo\Desktop\Nueva carpeta (4)>fastboot oem fb_mode_set
< waiting for device >
...
OKAY [ 0.010s]
finished. total time: 0.011s
C:\Users\Pablo\Desktop\Nueva carpeta (4)>
C:\Users\Pablo\Desktop\Nueva carpeta (4)>fastboot oem fb_mode_set
...
OKAY [ 0.009s]
finished. total time: 0.010s
C:\Users\Pablo\Desktop\Nueva carpeta (4)>fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.006s]
writing 'partition'...
(bootloader) This may take a few seconds, if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
OKAY [ 0.642s]
finished. total time: 0.650s
C:\Users\Pablo\Desktop\Nueva carpeta (4)>fastboot flash bootloader bootloader.img
target reported max download size of 536870912 bytes
sending 'bootloader' (2699 KB)...
OKAY [ 0.084s]
writing 'bootloader'...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
(bootloader) flashing pmic ...
(bootloader) flashing rpm ...
(bootloader) flashing tz ...
(bootloader) flashing hyp ...
(bootloader) flashing sdi ...
OKAY [ 1.686s]
finished. total time: 1.773s
C:\Users\Pablo\Desktop\Nueva carpeta (4)>fastboot flash logo logo.bin
target reported max download size of 536870912 bytes
sending 'logo' (3687 KB)...
OKAY [ 0.111s]
writing 'logo'...
OKAY [ 0.095s]
finished. total time: 0.209s
C:\Users\Pablo\Desktop\Nueva carpeta (4)>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (40960 KB)...
OKAY [ 1.233s]
writing 'boot'...
OKAY [ 0.901s]
finished. total time: 2.138s
C:\Users\Pablo\Desktop\Nueva carpeta (4)>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (41040 KB)...
OKAY [ 1.233s]
writing 'recovery'...
OKAY [ 0.901s]
finished. total time: 2.137s
C:\Users\Pablo\Desktop\Nueva carpeta (4)>fastboot flash system system.img_sparsechunk.0
target reported max download size of 536870912 bytes
sending 'system' (262003 KB)...
OKAY [ 7.649s]
writing 'system'...
OKAY [ 6.498s]
finished. total time: 14.154s
C:\Users\Pablo\Desktop\Nueva carpeta (4)>fastboot flash system system.img_sparsechunk.1
target reported max download size of 536870912 bytes
sending 'system' (247580 KB)...
OKAY [ 7.208s]
writing 'system'...
OKAY [ 6.407s]
finished. total time: 13.618s
C:\Users\Pablo\Desktop\Nueva carpeta (4)>fastboot flash system system.img_sparsechunk.2
target reported max download size of 536870912 bytes
sending 'system' (256658 KB)...
OKAY [ 7.471s]
writing 'system'...
OKAY [ 5.714s]
finished. total time: 13.188s
C:\Users\Pablo\Desktop\Nueva carpeta (4)>fastboot flash system system.img_sparsechunk.3
target reported max download size of 536870912 bytes
sending 'system' (255970 KB)...
OKAY [ 7.483s]
writing 'system'...
OKAY [ 5.623s]
finished. total time: 13.109s
C:\Users\Pablo\Desktop\Nueva carpeta (4)>fastboot flash system system.img_sparsechunk.4
target reported max download size of 536870912 bytes
sending 'system' (256069 KB)...
OKAY [ 7.468s]
writing 'system'...
OKAY [ 5.859s]
finished. total time: 13.330s
C:\Users\Pablo\Desktop\Nueva carpeta (4)>fastboot flash system system.img_sparsechunk.5
target reported max download size of 536870912 bytes
sending 'system' (254398 KB)...
OKAY [ 7.401s]
writing 'system'...
OKAY [ 5.705s]
finished. total time: 13.109s
C:\Users\Pablo\Desktop\Nueva carpeta (4)>fastboot flash system system.img_sparsechunk.6
target reported max download size of 536870912 bytes
sending 'system' (229432 KB)...
OKAY [ 6.697s]
writing 'system'...
OKAY [ 4.878s]
finished. total time: 11.580s
C:\Users\Pablo\Desktop\Nueva carpeta (4)>fastboot flash system system.img_sparsechunk.7
target reported max download size of 536870912 bytes
sending 'system' (255194 KB)...
OKAY [ 7.432s]
writing 'system'...
OKAY [ 5.769s]
finished. total time: 13.204s
C:\Users\Pablo\Desktop\Nueva carpeta (4)>fastboot flash system system.img_sparsechunk.8
target reported max download size of 536870912 bytes
sending 'system' (63484 KB)...
OKAY [ 1.852s]
writing 'system'...
OKAY [ 1.442s]
finished. total time: 3.296s
C:\Users\Pablo\Desktop\Nueva carpeta (4)>
C:\Users\Pablo\Desktop\Nueva carpeta (4)>fastboot flash modem NON-HLOS.bin
target reported max download size of 536870912 bytes
sending 'modem' (41686 KB)...
OKAY [ 1.218s]
writing 'modem'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.248s
C:\Users\Pablo\Desktop\Nueva carpeta (4)>fastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.016s]
finished. total time: 0.017s
C:\Users\Pablo\Desktop\Nueva carpeta (4)>fastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.013s]
finished. total time: 0.014s
C:\Users\Pablo\Desktop\Nueva carpeta (4)>fastboot flash fsg fsg.mbn
target reported max download size of 536870912 bytes
sending 'fsg' (704 KB)...
OKAY [ 0.027s]
writing 'fsg'...
OKAY [ 0.055s]
finished. total time: 0.084s
C:\Users\Pablo\Desktop\Nueva carpeta (4)>fastboot flash bluetooth BTFM.bin
target reported max download size of 536870912 bytes
sending 'bluetooth' (1295 KB)...
OKAY [ 0.043s]
writing 'bluetooth'...
OKAY [ 0.063s]
finished. total time: 0.109s
C:\Users\Pablo\Desktop\Nueva carpeta (4)>fastboot erase cache
erasing 'cache'...
OKAY [ 0.024s]
finished. total time: 0.025s
C:\Users\Pablo\Desktop\Nueva carpeta (4)>fastboot erase userdata
erasing 'userdata'...
OKAY [ 0.110s]
finished. total time: 0.111s
C:\Users\Pablo\Desktop\Nueva carpeta (4)>fastboot oem fb_mode_clear
...
OKAY [ 0.008s]
finished. total time: 0.011s
C:\Users\Pablo\Desktop\Nueva carpeta (4)>fastboot reboot
rebooting...
finished. total time: 0.004s
Click to expand...
Click to collapse

papo_blue7 said:
Yeah, I was one step ahead. I already flashed. It's working!!! Thanks a lot!!!
Here it's the log
Click to expand...
Click to collapse
Glad it is working... this bothers me a bit though
C:\Users\Pablo\Desktop\Nueva carpeta (4)>fastboot flash modem NON-HLOS.bin
target reported max download size of 536870912 bytes
sending 'modem' (41686 KB)...
OKAY [ 1.218s]
writing 'modem'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.248s
Click to expand...
Click to collapse
If it works, it works and I am not going to complain, but something still isn't right. I would try to flash just the radio stack again if it was me (not the whole ROM, just the 4 radio firmware commands) but if it works it's your call.

acejavelin said:
Glad it is working... this bothers me a bit though
If it works, it works and I am not going to complain, but something still isn't right. I would try to flash just the radio stack again if it was me (not the whole ROM, just the 4 radio firmware commands) but if it works it's your call.
Click to expand...
Click to collapse
Now it's ok! I have already flashed crDroid and TruPureXMM. Everything works perfectly by now! Thanks again
C:\xxx\xxx\Desktop\Nueva carpeta (4)>fastboot flash modem non-hlos.bin
target reported max download size of 536870912 bytes
sending 'modem' (41686 KB)...
OKAY [ 1.217s]
writing 'modem'...
OKAY [ 1.129s]
finished. total time: 2.348s
C:\xxx\xxx\Desktop\Nueva carpeta (4)>fastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.018s]
finished. total time: 0.019s
C:\xxx\xxx\Desktop\Nueva carpeta (4)>fastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.011s]
finished. total time: 0.012s
C:\xxx\xxx\Desktop\Nueva carpeta (4)>fastboot flash fsg fsg.mbn
target reported max download size of 536870912 bytes
sending 'fsg' (704 KB)...
OKAY [ 0.024s]
writing 'fsg'...
OKAY [ 0.052s]
finished. total time: 0.080s
C:\xxx\xxx\Desktop\Nueva carpeta (4)>fastboot reboot
rebooting...
finished. total time: 0.003s
Click to expand...
Click to collapse

Awesome!!! Glad you got it working!

help please brick bootloader.

I was using Resurrection Remix 7.1.1 Then I decided to install ElementalX.
I noticed that the unit was heating up.
Today when I woke up the device did not start anymore, it stayed on a black screen.
I decided to find a solution here in the forum.
I found this tip:
Https://forum.xda-developers.com/moto-g4-plus/help/solved-unbrick-hard-bricked-dead-t3585016
The device is back on again.
But I can not revert to stock rom.
{
"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"
}
When I try to upload GPT.bin it returns this error:
(Bootloader) Security version downgrade
(Bootloader) Image primary_gpt failed validation
(Bootloader) Preflash validation failed
FAILED (remote failure)
Finished. Total time: 0.05s
Same thing with bootloader.img
E: \ cel \ motog4> fastboot flash bootloader bootloader.img
Target reported max download size of 536870912 bytes
Sending 'bootloader' (3651 KB) ...
OKAY [0.119s]
Writing 'bootloader' ...
(Bootloader) validating: bootloader.default.xml ...
(Bootloader) Invalid partition name aboot
(Bootloader) will fail: flash: aboot
FAILED (remote failure)
Finished. Total time: 0.213s
I spent the whole dawn trying a solution, downloaded all the stocks I found on the internet and had no solution.
Same thing with recovery.
E: \ cel \ motog4> fastboot flash recovery recovery.img
Target reported max download size of 536870912 bytes
Sending 'recovery' (16484 KB) ...
OKAY [0.522s]
Writing 'recovery' ...
(Bootloader) Invalid partition name recovery
FAILED (remote failure)
Finished. Total time: 0.530s
I've tried all these ROMs
My device is an XT1640
According to the getvar the information is these.
E: \ cel \ motog4> fastboot getvar all
<Waiting for device>
(Bootloader) version: 0.5
(Bootloader) version-bootloader: moto-msm8952-B1.03 (*)
(Bootloader) product: athene_16mp
(Bootloader) board: athene_16mp
(Bootloader) secure: yes
(Bootloader) hwrev: P2A
(Bootloader) radio: 6
(Bootloader) storage-type: emmc
(Bootloader) emmc: 32GB SKHYNIX HBG4a2 RV = 08 PV = E4 FV = 00000000000000E4
(Bootloader) ram: 2GB SKHYNIX LP3 DIE = 8Gb M5 = 06 M6 = 03 M7 = 00 M8 = 1F
(Bootloader) cpu: MSM8952
(Bootloader) serialno: xxxxxxx
(Bootloader) cid: 0x0032
(Bootloader) channelid: 0x19
(Bootloader) uid:
(Bootloader) securestate: oem_locked
(Bootloader) iswarrantyvoid: yes
(Bootloader) max-download-size: 536870912
(Bootloader) reason: Failed to initialize partition table
(Bootloader) imei: 000000000000000
(Bootloader) meid:
(Bootloader) date: 01-01-1970
Bootloader sku: 000000000000000
(Bootloader) battid:
(Bootloader) iccid:
(Bootloader) cust_md5:
(Bootloader) max-sparse-size: 268435456
(Bootloader) current-time:
(Bootloader) ro.build.fingerprint:
(Bootloader) ro.build.version.full:
(Bootloader) ro.build.version.qcom:
(Bootloader) version-baseband:
(Bootloader) kernel.version:
(Bootloader) sbl1.git: sbl1.git
(Bootloader) rpm.git: rpm.git
(Bootloader) tz.git: tz.git
(Bootloader) hyp.git: hyp.git
(Bootloader) keymaster.git: keymaster.git
(Bootloader) cmnlib.git: cmnlib.git
(Bootloader) aboot.git: git = MBM-NG-VB1.03-0-gb44c0ee
(Bootloader) qe:
(Bootloader) frp-state: no protection (err)
(Bootloader) ro.carrier:
All: listed above
Finished. Total time: 0.106s

Was the above flashing tested with the GPT.bin from the 93-14 stock ROM file that you have? As you've noted, you can't downgrade your GPT (though at the moment we have no GPT or a corrupted partition table), so if you haven't, try flashing with the latest GPT.bin we've got access to.
You may also like to re-try with the blank flash and procedure from this post:https://forum.xda-developers.com/showpost.php?p=71405834&postcount=23

echo92 said:
Was the above flashing tested with the GPT.bin from the 93-14 stock ROM file that you have? As you've noted, you can't downgrade your GPT (though at the moment we have no GPT or a corrupted partition table), so if you haven't, try flashing with the latest GPT.bin we've got access to.
You may also like to re-try with the blank flash and procedure from this post:https://forum.xda-developers.com/showpost.php?p=71405834&postcount=23
Click to expand...
Click to collapse
Yes i try with 93-14 stock ROM.
XT1640_ATHENE_NPJ25.93-14_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
Samething at now
As you can see I tried all these roms.
All GPT.BINs that are inside of them
The question is:
How to force to enter em qboot again to make this procedure from this post:https://forum.xda-developers.com/showpost.php?p=71405834&postcount=23

ricardomilena said:
Yes i try with 93-14 stock ROM.
XT1640_ATHENE_NPJ25.93-14_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
Samething at now
As you can see I tried all these roms.
All GPT.BINs that are inside of them
The question is:
How to force to enter em qboot again to make this procedure from this post:https://forum.xda-developers.com/showpost.php?p=71405834&postcount=23
Click to expand...
Click to collapse
Bro, you are on the blank bootloader, I don't think you can get back there. You might have just been flashing the wrong gpt.bin and bootloader all that time?
Retry flashing the NPJ25.93-14 gpt.bin and bootloader.img, being tired and frustrated can cause lots of damage to your focus.

MK+2017 said:
Bro, you are on the blank bootloader, I don't think you can get back there. You might have just been flashing the wrong gpt.bin and bootloader all that time?
Retry flashing the NPJ25.93-14 gpt.bin and bootloader.img, being tired and frustrated can cause lots of damage to your focus.
Click to expand...
Click to collapse
I extracted all gpt.bin and bootloader.img to each separate folder.
I tried one by one but it still does not work
C:\adb>fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.004s]
writing 'partition'...
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.073s
C:\adb>fastboot flash bootloader bootloader.img
target reported max download size of 536870912 bytes
sending 'bootloader' (3651 KB)...
OKAY [ 0.119s]
writing 'bootloader'...
(bootloader) validating: bootloader.default.xml ...
(bootloader) Invalid partition name aboot
(bootloader) will fail: flash:aboot
FAILED (remote failure)
finished. total time: 0.216s
I try with this Extracted gpt.bin and bootloader.img from this archive.
https://cloud.mail.ru/public/CKF3/AWVREk6s9
Same thing
C:\adb>fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.004s]
writing 'partition'...
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.073s
C:\adb>fastboot flash bootloader bootloader.img
target reported max download size of 536870912 bytes
sending 'bootloader' (3651 KB)...
OKAY [ 0.119s]
writing 'bootloader'...
(bootloader) validating: bootloader.default.xml ...
(bootloader) Invalid partition name aboot
(bootloader) will fail: flash:aboot
FAILED (remote failure)
finished. total time: 0.216s

ricardomilena said:
I extracted all gpt.bin and bootloader.img to each separate folder.
I tried one by one but it still does not work
C:\adb>fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.004s]
writing 'partition'...
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.073s
C:\adb>fastboot flash bootloader bootloader.img
target reported max download size of 536870912 bytes
sending 'bootloader' (3651 KB)...
OKAY [ 0.119s]
writing 'bootloader'...
(bootloader) validating: bootloader.default.xml ...
(bootloader) Invalid partition name aboot
(bootloader) will fail: flash:aboot
FAILED (remote failure)
finished. total time: 0.216s
I try with this Extracted gpt.bin and bootloader.img from this archive.
https://cloud.mail.ru/public/CKF3/AWVREk6s9
Same thing
C:\adb>fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.004s]
writing 'partition'...
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.073s
C:\adb>fastboot flash bootloader bootloader.img
target reported max download size of 536870912 bytes
sending 'bootloader' (3651 KB)...
OKAY [ 0.119s]
writing 'bootloader'...
(bootloader) validating: bootloader.default.xml ...
(bootloader) Invalid partition name aboot
(bootloader) will fail: flash:aboot
FAILED (remote failure)
finished. total time: 0.216s
Click to expand...
Click to collapse
This is weird. When it says "downgrade" then it really sees itself higher than the file version you are trying to flash! Really weird.
Since you already tried gpt.bin of NPJ25.93-14 I cannot advise you to try the gpt.bin of the latest OTA NPJ25.93-14.4: if it works it would only prove that you have hope, but you won't be able to proceed further because OTA packages do not include fastboot flashable bootloader and boot images (else I would have used them myself to get out of CID = 0xDEAD problem of my older dead XT1642)
If it does not work, however, it would only tell that something really awkward happened to your phone. Can't even tell if it would be a bad blankflash for your model?!

ricardomilena said:
I extracted all gpt.bin and bootloader.img to each separate folder.
I tried one by one but it still does not work
Click to expand...
Click to collapse
This is trivial, but please triple check what you're trying to flash. I've got this errors on older Moto Gs (the G 2015 to be specific) because I used a firmware for the 1GB version against the 2GB version. Verify carefully.

@ricardomilena Just wanted to confirm whether you installed 93-14-4 update. If you did you'll have to wait till 93-14-4 images are available. If you didn't took that update then 93-14 bootloader & gpt should work. First flash gpt then flash bootloader then reboot to bootloader & finally you can flash all stock image as usual:
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
PS- See if you get success with the below attached gpt.bin it's from the new 93-14-4.

lCrD512 said:
@ricardomilena Just wanted to confirm whether you installed 93-14-4 update. If you did you'll have to wait till 93-14-4 images are available. If you didn't took that update then 93-14 bootloader & gpt should work. First flash gpt then flash bootloader then reboot to bootloader & finally you can flash all stock image as usual:
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
PS- See if you get success with the below attached gpt.bin it's from the new 93-14-4.
Click to expand...
Click to collapse
Just the other day this happened to me as well I was flashing Invicta and went to reboot into recovery once I set up the ROM and I got the black screen only the notification light would blink after many attempts of trying to flash everything to get it up and running I had had to flash that 40 megabyte update of the partition table and that solved it then you have to go and Flash the entire firmware don't forget to flash the bootloader right after flash the GPT. Bin
Sent from my Moto G4 using Tapatalk

lCrD512 said:
@ricardomilena Just wanted to confirm whether you installed 93-14-4 update. If you did you'll have to wait till 93-14-4 images are available. If you didn't took that update then 93-14 bootloader & gpt should work. First flash gpt then flash bootloader then reboot to bootloader & finally you can flash all stock image as usual:
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
PS- See if you get success with the below attached gpt.bin it's from the new 93-14-4.
Click to expand...
Click to collapse
Lol bricked my device again (random brick) don't know why it happens. I've already installed the 93-14-4 update & as expected flashing stock firmware failed with 93-14 gpt file. I will try this gpt & report back.

same problam bro
plz guys solution this problam request you and contact me 7688888588 plz

Anish1216 said:
plz guys solution this problam request you and contact me 7688888588 plz
Click to expand...
Click to collapse
Have you tried this blank flash in this thread? https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761

the same
Anish1216 said:
plz guys solution this problam request you and contact me 7688888588 plz
Click to expand...
Click to collapse
2019 and i have the same problem, any solution?

schondan0 said:
2019 and i have the same problem, any solution?
Click to expand...
Click to collapse
How did your device get bricked? Have you tried this blankflash? https://forum.xda-developers.com/showpost.php?p=79013024&postcount=523

echo92 said:
How did your device get bricked? Have you tried this blankflash? https://forum.xda-developers.com/showpost.php?p=79013024&postcount=523
Click to expand...
Click to collapse
i've tried a lot of gpt versions, I'm gonna try this one (thanks) and see if it works, I did blanckflash and now it shows the same error: (Bootloader) validating: bootloader.default.xml ...
(Bootloader) Invalid partition name aboot
(Bootloader) will fail: flash: aboot
FAILED (remote failure)
I TRIED, BUT I HAVE ALREADY THE PHONE ALIVE, I THINK I NEED A NEW VERSION OF BOATLOADER AND GPT THAT WORKS. (I'VE TRIED 6,0 AND 7,0)

schondan0 said:
i've tried a lot of gpt versions, I'm gonna try this one (thanks) and see if it works, I did blanckflash and now it shows the same error: (Bootloader) validating: bootloader.default.xml ...
(Bootloader) Invalid partition name aboot
(Bootloader) will fail: flash: aboot
FAILED (remote failure)
Click to expand...
Click to collapse
Hmm, is that with the blankflash GPT and bootloader or with the separate GPT and bootloader files?
Do you see errors when flashing the GPT? That error suggests your device doesn't have a partition map or had corrupted flash memory.
Depending on what GPT and bootloader you had previously, you may have to flash the GPT and bootloader from the Oreo stock firmware (but only if you had updated to stock Oreo in the past).
If you're still on stock Nougat, try this April 2018 GPT and bootloader https://drive.google.com/file/d/13AuJkn8eelq-wQ5wp7lNQTf7kT7_lLwI/view?usp=drivesdk if you do get your device booting, please flash the latest firmware to your device

I got it
thanks a million, this 2018 version worked, now just flash firmware
---------- Post added at 06:11 PM ---------- Previous post was at 05:20 PM ----------
IS POSSIBLE TO RE-LOCK BOOTLOADER? (I DO'T WANNA TRY TO SELL THE PHONE OR GET WARRANTY BACK) I want to lock bootloader to give it to my mother, (I got one one plus 5t). Or if you have the link to oreo rom to install via adb I will be more grateful than I already am.

schondan0 said:
I got it
thanks a million, this 2018 version worked, now just flash firmware
---------- Post added at 06:11 PM ---------- Previous post was at 05:20 PM ----------
IS POSSIBLE TO RE-LOCK BOOTLOADER? (I DO'T WANNA TRY TO SELL THE PHONE OR GET WARRANTY BACK) I want to lock bootloader to give it to my mother, (I got one one plus 5t). Or if you have the link to oreo rom to install via adb I will be more grateful than I already am.
Click to expand...
Click to collapse
Here is the link for the Oreo stock firmware
https://forum.xda-developers.com/showpost.php?p=79100802&postcount=1056
please read the initial post of the thread https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
to flash the firmware and relock your device bootloader - you will need to use fastboot. Of course, locking your bootloader will erase your device and revert your device to full stock, but if you're handing the device to your mother, that's likely for the best. Back up as necessary.

THANKS, I DID IT ALL. IT ALL WORKED WELL, NO ERROR (INCLUDE THE COMMON ERRORS LIKE FINGERPRINT ERROR OR IMEI ERROR) AND THE OSCARS GOES TO YOU. THANKS THANKS THANKS MATE:fingers-crossed:

Question ... for a newbie

I have a G4plus on android 7.0. I have flash few months ago this version 7.0 on my phone before the official update from moto.
My phone is rooted. Everything will work perfectly everyday except one point...
Since the begin, when i power on the phone, the boot image will be sticken on the logo Lenovo (i have flash the boot logo Lenovo instead of your device is ...).
I need to switch off, switch on several times and waiting...
If the phone will vibrate, i need to switch off again and again...
And sometimes, it will power on to the boot animation.
Because i'm not sure of the version, i will pasted the printscreen :
Build : NPJ25.75-2
Software :
{
"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"
}
Hardware :
I have free time this summer, so i want to pass using TWRP (already flash on my phone) to LineageOS or any ROM more updated...
but i want to fix this problem before !
Any idea ?
Thank you.

download stock 6.0 rom and flash using pc .
you will need to root it again after this .
then u can update officially or flash a custom rom like resurrection remix .
follow steps carefully .
Sent from my Moto G4 Plus using Tapatalk

Moto g4 plus slow charging
My moto g4 plus charging very slow campare to normal, I'm using RR ROM pls tel any one how to fix

parth00790 said:
download stock 6.0 rom and flash using pc .
you will need to root it again after this .
then u can update officially or flash a custom rom like resurrection remix .
follow steps carefully .
Sent from my Moto G4 Plus using Tapatalk
Click to expand...
Click to collapse
Because i saw on the website, I can brick my phone... i prefer to start from a 7.0 android stock.
https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
I have relock the bootloader (if i try to upload the rom without lock, i enter in boot loop).
Keep you in touch...
In progress !
After, i want to unlock again and except skip boot loop... and flash twrp+root and migrate to lineageos after...

Always, the same problem.
In the bootloader :
- software status : modified
oem_locked (seems to be locked, OK?)
If i try to power on, i will sticked with the motorola logo (blue and M...) and vibrate, and loop, boot, logo, vibrate, loop, boot...
Again and again.
Try to flash again the rom, now with my bootloader locked.

If i tried to flash again after relock the bootloader, i will boot (with no message this device is not trusted, bad key ...)...
But after few seconds, i have a droid open with ! (red) and NO COMMAND...
What can i do please ?
At this time :
When i power on the phone :
I saw a blue screen with M logo, vibrate once ; automatic reboot.
Blue screen with M logo, vibrate once and stick on the red logo during long time (< 1 min)
Automatic reboot
and black screen with opened droid and no command written.
I will power off the phone, power on and again again ...
And sometimes, it will start to the android 7 rom (on this previous link)
Please help me

benj29 said:
If i tried to flash again after relock the bootloader, i will boot (with no message this device is not trusted, bad key ...)...
But after few seconds, i have a droid open with ! (red) and NO COMMAND...
What can i do please ?
At this time :
When i power on the phone :
I saw a blue screen with M logo, vibrate once ; automatic reboot.
Blue screen with M logo, vibrate once and stick on the red logo during long time (< 1 min)
Automatic reboot
and black screen with opened droid and no command written.
I will power off the phone, power on and again again ...
And sometimes, it will start to the android 7 rom (on this previous link)
Please help me
Click to expand...
Click to collapse
Follow this guide
https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138

lCrD512 said:
Follow this guide
https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
Click to expand...
Click to collapse
This is what i already done (see my previous quote).
Thanks !

Just to be sure...
I've tried again using your link (which is the same as mine ).
But i use script batch instead of command lines...
I have downloaded the ROM.
download the script bat.
My bootloader says flashing_unlock, so i run only
To simply flash, run the "OEM Flash" file
Click to expand...
Click to collapse
At the end, the phone has rebooted with the page
"your device has been unlocked and can't be trusted
to learn more, visit : motorola.com/unlockbootloader
IT : bad key
your device will boot in 5 seconds
"
and my phone is blocked at this page....
is it normal to have bad key ?
i've try to lock again the bootloader... with the same script + lock.
EDIT : after flashing and lock again the bootloader, the phone has blue screen + red M logo.
I have waited for 1/2 minutes approx and the phone has reboot to "no-command"
Always the same problem, i don't understand !

The bad key is normal (especially with an unlocked bootloader), what's not normal is your device hanging after a flash...
Are you able to repeat the flash but executing the commands manually, please? You can copy paste each of the commands individually into your adb terminal, and check the result - it should say [OKAY] afterwards. The script, handy as it is, makes it difficult to read the outputs from each section of the flash
So the plan is:
Boot your device to the bootloader (just asking, what version is your bootloader now, B1:06?) and attach to your computer
In the adb terminal, check you're communicating with your device via 'fastboot devices', you should get a response with your device's serial number.
Open the 'OEM Flash' script in Notepad or your preferred text editor (don't run the script).
Copy each individual command line, in order, to your adb terminal and press Enter to execute that command.
EDIT - also, it's odd that on your previous flashing attempts, your device booted to the stock recovery (the opened droid with no command) rather than the system

In fact, when i saw no command, i was blocked in the recovery mode !
I tried to make a factory reset on the recovery, but the phone will do this :
- boot bluescreen, vibrate, reboot (automatic) => short time (< 15s)
- boot bluescreen => long time (1 minute) => vibrate, reboot (automatic)
- boot bluescreen, vibrate, reboot (automatic) => short time (< 15s)
- screen "no command" => recovery (power+volume up).
I try after to reboot to system...
But the phone will do the same, three reboots and recovery.
I don't understand my problem !

Thanks for your help.
After last try with lock, this is what i have on my bootloader. I will try to copy each individual command line, in order and past here the results.
BL : B1.06 (sha-0edfb0d, 2017-06-01 12:10:43)
Baseband : 8952_70030.25.03.62.01R Athene_Emea_DSDS_CUST
Product/variant : athene_16mp xt1642 32gb P2A
32 GB + 3 GB RAM
Console[Null] : null ?
Tools mode config : disabled
Battery : OK
oem_locked
software status : modified

benj29 said:
Thanks for your help.
After last try with lock, this is what i have on my bootloader. I will try to copy each individual command line, in order and past here the results.
BL : B1.06 (sha-0edfb0d, 2017-06-01 12:10:43)
Baseband : 8952_70030.25.03.62.01R Athene_Emea_DSDS_CUST
Product/variant : athene_16mp xt1642 32gb P2A
32 GB + 3 GB RAM
Console[Null] : null ?
Tools mode config : disabled
Battery : OK
oem_locked
software status : modified
Click to expand...
Click to collapse
Thanks - console [NULL] seems to be a normal response, though oem_locked means you may wish to unlock your device again before proceeding (thus, if you run into any issues, you can flash a custom ROM).
Are you unlocking by using 'fastboot oem unlock <your unlock code>' and with the OEM unlocking enabled in Developer Options?
Software status: modified might be an issue - can you remember what firmware you flashed before the soak test (the NPJ25.75-2 firmware)?
Also, as you're now on the B1:06 bootloader, try not to flash older stock firmware onto your device.

Yes, i have a problem.
Flash seems to work perfectly, see the quote after.
I start from a lock bootloader (with status modified software, how i can go back to official ?)
After the flash, the phone will start on the ROM, OK... yessss !!! NO.... if I reboot the phone i was block on the recovery again and again...
Don't understand !
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash partition gpt.bin
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slotartition: not found
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.010s]
writing 'partition'...
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
OKAY [ 0.130s]
finished. total time: 0.160s
Click to expand...
Click to collapse
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash bootloader bootloader.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:bootloader: not found
target reported max download size of 536870912 bytes
sending 'bootloader' (3651 KB)...
OKAY [ 0.120s]
writing 'bootloader'...
(bootloader) validating: bootloader.default.xml ...
(bootloader) will pass: flash:aboot
(bootloader) will pass: flash:rpm
(bootloader) will pass: flash:tz
(bootloader) will pass: flash:hyp
(bootloader) will pass: flash:cmnlib
(bootloader) will pass: flash:keymaster
(bootloader) will pass: flash:sbl1
(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 'hyp.mbn' to 'hyp'
(bootloader) - flashing 'cmnlib.mbn' to 'cmnlib'
(bootloader) - flashing 'keymaster.mbn' to 'keymaster'
(bootloader) - flashing 'sbl1.mbn' to 'sbl1'
OKAY [ 0.442s]
finished. total time: 0.562s
Click to expand...
Click to collapse
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash logo logo.bin
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:logo: not found
target reported max download size of 536870912 bytes
sending 'logo' (2186 KB)...
OKAY [ 0.080s]
writing 'logo'...
OKAY [ 0.060s]
finished. total time: 0.140s
Click to expand...
Click to collapse
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot boot.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:boot: not found
target reported max download size of 536870912 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.527s]
writing 'boot'...
OKAY [ 0.373s]
finished. total time: 0.912s
Click to expand...
Click to collapse
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery recovery.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (16484 KB)...
OKAY [ 0.525s]
writing 'recovery'...
OKAY [ 0.380s]
finished. total time: 0.905s
Click to expand...
Click to collapse
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash dsp adspso.bin
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:dsp: not found
target reported max download size of 536870912 bytes
sending 'dsp' (16384 KB)...
OKAY [ 0.520s]
writing 'dsp'...
OKAY [ 0.258s]
finished. total time: 0.778s
Click to expand...
Click to collapse
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash oem oem.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slotem: not found
target reported max download size of 536870912 bytes
sending 'oem' (96490 KB)...
OKAY [ 3.045s]
writing 'oem'...
OKAY [ 7.179s]
finished. total time: 10.234s
Click to expand...
Click to collapse
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.0
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (261013 KB)...
OKAY [ 8.223s]
writing 'system'...
OKAY [ 6.132s]
finished. total time: 14.355s
Click to expand...
Click to collapse
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.1
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (250842 KB)...
OKAY [ 7.914s]
writing 'system'...
OKAY [ 5.985s]
finished. total time: 13.900s
Click to expand...
Click to collapse
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.2
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (254485 KB)...
OKAY [ 8.018s]
writing 'system'...
OKAY [ 7.665s]
finished. total time: 15.686s
Click to expand...
Click to collapse
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.3
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (247298 KB)...
OKAY [ 7.800s]
writing 'system'...
OKAY [ 6.589s]
finished. total time: 14.390s
Click to expand...
Click to collapse
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.4
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (260398 KB)...
OKAY [ 8.286s]
writing 'system'...
OKAY [ 5.844s]
finished. total time: 14.134s
Click to expand...
Click to collapse
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.5
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (262041 KB)...
OKAY [ 8.247s]
writing 'system'...
OKAY [ 5.862s]
finished. total time: 14.119s
Click to expand...
Click to collapse
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.6
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (261941 KB)...
OKAY [ 8.287s]
writing 'system'...
OKAY [ 10.808s]
finished. total time: 19.096s
Click to expand...
Click to collapse
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.7
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (82497 KB)...
OKAY [ 2.610s]
writing 'system'...
OKAY [ 1.860s]
finished. total time: 4.470s
Click to expand...
Click to collapse
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash modem NON-HLOS.bin
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:modem: not found
target reported max download size of 536870912 bytes
sending 'modem' (76954 KB)...
OKAY [ 2.428s]
writing 'modem'...
OKAY [ 1.122s]
finished. total time: 3.551s
Click to expand...
Click to collapse
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase modemst1
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:modemst1: not found
erasing 'modemst1'...
OKAY [ 0.028s]
finished. total time: 0.028s
Click to expand...
Click to collapse
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase modemst2
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:modemst2: not found
erasing 'modemst2'...
OKAY [ 0.030s]
finished. total time: 0.040s
Click to expand...
Click to collapse
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash fsg fsg.mbn
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:fsg: not found
target reported max download size of 536870912 bytes
sending 'fsg' (2032 KB)...
OKAY [ 0.063s]
writing 'fsg'...
OKAY [ 0.070s]
finished. total time: 0.143s
Click to expand...
Click to collapse
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase cache
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:cache: not found
erasing 'cache'...
OKAY [ 0.020s]
finished. total time: 0.020s
Click to expand...
Click to collapse
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase userdata
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:userdata: not found
erasing 'userdata'...
OKAY [ 0.082s]
finished. total time: 0.092s
Click to expand...
Click to collapse
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase customize
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:customize: not found
erasing 'customize'...
OKAY [ 0.010s]
finished. total time: 0.010s
Click to expand...
Click to collapse
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase clogo
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:clogo: not found
erasing 'clogo'...
OKAY [ 0.020s]
finished. total time: 0.024s
Click to expand...
Click to collapse
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot reboot
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
rebooting...
finished. total time: -0.000s
Click to expand...
Click to collapse

echo92 said:
Thanks - console [NULL] seems to be a normal response, though oem_locked means you may wish to unlock your device again before proceeding (thus, if you run into any issues, you can flash a custom ROM).
Are you unlocking by using 'fastboot oem unlock <your unlock code>' and with the OEM unlocking enabled in Developer Options?
Software status: modified might be an issue - can you remember what firmware you flashed before the soak test (the NPJ25.75-2 firmware)?
Also, as you're now on the B1:06 bootloader, try not to flash older stock firmware onto your device.
Click to expand...
Click to collapse
Yes, i start from this Build : NPJ25.75-2.
Ok, for your remark, i don't flash older stock firmware (to prevent hard brick I supposed !)
At this time, my phone is blocked on the recovery.
Now, I unlock the bootloader using the classical method :
- phone on the bootloader (oem_locked written on the screen, software status : modified)
go on this website :
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem get_unlock_data
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) Unlock data:
(bootloader) BLABLA0737325667#
(bootloader) BLA93232334B53465347004D6F746F2047200000#
(bootloader) BLA7E8824CF486716F8F64F4CE1E39615A649B9C#
(bootloader) BLA1B501000000000000000000000000
OKAY [ 0.129s]
finished. total time: 0.134s
Click to expand...
Click to collapse
BLA is to mask the correct code... i use the data scrub on the moto website to prevent any mistake cut/paste !
After i received the email ...
I have to run twice the commands as mark :
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem unlock MYKEY
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) WARNING: This command erases all user data.
(bootloader) Please re-run this command to continue.
OKAY [ 0.020s]
finished. total time: 0.020s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem unlock MYKEY
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) Bootloader is unlocked! Rebooting phone
OKAY [ 0.237s]
finished. total time: 0.240s
C:\Program Files (x86)\Minimal ADB and Fastboot>
Click to expand...
Click to collapse
And after the automatic reboot after the second command line, the phone will written on the bootloader
software status : modified
flashin_unlocked...
If i choice "start" on the bootloader, the bootpage was : "your device has been unlocked etc etc, your device will boot in 5 seconds"
and do the same thing than previous :
5 boot loops on the boot page and after 3/4 minutes will start on the motorola bluescreen and logo motorola...
Don't understand !

benj29 said:
Yes, i start from this Build : NPJ25.75-2.
Ok, for your remark, i don't flash older stock firmware (to prevent hard brick I supposed !)
At this time, my phone is blocked on the recovery.
Now, I unlock the bootloader using the classical method :
- phone on the bootloader (oem_locked written on the screen, software status : modified)
go on this website :
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
BLA is to mask the correct code... i use the data scrub on the moto website to prevent any mistake cut/paste !
After i received the email ...
I have to run twice the commands as mark :
And after the automatic reboot after the second command line, the phone will written on the bootloader
software status : modified
flashin_unlocked...
If i choice "start" on the bootloader, the bootpage was : "your device has been unlocked etc etc, your device will boot in 5 seconds"
and do the same thing than previous :
5 boot loops on the boot page and after 3/4 minutes will start on the motorola bluescreen and logo motorola...
Don't understand !
Click to expand...
Click to collapse
Hmm, that fastboot flash log and the procedure you've mentioned to unlock should work. How long are you leaving your device on the Motorola bluescreen, as after a flash/wipe it might take some time to boot?
The bootloops aren't good though, I'm wondering if the flash storage on your device is okay or if it's failing. Does your device bootloop in the bootloader or in recovery? You mentioned your device hanging whilst you were in the stock recovery?

I don't stop the phone or reboot it, i wait each time... again and again (to avoid corruption or something like this).
To be exhaustive :
1. Power on
2. Bootscreen with bad id key etc...
3. The phone will enter in boot loop (3/4 times ) and after will go in recovery with "no command".
4. enter in the recovery (power + volume up)
5. reboot to the system now from the menu
6. boot to the ROM !
I don't understand why i need to pass by the recovery...

benj29 said:
I don't stop the phone or reboot it, i wait each time... again and again (to avoid corruption or something like this).
To be exhaustive :
1. Power on
2. Bootscreen with bad id key etc...
3. The phone will enter in boot loop (3/4 times ) and after will go in recovery with "no command".
4. enter in the recovery (power + volume up)
5. reboot to the system now from the menu
6. boot to the ROM !
I don't understand why i need to pass by the recovery...
Click to expand...
Click to collapse
I'm not sure either, whether there's an issue with your system (shouldn't be, since it's a clean flash), or if that's a fallback if you get a bootloop. Are you able to boot to the home screen/setup?

Yes, sorry, i write it (my english is not good ).
Yes, after the recovery and reboot the phone using the recovery, the phone will start.
SO, at this time, I have flashed TWRP, ElementalX and root using this :
https://forum.xda-developers.com/moto-g4-plus/how-to/guide-how-root-nougat-moto-g4-plus-t3484672
At this time : TWRP, root, and rom will works.
Even i need to have a complex power on sequence using the recovery

benj29 said:
Yes, sorry, i write it (my english is not good ).
Yes, after the recovery and reboot the phone using the recovery, the phone will start.
SO, at this time, I have flashed TWRP, ElementalX and root using this :
https://forum.xda-developers.com/moto-g4-plus/how-to/guide-how-root-nougat-moto-g4-plus-t3484672
Click to expand...
Click to collapse
At least it's working - which root manager did you go for, phh or SuperSU or magisk?

bootloader yellow alert

had the bootloader unlocked and ended up giving hardbrick after an update via OTA.
I managed to recover but had the alert that the bootloader was unlocked, so I wanted to block again, then by fasstboot, I made the command: fastboot flashing lock, and apois this alert began to appear.
I'm afraid to give a factory reset and give hardbrick.
image attached
https://drive.google.com/file/d/1V_UK0iGIhDO31dETqs9t83uZ_TOHHYIJ/view?usp=sharing

What device do you have and what firmware did you use to lock your device with? I'd check your ADB folder and make sure you've extracted the correct firmware. Also, that should give you an opportunity to delete any old stock ROMs - updating via OTA after flashing an old stock ROM runs a risk of hard bricking.
When you're locking your device bootloader, your device will be wiped anyway.

echo92 said:
What device do you have and what firmware did you use to lock your device with? I'd check your ADB folder and make sure you've extracted the correct firmware. Also, that should give you an opportunity to delete any old stock ROMs - updating via OTA after flashing an old stock ROM runs a risk of hard bricking.
When you're locking your device bootloader, your device will be wiped anyway.
Click to expand...
Click to collapse
I'm going to put the prints here of the device and the folder that I used to pass the mobile;
one detail that I realized is that the rom that step is at ATHENE_NPJS25.93-14-18, but on the device shows ATHENE_NPJS25.93-14-4.
https://drive.google.com/file/d/1ivZZP275zHBteiykw5hgF2elSkatCAOs/view?usp=sharing
https://drive.google.com/file/d/1znezKwp4esAJ6Q1rJFoeJtg-gmhZjAXy/view?usp=sharing
the rom was supposed to be the April 2018 patch but appears in March 2017;
I really wanted to reset the factory; but I'm afraid to brick it again

luis dambrowski said:
I'm going to put the prints here of the device and the folder that I used to pass the mobile;
one detail that I realized is that the rom that step is at ATHENE_NPJS25.93-14-18, but on the device shows ATHENE_NPJS25.93-14-4.
https://drive.google.com/file/d/1ivZZP275zHBteiykw5hgF2elSkatCAOs/view?usp=sharing
https://drive.google.com/file/d/1znezKwp4esAJ6Q1rJFoeJtg-gmhZjAXy/view?usp=sharing
the rom was supposed to be the April 2018 patch but appears in March 2017;
Click to expand...
Click to collapse
Hmm, you have the March 2017 stock ROM but the Feb/April 2018 baseband. I wonder if you've got a firmware mismatch in your ADB folder?
I'd delete all the stock ROM files from your ADB folder (except the ADB and fastboot files and your flashing scripts), then extract a fresh copy of the NPJS25.93-14-18 firmware, then copy the extracted files to your ADB folder (don't extract directly to the ADB folder if your ADB folder is on C drive, sometimes UAC can block the extraction. Extract then copy to the C drive). That way, you can be sure the firmware you're flashing is not mixed up (despite the same timestamps, have you verified the md5 checksums of the extracted files match the md5 checksums in the flashfile.xml or servicefile.xml? You can use a program like WinMD5Free to check).
When you recovered from the hard brick, did you flash a working GPT and bootloader before you attempted to lock your device?
What flashing commands are you using and what are the outputs? I'd suggest trying to flash the stock ROM again, provided you've cleaned out your ADB folder as suggested above.
Can you also post your getvar all info here please?
1)Boot your device to the bootloader, connect your device to your computer via USB.
2)Open an ADB terminal on your computer. Type 'fastboot getvar all' without quotes in the terminal. Press Enter.
3)Please post or paste the getvar all output in a text file and upload to this thread, or paste the output here. You may wish to omit your IMEI. This should give us an idea of your device health.

echo92 said:
Hmm, you have the March 2017 stock ROM but the Feb/April 2018 baseband. I wonder if you've got a firmware mismatch in your ADB folder?
I'd delete all the stock ROM files from your ADB folder (except the ADB and fastboot files and your flashing scripts), then extract a fresh copy of the NPJS25.93-14-18 firmware, then copy the extracted files to your ADB folder (don't extract directly to the ADB folder if your ADB folder is on C drive, sometimes UAC can block the extraction. Extract then copy to the C drive). That way, you can be sure the firmware you're flashing is not mixed up (despite the same timestamps, have you verified the md5 checksums of the extracted files match the md5 checksums in the flashfile.xml or servicefile.xml? You can use a program like WinMD5Free to check).
When you recovered from the hard brick, did you flash a working GPT and bootloader before you attempted to lock your device?
What flashing commands are you using and what are the outputs? I'd suggest trying to flash the stock ROM again, provided you've cleaned out your ADB folder as suggested above.
Can you also post your getvar all info here please?
1)Boot your device to the bootloader, connect your device to your computer via USB.
2)Open an ADB terminal on your computer. Type 'fastboot getvar all' without quotes in the terminal. Press Enter.
3)Please post or paste the getvar all output in a text file and upload to this thread, or paste the output here. You may wish to omit your IMEI. This should give us an idea of your device health.
Click to expand...
Click to collapse
about having incompatibility, I do not know what to do, what I did was download the rom that was supposed to be the april of 2018 and add the fastboot files and the .bat OEM lock and OEM Flash files, and run the OEM lock.bat
about the procedure of extracting the files, I believe that I have nothing mixed, I just do not understand how it does not load the right version, but I can do it if I think it's the problem

luis dambrowski said:
about having incompatibility, I do not know what to do, what I did was download the rom that was supposed to be the april of 2018 and add the fastboot files and the .bat OEM lock and OEM Flash files, and run the OEM lock.bat
about the procedure of extracting the files, I believe that I have nothing mixed, I just do not understand how it does not load the right version, but I can do it if I think it's the problem
Click to expand...
Click to collapse
Thanks for the commands and the getvar. The commands look okay. Your getvar indicates you have the Dec 2017 - April 2018 bootloader and a newer baseband, but your system and kernel appear to be much older. That suggests either the flash only partially worked (possibly there's a problem with your device) or you have a mixed firmware that accidentally got flashed.
I'd erase all the stock ROM files from your ADB directory, extract a fresh copy and copy to your ADB folder, then flash again. Try to make sure you see [OKAY] after each flash, and if you can, try to capture the flash log.
Edit - looking more closely at your ADB folder, there do appear to be firmware files of a different timestamp - some are from the 28th, others are from the 29th. If they were all from the same firmware, they should have the same timestamp as the files should have been extracted in one go... never mind, I had a look at my ADB folder and the same is for me
Those commands and the NPJS25.93-14-18 firmware do work, I've locked my XT1642 with them.
Edit 2: can you repeat the flash without the locking commands please (the two initial OEM lock commands and the final OEM lock command)

echo92 said:
Thanks for the commands and the getvar. The commands look okay. Your getvar indicates you have the Dec 2017 - April 2018 bootloader and a newer baseband, but your system and kernel appear to be much older. That suggests either the flash only partially worked (possibly there's a problem with your device) or you have a mixed firmware that accidentally got flashed.
I'd erase all the stock ROM files from your ADB directory, extract a fresh copy and copy to your ADB folder, then flash again. Try to make sure you see [OKAY] after each flash, and if you can, try to capture the flash log.
Edit - looking more closely at your ADB folder, there do appear to be firmware files of a different timestamp - some are from the 28th, others are from the 29th. If they were all from the same firmware, they should have the same timestamp as the files should have been extracted in one go...
Those commands and the NPJS25.93-14-18 firmware do work, I've locked my XT1642 with them.
Click to expand...
Click to collapse
a piece of the log
"
D:\Downloads\Nova pasta (2)\teste>fastboot oem lock begin
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) Not in unlocked state
OKAY [ 0.174s]
finished. total time: 0.175s
D:\Downloads\Nova pasta (2)\teste>fastboot oem lock begin
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) Not in unlocked state
OKAY [ 0.176s]
finished. total time: 0.178s
D:\Downloads\Nova pasta (2)\teste>fastboot flash partition gpt.bin
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slotartition: not found
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.007s]
writing 'partition'...
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
OKAY [ 0.137s]
finished. total time: 0.146s
D:\Downloads\Nova pasta (2)\teste>fastboot flash bootloader bootloader.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:bootloader: not found
target reported max download size of 536870912 bytes
sending 'bootloader' (3651 KB)...
OKAY [ 0.128s]
writing 'bootloader'...
(bootloader) validating: bootloader.default.xml ...
(bootloader) will pass: flash:aboot
(bootloader) will pass: flash:rpm
(bootloader) will pass: flash:tz
(bootloader) will pass: flash:hyp
(bootloader) flash permission denied
(bootloader) will fail: flash:cmnlib
FAILED (remote failure)
finished. total time: 0.329s
D:\Downloads\Nova pasta (2)\teste>fastboot flash logo logo.bin
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:logo: not found
target reported max download size of 536870912 bytes
sending 'logo' (2186 KB)...
OKAY [ 0.078s]
writing 'logo'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 0.095s
D:\Downloads\Nova pasta (2)\teste>fastboot flash boot boot.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:boot: not found
target reported max download size of 536870912 bytes
sending 'boot' (16384 KB)...
OKAY [ 1.176s]
writing 'boot'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 1.194s
D:\Downloads\Nova pasta (2)\teste>fastboot flash recovery recovery.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (16484 KB)...
OKAY [ 1.241s]
writing 'recovery'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 1.254s
D:\Downloads\Nova pasta (2)\teste>fastboot flash dsp adspso.bin
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:dsp: not found
target reported max download size of 536870912 bytes
sending 'dsp' (16384 KB)...
OKAY [ 0.540s]
writing 'dsp'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 0.553s
D:\Downloads\Nova pasta (2)\teste>fastboot flash oem oem.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slotem: not found
target reported max download size of 536870912 bytes
sending 'oem' (96490 KB)...
OKAY [ 3.140s]
writing 'oem'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 3.149s
D:\Downloads\Nova pasta (2)\teste>fastboot flash system system.img_sparsechunk.0
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (261013 KB)...
OKAY [ 16.071s]
writing 'system'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 16.079s
D:\Downloads\Nova pasta (2)\teste>fastboot flash system system.img_sparsechunk.1
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (250846 KB)...
......
"

echo92 said:
Thanks for the commands and the getvar. The commands look okay. Your getvar indicates you have the Dec 2017 - April 2018 bootloader and a newer baseband, but your system and kernel appear to be much older. That suggests either the flash only partially worked (possibly there's a problem with your device) or you have a mixed firmware that accidentally got flashed.
I'd erase all the stock ROM files from your ADB directory, extract a fresh copy and copy to your ADB folder, then flash again. Try to make sure you see [OKAY] after each flash, and if you can, try to capture the flash log.
Edit - looking more closely at your ADB folder, there do appear to be firmware files of a different timestamp - some are from the 28th, others are from the 29th. If they were all from the same firmware, they should have the same timestamp as the files should have been extracted in one go...
Those commands and the NPJS25.93-14-18 firmware do work, I've locked my XT1642 with them.
Edit 2: can you repeat the flash without the locking commands please (the two initial OEM lock commands and the final OEM lock command)
Click to expand...
Click to collapse
I will do now,
D:\Downloads\Nova pasta (2)\teste>fastboot flash partition gpt.bin
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slotartition: not found
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.067s]
writing 'partition'...
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
OKAY [ 0.137s]
finished. total time: 0.209s
D:\Downloads\Nova pasta (2)\teste>fastboot flash bootloader bootloader.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:bootloader: not found
target reported max download size of 536870912 bytes
sending 'bootloader' (3651 KB)...
OKAY [ 0.170s]
writing 'bootloader'...
(bootloader) validating: bootloader.default.xml ...
(bootloader) will pass: flash:aboot
(bootloader) will pass: flash:rpm
(bootloader) will pass: flash:tz
(bootloader) will pass: flash:hyp
(bootloader) flash permission denied
(bootloader) will fail: flash:cmnlib
FAILED (remote failure)
finished. total time: 0.368s
D:\Downloads\Nova pasta (2)\teste>fastboot flash logo logo.bin
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:logo: not found
target reported max download size of 536870912 bytes
sending 'logo' (2186 KB)...
OKAY [ 0.105s]
writing 'logo'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 0.120s
D:\Downloads\Nova pasta (2)\teste>fastboot flash boot boot.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:boot: not found
target reported max download size of 536870912 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.738s]
writing 'boot'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 0.755s
D:\Downloads\Nova pasta (2)\teste>fastboot flash recovery recovery.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (16484 KB)...
OKAY [ 0.707s]
writing 'recovery'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 0.723s
D:\Downloads\Nova pasta (2)\teste>fastboot flash dsp adspso.bin
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:dsp: not found
target reported max download size of 536870912 bytes
sending 'dsp' (16384 KB)...
OKAY [ 0.696s]
writing 'dsp'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 0.710s
D:\Downloads\Nova pasta (2)\teste>fastboot flash oem oem.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slotem: not found
target reported max download size of 536870912 bytes
sending 'oem' (96490 KB)...
OKAY [ 4.547s]
writing 'oem'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 4.555s
D:\Downloads\Nova pasta (2)\teste>fastboot flash system system.img_sparsechunk.0
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (261013 KB)...

luis dambrowski said:
I will do now,
.
Click to expand...
Click to collapse
Thanks - that (bootloader) flash permission denied error is not good though - are you using the original USB cable, or at least a high quality data USB cable to flash? Can you try another USB port to flash if possible? If you can, try to flash manually rather than using the scripts. You can copy paste each command in sequence to your ADB terminal and press Enter - this may be more reliable than using the scripts.
How did you unbrick your device after the hard brick, was it using a blankflash like the one here: https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761 Also, did you flash a working GPT/bootloader before attempting to lock your bootloader?

echo92 said:
Thanks - that (bootloader) flash permission denied error is not good though - are you using the original USB cable, or at least a high quality data USB cable to flash? Can you try another USB port to flash if possible? If you can, try to flash manually rather than using the scripts. You can copy paste each command in sequence to your ADB terminal and press Enter - this may be more reliable than using the scripts.
How did you unbrick your device after the hard brick, was it using a blankflash like the one here: https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761 Also, did you flash a working GPT/bootloader before attempting to lock your bootloader?
Click to expand...
Click to collapse
I have already done the process with another cable and another port and using the commands manually, without positive results.
exactly was using the blankflash, then it was stuck on the screen with the "start" in the bootloader, after this tried to flash several roms and without result, nothing worked.
Yes I tried to make GPT / bootloader flash, (gpt and boot), but it did not work.
So I downloaded that rom that I sent the print with the adb files that should be April 2018, and the phone revived, but with the red bootlader alert unlocked, and so I was using it without problems. but I wanted to remove the alert, and tried to block the bootloader, I used the command: fastboot flashing lock, and asked to flash again from a rom, but at the moment I did not have the files and just rebooted.
So I got that yellow alert, everything works normally, but I wanted to fix this problem, so I can make updates via OTA in the future.
Sorry for the bad English.

echo92 said:
Thanks - that (bootloader) flash permission denied error is not good though - are you using the original USB cable, or at least a high quality data USB cable to flash? Can you try another USB port to flash if possible? If you can, try to flash manually rather than using the scripts. You can copy paste each command in sequence to your ADB terminal and press Enter - this may be more reliable than using the scripts.
How did you unbrick your device after the hard brick, was it using a blankflash like the one here: https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761 Also, did you flash a working GPT/bootloader before attempting to lock your bootloader?
Click to expand...
Click to collapse
and if I do a blankflash again now and do the rom flash, would it work?

luis dambrowski said:
I have already done the process with another cable and another port and using the commands manually, without positive results.
exactly was using the blankflash, then it was stuck on the screen with the "start" in the bootloader, after this tried to flash several roms and without result, nothing worked.
Yes I tried to make GPT / bootloader flash, (gpt and boot), but it did not work.
So I downloaded that rom that I sent the print with the adb files that should be April 2018, and the phone revived, but with the red bootlader alert unlocked, and so I was using it without problems. but I wanted to remove the alert, and tried to block the bootloader, I used the command: fastboot flashing lock, and asked to flash again from a rom, but at the moment I did not have the files and just rebooted.
So I got that yellow alert, everything works normally, but I wanted to fix this problem, so I can make updates via OTA in the future.
Sorry for the bad English.
Click to expand...
Click to collapse
When you tried to re-flash the GPT and bootloader, what do you mean by 'it did not work'? Did it not flash? If not, try this GPT/bootloader: https://drive.google.com/file/d/13AuJkn8eelq-wQ5wp7lNQTf7kT7_lLwI/view?usp=sharing That should be from the April 2018 image.
Yeah, unless you have a fully clean flash of all the same firmware (no March 2017/April 2018), it's a really bad idea to re-lock your bootloader as you've found out.
You do not need to re-lock your bootloader to receive OTA updates at all. However, having a device all on the same firmware (bootloader, system, modem etc all matching) is a really good idea, else you may just keep hard bricking when you try to take OTA updates. In theory you could hard brick and try again, but with the flashing issues you're having at the moment, you may not be able to rescue your device, so I'd advise against it.
You could flash a custom logo.bin to hide the bootloader warning, but you may not be able to use OTA updates unless you revert back to stock and then use the OTA update.
I'd suggest re-downloading the fastboot image onto another computer, install ADB (please try to flash the latest ADB tools, minimal ADB v1.4.3 or the Google ADB tools) and try the process again - it could be due to your computer. If it's still occurring, then it may be that your device is having some issues.
The fastboot image should be:
ATHENE_NPJS25.93-14-18_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
md5: 75E60CA7F9E8574BF20F658508F766C2
Size: 1.05 GB (1,137,681,910 bytes)
Size on disk: 1.05 GB (1,137,684,480 bytes)

echo92 said:
When you tried to re-flash the GPT and bootloader, what do you mean by 'it did not work'? Did it not flash? If not, try this GPT/bootloader: https://drive.google.com/file/d/13AuJkn8eelq-wQ5wp7lNQTf7kT7_lLwI/view?usp=sharing That should be from the April 2018 image.
Yeah, unless you have a fully clean flash of all the same firmware (no March 2017/April 2018), it's a really bad idea to re-lock your bootloader as you've found out.
You do not need to re-lock your bootloader to receive OTA updates at all. However, having a device all on the same firmware (bootloader, system, modem etc all matching) is a really good idea, else you may just keep hard bricking when you try to take OTA updates. In theory you could hard brick and try again, but with the flashing issues you're having at the moment, you may not be able to rescue your device, so I'd advise against it.
You could flash a custom logo.bin to hide the bootloader warning, but you may not be able to use OTA updates unless you revert back to stock and then use the OTA update.
I'd suggest re-downloading the fastboot image onto another computer, install ADB (please try to flash the latest ADB tools, minimal ADB v1.4.3 or the Google ADB tools) and try the process again - it could be due to your computer. If it's still occurring, then it may be that your device is having some issues.
The fastboot image should be:
ATHENE_NPJS25.93-14-18_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
md5: 75E60CA7F9E8574BF20F658508F766C2
Size: 1.05 GB (1,137,681,910 bytes)
Size on disk: 1.05 GB (1,137,684,480 bytes)
Click to expand...
Click to collapse
When I did the GPT / bootloader flash (gpt and boot) process, there was apparently no change.
do you suggest doing the flash with that (bootloader.img and gpt.bin) now? to remove this alert?
in fact this alert does not bother me, but I intend to remove it for future upgrade via OTA.
finally I will try to redo the process with ADB v1.4.3.

echo92 said:
When you tried to re-flash the GPT and bootloader, what do you mean by 'it did not work'? Did it not flash? If not, try this GPT/bootloader: https://drive.google.com/file/d/13AuJkn8eelq-wQ5wp7lNQTf7kT7_lLwI/view?usp=sharing That should be from the April 2018 image.
Yeah, unless you have a fully clean flash of all the same firmware (no March 2017/April 2018), it's a really bad idea to re-lock your bootloader as you've found out.
You do not need to re-lock your bootloader to receive OTA updates at all. However, having a device all on the same firmware (bootloader, system, modem etc all matching) is a really good idea, else you may just keep hard bricking when you try to take OTA updates. In theory you could hard brick and try again, but with the flashing issues you're having at the moment, you may not be able to rescue your device, so I'd advise against it.
You could flash a custom logo.bin to hide the bootloader warning, but you may not be able to use OTA updates unless you revert back to stock and then use the OTA update.
I'd suggest re-downloading the fastboot image onto another computer, install ADB (please try to flash the latest ADB tools, minimal ADB v1.4.3 or the Google ADB tools) and try the process again - it could be due to your computer. If it's still occurring, then it may be that your device is having some issues.
The fastboot image should be:
ATHENE_NPJS25.93-14-18_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
md5: 75E60CA7F9E8574BF20F658508F766C2
Size: 1.05 GB (1,137,681,910 bytes)
Size on disk: 1.05 GB (1,137,684,480 bytes)
Click to expand...
Click to collapse
I did all the procedures, separated and together, with no results.
I made a "Format Factory" for the recovery and did the rom flash again also did not work.
it is in the same way.
* should i try to update via OTA

luis dambrowski said:
I did all the procedures, separated and together, with no results.
I made a "Format Factory" for the recovery and did the rom flash again also did not work.
it is in the same way.
* should i try to update via OTA
Click to expand...
Click to collapse
OTA updates should work with or without that warning you're trying to remove - updates don't appear to care if you have a locked or unlocked bootloader. You do need a clean system (no modifications) and also you require a system matching your bootloader.
What system are you on now, are you still on the March 2017 firmware or on the April 2018 firmware? If you're on the March 2017 firmware still, I would suggest do not use OTA updates.

echo92 said:
OTA updates should work with or without that warning you're trying to remove - updates don't appear to care if you have a locked or unlocked bootloader. You do need a clean system (no modifications) and also you require a system matching your bootloader.
What system are you on now, are you still on the March 2017 firmware or on the April 2018 firmware? If you're on the March 2017 firmware still, I would suggest do not use OTA updates.
Click to expand...
Click to collapse
ainda esta no firmware de março de 2017!
Tive uma ideia de desbloquear o bootloader e instalar o TWRP e colocar uma custom rom. No entanto, o código de desbloqueio não pode ser encontrado no site da motorola, mas sim o desbloqueio do bootloader.
Pois bem, o probloma aqui é o bootloader !!
Estou sem ideias de como prosseguir.
Sera que quando sair de novo update, (talvez algum) de certo o processo?

echo92 said:
OTA updates should work with or without that warning you're trying to remove - updates don't appear to care if you have a locked or unlocked bootloader. You do need a clean system (no modifications) and also you require a system matching your bootloader.
What system are you on now, are you still on the March 2017 firmware or on the April 2018 firmware? If you're on the March 2017 firmware still, I would suggest do not use OTA updates.
Click to expand...
Click to collapse
good news!!! solved problem.
What did I do:
I used the command: fastboot flashing unlock
then he asked to repeat the command and then unlocked the bootloader, with the alert that was yellow turned red.
There I did the rom flash of April 2018 and it went without errors.
rom update and no bootloader alert.
echo92 thank you very much for your attention. big hug!!!

Trashed my Bootloader, GPT tables corrupt

So after installing xposed and a few other things my phone crashed, and on reboot, I got boot image did not pass verification message or some such. Normally I would just flash stock then twrp and go from there, but it seems that somehow along the way my partition tables got corrupted. I can get into fastboot, but all fastboot commands fail. I tried to reflash the gpt partition and bootloader partitions first as some suggested, but it's not working
Code:
$ fastboot flash partition gpt.bin
Sending 'partition' (45 KB) OKAY [ 0.002s]
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...
(bootloader) Failed to write EFI backup GPT header.
(bootloader) Failed to program partition table
FAILED (remote failure)
Finished. Total time: 0.059s
$ fastboot flash bootloader bootloader.img
Sending 'bootloader' (5115 KB) OKAY [ 0.114s]
Writing 'bootloader' (bootloader) Validating 'bootloader.default.xml'
(bootloader) Committing 'bootloader.default.xml'
(bootloader) - flashing 'emmc_appsboot.mbn' to 'aboot'
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition aboot
FAILED (remote failure)
Finished. Total time: 0.309s
I also tried blankflash, but I am unsure how to make it work since everytime I connect a USB cable the device starts itself in bootloader/fastboot mode right away, and attempting to blank flash it then just hangs at
Code:
<waiting for device>
Flashing recovery results in
Code:
$ fastboot flash recovery twrp-3.2.3-1-potter.img
Sending 'recovery' (16316 KB) OKAY [ 0.351s]
Writing 'recovery' (bootloader) Image not signed or corrupt
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
Finished. Total time: 0.355s
Any help is appreciated!

Drkmatr1984 said:
So after installing xposed and a few other things my phone crashed, and on reboot, I got boot image did not pass verification message or some such. Normally I would just flash stock then twrp and go from there, but it seems that somehow along the way my partition tables got corrupted. I can get into fastboot, but all fastboot commands fail. I tried to reflash the gpt partition and bootloader partitions first as some suggested, but it's not working
I also tried blankflash, but I am unsure how to make it work since everytime I connect a USB cable the device starts itself in bootloader/fastboot mode right away, and attempting to blank flash it then just hangs at
Flashing recovery results in
Any help is appreciated!
Click to expand...
Click to collapse
Try erasing everything by using ADB codes then flash the latest bootloader and gpt then flash the stock ROM and lock the bootloader,and the flash the whole firmware again,so there will be no partition corrupted.after that you can unlock your bootloader.

Also, make sure to flash the latest stock firmware, being sure not to try and revert to an earlier version. Don't flash blankflash unless you are totally bricked, with just flashing light. Your device will never be the same if you do.

riyan65 said:
Try erasing everything by using ADB codes then flash the latest bootloader and gpt then flash the stock ROM and lock the bootloader,and the flash the whole firmware again,so there will be no partition corrupted.after that you can unlock your bootloader.
Click to expand...
Click to collapse
How do I use ADB if I can't get beyond fastboot? I can't load TWRP or flash TWRP to get into it to access ADB. And ADB commands don't work from the fastboot bootloader screen.
Doing "fastboot erase <partition name>" or "fastboot format:ext4 <partition name>" also fails same as the other fastboot flash commands so I can't erase my partitions from fastboot before re-flashing.

If all fastboot commands fail, including
Code:
fastboot devices
,
Code:
fastboot getvar all
I would uninstall, and reinstall adb/fastboot and all it's drivers. I would also reinstall the moto drivers. Try a different cable, and perhaps even a different pc. If the phone boots to bootloader mode, you should be able to execute those basic commands if it is communicating. If it is communicating, then try flashing the most recent stock firmware. Many gpt errors are from trying to downgrade.

[email protected] said:
If all fastboot commands fail, including
Code:
fastboot devices
,
Code:
fastboot getvar all
I would uninstall, and reinstall adb/fastboot and all it's drivers. I would also reinstall the moto drivers. Try a different cable, and perhaps even a different pc. If the phone boots to bootloader mode, you should be able to execute those basic commands if it is communicating. If it is communicating, then try flashing the most recent stock firmware. Many gpt errors are from trying to downgrade.
Click to expand...
Click to collapse
Ok, after trying 3 different USb cables, including a brand new one I just ordered, and after uninstalling all drivers on pc and rebooting, then reinstalling, I still get these same responses from fastboot devices and fastboot getvar all
Code:
C:\ProgramData\LMSA\Download\RomFiles>fastboot devices
ZY224262W9 fastboot
and
Code:
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>mfastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8953-C0.92
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.008s
Any other fastboot commands fail with similar errors. Trying to reflash OPSS28-85-17-2 results in
Code:
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot devices
ZY224262W9 fastboot
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot reboot bootloader
rebooting into bootloader OKAY [ 0.003s]
Finished. Total time: 0.005s
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>OREO.BAT
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot oem fb_mode_set
FAILED (remote failure)
Finished. Total time: 0.003s
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash partition gpt.bin
Sending 'partition' (45 KB) FAILED (command write failed
(Unknown error))
Finished. Total time: 5.146s
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash bootloader bootloader.i
mg
Sending 'bootloader' (5115 KB) FAILED (command write failed
(Unknown error))
Finished. Total time: 5.009s
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash logo logo.bin
Sending 'logo' (2186 KB) FAILED (command write failed
(Unknown error))
Finished. Total time: 5.009s
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash boot boot.img
Sending 'boot' (16384 KB) FAILED (command write failed
(Unknown error))
Finished. Total time: 6.967s
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash recovery recovery.img
Sending 'recovery' (20580 KB) FAILED (command write failed
(Unknown error))
Finished. Total time: 5.009s
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash dsp adspso.bin
Sending 'dsp' (16384 KB) FAILED (command write failed
(Unknown error))
Finished. Total time: 5.008s
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash oem oem.img
Sending 'oem' (104608 KB) FAILED (command write failed
(Unknown error))
Finished. Total time: 5.012s
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash system system.img_spars
echunk.0
Sending 'system' (256553 KB) FAILED (command write failed
(Unknown error))
Finished. Total time: 5.011s
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash system system.img_spars
echunk.1
Sending 'system' (256617 KB) FAILED (command write failed
(Unknown error))
Finished. Total time: 5.007s
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash system system.img_spars
echunk.2
Sending 'system' (254213 KB) FAILED (command write failed
(Unknown error))
Finished. Total time: 5.006s
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash system system.img_spars
echunk.3
Sending 'system' (256710 KB) FAILED (command write failed
(Unknown error))
Finished. Total time: 5.009s
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash system system.img_spars
echunk.4
Sending 'system' (256912 KB) FAILED (command write failed
(Unknown error))
Finished. Total time: 5.010s
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash system system.img_spars
echunk.5
Sending 'system' (257861 KB) FAILED (command write failed
(Unknown error))
Finished. Total time: 5.009s
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash system system.img_spars
echunk.6
Sending 'system' (260027 KB) FAILED (command write failed
(Unknown error))
Finished. Total time: 5.010s
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash system system.img_spars
echunk.7
Sending 'system' (257601 KB) FAILED (command write failed
(Unknown error))
Finished. Total time: 5.006s
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash system system.img_spars
echunk.8
Sending 'system' (257805 KB) FAILED (command write failed
(Unknown error))
Finished. Total time: 5.010s
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash modem NON-HLOS.bin
Sending 'modem' (71921 KB) FAILED (command write failed
(Unknown error))
Finished. Total time: 5.011s
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot erase modemst1
Erasing 'modemst1' FAILED (command write failed
(Unknown error))
Finished. Total time: 5.006s
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot erase modemst2
Erasing 'modemst2' FAILED (command write failed
(Unknown error))
Finished. Total time: 5.006s
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash fsg fsg.mbn
Sending 'fsg' (3012 KB) FAILED (command write failed
(Unknown error))
Finished. Total time: 5.011s
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot erase cache
Erasing 'cache' FAILED (command write failed
(Unknown error))
Finished. Total time: 5.008s
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot erase userdata
Erasing 'userdata' FAILED (command write failed
(Unknown error))
Finished. Total time: 34.761s
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot erase customize
Erasing 'customize' FAILED (command write failed
(Unknown error))
Finished. Total time: 14.723s
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot erase clogo
Erasing 'clogo' FAILED (command write failed
(Unknown error))
Finished. Total time: 5.008s
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot oem fb_mode_clear
FAILED (command write failed (Unknown error))
Finished. Total time: 5.003s
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot reboot bootloader
rebooting into bootloader FAILED (command write failed
(Unknown error))
Finished. Total time: 5.007s
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>
Occasionally I can get a different message
Code:
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash bootloader bootloader.i
mg
Sending 'bootloader' (5115 KB) OKAY [ 0.325s]
Writing 'bootloader' (bootloader) Validating 'boot
loader.default.xml'
(bootloader) Committing 'bootloader.default.xml'
(bootloader) - flashing 'emmc_appsboot.mbn' to 'aboot'
FAILED (status read failed (Too many links))
Finished. Total time: 0.533s
and
Code:
C:\ProgramData\LMSA\Download\RomFiles\POTTER_RETAIL_8.1.0_OPSS28.85-17-2_cid50_s
ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot flash partition gpt.bin
Sending 'partition' (45 KB) OKAY [ 0.005s]
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) Failed to write primary GPT.
(bootloader) Failed to program partition table
FAILED (remote failure)
Finished. Total time: 0.085s
But it always fails.

Drkmatr1984 said:
If all fastboot commands fail, including ,
Ok, after trying 3 different USb cables, including a brand new one I just ordered, and after uninstalling all drivers on pc and rebooting, then reinstalling, I still get these same responses from fastboot devices and fastboot getvar all
and
Any other fastboot commands fail with similar errors. Trying to reflash OPSS28-85-17-2 results in
Occasionally I can get a different message
and
But it always fails.
Click to expand...
Click to collapse
Why don't you try latest firmware version, as it is having latest bootloader and gpt.
Here is the link for latest version:-https://mirrors.lolinet.com/firmware/moto/potter/official/

riyan65 said:
Why don't you try latest firmware version, as it is having latest bootloader and gpt.
Here is the link for latest version:-https://mirrors.lolinet.com/firmware/moto/potter/official/
Click to expand...
Click to collapse
I am using the latest from lolinet, they do not have the latest (OPSS28.85-13-5) uploaded there yet. I did manage to find a copy here But I am at work on slow internet so it may take me all night to finish downloading it

At least it is communicating, so as riyan65 posted, you need the current firmware. You don't need blankflash, that will screw the pooch big time.

[email protected] said:
At least it is communicating, so as riyan65 posted, you need the current firmware. You don't need blankflash, that will screw the pooch big time.
Click to expand...
Click to collapse
I know, I am not inexperienced with this phone. Normally I would say that getting messages from fastboot at all is good, but the messages I am getting are all saying that my bootloader and gpt tables are write protected currently. I've actually already hard bricked this device once before, and was able to rescue with blank-flash and then flash the stock firmware. This time is different as it's not hard-bricked. I don't understand why I would "need the most recent firmware" as I was never on "the most recent firmware" I should only have to flash the most recent firmware I have had installed on this phone. I never took the december security update so I shouldn't in theory need the firmware he's recommending but Im giving it a shot anyway. I will update my reply when I get a chance to try flashing the december update.
Thanks for your help guys!

Drkmatr1984 said:
I know, I am not inexperienced with this phone. Normally I would say that getting messages from fastboot at all is good, but the messages I am getting are all saying that my bootloader and gpt tables are write protected currently. I've actually already hard bricked this device once before, and was able to rescue with blank-flash and then flash the stock firmware. This time is different as it's not hard-bricked. I don't understand why I would "need the most recent firmware" as I was never on "the most recent firmware" I should only have to flash the most recent firmware I have had installed on this phone. I never took the december security update so I shouldn't in theory need the firmware he's recommending but Im giving it a shot anyway. I will update my reply when I get a chance to try flashing the december update.
Thanks for your help guys!
Click to expand...
Click to collapse
Well, Still no success. The messages do not even change. At least if it was hard bricked I could try blank flash, but right now it's like all of the partitions are write protected, including the gpt tables themselves and the bootloader. Check out the logs here: The only fastboot commands that work are fastboot devices and fastboot reboot. I finally got fastboot getvar all to print more info out though:
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8953-C0.92
(bootloader) product: potter
(bootloader) board: potter
(bootloader) secure: yes
(bootloader) hwrev: P3B
(bootloader) radio: 1
(bootloader) storage-type: emmc
(bootloader) emmc: 64GB SAMSUNG RC14MB RV=08 PV=07 FV=0000000000000007
(bootloader) ram: 4GB SAMSUNG LP3 DIE=8Gb M5=01 M6=05 M7=00 M8=5F
(bootloader) cpu: MSM8953
(bootloader) serialno: xxxxxxxxxx
(bootloader) cid: 0x0032
(bootloader) channelid: 0x8d
(bootloader) uid: 6C657D3F00000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 534773760
(bootloader) reason: Last time flashing failed
(bootloader) imei: xxxxxxxxxxxxxxxxxx
(bootloader) meid:
(bootloader) date: 03-28-2017
(bootloader) sku: XT1687
(bootloader) carrier_sku:
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Fri Jan 2 23:25:13 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/potter_n/potter_n:7.0/NPN
(bootloader) ro.build.fingerprint[1]: S25.137-33-11/11:user/release-keys
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full[0]: Blur_Version.28.211.2.potter.reta
(bootloader) ro.build.version.full[1]: il.en.US
(bootloader) ro.build.version.qcom: LA.UM.6.6.r1-08600-89xx.0
(bootloader) version-baseband: M8953_41.50.07.85R POTTER_NA_CUST
(bootloader) kernel.version[0]: Linux version 3.18.71-ElementalX-G5-3.00
(bootloader) kernel.version[1]: ([email protected]) (gcc version 4.9.4 201506
(bootloader) kernel.version[2]: 29 (prerelease) (crosstool-NG 1.20.0 - L
(bootloader) kernel.version[3]: inaro GCC 2015.06 - Cortex-A15) ) #1 SMP
(bootloader) kernel.version[4]: PREEMPT Mon Oct 1 22:31:26 EDT 2018
(bootloader) sbl1.git: sbl1.git
(bootloader) rpm.git: rpm.git
(bootloader) tz.git: tz.git
(bootloader) devcfg.git: devcfg.git
(bootloader) keymaster.git: keymaster.git
(bootloader) cmnlib.git: cmnlib.git
(bootloader) cmnlib64.git: cmnlib64.git
(bootloader) prov.git: prov.git
(bootloader) aboot.git: git=MBM-NG-VC0.92-0-g3ea8df0
(bootloader) frp-state: no protection (err)
(bootloader) ro.carrier: retus
(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.010s
Is it because the secure boot is on?

You should edit your imei in your getvar output.
When you recovered from hard brick before, did you use Vache's for this device, or the albus blankflash for Addison?
I assume you are trying to get into recovery by using the volume button, but have you tried fastboot commands.
Code:
fastboot reboot recovery
sometimes works.
With a copy of TWRP in your adb/fastboot folder, try
Code:
fastboot boot image twrp.img
or
Code:
fastboot boot recovery twrp.img
where you have renamed your TWRP image to the twrp.img. This boots into twrp without installing, and has been reported to work with fubarred partition tables. If it boots, you then can access tools to repair gpt partition tables via adb.

Drkmatr1984 said:
Well, Still no success. The messages do not even change. At least if it was hard bricked I could try blank flash, but right now it's like all of the partitions are write protected, including the gpt tables themselves and the bootloader. Check out the logs here: The only fastboot commands that work are fastboot devices and fastboot reboot. I finally got fastboot getvar all to print more info out though:
Is it because the secure boot is on?
Click to expand...
Click to collapse
Before posting this kind of information it's better to remove IMEI ans serial number!
The previous message is a little wrong:
- it's possible to boot the recovery without flashing (and very often raccomanded) but the recovery (both original and TWRP) need a working boot partition!
- it' possible also to try to boot a boot.img: if the system it's ok Android can even start!
What is strange to me is the different behaviour in the same situation: it need investigation!

nicolap8 said:
Before posting this kind of information it's better to remove IMEI ans serial number!
The previous message is a little wrong:
- it's possible to boot the recovery without flashing (and very often raccomanded) but the recovery (both original and TWRP) need a working boot partition!
- it' possible also to try to boot a boot.img: if the system it's ok Android can even start!
What is strange to me is the different behaviour in the same situation: it need investigation!
Click to expand...
Click to collapse
Ok, thanks! and done!
I will give these new suggestions a try later tonight. I did hear about booting into TWRP before, but have had little luck with that. However, I think I have only tried fastboot boot twrp.img and not with recovery or image as keywords in there...

OK, so the two fastboot commands are not the correct syntax.
Code:
C:\Users\Hermes\Moto G5 Plus\TWRPs>fastboot boot image twrp.img
fastboot: error: cannot load 'image': No such file or directory
C:\Users\Hermes\Moto G5 Plus\TWRPs>fastboot boot recovery twrp.img
fastboot: error: cannot load 'recovery': No such file or directory
Doing this:
Code:
$ fastboot boot boot.img recovery.img
fastboot: error: cannot boot a boot.img *and* ramdisk
Almost works lol
"fastboot reboot recovery" just gives this:
Code:
C:\Users\Hermes\Moto G5 Plus\TWRPs>fastboot reboot recovery
fastboot: usage: unknown reboot target recovery
C:\Users\Hermes\Moto G5 Plus\TWRPs>fastboot reboot recovery
fastboot: usage: unknown reboot target recovery
Doing "fastboot boot twrp.img" works but it hangs at the "your device is not safe" screen and never actually loads. "fastboot getvar all" returns interesting things in the slot section. Those slots don't seem normal to me. Also, my ro.fingerprint looks like it's for nougat, but my bootloader is Oreo. I'm willing to break this phone to fix it if possible, so if anyone has any riskier suggestions for me to try I'm down as I've already gone 4 days without a phone and am about to buy a new one either way.

Drkmatr1984 said:
OK, so the two fastboot commands are not the correct syntax.
Click to expand...
Click to collapse
If you are not able to get the fastboot help you have not to try to flash anything!

nicolap8 said:
If you are not able to get the fastboot help you have not to try to flash anything!
Click to expand...
Click to collapse
What? I don't understand you.
I am reading this
And am trying to understand the fastboot boot command better. It requires a kernel image and a ramdisk image. So far I have tried by using zImage from ElementalX kernel as kernel and twrp.img as Ramdisk but the boot just hangs for a long time. Does anyone know the Correct command to boot into TWRP(and kernel) from USB on this device? (Confirmed working and tested, please!)
Here are all of my attempts so far:
Code:
[email protected] MINGW64 ~/Moto G5 Plus/TWRPs
$ fastboot boot elex.zImage twrp.img
creating boot image...
creating boot image - 26769408 bytes
Downloading 'boot.img' OKAY [ 0.563s]
booting OKAY [ 0.080s]
Finished. Total time: 0.860s
[email protected] MINGW64 ~/Moto G5 Plus/TWRPs
$ fastboot boot elex.zImage twrp.img
creating boot image...
creating boot image - 26611712 bytes
Downloading 'boot.img' OKAY [ 0.554s]
booting OKAY [ 0.073s]
Finished. Total time: 0.667s
[email protected] MINGW64 ~/Moto G5 Plus/TWRPs
$ fastboot boot linux-2.6/arch/arm/boot/zImage twrp.img
fastboot: error: cannot load 'linux-2.6/arch/arm/boot/zImage': No such file or directory
[email protected] MINGW64 ~/Moto G5 Plus/TWRPs
$ fastboot boot Ele
ElementalX-G5-3.00.zip elex.zImage
[email protected] MINGW64 ~/Moto G5 Plus/TWRPs
$ fastboot boot ElementalX-G5-3.00.zip twrp.img
creating boot image...
creating boot image - 29065216 bytes
Downloading 'boot.img' OKAY [ 0.606s]
booting OKAY [ 0.081s]
Finished. Total time: 0.764s
[email protected] MINGW64 ~/Moto G5 Plus/TWRPs
$ fastboot boot zImage twrp.img
creating boot image...
creating boot image - 23590912 bytes
Downloading 'boot.img' OKAY [ 0.496s]
booting OKAY [ 0.109s]
Finished. Total time: 0.642s
[email protected] MINGW64 ~/Moto G5 Plus/TWRPs
$ fastboot boot zImage
creating boot image...
creating boot image - 6883328 bytes
Downloading 'boot.img' OKAY [ 0.154s]
booting OKAY [ 0.079s]
Finished. Total time: 0.245s

Bump.
No one knows how to boot into TWRP from USB 100% tried and tested on this device?

Drkmatr1984 said:
Bump.
No one knows how to boot into TWRP from USB 100% tried and tested on this device?
Click to expand...
Click to collapse
fastboot boot twrp.img

craigl14 said:
fastboot boot twrp.img
Click to expand...
Click to collapse
That only works when you have a boot partition that is intact.
Since my partition tables are ****ed it just hangs at boot when I run that command. I need the full command with kernel option to make it boot so that I can edit the partitions from TWRP. However, I don't know enough about the kernel of this phone, or where to obtain its sources, or how to compile them, or any of that to make it work. I'm hoping one of the ROM devs will clue me in as I can't be the only person with this phone to ever Fubar their partition tables.
I found this :
Code:
To boot with a host-side kernel image (and rootfs image)
This command allows you to download a kernel image (and optional root filesystem image) and boot the phone with those, instead of using the kernel and rootfs in the boot flash partition. It is very useful while developing a kernel or modifying the rootfs.
fastboot boot <kernel> [ <ramdisk> ]
Ex: fastboot boot linux-2.6/arch/arm/boot/zImage root-image/recovery.img-ramdisk.cpio.gz
Which seems to suggest it's possible but I just need the correct kernel and rootfs image to boot TWRP.