yashsingh1/xdaforums huggingface dataset:
[Xperia Z1 Compact Android Development] 115ek:
Flashing stock ROM isn't necessary - I'm 99% sure. Maybe you can get a log with

adb pull /tmp/recovery.log

while your in TWRP and connected to a PC...

The kernel driver is - as the name says - located in the kernel, which is part of the recovery.img

So everyone flashing this image should have the same functionality (in theory). As it works for me (and some others) I'm just wondering. :rolleyes:

The behaviour is totally expected as amami uses the deprecated full disk encryption (FDE). Most likely your oneplus 6 is using file based encryption (FBE). That's the reason it can boot to your lockscreen because some files necessary for booting aren't encrypted (or not encrypted using your password...). To boot a device with fully encrypted /data you have to decrypt it first. If you're interested in details have a look here.

The other thing sounds a bit strange. However I don't know if it's possible to remove the FDE completely. Maybe the device just sets a default password then? :confused:

Concerning your question:

What definitely should work is taking a backup in TWRP (of course need to decrypt /data before), then format /data and restore the backup. Anyhow - I didn't test such a case so far.
[Xperia Z1 Compact Android Development] tramp20:
Flashing stock ROM was the only way that all older TWRP could read the correct date again after trying your twrp version.

I will try to get a log if I have enough time.

So the recovery.img = twrp.img or at least a part of it?

Thank you.
[Xperia Z1 Compact Android Development] 115ek:
New update:

As I had problems with installing OTA updates (especially with /data encrypted, but not limited to) on LineageOS 16.0 I came up with a fix.

Download Currently only on sourceforge - android filehost is buggy at the moment...

19.09.2019 3.3.1-0.3

fix non working OTA update (rebooting to recovery and stucking there unable to install update automatically)

Edit:

As reminder for me / interested guys: This commit breaks the OTA updating in some cases (when mmap isn't sufficient). The buildflag

-D_FILE_OFFSET_BITS=64

doesn't work as intended on my setup. Maybe I missed something.
[Xperia Z1 Compact Android Development] underflash:
Have the same time/date problem with twrp-3.3.1-0.3-amami.img

recovery.log >> https://pastebin.com/rBdHAmz2

Also does not reboot into the recovery from system (AICP 14), just shutdown and then power+volume down works.
[Xperia Z1 Compact Android Development] tramp20:
Until now I can not use this twrp :(
[Xperia Z1 Compact Android Development] 115ek:
I guess that's the problem:

I:TWFunc::Fixup_Time: failed load uint64 from file /data/time/ats_2

Twrp can only set the correct time if /data is mounted. Maybe it also has got something to do with encryption: I'm encrypted and the time is corrected AFTER I successfully decrypted /data.

But most likely it's just about mounting /data.

Give it a try and report back.

About the reboot issue: This TWRP uses lzma ramdisk compression. Long story short: your ROM (actually your boot.img) needs to suppport it. LineageOS 16 does and AICP 14 as well. BUT it was merged in july 2019. Please make sure you're using the latest version. I'm going to test it on my own as well.

Why is the correct/incorrect time a blocker for you? I can't really follow you.
[Xperia Z1 Compact Android Development] underflash:
Just updated ROM to the latest AICP 14 build and reboot started working :good: Time seems randomly wrong, randomly correct (not big deal, I guess). My phone is not encrypted.
[Xperia Z1 Compact Android Development] bananabytes:
Sorry for the late response. The binary from there worked. I was able to flash the latest version of AICP and access the data partition within recovery. The only thing is that Titanium Backup is not working correctly now.
[Xperia Z1 Compact Android Development] 115ek:
Let's move the ongoing discussion to the right thread. (beginning from here)

To sum up:

The time in the latest TWRP version(s) isn't working all the time. Until now we weren't able to figure out a clear and reproduceable case breaking it. That makes it more difficult to debug.

The main focus lies on

/data/time/ats_2

which stores an 64 bit (8 byte) time offset. Sometimes(?!) it gets corrupted and is only 4 bytes long what causes TWRP to fail reading it and so showing the wrong time.

The file is written / updated by Sony Timekeep. But timekeep is NOT shipped in the recovery image.

Actually it's quite easy: we only need to find the one who is accessing and corrupting it :good:

Nope. Definitely not - I just didn't include the fix therefore to check if there are dependencies. Sorry for that. ;)

The next testing versions will show up as TWRP 3.3.1-Tx to be more distinguishable.

Can someone give precise information with which version the problem started?

And it would be nice, if different combinations can be tested (AICP, LineageOS).
[Xperia Z1 Compact Android Development] tramp20:
How to decode these 8 bytes? Should this be the Unix timestamp?

On my first Z1c the values are e0fbb4006d010000

on my other Z1c 78865b2764010000

Both are running AICP 9 and taken at the same time.

If I try to decode them with

https://bin-dez-hex-umrechner.de/ and

https://rechneronline.de/uhrzeiten/timestamp.php

I get a complete wrong time.

Does Android really use and update these values?

Even after ~10 mins I see no difference.
[Xperia Z1 Compact Android Development] 115ek:
Checkout this. Here ats_2 is written. ;)

I haven't studied this myself...
[Xperia Z1 Compact Android Development] tramp20:
Again, how to decode this hex values from ats_2?

On my phones I see 2-bytes and 4-bytes values, each different from the other and never could decode them to correct date/time :(

They have all the same actual AICP-Rom, Magisk and edxposed.

https://bin-dez-hex-umrechner.de/

https://rechneronline.de/uhrzeiten/timestamp.php
[Xperia Z1 Compact Android Development] 115ek:
Again, checkout this. ats_2 is written there. After understanding what's happening there you'll most likely be able to decode it. And keep in mind that there are things like big/little endianess (as we're on arm it's most likely little endian). Take another look here: https://en.wikipedia.org/wiki/Endianness#Mapping_multi-byte_binary_values_to_memory
[Xperia Z1 Compact Android Development] tramp20:
Thank you.

I will try to understand the Wiki article but I fear that this will exceed my mental faculties (I am over 77 years old) :(
[Xperia Z1 Compact Android Development] tramp20:
[MENTION=8036586]115ek[/MENTION]

During testing some twrp-3.3.1-x-amami.img versions I am no longer able to flash another TWRP.

I had installed twrp-3.3.1-0-amami.img.

When try to I flash an other version I get always these error:

Sending 'recovery' (12152 KB) FAILED (Write to device failed (no link))

fastboot: error: Command failed

or

Sending 'recovery' (12152 KB) FAILED (Write to device failed (Too many links))

fastboot: error: Command failed

fastboot version 29.0.5-5949299

The last TWRP is functional at least. I never had this error and pressing the red reset does not help.

What can I do?
[Xperia Z1 Compact Android Development] 115ek:
I don't think it's a device problem. It's more likely to be a fastboot version problem.

Is

fastboot devices

working correctly? I guess you're using windows - else such a recent fastboot version won't be installed (maybe on Arch Linux or if you install it manually though).

Do you have any other PC's to test with?

It's a bit strange because flashing was working for you before. And the device side didn't change. So the problem lies in cable / PC driver / fastboot.
[Xperia Z1 Compact Android Development] tramp20:
This morning I fought two hours with flashing TWRP :( (I should really know how to do)

Then I left the phone for 4 hours alone (was mountain biking) and after this time flashing TWRP succeeded as always :)

Is this version twrp-3.3.1-0.3-amami.img the latest and no test version?
[Xperia Z1 Compact Android Development] marsa47:
Most likely an issue with the USB port (had the same problem with older z1c).

BTW, you could flash recoveries from within present recovery. When TWRP is booted:

Install -> Install Image (bottom right button) -> select img file -> select 'Recovery' partition - > Flash
[Xperia Z1 Compact Android Development] 115ek:
I uploaded a new version. Nothing critical changed but:

Sony bootlogo is now displayed

TWRP (sub)version number is now displayed to avoid confusion

TWRP app is excluded (as there isn't any use if we're not official)
[Xperia Z1 Compact Android Development] michalsmerf:
Hello

How can i flash this TWRP on my device ?

I started it after years, i have 5.1.1 Android and TWR 3.1.0

From PC, all looks fine but image don't flash and same with .img by TWRP and App

In all case i have note that all was fine or done but still not updated.
[Xperia Z1 Compact Android Development] 7alvoo:
put the twrp-3.3.1-0.4-amami.img file here:

Flashtool\x10flasher_lib\

run this command in this folder:

fastboot.exe flash FOTAKernel twrp-3.3.1-0.4-amami.img

switch off the phone and press volume up button and hold + connect the usb together
[Xperia Z1 Compact Android Development] michalsmerf:
P:\Flashtool\x10flasher_lib>fastboot.exe flash FOTAKernel twrp-3.3.1-0.4-amami.img

Sending 'FOTAKernel' (14040 KB) OKAY [ 0.457s]

Writing 'FOTAKernel' OKAY [ 0.953s]

Finished. Total time: 1.426s

-------------------------------------------------------------------------------------

After reboot still 3.1.0.0

Its that possible ? :D

Driver is ok ?

https://drive.google.com/file/d/14JCuddqPLTkiQ6QtFeheJUBHpjhQtXLk/view?usp=sharing
[Xperia Z1 Compact Android Development] tramp20:
IMHO you should use RECOVERY and not FOTAKernel with the Z1c.

FOTAKernel never worked on my phone.
[Xperia Z1 Compact Android Development] 115ek:
Please check the instructions in my old thread
[Xperia Z1 Compact Android Development] michalsmerf:
Hah :D

Still not working, something wrong with device ?
[Xperia Z1 Compact Android Development] 115ek:
What TWRP are you currently using? (link?)

How do you enter TWRP?

Did you make sure you installed the latest bootloader from here?
[Xperia Z1 Compact Android Development] ashtar_sheran:
Hi,

Just a small question regarding TWRP updating on the Z1c.

Right now I have my bootloader unlocked and XZdualrecovery installed. I wanted to upgrade the old TWRP version 2.8.7 to 3.3.1.

Can I just flash munjeni's openbootloader from here and then flash TWRP 3.3.1 via flashtool, or do I need to get completely rid of XZdualrecovery first?
[Xperia Z1 Compact Android Development] 115ek:
It should work directly. However using this TWRP only makes sense if you use one of the ROM's mentioned in the OP (Android >= 8) to be able to use all functions.

At least that's my opinion ;)
[Xperia Z1 Compact Android Development] OMiD_GH:
hi

Thank you very much for your work

i have one question..

I Can use TWRP 3.3.1-4 for tablet z2?

OR

Can you update TWRP 3.2.1 to 3.3.1 for z2 tablet?
[Xperia Z1 Compact Android Development] 115ek:
No, you can't. It's a different device (although it's also msm8974 based).
[Xperia Z1 Compact Android Development] michalsmerf:
I flashed that file like here : https://www.youtube.com/watch?v=ctqKNAzrKpQ

Then i disconnect device, enter TWRP and try update via TWRP but nothing.

Still same version.

My Xperia has:

DstrikerZ1 Kai ROM / SP008 5.1.1 Based

----------------------------------------

kernel : 3.4.25-lp-mr3-Advanced

sharonliu@xpt #1

Sat Mar 25 21:07:14 CST 2017

--------------------------------------

14.6.A.1.236

-------------------------------------

TWRP 3.1.0.0 ( show when enter TWRP)
[Xperia Z1 Compact Android Development] 115ek:
Hmm. Can you please try again with fastboot?

fastboot flash recovery twrp-3.3.1-0.4-amami.img

Afterwards disconnect. Then power on while holding VOL down. You can release power when bootlogo appears but continue holding VOL down until TWRP screen comes up.

EDIT: There's a another way to enter recovery: wait for the LED to light up and pressing VOL up then. However this only works if your bootimage supports that. And yours most likely does not...
[Xperia Z1 Compact Android Development] michalsmerf:
I do it with fastboot too and still, when i go recovery it still have 3.1.0.0

I can normaly enter to TWRP but can't update it.

From beginning:

I don't use z1c for 2/3 years.

I have now on it :

DstrikerZ1 Kai ROM / SP008 5.1.1 Based

----------------------------------------

kernel : 3.4.25-lp-mr3-Advanced

sharonliu@xpt #1

Sat Mar 25 21:07:14 CST 2017

--------------------------------------

14.6.A.1.236

-------------------------------------

TWRP 3.1.0.0 ( show when enter TWRP)

i saw there is lineage os for this device so i want flash it for z1c becuse i have it on xz1c.

But everytime i have error so i was thining maybe TWRP is to old.

The main point is to have LineageOS 16 on my Z1C :D
[Xperia Z1 Compact Android Development] 115ek:
How do you enter TWRP currently? That's really important.

You may also try

fastboot erase recovery

to clean it. But actually that shouldn't matter.
[Xperia Z1 Compact Android Development] michalsmerf:
I turn on device and then I press volume down like BIOS in PC :D
[Xperia Z1 Compact Android Development] 115ek:
I can only repeat myself once again "press and hold Vol. down and power, if device vibrates release power and keep Vol. down holding. That's it."

Vol down has to be pressed BEFORE power or at least at same time.
[Xperia Z1 Compact Android Development] michalsmerf:
I got it !

this one help me :D

https://xdaforums.com/sony-xperia-z...neageos-12-1-z1c-current-sec-patches-t3614936

Then i update from this to lates TWRP via flashing image in it (in recovery)

The only think is that have other .img file, all commands are same like in other link that you and other give me here.

Now all is fine :D

Thanks you all!
[Xperia Z1 Compact Android Development] 115ek:
I've just uploaded a new TWRP 3.4.0 image.

It only includes the latest twrp upstream changes and no further device-specific changes.

This update is mostly interesting for persons who are using OTA updates AND encryption AND Magisk.

A change was introduced allowing the user to unlock the /data partition during an OTA update. You'll be prompted to enter your unlock pattern/pin/password every time an OTA update is executed now (only when your device is encrypted). You can safely ignore that / cancel it if you're not using magisk. The installation will continue.

However, if you're using magisk it's necessary to decrypt /data.
[Xperia Z1 Compact Android Development] 115ek:
There's a new bugfix release: 3.4.0-1 which solves OTA updating problems in rare cases (rebooting to recovery automatically and stucking there without installing anything).
[Xperia Z1 Compact Android Development] wmiki75:
I unable to install and start TWRP recovery for my Z1 compact.

It seems to be flashed on, with fastboot mode (fastboot flash recovery twrp3401.img) or twrp.apk (rooted by: kingroot), but the recovery not start.

Power + Volume Down, or any other method not start recovery :(

Any ideas?

Sony D5503

Android 4.4.4

Build: 14.4.A.0.157

BootLoader Unlocked
[Xperia Z1 Compact Android Development] 115ek:
Make sure to install latest firmware at first. It's Android 5.

Then you can also have a look at the instructions here.
[Xperia Z1 Compact Android Development] wmiki75:
How can i install the latest firmware? OTA not find newest.
[Xperia Z1 Compact Android Development] 115ek:
There are many manuals.

You could obtain the .ftf firmware file using this tool: https://xdaforums.com/crossdevice-dev/sony/pc-xperifirm-xperia-firmware-downloader-t2834142

Then there's a flashtool: http://www.flashtool.net/index.php

Just search for it. You're not the first one trying to do something like this.
[Xperia Z1 Compact Android Development] clads:
Please delete this (mistake between XZ1C et Z1C)
[Xperia Z1 Compact Android Development] -FancyUsername-:
Just want to let you know that after installing 3.4.0-1, when I wanted to reboot it installed an update and ran this update installer script. This is the first time it actually worked. Before (3.3.1-0.4) I had to reinstall the newer TWRP because it always reset to 3.0.0, wipe the system, and install TWRP and the newer version from scratch, which also brought an entire reset of the phone except for photos. Shocking
[Xperia Z1 Compact Android Development] asdf2345:
Does not work at all, I'm using the munjeni bootloader, and have tried 3.2.1, 3.3.1, and 3.4.0, but none of them have worked. Holding power and volume down makes the phone vibrate, but never turn on. Holding power, then pressing volume down when the light goes on makes it reboot.
[Xperia Z1 Compact Android Development] o-l-a-v:
With v3.4.0-1 I can't get "swipe to flash" or even "swipe to unlock" to work. Makes it really hard to use the recovery for anything.

Edit: Might be the cheap replacement screen assembly I got from Ebay.
[Xperia Z1 Compact Android Development] Malk4ever:
Thanks... installing this image bricked my amami...
[Xperia Z1 Compact Android Development] lm089:
I'm sorry for you, but I can confirm that the recovery image itself basically works on my amami, or at least it never bricked my device.

Last installation was ~2 months ago when I had to wipe everything off it (something went badly wrong during an update), and I flashed this v3.4.0-1 without any big problems.

Just to be sure: did you flash to FOTAKernel? This very old thread here contains still valid instructions on how to install TWRP on our devices: https://xdaforums.com/t/closed-eol-lineageos-12-1-for-z1c-with-current-sec-patches.3614936/

BTW: if your amami is really gone, AND you really care to own one, AND you have an address somewhere in the EU: send me a PM, I'm considering giving mine away...
[Xperia Z1 Compact Android Development] asdf2345:
I'm in the US and I suck at doing repairs, so I have like two good amami boards and frames and a bunch of other stuff, but no buttons, displays, or backs.
[Tilt, TyTN II, MDA Vario III Windows Mobile ROM De] zwaenepoel:
I'm using the WM 6.1 WWE original rom from HTC.

How to install the keyboard that comes with the WM6.1 PTG ??
[Samsung Galaxy S8 Guides, News, & Discussion] Nabil Prodhan:
Is there any development of kali nethunter for samsung s8/g950fd ?
[Samsung Galaxy S8 Guides, News, & Discussion] TheMadScientist:
I was using the nexus build I believe on my US snap s8. It was some what functional. Of coarse I can't run modded kernel or anything
[Samsung Galaxy S8 Guides, News, & Discussion] Nabil Prodhan:
which nuexus build worked in your s8 ? and do you have any idea about exynos s8 ? and which bugs have you faced there after installing that kernel ? can you please clarify ......
[Samsung Galaxy S8 Guides, News, & Discussion] TheMadScientist:
I can't Install any kernel

https://************/how-to-install-kali-nethunter-on-the-galaxy-s8/

This is what I followed

https://www.google.com/amp/s/xdafor...g955u-s8-kali-nethunter-install-t3682285/amp/
[Samsung Galaxy S8 Guides, News, & Discussion] Nabil Prodhan:
Facing problem with flashfire (root was found ,but access could not be acquired)//// I am using magisk 19.3. And i can't go back to super su, i have to stick with magisk for using some of my necessary modules. Do you have any other idea ? or any idea how can i fix this flashfire problem ?
[Samsung Galaxy S8 Guides, News, & Discussion] TheMadScientist:
Use twrp. Flashfire is real finicky
[Samsung Galaxy S8 Guides, News, & Discussion] Nabil Prodhan:
can't find nethunter-flo-marshmallow-3.0.zip . can you please upload the file link ?
[Samsung Galaxy S8 Guides, News, & Discussion] TheMadScientist:
https://images.offensive-security.com/nethunter/nethunter-flo-marshmallow-kalifs-full-2019.2.zip
[Samsung Galaxy S8 Guides, News, & Discussion] Nabil Prodhan:
I am facing another problem after installing the zip, my left side display touch is not working. After the problem ,I have flashed stock rom with odin, but it's same problem with the touch. What should I do ?
[Samsung Galaxy S8 Guides, News, & Discussion] TheMadScientist:
That's weird I never had that issue. I wouldn't even know where to start on that.
[Samsung Galaxy S8 Guides, News, & Discussion] Nabil Prodhan:
What can I do ? and samsung lcd is too much expensive ,you know. Do you have any idea ?
[Samsung Galaxy S8 Guides, News, & Discussion] TheMadScientist:
I would assume it's in the kernel or something. Make sure there aren't any extra partitions. It shouldn't have done any hardware damage. It has to be something not set straight in Odin. There are only a select number of partitions actually touched by Odin.

So one would need to find out what other partitions get touched or modded. I have restored before Kali and had a bunch of partition errors I assume was due to locked bootloader but even after restore still had those errors. Eventually a total format and restore cleared them. But your unlocked bl and modifiable kernel makes it different than my case
[Samsung Galaxy S8 Guides, News, & Discussion] Nabil Prodhan:
I made a pit file and flashed this pit through odin. But no change, I think pit file does re-partition in phone. Any other way to totally clear all of the partitions and reinstall all of the drivers including touch drivers ?
[Samsung Galaxy S8 Guides, News, & Discussion] skedone:
You tried andrax instead installs on top of android as a normal app needs unlocked bootloader and root to full work but has all the same tools as kali nearly and few it doesn't
[Samsung Galaxy S8 Guides, News, & Discussion] unknown1818:
Nethunter and Andrax need custom kernel to suppot monitor mode usb wifi card, someone know what kernel i should use for that for G950f? I really need it but dont have PCto compile it myself, please if someone have kernel with a drivers for rtl8812au for s8. Thank you
[Samsung Galaxy S8 Guides, News, & Discussion] iim baby jesus:
Any way to install either andrax or nethunter on a S9 g960u rooted locked bootloader?

Having some issues with andrax, just wants to keep installing things on my phone. this is my first time using it.
[Samsung Galaxy S8 Guides, News, & Discussion] skedone:
It always has to install stuff it's downloading all the Linux apps , or you can install termux and so it via that too
[Asus Zenfone 5Z  Questions & Answers] Naveenjain:
Out of 6gb of ram - 5.1gb is currently in use while only 480mb is cached. is this normal? I'm not using any of these apps and instead of being cached, they remain in current use. Won't it consume battery a lot?
[Asus Zenfone 5Z  Questions & Answers] sedp23:
This is my average usage I'm considering getting the 8gb ram version of the zenfone 6 if I can find it because of this.

My battery life is still pretty good tho I can squeeze about 12 hours on LTE and a full day on wifi only
[Asus Zenfone 5Z  Questions & Answers] mickey36736:
Same for me too. I might replace the battery or get zenfone 6. I use heavily everyday and the battery starts dying even with schedule charging.
[Asus Zenfone 5Z  Questions & Answers] sedp23:
The battery is ok for me I'm able to stretch it to make it through my work day if I need to with the battery saver options. I'm usually streaming iheartradio and Spotify at least for 4 to 5 hours everyday with Bluetooth on that's the bulk of my battery usage. If I can ever find a zenfone 6 I can buy I'll definitely pick one up they are sold out everywhere. I wonder if the RAM would make a difference in the battery life
[Xiaomi Redmi Note 7 Pro Questions & Answers] askool:
Hi I have a problem while traveling I always lost redmi note 7 pro GPS signal lost.

1. I done no restriction for Google map in security battery saving.

2. I update new miui but still GPS signal lost.

Can anybody please tell it's for me or others user a similar issue of GPS signal lost in RMN7 pro.
[Xiaomi Redmi Note 7 Pro Questions & Answers] nuketron:
Unfortunately, depending on the batch, some Redmi Note 7 Pro suffers from a hardware issue rendering the GPS nearly unusable. You can find out if yours suffer from it by using GPS test apps. That's the bad news. The good news is it's a relatively easy and free fix. It takes some time if you do not have warranty.