Database Users

[HOWTO] Rooting + Wiping + Flashing : For the ultimate noob.

Note from rootsu:
XDA staff have transferred ownership of this thread to me so that I can update the rooting methods. The reason for this is because the rooting method contained within is outdated and since identified as unsafe.
I have PM'd the original OP @Stormlister to update the thread but unfortunately have received no response.
I aim to keep the structure of the thread in tact. I am only here to edit out / replace outdated and unsafe methods contained within this thread. The work below is not my own.
Disclaimer:
This guide is for total noobs (I am one myself). Until the information here can be confirmed by an experienced person please don't bet on the fact that this information is 100% accurate. I studied and put together bits and pieces of information that I found everywhere, tried it and it worked. I will mention the sources. Even though its probably not a good idea for a noob to write any sort of guide, these were taken from working sources, I have tried it myself and all works flawlessly.
About me:
I write open source software and also write documentation.
Why:
I wrote this tutorial as I found the scattered information all over kinda confusing on the subject of flashing, wiping and ROMS.
Who's it for?
You already know what you want to do, but don't know where to start.
THIS IS A WORK IN PROGRESS.
--------------------------------------------------------------------------------------------
Getting Started - Rooting
--------------------------------------------------------------------------------------------
Root means you are opening the operating system to allow a user or application full read and write access. This is needed by some special applications to change operating system files. For example the "Adfree" application changes system files to block certain domains which completely stops ads from showing up on your phone. Unlike other systems like in the iOS, all the root applications are available in the Google Play store, I think Google is great for allowing this.
The main thing I root first even though it is not needed to flash a rom is the fact that you ALWAYS need to make a backup, if something goes wrong you have a something to fall back on and the friendly xda community can help us get things running again.
The easiest way I found to quickly and safely root was by using the following software:
ODIN (Desktop software) (Incorrect usage may make your phone unusable.)
Before you start using Odin, make sure all the Kies* services on your desktop is stopped. (On Windows, you can press Ctrl+Alt+Delete, go to task manager, services and stop it from there). Infact you should consider uninstalling Kies altogether as it is really not needed if you are going to root. There are more than enough backup software that does not add the bloatware.
This piece of genius is a tool to flash among other things a new ROM to your phone.
We will be using this piece of software twice, first to root it, and then to flash your S3 with a new ROM.
------------------------------------------------------------------------------
<rootsu insert>
Recommended methods to "root" depending on your requirements...
1) You want root only. No custom ROMs, kernels etc. Just root, just to use root apps.
CF Auto Root Via Odin
Why? Tried and tested method, simple to use. No need to choose what exploit you want to use as it's tailored for your device.
What does it do? It gives you a stock recovery (so can't flash things) and roots the Android OS
The Steps:
1) Download the Latest Odin
2) Download CF-Auto-Root for your model
3) Follow These steps to root
2) You want to flash custom ROMs / Kernels
If you want root on your existing Android ROM, you can do 1) first. Then flash a recovery of your choice (CWM, Philz, TWRP) via Odin
However, if you immediately plan on flashing a ROM, there's no need to root your existing ROM. Simply skip straight to installing a recovery. Backup then flash what you like.
The Steps:
1) Download the Latest Odin
2) Download recovery of your choice CWM, Philz, TWRP
3) Follow The steps to Flash Philz recovery (But for the recovery of your choice)
These steps can also be followed to update recovery to newer versions
</rootsu insert>
------------------------------------------------------------------------------
Difficulty: Easy
After you have completed the tutorial your phone should be rooted and ready to go to the next step.
--------------------------------------------------------------------------------------------
Backing up
--------------------------------------------------------------------------------------------
The next thing we will need to do is backup our current apps, settings and even ROM. Now that the phone is rooted we can install a few applications to help with this process. Lets do this now.
In Google Play Store, search and install:
Titanium Backup (Google Play)
With this tool, you will be able to backup application and settings of your current installation.
To do so;
Open Titanium Backup
At some point it will ask for root access, you will need to allow it root access.
Click on Backup/Restore.
It will show you a list of software.
Click the ok tick top right.
It will now show a list of actions you can take.
You will now [ RUN ] Backup all user apps+ system data.
It will flip to a new screen, click top right ok tick again.
The backup process will take a few minutes.
After the backup completes, we will need to copy it to a safe place, just in case something else goes wrong.
With above explained, there are more optimized Titanium Backup methods, this is a must read:
http://checkrom.com/threads/titanium-backup-explained.433/
You could also backup your whole system from the boot menu of ClockWorkMod / custom recovery - which you will already have if you used the rooting method above. Have a look at this short yet very informative video to do just that:
http://www.youtube.com/watch?v=sPvNr7LqP30&feature=related
Difficulty: Easy
Bear in mind that custom recoveries vary, they all work pretty much the same. The backup is referred to as a "nandroid" backup, but in the recovery menus, it may well be referred to as simply "backup and restore".
To boot into whichever custom recovery you have installed, power off the phone. From off, hold Volume Up + Home then press and hold Power until the S3 splash screen shows. Release power. Once in recovery, find the backup and restore menu and take a backup.
There is one more place you need to manually write down some settings, the APN for your data and MMS, this is the only area besides the branding when another countries stock rom might affect you if you chose to use it. So head over to;
Settings->More Settings->Mobile Networks->Access Point Names.
Click on each and write down its settings.
Backing up EFS folder
---------------------------------------------------------------------------------------------------------------------
The EFS is a filesystem folder which contains important information like for instance your IMEI (International Mobile Equipment Identity) number, even though I cant find any evidence that anyone lost their EFS folder yet, I think it is probably important enough to back it up. First open your favorite file browser like ASTRO and click on your internal build in sdcard0 and see if you have a efs_Backup folder. If you have such a folder its is probably backup up inside already. To be honest, I dont know what backed mine up, but it was there, and it will be likely there if you followed the procedures listed in the collection of this tutorial.
However, the folder is only 6mb, if you don't have such a backed up folder, using an application like KTOOL, gives you the ability to backup the whole "/efs" folder to wherever you like. The external SSD and also your PC would be a good idea to back it up to.
----------------------------------------------------------------------------------------------------------------------
Difficulty: Easy
--------------------------------------------------------------------------------------------
ROM - Hunting for a new rom
--------------------------------------------------------------------------------------------
************************************************************************************************************
My ROM is not YOUR ROM
But I have an S3, wtf is this? Note that when hunting for a ROM that you make sure it is either based on your models ROM or supports your models ROM. The reason this should be noted is because the models are so profoundly different, from Dual Core to Quad Core, from 1GB memory to 2GB memory etc. This means each ROM is optimized of based on a specific model. If you have the GT-I9300, you have the most popular model which has a lot of custom ROMS.
Read more about the differences here:
http://forum.xda-developers.com/showthread.php?t=1870827
************************************************************************************************************
This is where I got confused, I did not know if I had to match the code base of my factory stock rom to the rom I wanted. I was afraid that it might flash my modems software making my phone unusable with my service provider. It seems that the rom file is only to flash the actual OS and wont include the modem flash too.
So what ROM to pick, there seems to be very good ROMS out there, but know, the further you go away from the stock rom, the more difficult things become. You might just want to upgrade to the latest Jelly Bean and not worry about an improve stock Samsung rom. Or you might want to take it to a whole new level and perhaps install a pure Android rom (however, I noted a few people having trouble with the pure android rom, you really need to know what you are doing). But as I say, it seems things gets kinda tricky the further you move away from the Stock Rom.
Lets look at a few examples of solid roms:
At this stage we only have one stock rom available in Jelly Bean, this is most probably the safest bet when you only want to upgrade to Jelly Bean (If you do decide to just go with the safest rom, you can just root again after the rom was successfully flashed) [INTERNATIONAL GALAXY S3 ONLY] [DONT USE THIS ROM ON ANYTHING ELSE THAN INTERNATIONAL VERSION (IT WONT WORK)]:
http://forum.xda-developers.com/showthread.php?t=1646610
Now we can start looking at roms based on stock roms that was improved by a linux guru, very good example of such a rom which is very solid is Android Revolution HD, if you have other Samsung devices I would recommend sticking to this one as it comes stock with Allshare Play:
http://forum.xda-developers.com/showthread.php?t=1797334
The most popular OMEGA rom for the S3 international, pure awesomeness:
http://forum.xda-developers.com/showthread.php?t=1663656
Then you get completely customized roms like Cyanogenmod, this is next level roms and should probably only be tried once you are more confident with flashing ( . Y . )
Note that Cyanogenmod is very controversial for the international version of the S3, there are technical issues, and newer stable version is always behind, I would NOT go for Cyanogenmod at the moment..
http://www.cyanogenmod.com/
For a very nice list of roms and some explanations have a look at:
http://forum.xda-developers.com/showthread.php?t=1674286
Now that you have your rom, lets continue.
Difficulty: Easy
--------------------------------------------------------------------------------------------
Wiping & Flashing - Cleaner Flashing Method
--------------------------------------------------------------------------------------------
[I will try and confirm all my findings below]
When people refer to the term wipe, it is my understanding that it means to delete the old ROM from various locations. This ensures a more clean installation, almost like its better to install Windows afresh instead of an upgrade. However, this is not Windows, its Linux, I am sure the logic behind this is because the way Linux works, it has certain files in certain directories, that if the file is there, the service is loaded automatically. Now if you had to replace a stock rom with something completely different, some of those auto loaded files will be left behind and you will be stuck with loaded services that should not be there. But this is just my experience, I am not sure if this completely accurate.
This is where things might start becoming slightly confusing. Many people seem to argue that when upgrading from a stock version to another stock version that you don't need to wipe, I completely agree with this, as this will almost be the same upgrade process the default upgrade will follow.
However, if you upgrade to a very different ROM, start paying attention, as things might just get slightly more complicated. This I have not tried myself yet, but it seems that for this to work you wont need Odin.
Some people also recommend formatting and not just deleting, I will even advice against this, this is the EXT4 filesystem, not some NTFS filesystem. I cannot see the real benefit of formatting.
At this stage I don't know how to wipe the phone if you are going to use the alternative Odin flashing method explained below, this I have done, tried and tested, working fine:
[Below method I use to flash my own international S3]
This is what you will be doing to install a custom rom while wiping it for a fresh install (make sure you have your titanium backups handy ):
Copy your ROM inside an easy locatable phone folder by browsing to it, from your PC and copying it to your phones folder using your micro USB cable. I strongly recommend using your External SD card as some roms may wipe your internal SD card leaving you without any ROM to update.. that will be very sad. :crying:
Boot into recovery (Vol up + Home + power from off)
You will see a new Unix like screen appear, use volume + and - to navigate up and down, home button is enter, and soft touch back button back is back.
Next we will wipe the phone (if your ROM does not have special instructions on wiping this is a standard method).
Goto Wipe Data/Factory Reset -> Yes
Goto Wipe Cache Partition -> Yes
Goto Advance -> Wipe Dalvik Cache -> Yes
Next Select Install Zip from SD Card (You may also mount External SD card and load ROMS from external SD card (I can recommend this))
It will take a while...
Reboot, and hope to god all is good.
I can confirm above works perfectly, I have flashed HD Revolution ROM successfully using above method.
BUT PLEASE BE WARNED: HD Revolution recommends using Super Wipe, the instructions are unclear, it says you must copy it to the your sd card, if you do this and copy it to your internal sd card all will be wiped including your images, I think you are screwed then. Rather copy them to your EXTERNAL SD card and choose zip from EXTERNAL SD card.
Or you can see a very clear example video of how to wipe data from your phone in preparation of a new rom;
Be aware, this video shows that you should UNLOCK your bootloader, some phones wont boot after this, don't do it except if you know you have to.
http://www.youtube.com/watch?v=EJUCOtX1cUk
Difficulty: Medium
--------------------------------------------------------------------------------------------
ALTERNATIVE Flashing - With Odin
--------------------------------------------------------------------------------------------
If you have not followed the wiping method and you will just be going for the stock updated rom, you should not be needing any wiping, you can just download the stock rom as linked and follow this great guide:
STOCK ROM:
http://forum.xda-developers.com/showthread.php?t=1646610
ODIN GUIDE
http://forum.xda-developers.com/showthread.php?t=1671969
Difficulty: Medium
--------------------------------------------------------------------------------------------
Restoring your data
--------------------------------------------------------------------------------------------
After you have are done with a successful flash, we want to recover our apps, but its not just a matter of recovering everything, it will be a mess if you do that.
Many people carry out a backup before installing a custom rom and didnt really understand what kind of backup they should of carried out and have just gone with what they have seen, WRONG!!! when it comes to custom roms there is only one type of backup you can do.
Custom roms have their own system files and dont like other system files being installed over it, you will definitely have rom problems if you carry out this kind of restore from a backup over a custom rom.
When using Titanium Backup its important not to use the settings - backup all system data and backup all user apps + system data, you cant use these with a custom rom, so dont try this kind of backup, this kind of backup is to restore your phone back to its previous state, should something go wrong with the rom installation.
Click to expand...
Click to collapse
Read more detail here:
http://checkrom.com/threads/titanium-backup-explained.433/
Difficulty: Easy
--------------------------------------------------------------------------------------------
Getting rid of bloatware
--------------------------------------------------------------------------------------------
If you went for a stock based ROM, you might want to get rid of all the SAMSUNG bloatware that sits in memory and really never gets used.
This is mostly all the "S" software like "S Suggest", I believe not a lot of people is going to use this for instance. And one can't simply uninstall it as it is hiden from uninstalling.
There is a very easy way if you are rooted though (another reason to root). Simply install the little greatness called "Nobloat Free" from the Play store.
Now select those bloatware you dont want and simply uninstall. But make sure it might not be useful for yourself. To give you an idea, "AllShare Play" might sound useless, however, if you have a XBMC media pc, by simply enabling "PNP" in the configuration, you can display photos and videos instantly from your G3, does not matter where you are in XBMC.
Difficulty: Very Easy
--------------------------------------------------------------------------------------------
Unrooting and getting back your Warranty!
--------------------------------------------------------------------------------------------
At some stage you might want to sell your phone or it is giving you hardware issues that has nothing to do with software. At this stage you want to reset the phone to it 100% factory state and status. It is completely possible, unfortunately it wont work to just update the rom to the stock factory rom as there are built in counters and status writes who flags the phone as modified. However, by following these tutorials, you can quickly reset your phone.
You will need the factory rom for your country, this can be downloaded here:
http://www.sammobile.com/firmware/
Then watch both of these tutorials and decide which one you feel the most comfortable with:
http://www.youtube.com/watch?v=ZEI_c1R0_nQ&feature=related
And another approach to regaining your warranty:
http://www.youtube.com/watch?v=TEsBwtqY2xE&feature=related
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Oops, if you are stuck on a crossroad and you think you might have bricked (term used to define the fact that you made your phone unusable) your phone, following this tutorial will help you out:
http://www.youtube.com/watch?v=ypmqJbZqOaU&feature=related
Difficulty: Easy
--------------------------------------------------------------------------------------------
Thanks to everyone
--------------------------------------------------------------------------------------------
I just want to say thanks to the wonderfully smart people who makes rooting possible. It is amazing how much more fun some people can make the life for other. I truly appreciate every bit of it.
Also special thanks to xdadevelopers who keeps an awesome community together.
Odin Greatness!
CF-Root
SuperSu
CWM
CWMManager
ClockworkMod (WTF, this is omg awesome!)
Titanium Backup
Adfree
--------------------------------------------------------------------------------------------
Congrats on your new firmare!
--------------------------------------------------------------------------------------------
--------------------------------------------------------------------------------------------
FAQ
--------------------------------------------------------------------------------------------
JiiNDER said:
Hey I want to thank you so much for your guide! It actually makes rooting a lot easier. I had one question though, if I root and a new official firmware comes out, can I still update to the latest stock rom with Kies even though I will lose my root.
Click to expand...
Click to collapse
It all depends what ROM you loaded, if its not the default factory ROM or based on it, you will have to follow the instructions of the CUSTOM rom provider on how an upgrade should be achieve. Else simply use the newest default rom and simply re-root, should be a very quick to do. Also, dont use KIES if you have already rooted, rather use ODIN and follow the instructions. NOTE: KIES, if left running will make ODIN behave incorrectly.

