[GUIDE] Root/Kernel+ViPER/Dolby+Theme/Mods - Google Pixel 2 XL Guides, News, & Discussion

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

Related

[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.

[TOOLS Fire HD 6&7 ] Rooting, Gapps, Launchers, Block OTA & Ads + More

Download the latest tools from the AFH link near end of post. It includes the changes in the attached "jobs" zip. You only need "jobs" if you downloaded the tools before May 11
EDIT May 29: Playstore is currently unreliable. Until updated, use the workaround here.
UPDATE May 17: Install Other Launcher and Install Kingroot tools may not complete if Windows username has spaces. I'll fix in next update. Until then, if your username has spaces, use this fix.
Here are tools for the 2014 Fire HD 6 and 7. A little late, I know, but some of you who still troll the forums may find them handy. Download the tools from AFH link, extract and run RUNME.bat.
IF YOU PLAN TO ROOT, TURN OFF WIFI NOW!
Tested working on OS 5.1.2.1 and below, except:
- Current Kingroot can't root 5.1.2.1. You need to downgrade. See "ROOT OS 5.1.2", below.
- OS 4: Only OTA blocking is implemented in the Block/Unblock jobs. [5/13/16 UPDATE: Also, Play Store isn't working on OS 4.
.. I probably won't fix it unless there's some demand. Try the video guide here. OS 4 users, also see post #11 for useful info about custom launchers.]
THE TOOLS
Install Play Store
Install Nova Launcher to /priv-app [root]
Install Other Launcher to /priv-app [root]
Uninstall priv-app Launchers [root]
Install Apps
Block/Unblock: OTA, ADS, AMAZON LAUNCHER, APPSTORE, AMAZON SEARCH [root]
Root Checker
Device Info
Root Tools
Install Kingroot ~ Root ~ Block OTA
Replace Kingroot with SuperSU [root]
DESCRIPTIONS
Before running a job, look here for any tips and instructions. This info is also in the readme.txt in the zip​
INSTALL PLAY STORE - Like it says. Works on both rooted and unrooted OS 5. Not for OS 4. EDIT May 29: Playstore is currently unreliable. Until updated, use the workaround here.
INSTALL NOVA LAUNCHER - Installs Nova to /system/priv-app so widgets work. If you just rooted, make this your first custom launcher. You can replace it or add a different one later.
INSTALL OTHER LAUNCHER Installs the launcher app in user_launcher folder to priv-app. Get the apk for the launcher you want (from apkmirror.com for example) and put it into the folder and run the job. EDIT 5/16/2016: Filenames must end with ".apk" No spaces allowed; replace with "_". (The tool will find spaces and pause while while you fix.)
HOW TO INSTALL GOOGLE NOW (also in Readme.txt):
It's much easier to install Google Now if Amazon is blocked, and you need a custom launcher to do that.
1. If you don't have a custom launcher installed, use Install Nova tool (installs Nova and blocks Amazon)
If you have a custom launcher, block Amazon so your custom launcher is running.
2. Get Google Now (small) from apkmirror.com, e.g., put into user_launcher folder and run Install Other Launcher job.
You'll boot to your "other" launcher
3. Run Google Now in app drawer and:
If prompted to Update Google App (Get it from Google Play), do it.
If prompted that other launcher is default, tap link to go to Amazon Settings. In Apps & Games>Manage all Applications: Swipe to All, scroll to your other launcher, tap it and see if "Launch by Default" is on. If yes, Clear Defaults. If no, go to your launcher settings and see if you can turn off default there.
Some launchers don't give up their default easily. If pressing home key doesn't show "Select Home App" after doing the above, run Block/Unblock tool and switch to Amazon. Then block Amazon again. After restart, press home key and you'll get "Select Home App" and be able to choose Google Now.
UNINSTALL LAUNCHERS - Uninstalls and deletes everything associated with a launcher installed to /priv-app. If multiple, prompts you to choose the one to uninstall.
INSTALL APPS - Installs all the apps in the user_apps folder. Put the apks into the folder and run the job. Filenames must end with ".apk" No spaces allowed; replace with "_". (The tool will find spaces and pause while while you fix.) Don't install a launcher with this; use one of the launcher tools.
BLOCK/UNBLOCK - OTA, ADS, AMAZON LAUNCHER, APPSTORE, AMAZON SEARCH
Except for OTA, these work only on rooted OS 5. OTA does a soft block on unrooted OS 4, hard block on rooted.
OTA: Disables update packages and renames DeviceSoftwareOTA.apk for a "hard" block. Unblock reverses it.
ADS: Blocks/unblocks the lockscreen ads.
AMAZON LAUNCHER: Block disables the stock launcher (Amazon UI) and the Appstore, which forces the home key to use your custom launcher. Unblock switches you to Amazon. Checks for custom launcher before disabling Amazon. Black screen with multiple custom launchers: If you haven't set a default launcher, disabling Amazon will boot to black screen. (System doesn't know which launcher to use.) Press home key (circle at bottom) for launcher choices. TIP: To easily switch between your launcher and Amazon, use @bibikalka's guide here to set up "one-tap switching" from launcher home screen.
APPSTORE: Blocks the appstore so in-app links take you to the Play Store (instead of throwing that stupid Appstore prompt). Amazon complains bitterly if you run this from Amazon UI, so use it at your custom launcher or just use the Amazon launcher block.
AMAZON SEARCH: If you have Google Search installed, blocking Amazon Search makes your launcher search bar use Google instead of Amazon shopping.
DEVICE INFO - Just some specs that I find interesting. Lazy man's way to find out which tablet is plugged in, OS it's running, whether rooted . . .
INSTALL KINGROOT, ROOT, BLOCK OTA - Installs Kingroot, prompts you through rooting and blocks OTA updates.
- Installs kingroot v.4.8.5 by default.
- You can skip installation if Kingroot already installed
- You can install a later version if available: Check for new versions here: http://forum.xda-developers.com/android/apps-games/one-click-root-tool-android-2-x-5-0-t3107461
ROOTING AND UPDATES: An update file can download while you're rooting. The Kingroot tool prevents it from installing as soon as you press Enter to tell the tool you're rooted. Then it looks for any downloaded file and if it finds one it tells you where it is and prompts you to delete.
Amazon says that updates install when the the device is not being used, but be aware that on OS 5 there's some risk. To minimize the risk, never leave the tablet idle while rooting. Just keep running Kingroot until root is successful and then press Enter to block installation of any download. (These instructions are in the tool.) To eliminate all risk, you can downgrade and root OS 4.5.3. On OS 4 the tool blocks update installation before rooting. (There's no way to do this on OS 5.) From OS 4.5.3, you upgrade with root in TWRP per bibikalka's root Tut.
True story: Kingroot once rebooted 5 times and told me "Root Failed" 3 times before finally succeeding. An update had downloaded to /cache, but the kingroot tool successfully blocked installation and found the file, which I deleted. So, although it's possible you could get upgraded, as long as you keep the tablet busy trying to root and then press Enter as soon as you're rooted, it's very unlikely.
REPLACE KINGROOT WITH SUPERSU - Installs W0lfDroid's sh script and prompts you through using it to replace Kingroot.
I reviewed and tested the script and it does (only) what it says: Removes all Kingroot (except Purify app, which tool uninstalls) and installs SuperSU. The tool uses SuperSU v. 2.4.6 for OS 5 (known working on OS 5.1.2) and SuperSU v. 2.4.9 for OS 4 (because 2.4.6 didn't seem to work).
FULL DISCLOSURE: I lost root one time after running this on OS 4. I think the problem was SuperSU 2.4.6 and that's why I changed it. I've tested many times and this only happened once, but you should know it happened. AFAIK W0lfDroid script is still the best free tool for the job.
ERRORS: Script was written to remove Kingroot from multiple android versions, so it tries to remove Kingroot files that don't exist on Lollipop. THIS PRODUCES LOTS OF ERRORS. THAT'S OK. I left in all commands so it will work on OS 4, too.
USE THIS SOON AFTER ROOTING. W0lfDroid's script should work fine even with root apps installed, but all I know for sure is it runs quick and easy on a "fresh" system.
ADB Sideload
There's an adb-sideload job in the jobs folder. I didn't put it on the menu because it uses commands that may not run on some systems. Also, if you know what you're doing, it's probably faster to manually sideload an update. If someone wants to try it, put the update bin file into adb_sideload folder and run sideload.bat.​WINDOWS TESTING: Script was tested on English-language versions of Win 7 Pro and Home. Some testing on Win 10. (Thanks @SpaceBananas!) There's nothing that can hurt your tablet, but there may be kinks to work out based on Windows version. Hope a tester will work with me to help make the tools accessible to everyone. Thanks!
ADB DRIVERS REQUIRED: Try the guide in first link below. If problems, try the second.
Guide: http://forum.xda-developers.com/fir...ivers-fire-t3189000/post62561840#post62561840
Other options: http://forum.xda-developers.com/showpost.php?p=63072252&postcount=2
ROOT OS 5.1.2
IF YOU PLAN TO ROOT, TURN OFF WIFI NOW!
ROOT GUIDE: Follow this guide to use Kingroot and the root tools to set up your tablet.
At this time, Kingroot can only root OS 5.1.2 (February 2016) and below.
You can downgrade OS 5.1.2.1 (March 2016) to 5.1.2 and root, as explained in Root Guide, but this is an exception!
In general, never downgrade in order to use Kingroot. It's the fastest way to a brick!
You may be able to safely downgrade a higher OS to OS 4.5.3, root, and then upgrade in TWRP per @bibikalka's root Tut. Before trying this on an OS later than 5.1.2.1, make sure the tutorial says it's safe.
DOWNLOAD THE TOOLS FROM AFH ➔ . FireHD_TOOLS v 1.2
Update as of 5/11/16
➔ If you got the tools before the update, just replace the jobs folder in FIREHD_TOOLS with the one in attached "jobs_v1.x.zip"
Change Log
5/11/2016 - v1.2: Updated sideload.bat. (Missed the Find/Findstr fixes.)
5/10/2016 - v1.1: Fixed "No such file or directory" and "Permission denied" errors for users with *nix Find command installed
.
Nice Work!
@DoLooper - Magnum Opus, no less !
Why version 0.1 ??? The first release - solid 1.0 !!!
Updated. See OP.
Guys, I could use some feedback. Tools are getting downloaded a lot. Anybody using them? Are they helpful? Problems? Wishes? Anything? Thanks!
.
Updated again <sigh>. Sideload tool didn't get updated in v1.1. Apologies to those who downloaded the jobs zip.
DoLooper said:
Updated. See OP.
Guys, I could use some feedback. Tools are getting downloaded a lot. Anybody using them? Are they helpful? Problems? Wishes? Anything? Thanks!
.
Click to expand...
Click to collapse
Thanks DoLooper.
I tried these tools on my Fire HD 7 running 4.5.5.1 rooted with KingRoot.
I was able to use the script to successfully switch from KingRoot to SuperSU as well as to install Nova Launcher.
However, I had issues with the script elsewhere.
The play store seemed to install okay and it let me put in my google account info. After that, things went down hill. I was able to open the Play Store app without it crashing, but I just kept getting the "Error retrieving information from server. [RH-01]" message . I tried numerous things to correct this, but nothing seemed to work. In the end, I downgraded to 4.5.5, wiped data, cache and dalvik, and then flashed gapps via TWRP. This worked out, so all is good now.
I also had trouble with blocking the default launcher. Nova seemed to install okay, but the default launcher still worked and was a constant nag with each press of the home button. I fixed this by freezing the default launcher via Titanium Backup.
I don't know if these issues are particular to 4.5.5.1, or if I'm just unlucky. Regardless, I still appreciate your effort for putting this together. :good:
I'm currently trying to get wallpapers and widgets to work on the Nova launcher with no success. I tried the fixes intended for earlier Kindle models and (not surprisingly), they didn't work. Specifically, I tried Stunt's Wallpaper Fix and Kindlefree from the app store.
Any ideas where I should look for guidance on making Wallpapers and Widgets work?
Thanks again!
notorious.dds said:
Thanks DoLooper.
I tried these tools on my Fire HD 7 running 4.5.5.1 rooted with KingRoot.
I was able to use the script to successfully switch from KingRoot to SuperSU as well as to install Nova Launcher.
However, I had issues with the script elsewhere.
The play store seemed to install okay and it let me put in my google account info. After that, things went down hill. I was able to open the Play Store app without it crashing, but I just kept getting the "Error retrieving information from server. [RH-01]" message . I tried numerous things to correct this, but nothing seemed to work. In the end, I downgraded to 4.5.5, wiped data, cache and dalvik, and then flashed gapps via TWRP. This worked out, so all is good now.
I also had trouble with blocking the default launcher. Nova seemed to install okay, but the default launcher still worked and was a constant nag with each press of the home button. I fixed this by freezing the default launcher via Titanium Backup.
I don't know if these issues are particular to 4.5.5.1, or if I'm just unlucky. Regardless, I still appreciate your effort for putting this together. :good:
I'm currently trying to get wallpapers and widgets to work on the Nova launcher with no success. I tried the fixes intended for earlier Kindle models and (not surprisingly), they didn't work. Specifically, I tried Stunt's Wallpaper Fix and Kindlefree from the app store.
Any ideas where I should look for guidance on making Wallpapers and Widgets work?
Click to expand...
Click to collapse
Thanks for feedback. Tools apparently need work for OS 4.5.5.1. I tested pretty well on 4.5.3 and 4.5.5, but not 4.5.5.1. There may be some peculiarity there.
- The play store error has been reported on some 2015 Fires (using a different tool, but same method to install). It's unclear why it happens on some devices and not others, and they haven't found a fix, but it may be an OS 4 issue on the Fire HDs. I'll look into it.
- Nova & stock launchers: The block on stock launcher didn't work because it isn't implemented for OS 4. As mentioned at top of OP, only OTA block is available for OS 4. I'll need to add it in an update. Hadn't thought about need for it when using the Nova tool.
Would you please look in /system/priv-app folder and see if com.teslacoil.launcher.apk is at the bottom of directory? If so, are perms set to rw- r-- r--? Let me know and we'll proceed from there to get you widgets. Thanks.
DoLooper said:
Thanks for feedback. Tools apparently need work for OS 4.5.5.1. I tested pretty well on 4.5.3 and 4.5.5, but not 4.5.5.1. There may be some peculiarity there.
- The play store error has been reported on some 2015 Fires (using a different tool, but same method to install). It's unclear why it happens on some devices and not others, and they haven't found a fix, but it may be an OS 4 issue on the Fire HDs. I'll look into it.
- Nova & stock launchers: The block on stock launcher didn't work because it isn't implemented for OS 4. As mentioned at top of OP, only OTA block is available for OS 4. I'll need to add it in an update. Hadn't thought about need for it when using the Nova tool.
Would you please look in /system/priv-app folder and see if com.teslacoil.launcher.apk is at the bottom of directory? If so, are perms set to rw- r-- r--? Let me know and we'll proceed from there to get you widgets. Thanks.
Click to expand...
Click to collapse
Thanks for the help!
I found the com.teslacoilsw.launcher-1.apk file, but it's in my /data/app folder... and it is chmod'ed to 644.
Also, I did successfully install the AppWidgetPicker.apk and LiveWallpapersPicker.apk files to /system/app using the "kindlefree" app, but I think that about all the app did. These files are also chmod'ed to 644.
notorious.dds said:
Thanks for the help!
I found the com.teslacoilsw.launcher-1.apk file, but it's in my /data/app folder... and it is chmod'ed to 644.
Also, I did successfully install the AppWidgetPicker.apk and LiveWallpapersPicker.apk files to /system/app using the "kindlefree" app, but I think that about all the app did. These files are also chmod'ed to 644.
Click to expand...
Click to collapse
I've been using OS 5 for too long! Forgot you can't get wallpaper on OS 4 without fussing. It's unclear from your post: Did the pickers get wallpaper to work? This is the way we did it back when we always booted twrp and installed xposed: http://forum.xda-developers.com/fire-hd/general/how-to-wallpaper-custom-launcher-t3123009
As to widgets: What I meant is, you should have /system/priv-app/com.teslacoil.launcher_4.2.2.apk. Do you? I just retested this on 4.5.3. Nova (com.teslacoil.launcher_4.2.2.apk) got copied there and chmod'ed to 644 as it should and widgets are working fine.
No wallpaper is a bad problem, though, and no tool can fix it--unless that LiveWallpapersPicker DID work. Let me know. And let me know about /system/priv-app/com.teslacoil.launcher_4.2.2.apk.
BTW, how come you want to stay on OS 4?
DoLooper said:
I've been using OS 5 for too long! Forgot you can't get wallpaper on OS 4 without fussing. It's unclear from your post: Did the pickers get wallpaper to work?
Click to expand...
Click to collapse
Nope.
DoLooper said:
This is the way we did it back when we always booted twrp and installed xposed: http://forum.xda-developers.com/fire-hd/general/how-to-wallpaper-custom-launcher-t3123009
Click to expand...
Click to collapse
I think I tried that to no avail, but I can't remember exactly which module I used.
DoLooper said:
As to widgets: What I meant is, you should have /system/priv-app/com.teslacoil.launcher_4.2.2.apk. Do you? I just retested this on 4.5.3. Nova (com.teslacoil.launcher_4.2.2.apk) got copied there and chmod'ed to 644 as it should and widgets are working fine.
Click to expand...
Click to collapse
I think I ended up installing Nova via the app store so that's why it wasn't on the system partition. However, my widgets seemed to work when I checked again. I have no idea why they wouldn't work when I first tried them. I did end up creating two simple scripts via the "Scripter" app that would enable and disable the stock launcher. I put them as widgets on the nova desktop allowing for single click toggling of the stock launcher.
DoLooper said:
No wallpaper is a bad problem, though, and no tool can fix it--unless that LiveWallpapersPicker DID work. Let me know. And let me know about /system/priv-app/com.teslacoil.launcher_4.2.2.apk.
Click to expand...
Click to collapse
No, nothing seemed to fix the wallpaper... always black. Am understanding this correctly that the wallpaper works on this thing if I load Lollipop?
DoLooper said:
BTW, how come you want to stay on OS 4?
Click to expand...
Click to collapse
I didn't want to fiddle around with change the bootloaders every time I wanted into TWRP. At this point, it doesn't matter anyway... I hard bricked the device by flashing the 5.2.0 stock recovery last night
The post about using this to revert to stock should be edited or removed. It's bad.
The only reason I was trying to revert to stock was that I ended up getting into a situation where the stock launcher would continue looping back to the Welcome/select language screen. I wiped cache, data, and dalvik and reflashed the 4.5.5 rom which didn't fix it. I even tried that same approach including a wipe of system... same result. I was quite surprised to see the problem continue even after wiping everything. At that point I figured I go back to full stock and start over... BAD IDEA.
Anyway, I ordered a new one and it should be here tomorrow. I'm now curious if it's possible to recover the bricked device via the UART port on the motherboard. We'll see.:fingers-crossed::fingers-crossed:
notorious.dds said:
. . .
I think I ended up installing Nova via the app store so that's why it wasn't on the system partition. However, my widgets seemed to work when I checked again. I have no idea why they wouldn't work when I first tried them. I did end up creating two simple scripts via the "Scripter" app that would enable and disable the stock launcher. I put them as widgets on the nova desktop allowing for single click toggling of the stock launcher.
No, nothing seemed to fix the wallpaper... always black. Am understanding this correctly that the wallpaper works on this thing if I load Lollipop?
I didn't want to fiddle around with change the bootloaders every time I wanted into TWRP. At this point, it doesn't matter anyway... I hard bricked the device by flashing the 5.2.0 stock recovery last night
The post about using this to revert to stock should be edited or removed. It's bad.
The only reason I was trying to revert to stock was that I ended up getting into a situation where the stock launcher would continue looping back to the Welcome/select language screen. I wiped cache, data, and dalvik and reflashed the 4.5.5 rom which didn't fix it. I even tried that same approach including a wipe of system... same result. I was quite surprised to see the problem continue even after wiping everything. At that point I figured I go back to full stock and start over... BAD IDEA.
Anyway, I ordered a new one and it should be here tomorrow. I'm now curious if it's possible to recover the bricked device via the UART port on the motherboard. We'll see.:fingers-crossed::fingers-crossed:
Click to expand...
Click to collapse
Sorry to hear about the brick. Good thing Amazon is patient with us.
Yes, wallpaper works fine on OS 5. [For others who read this, on OS 4 the only way to get wallpaper is with Xposed (installed in TWRP) and the kindleBG module in the link I posted above. And BTW, although the tools don't block OS 4 Amazon launcher ATM, it can be done manually. Commands are here.]
Thanks for your input. Play store didn't work for me either this time, despite earlier success. Everything else except the launcher block (and other non-OTA blocks) does work, so for now I'm just going to edit post and see if there's any other interest in play store on OS 4. (I trust you'll get OS 5 on replacement or will want to update to it.)
As to TWRP: Once tablet is set up, booting TWRP isn't needed much except for upgrading. and bibikalka gives us lots of options for doing it.
Let us know if anything comes of UART port tests. You'd be the hero of the community!
Workaround for Windows username with spaces
The Install Other Launcher and Install Kingroot jobs may not complete if your Windows username has spaces in it. I'll fix this in next update. Meanwhile here's the workaround:
1. Right-click RUNME.bat and choose Edit. [file opens in Notepad]
2. Add a blank line under :: Set paths and run menu.
3. Type: SET "username=abc"
4. Make sure this section of RUNME looks like below and then save and close Notepad
Code:
:: Set paths and run menu.
SET "username=abc"
SET "main=%CD%\"
SET "jobsdir=%main%jobs\"
[remaining code]
This changes the username only for the tools. The rest of Windows continues to use the real username.
I'm getting ready to update. Please let me know if you found any problems.
Used the tool on my Fire HD 6 (4th Gen) running a Rooted OS 5.1.2.1 to install a new launcher and block OTA's, ads, fire launcher, appstore, and Amazon search. Everything worked without issue! Thanks for the awesome and simple to use tool! Tablet is now almost pure Android. Great work!!!
Sidenote: Used bibikalka's TUT (http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-lollipop-root-gapps-t3163950) on my Fire HD 6 that was currently running Fire OS 4.5.3 with TWRP Recovery to obtain a Rooted Fire OS 5.1.2.1..
I adb'd the 5.1.2 upgrade to my slab this way.
$ adb push update-kindle-20.5.4.2_user_542168620.bin /sdcard/
3047 KB/s (663908627 bytes in 212.722s)
My OS is FIRE OS 5.1.2 Build Date March 31, 2016 1:37 AM.
I tried and got an error to the effect, "cannot upgrade because the upgrade you are trying is older than the one you have".
So I'm probably running an even later version of 5.1.2 where they blocked that loophole.
I'm just going to by a cheap Chinese slab and root that.
wallywallywally said:
I adb'd the 5.1.2 upgrade to my slab this way.
$ adb push update-kindle-20.5.4.2_user_542168620.bin /sdcard/
3047 KB/s (663908627 bytes in 212.722s)
My OS is FIRE OS 5.1.2 Build Date March 31, 2016 1:37 AM.
I tried and got an error to the effect, "cannot upgrade because the upgrade you are trying is older than the one you have".
So I'm probably running an even later version of 5.1.2 where they blocked that loophole.
I'm just going to by a cheap Chinese slab and root that.
Click to expand...
Click to collapse
use adb sideload in Stock recovery
Sent from my KFFOWI using XDA Labs
sd_shadow said:
use adb sideload in Stock recovery
Sent from my KFFOWI using XDA Labs
Click to expand...
Click to collapse
Yuh, I used sideload AND IT WORKED!!
I also have a fire 5th generation. Does the same procedure work for that, assuming I use the proper 5.1.2 for that device: https://kindle-fire-updates.s3.amaz...ate-kindle-global-37.5.4.2_user_542168620.bin
wallywallywally said:
Yuh, I used sideload AND IT WORKED!!
I also have a fire 5th generation. Does the same procedure work for that, assuming I use the proper 5.1.2 for that device: https://kindle-fire-updates.s3.amaz...ate-kindle-global-37.5.4.2_user_542168620.bin
Click to expand...
Click to collapse
yes
Sent from my KFFOWI using XDA Labs
Confirmed, this procedure worked for Fire (5th generation), however the amazon update file is different (see a few posts back)
I just got a fire HD 6 (4th Gen) with the 4.5.2 OS.
Everything I see talks about 4.5.3 and later. I have not turned on wifi, so basically in a holding pattern for now. I want to root/twrp and maybe a custom rom.
Can some give me advice on the best path to take? Should I upgrade then root? Or root then upgrade? Any advice is appreciated.

(Guide) De-chinese Stock KIW-AL10 (3GB VERSION) and make it Google friendly

This is a guide to debloat the KIW-AL10 and make stock Chinese usable.
First download Minimal adb and fastboot from here and install it.
Download HISuite and use that to install huawei drivers
Next Make sure developer options by hitting build number 7 times then open developer options and make sure usb debugging is activated in the developer options.
Plug phone into computer and install drivers, any unknown device will be adb so right click and select choose driver from list then select android devices then adb interface, always choose the older driver version for this phone.
One you have that installed you need to unlock your bootloader a great guide is here
Once you have unlocked the bootloader download install twrp using minimal adb and fastboot
First reboot into fastboot..
First check the device is present. using the command :adb devices
then boot into bootloader using the command : adb reboot-bootloader
if that doesn't work turn off device then switching on quickly hold down the volume down button while inserting the cable into the device
The device should then have a white screen with a robot and say unlocked in green writing
find the recovery image you downloaded and if its a different name rename it twrp.img so you know which one it is, files everywhere can get quite messy !
Now right click on the minimal adb link on the desktop and click open file location..
Now put the twrp.img file into the folder with the minimal adb files and close the window.
now flash the recovery using the command: fastboot flash recovery twrp.img
Voila if everything is sucessful your phone now has twrp recovery !
Next use the following command: adb reboot recovery, if that doesnt work force a shutdown by holding the power button then let the phone boot while holding down the volume up button, it should boot into recovery.
Next MAKE A BACKUP THIS IS VERY IMPORTANT AND WHEN ITS DONE COPY IT TO A SAFE DRIVE DO NOT KEEP IT JUST ON YOU SD CARD IN CASE YOUR CARD DIES ! BECAUSE OF THE NATURE OF THIS PHONE AND THE FACT THAT YOU CANT FLASH NON VOLTE ROMS ON THIS PHONE THIS IS YOUR ONLY WAY OF RESTORING THE PHONE SO GUARD IT LIKE YOUR LIFE DEPENDS ON IT !
Now get a cup of coffee and have a break its not good to rush things
Now to root your phone..
Finish your coffee.
Download supersu from here
Put the zip onto your phones sd card and boot into recovery, select install and select the supersu zip and let it install, once done reboot the phone, it may reboot a few times thats normal dont panic, once the phone has finished booting check you have the su app installed, if so now we can do the rest of the stuff.
Next download google play store from here and install it
After opening the play store and signing in you will probably be told to update google services, let it do it then reboot the phone
Next using the play store download root explorer
Next stage is to make the dialer English. and remove yellow pages.
Using root explorer navigate to /cust/alltelecom/cn/prop
hard press on the file local.prop and select open in text editor using the 3 dots on the top right
Look for the following lines of code ro.product.locale.region=CN or similar
Change this to ro.product.locale.region=GB (or whatever your location is such make sure the country code is in CAPS )
Save the file
Now navigate to /system and open build.prop in text editor and change the following lines of code so they end in County matching code not cn
Example
ro.product.locale.region=GB (or whatever your location is such )
ro.product.locale.language=en (or whatever your location is such )
ro.product.locale.region=GB
Go slow there is lots of lines there but you will see them if you take your time
select save and exit from root explorer then reboot.. viola the chinese and yellow pages is gone !
After reboot you may get a baidu warning about location tracking, dont panic we will kill that bugger next !
Next install system app safe remover from the play store https://play.google.com/store/apps/details?id=com.jumobile.manager.systemapp&hl=en_GB I always use this as its simple and keeps a backup of the removed app (just in case of problems)
Use that to remove all the chinse apps from the system including hivoice or it will interfere with google assistant, they are self explanatory
as they are all in chinese !
Next remove hi app
hi care
huawei id
network location (this is the one causing the nag screen dont worry work it will still work.
then reboot phone, there should be no more warnings about baidu location.
Now to get services google working.
You my have notice that despite installing a google account you contacts havent synced. we will fix that now..
To get google contacts to sync you need to install google contacts sync adaptor 6.0.1 from here
After you have installed it open up system apps and check it permision contacts is allowed, also open the battery setting and check it runs at boot and while screen is off, if there are no options for that ignore that bit and exit.
while you are there check google play services permission are all on especially contacts then reboot
Now install the google app from the app store
next install google assistant from the play store
now install google photos from the play store
Next install google chrome from play store
next install google calendar from the play store
next install google plus from the play store
next install google maps from the play store
next install youtube from the play store
Next install gboard from the play store
Then when all is done reboot the phone
After reboot check all the permissions of the apps and make sure all the google apps run at boot and keep running after screen off or they wont sync etc then reboot again.
Change horrible huawei keyboard to gboard in language settings
Open the google app and setup google and check your contacts have synced. set up the rest of your settings
Get a decent launcher as the huawei one sucks I use nova launcher prime its worth every penny but the free one is still good
Open settings app and click advanced, here you can change default launcher and select default app setting then select assistance and voice input, selectassist app as google select use text from screen and select use screenshot
I think that pretty much it, the rest you should be able to do yourself, have fun and good luck, any questions just ask.
I wrote this guide as there is very little info on the AL10,
Happy modding !
Very useful
Very useful post, my first venture into phone modding, enabled me to use my KIW-AL10 with Google functionality and to avoid the worst excesses of the stock Chinese software. Thanks!
Ed_shred said:
Very useful post, my first venture into phone modding, enabled me to use my KIW-AL10 with Google functionality and to avoid the worst excesses of the stock Chinese software. Thanks!
Click to expand...
Click to collapse
Thanks for the thanks ! glad it was of use to you, I wrote another guide which enables volte to be removed and put lineage os on instead which you may find useful, its a fairly lengthy process but foolproof and doesn't brick the phone which was my main concern as there is nowhere to download the stock roms for these 3gb variants, cheers
swukjay said:
Thanks for the thanks ! glad it was of use to you, I wrote another guide which enables volte to be removed and put lineage os on instead which you may find useful, its a fairly lengthy process but foolproof and doesn't brick the phone which was my main concern as there is nowhere to download the stock roms for these 3gb variants, cheers
Click to expand...
Click to collapse
So, the phone worked ok for a month, but then started restarting itself all the time. I deleted loads of apps, but it didn't solve the problem. Now, I decided to try to solve the problem by installing a custom ROM, so first step was to wipe the phone with TWRP. After wiping, I no longer had root access, and now installing SuperSU doesn't work, I can install the .zip through TWRP recovery, but I still don't have root access afterwards, according to Root Checker. Any ideas? Thanks!
Ed_shred said:
So, the phone worked ok for a month, but then started restarting itself all the time. I deleted loads of apps, but it didn't solve the problem. Now, I decided to try to solve the problem by installing a custom ROM, so first step was to wipe the phone with TWRP. After wiping, I no longer had root access, and now installing SuperSU doesn't work, I can install the .zip through TWRP recovery, but I still don't have root access afterwards, according to Root Checker. Any ideas? Thanks!
Click to expand...
Click to collapse
Repeated the process, ticked a few boxes in SuperSU, seems to be solved for now, thanks...
swukjay said:
Thanks for the thanks ! glad it was of use to you, I wrote another guide which enables volte to be removed and put lineage os on instead which you may find useful, its a fairly lengthy process but foolproof and doesn't brick the phone which was my main concern as there is nowhere to download the stock roms for these 3gb variants, cheers
Click to expand...
Click to collapse
OK, so I have tried quite a few times to install Lineage OS 14.1 and Viper, with both they get stuck in a bootloop. Trying to install Lineage with this guide https://wiki.lineageos.org/devices/kiwi/install, the 'format data' stage is not successful. I get a message saying ' E:Unable to wipe '/data' - unknown file system 'auto Unable to format to remove encryption '.
I'm not totally committed to a custom ROM, but I'd like this phone to work. Any ideas, either how to troubleshoot the ROM flashing issue, or to get the phone stable with the stock de-Chinesed stock ROM? Thanks!

FLOSSbOxIN - A Customized Stock ROM

FLOSSbOxIN - Since 2016, I am a non-foogle person, nor do I have shucksfook, or anything of those stuffs. I was on Telegram and used to run the flossboxin channel, but left the application due to too much of spam and useless stuffs, and moreover, privacy issues tbvh. Now my XMPP channel is named FLOSSbOxIN too. I recently lost my M30, however, I have been for quiet sometime trying to get this M30 debloated to a level where knox also does not trip, nor where one will have to face the unnecessary Samsung bloatware and annoying analytics. Finally, I have made it to that level, after several permutation combinations.
Code:
[B]FLOSSbOxIN M305F Debloated FOSS/FLOSS Stock ROM[/B]
Released: [B]20200925[/B]
Patch Level: September 01, 2020
Build Date: [B]20200926[/B]
Base Version: Android 10
Build #: QP1A.190711.020.M305FDDS6CTI1
Kernel: [I]4.4.177-19407255[/I]
UI Core: [U]One UI 2.0[/U]
Links:
M30 Database -- AFH
DM-Verity -- AFH
FLOSSbOxIN - ROM -- Cloud - Direct Link
Odin V3.14.4 -- AFH
TWRP 3.4.0-0 -- AFH
Magisk Canary -- AFH
Installation Guide (Only For Bootloader UL On Q/10)
Download ROM from the links given.
Boot to recovery (stock/TWRP) (Guide Link)
Code:
adb reboot download
You will have to format data, as the ROM is decrypted, and coming from an encrypted ROM will give issues. For decrypting, do a "format data" in TWRP Recovery and then reboot to recovery and Wipe Dalvik/ART, Cache, System, Data, Hidden, Internal
Copy over ROM OS & DM-Verity file (do not rename DM-Verity file, keep as is)
Flash ROM - Would take around 10 minutes time for it to flash
Go to wipe, and wipe /hidden
Flash DM-Verity file
Reboot - should take around 5-6 minutes
Notes:
I have removed the setup wizard altogether
Post system starts, wait 5-10 minutes, as system tries to integrate system apps, which are newly introduced
Only necessary foogle stuff is kept, including Maps+Location, GSF & Play Services and all other foogle stuffs is removed
Somehow, even after removing the notorious HIYA (so called caller id and spam protection service), it somehow comes back with a valid internet/mobile data connection. If you wish to remove it again, boot to TWRP, mount /system and then delete the hiya service folder and clear dalvik/cache, and reboot
If any app has permission issue, then reinstall as "user" app (install again manually), and reboot sysui. Should work post that, as sometime, few apps are by default not allowed system changes by Samsung framework, and to add each app to framework is a bigggg task, and very irritating too
Still if any app (e.g., AnysoftKeyboard (see git issue), then uninstall as system, and reinstall as user
Ensure minimal apps are made /system, as they can be harmful
Features:
Fully debloated
Fully stock
Smoother, faster and has long battery run
Foogle & Samsung stupidity free
FLOSS apps included:
Aurora Droid, Aurora Store
F-Droid Classic - Classic variant by bubu
F-Droid Privilege (if you ever install F-Droid main app)
Bromite Webview is default
UngoogledChromium is the default browser
FreeOTP+ is your FLOSS 2FA companion
K9 Mail is the default FOSS email
KeePassDX for auto-login and enhanced privacy
Notification Log allows you to view several logs, once usage access is granted, and is fully FLOSS
QKSMS replaces Samsung Messaging app
Power App allows you to reboot to various modes - sysui, recovery, bootloader....
Vinyl is your music buddy
Dual-Mod for audio included
Screen capture (image & video) feature added
Data transmit (Up/Down) in status bar added (thanks Akhil)
Various camera tweaks (FOSS - OpenCamera is not included)
My hosts file is included, which enhances privacy by blocking various trackers and ads - URL
Hosts editor also included
GPS fast locking in closed areas - debug included for it
USB debug revoke option added to Dev mode
initd support added
Shutdown thread log enabled
BUGS
FLOSSbOxIN - You tell me..
Contributors/Credits:
Samsung for the superb bloat filled operating system, which is like a bliss in the irritation module
topjohnwu for Magisk
Akhil99 for TWRP
vdbhb59 for actually spending hours on getting this sorted, and when I do not even have the phone anymore (lol)...
XDA:DevDB Information
FLOSSbOxIN, ROM for the Samsung Galaxy M30
Contributors
vdbhb59, vdbhb59
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
ROM Firmware Required: M305FDDS6CTI1, M305FDDUS6CT13
Based On: Stock
Version Information
Status: Stable
Current Stable Version: 2.0
Stable Release Date: 2020-09-25
Created 2020-09-25
Last Updated 2020-10-17
Snapshots
Snapshots
Reserved 2
Cool FLOSS Rom sar!
Thank you sir. Working on getting a Foogle Based FOSS ROM, so that few stupid apps which are GSF dependent can work out of box.
Google version added, and OFFICIAL tag added..
vdbhb59 said:
DM-Verity -- https://www.androidfilehost.com/?fid=8889791610682882483
Click to expand...
Click to collapse
@faiz5200 here is the link..
Ajayagrawal said:
Hello
Click to expand...
Click to collapse
Okay mate.
Few ways to do it.
1. By installing rooted AP with TWRP already included:->
Install September stock Firmware from my post here: https://forum.xda-developers.com/galaxy-m30/development/rom-t4167497
Use that to flash the September FW. Use ODIN via windows, and use the file: AP ROOTED WITH TWRP RECOVERY. Flash only AP. CP is optional. Follow the steps there. Ensure to flash DMVERITY.
This is one way...
Another way:
2. Flash stock ROM. Connect to wifi/mobile data and setup. Change the time to say 7 days prior to today. Wait 30 minutes and boot to download mode via the following method:: switch off. Press Vol+/- together and connect to laptop/pc via usb. Ensure usb debugging is ON and then perform. Now you are in download mode. Flash TWRP.tar file from AP. All checkboxes should be unticked. Once flashed successfully, press vol- and power button for 7-8 seconds and let go off vol- upon haptic feedback and press vol+ to enter to twrp recovery. You can let go of the buttons once twrp shows up.
Now format data and reboot to twrp again. Mount data and /system and if OS is installed boot to system, else flash a ROM of your choice.
3rd way:
3. Download FLOSSbOxIN (FLOSS/Google variant available). Extract to any desktop folder. Now open 7Zip and make a zip file with all the .img files. Choose .tar (available from 7Zip dropdown as well) and rename the tar file to say rom.tar.
Once done flash this one via AP. Ensure all checkboxes are unchecked. Reboot to TWRP following the steps in method 2 above. Format data, boot to twrp, flash dm-verity and boot to system. You can wipe cache/dalvik and /hidden if you want. Will take around 10 minutes to boot. Dont forget to boot to twrp first and flash dmverity, else you will end in bootloop.
Note: With Samsung, in case you forget to flash DMVerity, and by mistake clicked boot to system, do not worry. Switch off, or reboot to twrp and mount /system and flash. Wipe dalvik and cache, reboot. Done.
vdbhb59 said:
Okay mate.
Few ways to do it.
1. By installing rooted AP with TWRP already included:->
Install September stock Firmware from my post here: https://forum.xda-developers.com/galaxy-m30/development/rom-t4167497
Use that to flash the September FW. Use ODIN via windows, and use the file: AP ROOTED WITH TWRP RECOVERY. Flash only AP. CP is optional. Follow the steps there. Ensure to flash DMVERITY.
This is one way...
Another way:
2. Flash stock ROM. Connect to wifi/mobile data and setup. Change the time to say 7 days prior to today. Wait 30 minutes and boot to download mode via the following method:: switch off. Press Vol+/- together and connect to laptop/pc via usb. Ensure usb debugging is ON and then perform. Now you are in download mode. Flash TWRP.tar file from AP. All checkboxes should be unticked. Once flashed successfully, press vol- and power button for 7-8 seconds and let go off vol- upon haptic feedback and press vol+ to enter to twrp recovery. You can let go of the buttons once twrp shows up.
Now format data and reboot to twrp again. Mount data and /system and if OS is installed boot to system, else flash a ROM of your choice.
3rd way:
3. Download FLOSSbOxIN (FLOSS/Google variant available). Extract to any desktop folder. Now open 7Zip and make a zip file with all the .img files. Choose .tar (available from 7Zip dropdown as well) and rename the tar file to say rom.tar.
Once done flash this one via AP. Ensure all checkboxes are unchecked. Reboot to TWRP following the steps in method 2 above. Format data, boot to twrp, flash dm-verity and boot to system. You can wipe cache/dalvik and /hidden if you want. Will take around 10 minutes to boot. Dont forget to boot to twrp first and flash dmverity, else you will end in bootloop.
Note: With Samsung, in case you forget to flash DMVerity, and by mistake clicked boot to system, do not worry. Switch off, or reboot to twrp and mount /system and flash. Wipe dalvik and cache, reboot. Done.
Click to expand...
Click to collapse
@vdbhb59 THANK YOU SO MUCH ,SIR.I was about to sell the phone coz TWRP could not be booted.
Finally,TWRP is booted huge thanks to you.Procedure 2 did not work(bootloop) and Procedure 3 gave me .binary error in odin(maybe i messed up in some steps).But Procedure 1 was easiest and foolproof & it booted TWRP in first try without any bootloops.
Now coming to Floss ROM(Vanilla).It was simple,clean and elegant and performance is good as well.I have not checked the battery life with this ROM but i hope it gives me more than standard battery life.Will be checking other ROMS as well-Lineage,Bliss,Turbo etc. and will be settling once i find ROM suitable for me.
Again thank you DEV for guiding me,giving me your time and most importantly contributing to this community !!
Ajayagrawal said:
@vdbhb59THANK YOU SO MUCH ,SIR.I was about to sell the phone coz TWRP could not be booted.
Finally,TWRP is booted huge thanks to you.Procedure 2 did not work(bootloop) and Procedure 3 gave me .binary error in odin(maybe i messed up in some steps).But Procedure 1 was easiest and foolproof & it booted TWRP in first try without any bootloops.
Now coming to Floss ROM(Vanilla).It was simple,clean and elegant and performance is good as well.I have not checked the battery life with this ROM but i hope it gives me more than standard battery life.Will be checking other ROMS as well-Lineage,Bliss,Turbo etc. and will be settling once i find ROM suitable for me.
Again thank you DEV for guiding me,giving me your time and most importantly contributing to this community !!
Click to expand...
Click to collapse
Anytime mate. Actually all the 3 ways I mentioned, do work. Probably, some trouble while flashing. However, no worries, I am glad you were able to boot to TWRP and flash a bloat free OS. Enjoy mate, and happy riding.
Battery life is around 1.5-2 days basis your usage. At times more, touching 3.5 days too. Again, the logic basis is always usage and background stuff.
Bliss does not boot for all, LOS does though.
BTW, which FLOSSbOxIN variant did you try? Google one will eat more battery obviously, against FLOSS one.
FLOSS(Vanilla)-[without google] review
Everything is good with the ROM but some problems i faced could be solved by following procedures:
1.If some apps does not work/launch as expected then "UNINSTALL AS SYSTEM" then REINSTALL it or INSTALL APP OF YOUR CHOICE.For eg:Vinyl player.
2.If AURORA STORE does not download apps then first give permission to Aurora Services and then rerun Store.Otherwise install GooglePlayStore manually once, update GMS and it will work.PS:You can delete PlayStore or disable if you want to.
Other than these everything is FINE.Would certainly recommend to try this ROM ?
Ajayagrawal said:
Everything is good with the ROM but some problems i faced could be solved by following procedures:
1.If some apps does not work/launch as expected then "UNINSTALL AS SYSTEM" then REINSTALL it or INSTALL APP OF YOUR CHOICE.For eg:Vinyl player.
2.If AURORA STORE does not download apps then first give permission to Aurora Services and then rerun Store.Otherwise install GooglePlayStore manually once, update GMS and it will work.PS:You one delete PlayStore or disable if wants to.
Other than these everything is FINE.Would certainly recommend to try this ROM ?
Click to expand...
Click to collapse
Thanks for this mate. Though not bugs, but the app behaviour itself. The ROM itself does not have any bugs.
October release coming soon.
Dear Dev,
Thanks for the rom.
My 3 queries
1. Getting access denied on some files like magisk, odin, and m30 database.
2. Is there any aggresive battery saver or something alike in rom which switches off all functions except calling?
3. The download link to download google version is very slow and is showing close to 17 hours to download on 150 MBps connection.
Thanks and Regards
Ashish
ashish128 said:
Dear Dev,
Thanks for the rom.
My 3 queries
1. Getting access denied on some files like magisk, odin, and m30 database. Also, you will only need the ROM, DMV erity & Magisk files anyways.
2. Is there any aggresive battery saver or something alike in rom which switches off all functions except calling?
3. The download link to download google version is very slow and is showing close to 17 hours to download on 150 MBps connection.
Thanks and Regards
Ashish
Click to expand...
Click to collapse
Hi Ashish,
Actually, AFH is having some issues. I too am unable to view files at times. Magisk and ODIN are Public files anyways. You can navigate with androidfilehost then my user, which is vdbhb59.
Battery saver is there, Ultradata by Samsung itself. You can use any 3rd party app too.
Google version link is quick here. Showing 25 minutes at 80Mbps.
Update - 20201017
Hi All,
Update released for the new version.
N.B., the update by Samsung never was for October 2020 patches, and was only a con, as they moved the apps & priv-app between the 2 folders, and added a very big BUG along with several privacy issues.
When I reached out to them with the details, I was blocked, and my account was suspended.
I have stripped away every bit and piece of bloat and BUGS (afaic). Security patch is still September.
Also, the stock camera is now replaced with 2 open variants, and much better ones. With the latest update, while trying to remove Knox, and some resources, the stock Camera breaks up fully, and the hidl does not link, rendering the app useless.
Magisk Canary 20201017
20201017 - FLOSSbOxIN_Foogle_V2_20201017
20201017 - FLOSSbOxIN_V2.2_20201017
Difference between the 2 versions
Difference between the 2 versions -->
FLOSSbOxIN_Foogle_V2_20201017 - this version is a bit smaller compared to the version 2.2 below. Version 2.2 contains a few more privacy oriented apps, and XDA app as well inbuilt, along with OSMAnd+ and UNLP. I have retained GMS Core and Maps as OSMAnd does not cover many parts of Asia and Russia.
FLOSSbOxIN_V2.2_20201017 - this version contains the following:
SMS - QKSMS
Mail - K9 & pEp - both open source. Both more reliable then stock.
Clipboard - Added function for clipboard. Probably, some apps may not work with it. Ideally, it will come as an option with pop-ups.
Maps - GMaps, OSMAnd+, UNLP
Music - Odyssey & Vinyl
Video - MPV is a great tool. VLC somehow does not integrate with Samsung while building, so have not added it yet.
SimpleTools - Gallery & Calendar alongside stock ones. Do use the open source ones, as they are fully privacy oriented. Some folks like Samsung one, but it is filth filled, and I have taken huge time out to prepare these stuffs, so do try.
Camera - OpenCamera & FreeDCam have been added. I have been using these 2 since a long time, so, do use them too.
Browser - 2 variants of Ungoogled Chromium, Bromite Webview alongside Android Webview.
Terminal - Termus. Do install the relevant addons from F-Droid/AuroraDroid and enjoy.
Downloader - Download Navi is prebuilt.
Launcher - OpenLauncher is added too, which is a better option compared to Samsung one. Use the one you prefer.
Stores - As usual F-Droid (2 variants), Aurora Store and Aurora Droid.
The ROM has been tested completely, in terms of retaining of Samsung features, and additional stuffs that I could integrate. I hope on getting Stock custom ROM soon, if the framework parts pans out, and may have inbuilt power menu options, more QS stuffs and theming, all again depending on time I can spare and framework nuisance.
It would be great if Theme option is added
vdbhb59 said:
Hi All,
Update released for the new version.
N.B., the update by Samsung never was for October 2020 patches, and was only a con, as they moved the apps & priv-app between the 2 folders, and added a very big BUG along with several privacy issues.
When I reached out to them with the details, I was blocked, and my account was suspended.
I have stripped away every bit and piece of bloat and BUGS (afaic). Security patch is still September.
Also, the stock camera is now replaced with 2 open variants, and much better ones. With the latest update, while trying to remove Knox, and some resources, the stock Camera breaks up fully, and the hidl does not link, rendering the app useless.
Magisk Canary 20201017
20201017 - FLOSSbOxIN_Foogle_V2_20201017
20201017 - FLOSSbOxIN_V2.2_20201017
Click to expand...
Click to collapse
Did they replaced system.img with super.img ? Samsumg keeps adding their security related sh**t in the name of security patches making difficult for devs to mod their Roms.
akhil093 said:
Did they replaced system.img with super.img ? Samsumg keeps adding their security related sh**t in the name of security patches making difficult for devs to mod their Roms.
Click to expand...
Click to collapse
Nope. They moved few /system/apps to /priv-app and to /vendor and made a lot of framework changes to ensure boot goes for a toss. One of the worst was how system auto cleans at a schedule. Also busybox installation fails due to /system free space being minimal.
Few more things, which I think cannot explain here.

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...

Categories

Resources