Database Develop

[HOW TO] Rooting the LT25i without unlocking the bootloader (4.0.4)

Rooting the Xperia V: How-To.
(XDA member datagubben requested that I post this here, as per http://forum.xda-developers.com/showpost.php?p=36753824&postcount=19)
Mirrors for the files provided are welcome.
This root method is courtesy of Xperia-Freaks.org, originally developed for the Xperia AX, translated and adapted by me for the LT25i.
Supported firmware: 9.0.1.D.0.10, probably also 9.0.D.0.484.
Reportedly does not work with 9.1.A.0.489.
You will need: TRIMMED-LT25i-SOL21_9.0.F.0.195.ftf (direct link: TRIMMED-LT25i-SOL21_9.0.F.0.195.ftf) or the original LT25i-SOL21_9.0.F.0.195.ftf (this FTF has its loader.sin replaced with LT25i's loader.sin; the trimmed version lacks unneeded files like baseband etc. and as such removes unneeded wipe/exclude options, leaving only the three files we actually need) and an LT25i FTF of your choice; the rootkit (this one is "translated" and edited for convenience; do NOT use regular GX/SX rootkits blindly as they require modification).
Make a backup using the stock Backup and Restore app in case something goes wrong so you can perform a factory reset.
Once rooted, you can safely restore from that backup.
1. Power the phone up in Flashmode (hold Volume down; connect USB). Using Flashtool, flash TRIMMED-LT25i-SOL21_9.0.F.0.195.ftf (or the untrimmed version if you like fiddling with excess checkboxes) using:
kernel.sin
loader.sin
system.sin
(Remember to uncheck the wipe options!)
2. Unplug USB. Turn the phone on. Enable USB debugging if it wasn't enabled previously. Connect the phone via USB again.
3. Unpack the Rootkit and start it (run install.bat). Confirm restore of the backup as requested, and press any key in the cmd window. Press any key again; the device will reboot (twice).
4. Run adb shell. To do it, you can open the rootkit folder in Windows Explorer, and shift-Right Click the "files" folder inside it. Choose "Open command window here". Type "adb shell" in that window.
If you're presented with a prompt that ends with "$", type "su".
The prompt should end with "#" now.
Type "echo ro.kernel.qemu=1 > /data/local.prop" and check if the file was created successfully by typing "ls -l /data/local.prop": below you will find an example of what the output looks like.
Code:
C:\Software\Rootkit\files\> adb shell
[email protected]:/ $ su
su
[email protected]:/ # echo ro.kernel.qemu=1 > /data/local.prop
echo ro.kernel.qemu=1 > /data/local.prop
[email protected]:/ # ls -l /data/local.prop
ls -l /data/local.prop
-rw-r--r-- system system 17 2013-01-15 17:29 local.prop
[email protected]:/ #
5. Turn the phone off, and connect it in Flashmode again. Using Flashtool, flash your firmware of choice with:
loader.sin
system.sin
(Remember to uncheck the wipe options!)
6. Turn the phone on. Open a command prompt into the files subfolder of the rootkit folder, like in step 4, or return to that window if you haven't closed it.
Type "adb shell". If you get a $ prompt, try "su" to get to "#". Once in adb, type "/data/local/tmp/step2.sh", then "reboot". The phone will reboot.
When it boots back, run adb shell again, and type "/data/local/tmp/step3.sh". You'll witness another reboot or maybe two. You should be rooted now.
Code:
C:\Software\Rootkit\files\> adb shell
[email protected]:/ # /data/local/tmp/step2.sh
/data/local/tmp/step2.sh
0+1 records in
0+1 records out
57 bytes transferred in 0.001 secs (57000 bytes/sec)
[email protected]:/ # reboot
C:\Software\Rootkit\files\> adb shell
[email protected]:/ # data/local/tmp/step3.sh
data/local/tmp/step3.sh
43+1 records in
43+1 records out
22364 bytes transferred in 0.002 secs (11182000 bytes/sec)
1647+1 records in
1647+1 records out
843503 bytes transferred in 0.123 secs (6857747 bytes/sec)
2119+1 records in
2119+1 records out
1085140 bytes transferred in 0.089 secs (12192584 bytes/sec)
7. Turn the phone off, and connect it in Flashmode again. Using Flashtool, flash your firmware of choice with:
kernel.sin
loader.sin
(Remember to uncheck the wipe options!)
Do NOT skip this step: you need the LT25i kernel on your LT25i system!
8. Let's finish.
We will need adb shell once again. This time, you will need to type a few lines as follows:
Obtain root:
su
Remount /system:
mount -o remount,rw -t ext4 /dev/block/mmcblk0p12 /system
Remove /data/local.prop since it's a security hole; this is important and is normally done by the rootkit's step 3, but we needed to save the file to get to keep root access on our LT25i firmware:
rm /data/local.prop
And finally reboot:
reboot
Code:
G:\Android\LT25i\rootkitGXSX_v3\files>adb shell
[email protected]:/ $ su
su
[email protected]:/ # mount -o remount,rw -t ext4 /dev/block/mmcblk0p12 /system
mount -o remount,rw -t ext4 /dev/block/mmcblk0p12 /system
[email protected]:/ # rm /data/local.prop
rm /data/local.prop
[email protected]:/ # reboot
reboot
Done. You now have busybox, Superuser and su on your stock LT25i firmware.
Remember to clean up those pesky au apps.

Will link to the all in one. Many thanks

Good job translating!
Sent from your backyard...
Slender watches what you do...

I did some n00b experiments:
First I flash kernel.sin-, system.sin and loader.sin from above VL-firmware(Japan), then Bin4ary for root (OK) and back to V-kernel with system.sin again, but I lost root ofcourse :crying:
anyway, the first post is working but I get reboots when deleting something from system/apps/. Any fix?

datagubben said:
First I flash kernel.sin-, system.sin and loader.sin from above VL-firmware(Japan), then Bin4ary for root (OK) and back to V-kernel with system.sin again, but I lost root ofcourse
anyway, the first post is working but I get reboots when deleting something from system/apps/. Any fix?
Click to expand...
Click to collapse
Using the Bin4ry approach should be possible since as far as I know it's the exact same backup/restore timing exploit, you probably need to recreate /data/local.prop though before flashing the V's system.sin. Or do you mean reducing the number of flashing operations to 2? That won't work, we need to regain root on V's system to get it to enable adb root shell with the V's kernel.
If you delete something from /system/app and the phone starts rebooting, it means you just deleted a part of the Timescape framework, I'd presume?

This method will clean up my installed app?

Dude i'm step 6 but I keep getting this prompt.
C:\Users\user\Documents\Development\Xperia\Xperia V\rootkit-sony\files>adb shell
[email protected]:/ $ su
su
/system/bin/sh: su: not found
127|[email protected]:/ $
edit: now do i panic?

Aaron_035, this means you did not obtain root during previous steps.
Did you verify that /data/local.prop was successfully created during step 4?

Gasai Yuno said:
Aaron_035, this means you did not obtain root during previous steps.
Did you verify that /data/local.prop was successfully created during step 4?
Click to expand...
Click to collapse
Found my mistake, I'm going to try again Fifth time!
Edit: Done! Love you dude.

All I want is just to root the phone. Why is this flash some japanese firmware to my phone!
Yes I am a n00b.

sunny7day said:
All I want is just to root the phone. Why is this flash some japanese firmware to my phone!
Yes I am a n00b.
Click to expand...
Click to collapse
Because "some japanese" firmware is with exploit before it was fixed by Sony

where can I download official hong kong firmware? I am stuck on step 5.

sunny7day said:
where can I download official hong kong firmware? I am stuck on step 5.
Click to expand...
Click to collapse
I haven't seen HK firmware beeing uploaded here on XDA yet, but you can make yourself with PPC + flashtool (its not difficult, look in the forum how to do).

I just got the hk firmware and finished all the steps in the first post, now i am rooted.
Yes it is rooted but it left alot of unwanted au japanese sofware in my phone.
It should be noted in the first line in the first post of this thread.
But thank you anyways.
So, I have to wipe and re-flash my stock HK firmware.
Are there any other way to root my Xperia V without flashing other firmware?

If you did everything according to the howto I posted, you would be running your stock HK firmware, rooted.
All those au apps left after flashing back the stock LT25i firmware can be easily uninstalled. They're in /data/app, not in /system/app.
And, quoting the last line from the howto I posted,
Remember to clean up those pesky au apps.
Click to expand...
Click to collapse
sunny7day said:
Are there any other way to root my Xperia V without flashing other firmware?
Click to expand...
Click to collapse
You're welcome to find one and share it with us. Believe me, I'd rather do something simple than bother with all this reflashing and app removal.
Also, if you really want it simple, unlock your bootloader already.

Gasai Yuno said:
If you did everything according to the howto I posted, you would be running your stock HK firmware, rooted.
All those au apps left after flashing back the stock LT25i firmware can be easily uninstalled. They're in /data/app, not in /system/app.
And, quoting the last line from the howto I posted,
You're welcome to find one and share it with us. Believe me, I'd rather do something simple than bother with all this reflashing and app removal.
Also, if you really want it simple, unlock your bootloader already.
Click to expand...
Click to collapse
First of all, thanks for doing the tutorial for us with locked bootloader. :good: :highfive:
a) But you need a ftf-file in order to flash back the original kernel and HK is not available as a download here on XDA yet (If you don't do it yourself).
b) Not everybody has a Ph.d in translation and "pesky" is rarely used by less educated, at least in my case.
c) I have an app_log.sin that bothers me, when trying to flash back the LT25i kernel and system, does it matter?
d) Will this work when we get Jelly Bean?
Ps. Watashi wa Tokyo no Yukigaya-Otsuka de sunde ima****a. Boku no okusan wa nihonjin de****a. Demo owari desu :crying:
Ps. ps. The language filter on XDA removed S and H and I and T. WTF!

