yashsingh1/xdaforums huggingface dataset:
[Sony Xperia 1 Questions & Answers] munjeni:
He have fastboot access only! So he can perform oem commands (fastboot oem unlock 0xKEY)! 3 years old, yes, but sony phones functioning very similar, agree? Thing is very unclear what is happened with his phone, he say he flashed firmware from diferent device, thats strange too because firmware from diferent device is signed with diferent key, so strange thing is he succed in flashing that firmware, it messed something on his phone and gaved him no access to flash mode, only fastboot mode is available. Thing which he can do is to go to the sony site and reguest unlock key, by fastboot unlock his phone, boot an custom recovery and perform an slow and carefully restoration, I sugesting to ask somebody to give him DD partitions dump so to restore them on his phone. I don't understand what your mean "toggle OEM unlock" mean, sony phone never needed any toogle to perform unlocking, unlocking is done trought sony site (reguest unlock key) and trought fastboot oem unlock command phone gets unlocked, on sony phones (as I know) there is no need for "toggle OEM unlock". Even you can unlock phone by replacing drm trim area unit 0x1046B with unlock trim area unit 0x8B2, and finally change trim area partition unit hash, more info here https://xdaforums.com/crossdevice-dev/sony/dangerous-tool-trim-tool-t3516007 , so "toggle OEM unlock" is not need at all. To be honest "toggle OEM unlock" I saw for the first time, don't undrestand what you mean with that.
[Sony Xperia 1 Questions & Answers] Mackay53:
Sony will give you the code and the fastboot command but until OEM unlock is ticked it won't work.

More info here - XZ3 but same process for modern phones

https://www.teamandroid.com/2019/02/20/unlock-bootloader-sony-xperia-xz3/

It's a new layer of protection, think it was introduced in Oreo.

If it didn't have this option then anyone can steal the phone and unlock it and do what they want, with this method they can't unless they get access to the phone.

So no access no unlock bootloader
[Sony Xperia 1 Questions & Answers] munjeni:
This is for carier locked devices (status is NO). When status is YES bootloader can be unlocked in all cases. You misunderstand things from the link.
[Sony Xperia 1 Questions & Answers] Mackay53:
Have you got the phone? No

Have you unlocked the bootloader on the phone you don't have? No

Have I got the phone? Yes

Have I unlocked the bootloader on the phone that I have? Yes

You're the one who doesn't understand but that would make sense as you admitted you don't even have the phone
[Sony Xperia 1 Questions & Answers] munjeni:
Have I made newflasher without phone, yes! Have I addedd xperia 1 support to newflasher without phone, yes! Have I understand how thing working, yes. Can I be abble to make newflasher in case I not understand how things working?
[Sony Xperia 1 Questions & Answers] Mackay53:
Yes as unlocking bootloader is different to flashing firmware as I'm sure you are aware.
[Sony Xperia 1 Questions & Answers] munjeni:
"toggle OEM unlock" I'm believing you device was carier locked right? Bootloader status on your device was "no" right?
[Sony Xperia 1 Questions & Answers] Mackay53:
No it said yes. I always make sure it says yes when getting a Sony device as I always unlock the bootloader sooner or later.

If it says bootloader unlock allowed "no" then as far as I'm aware it can't ever be unlocked.

The carrier is not the OEM as the OEM is Sony

Anyway, back to the topic of helping the guy
[Sony Xperia 1 Questions & Answers] munjeni:
Than what is "toggle OEM unlock"? Can you provide link for how to toggle it? I never see something like that on xda, even not for needs for unlocking bootloader, I would be glad if you give me link which explains unlocking bootloader procedure which contain step "toggle OEM unlock", can you show link? And how you toggled it?
[Sony Xperia 1 Questions & Answers] Mackay53:
Half way down
[Sony Xperia 1 Questions & Answers] munjeni:
:eek: I realy didn't know about that! I'm not active on xda and I completelly missed that, sorry! https://android.gadgethacks.com/new...ting-before-modding-anything-android-0167840/

this explains why his device can't go to the flash mode. I will research further about this. Thank you for info, I understand now what you mean, sorry again!
[Sony Xperia 1 Questions & Answers] j4nn:
[MENTION=4120742]munjeni[/MENTION], as your PM linked to this thread, I am replying here, hopefully that's ok.

