Help regarding flashing stock and ota - Moto G5 Plus Questions & Answers

Hello!
I've the Indian variant of the Moto G5 Plus (XT1686), software channel: Retin. I have unlocked the device and flashed a custom ROM. I want to return to stock now but I have a few questions.
1) Where can I get the latest factory image for my XT1686?
2) Which one should I flash on my device amongst AMZ, RETLA & RETAIL?
3) I was on the November security patch before I unlocked and rooted. Should I flash stock, will my device continue receiving ota updates that are released for India?
4) If I flash the firmware that you guys will link me to here, will it hard brick my device when I try for ota update in the future? I read somewhere about mismatch in the partition table will lead to 9008/ some error and device won't go in bootloader mode and that you'll need blankfiles to revive your device and stuff.
Please tell me what to do to return to my complete stock image and to continue receiving ota updates safely on my XT1686, RETIN Software Channel?

1) To the best of my knowledge, this NPN25.137-92, Nov 2017 stock Motorola firmware, is the latest for retIN (retail India) devices, amongst other regions. https://forum.xda-developers.com/g5-plus/how-to/moto-g5-plus-patch-november-npn25-137-92-t3718976 It's been received by OTA to users, indicating it's been formally deployed in India and other regions too. Please verify this before flashing
Flash using the flashing instructions provided in this post: https://forum.xda-developers.com/g5-plus/how-to/solution-to-flash-stock-romfactory-t3691396 but using the above NPN25.137-92 ROM - the flashing instructions should apply to this ROM.
2)As you're on retail India, you want retail stock ROMs. AMZ are only for Amazon Prime devices (bootloader locked to Amazon, adverts on the lockscreen) and whilst you could flash retla (retail Latin America), it may cause problems for your device later down the line.
3)Provided you flash the correct stock firmware for your region, you should continue to receive OTA updates.
4)As this should be the same firmware as you had previously, you should not hard brick when receiving OTA updates in the future. Users appeared to commonly hard brick when they attempted to flash stock Motorola firmware older than the stock firmware they had (custom ROMs don't appear to matter here), then attempted to use OTA updates. You cannot downgrade bootloaders, thus you have a mismatched bootloader and system - your new bootloader and your downgraded system - so using an OTA update would flash older bootloader files. As OTA updates do not have the same checks as fastboot for bootloaders, that would corrupt your newer bootloader and hard brick your device. The OTA updates don't appear designed to consider downgraded devices, i.e. newer bootloaders but older stock systems, hence why Motorola likely warns you that whatever happens when unlocking the bootloader is the user's responsibility. If you were in that situation, then flashing fastboot ROMs would be the safest way to update.
However, as you're being conscientious enough to flash the same or latest firmware, then this should not occur. To summarise, hard bricks only appear to occur when downgrading/cross flashing stock firmware and then taking OTA updates when you previously had newer/different stock firmware on your device.
If you want to be truly sure this is the right firmware to revert back to stock to, then I would like to see your getvar info before proceeding:
1)Boot your device to the bootloader, connect to your computer via USB.
2)In the ADB terminal, type 'fastboot getvar all' without quotes and press Enter.
3)Copy the output to a post here. This output contains device variables including what the last stock firmware was on your device, which will be helpful in verifying the correct firmware for you. You may wish to remove IMEI from the output before posting.

Guys i unlocked the bootloader of NPN 25.137-92 indian retin variant with nov 1 patch. I unlocked the bootloader and rooted the phone with SU, only problem is that cam stops working. Then i installed Elemental X kernel 2.02 as a workround to get the cam working which went ok . But i want to go back to the stock kernel, i dont want to flash whole rom . Is their a way i get info or download link for the stock kernel, please reply. Is it possible that i can just flash the kernel.

Stifmeister11 said:
Guys i unlocked the bootloader of NPN 25.137-92 indian retin variant with nov 1 patch. I unlocked the bootloader and rooted the phone with SU, only problem is that cam stops working. Then i installed Elemental X kernel 2.02 as a workround to get the cam working which went ok . But i want to go back to the stock kernel, i dont want to flash whole rom . Is their a way i get info or download link for the stock kernel, please reply. Is it possible that i can just flash the kernel.
Click to expand...
Click to collapse
Answered on your post, please check

Related

Still waiting for OTA MM update

