Database Users

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

Good News Guys >>>>Official T-Mobile Galaxy J7 Android 7.1.1 Nougat update released

Good News Guys >>>>Official T-Mobile Galaxy J7 Android 7.1.1 Nougat update released
We reported recently that the Galaxy J7 might soon receive the Nougat update. The handset was spotted at the Wi-Fi Alliance running a Nougat build. It was a big indication that the company was planning on rolling out the update soon.
T-Mobile has now started rolling out the Android 7.1.1 Nougat update for the Galaxy J7. It’s one of the few devices that Samsung has updated straight to version 7.1.1 from Marshmallow.
T-Mobile Galaxy J7 Android 7.1.1 Nougat Update
T-Mobile has started rolling out the Nougat update for the Galaxy J7 over-the-air. However, the company’s support document for this handset is all over the place. It assigns version number Android 6.0.1, Android 7.0 and Android 7.1.1 to one single firmware version, J700TUVU3BQI5.
This is obviously not possible. Clearly, there are clerical issues with the document. That doesn’t mean the T-Mobile Galaxy J7 Android 7.1.1 Nougat update isn’t rolling out. Those who own this handset on T-Mobile will soon receive an update notification if they haven’t already.
This firmware is also available for download from our firmware section where the Android version is accurately mentioned as Android 7.1.1 Nougat. Despite the fact that this update has been released in October, it comes with the August security patch.
Galaxy J7 owners on T-Mobile can either wait for the update to go live in their region or simply download the firmware from our website.
Download 7.1.1 here and happy flashing J700TUVU3BQI5 - Galaxy J7 SM-J700T TMB USA (T-Mobile)
Click here
Source :- SamMobile

Tmobile received the update from samsung on 8/28. They filled it with their garbage and sent it last thursday, most of us flashed aqf1 stock and got it ota friday morning.i dont see any clerical errors or anything like that at all. And ive been digging through the build for a week. Im running it now. All internation j7 roms flash with this builds kernel, but reboot in the setup wiz, so once we get a good base there will be a ton of ports in this community. Also, we have found, edge screen, blf, high performance mode, and aod hidden but inactive in the phone. This build is something amazing folks.
Btw, sammobile is a useless, slow dinosaur. Updato via playstore is the best source for firmware.

fullofhell said:
Tmobile received the update from samsung on 8/28. They filled it with their garbage and sent it last thursday, most of us flashed aqf1 stock and got it ota friday morning.i dont see any clerical errors or anything like that at all. And ive been digging through the build for a week. Im running it now. All internation j7 roms flash with this builds kernel, but reboot in the setup wiz, so once we get a good base there will be a ton of ports in this community. Also, we have found, edge screen, blf, high performance mode, and aod hidden but inactive in the phone. This build is something amazing folks.
Btw, sammobile is a useless, slow dinosaur. Updato via playstore is the best source for firmware.
Click to expand...
Click to collapse
I would like to have the edge screen without installing a Rom you think is possible?.

carlosbalbuena_ said:
I would like to have the edge screen without installing a Rom you think is possible?.
Click to expand...
Click to collapse
Not sure. It isnt working yet.

Will this work for the metro pcs variant ( SM-J700T1) as well?

hightech316 said:
Will this work for the metro pcs variant ( SM-J700T1) as well?
Click to expand...
Click to collapse
I think so..i got edge lighting to work. Im writing each csc tweak down and will include them in our next build.see photo,.this is native in the stock firmware

Has anyone flashed this update on their metro J7?
Does this update contain t-mobile bloat?

hightech316 said:
Has anyone flashed this update on their metro J7?
Does this update contain t-mobile bloat?
Click to expand...
Click to collapse
flash the aqf1 metro firmware, then take update to 7.1.1 ota. Then u will have metro nougat

fullofhell said:
Not sure. It isnt working yet.
Click to expand...
Click to collapse
And the Performance mode got it by installing some application or what?