I know about the 'OEM Unlocking' option, but you making me to check this thread caused me to realize the consequences of having that option not enabled while experimenting with a locked phone.

So I've updated the TA backup thread with an advice to enable this option in advance. Thank you.

Concerning your question: I guess this information from the_laser may be useful - see here please - in my opinion that's is the 'OEM Unlocking' option in developer menu:

I am not sure if TrustZone is involved when this unit is written, it may be.

In any case I guess this unit is not flashable even in flash mode, similarly as the device key unit (66667) cannot be flashed with patched newflasher, even with bootloader already unlocked.

And most likely these high area units are signature protected, signatures possibly computed in trustzone - just my guess, I do not have any proof for that.

Also this post from the_laser seems to contain very detailed and precise info, that may be related.
[Sony Xperia 1 Questions & Answers] j4nn:
I would also try to erase userdata from fastboot. If the above did not work, maybe one of following could?

fastboot -w

fastboot -w reboot

So to summarize, [MENTION=5271437]jeoleo7[/MENTION] flashed J8010 firmware into Xperia 1 dual (J9110) device, flashing everything: that is including bootloader and erasing userdata.

It then even booted into setup screens, but crashed/rebooted somewhere later during setup.

But it had still been possible to enter flash mode, so J9110 firmware could fully be flashed back?

But then it did not boot anymore and does not enter flashmode anymore, only fastboot?

That is quite strange, if all above is like that. It would mean the phone has now the original bootloader flashed back, so in my opinion it's quite strange that it would not enter flash mode anymore.

Maybe something has been corrupted in TA when it crashed in setup screens with J8010 firmware running?

But in such case, why it has been possible to enter flash mode right after that crash, flashing successfully J9110 firmware back, but not enter flashmode again after that?

Attached two splash screens extracted from bootloader/xbl of J9110's 55.0.A.6.16 firmware - the phone seems to be in 'verifiedboot_state_red' (even if one of them has white triangle).
[Sony Xperia 1 Questions & Answers] jeoleo7:
Hi,

Thank you for your efforts and suggestions. I tried above commands and this gives not allowed in Locked State message.

The image that appears in mine is with the white triangle.

After the wrong flashing, the device restarted twice.

First startup ended in choosing a language and then second ended up to a later step than that.

Then I started seeing the message and then couldn't enter the flashmode. I connected the phone to the wall charger and It was the last time I saw Sony logo.
[Sony Xperia 1 Questions & Answers] j4nn:
[MENTION=5271437]jeoleo7[/MENTION], just wondering because of your last post - were you really able to flash back the J9110 fw fully including bootloader (the boot/ subdirectory) before it stopped to be able to enter the flash mode (the green led light)?

In any case, if the phone is still locked, not able to enter flash mode to reflash stock fw, most likely under warranty, your best chance is now in my opinion claiming the warranty, so sony service would fix it for you (replacing the mother board).

Particularly if you managed to flash back the J9110 fw, it probably cannot be recognized anymore what has caused the wrong state.

Not having OEM Unlocking enabled, you cannot go the way of 'fastboot oem unlock' that would enable recovery options using fastboot, while sony flash mode is not working, so that way is also closed.
[Sony Xperia 1 Questions & Answers] munjeni:
Yes sure, if I remember right ta units range e.g. 0 to 0x10000 is not protected but all after 0x10000 is protected, needs a handshake for access as many other locked commands (you can see it in lilo). One thing which I wanted to figure out two years ago was to simulate signature check using openssl, e.g. to simulate unlock key, tried many combinations using marlin certificates from an ta unit and its signature from another unit, using unlock key as a secret key but I didn't succedd, have realy no idea how that unlock key is checked by lilo (lilo?) so by that I have no idea how to simulate thing using openssl. Lilo contain openssl implementation and there is some functions for thing but thats hard for my head, ended and leave. I'm believing we can modify some lilo functions (preload) to print some secret things into output log? E.g device secret key

---------- Post added at 03:50 PM ---------- Previous post was at 03:17 PM ----------

I searched a bit and found some posts from 3 years ago with the same situation, no bootloader but fastboot, it if I am not wrong an LG device, some replied with success with fastboot command "fastboot continue", hope it is the case on xperia 1

Edit:

No, if trim area is corupted device is totaly dead, only blinking red without anything on usb

Edit:

Probably true, if I remember right there is doubled partitions with extension _bak? So probably right bootloader is restored back. I'm believing his bootloader searching for something but stuck on "wrong item" and reboot itself to fastboot. Or probably OEM lock flag cause that, who know.

---------- Post added at 04:35 PM ---------- Previous post was at 03:50 PM ----------

I didn't pay attention to what the_laser told me in that post about that unit because until yesterday I didn'tknow anythin about oem lock:

Now I see huh. If somebody allready have trim area dump from an modern device with oem lock feature plese give me by pm, need to see size of the unit 66671, if it is with size 1 its just probably an flag "0" or "1", in worst case its signed unit with size more than 1. If it is with size 1 you can search for it by this hex string:

6F 04 01 00 01 00 00 00 C1 E9 F8 3B

or skip red and search for 6f040100 (skip 8 red strings in case you didn' t fing anthing with red) c1e9f83b

---------- Post added at 05:14 PM ---------- Previous post was at 04:35 PM ----------

By my research based on s1tool and my first hard brick on z1c only 3 units can't be modified (at least s1tool use only 3 units for unbrick, 0x7d3, 0x7da, 0x851), cause total hard brick, I have added more:

https://github.com/newflasher/newflasher/blob/master/newflasher.c#L2090

Wrong ta partition adler32 checksum on partition which contain danger units also cause hard brick. Don't know now whats on modern devices, probably some more. I'm believing units writen from android is not signature protected.

Edit:

I see now, found it year-two in lilo, and now updated :)
[Sony Xperia 1 Questions & Answers] j4nn:
[MENTION=5271437]jeoleo7[/MENTION], as fastboot still works with your xperia 1 dual, could you please post the output of following command?

fastboot getvar all

That would reveal what sw versions are flashed on the phone including bootloader version.

Please clarify also, if you really could flash J9110 firmware back with newflasher and only after that it flash mode stopped working.

This is really important, as it may reveal, that some fw components could have been silently not flashed, like the bootloader designed for your device.
[Sony Xperia 1 Questions & Answers] j4nn:
[MENTION=5271437]jeoleo7[/MENTION], could you please confirm, that you really was able to flash back the J9110 fw or you could not enter flash mode already, so it has not been possible to even try to flash the J9110 firmware back?

Your physical device is J9110 (xperia 1 dual), the fw for it (55.0.A.6.16) contains LA1_0_P_39 bootloader.

Firmware for J8010 (the new 'sphinx' device) - yesterday available 55.0.B.0.567 version - contains LA1_0_P_43 bootloader (now xperifirm does not list any fw with J8010 btw).

I am wondering if you managed to flash fw for J9110 back - if you were able to enter flash mode and you actually tried it - it could have been refused, as being considered as 'downgrade' of everything, including bootloader - that is if sony has strict verified boot 2.0 restrictions now in place?

Anyway, maybe as a last chance, you could try to switch active boot slot from 'a' to 'b' and if possible, see if the alternate system would boot - try some from following fastboot commands:

fastboot set_active b
fastboot --set-active=b
fastboot --set-active=b reboot

You may need recent fastboot version - you may get it here.
[Sony Xperia 1 Questions & Answers] j4nn:
In past, I have tested the influence to TA of "OEM Unlocking" developer menu option, I have my TA back images with me.

Just checked it again and it is like this: when the option is disabled (the default state), TA unit 0x1046f (66671) contains four bytes: 01 00 00 00.

When the "OEM Unlocking" option is enabled, the TA unit 0x1046f gets zero size.

This option gets modified on runtime - my TA backups when checking this option are from the same boot up, so there are minimal differences, if comparing just the extracted TA units - only 0x007e5 unit got modified with it, but I am not sure, if that is significant at all:

-00000000 01 02 00 00 08 70 02 4f 4b 71 02 4f 4b 74 fc 6e |.....p.OKq.OKt.n|
+00000000 01 02 00 00 08 70 02 4f 4b 71 02 4f 4b 00 00 00 |.....p.OKq.OK...|

So there is some way that even on runtime allowing high area TA units modification. But my guess is that it is done with help of TrustZone.
[Sony Xperia 1 Questions & Answers] jeoleo7:
Hi,

Thank you for the message.

Regarding the flashing steps. I flashed the wrong firmware and tried setup, it failed two times and then as I remember, It started showing the message.

Then I tried to get to flashmode for flashing but it didn't hold though the green light was there also with the warning message.

