yashsingh1/xdaforums huggingface dataset:
[Xperia Z4/Z3+ General] AndroPlus:
USB isn't detected by PC in TWRP and I can't create full log...

Is there any other way to make log?

Here's last_log from /cache/recovery:

http://x.andro.plus/1Lvvhom
[Xperia Z4/Z3+ General] [NUT]:
Seeing that XZDR log... I have a few things to add for [MENTION=4433143]venkat kamesh[/MENTION]

First of all, update your XZDR repository to 2.8.21, this is better suited to work with and defeat the SELinux and Sony RIC security features in Lollipop. 2.8.1 will not work on Lollipop.

Then update the following lines at these points to match the correct block device path where [MENTION=6902252]Sacktreter[/MENTION] here already stated.

https://github.com/xNUTx/XZDualRecovery/blob/2.8-RELEASE/src/chargemon.sh#L253-L254

https://github.com/xNUTx/XZDualRecovery/blob/2.8-RELEASE/src/chargemon.sh#L336-L337

https://github.com/xNUTx/XZDualRecovery/blob/2.8-RELEASE/patches/all/twrp/etc/twrp.fstab#L1-L5

https://github.com/xNUTx/XZDualRecovery/blob/2.8-RELEASE/src/installrecovery.sh#L126

change /dev/block/platform/msm_sdcc.1 to /dev/block/platform/f9824900.sdhci on all the above lines.

This is the reason why I didn't release XZDR for the Z3+/Z4/TabZ4 yet, too much difference with the Shinano and older device trees.

That should be solved with 2.9 though...

---------- Post added at 03:15 PM ---------- Previous post was at 03:04 PM ----------

What OS do you run on your pc? Does windows register anything (even if it's just an unknown device) on the usb port?
[Xperia Z4/Z3+ General] AndroPlus:
Windows 10 and there's no unknown device.

I can connect my Z3 in TWRP, so maybe something is preventing loading of init scripts.
[Xperia Z4/Z3+ General] [NUT]:
Well, I suspect the USB device might also have a different name from the shinano hardware, which causes TWRP to mis configure the USB stack, or ignore it altogether...

See if you can find the USB root hub/controller in the ROM inside the /sys/class directory or a mention of the location in the init.usb.rc setup files (there should be at least one shell script being executed to set up the USB stack), see if you can find a device name there and then match that with the one in the kitakami repo's. The mention of this can be in either the device or the common repository.
[Xperia Z4/Z3+ General] Sacktreter:
[MENTION=410007]Nut[/MENTION]

its a pleasure for me to talk with the master (i smile)

i dont wanna open a new answer so i edit my answer, sorry but in future i answer in a new post. Please watch my second result, i changed the path and the log is without errors, but still no enter to recovery. I konw you can help.

Edit: as you told the version 2.8.1 is needed update to version 2.8.21, now i understand and I wait. Sorry for my bad english, german is my favorite language
[Xperia Z4/Z3+ General] [NUT]:
I saw your edit before, just post a new reply if you have any updates, makes it easier to track progress :)

In your USB driver inf file, you should remove &MI_00 from the device ID lines, this makes it match anything which starts with VID_18D1&PID_4EE2

https://github.com/xNUTx/XZDualReco...y/files/adbdrivers/android_winusb.inf#L28-L40

I'm not saying to use the ID's from this inf file, because this driver is meant for the ID's I am using in the recoveries for the 'official' XZDR releases.
[Xperia Z4/Z3+ General] DHGE:
init.kitakami.usb.rc

[MENTION=410007]Nut[/MENTION]

see attachment from my karin_windy AOSP build
[Xperia Z4/Z3+ General] [NUT]:
[MENTION=5169444]AndroPlus[/MENTION] scrap that search, I think something else is wrong. Seeing the usb config posted by [MENTION=6774113]DHGE[/MENTION] and the init in the aosp repositories I think twrp might be crashing when it finishes loading. Though the log you provided doesn't specify this (restart counter), it does seem to restart at some point...
[Xperia Z4/Z3+ General] venkat kamesh:
thank you [MENTION=6902252]Sacktreter[/MENTION] for testing the recoveries and for the log

Thanks for the suggestions [MENTION=4904057][NUT][/MENTION]

i will look into them ;)

i am not expert, i am learner

your commits and codes teach me a lot....

