Related
Hi All,
I have seemingly broken my system partition and can't boot into Android.
The phone always boots to the bootloader.
Fastboot, Hboot, and stock recovery all work.
Factory reset works, but fixes nothing.
Flashing TWRP works, but it fails to boot into the recovery and returns to the bootloader.
I do not have S-off. I cannot try the Sunshine S-off as I cannot boot the phone.
I have tried flashing a matching stock rom (easy-firmware com/index.php?a=browse&b=category&id=722), but it fails as it has a different CID.
This is my getvar output.
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: [email protected]
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.05.980.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: a51_tuhl
(bootloader) platform: hTCBmsm8939
(bootloader) modelid: 0PFJ50000
(bootloader) cidnum: HTC__039
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 735c2625
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
(bootloader) mfg-name: 0001
I'm in New Zealand, and I believe the phone is the Australian version, CID: HTC__39.
Does anyone know how I can fix this?
Thanks in advance.
James
I haven't seen a working TWRP for your device model.
Which twrp have you tried? Did you unlock your bootloader?
tomal said:
I haven't seen a working TWRP for your device model.
Which twrp have you tried? Did you unlock your bootloader?
Click to expand...
Click to collapse
Yes, bootloader is unlocked.
I've tried a few of the recoveries on the 820 forums, though I don't remember exactly which ones now.
Edit: This one: "Desire 820 (all models with MSM chipset) TWRP 2.8.7.0"
The working recovery I have is not my original stock one, but one I found on the forums.
Edit: I guess I should mention what I did to break it:
Before I knew the the 820s was dual-sim, I followed these instructions: "[Desire 820s][A50ML]Root - CWM Recovery - Stock Roms - Stock Rom Flashable Zip"
I rooted the phone with Kingroot, but nothing stuck after a reboot.
So without thinking, I flashed a boot img that was meant to allow permanent root onto a partition - thus breaking the system.
I find it disappointing when manufacturers make multiple versions of the same device and I have the one with the least development.
Do you know of anything else I can do to fix the system on the phone?
From the description of above, it seems the variant of a 820n.
emjas said:
I flashed a boot img that was meant to allow permanent root onto a partition - thus breaking the system
Click to expand...
Click to collapse
Check the following link:
0PFJIMG_A51_TUHL_K44_DESIRE_SENSE60_Optus_AU -
http://mobilefileserver.com/category.aspx?get=39048
Thanks for that tomal.
I'll give it a go sometime and return with the result.
Hey tomal, I've successfully restored my phone by flashing the right firmware. Thanks for finding it.
Do you know if it is possible to permanently root or s-off this model?
Kingroot works, but system changes are reverted on reboot.
The modified boot.img and twrp recoveries found on the forum don't work and make the phone unbootable, until I flash the stock img back onto it.
Hello,
The first day I got my moto x style (XT1572) I started to root, everything was more or less well until I tried to install the SU when I finished installing the binary from the TWRP custom recovery-3.0.2-0- clark you say yes to install the root since the phone would not start and remains in boot loop.
After much look I followed some tutorial XDA (http://forum.xda-developers.com/moto-x-style/help/brick-downgrade-6-0-to-5-1-heeeeelp-t3253716) to return to flash the phone with the rom that theory came from factory cbox1s_XT1572_CLARK_RETEU_6.0_MPHS24.49-18-3_cid7_subsidy-DEFAULT_CFC.xml after following all the steps mobile and well lit and seems it was all sorted.
Well, I went back to the load to make root and remove the message that the bootloader was unlocked this time all fu well, except now every time I reboot I enter into fastboot mode and have to select START to boot normal to me.
Any ideas or suggestions to fix it?
regards,
PD: Sorry for my google translate english i'am spanish a my english level is very bad :crying:
SOLVED, the problem was the BP Tools in the fastboot, i had "Fastboot Reason: UTAG "bootmode" configured as fastboot" i changed to "Normal Powerup" and all perfect
same problem with Motorola z xt1650-03 , unlocked bootloader , every time I start up remain stuck in fastboot mode , after ,push the power button for start , and start normal.
I try to reload stock firmware 7.0 with fastboot mode but when try to flash partition.gpt he say bad key .
now I used like this ,
sagutxo97 said:
SOLVED, the problem was the BP Tools in the fastboot, i had "Fastboot Reason: UTAG "bootmode" configured as fastboot" i changed to "Normal Powerup" and all perfect
Click to expand...
Click to collapse
What? how do you do it? can you tell me how to do it more specific? I'm new so I don't understand what you mean and how you do it :/
thank you.
Moto devices have a flashing mode called "fb_mode" that when enabled causes the bootloader to start on each boot, it is used for flashing stock firmware images since in some cases the device needs to reboot after flashing a certain partition or image and it needs a way to return to the fastboot mode. Remember when flashing a stock image you may have entered "fastboot oem fb_mode_set"? If not then a toolkit or other flashing tool may have done it but not cleared it correctly. To clear it manually you need to literally clear it with a fastboot command... With the phone in the bootloader, enter this command from your computer"
fasboot oem fb_mode_clear
And reboot, it should no longer go to the bootloader unless you are holding VOL DN and the operating system should start normally.
acejavelin said:
Moto devices have a flashing mode called "fb_mode" that when enabled causes the bootloader to start on each boot, it is used for flashing stock firmware images since in some cases the device needs to reboot after flashing a certain partition or image and it needs a way to return to the fastboot mode. Remember when flashing a stock image you may have entered "fastboot oem fb_mode_set"? If not then a toolkit or other flashing tool may have done it but not cleared it correctly. To clear it manually you need to literally clear it with a fastboot command... With the phone in the bootloader, enter this command from your computer"
fasboot oem fb_mode_clear
And reboot, it should no longer go to the bootloader unless you are holding VOL DN and the operating system should start normally.
Click to expand...
Click to collapse
You saved my [email protected]#! Thanks.
I'm trying help a friend with her Moto X Style. The buttoms RETURN, HOME and APP is not working. I'm trying upload a ROM, but I got errors everytime and the fastboot was entering every boot.
acejavelin said:
Moto devices have a flashing mode called "fb_mode" that when enabled causes the bootloader to start on each boot, it is used for flashing stock firmware images since in some cases the device needs to reboot after flashing a certain partition or image and it needs a way to return to the fastboot mode. Remember when flashing a stock image you may have entered "fastboot oem fb_mode_set"? If not then a toolkit or other flashing tool may have done it but not cleared it correctly. To clear it manually you need to literally clear it with a fastboot command... With the phone in the bootloader, enter this command from your computer"
fasboot oem fb_mode_clear
And reboot, it should no longer go to the bootloader unless you are holding VOL DN and the operating system should start normally.
Click to expand...
Click to collapse
I did this several times and it set continues it say fasboot reason reboot mode set to fastboot and I tried fastboot oem fb_mode_clear but it just says boot loader slot count not found and etc
Sam to me. Any help?
ninormalen said:
Sam to me. Any help?
Click to expand...
Click to collapse
Yea I do need help, I had flashed a custom rom with twrp recovery on my phone but every time I reboot I either loads into recovery or boot loader if I fb mode clear or not. Even if theirs a system to boot, I have to manually boot into through boot loader and start. If I go to bootloader logs it just says reboot mode set to fastboot.
typo - fastboot, not fasboot
fastboot oem fb_mode_clear
fastboot oem fb_mode_clear
Click to expand...
Click to collapse
When I type this commend, I get the following error:
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
Can someone tell me whats is the problem?
lucas.passos said:
When I type this commend, I get the following error:
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
Can someone tell me whats is the problem?
Click to expand...
Click to collapse
There is no problem... The Moto X does not have A/B software slots, the messages above are merely informational and completely normal.
With mfastboot there is no messages like this. Only "OKAY" one
However it didn't help with my Moto G (falcon).
What helped was checking the kernel. My "smartness" told me to flash Nouagt when I had Pie rom...
Dunken415 said:
Yea I do need help, I had flashed a custom rom with twrp recovery on my phone but every time I reboot I either loads into recovery or boot loader if I fb mode clear or not. Even if theirs a system to boot, I have to manually boot into through boot loader and start. If I go to bootloader logs it just says reboot mode set to fastboot.[/QUOTE
same problem here brother did you find any solution to it?? please help me brother.
Click to expand...
Click to collapse
sagutxo97 said:
SOLVED, the problem was the BP Tools in the fastboot, i had "Fastboot Reason: UTAG "bootmode" configured as fastboot" i changed to "Normal Powerup" and all perfect
Click to expand...
Click to collapse
How'd you do that? i have the same problem how do switch back to normal powerup?
XT-1570 "bootmode-recovery"
Dunken415 said:
I did this several times and it set continues it say fasboot reason reboot mode set to fastboot and I tried fastboot oem fb_mode_clear but it just says boot loader slot count not found and etc
Click to expand...
Click to collapse
I am having the same issue. Would appriciate any help.
E:\fastboot oem fb_mode_clear
...
OKAY [ 0.000s]
finished. total time: 0.016s
PS E:\Backup\Android - XT1570> fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8992-A0.43
(bootloader) product: clark
(bootloader) board: clark
(bootloader) secure: no
(bootloader) hwrev: 0x82A0
(bootloader) radio: 0x3
(bootloader) emmc: 64GB Toshiba REV=07 PRV=00 TYPE=57 PNM=064G38
(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: LX7C2xxxxx
(bootloader) cid: 0xDEAD
(bootloader) channelid: 0xDEAD
(bootloader) uid: EFFA2C001E000000000000000000
(bootloader) unlocked: Not supported
(bootloader) securestate: Engineering
(bootloader) iswarrantyvoid: Not supported
(bootloader) mot_sst: 1
(bootloader) max-download-size: 536870912
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: 35550006xxxxxxx
(bootloader) meid:
(bootloader) date: 04-30-2015
(bootloader) sku: XT1570
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Sat Jul 18 7:57:55 UTC 2020"
(bootloader) ro.build.fingerprint[0]: motorola/clark_retasia_ds/clark_ds
(bootloader) ro.build.fingerprint[1]: :6.0.1/MPHS24.107-58-5/4:user/rele
(bootloader) ro.build.fingerprint[2]: ase-keys
(bootloader) ro.build.version.full[0]: Blur_Version.24.221.5.clark_retas
(bootloader) ro.build.version.full[1]: ia_ds.retasia.en.03
(bootloader) ro.build.version.qcom: <not found>
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 3.10.84-perf-gb67345b (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x-goo
(bootloader) kernel.version[2]: gle 20140827 (prerelease) (GCC) ) #1 SMP
(bootloader) kernel.version[3]: PREEMPT Thu Sep 29 00:24:52 CDT 2016
(bootloader) sbl1.git: git=MBM-NG-VA0.43-0-g8cea836
(bootloader) rpm.git: git=90a41be
(bootloader) tz.git: git=16279de-dirty
(bootloader) hyp.git: git=16279de-dirty
(bootloader) sdi.git: git=52a3f93
(bootloader) pmic.git: git=MBM-NG-VA0.43-0-g8cea836
(bootloader) aboot.git: git=MBM-NG-VA0.43-0-gde54c6f
(bootloader) qe: qe 1/1
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: unknown
all: listed above
finished. total time: 0.172s
C:\fastboot oem fb_mode_clear
...
OKAY [ -0.000s]
finished. total time: -0.000s
Hey there,
To make it short, the phone was rooted, bootloader unlocked, and it was on Resurrection Remix (don't know which one, it was Nougat 7.1.2).
I tried to restore it back to stock, lock the bootloader etc (following this guide : https://forum.xda-developers.com/mo...de-return-to-stock-relock-bootloader-t3489110 which has files for xt1572 too ).
During the process, I got the error that a lot of people get about the Preflash validation error and yet i went through, except that I still locked at the end (I did not notice the Note about it below the command lines, I so regret it).
I also flashed the original Motorola logo (instead of "Bootloader is unlocked"), but I don't think this has anything to do with the fact that it got bricked (I can be wrong though).
Now, I can't access the phone through the cable. adb devices (with killing and restarting server) doesn't detect anything, I'm just stuck on the big Motorola logo splash screen.
Anyone has any idea on any possible way to unbrick it ? (I heard about qualcomm hsusb something but I'm just not sure where it can lead)
Thanks !
@pef6000
Bootloader is locked? What is status code...?
can't you use fastboot (from device turned off hold power + vol down) and flash stock motorola rom?
Hey there, thanks for your answers.
I can't access bootloader nor fastboot. adb doesn't show any device anymore.
I cannot even turn on or off the phone. It just reboots even if I long-press the power button. It just boots back up, and I can only leave it like this until battery is depleted.
Hold power, when screen turn off hold only vol-. It should go to bootloader.
Check and post here BL status. @pef6000
---------- Post added at 11:04 PM ---------- Previous post was at 10:58 PM ----------
Btw, if you will go to bootloader mode(locked) - you can only flash again stock 6.0.1(newest).
Without bootloader and gpt.
Check how many sparsechunks you have in zip file, I think from 0 to 11.
Sorry for being late. I tried that yesterday, but one problem after another, Windows died
I'll pass some time on it whenever I get the computer working.
I tried starting in BL and it worked !
I think the fact that it wasn't working before was due to the phone bootlooping directly on splash screen (maybe, I don't know).
Here, battery was dead since I couldn't turn it off. So I plugged the phone in while keeping vol- pressed, and it booted immediately in.
Couldn't get a hold of the status code though, the computer rebooted and crashed, so I had something else in mind, sorry :/
Anyway, I'll do that whenever I can, thanks for your help !
Here again. I accessed bootloader and I get :
AP Fastboot Flash Mode (Secure)
[…]
Console [NULL]: null
Battery OK (charging)
Device is UNLOCKED. Status Code: 3
Software status: Modified
Before this problem, when I tried to flash everything, I have parsechunks from 0 to 8, not 11.
Now, I don't really know what to do. Should I do everything back again with a 6.0.1 zip ?
pef6000 said:
Should I do everything back again with a 6.0.1 zip ?
Click to expand...
Click to collapse
Yes.
Without bootloader, gpt and Don't lock BootLoader.
Hey.
I did it, didn't lock bootloader, didn't flash bootloader.img nor gpt.bin, but it still freezes on the splash screen logo. I suppose it woudn't take as much as 15 to 30 minutes to switch from that splash screen to any other screen.
The bootloader is still accessible, and I still have the same things (unlocked, status 3, etc).
Am I doing something wrong ? :/
What is your model and what rom are you flashing?
What do you have on pc after: "fastboot getvar all"? @pef6000
It's a XT1572, European (got it in France).
I'm trying to flash the one for XT1572 in the link with the instructions : https://dl.prazaar.de/?dir=Android/XT1572/Factory/6.0.1/MPHS24.107-58-5_September_2016
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8992-A0.4C
(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 Samsung S8 SDRAM DIE=6Gb M5=x1 M6=x5 M7=x0 M
(bootloader) ram[1]: 8=x3B
(bootloader) cpu: MSM8992
(bootloader) serialno: TA3910197I
(bootloader) cid: 0x0007
(bootloader) channelid: 0x42
(bootloader) uid: 42C5D7001E000000000000000000
(bootloader) unlocked: yes
(bootloader) securestate: unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) mot_sst: 3
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: [...]
(bootloader) meid:
(bootloader) date: 11-12-2015
(bootloader) sku: XT1572
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Wed Jul 6 10:58:55 UTC 2016"
(bootloader) ro.build.fingerprint[0]: motorola/clark_reteu/clark:6.0/MPH
(bootloader) ro.build.fingerprint[1]: S24.49-18-4/3:user/release-keys
(bootloader) ro.build.version.full[0]: Blur_Version.24.221.4.clark_reteu
(bootloader) ro.build.version.full[1]: .reteu.en.EU
(bootloader) ro.build.version.qcom: <not found>
(bootloader) version-baseband[0]: M8992_1255331.29.01.88.02R CLARK_EMEA_
(bootloader) version-baseband[1]: CUST
(bootloader) kernel.version[0]: Linux version 3.10.84-perf-g0ec7138 (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 Tue Nov 3 05:05:40 CST 2015
(bootloader) sbl1.git: git=MBM-NG-VA0.4C-0-g07bb07e
(bootloader) rpm.git: git=90a41be
(bootloader) tz.git: git=7ea7c4c-dirty
(bootloader) hyp.git: git=7ea7c4c-dirty
(bootloader) sdi.git: git=52a3f93
(bootloader) pmic.git: git=MBM-NG-VA0.4C-0-g07bb07e
(bootloader) aboot.git: git=MBM-NG-VA0.4C-0-g1fa1c30
(bootloader) qe: qe 2/1
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: retfr
all: listed above
finished. total time: 0.242s
Did you flash: boot, recovery, all sparsechunks(0-11), modem, all erases? Each command ended with OK? @pef6000
Yes, I did all of this, everything turns out ok except one error (the Preflash Validation).
Now that I read it again, the post says it happens on gpt.bin, except I didn't flash it as you said.
I just did it again and I get it again at this step :
> fastboot flash modem NON-HLOS.bin
target reported max download size of 536870912 bytes
sending 'modem' (41699 KB)...
OKAY [ 0.923s]
writing 'modem'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.981s
Do I also not flash the modem ? :/
EDIT :
Btw, the bootloader log on the phone says "Image is too large" after the "cmd: flash:modem" line.
pef6000 said:
It's a XT1572, European (got it in France).
Click to expand...
Click to collapse
You should edit your post and remove the IMEI number...
Is it possible your last stock system was 6.0?
Download and try to flash reteu 24.49-18-4, still without BL, gpt, oem.
(I don't know how many sparsechunks there is, check it).
https://mirrors.lolinet.com/firmware/moto/clark/official/RETEU/ @pef6000
dzidexx said:
Is it possible your last stock system was 6.0?
Download and try to flash reteu 24.49-18-4, still without BL, gpt, oem.
(I don't know how many sparsechunks there is, check it).
https://mirrors.lolinet.com/firmware/moto/clark/official/RETEU/ @pef6000
Click to expand...
Click to collapse
From the getvar output, the bootloader is on 6.0
(bootloader) ro.build.fingerprint[0]: motorola/clark_reteu/clark:6.0/MPH
(bootloader) ro.build.fingerprint[1]: S24.49-18-4/3:user/release-keys
(bootloader) ro.build.version.full[0]: Blur_Version.24.221.4.clark_reteu
(bootloader) ro.build.version.full[1]: .reteu.en.EU
Click to expand...
Click to collapse
on MPHS24.49-18-4... I would suggest using the same version or XT1572_CLARK_RETEU_6.0_MPHS24.49-18-8_cid7_subsidy-DEFAULT_CFC.xml.zip and NOT 6.0.1. The 6.0.1 versions were only for certain variants, and I do not know if the RETFR ones had that.
And don't skip the bootloader or gpt UNLESS they actually fail... It is best to do it like this:
Also, if possible boot into the factory recovery and perform a full factory reset before beginning.
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
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 [Verify number of sparse chunks and make sure you are doing the correct #]
fastboot flash modem NON-HLOS.bin [May need to be done more 2 or 3 times to "take", make sure it returns an "OKAY"]
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
My 2 cents worth... hope it helps.
@acejavelin Oh damn, thank you. I thought I checked correctly but I didn't notice the IMEI in there.
Thank you both for your help. Phone booted up on original rom, I'm happy
I'll mark this post as Solved, but I have a quick question : Can I use the XT1575 logo.bin found here :https://forum.xda-developers.com/mo...o-remove-unlocked-bootloader-warning-t3201141
Or is it better not to do so ?
Yes you can.
Or any from here:
https://forum.xda-developers.com/moto-x-style/themes-apps/boot-animation-logo-bin-t3558942 @pef6000
Btw.
You flashed ...18-8 or 18-4? Maybe someone will need it in future.
dzidexx said:
Yes you can.
Or any from here:
https://forum.xda-developers.com/moto-x-style/themes-apps/[email protected]
Btw.
You flashed ...18-8 or 18-4? Maybe someone will need it in future.
Click to expand...
Click to collapse
@pef6000 Any of these or the one you mentioned is fine.
Sorry for the late answer, I flashed the 18-8 in the end.
Thanks again, I'll mark this as solved !
Hii there I'm a moto g4 plus(XT1643) user......... tomorrow I was updating my device from marshmallow to nougat from the OTA update but after updating the device did not boot up.......and also I was not able to boot into bootloader mode so that I can flash nougat stock firmware........then I searched on Xda and get "BLACK FLASH" method but after running 'blankflash.bat' the device booted into the bootloader mode. the bootloader is like a dummy bootloader but I'm not able to flash stock rom by this!!!! And also I had posted a screenshot of bootloader!!!!!
please help me to get out of this problem.....I'm a noob so please help me!!!!!!!!
thanks in advance
yshiv666 said:
Hii there I'm a moto g4 plus(XT1643) user......... tomorrow I was updating my device from marshmallow to nougat from the OTA update but after updating the device did not boot up.......and also I was not able to boot into bootloader mode so that I can flash nougat stock firmware........then I searched on Xda and get "BLACK FLASH" method but after running 'blankflash.bat' the device booted into the bootloader mode. the bootloader is like a dummy bootloader but I'm not able to flash stock rom by this!!!! And also I had posted a screenshot of bootloader!!!!!
please help me to get out of this problem.....I'm a noob so please help me!!!!!!!!
thanks in advance
Click to expand...
Click to collapse
Which ROM version you are trying ?
Try with latest September's patch one available here: https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
____Mdd said:
Which ROM version you are trying ?
Try with latest September's patch one available here: https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
Click to expand...
Click to collapse
yes I had tried it but it is not working
yshiv666 said:
yes I had tried it but it is not working
Click to expand...
Click to collapse
Was your bootloader unlocked ?
In bootloader loader screen it shows locked now, and system modified !
Baseband is unknown in bootloader screen, so i can say modem is not getting installed, (plus there may be other things too which are not getting installed)
Noe, do it, Flash ROM again,
But with entering one command at time,
After flashing/ending of one command, check that you are getting "OKAY"..
Let us know if there is any error or "FAILED" at command end.
____Mdd said:
Was your bootloader unlocked ?
In bootloader loader screen it shows locked now, and system modified !
Baseband is unknown in bootloader screen, so i can say modem is not getting installed, (plus there may be other things too which are not getting installed)
Noe, do it, Flash ROM again,
But with entering one command at time,
After flashing/ending of one command, check that you are getting "OKAY"..
Let us know if there is any error or "FAILED" at command end.
Click to expand...
Click to collapse
yes!!!! it says "FAILED" at the end.... see the screenshot of CMD
yshiv666 said:
yes!!!! it says "FAILED" at the end.... see the screenshot of CMD
Click to expand...
Click to collapse
That screenshot is of system,
What about bootloader and gpt ?
Again, tell me which version of ROM you are trying ?
____Mdd said:
That screenshot is of system,
What about bootloader and gpt ?
Again, tell me which version of ROM you are trying?
Click to expand...
Click to collapse
here is the screenshot for gpt.bin and bootloader.img!!!!!
and I'm flashing Sept 01 Security Patch which you have mentioned above.........
yshiv666 said:
here is the screenshot for gpt.bin and bootloader.img!!!!!
and I'm flashing Sept 01 Security Patch which you have mentioned above.........
Click to expand...
Click to collapse
I have never faced or seen anyone with this like issue,
Wait a while, @echo92 has better experience with this like stuff, he will guide you better than me.
Till than you can try blank flash again, with replacing gpt and bootloader from ROM's zip.
____Mdd said:
I have never faced or seen anyone with this like issue,
Wait a while, @echo92 has better experience with this like stuff, he will guide you better than me.
Till then you can try blank flash again, with replacing gpt and bootloader from ROM's zip.
Click to expand...
Click to collapse
thanks, bro!!!!!! I copied the gpt.bin file from latest December security patch and the flashed the rom and it works
thanks a lot, bro.......:good::good::good:
yshiv666 said:
thanks, bro!!!!!! I copied the gpt.bin file from latest December security patch and the flashed the rom and it works
thanks a lot, bro.......:good::good::good:
Click to expand...
Click to collapse
Wait, December's !
You got your device back is good thing, but remain stuff will be of September's patch..
Now if you get update notification for December's patch dont take it... It will brick your device again.
You will have to wait for fastboot ROM of December's patch..
Till then, keep your phone on September...
Don't take OTA...
When December's patch build is available flash it with fastboot...
yshiv666 said:
thanks, bro!!!!!! I copied the gpt.bin file from latest December security patch and the flashed the rom and it works
thanks a lot, bro.......:good::good::good:
Click to expand...
Click to collapse
Good to hear you got your device working. As ____Mdd has mentioned, I would strongly recommend you wait for the Dec 2017 stock ROM to flash. Looking at your bootloader details, since you've got a Dec 2017 GPT, a June/September 2017 bootloader and a marshmallow baseband, you likely cannot safely take OTA updates.
Because you've downgraded from Nougat to marshmallow, taking OTA updates runs a high risk of hard bricking again and our current blank flash may not work on your device now you've flashed the Dec 2017 GPT. Thus, do not take OTA updates until you flash the Dec 2017 Nougat stock ROM (which isn't available yet), and if you later downgrade again, do not accept OTA updates. Else the OTA updates may corrupt your newer bootloader again (bootloaders do not downgrade) with no recourse except to wait for a newer blankflash or a 8000+ rupees repair.
I have the same case and it sends me an error in the boot.
Can somebody help me
Turning OEM on without phone turning on
al3al3al3jandr0 said:
I have the same case and it sends me an error in the boot.
Can somebody help me
Click to expand...
Click to collapse
I am trying to flash my ROM as the phone is not turning on in any method be it normal of recovery mode or factory mode. My phone MOTO G4 Plus is unable to flash the ROM as it is OEM_LOCKED and None of the options from the bootloader menu works. On selecting any of the options from the power button nothing happens except for the barcodes which show the barcode and RESTART BOOTLOADER restarts the bootloader.
Please help someone.
Is there a way to unlock OEM without turning the phone on as I can't turn it on.
qjzxvkw said:
I am trying to flash my ROM as the phone is not turning on in any method be it normal of recovery mode or factory mode. My phone MOTO G4 Plus is unable to flash the ROM as it is OEM_LOCKED and None of the options from the bootloader menu works. On selecting any of the options from the power button nothing happens except for the barcodes which show the barcode and RESTART BOOTLOADER restarts the bootloader.
Please help someone.
Is there a way to unlock OEM without turning the phone on as I can't turn it on.
Click to expand...
Click to collapse
why doesn't it boot??? What were you doing before this happened. Please give the details
Heeth21 said:
why doesn't it boot??? What were you doing before this happened? Please give the details
Click to expand...
Click to collapse
Nothing I just kept it for charging overnight. And it doesn't power on in the morning. I plugged it while it was on though.
Someone suggested it has damaged its motherboard.
qjzxvkw said:
Nothing I just kept it for charging overnight. And it doesn't power on in the morning. I plugged it while it was on though.
Someone suggested it has damaged its motherboard.
Click to expand...
Click to collapse
Hmm, do you recall if there was an update notification at all before you put your device on charge?
Without getting your device to boot, there's no way to toggle the OEM_unlocking function unfortunately.
If you can, when you've plugged your device to your computer and booted to the bootloader:
1)Open a minimal ADB command window on Windows (download/install minimal ADB from here: https://forum.xda-developers.com/showthread.php?t=2317790 other fastboot/adb tools should work too)
2)Type 'fastboot devices' without quotes into the window. Press Enter - your device should respond with its serial number.
3)If you get that response, type 'fastboot getvar all' without quotes. Press Enter.
4)Please paste the output here or upload it as a text file (or paste it into a site like pastebin and put the link here). You may wish to omit the IMEI.
We could try to re-flash the stock firmware that you had, but if that doesn't solve things it may start to look like a hardware failure.
yshiv666 said:
Hii there I'm a moto g4 plus(XT1643) user......... tomorrow I was updating my device from marshmallow to nougat from the OTA update but after updating the device did not boot up.......and also I was not able to boot into bootloader mode so that I can flash nougat stock firmware........then I searched on Xda and get "BLACK FLASH" method but after running 'blankflash.bat' the device booted into the bootloader mode. the bootloader is like a dummy bootloader but I'm not able to flash stock rom by this!!!! And also I had posted a screenshot of bootloader!!!!!
please help me to get out of this problem.....I'm a noob so please help me!!!!!!!!
thanks in advance
Click to expand...
Click to collapse
make sure your bootloader is unlocked. and let me know.
echo92 said:
Hmm, do you recall if there was an update notification at all before you put your device on charge?
Without getting your device to boot, there's no way to toggle the OEM_unlocking function unfortunately.
If you can, when you've plugged your device to your computer and booted to the bootloader:
1)Open a minimal ADB command window on Windows (download/install minimal ADB from here: https://forum.xda-developers.com/showthread.php?t=2317790 other fastboot/adb tools should work too)
2)Type 'fastboot devices' without quotes into the window. Press Enter - your device should respond with its serial number.
3)If you get that response, type 'fastboot getvar all' without quotes. Press Enter.
4)Please paste the output here or upload it as a text file (or paste it into a site like pastebin and put the link here). You may wish to omit the IMEI.
We could try to re-flash the stock firmware that you had, but if that doesn't solve things it may start to look like a hardware failure.
Click to expand...
Click to collapse
Thanks for the response: Here is everything you asked:
I am sure there was no update notification as I always download any update that is released as soon as I see it. So I might have updated already.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
ZY223BGGD2 fastboot
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-B0.0E(*)
(bootloader) product: athene_16mp
(bootloader) board: athene_16mp
(bootloader) secure: yes
(bootloader) hwrev: P2A
(bootloader) radio: 4
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG RX1BMB RV=08 PV=07 FV=0000000000000007
(bootloader) ram: 3GB SAMSUNG LP3 DIE=6Gb M5=01 M6=05 M7=00 M8=7B
(bootloader) cpu: MSM8952
(bootloader) serialno: ZY223BGGD2
(bootloader) cid: 0x0032
(bootloader) channelid: 0xc0
(bootloader) uid: 6E23DD0000000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: *************
(bootloader) meid:
(bootloader) date: 06-06-2016
(bootloader) sku: XT1643
(bootloader) battid: SNN5966A
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Wed Apr 20 23:52: 3 UTC 2016"
(bootloader) ro.build.fingerprint[0]: motorola/athene_f/athene_f:7.0/NPJ
(bootloader) ro.build.fingerprint[1]: S25.93-14-4/4:user/release-keys
(bootloader) ro.build.version.full[0]: Blur_Version.25.201.4.athene.reta
(bootloader) ro.build.version.full[1]: il.en.US
(bootloader) ro.build.version.qcom: LA.BR.1.3.6-01710-8976.0
(bootloader) version-baseband[0]: M8952_70030.25.03.62R ATHENE_INDIA_DSD
(bootloader) version-baseband[1]: S_CUST
(bootloader) kernel.version[0]: Linux version 3.10.84-gb9596e1 (hudsoncm
(bootloader) kernel.version[1]: @ilclbld31) (gcc version 4.8 (GCC) ) #1
(bootloader) kernel.version[2]: SMP PREEMPT Fri Mar 3 02:04:02 CST 2017
(bootloader) sbl1.git: git=MBM-NG-VB0.0E-0-g83950b7
(bootloader) rpm.git: git=1dc910e
(bootloader) tz.git: git=9fa1804
(bootloader) hyp.git: git=9fa1804
(bootloader) keymaster.git: git=9fa1804
(bootloader) cmnlib.git: git=9fa1804
(bootloader) aboot.git: git=MBM-NG-VB0.0E-0-g4986429
(bootloader) qe: qe 0/0
(bootloader) frp-state: protected (208)
(bootloader) ro.carrier: retin
all: listed above
finished. total time: 0.244s
C:\Program Files (x86)\Minimal ADB and Fastboot>
Thanks. It was indeed a hardware problem. Motherboard was broken in two pieces just below camera position.
Hi guys, I'm new here and I just wanted to know if someone else have had this issue too and knew how to solve it.
Yesterday I was playing pool on my phone when suddenly it turned off. I though the battery was very low but I had barely charged it. When I was trying to turn it on it didn't respond, I connected the charger and noticed that the only thing that was working was the LED and the screen never turned on again, I realized that it was a hardbrick.
I guess the cause was that a few days ago I changed the kernel, I installed Elemental X kernel, but I didn't like how it was working on my device so I restored the backup with the RR ROM I always use and everything was normal until yesterday.
I've been all the last day trying to fix it and I just have got blankflashed. Then I've tried to flash around 6 firmwares from 4 different sites and they all fail throwing me a "FAILED (remote failure)".
I use a zip file as help through adb commands on my laptop and the Fastboot Flash Mode (Secure) on my device.
I don't know what else to do and the problem is unknown for now.
Would it be the bootloader?
Is there a problem if the OEM is locked?
Is the non-existent IMEI interfering?
Am I doing things right?
What else should I do?
PS: It's obvious that I'm desperate and I know that is possible to save it.
Thanks for reading I hope someone answer.
Caney said:
I've been all the last day trying to fix it and I just have got blankflashed. Then I've tried to flash around 6 firmwares from 4 different sites and they all fail throwing me a "FAILED (remote failure)".
Click to expand...
Click to collapse
That's not good, flashing wrong firmware can be dangerous to losing fingerprint and losing IMEI.
Get latest December's patch ROM from link thred and try to flash it. : https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
@Caney Have you tried pressing power button and volume down button for approx 10 mins.. this should force reset back into bootloader and go from there. Just make sure they is some charge in the battery but when pressing buttons make sure it's NOT connected to anything else it wont work
The device is in Fastboot Flash Mode (Secure), is it necessary to do that?
Caney said:
The device is in Fastboot Flash Mode (Secure), is it necessary to do that?
Click to expand...
Click to collapse
I'm not too sure what fastboot flash mode (secure) is tbh... Does the led just flash when you try to turn it on? And if you connect to pc it detects it something odd like qloader (I forget the exact name) if so yes. Try it
stehaworth said:
@Caney Have you tried pressing power button and volume down button for approx 10 mins.. this should force reset back into bootloader and go from there. Just make sure they is some charge in the battery but when pressing buttons make sure it's NOT connected to anything else it wont work
Click to expand...
Click to collapse
stehaworth said:
I'm not too sure what fastboot flash mode (secure) is tbh... Does the led just flash when you try to turn it on? And if you connect to pc it detects it something odd like qloader (I forget the exact name) if so yes. Try it
Click to expand...
Click to collapse
Yes, it was like that until I used blankflash and entered to Fastboot Flash Mode (Secure); It's like bootloader menu but instead of an android image you have a green "Start" text.
Caney said:
Yes, it was like that until I used blankflash and entered to Fastboot Flash Mode (Secure); It's like bootloader menu but instead of an android image you have a green "Start" text.
Click to expand...
Click to collapse
Tbh.... I'm not too sure... But I would start at looking into flashing full Moto stock image via fastboot (see other thread for details)
Hey, I think I have lock my bootloader accidentally :'c When I try to put the commands to flash firmware it throws me this:
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slotartition: not found
error: cannot load 'gpt.bin'
How do I unlock it?
You tried blank-flash too!! That's not good if you try with December's patch.
First, it will make confusion to discuss same thing on different threads, (reported other one)
Now discuss here,
when that green start is shown, type following commands.
To check if your device is connected,
- fastboot devices
To see your phone's information, post result of it.
- fastboot getvar all
C:\Users\hp>fastboot getvar all
(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: 5
(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: b61bc8aa
(bootloader) cid: 0x0032
(bootloader) channelid: 0x23
(bootloader) uid: 57A9A70100000000000000000000
(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.291s
@Caney from this data, i can see bootloader version is old, so you can try blank-flash with September's gpt and bootloader.
Follow (link below) thread for it, and where it says about download gpt and Bootloader files, go for September's one (2nd link there)...
https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761
When you get bootloader (after blank-flash), flash December's update.
____Mdd said:
You tried blank-flash too!! That's not good if you try with December's patch.
First, it will make confusion to discuss same thing on different threads, (reported other one)
Now discuss here,
when that green start is shown, type following commands.
To check if your device is connected,
- fastboot devices
To see your phone's information, post result of it.
- fastboot getvar all
Click to expand...
Click to collapse
Why isn't that good?
Caney said:
Why isn't that good?
Click to expand...
Click to collapse
In December's patch, there is update for bootloader, so when bootloader is updated, we need new blank-flash files for new bootloader, so we currently don't have blank-flash files for December's update...
But yours is B1.03 (in getvar info), which is old, so no need to worry about it. Just do as above i said, try blank-flash with September's gpt and bootloader...
____Mdd said:
In December's patch, there is update for bootloader, so when bootloader is updated, we need new blank-flash files for new bootloader, so we currently don't have blank-flash files for December's update...
But yours is B1.03 (in getvar info), which is old, so no need to worry about it. Just do as above i said, try blank-flash with September's gpt and bootloader...
Click to expand...
Click to collapse
Oooh man, can you please attach the link of that gpt here? I don't find it.
Caney said:
Oooh man, can you please attach the link of that gpt here? I don't find it.
Click to expand...
Click to collapse
GPT and bootloader of the September 2017 stock ROM update (NPJS25.93-14-10) - bootloader version B1:06. https://drive.google.com/open?id=0B-GUyOfb8Ogzc25FdW1WUDBMS1U
GPT and bootloader of the December 2017 stock ROM update (NPJS25.93-14-13) - bootloader version B1:07.
https://drive.google.com/open?id=1IfAX7v94ooB5wS7KTJGNYfQ2kXkHxP80
However, I would caution against just using these files, and suggest that you update fully by flashing the entire stock September or December 2017 ROM. Your bootloader is from the November/December 2016 firmware (B1:03) so just updating your bootloader isn't a good idea, especially when it comes to OTA updates.
Alternatively, if you want to reflash the stock ROM that has the same bootloader version as your reported bootloader, have a look at this thread: https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369
I decided to download the file from the third link provided. But I don't know if I'm flashing correctly, how do I do it?
Caney said:
I decided to download the file from the third link provided. But I don't know if I'm flashing correctly, how do I do it?
Click to expand...
Click to collapse
Are you following a guide to help you flash?
Generally for any flashing via fastboot (e.g. for stock ROMs or for TWRP)
1)Install the ADB and Motorola drivers as directed by the guide.
1a)Extract the stock ROM zip file (should be about 2 GB in size extracted), copy all the files to your ADB folder (so they're on the same level as your adb.exe and fastboot.exe).
2)Reboot your device to the bootloader (fastboot mode) and connect to your computer via USB. Preferably this should be the same cable as came with your device or another high quality data + power USB cable.
3)Open the ADB terminal on your computer and verify that your device is communicating by typing 'fastboot devices' in the ADB terminal, without quotes. This should return your device's serial number.
4)If so, then proceed with flashing as per the guide's fastboot commands. They are the same as the stock ROMs for Moto G4/Plus devices have followed the same layout (7 sparsechunks for system, for example). If you do not wish to re-lock your bootloader, then do not use the two OEM lock begin or the OEM lock commands. If you wish to try to keep your data, then you can omit fastboot erase userdata. However, with your device in the state it is, it may be worth thinking about a fresh start and erasing your userdata.
For omitting bootloader re-locking and trying to preserve your data (though be aware you may have to wipe anyway, the following fastboot commands should suffice.
Code:
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 reboot
You can either edit a flashing script to mirror these commands and use the script or enter the commands, individually and in order, by copypasting each line into the ADB terminal, then executing. Ideally, you want to see [OKAY] before you proceed. You may see errors about 'Image signed with bad key' if you're actually still unlocked, that's normal.
However, if you see any other errors, such as pre-flash validation or security downgrade, then you will need to use a newer stock ROM. Depending on which blankflash you used, the September 2017 or December 2017 stock ROMs would be suitable candidates.
This is what I was doing but with flash script. If I'm going to flash one of those Dec o Sep, will be necessary to update my bootloader from B1.03 to B1.07 or B1.06?
And another problem, when I open a command window in the fastboot files Windows opens Windows PowerShell instead of adb.
Caney said:
This is what I was doing but with flash script. If I'm going to flash one of those Dec o Sep, will be necessary to update my bootloader from B1.03 to B1.07 or B1.06?
Click to expand...
Click to collapse
After flashing bootloader file from September ROM, your bootloader will be automatiically updated to B1.06 and same apply for December ROM.
But you have used the blank flash file so it is recommended to downloading the June 2017 fastboot ROM and flashing that in fastboot.
Caney said:
And another problem, when I open a command window in the fastboot files Windows opens Windows PowerShell instead of adb.
Click to expand...
Click to collapse
As of Windows PowerShell of WIndows 10 still it doesn't fully supported for all Commands and Features so Its better to use CMD or ADB.
Caney said:
This is what I was doing but with flash script. If I'm going to flash one of those Dec o Sep, will be necessary to update my bootloader from B1.03 to B1.07 or B1.06?
And another problem, when I open a command window in the fastboot files Windows opens Windows PowerShell instead of adb.
Click to expand...
Click to collapse
Then you may wish to try manually flashing each command individually, and in order, ensuring you see [OKAY] before continuing. The script may proceed too quickly to see if it's all worked, so manually flashing is another option. You could always add 'pause' before 'reboot' in the script (without quotes) to let you review the flash before rebooting.
As for Powershell instead of cmd, have a look at this thread: https://forum.xda-developers.com/moto-g4-plus/help/installing-twrp-using-powershell-t3727761/
As for updating bootloaders, I would recommend it - your bootloader is a crucially important piece of firmware and should stay at the same patch level as your system/device firmware. This should reduce the number of complications you may face and also ensure that OTA updates go more smoothly.
Be aware that the B1:06 bootloader in the June 2017 and September 2017 security patches (NPJS25.93-14-8 and NPJS25.93-14-10) close a bootloader vulnerability, which makes downgrading to an older stock ROM even more risky as it appears Motorola does not like you downgrading. Strictly speaking, it's not the act of downgrading, but the act of taking an OTA update whilst downgraded - the mismatch between your newer bootloader patch level and the older stock ROM can hard brick your device should you attempt to install an OTA update.
Furthermore, with the December 2017 stock ROM patch, bootloaders are updated to B1:07, meaning our current latest blankflash is not likely to work (blankflashes older than your current bootloader, corrupted or not, do not appear to be permitted to flash to your bootloader). So be careful when updating and flashing anything to your device if you choose to update to the December 2017 patch.