yashsingh1/xdaforums huggingface dataset:
[Xperia Z5 Compact Q&A, Help & Troubleshooting] klausstoertebeker:
Hello!

I wrote the following email to Sony Developer World, but they asked me to post it here.I don't know why I should do this because this page is not meintained by Sony. But hoping that Sony will give me a definitive answer I do as they asked me for:

[start of email]

I haven’t understood your risk explanation on your „Unlock your boot loader“ page because to my mind it is a little bit unprecise:

You wrote there:

“Risks

Please be aware that Sony cannot guarantee the full functionality, and will not be responsible, for any unsigned custom ROM being flashed to your device after the boot loader is unlocked. An unsigned custom ROM may not have gone through the thorough tests that we run for each device and software version that we release.

Also, a custom ROM might not work properly on your device, and certain functions and offerings may cease to work. The performance of the device might also be affected, and you may damage your device permanently. In worst case, unlocking the boot loader will cause physical injuries or material damage, for example, due to the device overheating.

Certain pre-loaded content on your device may also be inaccessible due to the removal of DRM security keys.

For high-end devices running recent software versions, for instance Xperia Z3, the removal of DRM security keys may affect advanced camera functionality. For example, noise reduction algorithms might be removed, and performance when taking photos in low-light conditions might be affected. The secure user data partition may also become inaccessible, and you will not be able to get any more official software upgrades if you unlock the boot loader.

After unlocking your device, you should not enable My Xperia (found in the settings menu under security on some devices running Android 5.0) as this might cause the device to malfunction.”

I don’t understand the red marked sentence. So my question concerns the removal of the DRM security keys because I haven’t found out who and when they are removed:

WHO removes the DRM security keys? Is it done by SONY when unlocking the bootloader (and why do you do that?) or is it a risk caused by installing custom ROM’s or recovery images?

And what will happen if I’ll unlock the bootloader of my Sony Xperia Z5 compact via the integrated function “OEM unlock”? Will the DRM security keys deleted any way using this or will they be preserved? And will I be able to lock the bootloader again?

Regards

Ansgar

[end of email]
[Xperia Z5 Compact Q&A, Help & Troubleshooting] nilezon:
It's done automatically if you unlock the bootloader, i.e. "by Sony".

The DRM keys will be erased.

Most likely, but the DRM keys cannot be restored. They are forever lost.
[Xperia Z5 Compact Q&A, Help & Troubleshooting] basthet:
sorry, that's bull****.

remove the bootloader lock in developer settings and you will see, that Marlin, Widevine and CKB are still active and reported as "key ok"

and no, Sony does not remove them, you do it while flashing.

BTW. there are already early attempts in flashing, and yes they have deleted their DRMs. and no, there is no way to bring them back.

however, for the time being: keep the bootloader closed, as you've no benefits from unlocking it, yet.

Gesendet von meinem E5823 mit Tapatalk
[Xperia Z5 Compact Q&A, Help & Troubleshooting] nilezon:
Dude, you should relax. There's no manure in my post.

You have misunderstood the toggle in the developer settings menu. It does NOT unlock the bootloader.

The toggle only disables some software features that would cause trouble if you actually choose to unlock the bootloader.

Bootloader in unlocked using fastboot oem unlock, as always.

Please read up:

http://xdaforums.com/showpost.php?p=63216335&postcount=23

http://xdaforums.com/showpost.php?p=63216352&postcount=24

http://xdaforums.com/showpost.php?p=63343765&postcount=33 (quoting you)

http://xdaforums.com/showpost.php?p=63299154&postcount=17
[Xperia Z5 Compact Q&A, Help & Troubleshooting] basthet:
Well, I'm relaxed, but you help no-one in posting wrong stuff.

Lets make it simple:

Compare it with a simple door and a door guard.

The door guard has order only to let you in, having a specific key.

In order to get this key, e.g. for the z3 family:

Go to Sonys webpage, register, download the key.

procedure for the z5c:

go into developer settings, enable: OEM unlock.

This corresponds to: Tell the guard, no key is required anymore.

Setting the flag of making something accessible is called "unlock" - so: in fact you can call it "unlock the boot loader" by enable the "OEM unlock" in Developer Settings*.