just a slight correction/heads up.... if you root with cf root then cwm recovery is installed, hence no need to use Rom manager, it's kinda outdated now imho
---------- Post added at 05:51 PM ---------- Previous post was at 05:49 PM ----------
further to that you may want to provide instructions after the rooting process on how to get into recovery and download mode

slaphead20 said:
just a slight correction/heads up.... if you root with cf root then cwm recovery is installed, hence no need to use Rom manager, it's kinda outdated now imho
---------- Post added at 05:51 PM ---------- Previous post was at 05:49 PM ----------
further to that you may want to provide instructions after the rooting process on how to get into recovery and download mode
Click to expand...
Click to collapse
Thanks, I will note that above.

The stock rom at the bottom goes to the international version rom. I found this thread in the Sprint version so u might want to note that. If someone were to flash that they wouldn't boot up.
Sent from Galaxy SIII

Added many corrections.

musclehead84 said:
The stock rom at the bottom goes to the international version rom. I found this thread in the Sprint version so u might want to note that. If someone were to flash that they wouldn't boot up.
Sent from Galaxy SIII
Click to expand...
Click to collapse
Could you please explain why you think it wont boot, what exactly would be different that wont make it boot. I believe it will?

Great tutorial for the noobs. Would be really useful for them. :thumbup:
Sent from my GT-I9300 using xda app-developers app

Stormlister said:
Could you please explain why you think it wont boot, what exactly would be different that wont make it boot. I believe it will?
Click to expand...
Click to collapse
Different CPU's, different kernels, different drivers, different partitions, different radios and tech (one being GSM the other being CDMA) and the list goes on...

graffixnyc said:
Different CPU's, different kernels, different drivers, different partitions, different radios and tech (one being GSM the other being CDMA) and the list goes on...
Click to expand...
Click to collapse
Thanks for the feedback man... will mark it as International Only.

I had question regarding Odin behaving strangely, make sure KIES is stopped in your services. I have added it in the tutorial.

Stormlister said:
I had question regarding Odin behaving strangely, make sure Kiss is stopped in your services. I have added it in the tutorial.
Click to expand...
Click to collapse
Do you mean Kies ? (Samsung) good tut for super noobs btw
Sent from my GT-I9300 using xda app-developers app

i would recommend you to recommend not installing Kies at all, or uninstall it if installed.
any backup that you can do with it, can be done by 3rd party apps. it has a lot of security issues. and worst, its slow as hell.
i think a person that want to root his phone and flash a custom rom, will have no need of it anyway.
Edit: thumbs up for the effort! i could have really used such guide when i just started, instead i learned it the hard way!