datagubben said:
First of all, thanks for doing the tutorial for us with locked bootloader. :good: :highfive:
a) But you need a ftf-file in order to flash back the original kernel and HK is not available as a download here on XDA yet (If you don't do it yourself).
Click to expand...
Click to collapse
And if you do please PLEASE share it as we could do with it here
b) Not everybody has a Ph.d in translation and "pesky" is rarely used by less educated, at least in my case.
Click to expand...
Click to collapse
not a scooby doo fan then?
c) I have an app_log.sin that bothers me, when trying to flash back the LT25i kernel and system, does it matter?
d) Will this work when we get Jelly Bean?
Click to expand...
Click to collapse
There is no way to know untill it lands on our devices, Sony can(and do) monitor what we do on this forum and, allthough they are quite dev friendly, do find way to fix the loopholes we exploit to get root access. They want us only to get that via an official unlocking from their site. You cant blame them for that, they are a big company and have lots of ways of losing contracts if they cant secure their system.
But you can be your bottom dollar tha if they close that exploit, we will find another way
[/quote]
Ps. Watashi wa Tokyo no Yukigaya-Otsuka de sunde ima****a. Boku no okusan wa nihonjin de****a. Demo owari desu :crying:
Click to expand...
Click to collapse
I know this is a personal message but the rules state this is an english speaking forum. You can post in other languages but an english translation is always required. (I know you dont need this next bit but..) Please use google translate if you have trouble with getting an english translation
Ps. ps. The language filter on XDA removed S and H and I and T. WTF!
Click to expand...
Click to collapse
lol!