fastboot oem unlock does much more.

In my example:

go to the door,

ask the guard: is door open / already unlocked?

[z3c: handover the key to the guard]

[z3c: Wait to get the "Ok" to pass - guard: unlock the door] -> correspond to: setting flag: accessible = unlock

pushing the door open,

hanging a fat note in the entrance hall telling "Door is open";

So: you did not miss understood what the toggle does, but the whole procedure.

And no: the toggle does not disable some software feature, it just removes the OEM specific key requirement by accessing the boot loader

*Note: I know, that was quite rough simplification, and to be absolute correct: the OEM unlock toggle in Dev. Setting does in fact not physically "unlock" the boot loader. It just removes the requirement for a key in the unlocking process. However, that correspond to an open boot loader, as all attempt to enter it, will not be denied.
[Xperia Z5 Compact Q&A, Help & Troubleshooting] nilezon:
I can't argue with you. I'm not even sure where we agree and disagree.

For the sake of other users, here's the clarification:

Under Developer settings, there is a setting called "OEM Unlocking - Allow the bootloader to be unlocked".

This setting does not unlock the bootloader, it just enables the possibility to unlock. That's why it's called "Allow the bootloader to be unlocked".

No DRM keys will be deleted by toggling this setting.

After setting "Allow the bootloader to be unlocked", you can unlock the bootloader using fastboot.

When doing so, the DRM keys will be deleted and the bootloader will be unlocked.

Until you issue the fastboot command, you can't flash any unsigned code - as usual.
[Xperia Z5 Compact Q&A, Help & Troubleshooting] basthet:
We are not arguing here :)

I asked you to be more specific as unlocking a door does not mean opening it.

However - there is one important thing missing and quite profound error in your summary (beside the "unlock" wording stuff...).

Enabling the "OEM Unlocking" switch bears a high security risk. Unsigned software now can enter the TA.

In fact: you do not have to run the fastboot unlock by yourself. Any piracy software can now make irreparable damages to the phone!
[Xperia Z5 Compact Q&A, Help & Troubleshooting] nilezon:
You are saying that toggling the "OEM Unlocking" switch would make TA partition writeable (by any other user than root)?

Why would you assume that?
[Xperia Z5 Compact Q&A, Help & Troubleshooting] basthet:
No, I'm not saying this.

But the reason for the OEM Lock is to ensure, only OEM signed software is able to be installed.

Enabling "OEM Unlocking" removes this check.

This implies:

- Nice people can now provide software to be installed -> custom roms.

- Bad people can now also install software, but to their needs.

To keep it simple: Let some evil person post any rom called "official Sony z5c Android 6.0".

Let this bad person make the appearance of this rom as any official Sony Update.

Users with the OEM lock in place will not be able to install it, as the OEM key from Sony is missing.

Users with the OEM lock removed will install it w/o any burden.

Do not forget:

Original OEM Software still is signed as original software.

To install the original software, you do not have to toggle the "OEM unlock" in the Developers Settings, as this ROM carries the original OEM key.

to install original software, you do not have to fastboot oem unlock

Removing the OEM-key check with the "OEM unlock" switch, makes the OEM-key obsolete. Hence bears a security risk.
[Xperia Z5 Compact Q&A, Help & Troubleshooting] nilezon:
OMG dude. Where are you getting this?

You toggle that switch and install an unsigned ROM and I'll eat my shorts.
[Xperia Z5 Compact Q&A, Help & Troubleshooting] basthet:
You either learn this in school, or should find it s.w. in the Android docs.

And instead of flaming you should start reading and learn IT.

So be brave and toggle the switch, which by your interpretation has no meaning.

The rest of the user i can only advice to keep it locked and only enable in order to flash customs Roms.

Gesendet von meinem E5823 mit Tapatalk
[Xperia Z5 Compact Q&A, Help & Troubleshooting] klausstoertebeker:
[MENTION=990850]basthet[/MENTION]:

So, if I get you right, I just need a customized firmware (e. g. a pre-rooted one), toggle that "OEM unlock" switch and install it via recovery mode? And that without loosing DRM keys? If it is so easy rooting is no problem, isn't it?
[Xperia Z5 Compact Q&A, Help & Troubleshooting] AndroPlus:
No, "OEM Unlock" is just a option to allow OEM unlock, so you have to unlock bootloader after enabling it (and you'll loose DRM key)
[Xperia Z3 Compact Q&A, Help & Troubleshooting] Fryktlaus:
Hi.

I managed to make an NFC tag for WiFi handover with my Nexus5 running Android 6, Marshmallow.

The "tap-to connect" works on my N4 and N5, it works with my friends Xperia Z5 and Galaxy Edge.

But the Xperia Z3 compact with stock Android 5.1.1 (the latest live update), fails while reading the NFC tag.

Anyone else with similar experience? And how did you solve it?

Attached images shows how i created the NFC sticker with N5, and the result while reading it with my Xperia.
[Android General] patriotaki:
Oneplus X​

The new oneplus device has been announced here is a leaked picture

at the time i found only these specifications

4.99-inch touchscreen

2,450 mAh

dimensions are said to be 140 x 69 x 6.9 mm,

if anyone knows more details please share with me
[Android General] Rawwrius01:
1920 x 1080 / 5,5"

401 dpi

2gb RAM

Helio x10 processor

Oxygen os 3.0

2540 mhA battery

Clearforce

Rumor: https:// curved.de/news/oneplus-mini-amazon-seite-soll-namen-und-specs-bestaetigen-310470

Gesendet von meinem Nexus 5
[Android General] Krystyna:
OnePlus X specs: http://www.gizok.com/oneplus-x.html
[Android General] patriotaki:
i found it for 300$ on geekbuying.. is it worth it?
[Android General] unlethal:
If there is NFC, and is very cheap, this could be a better deal than the Oneplus Two...
[Android General] kjell123456789:
just a cheaper version of the oneplus 2

but it would be nice if it had nfc
[Android General] patriotaki:
Where do you guys use nfc for? I rarely use it
[Android General] frankandwendy:
Oneplus X is Oneplus Mini?
[Android General] kjell123456789:
for mobile payments it would be nice so you don't need a credit card only a smartphone
[Android General] patriotaki:
https://www.youtube.com/watch?v=gKdJaWFYVBU
[Android General] adityaduggal:
I dont really see the reason why they are releasing X when 1+2 is working fine.
[Galaxy Note 3 Q&A, Help & Troubleshooting] highka02:
Anyone know if samsung has them planned?
[Galaxy Note 3 Q&A, Help & Troubleshooting] ithehappy:
No. This is asked by others many times too. Keep an eye on sammobile, cause if there is any chance of Note 3 getting Marshmallow then chances are high they will be the first to post it. I am just waiting for 5.1.1 anyway. I won't mind if a two year old flagship doesn't get Marshmallow.
[Galaxy Note 3 Q&A, Help & Troubleshooting] emuandco:
CM/AOSP always has a new Android for you ^^ After Samsung takes longer and longer to fix stuff and Stagefright etc on older phones, I went to Temasek's ROM. Works perfectly.

AAND it seems like ppl started to port Note5's ROM to Note 3 too....
[Galaxy Note 3 Q&A, Help & Troubleshooting] ithehappy:
Good for you then :o
[Xperia Z5 Compact Original Android Development] Tommy-Geenexus:
Zombie is a Kernel which extends the Xperia Z5C's capabilities.

It is aimed at including

only useful and strictly tested features, enhancements and optimisations

,

Important: I do not accept Bug reports when you are running a modified Rom or using Xposed!

Changes compared to Stock-Kernel:

* Important bug fixes / security patches

* CPU-Speedbin visible in debugfs node (sys/kernel/debug/msm8994_cpuinfo/*Speedbin)

* Underclocked both Cluster to 1,344/1,536 GHz respectively

* Custom brightness scaling (reduced min. brightness, increase max. brightness)

* Hold Power-Button for 5 seconds to reboot into bootloader

Security Patch-Level: November

Todo:

* -

App to check your device's Panel Manufacturer:

SonyKitakamiPanelInfov1.0 Download

Downloads:

Kernel Zip Package:

Latest Build: Zombie-b9

Installation:

* Unpack ZIP and flash Kernel via Fastboot

Sources:

Zombie-MM Kernel Source at Github

PanelInfo-App Source at Github

XDA:DevDB Information

Zombie, Kernel for the Sony Xperia Z5 Compact

Contributors

Tommy-Geenexus

Kernel Special Features:

Version Information

Status: Testing

Created 2015-10-13

Last Updated 2016-11-12
[Xperia Z5 Compact Original Android Development] Tommy-Geenexus:
Reserved

// nothing to see here
[Xperia Z5 Compact Original Android Development] bubimir13:
Great, hope there will be a continous work on these thingies as this device is rather new and we need every bit that can help. Even for Locked Bootloaders...
[Xperia Z5 Compact Original Android Development] nilezon:
Since it is insecure (ro.secure=0), will adbd run as root?
[Xperia Z5 Compact Original Android Development] Tommy-Geenexus:
Nope, it needs also ro.debuggable=1 and a modified adbd binary in ramdisk.
[Xperia Z5 Compact Original Android Development] nilezon:
Thank you.

I guess it would be easier to just drop a "rootsh" shell binary in ramdisk with setuid and root owner (chmod 4750) ?

I need that root shell :)

Edit:

I'm trying to compile your kernel but am getting a weird error:

CC mm/filemap.o
mm/filemap.c: In function 'grab_cache_page_write_begin':
mm/filemap.c:2306:1: internal compiler error: Segmentation fault
}

Using aarch64-linux-android-4.9 toolchain from Google.

Do you have any pointers for me?
[Xperia Z5 Compact Original Android Development] Tommy-Geenexus:
One could implement su and all needed files in the ramdisk and copy them over, however i'd vote for someone to build TWRP.

I have not much experience in shell scripting, and having a working recovery would be the optimal solution.
[Xperia Z5 Compact Original Android Development] Tommy-Geenexus:
Had exactly the same issue.

I suppose you cloned the GCC from Google like me, just checkout the marshmallow branch, the master branch has some issues.

Otherwise i can upload my GCC (latest AOSP toolchain) and link it.
[Xperia Z5 Compact Original Android Development] nilezon:
Got it working using marshmallow-release branch.

THANK YOU!
[Xperia Z5 Compact Original Android Development] Tommy-Geenexus:
Np, feel free to contribute if you find any useful stuff, always good to have some dev's around.
[Xperia Z5 Compact Original Android Development] Joeisgood99:
Hey [MENTION=5243932]Tommy-Geenexus[/MENTION].

1.) Great work btw.

2.) Have you run

$. su
#. cat /proc/emmc

(or similar) On your Z5C yet?

Id love to know the partition lay out. Will speed along the development of a custom recovery. I would do this my self but I don’t have a Z5C yet.

3.) Have you attempted to/had any luck compiling your kernel with any tool chain other then GCC 4.9 from marshmallow branch?

Regards

Joeisgood99.
[Xperia Z5 Compact Original Android Development] AndroPlus:
You can use

/dev/block/platform/soc.0/by-name/***

if you need it for fstab.

https://github.com/AndroPlus-org/an...ob/TWRP-28.0.A.8.251-karin/rootdir/twrp.fstab

I posted test TWRP build for E6653 before in Z5 forum, but no one has interest....

http://x.andro.plus/1OrEQ7i

[EDIT] @nilezon

It's for E6653, but differences are only configs in default.prop and kernel modules in sbin in recovery ramdisk, so you can use it on other Z5/Z5C after editing codenames and lcd_density and overwriting kernel modules.
[Xperia Z5 Compact Original Android Development] nilezon:
Good job!

Does the E6653 recovery work with E5823, or could you recompile it for suzuran, please?

Edit [MENTION=5169444]AndroPlus[/MENTION]

Thank you. I'll get the Z5C in a few days and will take the recovery for a spin then.
[Xperia Z5 Compact Original Android Development] Tommy-Geenexus:
Not yet, but here is the output of "cat /proc/partitions":

major minor #blocks name

254 0 524288 zram0
179 0 30535680 mmcblk0
179 1 2048 mmcblk0p1
179 2 16384 mmcblk0p2
179 3 81920 mmcblk0p3
179 4 128 mmcblk0p4
179 5 128 mmcblk0p5
179 6 1 mmcblk0p6
179 7 1024 mmcblk0p7
179 8 256 mmcblk0p8
179 9 256 mmcblk0p9
179 10 1 mmcblk0p10
179 11 512 mmcblk0p11
179 12 512 mmcblk0p12
179 13 1536 mmcblk0p13
179 14 8 mmcblk0p14
179 15 1024 mmcblk0p15
179 16 1024 mmcblk0p16
179 17 1536 mmcblk0p17
179 18 1536 mmcblk0p18
179 19 256 mmcblk0p19
179 20 256 mmcblk0p20
179 21 128 mmcblk0p21
179 22 128 mmcblk0p22
179 23 1024 mmcblk0p23
179 24 1024 mmcblk0p24
179 25 512 mmcblk0p25
179 26 512 mmcblk0p26
179 27 1024 mmcblk0p27
179 28 1024 mmcblk0p28
179 29 65536 mmcblk0p29
179 30 32768 mmcblk0p30
179 31 32768 mmcblk0p31
259 0 65536 mmcblk0p32
259 1 1024 mmcblk0p33
259 2 512 mmcblk0p34
259 3 1 mmcblk0p35
259 4 512 mmcblk0p36
259 5 102400 mmcblk0p37
259 6 10240 mmcblk0p38
259 7 16384 mmcblk0p39
259 8 307200 mmcblk0p40
259 9 204800 mmcblk0p41
259 10 24182784 mmcblk0p42
259 11 5384192 mmcblk0p43
179 32 4096 mmcblk0rpmb
179 64 31166976 mmcblk1
179 65 31162880 mmcblk1p1

The names are missing, however from my first research there is no recovery partition (I guess thats what you're interested in).

Regarding TC'S, 4.8 did not work, 4.9 works fine, haven't tested anything higher though.
[Xperia Z5 Compact Original Android Development] shafiq01:
i saw this recovery in z5 forum, i've used android kitchen on windows to unpack and edited the lcd density etc in the default.prop and repacked file

but havent done anything to the kernel modules. dont know how to :)

anyway here's the thing i've done for now. it's the recovery i've played with

https://db.tt/tqhL9Qba
[Xperia Z5 Compact Original Android Development] Joeisgood99:
Hey thanks [MENTION=1262833]shafiq01[/MENTION]

But that link takes me to a picture of your settings menu.

Thanks [MENTION=5243932]Tommy-Geenexus[/MENTION] for the partition table! Thats a great help.

Are you able to get the partition names?

Regards

joeisgood99.
[Xperia Z5 Compact Original Android Development] nilezon:
Here is a repack of [MENTION=5169444]AndroPlus[/MENTION] TWRP.

Anyone with an E5823 and unlocked bootloader can try it out using:

fastboot boot recovery.img

I still have no phone, so it is not tested.

Download:

https://mega.nz/#!pgIy2bYR!G-Hemo8rZdh9GBG_hIQOxHnPhdweFZNGpcQdAWPT1t8

All credit to [MENTION=5169444]AndroPlus[/MENTION] !
[Xperia Z5 Compact Original Android Development] Tommy-Geenexus:
Screen is blank, ADB controls work though.

However mounting /data failed, something must be up with the twrp fstab.
[Xperia Z5 Compact Original Android Development] nilezon:
Thank you for testing.

I'll get the phone tomorrow and will fix the bugs then.
[Xperia Z5 Compact Original Android Development] shafiq01:
Joeisgood99 sorry, i uploaded to dropbox while battery on laptop was dying hehe... socopy wrong url

anyway, now i see nilezon has done it. so no reason to i also try :)

anyway a bit of topic (but then again we all aim to get root in the smartest way and avoid loss of drm at the same time)

have to wait a bit and see if we in some way can root before unlocking bl

i saw in another thread that if we flash userdebug dev firmware, then we could use adb commands such as 'adb remount' 'adb disable-verity' and then 'adb root'

i'll try to flash userdebug firmware first and see what outcome it gives, hence i have access to that :D but last time i didn't managed to pack it correctly in flashtool

but i will give it shot more
[Verizon Samsung Galaxy S6] eladios:
NOW ALL MY THEMES TOGETHER IN ONE THREAD,​

ACCESSED FROM THIS LINK​

http://xdaforums.com/android/themes/eladiosthemes-20-themes-apk-format-root-t3341840/post65961932#post65961932​
[Verizon Samsung Galaxy S6] eladios:
SCREENSHOTS STAR WARS:

SCREENSHOTS BLACKANDCOLORS:

SCREENSHOTS BLACKBLUENIGHT:

SCREENSHOTS THE LORD OF THE RINGS:

SCREENSHOTS BLACKTURQUOSE:

SCREENSHOTS DRAGON BALL:

SCREENSHOTS GAME OF THRONES:

SCREENSHOTS PUNISHER:

SCREENSHOTS FC BARCELONA:

SCREENSHOTS IOS 9:

SCREENSHOTS STAR WARS EPISODE VII:

​
[Verizon Samsung Galaxy S6] thrgk:
I have an s6 rooted but use flash for recovery and flashing. Can I just flash the zip via flash fire ?
[Verizon Samsung Galaxy S6] eladios:
Best flashes for recovery. I have not tried otherwise. Thank you.

SM-G928F By Eladios
[Verizon Samsung Galaxy S6] eladios:
New theme this week. BlackBlue.[emoji3] [emoji3]

edited by my
[Verizon Samsung Galaxy S6] eladios:
New topic posted in the first post. You can view the images. Thank you

SM-G928F By Eladios
[Verizon Samsung Galaxy S6] eladios:
Theme Lord of the Rings is finished. I hope this afternoon and is available in the Play Store. Greetings and thank you.

edited by my
[Verizon Samsung Galaxy S6] eladios:
3 NEW THEMES IN THE FIRST POST UPDATED

SCREENSHOTS THE LORD OF THE RINGS:

SCREENSHOTS BLACKTURQUOSE:

SCREENSHOTS DRAGON BALL:

[/CENTER]
[Verizon Samsung Galaxy S6] eladios:
Links of premium themes for the play store and the first post are available. Thanks and regards.

SM-G928F By Eladios
[Verizon Samsung Galaxy S6] eladios:
Two new themes this week. Game of Thrones and punisher. A greeting.

View attachment 3538410View attachment 3538411View attachment 3538412View attachment 3538413View attachment 3538414

EladiosThemes By S6 edge +
[Verizon Samsung Galaxy S6] eladios:
Two new themes already included in my application. premium and free. Game of Thrones and Punisher

EladiosThemes By S6 edge +
[Verizon Samsung Galaxy S6] eladios:
Here are all my themes, now an easier way to buy, with more payment options.

You only have to buy the item you like and immediately after payment is automatically sent you an email with the download link, download and install Theme and enjoy.

Please follow the detailed installation instructions in my new web www.eladiosthemes.com​

​

DOWNLOAD MY NEW SHOP:​

http://www.mediafire.com/download/cf6w3nyx8o83dwb/EladiosThemes_New_Shop.apk​

CLICK IMAGE

​
[Verizon Samsung Galaxy S6] eladios:
New theme Star Wars Episode VII. To celebrate the release. And what you have available in my store. Free and Premium. A greeting.

EladiosThemes By S6 edge +
[Verizon Samsung Galaxy S6] eladios:
December Offer Christmas. Pay 3x2 two themes of, 3€ get one € 1.50 free. watch it in my store. A greeting.

EladiosThemes By S6 edge +
[Verizon Samsung Galaxy S6] eladios:
New theme available in my online store. FC Barcelona. I hope you like it. A greeting.

EladiosThemes By S6 edge +
[Verizon Samsung Galaxy S6] eladios:
Good news comes the revolution of my subjects. From now on they will be installed as a any application in 2 minutes you will have in store samsung issues. No longer we need bases for them. Now they go under my own name and as if they were official themes. But most important of all. NO LONGER we NEED ROOT AND RECOVERY. for those who do not want to root the phone. I mean that mobile factory stock. Tested in S6. S6 edge and edge + factory stock. And it is working perfectly.

They are not yet available in my store because I'm adapting all my subjects. But I hope to have everything ready this week. So far I have adapted and Star Wars and Star Wars Episode VII. I'll report.

EladiosThemes By S6 edge +