OverRipeBananas said:
Do you mean Kies ? (Samsung) good tut for super noobs btw
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
Yes, yes Kies, thanks for spotting it

Thanks, I'll try this soon! Glad I found this, voiding warranty still sounds scary. I have other rooted devices and sometimes they can blow me away, so I think I'll go for it anyway.
Cheers.

MrEdgar said:
Thanks, I'll try this soon! Glad I found this, voiding warranty still sounds scary. I have other rooted devices and sometimes they can blow me away, so I think I'll go for it anyway.
Cheers.
Click to expand...
Click to collapse
I personally think it is well worth-it, it is almost as if the phones turns into mini super computer when rooted. It is so much fun to have a ROM installed and setup that you are completely happy with, removing bloatware, no intrusive ads. Just stay away from overclocking, I think that is taking it too far if you are a scary pants like myself.
Also, you know how the retailers are, they almost never deliver on their warranty anyway.

No offence, but given this guide is designed 'for the ultimate noob' AND it has been stickied, there are some glaringly obvious things missing, that should be cover at the beginning of your post/guide before hitting the processes of
In the first post, you do not cover information pertaining to the flash counter and triangle away, and most importantly by far, BACKING UP THE EFS. Also, possible risks from installing potentially malicious apks from 'other sources' to a rooted device.
Sent from my GT-I9300 using xda app-developers app

Good job! :good:

bootx1 said:
No offence, but given this guide is designed 'for the ultimate noob' AND it has been stickied, there are some glaringly obvious things missing, that should be cover at the beginning of your post/guide before hitting the processes of
In the first post, you do not cover information pertaining to the flash counter and triangle away, and most importantly by far, BACKING UP THE EFS. Also, possible risks from installing potentially malicious apks from 'other sources' to a rooted device.
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
None taken, but in a community it works like this. We build a tutorial together. Instead of taking the time pointing out what you think is missing. Why did you not just write the part so I could add it? This tutorial is based on the international version, I am not sure if the triangle notification does not affect this version but I could not test it as I did not ran into this problem.
Regarding the EFS, I will do some research regarding this and add it to the tutorial.

I have added detail on backing up EFS folder and also triangle away.

CF-Root 6.4 - SuperSU+CWM5.5+CWMManager does not work on stock JellyBean Firmware right?

[WIP/TBD][5.0.1][LRX22C][YT2-830F][SleepyBear 830F: Feedback Needed!]

**NOTICE: Due to unforeseen circumstances - my car's starter died, and I had to return my Yoga 2 for emergency cash - ROM development is on hiatus. Best Buy has put back a brand new Yoga 2 for me when payday comes again, provided I can eek it out.
I thought of a GoFundMe to help pick one up, but I didn't feel comfortable doing this.
Updates will come as available. Again, I am so sorry.
This ROM is for the **LENOVO YOGA TABLET 2-830F ONLY!**. You are responsible for your device and its warranty, health, happiness, sanity, love and abuse. The initial release will come over the next couple of weeks. I wanted to throw up this post to get your feedback and get a few folks to beta test. I have been using it as my daily driver for over a week, and all has been well
Android Lollipop source (provided via Lenovo's Open Source documentation):
http://support.lenovo.com/us/en/products/tablets/yoga-series/yoga-tablet-2-830/downloads/DS102874/
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
SleepyBear - A gently modified and streamlined Lollipop ROM for the YT-830F This ROM is based off of Lenovo's stock Lollipop ROM for the YT-830F (.LRX22C.YT2-830F_USR_S100067_1507101258_WW52_ROW)
Introduction
Last year, I spent a lot of time pouring over the Dell Venue 7840, one of the first "mainstream" Intel x86-based Android tablets to hit the market (Intel Z3580 - Mooresfield). There was nothing in the way of custom ROMs available, so I maintained a KitKat 4.4.4 ROM for the handful of XDA folks that were using it. Fast forward - I have been using the Yoga Tab 2-830F for about a month, and its story is quite familiar - Intel Z3745 Baytrail, 64-bit Android, also one of Intel's premier devices pushed to devs for its foray into the Android market.
I have been using Android-based devices since 2010, and it's been nothing but fun - handsets, smartphones, tablets, media centers, USB system-on-a-chip and a couple of those tiny set top boxes that go well with XBMC/Kodi. I can't much deal with vendor UI overlays, bloat and the like. Thanks for the work of so many XDA comrades, I have received so much. In return, I'm trying to give some back.
Features
This ROM is based on Lenovo's stock Lollipop 5.0.1 update for the YT-830F (LRX22C/.YT2-830F_USR_S100067_1507101258_WW52_ROW). The image can be flashed via ClockworkMod using the Tethered CWM method. For now, I would all but recommend that you already have the Lenovo Lollipop OTA already in place and are comfortable. The finer points of that process might be malleable later.
ROM Details:
SleepyBear v1 - TBD December 2015
* Android 5.0.1 (modified Lenovo Lollipop stock ROM)
* ROOTed via SuperSU 2.52
* Xposed Framework v78
* NTFS/CIFS filesystem support
* Debloated (Nova Launcher beta instead of Lenovo's UI. The uptick in responsiveness is almost absurd)
* Deodexed
* Zipaligned
* BusyBox
* Init.d
* SD card write fix
* Stock kernel optimized (Interactive governor, cfq scheduler, 512KB read-ahead - Best balance of multitasking, performance and battery life)
* AdAway
* YouTube AdAway (Xposed module)
* YouTube Background Playback (Xposed module)
* Android Terminal Emulator​
Installation
1. SleepyBear v1 COMING LATER THIS DECEMBER. LINK WILL BE HERE.
2. Copy the folder to the microSD device of your YT-830F - more than likely /clockworkmod/backup
3. Boot the device to ClockworkMod Recovery using the instructions for the Tethered CWM method.
4.

:good:
From my LG-G4, Rooted running Stock 5.1

Nice stuff. I'm on the Yoga 10 inch (1050F) so I can't really test this ROM, but hopefully this is the start of custom ROMs for the Yoga range.

Wohoo :victory:
Thanks for your work! Finally the waiting for a custom rom is over :highfive:
I will definitely test this rom in the next few days, but first of all: Am I blind or where is the link for downloading the files?
And my second question: will it be possible to make a clean install with a flashable zip? Since the bootloader can be unlocked with the method ionioni provides in his thread it should be possible, right?

1subw00fer1 said:
Wohoo :victory:
Thanks for your work! Finally the waiting for a custom rom is over :highfive:
I will definitely test this rom in the next few days, but first of all: Am I blind or where is the link for downloading the files?
And my second question: will it be possible to make a clean install with a flashable zip? Since the bootloader can be unlocked with the method ionioni provides in his thread it should be possible, right?
Click to expand...
Click to collapse
@1subw00fer1 - correct, there is not yet a download link. I'd like to get some Yoga Tab 2 8-inch owners (YT-810F only for now) to test this out.
Now that I've gotten some sleep, I'm going to put my device back on KitKat, firmware and all, and flash this ROM to make sure both firmware and OS load correctly. It *should*, given that I am using a full ClockworkMod backup that contains boot, recovery, data and a couple of low-level partitions. If that works, then you could do the clean flash via tethered CWM.
I am also using NAndroid Manager to build a full, flashable ZIP that I'll be testing with tethered CWM. I don't see any impediments to doing this. We shall see.
I'll try this with both locked and unlocked bootloader. Details will be added to the main post.
@workdowg - care to test it on the 1050? - we could tweak the partition layout if need be.
Does that answer your questions?

F1Fanatic27 said:
Nice stuff. I'm on the Yoga 10 inch (1050F) so I can't really test this ROM, but hopefully this is the start of custom ROMs for the Yoga range.
Click to expand...
Click to collapse
@F1Fanatic27 - do you have unlocked bootloader on your 1050F? Are you you versed on using the Tethered CWM and doing system image backups, etc.? If so, I'd like some folks to try with this model.

1subw00fer1 said:
Wohoo :victory:
Thanks for your work! Finally the waiting for a custom rom is over :highfive:
I will definitely test this rom in the next few days, but first of all: Am I blind or where is the link for downloading the files?
And my second question: will it be possible to make a clean install with a flashable zip? Since the bootloader can be unlocked with the method ionioni provides in his thread it should be possible, right?
Click to expand...
Click to collapse
I have updated the Installation section with mention of ETA for the first release.

jumpup said:
@F1Fanatic27 - do you have unlocked bootloader on your 1050F? Are you you versed on using the Tethered CWM and doing system image backups, etc.? If so, I'd like some folks to try with this model.
Click to expand...
Click to collapse
Oh yes definitely willing to try it out. I reflashed Lollipop a few days ago so my bootloader's not unlocked at the moment, but I know how to do it so I can get it done in a jiffy. As for CWM, I've been using TWRP for a while now, but a few minutes with CWM and I should be re-accustomed.

F1Fanatic27 said:
Oh yes definitely willing to try it out. I reflashed Lollipop a few days ago so my bootloader's not unlocked at the moment, but I know how to do it so I can get it done in a jiffy. As for CWM, I've been using TWRP for a while now, but a few minutes with CWM and I should be re-accustomed.
Click to expand...
Click to collapse
@F1Fanatic27 - EXCELLENT! Here are a couple of preliminary tasks that will verify CWM:
1. Make a full CWM backup of your device.
2. Reboot and make sure your Android instance is still functioning
3. Perform a full restore of the CWM backup from Step 1.
4. Reboot once more, and make sure Android is still good.
Let me know if that's good.

jumpup said:
@F1Fanatic27 - EXCELLENT! Here are a couple of preliminary tasks that will verify CWM:
1. Make a full CWM backup of your device.
2. Reboot and make sure your Android instance is still functioning
3. Perform a full restore of the CWM backup from Step 1.
4. Reboot once more, and make sure Android is still good.
Let me know if that's good.
Click to expand...
Click to collapse
Well, almost good. The backup was fine, but after the restore the tablet hung on boot and after about 30 seconds loaded recovery instead. :crying:

F1Fanatic27 said:
Well, almost good. The backup was fine, but after the restore the tablet hung on boot and after about 30 seconds loaded recovery instead. :crying:
Click to expand...
Click to collapse
Really? Download and flash the your model's LL OS Loader from the first post.
Damn!
@F1Fanatic27
Was your bootloader locked or unlocked when testing this?

jumpup said:
Really? Download and flash the your model's LL OS Loader from the first post.
Damn!
@F1Fanatic27
Was your bootloader locked or unlocked when testing this?
Click to expand...
Click to collapse
Unlocked.

F1Fanatic27 said:
Unlocked.
Click to expand...
Click to collapse
I would reflash the OS loader for your device. Let's see if that fixes the issue. If this does not fix it, follow that up by locking your bootloader.
In the interim, download your device's last Lenovo OTA update and the Intel Flash utility

jumpup said:
I would reflash the OS loader for your device. Let's see if that fixes the issue. If this does not fix it, follow that up by locking your bootloader.
In the interim, download your device's last Lenovo OTA update and the Intel Flash utility
Click to expand...
Click to collapse
Well reflashing the OS loader and locking the bootloader haven't put me back on track. You mentioned the Intel flash tool and the OTA update which I already have. Anyway I can flash the update without losing data? I tried with stock recovery but it basically told me the build number was wrong (i.e. you're supposed to flash from KitKat to Lollipop, not Lollipop to Lollipop!!) and restoring the Kitkat bios hasn't changed the situation.

F1Fanatic27 said:
Well reflashing the OS loader and locking the bootloader haven't put me back on track. You mentioned the Intel flash tool and the OTA update which I already have. Anyway I can flash the update without losing data? I tried with stock recovery but it basically told me the build number was wrong (i.e. you're supposed to flash from KitKat to Lollipop, not Lollipop to Lollipop!!) and restoring the Kitkat bios hasn't changed the situation.
Click to expand...
Click to collapse
You mentioned previously that you had been using TWRP. For the sake of redundancy, I'd suggest making a full backup with it as well.
With either CWM/TWRP, try restoring only SYSYEM and DATA partitions. See if that help.
If you end up having to restore stock via Intel Flash utility, you can use an app called Online NAndroid Backup and NAndroid Manager to open up the image and manually choose which apps (and data) you want to restore.
You would restore this data after you reapplied the stock image to your system. The apps require root.
Moving forward, I'd also suggest investing in Titanium Backup. Always do a full backup of user, system apps and data. With that, you'd just root your fresh stock and restore with the TB app. I do that for multilayered protection.
I will post the app links later this morning. Gotta get in to the office right quick
Lastly, with the Intel flash util, have you tried restoring just boot and recovery? A partial restore. Don't forget the 'Sparcing' setting.