as you said mate, Z3+ was completely different from other z devices :p

and yes i will change to 2.8.21

3 more hours left for me to reach home :p

once i reach home i would look up my source and will push to git

hope you can help me for this mate :)
[Xperia Z4/Z3+ General] Syndikats:
It does not work , even it does not go .
[Xperia Z4/Z3+ General] AMoosa:
I'm a power user but not a developer. Desperately waiting for XZDR on my Z3+. I'm carrying on using my Z3 In The meantime. Let me know if there's any testing or anything I can do to help. Good luck guys.

Sent from my Xperia Z3
[Xperia Z4/Z3+ General] Sacktreter:
venkat kamesh is working to build a recovery, he need time for that. When results are given I'm sure he's posting here.
[Xperia Z4/Z3+ General] [NUT]:
[MENTION=4433143]venkat kamesh[/MENTION]

Any updates?
[Xperia Z4/Z3+ General] AndroPlus:
Can anyone build with new flag "TW_IGNORE_ABS_MT_TRACKING_ID"?

I can't build right now, but this is interesting...

https://github.com/omnirom/android_bootable_recovery/commit/d6821a11bb6d664283ae96030044270ad68eaed0
[Xperia Z4/Z3+ General] [NUT]:
Unfortunately I am still building using a CM repository, I still need to make the switch to AOSP repos on my build system...

Sooo.... [MENTION=4433143]venkat kamesh[/MENTION], over to you :)
[Xperia Z4/Z3+ General] venkat kamesh:
Testings :)

Hello [MENTION=4904057][NUT][/MENTION]

its already in progress ;)

[MENTION=6902252]Sacktreter[/MENTION] is testing my builds

once it got worked

i will expose all my work mate :)
[Xperia Z4/Z3+ General] AMoosa:
I'm hoping you have a solution to root and keep a locked bootloader. Fingers crossed and good luck.
[Xperia Z4/Z3+ General] hasona:
Just wanted to pop in and say awesome work from you guys! I really hope I can get my hands on LB ROOT soon, if you need anyone to test out on locked bootloaders later on hit me up and I will try to help out if I can free up some time! :D
[Xperia Z4/Z3+ General] AMoosa:
Me too. Happy to help testing wherever you need it.
[Xperia Z4/Z3+ General] venkat kamesh:
Recovery work / source

[MENTION=4904057][NUT][/MENTION] i need some help in between

i had just pushed my sources to git

most of the changes were by [MENTION=5169444]AndroPlus[/MENTION]

Here is my sources

Device : https://github.com/venkatkamesh/android_device_sony

Vendor : https://github.com/venkatkamesh/android_vendor_sony

Qcom (tipos) : https://github.com/venkatkamesh/android_device_qcom_sepolicy

presently twrp ( not sure how its working )

its getting hard for me without device

but i will help all i can do.......... i need help so we can carry on work ;)

if any one want to try ( Only for z3+/ivy device ) http://d-h.st/qS97 ( hope only built twrp,,,, test versions, tomorrow philz )

get me quick report ;)

best regards
[Xperia Z4/Z3+ General] [NUT]:
I'd like a log from the latest build though, without it I can't help much...
[Xperia Z4/Z3+ General] AMoosa:
What's an Ivy device? Will this work on locked bootloader?

Sent from my Xperia Z3+
[Xperia Z4/Z3+ General] [NUT]:
FYI: https://en.wikipedia.org/wiki/Sony_Xperia

And, no, this won't work on unlocked bootloader, as there is no root for that yet, which simply implies it needs to be unlocked to obtain root.
[Xperia Z4/Z3+ General] chrisss5000:
I will test it when I get home later today! :)

---------- Post added at 12:12 PM ---------- Previous post was at 11:39 AM ----------

So I will just set the phone in fastboot mode ( I have unlocked bootloader and root)

and type "Fastboot flash recovery" in cmd and then drag the file into cmd and hit enter? or does this recovery come as a boot file?
[Xperia Z4/Z3+ General] [NUT]:
Neither.

If you unlocked the bootloader, make sure you have root (the autoroot kernel is a good place to start).

