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 reinstalled the stock os .. unrooted .. And booted up my phone .. everything works perfectly ..but when I tried to update from December to Feb security update ..the phone got hard bricked ...I did the blank flash and got it working ...I didn't try to update again ...so I don't know whether I should update to September update or not .. someone please help
First thing, Motorola does NOT support downgrading. What you did was you flashed the December update over some custom ROM you were using which in turn downgraded your bootloader and gpt partitions. Then you took OTA again which bricked your device.
You should always make sure that when you flash the stock ROM, you only flash the latest version available on XDA, in this case the June security update(NPJS25.93-14-8).
In case you flash any previous build of stock ROM DON'T flash the bootloader and gpt partitions (just ignore those two fastboot commands).
So what should you do now?
The link to the June security update full fastboot ROM : https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
Flash this one using the scripts provided. Then take the September OTA. Things should go fine now if you follow the steps carefully.
Swapnanil said:
First thing, Motorola does NOT support downgrading. What you did was you flashed the December update over some custom ROM you were using which in turn downgraded your bootloader and gpt partitions. Then you took OTA again which bricked your device.
You should always make sure that when you flash the stock ROM, you only flash the latest version available on XDA, in this case the June security update(NPJS25.93-14-8).
In case you flash any previous build of stock ROM DON'T flash the bootloader and gpt partitions (just ignore those two fastboot commands).
So what should you do now?
The link to the June security update full fastboot ROM : https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
Flash this one using the scripts provided. Then take the September OTA. Things should go fine now if you follow the steps carefully.
Click to expand...
Click to collapse
Thank you soo much ...I'll try this ?
I'd like to add a correction to what's been mentioned so far.
I agree that you likely hard bricked from flashing an older stock ROM than what you had on your device already. However, the act of downgrading your device may not cause a brick, but by downgrading you may not be able to flash an older GPT/bootloader as they detect a 'security version downgrade' and block you from flashing the older versions of the GPT/bootloader. However, as you were able to flash the system side of the firmware, then you'd have the mismatch of a newer bootloader (likely B1:06 from the June 2017 stock update?) and an older system from the December 2016 patch.
Now, when you accepted and downloaded the OTA, the OTA assumed that your device is fully patched to the December 2016 security level and was all on the same patch level, which by downgrading your device was not. OTAs appear to check if your system and OEM and other partitions are of the expected patch level and do not necessarily verify that your GPT and bootloader are matching too. Thus, when it attempted patching to upgrade your device to the March 2017 patch, it applied updates to your bootloader and thus corrupted your newer bootloader, leading to a hard brick.
That's a reason why downgrading and updating by OTA updates is so risky now. Therefore, if you've downgraded, do not update via OTA.
I agree with the suggestion that you should use the full fastboot ROM, (you may wish to omit the 'erase userdata' command) to ensure your device is fully flashed to the same patch level. We've now got the September 2017 fastboot ROM to flash too if you're unsure about taking OTA updates.
In future, verify what stock firmware you had on your device before you flashed a custom ROM, and ensure you flash the firmware of the same patch level.
echo92 said:
I'd like to add a correction to what's been mentioned so far.
I agree that you likely hard bricked from flashing an older stock ROM than what you had on your device already. However, the act of downgrading your device may not cause a brick, but by downgrading you may not be able to flash an older GPT/bootloader as they detect a 'security version downgrade' and block you from flashing the older versions of the GPT/bootloader. However, as you were able to flash the system side of the firmware, then you'd have the mismatch of a newer bootloader (likely B1:06 from the June 2017 stock update?) and an older system from the December 2016 patch.
Now, when you accepted and downloaded the OTA, the OTA assumed that your device is fully patched to the December 2016 security level and was all on the same patch level, which by downgrading your device was not. OTAs appear to check if your system and OEM and other partitions are of the expected patch level and do not necessarily verify that your GPT and bootloader are matching too. Thus, when it attempted patching to upgrade your device to the March 2017 patch, it applied updates to your bootloader and thus corrupted your newer bootloader, leading to a hard brick.
That's a reason why downgrading and updating by OTA updates is so risky now. Therefore, if you've downgraded, do not update via OTA.
I agree with the suggestion that you should use the full fastboot ROM, (you may wish to omit the 'erase userdata' command) to ensure your device is fully flashed to the same patch level. We've now got the September 2017 fastboot ROM to flash too if you're unsure about taking OTA updates.
In future, verify what stock firmware you had on your device before you flashed a custom ROM, and ensure you flash the firmware of the same patch level.
Click to expand...
Click to collapse
Thank you for your help !!!!!!!
Does anyone have and/or able to post the most recent factory images for the XT1575? Given my phone previously received an OTA update to NPH25.200-23 (November 2017), I cannot use the NPH25.200-22 images posted here to flash my phone (or lock the bootloader). My understanding is that is not possible to downgrade to the Android 6.0 firmware after this OTA update or to a lower build number either.
I believe a large number of users should have received the OTA to NPH25.200-23, if anyone has the stock image for this build I would really appreciate it. As of now I am unable to restore my phone or lock my bootloader, flashing to NPH25_200-22 fails. Really appreciate any help, sure regret accepting the OTA update to NPH25.200-23. I received a warranty replacement from Motorola that was still running Marshmallow, and as soon as I fired it up it presented the OTA update to NPH25.200-23 (not NPH25.200-22), and shortly thereafter a security patch to October 2017. At this point I decided to unlock the bootloader and play with customer roms which was bad move, as none of the custom roms support the Nougat firmware on the XT1575, and all the ones I tried loaded would result in a boot loop. I couldn't find any mention of this constraint on the LineageOS or AICP websites, if only I had known!
Pretty sure my only options are to flash a factory image of build NPH25.200-23 or wait for the custom roms to support the more recent firmware. Any other suggestion would be appreciated. Really hoping someone has the NPH25.200-23 factory image.
You can't relock BL(maybe in future).
But
You can flash(Asia, LA, US, dd EU) any stock Nougat and ota's will be installed succesfully.
What fails when you flash .22? gpt.bin .. bootloader... a sparsechunk? BTW good luck getting the .23. Was surprised to even get the .22 firmware.
BL, GPT always fail if lower version.
dzidexx said:
BL, GPT always fail if lower version.
Click to expand...
Click to collapse
Not true. Downgraded from nougat .201.1 to .22 only thing failed was gpt.bin. So if that was the only thing that failed when he did the .22 flash from .23 then replace the gpt.bin. But if also the bootloader then hes screwed till firmware is available.
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