carlosbalbuena_ said:
And the Performance mode got it by installing some application or what?
Click to expand...
Click to collapse
Download csc editor by wanam via playstore its in one of those...u look thru and change each item to "true" then reboot. Its called performance tuning

fullofhell said:
Download csc editor by wanam via playstore its in one of those...u look thru and change each item to "true" then reboot. Its called performance tuning
Click to expand...
Click to collapse
Ok bro I'm going to try and the edge lighting like it did

I got the stock ROM deodex and services jar modded but when I connect it to my lab top it don't come up unless I go and turn off USB debugging

mario1634 said:
I got the stock ROM deodex and services jar modded but when I connect it to my lab top it don't come up unless I go and turn off USB debugging
Click to expand...
Click to collapse
This firmware is being a arsehat for me too.

When I flashed the original boot img. Now my lab top able to see my phone. It crazy because I can still pull and push but programs like assayyed don't see it until I flash stock boot img

mario1634 said:
When I flashed the original boot img. Now my lab top able to see my phone. It crazy because I can still pull and push but programs like assayyed don't see it until I flash stock boot img
Click to expand...
Click to collapse
Weird af

fullofhell said:
flash the aqf1 metro firmware, then take update to 7.1.1 ota. Then u will have metro nougat
Click to expand...
Click to collapse
Great, thanks!
Once I have time I'll upload a rooted nandroid

Safe to flash through TWRP while rooted with xposed? Or should I disable xposed and uninstall root? Also, should I wipe when flashing or does it matter

phoen1x74 said:
Safe to flash through TWRP while rooted with xposed? Or should I disable xposed and uninstall root? Also, should I wipe when flashing or does it matter
Click to expand...
Click to collapse
U cannot in any capacity flash a stock firmware with twrp.u have to wipe your whole phone and go to download mode and flash the firmware via odin. Dont forget to unzip the file first so u have the unzipped form of it loaded in the ap slot

Aight I'm chill (no way at all to update without wiping my phone?) Like what if I don't wipe and flash in odin; will that lead to problems?

phoen1x74 said:
Aight I'm chill (no way at all to update without wiping my phone?) Like what if I don't wipe and flash in odin; will that lead to problems?
Click to expand...
Click to collapse
U could if u werent rooted or had twrp installed..if u dont wipe before odin, it will prob fail until u wipe it honestly.

Android 8 Oreo Update

Deleted

Maybe because the Sprint Oreo will be using BLv6 so its 2 numbers behind everyone else? lol ... anyone have any thoughts about what the BL-version could possibly be for the Sprint Oreo? ... could they or would they use a BLv4 like everyone else?

that was the Sprint answer

SprintBama said:
Maybe because the Sprint Oreo will be using BLv6 so its 2 numbers behind everyone else? lol ... anyone have any thoughts about what the BL-version could possibly be for the Sprint Oreo? ... could they or would they use a BLv4 like everyone else?
Click to expand...
Click to collapse
If anything, they would change it to v7. Maybe they are waiting for a merger, which could happen next week

I checked for update today and got 1627.64mb g930pvpu6cre7 Samsung experience 9.0 with oreo.

I haven't gotten an update from Sprint on my S7 since December 2016. I am still on some random Nougat beta version.
I thought a brand new firmware update to Oreo would reset whatever bug was in there causing this, but it looks like one person in my house got the Oreo update and mine is still saying I am up to date when I check manually.
Is there no longer an ODIN for macOS? I thought there was one, but I used it on another Mac maybe 4 years ago when I was on my S3 and rooting it. Doesn't seem to exist anymore.

Just received oreo on my s7 for boost. So far I'm not impressed. I was really hoping for Dolby on this but guess not. The build number is SMG930PVPU6CRE7