I can only post the ftf.firmware from operators in Nordic/Sweden:
http://www.swedroid.se/forum/showthread.php?t=86895
What about "app_log.sin", does it matter? Cause it is flashed together with the Kernel.sin and system.sin
I don't watch Scooby Doo.
I speak japanese and I said "I lived in Tokyo but not now".
S,h,i,t

datagubben said:
I can only post the ftf.firmware from operators in Nordic/Sweden:
http://www.swedroid.se/forum/showthread.php?t=86895
Click to expand...
Click to collapse
I meant the other guy, in response to your post about making his own ftf, if he does, he should post it and share
What about "app_log.sin", does it matter? Cause it is flashed together with the Kernel.sin and system.sin
Click to expand...
Click to collapse
not sure
I don't watch Scooby Doo.
Click to expand...
Click to collapse
google it and watch, a clasic kids cartoon with a classic catchphrase of "I would have got clean away with it, if it wasnt for you PESKY kids!
I speak japanese and I said "I lived in Tokyo but not now".
Click to expand...
Click to collapse
thanks
S,h,i,t
Click to expand...
Click to collapse
I gathered that

datagubben said:
c) I have an app_log.sin that bothers me, when trying to flash back the LT25i kernel and system, does it matter?
d) Will this work when we get Jelly Bean?
Click to expand...
Click to collapse
c) Make a copy of your stock FTF file. Open the copy in Total Commander or 7-Zip. Delete everything except the manifest, loader.sin, kernel.sin and system.sin. No more app_log.sin appearing in Flashtool, yay!
d) Depends on two factors.
First, if the 4.1 update will replace the keys used to sign .sin files, removing compatibility with older firmware, this approach will be unavailable. This is what Motorola did with the DROID 2/X/2 GLOBAL.
Second, provided they don't replace the bootloader, and we can still flash back to 4.0: whether we will be able to retain root during firmware update (via OTA RootKeeper or whatever else exists).
As for the language filter, use Kunrei romaji (you know, the system where you use “si” instead of “shi” for し and “ti” instead of “chi” for ち) to work around it.