Thanks again. I already reflashed KitKat and then updated to Lollipop before I saw your post, but the online Nandroid Manager thing sounds shockingly useful!! I'll see about restoring the apps from the backup.
Meanwhile I should probably start using Titanium Backup with this tablet, somehow never thought of doing so as I am with my LG G4.

F1Fanatic27 said:
Thanks again. I already reflashed KitKat and then updated to Lollipop before I saw your post, but the online Nandroid Manager thing sounds shockingly useful!! I'll see about restoring the apps from the backup.
Meanwhile I should probably start using Titanium Backup with this tablet, somehow never thought of doing so as I am with my LG G4.
Click to expand...
Click to collapse
So, you were able to restore your Yoga tablet with the Intel flasher and OWA. Is that correct?
Thanks for boldly going where no Yoga user has gone before.
I am keeping notes on everything and will update you all after I test a few scenarios and options.
For all reading, the following are important prerequisites for a project like this where no custom recovery and the like make the scenario different:
- Titanium Backup: Make a full apps+data backup in Android with this app
- Make a full backup with tethered CWM
-Make another backup with tethered TWRP
I still need direct 830F testers or models close to this.

jumpup said:
So, you were able to restore your Yoga tablet with the Intel flasher and OWA. Is that correct?
Click to expand...
Click to collapse
Yep, Intel flasher for Kitkat and then standard OTA update for Lollipop. Can't wait for the ROM!!

F1Fanatic27 said:
Yep, Intel flasher for Kitkat and then standard OTA update for Lollipop. Can't wait for the ROM!!
Click to expand...
Click to collapse
And, to confirm, you were running Lollipop at the beginning of all this, right?
Sent from my SM-N910T3 using Tapatalk

Status Update: I am working with a few of the better deodex/zipalign/etc dev apps to find one that's a good feel for the Yoga. Things like the following:
http://forum.xda-developers.com/showthread.php?t=2360670
Anyone familiar with these tools that prefer any one over the other?

[Root][FIX][S8+]Root Green Screen/Corruption FIXED with AQI1 COMBINATION Boot Firm

Greetings!
Allow me to present to you:
How to Dramatically improve your Rooted S8 Display Quality
And Eliminate the Green/Garbled Screen bug
NOTE: Some users are still experiencing the green/garbled screen issue after flashing.
However all reports of this have indicated that it is happening noticeably less frequently.
Update:
I am looking into this and will have some changes out shortly that will hopefully help. It is difficult for me to troubleshoot because I literally can not get it to happen to my phone anymore so it is difficult to verify improvements before shipping them out to you, but I am doing my best.
​
WHAT?!
I found the following today while digging around chinese phone firmware sites via baidu:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
In case you can't tell what that is, it is a BRAND NEW "Combination" Firmware with the label AQI1. The combination firmware is a special factory image used by service workers and XDA members who want to do things like change their CSC or bypass a FRP lock. meaning its almost completely brand new! AQI1 stands for "September 2017", which means this is a brand spanking new image only a few days old!
WHO CARES?
Why is this important? Well it just so happens that the Combination firmware boot image (boot.img) is what we all flashed as part of the SamPWND root. The boot.img file contains the kernel and root filesystem ramdisk. We were running one from sometime around April, which is very old compared to the modern builds most of us flashed after rooting. Furthermore, the image we all are currently running is likely one of the first kernels rolled out for the phone, so its no wonder there was an issue like this that was not fixed (who cares if you get greenscreen in 5m of CSC update).
So all it takes is a simple flash in FlashFire of the AQI1 boot.img (provide at the bottom of this post), an operation that does NOT require a wipe of /system, /data, or anything really (although I recommend a cache wipe in recovery for good measure, but it is very likely not necessary). Your phone will just come back up with a slicker modern kernel and most of all NO MORE ANNOYING DISPLAY BUGS!!!
WHAT IT IS NOT:
Now that I have explained what this thread is about, I wanted to outline a few things it is NOT about, to make a valliant effort to stem off the flow of questions before they begin (ha!):
NOT: A new Stock ROM for Your Phone
THIS IS NOT A FULL OS BUILD! DO NOT DOWNLOAD THE WHOLE THING AND FLASH IT EXPECTING AN UPGRADED OS.
This is ONLY the special factory / Combination CSC and diagnostic ROM that has been floating around forever, just a modern build.
It is also the ONLY AQI1 image I have found. Believe me I looked a bunch of places after I found it
NOT: Oreo Early Preview
Given the predictions that the next release from Samsung would likely be Oreo, there was some initial over excitement. This wound up being NOT the case and if you read at least current Samsung Oreo projections they are predicting AQB now.
NOT: A Fix for the 80% Battery Issue
I know this is completely futile to hope for but:
THIS DOES NOT FIX THE 80% BATTERY ISSUE!!!!
NO WE DO NOT HAVE A FIX FOR THAT OR ONE COMING ANY TIME SOON!
YES SOME PEOPLE ARE STILL TRYING!
PLEASE DO NOT ASK! OFF TOPIC FOR THS THREAD
NOT: Currently Tested by ANYONE
I tested this on my S8 G950U but I don't have an s8+ to test with. I imagine that it will work the exact same way but I can't be sure. Hopefully some of you early adopters can share your results with the thread so that we can build some confidence here
NOTE: This is for the s8+ G955 US Snapdragon models ONLY! Do NOT Flash this on your exynos, your Chinese/HK S8, your N8, your MOTO RAZR flip phone, whatever else you have. Kernels/boot.img files are very device specific and you will surely break it if not completely brick it. See the other thread if you have a regular S8 US Snapdragon model.
DISCLAIMER:
YOUR WARRANTY IS ALREADY VOID if you are paying attention and are doing this to fix bugs with the existing sampwnd root.
HOWEVER IT IS EVEN VOIDER NOW. FLASH THUS TO YOUR DEVICE AT YOUR OWN RISK!
and if you break it I AM NOT RESPONSIBLE! FLASH AT YOUR OWN RISK!
As I said I have not tested this anywhere as I don't have an s8+
STEPS
Download Boot Image
Use the URL here to Download the AQI1 boot.img file: G955USQU1AQI1 BOOT.IMG
Prepare Phone for Flashing in FlashFire
If you did not download it on your phone, copy it somewhere FlashFire can see it.
Flash it
Open up FlashFire
Hit the "+" button
Select the "Flash Firmware Package" option, NOT the "Flash Zip or OTA" option!
You should see a popup window thing that has a checkbox next to the word BOOT, with "boot.img, 22MiB" underneath.
Make sure the checkbox is checked.
Make sure that it says BOOT above boot.img.
I have no idea if its possible for this to get messed up, but BOOT implies flashing the BOOT partition so if it says something else you are headed towards brick town, abort immediately.
Press the Check mark at the top right corner once you have confirmed the two things above.
MAKE SURE EVER ROOT IS DISABLED!!!
Click on the "Reboot" box, and choose "Recovery". MAKE SURE PRESERVE RECOVERY IS NOT CHECKED!
Back at the main menu, click the lightening bolt next to the word FLASH. Confirm.
Wait for FlashFire to do its thing. Sometimes it takes a minute for FF to wake up and start flashing. Occasionally for me it never happens, if this happens DO NOT PANIC ITS FINE. Hold down power+volDown until you eventually wind up in upload mode, then just reboot normally and everything will come back fine.
When FlashFire finishes (it will go really fast, the image is only 22MB we arent flashing a 5GB system here), it will auto-reboot your device into the recovery men
Select Wipe Cache and Confirm
This will wipe cache which is fine and safe. Again maybe not needed, feel free to skip if you know what you are doing. If you mess up and factory reset your device tell me so I can laugh at you.
Reboot into a Clear New World
Select reboot and boot the system normally. If you formatted the cache partition above, it will take a little longer to start your phone. This is just the first time per normal.
Thats it! Welcome to the world of clear screens and bright colors. It could be a total placebo effect but I actually think this kernel drives the display better sometimes.
Please let me know what you think, and if this works for you. I will be here for a while to answer questions or fix anything i typoed above or whatever.
FYI: There is an s8 thread in the s8 forums, if you have one of those use that method. There absolutely are binary diffs between versions so SOMETHING is different, and Id rather not have your briked phone on my concious.
SPECIAL THANKS TO:
@elliwigy and @stf_TimelessGoD and the rest of the SamPWND crew for getting us this awesome root in the first place
@elliwigy again for turning me on to the fact that this was a thing at all
@jhofseth for nerding out with me the last few nights on trying crazy **** to get a bootloader unlock which prompted me to dig at this in the first place
Most of all, the tons of you out who have made so many awesome mods, themes, apps, workarounds, tools, etc etc etc. What you have made I use every day and all of it makes me enjoy my device all the more. I could not be happier to have the opportunity to give back a little.
BONUS: Here is a link to the entire combination image if you want to take a look at the rest of it. Don't flash the rest of it if you don't know what it is, as it wipes everything and you will have to root from scratch again!
http://goo.gl/pYyg7s

