Moto g5 plus stock ROM - Moto G5 Plus Questions & Answers

I'm having Moto g5 plus Indian variant xt1686. I have installed a custom ROM Resurrection remix and I'm currently running it.I want to get back to stock rom. I went through many existing threads only to get myself confused. I want you guys to help me get back to stock ROM so that I can get OTA updates.
1. I have working volte and IMEI till now. I didn't take back-up of persist or efs as I was lacking knowledge. Can I take back-up of those now for going back to stock. If yes then suggest how?
2. I don't remember my build number from which I unlocked my bootloader. Should I lock the bootloader again to get OTA? If not then please suggest any way to get back to stock whether Oreo or nougat (get updates to Oreo then).

kash664 said:
I'm having Moto g5 plus Indian variant xt1686. I have installed a custom ROM Resurrection remix and I'm currently running it.I want to get back to stock rom. I went through many existing threads only to get myself confused. I want you guys to help me get back to stock ROM so that I can get OTA updates.
1. I have working volte and IMEI till now. I didn't take back-up of persist or efs as I was lacking knowledge. Can I take back-up of those now for going back to stock. If yes then suggest how?
2. I don't remember my build number from which I unlocked my bootloader. Should I lock the bootloader again to get OTA? If not then please suggest any way to get back to stock whether Oreo or nougat (get updates to Oreo then).
Click to expand...
Click to collapse
From what I believe, you should definitely backup your EFS and Persist right now while it's all good.
If you don't remember your last stock build number, it is safe to use the latest build for your region.
Once you flash a fastboot ROM and everything's good to go, there's absolutely no need to relock bootloader as the script in the OTA only checks for system modifications and if it finds any on your phone, the OTA will not be applied and the update will eventually fail. To ensure that you are able to apply OTAs without any hassle, I recommend you don't do ANY system modifications like root or camera mods or similar. Stick with the core OS and you'll be good to go.
You can alternatively use TWRP flashable ROMs by @NZedPred, they're like a newbie-proof solution to getting to stock ROM from virtually any ROM without losing any functionality as they only flash the OS part of the ROM and rarely do any changes to the HW functionality of the ROM like Radios and Sensors. If all else fails, you can always flash a TWRP flashable stock and be ready to go.
Or
You could simply download the Oreo fastboot ROM with the August security patch which is available at the moment but isn't the latest one as the latest October security patch rolled out to RETIN devices just a few days ago so I doubt that the full fastboot ROM would be available this early. But then again, if you flash the Oreo August patch, you can take the OTA to October patch and be just fine.
Note:
But a bit of advice, if you're planning to go back to Nougat using a Nougat fastboot ROM, I'd highly recommend the TWRP flashable as one can mess stuff up while trying to downgrade using a fastboot ROM as Moto phones have problems downgrading. It's all about these two partitions called "gpt" and "bootloader" which when not paying attention to while flashing can cause a hard-brick.
A safer approach would be to skip these two partitions while using a fastboot ROM to downgrade but I'd be honest and would suggest you to wait to be sure this would work as I myself haven't tried this while downgrading from one Android version to another as Oreo bought with itself some Modem and a few other changes in partitions as compared to Nougat.
If I were you, I would wait for some to confirm the part in the "Note" just to be absolutely sure that it'd work.

Thanks for the response
Thanks for your response.
I'll be going with your suggestion and flash the twrp flashable oreo.

psychopac said:
From what I believe, you should definitely backup your EFS and Persist right now while it's all good.
If you don't remember your last stock build number, it is safe to use the latest build for your region.
Once you flash a fastboot ROM and everything's good to go, there's absolutely no need to relock bootloader as the script in the OTA only checks for system modifications and if it finds any on your phone, the OTA will not be applied and the update will eventually fail. To ensure that you are able to apply OTAs without any hassle, I recommend you don't do ANY system modifications like root or camera mods or similar. Stick with the core OS and you'll be good to go.
You can alternatively use TWRP flashable ROMs by @NZedPred, they're like a newbie-proof solution to getting to stock ROM from virtually any ROM without losing any functionality as they only flash the OS part of the ROM and rarely do any changes to the HW functionality of the ROM like Radios and Sensors. If all else fails, you can always flash a TWRP flashable stock and be ready to go.
Or
You could simply download the Oreo fastboot ROM with the August security patch which is available at the moment but isn't the latest one as the latest October security patch rolled out to RETIN devices just a few days ago so I doubt that the full fastboot ROM would be available this early. But then again, if you flash the Oreo August patch, you can take the OTA to October patch and be just fine.
Note:
But a bit of advice, if you're planning to go back to Nougat using a Nougat fastboot ROM, I'd highly recommend the TWRP flashable as one can mess stuff up while trying to downgrade using a fastboot ROM as Moto phones have problems downgrading. It's all about these two partitions called "gpt" and "bootloader" which when not paying attention to while flashing can cause a hard-brick.
A safer approach would be to skip these two partitions while using a fastboot ROM to downgrade but I'd be honest and would suggest you to wait to be sure this would work as I myself haven't tried this while downgrading from one Android version to another as Oreo bought with itself some Modem and a few other changes in partitions as compared to Nougat.
If I were you, I would wait for some to confirm the part in the "Note" just to be absolutely sure that it'd work.
Click to expand...
Click to collapse
Thanks for your response.
I'll be going with your suggestion and flash the twrp flashable oreo.