kalala said:
I haven't gotten an update from Sprint on my S7 since December 2016. I am still on some random Nougat beta version.
I thought a brand new firmware update to Oreo would reset whatever bug was in there causing this, but it looks like one person in my house got the Oreo update and mine is still saying I am up to date when I check manually.
Is there no longer an ODIN for macOS? I thought there was one, but I used it on another Mac maybe 4 years ago when I was on my S3 and rooting it. Doesn't seem to exist anymore.
Click to expand...
Click to collapse
On Mac you can use Heimdall to flash the latest Nougat firmware then update through OTA to Oreo. Because there isn't any firmware file yet on Updato or Sammobile.

i manfully updated @ 4:15. they sent it @ 1627.64 mb. still downloading. when I got my att update I tried all the batch root methods for my 935a. saving magisk for last bc I didn't have the boot.img for the cre4 update.
I I only had the "att beta" update from March. long story short it won't boot with the nougat eng.boot. I gave it an hour. I cleared the cache, factory reset, tried to add flash all of the earlier img files I had for oreo, nothing worked. had to flash it back to nougat bra1. I immediately requested the update again. they approved. the next day I attempted to flash magisk 16.4. w/ the modified odin 3.1.3 version. it wouldn't flash. with the cre4 boot.tar in hand, I tried every method on gods green earth to gain some sort of r/w access. it was late, I was tired, I flashed the eng boot. once again it was stuck at the Samsung boot logo. it wouldn't allow me into recovery to push the cre4 update zip. once again I'm back to bra1 nougat. I booted into recovery & updated it from the sd card. when it booted I noticed it wasn't anywhere as clean & polished as the ota I had twice. I've flashed back to brd1 ten times, & requested the ota. after smart switch, I used all the avail windows software I could acquire & kept trying, they won't send it. but they did provide me with a new picture for my samsung account. I'll post it later. gotta check out this 930p oreo.

razor001_ said:
On Mac you can use Heimdall to flash the latest Nougat firmware then update through OTA to Oreo. Because there isn't any firmware file yet on Updato or Sammobile.
Click to expand...
Click to collapse
I don't think Heimdall works on High Sierra or even Sierra anymore.

I'm wanting to move to a SM-930U version of stock android on my 930P. But in struggling to do so for the past couple of weeks I finally figured out that sprint as updated the bootloader to version 5 and most of the firmware images for 930U are version 4 (android 7 nugut). (PU4 vs PU5) which results in a Odin fuse error.
The phone is currently nagging me to go from PU5BQL1 to BU6BRD2. If I understand the nameing convention that would move me to version 6 of the bootloader.
What are the odds I can move to oreo for 930U and avoid the bootloader fuse issue? I think I also understand that as of this posting date a 930U oreo firmware has not been released?

schmism said:
I'm wanting to move to a SM-930U version of stock android on my 930P. But in struggling to do so for the past couple of weeks I finally figured out that sprint as updated the bootloader to version 5 and most of the firmware images for 930U are version 4 (android 7 nugut). (PU4 vs PU5) which results in a Odin fuse error.
The phone is currently nagging me to go from PU5BQL1 to BU6BRD2. If I understand the nameing convention that would move me to version 6 of the bootloader.
What are the odds I can move to oreo for 930U and avoid the bootloader fuse issue? I think I also understand that as of this posting date a 930U oreo firmware has not been released?
Click to expand...
Click to collapse
almost zero... asuming that Oreo for "U" Variants step up with BL on this month maybe next one, is something pausible but stepping up two versions in any short time is questionable... but who knows. The best you can do is wait this or the next month for BL update on U variants.

To be clear I'm still on version 5. I will continue to put off the upgrade to 6.

Moto g5 plus stock ROM

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

Problem with downgrading S8

