[TIP/TRICK] - How to enable app/screen pinning on MIUI [works for other devices] - Redmi Note 8 Pro Guides, News, & Discussion

Code:
/*
* I am not responsible for bricked devices, dead SD cards, data loss,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about tips provided here.
* Before making any alteration to your system make sure you know what you
* are doing and have previously made a backup of all sensitive data!
* YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will just laugh at you.
*/
BEWARE THE APP LINKED IN THIS THREAD ALLOW YOU TO MAKE MODIFICATIONS TO YOUR OPERATING SYSTEM WHICH CAN SERIOUSLY MESS UP YOUR DEVICE, SOME YOU MIGHT NOT BE ABLE TO RECOVER FROM
Credits for this trick goes to those two threads here and here where I found the technique.
As being said by @Thakur here are the steps to reproduce to enable app pinning.
[email protected] said:
Steps to activate/disable Screen pinning:
- Install Settings Database Editor
- Open App and go to "System Table"
- Find or Create a key (it didn't exist in my case, so I created it) with name "lock_to_app_enabled" and set value "1" (ON) or "0" (OFF)
Tested in miui global beta 9.3.21 and works flawlessly.
Credits: VAGR2018
Click to expand...
Click to collapse
Despite being last updated in 2018 the app Settings Database Editor by 4A, I can confirm this application works flawlessly on my EEA RN8PRO running MIUI 11.0.2.0 PGGEUXM.
The app being a bit similar to like regedit on Windows, dong go mess up with everything or it might end up with cries and tears.
At this point you already have App Pinning enabled. But only this.
If like for me it was enough, you may want to proceed with the next step which will enable screenlock on unpinning.
Assuming I would find the matching setting for that from a phone running stock android, I grabbed my old non MIUI phone and went to dig for the corresponding setting to lock screen when unpinning.
Turns out we can enable lock on unpinning by just adding an other simple value key in the Secure table.
To be allowed to do so, you first need to grant extra permission to app through adb:
It may not be the case for all devices but for my RN8PRO I needed root (su) to apply the adb command.
Code:
pm grant by4a.setedit22 android.permission.WRITE_SECURE_SETTINGS
Once permission granted, select Secure table in the Settings Database Editor application , and add the following new key:
Code:
lock_in_app_exit_locked 1
All set, you will now be asked to unlock screen once you unpin pinned app by long pressing back.
Hope this helps.
Regards.

Related

Viper4Android Working on S6 Edge (Root)

Here is how I got Viper4Android working on my stock rooted S6 Edge. This has been confirmed to work on the original S6 (non-Edge) version (see here).
Try it at your own risk. Also, if you don't know how to rename files, place new files under the "/System/" directory, change permissions, or disable system apps... don't even try to do this. Maybe in the future when we get a true custom recovery we can then create a flashable zip.
Below is what I did to get it to work:
1. Root your phone and install "Busybox". (Search to learn how)
- Example: BusyBox by Stephen (Stericson)
2. Download the latest of Viper4Android APK file and place it under "/System/Priv-app/Viper4Android/" folder. Don't attempt to install it just place the apk in this location. Also make both the Viper4Android folder and apk file have their permission set too 0755 or full access of 0777. ( Permission help, click here )
- Better Option: Alternative download to the Viper4Android APK, attached below. (I personaly use this, and others report better success. This Viper4Android version was originally created and post from this thread)
- Viper4Android Official Thread: http://forum.xda-developers.com/showthread.php?t=2191223
3. Locate the audio_effect.conf file under "/System/etc/" and rename it to "audio_effect.conf.bak". This is to save a copy of original file in case you need to revert back.
4. Download the new "audio_effect.conf.zip" (attached below) and extract the "audio_effect.conf" from the zip to the "/System/etc/" and "/vender/etc/" folders. Make sure the permissions are set to "0644" after dropping the audio_effect.conf in both locations. ( Permission help, click here )
- The "audio_effect.conf.zip" file includes the original stock audio_effect.conf and modified version so you can revert back if needed.
5. Using TitaniumBackup, freeze/disable the following apps:
Adapt Sound 4.0
SoundAlive 3.0
(if you skip the #5 step this install will never work)
6. Reboot your phone.
7. Open Viper4Android. You should be prompt to install drivers and allow superuser access. Do so, and reboot your phone once more.
8.You should be ready to use Viper4Android on your new S6 Edge or S6.
Best of luck!
* * * * * * * * * * * * * * * * * * * * * * * * * * * *
Alternative Installation Method - Flashable Zip
Goto the following to learn how: http://forum.xda-developers.com/showthread.php?p=60417795
* * * * * * * * * * * * * * * * * * * * * * * * * * * *
In case you've never played with Viper4Android or just wanted to try out my effects settings, I've linked them below. In my opinion this can dramatically improve the audio quality with the stock Samsung earplugs.
Effect Profile: S6 Edge 20150402.
NOTE: This is not a flashable zip, you extract the folder into the "/storage/emulated/0/ViPER4Android/Profile". Then use the "Load Effect Profile" from within Viper4Android to get them going. Keep in mind this is tuned to my liking, it may not be great for all... but it's a good base to start from.
Please post your results
This works. Had to install busybox as well though.
elsupermang said:
This works. Had to install busybox as well though.
Click to expand...
Click to collapse
I forgot to add that step.. updating op
Sweet. Can't wait to install this!
It didn't work for me, I did all the steps you listed, and installed busybox before even beginning. I've restarted multiple times, reinstalled Viper too. When I extracted the Viper4Android zip, there were two different apks, one that's 2.xx and one thats 4.xx.
idksomuch said:
It didn't work for me, I did all the steps you listed, and installed busybox before even beginning. I've restarted multiple times, reinstalled Viper too. When I extracted the Viper4Android zip, there were two different apks, one that's 2.xx and one thats 4.xx.
Click to expand...
Click to collapse
Use the APK called ViPER4Android_FX_A4.x.apk. I've attached the APK I'm using to th OP.
That's the one I used,no luck. was I supposed to extract the zip file somewher?
Edit: on second thought,that may be a different file. I'll give it a try after class, thanks
idksomuch said:
That's the one I used,no luck. was I supposed to extract the zip file somewher?
Edit: on second thought,that may be a different file. I'll give it a try after class, thanks
Click to expand...
Click to collapse
You sound like you are not taking the files out of the zip. You can't just place the entire zip file in the directory.
nappent said:
You sound like you are not taking the files out of the zip. You can't just place the entire zip file in the directory.
Click to expand...
Click to collapse
I couldn't get it to work, I placed the apk in priv-app and it wouldn't even install. The older apk you posted installs, after installing the app and installing drivers, it still doesn't work.
I have no idea why you can't get the APK to install. That makes no sense.
Installation worked first time....thanks. I changed permissions for each file after copying to proper place just as a failsafe. rw-r--r 0644
Also in priv_app I put the apk inside a folder named V4A. Name is irrelevant though.
idksomuch said:
I couldn't get it to work, I placed the apk in priv-app and it wouldn't even install. The older apk you posted installs, after installing the app and installing drivers, it still doesn't work.
Click to expand...
Click to collapse
Are you making sure to set the permissions to rw-r-r?
0dBu said:
Are you making sure to set the permissions to rw-r-r?
Click to expand...
Click to collapse
What exactly does rw-r-r mean? I understood pretty much every other step but that one.
Nvm. I think I got it and the drivers installed correctly. Thanks everyone!
Thanks! Getting Viper working for the Edge made my miss my SGS4 no more.
This mod alone is so worth going back to android for. This was my bread and butter when it came to listening to music. People that tried my headphones on couldn't believe how perfect the sound was. Can't wait to get my S6 Edge.
Sent from my soon to be my Galaxy S6 Edge
I can't get it to work. Says busybox is not installed when it is, I have rebooted and everything but viper does not want to install without busybox.
Any ideas?
What did you use to install busybox?
nappent said:
What did you use to install busybox?
Click to expand...
Click to collapse
The app from play store. I've used viper for the longest time and busy box never gave me an issue. Hmmm
nappent said:
Please post your results
Click to expand...
Click to collapse
How did you get busybox working? Viper4android doesn't recognize I have it installed.

[port]Ultra stamina mode

PHP:
/*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Hit thanks if work for u
After so many search on internet and xda developer i found a way for ultra stamina port
and its also have multi user
step 1-install both apk file as normal apks
step 2-then reboot to recovery and intall zip
Tadddaa ultra stamina mode and multi user in setting
tested and working on sony d5322
View attachment 3566179
View attachment 3566180
View attachment 3568188
hi...
I installed this. but having one doubt that after exiting ultra stamina mode phone is re-starting...Is this normal???
thank u.
bsvinod said:
hi...
I installed this. but having one doubt that after exiting ultra stamina mode phone is re-starting...Is this normal???
thank u.
Click to expand...
Click to collapse
Yes,because ultra stamina mode disabled all backgrounds application and many functions so after disabling ultra stamina mode phone restart..
User selection in lock screen
Unable to select user in lock screen, is there any way to add this???
bsvinod said:
Unable to select user in lock screen, is there any way to add this???
Click to expand...
Click to collapse
No for that we need system ui from Z1 or Z2 another which have multi user..but that didn't work on our phone..
What is boot to recovery means ?? How to do
If u don't have a recovery then u can also.. Replace the build.prop which I have in that zip or intall dual recovary from intaller zip and connect your phone with debugging on and give root permission
http://nut.xperia-files.com
In zip u will see intall.bat file click on that and press 1 then enter do what the say. You will boot into recovary
sarath1701 said:
What is boot to recovery means ?? How to do
Click to expand...
Click to collapse
If u don't have a recovery then u can also.. Replace the build.prop which I have in that zip or intall dual recovary from intaller zip and connect your phone with debugging on and give root permission
http://nut.xperia-files.com
In zip u will see intall.bat file click on that and press 1 then enter do what the say. You will boot into recovary

New build TWRP for only Realme Q support flash ozip

Hello . twrp only for realme Q stable
Link download : <Mod edit>
Link vbmeta support root , rom mod : <Mod edit>
Changelog
Modify the optimization project:
* Delete redundant languages, keep English, add Chinese language, default Chinese.
* Modify the default configuration, for example, the default time zone is East Eight Zone, default screen brightness, default vibration, default 24 hours, default return button on the right, default Chinese and so on.
* Modify the default configuration file path to reduce the possibility of conflicts with other people's compiled versions.
* Adjust and optimize the Chinese text and description, and re-edit all the items one by one to make it more accurate, understandable and humanized. Also added display mtp enable off display, file operation result display, operation page title display, permission description when modifying permissions, etc. UI text display.
* Modify the unlocking interface and adjust the height of the sliding unlocking bar, which can effectively prevent misoperation (the original unlocking bar and the operating unlocking bar are of the same height. When the unlocking is completed, the sliding may be repeated, and the corresponding action is directly operated).
* Open more partition backup and restore, such as modern baseband partition, bootloader, persist, cust and other partitions, easy to backup the underlying files before brushing, can restore the underlying files after brushing.
* Add .bin and .mbn format image files, so you don't need a zip brush package, you can write the underlying file. The original version only supports the brushing of .img format image files. (Be sure to pay attention to the right partition!!!!)
* Solve the problem of interface jam when using the simulation operation (the simulation operation is mainly for testing the theme, and no actual operation).
* Add the manual installation root function in Advanced Options > root system. Add a display root system option on this basis for manual operation.
* Added the ability to unenforce encryption, in advanced options > Unforce Encryption. You can remove the official system to force encryption and cancel the check.
* Change the built-in root mode and add magisk as the default root mode.
* Fixed button and button operations for some interfaces.
* The adb/usb debug mode is enabled by default, which is convenient for operating the phone through the computer command line in rec mode.
* MTP is enabled by default. In the rec state, you can also connect your phone to your computer to facilitate file copying.
* Modify the logo interface, modify the main interface page header, and add the display phone model and team name, author name.
* Fix some logical relationships and modify some interface displays.
* Added clear root function
* Added clear power-on password function
* Added ability to clear battery information
* Increase signature boot function
* Restore official rec function, need official boot and system system to operate successfully
* Increase the option of restarting after the automatic upgrade is completed. In the twrp setting, the default is automatic restart. If you uncheck the box, you can either not restart, and it is convenient to perform some operations after the automatic upgrade to prevent twrp from being overwritten.
* Increased avb2.0 verification function
important:
1. This rec supports data partition automatic decryption, encrypted data can be used normally under rec without formatting.
Please do not arbitrarily brush into the recue of unknown origin, it is likely that the data data can not be decrypted, and the data is completely lost.
The official default is to lock the password to encrypt the data. To enter twrp, you need to enter the lock screen password.
2. This rec supports the official original full-size ozip card brush package.
3. You must unlock the bootloader to brush the third-party rec. Please unlock the BL.
4. Built-in root system / remove root function, through the root system, can not only remove dm check, but also enable the system to obtain root privileges.
5. Built-in remove dm checksum and cancel the forced encryption function. Through certain operations, you can remove the official data forced encryption (the person who knows how to operate naturally).
6. Prevent the functions covered by the official rec (any one can be): root system, signature boot, remove dm check, cancel forced encryption, etc.
7. After the card is officially packaged, it is recommended to turn off the avb2.0 check, otherwise it may cause the boot prompt system damage due to root! ! !
8. If the boot prompt system is damaged due to root, etc., you can use the fastboot line to brush boot.img or brush the verification vbmeta to restore normal! ! !
Sounds good. Will I be able to flash lineage os, opengapps pico and latest magisk with this recovery? I don't want anything else complex.
---------- Post added at 06:13 ---------- Previous post was at 05:59 ----------
Says failed to mount /system_root (invalid agument) error: 7 while trying to flash anything from it.
Rom LG16 support only realme 5pro india...realme Q from china no support
29y6145 said:
Rom LG16 support only realme 5pro india...realme Q from china no support
Click to expand...
Click to collapse
Then why the hell is realme q in the title?
Btw after 10 minutes of showing decrypting ozip file I got an error, invalid argument.
29y6145 said:
Rom LG16 support only realme 5pro india...realme Q from china no support
Click to expand...
Click to collapse
what is the codename for Rm5P india? is it same like global (RMX1971EX)?
rah_asia said:
what is the codename for Rm5P india? is it same like global (RMX1971EX)?
Click to expand...
Click to collapse
Yes.
Contacted developer of this Chinese twrp and even he himself said that we shouldn't try to flash custom rom, magisk.zip or gapps package with it for it can't really flash anything else but stock rom and inbuilt magisk 20.0 that is embedded in twrp itself. So aside from rooting color os or installing stock rom in case of hard brick this twrp pretty much useless for custom rom development, testing, flashing or migrating.
greenys' said:
Contacted developer of this Chinese twrp and even he himself said that we shouldn't try to flash custom rom, magisk.zip or gapps package with it for it can't really flash anything else but stock rom and inbuilt magisk 20.0 that is embedded in twrp itself. So aside from rooting color os or installing stock rom in case of hard brick this twrp pretty much useless for custom rom development, testing, flashing or migrating.
Click to expand...
Click to collapse
So, is problem so difficult to overcome that developers can't build proper twrp?
555frost555 said:
So, is problem so difficult to overcome that developers can't build proper twrp?
Click to expand...
Click to collapse
No. The developers are just lazy and most of time they're not in the mood for it for they mostly own RM5P instead of RMQ. However, @thesprintster compiled a theoretically working twrp for our RMQ devices. We're waiting for him to release so we could test it. On the other hand seemingly even roms need a few lines of change so they'll work on Realme Q. It's a huge pain in the ass but it seems RM5P roms won't work on RMQ even with proper recovery these roms need to be changed, recompiled ?* So yeah. This sucks.
greenys' said:
No. The developers are just lazy and most of time they're not in the mood for it for they mostly own RM5P instead of RMQ. However, @thesprintster compiled a theoretically working twrp for our RMQ devices. We're waiting for him to release so we could test it. On the other hand seemingly even roms need a few lines of change so they'll work on Realme Q. It's a huge pain in the ass but it seems RM5P roms won't work on RMQ even with proper recovery these roms need to be changed, recompiled ?* So yeah. This sucks.
Click to expand...
Click to collapse
God, damn it!
Not for nothing that I bought RM5P
"...even roms need a few lines of change..." - it means that there are differences between RM5P and RMQ. What are they like?
555frost555 said:
God, damn it!
Not for nothing that I bought RM5P
"...even roms need a few lines of change..." - it means that there are differences between RM5P and RMQ. What are they like?
Click to expand...
Click to collapse
Dunno. I've never successfully compiled a working
... thing in the past 10 years even though I followed step by step tutorials so I gave up on compiling Android stuff. All I can do is to bug devs to do the work instead of me but I can do that relentlessly thus it bears fruit more or less often. Ask thesprintster about it. I'm bugging him to make that flashable lineage os soon and after that I'm done for good.
THREAD CLOSED!
@29y6145 Please consult the inbox of your private messages.

(Moto g fast rav) I bricked my device

So, I was trying to flash a custom ROM onto my moto g fast (product name rav), and it's bricked. I can't seem to flash really anything, is there a chance of saving this phone? Anything will help!
Ill try to help u but there a slight twist, do u have a pc? or lappy?
Icicle2413 said:
Ill try to help u but there a slight twist, do u have a pc? or lappy?
Click to expand...
Click to collapse
If u do have a computer, does it recognize your phone?
Icicle2413 said:
Ill try to help u but there a slight twist, do u have a pc? or lappy?
Click to expand...
Click to collapse
Laptop, on Windows 10 Home 1904
Icicle2413 said:
If u do have a computer, does it recognize your phone?
Click to expand...
Click to collapse
When I do fastboot devices it's detected
JN2002 said:
When I do fastboot devices it's detected
Click to expand...
Click to collapse
What does getvar all say
Code:
fastboot getvar all
JN2002 said:
Laptop, on Windows 10 Home 1904
Click to expand...
Click to collapse
good
JN2002 said:
When I do fastboot devices it's detected
Click to expand...
Click to collapse
also good
Code:
* Your warrenty is now void.
* I am not responsible for bricked devices, dead SD cards, thermonuclear war, or your getting fired because the alarm app failed.
* Please do some research if you have any concerns about features included in this ROM.
* before flashing it! YOU are choosing to make these modifications, and if you point the finger at us for messing up your device, I will laugh at you. VERY HARD!
Now follow me:
i-) Connect your device to your lappy, and download SDK Platform-Tools for Windows.
ii-) Go to where u downloaded platform-tools and unzip it. Open the folder.
iii-) Hold Shift and right-click anywhere in the folder, thee should be an option, namely "Open Powershell Window here" or maybe "Open command prompt window here", Its most likely youll get the second option (Open command prompt here). If u see neither. Then open the folder and click "File" in the top right corner. and youll see open either one of the above options.
iv-) Make sure u have connected your device to your lappy, In powershell or cmd and type
adb devices
v-) u should see your device, now reboot to fastboot mode and then type
fastboot devices
. After u see ur device, download twrp-recovery_moto-g8_moto_g_fast.img (Alternate link here)
vi-) Go to the folder where u downloaded the file, next type:
fastboot flash twrp-recovery_moto-g8_moto_g_fast.img
vii-)boot into recovery by pressing and holding the volume down + power button at the same time(when the phone is powered off, obviously).
viii-) This step is crucial!! Click on Settings / File Manager and navigate where u downloaded the lineage-18.1-moto-g8-moto-g-fast-rav-20210222.zip and move it to "/" also called ROOT folder.
Very Important!
Take a complete backup of the phone because the next steps will LITERALLY delete EVERYTHING in your phone INCLUDING the SYSTEM!!​
I think this post is becomig a bit too big so ill post the next part after posting this post.
Icicle2413 said:
Code:
* Your warrenty is now void.
* I am not responsible for bricked devices, dead SD cards, thermonuclear war, or your getting fired because the alarm app failed.
* Please do some research if you have any concerns about features included in this ROM.
* before flashing it! YOU are choosing to make these modifications, and if you point the finger at us for messing up your device, I will laugh at you. VERY HARD!
Now follow me:
i-) Connect your device to your lappy, and download SDK Platform-Tools for Windows.
ii-) Go to where u downloaded platform-tools and unzip it. Open the folder.
iii-) Hold Shift and right anywhere in the folder, thee should be an option, namely "Open Powershell Window here" or maybe "Open command prompt window here", Its most likely youll get the second option (Open command prompt here). If u see neither. Then open the folder and click "File" in the top right corner. and youll see open either one of the above options.
iv-) Make sure u have connected your device to your lappy, In powershell or cmd and type
adb devices
v-) u should see your device, if not, reboot to fastboot mode and then type
fastboot devices
. After u see ur device, download twrp-recovery_moto-g8_moto_g_fast.img (Alternate link here)
vi-) Go to the folder where u downloaded the file, next type:
fastboot flash twrp-recovery_moto-g8_moto_g_fast.img
vii-)boot into recovery by pressing and holding the volume down + power button at the same time(when the phone is powered off, obviously).
viii-) This step is crucial!! Click on Settings / File Manager and navigate where u downloaded the rom.zip and move it to "/" also called ROOT folder.
Very Important!
Take a complete backup of the phone because the next steps will LITERALLY delete EVERYTHING in your phone INCLUDING the SYSTEM!!​
I think this post is becomig a bit too big so ill post the next part after posting this post.
Click to expand...
Click to collapse
ill post the next tomorrow im going to bed.
Icicle2413 said:
ill post the next tomorrow im going to bed.
Click to expand...
Click to collapse
ix-) Now Select Wipe / Advanced Wipe and select everything and swipe to wipe. Then again go to Wipe / format data and type "yes" without the quotes.
x-) Next Tap Install / (Go to root folder) rom.zip and swipe to install.
DONE!!!!!!!!!!!!!!!!!!!!!
JN2002 said:
So, I was trying to flash a custom ROM onto my moto g fast (product name rav), and it's bricked. I can't seem to flash really anything, is there a chance of saving this phone? Anything will help!
Click to expand...
Click to collapse
I bricked my Moto G Fast by trying to flash RetUS firmware without unlocking the bootloader first. Attempts to flash Boost official firmware didn't work.
What did work for me was installing the Lenovo Motorola Rescue and Smart Assistant app on my PC. Even that failed the first couple times I tried it. I think the third or fourth attempt it finally succeeded.
Rescue and Smart Assistant Tool - Motorola
<h6><span style="color:#FFFFFF"><strong>Our Rescue and Smart Assistant tool</strong><br />can help diagnose and resolve issues on your<br />Motorola phone or Lenovo phone/tablet.</span></h6>
www.motorola.com
Did you THEN unlock the bootloader? heh
Icicle2413 said:
Code:
* Your warrenty is now void.
* I am not responsible for bricked devices, dead SD cards, thermonuclear war, or your getting fired because the alarm app failed.
* Please do some research if you have any concerns about features included in this ROM.
* before flashing it! YOU are choosing to make these modifications, and if you point the finger at us for messing up your device, I will laugh at you. VERY HARD!
Now follow me:
i-) Connect your device to your lappy, and download SDK Platform-Tools for Windows.
ii-) Go to where u downloaded platform-tools and unzip it. Open the folder.
iii-) Hold Shift and right-click anywhere in the folder, thee should be an option, namely "Open Powershell Window here" or maybe "Open command prompt window here", Its most likely youll get the second option (Open command prompt here). If u see neither. Then open the folder and click "File" in the top right corner. and youll see open either one of the above options.
iv-) Make sure u have connected your device to your lappy, In powershell or cmd and type
adb devices
v-) u should see your device, now reboot to fastboot mode and then type
fastboot devices
. After u see ur device, download twrp-recovery_moto-g8_moto_g_fast.img (Alternate link here)
vi-) Go to the folder where u downloaded the file, next type:
fastboot flash twrp-recovery_moto-g8_moto_g_fast.img
vii-)boot into recovery by pressing and holding the volume down + power button at the same time(when the phone is powered off, obviously).
viii-) This step is crucial!! Click on Settings / File Manager and navigate where u downloaded the lineage-18.1-moto-g8-moto-g-fast-rav-20210222.zip and move it to "/" also called ROOT folder.
Very Important!
Take a complete backup of the phone because the next steps will LITERALLY delete EVERYTHING in your phone INCLUDING the SYSTEM!!​
I think this post is becomig a bit too big so ill post the next part after posting this post.
Click to expand...
Click to collapse
you know what to do when device recognize on pc on usb but don't go anywhere?. My device recognize on pc but when i will run the blank flash to open the fastboot it don't run the fastboot screen and continues black. The process that i trying to do is connect the phone on pc and turn it on by the connectors on the motherboard, after that theoretically i have to put it in fastboot with blankflash and install the rom by the qualcom driver but it stops on the blankflash part. It's like my phone don't have the fastboot anymore.

How To Guide Enable 5G NSA on OOS 11 and OOS 11 based Custom ROMs.

Hi there!
OnePlus didn't enable/add 5G in the modem's Carrier Policy files. This is a quick guide on how to enable it.
This guide will work on both OnePlus 9 and OnePlus 9 Pro devices.
Requirements
Root (Magisk)
QPST
Qualcomm drivers installed (EDL ones should do)
Attached .zip file.
USB Cable, of course.
Code:
/*
* Your warranty is now maybe void.
*
* I am not responsible for bricked devices, dead SD cards, thermonuclear
* war, or you getting fired because the alarm app failed. Please do some
* research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*
*/
Got all the things required? Now let's go ahead.
Steps -
1. Root your phone running on OOS 11.
2. Enable USB Debugging
3. Connect your device to your PC in MTP mode and execute the following through cmd
Code:
adb shell
su
setprop sys.usb.config diag,diag_mdm,qdss,qdss_mdm,serial_cdev,dpl,rmnet,adb
4. Now open Device Manager to see the connected device. It would be recognized as Unknown if not configured in the past.
5. Right click on the device, select Update Driver -> browse my computer drivers -> Let me pick form a list of available drivers -> click on Have Disk -> show all devices browse then go to the Qualcomm Drivers that you downloaded earlier. Then do the same to the other unknown Driver (if exists). Choose 9018 for both unknown drivers.
6. Open the QPST application. Click on Add new port from the right corner. if it shows 2 add them both. (Skip this step if you already see the ports).
7. Open QPST EFS Explorer and select your device. You should now be able to see your device files.
8. Search for policyman/ directory and enter it.
9. Extract the files in the attached zip. Drag and drop all the files inside the zip to the already open policyman/ directory in QPST EFS Explorer.
10. Overwrite all the files and copy them.
11. Reboot your device
12. Dial *#*#4636#*#*. Select Phone Information -> Set Preferred Network -> Choose NR/LTE/TDSCDMA/CDMA/EvDo/GSM/WCDMA.
PS :- You might need to select preferred network on every reboot in OOS11.
This guide will also work with Custom ROMs. Assuming the Custom ROM already has 5G enabled in the Carrierconfig (Like AOSPA), you can skip step 12 and 13.
These files in policyman/ directory have been taken from OOS 13 (F.20) modem.
Please don't bite on me if this guide doesn't work. I tried it personally on my local carrier in India (Airtel), it is working fine. (AOSPA and also OOS 11).
Cheers if this works for you as well!
Like my work? Buy me a coffee
PayPal
Thank you very much! Will test ASAP.
EDIT: Does anyone know why my device does not show up in Device Manager after setprop in adb shell? Any fix for that?

Categories

Resources