kash664 said:
Thanks for your response.
I'll be going with your suggestion and flash the twrp flashable oreo.
Click to expand...
Click to collapse
Make sure to follow the flashing instructions mentioned by the thread OP properly

psychopac said:
Make sure to follow the flashing instructions mentioned by the thread OP properly
Click to expand...
Click to collapse
Yes. Hope everything turns out fine

kash664 said:
I'm having Moto g5 plus Indian variant xt1686. I have installed a custom ROM Resurrection remix and I'm currently running it.I want to get back to stock rom. I went through many existing threads only to get myself confused. I want you guys to help me get back to stock ROM so that I can get OTA updates.
1. I have working volte and IMEI till now. I didn't take back-up of persist or efs as I was lacking knowledge. Can I take back-up of those now for going back to stock. If yes then suggest how?
2. I don't remember my build number from which I unlocked my bootloader. Should I lock the bootloader again to get OTA? If not then please suggest any way to get back to stock whether Oreo or nougat (get updates to Oreo then).
Click to expand...
Click to collapse
I hope i can help !!

vishalrickz said:
I hope i can help !!
Click to expand...
Click to collapse
Sure sir

Related

HELP, Can I downgrade to Stock Marshmallow and Upgrade to Nougat?

Hello,
Can I downgrade completly with the bootloader on Marshmallow and then upgrade to Nougat?
I want to lock my bootloader.
My G2 bricked after doing this. But I don't know if this would happen to my G4 Plus again
inFiniTyz_Z said:
Hello,
Can I downgrade completly with the bootloader on Marshmallow and then upgrade to Nougat?
I want to lock my bootloader.
My G2 bricked after doing this. But I don't know if this would happen to my G4 Plus again
Click to expand...
Click to collapse
If you wish to simply re-lock your bootloader, the easiest thing is to flash this fastboot stock ROM (which is Nougat) and use the locking script as directed in the first post. https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369 Of course, this may wipe your data - so back up, and the relocking may or may not work, in which case you may have to wait for a more up to date fastboot stock ROM to become available.
If you were to downgrade to Marshmallow, you cannot downgrade your bootloader and GPT partitions, at best, your existing bootloader would try to prevent you from downgrading those partitions. At worst, you'll brick your device again if you were to flash those - though we've got possible ways of fixing that, it's not a route I'd want to go down. Flashing the rest of Marshmallow is no problem, however, ensure you have the correct MM firmware for your device and territory.
Will this version work for my country(Germany) without OTA trouble?
inFiniTyz_Z said:
Will this version work for my country(Germany) without OTA trouble?
Click to expand...
Click to collapse
Should be okay to flash - the 93-14 build appears to be the global build that was deployed by Motorola, and should be eligible for the 93-14.4 (March 2017 security update) whenever that arrives in the EU/UK I've flashed the stock ROM onto my XT1642 several times without issue.
echo92 said:
Should be okay to flash - the 93-14 build appears to be the global build that was deployed by Motorola, and should be eligible for the 93-14.4 (March 2017 security update) whenever that arrives in the EU/UK I've flashed the stock ROM onto my XT1642 several times without issue.
Click to expand...
Click to collapse
THANK YOU IT WORKED AND THE WARNING DISAPPEARED. I am on Nougat, locked and its working like a charm
I WOULD KISS YOUR BUTT IF ITS HAVE TO BE

Unlocked Amazon XT1625 to retail firmware?

So, I have a 32gb Amazon-variant XT1625 on MPJ24.139-48 with an unlocked bootloader and root. I want to update to Nougat, but it's looking like setting up to take the Amazon update is going to be a fair amount of effort; I'm wondering if it's possible to just flash the retail version of Nougat since it's looking like I'm going to have to go to a fair sum of effort anyway.
I've also heard that Moto G4 Plus ROMs will work on the G4, but I don't know the specifics on that.
i dont see why not as long as you already unlocked the bootloader prior to Moto(Lenovo) disallowed unlocking of amazon varients of the g4. heres a link to the stock nougat firmware
https://androidfilehost.com/?fid=673368273298955218
I flashed -64 retus software on mine and it immediately had two nougat updates afterwards. Still waiting for one that fixes the aboot sector vulnerability too but never know when that may come
Travisholt92 said:
I flashed -64 retus software on mine and it immediately had two nougat updates afterwards. Still waiting for one that fixes the aboot sector vulnerability too but never know when that may come
Click to expand...
Click to collapse
then you was able to flash retail version in a amazon prime phone? I have one and it dont boot if i instal a retail version.
di anybody actually get this working? I had the same issue as @iurd2007 I was able to unlock the bootloader just fine. The flash appeared to have taken successfully. But it just gets caught in a boot loop when trying to reboot the system after the flash. I followed the instructions here:
https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
okay, so i've tried various roms both official and unofficial, as well as even the stock Nougat and Oreo flashable roms found here:
https://forum.xda-developers.com/moto-g4-plus/development/rom-oreo-8-1-0-soak-test-t3873367
So far, the only ROM i've been able to get installed is omni rom 9, but it keeps crashing several apps over and over on the setup wizard. I've read somewhere that using a different version of TWRP recovery image might help. I've tried the official TWRP recovery from twrp.me, the patched arm64 version found here: https://sourceforge.net/projects/tw...3-r1-athene-arm64_rajatgupta1998.img/download , also the latest version patched for efs backup/restore here: https://forum.xda-developers.com/devdb/project/?id=29106#downloads. So far the the one that seems to work the best is the third version of TWRP. It would be nice if all these custom patches made it back into an official release, but it's probably asking a lot of a phone that is almost 4 years old at this point. and a budget friendly phone at that.