[MOD][4.0+] Enable Trackball Wake

Please notice. It is not intended for PRE-ICS ROMS!
Project is now Open Source with MIT license attached.
Visit
Code:
https://github.com/bhm/trackballwake
What ROMs will it work with?
It was initially made for Wasimk32's akop_light ROM. update-trackballwake-signed.zip package works for sure.
It should work with any AOKP based ROM. CyanogenMod 9 and 10 should work too as original script was written for CM ROM.
What Devices will it work with?
Original script was written for HTC Liberty. Method used works in our WIldfire. I assume it is safe to say it will work on other devices too. No guarantee, though.
THE SAFE ROUT
ALWAYS make sure you have a working nandroid backup. ALWAYS.
Flash the update-trackballwake-signed.zip in recovery. Boot up and it should work. After a fresh start it may lag a bit. What I experienced is that trackball wakes up the devices and the lockscreen doesn't have the usual lag.
How to use the script if you have S-OFF device
Flash the package with the script
boot up
Plug in the device
Open terminal console on your desktop and type
Code:
adb shell
The device may ask for permissions.
then type
Code:
trackballwake2
OR
Download Terminal Emulator
Open it up and type
Code:
su
. Grant permissions.
type
Code:
trackballwake
Finally reboot the device.
trackballwake2
Rewritten script that modifies proper file. Checks for S-ON. Use only when you have S-OFF.
update-trackballwake-script-signed.zip
Flashes new script to be run. Use only when you have S-OFF.
update-trackballwake-signed.zip
Flashes the new file that enbles wake by trackball. Will work with S-ON flag.
Enjoy and report problems.

Looks like there have been a mismatch!
Cause when I use terminal emulator with the trackballwake command it says not found?!!
And when I use adb shell with the trackballwake2 command it says "trackballwake2" it says "trackball will be disabled"!!

