Can you give me the adb dmesg and adb logcat?
It did work on the XZ2C
I get this message when I try to create dmesg.log:
1|H8266:/ $ adb shell su -c dmesg > dmesg.log
/system/bin/sh: can't create dmesg.log: Read-only file system
I get this message when I try to create dmesg.log:
1|H8266:/ $ adb shell su -c dmesg > dmesg.log
/system/bin/sh: can't create dmesg.log: Read-only file system
Please either use "adb shell dmesg" or direct the output on your internal storage / sdcard.
Please either use "adb shell dmesg" or direct the output on your internal storage / sdcard.
127|H8266:/ $ dmesg > /sdcard/dmesg.log
dmesg: klogctl: Permission denied
Your DMESG is completely fine.
Are you sure it is from the freeze?
In your DMESG is a normal system start with google apps.
And if TWRP freeze I additionally need the /tmp/recovery.log file.
I don't know if my phone is special or something, but su and pull doesn't works for me.
H8266:/ $ pull /tmp/recovery.log > /sdcard/recovery.log
/system/bin/sh: pull: not found
127|H8266:/ $ su pull /tmp/recovery.log > /sdcard/recovery.log
/system/bin/sh: su: not found
127|H8266:/ $
It is "adb pull" from your computer, not in the "adb shell"
You can also execute "adb shell bla" to execute commands.
About su, I'm sorry that I forgot that you mean the stock ROM.
It needs magsik, before you can execute "su"
But are you really sure that your normal android system freezes? TWRP doesn't interfere with the normal android boot.
I mean, when I try boot to twrp using power button + volume down it stucks at twrp logo. This is what I got from recovery.log :
adb: error: failed to stat remote object '/tmp/recovery.log': No such file or directory
Is there no recovery.log in the temp folder?
"adb shell ls /tmp -l"
And what says the dmesg?
"adb shell dmesg > dmesg.log" will create the dmesg file on your computer.
C:\Program Files (x86)\Minimal ADB and Fastboot>adb shell ls /tmp -l
ls: /tmp: No such file or directory
C:\Program Files (x86)\Minimal ADB and Fastboot>adb shell dmesg > dmesg.txt
dmesg: klogctl: Permission denied
C:\Program Files (x86)\Minimal ADB and Fastboot>
Yep. Also tried rolling back to oreo then again to latest pie firmware but still nothing.
TWRP is root by default and the last time you gave me your DMESG it was from the android system.
So are you really sure trying to acquire the dmesg from TWRP?
Using oreo with my orep twrp (I uploaded the latest oreo firmware) should work too, since it worked in the past.
Okay, previous dmesg was from system so my bad. Now I got it from twrp. Log is in attachments
Btw, Is there any improvement in terms of camera on OmniRom/SODP based roms? Last time I've used OmniRom all was ok but not camera. Even in good daylight conditions photos looked very bad.
Last edited:
Thank you !
Oh no
Omnirom still didn't update the security patch level, so I did hope simply raising the security path level would fix it, but no
Damn damn damn
Camera improvements will come with Android 10.0 and kernel 4.14 (starting with OEMv2)
I don't know if in all of the 448 pages of this thread, the question was posted, but my XZ2 (bootloader unlocked under Android 8) who is on Android 9 (52.0.A.8.83) has a L3 certification with Widevine. That's weird because Sony says the phone will have the L1 certification with Android 9.
*Widevine is the certification for playing HD video from Netflix/PrimeVideo on a phone (L3 = 480p & L1 = >480p)
*Widevine is the certification for playing HD video from Netflix/PrimeVideo on a phone (L3 = 480p & L1 = >480p)
Similar threads
- Poll
Top Liked Posts
-
There are no posts matching your filters.
-
51The Sony Open Devices Project is always happy about volunteers (coding, testing, etc)
Also mainlining your favorite snapdragon powered xperia device into the mainline kernel is possible and we will be glad to help you!
Code:#include <std_disclaimer.h> /* * * We are 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 us for messing up your device, we will laugh at you. * */
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
FAQ:
- If your stock camera preview is black, please follow this issue ticket.
https://github.com/sonyxperiadev/bug_tracker/issues/261
https://github.com/MartinX3-AndroidDevelopment/bug_tracker/issues/7 - Just wiping your phone in TWRP lead into an encrypted & not readable userdata in the stock system.
You need to open advanced wiping and check the entries data and internal storage.
Of course clear the dalvik, too. - If you backed up system and/or vendor partitions and you want to restore them, make sure that TWRP setting "Use rm -rf instead of formatting" is set!.
- If after the usage of NewFlasher or the OTA Updater or something else, which installs stock firmware parts you get stuck into the TWRP or SONY Logo, you need again to disable the verification with the vbmeta.img file and its parameters in fastboot.
- fastboot & adb
- Weird problems not easily to reproduce by other users require that you make sure, that you
- Use the newest platform tools (adb & fastboot)
- Downloaded the newest firmware via Xperifirm from XDA and installed the newest firmware via Newflasher from XDA
- Newflasher from XDA
- Xperifirm from XDA
- Removing the stock bloat apps via titanium backup may result in a boot loop. Use a file explorer to remove them, disable them or try to use my unfinished bloat removal script at github.
- Your phone reboots into recovery, instead of system? Maybe it crashed too often due to a wrong installation or whatever?
In TWRP:-
shows you the reason.Code:
cat /dev/block/bootdevice/by-name/misc - Please replace it with an empty string.
-
Known Bugs:
- The "fastboot boot twrp.img" doesn't work, if you use the hardware buttons to open the blue fastboot bootloader mode. Only use adb, twrp or the android system to reboot into blue fastboot bootloader mode or flash the twrp.img, boot the device, reboot into bootloader and flash the original boot.img back, before booting into twrp.
You can also "fastboot reboot bootloader" in the blue fastboot mode.
This is a bootloader bug, maybe it gets fixed with the stock Q bootloader.
Bugtracker:
- TWRP Bugtracker -> If you think the problem is in TWRP
- My Bugtracker -> If you think the problem is in my implementation
Bugreport:
- A bugreport needs your device name, dmesg, the /tmp/recovery.log and a way to reproduce the issue.
- If the TWRP is stuck at the TWRP logo, the chances are high, that the decryption didn't succeed.
- The TWRP should be still usable if you just "fastboot boot twrp.img" it.
- To rescue a not responding phone:
- VOLUP+POWER for 3 Seconds -> RESTART with one Vibration.
- VOLUP+POWER for 20 Seconds -> SHUTDOWN with 3 Vibrations.
- VOLUP+POWER+CAMERA for 30 Seconds -> HARDWARE SHUTDOWN by discharging a capacitor.
Thank you very much for your help, code contribution & testing! (Random order):
- @dees_troy and his team of volunteers for the TWRP code
- @M-ROM for his hint activating the touch in TWRP
- @osm0sis
- @nreuge
- @FartyParty
- @pandemic
- @nasko_spasko
- @VeixES
- @Klaus N.
- @old.splatterhand
- @yanke928
- @michele2
- @niaboc79
- @j4nn for hacking the kernel to make "fastboot boot twrp.img" possible
- @shoey63 for testing @j4nn 's hack
- @oshmoun for a better "fastboot boot twrp.img" solution
- @dhacke thank your for providing a download server
- Shame on me if I forgot someone after searching through the thread and my PM's!
- And many thanks to the few donators!
A telegram group for technical SODP stuff:
https://t.me/xda_tv
XDA:DevDB Information
TWRP, ROM for the Xperia XZ2
Contributors
MartinX3, oshmoun, Marijn, Sony
Source Code: https://github.com/MartinX3-AndroidDevelopment
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
ROM Firmware Required: Matching to firmware in twrp name
Based On: AOSP
Version Information
Status: No Longer Updated
Current Stable Version: 3.3.1-0
Stable Release Date: 2019-08-10
Created 2018-07-26
Last Updated 2020-10-2312Download & Installation
Download:
- https://androidfilehost.com/?w=devices&uid=11410963190603893035
- https://www.dhsfileserver.de/ftp/martinx3/ Thank you @dhacke for the second download server
- Unzip the *.gz files with https://7-zip.org/ or Linux.
Installation Android 9.0:
- Update to newest stock firmware before unlocking!!!
- Enter fastboot via software, not hardware buttons. See "Known Bugs".
- (Optional; If you modify the system or need the camerafix.zip)
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img - fastboot boot twrp.img
- Advanced menu -> "Install recovery ramdisk" -> Choose twrp.img
- Reboot into installed TWRP
- Want Root? -> Magisk
- (Optional; Security degradation; Only if you know what you're doing) Switch SELinux to permissive (with my permissive.zip)
In case of touch issues on the XZ2 compact:
- Download (try the v10 zip first, if it doesn't work try v9 or v8)
- Do the same steps, but with the TWRP test release.
Installation Android 8.0:
- fastboot --disable-verity --disable-verification flash vbmeta vbmeta-xz2(?).img
- fastboot flash boot twrp.img
- Install stockkernel-xz2(?)-installer.zip
- Install twrp-3.2.3-0-xz2-xz2c-xz2p-installer-xz?-installer.zip
- Install Magisk-v17.1.zip
- (Optional; Security degradation; Only if you know what you're doing) Switch SELinux to permissive (with my permissive.zip)
12@MartinX3 @sToRm// @modpunk
I got drmfix working on enforcing selinux!
How-to:
After reboot into system (post #3 - First time installation of TWRP & after newflasher installation), open a shell window and type:
Enjoy it!Code:su mount -orw,remount /vendor magiskpolicy --load /vendor/etc/selinux/precompiled_sepolicy --save /vendor/etc/selinux/precompiled_sepolicy "allow init domain process { noatsecure }" "allow init secd process { noatsecure }" mount -oro,remount /vendor
(you may now add it in your scripts if you want to) - If your stock camera preview is black, please follow this issue ticket.