Confused Noob+H990DS - Unlock/Root+TWRP Official Custom ROM possible (W/ 2. Screen)?

hi folks!
I am pretty confused now. I am looking to get the V20 H990DS, but i am more confused now after reading here. My questions:
1. Is Bootloader unlock possible?
2. Can i install TWRP?
3. Can i root?
4. There is LOS official i know, but is the problem with 2. screen now fixed / going to be fixed?
Seems so good of a device, but i am insecure about it now after reading here. My old Mi4/Cancro is one of the best supported phones out there, so i dont expect it to be the same with V20, but i need working LOS with Root and working 2. screen (or the outlook on it working in the future) to be confident in buying it.
I hope you forgive me my nood questions,
Greetings
With sadly no replys, let me add what i know now:
1. + 2. + 3. Still no easy way in sight AFAIK. EDIT: To be clear: There IS a way, Dirty Santa, but the instructions are somewhat too complicated to be confident with trying. Have had rooted Phones with custom ROMs since over 5 years and never again a stock device, but i dont dare it. The 300€ i payed are much to much to have spend it on a bricked device. Will try to find more dirty Santa noob friendly explanations and post them here. EDIT2: For those who DO dare it, here the thread: https://forum.xda-developers.com/v20/development/dirtysanta-h990-t3624296
4. Second screen still a problem, nothing new heard for quite a long time.
Anyone with knowledge to add or correct, please help! Stock ROM is not as bad as i thought, but without Root, Android is not fully usable for me.
thank you pro for this thread
very useful for me.
Stele88 said:
With sadly no replys, let me add what i know now:
1. + 2. + 3. Still no easy way in sight AFAIK. EDIT: To be clear: There IS a way, Dirty Santa, but the instructions are somewhat too complicated to be confident with trying. Have had rooted Phones with custom ROMs since over 5 years and never again a stock device, but i dont dare it. The 300€ i payed are much to much to have spend it on a bricked device. Will try to find more dirty Santa noob friendly explanations and post them here. EDIT2: For those who DO dare it, here the thread: https://forum.xda-developers.com/v20/development/dirtysanta-h990-t3624296
4. Second screen still a problem, nothing new heard for quite a long time.
Anyone with knowledge to add or correct, please help! Stock ROM is not as bad as i thought, but without Root, Android is not fully usable for me.
Click to expand...
Click to collapse
i dont get about your complain. you said already using phone with root for 5 years so i guess you've been here on xda for a while. if you really want a phone which support custom rom go with phone which support unlock bootloader like HTC, Oneplus, or even xiaomy. its not that hard finding them on XDA. 300euro for briked devices? well, if you read v20 section carefully you knew most people here bought this devices for the camera, audio, and other things like removable battery, etc. i never found someone who bricked their devices while rooting here, even if they do we already had flasher tools like LG up which already tested fully working by some members. and whats the problem with second screen? its working for whatever it made for. are you expecting to watch movie on those 2.1 inch display? i had lg v20 h990ds rooted with magisk and had no problem so far. bought some apps like grenify and titanium backup for debloated and my phone rocking solid for abouth 2 month. if you cant wait for LOS just bought lenovo zuk2 or oneplus 3t on the same price range.
No problem doing 1+2+3 with DirtySanta exploit/procedure. It's not as complicated or dangerous as it might seem from the instructions. I thought I had soft-bricked my phone twice after rebooting normally with the old kernel instead of straight to TWRP to update the kernel first, but it was easy to re-flash the 10d factory firmware file I had and start over again without any issues both times.
Basic summary of procedure:
1. Flash factory firmware version earlier than 31 December 2016 (only needed if installed firmware version is after 1 January 2017).
2. Do DirtySanta exploit to unlock bootloader and install TWRP and root.
3. Use kdzwriter to update phone's system/modem/cust partitions to latest firmware version without overwriting unlocked bootloader/TWRP, reinstall root (SuperSU or Magisk) from TWRP.
4. Disable automatic OTA updates so that any future firmwares won't automatically install and overwrite bootloader/recovery and remove root and set ARB 1. If that ever happens then TWRP/root will probably be gone forever.
provided you follow the instructions carefully, it's safe to root with DirtySanta.
xoose said:
No problem doing 1+2+3 with DirtySanta exploit/procedure. It's not as complicated or dangerous as it might seem from the instructions. I thought I had soft-bricked my phone twice after rebooting normally with the old kernel instead of straight to TWRP to update the kernel first, but it was easy to re-flash the 10d factory firmware file I had and start over again without any issues both times.
Basic summary of procedure:
1. Flash factory firmware version earlier than 31 December 2016 (only needed if installed firmware version is after 1 January 2017).
2. Do DirtySanta exploit to unlock bootloader and install TWRP and root.
3. Use kdzwriter to update phone's system/modem/cust partitions to latest firmware version without overwriting unlocked bootloader/TWRP, reinstall root (SuperSU or Magisk) from TWRP.
4. Disable automatic OTA updates so that any future firmwares won't automatically install and overwrite bootloader/recovery and remove root and set ARB 1. If that ever happens then TWRP/root will probably be gone forever.
Click to expand...
Click to collapse
Using the steps on #3, would it be safe to say that we can update the device to oreo and still keep root?
nurse_chuck said:
Using the steps on #3, would it be safe to say that we can update the device to oreo and still keep root?
Click to expand...
Click to collapse
No, right now if you update you'll lose root as the engineering aboot isn't compatible with Oreo and you have possibly non working data, invalid sim issues etc
Sent from my LG-H910 using XDA Labs
cnjax said:
No, right now if you update you'll lose root as the engineering aboot isn't compatible with Oreo and you have possibly non working data, invalid sim issues etc
Sent from my LG-H910 using XDA Labs
Click to expand...
Click to collapse
Too bad. Your earlier post actually got me excited. Hehe. Anyway, hopefully someones starts working on rooting the oreo firmware.
The short answer? @Stele88
Yes. To all of it.
The long answer starts with the Dirty Santa root process. Believe me, I was daunted by it as well, but as long as you follow it (or the noob version of the guide you can find by searching around the same section the original guide is in) and take your time, you'll be okay. It's what I did and I'm now where I am today.
I'll address a couple things since I have the same device as you. If you want to get your device working properly on LineageOS/ResurrectionRemix (LOS with more customisation) then it's a long process.
1. Start by following the bootloader unlock process for Dirty Santa. Depending on what firmware your device gets shipped with, you may need to downgrade to (in the case of the H990DS) the v10c firmware. Once done, then you can Dirty Santa the bootloader and get it unlocked.
2. Once that's done and you're rooted with the initial TWRP from the thread installed, you'll want to look into KDZWriter. It's a program by the same emdroidle who did the Dirty Santa process for us that allows you to update your STOCK system software to newer versions and keep root. You can use it for example with the H990DS firmware KDZ files and go from rooted 10c -> rooted 10f -> rooted 10xx -> etc. until you're on the latest available 7.0 KDZ for the H990DS. This will be the longest part of your process, but it ensures that everything is up to date before going to AOSP/Lineage/Resurrection, specifically the modem partition. I recommend using the TWN region of firmwares if you're just going to convert to a custom ROM anyway, but any region will work fine (the only real difference is that, for example, the Australia region of firmwares comes with more bloat than the TWN region).
2b. You can also use KDZWriter from an updated TWRP you can get in the thread by Phoenix591, his latest TWRP versions have KDZWriter built-in so you don't have to run it off the computer, you can do it all with the kdz files in recovery.
3. Yes, you can root using the Dirty Santa method on v10c kdz firmware. I recommend Magisk for root over SuperSU.
4. There's no official LineageOS that is as up to date as the unofficial ones, and there's no official ones with second screen enabled full stop. That being said, the unoffcial LineageOS 15.1 by x86cpu has been my rock solid daily driver for about 2 months now and I've never had any issues that stop me from using it. The same can be said for ResurrectionRemix 6.2 by Blaises. To use either of these, you will need the updated TWRP from Phoenix591.
4. Second-screen enabled builds of LineageOS and ResurrectionRemix do exist, and in this case ResurrectionRemix is (as of this post) more up-to-date than the LineageOS 15.1 second screen version. If you find yourself needing additional features that aren't in the stock kernels for those ROMs (such as KCAL configuration to help with burn in, among other things), then I maintain the second-screen version of the Gamma Kernel by Omar-Avelar. People are successfully using this with second-screen ROMs and have full functionality. You can purchase the app BoredSigns from the play-store to add additional functions to the second-screen.
As I said at the start, it is a long process, but a very worthwhile one. The jump from stock to custom-ROMs is absolutely incredible. Again, in short, yes. You can get everything you want.
Just do your searching around the forums for the processes I outlined above, ask any questions you have, pre-download your kdz firmwares from HERE and any software you need, and just take your time. It's maybe a couple hours to get setup with a rooted stock system that's up-to-date, and maybe another hour or so to go from stock to Lineage/Resurrection.
P.S: If all goes well with the Dirty Santa process, but you get screen distortion after rebooting when flashing the TWRP from Dirty Santa, just pull the battery instead of rebooting.
Good luck, good searching, and remember to not be afraid to ask questions in the relevant threads.
---------- Post added at 04:50 AM ---------- Previous post was at 04:49 AM ----------
nurse_chuck said:
Too bad. Your earlier post actually got me excited. Hehe. Anyway, hopefully someones starts working on rooting the oreo firmware.
Click to expand...
Click to collapse
It's highly doubtful this will happen, but one can hope. Right now the best way to get Oreo is through a custom ROM, purely because of how security is implemented by LG in the stock Oreo ROMs.
iDefalt said:
It's highly doubtful this will happen, but one can hope. Right now the best way to get Oreo is through a custom ROM, purely because of how security is implemented by LG in the stock Oreo ROMs.
Click to expand...
Click to collapse
Actually it is possible runningnak3d has already said awhile ago he has a process to root stock oreo he's just not releasing it yet so LG can't patch it before the Oreo roll out is complete
Sent from my LG-H910 using XDA Labs