Then install it using a PC/Mac, this recovery package integrates in to the system partition and is officially meant for locked bootloader devices, but during development this is easier to use as this makes it easier to update the recoveries as you can just copy in a new recovery archive, even without a PC.
[Xperia Z4/Z3+ General] chrisss5000:
its sais it cant recognize adb but I have usb debugging on?
[Xperia Z4/Z3+ General] chrisss5000:
Ehhm something is wrong with the recovery.....I successfully installed it. BUT there is a stop..

Everything boots up well but as the green little light turns on i pushed volume up and then a purple light shows for a sec and then nothing more happens than it got stuck at Sony Xperia start screen...I've tested volume down too..same thing there..

My device can boot up normally tho! No bootloop!

I know how to boot into recovery I have done it like 100000x at my xperia z3. '

Anyway the phone works well without any issues! Just cant boot into recovery mode yet!
[Xperia Z4/Z3+ General] [NUT]:
Can you flash the stock kernel and see if full root survives?

And please attach the logs. Please try to enter recovery by using the app, then reboot and copy the xzdualrecovery logs.

Then reboot and try to enter recovery using the volume rockers. Again, reboot and copy the xzdualrecovery logs.

Did you install the latest version [MENTION=4433143]venkat kamesh[/MENTION] put online?
[Xperia Z4/Z3+ General] venkat kamesh:
Great thanks for testing

I got something to change with source

I will update it

And will provide new recoveries....

Some one said king root app worked to root

Root will help to take drmkeys back up

Can any one with locked bootloader try king root ?

If so just ping me up mates
[Xperia Z4/Z3+ General] chrisss5000:
I will test flashing stock kernel later today after work!

Where can I find stock kernel? In flash tool?? I have the autoroot kernel now!

Yes I installed latest version! The one he putted out 29/8-2015!

I tried to do it via the app! Same issue! Stuck at Sony Xperia screen! (Phone working normaly, no bootloops)!

If you guys succed to make this work I would be more then glad to help you test it and put out the logs!

---------- Post added at 04:57 AM ---------- Previous post was at 04:53 AM ----------

Something thats weird is that I still have awesome quality even with UNLOCKED bootloader! And I rooted it via autoroot kernel! Works awesome!!

I think I tried the kingroot with locked bootloader but it gave me no root..so I unlocked my bootBL to root via autoroot kernel and be prepared to test custom roms and recoveries! :D
[Xperia Z4/Z3+ General] [NUT]:
You might not have a working recovery yet, but the package installed anyway.

Please follow my guide to gather the logs and test for full root on stock kernel, you can use the FlashTool and FTF to flash just the kernel. The logs are either in /cache/XZDualRecovery or on your external sdcard /sdcard1/XZDualRecovery and please perform the test on the stock kernel.
[Xperia Z4/Z3+ General] airlessproject:
I just tested, neither latest kingroot nor towel work on LB :(

kingroot says no strategy yet, towel just hangs doing nothing
[Xperia Z4/Z3+ General] chrisss5000:
I have tested both...the map is empty, no logs!

I'll test the stock kernel with root later! I belive we have different timezone, here in sweden it is 10:14 AM.
[Xperia Z4/Z3+ General] [NUT]:
Same timezone. I work in IT :)

Just telling you what to do, not when ;)
[Xperia Z4/Z3+ General] chrisss5000:
Haha nice! Okey! Just thought that you maybe wanted to know..so you dont wait all day long for me to test it ?
[Xperia Z4/Z3+ General] [NUT]:
[MENTION=6902252]Sacktreter[/MENTION] thanks for all the info, you made a remark about the kernel module... You might be right there...

I do have one question... Did you flash the stock kernel or did you try this all using the autoroot kernel?

If so... Could you please give it one more (and gather the logs but just from one attempt, using only one volume rocker) try using the stock kernel?

I'll see what I can do about the kernel module on short notice...
[Xperia Z4/Z3+ General] Sacktreter:
Hi [MENTION=410007]Nut[/MENTION],

I tried many things to get root, at the end many chinese apps were in my phone and chrome was displayed in chinese language. I was not sure if I'm still the master of my phone or whether i have to learn chinese language. After many test's i prefered to unlock the bootloader.

I used XperiFirm to download Firmware and via Flashtool i build this E6553_o2 DE_1296-2974_28.0.A.7.24_R8A.FTF. I flashed the phone completely and checked all 3 wipe options in Flashtool's Flashmode.

