Database Users

Revert to Stock Recovery

Hello,
I see my Moto G4 has a System update today, but I have installed a custom Recovery (TeamWin), how do I go back to stock recovery, so I can install the update.
Thanks,
Shannon

You need the stock recovery.img. You can get it downloading the same ROM your device is running. After that, start your device in fastboot mode, copy the recovery.img that came with the ROM that you downloaded before and paste inside ABD folder and finally write this command in CMD:
fastboot flash recovery recovery.img
Done!

shannonsumner said:
Hello,
I see my Moto G4 has a System update today, but I have installed a custom Recovery (TeamWin), how do I go back to stock recovery, so I can install the update.
Thanks,
Shannon
Click to expand...
Click to collapse
You've got a couple of options:
1a) Download a stock recovery from shrep's site https://moto.shreps.fr/?dir=Moto G4 (athene)/recovery Try to ensure the recovery you download matches your region's build number (MPJ24.139-23.4 and MPJ24.139-63 are MM recoveries, I think for EMEA regions and maybe for India too for 139-63, whereas NPJ25.75-2 is a Nougat soak test recovery).
1b)Flash in TWRP (I recall in TWRP, under Install, there's an option to flash images and you'll want to flash this as a recovery image.) Reboot to recovery to ensure the stock recovery doesn't get overwritten.
2) If you're not sure whether the recoveries on shrep's site are suitable for your device/region, you may wish to directly upgrade to Nougat using the fastboot 93-14 Nougat ROM file here:https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369 This will flash a stock Nougat ROM, v7.0, Dec 2016 security patch, which appears to be the current global build deployed (and likely would be the same build as if you updated via OTA). Of course, this process may erase your data so back up, and will remove TWRP as it'll flash a stock recovery onto your device.

shannonsumner said:
Hello,
I see my Moto G4 has a System update today, but I have installed a custom Recovery (TeamWin), how do I go back to stock recovery, so I can install the update.
Thanks,
Shannon
Click to expand...
Click to collapse
You'll need to correct image for your model XT16XX, you can find it at https://firmware.center

shannonsumner said:
Hello,
but I have installed a custom Recovery (TeamWin), how do I go back to stock recovery,
Thanks,
Shannon
Click to expand...
Click to collapse
The same way you installed the custom recovery.

CEDRIC_NPPS25.137-72-4_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip

Download full fw.
BUILD REQUEST INFO:
SW Version: cedric-user 7.0 NPPS25.137-72-4 4 release-keysM8937_11.16.02.51R
MBM Version: B8.23
Modem Version: M8937_11.16.02.51R
FSG Version: FSG-8937-02.65.05
Build Fingerprint: motorola/cedric/cedric:7.0/NPPS25.137-72-4/4:user/release-keys
VERSION INFO FOUND UNDER 'ABOUT PHONE' SCREEN:
System Version: 25.246.4.cedric.retail.en.US
Model number: Moto G (5)
Android Version: 7.0
Baseband Version: M8937_11.16.02.51R
Build Number: cedric-user 7.0 NPPS25.137-72-4 4 release-keys
Build Date: Fri Aug 4 04:22:37 CDT 2017
OTHER MISC VERSION INFO:
Subsidy Lock Config: slcf_rev_d_default_v1.0.nvm
Regulatory Info (eLabel): regulatory_info_default.png
Blur Version: Blur_Version.25.246.4.cedric.retail.en.US
Version when read from CPV: cedric-user 7.0 NPPS25.137-72-4 4 release-keys
CEDRIC_NPPS25.137-72-4_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip

What is that?
Sent from my Moto G (5) using Tapatalk

fxdRoiD said:
What is that?
Sent from my Moto G (5) using Tapatalk
Click to expand...
Click to collapse
It's the last available fw for XT1676. NPPS25.137-72-4
https://forum.xda-developers.com/g5/help/stock-rom-moto-g5-xt1676-3-16-dualsim-t3696622
Haven't seen it anywhere untill now when I got a link that was valid for just a few hours, so I thought I should download it and share it.

Is this rom work for moto g5 model XT1677 Indian varient Amazon exclusive ?? If yes voLTE is working or not ??

Anyone have NPPS25.137-79-3 for the XT1670?
Sent from my Moto G5 using Tapatalk

It can relock bootloader?

When I try to install this from TWRP I'm getting an "Invalid zip file format!" error and it refuses to.
Any thoughts on why this could be? Would it be a bad idea to use fastboot to execute all the instructions in flashfile.xml?
I'm trying to install this to rid myself of a stubborn TWRP bootloop (wasn't fixed by e.g. reflashing twrp) and to do an OEM update before trying to restore TWRP, no-verity, Magisk, and my nandroid backup.
My XT1676 currently has TWRP and Magisk. Its settings indicate build number NPPS25.137-72-4, software channel reteu, and baseband version M8937_11.16.02.51R CEDRIC_EMEADSDS_CUST.