@wildermjs8 thanks for digging around. If we flash this and have problems what is the best way to go back?
UPDATE: got impatient and flashed per your instructions and all seams ok so far. Shows Sept 4 kernel version in about phone. Will update later. Thanks again

This can be flashed over AQH3, right ?.

jawonder said:
This can be flashed over AQH3, right ?.
Click to expand...
Click to collapse
why not? as long as its not incremented you are good.. u could prolly even dd it if u want

Working ok for me .

mopartonyg said:
@wildermjs8 thanks for digging around. If we flash this and have problems what is the best way to go back?
UPDATE: got impatient and flashed per your instructions and all seams ok so far. Shows Sept 4 kernel version in about phone. Will update later. Thanks again
Click to expand...
Click to collapse
Good idea I will post a rollback tar in case anyone has issues

All seems to be working well, if not, things are more fluid for me. No green screen yet either. Thanks, will continue to report in.

Glad to hear it's working out!
I thought the screen looked better too but I thought it was likely I was seeing things lol

The green screen came back. But it took like a dozen or more reboots before it appeared. Sprint s8+ on QGL.

Great job @wildermjs8 - thanks for the upload ?????

patmorris said:
The green screen came back. But it took like a dozen or more reboots before it appeared. Sprint s8+ on QGL.
Click to expand...
Click to collapse
sounds like it minimized it at least for u lol.. i dont think there will be a true "100%" fix until we can be rooted on a stock boot.img

elliwigy said:
sounds like it minimized it at least for u lol.. i dont think there will be a true "100%" fix until we can be rooted on a stock boot.img
Click to expand...
Click to collapse
I'm perfectly content. It's definitely much better than it was.

Thanks for this. I have not had the chance to install yet, too late if in the event a problem arises. I don't like to do "10 sec fix" unless I have extra time jut to be safe. But I'll try tomorrow.
This is the wrong thread but root has been pretty good with the exception of excessive battery drain. Maybe just me so ymmv.
Many thanks for this and the files
Sent from my SM-G955U1 using Tapatalk

Araltd said:
Thanks for this. I have not had the chance to install yet, too late if in the event a problem arises. I don't like to do "10 sec fix" unless I have extra time jut to be safe. But I'll try tomorrow.
This is the wrong thread but root has been pretty good with the exception of excessive battery drain. Maybe just me so ymmv.
Many thanks for this and the files
Sent from my SM-G955U1 using Tapatalk
Click to expand...
Click to collapse
Nice to see ya over here! Far cry from the s7 edge root that's for sure!
How bad is the battery drain? While using or while sleeping? These phones even stock don't sleep well, I'd say they lose on average a percentage an hour, which is sad really lol

It's early days with new firmware so we will see

Quickvic30 said:
Nice to see ya over here! Far cry from the s7 edge root that's for sure!
How bad is the battery drain? While using or while sleeping? These phones even stock don't sleep well, I'd say they lose on average a percentage an hour, which is sad really lol
Click to expand...
Click to collapse
I'm late to the s8+ literally just bought a used one (they made me a deal I couldn't refuse).
I'm losing about +3%/hr while screen off... Screen On is another story... Obviously depends on the activity - but battery drain is high in my opinion and as you know @Quickvic30 I'm NEW to all this still learning what the green button does when the phone makes noise and I see a phone number on the screen.
But the rooting method is still young and improvements and tweaks are already coming LIKE THIS THREAD.
Sent from my SM-G955U1 using Tapatalk

Araltd said:
I'm late to the s8+ literally just bought a used one (they made me a deal I couldn't refuse).
I'm losing about +3%/hr while screen off... Screen On is another story... Obviously depends on the activity - but battery drain is high in my opinion and as you know @Quickvic30 I'm NEW to all this still learning what the green button does when the phone makes noise and I see a phone number on the screen.
But the rooting method is still young and improvements and tweaks are already coming LIKE THIS THREAD.
Click to expand...
Click to collapse
i wouldnt say its a fix lol some still have issues.. although it minimizes it so far, all this thread is about is flashing a newer official combo boot.img lol
a "fix" i would say would be finding a way to manipulate the phone to use a stock boot.img while maintaining root..
basically we are still on a factory binary boot.img which means its not fixed and unstable for daily use (it even says this within the logs lol) this type of boot.img isnt supposed to be a daily so regardless of how new it is, its still bound to have some issues at some point

elliwigy said:
i wouldnt say its a fix lol some still have issues.. although it minimizes it so far, all this thread is about is flashing a newer official combo boot.img lol
a "fix" i would say would be finding a way to manipulate the phone to use a stock boot.img while maintaining root..
basically we are still on a factory binary boot.img which means its not fixed and unstable for daily use (it even says this within the logs lol) this type of boot.img isnt supposed to be a daily so regardless of how new it is, its still bound to have some issues at some point
Click to expand...
Click to collapse
That would be better yes but if a later kernel fixes it in the combo build that is a fix for this issue lol
Given the fact that many have reported no issues I wonder if a match between kernel and some other firmware fixes it. It could be that those affected are on older versions than me.
Hmm

wildermjs8 said:
That would be better yes but if a later kernel fixes it in the combo build that is a fix for this issue lol
Given the fact that many have reported no issues I wonder if a match between kernel and some other firmware fixes it. It could be that those affected are on older versions than me.
Hmm
Click to expand...
Click to collapse
u are not understanding my point, a debug kernel is a debug kernel.. they arent meant for daily use so ppl are bound to have issues and it will mot function the same as a regular stock kernel
i have experienced the screen issue at least twice since last night and at least one other person said he still gets it also...
also not trying to be rude but a fix would be a way to use stock boot.img to get away from debug boot as much as possible.. that will actually require development to be done.. u basically just created a development thread by copy pasting a link to the latest combo firmware, these posts typically go in the general section since u didnt develop the combo, its a stock factory binary firmware
now if you somehow modified it and got it to boot then that would be development lol then again if that were the case we wouldnt be where we are today

elliwigy said:
u are not understanding my point, a debug kernel is a debug kernel.. they arent meant for daily use so ppl are bound to have issues and it will mot function the same as a regular stock kernel
i have experienced the screen issue at least twice since last night and at least one other person said he still gets it also...
also not trying to be rude but a fix would be a way to use stock boot.img to get away from debug boot as much as possible.. that will actually require development to be done.. u basically just created a development thread by copy pasting a link to the latest combo firmware, these posts typically go in the general section since u didnt develop the combo, its a stock factory binary firmware
now if you somehow modified it and got it to boot then that would be development lol then again if that were the case we wouldnt be where we are today
Click to expand...
Click to collapse
Except that isn't always the case. Having run pre-release engineering kernels from cupcake-marshmellow I have a little experience in this area, and outside of VERY early days G/Nexus/Pixel never exhibited a problem like this so I find it a bit surprising.
Forgive me for putting the thread in the wrong place, I guess I deserved that for trying putting related things together. Why does it feel like I'm being dragged into a pissing contest?
I was just trying to help people out, maybe I just shouldnt bother.
Mods can move the threads wherever it doesn't matter to me.