which rom??
Wysłane z mojego Wildfire przy użyciu Tapatalka

[Q] Xperia Z into Diag Mode

I was wondering if it was possible to put the Xperia Z into diagnostics mode?
To see if QXDM could see and use its just monitoring tools to do some scans around the area

qew204 said:
I was wondering if it was possible to put the Xperia Z into diagnostics mode?
To see if QXDM could see and use its just monitoring tools to do some scans around the area
Click to expand...
Click to collapse
Hmm, I don't know.
But tell me more about it or link me to a thread. :laugh:

Nexus 4 Diag Mode
I tried the su -c 'setprop usb.sys.config diag,adb' command in the android terminal and nothing happen when I plugged it into the computer.
I'm wondering if the command would be different for the Xperia Z.

qew204 said:
Nexus 4 Diag Mode
I tried the su -c 'setprop usb.sys.config diag,adb' command in the android terminal and nothing happen when I plugged it into the computer.
I'm wondering if the command would be different for the Xperia Z.
Click to expand...
Click to collapse
Hey.Have you found out how to put it to diag mode?

fil925 said:
Hey.Have you found out how to put it to diag mode?
Click to expand...
Click to collapse
No, never really worked. I think that Diag mode may only be for the Nexus 4

qew204 said:
No, never really worked. I think that Diag mode may only be for the Nexus 4
Click to expand...
Click to collapse
have you tried connecting through bootloader because it should be connecting as modem.I wound but i can't unlock bootloader

Diag Mode for XPERIA ZL
I have tried as well with Sony ZL,
setprop persist.sys.usb.config diag,adb
Nothing happened while connecting the device, no new hardware detected for COM port
Appres=ciate please your help as I need to connect to QXDM, QPST
thanks
BR
Samir

qew204 said:
I was wondering if it was possible to put the Xperia Z into diagnostics mode?
To see if QXDM could see and use its just monitoring tools to do some scans around the area
Click to expand...
Click to collapse
Open ADB console and type :
adb shell
su
setprop persist.usb.eng 1
source : http://forum.xda-developers.com/cro...ad-progress-please-leave-im-updating-t2871269
i follow thread above but cant get the diag driver for C6603 so QXDM wont work..

Xposed for Pipo X8 -infinite bootloop

Hello. I am trying to install Xposed on a Pipo X8 dual-booting (Android/Windows selectable from start) tablet, however I get stuck in an infinite bootloop. Any ideas on how to make it work for the Pipo X8? I tried installing SELinux permissive mode apk, however that app says it is already in that mode, and it doesn't help.
KitKat 4.4.4

same result on X9
Just tried same on a Pipo X8. Same bootloop.

ulev said:
Just tried same on a Pipo X8. Same bootloop.
Click to expand...
Click to collapse
Do you mean X9 or X8?

misterbobdobalina said:
Do you mean X9 or X8?
Click to expand...
Click to collapse
.
X9 like I said, but that really doesn't make any difference.

ulev said:
same result on X9
Just tried same on a Pipo X8. Same bootloop.
Click to expand...
Click to collapse
Yes, or X8 like you also said.
Made me wonder...

ulev said:
Just tried same on a Pipo X8. Same bootloop.
Click to expand...
Click to collapse
misterbobdobalina said:
Hello. I am trying to install Xposed on a Pipo X8 dual-booting (Android/Windows selectable from start) tablet, however I get stuck in an infinite bootloop. Any ideas on how to make it work for the Pipo X8? I tried installing SELinux permissive mode apk, however that app says it is already in that mode, and it doesn't help.
KitKat 4.4.4
Click to expand...
Click to collapse
Read rovo89's reply in the latest change log for his Xposed framework for Lollipop. Seems that he is aware of the issues with pre-Lollipop Android systems.