restart the phone without internet connection, then i used Fastboot mode in Flashtool and the option "Reboot into fastboot mode (via Fastboot)". I flashed the boot.img getting from this site auto root kernel. After that restart I restart the phone and it was rooted.

I do test for you and later i report.
[Xperia Z4/Z3+ General] AMoosa:
Have you tried xposed yet? Does it work?

Sent from my Xperia Z3+
[Xperia Z4/Z3+ General] Sacktreter:
Hi [MENTION=340246]AMoosa[/MENTION]

this is my target, but without recovery i cant flash zip files. The framework for xposed i only can install in recovery mode. This is one thing i want to get recovery mode and I'm sure sooner or later we get it. :D :laugh:
[Xperia Z4/Z3+ General] ChrisJ951:
Xposed bootloops when flashed (I tried the 64bit 5.0 version)
[Xperia Z4/Z3+ General] [NUT]:
Thank you for all the testing... But you made it more complicated then I meant you should ;)

Use flashtool to flash the entire kernel, not just the ramdisk :D

Just the kernel, nothing else :good:

the reason is simple:

The autoroot kernel disables a lot of the security features, which xzdualrecovery also tries to disable. I want to make sure you will still have full root and can boot without problems.

Once we know that all works, we can conclude the recoveries SHOULD work without issues if the recoveries are built correctly.

Eliminating one possible reason for the recoveries to fail at a time :)
[Xperia Z4/Z3+ General] DHGE:
file corrupt?

[MENTION=6902252]Sacktreter[/MENTION]

md5sum kernel_S1-SW-LIVE-F936-PID1-0005-MMC.sin
b539817e16051c158f5af705c1438e43 kernel_S1-SW-LIVE-F936-PID1-0005-MMC.sin

Works here on my Z4 Tablet, from the original SONY DL

Maybe your sin-file is corrupt?

You can not flash an elf file.

Flashtool Version 0.9.19.0 is the best for our devices - OK at your side.
[Xperia Z4/Z3+ General] Sacktreter:
Yes @DHGE

i use flashtool 0.9.19.0 and works fine.

md5sum kernel_S1-SW-LIVE-F936-PID1-0005-MMC.sin
0756ca8992afc836e9d8f72defadd26e kernel_S1-SW-LIVE-F936-PID1-0005-MMC.sin

:confused:I think you are right with md5sum. But keep in mind - I have Z3+ E6553 phone. I download again these files and take a look.

And yes now i know i can't flash an elf file, but i tried for good luck. :)

______________________________

edit because brain is working

Could it be an other checksum coz i use firmware by o2 germany?
[Xperia Z4/Z3+ General] [NUT]:
The funny thing is, you confirmed our already existing suspicion on the kernel module.

Wait with further testing until I have a new module for you.
[Xperia Z4/Z3+ General] addicted1900:
I am really thankful for you guys who are developing and also the ones who are doing the testing stuff. Really nice work!

Gesendet von meinem E6553 mit Tapatalk
[Xperia Z4/Z3+ General] AMoosa:
Guys, keep up the good work. I hope we get to a locked bl root solution soon. I'm really grateful for your hard work.

Sent from my Xperia Z3+
[Xperia Z4/Z3+ General] [NUT]:
With big thanks to [MENTION=4712883]McBane87[/MENTION]:

ByeSELinux for ARM64:

https://mega.nz/#!idQ2BIya!30MTco7iY9zruIVXNpSFVEgBqXIueRV7KkVMx3zy5Lc

Hope it works ☺
[Xperia Z4/Z3+ General] Sacktreter:
:crying: After more tests, always the same (Lollipop 5.0.2)

Module found, loading it now...
Loading the module failed with exit code 1

I was more times testing, sorry. I preciate your hard work. Dont give up. :)
[Xperia Z4/Z3+ General] [NUT]:
I hate it that I'm unable the purchase the device myself... It would make debugging a lot easier...

If there is a Dutch reader here with a Z3+ with the bootloader unlocked, I would like to borrow it for a few days up to a week... I have a Z1 which I have only for recovery development testing as a temporary replacement.

[MENTION=6902252]Sacktreter[/MENTION] Can you flash a clean rom (no root, no recovery) using the ftf you have now.

Then flash the autoroot kernel to get root access. After that try to install recovery again, with the new byeselinux module placed in the files/byeselinux folder.

