hey i want to root my alcatel 4033 because of the 512mb of memory, most of it is used up by preinstalled apps but i dont know what to do after rooting it. Can any one help me? i can help my self when it comes to technology and i can follow instuctions
Hi there, i have the same Phone. Got it rooted with the framaroot app. Then i searched the web for custom roms. First Nothing Then i came a cross this site http://www.442kitkat.info/mp3-0/alcatel-one-touch-pop-c3-5687.html. seems interessting? ! I will try to flash it and See how it works out
---------- Post added at 11:22 AM ---------- Previous post was at 11:20 AM ----------
I got the A version (4033a) i guess. Without dual sim
Bull****. Got to complete a task/buy something. Forget about this link.
Hi, U can remove useless apps using root explorer or root app delete.. Or search for any other custom rom built for ur fone.
Without custom roms, usually this http://forum.xda-developers.com/xposed/framework-xposed-rom-modding-modifying-t1574401 . With the different modules available for everything from ad blocking to theming to customizing the lockscreen, this is about as custom as you can go without a rom.
I have an app
ackeella27 said:
hey i want to root my alcatel 4033 because of the 512mb of memory, most of it is used up by preinstalled apps but i dont know what to do after rooting it. Can any one help me? i can help my self when it comes to technology and i can follow instuctions
Click to expand...
Click to collapse
Hello ackeella27, I have an Alcatel POP C3 4033X and I had the same problem: preinstalled apps and some ram used by these (for example Viber, that sometimes used to crash even if I didn't open it). So i had decided to root my phone and remove these useless (for me) apps by deleting them from the system (they are in a folder called "/custpack/app/" in the case of 4033X but i don't know if it is the same for other model of POP C3).
But I use to reset my phone sometimes (with the decision to not install again too much apps xD ) so made an app, called "App Removal for Alcatel POP C3"
I think if you have 4033X model you can surely use it, if not but you decide even to try please tell me the result so I know that this app is also for another model of POP C3.
You can find the app atached the post; I've put an ads at the bottom because I'm planning to put it on Play Store
In the app, if you haven't already rooted your phone you can click "Get SU" button, and installation of Framaroot will be started: when it finishes open Framaroot and click Boromir. Restart the phone. You can open App Removal, and may modify the code, and then click "execute" button to remove the unnecessary apps.
I posted some sceenshot to show you how is the app
Description of used permissions:
1) SD Card
2) Network State and Internet
3) Superuser
1)To put Framaroot in the SD Card and start the installation process
2)To display Ads
3)To execute the root commands
I hope it works and is usefull
Have a nice day
- dicciassei -
Edit: The app is now obsolete: wait about one week and I will make a topic with the new app (better than this). Bye
dicciassei said:
Hello ackeella27, I have an Alcatel POP C3 4033X and I had the same problem: preinstalled apps and some ram used by these (for example Viber, that sometimes used to crash even if I didn't open it). So i had decided to root my phone and remove these useless (for me) apps by deleting them from the system (they are in a folder called "/custpack/app/" in the case of 4033X but i don't know if it is the same for other model of POP C3).
But I use to reset my phone sometimes (with the decision to not install again too much apps xD ) so made an app, called "App Removal for Alcatel POP C3"
I think if you have 4033X model you can surely use it, if not but you decide even to try please tell me the result so I know that this app is also for another model of POP C3.
You can find the app atached the post; I've put an ads at the bottom because I'm planning to put it on Play Store
In the app, if you haven't already rooted your phone you can click "Get SU" button, and installation of Framaroot will be started: when it finishes open Framaroot and click Boromir. Restart the phone. You can open App Removal, and may modify the code, and then click "execute" button to remove the unnecessary apps.
I posted some sceenshot to show you how is the app
Description of used permissions:
1) SD Card
2) Network State and Internet
3) Superuser
1)To put Framaroot in the SD Card and start the installation process
2)To display Ads
3)To execute the root commands
I hope it works and is usefull
Have a nice day
- dicciassei -
Click to expand...
Click to collapse
Q did u als had this annoying message when u disable viber. Viber has stopped. Keeps popping up
Yes, so I reset my phone and delete it from the system. I think this phone's version of viber is bugged because if I install it from Play Store it function normally. If you would remove it feel free to use my app (it not remove only viber but also other programs, in future I update if with a cecklist of Alcatel system apps you can check to be removed, more comfortable)
Sent from my ONE TOUCH 4033X using XDA Free mobile app
Aight that woud be cool
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!
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
Hello,
I want to debloat my P9 Lite from apps like Youtube etc. I used the approach from a video called "Remove ALL Bloatware from any Android Smartphone without Root" (cannot post link)
Bringing my phone into debug mode and installing adb all went fine. However, when I start Debloater (version 4.0) -- it shows me the correct serial number and battery status, though -- the model gets called "generic_a15" in Debloater. Furthermore, no package is listed when I click "Read Device Packages".
Does somebody know how I can resolve this issue? Thank you very much for your attention!
UndercoverDebloater said:
Hello,
I want to debloat my P9 Lite from apps like Youtube etc. I used the approach from a video called "Remove ALL Bloatware from any Android Smartphone without Root" (cannot post link)
Bringing my phone into debug mode and installing adb all went fine. However, when I start Debloater (version 4.0) -- it shows me the correct serial number and battery status, though -- the model gets called "generic_a15" in Debloater. Furthermore, no package is listed when I click "Read Device Packages".
Does somebody know how I can resolve this issue? Thank you very much for your attention!
Click to expand...
Click to collapse
Hi,
i never used that method, so
just my thought...
Maybe you have to try to reboot your device in fastboot mode,
then try to launch the debloater and see if it shows you packages.
Regards
Downloaded and installed, also not working.
Any other method to remove unwanted apps?
Kennabiz said:
Downloaded and installed, also not working.
Any other method to remove unwanted apps?
Click to expand...
Click to collapse
Installing a custom ROM usually brings a series of benefits including that
of not having bloatweres so it is my main recommendation.
On the other hand, manually, with superuser permissions and a root app manager,
you can uninstall all the applications you want, but you must pay attention to what you touch,
the system could become unstable (google apps). Do some research before venturing.
Making a Nandroid backup before starting is almost mandatory, always recommended.
Good luck
Installing custom roms is nice But simple huawei backup and restore for stuffs is so much easier than some third party app to do.
I would so easy install some of the many custom roms But eui is so easy and works.....
Dadditz please help here
Kennabiz said:
Dadditz please help here
Click to expand...
Click to collapse
Excuse me I probably did not grasp the juice of the speech.
I have already answered for what I know, custom roms or manual uninstallations of what you do not want.
Another way would be to freeze / disable unwanted apps ... the device will be grateful ..
Dear use @ to quote.
Best regards