orville87 said:
Read rovo89's reply in the latest change log for his Xposed framework for Lollipop. Seems that he is aware of the issues with pre-Lollipop Android systems.
Click to expand...
Click to collapse
Thanks for info.
I am trying to log logcat when the bootloop occurs, but I can't trigger logcat myself because Ethernet doesn't work, there is no USB-debugging, and obviously I can't trigger something from screen. How can I write a script that logs logcat to file early on? I haven't managed...

misterbobdobalina said:
Thanks for info.
I am trying to log logcat when the bootloop occurs, but I can't trigger logcat myself because Ethernet doesn't work, there is no USB-debugging, and obviously I can't trigger something from screen. How can I write a script that logs logcat to file early on? I haven't managed...
Click to expand...
Click to collapse
Well, ADB per command line works during boot. USB debugging should be available via Developer Options, which you can activate manually.

orville87 said:
Well, ADB per command line works during boot. USB debugging should be available via Developer Options, which you can activate manually.
Click to expand...
Click to collapse
Yes, it's only that I don't have an USB jack to plug into. Only host ports...

misterbobdobalina said:
Yes, it's only that I don't have an USB jack to plug into. Only host ports...
Click to expand...
Click to collapse
At your PC or at your device?

orville87 said:
At your PC or at your device?
Click to expand...
Click to collapse
At the Pipo X8 device. It has only USB host ports.

misterbobdobalina said:
At the Pipo X8 device. It has only USB host ports.
Click to expand...
Click to collapse
Aren't there USB to USB cables (male to male) available at your place?

orville87 said:
Aren't there USB to USB cables (male to male) available at your place?
Click to expand...
Click to collapse
That won't work. Can't connect host-to-host.

logcat of xposed bootloop!
I managed to get a logcat of when xposed tries to load and gets stuck in a bootloop for device Pipo X8.
See attachement.
This thread may also be of interest since it also concerns Intel Atom processors:
http://forum.xda-developers.com/xposed/xposed-causing-bootloops-intel-z3735d-t2794565

Great news!
I managed to activate Xposed Framework 2.6.1 without causing bootloop using the following method:
http://www.androidauthority.com/community/threads/installing-xposed-framework-on-intel-powered-devices.25841/ :angel:
I did however have to modify the above procedure slightly because there existed no
/data/data/de.robv.android.xposed.installer/conf directory
or
conf/jit_reset_offset file
What I did was this (requires root):
adb install de.robv.android.xposed.installer_v32_de4f0d.apk
adb shell
su
mkdir /data/data/de.robv.android.xposed.installer/conf
chmod 771 /data/data/de.robv.android.xposed.installer/conf
chown u0_a71:u0_a71 /data/data/de.robv.android.xposed.installer/conf (u0_a71-user might differ)
touch /data/data/de.robv.android.xposed.installer/conf/jit_reset_offset
echo 148> /data/data/de.robv.android.xposed.installer/conf/jit_reset_offset
chmod 771 /data/data/de.robv.android.xposed.installer/conf/jit_reset_offset
chown u0_a71:u0_a71 /data/data/de.robv.android.xposed.installer/conf/jit_reset_offset
Basically make the conf/jit_reset_offset file and conf directory have exactly the same owner and permissions as the other files in the folder.
Then exit adb, open the app and install the framework. It should work. Make sure you know your way out of a bootloop before you try though. Just in case. If the permissions of one of the folders or files differ then the Framework wont be correctly installed. In such a case just change them and try to reinstall the Framework once again. :good:

Does it only works for your phone or for everyone who had a bootloop?

Chekaaaa said:
Does it only works for your phone or for everyone who had a bootloop?
Click to expand...
Click to collapse
I suspect it might work for phones/tablets with Intel Atom processors.