J727P Spotted running Oreo!

The J727P has been certified by Wi-Fi Alliance running Oreo 8.0. If I can find the leaked firmware, I will post it here. If anyone else happens to track it down before me, please also post it here!
stock boot.img ?
Spaceminer said:
The J727P has been certified by Wi-Fi Alliance running Oreo 8.0. If I can find the leaked firmware, I will post it here. If anyone else happens to track it down before me, please also post it here!
Click to expand...
Click to collapse
Sounds good, one question thought, where is stock boot.img on j727p firmware for odin? BP,CSC,CP, or AP.
J727P
Spaceminer said:
The J727P has been certified by Wi-Fi Alliance running Oreo 8.0. If I can find the leaked firmware, I will post it here. If anyone else happens to track it down before me, please also post it here!
Click to expand...
Click to collapse
One question is this fore real ?
Yes I ask this because I was on stock firmware three days ago an I checked for the update an there wasn't one ! Maybe Verizon gets the update first I will check again in a day or two !
---------- Post added at 12:32 AM ---------- Previous post was at 12:00 AM ----------
lamike said:
Sounds good, one question thought, where is stock boot.img on j727p firmware for odin? BP,CSC,CP, or AP.
Click to expand...
Click to collapse
Boot img is in the AP file !!
peter couniaz said:
One question is this fore real ?
Yes I ask this because I was on stock firmware three days ago an I checked for the update an there wasn't one !
Click to expand...
Click to collapse
Yes. It's just not officially released yet. I've been scouring the web for a leak. This means Oreo has been built for our device already and the official release coming. If you're curious about WiFi Alliance, wikipedia has good information about them.
J737P
Spaceminer said:
Yes. It's just not officially released yet. I've been scouring the web for a leak. This means Oreo has been built for our device already and the official release coming. If you're curious about WiFi Alliance, wikipedia has good information about them.
Click to expand...
Click to collapse
Ok thank you an let me know if you find anything more about this !
peter couniaz said:
Ok thank you an let me know if you find anything more about this !
Click to expand...
Click to collapse
I managed to find the firmware, however, it's behind a pay wall on servers in Iran. The firmware name is J727PVPU4BRH5 if you want to help look for it. As soon as find it on a free server, I'll post an update.
J727P
Spaceminer said:
I managed to find the firmware, however, it's behind a pay wall on servers in Iran. The firmware name is J727PVPU4BRH5 if you want to help look for it. As soon as find it on a free server, I'll post an update.
Click to expand...
Click to collapse
Yes the 8.0 update is up for this phone I'm on stock firmware an I don't know if I will do the update until I see root for it ! I will let you what I decide !
J727P update
peter couniaz said:
Yes the 8.0 update is up for this phone I'm on stock firmware an I don't know if I will do the update until I see root for it ! I will let you what I decide !
Click to expand...
Click to collapse
I'm going to take the update to 8.0 an hope someone cames up with a Root process ! an it is the U4 bootloader so backdating the firmware should work if I don't like it !
peter couniaz said:
I'm going to take the update to 8.0 an hope someone cames up with a Root process ! an it is the U4 bootloader so backdating the firmware should work if I don't like it !
Click to expand...
Click to collapse
I'm already running Oreo. TWRP has problems with it. I can't make a backup of the OS. You can restore a back up, but you have to flash the BL file from ARG2 then wipe everything in TWRP first. SuperSU 2.82-SR5 will cause a boot loop. I'm going to try magisk 17.1. Honestly, I'm very disappointed with Samsung's Oreo... It's almost the exact same as Nougat, and the new camera sucks, very bad. They gave us Nougat, with Oreo 8.1 as the base firmware. That's my literal take on it. I'm definitely getting a Moto G6 after seeing this, and I'm going back to my stock build.
J727P update
Spaceminer said:
I'm already running Oreo. TWRP has problems with it. I can't make a backup of the OS. You can restore a back up, but you have to flash the BL file from ARG2 then wipe everything in TWRP first. SuperSU 2.82-SR5 will cause a boot loop. I'm going to try magisk 17.1. Honestly, I'm very disappointed with Samsung's Oreo... It's almost the exact same as Nougat, and the new camera sucks, very bad. They gave us Nougat, with Oreo 8.1 as the base firmware. That's my literal take on it. I'm definitely getting a Moto G6 after seeing this, and I'm going back to my stock build.
Click to expand...
Click to collapse
You haven't tried flashing back to nougat then !
peter couniaz said:
You haven't tried flashing back to nougat then !
Click to expand...
Click to collapse
I have, and flashing back to nougat works fine. You have to flash ARG2 for it to work, and you can't downgrade the Modem. I'll put together instructions and probably a debloated ROM later this evening, and I'll get the firmware uploaded ASAP. Some notes, clearing the camera data fixes the blurry image problem, and it can be rooted. You need the latest TWRP, and Magisk 17.1 stable. You must flash TWRP, swipe to allow modifications, then format data with the option that makes you type "yes", then flash magisk. Root works perfectly. No issues. I'm debloating the OS right now. I'm about to test Viper too. Its actually much faster than Nougat once the junk is out and yes, it can be fully deknoxed. This might not be so bad. I'm still disappointed with their lack of Oreo-esq cosmetics though.
J727P update
Spaceminer said:
I have, and flashing back to nougat works fine. You have to flash ARG2 for it to work, and you can't downgrade the Modem. I'll put together instructions and probably a debloated ROM later this evening, and I'll get the firmware uploaded ASAP. Some notes, clearing the camera data fixes the blurry image problem, and it can be rooted. You need the latest TWRP, and Magisk 17.1 stable. You must flash TWRP, swipe to allow modifications, then format data with the option that makes you type "yes", then flash magisk. Root works perfectly. No issues. I'm debloating the OS right now. I'm about to test Viper too. Its actually much faster than Nougat once the junk is out and yes, it can be fully deknoxed. This might not be so bad. I'm still disappointed with their lack of Oreo-esq cosmetics though.
Click to expand...
Click to collapse
Thank you for the info on downgrading back to nougat !
peter couniaz said:
Thank you for the info on downgrading back to nougat !
Click to expand...
Click to collapse
I've got 3 of 4 firmware files uploaded. The AP file is giving me trouble cause my WiFi sucks, and it keeps failing before it finishes. I did put together a full stock Oreo ROM but its got problems. You can only flash it using TWRP if you have the ARG2 bootloader, but, the ARG2 bootloader, won't allow Oreo to boot up no matter what. We'd need a custom boot.img and I can't make one. The ROM can't be flashed with the Oreo bootloader installed either, because it prevents TWRP from copying/writing to the data or system partitions. If it tries to, it'll reboot half way through. Magisk 17.1 will also lose root after awhile. We need a custom boot, or we need a modified root method and an updated TWRP to have any fun with it. SMH at Samsung right now. They gave us Oreo, with no milk, and a slap in the face. Nougat everything, running on Oreo 8.1 firmware... I'll never get over that. I'm running an ARG2 build cause everything works, and largely looks the same. I swear, they didn't even try. They just reskinned some Nougat apps and put them in an Oreo system. I will never buy another Samsung product after seeing this half hearted Oreo they gave us.
J727P update
Spaceminer said:
I've got 3 of 4 firmware files uploaded. The AP file is giving me trouble cause my WiFi sucks, and it keeps failing before it finishes. I did put together a full stock Oreo ROM but its got problems. You can only flash it using TWRP if you have the ARG2 bootloader, but, the ARG2 bootloader, won't allow Oreo to boot up no matter what. We'd need a custom boot.img and I can't make one. The ROM can't be flashed with the Oreo bootloader installed either, because it prevents TWRP from copying/writing to the data or system partitions. If it tries to, it'll reboot half way through. Magisk 17.1 will also lose root after awhile. We need a custom boot, or we need a modified root method and an updated TWRP to have any fun with it. SMH at Samsung right now. They gave us Oreo, with no milk, and a slap in the face. Nougat everything, running on Oreo 8.1 firmware... I'll never get over that. I'm running an ARG2 build cause everything works, and largely looks the same. I swear, they didn't even try. They just reskinned some Nougat apps and put them in an Oreo system. I will never buy another Samsung product after seeing this half hearted Oreo they gave us.
Click to expand...
Click to collapse
You are using the latest twrp try going back 2 builds on the twrp an see if that will stick on the full 8.1.0 firmware don't know if it will work but if you have the full 8.1.0 firmware give it a shot an let us all know if it does ! Or when you get the full firmware uploaded send me a link an I will try it ! Thank you !!
I have posted the oreo firmware here https://forum.xda-developers.com/galaxy-j7/how-to/sm-j727p-oreo-8-1-firmware-t3841778
HELP FLASH BACK J727P to nougout
i need some help, every time i try to downgrade to android 7 in this phone j727p, i get errors flashing modem, ive tried combination firmware, and full flash 4arg2 im currently 8.1.0 4brh5 and cant flash back to nougout
---------- Post added at 07:09 PM ---------- Previous post was at 07:04 PM ----------
Spaceminer said:
I have, and flashing back to nougat works fine. You have to flash ARG2 for it to work, and you can't downgrade the Modem. I'll put together instructions and probably a debloated ROM later this evening, and I'll get the firmware uploaded ASAP. Some notes, clearing the camera data fixes the blurry image problem, and it can be rooted. You need the latest TWRP, and Magisk 17.1 stable. You must flash TWRP, swipe to allow modifications, then format data with the option that makes you type "yes", then flash magisk. Root works perfectly. No issues. I'm debloating the OS right now. I'm about to test Viper too. Its actually much faster than Nougat once the junk is out and yes, it can be fully deknoxed. This might not be so bad. I'm still disappointed with their lack of Oreo-esq cosmetics though.
Click to expand...
Click to collapse
sr ive been trying to flash back the nougout firmware arg2 but still problems, the cp box in z3x uncheck, but still got errors with csc, i need to downgrade from brh5 and it wont let me, if you could be more specific how did you do the process
Galaxy J7 Perx (Boost) on J727PVPU4BRH5
Spaceminer said:
I managed to find the firmware, however, it's behind a pay wall on servers in Iran. The firmware name is J727PVPU4BRH5 if you want to help look for it. As soon as find it on a free server, I'll post an update.
Click to expand...
Click to collapse
Dear Sirs;
Having had to replace my originally bought (Nov 17, 2017) J7 Perx from Boost, then bricking it and replacing it with a Galaxy S6 refurb from Boost, which was then STOLEN by a "friend" of 6(six) years, has been replaced by a NEWER J7 Perx. This device received at lest 3, if not 4 OTA updates, one of which was a supplemental firmware/software update. About Phone (and Samsung INFO app) NOW reveal the following detail:
HARDWARE VERSION; J727P.02
Mfg date; 03/15/2018
Software Version; J727PVPU4BRH5
Android Version; 8.1.0
Samsung Experience; 9.5
Baseband Version; J7272PVPU4BRH5
Build Number; M1AJQ.J727PVPU4BRH5
Android Security Patch; August 1, 2018.
If given instruction and link to necessary utility to extract the firmware from my device to my PC, I would be more than pleased to provide the files(s) procured from that process.
I look forward to hearing more about possible deodexed firmware to ROOT my newest device.
A custom ROM would be nice, too.
---------- Post added at 15:23 ---------- Previous post was at 15:14 ----------
Guess I should have browsed a few more posts before posting.
I found the link to all the 8.x firmwares for the various models, and must say "Bravo!" for the Herculean effort expended to collect, upload and make all that available.
Thanks!

