Hey. my phone was bootlooped and i recover to stock rom marshmallow 6.0. then came update 6.0.1 it was ok i installed it. after that came Nougat 7.1 update and in installation time phone won't boot. bootloader was unlocked. computer can not see phone, it says usb device not recognized. phone is moto g4 xt1622 dual sim
is there any way to survive? motherboard is dead? thanks. i can not know what to do i am so sorry i feel so bad
just there is white light phone is charging, but no switch on and no bootloader menu. nothing happens
gioyocho said:
Hey. my phone was bootlooped and i recover to stock rom marshmallow 6.0. then came update 6.0.1 it was ok i installed it. after that came Nougat 7.1 update and in installation time phone won't boot. bootloader was unlocked. computer can not see phone, it says usb device not recognized. phone is moto g4 xt1622 dual sim
is there any way to survive? motherboard is dead? thanks. i can not know what to do i am so sorry i feel so bad
just there is white light phone is charging, but no switch on and no bootloader menu. nothing happens
Click to expand...
Click to collapse
Looks like you downgraded your bootloader and then take ota = hardbrick. Have you tried that guide and read the discussion of others? https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761
strongst said:
Looks like you downgraded your bootloader and then take ota = hardbrick. Have you tried that guide and read the discussion of others? https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761
Click to expand...
Click to collapse
Thanks for reply! i used your link for stock rom marshmallow. but now computer can not see phone, it says not recognized. i can not get access to fastboot menu. i am going to take it to programmer, but i have no hope. so sad
gioyocho said:
Thanks for reply! i used your link for stock rom marshmallow. but now computer can not see phone, it says not recognized. i can not get access to fastboot menu. i am going to take it to programmer, but i have no hope. so sad
Click to expand...
Click to collapse
What do you see in Device Manager when your device is connected, do you see Qualcomm HS-USB 9008 or similar listed? Do you have the Motorola drivers installed on your computer, and, if you have Windows 8.1 or 10, do you have driver signature enforcement disabled? https://www.howtogeek.com/167723/ho...8.1-so-that-you-can-install-unsigned-drivers/
I'm confused that you used the link provided by strongst to flash a MM firmware though, from what I recall reading of your post it sounded like you soft bricked but somehow managed to flash a MM firmware. However, as strongst pointed out, if you'd downgraded your device when you flashed MM, taking the OTA update would have corrupted your bootloader, leaving you with the hard brick and no fastboot mode.
EDIT - looking through your previous posts, it looked like you had formally updated to stock Nougat, then downgraded to the stock MM firmware (but still had a Nougat bootloader - you cannot generally downgrade bootloaders), then using an old Nougat OTA corrupted your bootloader. Ouch... What firmware did you download?
I'd try to install the Motorola drivers to your computer https://support.motorola.com/us/en/drivers , disable driver signature enforcement if you can and then try the blankflash from that guide. If the blankflash can communicate with your device, then it may be able to flash a basic bootloader and give you fastboot. Ensure you use your original Motorola cable or a good quality USB data cable and that the physical connection to your device is good.
I am also faced same issue ,even Motorola service centre guys won't helped me. But I did it with patience ,I sure your problem will be with Qualcomm usb driver ,so install it correctly .
echo92 said:
What do you see in Device Manager when your device is connected, do you see Qualcomm HS-USB 9008 or similar listed? Do you have the Motorola drivers installed on your computer, and, if you have Windows 8.1 or 10, do you have driver signature enforcement disabled? https://www.howtogeek.com/167723/ho...8.1-so-that-you-can-install-unsigned-drivers/
I'm confused that you used the link provided by strongst to flash a MM firmware though, from what I recall reading of your post it sounded like you soft bricked but somehow managed to flash a MM firmware. However, as strongst pointed out, if you'd downgraded your device when you flashed MM, taking the OTA update would have corrupted your bootloader, leaving you with the hard brick and no fastboot mode.
EDIT - looking through your previous posts, it looked like you had formally updated to stock Nougat, then downgraded to the stock MM firmware (but still had a Nougat bootloader - you cannot generally downgrade bootloaders), then using an old Nougat OTA corrupted your bootloader. Ouch... What firmware did you download?
I'd try to install the Motorola drivers to your computer https://support.motorola.com/us/en/drivers , disable driver signature enforcement if you can and then try the blankflash from that guide. If the blankflash can communicate with your device, then it may be able to flash a basic bootloader and give you fastboot. Ensure you use your original Motorola cable or a good quality USB data cable and that the physical connection to your device is good.
Click to expand...
Click to collapse
Thanks for reply!
i had installed many drivers. even qualcomm and motorola, but situation is such. see file attachment. looks like my phone is in coma. i have windows 10. i will say long story short
1. i had android 8.1.0 RR, it was heating and i changed to RR 7.1.2. it worked good
2. it was also heating and i decides to change kernel and phone stop on RR logo, it was rounding but phone won't working. i had no backup or rom files
3. then i installed stock rom 6.0 marshmallow from fastboot with cmd, i downloded it from motorola's official site. i had 6.0 and bootloader unlocked. than came 6.0.1 ota and i updated it was ok. than came also ota update Nougat and installation process phone won't boot
echo92 said:
What do you see in Device Manager when your device is connected, do you see Qualcomm HS-USB 9008 or similar listed? Do you have the Motorola drivers installed on your computer, and, if you have Windows 8.1 or 10, do you have driver signature enforcement disabled? https://www.howtogeek.com/167723/ho...8.1-so-that-you-can-install-unsigned-drivers/
I'm confused that you used the link provided by strongst to flash a MM firmware though, from what I recall reading of your post it sounded like you soft bricked but somehow managed to flash a MM firmware. However, as strongst pointed out, if you'd downgraded your device when you flashed MM, taking the OTA update would have corrupted your bootloader, leaving you with the hard brick and no fastboot mode.
EDIT - looking through your previous posts, it looked like you had formally updated to stock Nougat, then downgraded to the stock MM firmware (but still had a Nougat bootloader - you cannot generally downgrade bootloaders), then using an old Nougat OTA corrupted your bootloader. Ouch... What firmware did you download?
I'd try to install the Motorola drivers to your computer https://support.motorola.com/us/en/drivers , disable driver signature enforcement if you can and then try the blankflash from that guide. If the blankflash can communicate with your device, then it may be able to flash a basic bootloader and give you fastboot. Ensure you use your original Motorola cable or a good quality USB data cable and that the physical connection to your device is good.
Click to expand...
Click to collapse
now i changed something, disabled test mode windows and it says some qualcomm device in device manager port. what i can do now?
Omg people i survived it again. you make me day i am so happy. just there is december security patch 2016 but i feel so great. the problem was next: when i installed many drivers and applications, windows came to test mode (it was written right and down side of screen), then i go to youtube and did everything exactly run as administrator and run words, then i restarted computer and it saw my qualcomm driver 9008 or something, i used blankfish file for install bootloader and downloaded 7.0 rom for 1 april security patches. i swear that never root, or set twrp, or unlock bootloader, because it is so risky. Thanks everyone so much. admin you can close the topic
i must say something too. i do know reason why my phone was bricked, maybe main reason is that when i first time survived phone and installed stock 6.0 firmware, then i try to re-lock bootloader, and after 6.0 to 7.0 install i got bricked. i say this because now when i installed bootloader, there is written oem_locked it means bootloader locked. looks like first time i locked bootloader, but screen was and is same (when i start up phone it says bootloader unlocked won't trust wait 5 seconds). so big thanks you guys
gioyocho said:
i must say something too. i do know reason why my phone was bricked, maybe main reason is that when i first time survived phone and installed stock 6.0 firmware, then i try to re-lock bootloader, and after 6.0 to 7.0 install i got bricked. i say this because now when i installed bootloader, there is written oem_locked it means bootloader locked. looks like first time i locked bootloader, but screen was and is same (when i start up phone it says bootloader unlocked won't trust wait 5 seconds). so big thanks you guys
Click to expand...
Click to collapse
Hmm, if you previously had stock Nougat on your device, you wouldn't have been able to lock your bootloader with the marshmallow firmware ( you need the stock firmware as new or newer than your Nougat bootloader).
Regardless, it's good that you got your device working again, just as a reminder, please if you do decide to flash old stock firmware, do not use old OTA updates, they are not safe to use on downgraded devices. We're lucky to have this blankflash leaked to us. If you flash old stock firmware, only use newer stock firmware to update.
echo92 said:
Hmm, if you previously had stock Nougat on your device, you wouldn't have been able to lock your bootloader with the marshmallow firmware ( you need the stock firmware as new or newer than your Nougat bootloader).
Regardless, it's good that you got your device working again, just as a reminder, please if you do decide to flash old stock firmware, do not use old OTA updates, they are not safe to use on downgraded devices. We're lucky to have this blankflash leaked to us. If you flash old stock firmware, only use newer stock firmware to update.
Click to expand...
Click to collapse
yes i do not know. it is strange situation. example now i had 2016 december security patch. came again ota update 1 april 2018 security patch and while installing finished again boot dead. and i survive again with newest rom. when i survive first time i just downloaded older bootloder file which was in the topic and that's why there was 2016 security patch. after download lastest rom with security patch and with new bootloader, and replace with new bootloader. now there is 1 april 2018 security patch
i guess ota updates is not safe
gioyocho said:
yes i do not know. it is strange situation. example now i had 2016 december security patch. came again ota update 1 april 2018 security patch and while installing finished again boot dead. and i survive again with newest rom. when i survive first time i just downloaded older bootloder file which was in the topic and that's why there was 2016 security patch. after download lastest rom with security patch and with new bootloader, and replace with new bootloader. now there is 1 april 2018 security patch
i guess ota updates is not safe
Click to expand...
Click to collapse
I'm confused, if you flashed the Dec 2016 stock ROM, the next update you'd have received would have likely been the March 2017 security patch OTA (NPJS25.93-14-4) update. How did you get the April 2018 OTA update? If your device had been on a previously newer build of stock Nougat, using that would have been a bad idea.
If you fully updated to the April 2018 security patch stock ROM, with the bootloader at version B1:07, you may be okay taking OTA updates. Please next time, double check the firmware you need. There's many sites with various firmwares and some of them can be quite old.
echo92 said:
I'm confused, if you flashed the Dec 2016 stock ROM, the next update you'd have received would have likely been the March 2017 security patch OTA (NPJS25.93-14-4) update. How did you get the April 2018 OTA update? If your device had been on a previously newer build of stock Nougat, using that would have been a bad idea.
If you fully updated to the April 2018 security patch stock ROM, with the bootloader at version B1:07, you may be okay taking OTA updates. Please next time, double check the firmware you need. There's many sites with various firmwares and some of them can be quite old.
Click to expand...
Click to collapse
No, i did not flashed 2016 stock rom, i flashed 2018 stock rom, but bootloader file was old, because i downloded it from old topic. when i replaced 2018 stock rom's bootloader file instead of old bootloader file, now i have 2018 1 april security patch. i think i can not install ota updates if them future come, because again my phone will be bricked
one reason is that if bootloader is unlocked, you do not have pemission to change something, but yesterday i installed ota update from 6.0 to 6.0.1 or security patch i do not know exactly, and while Nougat install finishes phone was bricked
gioyocho said:
Thanks for reply!
i had installed many drivers. even qualcomm and motorola, but situation is such. see file attachment. looks like my phone is in coma. i have windows 10. i will say long story short
1. i had android 8.1.0 RR, it was heating and i changed to RR 7.1.2. it worked good
2. it was also heating and i decides to change kernel and phone stop on RR logo, it was rounding but phone won't working. i had no backup or rom files
3. then i installed stock rom 6.0 marshmallow from fastboot with cmd, i downloded it from motorola's official site. i had 6.0 and bootloader unlocked. than came 6.0.1 ota and i updated it was ok. than came also ota update Nougat and installation process phone won't boot
Click to expand...
Click to collapse
just to be clear this all happened from RR 8.1.0? why did you not just follow what i said here and start your RR 7.1.2?
https://forum.xda-developers.com/showpost.php?p=76628308&postcount=1828
You could have saved yourself all the hassle
gioyocho said:
No, i did not flashed 2016 stock rom, i flashed 2018 stock rom, but bootloader file was old, because i downloded it from old topic. when i replaced 2018 stock rom's bootloader file instead of old bootloader file, now i have 2018 1 april security patch. i think i can not install ota updates if them future come, because again my phone will be bricked
one reason is that if bootloader is unlocked, you do not have pemission to change something, but yesterday i installed ota update from 6.0 to 6.0.1 or security patch i do not know exactly, and while Nougat install finishes phone was bricked
Click to expand...
Click to collapse
I'm still confused, you mentioned the December 2016 security patch (NPJ25.93-14), is that the firmware you were on before? I'm just trying to work out what firmware you had/were flashing on your device (since you mentioned Marshmallow 6.0.1 and then mentioned April 2018, there's a lot of builds inbetween those versions...)
I'm also confused by the reasoning for using the old bootloader file with the April 2018 stock ROM, can you explain the thinking behind mixing old and new firmware files, or have I misunderstood you?
You mentioned previously with bricking on the April 2018 OTA, what firmware version were you on then, if you can remember? I'm just curious as I've not heard of bricks on the April 2018 update yet.
The safest way to use OTA updates is to have your device formally on the same security patch level. In your case, you must ensure your device has the April 2018 B1:07 bootloader/GPT/system/modem etc. Doesn't matter if your bootloader is unlocked or locked (though a locked bootloader would strictly enforce having the same firmware patch level). Mixing firmwares is not a good idea for OTA updates as you found out. When you downgraded to Marshmallow, you likely did not downgrade your bootloader (your bootloader would have blocked the flashing of an older bootloader), so you had a Nougat bootloader but a Marshmallow system. Taking a Marshmallow or old Nougat OTA would have likely corrupted your newer Nougat bootloader (as OTA updates do not appear to check your bootloader version). Hence why you hard bricked then. I'm curious as to why this may have happened with the April 2018 OTA though.
Ayan Uchiha Choudhury said:
just to be clear this all happened from RR 8.1.0? why did you not just follow what i said here and start your RR 7.1.2?
https://forum.xda-developers.com/showpost.php?p=76628308&postcount=1828
You could have saved yourself all the hassle
Click to expand...
Click to collapse
Thanks for reply. your post was after i installed another kernel and i had bootloop
Related
I've flashed a stock firmware everyone else flashed. But after flashing, my phone's fingerprint and networks are not working.
In the settings, the baseband is also not "ATHENE_INDIA_DSDS_CUST". It's "DFLT_FSG".
Please help me.
You flashed the wrong one obviously. Which file did u flash?
Sent from my Moto G4 Plus using Tapatalk
Silesh.Nair said:
You flashed the wrong one obviously. Which file did u flash?
Sent from my Moto G4 Plus using Tapatalk
Click to expand...
Click to collapse
This one
http://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1643-updated-signed-t3460695
That's the correct one. Only your baseband is different? Rest all works. In that case just flash fsg.bin and NON-HLOS.bin and wipe modem1 and modem2.
Sent from my Moto G4 Plus using Tapatalk
Silesh.Nair said:
That's the correct one. Only your baseband is different? Rest all works. In that case just flash fsg.bin and NON-HLOS.bin and wipe modem1 and modem2.
Sent from my Moto G4 Plus using Tapatalk
Click to expand...
Click to collapse
Tried flashing it. No success. Also the fiingerprint reader is also missing.
Even i have the same issue...FP sensor is not recognised during initial setup and also the setting is missing in the settings menu.
Flash the Indian modems doesn't work. Dailing *#06# shows only one IMEI number.Sim card is detected but always stays on No service mode....attempting to search for networks from setting results in an error.Service centre didn't accept my phone saying theres only one IMEI number and the bootloader is unlocked.Any help would be appreciated as we have no where to go.
GeeteshKhatavkar said:
Even i have the same issue...FP sensor is not recognised during initial setup and also the setting is missing in the settings menu.
Flash the Indian modems doesn't work. Dailing *#06# shows only one IMEI number.Sim card is detected but always stays on No service mode....attempting to search for networks from setting results in an error.Service centre didn't accept my phone saying theres only one IMEI number and the bootloader is unlocked.Any help would be appreciated as we have no where to go.
Click to expand...
Click to collapse
Glad that someone acknowledge the issue. There is one more guy here at xda roaming with the same problem. I've tried almost every method possible. Still no luck. But for luck, my service center guy offered a free board replacement for the problem. If xda guys didn help, I would send it for replacement. Mine is also bootloader unlocked and software status modified, but he is okey to offer a replacement.
sabithmk said:
Glad that someone acknowledge the issue. There is one more guy here at xda roaming with the same problem. I've tried almost every method possible. Still no luck. But for luck, my service center guy offered a free board replacement for the problem. If xda guys didn help, I would send it for replacement. Mine is also bootloader unlocked and software status modified, but he is okey to offer a replacement.
Click to expand...
Click to collapse
Which city ?I think you should go for the replacement and then update it via OTA when you get a notification.
Any Solutions Yet ?
Has anyone found any solutions yet !?
It is surely a Software issue
Service Center people are asking Rs.6500/- to replace the motherboard
Can't even relock the bootloader as i flashed the Nougat OTA and thus i can't downgrade the bootloader and lock it either !!
Please Help !
sabithmk said:
I've flashed a stock firmware everyone else flashed. But after flashing, my phone's fingerprint and networks are not working.
In the settings, the baseband is also not "ATHENE_INDIA_DSDS_CUST". It's "DFLT_FSG".
Please help me.
Click to expand...
Click to collapse
You found any solution?? I am facing the same problem...
bonnyshroff said:
You found any solution?? I am facing the same problem...
Click to expand...
Click to collapse
I sent it for service and got a free replacement.
bonnyshroff said:
You found any solution?? I am facing the same problem...
Click to expand...
Click to collapse
Yes I found it..
I created a thread. Check this.
https://forum.xda-developers.com/moto-g4-plus/how-to/solve-moto-g4-plus-one-imei-fp-sensor-t3800410
---------- Post added at 11:38 AM ---------- Previous post was at 11:36 AM ----------
sabithmk said:
I've flashed a stock firmware everyone else flashed. But after flashing, my phone's fingerprint and networks are not working.
In the settings, the baseband is also not "ATHENE_INDIA_DSDS_CUST". It's "DFLT_FSG".
Please help me.
Click to expand...
Click to collapse
Check this link friend. I did it. Was having same problem as you.
Check the thread I created.
https://forum.xda-developers.com/moto-g4-plus/how-to/solve-moto-g4-plus-one-imei-fp-sensor-t3800410
Try this https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
I have moto g4 xt1622 and everything works fine
I did it by next topic
https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761
But do not use ota updates in future. You can flash new same system if someone collect again after came securty patch or os update
You need these files and run commands. See up link guide
http://www.mediafire.com/file/owo07yg79m3mxw6/Minimal ADB and Fastboot.rar
gioyocho said:
Try this https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
I have moto g4 xt1622 and everything works fine
I did it by next topic
https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761
But do not use ota updates in future. You can flash new same system if someone collect again after came securty patch or os update
You need these files and run commands. See up link guide
http://www.mediafire.com/file/owo07yg79m3mxw6/Minimal ADB and Fastboot.rar
Click to expand...
Click to collapse
A few things:
1) As long as you are fully updated to the latest stock ROM, OTA updates should not be a problem. OTA updates are usually a problem if you have downgraded your device (like in your case downgrading to Dec 2016 firmware) or not having the full stock ROM, including the bootloader of the same patch level, (i.e. having mixed firmware) flashed to your device. If you really want to, you can use the latest stock ROM to re-lock your bootloader, and providing it's the correct stock ROM for your region/device, you should receive and be able to flash OTA updates without problem (as a locked bootloader will enforce you having firmware matching the bootloader update level).
2)I'm not sure how a minimal ADB/fastboot image is 900+ MB. Unless that mediafire link is pointing to the Android SDK which includes the ADB and fastboot programs, the minimal ADB/fastboot is about 1 MB https://forum.xda-developers.com/showthread.php?t=2317790
3)Unfortunately, repairing IMEI and loss of fingerprint sensor is not as straightforward as flashing the stock ROM. You may require the hw, fsg and modem images.
echo92 said:
A few things:
1) As long as you are fully updated to the latest stock ROM, OTA updates should not be a problem. OTA updates are usually a problem if you have downgraded your device (like in your case downgrading to Dec 2016 firmware) or not having the full stock ROM, including the bootloader of the same patch level, (i.e. having mixed firmware) flashed to your device. If you really want to, you can use the latest stock ROM to re-lock your bootloader, and providing it's the correct stock ROM for your region/device, you should receive and be able to flash OTA updates without problem (as a locked bootloader will enforce you having firmware matching the bootloader update level).
2)I'm not sure how a minimal ADB/fastboot image is 900+ MB. Unless that mediafire link is pointing to the Android SDK which includes the ADB and fastboot programs, the minimal ADB/fastboot is about 1 MB https://forum.xda-developers.com/showthread.php?t=2317790
3)Unfortunately, repairing IMEI and loss of fingerprint sensor is not as straightforward as flashing the stock ROM. You may require the hw, fsg and modem images.
Click to expand...
Click to collapse
Well
1. if you have unlocked bootloader, you can not re-lock. i think this is the brick's reason. i had installed yes old bootloader file with december 2016 security patch, then came ota update to april 2018 security patch and phone has bricked, as from marshmallow to nougat update while bootloader was unlocked. but i do not know reason exactly, because first time i did stock marshmallow 6.0 rom, then came ota update everything works fine new security patch of 6.0, after that came nougat ota update and phone was bricked
2. yes there is difference between .rar and folder. just extract it
3. if it is hardware issue, rom can not change anything yes
gioyocho said:
Well
1. if you have unlocked bootloader, you can not re-lock. i think this is the brick's reason. i had installed yes old bootloader file with december 2016 security patch, then came ota update to april 2018 security patch and phone has bricked, as from marshmallow to nougat update while bootloader was unlocked. but i do not know reason exactly, because first time i did stock marshmallow 6.0 rom, then came ota update everything works fine new security patch of 6.0, after that came nougat ota update and phone was bricked
2. yes there is difference between .rar and folder. just extract it
3. if it is hardware issue, rom can not change anything yes
Click to expand...
Click to collapse
1)You can re-lock your device with the April 2018 stock firmware https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138. You need a stock firmware image as new or newer than your bootloader - we've seen many examples on this stock ROM thread of users re-locking their bootloaders.
The likely reason that you hard bricked is that you did not actually downgrade your bootloader when you flashed the Marshmallow stock ROM. Hence, you still had the Nougat bootloader on your device, which got corrupted when you used the old MM to Nougat OTA.
To re-lock your device, you must use the newest appropriate firmware for your device. Do not flash old stock firmware (including MM) and do not mix your firmwares (do not flash old bootloader files with new firmware). Of course, re-locking your bootloader will not restore your warranty and the process will erase your device, so up to you.
gioyocho said:
Try this https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
I have moto g4 xt1622 and everything works fine
I did it by next topic
https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761
But do not use ota updates in future. You can flash new same system if someone collect again after came securty patch or os update
You need these files and run commands. See up link guide
http://www.mediafire.com/file/owo07yg79m3mxw6/Minimal ADB and Fastboot.rar
Click to expand...
Click to collapse
Check my link.
You can even OTA update in future if you installed the latest firmware.
https://forum.xda-developers.com/moto-g4-plus/how-to/solve-moto-g4-plus-one-imei-fp-sensor-t3800410
echo92 said:
1)You can re-lock your device with the April 2018 stock firmware https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138. You need a stock firmware image as new or newer than your bootloader - we've seen many examples on this stock ROM thread of users re-locking their bootloaders.
The likely reason that you hard bricked is that you did not actually downgrade your bootloader when you flashed the Marshmallow stock ROM. Hence, you still had the Nougat bootloader on your device, which got corrupted when you used the old MM to Nougat OTA.
To re-lock your device, you must use the newest appropriate firmware for your device. Do not flash old stock firmware (including MM) and do not mix your firmwares (do not flash old bootloader files with new firmware). Of course, re-locking your bootloader will not restore your warranty and the process will erase your device, so up to you.
Click to expand...
Click to collapse
I do not know how to re-lock bootloader. i have latest stock rom 7.0 with april security patch
gioyocho said:
I do not know how to re-lock bootloader. i have latest stock rom 7.0 with april security patch
Click to expand...
Click to collapse
If you have a look and read of the stock ROM initial post https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 in that guide you'll see flashing commands that should let you re-lock your bootloader.
Also, if you want to re-lock your bootloader, check that you have OEM unlocking enabled in Settings>Developer Options (the same toggle you turned on when you unlocked the bootloader in the first place).
So the summary is:
1)Turn on OEM unlocking in Settings>Developer Options.
2)Boot your device to bootloader
3)Fully flash the April 2018 stock ROM (all files must be from the April 2018 stock ROM, no exceptions) as per the flashing commands in the guide, including all the OEM lock commands. This should wipe your device, re-lock your bootloader and let you boot with stock files. Attempting to mix files will cause your lock to fail or your device to not boot, as the firmware you flashed is now being checked by your bootloader to verify it's all from the same firmware.
echo92 said:
If you have a look and read of the stock ROM initial post https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 in that guide you'll see flashing commands that should let you re-lock your bootloader.
Also, if you want to re-lock your bootloader, check that you have OEM unlocking enabled in Settings>Developer Options (the same toggle you turned on when you unlocked the bootloader in the first place).
So the summary is:
1)Turn on OEM unlocking in Settings>Developer Options.
2)Boot your device to bootloader
3)Fully flash the April 2018 stock ROM (all files must be from the April 2018 stock ROM, no exceptions) as per the flashing commands in the guide, including all the OEM lock commands. This should wipe your device, re-lock your bootloader and let you boot with stock files. Attempting to mix files will cause your lock to fail or your device to not boot, as the firmware you flashed is now being checked by your bootloader to verify it's all from the same firmware.
Click to expand...
Click to collapse
well i tried and did not work those run commands
Solved, Check below for solution
Please help me to revive my Moto G4 .
Hi got a pure evil phone (Hard Bricked)
How This Happened :
Everything was going good then i lost my Volte network, I tried to solve by wiping cache and dalvik cache, didn't worked then wiped data, didn't worked, Then i decided to flash it to stock.
I was in the latest version of Nougat 01 June Security patch a custom kernel with root, TWRP and obviously unlocked bootloader. In first i could not find my version of stock rom which is NPJS25 then i decided to flash another stock which is at November 2016 patch version (NPJ25). When flashing I just left the gpt.bin and bootloader.bin thinking that i already have the latest partition table (Maybe it was an horrible mistake). After flashing i got my VOLTE back everything good now.
Then I searched for system update, got one from December (118MB) installed it, Then searching got another from March(May be) it was getting installed then the disaster happened it got switched off, waited for 5 mins tried to Start it, failing hereafter connected it to Pc, got QSHUSB_BULK in device manager. Then updating the driver and flashing the blankflash i got fastboot(the first sign of live). after that i am not moving.
what i tried
Upon starting it i get "Failed to initialize partition table" in Bootloader logs
When i try to flash gpt.bin from NPJ25 it says "Preflash Verification failed".
Now what i got is a nice fastboot mode, locked bootloader, ****ed up gpt.bin.
Any idea of solving it ??
This Thread Solved my problem, try it if you have same type of problem
You may wish to consult the following blankflash guide: https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761 This has links to a blankflash, and GPT/bootloader and a fastboot ROM of the June 2017 NPJS25.93-14-8 stock ROM (that's been around for a little while too). Hopefully that'll rescue your device. Sounds like you need the fastboot June 2017 stock ROM to reflash your GPT, bootloader and core firmware. How did you manage to re-lock your bootloader btw?? (NOTE - the NPJS25.93-14-8 ROM appears to be for retail non-USA devices).
Also, with losing VoLTE, did you confirm with your mobile network operator if it was you or if they were having an outage in your area?
As an aside to anyone else, downgrading from June 2017 with an older stock ROM and then attempting to take an OTA has a very high risk of hard bricking.
echo92 said:
You may wish to consult the following blankflash guide: https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761 This has links to a blankflash, and GPT/bootloader and a fastboot ROM of the June 2017 NPJS25.93-14-8 stock ROM (that's been around for a little while too). Hopefully that'll rescue your device. Sounds like you need the fastboot June 2017 stock ROM to reflash your GPT, bootloader and core firmware. How did you manage to re-lock your bootloader btw?? (NOTE - the NPJS25.93-14-8 ROM appears to be for retail non-USA devices).
Also, with losing VoLTE, did you confirm with your mobile network operator if it was you or if they were having an outage in your area?
As an aside to anyone else, downgrading from June 2017 with an older stock ROM and then attempting to take an OTA has a very high risk of hard bricking.
Click to expand...
Click to collapse
Yes that fantastic thread save my phone. What i was doing is that flashing the gpt partition taken out from november Nougat rom and i was getting error because i already had the latest corrupted partition. ''fastboot oem lock'' reports that The devices is not in unlocked form, but that was not actually it. May be the fastboot had trouble getting out the information of state of lock because of corrupted partition but after flashing the latest gpt.bin and rebooting fixed all the problems everything is good as it was. I didn't had to even flash anything after that and phone was also updated to the version it corrupted in.
So the experience told that while updating through OTA it tries to update the partition at last even it had not to. Maybe it is technically not possible check the state, i dont know.
xCALIFIER said:
Yes that fantastic thread save my phone. What i was doing is that flashing the gpt partition taken out from november Nougat rom and i was getting error because i already had the latest corrupted partition. ''fastboot oem lock'' reports that The devices is not in unlocked form, but that was not actually it. May be the fastboot had trouble getting out the information of state of lock because of corrupted partition but after flashing the latest gpt.bin and rebooting fixed all the problems everything is good as it was. I didn't had to even flash anything after that and phone was also updated to the version it corrupted in.
So the experience told that while updating through OTA it tries to update the partition at last even it had not to. Maybe it is technically not possible check the state, i dont know.
Click to expand...
Click to collapse
Good to hear that the guide and just repairing your bootloader/GPT was enough to get your device running.
As I understand it, OTAs check your system version and whether you have a stock recovery/stock kernel and unmodified system, but not necessarily whether your bootloader or GPT are at the same patch level as your system. Thus, the OTA you downloaded thought your device was on the December 2016 patch level, and attempted to patch up to March 2017, but your bootloader was actually from June 2017, so corrupting your bootloader. Hence why taking OTAs are so dangerous after a downgrade, especially recently with the June 2017 update, where Motorola patched a bootloader vulnerability, and thus may prevent you downgrading to stop you from re-opening the vulnerability.
Incidentally, this OTA behaviour isn't isolated to our Moto G4/Plus, we've seen it on Moto X (https://forum.xda-developers.com/moto-x-2014/general/warning-downgrade-bootloader-partition-t3105147), Moto Z/Play and other Moto devices, and I've noted it on LG devices too. It's just becoming riskier to update via OTA if you've downgraded. The safest way is either to not downgrade or update using the latest fastboot ROM (preferably the same build as the one you had previously)
echo92 said:
Good to hear that the guide and just repairing your bootloader/GPT was enough to get your device running.
As I understand it, OTAs check your system version and whether you have a stock recovery/stock kernel and unmodified system, but not necessarily whether your bootloader or GPT are at the same patch level as your system. Thus, the OTA you downloaded thought your device was on the December 2016 patch level, and attempted to patch up to March 2017, but your bootloader was actually from June 2017, so corrupting your bootloader. Hence why taking OTAs are so dangerous after a downgrade, especially recently with the June 2017 update, where Motorola patched a bootloader vulnerability, and thus may prevent you downgrading to stop you from re-opening the vulnerability.
Incidentally, this OTA behaviour isn't isolated to our Moto G4/Plus, we've seen it on Moto X (https://forum.xda-developers.com/moto-x-2014/general/warning-downgrade-bootloader-partition-t3105147), Moto Z/Play and other Moto devices, and I've noted it on LG devices too. It's just becoming riskier to update via OTA if you've downgraded. The safest way is either to not downgrade or update using the latest fastboot ROM (preferably the same build as the one you had previously)
Click to expand...
Click to collapse
Yes, exactly. Before upgrading through One should keep in mind that if the update was built for him or not in context of modification to his device.
Hi everyone When I am Rooted My Moto G4 Plus and install custom rom thn i downgrade to Official 7.0 with Dec 2016 Security Patch Update and when i try to Official OTA update of march 2017 with unlock bootloader but my phone goes hardbrick than via "blank flash" now i am on Official stock June 2017 security patch update and i Relocked my bootloader.....So My Question Is can i Update Further Upcoming Security patch or any official OTA update..??? Or My phone get Hardbrick????? Plz reply....
pritesh barot said:
Hi everyone When I am Rooted My Moto G4 Plus and install custom rom thn i downgrade to Official 7.0 with Dec 2016 Security Patch Update and when i try to Official OTA update of march 2017 with unlock bootloader but my phone goes hardbrick than via "blank flash" now i am on Official stock June 2017 security patch update and i Relocked my bootloader.....So My Question Is can i Update Further Upcoming Security patch or any official OTA update..??? Or My phone get Hardbrick????? Plz reply....
Click to expand...
Click to collapse
I have same question ,but I'm asking you can I unlock bootloader again
1) You can unlock the bootloader again, each time will wipe your device however. I think you can use the same unlock code as issued by Motorola (provided nothing has changed with your device hardware - i.e. you have the same motherboard).
2)As I mentioned in the other thread, if you've hard bricked and you flashed the June 2017 stock ROM in its entirety - all commands and wipes, then you may be okay to accept and install OTA updates. This is dependent on you having flashed all parts of that stock ROM, so your device is at the same patch level - if you have not, then taking the OTA might hardbrick you again. The OTA updates do not necessarily include complete files, they mainly are a collection of patches, and assume your device is at the same patch level (GPT, bootloader, system, kernel, and other firmware are all at the June 2017 patch level, for example).
If you're worried at all about the OTA updates, wait for an updated fastboot stock ROM with the included update, which is safer.
3)Once you've taken any OTA updates newer than June 2017, it is no longer safe to attempt to flash the June 2017 stock ROM - if you want to go back to stock, wait for an updated stock ROM to be leaked. Else, you could downgrade (which I do not recommend), but do not accept OTA updates. Our newest blankflash works on B1:06 bootloaders, I do not know if it works on newer bootloaders. If not, and you hard brick, you'll likely have to wait for a new blankflash or pay for a new motherboard. A new motherboard is around 7000-10000 rupees or your regional equivalent, from what I've seen.
echo92 said:
1) You can unlock the bootloader again, each time will wipe your device however. I think you can use the same unlock code as issued by Motorola (provided nothing has changed with your device hardware - i.e. you have the same motherboard).
2)As I mentioned in the other thread, if you've hard bricked and you flashed the June 2017 stock ROM in its entirety - all commands and wipes, then you may be okay to accept and install OTA updates. This is dependent on you having flashed all parts of that stock ROM, so your device is at the same patch level - if you have not, then taking the OTA might hardbrick you again. The OTA updates do not necessarily include complete files, they mainly are a collection of patches, and assume your device is at the same patch level (GPT, bootloader, system, kernel, and other firmware are all at the June 2017 patch level, for example).
If you're worried at all about the OTA updates, wait for an updated fastboot stock ROM with the included update, which is safer.
3)Once you've taken any OTA updates newer than June 2017, it is no longer safe to attempt to flash the June 2017 stock ROM - if you want to go back to stock, wait for an updated stock ROM to be leaked. Else, you could downgrade (which I do not recommend), but do not accept OTA updates. Our newest blankflash works on B1:06 bootloaders, I do not know if it works on newer bootloaders. If not, and you hard brick, you'll likely have to wait for a new blankflash or pay for a new motherboard. A new motherboard is around 7000-10000 rupees or your regional equivalent, from what I've seen.
Click to expand...
Click to collapse
Now I Hve Successfully Relock My Bootloader and now i am on stock June 2017 Can I Reflash With Same June 2017 without Unlocking Bootloader Again because during Relock i used Command Directly From X Da Thread For Relock Bootloader and Don't Sure Fully Install June 2017 Rom So Want To Reflash With 'Stock Flash.Bat' File So I Will Get OTA Without Waiting For Updated Fastboot Stock Rom....So Can I Flash June 2017 Without Unlocking Bootloader....??? Plz Reply...
pritesh barot said:
Now I Hve Successfully Relock My Bootloader and now i am on stock June 2017 Can I Reflash With Same June 2017 without Unlocking Bootloader Again because during Relock i used Command Directly From X Da Thread For Relock Bootloader and Don't Sure Fully Install June 2017 Rom So Want To Reflash With 'Stock Flash.Bat' File So I Will Get OTA Without Waiting For Updated Fastboot Stock Rom....So Can I Flash June 2017 Without Unlocking Bootloader....??? Plz Reply...
Click to expand...
Click to collapse
Can I Reflash With Same June 2017 without Unlocking Bootloader - yes, the stock ROMs we have access to should be signed by Motorola, so should flash on a locked or unlocked bootloader regardless.
You should be able to get OTA updates without waiting for an updated stock ROM. From your previous posts, you seem unsure of this. It is still up to you and your responsibility whether you choose to take an OTA or wait for the updated stock ROM. If you re-locked your bootloader, then you must have been able to re-flash the entire stock ROM, else you may have failed to boot (as you'd have likely failed the verification checks performed by a locked bootloader). Thus, your device might be okay to update. Again, as I have mentioned previously in replies to your posts, if you are worried about hard bricking, then wait for the updated fastboot ROM. The updated fastboot ROM has complete files and thus has a lower risk of damaging/bricking your device. I understand you're eager to get the latest OTA updates, however you could wait and see if there are any bugs/outstanding issues before updating.
Depending on the commands in that stock flash.bat file, you may wipe your device, so back up accordingly.
As an aside, how are you not sure you flashed the full stock ROM? Surely if you followed the guide and used all the commands, you'd have fully flashed? If you look in the stock flash.bat script (open it in Notepad or a text viewer), you'll note the commands should be the same as what you used previously?
I cannot turn on moto g4 plus. While connecting the charger the led is blinking but cannot see the charging sign on screen. Please help
What ROM were you running and what device do you have?
Did you flash anything or install anything prior to your device being in this state?
echo92 said:
What ROM were you running and what device do you have?
Did you flash anything or install anything prior to your device being in this state?
Click to expand...
Click to collapse
I was using AICP oreo, but after that i unroot my device and backed to stock.i installed the security patch and after that it's dead. Nothing else i did.
My device is XT1643
Krish_Vihaag said:
I was using AICP oreo, but after that i unroot my device and backed to stock.i installed the security patch and after that it's dead. Nothing else i did.
My device is XT1643
Click to expand...
Click to collapse
Sounds like you bricked it cause you take ota on stock rom and you don't have stock recovery I think... You should try to flash the stock rom via fastboot https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
Your information about what you did isn't exactly enough to provide a detailed troubleshooting. If you have more detailed information which steps you exactly take and which rom versions you restored etc it would be helpful.
Krish_Vihaag said:
I was using AICP oreo, but after that i unroot my device and backed to stock.i installed the security patch and after that it's dead. Nothing else i did.
My device is XT1643
Click to expand...
Click to collapse
Do you remember what version of stock ROM you had when you flashed AICP ?
I don't think you had December's security patch as itis just month old, so you can try blank-flash with September's patch update.
to blank-flash (download September's gpt and bootloader, where it's mentioned on thread)
Follow it.: https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761
EDIT: Before proceeding to blank-flash, can you tell us if you have access to bootloader or recovery ?
If not, then proceed for blank-flash.
After flashing my phone with Moto G4 Plus XT1640-43 ATHENE NPJ25.93-14 Stock Img, I tried to update the April 2018 security patch. After that my phone doesn't start. Then I use blank flash and my phone starts with recovery mode. Now the problem is when I try to flash my phone again, it say security version downgrade and FAILED. Can you guys please help me into this?
Mayur Thakur said:
After flashing my phone with Moto G4 Plus XT1640-43 ATHENE NPJ25.93-14 Stock Img, I tried to update the April 2018 security patch. After that my phone doesn't start. Then I use blank flash and my phone starts with recovery mode. Now the problem is when I try to flash my phone again, it say security version downgrade and FAILED. Can you guys please help me into this?
Click to expand...
Click to collapse
Sounds like you flashed the Dec 2016 security patch firmware, and then took an OTA - the OTA update on a downgraded firmware likely is what hard bricked your device.
Flash this April 2018 stock firmware: https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
In future, please do not flash older stock firmware, or if you do downgrade, please do not use OTA updates. The safest way to update is to flash the latest stock firmware for your device/region - after that, OTA updates may be safe.
MOTO G4 plus stock rom
MOTO G4 plus will get OREO update officially so I flashed latest firmware via fastboot on my phone so can update it through ota update when it will be able without bricking my phone or else when it comes I should download the zip and flash it with fastboot with step same step of flahsing nougat forward on my phone
Gaminwarrior said:
MOTO G4 plus will get OREO update officially so I flashed latest firmware via fastboot on my phone so can update it through ota update when it will be able without bricking my phone or else when it comes I should download the zip and flash it with fastboot with step same step of flahsing nougat forward on my phone
Click to expand...
Click to collapse
Nobody can tell you about future things, but in my opinion it should be like this.
Hi everyone,I hope someone can help.I recently used the toolkit available to unlock my bootloader,flash twrp and tried to flash a rom.
To say it didnt go to plan would be putting it mildly
Nothing i tried to flash via twrp would actually flash,any rom would fail.
I did eventually get stock reflashed via adb ,still with twrp....had problems with camera and with other apps.
Its working ok now but im stock with october security patch and i cant seem to update it,either by ota or by flashing it
Im on build NPN25.137-92
Baseband m8953_37.46.07.47R POTTER-EMEA_CUST
either id like to get back to fully stock and just wait for the incoming Oreo update or be able to flash a custom rom......help me XDA'ers,your my only hope
Are you running a device with the reteu software channel (I'm guessing so from the EMEA baseband)? If so, the NPN25.137-92 firmware is not for your device - that series of firmwares is for Brazil and Indian devices. EU/US/Asia devices received the NPN25.137-93 series of firmwares (with the latest being NPNS25.137-93-10), so having the incorrect firmware for your device is likely why you are not receiving OTA updates (it's likely the servers don't recognise the combination of your software channel and firmware build).
You can either flash the NPNS25.137-93-4 (Jan 2018 security patch) firmware from here https://forum.xda-developers.com/showpost.php?p=75666258&postcount=3 or the NPNS25.137-93-10 April 2018 security patch firmware from here https://forum.xda-developers.com/g5-plus/development/april-security-patch-xt1687-npns25-137-t3796797 Both should get you back on the OTA update channel, though as always, you may have to lose TWRP (then again, you cannot use OTA updates with TWRP flashed, you need a fully stock and clean device for OTA updates). You could flash TWRP after flashing either of these stock ROMs.
If you do decide to flash either of the aforementioned stock ROMs, please delete the NPN25.137-92 stock ROM and any older stock ROMs from your computer, so you don't accidentally flash an older stock ROM to your device. If you do decide to flash an older stock ROM than the latest firmware on your device, be very careful when using OTA updates; OTA updates on downgraded firmware could cause hard bricks.
Im actually just over the bridge from you in Looe,so im guessing they are very wrong firmwares for me...should of mentioned previously that im in the uk
hippopig said:
Im actually just over the bridge from you in Looe,so im guessing they are very wrong firmwares for me...should of mentioned previously that im in the uk
Click to expand...
Click to collapse
Woo, good to meet you - how's things been in Looe? I imagine really busy given how sunny it's been our way?
Yeah, if you flash either of the NPN25.137-93 series of firmwares, you should be back on the official OTA track for EU/UK firmware (I think that the EU firmware release is the same as the UK), so should get your device back up and running. As for Oreo, we've not seen the soak test beta firmware being tested yet, so we might be waiting a while for the official Oreo.
What errors were you getting btw with TWRP flashing? The error wasn't error 255 by any chance?
Yeah super busy...summer is here woooo,ok ill try and find them tonight and flash it again,I dont think oreo will be coming soon either really......might just flash a custom rom once i can
And yes its error 255 all the time,cant flash anything via twrp at all
hippopig said:
Yeah super busy...summer is here woooo,ok ill try and find them tonight and flash it again,I dont think oreo will be coming soon either really......might just flash a custom rom once i can
And yes its error 255 all the time,cant flash anything via twrp at all
Click to expand...
Click to collapse
Honestly it's up to you - there's reports that soak test invitations have been sent out to Motorola Feedback Network members, so the tests should be happening in the next few weeks. Of course, when the official Oreo OTA will arrive will be dependent on the results of those tests (and what bugs occur).
Hmm, what TWRP version are you using to flash the custom ROMs, and which custom ROMs have you had the issue with?
The problem is that the toolkit twrp is 32bit. You need the latest 64bit twrp to flash anything oreo. I assume you are trying to flash oreo ROMs since most of them are.
on it now,thanks for the replies guys,lol now my pc wont recognise my phone at all
hippopig said:
on it now,thanks for the replies guys,lol now my pc wont recognise my phone at all
Click to expand...
Click to collapse
That's not good - are you in fastboot or ADB when your device isn't recognised? If you're in fastboot, and on Windows 10 or 8.1, try to disable driver signature enforcement (as Microsoft appears to only let signed WHQL drivers load otherwise, which fastboot isn't as far as I know). Have you still got the Motorola USB drivers installed on your computer? If you're using Windows, does your device appear in Device Manager?
Sorry,looks as though its the lead....connecting now
as always,thanks you guys....would be knackered without the support of xda'ers from all over....up and running again on pixel experience