I then thought the battery was discharged so connected to the charger. Then I was able to see the Sony logo once I connected to the charger and then it started the same message.
[Sony Xperia 1 Questions & Answers] munjeni:
Thanks for info! So zero size mean "allow bootloade unlock", great. He have problem right now and he will not be abble to repair device without an hardware tool. One strange thing mentioned here -> https://android.gadgethacks.com/new...ting-before-modding-anything-android-0167840/

Thats probably mean repair centre is lazy to repair or there something more is need for enabling oem unlock. My gues is it is easy with for example easy jtag with emmc adapter, problem might be getting pinout, with pinout it can be achievable by modifying trim area unit 66671 and updating adler checksum, than using newflasher for reflashing everything. Another thing, he can't get slot b working even can't get slot a working right now, booth slots is not working:
[Sony Xperia 1 Questions & Answers] munjeni:
[MENTION=4418980]j4nn[/MENTION] did you analysed lilo binary?

char *off_139008[33] =
{
"getvar:",
"download:",
"flash:",
"Format-TA",
"Read-TA:",
"Read-all-TA:",
"Write-TA:",
"powerdown",
"reboot",
"continue",
"reboot-bootloader",
"erase:",
"Secure-erase:",
"Erase-sector:",
"Secure-erase-sector:",
"Read-partition:",
"Read-sector:",
"Get-partition-list",
"Repartition",
"Getlog",
"Digest:",
"signature:",
"Set-security",
"Get-security",
"Get-gpt-info",
"Get-ufs-info",
"SAKE-Authenticate:",
"Get-root-key-hash",
"Charge:",
"oem unlock",
"Sync",
"partitionimage",
"Read-partition:appslog"
}; // weak

Via fastboot SAKE-Authenticate, can it be that sake key is unlock key received from sony? I don't owning modern sony device for try, but in case sake authentification pass we can use write-ta and read-ta commands...
[Sony Xperia 1 Questions & Answers] j4nn:
[MENTION=4120742]munjeni[/MENTION], in my opinion xperia unlock code from sony serves only for the bootloader unlock purpose. My guess is that the unlock key is used to calculate 'MiscTA Unit 2226 (TA_RCK)' which is checked by bootloader, and when valid, BL unlocks itself. Check the info provided by the_laser.

In my opinion, with still locked BL (with oem unlocking disabled), there is no way to recover a brick with not available sony flashmode. Even in case fastboot still works. Maybe only if fastboot allowed some kind of authentication to enable some recovery commands.
[Sony Xperia 1 Questions & Answers] munjeni:
Can you please watch unit 0x10471 (66673), I'm believing that unit is an "startup flag", protocol switch? For example when need to reboot to fastboot or to flashmode or to android it is firstly writen before reboot. One question trought, is fastboot able to boot sin file? I didn't remember.
[Sony Xperia 1 Questions & Answers] j4nn:
[MENTION=4120742]munjeni[/MENTION], I would propose to move our discussion into a different thread - continuing here would not help with the problem of this "xperia 1 bootloop/brick" thread...

If it is ok with you, I would reply in the [XZ1c/XZ1/XZp] temp root exploit to backup drm keys thread.

I think I have interesting finds to discuss as coincidently I have been to analysing boot override possibilities myself for few days alredy...
[Sony Xperia 1 Questions & Answers] munjeni:
Ok, lets keep this thread clean and continue to yours
[Sony Xperia 1 Questions & Answers] jeoleo7:
Hi,

I had my phone repaired from Xperia Centre HK and I'm happy it is fine now.

Thank you all!

:)
[Sony Xperia 1 Questions & Answers] j4nn:
glad to hear you got it fixed...
[Sony Xperia 1 Questions & Answers] MeltdownSpectre:
How did you get out of the bootloop?
[Sony Xperia 1 Questions & Answers] snake218:
Select Wipe userdata when flashing.
[Sony Xperia 1 Questions & Answers] jeoleo7:
Mine worked fine with the upgrading to latest (55.1.A.3.49 Customized SEA) firmware yesterday but while downgrading to a previous version (55.1.A.0.748 Customized HK) I had to wipe data.

My phone booted to recovery and offered me to try again or clear data. I cleared data and it worked.
[Samsung Galaxy Note 9 Questions & Answers] 860lacov:
I've seen a youtube video where author says that dark mode in S9+ killed his phone screen.

