Related
Hi guys.Im form Bosnia,and i have bad english,sorry for that.I have HTC M9+ and i have one really big problem for me.My phone is soft bricked.When i want to instal TWRP on my phone i use ADB tool and download twrp form site and type on command fastboot flash recovery recovery.img i have this massage on command
target reported max download size of 800000000 bytes
sending 'recovery' (9708 KB)...
OKAY [ 1.439s]
writing 'recovery'...
(bootloader) HOSD CL#522373
(bootloader) [email protected]
(bootloader) [email protected]%
(bootloader) Update partition OK
(bootloader) [email protected]
OKAY [ 1.210s]
finished. total time: 2.651s
And when i want to join on recovery on my phone i have this massage
THIS BUILD IS FOR
DEVELOPMENT PURPOSES ONLY
DO NOT DISTRIBUTE OUTSIDE OF HTC
WITHOUT HTCs WRITTEN PERMISSION
FAILURE TO COMPLY MAY
LEAD TO LEGAL ACTION.
I need really help and thanks guys.
I need help,please.
can you post some information from you bootloader and indicate if your trying to make a factory reset ? i will try to help you
That message is standard for all HTC after bootloader unlock and installation of a custom recovery. NOthing to worry about. Did you flash the right recovery image, as in one that was specifically developed for this device?
ag6ag said:
can you post some information from you bootloader and indicate if your trying to make a factory reset ? i will try to help you
Click to expand...
Click to collapse
RayToral]C:\Users\RayToral\Desktop\Fastboot HTC>fastboot getvar all
(bootloader) kernel: lk
(bootloader) product: htc_hiau_ml_tuhl
(bootloader) version: 1.0
(bootloader) imei:
(bootloader) version-main: 1.06.1405.1
(bootloader) boot-mode: RUU
(bootloader) version-bootloader: 1.01.0000
(bootloader) mid: 0PK711000
(bootloader) cid: HTCCN701
all:
finished. total time: 0.016s
Im try to install all version of twrp from this site for this mobile,and always same thing.
https://dl.twrp.me/hima/
This is picture from download mode.
http://img.xda-balkan.com/image.uploads/10-12-2016/original-525efc91bed11e8db91e5e2732721527.jpeg
bro this is not for m9+ this is for m9 only !
you have to install this twrp http://forum.xda-developers.com/one-m9/one-m9-general/recovery-twrp-2-8-6-0-english-m9pw-t3116099
ag6ag said:
bro this is not for m9+ this is for m9 only !
you have to install this twrp http://forum.xda-developers.com/one-m9/one-m9-general/recovery-twrp-2-8-6-0-english-m9pw-t3116099
Click to expand...
Click to collapse
Cant download this.Do you have a different link for download?
https://www.mediafire.com/?wlux7k71xsl6bk6
md5 : C3AD293A7BBFB829D5904FFC6F9119C2 credit goes to tbalden
ag6ag said:
https://www.mediafire.com/?wlux7k71xsl6bk6
md5 : C3AD293A7BBFB829D5904FFC6F9119C2 credit goes to tbalden
Click to expand...
Click to collapse
They work.Thank you man.
Remove your IMEI from all the post..
naughty6t9 said:
Remove your IMEI from all the post..
Click to expand...
Click to collapse
Its removed
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!
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:
So i unlocked the bootloader using the code that you get from the motorola official website and then installed twrp. It all went just find, but then I flashed the magisk zip and tried booting up but no response. Its like the power button doesnt work at all. Fastboot mode is still working and i can get into the recovery, tried restoring the old backup, factory reset, installing a rom (RR) but no luck. pls help this fella
Wipe data. Install the ROM of your choice.
If that fails, flash your device's stock ROM.
You have to flash a custom kernel like ElementalX before rooting because magisk roots your phone by patching the boot image which isn't supported by the stock kernel! This is why your phone is not booting up!
If you can still access bootloader mode, try this https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369
Saumitraa said:
You have to flash a custom kernel like ElementalX before rooting because magisk roots your phone by patching the boot image which isn't supported by the stock kernel! This is why your phone is not booting up!
If you can still access bootloader mode, try this https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369
Click to expand...
Click to collapse
i see, will try this right now
Darkther said:
i see, will try this right now
Click to expand...
Click to collapse
You have to flash the custom kernel before rooting only when you are on stock or stock based roms and not on custom roms! Good Luck
Saumitraa said:
You have to flash the custom kernel before rooting only when you are on stock or stock based roms and not on custom roms! Good Luck
Click to expand...
Click to collapse
while flashing the images i am getting the following error
Code:
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:partition: not found
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.006s]
writing 'partition'...
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.054s
Darkther said:
while flashing the images i am getting the following error
Click to expand...
Click to collapse
Looks like you are trying to get back to stock, follow the steps here
https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369
Darkther said:
while flashing the images i am getting the following error
Code:
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:partition: not found
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.006s]
writing 'partition'...
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.054s
Click to expand...
Click to collapse
If the above firmware isn't working, it might be because the firmware you're trying to flash is too old; you may have to flash the March 2017 firmware (the latest firmware we have) which is here: https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
Hello,
I have bricked my bootloader in the past to refresh my bootloader. I have unbricked my phone to bootloader 1.03 with blank flash. Now when i try to flash, erase do ANYTHING it won't allow me because my OEM_LOCKED state. If i try to unlock my bootloader it says:
Code:
(bootloader) Check 'Allow OEM Unlock' in Android Settings > Developer
(bootloader) Options
OKAY [ 0.032s]
finished. total time: 0.036s
but there is no android installed.
When i try to flash a stock rom it says:
Code:
C:\Users\nick\Desktop\total firmware>fastboot flash logo logo.bin
target reported max download size of 536870912 bytes
sending 'logo' (1848 KB)...
OKAY [ 0.068s]
writing 'logo'...
(bootloader) Invalid partition name logo
FAILED (remote failure)
finished. total time: 0.088s
C:\Users\nick\Desktop\total firmware>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.540s]
writing 'boot'...
(bootloader) Invalid partition name boot
FAILED (remote failure)
finished. total time: 0.576s
C:\Users\nick\Desktop\total firmware>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (16484 KB)...
OKAY [ 0.548s]
writing 'recovery'...
(bootloader) Invalid partition name recovery
FAILED (remote failure)
finished. total time: 0.568s
C:\Users\nick\Desktop\total firmware>fastboot flash dsp adspso.bin
target reported max download size of 536870912 bytes
sending 'dsp' (16384 KB)...
OKAY [ 0.532s]
writing 'dsp'...
(bootloader) Invalid partition name dsp
FAILED (remote failure)
finished. total time: 0.560s
C:\Users\nick\Desktop\total firmware>fastboot flash oem oem.img
target reported max download size of 536870912 bytes
sending 'oem' (124713 KB)...
OKAY [ 3.993s]
writing 'oem'...
(bootloader) Invalid partition name oem
FAILED (remote failure)
finished. total time: 4.017s
C:\Users\nick\Desktop\total firmware>fastboot flash system system.img_sparsechunk.0
target reported max download size of 536870912 bytes
sending 'system' (261790 KB)...
Everything is 'invalid partition name'.
when i try to brick my bootloader again to install try again it says
Code:
target max-sparse-size: 256MB
sending 'sbl1' (264 KB)...
OKAY [ 0.020s]
writing 'sbl1'...
(bootloader) Invalid partition name sbl1
FAILED (remote failure)
finished. total time: 0.036s
rebooting...
And when i try to flash another bootloader it says:
Code:
PS C:\Users\nick\Desktop\total firmware> fastboot flash bootloader bootloader.img
target reported max download size of 536870912 bytes
sending 'bootloader' (3651 KB)...
OKAY [ 0.141s]
writing 'bootloader'...
(bootloader) validating: bootloader.default.xml ...
(bootloader) Invalid partition name aboot
(bootloader) will fail: flash:aboot
FAILED (remote failure)
finished. total time: 0.250s
PS C:\Users\nick\Desktop\total firmware>
please help
I guess there is a partion problem
Look into this thread
https://forum.xda-developers.com/showthread.php?t=3496912
Sent from my Moto G4 Plus using Tapatalk
Yes i know, but i cant flash any partitions or fix Them. I have Read the whole threath but i cannot find a solution.
codGmer said:
Yes i know, but i cant flash any partitions or fix Them. I have Read the whole threath but i cannot find a solution.
Click to expand...
Click to collapse
Did you run all stock steps in order? In particular this one first:
Code:
fastboot flash partition gpt.bin
That will restore your partition table which seems to be messed up. Make sure you try to restore firmware version that was last working for you.
If your phone is completely wiped and you have no backups of ALL of the partitions, I doubt you can recover as some of the partitions have phone specific data for IMEIs and such.
givitago said:
Did you run all stock steps in order? In particular this one first:
Code:
fastboot flash partition gpt.bin
That will restore your partition table which seems to be messed up. Make sure you try to restore firmware version that was last working for you.
If your phone is completely wiped and you have no backups of ALL of the partitions, I doubt you can recover as some of the partitions have phone specific data for IMEIs and such.
Click to expand...
Click to collapse
I dont think all is wiped but when i try to flash the gpt.bin it says 'cannot find partition gpt'
codGmer said:
Did you run all stock steps in order? In particular this one first:
I dont think all is wiped but when i try to flash the gpt.bin it says 'cannot find partition gpt'
Click to expand...
Click to collapse
I too have this question bro .... Plus help me if you find a solution ... I m a newbie... Nd face the same problem as yours
Sounds like fastboot expects a working partition table to start with then.
I would boot into twrp from fastboot (from an image on your PC) and use adb shell to take a look at what the flash looks like (fdisk -l command). You may have to restore the partition table first via sgdisk or dd. I've never done it and I'm no expert on this stuff but Google is your friend. General linux forums are just as helpful as android specific forums as at this level, we aren't even talking about android.
Good luck.
givitago said:
Sounds like fastboot expects a working partition table to start with then.
I would boot into twrp from fastboot (from an image on your PC) and use adb shell to take a look at what the flash looks like (fdisk -l command). You may have to restore the partition table first via sgdisk or dd. I've never done it and I'm no expert on this stuff but Google is your friend. General linux forums are just as helpful as android specific forums as at this level, we aren't even talking about android.
Good luck.
Click to expand...
Click to collapse
Im affraid i already tried booting twrp but without success.
Code:
(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: 3
(bootloader) storage-type: emmc
(bootloader) emmc: 16GB SAMSUNG QE13MB RV=08 PV=07 FV=0000000000000007
(bootloader) ram: 2GB SAMSUNG LP3 DIE=8Gb M5=01 M6=05 M7=00 M8=1F
(bootloader) cpu: MSM8952
(bootloader) serialno: 74f9d6fa
(bootloader) cid: 0x0032
(bootloader) channelid: 0x40
(bootloader) uid: A420B70000000000000000000000
(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.147s
hey bro , did you get any solution of this problem?
i am getting
fastboot reason : failed to initialize partition table
any solution?
king_priithvi said:
hey bro , did you get any solution of this problem?
Click to expand...
Click to collapse
Provide more information of your problem/situation,
what happened ?
Have you flashed any firmware ?
Took any OTA ?
What was firmware version you were using ?
Tried latest December's firmware ? This> https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
I think you're flashing older bootloader & GPT then it is already installed on your device;
take a look here: https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
from that thread download the latest ROM and firstly flash GPT and boot-loader by following command:
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
but however after flashing the latest firmware the current blankflash that we have won't work, because GPT and boot-loader version is higher.
now after you flashed the GPT and bootloader then flash the whole firmware by following commands:
Code:
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 dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot
Now once you flashed it then you're good to go:good:
i cant flash anything , my android is not installed
it kept saying
AP Fastboot Flash Mode (Secure)
Fastboot Reason: Failed to initialize partition table
ERROR: No BootImage Found. skip to fastboot
boot up failed
king_prithvi said:
i cant flash anything , my android is not installed
it kept saying
AP Fastboot Flash Mode (Secure)
Fastboot Reason: Failed to initialize partition table
ERROR: No BootImage Found. skip to fastboot
boot up failed
Click to expand...
Click to collapse
Are you able to flash the latest stock ROM via fastboot? https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
I am getting an error when I try to flash twrp. I want to make sure I am doing it right
in the linux terminal I typed this
adb reboot bootloader
then
fastboot flash recovery twrp-3.2.1-motorola-x4.img
then I got this error
target reported max download size of 536870912 bytes
sending 'recovery' (19276 KB)...
OKAY [ 0.447s]
writing 'recovery'...
(bootloader) Invalid partition name recovery
FAILED (remote failure)
finished. total time: 0.453s
has anyone else run into this problem. Am I doing something wrong?
kiyip said:
I am getting an error when I try to flash twrp. I want to make sure I am doing it right
in the linux terminal I typed this
adb reboot bootloader
then
fastboot flash recovery twrp-3.2.1-motorola-x4.img
then I got this error
target reported max download size of 536870912 bytes
sending 'recovery' (19276 KB)...
OKAY [ 0.447s]
writing 'recovery'...
(bootloader) Invalid partition name recovery
FAILED (remote failure)
finished. total time: 0.453s
has anyone else run into this problem. Am I doing something wrong?
Click to expand...
Click to collapse
What device do you have? I'm guessing it's a Moto X4 from the TWRP name?
Are you on Nougat or Oreo? From looking at this thread, you've got 2 different build: https://forum.xda-developers.com/moto-x4/development/dev-testing-t3707432
If you are running a X4, you may have better luck over there rather than here on the Moto G4 forums, as there's more users familiar with the A/B partitioning on the Moto X4.
Ohh my bad, I had like 6 xda tabs open, I actually meant to post it there. My bad man, thank you!
got the same problem any luck yet?
Any luck yet? I got a suggestion that the problem could only get fixed flashing the memory of the phone directly with this kind of device... (search for the octopus box, I cant post links yet im new here) but im lost and they say that thing is expensive... I really want my phone to be saved on my computer. My case is exactly the same as you.... oem locked and failed partition everything and remote failure.
SOLVED!! Failed to initialize partition table
..
First of all convert phone to hard brick to Softbrick...
After that if you want to bootup phone than..IT shows bootloader log::
Failed to initialize partition Table
SOLUTION:-
1) Download Minimal ADB Drivers , gpt.bin, Motorola Device driver
For link mail me on [email protected]
2.) Now Install adb and motorola drivers .
3.) Copy gpt.bin file in ADB folder in installed drive.
4.) Open Minimal ADB and Fastboot.exe
Now Run the following command
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot reboot
The cell phone should restart after this if you do not type the last code and enter if still yes it is not just hang up and call to enter the fastboot.
Now YOUR PROBLEM SOLVED
codGmer said:
I dont think all is wiped but when i try to flash the gpt.bin it says 'cannot find partition gpt'
Click to expand...
Click to collapse
Even I got the same error. Its because adb couldn't find the gpt.bin file in the adb folder from where you had executed the command window.
Copy the gpt.biin file in that folder and try again, that should work.