macho_ said:
When I try to install this from TWRP I'm getting an "Invalid zip file format!" error and it refuses to.
Any thoughts on why this could be? Would it be a bad idea to use fastboot to execute all the instructions in flashfile.xml?
I'm trying to install this to rid myself of a stubborn TWRP bootloop (wasn't fixed by e.g. reflashing twrp) and to do an OEM update before trying to restore TWRP, no-verity, Magisk, and my nandroid backup.
My XT1676 currently has TWRP and Magisk. Its settings indicate build number NPPS25.137-72-4, software channel reteu, and baseband version M8937_11.16.02.51R CEDRIC_EMEADSDS_CUST.
Click to expand...
Click to collapse
To start off with this is a stock firmware - stock firmware is flashed via fastboot and not twrp using fastboot commands
secondly - if you are talking about your phone booting into twrp instead of booting to system you obviously didn't read the FAQs on my TWRP thread as the answer is there
How to flash stock firmware
https://forum.xda-developers.com/g5/development/official-stock-moto-g5-cedric-firmware-t3733897
twrp thread
https://forum.xda-developers.com/g5/development/official-twrp-3-1-1-0-moto-g5-t3699737

This is great: my searches hadn't previously led me to either of those threads, thanks.
The TWRP bootloop solution seemed to work, although after I tried do the Nov OTA update, I got back into the bootloop and the update failed. Presumably I could have just repeated the fix again.
But instead of doing that, I flashed the stock image above using fastboot. On rebooting I initially got a scary robot-with-its-front-panel-open error that just said "Error!" When I tried to reboot to recovery I got the same robot with "No command". But then weirdly it soon just booted normally on its own. From there the most recent (November) OTA update finally installed without issue, then I restored twrp, magisk, no-verity-opt-encrypt, and finally the data partitions of a backup I made before starting everything above.
I'm really happy about this: these problems had been plaguing me for a while. Thanks again.

macho_ said:
This is great: my searches hadn't previously led me to either of those threads, thanks.
The TWRP bootloop solution seemed to work, although after I tried do the Nov OTA update, I got back into the bootloop and the update failed. Presumably I could have just repeated the fix again.
But instead of doing that, I flashed the stock image above using fastboot. On rebooting I initially got a scary robot-with-its-front-panel-open error that just said "Error!" When I tried to reboot to recovery I got the same robot with "No command". But then weirdly it soon just booted normally on its own. From there the most recent (November) OTA update finally installed without issue, then I restored twrp, magisk, no-verity-opt-encrypt, and finally the data partitions of a backup I made before starting everything above.
I'm really happy about this: these problems had been plaguing me for a while. Thanks again.
Click to expand...
Click to collapse
The robot is stock recovery - hold Vol up & press power button I think to access its menu but all you can really do is a factory reset

Can i install this on 1675 variant?
My bootloader is locked

can I flash stock ROM - with the same patch but another channel (from retin to retus) on a device with a locked bootloader?
if yes, how can I do that? from adb fastboot? RSD lite?

TheFixItMan said:
To start off with this is a stock firmware - stock firmware is flashed via fastboot and not twrp using fastboot commands
secondly - if you are talking about your phone booting into twrp instead of booting to system you obviously didn't read the FAQs on my TWRP thread as the answer is there
How to flash stock firmware
https://forum.xda-developers.com/g5/development/official-stock-moto-g5-cedric-firmware-t3733897
twrp thread
https://forum.xda-developers.com/g5/development/official-twrp-3-1-1-0-moto-g5-t3699737
Click to expand...
Click to collapse
My phone is Moto g5 cedric with NPP25.137-72 android 7.0 this flash update but I want to flash oreo directly, you know about this???

rosel11078 said:
My phone is Moto g5 cedric with NPP25.137-72 android 7.0 this flash update but I want to flash oreo directly, you know about this???
Click to expand...
Click to collapse
Oreo firmware images have not been leaked/released - only the soak ota for a specific firmware - see dev section

TheFixItMan said:
Oreo firmware images have not been leaked/released - only the soak ota for a specific firmware - see dev section
Click to expand...
Click to collapse
OK so, I have to flash latest offcial stock and apply update oreo then???

TheFixItMan said:
Oreo firmware images have not been leaked/released - only the soak ota for a specific firmware - see dev section
Click to expand...
Click to collapse
Do you know what is the lastest flashable firmware for moto g5 cedric 32gb 2ram xt1670 NPP25.137.72????
That will allow me to upgrade Oreo????

CEDRIC_NPPS25.137-93-2-5_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml

Can't turn on moto g4 plus

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.

Unlocked bootloader and OTA updates

Will i recive OTA update if i unlock the bootloader?

Androidtroll said:
Will i recive OTA update if i unlock the bootloader?
Click to expand...
Click to collapse
Yes. Just unlocking the bootloader still allows everything to work normally, though you can't install otas if you mounted or modified /system and /oem partitions, or have twrp recovery.
Otherwise your phone should still function as if it weren't unlocked.