Copy the contents of the installer CMD window and attach that here.

That will be all for now.
[Xperia Z4/Z3+ General] Sacktreter:
yes i do. I use the version Lollipop 5.0.2. This story slowly has to get an end.
[Xperia Z4/Z3+ General] Sacktreter:
HI [MENTION=410007]Nut[/MENTION],

success, module is loaded and works. first step is done. :o :o :o. Logfiles are coming soon.
[Xperia Z4/Z3+ General] thienbrand:
Sorry for being a noob, but what are you focus right now ? Is it locked bootloader root? :p
[Xperia Z4/Z3+ General] Sacktreter:
[MENTION=1818980]thienbrand[/MENTION]

not at all, we try to get recovery first for unlocked bootloader, later for locked. Step by step.

NUT, here are your logfiles. Well done bro. Now i concentrate to get recovery screen. :o :D :o :)
[Xperia Z4/Z3+ General] McBane87:
So the new Module worked? Great.

But what about other binaries used by installer like "modulecrcpatch". Because this binary is compiled for "normal arm".

I'm curious if it is working on arm64.
[Xperia Z4/Z3+ General] [NUT]:
Well, one more test to do:

Flash the stock KERNEL ONLY from the rom ftf and see if you can still boot and if you still have full root access (which means you should be able to remount system rw and also be able to put a file there).

Once we know THAT works, we will move on to the next thing to fix.

---------- Post added at 10:22 PM ---------- Previous post was at 10:18 PM ----------

Executables should actually work fine but the kernel has special needs as it really uses the 64 bit architecture. The 64 bit system is backwards compatible when it comes down to binaries.

Modulecrcpatch is clearly able to handle 64 bit address spaces itself :)
[Xperia Z4/Z3+ General] Sacktreter:
Now i flashed phone in all posibility variants with autoroot and back to Stock without toolbox installed... always bootloop.

During this processes 4 drivers were used, maybe some need this information.

[COLOR="SeaGreen"]# Device - in Device Manager as a sub of portable devices (Tragbare Geräte)
# Displayed Name[/COLOR]
Xperia Z3+
[COLOR="SeaGreen"]# Device description[/COLOR]
E6553
[COLOR="SeaGreen"]# Hardware-IDs[/COLOR]
USB\VID_0FCE&PID_51C9&REV_0310&MI_00
USB\VID_0FCE&PID_51C9&MI_00
[COLOR="SeaGreen"]# Kompatible IDs[/COLOR]
USB\MS_COMP_MTP
USB\Class_ff&SubClass_ff&Prot_00
USB\Class_ff&SubClass_ff
USB\Class_ff

[COLOR="SeaGreen"]# Device - in Device Manager as a sub of portable devices (Tragbare Geräte)
# driver is installed, but always displayed with a yellow exclamation mark "can't activate Device"
# Displayed Name[/COLOR]
MTP-USB-Gerät
[COLOR="SeaGreen"]# Device description[/COLOR]
MTP-USB-Gerät
[COLOR="SeaGreen"]# Hardware-IDs[/COLOR]
USB\VID_0FCE&PID_01C9&REV_0310
USB\VID_0FCE&PID_01C9
[COLOR="SeaGreen"]# Kompatible IDs[/COLOR]
USB\MS_COMP_MTP
USB\Class_FF&SubClass_FF&Prot_00
USB\Class_FF&SubClass_FF
USB\Class_FF

[COLOR="SeaGreen"]# Flashtool uses in Flashmode
# Device - in Device Manager as a sub of USB-Controller
# Displayed Name[/COLOR]
SOMC Flash Device
[COLOR="SeaGreen"]# Device description[/COLOR]
SOMC Flash Device
[COLOR="SeaGreen"]# Hardware-IDs[/COLOR]
USB\VID_0FCE&PID_ADDE&REV_0100
USB\VID_0FCE&PID_ADDE
[COLOR="SeaGreen"]# Kompatible IDs[/COLOR]
USB\Class_FF&SubClass_00&Prot_FF
USB\Class_FF&SubClass_00
USB\Class_FF