Problems with Moto G5 Plus

I'm worried that I've permanently messed up my phone. I didn't make a backup of my stock firmware when I first flashed Lineage OS, and then I was having issues with that, so now I'm using the stock one again, but it's not official. I used fastboot to flash it and then flashed twrp and magisk. That should of been sufficient to factory reset it right? It just keeps having little problems that it didn't have before, like internet loading things slowly and bugs and crashing apps. The reason I switched off the Lineage OS rom is because it had little problems like that too. I just don't know what to do anymore.
Relevant Info:
Device: Moto G5 Plus Unlocked US version
Carrier: T-Mobile
lumbo7333 said:
I'm worried that I've permanently messed up my phone. I didn't make a backup of my stock firmware when I first flashed Lineage OS, and then I was having issues with that, so now I'm using the stock one again, but it's not official. I used fastboot to flash it and then flashed twrp and magisk. That should of been sufficient to factory reset it right? It just keeps having little problems that it didn't have before, like internet loading things slowly and bugs and crashing apps. The reason I switched off the Lineage OS rom is because it had little problems like that too. I just don't know what to do anymore.
Relevant Info:
Device: Moto G5 Plus Unlocked US version
Carrier: T-Mobile
Click to expand...
Click to collapse
What exactly are your problems? Check the thread of the custom ROM you installed and look for fixes there, maybe you installed an outdated version and your problems have been fixed in the updates. Good luck.
lumbo7333 said:
...now I'm using the stock one again, but it's not official. I used fastboot to flash it and then flashed twrp and magisk.
Click to expand...
Click to collapse
What do you mean with "stock but not official"?
Where did you get it from?
There are some sources for official firmwares signed by Motorola here on XDA so what makes you think the one you use isn't official?
If so that could be for sure the reason for problems for I have to say that I haven't seen unofficial stock ROMs except TWRP flashables (you said you flashed using fastboot so it can't be this) or debloated stock ROMs.
Wolfcity said:
What do you mean with "stock but not official"?
Where did you get it from?
There are some sources for official firmwares signed by Motorola here on XDA so what makes you think the one you use isn't official?
If so that could be for sure the reason for problems for I have to say that I haven't seen unofficial stock ROMs except TWRP flashables (you said you flashed using fastboot so it can't be this) or debloated stock ROMs.
Click to expand...
Click to collapse
I mean it didn't come officially from Motorola. I got it from this:
getdroidtips.com/moto-g5-plus-stock-firmware-collections-updated (It's not allowing me to post outside links because I'm a new user, so just add www to that)
lumbo7333 said:
I mean it didn't come officially from Motorola. I got it from this:
getdroidtips.com/moto-g5-plus-stock-firmware-collections-updated (It's not allowing me to post outside links because I'm a new user, so just add www to that)
Click to expand...
Click to collapse
If you can flash the firmware by fastboot it's most likely an official signed firmware that was leaked. To be on the safe side use the firmware found here on XDA like this source:
https://mirrors.lolinet.com/firmware/moto/potter/official/RETAIL/
Just make sure to use the same firmware you we're on or a newer one that fits to your region.
I recommend to reflash the latest stock firmware, maybe something went wrong the first time.
And remember to always make a backup before you flash anything that could cause problems.
It the latest stock firmware different from the stock rom I flashed?
You can also try the repair function in Lenovo Moto Smart Assistant app.
https://support.motorola.com/us/en/solution/MS126499
Hmm. Now my security updates are failing.
goodjuju said:
You can also try the repair function in Lenovo Moto Smart Assistant app.
https://support.motorola.com/us/en/solution/MS126499
Click to expand...
Click to collapse
Will doing that use official firmware?
lumbo7333 said:
It the latest stock firmware different from the stock rom I flashed?
Click to expand...
Click to collapse
lumbo7333 said:
Will doing that use official firmware?
Click to expand...
Click to collapse
Sure. The firmwares from Moto Smart Assistant are the same like the ones I've posted above, I compared the hash files.
Would be interesting to know what firmware you're on at the moment.
I'm on OPSS28.85-17-2
I thought my firmware was unofficial since it was leaked. Also do you why I can't update?
lumbo7333 said:
I'm on OPSS28.85-17-2
I thought my firmware was unofficial since it was leaked. Also do you why I can't update?
Click to expand...
Click to collapse
Any firmware you'll find is leaked even the official ones. Motorola doesn't release any firmwares except the ones you can download with Lenovo Motorola Smart Assistant.
The link I posted https://mirrors.lolinet.com/firmware/moto/potter/official/RETAIL/
contains official firmwares too. The latest one for the US (85-17-4) can be found there too.
What happens exactly when your OTA fails?
Wolfcity said:
Any firmware you'll find is leaked even the official ones. Motorola doesn't release any firmwares except the ones you can download with Lenovo Motorola Smart Assistant.
The link I posted https://mirrors.lolinet.com/firmware/moto/potter/official/RETAIL/
contains official firmwares too. The latest one for the US (85-17-4) can be found there too.
What happens exactly when your OTA fails?
Click to expand...
Click to collapse
- I download the update the update
- It reboots and goes into TWRP for some reason
- I have to manually reboot to system from TWRP
- My phone boots to system and says update unsuccessful
(This is a security update by the way.)
lumbo7333 said:
- I download the update the update
- It reboots and goes into TWRP for some reason
- I have to manually reboot to system from TWRP
- My phone boots to system and says update unsuccessful
(This is a security update by the way.)
Click to expand...
Click to collapse
You can't take any system updates when you have TWRP installed!
For OTA you have to be on unrooted full stock ROM incl. stock recovery. This is a very important rule.
So you have to ways to handle this:
- Flash clean stock firmware and apply to the OTA afterwards (if you flash the latest firmware 17.4 you don't need the OTA anymore). You will loose your internal storage data or skip the "erase userdata" command.
Firmware from here: https://mirrors.lolinet.com/firmware/moto/potter/official/RETAIL/
- Take a TWRP flashable build but be aware that you can't take OTA updates at all in the future which is not needed as the firmwares are up to date.
TWRP flashables here:
https://forum.xda-developers.com/g5...o-twrp-flashable-stock-builds-coming-t3830482
Wolfcity said:
You can't take any system updates when you have TWRP installed!
For OTA you have to be on unrooted full stock ROM incl. stock recovery.
So you have to ways to handle this:
- Flash clean stock firmware and apply to the OTA afterwards (if you flash the latest firmware 17.4 you don't need the OTA anymore). You will loose your internal storage data or skip the "erase userdata" command.
Firmware from here: https://mirrors.lolinet.com/firmware/moto/potter/official/RETAIL/
- Take a TWRP flashable build but be aware that you can't take OTA updates at all in the future which is not needed as the firmwares are up to date.
TWRP flashables here:
https://forum.xda-developers.com/g5...o-twrp-flashable-stock-builds-coming-t3830482
Click to expand...
Click to collapse
Will flashing a new build delete my data?

Categories

Resources