Ok, I stumbled upon this but here it is and I provide no warranty for any of this. You do this at your own risk!:
Requirement: Bootloader unlocked, Rooted, BACKED UP PERSIST.
Following this guide: https://www.xda-developers.com/enable-google-stadia-any-android-smartphone/
Open MagiskManager and look for the MagiskHide Props Config module.
Install and reboot
Get to ADB or term and type:
Code:
props
Type “4” to add/edit custom props.
Type “5” to add/edit custom props.
Type “n” to add a new custom prop.
Type “ro.product.model” to set this prop.
Type “in2025” to set it as the value for “ro.product.model“ (or your proper region)
Type “y” to accept the prop change.
Type “y” to accept the reboot.
You should now have photochrom!
{
"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"
}
Confirmed working on IN2020 on 10.5.10IN11AA
Confirmed too on my IN2020, this is great (Art)work, kevkid, thanks!
Just one small thing; I had to clear camera's cache and storage data to finally have photochrom option appear. Without this final step, it wouldn't. Seems obvious but maybe not for everyone, so you may want to add it as a final step in your instructions maybe.
Also had to use an adb terminal emulator Android app, and not computer's adb terminal, to have access to the props through that module and be able to edit them.
Wish there was such an easy way to get back to Widevine-L1 after bootloader's unlocked...
Works without any issue
I am on IN2021 model with Oxygen OS 10.5.10 IN11DA and its working.
This worked on my IN2020 running OOS 10.5.10 IN11AA. Thanks!
Exactly what I needed! Thanks!
sd2019 said:
This worked on my IN2020 running OOS 10.5.10 IN11AA. Thanks!
Click to expand...
Click to collapse
Not possible
---------- Post added at 06:34 PM ---------- Previous post was at 05:49 PM ----------
[/COLOR]
Tarun143007 said:
I am on IN2021 model with Oxygen OS 10.5.10 IN11DA and its working.
Click to expand...
Click to collapse
Good
DrStrange00 said:
Not possible
Click to expand...
Click to collapse
Why not?
Anyways to enable it in non rooted devices?
Maddyboy22 said:
Anyways to enable it in non rooted devices?
Click to expand...
Click to collapse
Not as far as I know, but I haven't really looked into it
Thanks. worked perfectly in Indian Version.
But how to disable it. Already tried to enter the IN2021, but still it shows 2025
kevkid said:
Why not?
Click to expand...
Click to collapse
It will be temporary, till the device is kept rooted?
kevkid said:
Not as far as I know, but I haven't really looked into it
Click to expand...
Click to collapse
Why can't a third party software enable it?
Maddyboy22 said:
Why can't a third party software enable it?
Click to expand...
Click to collapse
I'm not sure I understand the question
DrStrange00 said:
It will be temporary, till the device is kept rooted?
Click to expand...
Click to collapse
I assume so, but I haven't tested it
Maddyboy22 said:
Why can't a third party software enable it?
Click to expand...
Click to collapse
Idk? Someone wrote a magisk module using this method
To undo the camera changes and change back the model no back to default. Try this
Get to ADB or term and type:
Code:
props
Type “4” to add/edit custom props.
Type “1” to select the ro.product.model prop.
Type “r” to reset custom prop.
Type “y” to accept the prop change.
Type “y” to accept the reboot.
Must root
sd2019 said:
This worked on my IN2020 running OOS 10.5.10 IN11AA. Thanks!
Click to expand...
Click to collapse
How did you root this device with this os version?
ranjib said:
How did you root this device with this os version?
Click to expand...
Click to collapse
I followed this thread https://forum.xda-developers.com/oneplus-8-pro/how-to/guide-how-to-root-oneplus-8-pro-twrp-t4083981
I also followed this YouTube video
Related
http://forum.xda-developers.com/honor-6/general/guide-workaround-running-xposed-t3338765
Thread above. Im probably gonna try it later
{
"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"
}
Sent from my KIW-L21 using Tapatalk
Faheemarif252 said:
HUGE IMG
Click to expand...
Click to collapse
Use a web browser, if u getting that message when tryna click the link
Kennii said:
Use a web browser, if u getting that message when tryna click the link
Click to expand...
Click to collapse
It opened fine.... And the method should work just fine.... Yielding no problems whatsover... Do give it a try and tell us your findings...
Ps. I wouldve tried but I'm still waiting for my unlock code
Sent from my KIW-L21 using Tapatalk
Trying this now. Just to be certain this is an ARM64 device? Can't find any info on this other than somone using 64-bit G-apps.
EDIT: Didn't work for me Using stock rom. KIW-L21
Jammo2k5 said:
Trying this now. Just to be certain this is an ARM64 device? Can't find any info on this other than somone using 64-bit G-apps.
Click to expand...
Click to collapse
Yes ARM64, and xposed work's very well
flecky22 said:
Yes ARM64, and xposed work's very well
Click to expand...
Click to collapse
Hmmm How long did it take to boot after you flashed the xposed zip?
about 5/10 minutes
flecky22 said:
about 5/10 minutes
Click to expand...
Click to collapse
Damn i din't leave it that long. Will redo now
flecky22 said:
Yes ARM64, and xposed work's very well
Click to expand...
Click to collapse
So this does work? What model do you have? Can anyone confirm it's working on l24? I've been hoping to get xposed until we get some custom rom action!
wickedesires said:
So this does work? What model do you have? Can anyone confirm it's working on l24? I've been hoping to get xposed until we get some custom rom action!
Click to expand...
Click to collapse
Yes it's work, i have a L21.
flecky22 said:
Yes it's work, i have a L21.
Click to expand...
Click to collapse
Sweet! Gonna try this in a bit. Thanks for confirmation. Any performance issues so far?
No, for me it works as before
Yeah i have another issue now... It says it's installed but not activated :/
"For Android 6.0pen build.prop and add these lines ro.config.hwtheme=0 and ro.config.hw_theme=0
For Android 5.0-5.1.1: Open local.prop (in system/emui/base/prop/local.prop) and add these lines ro.config.hwtheme=0 and ro.config.hw_theme=0
Again reboot your device (this boot won't take long)."
In honor 5x local.prop (in cust/hw/eu/prop)
flecky22 said:
"For Android 6.0pen build.prop and add these lines ro.config.hwtheme=0 and ro.config.hw_theme=0
For Android 5.0-5.1.1: Open local.prop (in system/emui/base/prop/local.prop) and add these lines ro.config.hwtheme=0 and ro.config.hw_theme=0
Again reboot your device (this boot won't take long)."
In honor 5x local.prop (in cust/hw/eu/prop)
Click to expand...
Click to collapse
Yeah i missed that bit. A combination of being a bit of an idiot, tiredness and nagging girlfriend.
Jammo2k5 said:
Yeah i missed that bit. A combination of being a bit of an idiot, tiredness and nagging girlfriend.
Click to expand...
Click to collapse
lol
Arobase40 said:
How long did it take after the first boot (after app, framework and Priv-app copying) and did you have any messages saying "optimizing apps" or such ?
It's being said to wait about 20-30 mn and I'm waiting for almost 1 hour at the Honor Logo... ^^
Click to expand...
Click to collapse
5/10 minutes and yes i have a message like optimizing apps
Test in build.prop or deactivates resource hooks in xposed settings, but then if you want to use gravity box for example, it will not work, build.prop change is the best solution.
---------- Post added at 10:56 PM ---------- Previous post was at 10:47 PM ----------
build.prop change is enough , I just tried , no need to change local.prop .
Arobase40 said:
Hmmm, damn it !
Don't understand why it was not working the first time...
Now, I got everything installed but I couldn't modify the /cust/hw/eu/prop/local.prop file !!!
I'm in R/W, but every time I modify the file, I loose the changes when I leave it and so the Xposed framework can't activate... ^^
Click to expand...
Click to collapse
I used es file explorer (an older version) to edit the local.prop and I had to select the root of the SD card to get it to save correctly (I have absolutely no idea why lol). After that everything worked great.
Hey,
I experimented a bit and found 2 ways to reuse the Photochrome filter.
{
"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"
}
[ROOT]
1. Download the Magisk Module from the Attachment.
2. Install the Module using Magisk Manager.
3. Reboot.
4. Open Phone App and type *#808#
5. Go to the Camera tab and click to "fourth back camera preview".
6. Now you can screenshot objects.
Screens:
[NON-ROOT]
1. Download this Package: Download
2. Open the zip and install the "GoogleCamera.apk"
3. Copy the "GCam" folder on the internal memory.
4. Open GCam and Restore the "Urnyx 7.3 Hooolm v8 (OP8 Pro).xml" Profile.
5. Now you can click on the "C" logo and can use the Photochrome filter again.
Screen:
Does the non-root variant work without Magisk? Because you can't change the cameras if you don't use the Aux Magisk Module that patches SELinux.
Works without Module
The AUX module is only needed for some GCam features like slow motion etc.
But for the Photochrome filter the module is not needed.
Interesting. The other cams only work with the Aux module on the 7 series. Good to know
Np
Followed the steps for non-root. Anytime I try to use a camera other than the main it kills the app and I have to clear data and start over again to make it turn on.
geomez said:
Followed the steps for non-root. Anytime I try to use a camera other than the main it kills the app and I have to clear data and start over again to make it turn on.
Click to expand...
Click to collapse
It's about the filter there.
If you want to use everything else, you need the AUX module, but you need root.
It's about the filter there.
If you want to use everything else, you need the AUX module, but you need root.
Click to expand...
Click to collapse
That's the thing, the color filter button shuts it down just the same
jamal2367 said:
It's about the filter there.
If you want to use everything else, you need the AUX module, but you need root.
Click to expand...
Click to collapse
I might be dumb, so please bear with me. I tried *#808# without the module and the same screen popped up. Is there something I'm missing that this module does that I don't see?
Deinstall all FactoryMode updates in Settings and install the Module then you can access *#808#
jamal2367 said:
Deinstall all FactoryMode updates in Settings and install the Module then you can access *#808#
Click to expand...
Click to collapse
I meant I can already access it, sorry for the misunderstanding. I get the camera tab and can select the stuff an all, without installing the module, so wanted to know if I missed something. Sorry.
I guess I misunderstood.
So all is well
Warning!!!
I install the FactoryMode module
Don't play with the fingerprint sensor tests or you will lose it. And without your own backup of the persist.img, there is nothing you can do to recover it. Fortunately I had my backup and I was able to recover the sensor. @jamal2367, can you take a look?
geomez said:
That's the thing, the color filter button shuts it down just the same
Click to expand...
Click to collapse
Same for me i cant Access the color Filter without crashing the camera App.. ist there anybody where this works? (Non root Variant)
blackst225 said:
Same for me i cant Access the color Filter without crashing the camera App.. ist there anybody where this works? (Non root Variant)
Click to expand...
Click to collapse
same，，crash every time
jamal2367 said:
Deinstall all FactoryMode updates in Settings and install the Module then you can access *#808#
Click to expand...
Click to collapse
Sir
How to deinstall?
Not working non root method camra crashing
Thank you but Not working non root method camra crashing
Sent from my IN2020 using Tapatalk
Hello, I'm going to receive my OnePlus 8 Pro this week (sadly, i've seen it's the in2020 version), if I flash OOS instead of HOS, is this guide needed or will it works natively on OOS ?
Does is work on OP8?
I get a tiny message that says
Code:
the serial is not match
fastboot_unlock_verify ok
And the phone doesn't show up in fastboot devices.
Would really appreciate some help!
{
"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"
}
install drivers
23Aaron said:
I get a tiny message that says
Code:
the serial is not match
fastboot_unlock_verify ok
And the phone doesn't show up in fastboot devices.
Would really appreciate some help!View attachment 5376939
Click to expand...
Click to collapse
Hey mate I also get this, how did you fix it?
mlgmxyysd said:
install drivers
Click to expand...
Click to collapse
I am using a mac and am able to see the phone using 'adb devices'. I do not have Advanced Reboot in dev options, and trying to get to fastboot with 'adb reboot bootloader' gets the same screen as OP. Could not find drivers when I looked, I am unsure what to look for.
Any suggestions?
23Aaron said:
私は言う小さなメッセージを受け取ります
[コード]シリアルが一致しません
fastboot_unlock_verify ok [/ CODE]
また、電話はfastbootデバイスに表示されません。
本当に助けていただければ幸いです！View attachment 5376939
Click to expand...
Click to collapse
私は同じ状態です。再起動できません。助けて。
moisthat said:
Hey mate I also get this, how did you fix it?
Click to expand...
Click to collapse
I still haven’t been able to fix it
23Aaron said:
I still haven’t been able to fix it
Click to expand...
Click to collapse
Do you also have Advanced Reboot missing from Developer Options?
23Aaron said:
I still haven’t been able to fix it
Click to expand...
Click to collapse
Turns out this is the correct screen, and you can just unlock the bootloader from here!
moisthat said:
Turns out this is the correct screen, and you can just unlock the bootloader from here!
Click to expand...
Click to collapse
Kindly tell me how to proceed after mentioned screen. As I cannot do anything further ,
garapaboy said:
Kindly tell me how to proceed after mentioned screen. As I cannot do anything further ,
Click to expand...
Click to collapse
fastboot flashing unlock
Has anyone been able to unlock the bootloader?
Eastw1ng said:
Has anyone been able to unlock the bootloader?
Click to expand...
Click to collapse
Yes, sure
juergenh99 said:
Yes, sure
Click to expand...
Click to collapse
Yeah a pretty useless reply. I got it to work, some extra info here: https://forum.xda-developers.com/t/unlocking-the-bootloader.4327217/
Eastw1ng said:
Yeah a pretty useless reply. I got it to work, some extra info here: https://forum.xda-developers.com/t/unlocking-the-bootloader.4327217/
Click to expand...
Click to collapse
your question and that post is pretty useless - whats your problem? you asked and got an answer - you didn't ask for a step by step guide or whatsoever.
moisthat said:
fastboot flashing unlock
Click to expand...
Click to collapse
step by step guide?
Overlay uses with all GSI
...and what does this solve? What is the purpose of this? I don't see this answered in the first post.
nirogu325 said:
...and what does this solve? What is the purpose of this? I don't see this answered in the first post.
Click to expand...
Click to collapse
Fixed
tom.android said:
Fixed
Click to expand...
Click to collapse
That's actually great info. How do I get the SM-T220 files so I can do the same for the T220?
nirogu325 said:
That's actually great info. How do I get the SM-T220 files so I can do the same for the T220?
Click to expand...
Click to collapse
Extract from stock ( system.img) AP file
Copy to linux
(/system/framework/framework-res.apk )
tom.android said:
Extract from stock ( system.img) AP file
Copy to linux
(/system/framework/framework-res.apk )
Click to expand...
Click to collapse
Attached is the T220's framework extracted from the AVE1 firmware. The rest of the instructions are...kinda advanced for me. Although the only difference between the T220 and T225 is SIM card capabilities so perhaps your file also works for the T220. I shall test in a moment.
Edit: Tested your file and my T220 does not boot.
Edit #2: Also uploaded the vendor file called framework-res__auto_generated_rro_vendor.
nirogu325 said:
Attached is the T220's framework extracted from the AVE1 firmware. The rest of the instructions are...kinda advanced for me. Although the only difference between the T220 and T225 is SIM card capabilities so perhaps your file also works for the T220. I shall test in a moment.
Edit: Tested your file and my T220 does not boot.
Edit #2: Also uploaded the vendor file called framework-res__auto_generated_rro_vendor.
Click to expand...
Click to collapse
Will try to patch your framework.
tom.android said:
Will try to patch your framework.
Click to expand...
Click to collapse
I managed to compile one but the ROM gets stuck at the boot screen. I'm using CherishOS, one that says secure. Maybe that's why it bootloops when something is modified?
nirogu325 said:
I managed to compile one but the ROM gets stuck at the boot screen. I'm using CherishOS, one that says secure. Maybe that's why it bootloops when something is modified?
Click to expand...
Click to collapse
Try
CherishOS_v415-arm64-bgS-lite_20220816.img.xz
1.16GB
tom.android said:
Try
CherishOS_v415-arm64-bgS-lite_20220816.img.xz
1.16GB
Click to expand...
Click to collapse
I'm on
CherishOS_v415-arm64-bgS_20220816.img.xz
1.21GB
But not yet success (autobringthness slide shown up with not auto adjustment ).
tom.android said:
Try
CherishOS_v415-arm64-bgS-lite_20220816.img.xz
1.16GB
Click to expand...
Click to collapse
Yes, that's the one I've just flashed and same result. ROM does not finish booting.
nirogu325 said:
Yes, that's the one I've just flashed and same result. ROM does not finish booting.
Click to expand...
Click to collapse
Oh forgot to tell you , can't changes framework
{
"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"
}
tom.android said:
Oh forgot to tell you , can't changes framework
Click to expand...
Click to collapse
I see. Well, I tried. Right now I'm modifying a script to remove the file cuz I don't want to reflash the ROM.
Howto easy create home shotcut.
MOVE ICON TO HOMESCREEN from App Drawer.
2.1 Disable locked layout
2.2 Enable Suggestion on Home screen
Delete
Auto ScreenBrightness working now. @niroku325
Tested your new file on my T220 and can confirm Auto Brightness is now working!
Could you do them for 225N
Attached framework res ,
Thanks for doing or not doing(thanks your old posts)
Civil123y said:
Could you do them for 225N
Attached framework res ,
Thanks for doing or not doing(thanks your old posts)
Click to expand...
Click to collapse
On your device, in adb or Termux app use this command: getprop ro.vendor.build.fingerprint
and tell me
tom.android said:
On your device, in adb or Termux app use this command: getprop ro.vendor.build.fingerprint
and tell me
Click to expand...
Click to collapse
I was about to ask you about the fingerprint you used for the T220 files. For the A12 file, did you use the following one?
Code:
ro.system.build.fingerprint=samsung/gta7litewifixx/gta7litewifi:12/SP1A.210812.016/T220XXU1BVGB:user/release-keys
I'm pretty sure I got my OnePlus 10T fixed to 120fps
adb shell settings put secure oplus_customize_screen_refresh_rate 3
adb shell settings put secure oplus_customize_min_refresh_rate 1
adb shell settings put secure oplus_customize_peak_refresh_rate 1
Thanks for sharing bro, is it for rooted only?
Von192 said:
Thanks for sharing bro, is it for rooted only?
Click to expand...
Click to collapse
No seems to work with allow_hidden_apis
I just tried it on my phone, Chrome is still locked at 90 fps
It doesn't work on lock bl and unroot.
{
"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"
}
Von192 said:
It doesn't work on lock bl and unroot.
View attachment 5806451
Click to expand...
Click to collapse
Show me the commands you're using and did you turn on hidden API?
AkayamiShurui said:
Show me the commands you're using and did you turn on hidden API?
Click to expand...
Click to collapse
I just type in the command you posted. How to turn on hidden API?
Von192 said:
I just type in the command you posted. How to turn on hidden API?
Click to expand...
Click to collapse
So you should add my discord I got a lot of tips that could help you
AkayamiShurui said:
So you should add my discord I got a lot of tips that could help you
Click to expand...
Click to collapse
What is your discord?
Von192 said:
I just type in the command you posted. How to turn on hidden API?
Click to expand...
Click to collapse
adb shell settings put global hidden_api_policy 1
Von192 said:
What is your discord?
Click to expand...
Click to collapse
Senna#3702
AkayamiShurui said:
adb shell settings put global hidden_api_policy 1
Click to expand...
Click to collapse
Still the same error.
I managed to enter all the command without error, but the refresh rate remains the same.
Von192 said:
I managed to enter all the command without error, but the refresh rate remains the same.
Click to expand...
Click to collapse
Which app isn't changing
AkayamiShurui said:
Which app isn't changing
Click to expand...
Click to collapse
And also do you have color OS on your background when you go to about phone or does it say oxygen OS cuz if it's colorless you have to do color OS instead of oplus
AkayamiShurui said:
I'm pretty sure I got my OnePlus 10T fixed to 120fps
adb shell settings put secure oplus_customize_screen_refresh_rate 3
adb shell settings put secure oplus_customize_min_refresh_rate 1
adb shell settings put secure oplus_customize_peak_refresh_rate 1
Click to expand...
Click to collapse
So I have to comment on this and say that doesn't work it seemed like it but after playing around with my system settings via command line I can save the last 4 days as far as gaming goes I do get 120 FPS but I can't stop it from auto switching on other apps but it no longer switches the peak refresh rate on its own anymore It's always on 120 it's just certain apps still don't switch which from all my research is a qualcomm thing