Hello,
Recently I've updated my Galaxy S8 g950fd from Android 8.0 to 9.0, however i found it terrible and I would love to go back to 8.0. I've read many topics and all of them states that I have to downgrade it through the Odin. I've downloaded a few softs from websites:
SM-G950F_1_20181227130827_c3nriwjmas_fac
G950FXXS4CRLB
G950FXXS4CRLB_G950FOXM4CRL1_LYS
G950FXXU3CRGH_CL14023573_QB19093103
G950FXXS4CRLB_G950FOXM4CRL1_LYS
G950FXXU1AQG5_G950FOXM1AQG5_ZTO_4file
And non of them works. Odin keep showing FAIL message, phone stuck on bootloop and the only software I can use is 9.0 ( G950FXXS5DSF1_OXM5DSF1_(SM-G950FD))
At this moment I'm downloading 2 firmwares from sammobile.com website: XSG-G950FXXU4CRL3-20181218135110 and XSG-G950FXXS4CRLB-20190128142840 and I hope they will resolve the issue I'm facing.
What am I doing wrong? Is there any other way to downgrade my phone?
Thanks a lot for replies!

Your bootloader version is v5 and all other firmware including previous pie and all Oreo firmware are at v4 . If u installed June or July update on your phone then u can't go back anymore and thus Odin keep faling for your

Scorpionea said:
Your bootloader version is v5 and all other firmware including previous pie and all Oreo firmware are at v4 . If u installed June or July update on your phone then u can't go back anymore and thus Odin keep faling for your
Click to expand...
Click to collapse
What about going back to 8.0 through TRWP? Impossible?
I've found this thread: https://forum.xda-developers.com/galaxy-s8/help/s8-downgrade-version-9-t3922577 and I've downloaded G955USQU5CSA4_G955UOYN5CSA4_CCT.zip
G955USQS5CRL1_G955UOYN5CRL1_USC.zip
G955USQU5CSA4_G955UOYN5CSA4_LRA.zip
G955USQU5CRK1_G955UOYN5CRK1_TMB.zip , however when I try to install s8+ firmware through Odin it keeps showing FAIL. Damn.. No other way to go back to 8.0 than new phone?

sssylaru said:
What about going back to 8.0 through TRWP? Impossible?
I've found this thread: https://forum.xda-developers.com/galaxy-s8/help/s8-downgrade-version-9-t3922577 and I've downloaded G955USQU5CSA4_G955UOYN5CSA4_CCT.zip
G955USQS5CRL1_G955UOYN5CRL1_USC.zip
G955USQU5CSA4_G955UOYN5CSA4_LRA.zip
G955USQU5CRK1_G955UOYN5CRK1_TMB.zip , however when I try to install s8+ firmware through Odin it keeps showing FAIL. Damn.. No other way to go back to 8.0 than new phone?
Click to expand...
Click to collapse
U can root the phone and try some of the old custom based rom on Oreo, officially u can't go back

S8
Scorpionea said:
U can root the phone and try some of the old custom based rom on Oreo, officially u can't go back
Click to expand...
Click to collapse
I've found Lineage 15.1 OS with bootloader v5 on android 8.0 however I am struggling now with installing TWRP. Keep getting FAIL in ODIN and note in phone: Only official relased binaries are allowed to be flashed (RECOVERY). I've tried to reset cache, perform factory data, OEM is enabled and usb debugging as well. I don't know what's going on to be honest and after reviewing thousands of posts - I can't fix that issue.. My current software on my g950fd is G950FXXU5DSFB Android 9.0.
Is here anyone who can advice me what should I do? I would really appreciate that. Thanks!

Anyone?

Sorry can't help you with that much, it seems u did all correct steps for rooting the phone. dunno why u get only official binary message.
Edit:
Post your issue here, maybe someone here can help you more
https://r.tapatalk.com/shareLink?ur...share_tid=3847712&share_fid=3793&share_type=t

Scorpionea said:
Sorry can't help you with that much, it seems u did all correct steps for rooting the phone. dunno why u get only official binary message.
Edit:
Post your issue here, maybe someone here can help you more
https://r.tapatalk.com/shareLink?ur...share_tid=3847712&share_fid=3793&share_type=t
Click to expand...
Click to collapse
Thanks! I try!