This post/thread is to summarize where to find full SBF files, leaks, etc for the Moto X (2013 or First Generation).
REMEMBER... Always flash the same ROM/SBF or Newer to your phone. NEVER attempt to downgrade your rom!!! for more info, see DOWNGRADING
Motorola posts their complete STOCK "Recovery Images" (aka SBF files) for the GSM and Verizon Developer Edition X at -> https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images
If you have the Retail and/or Moto Maker XT1053 (aka Unlocked ships with T-Mobile SIM, or Unlocked Ships with Net10 SIM), you can also use the GSM Developer Edition (XT1053) roms from Moto's site.
If you have the Retail and/or Moto Maker Verizon X (XT1060), you can also use the Verizon Developer Edition (XT1060) roms from Moto's site.
There might be a delay in Moto making an SBF available.
For other models of X, I know of 3 sites for "leaks" which contain the SBF files for nearly every model of X (2013). You may need to check EACH site to find the particular rom you are looking for. NOTE: None of the following sites are owned, operated, or sponsored by Motorola. They may be down or offline at any time, without warning.
http://sbf.droid-developers.org/ <- DEAD when checking on 8/22/15
http://www.filefactory.com/folder/dd05c058d3ff8dbe/?sort=created&order=DESC&show=100&page=1 <- seems to have the most 4.4.4 roms
http://motofirmware.com/files/category/9-ghost/ <- DEAD when checking on 8/22/15 once there, look under the GHOST folder. (as of 11/9/2014, its format and access has changed)
http://motofirmware.center/files/ <- Select Moto X 1St Generation from the list along the right side of the page
Are there any others?
@dagoban has linked a few other in Post #17 of this thread..
dagoban said:
..Really good and fast overview page with most/all files, when you look for something, go here 1st:
https://cloud.mail.ru/public/64a43f0fcc1e/Moto_X or here:
https://cloud.mail.ru/public/a083d0bb5e97/Motorola
Big Thx to OP: http://4pda.ru/forum/index.php?showtopic=514209&st=8360
Click to expand...
Click to collapse
See Post #17 for more direct links.
As 5.1 SBF files become available, they are being collected and curated in this thread -> [OFFICIAL] Collection Full Firmwares (FXZ/SBF) Lollipop 5.1
FAQ:
1. How do I know which file to download?
- If you are NOT running a 3rd Party or Custom ROM... take a look on your phone, under App Drawer -> Settings... Make note of what is listed under System Version, Android Version, and build number. Then visit one (or all) of the sites until you find the SBF that matches. The file name will usually contain parts or all of that info listed under settings, and possibly the carrier name, or acronym for the carrier name (Verizon might be VZW, Rogers Canada might be RCI, etc).
Normally I would suggest BEFORE you flash away from Stock, on the phone you first go App Drawer -> Settings -> About Phone... Make note of what is listed under System Version, Android Version, and build number. Then visit one (or all) of the sites until that host the leaked SBF files until you find the SBF that matches and down load the file to your PC for use later.. The file name will usually contain parts or all of that info listed under settings, and possibly the carrier name, or acronym for the carrier name (Verizon might be VZW, Rogers Canada might be RCI, etc).
So for example: If your phone model is XT1058 and under about phone it reports...
android version is 4.4.4
system version is 212.44.26. ghost_row.RCI.en.ca
build nunber is KXA21.12-L1.26
That tells me you have a Rogers Canada (RCI) XT1058 with 4.4.4 ROM on it. When you look at the file factory site for your SBF, you want to look for a file that contains some/all of that info, like... XT1058_RCI-CA_4.4.4_KXA21.12-L1.26_59_cid14_CFC_1FF.xml.zip
(notice the parts of the "about phone" info and file name which are highlighted in Bold to help illustrate the example)
IF you are already running a CUSTOM or 3Rd party rom, like CM, system version and build number will not match STOCK Moto SBF files
2. Where do all these SBF files come from?
As mentioned earlier, Moto does make the Dev Edition "recovery images" (in SBF format) available on their web site. For all others, the only way for us to get firmware files, is for a copy to be LEAKED to us.. The "Leaked" firmwares are files that are basically "stolen" by a Motorola or wireless carrier employee, who then posts the file on the internet for us... So we can't always count on this ever happening, nor can we have any expectations that a particular firmware will actually get leaked, or when it will be leaked.
There is some talk about using Motorla Device Manager (MDM) app to upgrade your phone, and how during the update process, the app downloads the full FXZ (another term for SBF) to your PC, so it could be copied/saved to another folder for use later. I have not done this with MDM.
EDIT: As of 12/12/14, Only the filefactory.com link is working. The others appear to be down. I don't know the owners of the sites, so I can't say if they will return or not.
EDIT2: As of 1/2/15, motofirmware.com seems to be back up, but sbf.droid-developers.org appears to be gone.
Great info! ??
SBF is my first choice, but when I needed the 4.4.4 retail firmware not found it in SBF, I had to turn to Google and found it.
FTP of Moto Firmware is empty, but the File Factory folder has many versions! Very cool.
if my firmware is currently 4.2.2, can I download the 4.4.2 or 4.4.4 firmware and it would fix a soft brick with 4.2.2? or must i find the 4.2.2 firmware in order to fix the issues?
x000x said:
if my firmware is currently 4.2.2, can I download the 4.4.2 or 4.4.4 firmware and it would fix a soft brick with 4.2.2? or must i find the 4.2.2 firmware in order to fix the issues?
Click to expand...
Click to collapse
I'm not sure what problem you encountered is.. If it is truely "soft bricked" first start by booting the phone to APFastboot/Booloader screen and use fastboot or mFastboot on the PC to erase the phone's cache then try to reboot.
If that doesn't work, generally to recover from any issues, if you can boot into APFasboot/Booloader, check the version on the second line, then download and flash the appropriate ROM version, you can recovery from most soft brick scenarios.
30.70 = original 4.2.2
30.71 = 4.2.2 OTA with camera update
30.B2 = 4.4
30.B4 = 4.4.2
30.B7 = 4.4.4
Once on 4.4.2, 4.4.3 or 4.4.4, NEVER flash an older version ROM!!!
On occasion, you need to use mfastboot, and do a few extra commands (See Option 5 at -> http://mark.cdmaforums.com/MotoX-ReturnToStock.html )
If you have any questions, please search and see if any threads with your phone's symptoms already exist then post in that thread. If a thread doesn't already exist, start a new one, and post any details of what phone you have (model, carrier), what the symptom is, and what was done leading up to the symptom appearing. The more details you can supply the better.
edit: problem resolved. see my findings: http://forum.xda-developers.com/showpost.php?p=57122184&postcount=635
Thanks Kidjoe
x000x said:
well issue was I was rooted with twrp and silly me I tried to do the ota update. so now it won't get past the warning about unlocked bootloader. I read after the fact that you needed to revert back to stock before taking ota. mine is 30.71, but the other issue is I cannot find that firmware anywhere. my only option in regards to firmware is to use 4.4.2 that I found. I've posted the question here http://forum.xda-developers.com/showthread.php?t=2542219&page=123
Click to expand...
Click to collapse
BUT if you tried to take the OTA while TWRP was on your phone, just boot into fastboot mode on the phone, and do a mfastboot erase cache will get you out of the bootloop. Then you can flash stock recovery on there, take the ota.
Or you can just flash the 4.4.2 or 4.4.4 for your phone, when completed, flash TWRP on there, reboot hte phone to bootloader, enter Recovery/TWRP and root.
Yes, You can flash a higher/newer version without problems. You just can't flash older once 4.4.2 or higher has been flashed to your phone. (the only time its safe to flash older was when you had 4.4 on your phone, and you were Following the SlapMyMoto process to downgrade to 4.2.2. W/Camera Update as part of the process).
Thank you for this!
KidJoe said:
I'm not sure what problem you encountered is.. If it is truely "soft bricked" first start by booting the phone to APFastboot/Booloader screen and use fastboot or mFastboot on the PC to erase the phone's cache then try to reboot.
If that doesn't work, generally to recover from any issues, if you can boot into APFasboot/Booloader, check the version on the second line, then download and flash the appropriate ROM version, you can recovery from most soft brick scenarios.
30.70 = original 4.2.2
30.71 = 4.2.2 OTA with camera update
30.B2 = 4.4
30.B4 = 4.4.2
30.B7 = 4.4.4
Once on 4.4.2, 4.4.3 or 4.4.4, NEVER flash an older version ROM!!!
On occasion, you need to use mfastboot, and do a few extra commands (See Option 5 at -> http://mark.cdmaforums.com/MotoX-ReturnToStock.html )
If you have any questions, please search and see if any threads with your phone's symptoms already exist then post in that thread. If a thread doesn't already exist, start a new one, and post any details of what phone you have (model, carrier), what the symptom is, and what was done leading up to the symptom appearing. The more details you can supply the better.
Click to expand...
Click to collapse
Getting a Moto X VZW dev ed in a few days, and while it may never apply to me, I had his same question.
I understand what you said, but it doesn't really address the issue of if it is OK to use these images to flash to a later version...
I am aware of the risks of flashing to older firmwares, but are their risks to flashing NEWER updates? I have seen people go as far as to recommend flashing the current version first to recover, then updating... But is this necessary?
scryan said:
Getting a Moto X VZW dev ed in a few days, and while it may never apply to me, I had his same question.
I understand what you said, but it doesn't really address the issue of if it is OK to use these images to flash to a later version...
I am aware of the risks of flashing to older firmwares, but are their risks to flashing NEWER updates? I have seen people go as far as to recommend flashing the current version first to recover, then updating... But is this necessary?
Click to expand...
Click to collapse
U can always flash newer images without a problem. It's flashing older images (downgrading) that's a problem.
scryan said:
I am aware of the risks of flashing to older firmwares, but are their risks to flashing NEWER updates? I have seen people go as far as to recommend flashing the current version first to recover, then updating... But is this necessary?
Click to expand...
Click to collapse
The OTA updates are incremental, so you need to be on a certain level to take them. (to take 4.4.4 you need to be on 4.4.2, to take 4.4.2 you need to be on 4.4, etc)
Full SBF/FXZ files are complete roms. They are not incremental like the OTA Updates are. When flashing a FULL SBF/FXZ you can just flash it, so long as its the same version OR newer than what is on your phone, with no need to "step up." In other words, if you have 4.4 on your phone, you can flash directly to 4.4.4 using the full 4.4.4 SBF, without having to flash 4.4.2 on there first.
The risks to keep in mind would be, just like any update...
If you have a locked bootloader, the vulnerabilities exploited to root and disable write protection might be patched in the newer roms, that means you might not be able to root, or the processes may change for the newer rom. However, with an unlocked bootloader, there is no issue rooting and disabling write protection (lollipop is yet to be confirmed).
In either case, since you can't safely downgrade, if you find bugs, other issues (battery life, reception, etc), or there is something you don't like about the rom, you're stuck, since you can't safely downgrade.
THANK YOU SO MUCH every damn site I went to posted a link to a long dead server LIFE SAVER YOU ARE....
Method to go STOCK.
Hey,I'm currently on CM12/5.0.2 Official ROM for ghost[Bootloader unlocked & I had rooted my device for upgrading to CM12 obviously but now Root Checker says that my device is not rooted].My model number is XT1052(Asia Retail/India).I've found a link(but sadly can't post) for the stock ROM on FileFactory but I don't know the further steps to return back to stock.Before upgrading to CM12/5.0.2 I was on 4.4.4 and since Official 5.0.2 is just right around the corner I'd like to go stock(4.4.4). I'd be highly obliged.I've even downloaded a recovery file as posted by @flasherruts in his thread
"Stock Recovery 4.4.4 XT1052". Will your guide for Returning to stock work for me as well?Sorry but I'm new to this community.
Build Number: KXA21.12-L1.26
System Version:212.44.26.ghost_row.AsiaRetail.en.03
Model Number:XT 1052
Thanks in Advance!
the_fiasco said:
Hey,I'm currently on CM12/5.0.2 Official ROM for ghost[Bootloader unlocked & I had rooted my device for upgrading to CM12 obviously but now Root Checker says that my device is not rooted].My model number is XT1052(Asia Retail/India).I've found a link(but sadly can't post) for the stock ROM on FileFactory but I don't know the further steps to return back to stock.Before upgrading to CM12/5.0.2 I was on 4.4.4 and since Official 5.0.2 is just right around the corner I'd like to go stock(4.4.4). I'd be highly obliged.I've even downloaded a recovery file as posted by @flasherruts in his thread
"Stock Recovery 4.4.4 XT1052". Will your guide for Returning to stock work for me as well?Sorry but I'm new to this community.
Build Number: KXA21.12-L1.26
System Version:212.44.26.ghost_row.AsiaRetail.en.03
Model Number:XT 1052
Thanks in Advance!
Click to expand...
Click to collapse
http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515
I suggest you use this : perfect compatible stock firmware for xt1052 asia retail first gen moto x. : http://www.filefactory.com/file/3qr..._4.4.4_KXA21.12-L1.26_18_cid7_CFC_1FF.xml.zip pl. check it with someone else just in case if I'm wrong. pm me if you have any problems
Hey, thanks for replying!
Yeah, I found this stock recovery a while ago and downloaded it and now back to stock 4.4.4. Thanks a lot!
Sent from my Moto X using XDA Free mobile app
@KidJoe since filefactory is really slow, I searched for some alternatives and found some good ones, maybe you could add it to your 1st post?
Really good and fast overview page with most/all files, when you look for something, go here 1st:
https://cloud.mail.ru/public/64a43f0fcc1e/Moto_X or here:
https://cloud.mail.ru/public/a083d0bb5e97/Motorola
Big Thx to OP: http://4pda.ru/forum/index.php?showtopic=514209&st=8360
Some other alternatives:
XT1053 4.4.2; 4.4.3; 4.4.4 (downloading from mega server (fast!)), thx to OP (http://www.grupoandroid.com/topic/110743-aporte-firmware-t-mobile-retail-442/):
TMO_RETAIL_XT1053_4.4.2-KXA20.16-1.25_MR3_CFC.xml.zip: https://mega.co.nz/#!7RJygbQI!Sbx-bGRV8NbRsqLKS-d33nM_SEgY81czr8rye2ROYb0
TMO_RETAIL_XT1053_4.4.3-KXA21.12-L1.21_MR4_CFC.xml.zip: https://mega.co.nz/#!HQ4l2JIT!LD1gf8m2GxBou3NDFD8lzuxSi2OCn37X7Vhbe-hjNqc
TMO_RETAIL_XT1053_4.4.4_213.44.1.ghost_row.Retail.en.US_MR4_CFC.tgz: https://mega.co.nz/#!zIJhlSCS!o9B7xvRSJ9gTCdTYjXdmVActEmdWRBvhIVjs8JUHI8Q
XT1052_RETAIL-EU_4.4.4_KXA21.12-L1.26_54_cid7_CFC_1FF.xml.zip: https://yadi.sk/d/M2H9LMFJbYiag
from mega (fast!):http://www.mega.co.nz/#!jZgjECZT!sG0-9Vqngms551gwv9PfejY1mw_5QCL8Pg48KTVx4m0
XT1052_RETAIL-GB_4.4.4_KXA21.12-L1.26_56_cid7_CFC_1FF.xml.zip: https://yadi.sk/d/KLmLR43SbYiaX
XT1052_RETAIL-DE_4.4.4_KXA21.12-L1.26_54_cid7_CFC_1FF.xml.zip: https://yadi.sk/d/hDEHw2O-bYiae
For Brazilians user's
http://www.motoforum.com.br/topic/4...oto-g-2014-moto-e-moto-maxx-nexus-6-moto-360/
Does anyone know of a link that contains the Rogers 4.4.4 file? I need it to update to 5.1.
I have tried the filefactory link but after the countdown, the file is unavailable. I haven't seen any other links for it.
Thanks
I have the same problem. I've looked everywhere and cannot find the rogers 4.4.4 file.
If anyone has it download, could you please share with us.
Alternatively, would i be able to Flash XT1058_VIVO-BR_4.4.4_KXA21.12-L1.26_59_cid12_CFC_1FF.xml.zip since the build versions are the same?
I only need the 4.4.4 in order to install the Lolipop update.
Thanks
Hello guys,
I'm currently on Stock 5.0.1 rooted w/ TWRP.
Can someone explain to me hoy can I update to Marshmallow? When I look for updates in the phone nothing happens.
I've tried some threads but I can't get my head around this.
Thanks a lot
zuperpailon said:
I'm currently on Stock 5.0.1 rooted w/ TWRP.
Can someone explain to me hoy can I update to Marshmallow? When I look for updates in the phone nothing happens.
Click to expand...
Click to collapse
Unfortunately, absynte's guide is unlikely to work.
Have a look at your own past thread from October last year about the same query, which was answered & seemed to have been solved?
How to update to 6.0?
If not, follow erayrafet's advice there. Let us know if you need help to follow it.
Please don't keep opening a fresh thread for the same query - post in one thread from now on: either that one or this one (not both). Thanks.
absynte said:
Look at this post ,listen to the senior members
https://www.howtogeek.com/192402/why-androids-ota-updates-remove-root-and-how-to-keep-it/
Flash fire: Title:What to Do if Flashing the OTA Doesn’t Work
Click to expand...
Click to collapse
Unfortunately, FlashFire doesn't work well with Huawei phones. After posting this exact same suggestion in that previous thread, I tried it on my P6 despite the prior warning (see below), & true enough it didn't work. Thankfully, I easily managed to fix the resulting 'soft' brick by restoring a nandroid backup.
"- Added warning for Huawei users about brickability" (from the main FlashFire thread Changelogs post)
--------------------------------------
So zuperpailon, whatever you do or try, please make sure to create a prior nandroid backup with TWRP & transfer a copy of the backup to a computer or similar for safekeeping.
How to Back Up and Restore Your Android Phone with TWRP
How to Copy TWRP Android Backups to Your PC for Safe Keeping
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