misterbobdobalina said:
Great news!
I managed to activate Xposed Framework 2.6.1 without causing bootloop using the following method:
http://www.androidauthority.com/community/threads/installing-xposed-framework-on-intel-powered-devices.25841/ :angel:
I did however have to modify the above procedure slightly because there existed no
/data/data/de.robv.android.xposed.installer/conf directory
or
conf/jit_reset_offset file
What I did was this (requires root):
adb install de.robv.android.xposed.installer_v32_de4f0d.apk
adb shell
su
mkdir /data/data/de.robv.android.xposed.installer/conf
chmod 771 /data/data/de.robv.android.xposed.installer/conf
chown u0_a71:u0_a71 /data/data/de.robv.android.xposed.installer/conf (u0_a71-user might differ)
touch /data/data/de.robv.android.xposed.installer/conf/jit_reset_offset
echo 148> /data/data/de.robv.android.xposed.installer/conf/jit_reset_offset
chmod 771 /data/data/de.robv.android.xposed.installer/conf/jit_reset_offset
chown u0_a71:u0_a71 /data/data/de.robv.android.xposed.installer/conf/jit_reset_offset
Basically make the conf/jit_reset_offset file and conf directory have exactly the same owner and permissions as the other files in the folder.
Then exit adb, open the app and install the framework. It should work. Make sure you know your way out of a bootloop before you try though. Just in case. If the permissions of one of the folders or files differ then the Framework wont be correctly installed. In such a case just change them and try to reinstall the Framework once again. :good:
Click to expand...
Click to collapse
Thanks a lot. This also works with my dual-boot baytrail tablet Voyo A1 Mini. In my case the correct user and group is u0_a98, which I found out after installing the Framework by doing ls -al /data/data/de.robv.android.xposed.installer/ in Terminal.
I executed the few lines all in one go by copy paste in Terminal after I had manually installed the apk. So no need for using adb which is hard to use anyway with my tablet because same as for your Pipo it doesn't support usb slave mode.