He said that when you use app that is not affected by dark mode (stays white) and this app uses keyboard (black in dark mode) it causes screen fatigue when you open keyboard and than close it.

Of course it depends on usage but in his example (using this app few times a day) his screen died after two weeks or something like that.

Is it even possible?

If I understood him correctly it wasn't usual screen burn in.
[Samsung Galaxy Note 9 Questions & Answers] raul6:
whatever caused the screen to malfunction wasn't use of dark mode
[Samsung Galaxy Note 9 Questions & Answers] 860lacov:
It seemed WEIRD but I decided to ask. I've thought abut it like a light switch.

On bright screen when we turn on black keyboard it will make pixels black. Maybe doing this a lot could be harmful.

Well... I like dark mode so I might turn it on again someday :)

Thx
[Samsung Galaxy Note 9 Questions & Answers] bober10113:
its like saying that driving your car is bad for the car because when you were driving it failed.
[Samsung Galaxy Note 9 Questions & Answers] freeza:
Dark mode doesn't kill displays
[Samsung Galaxy Note 9 Questions & Answers] bober10113:
randomness of the QC does.
[Samsung Galaxy Note 9 Questions & Answers] Jammol:
On Oled screens, the sections of the screen that are black are actually turned off completely. So so those pixels aren't even being powered.
[Samsung Galaxy Note 9 Questions & Answers] 860lacov:
I think that idea behind "problem" is :

When you have bright screen and you turn on keyboard with black elements than turn keyboard off it will work like power switch.

To be honest I choose to believe people from xda and assume that if I'm not unlucky than my screen is gonna be fine .

I feel that dark mode has got to much bright elements like icons . They should be grey or something
[Samsung Galaxy Note 9 Questions & Answers] gruuvin:
What do you mean "it will work like power switch"? And please explain why "work like power switch" is bad for the screen.
[Samsung Galaxy Note 9 Questions & Answers] 860lacov:
Imagine Light bulb.

When switch is on there is light. When off there is no light.

If I'm correct light bulbs burn when you turn on power . Not while emitting light.

I have no idea if this comparison is even near the truth but this is what came to my mind .
[Samsung Galaxy Note 9 Questions & Answers] bober10113:
sounds logical to me.

let's see if an engineer can disprove it.

im not one but i know that incandescent bulbs and oled are pretty different. the burning filament part of a bulb has a high peak uppon power on and and just the nature of the "burning" makes it much more prown to burnouts. plus the AC current switching created by 50 or 60 hz must be a big part of why bulbs break more...just the strain of it switching polarity back and forth and there is no capacitor to smooth it out. Oled being part of a DC electronic device and natively consuming much less, has all sorts of controls and capacitors to smooth everything out and moreover, it is constant.. but id bet if there is some sort of app that could strobe between full max brightness and blackout real quickly, I'd presume failure faster than we might think.
[Samsung Galaxy Note 9 Questions & Answers] Da-BOSS:
LED works differently than light bulbs... if LED is near to dead... it won't produce the correct light colors which is nearly happens when there's a screen burn on any OLED screens... it will display colors differently

Correct me if I am wrong but that's how I see it :)
[Samsung Galaxy Note 9 Questions & Answers] Danikin:
[IMG="thas no how this works"]https://media.giphy.com/media/2fs2I4ujlBf20/giphy.gif[/IMG]
[Samsung Galaxy Note 9 Questions & Answers] 860lacov:
Maybe some conclusion ??

Dark mode and normal mode are the same for the screen ?
[Samsung Galaxy Note 9 Questions & Answers] Danikin:
Oleds are designed to turn off the pixels that are not neded, so no, using a dark theme wont damage the screen.

and the power switch theory is very far from beeng anything, everything you turn on works like a "power switch" and you dont see everything on fire :D

in the case of the phone, is best for the pixels to be off because they have a sort of fixed lifetime, you will extend that lifetime using them only when needed.

:D
[Samsung Galaxy Note 9 Questions & Answers] Guyinlaca:
A friend of mine used their S8+ in light mode at 80% brightness and after 18 months the screen was badly burned in. There was a brown haze affect over the entire screen and the status and Navigation bars were heavily noticeable on videos.

Dark mode saves battery and is easier on the eyes. Samsung has done well at preventing burn in, whereas LG is still questionable.