In addition to the above reply - if you do modify your system and want to flash back to stock firmware, please check if you can download the correct firmware for your device. I see from your history you have a retEU device, so the latest series of firmwares would be the NPNS25.137-93 series (with NPNS25.137-93-10 being the April 2018 security patch). I'd suggest checking to see if there is a stock ROM matching your current build before you unlock the bootloader (either at https://mirrors.lolinet.com/firmware/moto/potter/official/RETAIL/ or https://firmware.center/firmware/Motorola/Moto G5 Plus/Stock/ or https://androidfilehost.com/?a=show&w=files&flid=171014 ) though it seems the latest firmware that's been leaked is NPNS25.137-93-4 (the Jan 2018 security patch build). Just as a headsup, firmware.center has a cryptominer that could keep your CPU at 100 % if you have their page open.
If you download and flash the NPNS25.137-92-10 firmware, which is the April 2018 security patch for Brazil/India devices, you may be able to re-lock your bootloader and get back to full stock, but you may not be able to receive OTA updates (as the NPNS25.137-92 series of updates do not appear to be deployed to the retEU channel), so be careful which firmware you flash.
You can still unlock your bootloader without having the latest firmware to hand, but until the firmware matching your stock firmware before you unlocked or newer is available, you may not be able to re-lock your device. You may be able to flash older stock firmware for EU devices, but please do not use OTA updates if you flash older stock firmware, else you may hard brick your device.
Good luck whichever way you decide.

bazinga137 said:
Yes. Just unlocking the bootloader still allows everything to work normally, though you can't install otas if you mounted or modified /system and /oem partitions, or have twrp recovery.
Otherwise, your phone should still function as if it weren't unlocked.
Click to expand...
Click to collapse
Yes the Same thing Happened
I had TWRP recovery and I installed the Security Patch
my Phone Stuck at TWRP
but it has One solution
First, take the data backup of all in twrp at your sd card
now install any custom Rom
Reboot your device and check the rom is working or not
do reboot and go back to your Twrp and Restore the backup
I tested it and It worked perfectly

echo92 said:
In addition to the above reply - if you do modify your system and want to flash back to stock firmware, please check if you can download the correct firmware for your device. I see from your history you have a retEU device, so the latest series of firmwares would be the NPNS25.137-93 series (with NPNS25.137-93-10 being the April 2018 security patch). I'd suggest checking to see if there is a stock ROM matching your current build before you unlock the bootloader (either at https://mirrors.lolinet.com/firmware/moto/potter/official/RETAIL/ or https://firmware.center/firmware/Motorola/Moto G5 Plus/Stock/ or https://androidfilehost.com/?a=show&w=files&flid=171014 ) though it seems the latest firmware that's been leaked is NPNS25.137-93-4 (the Jan 2018 security patch build). Just as a headsup, firmware.center has a cryptominer that could keep your CPU at 100 % if you have their page open.
If you download and flash the NPNS25.137-92-10 firmware, which is the April 2018 security patch for Brazil/India devices, you may be able to re-lock your bootloader and get back to full stock, but you may not be able to receive OTA updates (as the NPNS25.137-92 series of updates do not appear to be deployed to the retEU channel), so be careful which firmware you flash.
You can still unlock your bootloader without having the latest firmware to hand, but until the firmware matching your stock firmware before you unlocked or newer is available, you may not be able to re-lock your device. You may be able to flash older stock firmware for EU devices, but please do not use OTA updates if you flash older stock firmware, else you may hard brick your device.
Good luck whichever way you decide.
Click to expand...
Click to collapse
I would unlock the bootloader just to try to fix the camera (then edit the system files), not for flash twrp / custom rom

Androidtroll said:
I would unlock the bootloader just to try to fix the camera (then edit the system files), not for flash twrp / custom rom
Click to expand...
Click to collapse
Just unlocking the BL wouldn't be enough to edit system files. You'll need root privileges to do so and for that you will have to flash/boot TWRP to install a root app like magisk.
So all the useful information @echo92 posted above is significant for you.
Sent from my Moto G5 Plus using XDA Labs

Is there a way to take TWRP off or disable to still grab the security patches? Or is clean install/backup (like Rutambh mentioned) the only option? The reason I ask I needed TWRP to install camera mod, so it would be nice to still get those OTA's. I tried to just fastboot boot TWRP but it would just hang at it's logo. Flash was only option.

Frawgg said:
Is there a way to take TWRP off or disable to still grab the security patches? Or is clean install/backup (like Rutambh mentioned) the only option? The reason I ask I needed TWRP to install camera mod, so it would be nice to still get those OTA's. I tried to just fastboot boot TWRP but it would just hang at it's logo. Flash was only option.
Click to expand...
Click to collapse
If anything in /system or /oem is tampered like installing a camera mod (or just mounting system r/w) the only way to receive future OTA updates is flashing your current ROM incl. stock recovery via fastboot.
Sent from my Moto G5 Plus using XDA Labs

Help. phone dead

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