jockyw2001 said:
Thanks a lot. This also works with my dual-boot baytrail tablet Voyo A1 Mini. In my case the correct user and group is u0_a98, which I found out after installing the Framework by doing ls -al /data/data/de.robv.android.xposed.installer/ in Terminal.
I executed the few lines all in one go by copy paste in Terminal after I had manually installed the apk. So no need for using adb which is hard to use anyway with my tablet because same as for your Pipo it doesn't support usb slave mode.
Click to expand...
Click to collapse
That's good to know!
However, if you do:
setprop persist.adb.tcp.port 5555 (might require a reboot!)
in terminal app, you can connect via Ethernet using:
adb connect [Tablet's IP address]
then use
adb shell
if you want to use adb via Ethernet some time.

Pipox8 alternative xposed install method
My experience with PipoX8 was slightly different, but reliably installs without bootloop, I would never have got there without the help above.
Install xposed installer.
Install xposed framework
Install terminal app
Open terminal app
Su
CD data
CD data
CD de.robv.android.xposed.installer
ls -al
Check which user owns the conf directory, if installed (mine was)
If not installed then:
mkdir /conf
chmod 644 /conf
chown u0_a71:u0_a71 /conf (u0_a71-user might differ, make it the same as the other directories)
ls -al
Check that user and permissions are exact match
Now we need to check if jit file is installed
CD conf
Is -al
Check to see if jit_reset_offset file is installed.
If not installed then
touch jit_reset_offset
echo 148> jit_reset_offset
chmod 644 jit_reset_offset
chown u0_a71:u0_a71 jit_reset_offset(u0_a71-user might differ, make it the same as the other files)
ls -al
Check user name and permissions are exact match to other files
Reinstall xposed framework.
Reboot device
Check xposed logs to ensure xposed is working.
Finally ensure you tick the box to make any modules you download active.

Unable to deactivate the blue light filter

Hello. I contact you because I have a problem every day at 5:02 pm an anti blue light filter activates automatically on my phone.Not possible to remove it, do you have a solution? It's very strange. I'm going to make a video to show you.
Envoyé de mon RMX1931 en utilisant Tapatalk

Do you mean nightshield?
You should be able to deactivate it under Display & brightness ---> Night shield

Riffen87 said:
Do you mean nightshield?
You should be able to deactivate it under Display & brightness ---> Night shield
Click to expand...
Click to collapse
Unfortunately it is already deactivated. And everything related ... And I really don't understand
Envoyé de mon RMX1931 en utilisant Tapatalk

tidav52 said:
Unfortunately it is already deactivated. And everything related ... And I really don't understand
Click to expand...
Click to collapse

Tried this earlier... Set my alarm to 5.00pm and sat and watched the screen for 5 minutes on a white background... Nothing changed so it's definitely not something that happens on them all.

indeed all phones are not affected.
Envoyé de mon RMX1931 en utilisant Tapatalk

tidav52 said:
indeed all phones are not affected.
Envoyé de mon RMX1931 en utilisant Tapatalk
Click to expand...
Click to collapse
I got the same problem...17h08 and it"s not the night mode it's the blue fliter activated until 8h08...

I've got this too on my new mobile. The screen color gets an orange tint and it happens at 23:20 for me. Night shield disabled and I can't find how to disable it. Any help welcome!

Hi, I've had this problem too. This happens because you probably had the blue light filter activated in your previous phone. To solve this you have to run some ADB commands, do the following:
1. Go to developer options and enable the option Disable permission supervision (and of course USB Debugging).
2. Connect your phone to a PC and run this commands: adb shell 'settings put secure night_display_activated 0' and adb shell 'settings put secure night_display_auto_mode 0'.
I found the solution here.
I hope it helps.

good evening unfortunately this command is not in the dev menu
Sent from my RMX1931 using Tapatalk

narcisrm said:
Hi, I've had this problem too. This happens because you probably had the blue light filter activated in your previous phone. To solve this you have to run some ADB commands, do the following:
1. Go to developer options and enable the option Disable permission supervision (and of course USB Debugging).
2. Connect your phone to a PC and run this commands: adb shell 'settings put secure night_display_activated 0' and adb shell 'settings put secure night_display_auto_mode 0'.
I found the solution here.
I hope it helps.
Click to expand...
Click to collapse
i tried this method and it's not working it was for a samsung phone...

narcisrm said:
Hi, I've had this problem too. This happens because you probably had the blue light filter activated in your previous phone. To solve this you have to run some ADB commands, do the following:
1. Go to developer options and enable the option Disable permission supervision (and of course USB Debugging).
2. Connect your phone to a PC and run this commands: adb shell 'settings put secure night_display_activated 0' and adb shell 'settings put secure night_display_auto_mode 0'.
I found the solution here.
I hope it helps.
Click to expand...
Click to collapse
Hi, thank you for advice, it worked!
In cmd i had to write
Code:
adb shell
and then
Code:
settings put secure night_display_auto_mode 0

Kingič said:
Hi, thank you for advice, it worked!
In cmd i had to write
Code:
adb shell
and then
Code:
settings put secure night_display_auto_mode 0
Click to expand...
Click to collapse
it worked for me too thanks a lot !

narcisrm said:
Hi, I've had this problem too. This happens because you probably had the blue light filter activated in your previous phone. To solve this you have to run some ADB commands, do the following:
1. Go to developer options and enable the option Disable permission supervision (and of course USB Debugging).
2. Connect your phone to a PC and run this commands: adb shell 'settings put secure night_display_activated 0' and adb shell 'settings put secure night_display_auto_mode 0'.
I found the solution here.
I hope it helps.
Click to expand...
Click to collapse
This worked for me after moving from my OnePlus 3T to Realme XT RMX1921 via Google backup/restore. Sorted. Thank you!

/system/bin/sh: settings put secure night_display_activated 0: not found
/system/bin/sh: settings put secure night_display_auto_mode 0: not found
It seems not working for me
Any solutions..PLs?