Database Users

[Tutorial] [OTA 3.0] [Nvidia Shield Tablet] How to debloat and optimize ota 3.0

DISCLAIMER: though this seems safe, there are always risks. Warranty may be void, bugs might crawl out of your shield. I am not responsible for mishaps, bugs, crashes, damage, loss of jobs, girlfriends, and/or if your shield turns into Skynet and begins to destroy the human race!
Firstly, throughout this tutorial I will be shamelessly pointing you toward others threads. Please, give them your thanks. They are masters in their fields and with out them none of this would be happening! Also remember noone gets paid for any of this, they with their skills and I with time do this out love for tech and a desire to help others and see them enjoy their tech as much as we all love ours. That said... Onto the cookies!
*********PLEASE NOTE*********
*********THIS ENTIRE PROCESS CAN BE DONE WITH OUT ANY ACCESS TO A PC!
--BUT--
TO KEEP A LOCKED BOOTLOADER AND AVOID WARRANTY NASTYNESS PLEASE READ
*If you are still on a locked bootloader, and want to easily keep it. Root ota 2.2.1 first, install flashify, and use it to install twrp.
*Rooting ota 3. 0 and using flashify from there will also preserve locked bootloader.
*Rooted ota 2.2.1 or a custom recovery will break nvidias native ota system. You will have need a copy if the FULL OTA from the links provided. They flash easily in twrp. But ONLY THE FULL OTA, NOT THE INCREMENTAL.
******PREREQUISITES (These Are Required)******
*Must be rooted.
If coming from stock, (unrooted, stock recovery, and locked bootloader) Kingroot will root any ota so far.
Install apk, run it, it will most likely reboot your shield, on ota 3 it will freeze, (mine did at around 30% on ota 3, but instead of a reboot, I got a freeze) this is normal. Hold power button until the shield turns off. Boot back up, and run Kingroot again. It should now complete fine, installing Kinguser as root control app. This gives you enough root to run flashify from play store to install the next step. (thanks to China for making kingroot and whoever translated it for us)
Kingroot link: http://forum.xda-developers.com/android/apps-games/one-click-root-tool-android-2-x-5-0-t3107461
*Team Win Recovery Project (twrp) must be installed.
Head over here to @Steel01 thread for multi rom twrp. You will only (at the moment) need his modified twrp build. More instructions there. Don't forget to thank him! (Thanks @Steel01)
@Steel01 multi rom twrp thread: http://forum.xda-developers.com/shield-tablet/development/multirom-v30-unofficial-port-t3025355
*ota 3.0 FULL OTA (thanks to @MidgetMob)
Link: http://forum.xda-developers.com/shi...k-recovery-images-ota-library-guides-t2988881
*MEGA may or may NOT work. Mega has issues from time to time. (thanks @Ctrl_Alt_Del for the heads up)
****If MEGA links are not working, here's another source.
Thanks @gavin-phelan for the links.
OTHER Link for full ota: http://forum.xda-developers.com/shield-tablet/general/android-5-1-t3115536
*SuperSU recovery flashable installer. (thanks to @Chainfire)
Link to supersu beta (beta works better for the xposed framework):
http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
*Fdroid store for selinux mode changer (needed for viper) and ad away apps! (thanks Fdroid!)
Link: https://f-droid.org
*****OPTIONAL*****
*Xposed super alpha for Android 5.1 (sdk22) (thanks @romracer)
Link: http://forum.xda-developers.com/xposed/super-alpha-posted-permission-xposed-t3072979
You must read that thread a bit. You will need the xposed installer from the main xposed lollipop thread. (thanks @rovo89)
Main xposed thread
Link: http://forum.xda-developers.com/showthread.php?t=3034811
*Gravitybox works on 5.1 now (thanks @C3C076)
Link: http://forum.xda-developers.com/xposed/modules/app-gravitybox-v5-0-0alpha-tweak-box-t3037566
*BusyBox - Busybox is required for viper4android install. Make sure to run and install it BEFORE YOU INSTALL VIPER DRIVER. The apk can be installed, but when you run it. It will try to install the viper driver. Selinux must be set to permissive, and busybox installed first.
It can be found in play store.
*selinuxmodechanger can be found in fdroid repository.
*ViPER4Android audio engine (thanks @zhuhang)
For viper install. Be sure to install fdroid and get selinux mode changer. And change to permissive BEFORE YOU INSTALL VIPER DRIVER. the app is fine but for the driver to install selinux must be set to permissive. After that it's fine to set it back to enforcing.
Link: http://vipersaudio.com/blog/?page_id=48
Forum:
http://forum.xda-developers.com/showthread.php?t=2191223
Someone said cookies? (Procedure)
**tip** titanium backup SUCKS FOR backing up app data. Bugs out the apps sometimes. So for games, manually backup saves and place them back after reinstall. It's helpful to use tibu to backup your apps alone. Then use tibu again to make a recovery flashable zip to reinstall them all at once....
*Firstly you will need a root enabled file browser (I use es file explorer)
*On the internal memory, firstly back up any pics or ANYTHING you want saved from internal memory to the external SD card. (I usually name my backup folders starting with a # to keep them separated from anything that's written to external via an app or the system. Helps to keep track.)
*Next delete it ALL. In es file Explorer just as everything in sdcard0. /android gone, all folders, ax them. I even nuked the hidden folders and all. I wanted a totally clean install. So anything in the /sdcard0 folder can get wiped. As wiping through twrp DOES NOT WIPE THESE FILES. And sometimes can cause oddness on new installs. This can also be achieved through twrp but it takes longer. Keep in mind that everything inside /sdcard is rebuilt on FIRST boot. Hence deleting in twrp. Don't navigate to straight / things go bad if you mess about in those files....
*After everything has been deleted on internal, and the folders your not using for backups on external. Namely the /android folder on external. You should be ready to reboot to recovery....
*Now reboot into twrp. Click wipe, advanced, then check dalvik, system, data, and cache. Wipe
*Now flash the FULL OTA for your model of shield.
*Next click the home button in twrp. Then Mount, then, uncheck the box for system, then, re-check it. (remount system)
*Now click on the Home button again, Advanced, File Manager.....
*Now the fun part...
Navigate to /system/app and delete the following FOLDERS, contents and all, by clicking on each folder one at a time, once clicked, it will show you contents of that folder. At the bottom click select, then delete, swipe to delete. For each of the following folders....
++*NOTICE* Some of these folders contain libs (library files) and i discovered some issues with deleting them. (videos not working, possible connection console mode crashing, etc) These folders are indicated below, and any side effects possible due to its removal. Console mode has been solid so far even without the libs. That doesnt mean that it wont cause any issues later and i just havent seen it yet. So BEWARE o0o0o =D
Adobe reader
Books
Calendar
++**Chrome (I use chrome beta) (CONTAINS LIBS) possible connection to the "great chrome slowdown" These ARE SAFE to remove and removal may cure the slowdown bug. either way, using any browser BUT chrome (i.e. Chrome Beta, Dolphin, Opera etc.) also fixes the "Chrome slug races"
Cloud print
Input methods for Japanese and Korean (unless you need it)
++**Drive (CONTAINS LIBS) i havent noticed any side effects from removing these and SHOULD BE SAFE to delete. also i use es file explorer for drive access
Email (I use inbox)
Evernote
Evernote widget
Exchange2
Gmail (I use inbox or reinstall from store)
++**Hangouts (CONTAINS LIBS) i use hangouts for OUTGOING PHONE CALLS, as such i feel these libs are POSSIBLY NOT SAFE to remove. i havent found any issues so far but BETTER SAFE THAN SORRY on an essential core sytem
Holo spiral
Google tts (optional)
Juswrite (I don't use the stylus or handwriting)
latinIME (aosp keyboard)
++**Maps (CONTAINS LIBS) i havent found any issues but NAVIGATION to me is an essential core system therefore i feel these are POSSIBLY NOT SAFE to remove. again BETTER SAFE THAN SORRY
Music2 (I use gonemad music player or reinstall from store)
Newstand
Nvcameraawesome (it sucked and I use camera51)
Phase beam
Play games
++**Print spooler (CONTAINS LIBS) never use(d) it so i dunno really. SHOULD BE SAFE to remove (feedback welcome)
Street
Stylusmobileoem (like I said I don't even HAVE a stylus (unless someone has an extra they are willing to mail....)
Talkback
Trine 2 (unless you like it)
Twitch (unless you use it, also in play store)
++**Videos (CONTAINS LIBS) I had issues playing embedded videos in play store (app trailers) and some websites. i would recommend DO NOT REMOVE THIS. i ONLY left this here for info only. remove ONLY AT YOUR OWN RISK
Write (again with stylus stuff)
++**Youtube (CONTAINS LIBS) never had any issues removing this. but i feel it could be related to my above mentioned video playback bug. this is OPTIONAL.
*now navigate to /system/priv-app
Delete folder musicfx (needs to be gone or disabled for viper4android audio install)
*now navigate to /system/vendor/app
Delete the folder watercolor (dabbler can be gotten from play store)
*if you feel busy /system/media/audio is where the ring tones are and you can delete the ones you don't use for more space but it's only 3mb....
*FINALLY hit the home button in twrp again.
**DO NOT FORGET** Install superSU beta for root!!!
*REBOOT!!
*After system boots up and gets done optimizing, it's safe to reboot back to twrp and flash the xposed framework.
*You're done! That's it... Wait... What? You want even MORE cookies? Well, OK....
*Keep reading for optional steps for even better results!
***PS... Keep checking our friend's @BitOBSessiOn and @twistedumbrella threads for really great kernels for our ota..
Thanks @BitOBSessiOn
Thanks @twistedumbrella
Links:
Bito: http://forum.xda-developers.com/shi.../tweaked-kernel-nvidia-shield-tablet-t3069776
++++++ ***check out @BitOBSessiOn thread, ota 3.0 source built, optimized kernels for all models released!
NEW UNIFIED BUILDS FOR OTA 3.0 (ONE FILE FOR ALL MODELS)
Twistedumbrella: 2.2.1 ONLY http://forum.xda-developers.com/shi...t/stock-lollipop-kernel-cifs-support-t2967839
And some more post script.
PPS **tips**
*System apps always keep a copy of themselves for when it gets updated, so all those apps (that you just deleted) end up being over 400 mb after they all update once. And they ALL HAVE updates at time of install. So you save there. Just takes a minute to reinstall as user apps from the play store,and save a bunch of space.
***WIFI ISSUES!** If you do NOT HAVE a 5ghz router. Go to wifi settings, advanced, wifi band, switch from auto to 2.4ghz, makes the Web run faster and if it's set to auto I notice a good 40 second delay in wifi connecting. Also make sure the box "wifi always scan" is turned in. Otherwise wifi doesn't auto connect at boot.
*Get folder mount from the play store. It automagically patches android to let apps write to external SD. As well as links folders on external to internal so you can move ANY app to sd card. Profit!
*For a cleaner install. Install fdroid, then ad away. And run ad away before you ever open more than play store for es file Explorer to install fdroid. This way ad away is the first or one of the first apps to open. Blocking ads from that point on. That way if apps have built in ads, they won't even be able to load!
*Also thanks to @djdarkknight96 here's a link for a bad ass themed SwiftKey keyboard
http://forum.xda-developers.com/showthread.php?t=1016053
*To improve system responsiveness, enable developer options (In settings, click about tablet, click build number 7 times.) Then in developer options about midway down, turn "window animation scale" "transition animation scale" and "animator duration scale" from 1.0 to .5 this increases the speed of animations throughout the system/rom
*After installing the gravitybox xposed module, you can turn those 3 animation scales down further to .25 for even faster response.
*Native lcd density for shield tablet is 283.
It comes stock at 320
*Nvidia corporate tegra color scheme. Green is hex (#76b900) rgb (r:118 g:185 b:0), and grey, hex (#5c5c5c) not sure greys rgb. And black.... I looked it up in their corporate and product guidelines pdf.
*You can add apps to console mode by clicking the little + symbol under "android games" and "media apps" in shield hub. They will then be added to the "easier" to navigate shield hub menu.
*In the play store kernel adiutor (yes that's how it's spelled) allows control over the cpu speed and other critical stuff and things. To squeeze alot more juice from your battery, if everything else here is done, I found I could clock the cpu @2ghz (200mhz down from stock) and it's just as fast as true stock. Killer battery savings on top of the improvements already made in ota 3.0
*If you adjust the clock speeds in kernel adiutor... Make sure to reset the minimum to 51 every time and sit and watch to make sure they stuck. They will float around, then settle. But if you exit after altering the max and the minimum is floating high, it will set the minimum to that value.... Found THAT out the hard way......
*The letters that form the word "SHIELD" on the back of our devices.... Are stickers in small indents.... Looks really kewl if taken out. (see post #13 for pics)
+ *POSSIBLE USB ON THE GO (OTG) FIX*
Power off your shield, plug in USB OTG cable with a flash drive in it. Power on the shield. Once booted, pull flash drive and use whatever OTG compatible device you wish (mouse, keyboard, micro missile launcher--thanks ThinkGeek!))
ONE CONDITION! This method BREAKS CHARGING UNTIL NEXT REBOOT! (thanks nvidia!)
Enjoy!
Questions and comments always welcomed and encouraged!
If i forgot something, missed a step, whatever. Let me know!
I'll update/add to this if/when I think of things.
Ideas? Let me know!
CHECK POST #2 FOR UPDATE TIMES.
I'll try to highlight changes until I update again.
Look for the + symbol
Cheers,
Cyris
Mmm cookies just like mom makes!

Just a reminder! ALWAYS CHECK THE MD5 CHECKSUM FOR DOWNLOADED FILES. Md5 checker in play store works great. It can certainly save some headaches!
A SECOND MORE IMPORTANT REMINDER, KEEP A COPY OF YOUR FULL OTA IN THE ROOT OF YOUR EXTERNAL SD CARD. THAT WAY IF THE LIQUID DEFECATION TRULY STRIKES THE AUXILIARY ROTOR. YOU CAN USE NVIDIAS BACKUP STOCK RECOVERY (AT BUGDROID (ANDY ON HIS BACK WITH A RED ! OVER IT) HIT "VOLUME UP" + "POWER") TO WIPE DATA AND FLASH A STOCK FULL OTA AND GET BACK UP AND RUNNING AGAIN. THEN USE KINGROOT, THEN FLASHIFY, THEN TWRP, TO GET ROOT BACK AND CUSTOM RECOVERY....
**UPDATES**
Times are Pacific (my local)
+Initial post 5/25 @ 1300 (apx)
+Updated 5/25 @ 1655
+Updated 5/25 @ 1730
+Updated 5/25 @ 1810 - make sure you check this one for viper audio install
+Updated 5/25 @ 2304 - new full ota links
+Updated 5/26 @ 1030 - @BitOBSessiOn ota 3 kernel release, links posted
+Updated 5/26 @ 1546 - Added usb-otg temporary fix
+Updated 5/27 @ 2200 - Cleanup OP, removed old + symbols
+Updated 6/17 @ 1430 - Added info on folders containing LIBS in the wiping section.

Nice! I will report back once I have redone my tablet.
And please, give me some time. It's the end of a holiday weekend & I have a few things to do before going back to work Tuesday.

Ctrl_Alt_Del said:
Nice! I will report back once I have redone my tablet.
And please, give me some time. It's the end of a holiday weekend & I have a few things to do before going back to work Tuesday.
Click to expand...
Click to collapse
No worries. I created this thread for a laid back easy way to (try) and get the most from our device. Xda was always my go to place to find help and it's a bit different now. Not everyone is a developer, but it shouldn't be hard to get knowledge from those that are. Hell I'm no dev, just like to test stuff, a crack flasher. But at one time I didn't know what root was..... We all were. I know I love it when I show someone my device I spent 100s of hours tweaking just right and the look on their face! At one time that was me. I had to ask questions that probably got a few chuckles. But usually there was someone there to ask. If i can help I figure I SHOULD,
As I said I encourage questions. It may help someone else later on. Cheers!

... Wrong button.....

All is well. And the wipe,install directions from TWRP went flawlessly.
As soon as it booted, I was presented with the Welcome screen, as if it were a brand new device, unlike just updating an older OS. Chose the language, if I had a Google account & signed in...all that cookie dust. Apps from the list I have backed up to the Google servers under my account downloaded & installed automagically.
And best of all....no more "Android is Starting" & no more "optimizing the apps" at cold startup! Big thumbs up there! :good:
By the way, I could not get the full install from the link you provided from another user. It went to Mega & Mega is having transfer issues. It would download about 10 thru 15 % then flash something about a transfer error, then reduce the file transferred back down to 8 or 9 %...then download that again up to around 12 % or so, then back down to 8 %....lather, rinse, repeat...indefinitely! I used this user's link in his post to get the correct ROM: Android 5.1 out now
Just an FYI there.

Ctrl_Alt_Del said:
All is well. And the wipe,install directions from TWRP went flawlessly.
As soon as it booted, I was presented with the Welcome screen, as if it were a brand new device, unlike just updating an older OS. Chose the language, if I had a Google account & signed in...all that cookie dust. Apps from the list I have backed up to the Google servers under my account downloaded & installed automagically.
And best of all....no more "Android is Starting" & no more "optimizing the apps" at cold startup! Big thumbs up there! :good:
By the way, I could not get the full install from the link you provided from another user. It went to Mega & Mega is having transfer issues. It would download about 10 thru 15 % then flash something about a transfer error, then reduce the file transferred back down to 8 or 9 %...then download that again up to around 12 % or so, then back down to 8 %....lather, rinse, repeat...indefinitely! I used this user's link in his post to get the correct ROM: Android 5.1 out now
Just an FYI there.
Click to expand...
Click to collapse
Glad to hear it went well. And thanks for the info on mega. It does that from time to time. Could be alot of people trying to get that file right now. Links updated.
If you go through the xposed install and all. It gets spooky fast....

can you explain about screen density? native 283? how do you know that? table has 320 dpi

Excellent guide and info. Spent all weekend formatting and dealing with "optimizing apps", this fixed it all, great tablet now

GOALAR said:
can you explain about screen density? native 283? how do you know that? table has 320 dpi
Click to expand...
Click to collapse
It's an 8 inch screen. With a resolution of 1920x1200 I'm not sure the math, but it adds up to 283,or there are a few sites that you can go to and enter your the screen info and it will tell you what you density is. Density is how many pixels are in a square inch. Also GSM arena and a few other sites show this data if you Google "shield tablet specs".
Switching from 320 to 283 just makes the screen look sharper. It also can effect what games are listed as compatible in the play store. Example, dead space and dead trigger 2 will not install @ 283. But will run at it. I have dead space myself and it plays fine but I have to side load it or set my density back to 320 in build.prop then install it.
Think of it like running different resolutions on your pc monitor. The monitor will show them just fine, but only 1 is the exact spec from the factory, and look the best.

Thanks For This
Hi, @Pariahnoble. Just wanted to say that this is great, exactly the kind of effort that supports the XDA community.
I am sure that this will be a huge help to a lot of people.

koop1955 said:
Hi, @Pariahnoble. Just wanted to say that this is great, exactly the kind of effort that supports the XDA community.
I am sure that this will be a huge help to a lot of people.
Click to expand...
Click to collapse
Thanks! =D Just hope it does in fact help some folks enjoy their shields a little more. I've been pretty unhappy so far, it was this or a Nexus 9, now I don't regret my decision anymore lol

Pictures of back of shield with letter stickers removed

Updated again

I'm surprised there aren't more comments on this thread. This looks great.
By the way, did I miss something or can this actually be done completely without the use of a computer?

radio five said:
I'm surprised there aren't more comments on this thread. This looks great.
By the way, did I miss something or can this actually be done completely without the use of a computer?
Click to expand...
Click to collapse
Nope didn't miss a beat. This whole process can be done with no pc (I don't have a pc, my shield is my ONLY device.) so I've learned how to do it all locally (on board the shield itself).
This is only just now available, 5/13 kingroot was released that would root the tablet stock off the shelf. And flashify to put on the custom twrp. After that it's good times!
Ps, thanks for the heads up on the no pc thing, I forgot to mention that, OP updated...

That's great news for me since my computer recently took a **** and I'm about to throw my old laptop out the window. (windows vista, won't take adb drivers, runs out of memory using chrome, etc...)
Sent from my SHIELD Tablet using XDA Free mobile app

radio five said:
That's great news for me since my computer recently took a **** and I'm about to throw my old laptop out the window. (windows vista, won't take adb drivers, runs out of memory using chrome, etc...)
Sent from my SHIELD Tablet using XDA Free mobile app
Click to expand...
Click to collapse
Ouch! I feel your pain. I recently had to try to flash using add (adb but "add" was a great typo) on Windows xp.... Oh yeah... THAT went well.... Then 2 days later kingroot came out.
Just make sure (and I'll add this to the op as well) to keep a copy of the full ota on the ROOT of your external SD card, that way if your shield take a flaming deuce in your hands, you can STILL use nvidia backup recovery. If you have ever seen the "bug droid" (ole Andy on his back and the flaming red ! Over it) hold the "volume up" button and hit power and the nvidia recovery comes up. Let's you flash a STOCK FULL OTA and bam, back in business, just kingroot, flashify, twrp, keep calm, and carry on!

Man, I'm glad you said something! I'm gathering all the files on my external sd card in a folder (downloads/Shield Optimization) and I was getting ready to take the plunge. I'll move everything to the sd card's root before I get started.
I'm also considering backing all of my sd card to a work computer temporarily so I can reformat it. My junk heap of a laptop can't read it but I suspect my shield may have formatted it to a weird..... format.
I just want to have the card ready in the event I want to transfer large files and not wait as long.
Speaking of which, would I be able to format my sd card via my PC with it still in the Shield, connected by a usb cable?
Sorry if I'm getting slightly off topic.
Sent from my SHIELD Tablet using XDA Free mobile app

@radio five
Firstly the only file you really need in the root folder is the ota zip. That's only because I'm pretty sure that's where the stock recovery will look for it, IF everything goes to hell.
Yes about formatting your card or storing files elsewhere during all this. The closer to a fresh card and internal memory the better.
Not sure what if any besides ntfs that the shield would format it to. But ntfs is recommended. And it's so far the only (I think) supported format for cards over 32gb. Also. After you format it to ntfs, quick format is OK, full is better but much slower on Windows, make sure to name it. Any is OK. "Sdcard" works.
In Windows Explorer, click on the volume (Sdcard you just formatted) to select it. Wait a sec. Then click it again. And name it when it highlights.
It fixes SOMETHING, Noone really knows what, but makes the shield recognize SD cards over 32gb
I'm sure there IS a way to format via adb, but I have no idea how...
What topic? >.< lol all questions are encouraged.

[GUIDE] Root/Kernel+ViPER/Dolby+Theme/Mods

Intro
I decided to put together this all-in-one guild compiling all the research and testing I've done. I've seen a lot of the same questions and misunderstandings come up over and over in the various threads, most of which I had myself. I've spent lots of time, since I got my new Google Pixel 2 XL, searching XDA, following all the guides the fine folks here put together, flashing, restoring, testing, etc. I've been using Android since my Google Nexus One, so I've been messing around with all this for quite some time now. The Android community is amazing and I've learned a lot over the years, so it's my turn to hopefully help someone out.
I'll also share some of the caveats, issues and fixes I had to do with this setup. This was all done with a Google Pixel 2 XL on Project Fi with an eSIM & physical SIM, so this guide was written and tested with that, however it should work the same in theory with other carriers, but your results may vary.
NOTE: I am not a developer by any means. I've toyed with creating my own custom ROM, but I'm not a ROM or Kernel developer. I just got really good at using the stuff the other amazing smart people here developed and shared with the community.
NOTE 2: Following these steps WILL wipe your device, so make backups if needed!
Thanks
I would like to give thanks to the following folks for the guides, development and help; @topjohnwu, @nathanchance, @Dees_Troy, @luciusfox, @thedude420, @Quinny899, @airmaxx23, @matt1313, @sharkie405, @Tulsadiver, and @zachman1750. Please forgive me if I forgot to mention you directly as I've gone through many threads and guides at this point. I also thank the community for helping each other out and providing their experiences and testing as well.
Why Root?
I get the same question from everybody all the time, "why do you root your phone?" Well, many reasons, which I'll list a few below, but because I spent a lot of money on my phone and I feel I should have full access to it. If your phone is leased or company owned, I understand why you wouldn't, but if you own it outright, why not have full access to do what you want with it? I mean, how would you feel if you purchased a computer (I'll use Windows in this analogy) and it came with one user account that was only part of the "Users" group, no local Administrator or account part of the Administrators group and no way to grant your one user account Admin rights? I'd be upset as I wouldn't be able to do much with it including; remove bloatware, install my own applications, replace the stock AV/Malware software, upgrade my video driver or even start from scratch. I mean the first thing I do when I get a new computer is format the HDD lol. I know it might be a silly analogy, but I don't see how it's any different than having root access on my phone.
- Remove bloatware (system apps you don't want/need)
- Custom Kernels (though the stock kernel on this phone is amazing out to the box, custom gives us more access to manage wakelocks, color control, vibrations, among other kernel items) (EXKM and Kernel Adiutor are a couple great apps to tweak your custom kernel)
- Customer recovery (easy backup/recovery, easy flashing of Zips, etc...)
- Untethered system theming including; custom fonts, launcher tweaks, status/navbar tweaks, etc...)
- System wide ad blocking
- Full system backup/restore (Titanium Backup is amazing for full system backups and then upload to cloud storage of your choice)
- Terminal root access (every have horrible battery drain and can't figure out exactly why quick and easy? Drop to terminal, elevate using su, then run top and and see what app is hogging the CPU)
- Xposed modules for system customizations (I've used a lot over the years, but not on this phone yet. You will also FAIL SafetyNet if you use the Xposed Framework.)
- AUDIO MODS! I honestly don't know how I lived my life without apps like ViPER and Dolby on my phone
A/B Partitions
To hopefully help clear up some confusion here, I'll list some important points to take note of.
- The whole point of the dual partition setup is to make OTA updating easier, allowing for updating the OS in the background
- There are two system, two boot and two vendor partitions, but only one data partition
- Only one system and its corresponding boot partition are active at one time
- Whichever system/boot partition is active will use the one data partition
- Flashing a custom kernel, mod zip or Magisk will flash to the current active slot from recovery, however flashing the Google Image or a custom rom will flash to the inactive slot
- The recovery is part of the boot partition, meaning anytime you flash the stock or custom kernel, for example, you'll need to reflash your custom recovery again (unless you install a kernel zip created with AnyKernel2 by @osm0sis)
My Build
Sharing these details as if you are on a different image, kernel, carrier, etc... your results may vary.
Phone: Google Pixel XL 2 Black 128GB - purchased from Google Store / Hardware Version: rev_10
Carrier: Project Fi with eSIM & physical SIM
Android Version: Official 8.1.0 / Security Patch Level: February 5, 2018
Build Number: OPM1.171019.018
Kernel: 4.4.119-FlashKernel-Taimen-v2.20 (clang version 6.0.0)
Root: Magisk Manager 5.6.1(105) (patched dtbo NOT preserving "force encryption" or "AVB2.0/dm-verity") & Magisk 16.0(1600) / Modules: Busybox for Android NDK 1.28.1, Magisk Manager for Recovery Mode (mm) 2018.1.31, Single User Mod 1.4, ViPER4Android FX Materialized 1.5.1 (2.5.0.5)
Recovery: TWRP 3.2.1-0
APKs: SELinuxModeChanger v11.0, AdAway 3.2-60, Dolby, MinitBatteryResrouces
Convenient Play Store Apps: 3Minit Battery Settings, FiSwitch, Kernel Adiutor, Light Manager, Root Explorer, substratum (Swift Black), TiBu Pro (I do scheduled backups of my phone to my Google Drive) & Terminal Emulator (great to use Busybox commands like "traceroute" or "top" to find that app killing your battery!)
Android Platform Tools Install
1. Download the latest version for your computer OS (PC/Mac/Linux) from Google: https://developer.android.com/studio/releases/platform-tools.html
2. Unzip the downloaded file to your hard drive somewhere and:
- Windows: add to your PATH (google "add adb to path")
- Mac/Linux: From terminal of your choice "sudo install adb /usr/local/bin && sudo install fastboot /usr/local/bin" (run from within the extracted directory and enter your password when prompted)
- Windows 10 & macOS High Sierra detect the phone automatically, but older versions you may need Android Device Drivers. Just Google what you might need and how to do it if your phone is not detected automatically.
Unlocking
1. Turn your phone off.
2. Press and hold Volume Down, then press and hold Power.
3. Plug your phone into your computer.
4. From command prompt/terminal on your computer (run Command Prompt as Admin in Windows throughout this guide):
- fastboot flashing unlock
- fastboot flashing unlock_critical
NOTE: I've read a lot of back and forth on if we should unlock_critial or not. This is just my opinion, but if you're here to do all this stuff to your phone, want complete access to do whatever you want to it, just do it. It's better to be ready now for the future because every time you unlock or relock, it will factory reset your phone. I've been unlocked both regular and critical since the first boot when I took my phone out of the box. I'll also mention, I’m not entirely sure what steps will work or not work in this guide if you don't since I've never not been unlocked with critical.
5. Follow the instructions on the phone screen to do the factory reset.
Clean Start
1. Download the "taimen" for Pixel 2 XL factory image [8.1.0 (OPM1.171019.018, Feb 2018)]: https://developers.google.com/android/images
2. Turn your phone off.
3. Press and hold Volume Down, then press and hold Power.
4. Plug your phone into your computer.
5. Unzip the downloaded file to your hard drive somewhere and from the directory you extracted the files (CMD/Terminal):
- Windows: flash-all.bat
- Mac/Linux: ./flash-all.sh
- Unplug your phone from your computer
Initial Config/Prep
1. Go through the initial phone setup steps.
- Make sure you setup your Google account so you have access to the Play Store and you can activate your eSIM if that's what you're using.
NOTE: When setting up with only an eSIM, I ran into some bugs and caveats I had to figure out on my own as Google support couldn't figure it out let alone understand what I was trying to explain to them. I ordered a physical SIM and now have both an eSIM and a physical SIM installed and can switch between them.
Verizon SIM: As @jrbxx7 was kind enough to share below; if running a Verizon SIM, wait till after setup is complete before inserting it. That way the vzw apps don't get installed on google setup.
eSIM Caveat: If you have 2 Step Authentication turned on for your Google account and your phone is your only device with the Google Authenticator App or Google Prompt, you will have to use one of your backup codes to log back into your account as your phone will not be activated until it's completed in the Project Fi application.
eSIM Bug: After you go through the initial phone setup, let Play Store finish its updates and don't reboot yet. Open Play Store and search for "Project Fi", then click "Enable", but DON'T update it. Just open Project Fi, complete the activation then reboot your phone. You can update the Project Fi app after the activation is successful. I've tested this through three factory restores and the result is the same every time.
Physical SIM: No issues since your phone will just be activated after boot so you can receive SMS codes.
2. Enable Developer Mode: tap "Build number" under "About phone" 7 times.
3. Under "Developer options", enable "USB debugging".
4. Download necessary files:
- Magisk 16.0(1600): https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
- SELinuxModeChanger 11.0: https://f-droid.org/en/packages/com.mrbimc.selinux/
- AdAway 3.2-60: https://f-droid.org/en/packages/org.adaway/
- Dolby: https://forum.xda-developers.com/pixel-2-xl/how-to/viper-dd-atom-t3724096
- Kernel. I use @nathanchance Flash Kernel: https://forum.xda-developers.com/pixel-2-xl/development/taimen-flash-kernel-1-00-t3702057
NOTE: You can use whatever kernel you want, but I've only used/tested with Flash. Flash Kernel also has the proper drives to resolve the TWRP touch issues. I've read other custom kernels do as well.
- TWRP 3.2.1-0 (image & installer): https://forum.xda-developers.com/pixel-2-xl/development/twrp-alpha-pixel-2-xl-t3698148
5. Plug your phone into your computer.
- If prompted on your phone, save and allow USB Authorization for your computer.
6. Push downloaded files to your phone (CMD/Terminal):
- adb push <path_to_Magisk_file>.zip /sdcard/Download
- adb push <path_to_SELinuxModeChanger_file>.apk /sdcard/Download
- adb push <path_to_AdAway_file>.apk /sdcard/Download
- adb push <path_to_Dolby_file>.zip /sdcard/Download
- adb push <path_to_Kernel_zip_file>.zip /sdcard/Download
- adb push <path_to_TWRP_image_file>.img /sdcard/Download
- adb push <path_to_TWRP_installer_file>.zip /sdcard/Download
Install Kernel & TWRP
NOTE: As of the Google February security image release, TWRP will no longer decrypt. You have three options to flash in TWRP until it's fixed; disable security before booting to TWRP, use USB storage via your OTG adapter, or put the files you need in the /data partition.
1. adb reboot bootloader (CMD/Terminal while your phone is still plugged into your computer)
2. Flash TWRP:
- fastboot boot <path_to_TWRP_image_file>.img
- Once in TWRP, install the TWRP_installer.zip file
- Reboot into TWRP
- Install Kernel.zip file
- Install the Magisk_16.0(1600).zip file
- Reboot to System.
3. Configure Magisk:
- Open Magisk Manager
- (OPTIONAL) Patch dtbo by unchecking both "force encryption" and "AVB2.0/dm-verity", tap "Install", tap "Install", tap "Direct Install (Recommended), then reboot
NOTE: By patching dtbo, you will receive a message on every boot that says something along the lines of "There's an internal problem with your device". This is perfectly normal when patching the dtbo and can be ignored as nothing is broken. Now, to be honest, I patch dtbo as I can't get certain things to work properly without, like Dolby, and the message doesn't bother me as it's only on boot up. I know patching dtbo is necessary for some things. For example, I don't think you can do manual build.prop edits without editing dtbo, if I'm not mistaken. I have had a few others on other threads say they were able to get Dolby to work without patching dtbo and just using SELinux in "permissive" mode, but I couldn't. Up to you, hence the "optional" part. If you decide to patch dtbo and want to go back, just flash the stock dtbo image file in fastboot or TWRP.
- Open Magisk Manager
- Goto Settings and tap "Hide Magisk Manager"
- Reopen Magisk after it's done
- Goto Settings and make sure "Magisk Hide" and "Systemless hosts" are both enabled
- Gogo Magisk Hide and check the applications you need to hide from Root (banking apps, authenticators, etc...)
4. If Play Store is not showing as "Certified" under Play Store Settings, clear Data and Cache on the Play Store under Phone Settings. Your Play Store will now be "Certified" under the Play Store Settings.
Install/Configure SELinuxModeChanger and AdAway
NOTE: It's my understanding that SELinux does not need to be set to "permissive" for ViPER and Dolby to work, but I can't get them to work otherwise. My Dolby will FC without setting SELinux to "permissive", which is why I'm adding it to my guide in case someone else is having the same issue. You can use the Magisk Module script if you want, but I like the convenience of the App to turn on and off easily.
1. Open "Downloads" from the App Launcher on your phone.
2. Install both SELinuxModeChanger.apk and AdAway.apk.
3. Open SELinuxModeChanger:
- Tap "Permissive"
- Tap "Automatically start on boot"
4. Open AdAway:
- Open Preferences and make sure "Enable systemless mode" is enabled". It's normal to be Greyed out. This is verification from the Magisk Settings you set above.
- Tap "Download files and apply ad blocking"
5. Reboot phone.
Install & Configure Magisk Modules / Dolby
1. Open Magisk Manager and go to Downloads:
- Download "Busybox for Android NDK" (some root apps need this, but it's also nice to have these utilities)
- Download "Single User Mod" (needed for latest TWRP install to my understanding, but it worked for me without. I like this anyway because I don't share my phone)
- Download "ViPER4Android FX" (make sure to get the v1.5.1(2.5.0.5) version) / during install you will be asked what version and theme, chose the 2.5.0.5 driver version and the Materialized version (needed for Dolby).
- Reboot Phone
2. Open ViPER 4 Android FX application:
- Under Settings tap "Turn on developer mode" then tap "Disable SELinux"
3. Reboot Phone.
- After reboot, open ViPER 4 Android FX application and enable/configure the effects you want.
NOTE: Be patient after a phone reboot. It sometimes takes a minute for the Magisk modules to load.
4. Reboot to TWRP.
- Install Dolby.zip file
- Reboot into System
5. Open Dolby, and if it force closes, make sure your SELinux is "permissive" first and if you still have force closes, patch dtbo following instructions above.
Themes & Mods - Screenshots attached below!
I use substratum and Swift Black from the Play Store for my system wide theme. I use Light Manager from the Play Store for custom status lights for applications, etc... You can also get more customization of what icons to show or not show on your status bar by pulling down the notifications at the top of the phone and holding down the Settings gear icon until you feel a vibrate. You'll now have "System UI Tuner" under Settings->System. I'm also using the following Mods:
- SearchLess Launcher: https://forum.xda-developers.com/pixel-2-xl/themes/mod-pixel-2-xl-launcher-mods-8-1-0-dp1-t3701939
- Rosemary Font: https://forum.xda-developers.com/pixel-2-xl/themes/font-flashable-ubuntu-font-zip-pixel-2-t3710892
- Various Mods Aroma w/ 3Minit Battery: https://forum.xda-developers.com/pixel-2-xl/themes/various-mods-8-1-december-update-t3721741
- Substatum /w Swift Black (I dont theme System UI or System UI Navigation as part of my setup with the Various Mods Aroma)
- ViPER w/ Audiophile X profile & Dolby using Music profile (Volume Leveler / Surround Virtualizer / Intelligent EQ: Open)
Updating
I'm going to keep these steps kind of generic and provide the order in which things have to be done (order is important), however for the details just follow the steps for each part above. You shouldn’t have to do the setup for Magisk Modules again unless:
- You ran into issues and needed to do a clean start with Magisk using the Magisk Uninstaller
- You are doing a Google Image update
Magisk - Push the updated Magisk Zip to your /sdcard/Download folder, boot into TWRP, flash new Magisk Zip, reboot into System, go through Magisk setup steps again.
Kernel – Push the updated Kernel Zip file to your /sdcard/Download folder, make sure you have the Magisk Zip file in your /sdcard/Download folder as well. Reboot to TWRP, flash new Kernel, flash Magisk, boot System and setup Magisk again.
TWRP – Push the updated TWRP Zip to your /sdcard/Download folder, reboot to TWRP, flash new TWRP Zip, boot into TWRP to test, boot System.
Google -
1. Disable any screen security you have.
2. Disable and uninstall Substratum themes, if you have any.
3. Full backup of some sort recommended!
4. Boot to Bootloader and do a flash-all (without -w) of 8.1 factory image, boot to System and allow the update to finish.
5. Boot back to Bootloader, boot TWRP, install TWRP, reboot to TWRP, install Kernel Zip file, install Magisk Zip file, boot back to System.
6. Complete Magisk setup steps (Magisk hide, App hide, systemless, etc..), check SafetyNet.
7. Apply any mods and themes in Substratum.
Have fun!

Right on brother. My own journey is pretty much a mirror of your write up and I can't think of a single thing to add. Nice work. We have the same setup. Lol

CyberpodS2 said:
Right on brother. My own journey is pretty much a mirror of your write up and I can't think of a single thing to add. Nice work. We have the same setup. Lol
Click to expand...
Click to collapse
Thanks man! Yeah, this stuff has always been fun to me. I don't mind "breaking" my phone so I have to figure out how to fix it. lol I lost count how many times I wiped, flashed, etc to come up with my list.
I've also updated the guide to include "updating" stuff.

felosisman said:
Thanks man! Yeah, this stuff has always been fun to me. I don't mind "breaking" my phone so I have to figure out how to fix it. lol I lost count how many times I wiped, flashed, etc to come up with my list.
I've also updated the guide to include "updating" stuff.
Click to expand...
Click to collapse
Exactly, I got really quick at starting from scratch... Lol

Nice write up! One note if u feel like adding it, if running a verizon sim, wait till after setup is complete before inserting it. That way the vzw apps dont get installed on google setup.

jrbxx7 said:
Nice write up! One note if u feel like adding it, if running a verizon sim, wait till after setup is complete before inserting it. That way the vzw apps dont get installed on google setup.
Click to expand...
Click to collapse
Thanks for the addition, I"ll add it now! I don't have a VZW SIM so I would never have known lol.

This is the best guide on XDA now! I've been reading 10 different threads to do stuff, but someone who understands how it all works together can make it so much easier... Thanks again [emoji106]
Sent from my [device_name] using XDA-Developers Legacy app

slaydog said:
This is the best guide on XDA now! I've been reading 10 different threads to do stuff, but someone who understands how it all works together can make it so much easier... Thanks again [emoji106]
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
You're welcome! I'm happy to know this is helpful to folks.

Sticky?
Mods,
Is there any way to make this thread a sticky so it's easier for everybody to find?
Thanks!

jrbxx7 said:
Nice write up! One note if u feel like adding it, if running a verizon sim, wait till after setup is complete before inserting it. That way the vzw apps dont get installed on google setup.
Click to expand...
Click to collapse
What exactly is installed for Verizon apps? I didn't notice them on my install. Not saying they are not there, just didn't notice the changes.

felosisman said:
Mods,
Is there any way to make this thread a sticky so it's easier for everybody to find?
Thanks!
Click to expand...
Click to collapse
I think this thread is worth a sticky because it covers a lot of stuff that other guides don't, and covers them well. TWRP wasn't even a viable option when other guides were made, and it has made things much simpler...
Sent from my [device_name] using XDA-Developers Legacy app

Thank you for the guide. So I assume that if I were to brick the device I could use the factory images and fastboot to restore? Does anyone know what would happen if you tried to flash an older factory image street upgrading through OTA?
Sent from my Pixel 2 XL using Tapatalk

andrewjt19 said:
Thank you for the guide. So I assume that if I were to brick the device I could use the factory images and fastboot to restore? Does anyone know what would happen if you tried to flash an older factory image street upgrading through OTA?
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
You should always be able to restore using the factory images from Google. In all the years I've been doing this, I've never once actually bricked a device to where is wouldn't work anymore. Just basically boot up to the bootloader and run the flash-all script. You can get the full Google images and instructions here: https://developers.google.com/android/images
As for downgrading, I've not personally done it. I know folks have gone from the 8.1 DPs back to 8.0, but if I'm not mistaken Google is making it hard to downgrade for security reasons. Once 8.1 is officially released, we may not be able to go back to 8.0, for example. I'll let others chime in with their experiences.
EDIT: After reading your post again, if you mean you took the November OTA you will be fine. The latest factory image from Google is the same as the Nov OTA.

please delete

felosisman said:
You should always be able to restore using the factory images from Google. In all the years I've been doing this, I've never once actually bricked a device to where is wouldn't work anymore. Just basically boot up to the bootloader and run the flash-all script. You can get the full Google images and instructions here: https://developers.google.com/android/images
As for downgrading, I've not personally done it. I know folks have gone from the 8.1 DPs back to 8.0, but if I'm not mistaken Google is making it hard to downgrade for security reasons. Once 8.1 is officially released, we may not be able to go back to 8.0, for example. I'll let others chime in with their experiences.
EDIT: After reading your post again, if you mean you took the November OTA you will be fine. The latest factory image from Google is the same as the Nov OTA.
Click to expand...
Click to collapse
Thanks buddy for the reply. That's what I figured but my personal policy had always been to "find" the fix before I tamper with anything. Once I unlock the bootloader I'm assuming I cannot take OTA's in typical fashion right? Also is relocking the bootloader the same as unlocking (obviously using the opposite command)? Thanks so much.
Sent from my Pixel 2 XL using Tapatalk

andrewjt19 said:
Thanks buddy for the reply. That's what I figured but my personal policy had always been to "find" the fix before I tamper with anything. Once I unlock the bootloader I'm assuming I cannot take OTA's in typical fashion right? Also is relocking the bootloader the same as unlocking (obviously using the opposite command)? Thanks so much.
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
You're welcome! Absolutely, might as well be prepared just in case.
So, I've not tried it myself from "System Updates", but to my understanding you can still take OTA with the bootloader unlocked. I think the OTAs stop working when the System partition has been modified. But considering pretty much everything we do these days is Systemless, I think it'd be fine. I did manually install the November OTA from fastboot with my bootloader unlocked and it worked fine. To relock, yeah the command is pretty much just the opposite.
"fastboot flashing lock" would relock your device. Keep in mind though, every time you lock or relock it will wipe your device.

Sticky Request
I've done sone searching and can't figure it out, but does anybody know if there is an official way to request this to be a sticky?

felosisman said:
I've done sone searching and can't figure it out, but does anybody know if there is an official way to request this to be a sticky?
Click to expand...
Click to collapse
Your guide helped
Cheers ?
You using any other mods
Sent from my Google Pixel 2 XL using XDA Labs

Prattham said:
Your guide helped
Cheers
You using any other mods
Sent from my Google Pixel 2 XL using XDA Labs
Click to expand...
Click to collapse
Excellent, happy it was helpful!
No, I'm only using what I've got posted; ViPER, Single User and BusyBox.

I'll go ahead and ask this here since the Viper thread is so busy and I have seen a lot of answers and it's things that I've already tried over and over again. But, no matter which Viper version I download whether it be through magisk or a zip install via TWRP, I can never ever ever get the drivers to install. You got Viper in the title of your thread but I only seen one line of Viper in the op and that's to do with setting selinux to permissive, which I already have set to.
So does anybody have any out-of-the-box advice on what to do to get that Viper driver to install on a pixel 2 XL running 8.1 .0 DP2?
I'll spend all my 8 thanks for the day thanking somebody if they can help me figure this out.
Edit: I did just notice some more Viper instructions, my bad. I will try those out and report back
Edit 2: So I followed your instructions to the T, and the driver still won't install. Anyone got any ideas? It's not some sort of bug with the program is it where the driver has really been installed already but it's just saying that it's not?
Sent from my Pixel 2 XL using XDA Labs

Stable AOSP 7.1 setup w/ working Google and Voice - ACHIEVED!

This guide is to install AOSP 7.1.2 and GApps on the Samsung Galaxy Tab 10.1, model GT-P7500 ("p4"). It has also been reported working on the Wifi-only version GT-P7510 ("p4wifi") with minor changes, noted in the instructions. I will update this main post as better information becomes known.
Updated 2018-Aug-06
After a couple dozen wipe-and-retry sessions, I thought I'd share my current setup which to date has been the most stable configuration I've had between Nougat and Oreo. I've had absolutely no stability issues so far with this setup, and I even have fully functional Google search, voice search (and Ok Google), and voice typing - no crashes. Anyone who's tried to install a modern GApps on these devices will know the frustration of literally endless and unstoppable "....has stopped" messages!
Here's what I've got working on my GT-P7500:
- AOSP Nougat 7.1 (all thanks to @decatf)
- Fully functional Google Apps - NO "... has stopped working"/"... keeps crashing" issues. None.
- Google Search, Google Now, voice search, voice typing, and other voice-related services ALL WORK. No crashing.
I should also mention that I have NOT included the instructions to create the 1GB /system partition. I figured this out when I was trying to install modern GApps that needed more space; in the end the instructions below turned out to be the best and do not require the expanded space. I have posted the file in another thread if anyone wants it for other purposes.
Installation Instructions:
Download these files to your PC. Some files are different for different variants of the device - make sure you get the right ones for your device!
Odin v1.85 (download)
Use only this version, the newer ones don't work well with this device.
TeamWin Recovery Project
Custom unofficial versions for p4* by @decatf. Direct download links below; select the right one for your device. (original thread / downloads page) Some have reported issues with TWRP 3.1.1; if you experience issues, try TWRP 2.8.7.0 instead.
TWRP 3.1.1.0 - for GT-P7500/p4 (download) - for GT-P7510/p4wifi (download) - for SGH-T859 (download)
TWRP 2.8.7.0 - for GT-P7500/p4 (download) - for GT-P7510/p4wifi (download) - for SGH-T859 (download)
Android Open Source Project 7.1.2 Custom Built for Galaxy Tab 10.1 - AOSP 7.1.2 built for p4* by @decatf (downloads page) (original thread).
decatf's AOSP 7.1.2 2017-10-05 - for GT-P7500/p4 (download) - for GT-P7510/p4wifi (download) - for SGH-T859 (download)
SuperSU v2.82 (download) (original thread).
Custom GApps from decatf's Lollipop release (download) (original thread).
Yes, really, the Lollipop version. Just trust me.
Boot into Download mode (instructions).
Connect to PC.
Start up Odin v1.85.
If the device is properly recognized, it will show up in the first of the row of white squares at the top. If not, install the Samsung USB Drivers and start again.
Use Odin 1.85 to install TWRP 3.1.1 Custom.
Reboot to Recovery mode (instructions).
Wipe the device, including the /system partition.
Transfer the AOSP, SuperSU, and GApps files to the device.
Install decatf's AOSP 7.1.2.
Install SuperSU v2.82.
Do NOT install GApps at this time, despite all the instructions everywhere else that you would normally install GApps before the first boot. This older release is being used to get a version of the Google app that works on this tablet's no-longer-supported CPU, and the install is done after first boot to bypass Google's Setup Wizard which will put you in an impossible-to-exit loop.
Reboot to System, and allow complete boot-up. Note that the boot will take several minutes as Android 7 does its thing setting up - be patient!
Once fully booted, wait a minute for the system to settle, then reboot back into Recovery.
Install custom GApps.
Reboot to System. Boot should be much faster this time.
You can do this part later, but the final steps will be smoother if you do this first.
Install a CPU Speed Control program of your choice. Device Control, 3C Toolbox, No-Frills CPU, heck even Automate or Tasker if you already have a script setup.
Set your CPU Max speed to 1400 MHz (1.4 GHz). I find stability issues at anything above 1400 on my device; your mileage may vary. When testing speeds, do not set them to apply on boot until you are certain it is still stable, or you may have some difficulty reverting.
Optionally Set your CPU Governer to Performance. This results in a smoother system overall, and doesn't seem to have much of an effect on battery life. I also use some settings to drop the Governer to Interactive when the screen is off, back to Performance on screen on. You can do this using any number of programs like Automate, Tasker, IFTTT, 3C Toolbox, and many others...
Most important step - open Play Store, go to My Apps, select Google, click the Menu in the top-right corner, and uncheck Auto-Updates. Alternately, you can go to Play Store Settings, and disable auto-updates altogether, but that is more troublesome than simply inhibiting the single app.
Update Google Play Services. It will need to be updated before most of the newer apps will function, so might as well do it now.
Install all the other Google apps you want from the Play Store, and any updates... you will need to update Play Services before most of the newer apps will function... but never, ever update the main Google app.
Open Settings.
Scroll to the bottom, and open Language and Input. Select Physical Keyboard settings, and enable "Show Virtual Keyboard". This ROM fakes having a physical keyboard always connected for some reason, so you will never see an on-screen keyboard unless you turn this on.
As long as we're in Settings, go to Security, and enable Unknown Sources. You'll probably want this.
Set up your Wi-Fi connection.
Adjust any of your other preferred settings.
You're finished! Try installing some of the software below.
Known issues:
Browser will crash once or twice during the first few minutes of operation for unknown reasons. Doesn't seem to happen again after that.
Recommended software that works: (I'll add Play Store links later...)
3C Toolbox / 3C Toolbox Pro - I've found this to be an excellent package for numerous functions including CPU control, app control, and battery reporting - I was able to quickly determine which of my chargers would charge it fastest. Also gives options for optimizing device on each boot and a number of other useful functions.
Via Browser, a modern browser built to be slim and speedy "for geeks". It is surprisingly responsive compared to the other two options on this old device.
decatf's Chromium for Tegra 2 CPUs (direct link to Downloads). This is a modern browser with all the features you expect, but compiled to run on the older CPU. It is a little bit slow but is essentially Chrome without the official branding, including the ability to sync with Chrome on other devices. @decatf is nice enough to keep compiling new versions to keep it roughly on par with Chrome, let's hope he keeps it up.
Firefox Focus, a privacy-focused version of the Firefox browser maintained separately. For whatever reason, this one is still compiled for older devices where the full browser is not. It is a modern and relatively speedy browser which can be nice to have on hand, but purposely eliminates features most people want in a daily-use browser, like bookmarks, history, etc.
Got suggestions for useful software that functions well on this old device? Let me know!
Mainstream software that WILL NOT WORK, even though it shows up as compatible in the Play Store and will install fine (but complain about your CPU type or report 'unsupported device'):
Google Chrome browser - as an alternative, check out decatf's Chromium, noted above.
Mozilla Firefox browser - as an alternative, check out Firefox Focus and Via Browser, noted above.
Find another one? Let me know! There were more but I've forgotten.
Original post...
You read it. I have a Tab 10.1 (GT-P7500) which I have managed to configure with decatf's AOSF Nougat 7.1, Google Apps with fully functional Google App and Voice Search (NO crashes), and with an enlarged /system partition so there is actually room on the partition to install some extra system apps without mucking about with linking or anything.
I slapped a quick guide to the GApps bit on the end of decatf's 7.1 thread in Development, but I wonder if there is enough of an interested audience for me to write up how I did the whole thing?
Disclaimer: It may or may not involve pentagram carvings and Satanic rituals.
Click to expand...
Click to collapse

I could find little to no information on how to do any of this, but I pieced it all together, experimented, and got it working. I've solved most of the problems I was having, including the ones that seem to be most commonly posted here from what I can see.
So here's what I've got working on my GT-P7500:
- decatf's AOSF Nougat 7.1
- Fully functional Google Apps, NO "... has stopped working"/"... keeps crashing" issues. None.
- Google App WORKS. No crashing.
- Google Now WORKS. No crashing.
- Voice search WORKS. No crashing.
- Voice typing and other voice-related services WORK. No crashing.
- Larger /system partition.
What I haven't figured out or haven't worked on yet:
- Some apps do not seem to be reading the compass properly, but I think a test app showed it as working, so needs more investigation...
- Get (standard) Firefox running.
- Which partitions can be safely reduced or eliminated to increase available data space.
- Experimenting to see if any voltage adjustments will allow 1.6GHz overclocking to function without freezing up. My device will only run stable at 1.4GHz

pOST the instructions
please post instructions

Yes Please!
Please post the instructions. I still use the OG Galaxy Tab 10.1 regularly. Yes its slow as all heck, and barely runs 2 apps at a time. But Id like to do this just for giggles before my Yoga Book comes in the mail and i lay my 6yr old Tab to rest.

I'd also be very much interested in this. I just got one of these as a gift for a NGO that I'm working for, and would love to be able to use it...

yes please!
Please post instructions/guide. Would love to able to update the tablet. My daughter uses it and it's so slow

pls advice if said method can be aplied to P7100

I am also interested in what you did to get everything working (for me, the Setup Wizard continually crashes right after the first screen).

Was this guide ever posted and has anyone tried it

robbinmoreka said:
Was this guide ever posted and has anyone tried it
Click to expand...
Click to collapse
Yes they posted it here:
https://forum.xda-developers.com/showpost.php?p=75777254&postcount=1046
I followed all the steps up until I got to 'install SuperSU'. First root I did, it stopped the home button/recent apps button from working. So I started again and didn't install it
GApps worked perfectly and I was able to login to google and download all my apps
Once I rebooted the system, the tablet was stuck on the "Android" logo for about 5-8 mins so I left it and then it loaded normally. 2nd time it loaded perfectly.
Installed Device Control [root] but it said it wasn't able to access the processor tab so uninstalled.

FYI, I had to use TWRP 2.8.7.0 available at the same link https://forum.xda-developers.com/devdb/project/dl/?id=24424 for my p4wifi. I tried the latter one, but didnt work so just copied over the older tar file, installed in TWRP itself, rebooted recovery, and then the rest of the steps worked. Thanks OP for trying to bring this old tablet back to life!

When I install aosp-7.1-p4-20171005.zip, I got:
E3004: This package is for "p4" devices; this is a "p4wifi"
and stop installing
How to solve this?

oncinc said:
E3004: This package is for "p4" devices; this is a "p4wifi"
Click to expand...
Click to collapse
My bad, so sorry, I forgot to provide the links for multiple devices! I've fixed the main post. You want to get this file: https://forum.xda-developers.com/devdb/project/dl/?id=26886

Perfect guide, thank you! Brought my long forgotten tab back to life with some extra sparkle. I too had to use TWRP 2.8.7.0 to get the ROM to install on my P4. (Donwload link to 2.8 Recovery as the main thread links were down : https://get.xda-developers.com/dl/1....md5?key=juCucVnKuO7-Lt_mR3qH6g&ts=1534633325)

Word/Excel
Hi! I can't launch Microsoft Word/Excel/PowerPoint from Play Store. I get a message "This device uses a processor that doesn't meet the system requirements for installing Office.". Have I done something wrong during the update? Thanks!

Mine is running very smoothly including internet and video, however, I am having the following issues:
- home screen circle and task history triangle buttons in the bottom menu are not working
- when I plug in the USB cable my computer recognizes the device but no menu pops up on the tablet allowing me to select file sharing
- I can't access developer options in the settings menu (tapping 7 times on the build version does not bring it up)
So right now I can't move any files to the tablet.

robert_vdv said:
Mine is running very smoothly including internet and video, however, I am having the following issues:
- when I plug in the USB cable my computer recognizes the device but no menu pops up on the tablet allowing me to select file sharing
So right now I can't move any files to the tablet.
Click to expand...
Click to collapse
Slide down the notification bar. Select Nougat symbol to switch the USB mode.
Can you run Microsoft Word?

astepkin said:
Slide down the notification bar. Select Nougat symbol to switch the USB mode.
Can you run Microsoft Word?
Click to expand...
Click to collapse
Unfortuntately, something is wrong with my onscreen menus. I can't swipe down to expand the menu, so I only see the top row of symbols (wifi, user, flashlight, auto-rotate, Bluetooth) and can't get to any other symbols. I'm kind of new to this so I'm not sure what impact different versions of TWRP would have - my version is 3.0.3. Maybe I should update to the version noted in the post.
I get the same error for Word.

Good guide, but some inconsistencies in the sequence.
For example, you indicate to disable the auto-update on the Google app BEFORE to fill in your Google account: it's impossible.
And even after you enter your Google account, you need to install at least one application (and therefore activate the wifi) to see the Google app in the list "My applications".
Other than that, it's more stable than my previous installation, and just for that: thank you!

f4t2
Good guide, I successfully installed Nougat on my Tab 10.1. following your steps. Very smooth. BTW, I didn't install any Gapps son I can't provide any feedback about it. I can say overclocking to 1400 Mhz seems pretty stable on my unit.
Regarding the non-NEON issue, I found this guy built a relatively recent Firefox 59 package compatible with our device. It's not the latest version, but it's better than what we had. It works fine for me.:good:
If you're interested the project is here:
https://github.com/schmaller/Fennec4Tegra2

Oneplus 8T (Cyberpunk Edition) - HydrogenOS (Google Apps, Theme, OTA Updates!)

Originality/HydrogenOS
If you have a Chinese Cyberpunk Edition phone with OxygenOS, you'll notice that the Cyberpunk theme/assets are missing, and OTA updates lead to a boot loop. This guide will tell you how to restore the phone to its original software (HydrogenOS), unlock the bootloader, root it, and get Google Apps working. If you are American, this is the golden ticket. OTA updates will work and you will get the original theme/assets back.
I have made this guide because I purchased a Cyberpunk phone and the vendor installed OxygenOS. The Chinese Cyberpunk Edition phones are meant to use HydrogenOS. OxygenOS is not currently designed for the Chinese Cyberpunk Edition phones, despite many vendors installing it. I've spoken to Oneplus and it doesn't appear there are immediate plans to support the phone using OxygenOS.
This information is only for Chinese Cyberpunk Edition phones.
Rooting the phone is optional if you just want Google Apps.
Proceed at your own risk.
Setting Up
You're going to need to download and install these things for the remainder of the guide.
Minimal ADB/Fastboot (Download)
Oneplus USB Drivers (Download)
Qualcomm USB Drivers (Download)
If you've already been toying with the phone, you might already have these. If so, skip ahead.
Restoring HydrogenOS (Credit: Some_Random_Username)
You are going to want to download the MSM Download Tool, designed for Chinese KB2000 phones. This tool will wipe your phone and restore the original HydrogenOS software, as well as your Cyberpunk theme/assets.
You will need to download the tool here:
https://androidfilehost.com/?w=files&flid=320230 (Credit: g96818)
Rootk1t said:
https://androidfilehost.com/?fid=10763459528675590014 or https://drive.google.com/file/d/1-MwwMBiszDvAoCoqH1P5aZRaLvDFL_66/view
The difference is only in HOS version.
If your phone is made after march 2021, i suggest using latest one HOS MSM (google link).
Click to expand...
Click to collapse
After downloading:
Extract the archive to a folder.
Remove any Chinese characters from folder names (if applicable).
Open "MsmDownloadTool V4.0".
Under "User Type", select "Others".
Click "Next".
Notice that "Target" is selected on the dropdown in the top-right of the window.
Change the option from "Target" to "H2" instead.
Now make sure your phone is ready:
Turn your phone off and wait a few seconds.
Press the "Start" button on the tool.
Hold both volume buttons down, while plugging your phone in through USB (to enter Qualcomm EDL mode).
The download tool will begin to work it's magic (should take 200-300 seconds).
Once it says "Download Complete", your phone should reboot into HydrogenOS.
Close the tool completely.
Perform the phone's setup, then decide whether you want to root the phone, or just install Google Apps. Your phone will be wiped if you unlock the bootloader.
If your device wasn't detected when running the tool, make sure you have the Qualcomm USB driver installed. To do this, open device manager. Under "QHUSB_BULK", select "Update Driver Software", and use the .cab file you found earlier.
Unlock the Bootloader (Optional)
Before you may root the phone, you will need to do the following.
Enable Developer Mode:
Open your Settings application and go to "About Phone".
Tap the section that says "Build Number" five times consecutively.
You will now have developer mode.
Enable OEM Unlocking/USB debugging:
Open your Settings application and click the search button.
Search for and enable the option: "OEM unlocking".
Search for and enable the option: "USB debugging".
You will be asked if you want to trust the device when it's plugged in. Click "Allow".
You will want to do the following, using the ADB/Fastboot you downloaded:
Make sure your phone is plugged in.
Run the following:
adb reboot bootloader
Your phone will reboot into the bootloader.
Run the following:
fastboot oem unlock
Use the volume/power buttons on your phone, to confirm.
Your phone will reboot and wipe itself, as well the Chinese applications. Perform the phone's normal setup again.
The bloatware and Chinese apps will return when you perform an OTA update at the end of the guide. They can also be removed/disabled.
Rooting (Optional)(Credit: DroidFreak32)
To root the phone we will be installing Magisk, using a patched boot.img from your current version of HydrogenOS. In this case, we are using version 11.0.1.2 (the version of the MSM Download Tool). I will be providing the boot.img from my phone, which I have used personally.
You will want to download the following:
Patched 11.0.1.2 Boot.img (Download)
Canary Magisk Manager (Download)
Preparation:
Re-enable developer mode, as well as USB debugging. Just like you did in the previous section.
Transfer the app-debug.apk to your phone, and install it through the phone's file manager.
Copy "magisk_patched_11.0.1.2.img" to your computer's ADB directory.
Rooting:
Run the following:
adb reboot bootloader
Your phone will reboot into the bootloader.
Run the following:
fastboot boot magisk_patched_11.0.1.2.img
Your phone will reboot, using the patched boot.img.
Enter the Magisk Manager app you installed earlier.
Tap Magisk (Install) -> Perform Direct Install
You will have root on reboot!
If Magisk says it needs to reboot to apply changes, you will need to follow the last set of steps again.
If for some reason the boot.img I provided doesn't work, you will need to follow DroidFreak32's guide. His guide is very detailed and will instruct you on how to create your own patched boot.img and root the phone.
Installing Google Apps (Credit: Steve0007 and @xxxrichievxxx)
To install, you will want to obtain a copy of the Google Play Store from a 3rd Party. @xxxrichievxxx suggested this solution, which worked for me regardless of unlock/root status.
You'll want to download, copy, and run the newest version from your device:
https://www.apkmirror.com/apk/google-inc/google-play-store/google-play-store-23-1-19-release/
We had also tried using WeebGapps, which has problems after updating:
https://t.me/s/WeebGAppsChannel?q=#Android_11+#magisk_mode (Requires Telegram)
Updating
Unlike on OxygenOS, you will actually be able to download and perform OTA updates, through the Settings app. If you do not follow the steps below when updating, you will lose root.
Disable your Magisk modules (if applicable) when updating, and re-enable after you have successfully updated!
I also recommend disabling "automatic system updates" via Settings, as they can break your root.
Follow these steps:
epr said:
- Go to System-Update
- Tap OK when the message that you are rooted appears
- Tap "Download and install"
- Wait until you are prompted to reboot - DO NOT REBOOT NOW!
- Open Magisk Manager, select install -> Install to inactive slot and start installation
- When Magisk has finished installing, reboot and you stay rooted with latest OTA.
Click to expand...
Click to collapse
If you are missing the Play Store after updating, install it from here. If you happen to mess up or lose Google Apps, try uninstalling/reinstalling the module.
If you do happen to lose root, you will want to follow DroidFreak32's guide, as I've only provided the patched boot.img for 11.0.1.2.
Bloatware
You're probably annoyed by all the preinstalled garbage. I've made a short script that disables the Chinese market and removes all 3rd party Chinese (By_3rd and heytap) applications.
Removing Market and Almost All 3rd Party Apps:
Visit here: https://pastebin.com/raw/3SsA1tpc
Open notepad and save the above text as a .bat file.
Copy and run the file from your ADB directory.
You will likely need to run this script each update, as applications are added back on update. I've decided to leave the other applications on my device for now. If you want to remove even more, Steve0007 recommended this resource.
Credits
Steve0007 and xxxrichievxxx for helping to find the solid solution for Google Apps.
WeebGApps for the module that installs Google Apps.
DroidFreak32 for his thread on rooting the Oneplus 8T.
Some_Random_Username and g96818 for uploading/sharing the MSM download tools.
Most of this information is compiled from other sources, so consider supporting the developers listed above.

Informative and well explained. It will definitely help a lot of users.

Very helpful, good job
Should be sticky.

sunmughans said:
Informative and well explained. It will definitely help a lot of users.
Click to expand...
Click to collapse
Hopefully it prevents some headaches. Vendors are still shipping the phones out with OxygenOS.
Steve0007 said:
Very helpful, good job
Should be sticky.
Click to expand...
Click to collapse
Wouldn't exist without your help!

Awesome! Going to try this out today

AWESOME!!!! Thank you very much!! Is google play installed as well? Last time I read something about all the google apps installed except Google play lol

Updated the bloatware section. The script will now remove 40 bloatware apps. These apps may conflict with Google Play, so I do suggest removing them.
xxxrichievxxx said:
AWESOME!!!! Thank you very much!! Is google play installed as well? Last time I read something about all the google apps installed except Google play lol
Click to expand...
Click to collapse
Google Play has installed fine in my tests. However, updating might cause it to get removed. I'd keep a copy of the APK in your phone's storage, just so you have it if you need it.
You can find it here:
https://www.apkmirror.com/apk/google-inc/google-play-store/google-play-store-23-1-19-release/

Hi, it's very strange, because on all oneplus, you can put hydrogen or oxygen without any problem.
Some people buy cyberpunk édition on Giztop or cect without any problem...very strange, no ?
Another question, IS it possible to add other language on hydrogen if de want to use it ?
Thanks

g4seb said:
Hi, it's very strange, because on all oneplus, you can put hydrogen or oxygen without any problem.
Some people buy cyberpunk édition on Giztop or cect without any problem...very strange, no ?
Another question, IS it possible to add other language on hydrogen if de want to use it ?
Thanks
Click to expand...
Click to collapse
Try this: morelocale 2
MoreLocale 2 - Apps on Google Play
This is just MoreLocale2
play.google.com
or this
Locale Language (Pro) Set Locale & Language for Android - APK Download
Download Locale Language (Pro) Set Locale & Language apk 3.5.8 for Android. This application let activate your home language (locale) with ease.
apkpure.com

Right now I recommend updating the phone before installing Google Apps.

Went though this process to update, very well detailed. I went from Oxygen OS to Hydrogen then followed the rest of the steps to install Google Play.
I made the mistake of updating via OTA after restoring Hydrogen OS and had to repeat a couple step to get to the root step then followed the rest to install Google Play.
Youll need to download the 7z software to extract MSM software and one of the files needs a Telegram account. Its a messaging app that requires a phone number to create.
Also make sure you have the drivers sorted out, I had to do a bit of trouble shooting on the qualcomm drivers.
The cyberpunk theme is pretty cool.
I am having some spotty issues with google though, after updating OTA everything was fine but occasionally I will lose the play store. I have tried to directly install the apk and reinstall the module in magisk. But there is something kicking it off. The apps that I downloaded are still there, just the play store that drops. Edit: I am on module 4.0.4. Might try 4.0.5
Testing out the apps, I cannot get the maps app to work, keeps crashing. And for some reason I cannot log in to Chrome. It wont detect the account that is already logged into the phone (gmail, youtube etc) when I sign in manually it says 'This account already on device' I have signed in and out numerous times.
This is a pretty good solution to keep the cyberpunk theme, which you want if you have this phone. I get 5g speeds on US T-Mobile and have no issues with texts and calls. If the play store was more stable this will be a solid solution.
Props to @OniAraAra for compiling this detailed guide and members who contributed

Went through the WHOLE guide and I too was able to revert back to the Cyberpunk ROM! Super COOL!!! I am extremely happy! Thank you!
Also would like to note that Android Auto also crashes

I've been reading and mentally preparing all the steps by downloading the required files and walking through them, but I've no development experience and I'm worried that if I mess up a step, I would have no idea how to unstuck myself...
For example:
If your device wasn't detected when running the tool, make sure you have the Qualcomm USB driver installed. To do this, open device manager. Under "QHUSB_BULK", select "Update Driver Software", and use the .cab file you found earlier.
Click to expand...
Click to collapse
I tried to look up my device manager on my PC and I do not see "QHUSB_BULK" so little things like that worry me

Is it possible to convert European 8T to full cyberpunk version?

jirka607 said:
Is it possible to convert European 8T to full cyberpunk version?
Click to expand...
Click to collapse
Do not use this guide for that. It will not work. There's other threads on how to install the Cyberpunk goodies for a normal 8T.
Nables said:
I've been reading and mentally preparing all the steps by downloading the required files and walking through them, but I've no development experience and I'm worried that if I mess up a step, I would have no idea how to unstuck myself...
For example:
I tried to look up my device manager on my PC and I do not see "QHUSB_BULK" so little things like that worry me
Click to expand...
Click to collapse
For the most part, any accidents are easily reversible, as there's a great guide on unbricking here:
[OP8T][OOS KB05AA/BA/DA] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com
Arr6 said:
This is a pretty good solution to keep the cyberpunk theme, which you want if you have this phone. I get 5g speeds on US T-Mobile and have no issues with texts and calls. If the play store was more stable this will be a solid solution.
Props to @OniAraAra for compiling this detailed guide and members who contributed
Click to expand...
Click to collapse
It is as you say. Across multiple installs I've had minor issues with the Google Play store disappearing, but you can always reinstall the APK. I did not notice this until after I had made the guide.
@Steve0007 and I are looking for a more stable solution as we speak, so hopefully we'll have that soon!

OniAraAra said:
Originality/HydrogenOS
If you have a Chinese Cyberpunk Edition phone with OxygenOS, you'll notice that the Cyberpunk theme/assets are missing, and OTA updates lead to a boot loop. This guide will tell you how to restore the phone to its original software (HydrogenOS), unlock the bootloader, root it, and get Google Apps working. If you are American, this is the golden ticket. OTA updates will work and you will get the original theme/assets back.
I have made this guide because I purchased a Cyberpunk phone and the vendor installed OxygenOS. The Chinese Cyberpunk Edition phones are meant to use HydrogenOS. OxygenOS is not currently designed for the Chinese Cyberpunk Edition phones, despite many vendors installing it. I've spoken to Oneplus and it doesn't appear there are immediate plans to support the phone using OxygenOS.
This information is only for Chinese Cyberpunk Edition phones.
Proceed at your own risk.
Setting Up
You're going to need to download and install these things for the remainder of the guide.
Minimal ADB/Fastboot (Download)
Oneplus USB Drivers (Download)
Qualcomm USB Drivers (Download)
If you've already been toying with the phone, you might already have these. If so, skip ahead.
Restoring HydrogenOS (Credit: Some_Random_Username)
You are going to want to download the MSM Download Tool, designed for Chinese KB2000 phones. This tool will wipe your phone and restore the original HydrogenOS software, as well as your Cyberpunk theme/assets.
You will need to download the tool here:
https://androidfilehost.com/?w=files&flid=320230 (Credit: g96818)
After downloading:
Extract the archive to a folder.
Remove any Chinese characters from folder names (if applicable).
Open "MsmDownloadTool V4.0".
Under "User Type", select "Others".
Click "Next".
Notice that "Target" is selected on the dropdown in the top-right of the window.
Change the option from "Target" to "H2" instead.
Now make sure your phone is ready:
Turn your phone off and wait a few seconds.
Press the "Start" button on the tool.
Hold both volume buttons down, while plugging your phone in through USB (to enter Qualcomm EDL mode).
The download tool will begin to work it's magic (should take 200-300 seconds).
Once it says "Download Complete", your phone should reboot into HydrogenOS.
Close the tool completely.
Perform the phone's setup, then proceed to the next step. Your phone will be wiped again in the next step.
If your device wasn't detected when running the tool, make sure you have the Qualcomm USB driver installed. To do this, open device manager. Under "QHUSB_BULK", select "Update Driver Software", and use the .cab file you found earlier.
Unlock the Bootloader
Before you may root the phone, you will need to do the following.
Enable Developer Mode:
Open your Settings application and go to "About Phone".
Tap the section that says "Build Number" five times consecutively.
You will now have developer mode.
Enable OEM Unlocking/USB debugging:
Open your Settings application and click the search button.
Search for and enable the option: "OEM unlocking".
Search for and enable the option: "USB debugging".
You will be asked if you want to trust the device when it's plugged in. Click "Allow".
You will want to do the following, using the ADB/Fastboot you downloaded:
Make sure your phone is plugged in.
Run the following:
adb reboot bootloader
Your phone will reboot into the bootloader.
Run the following:
fastboot oem unlock
Use the volume/power buttons on your phone, to confirm.
Your phone will reboot and wipe itself, as well the Chinese applications. Perform the phone's normal setup again.
The bloatware and Chinese apps will return when you perform an OTA update at the end of the guide. They can also be removed/disabled.
Rooting (Credit: DroidFreak32)
To root the phone we will be installing Magisk, using a patched boot.img from your current version of HydrogenOS. In this case, we are using version 11.0.1.2 (the version of the MSM Download Tool). I will be providing the boot.img from my phone, which I have used personally.
You will want to download the following:
Patched 11.0.1.2 Boot.img (Download)
Canary Magisk Manager (Download)
Preparation:
Re-enable developer mode, as well as USB debugging. Just like you did in the previous section.
Transfer the app-debug.apk to your phone, and install it through the phone's file manager.
Copy "magisk_patched_11.0.1.2.img" to your computer's ADB directory.
Rooting:
Run the following:
adb reboot bootloader
Your phone will reboot into the bootloader.
Run the following:
fastboot boot magisk_patched_11.0.1.2.img
Your phone will reboot, using the patched boot.img.
Enter the Magisk Manager app you installed earlier.
Tap Magisk (Install) -> Perform Direct Install
You will have root on reboot!
If Magisk says it needs to reboot to apply changes, you will need to follow the last set of steps again.
If for some reason the boot.img I provided doesn't work, you will need to follow DroidFreak32's guide. His guide is very detailed and will instruct you on how to create your own patched boot.img and root the phone.
Installing Google Apps (Credit: Steve0007)
To install Google Apps, we will be using WeebGapps (Magisk Module). There is no custom recovery available, so this is the best way to sideload Google Apps currently.
You will want to download the zip from this link:
https://t.me/s/WeebGAppsChannel?q=#Android_11+#magisk_mode (Requires Telegram)
After downloading the zip:
Transfer the zip you have downloaded to your phone's storage.
Open Magisk Manager
Select the Modules icon (looks like a puzzle piece)
Select "Install from storage"
Install the module's zip file
Your phone will reboot, with Google Apps
If you receive version errors when installing the module, download an older version. Version 4.0.4 worked perfect for me.
Updating
Unlike on OxygenOS, you will actually be able to download and perform OTA updates, through the Settings app. If you do not follow the steps below when updating, you will lose root.
Disable your Magisk module when updating, and re-enable after you have successfully updated!
I also recommend disabling "automatic system updates" via Settings, as they can break your root.
Follow these steps:
If you are missing the Play Store after updating, install it from here. If you happen to mess up or lose Google Apps, try uninstalling/reinstalling the module.
If you do happen to lose root, you will want to follow DroidFreak32's guide, as I've only provided the patched boot.img for 11.0.1.2.
Bloatware
You're probably annoyed by all the preinstalled garbage. I've made a short script that disables the Chinese market and removes all 3rd party Chinese applications.
Disabling Market and Removing 3rd Party Apps:
Visit here: https://pastebin.com/raw/3SsA1tpc
Open notepad and save the above text as a .bat file.
Copy and run the file from your ADB directory.
You will likely need to run this script each update, as applications are added back on update. I've decided to leave the other applications on my device for now. If you want to remove even more, Steve0007 recommended this resource.
Credits
Steve0007 for working with me to find the solid solution for Google Apps.
WeebGApps for the module that installs Google Apps.
DroidFreak32 for his thread on rooting the Oneplus 8T.
Some_Random_Username and g96818 for uploading/sharing the MSM download tools.
Most of this information is compiled from other sources, so consider supporting the developers listed above.
Click to expand...
Click to collapse
Hello.
Thinking to experience the Hydrogen and using all related Google Apps at the same time but the file downloaded was in 7z format. Thought it is in zip format. How am I going to extract then?

Salam.Husin said:
Thinking to experience the Hydrogen and using all related Google Apps at the same time but the file downloaded was in 7z format. Thought it is in zip format. How am I going to extract then?
Click to expand...
Click to collapse
You'll need WinRAR or another program to extract the archive. Apologies for the confusion.

OniAraAra said:
You'll need WinRAR or another program to extract the archive. Apologies for the confusion.
Click to expand...
Click to collapse
Got it.
To be frank, how is it going? I mean with hydrogen os and having google apps workable at the same time?

Salam.Husin said:
Got it.
To be frank, how is it going? I mean with hydrogen os and having google apps workable at the same time?
Click to expand...
Click to collapse
After eliminating the bloatware, it's actually very nice. Asides from minor issues with the Play store vanishing, it should serve everyone's needs perfectly.
That said, I do encourage people abstain from installing the Google Apps if they are uncomfortable reinstalling the APK when or if it vanishes. We're finding a fix for this.

OniAraAra said:
After eliminating the bloatware, it's actually very nice. Asides from minor issues with the Play store vanishing, it should serve everyone's needs perfectly.
That said, I do encourage people abstain from installing the Google Apps if they are uncomfortable reinstalling the APK when or if it vanishes. We're finding a fix for this.
Click to expand...
Click to collapse
You mean, Google Play Store and/or Google Play Services, to be specific? It keeps vanishing even after all means taken into consideration?
Right now, I have already got the msm tool for hydrogen. Thinking about to go through it or not... hmmm...

[ROM][N][7.0][STOCK][G920W8][zerofltebmc/zerofltecan]SamStock November Patch (Lightly Debloated)[RE-PACK]

Original ROM: https://forum.xda-developers.com/t/...loat-7-0-920-5-w8-f-i-november-patch.3649798/
I removed several apps in the ROM including a very annoying DiagMonAgent app that caused it to continuously show popup notifications.
Here is a complete list of apps I removed from this ROM: http://dr.mywebcommunity.org/g920w8/debloat/20210831-samstock-debloat-results.html
My phone works super well with this setup.
Download information:
Location: androidfilehost.com
File name: 20210831-1914-sst05-safe.zip
File size: 1.4 Gb
Information
I did not include the AROMA options for different phone vendors so if you really need those files, please use original rom. I uploaded this rom for my peronal use and because I am trying to make a debloated rom and bring the size of the zip file back down to under 1 Gb but I have several issues with required apks causing bootloops. So for now, this is a fully functional re-packed rom. I do plan to re-pack the phone vendors in a futur aroma setup but for now, I am still struggling to debloat this rom entirely. I just needed a base stock rom with as little modification as possible and this is the only ROM I found to fit this category. I am fully opened to receive any kind of help or assistance. The goal is to change the ZIP file only through my Windows computer, change any files through Notepad++ if necessary.
If you want details of what has been done in the ROM, please refer to the original author's thread.
GOAL OF THIS RE-PACK
My goal is to keep the original system but remove every other useless things. I want to drop the ROM size to under 1 Gb. I want to remove all Samsung and Google apps that are not necessary for the system to work. If people want Google Play, I want to simply download it on Open GApps. Of course, for now, I have been unsuccessfully removing other apps and had several boot loops, this is the only package I managed to re-pack that has a successfull boot and work well with my needs.
Why use an old 7.0 version?
Honestly? Because everything! Bluetooth connection, camera, stability. Everything works. The only VERY annoying things I hate about v7.0 are:
PROBELM: Picture-in-Picture (PiP) mode does NOT work. Apps compatible with PiP will not display any PiP content such as floating video call windows.
SOLUTION: The only similar effect you can have is by enabling in the dev options the "Force activities to be resizable" at the very bottom. Then, in an app you want to have displayed in a floating window, tap on your "All apps" button and drag your app's window on the little square that says "Open in pop-up view".
PROBLEM: Dark modes for apps like GMail and the user interface is not supported unless you seriously start to tinker arround with very creative workarrounds I have not tested.
SOLUTION: I did not test any.
Kernel Source
The kernel supplied in this re-pack is the original kernel from SamStock's original package (G920W8) with no changes. Based off SamStock's thread which states:
Untouched. Completely stock out of the latest zip from sammobile.
Click to expand...
Click to collapse
So source is based off original Samsung Kernel Source.
ROOT Magisk
This rom is NOT ROOTED. I removed the outdated supplied Magisk from the original ROM since I prefer to use the latest available version that works without any issues. Just remember to rename the Magisk APK file's extension to ".zip" and flash after flashing this rom. I also use the original APK file to install after first boot because the zip only enables root access but the APK installs the Magisk manager app and enables the popup message to grant root permissions to apps. It is not a requirement since Magisk will download the app automatically when you try to open it the first time, but it just makes you spend less time waiting for the automatic download and installs the app immediately. Installing the APK manually will require a reboot.
AdAway
This is the goto app to remove annoying ads in almost all apps. ROOT is required. To install, head to ApkMirror and download version 4.3.6. That's the latest version that still works very well on Android v7.0. You will be required to do 2 reboots, one after installing the app and enabling adblock and one for updating the hosts file.
Google
You will have a long update list to go through your initial boot to update all apps from Google App Store INCLUDING the app store itself. Please pay attention to Google Services notification because you may need to manually update Google Services if it does not do it on it's own for apps to work such as GMail and other Google apps.
I suggest you disable the "upday" app which Google Update installs. I hate this app so much that I disable the notification, force stop AND disable the app. I have not found any solution yet to prevent this app from being installed.
XPosed Framework
You need the sdk24 version. It works and boots without any problems BUT, it's old and I found it to be pretty much useless. Some stuff such as the Dark mode for GMail module does not work anymore. So I do not recommend you to install XPosed unless you already are familiar with modules you want to use and already know that is working.
What I wil NOT do (unsupported models)
I own only the W8 version of the phone so any other models I cannot support. BUT, I can say this, you can refer to the debloated list above to remove the apps from the ZIP file and repackage the file yourself for your model by downloading the right version on the original author's mod page. As I mentioned, this is a safe debloat list where the phone successfully boots and setups.
I cannot test phone calls and SMS because I do not use this function on my phone. I use a SIP phone service through GrandStream Wave and VoIP.ms. So if you have any issues concerning phone calls or SMS, please comment or check the list of removed apps above and mention to me what is needed and I will post a new upload with the included package. While you may be waiting for my fix, I suggest you use the original author's files.
KNOWN ISSUES
You will need to install another launcher to be able to change wallpaper since I removed some of Samsung's core apps which were linked to the Samsung store including the wallpaper switcher. I recommend the Microsoft Launcher which is entirely free and has all the basic functions including notification dots and icon pack themes.
INSTALLATION
• Backup your system and files
• Boot in TWRP (Hold Volume Up+Home Button+Power Button)
• Format and advance wipe everything
• Install zip file
• Optional: Install Magisk (rename apk extension to zip)
• Reboot System
Stuck in a bootloop or unresponssive phone?
Hard reboot your phone by holding Volume Down+Home Button+Power Button. Once the screen goes black, immediately Hold Volume Up+Home Button+Power Button and you will be back in TWRP. If it fails, simply repeat the Volume Down hard reboot until you get the timing right with Volume Up afterwards. That's what I do and it works but hopefully, this should NOT happen because it does not on my end.
Permission: I requested month's ago permission from the author and never got an answer so I presume that the project is abandonned or not followed anymore. So if ever the author somehow has specific requests or want's me to remove this, I will do so without hesitating after contacting me through PM.
XDA DevDB Information
SamStock ROM Debloated, ROM for the Samsung Galaxy S6 G920W8
Contributors
Moiz Ahmed
Supported Model: SM-G920W8 ONLY
ROM OS Version: 7.0 Nougat
ROM Kernel: Linux 3.10.x
ROM Firmware Required: Latest Modem and Bootloader
Based On: Samsung Stock / SamStock Rom (G920W8)
Version Information
Status: Stable
Stable Release Date: 2017-07-31
Created 2017-08-01
Last Updated 2017-12-25
Re-Pack Date: 2021-08-31