Related
Quick update: As (I hope) no one is still using OOS9, this method must be considered deprecated.
Hello,
this is how to enable the McLaren fingerprint animation from the Oneplus 6T McLaren edition on normal 6T editions without a PC, root, module, app whatsoever (depends on the method you choose). You can also choose to disable the animation at all. For the McLaren animation OOS 9.0.9 or newer is needed since the animation files are included from this verison on. You just can't enable it through the settings app. If you ask me, the unlocking feels even faster with this animation!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Requirements:
OOS version greater than 9.0.9, OOS 10 does not work (if you want to disable the animation, any version will work)
Either the app below (no root), adb (no root), magisk or another root solution
Method 1: No root, on-device, super-easy
Download this app from Google Play.
Open it and confirm that "System table" is selected.
Scroll down and search for the line "op_custom_unlock_animation_style".
Touch the line and then press on "Edit value".
Enter "3" (no quotes) and confirm.
Enjoy. You can delete the app now if you want.
Can't find the line? Go with this:
Try to change your current fingerprint animation in settings and check the app for the line again (fully close it first). If there, continue above, if not continue below.
Confirm that "System table" is selected.
Tap "Add new setting". There will be 2 prompts.
Replace "NEW_SETTING" with "op_custom_unlock_animation_style" (no quotes) in the first one and confirm.
Replace "SETTING_VALUE" with "3" (no quotes) in the second one.
You should be good to go! If you want you can delete this app now.
Please note:
Some users reported that the setting didn't survive reboots when removing the app. Try for yourself.
I recommend not to mess with other settings if you don't know what you are doing.
Method 2: No root, adb needed
Connect your device and verify your adb connection by using
adb devices
Proceed by entering
adb shell settings put system op_custom_unlock_animation_style 3
All done!
Please note:
If you do not understand what adb is or how to set it up, please use method 1 from above.
Method 3: Root needed, Magisk module
Download the Magisk module .zip from the attachments below.
Install it through Magisk Manager.
Enjoy!
Please note:
There will be no module visible in Magisk Manager, no files modified and no boot scripts. To disable just select a default fingerprint animation through settings and to enable reflash the module. Don't know if TWRP flashing works.
You can alternatively use AnoopKumar's module to enable a full McLaren experience with bootanimation, fingerprint animation, wallpapers etc. Found here. Difference to my module: Enables the animation on every boot so it will overwrite your setting if you choose another animation but don't disable the module.
Method 4: Root needed, terminal solution
Open your terminal app of choice
Switch to root by entering
su
Enable the animation by entering
settings put system op_custom_unlock_animation_style 3
Extra: Disable animation at all
You can use any of the above methods
Just replace the value "3" with a non-existent animation number, for example "4" (if future OOS updates add more animations, you need to use a higher value)
Magisk module also available ("no-fp")
Extra: McLaren color theme
Head over to Settings -> Display -> Theme, and set it to "Dark".
Next, tap on "Accent color" and tap on the custom color icon.
Input the hex code "#E0610E" in there.
That's it.
Additional information:
The setting survives reboots.
You might have to try it several times to make it stick after reboots.
Some users reported that they needed to keep the app installed in order to make it stick after reboots when using method 1.
To disable the changes, just enable one of the default fingerprint animations through the settings app. This works the same way for EVERY method.
Hit thanks!
Your post doesn't view right on the XDA app, here's the actual command for others
Code:
adb shell settings put system "op_custom_unlock_animation_style" "3"
OMG. Thank you!
Lartsch said:
Hello,
this is how you can enable the McLaren fingerprint animation from the Oneplus 6T McLaren edition on normal 6T editions without any mods, modules, apps whatsoever.
OOS 9.0.10 is needed since the animation files are included with this verison (you just can't enable it through settings).
Requirements:
OOS 9.0.10
ADB up and running
Steps:
Connect your device and verify your adb connection by using
adb devices
Proceed by entering
adb shell settings put system "op_custom_unlock_animation_style" "3"
All done!
Additional information:
The setting survives reboots.
To disable it again, just enable one of the default fingerprint animations through normal settings.
Click to expand...
Click to collapse
I'll try this out later when I can get to a PC, but thanks man! It would be awesome if someone could make a Magisk module for this, since I have a feeling the animation is going to be removed from later updates for the normal 6t!
H4X0R46 said:
I'll try this out later when I can get to a PC, but thanks man! It would be awesome if someone could make a Magisk module for this, since I have a feeling the animation is going to be removed from later updates for the normal 6t!
Click to expand...
Click to collapse
If you're already rooted check OP, you can do the same with a terminal emulator and root privilege of course.
Lartsch said:
If you're already rooted check OP, you can do the same with a terminal emulator and root privilege of course.
Click to expand...
Click to collapse
......... I love you.... LOL jokes aside, thanks man! That worked! ???
H4X0R46 said:
......... I love you.... LOL jokes aside, thanks man! That worked!
Click to expand...
Click to collapse
Updated OP once more, now with an even easier method
You're welcome!
yes it works
Thanks Buddy For This really Awesome.
Way 1 Is Super Duper Easy and works like charm
Works on 9.0.9 btw
EDIT: I like 2 better tbh
Can't find that line in the app.
OS 9.0.10
Thank you very much. Method 1 with the app works. It took 10 seconds.
EDIT: I'm on 9.0.10, rooted with Magisk, no TWRP. But as the OP stater, NO ROOT IS NEEDED!
That's amazing. Thank you so much!
In the app I can not find that line?
candleworth7808 said:
Can't find that line in the app.
OS 9.0.10
Click to expand...
Click to collapse
I don't have it either, I am on the TMO variant running international 10. don't know if that makes a difference
Sent from my ONEPLUS A6013 using Tapatalk
Update
I ran the command in terminal then opened the app and the line was there twice, I removed the one I entered and changed the Vale to 3 as per instructions and I'm good to go.
If you can't find that line in the app, you can add it in the app yourself.
Simply tap +Add New Setting
Then type
op_custom_unlock_animation_style
Tap save changes
Then enter the value of 3
Tap save changes.
Then go to settings, security, fingerprints, and see McLaren!
@Lartsch Good one mate, I can confirm this works on Open Beta 1 also. You may update the OP :good:
Sent from my OnePlus6T using XDA Labs
Thank you OP.
I used the first method as i m stock and locked. Super easy.
The line wasn't present so as per suggestion i added it and it works perfectly. In settings it shows cosmos, idk why.
Edit - it didn't survive reboot, had to do it again.
Does adb shell method survive reboot?
Edit 2 - on second try it shows McLaren in settings and also survived reboot. I m glad that it works.
App worked but I had to change from default in normal phone settings before the line showed up in app. Thanks OP.
Everything is working flawless but my alert slider isn't showing the notifications of phone mute or vibrate with icon on the main screen but it's working any fixes please
Just got this device and here are some tweaks for the stock miui 11 rom.
A few little things. Maybe I post more if I find them useful.
Know your hardware (Device Info HW app)
You need to know what specific hardware is in your Redmi Note 8 (camera, fingerprint sensor etc) for some tweaks.
General info
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Camera sensor info
Enable App drawer in Launcher (4.14.1404)
Install quickshortcut maker from the play store. (https://play.google.com/store/apps/details?id=com.sika524.android.quickshortcut)
Start QSM and go down to Systemlauncher > expand it > click on last activity: AllAppsSettingsActivity.
Click Try
Select App drawer!
Lab camera options
Not very useful. Create folder in storage DCIM/Camera called Lab_options_visible
Kill camera app and start it. Now you see more items in camera settings.
Hidden menus in About Phone
In the settings goto About phone > All specs
tap 7 times on Processor > Bug report
tap 5 times on Kernel version > CIT (Phone hardware test)
tap 5 times on Internal Storage > Mobile radio sim 1/2 and Wifi things
Change Font
Goto Settings > Themes > More
Type the word Font in the Search box
In the Results you see Fonts > click More
Download and Apply the font. Reboot needed
Manage your Fonts: Use QuickShortcutMaker > Expand Themes > Click FontsettingsActivity > Try
When not to use Battery saver
In general saving energy when you switch of the screen is a good idea.
Unless you have apps that need to run all the time. Like Navigation apps.
So if you have problems with Navigation/gps apps that behave odd do this:
Long click on the app icon > App info > Battery saving > switch from "Battery saving" to None.
Disable/Uninstall a package
When you have adb access to the Note 8 you can disable packages. Well uninstall.
- adb shell
- pm list packages -s -f -e | sort -> gives you sorted enabled system package names
- pm uninstal --user 0 <packagename>
If you need the package back you can use: adb shell pm install-existing <packagename>
(if you have root better use: pm disable <packagename>, easier to enable again)
List only disabled (system) packages: pm list packages -s -f -d | sort
Battery saving tips
Switch off in Settings > Battery > cog wheel top right > Scenario's > Detect sleep (is high wakelock on android system)
Switch off MIUI optimization in developer settings
Switch off Notifications for Xiaomi Service Framework and Xiaomi Service Framework Keeper
Assisted GPS
Don't know if this makes a big difference but GPS indoors is really fast now.
Use Quickshortcutmaker and search for GPS. In settings you find A-GPS-settings. Click it and click Try.
- Network: All
- SI-mode: MSB
- Server: supl.google.com
- Port: 7276
- Reset: HOT
- More -> SAVE !!!
TWRP and modifying /system issues on MIUI 11 (Android 9 system-as-root)
After installing TWRP and you want to change files in TWRP mode on /system_root/system it will not work.
You need to install MAGISK and then use SU to modify the system. (TWRP/MAGISK instructions: https://forum.xda-developers.com/re...de-unlocking-bootloader-twrp-rooting-t4031831)
Some mods for rooted ginkgo (with Magisk)
Before overwrite PLEASE make copy of original file FIRST (like build.prop.ORG)
- /system/build.prop (see last part in build.prop that was added, if you have other MIUI version add only the that last part)
- /system/etc/device-features/ginkgo.xml (expose some other features on the MIUI ROM)
- /data/adb/service.d/tweakradje-ginkgo.sh (my script to "correct" some cpu/linux settings, also loads my /system/etc/sysclt.conf)
- /system/etc/sysclt.conf (some linux/kernel improvements)
How to install from a pc:
Open DOS/CMD in the folder where the downloaded files are, unzip the zip files
Copy the files to the "/sdcard": adb push <file> /sdcard/
adb.exe shell
su
stop
mount -o rw,remount / (that is system partition)
mount -o rw,remount /vendor (that is vendor partition)
cd /system
cp -p build.prop build.prop.ORG (one time to make copy of original file)
cp /sdcard/build.prop . (permissions should be ok)
....etc...
sync
reboot
See attachements for files
Use fingerprint button for sleep
My fingerprint sensor is a fpc1020. Now I can reassign a tap on the fp sensor to any function.
Edit the file /system/usr/keylayout/uinput-fpc.kl (remember I have fpc sensor)
#key 96 DPAD_CENTER
key 96 SLEEP
#key 96 CAMERA
Wifi performance testing
Wifi performance is pretty avarage. When BT is switched on it is getting worse.
The wcn3990 Wifi/BT combo chip isn't that bad. Must be driver (firmware) issue or configuration issue.
I have attached /vendor./etc/wifi/WCNSS_qcom_cfg.ini file with some mods. Looks like it is little better.
Maybe you can give feedback?
EDIT: 23 aug 2020
Best experience for the RN8 using a MIUI based ROM: MiuiMiX_2.0_ginkgo_20.3.26_v11-9 Download: https://androidfilehost.com/?fid=4349826312261756420
For best wifi settings use this setting in GLOBAL db:
Code:
settings put --user 0 global wifi_score_params rssi2=-95:-85:-73:-60,rssi5=-85:-82:-70:-57
settings put --user 0 global wifi_coverage_extend_feature_enabled 0
settings put --user 0 global wifi_networks_available_notification_on 0
settings put --user 0 global wifi_poor_connection_warning 0
settings put --user 0 global wifi_scan_always_enabled 0
settings put --user 0 global wifi_scan_throttle_enabled 0
settings put --user 0 global wifi_verbose_logging_enabled 0
settings put --user 0 global wifi_suspend_optimizations_enabled 1
settings put --user 0 global wifi_wakeup_enabled 0
settings put --user 0 global sysui_powerui_enabled 1
settings put --user 0 global ble_scan_always_enabled 0
---new 4 jan 2021---
settings put global network_avoid_bad_wifi 0
settings put global network_scoring_ui_enabled 0
settings put global tcp_default_init_rwnd 20 #60, kernel 4-20 MAJOR network speedup! Also try 10!
settings put global wifi_country_code GB
settings put global wifi_frequency_band 0 #0=auto 1=5 2=2.4
settings put global wifi_max_dhcp_retry_count 0
settings put global wifi_framework_scan_interval_ms 0 # 5*60*1000 5min 0=don't scan when connected, we are stationary/screen on!
settings put global wifi_supplicant_scan_interval_ms 5000 #15000 15sec search while connected for connect, roaming or open network, screen on, not wakeup scan (5sec is min)
settings put global wifi_watchdog_poor_network_test_enabled 0
settings put global netstats_enabled 1 # bandwidth monitoring, some apps need this
settings put global connectivity_metrics_buffer_size 20000 #2000 max=10*2000
settings put system bluetooth_discoverability 1 # 2=always 1=only connect 0=off, improve wifi!
settings put system bluetooth_discoverable_timeout 60 #after 60s wifi is fast!
cmd wifi get-poll-rssi-interval-msecs
>>> WifiStateMachine.mPollRssiIntervalMsecs = 3000
cmd wifi get-ipreach-disconnect
>>> IPREACH_DISCONNECT state is true
cmd wifi set-ipreach-disconnect disabled
cmd wifi get-ipreach-disconnect
>>> IPREACH_DISCONNECT state is false
And add this before END to the /vendor/etc/wifi/WCNSS_qcom_cfg.ini file:
Code:
gEnableDebugLog=0
gLinkSpeedRssiHigh=-60
gLinkSpeedRssiMed=-70
gLinkSpeedRssiLow=-82
gEnableFatalEvent=0
5g_rssi_boost_threshold=-65
5g_rssi_boost_factor=2
5g_max_rssi_boost=20
gSetAntennaIsolation=15
enableBTChainSeparation=1
gSetBTCMode=1
HQ Hifi Headphone mod
Copy xml files over existing /vendor/etc/ files. Make copy of original first. Then reboot.
audio_platform_info_intcodec.xml
mixer_paths_idp.xml
For MiSound you maybe need to set setprop ro.audio.hifi true (or in /vendor/build.prop:ro.audio.hifi=true)
Suggestions are welcome! Please post below.
Cheers
my phone is rooted (magisk)
how to remove "updater" "find device" "fingerprint" "security" and "Gapps" without bootloop ?
tweakradje said:
Change Font
Goto Settings > Themes > More
Type the word Font in the Search box
In the Results you see Fonts > click More
Download and Apply the font. Reboot needed
Manage your Fonts: Use QuickShortcutMaker > Expand Themes > Click FontsettingsActivity > Try
Click to expand...
Click to collapse
Easier way:
Change Region into India
Force Stop Themes app
Open Themes app
There will be new categories like Fonts and Ringtones. When finish and reboot, change back to Region of choice
This trick still works since MIUI 4
Useful topic, particularly fot those that are on stock rom.
kokopipiss said:
Easier way:
Change Region into India
Force Stop Themes app
Open Themes app
There will be new categories like Fonts and Ringtones. When finish and reboot, change back to Region of choice
This trick still works since MIUI 4
Click to expand...
Click to collapse
Does this hold only with India or with other regions, too ?
TapaSte said:
Does this hold only with India or with other regions, too ?
Click to expand...
Click to collapse
different regions supposedly have different themes avaliable, so it would work with other regions too.
jc9896 said:
different regions supposedly have different themes avaliable, so it would work with other regions too.
Click to expand...
Click to collapse
The majority of other regions I've tried do not allow the font selection.
It's not a problem of themes choice...
Sent by RN8T
TapaSte said:
The majority of other regions I've tried do not allow the font selection.
It's not a problem of themes choice...
Sent by RN8T
Click to expand...
Click to collapse
then fonts are india & china exclusive then.
jc9896 said:
then fonts are india & china exclusive then.
Click to expand...
Click to collapse
Ok, thanks. Really strange that all over the world only China and India let the font choice.
Sent by RN8T
loopypalm said:
my phone is rooted (magisk)
how to remove "updater" "find device" "fingerprint" "security" and "Gapps" without bootloop ?
Click to expand...
Click to collapse
I have Installed an Xposed app called MIUI Anesthetist also Customiuizer , the 1st one has no interface but in it's description it won't let the phone be in bootloop after removing system app and I removed many system apps so far without any bootloop the 2nd one let do a lot of change in you MIUI you should give a try...
but you can't use those app without Xposed
also make a backup of you data in case
ssamurai said:
I have Installed an Xposed app called MIUI Anesthetist also Customiuizer , the 1st one has no interface but in it's description it won't let the phone be in bootloop after removing system app and I removed many system apps so far without any bootloop the 2nd one let do a lot of change in you MIUI you should give a try...
but you can't use those app without Xposed
also make a backup of you data in case
Click to expand...
Click to collapse
yes , i know about those 2 apps
but the idea of runing an app to prevent an app from runing is the same for me ^^
(you may have a bootloop if you force stop/freez the exposed module)
i gave up on miui rom last week, i installed a custom rom and until now it's waaay better than miui in ram managment and battery life ...
loopypalm said:
yes , i know about those 2 apps
but the idea of runing an app to prevent an app from runing is the same for me ^^
(you may have a bootloop if you force stop/freez the exposed module)
i gave up on miui rom last week, i installed a custom rom and until now it's waaay better than miui in ram managment and battery life ...
Click to expand...
Click to collapse
Indeed. Switching to crDroid 6.8 and test Inception 6.1 with it.
Battery life is crap on MIUI.
tweakradje said:
Indeed. Switching to crDroid 6.8 and test Inception 6.1 with it.
Battery life is crap on MIUI.
Click to expand...
Click to collapse
crDroid is good but has bad ram managment
(it also have a phone bug ,when you dial a number , you can't find it in recent calls until you relaunch the app)
i'm using "AospExtended-v7.3"
everything is working and ram usage is :
when i stop the background apps it takes 1.5gb or less (i have 6gb ram)
(the ram usage is done with gravitybox)
Tried crDroid 6.8 for 2 days but not satisfied. Battery life not so good, and wifi was terrible.
Now I'm back on MIUI 11 (TWRP backup).
loopypalm said:
yes , i know about those 2 apps
but the idea of runing an app to prevent an app from runing is the same for me ^^
(you may have a bootloop if you force stop/freez the exposed module)
i gave up on miui rom last week, i installed a custom rom and until now it's waaay better than miui in ram managment and battery life ...
Click to expand...
Click to collapse
I will install a custom rom also soon, the Miui rom is full of bug issue sending and receiving data in BT the internet sharing option via WIFI work only the that placed in the 2nd SIM slot, the Launcher is poor, can't copy paste a password and others things...
I'm testing LuisROM crDroid 6.8 now. Looks good so far.
Only MIUI Camera is not having good portrait mode (bokeh).
Can be downloaded from his site: http://luis-builds.de/downloads/lineageos/cr/Xiaomi_Redmi_Note_8-8T_(ginkgo-willow)/
Kudos to Frank
EDIT: Why does Wifi quits when connection speed is below 7 mbs? X appears in Wifi taskbar icon (not disconnected!) and mobile data takes over. What setting is that? Anyone? Something I can set in GLOBAL?
This doesn't help:
settings put global wifi_watchdog_on 0
settings put global wifi_watchdog_poor_network_test_enabled 0
settings put global network_avoid_bad_wifi 0
Maybe it has something to do with wifi_data_stall_min_tx_bad or wifi_link_probing_enabled
https://gerrit.pixysos.com/plugins/...5dc1/core/java/android/provider/Settings.java
Switching back to MIUI 11.0.9.0 again.
thanks
Now testing MIUI 12 (upgrated today from miui 11.0.9.0 Global to MiuiMix 12 ROM (MMX_2.2.0_ginkgo_20.8.13_v12-10_20200813)
https://androidfilehost.com/?fid=8889791610682914715
So far so good. But Wifi had trouble (like custom Android 10 ROMS)
Maybe found solution for wifi disconnect (from Android 9 and up). Testing for one day now and looks promissing.
1) add this line before END to /vendor/etc/wifi/WCNSS_qcom_cfg.ini -> gRoamPrefer5GHz=0 TEST maybe not needed!!!
2) in adb shell add this to global settings: settings put global wifi_score_params rssi2=-95:-85:-73:-60,rssi5=-85:-82:-70:-57
3) reboot
Let us know
Cheers
After experimenting I came to the conlusion that wifi antenna in Redmi Note 8 is terrible.
I compared it with wifi RSSI values of my old Redmi 4X and rssi values are at least 10 dB lower. That is more than 8 times worse antenna.
You might wonder if there is a wifi antenna at all in the Note 8.
I don't want to open the back cover to fix this (if possible). You get what you pay for. Be warned.
High Quality Headphones
Hi,
Added 2 xmlfiles for improved High Quality Headphone sound. Copy them to /vendor/etc (maybe make copy of original first?)
audio_platform_info_intcodec.xml
mixer_paths_idp.xml
For MiSound you maybe need to set setprop ro.audio.hifi true (or in build.prop:ro.audio.hifi=true)
Happy listening with good headphones
Cheers
how to wakeup screen by using fingerprint？i'm on aosp rom
same to set sleeping function in the uinput-fpc.kl
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Tired of all the pre-installed applications that come with your new phone. Most of them tend to be useless and some tend to be on annoying side with push notifications and battery drains.
One way to get rid of all these intruders is to root your device and delete them using some application or manual purge. Not everyone is comfortable with rooting and it's risks. Also, rooting is not an option on many phones coz of limited support from the developer community. Does that mean one has to learn to live with the bloat?
Thankfully, No. You can get rid of them with the use of ADB (Android Debugging Bridge). The method is safer than manual purge and would not break any system variables, allowing to keep accepting OTAs w/o any issues.
Let's Debloat your Phone.
Note: This method works on every OEM rom as well as custom rom without root access.
Requirements:
Android Platform Tools
Prerequisites:
Disable "App Vault", "Swipe up for google", "Wallpaper Carousel", "Find Device", "Mi Sync"(Don't confuse Mi Sync and Google Sync though)
Follow the steps carefully :
Initial Setup
1. Go to About Phone in Settings.
2. Tap on MIUI version/Build version until it shows You're now a developer. It might ask for password in some cases.
3. Go to Settings>Additional Settings>Developer Options or Settings>System>Developer Options.
4. Enable USB Debugging, Install via USB, USB Debugging(Security Settings). Accept all the prompts thrown.
Note: Most ROMs will only have USB Debugging toggle.
Note: On MIUI, the above step requires an MI Account.
Main Process
Connect your device to the PC now. Recommend using a good quality USB cable for this.
1. Extract the platform tools zip. Navigate to the folder.
2. Shift+Right click and select open command window here.
3. Type adb devices
4. Grant authorization on your phone.
5. Type adb devices again and ensure that it shows your device as connected and authorized.
Note: If your device doesn't show up, you might need to install latest USB drivers for your phone. It usually happens automatically if you have an updated OS. If that's not the case, use this and install the USB drivers.
6. Type adb shell.
7. Type
Code:
pm list packages | grep 'mi'
Here mi is a keyword. You can replace it with whatever you want. This command would return all packages which have the phrase mi in their name.
Type
Code:
pm list packages
for complete list of installed packages.
8. Type
Code:
pm uninstall -k --user 0 <package-name>
Replace the <package-name> with the package you want to remove. The names can be obtained from the list command in the previous step.
Tip: Package name can be found in app list. Just tap on the small 'i' icon on the top right corner of each app page on MIUI. On custom roms, it's usually given at the bottom.
Tip : If you can't see all apps. Tap on the three dots in the top corner on "Manage Apps" page and tap "Show All Apps". SImilarly on custom roms, it can be achieved by selecting "Show System Apps".
I'm not going to cover all the OEMs or Custom Roms. The process is similar across all OEMs and Custom Roms. Packages that are safe to remove on MIUI are given below:
(Skip to the next step if you're not on MIUI)
- Cleaner
Code:
com.miui.cleanmaster
- Tracking Application
Code:
com.miui.daemon
- Ad Serving Application
Code:
com.miui.msa.global
- Xiaomi System Webview
Code:
com.mi.webkit.core
- Tracking Application
Code:
com.xiaomi.joyose
- Facebook Bloat
Code:
com.facebook.services
- Facebook Bloat
Code:
com.facebook.appmanager
- Facebook Bloat
Code:
com.facebook.system
- Tracking Application
Code:
com.miui.analytics
- Wallpaper Carousel
Code:
com.miui.android.fashiongallery
- ShareMe/Mi Drop
Code:
com.xiaomi.midrop
- Broswer with Ads
Code:
com.android.browser
- Calendar with Ads
Code:
com.android.calendar
- Tracking Application
Code:
com.miui.bugreport
- Tracking Application
Code:
com.xiaomi.glgm
- Tracking Application
Code:
com.miui.yellowpage
- Weather Application
Code:
com.miui.weather2
- Tracking Application
Code:
com.miui.miservice
- Music player with Ads
Code:
com.miui.player
- Mi Pay
Code:
com.mipay.wallet.id
- Mi Pay
Code:
com.mipay.wallet.in
- Mi Pay
Code:
com.xiaomi.payment
- Quick Apps
Code:
com.miui.hybrid
- Quick Apps Addon
Code:
com.miui.hybrid.accessory
- Video Player with Ads
Code:
com.miui.videoplayer
- GetApps
Code:
com.xiaomi.mipicks
- Translation Service
Code:
com.miui.translation.kingsoft
- Translation Service
Code:
com.miui.translation.youdao
- Translation Service
Code:
com.miui.translation.xmcloud
- Translation Service
Code:
com.miui.translationservice
- Mi Doc Viewer (XPS based)
Code:
cn.wps.xiaomi.abroad.lite
- Recycle Service
Code:
com.xiaomi.mirecycle
- Ad based App Installer
Code:
com.miui.global.packageinstaller
- Auto Installs from Play Store
Code:
android.autoinstalls.config.Xiaomi.ginkgo
- App Vault
Code:
com.mi.android.globalminusscreen
- Mi Credit
Code:
com.micredit.in
- Mi Health
Code:
com.mi.health
- Downloads Application with Ads
Code:
com.android.providers.downloads.ui
(make sure you have an alternate file explorer installed before you uninstall the next one)
- Ad based File Explorer
Code:
com.mi.android.globalFileexplorer
Google BloatWare
A few Google Applications that always come pre-installed :
- Youtube
Code:
com.google.android.youtube
- Hangouts
Code:
com.google.android.talk
- Play Movies & TV
Code:
com.google.android.videos
- Google Duo
Code:
com.google.android.apps.tachyon
- Google Chrome
Code:
com.android.chrome
- Google Search Application
Code:
com.google.android.googlequicksearchbox
- Digital Wellbeing
Code:
com.google.android.apps.wellbeing
- Android Feedback
Code:
com.google.android.feedback
- Talkback
Code:
com.google.android.marvin.talkback
Note: Removal of Google Search App will Remove Assistant and Google search.
Conclusion
This is not a complete list. You can remove anything that you find annoying using these commands. Just replace the package name with the package you wish to remove.
However, removing some apps could cause issues. Stay away from MI Account, Security and Google Services related apps. If you accidentally remove something and end up experiencing crashes, please follow the following steps.
Type
Code:
adb shell
.
Type
Code:
cmd package install-existing <name-of-package>
Replace <name-of-package> with the name of the package to be restored.
Note : The method doesn't delete the application. It only changes the permissions of each package and hides it in the system. A Factory Reset, OTA update or a Reinstall would restore the application. Also, if you create a new user, he would have access to the removed applications.
MOD EDIT: Telegram link removed, please read the STICKY!
Reserved
using this much easier and faster https://github.com/Szaki/XiaomiADBFastbootTools
if i remember correctly when i was on miui (ginkgo)
i removed "Find Device" and the phone stay in bootloop
anyway ...
the command : pm uninstall -k --user 0 <package-name>
can remove app for user 0
but what if i want to remove the app for all users ???
nneko904 said:
using this much easier and faster https://github.com/Szaki/XiaomiADBFastbootTools
Click to expand...
Click to collapse
It's personal choice. The tool does the same thing. This is for people who want to do it manually without a tool.
Also that tool is specific to the xiaomi devices to an extent. You can use this on any android smartphone. This doesn't have java dependencies as well.
loopypalm said:
if i remember correctly when i was on miui (ginkgo)
i removed "Find Device" and the phone stay in bootloop
anyway ...
the command : pm uninstall -k --user 0 <package-name>
can remove app for user 0
but what if i want to remove the app for all users ???
Click to expand...
Click to collapse
You can't remove an app completely from the system without root access. If you have a second user, you have to remove it for other users as well.
And I haven't mentioned find find device anywhere.
Great, debloated here. Missed play music only.
uncannyjish said:
And I haven't mentioned find find device anywhere.
Click to expand...
Click to collapse
you mentioned it in prerequisites , i tought u r goin to remov it ...
uncannyjish said:
You can't remove an app completely from the system without root access. If you have a second user, you have to remove it for other users as well..
Click to expand...
Click to collapse
i have root access,and no 2nd user
when i use the comand the app is removed just for user 0 but it stays in the system
thats why i asked for a comand to remove it completely
loopypalm said:
you mentioned it in prerequisites , i tought u r goin to remov it ...
i have root access,and no 2nd user
when i use the comand the app is removed just for user 0 but it stays in the system
thats why i asked for a comand to remove it completely
Click to expand...
Click to collapse
Well if you're have root, and can mount system as rw. You could use some root explorer and remove the apk's and there folder. But doing this prevents the ability for OTA update because now the system is changed.
The space saved by doing this is so tiny, you will never notice it.
---------- Post added at 05:22 PM ---------- Previous post was at 04:53 PM ----------
uncannyjish said:
Note : The method doesn't delete the application. It only changes the permissions of each package and hides it in the system. A Factory Reset, OTA update or a Reinstall would restore the application. Also, if you create a new user, he would have access to the removed applications.
Click to expand...
Click to collapse
Very nice thread.
FYI, I have been doing this on stock ROMs for long time. It's nice to see a listed description.
FYI, with this adb method , your debloated apps will remain gone after an OTA update. At least for me they do.
mrmazak said:
Well if you're have root, and can mount system as rw. You could use some root explorer and remove the apk's and there folder. But doing this prevents the ability for OTA update because now the system is changed.
The space saved by doing this is so tiny, you will never notice it
Click to expand...
Click to collapse
i use custom rom and i don't want OTA
i asked for the command because it remove the app + data
i can delete the app manualy by browsing system/app or priv app but i have to look for eatch app data folder
loopypalm said:
i use custom rom and i don't want OTA
i asked for the command because it remove the app + data
i can delete the app manualy by browsing system/app or priv app but i have to look for eatch app data folder
Click to expand...
Click to collapse
Well if you are concerned about the app data being left. Just run the command as in the . OP bit leave the "-k" off. This part of the command is (keep) , it keeps the user data on device. If you run the command without the -k, then it does not keep data.
loopypalm said:
i use custom rom and i don't want OTA
i asked for the command because it remove the app + data
i can delete the app manualy by browsing system/app or priv app but i have to look for eatch app data folder
Click to expand...
Click to collapse
Try running adb root and use the uninstall command on the package without the flags. Since you're rooted, it might just remove app + data.
godoy.rafa said:
Great, debloated here. Missed play music only.
Click to expand...
Click to collapse
Find the package name and remove it. I already explained all command
loopypalm said:
you mentioned it in prerequisites , i tought u r goin to remov it ...
i have root access,and no 2nd user
when i use the comand the app is removed just for user 0 but it stays in the system
thats why i asked for a comand to remove it completely
Click to expand...
Click to collapse
I asked everyone to disable those stuff, so to prevent any app from returning.
mrmazak said:
Well if you are concerned about the app data being left. Just run the command as in the . OP bit leave the "-k" off. This part of the command is (keep) , it keeps the user data on device. If you run the command without the -k, then it does not keep data.
Click to expand...
Click to collapse
i know, i asked for a command that remove the app completly not only for "user 0" and it seems no one knows it
Can i remove gallery? Is it safe? I mean com.miui.gallery .
OliveReeve said:
Can i remove gallery? Is it safe? I mean com.miui.gallery .
Click to expand...
Click to collapse
yes
OliveReeve said:
Can i remove gallery? Is it safe? I mean com.miui.gallery .
Click to expand...
Click to collapse
better not, there's several problems user reported when they remove it
there's many thread over which app you could remove and shouldn't, i recommend you should go search them
nneko904 said:
better not, there's several problems user reported when they remove it
there's many thread over which app you could remove and shouldn't, i recommend you should go search them
Click to expand...
Click to collapse
What problems are related to miui gallery removal? Please tell me I don't want to search over whole xda. It is probably bootloop too but I am not sure (hint from some github page).
---------- Post added at 11:27 AM ---------- Previous post was at 11:24 AM ----------
If I get it it to bootloop by debloating, Can I fix it by adb? I know that I can reinstall app back by adb. I don't have root and twrp so far. Does it respond to adb during this bootloop?
OliveReeve said:
What problems are related to miui gallery removal? Please tell me I don't want to search over whole xda. It is probably bootloop too but I am not sure (hint from some github page).
---------- Post added at 11:27 AM ---------- Previous post was at 11:24 AM ----------
If I get it it to bootloop by debloating, Can I fix it by adb? I know that I can reinstall app back by adb. I don't have root and twrp so far. Does it respond to adb during this bootloop?
Click to expand...
Click to collapse
If you get bootloop from adb app uninstall, you will not get to use adb. Factory reset from recovery will undo the changes.
As for the gallery apk. I had removed it and was no longer able to save any photos, from any camera. I was not able to delete files from device either. The gallery app is somehow forced into needed for /sdcard file permissions. You can set it to "adb hide". If you don't want to see it
If you've installed a custom ROM that doesn't come with Android Auto pre-installed, you'll get the following error when connecting your phone to your car (the Android Auto app opens correctly, the error is only shown when you connect to the car):
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This error happens because Android Auto is not installed as a system app under /system/priv-app.
The following steps will ensure you can convert Android Auto from a user app to a system app. As usual, I'm not responsible for any damage to your device due to this guide.
Requirements:
Magisk and Magisk Manager (I've tested with 24.3)
Android Auto installed as a user app (I have 7.6.621734-release)
A computer with ADB or an app like Termux
I've tested this on a Xiaomi 11T Pro with Pixel Experience Plus Slim 12.1 (GSI) and Android 12, but it should work for other devices and ROMs as well.
Steps:
Install BusyBox from the Play Store
I could only install to /system/bin, but try out what works for you ROM
Click "Install" and wait for a successful message
(optional) This is just a BusyBox installer, I think you can remove the app at the end of this tutorial
Download terminal_systemizer Magisk module. Keep in mind the latest official release is outdated and does not work on Android 12 and Magisk 24.3. Because of this, you can download it from this post on XDA or clone this fork on GitHub and zip it
Install the Magisk module through Magisk Manager and reboot
Now connect your phone to your computer and launch an adb shell with adb shell, or open Termux
Enter root mode by typing su (not sure if this is required on Termux, but you must do it on adb shell)
Verify that the systemizer module is working by running the help command
Code:
# systemize -h
App Systemizer (Terminal Emulator) v17.5(73)
by veez21, KreAch3R, entr0pia
Usage: systemize
or: systemize [options]...
Options:
-nc removes ANSI escape codes
-f use 'Set SELinux' in the session for faster app listing
-a [package name] systemizes the package name(s) provided
-d [apk dir] systemizes the apk(s) provided
-l list all systemized apps
-h show this message
If you get a similar output, you're ready to proceed
Now run the systemize command without any arguments and answer the prompts accordingly. The app you want to systemize is com.google.android.projection.gearhead, which is Android Auto. You want to install it to /system/priv-app and NOT to /system/app.
Below is a sample output:
Code:
============================================
App Systemizer (Terminal Emulator) v17.5(73)
by veez21, KreAch3R, entr0pia
============================================
BusyBox v1.32.0-Stericson
/system/bin/busybox
============================================
Enter logs to upload logs
============================================
Set SELinux Enabled: false
SELinux Status: Enforcing
============================================
1 - Systemize Installed Apps (Listed)
2 - Systemize Installed Apps (Enter label)
3 - Systemize given APK
s - Set SELinux
0 - Exit
[CHOICE]: 1
Loading Apps [/]
============================================
Installed Apps =============================
============================================
...
18 - com.google.android.projection.gearhead
...
To systemize multiple apps, enter multiple number. Example: "1 23 30"
x - Back to Menu
r - Refresh list
0 - Exit
[CHOICE]: 18
============================================
Systemizing com.google.android.projection.gearhead
Checking APK directory - OK
Checking package name - com.google.android.projection.gearhead
Where to install?
< 1 - /system/app | 2 - /system/priv-app | 0 - cancel > : 2
Checking APK size - 41M
Transfering base.apk(com.google.android.projection.gearhead) to '/system/priv-app'...
Transfering libs
Granting Permissions
/system/bin/systemize[584]: aapt: can't execute: Permission denied
com.google.android.projection.gearhead - Done
Reboot to apply changes
Return to menu? < y | n >: n
Notice that it threw an error at the end, but it still worked for me. Not sure what happened, let me know if this also happened to you.
Reboot
Check that Android Auto is a system app by opening its app info page. If there is no uninstall button like below, it's installed as a system app
Please reply if you have any questions or issues!
Hope this helps
Good guide
Yh this error comes because Android auto needs to be installed as an system app.
Thank you for sharing this, I made all the steps, it worked without errors but I see the app as system app but I don't have "open" button, in fact the app itself doesn't appear with others (I had to search in settings>app)
Any idea? Thx
suiller said:
Thank you for sharing this, I made all the steps, it worked without errors but I see the app as system app but I don't have "open" button, in fact the app itself doesn't appear with others (I had to search in settings>app)
Any idea? Thx
Click to expand...
Click to collapse
Hm that's weird, I don't see how that could happen.
Try grabbing an APK from apkmirror and installing the app again (must be the same version or newer)
I managed it... now I see the app as regular (system) app...
The problem was busybox, I used that one provided as magisk module and worked at 1st attempt
diogotc said:
Hm that's weird, I don't see how that could happen.
Click to expand...
Click to collapse
I dunno why but busybox was the problem, I just installed the version provided here in 1st post, even if without error something happened so I had the app moved under priv but it wasn't available as regular/working app
Anyway I had to:
restore androidauto from systemize, reboot
deinstall androidauto, reboot
install busybox as module from magisk
re-run systemize as instructions at 1st post, reboot
Hi
no work for me
have asus rog 5 with china rom
installed android auto
root ok
i follow this guide...android auto install is marked ok and seems all ok....it is system app
but in my car i obtain a loop android auto: link, after 1 sec stop, then link, then stop and so away
if i run systemize again, android auto is not became a system app anymore
Thanks bro work great Xiaomi 12s ultra 13.0.8
Thanks for your guide,it worked on a Redmi Note 7 with latest PPUI ROM, but as soon as I remove Magisk the app reverts to user app and not system app. Since I cant get my bank app to work on rooted phones, even with Magisk hidden, is there a way to keep AA as system app without having to keep Magisk installed?
farrayoles said:
Thanks for your guide,it worked on a Redmi Note 7 with latest PPUI ROM, but as soon as I remove Magisk the app reverts to user app and not system app. Since I cant get my bank app to work on rooted phones, even with Magisk hidden, is there a way to keep AA as system app without having to keep Magisk installed?
Click to expand...
Click to collapse
As far as I know you'll need Magisk installed. The latest version of the Pixel Experience GSI already includes an Android Auto stub to avoid this problem, maybe you can ask that ROM developer to do the same.
Anyway, you should be able to bypass your banking app verification. Have you added it to the DenyList as well as change the package name of MagiskManager?
You can try an app like RootBeer to see what else you need to do.
It might also help deleting the data from the banking app, since it might store if you had root or not.
Hope that helps!
Skyline_r said:
Thanks bro work great Xiaomi 12s ultra 13.0.8
Click to expand...
Click to collapse
Does wireless android auto work for you? My AA crashes on the xiaomi mi fold x 2
Does Root is required to do so before start? Becuase I can't install Busybox if the phone is not rooted.
I tried this on my SM-X200 and all the steps worked (can not uninstall at app info) but when I went to plug the tablet into my car it still gives me error 22
Skyline_r said:
Thanks bro work great Xiaomi 12s ultra 13.0.8
Click to expand...
Click to collapse
hi, can i check if you performed these steps on a custom rom? or the chinese rom? thanks!
diogotc said:
If you've installed a custom ROM that doesn't come with Android Auto pre-installed, you'll get the following error when connecting your phone to your car (the Android Auto app opens correctly, the error is only shown when you connect to the car):
View attachment 5636057
This error happens because Android Auto is not installed as a system app under /system/priv-app.
The following steps will ensure you can convert Android Auto from a user app to a system app. As usual, I'm not responsible for any damage to your device due to this guide.
Requirements:
Magisk and Magisk Manager (I've tested with 24.3)
Android Auto installed as a user app (I have 7.6.621734-release)
A computer with ADB or an app like Termux
I've tested this on a Xiaomi 11T Pro with Pixel Experience Plus Slim 12.1 (GSI) and Android 12, but it should work for other devices and ROMs as well.
Steps:
Install BusyBox from the Play Store
I could only install to /system/bin, but try out what works for you ROM
Click "Install" and wait for a successful message
(optional) This is just a BusyBox installer, I think you can remove the app at the end of this tutorial
Download terminal_systemizer Magisk module. Keep in mind the latest official release is outdated and does not work on Android 12 and Magisk 24.3. Because of this, you can download it from this post on XDA or clone this fork on GitHub and zip it
Install the Magisk module through Magisk Manager and reboot
Now connect your phone to your computer and launch an adb shell with adb shell, or open Termux
Enter root mode by typing su (not sure if this is required on Termux, but you must do it on adb shell)
Verify that the systemizer module is working by running the help command
Code:
# systemize -h
App Systemizer (Terminal Emulator) v17.5(73)
by veez21, KreAch3R, entr0pia
Usage: systemize
or: systemize [options]...
Options:
-nc removes ANSI escape codes
-f use 'Set SELinux' in the session for faster app listing
-a [package name] systemizes the package name(s) provided
-d [apk dir] systemizes the apk(s) provided
-l list all systemized apps
-h show this message
If you get a similar output, you're ready to proceed
Now run the systemize command without any arguments and answer the prompts accordingly. The app you want to systemize is com.google.android.projection.gearhead, which is Android Auto. You want to install it to /system/priv-app and NOT to /system/app.
Below is a sample output:
Code:
============================================
App Systemizer (Terminal Emulator) v17.5(73)
by veez21, KreAch3R, entr0pia
============================================
BusyBox v1.32.0-Stericson
/system/bin/busybox
============================================
Enter logs to upload logs
============================================
Set SELinux Enabled: false
SELinux Status: Enforcing
============================================
1 - Systemize Installed Apps (Listed)
2 - Systemize Installed Apps (Enter label)
3 - Systemize given APK
s - Set SELinux
0 - Exit
[CHOICE]: 1
Loading Apps [/]
============================================
Installed Apps =============================
============================================
...
18 - com.google.android.projection.gearhead
...
To systemize multiple apps, enter multiple number. Example: "1 23 30"
x - Back to Menu
r - Refresh list
0 - Exit
[CHOICE]: 18
============================================
Systemizing com.google.android.projection.gearhead
Checking APK directory - OK
Checking package name - com.google.android.projection.gearhead
Where to install?
< 1 - /system/app | 2 - /system/priv-app | 0 - cancel > : 2
Checking APK size - 41M
Transfering base.apk(com.google.android.projection.gearhead) to '/system/priv-app'...
Transfering libs
Granting Permissions
/system/bin/systemize[584]: aapt: can't execute: Permission denied
com.google.android.projection.gearhead - Done
Reboot to apply changes
Return to menu? < y | n >: n
Notice that it threw an error at the end, but it still worked for me. Not sure what happened, let me know if this also happened to you.
Reboot
Check that Android Auto is a system app by opening its app info page. If there is no uninstall button like below, it's installed as a system app
View attachment 5636069
Please reply if you have any questions or issues!
Hope this helps
Click to expand...
Click to collapse
Hey Bro. I'm trying to follow your instruction but I'm not able to use the busy box it's saying that I should remove the superuser.
Can you please help?
Hi, diogotc
Thank you so much, worked flawlessly. The instructions you provided were excellent. I used the systemizer on AA 8.3.624114. I used this on a Lenovo Legion Duel 2 with CN rom Android 12, with Magisk 25.2.
One difference I had was the AA app was just named Android Auto (number 3) in the systemizer list, but I had zero issues.
Thanks again!
The con.android.... path does not appear... I stay un systemize option 1 por 2 and it tells me that the file does not existe, do i hace to create it un busybox?
I don't understand why it doesn't appear it xd
Thanks for this
Just followed your instructions running ThinROM A13 v4 [15/12/2022]-[GVK9-[EXYNOS]-[SM-N986B]-[SM-N985F] on my SGN20U (SM-N986B/DS)
I couldn't get SU permission, Terminal Systemizer was greyed out in MM, so installed ADB Root v1.0 and it all worked like a charm from there.
Hi,
Thanks for the guide. I want to install the Android Auto on Redmi Pad so that I can use the pad as an Entertainment HeadUnit in my car. Can I follow these instructions and still it will work ?
Let me know. Appreciate your help and support
Thanks for that useful post but i'm receiving error after choose 2 - /system/priv-app and paste com.google.android.projection.gearhead
/data/app/com.google.android.projection.gearhead-*/base.apk doesn't exist!
Android auto is already insattaled. i'm using windows 10 and adb shell command.
Any idea ?
Overview
This rooting method is based on a vulnerability in the ARM Mali GPU driver (CVE-2022-38181) discovered by security researcher Man Yue Mo at GitHub Security Lab, to gain root access to the 2nd gen Cube that is on firmware PS7624/3337 or older. Newer method for PS7633 and PS7646 here.
The exploit program (raven_shrinker) is run directly on the Cube to spawn a temporary root shell for quick access. It can also be run automatically on every boot in combination with @diplomatic's bootless Magisk script to grant apps root access. Cubes that are on firmware PS7292/2984 or older, are able to use @Functioner's bootloader exploit used in the previous Raven Root bootloader unlock to install TWRP & full Magisk without a DFU device.
For best results, run raven_shrinker 30-90sec after boot up, when loading is complete and the device is idle.
Three options for root depending on your needs & comfort level
1) Temporary ADB root - Open an adb root shell to for quick access (PS7624/3337 or older)
Pros:
Access all files and folders from ADB
Simple to use, runs in RAM and doesn't make any changes to the Cube, no chance of bricking.
Remove app package protection so that you can enable/disable any app even without root (eg custom launchers, disabling updates, debloat, etc).
Cons:
Only enables ADB root
raven_shrinker occassionally crashes/reboots the Cube when being run. Run it 30-90sec after bootup for greater reliability.
NOTE: raven_shrinker won't brick your device, but what you do with that root access can. DM-verity is still in place checking the integrity of the system/vendor partitions, do NOT modify anything in those directories, or the boot partition!!
2) Bootless Magisk - Automatically start a lite version of Magisk that runs entirely from the data partition, (PS7624/3337 or older).
Pros:
Both ADB root and ability to grant root to apps through Magisk Manager
Once the Magisk dameon has started, root can be granted stably whenever needed
Doesn't modify boot or system/vendor partitions, DM-verity is preserved
Cons:
This is experimental, use at your own risk! It's been working stably during my testing but it's impossible to foresee every issue.
Still relies on raven_shrinker to start, and may occasionally crash when raven_shrinker runs at boot
Most Magisk modules don't work.
NOTE: Be careful of what apps you give root access to. Giving root access to an app that modifies the boot, system or vendor partitions will brick your device. Again, DM-verity is still actively checking that no changes have been made to system/vendor directories.
3) Bootloader Unlock - Install Magisk & TWRP, and enable many more features (PS7292/2984 or older)
Pros:
Use the latest version of Magisk, with Zygisk & module support
Use TWRP for backups & upgrades
Unrestricted use of Fastboot and the U-Boot command line (Amlogic Update)
Only requires raven_shrinker for the initial installation, more stable and tested than bootless Magisk
Remap Cube buttons to allow booting to fastboot, TWRP, Amlogic update.
Possible to update firmware to PS7624/3337 through TWRP and keep device unlocked
Cons:
There is no recovery option in case of a brick.
Requires older firmware to work
NOTE: It's very important to NEVER allow the Amazon OTA app to update the firmware. NEVER run the factory reset option in FireOS settings. If either of these occur, the Cube will be bricked.
Contributors:
Man Yue Mo, @Functioner, @Pro-me3us
Thanks to @Michajin & @mavsman13 for testing & feedback
Thanks to @diplomatic for bootless Magisk script, and @SweenWolf for Launcher Manager
Thanks to @Renate for many great tools
Thanks to all the folks who have worked on TWRP & Magisk
Temporary ADB root (PS7624/3337 or older)
Disclaimer: Use this at your own risk, I'm not responsible for any data loss or corruption to your device. There is a nonzero chance of bricking the Cube, and little to no recovery options.
Instructions
Enable ADB debugging in FireOS settings
Download, unzip and copy raven_shrinker to your Cube
Code:
adb push raven_shrinker /data/local/tmp/
Give raven_shrinker execution permission (only needs to be done once)
Code:
adb shell
chmod +x /data/local/tmp/raven_shrinker
Run the program
For best results, run raven_shrinker 30-90sec after boot up, when loading is complete and the device is idle.
Code:
adb shell
/data/local/tmp/raven_shrinker
NOTE: Some functions do not work with this root shell. Services can't be accessed, so package manager 'pm' commands can't be run as root. However, package protections can still be removed so that you can enable/disable any app without root. Use bootless Magisk option if you need to access services as root.
How to disable package protection
Use raven_shrinker to open a root shell and delete all the apps listed in the file /data/system/PackageManagerDenyList
Code:
echo '<?xml version="1.0" encoding="utf-8" standalone="yes" ?><map><set name="DenyListKeyPackages"></set></map>' > /data/system/PackageManagerDenyList
Exit out of the root shell, and clear Arcus Proxy
Code:
exit
pm clear com.fireos.arcus.proxy
A reboot is required before the changes take effect, but FireOS will attempt to connect to Amazon servers on bootup and rebuild PackageManagerDenyList. Temporarily disable your internet, so that the Cube can't connect to the internet, then reboot.
Package protections are now removed, and Arcus Proxy needs to be disabled to prevent it from being re-activated
Code:
pm clear com.fireos.arcus.proxy
pm disable-user com.fireos.arcus.proxy
Re-enable your Internet. You should now be able to enable/disable any app. Verify that any apps you disable are actually disabled. Then reboot, and verify again!
Code:
pm list packages -d
It's strongly recommended that you disable updates immediately
Code:
pm disable-user com.amazon.device.software.ota
pm clear com.amazon.device.software.ota
pm disable-user com.amazon.device.software.ota.override
pm disable-user com.amazon.tv.forcedotaupdater.v2
Changelog:
v1.1 April 23th, 2023
Fix for PS7608/3614
v1.2 May 4th, 2023
added support for PS7206/1098
v1.3 June 23rd, 2023
added support for PS7201/942
Bootless Magisk (PS7624/3337 or older)
These instructions use an adapted version of @diplomatic's bootless Magisk script, it's recommended you read the original post to better understand how it works, and it's limitations.
Disclaimer: Use this at your own risk, we're not responsible for any data loss or corruption to your device. There is a nonzero chance of bricking the Cube, and little to no recovery options.
There are two reports of a possible compatibility issue with PS7614/3227, so we aren't recommending this method for that firmware at this time.
Instructions
Enable ADB debugging in FireOS settings
Download raven_bootless_magisk, unzip it, and copy it to your Cube keeping the same directory structure
Code:
adb shell mkdir /data/local/tmp/bin
adb push raven_bootless_magisk/* /data/local/tmp/
adb shell pm install -r /data/local/tmp/magisk_manager.apk
Give scripts & binaries execution permissions
Code:
adb shell
chmod +x /data/local/tmp/start.sh
chmod +x /data/local/tmp/magisk-boot.sh
chmod +x /data/local/tmp/bin/raven_shrinker
chmod +x /data/local/tmp/bin/magiskinit
Install Launcher Manager on your Cube, open, navigate to 'other settings', 'ADB Commands'
Tap on the + icon in the top right corner to create a new command
Enter Name: Start Magisk
Enter Command: sleep 30 && /data/local/tmp/start.sh
Check 'Execute on Boot'
Save
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
When you reboot your Cube, bootless Magisk will automatically start ~30sec after your homescreen loads. It's important that FireOS has loaded and that the device isn't busy, so don't open any apps until after Magisk has loaded. There's a greater chance that raven_shrinker will fail or reboot the Cube while launching Magisk if the device is busy.
TO AVOID BRICKING YOUR DEVICE:
Be careful of what apps you give root access to. Giving root access to an app that modifies the boot, system or vendor partitions will brick your device. DM-verity is still actively checking that system/vendor directories haven't been tampered with.
Don't run the boot-magisk.sh script (from either ADB or Launcher Manager) more than once per boot. Doing so will mess up the mounting and module initiation.
Never toggle ADB debugging off/on in the Developer's menu while Magisk is running. This will kill the Magisk daemon running in the background, and could corrupt your device if it's in the middle of an important process.
Only use WiFi ADB, not USB ADB. Booting the Cube with an USB attached computer puts USB in device mode, and ADB will close and kill Magisk when the Cube sleeps in device mode.
This release includes Magisk v21.4 (magiskinit) and Magisk Manager v8.0.7. Don't update Magisk! Patching your boot image will brick your device!
Changelog:
v1.1 April 23th, 2023
Fix for PS7608/3614
v1.2 May 4th, 2023
Added support for PS7206/1098
v1.3 June 23rd, 2023
Added support for PS7201/942
Bootloader unlock, install TWRP & Magisk (PS7292/2984 or older)
This rooting method will put your Cube on the same exploit and software versions used in the original Raven Root, without a DFU recovery option. Please post any questions or problems regarding this post & it's process, on the Raven Root thread.
Disclaimer: Use this at your own risk, I'm not responsible for any data loss or corruption to your device. There is a nonzero chance of bricking the Cube, and little to no recovery options.
NEVER FACTORY RESET YOUR CUBE!!!
NEVER ALLOW AN AMAZON OTA UPDATE!!!
Both of these will brick your Cube!
To avoid any potential conflicts, if you were previously using a different version of Magisk, such as bootless Magisk (v21.4), first delete /data/adb/magisk.db before proceeding.
Instructions
Enable ADB debugging in FireOS settings
Download the raven_root_shrinker, unzip, and copy the 7 files to /data/local/tmp on the Cube
Code:
adb push raven_root_shrinker/* /data/local/tmp/
Give raven_shrinker & install script executable permissions
Code:
adb shell
chmod +x /data/local/tmp/raven_shrinker
chmod +x /data/local/tmp/install_root.sh
Open a root shell and run the install_root.sh script
Code:
adb shell
/data/local/tmp/raven_shrinker
/data/local/tmp/install_root.sh
Finish by typing 'exit' to switch root back to regular shell, install Magisk Manager, and reboot to TWRP
Code:
exit
pm install -r /data/local/tmp/magisk.apk
reboot recovery
The Cube will reboot to TWRP, automatically flash Magisk and Amazon OTA blocker module, then reboot back to FireOS.
NOTE: It's very important to NEVER allow the Amazon OTA app to update the firmware. NEVER run the factory reset option in FireOS settings. If either of these occur, the Cube will be bricked.
Read here for TWRP firmware flashing instructions
Changelog:
v2.2.1 April 23th, 2023
Added additional Magisk script to help prevent user from accidentally initiating FireOS factory reset.
If you already installed v2.2, you can copy and paste the following as one ADB command to add this script to your Cube:
Code:
echo '#!/sbin/sh
# Rename misc partition
mv /dev/block/misc /dev/block/misc_real
# Create symbolic links
ln -s /dev/null /dev/block/misc' > /data/adb/post-fs-data.d/misc_hide.sh && chmod +x /data/adb/post-fs-data.d/misc_hide.sh
v2.2.2 May 4th, 2023
Added support for PS7206/1098
v2.2.3 June 23rd, 2023
Added support for PS7201/942
reserved
to bad: mine was already on PS7633/3445
Hey @Pro-me3us . I've been trying to use the 2.2 update with no luck. My cube is on version PS7292/2984. I keep getting the message "/data/local/tmp/raven_shrinker: can't execute: Permission denied." Not sure what I'm doing wrong. Any help would be greatly appreciated.
coltxL2717 said:
Hey @Pro-me3us . I keep getting the message "/data/local/tmp/raven_shrinker: can't execute: Permission denied."
Click to expand...
Click to collapse
I didn't need to change the permissions on raven_shrinker while testing, but maybe that's different on other firmware versions.
Try this:
Code:
chmod +x /data/local/tmp/raven_shrinker
This will give the file execution permission. Let me know if that works, then I'll add it to the instructions. You only need to do this once for that file.
You may also need to do the same for install_root.sh in that case. Try running it first without, and if needed use:
Code:
chmod +x /data/local/tmp/install_root.sh
Pro-me3us said:
I didn't need to change the permissions on raven_shrinker while testing, but maybe that's different on other firmware versions.
Try this:
Code:
chmod +x /data/local/tmp/raven_shrinker
This will give the file execution permission. Let me know if that works, then I'll add it to the instructions. You only need to do this once for that file.
You may also need to do the same for install_root.sh in that case. Try running it first without, and if needed use:
Code:
chmod +x /data/local/tmp/install_root.sh
Click to expand...
Click to collapse
That did it. Thank you so much. I had to chmod both files for the root to work.
coltxL2717 said:
That did it. Thank you so much. I had to chmod both files for the root to work.
Click to expand...
Click to collapse
Thanks for confirming, added granting executable permissions to the instructions
How to block future updates?
errut said:
How to block future updates?
Click to expand...
Click to collapse
Post #2 (needs root). unless you are on PS7633/3445 +, then you have to do it on a network router blocking the OTA webwites.
Good afternoon . I would like to clarify whether it is possible to install TWRP on my Cube?
teschke said:
Good afternoon . I would like to clarify whether it is possible to install TWRP on my Cube?
Click to expand...
Click to collapse
Yes, your firmware is older than PS7292 so you can use these instructions
This will install TWRP 3.7.0-9.0 + Magisk 25.208.
Hi all,
where can I DL "The exploit program (raven_shrinker") ?
u_no_fr said:
Hi all,
where can I DL "The exploit program (raven_shrinker") ?
Click to expand...
Click to collapse
It's part of each of the three methods listed in the OP
1) Temporary root (raven_shrinker only)
2) bootless Magisk
3) bootloader unlock
Check the post attachments
Hi,
Thanks for posting this.
I have two Gen 2 Cubes that are on Fire OS 7.2.4.2 (PS7242/2906). Both have updates blocked.
If I installed TWRP and Magisk, what can I do? Are there and roms you recommend I install?
Sorry for asking. I have installed roms on old Samsung and LG phones but never done anything like this on Fire TV products.
Thanks
Osaka_23 said:
I have two Gen 2 Cubes that are on Fire OS 7.2.4.2 (PS7242/2906). Both have updates blocked.
If I installed TWRP and Magisk, what can I do? Are there and roms you recommend I install?
Click to expand...
Click to collapse
There aren't any custom ROMs for the Cube at the moment. TWRP would let you update to PS7624/3337 while maintaining root, but honestly I don't see a whole lot of benefit to the post PS7273 firmware. There are a handful of small new features, nothing particularly great IMO.
Magisk might actually have more of a functional benefit for you. With that you can grant apps root, and use modules. Exposed Edge is very nice, and will let you completely remap your remote buttons, including double and tripple clicks, overlays, shortcuts, etc. You can change the bootup logo, use file explorers with full system access etc. TWRP/Magisk are just the tools, what you do with them is up to you
Hello Pro-me3us, my cube is running PS7633/3445. I followed the instructions #2 to Temporary ADB root (PS7624/3337 or older)
I was able to push the file (or i had to push the folder???)
Well, then after
raven:/ $ /data/local/tmp/raven_shrinker
fingerprint: Amazon/raven/raven:9/PS7633.3445N/0027347744000:user/amz-p,release-keys
/data/local/tmp/raven_shrinker: flags_change failed
: Invalid argument
what can i do now?
any help ?
thanks
Note: the file was pushed because:
1|raven:/ $ cd /data/local/tmp/
127|raven:/data/local/tmp $ ls
raven_shrinker
yakovperelman69 said:
my cube is running PS7633/3445
Click to expand...
Click to collapse
The vulnerability was patched in PS7633/3445, so it won't work on any firmware newer than PS7624/3337. There's no workaround.