H918 - Newbie

It's been about 10 years since I've last signed into XDA
I just purchased an H918 on eBay for $50 and a new 4500mah battery on Amazon for $19.
I specifically sourced this phone for: the removeable battery and IR blaster.
I will follow up on the actual software versions when I power it up for the first time...
I'm looking for recommendations on what I should run for the most stable experience
Thanks in advanced all

Welcome Back Supovitz!
I am a newbie for V20, and looking to answer the same question as you, plus how to root. By writing out my small collection of knowledge in response to your question, I hope to help myself first, to organize and bake -in my knowledge so that it becomes useful to me and starts making sense. But keep in mind that I am a newbie.
MODEL AND VERSIONS
You can find the exact model here (from your IMEI):
Download LG Firmware Official By IMEI Free Direct Link
Download official KDZ LG Firmware Update by IMEI (ROM) for Update or Unbrick all LG Mobile phone and Tablets
lg-roms.com
Mine is listed as H918 on the label behind battery, but the http://lg-roms.com/ gives me H918TN
(I do not know if this difference is significant, however, elsewhere on this forum there is a lot of warnings that specifically with H918 there should be NO CROSSFLASHING, the model number must match - or BRICK.)
For H918 what matters is what ARB version your phone is on (ARB=AntiRollBack):
Nougat was ARB0 then ARB1, Oreo is ARB1 so far.
These ARB versions are loosely associated with the phone software versions such as 10j, 10p or 20h and so on.
Look at this page to get an idea when these software versions were released and how many of them are there:
LG H918TN(LGH918TN) aka LG V20 - LG-Firmwares.com
LG H918TN download the firmware for free! Detailed installation instruction. Video review of the model and its features. User feedback and latest news.
lg-firmwares.com
To find ARB and Software version, you can use the about phone info in settings (at least for H918 they are visible):
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Mine is running Nougat Android v7, software version 10j (ARB0)
Another way isto check by entering the dial code:
dial: *#LGMENU#*model# ( *#546368#*918# )
choose SVC Menu
choose Version
scroll to bottom
Thus for H918 there have been two ARB versions, 0 and 1 so far:
ARB0 - 10a - 10o
ARB1 - 10p - 10u
The point of knowing the ARB version is that there are two rules:
- if you flash a ROM for a lower version of ARB than the device shows, this will brick your device
- once you flash a ROM that has a higher version than what the device is currently on, ARB adjusts irreversibly
This is why the Anti Roll Back, - we can only move up in software versions, once we discover a root, they issue a new version and severely reduce the number of devices for sell that could use that discovered root.
( there is an actual fuse on the SOC that is burned, and this cannot be ever restored )
So this needs to be considered when choosing a ROM.
TOOLS INVOLVED, TIPS AND LIMITATIONS
Another thing you need to know about H918, is that you cannot count on FASTBOOT flash command on H918. These important FastBoot commands were disabled by T-Mobile. The only use for the fastboot remains on H918 is to unlock the bootloader / check if it is unlocked, i.e. fastboot oem unlock and fastboot getvar unlocked
Searching for a way to flash our files to the H918, XDA RunningNak3d created a method to exploit the "Download Mode" (hold VOL+ insert USB cable to enter the DM) present on H918 which is there to allow for the "LG Advanced Flash".
(I do not know why we can't just use that LG Advanced Flash tool to push our images, such as TWRP? I am sure there is a reason)
Now this exploit allows us to place a TWRP onto the LAF partition (where the Download Mode binary normally is) and thru that TWRP gain an ability to flash images rather than using the the LGUP tool (is LGUP the same as LG Advanced Flash " tool ?). IIRC, the LGUP does have some sort of control what is it asked to flash, so may-be this is why we can't use LGUP to flash TWRP onto Recovery partition and be done with it. So , we use the LAFSPLOIT.
To use LAFSPLOIT you would need to have a prepared linux environment to run the script by the RunningNak3d. There is a prepared bootable ISO image of such environment complete with many tools and LAFSPLOIT and also the ADB called FWUL. Once you get the TWRP on LAF, you typically use it to flash another TWRP, this time to Recovery partition, flash LAF Partition back if you want a working Download mode, and also flash your ROM and your chosen ROOT thingy.
With this it is important to note that H918 has some intricate issue that has to do with encryption. As you know you first Encrypt and then you Root, if you want to have the encryption.
Look at the currently ongoing attempt by XDA PineappleMousepad to ROOT the H918 and keep the Encryption here: https://forum.xda-developers.com/t/h918-rooted-and-encrypted-on-stock.4302253/
But there is this issue with booting to system from TWRP on a stock based ROMs (as opposed to AOSP, for instance). The issue is that the phone goes into the bootloop on SecureBoot (aka DM-Verity), trying to decrypt the DATA partition. To prevent this you must remember to do an advanced wipe from TWRP, before it had a chance to boot to system! So you Reboot to Recovery / and/or use hardware buttons to reboot to recovery, and you have you back cover off, standing ready to pull the battery if you think the phone boot process is going to miss the recovery.
The wipe (format ?) of data (and some say data and cache, some say data system and cache, again needs more research)(Some recommend now to boot to TWRP again and do a full format ? - 3808258 post #1) partition must be the advanced one, - where you have to type YES to confirm. As you can tell my understanding of this aspect is very cloudy, research this.
Finally, when you use the hardware button combination to enter the TWRP that is on the Recovery partition, the process had to be made such that it appears you are about to factory reset your phone. But, no, this is how you actually enter that TWRP. See bolow in BUTTONS section.
BUTTONS
Shutdown:
Hold POWER button for 10 sec
Exit from any Mode:
Hold the [POWER] until reboot
Factory Reset / Recovery Mode:
Shutdown > [VOL-] & [POWER] few seconds (10) > LG-Logo > release [POWER][if not working try releasing both] (only let go of the power button for half a second) but keep [VOL-] > [POWER] once more > Release all once in
Factory Recovery Mode
Note: Accept the factory reset prompt using the hardware buttons. (YES two times) This will not actually reset your device but instead will boot the custom recovery [if TWRP is isntalled on Recovery Partition]
Download Mode: (LAF mode on H918 aka LG Advanced Flash)
Shutdown > Plug one end of cable to PC > while [VOL+] connect other end of cable to phone > Release once in Download Mode
Note: You will enter the TWRP LAF Version if it is installed onto the LAF Partition
Bootloader Fastboot Mode:
Shutdown > Plug one end of cable to PC > while [VOL-] connect other end of cable to phone > Release once in Bootloader Mode
FIXES
There are several fixes available for H918. I am not entirely certain what situations require these fixes, but I want to mention them anyway so that you are aware of what might go wrong.
-Thermal throttling fix
-RCTD removal
-Screen Recalibration with Kernel Auditor
-bluetooth fix? (I've seen a file but failed to findout what it is for)
-LG V30 Camera by Zacharee
-Josh Camera Mod
ROMS
I don't know a whole lot, but it seems that the Stock is the most stable, if you only want the root (like I do).
The Lineage OS has major issues, such as a dead 5G tether, dead VoLTE, No second screen, etc.
(Second screen seems to be enabled on builds of LOS and ResurrectionRemix by Blaises from XDA, but I don't think he is watching the activity here anymore. If you want those, check here:
Downloads for : LG V20 | AndroidFileHost.com | Download GApps, Roms, Kernels, Themes, Firmware and more. Free file hosting for all Android developers.
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
There is SuperV20 ROM , and again, I read there are issues, allthough, many do like it
Download: https://androidfilehost.com/?fid=673956719939834027
Discussion: https://forum.xda-developers.com/t/...-vs9951ca-h990-ds-more.3764390/#post-75915485
I read somewhere on XDA and did not take a note of URL, that If the custom ROM is not stock based, you lose the great camera that V20 has. Don't know if this all the truth, nothing but the truth or what. Also, there were some fixes for the camera if flashing not a stock based rom, but did not do a great research there yet.
Obviously the WETA ROM, which was made for audiophiles and stability:
https://forum.xda-developers.com/t/rom-kern-weta-5-0-7-16th-jun.3532778/

I should note that the WETA ROM for the H918 is ARB0 only as it was made before ARB1 existed, so anyone on software version H91810p or later should stay away from it unless they want a permanent brick.

C D said:
WETA ROM for the H918 is ARB0
Click to expand...
Click to collapse
That is a great question seldom discussed:
Q-How does one know what version of ARB a certain ROM is made for?
A--consider ROM creation date vs. ARB history timeline
A--read ROM thread and in case the OP cared to mention
A--ask around
But, is there a way to check? I mean is that a different looking file, a property, ...?
Let's say, the OP did not mention, no one knows and the ROM was made after ARB1 was sent out.
It is likely that the OP had made the ROM using the new firmware, but it could be that he took a while and his ROM was started and got finished on older, ARB0 firmware.
How to know for sure? Is there a way?

I am writing this out to organize my own thought and to receive a correction, because I am kind of just now learning about this. Feel free to tell me where I am wrong.
My second question is to clarify firmware vs. software.
If you look in the "About" section of settings, you will see that the firmware version [..like H91810p] is actually listed as a "Software Version". So, this is one source of confusion.
My understanding currently is that the OEM calls it "Software" because they do not want the consumers to know too much about how things work, i.e. they create this confusion on purpose.
What is "Firmware" ?
Currently, I hold that it is the code that runs the metal. To say it in a way that is easier to understand, there is a phone (bare metal), it is is run by drivers and binary blobs, which is a code, thus a software, but for the purpose of confusion it is called a firmware because it comes from the OEM (thus, from "a firm"). The phone can run with just that, even though it will not be useful to most people it that way, but never the less, it would be a fully functional device (from a robot point of view). Functional, in a sense that it has a hardware charger component, and there is also would be a code that runs a charger (firmware). It has a radio and there is also a code that runs the radio (again, firmware). Just like a computer that came without the OS, already has the BIOS, which is the firmware by our convention, and it also has a lot of code in many chips throughout (Video card chips, Bridges, Audio circuits and so on). All that code is Firmware.
There will also be the drivers for the OS, which I think would also be the firmware (drivers), but they come with the software because they were written as an interface between a given hardware and a given OS. I do not know if this is exactly the same with phones or not.
What is missing so far is the software, or what we, in these forums call the software. Again, this is some code, but this time it comes from Google who pays the Open Handset Alliance to write it. This time, however, we are talking about the code that runs the OS (Android). This code makes the phone which was already a completely finctioning device (for robots and reversers maybe), useful to the regular consumers as it creates all the windows, dialog boxes, buttons, colors and sounds that makes a regular user able to actually operate the device.
Technically, I think the OS could come as Windows if it was requested to the same device that was running Android OS before, there is no hard rule that would make it impossible. Why I am mentioning this? Because I think it helps to mentally separate the role of firmware from the role of software.
The firmware is stored is a separate partition (in case of modem / baseband / radio code) because:
- it frequently is the case that this firmware operates literally it's own CPU, and
- because it keeps things cleaner - you can re-flash modem partition only (same reasons as for /data), leaving everything else intact, or vice versa, you could leave the firmware partition intact while wiping / re-writing (flashing) others.
What I don't know is where is the firmware that is related to the ARB version stored? Is it only the modem? What other partitions are the firmware?
If this is known, can't we flash only the software and downgrade the OS, while leaving all the firmware (firmware partitions?) intact?
Also about what exactly constitutes a ROM, specifically, what partitions must it include and why, and what partitions can it include that are optional and could be replaced, omitted? At this time I think that the ROM must include a /system as a minimum, it might include boot.img (kernel and ramdisk) and if it does then it is NOT optional because this is where the OS "drivers" are for the given phone (these would be the ones that are compatible with both the given FW version of the device and on the other side, the modded OS that is the reason for this ROM). What other partitions might come with the ROM and are they optional?

Descent2 said:
That is a great question seldom discussed:
Q-How does one know what version of ARB a certain ROM is made for?
A--consider ROM creation date vs. ARB history timeline
A--read ROM thread and in case the OP cared to mention
A--ask around
But, is there a way to check? I mean is that a different looking file, a property, ...?
Let's say, the OP did not mention, no one knows and the ROM was made after ARB1 was sent out.
It is likely that the OP had made the ROM using the new firmware, but it could be that he took a while and his ROM was started and got finished on older, ARB0 firmware.
How to know for sure? Is there a way?
Click to expand...
Click to collapse
The simple answer is: If you can't find out any of the above information, then it shouldn't be trusted or touched. That info should be found somewhere in the ROM's respective thread.
And of course, the ARB0 vs ARB1 issue only applies to Nougat ROMs. From what I've seen, WETA is clearly ARB0 due to its age, Alpha Omega Nougat is ARB1, the later versions of Super Rom are ARB1, and some LineageOS builds have the ARB0 ones labeled "h918-PRE10p" in their filenames. It's probably safe to assume that all recent Lineage versions not labeled this way are ARB1.
Since you can still freely go between Nougat and Oreo on ARB1, very few still care about ARB0 since the only reason to still have ARB0 is to run older Nougat ROMs on the phone.
As for your software/firmware/ROM parts questions, any ROM developer should be able to give you the answers to those.

Thank you!

Descent2 said:
Q-How does one know what version of ARB a certain ROM is made for?
Click to expand...
Click to collapse
If you have the .zip, you can extract it and look at system/build.prop
Look for the line ro.lge.swversion=

PineappleMousepad said:
If you have the .zip, you can extract it and look at system/build.prop
Look for the line ro.lge.swversion=
Click to expand...
Click to collapse
What I was looking for, exactly. Thank you! This is the main thing, the main hint.
Still a hint and every other hint is no less important, because as we know from RunningNak3d the QFPROM cannot be fooled even if we change this in build.prop.
I am writing the above as a warning to anyone who might have read only this Q and A and nothing else, a decided that he will change the value in build.prop and flash a lower ARB version onto a device showing a higher ARB version installed. AFAIK, you will be bricked.

I have my phone up and running on WETA. It's a little slow in comparison to my newer OnePlus 7 but I am enjoying it!
I used LGUP to roll all the way back to original Nougat and then flashed WETA.
Does anyone run Lineage and find it to be smoother?

Could you give a link to the exact Weta you installed and also let me know your downgrade path? (Like you downgraded from 20h to 10p, for example). Thanks and congrats on your success loading that!

[GUIDE] Complete Step-by-Step Convert T-Mobile to Global (or other) firmware

*** Use this at your very own risk.
*** You will lose all data
*** Backup your working modem and persist, just in case.
*** USE USB 2.0 Port and Windows Machine
!!! BEFORE YOU CONTINUE, POST #3 CONTAINS AN IMPORTANT MESSAGE SPECIFICALLY FOR THIS THREAD !!!​
Spoiler: Requirements = Install these prerequisites before proceeding
- 32-bit | 64-bit Qualcomm Driver
- OnePlus Drivers
- Google USB Driver
Part 1: Return to T-Mobile Stock Firmware via MSM TOOL​Turn on Test Mode, Disable Device Driver Signing via Powershell and set Time Date to 2017, then restart PC
Code:
bcdedit.exe /set nointegritychecks off
bcdedit.exe /set testsigning off
1. Launch MsmDownloadTool V4.0.exe.
2. On the login prompt select "Other" in the dropdown menu and click on Next.
3. Click on Target button and select TMO.
4. Press Start button so that it waits for your device to be connected
5. Power off your device
6. Put your phone in EDL mode
by completely turning off your device, hold vol up + vol down and plug in the cable
OR
via ADB command
Code:
adb reboot edl
7. Once phone is in EDL Mode, immediately Click ENUM button and then START button
Wait approximately ~250-300 seconds.
Device will reboot afterwards.
Part 2: Unlock Bootloader with no code and apply Dual SIM​After reboot, Turn on OEM Unlock in Developer Options before proceeding with the steps
1. Rename and move “instantnoodlet_15_O.16_201001.ops” from MSM Tool directory to somewhere else (e.g., Documents Folder)
2. Download "unlock.ops" and rename it to instantnoodlet_15_O.16_201001.ops
3. Move the "renamed unlock.ops" to MSM Tool directory
4. Launch MSM Tool and proceed using the steps from Part 1
MSM Tool will finish flashing in under 15 seconds and the device will reboot with the message, "<!> The device is corrupt.."
5. Unplug phone from PC and Force Shutdown device by simultaneously press and holding Power and Vol buttons till the device reboots
6. Let go of all buttons once you see device reboot with the logo FASTBOOT MODE, the big START logo will appear afterwards
7. Open SDK Platform Tools folder and launch Powershell/CMD from there
8. Copy and paste this command to check if device is recognized in FASTBOOT
Code:
fastboot devices
9. Once device isrecognized by terminal, copy and paste this other command
Code:
fastboot flashing unlock
10. A confirm bootloader prompt will appear, use Vol buttons to hover on UNLOCK THE BOOTLOADER and to confirm, simply press Power button
Once confirmed, device will reboot back to T-Mobile Firmware but now with Dual SIM and an unlocked bootloader. To use the MSM Tool again without the "unlock.ops", move the unlock.ops to a different place and put back the original ops.
Part 3: Converting to other regions (e.g., Global, EU, Indian) and lock Bootloader​*** Cannot lock bootloader after flashing Fastboot ROM. Will corrupt device ​*** As of right now, Dual SIM doesn't work on OOS12/13 Indian Firmware​1. Download this Fastboot ROM
2. Open Fastboot ROM Folder, click flash-all.bat and type and enter "y" to the terminal
Code:
Do you want to wipe all the data ( Reccomended )[Y/N]?y
< waiting for any device >
3. Reboot phone to FASTBOOT MODE and plug the phone back to the PC
4. Once the process is done, find an OTA ZIP from this thread to update to and download it
(You can use ota.zips from any region whether it be EU/India/Global, e.g., OxygenOS 11 Global 11.0.11.11)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
5. put the OTA ZIP in the phone, update it and reboot
After rebooting, you can either lock bootloader or stay unlocked to root
6. To lock bootloader, reboot to FASTBOOT and plug phone in to PC
7. Open platforms-tool and open a terminal from the folder
8. Copy, paste and enter this command:
Code:
fastboot flashing lock
9. Confirm the prompt LOCK THE BOOTLOADER and the phone will perform a factory reset and reboot.
There you go! What you can do at this point is stay and daily drive OxygenOS 11 or update to OxygenOS 12/13 or even ColorOS. Dual SIM will work on any Firmware Region. The phone's model will also permanently change to IN2015=OnePlus 8 Global Version Model unless you go back and use MSM Tool again with the original ops.

Thanks thattechguy_69 for the shout out much appreciate that, just glad I was able to help

Dear OnePlus 8 community,
This is my last time visiting y'all. Thank you for all the support and help you guys have gave me throughout the past year. You guys were the first community that I was a part of. I have now retired my OnePlus 8. This device is what entered me into the realm of XDA in the first place. This place will always be a part of my heart and I will cherish the memories I have experienced with it. This guide will be a step-by-step summary of all the guides scattered in the OnePlus 8 Guides Section. A reminder to the next OnePlus 8 users, don't let this community die and keep the old OnePlus Never Settle spirit, alive!
Sincerely, Aaron
22 November 2022​
Credits to these amazing people for making this possible:
@matteosaeed and his Guide.
Ms. user_ajusee's Guide
Mr. gregoryaul (@Aulgreg38) from HighOnAndroid Forums
THE MAN HIMSELF: Mr. Max Lee of HighOnAndroid Forums; link to his YouTube channel.
@MohmmadUzairKhan for figuring out the details for instant bootloader unlock that also came with dual sim
@Mason220 for providing unlock.ops for the Verizon models which also happen to work on T-Mobile models
@Some_Random_Username for the MSM Tool and instructions

Aulgreg38 said:
Thanks thattechguy_69 for the shout out much appreciate that, just glad I was able to help
Click to expand...
Click to collapse
Oh thank you Mister!

Hi man i do everthing like the post say and i got it. But i notices that when you convert t-mobile oneplus 8 to global you lose safetynet. so i was wondering 2 things. How can i get safetynet working again, and if i relock the bootloader with the global firmware will it boot or it will break? Thanks mate.

Adriancris7 said:
Hi man i do everthing like the post say and i got it. But i notices that when you convert t-mobile oneplus 8 to global you lose safetynet. so i was wondering 2 things. How can i get safetynet working again, and if i relock the bootloader with the global firmware will it boot or it will break? Thanks mate.
Click to expand...
Click to collapse
If you lock bootloader the system will say your phone has been corrupted and if you did happened to lock your bootloader. You are gonna have to use MSM tool to restore OS and your are gonna have to start again to step 1.
For the other issue which is safetynet, did you root your phone? From what I know you would only lose your safety net when you root your phone. I did root my phone 2 weeks ago and from what I remember my safetynet was fine. You are gonna have to ask someone about safety net man since I am no expert at that region.
Anyways, thank you for using this guide. Really appreciate it man

thattechguy_69 said:
If you lock bootloader the system will say your phone has been corrupted and if you did happened to lock your bootloader. You are gonna have to use MSM tool to restore OS and your are gonna have to start again to step 1.
For the other issue which is safetynet, did you root your phone? From what I know you would only lose your safety net when you root your phone. I did root my phone 2 weeks ago and from what I remember my safetynet was fine. You are gonna have to ask someone about safety net man since I am no expert at that region.
Anyways, thank you for using this guide. Really appreciate it man
Click to expand...
Click to collapse
Ok, I see.. I didn't root the phone. I just want to know. It's just I try to install Netflix in play store and the app didn't show.... So I install safetynet test and shows that it's not working... I don't have plane to root the phone. I only want to convert the phone to global... I don't know how to solve the issue of safetynet.. that why I ask you. Anyway the phone is working flawless no issue at all.

Adriancris7 said:
Ok, I see.. I didn't root the phone. I just want to know. It's just I try to install Netflix in play store and the app didn't show.... So I install safetynet test and shows that it's not working... I don't have plane to root the phone. I only want to convert the phone to global... I don't know how to solve the issue of safetynet.. that why I ask you. Anyway the phone is working flawless no issue at all.
Click to expand...
Click to collapse
Ok so I check my Play Store Certification and I just found out that my device has not been certified which means that's the reason why you couldnt install/update Netflix.

thattechguy_69 said:
Ok so I check my Play Store Certification and I just found out that my device has not been certified which means that's the reason why you couldnt install/update Netflix.
Click to expand...
Click to collapse
Yeah, that's what I told you. How can we solve the issue. It's the only bug I've found.

Adriancris7 said:
Yeah, that's what I told you. How can we solve the issue. It's the only bug I've found.
Click to expand...
Click to collapse
Download "Device ID" and copy Google Service Framework (GSF) and then paste it on this link
https://www.google.com/android/uncertified/ , just wait for Google to Verify your device. If it does not work then just download apk on apkmirror or revert back to T-Mobile ROM. I am in the process of trying to get mine also certified.

This worked for me, but had the same issue with the safetynet and thus can't use google pay. Just submitted the GSF for google to verify. Did google verified your device yet?

Oneplus8rooter said:
This worked for me, but had the same issue with the safetynet and thus can't use google pay. Just submitted the GSF for google to verify. Did google verified your device yet?
Click to expand...
Click to collapse
I changed my ROM to Pixel Experience because of OOS 11 battery issues and etc. But I dont think it did certify my device. Did some research on this before I switch and someone said it should certify your device but it wont say it. Another method I heard is to clear cache and storage cache on Play Store App and it should but I have never tested this one. The most sure method I saw was to root phone and bypass.

thattechguy_69 said:
I changed my ROM to Pixel Experience because of OOS 11 battery issues and etc. But I dont think it did certify my device. Did some research on this before I switch and someone said it should certify your device but it wont say it. Another method I heard is to clear cache and storage cache on Play Store App and it should but I have never tested this one. The most sure method I saw was to root phone and bypass.
Click to expand...
Click to collapse
Yeah, I tried the play store app and gpay cache and storage cache clearing with no luck. I use gpay with NFC quite often so it was a bummer that it won't work without being certified. Thanks you for writing the guide regardless!

Oneplus8rooter said:
Yeah, I tried the play store app and gpay cache and storage cache clearing with no luck. I use gpay with NFC quite often so it was a bummer that it won't work without being certified. Thanks you for writing the guide regardless!
Click to expand...
Click to collapse
So sorry man. Thanks for letting me know it worked tho! You should try pixel experience tho. It is certified

thattechguy_69 said:
So sorry man. Thanks for letting me know it worked tho! You should try pixel experience tho. It is certified
Click to expand...
Click to collapse
Yeah, everything else seems to work well besides that.
As much as I would like to try the other ROM, do they keep up with security patches? I just bought this phone used (Tmobile unlocked) and haven't rooted an android for a while and wasn't sure if they still get updates directly from google or some volunteer is maintaining the ROM. Would like to root it to whatever ROM that is the most maintenance free and would support security updates at least for a couple of years. I think oneplus support it up to 2023 for oneplus 8 if I'm not wrong.

Oneplus8rooter said:
Yeah, everything else seems to work well besides that.
As much as I would like to try the other ROM, do they keep up with security patches? I just bought this phone used (Tmobile unlocked) and haven't rooted an android for a while and wasn't sure if they still get updates directly from google or some volunteer is maintaining the ROM. Would like to root it to whatever ROM that is the most maintenance free and would support security updates at least for a couple of years. I think oneplus support it up to 2023 for oneplus 8 if I'm not wrong.
Click to expand...
Click to collapse
Yes they do keep up with updates but the people that are maintaing it are not from google. But I will assure you that it is way smoother and more optimized that the current oos 11. I also bought my phone recently 1 month ago as used! You can check some youtube channels if you are interested in pixel experience. Also changing rom does not require root so you dont have to tinker with safetynet and stuff

thattechguy_69 said:
Yes they do keep up with updates but the people that are maintaing it are not from google. But I will assure you that it is way smoother and more optimized that the current oos 11. I also bought my phone recently 1 month ago as used! You can check some youtube channels if you are interested in pixel experience. Also changing rom does not require root so you dont have to tinker with safetynet and stuff
Click to expand...
Click to collapse
Wow, that looks really good. I might just try that out instead of going back to t mobile stock. Thank you!!

Oneplus8rooter said:
Wow, that looks really good. I might just try that out instead of going back to t mobile stock. Thank you!!
Click to expand...
Click to collapse
Here are the instructions and Follow THE GUIDE AND I MEAN IT: https://wiki.pixelexperience.org/devices/instantnoodlep/install/
you have to be in the latest oos 11 and in the last part of the guide, you can lock back the bootloader by replacing avb key with a custom one. If you dont update to the latest. It will keep saying system ui not working. Learned it the hard way and was hard stuck for 3 days lol. The os itself is directly from the pixels but with added features that was unique from oxygen os so google will think you have a pixel.

thattechguy_69 said:
Here are the instructions and Follow THE GUIDE AND I MEAN IT: https://wiki.pixelexperience.org/devices/instantnoodlep/install/
you have to be in the latest oos 11 and in the last part of the guide, you can lock back the bootloader by replacing avb key with a custom one. If you dont update to the latest. It will keep saying system ui not working. Learned it the hard way and was hard stuck for 3 days lol. The os itself is directly from the pixels but with added features that was unique from oxygen os so google will think you have a pixel.
Click to expand...
Click to collapse
You are a godsend sir!! Looks like I'll be tinkering with it tonight! Thank you so much!

Oneplus8rooter said:
You are a godsend sir!! Looks like I'll be tinkering with it tonight! Thank you so much!
Click to expand...
Click to collapse
No problem!!! Just love helping people