Related
Recently acquired a bricked moto x pure. No way of knowing for sure how it was bricked but I'm guessing attempted downgrade. When starting up the Bootloader logs say:
AP fastboot flash mode (secure)
failed to validate boot image
ERROR: Failed to pass validation, backup to fastboot
Fastboot reason: Fall-through from charger boot mode
CID read failure
Invalid CID status 0x69
Click to expand...
Click to collapse
fastboot getvar all gives:
(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: 0x2
(bootloader) emmc: 16GB Samsung REV=07 PRV=01 TYPE=57 PNM=AGND3R
(bootloader) ram[0]: 3072MB SK Hynix S8 SDRAM DIE=6Gb M5=x6 M6=x3 M7=x0
(bootloader) ram[1]: M8=x3B
(bootloader) cpu: MSM8992
(bootloader) serialno: TA084034CW
(bootloader) cid: 0xDEAD
(bootloader) channelid: 0x8d
(bootloader) uid: 3862CC001E000000000000000000
(bootloader) unlocked: no
(bootloader) securestate: locked
(bootloader) iswarrantyvoid: no
(bootloader) mot_sst: 0
(bootloader) max-download-size: 536870912
(bootloader) reason: Fall-through from charger boot mode
(bootloader) date: 10-07-2015
(bootloader) sku: XT1575
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Wed Mar 9 14:23:32 UTC 2016"
(bootloader) ro.build.fingerprint[0]: motorola/clark_retus/clark:6.0/MPH
(bootloader) ro.build.fingerprint[1]: S24.49-18-3/3:user/release-keys
(bootloader) ro.build.version.full[0]: Blur_Version.24.201.3.clark_retus
(bootloader) ro.build.version.full[1]: .retus.en.US
(bootloader) ro.build.version.qcom: <not found>
(bootloader) version-baseband: M8992_1255331.29.01.88.02R SUPER_NA
(bootloader) kernel.version[0]: Linux version 3.10.84-perf-g6898f68 (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 Sat Jan 30 14:35:02 CST 2016
(bootloader) sbl1.git: sbl1.git
(bootloader) rpm.git: rpm.git
(bootloader) tz.git: tz.git
(bootloader) hyp.git: hyp.git
(bootloader) sdi.git: sdi.git
(bootloader) pmic.git: pmic.git
(bootloader) aboot.git: git=MBM-NG-VA0.48-0-g8c942c6
(bootloader) qe:
(bootloader) frp-state: no protection (err)
(bootloader) ro.carrier: retus
all: listed above
finished. total time: 0.422s
Click to expand...
Click to collapse
I attempted to flash the CLARK_RETUS_6.0_MPHS24.49-18-3_cid9_subsidy-DEFAULT_CFC.xml stock firmware but got the following error:
fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.094s]
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) Failed to write primary GPT.
(bootloader) Failed to program partition table
FAILED (remote failure)
finished. total time: 0.953s
Click to expand...
Click to collapse
I also tried using mfastboot, with the same results. Anybody know how to fix this?
Is your bootloader locked?
thebaconbox said:
Is your bootloader locked?
Click to expand...
Click to collapse
Yes it is. Tried to unlock it already but I get:
>fastboot oem get_unlock_data
...
(bootloader) Failed to get unlock data, please try again!
FAILED (remote failure)
finished. total time: 0.016s
Click to expand...
Click to collapse
Just ignore the gpt.bin error and continue... The partition table hasn't changed since Marshmallow released on this device.
Any reason not to use the 18-4 firmware? It is readily available...
acejavelin said:
Just ignore the gpt.bin error and continue... The partition table hasn't changed since Marshmallow released on this device.
Any reason not to use the 18-4 firmware? It is readily available...
Click to expand...
Click to collapse
I tried 18-4 as well and got the same results. 18-3 seemed to be what was on the device before it was bricked so I tried that one first. If I continue get more errors:
>fastboot flash bootloader bootloader.img
target reported max download size of 536870912 bytes
sending 'bootloader' (2699 KB)...
OKAY [ 0.094s]
writing 'bootloader'...
(bootloader) flashing aboot ...
(bootloader) Failed to erase partition
(bootloader) Failed to flash aboot
FAILED (remote failure)
finished. total time: 1.961s
>fastboot flash logo logo.bin
target reported max download size of 536870912 bytes
sending 'logo' (3687 KB)...
OKAY [ 0.141s]
writing 'logo'...
(bootloader) Failed to erase partition
(bootloader) Failed to flash partition logo
FAILED (remote failure)
finished. total time: 0.234s
Click to expand...
Click to collapse
I get the same errors if I try to flash anything.
jml1290 said:
I tried 18-4 as well and got the same results. 18-3 seemed to be what was on the device before it was bricked so I tried that one first. If I continue get more errors:
I get the same errors if I try to flash anything.
Click to expand...
Click to collapse
Try 'fastboot oem fb_mode_clear' followed by 'fastboot oem fb_mode_set' and try again.
acejavelin said:
Try 'fastboot oem fb_mode_clear' followed by 'fastboot oem fb_mode_set' and try again.
Click to expand...
Click to collapse
Here's what I get:
>fastboot oem fb_mode_clear
...
OKAY [ 0.000s]
finished. total time: 0.000s
>fastboot oem fb_mode_set
...
FAILED (remote failure)
finished. total time: 0.000s
>fastboot flash bootloader bootloader.img
target reported max download size of 536870912 bytes
sending 'bootloader' (2699 KB)...
OKAY [ 0.078s]
writing 'bootloader'...
(bootloader) flashing aboot ...
(bootloader) Failed to erase partition
(bootloader) Failed to flash aboot
FAILED (remote failure)
finished. total time: 1.561s
Click to expand...
Click to collapse
jml1290 said:
Here's what I get:
Click to expand...
Click to collapse
Hmm... Looks bad... Nothing will write, erase, or format, like the emmc module is bad.
acejavelin said:
Hmm... Looks bad... Nothing will write, erase, or format, like the emmc module is bad.
Click to expand...
Click to collapse
That's what I was afraid of. My only other idea was to try and force the phone into HS-USB QDLoader mode and fix it from there. But I have no idea how to do this and if there was something physically wrong with the emmc I doubt it would help anyway. Thanks for the input!
jml1290 said:
That's what I was afraid of. My only other idea was to try and force the phone into HS-USB QDLoader mode and fix it from there. But I have no idea how to do this and if there was something physically wrong with the emmc I doubt it would help anyway. Thanks for the input!
Click to expand...
Click to collapse
Sorry... But if the bootloader is locked you might be able to register it on your Motorola account and file a warranty claim, couldn't hurt to try.
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:
I will flash the latest POTTER_NPN25.137-35_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip but i get every time a failed.
Code:
D:\Software_Tools\Multimedia\Handy-Taplet\Handy\Backup\Download\Rom\G5Plus\POTTER_NPN25.137-35_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>mfastboot flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (45 KB)...
OKAY [ 0.000s]
writing 'partition'...
(bootloader) Validating 'gpt.default.xml'
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'gpt.default.xml'
FAILED (remote failure)
finished. total time: 0.078s
D:\Software_Tools\Multimedia\Handy-Taplet\Handy\Backup\Download\Rom\G5Plus\POTTER_NPN25.137-35_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>
D:\Software_Tools\Multimedia\Handy-Taplet\Handy\Backup\Download\Rom\G5Plus\POTTER_NPN25.137-35_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml>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' (5115 KB)...
OKAY [ 0.109s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) Security version downgrade
(bootloader) Image aboot failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'bootloader.default.xml'
FAILED (remote failure)
finished. total time: 0.390s
I recently flash the stock rom using this method, is the easiest way.
https://youtu.be/qjbU72RH_Rk
Hope this helps you...
That video is over a year old and the AFH firmware listed for G5+ isn't as complete as the latest official list here, also you don't need to install certain utilities he mentions.
HOW TO UNBRICK MOTO G5 PLUS AND RESTORE TO STOCK
I'd recommend that 4-27-17 article meant just for our phone containing a link to a toolkit with everything you need including the POTTER_NPN25.137-35 firmware. Your variant's firmware may be different though. so check in settings and get the correct one at the above link I gave, if necessary. I've successfully restored to stock several times using this method.
I have a EU Version i think. Have buy in Austria. Have download .35 but its 7.0 and not 7.1. Security Patch show me January 2017? Befor i have unlock the Bootloader its have show me March 2017 i think.
hi will it work ?
will it work definitely ?
to be able to revive but to flash the December rom stock of error
What errors are you getting? Which stock firmware version are you getting these errors with?
What device do you have and how did you hard brick your device? Which blankflash did you use?
Are you following this guide here: https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761
echo92 said:
what errors are you getting? Which stock firmware version are you getting these errors with?
What device do you have and how did you hard brick your device? Which blankflash did you use?
Are you following this guide here: https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761
Click to expand...
Click to collapse
i tried with above link but no success
prasadak2811 said:
i tried with above link but no success
Click to expand...
Click to collapse
Can you provide us with some information please as well?
What device do you have, how did your device hard brick and what errors/messages are you getting?
echo92 said:
What errors are you getting? Which stock firmware version are you getting these errors with?
What device do you have and how did you hard brick your device? Which blankflash did you use?
Are you following this guide here: https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761
Click to expand...
Click to collapse
xt 1640
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8952-B1.07
(bootloader) product: athene_16mp
(bootloader) board: athene_16mp
(bootloader) secure: yes
(bootloader) hwrev: P2A
(bootloader) radio: 6
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG QX13MB 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: 0038111937
(bootloader) cid: 0xDEAD
(bootloader) channelid: 0x00
(bootloader) uid: D6EBBF0200000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: n/a
(bootloader) max-download-size: 536870912
(bootloader) reason: UTAG "bootmode" configured as fastboot
(bootloader) imei:
(bootloader) meid:
(bootloader) date: 09-15-2017
(bootloader) sku: XT1640-DS
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Wed May 4 19:56:34 UTC 2016"
(bootloader) ro.build.fingerprint[0]: motorola/athene_f/athene_f:7.0/NPJ
(bootloader) ro.build.fingerprint[1]: S25.93-14-13/3:user/release-keys
(bootloader) ro.build.version.full[0]: Blur_Version.25.226.3.athene.reta
(bootloader) ro.build.version.full[1]: il.pt.BR
(bootloader) ro.build.version.qcom: LA.BR.1.3.6-01710-8976.0
(bootloader) version-baseband: M8952_70030.25.03.62.01R DFLT_FSG
(bootloader) kernel.version[0]: Linux version 3.10.84-ElementalX-G4-2.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 Thu Jan 25 12:45:01 EST 2018
(bootloader) sbl1.git: git=MBM-NG-VB1.07-0-g57d1343
(bootloader) rpm.git: git=MBM-NG-VB1.06-0-ga970ead
(bootloader) tz.git: git=69dd24b-dirty
(bootloader) hyp.git: git=69dd24b-dirty
(bootloader) keymaster.git: git=69dd24b-dirty
(bootloader) cmnlib.git: git=69dd24b-dirty
(bootloader) aboot.git: git=MBM-NG-VB1.07-0-gf9b89ba
(bootloader) qe: qe 0/0
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: retbr
all: listed above
finished. total time: 0.488s
echo92 said:
What errors are you getting? Which stock firmware version are you getting these errors with?
What device do you have and how did you hard brick your device? Which blankflash did you use?
Are you following this guide here: https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761
Click to expand...
Click to collapse
I'm getting these errors
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.024s]
writing 'partition'...
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
OKAY [ 0.111s]
finished. total time: 0.138s
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.158s]
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.459s]
finished. total time: 0.622s
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.101s]
writing 'logo'...
OKAY [ 0.064s]
finished. total time: 0.170s
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.593s]
writing 'boot'...
(bootloader) Image boot failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.801s
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.590s]
writing 'recovery'...
(bootloader) Image recovery failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.802s
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.573s]
writing 'dsp'...
OKAY [ 0.267s]
finished. total time: 0.845s
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.297s]
writing 'oem'...
(bootloader) Image o failed validation
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 3.425s
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.868s]
writing 'system'...
(bootloader) Image s failed validation
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 8.995s
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 [ 8.556s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 8.622s
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' (254493 KB)...
OKAY [ 8.667s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 8.714s
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' (247302 KB)...
OKAY [ 8.439s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 8.518s
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' (260402 KB)...
OKAY [ 8.872s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 8.918s
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' (262057 KB)...
OKAY [ 8.904s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 8.956s
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.897s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 8.977s
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.817s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 2.876s
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' (76958 KB)...
OKAY [ 2.624s]
writing 'modem'...
OKAY [ 1.136s]
finished. total time: 3.764s
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.040s]
finished. total time: 0.043s
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.039s]
finished. total time: 0.041s
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.096s]
writing 'fsg'...
OKAY [ 0.077s]
finished. total time: 0.179s
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.042s]
finished. total time: 0.049s
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.120s]
finished. total time: 0.122s
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.033s]
finished. total time: 0.035s
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.031s]
finished. total time: 0.033s
C:\Program Files (x86)\Minimal ADB and Fastboot>
jadeilson777 said:
I'm getting these errors
<snip>
Click to expand...
Click to collapse
Thanks for that. A few things I've noted:
1)I'm not sure what's happened to your device, and perhaps you can elaborate on if anything happened before, but the CID=0xDEAD and the odd serial number (unless you changed that) and no presence of the iswarrantyvoid parameter is concerning. Did you try to restore a backup or give your device to a JTAG service, or did you use a blankflash?
2)Your radio baseband version is reporting DFLT_FSG as opposed to BRAZIL, so you may have no network access, though that might be immaterial at this point.
3)Which firmware are you trying to flash at the moment that is giving you the validation errors (e.g. Image boot failed validation?) Is it the NPJS25.93-14-13 Dec 2017 firmware? I note your device is running Blur_Version.25.226.3.athene.retail.pt.BR whereas the stock ROM on XDA is Blur_Version.25.226.3.athene.retail.en.US but I don't know if the different languages are that significant. Verify that you're flashing the NPJS25.93-14-13 stock ROM.
If you are flashing the NPJS25.93-14-13 stock ROM on XDA, I'm concerned that only an expensive motherboard replacement may fix the issues. However, please answer the questions I've asked so we have more information to help you. You can type your response in Portuguese or your native language and then use Google Translate or your favourite translator to translate your response into English if you so choose.
echo92 said:
Thanks for that. A few things I've noted:
1)I'm not sure what's happened to your device, and perhaps you can elaborate on if anything happened before, but the CID=0xDEAD and the odd serial number (unless you changed that) and no presence of the iswarrantyvoid parameter is concerning. Did you try to restore a backup or give your device to a JTAG service, or did you use a blankflash?
2)Your radio baseband version is reporting DFLT_FSG as opposed to BRAZIL, so you may have no network access, though that might be immaterial at this point.
3)Which firmware are you trying to flash at the moment that is giving you the validation errors (e.g. Image boot failed validation?) Is it the NPJS25.93-14-13 Dec 2017 firmware? I note your device is running Blur_Version.25.226.3.athene.retail.pt.BR whereas the stock ROM on XDA is Blur_Version.25.226.3.athene.retail.en.US but I don't know if the different languages are that significant. Verify that you're flashing the NPJS25.93-14-13 stock ROM.
If you are flashing the NPJS25.93-14-13 stock ROM on XDA, I'm concerned that only an expensive motherboard replacement may fix the issues. However, please answer the questions I've asked so we have more information to help you. You can type your response in Portuguese or your native language and then use Google Translate or your favourite translator to translate your response into English if you so choose.
Click to expand...
Click to collapse
1) I was in the stock rom of December with elemental kernel x to get root with magisk and was without network because of the baseband and I looked in the forum something about there I tried to transfer some files of the 1643 xt was when the hard brick occurred I used the recent blankflash and able to revive the bootloader but when trying to flash again the stock of December gave error plus the boot loader went back to normal as in the attached image
echo92 said:
Thanks for that. A few things I've noted:
1)I'm not sure what's happened to your device, and perhaps you can elaborate on if anything happened before, but the CID=0xDEAD and the odd serial number (unless you changed that) and no presence of the iswarrantyvoid parameter is concerning. Did you try to restore a backup or give your device to a JTAG service, or did you use a blankflash?
2)Your radio baseband version is reporting DFLT_FSG as opposed to BRAZIL, so you may have no network access, though that might be immaterial at this point.
3)Which firmware are you trying to flash at the moment that is giving you the validation errors (e.g. Image boot failed validation?) Is it the NPJS25.93-14-13 Dec 2017 firmware? I note your device is running Blur_Version.25.226.3.athene.retail.pt.BR whereas the stock ROM on XDA is Blur_Version.25.226.3.athene.retail.en.US but I don't know if the different languages are that significant. Verify that you're flashing the NPJS25.93-14-13 stock ROM.
If you are flashing the NPJS25.93-14-13 stock ROM on XDA, I'm concerned that only an expensive motherboard replacement may fix the issues. However, please answer the questions I've asked so we have more information to help you. You can type your response in Portuguese or your native language and then use Google Translate or your favourite translator to translate your response into English if you so choose.
Click to expand...
Click to collapse
2) Yes I was without a network and was trying to fix what happened to the hard brick
3) Yes I am trying to flash the December rom stock NPJS25.93-14-13
jadeilson777 said:
1) I was in the stock rom of December with elemental kernel x to get root with magisk and was without network because of the baseband and I looked in the forum something about there I tried to transfer some files of the 1643 xt was when the hard brick occurred I used the recent blankflash and able to revive the bootloader but when trying to flash again the stock of December gave error plus the boot loader went back to normal as in the attached image
Click to expand...
Click to collapse
jadeilson777 said:
2) Yes I was without a network and was trying to fix what happened to the hard brick
3) Yes I am trying to flash the December rom stock NPJS25.93-14-13
Click to expand...
Click to collapse
Hmm, what files did you try to transfer, was it the hw, fsg and modem partitions, and did you transfer them to the correct partitions? Those commands are very powerful and will not alert you if the incorrect partition is overwritten.
I'm guessing by the screenshot you're showing that your bootloader screen is similar, as that bootloader screen is for Osprey devices (Moto G 2015). It should be like that as you've flashed the bootloader from the stock NPJS25.93-14-13 ROM, just with athene (Moto G4) details.
How did you lose network in the first place, was it after flashing firmware?
If you can, I'd doublecheck if your bootloader is unlocked and try unlocking your bootloader (which will erase your information), as looking through your flash results, it looks like your bootloader is rejecting your flashing. NPJS25.93-14-13 should not give you pre-flash validation errors on a G4 Plus as that's the current firmware we have, unless you've flashed a different December 2017 build before or received an OTA update newer than December 2017.
If unlocking the bootloader doesn't work or doesn't resolve not being able to flash, then we may have to begin considering an expensive service repair.
echo92 said:
Hmm, what files did you try to transfer, was it the hw, fsg and modem partitions, and did you transfer them to the correct partitions? Those commands are very powerful and will not alert you if the incorrect partition is overwritten.
I'm guessing by the screenshot you're showing that your bootloader screen is similar, as that bootloader screen is for Osprey devices (Moto G 2015). It should be like that as you've flashed the bootloader from the stock NPJS25.93-14-13 ROM, just with athene (Moto G4) details.
How did you lose network in the first place, was it after flashing firmware?
If you can, I'd doublecheck if your bootloader is unlocked and try unlocking your bootloader (which will erase your information), as looking through your flash results, it looks like your bootloader is rejecting your flashing. NPJS25.93-14-13 should not give you pre-flash validation errors on a G4 Plus as that's the current firmware we have, unless you've flashed a different December 2017 build before or received an OTA update newer than December 2017.
If unlocking the bootloader doesn't work or doesn't resolve not being able to flash, then we may have to begin considering an expensive service repair.
Click to expand...
Click to collapse
my bootloader is blocked and in my opinion this is giving pre-flash error pq was in stock rom December with twrp and with elemental kernbel x
jadeilson777 said:
my bootloader is blocked and in my opinion this is giving pre-flash error pq was in stock rom December with twrp and with elemental kernbel x
Click to expand...
Click to collapse
If your bootloader is locked, then having TWRP and ElementalX on your device will cause your device to fail to boot. A locked bootloader, especially under Nougat, is quite strictly enforced, and is expecting stock recovery and stock kernel, no modifications whatsoever.
The stock ROM flash should be overwriting both partitions with the stock firmware, but as you're not bypassing the strict verification checks, then you can try to unlock your bootloader again and try to re-flash. Alternatively, if you unlock, you may be able to boot if there's still TWRP and ElementalX on your device. Your warranty is voided anyway as you'd have unlocked your bootloader in the past to flash TWRP and ElementalX.
If that doesn't work, it may suggest the flash memory or another hardware fault is present, which may require a motherboard replaement.
echo92 said:
If your bootloader is locked, then having TWRP and ElementalX on your device will cause your device to fail to boot. A locked bootloader, especially under Nougat, is quite strictly enforced, and is expecting stock recovery and stock kernel, no modifications whatsoever.
The stock ROM flash should be overwriting both partitions with the stock firmware, but as you're not bypassing the strict verification checks, then you can try to unlock your bootloader again and try to re-flash. Alternatively, if you unlock, you may be able to boot if there's still TWRP and ElementalX on your device. Your warranty is voided anyway as you'd have unlocked your bootloader in the past to flash TWRP and ElementalX.
If that doesn't work, it may suggest the flash memory or another hardware fault is present, which may require a motherboard replaement.
Click to expand...
Click to collapse
I already tried to unlock the bootloader but I get the result of fetuare disable which is the debugging usb or unlock option of oem that is disabled
jadeilson777 said:
I already tried to unlock the bootloader but I get the result of fetuare disable which is the debugging usb or unlock option of oem that is disabled
Click to expand...
Click to collapse
That's not good - can you boot into the system? If so, you can go to Settings>About Phone, tap the build 7 times, then go back one menu, access Developer Options and then toggle OEM unlocking, which should then let you unlock your bootloader.
If you've re-locked your bootloader and you cannot boot, then unfortunately you may have to consider a motherboard replacement (expensive) or put the money towards a new device. I think we don't have the means to bypass the bootloader security lock if you cannot boot into the system.
echo92 said:
That's not good - can you boot into the system? If so, you can go to Settings>About Phone, tap the build 7 times, then go back one menu, access Developer Options and then toggle OEM unlocking, which should then let you unlock your bootloader.
If you've re-locked your bootloader and you cannot boot, then unfortunately you may have to consider a motherboard replacement (expensive) or put the money towards a new device. I think we don't have the means to bypass the bootloader security lock if you cannot boot into the system.
Click to expand...
Click to collapse
if I was in hard brick but can revive only the bootloader and the system can not activate these options so there is no way to flip the bootloader and with the bootloader locked I can not flashear a previous ROM nor the stock of December pq was with the elemental kernel x of January 25th so I have to wait for a security patch update to flash over
echo92 said:
That's not good - can you boot into the system? If so, you can go to Settings>About Phone, tap the build 7 times, then go back one menu, access Developer Options and then toggle OEM unlocking, which should then let you unlock your bootloader.
If you've re-locked your bootloader and you cannot boot, then unfortunately you may have to consider a motherboard replacement (expensive) or put the money towards a new device. I think we don't have the means to bypass the bootloader security lock if you cannot boot into the system.
Click to expand...
Click to collapse
I'm 16 years old and I do not have money for another motherboard or a new moto g4 plus
jadeilson777 said:
if I was in hard brick but can revive only the bootloader and the system can not activate these options so there is no way to flip the bootloader and with the bootloader locked I can not flashear a previous ROM nor the stock of December pq was with the elemental kernel x of January 25th so I have to wait for a security patch update to flash over
Click to expand...
Click to collapse
Yeah, hopefully the February 2018 security patch ROM should be on its way soon. If that doesn't fix things then you may have to visit a service centre.
---------- Post added at 06:56 PM ---------- Previous post was at 06:53 PM ----------
jadeilson777 said:
I'm 16 years old and I do not have money for another motherboard or a new moto g4 plus
Click to expand...
Click to collapse
Unfortunately a hard brick in this manner seems to be quite hard to fix, especially if you cannot flash the stock ROM (with a locked bootloader failing validation). However, we'll have to see if the newer stock ROM resolves this.
echo92 said:
Yeah, hopefully the February 2018 security patch ROM should be on its way soon. If that doesn't fix things then you may have to visit a service centre.
---------- Post added at 06:56 PM ---------- Previous post was at 06:53 PM ----------
Unfortunately a hard brick in this manner seems to be quite hard to fix, especially if you cannot flash the stock ROM (with a locked bootloader failing validation). However, we'll have to see if the newer stock ROM resolves this.
Click to expand...
Click to collapse
Can you tell me when the next update comes out if and still this month?
jadeilson777 said:
Can you tell me when the next update comes out if and still this month?
Click to expand...
Click to collapse
Honestly no idea - we've not even seen the OTA update for the February 2018 security update, just the patch notes. Could be this month, could be next month. Furthermore, that still relies on someone capturing and uploading the stock ROM firmware with that patch to Android FileHost or somewhere.
Hello there,
I am trying to root my nokia 6 TA - 1033.
(bootloader) version:0.5
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:4029000
(bootloader) variant:FIH eMMC
(bootloader) unlocked:no
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) display-panel:
(bootloader) off-mode-charge:0
(bootloader) charger-screen-enabled:0
(bootloader) max-download-size: 0xf0000000
(bootloader) partition-type:userdata:ext4
(bootloader) kernel:lk
(bootloader) product1C
1. cmd : fastboot oem dm-verity XXXXXXXXXXXXXXXXXXXXXXXX (MD5 number)
FAILED (remote: unknown command)
finished. total time: 0.005s
2. no help with this cmd too : adb reboot "dm-verity enforcing"
fastboot oem disable_dm_verity
3. fastboot flash recovery /home/$USER/me.twrp.twrpapp-26.apk
target reported max download size of 535822336 bytes
sending 'recovery' (2703 KB)...
OKAY [ 0.109s]
writing 'recovery'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 0.113s
gaganhere said:
Hello there,
I am trying to root my nokia 6 TA - 1033.
(bootloader) version:0.5
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:4029000
(bootloader) variant:FIH eMMC
(bootloader) unlocked:no
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) display-panel:
(bootloader) off-mode-charge:0
(bootloader) charger-screen-enabled:0
(bootloader) max-download-size: 0xf0000000
(bootloader) partition-type:userdata:ext4
(bootloader) kernel:lk
(bootloader) product1C
1. cmd : fastboot oem dm-verity XXXXXXXXXXXXXXXXXXXXXXXX (MD5 number)
FAILED (remote: unknown command)
finished. total time: 0.005s
2. no help with this cmd too : adb reboot "dm-verity enforcing"
fastboot oem disable_dm_verity
3. fastboot flash recovery /home/$USER/me.twrp.twrpapp-26.apk
target reported max download size of 535822336 bytes
sending 'recovery' (2703 KB)...
OKAY [ 0.109s]
writing 'recovery'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 0.113s
Click to expand...
Click to collapse
WhatsApp me at 9650710447 for bootloader unlock
sltushar said:
WhatsApp me at 9650710447 for bootloader unlock
Click to expand...
Click to collapse
I also want to root nokia 6.1 plus
rohitgnw said:
I also want to root nokia 6.1 plus
Click to expand...
Click to collapse
I also want to root my device.... Any help?
rohitgnw said:
I also want to root nokia 6.1 plus
Click to expand...
Click to collapse
You need bootloader unlock key, pm me for that on WhatsApp