Hello,
I have an XT1562 single-SIM. I unlocked and rooted the device using TWRP 2.8.7-v2 and SuperSU 2.46.
Since I read rumours that this will prevent the OTA MM update I would like to update by flashing the new firmware.
This forum is a great source of information, but that information is scattered all over the place. I have read dozens of topics and hundreds of posts, and still have some questions . I hop this post will lead to the answers...
Do I need to upgrade TWRP to 3.0.0-r2 before upgrading the firmware?
Do I have to uninstall SuperSU first?
Can I skip the fastboot erase userdata step?
Will flashing bootloader and image re-lock the bootloader?
If I want to keep using TWRP, do I need to skip the fastboot flash recovery recovery.img step?
Thanks,
GeWe
Just wanted to get some extra information that may assist others in replying to this thread my good friend.
What version of software are you running? (Brazil Retail, Europe retail, Asia retail, Canada retail, USA or a Carrier branded version)
I will attempt to answer your questions as best I can.
1. I don't believe you need to upgrade to TWRP 3 to receive a MM version. I am running 2.8.7.0 IIRC and am running MM just fine.
2. You need to be completely stock to receive an OTA update. ie, no custom recovery and completely stock firmware. In Fastboot it should say "Stock" next to "Software Status" instead of "Modified"
3. You can when flashing original stock firmware, I don't recommend it though as I have had bootloops in the past. Best to backup and completely start fresh.
4. You don't need to relock the bootloader. I did this on a Moto G and then had to get the unlock code again to go back to custom. It doesn't completely relock anyway, it still says Status 3 I believe and shows the bootloader unlocked warning.
5. Again, best to flash completely stock then flash TWRP recovery.
All that being said, your best bet is to use the Stock backups in TWRP and restore from them. I used the Canadian one and am running TWRP with Canada firmware and haven't looked back. I will get you the link shortly.
Edit: this is the link. I used the Canada firmware in this thread and restored on my phone. Works great.
http://forum.xda-developers.com/showthread.php?t=3272979
Sent from my XT1563 using Tapatalk
Sorry, I forgot to mention the software version. Apart from the recovery it is running the stock ROM, Android 5.1.1, European retail verion. (Baseband version is M8936_2020613.22.03.21.33R LUX_EMEA_CUST.)
After some more searching I found another thread that contained a link to the reteu OTA file. I followed the instructions there and now I have 6.0 running.

After flashing phone changed from G4 Plus to G4

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

Not receiving system updates

Hello everyone, I stumbled upon this problem but I can't find much useful information to solve this: I rooted my Moto G4 Plus and after some time I decided to unroot and I flashed stock rom in it with unlocked bootloader. After that I'm stuck at Marshmallow and can't receive Nougat update. Everything was fine before I rooted and flashed stock rom in it with unlocked bootloader but now it doesn't seem to update. My model number is XT1642. How can I solve this problem and receive OTA updates? I also want to relock my bootloader. So to sum it all up: I want my device to be just as after I bought so to speak.
Depending on what Marshmallow ROM you flashed, it might have not been the correct version for your software channel, and thus your device won't have received an OTA (since the server is expecting a different build to the one you have).
If you wish to update to Nougat and re-lock your bootloader, you may wish to flash the June 2017 fastboot ROM, which should also re-lock your bootloader if you use the commands mentioned. Be aware that re-locking your device may wipe your data, back up and keep your data off your device until you're done.
https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 for the June fastboot ROM. If at a later date you choose to unlock your bootloader again, do not downgrade your device to an older stock ROM from the June update.

Custom ROMs and future updates. What do I have to bear in mind?

So, we all know Motorola will eventually (aka never) release Oreo for the G5 Plus.
I am way too anxious so I am going to flash a Custom ROM until they deliver it. However I am quite afraid about something.
I plan to use Lineage 15.1 until Oreo comes out for the G5 Plus. However, I am kind of afraid that I may screw things up when the OTA comes out.
I have recently hard bricked my Moto G 2014 because of OTAs and Bootloader.
So, Oreo releases...
Will it be fine to install the OTA (through normal System Update check) having the latest Stock ROM Firmware for my region installed? (I would erase Lineage 15 and use fastboot to flash Stock again)
Or will I instead need to wait for someone to post the system images and flash it through fastboot instead? (I assume I would need to install the OTA through normal methods because of bootloader changes but still...)
I just don't want this: https://forum.xda-developers.com/g5-plus/help/moto-g5-plus-hard-bricked-t3694119
To happen.
You won't get system updates when you are on a custom ROM like Lineage OS or any other custom ROM. The only system updates you might get are ROM updates if the ROM maintainer has that feature built in.
If official Oreo comes out and you are on the correct stock firmware for your model and region, everything should work fine.
Before flashing custom roms you should backup your efs partition using twrp else you could lose your imei(recoverable) / volte(not recoverable till now) when flashing fastboot firmwire.
You need to flash fastboot firmwire to receive oreo ota.
If you want to avoid hard bricking, then you must flash the same stock ROM or newer onto your device when you revert back to stock firmware.
I imagine your Moto G 2014 got bricked when you took an OTA update? That could have occurred if firmware older than what was present on your device was flashed (bootloaders cannot be downgraded), and like in that thread you linked, attempting to use OTA updates would corrupt your newer bootloader with the older OTA patches, leading to a hard brick.
As mentioned above, if you revert to the correct build for your region and matching your current build at least, you should be okay to receive OTA updates (should also include up to Oreo). Alternatively, you could wait for the Oreo fastboot ROM to be safe, or the Oreo TWRP flashable for a near stock ROM experience (since TWRP flashables shouldn't care about your bootloader or GPT partitions, do it'd be difficult to brick your device. However, TWRP flashable stock ROMs aren't OTA compatible).
Before you unlock your bootloader and flash TWRP/custom ROMs, make a note of your current build version and see if you can find a stock ROM leaked of that build, so you can be sure that you're reverting to the right build for your device.
Just do not flash older stock Motorola firmware to your device or if you do, do not use OTA updates.
Yeah, I did some research and now I understand what happened. Thanks for the comments.

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

Categories

Resources