[COLOR="SeaGreen"]# Flashtool uses in Fastboot mode
# Device - in Device Manager as a sub of Android Device
# Displayed Name[/COLOR]
Sony ADB Interface
[COLOR="SeaGreen"]# Device description[/COLOR]
Sony ADB Interface
[COLOR="SeaGreen"]# Hardware-IDs[/COLOR]
USB\VID_0FCE&PID_0DDE&REV_0100
USB\VID_0FCE&PID_0DDE
[COLOR="SeaGreen"]# Kompatible IDs[/COLOR]
USB\Class_FF&SubClass_42&Prot_03
USB\Class_FF&SubClass_42
USB\Class_FF

[MENTION=4433143]venkat kamesh[/MENTION], I didn't forget you, but i flashed and stressed my Z3+ so often at the end my SDCard extern was also flown away in a moment without concentration. How far are you with work??
[Xperia Z4/Z3+ General] venkat kamesh:
Thanks bud..... ;)

i actually found something after you sent me rootfiles

i had some changes ( take a look here )

since i was busy these days i was unable to participate :p

i will send you new files

i have read all your logs

Thank you for your patience

[MENTION=4904057][NUT][/MENTION] thank you for module

lets see how sure it gonna work
[Xperia Z4/Z3+ General] dl12345:
Flashing the stock kernel won't work as it uses CONFIG_DM_VERITY and a verity key on the ramdisk and so needs an unmodified ROM otherwise the check fails and the kernel panics
[Xperia Z4/Z3+ General] [NUT]:
I did not check the kernel config for the ivy yet, and I didn't know this feature... I've been reading up on it and this might very well kill locked bootloader recovery altogether:

(source) https://source.android.com/devices/tech/security/verifiedboot/index.html

This has been implemented by Sony in their kernels and makes RIC as service and their RIC kernel protection look like child's-play... :eek:

Unless there is a switch to throw using a kernel module ( like wp_mod.ko does on RIC ) to make the kernel accept the failed hash check and make it not panic (and with that, not reboot), there is no way around this.

[MENTION=3975929]zxz0O0[/MENTION]
[MENTION=2011359]MohammadAG[/MENTION]
[MENTION=2784807]DooMLoRD[/MENTION]

We need your help guys...
[Xperia Z4/Z3+ General] DHGE:
we might need the source for init

[MENTION=410007]Nut[/MENTION]

I have greped the sources for kernel .31

It is in there - OK. But it has to be implemented (where are the hashes? - not in kernel land) and called.

I have compiled the .31 source with only RIC disabled and everything is fine here - even with SELinux.

I found a thread on xdadevelopers where one guy patched the init binary to disable some checking by SONY.

I am waiting for the .251 sources to get this release working as root again (with SELinux, not Androplus kernel).

There is also init.rc and its includes where one could do some finetuning.
[Xperia Z4/Z3+ General] [NUT]:
When does the bootloop occur? Does it happen at the boot animation or before that? Do you still see the green LED and feel the vibrations before it reboots?

Can you extract the kernel.sin and attach it here, I want to inspect it a bit (you can open the FTF using winrar or winzip, it's effectively a zip file, and just attach the sin file here).

---------- Post added at 11:03 AM ---------- Previous post was at 11:00 AM ----------

Then we will be updating wp_mod.ko as well with a 64bit version....
[Xperia Z4/Z3+ General] McBane87:
Hey guys,

I tired to compile the wp_mod.ko Module for ARM64. PLease try first if it is loading and second if it helps with the current problem.
[Xperia Z4/Z3+ General] [NUT]:
Thanks for the help buddy.

[MENTION=6902252]Sacktreter[/MENTION] this time you need to update wp_mod.ko in the installer files directory as well, replace any of them you can find with this one.

Then again, flash the stock system partition and the autoroot kernel, install XZDR and see if it all works.
[Xperia Z4/Z3+ General] zxz0O0:
Can you add a dmesg to the log after loading the kernel modules? Also try to dump the kallsyms

su
echo 1 > /proc/sys/kernel/kptr_restrict
cat /proc/kallsyms

That will not work because it has 32bit bytecode.
[Xperia Z4/Z3+ General] monx®:
i can smell root on LB once [MENTION=3975929]zxz0O0[/MENTION] passby :)
[Xperia Z4/Z3+ General] McBane87:
OK, thanks for advice. Was just building it.... Don't know how to rework code to make it work.
[Xperia Z4/Z3+ General] zxz0O0:
It's more compilcated since aarch64 instruction set can not store immediate values to pc register. But shouldn't be impossible ;)