yashsingh1/xdaforums huggingface dataset:
[Sony Xperia XZs Guides, News, & Discussion] nlra:
I'm not 100% sure I understand you, or if maybe you misunderstood me.

Are you saying that you have successfully tried flashing XZ firmware to an XZs, and it worked? In all of the threads I have read on XDA from others who have tried this, the result has been a bricked phone...

It doesn't matter if the camera is unresponsive when running XZ firmware on an XZs. Running the XZ firmware would be *temporary*. You would only have it on your phone long enough to extract a complete copy of the TA partition, with all DRM keys intact. Once you have extracted a TA backup, you would re-flash back to XZs firmware. So, you maybe will run your phone with XZ Marshmallow firmware for 5 minutes, tops.

You can't "recover" or "restore" TA if you don't have a backup to begin with, so I'm not sure what you are talking about there. If you unlock your bootloader without first making a backup of TA, then your DRM keys are gone. Forever. NO recovery is possible. So, of course, if you have already unlocked your bootloader, it is too late, and putting XZ Marshmallow on your phone for 5 minutes to make a backup of TA would be pointless. My proposal is for people who have XZs phones still with LOCKED bootloader, who want to make a pristine backup of their DRM keys *before* unlocking for the first time.

Up until now, XZs users have had no means of making a backup of TA before unlocking their bootloader. So only solution for XZs users who unlock is "drmfix", which does some tricks to make *some* of the Sony software think that DRM keys are present even though they are not.

This is not as good of a solution as actually keeping your DRM keys, however. Most of the Xperia models before XZs have a more comprehensive "drmfix", where you extract the DRM keys for your phone from your TA backup that you made *before* unlocking your bootloader, flash them *back* to the TA (*just* the DRM part, and nothing else), and then you have the perfect solution: DRM keys AND unlocked bootloader!

Plus, with a copy of the original, pre-unlock TA partition, you have the option to flash the whole TA backup back to your phone at any time in order to re-lock your bootloader and put things back to stock.

All of this is only possible with SD820 or older Xperia models. The ones that came with SD835 and newer (XZ Premium, XZ1, XZ2, etc.) have additional security. It's still possible to extract DRM keys from TA on some of these phones before unlocking the bootloader, but you can never go back to locked bootloader on those phone models, even with a complete TA backup.

-- Nathan
[Sony Xperia XZs Guides, News, & Discussion] &(*):
You're right, my mistake - I meant DRM is recoverable (sort of) not TA . What you are suggesting with a locked bootloader will not work, as it will not contain the verification keys to allow a rewrite of it - in short.
[Sony Xperia XZs Guides, News, & Discussion] &(*):
Boot.sin would not suffice, boot is now a folder with a number of files to choose from based on what is read from the bootloader status during flash. There are keys stored and keys appended to the enrolled verified signatures during an upgrade, a downgrade would attempt the same with keys for that version or possibly based on how it parses the list insert the keys to the top of the list. In order for the bootloader to accept a write to the table and enroll the keys for signed images of the sort, the bootloader requires a key itself to allow a write to it. The key for the XZs bootloader will more than likely not match is my thought at which point the loader is flagged for being corrupt and will no longer boot or simply not write and abort (which apparently other's state is not the case). I'm not missing the point here, it's just not likely that the bootloader or the TA where the flags are set will allow a write to the loader itself considering how it handles OEM signed images and how it verifies each partition before it writes to it with keys (signatures). My understanding might not be descriptively accurate in terms of technicality with the order and operations of how the bootloader protects itself, best bet here is to coach your friend on the flashing process and report the results. I don't think the loader will allow a downgrade to a system it didn't support during it's lifecycle.
[Sony Xperia XZs Guides, News, & Discussion] nlra:
Sorry, my mistake...I meant kernel.sin, not boot.sin. I misspoke since I had in mind that fastboot itself calls the kernel partition 'boot', so when you reflash a new kernel (in uImage format, not .sin) with fastboot, you use 'fastboot flash boot'. So, a brain fart moment on my part.

Yes, I'm aware the bootloader itself is made up of a number of files in a folder, though until your explanation I did not know what the point of the diversity of files was.

Got it; thanks. I was not aware of this.

But this sounds like the bootchain keys in the TA only get touched/written to when the bootloader itself is being flashed. What if only main application processor code (kernel, system) partitions are being touched while in flashmode?

Right; my mistake was in misleading you by writing "boot.sin", when I was trying to reference the Linux kernel. It seems to me that if you attempt to only flash kernel and/or system from a different model with a locked bootloader, at most you risk the system not booting because bootloader refuses to chain off to the kernel on account of mismatched keys or whatever, but this is a state that can be recovered from by going back into flashmode (which still works, since XZs bootloader hasn't been touched and is still intact) and reflashing actual stock XZs kernel and system again. So, on the off-chance that it works, my thought is why not give it a try, since the only thing you potentially have to lose/waste is time...

This is all predicated on the theory that pre-SD835, Sony largely re-used the same set of bootchain signing keys across all models. Which admittedly could be entirely wrong. The main reason why it seems probable is that there doesn't seem to be any problem with cross-flashing different firmware customizations within a model, nor with cross-flashing between variants of a model (e.g., any Z5c E5803 firmware of any version can be flashed to E5823, or vice-versa), all while running a locked bootloader. It's also never been a problem to upgrade or downgrade Android version at-will with a locked bootloader, suggesting (to my simple mind) that the keys haven't changed over the lifetime of that platform.

I suppose one test that would be interesting would be to see if I could flash and boot a Marshmallow kernel and userland on a Z5c with a bootloader from either a Lollipop or Nougat firmware bundle, while the bootloader is in a locked state. If a mismatched but locked bootloader willingly passes off to a signed kernel from a different firmware version than what it itself shipped with, that's an indication the signing keys didn't change. Right?

What I have heard almost no chatter about, other than in XZs-land, is attempting to cross-flash between any models that are part of a larger shared platform (e.g., flash any official Kitakami platform firmware to any other Kitakami model phone with locked BL). XZ and XZs are both part of such a shared platform (Tone).

-- Nathan
[Sony Xperia XZs Guides, News, & Discussion] nlra:
Z5 Compact + locked bootloader + Z5c bootloader from Nougat + Z3plus kernel + Z3plus system:

It works.

A stock, Sony-signed kernel and system image for Android 6.0 from a KITAKAMI device (Z3+) can be booted just fine by a locked bootloader (from the Android 7.1.1 firmware, no less) on a KITAKAMI-r2 device (Z5c). I have an ADB shell and a logcat running and everything.

Now, naturally, things don't run *well*. I can't see anything on the screen because the Z3+ display is higher resolution than the Z5c display, and so the Z5c display isn't initialized properly by the Z3+ kernel. (Touch inputs work, however! I'm hitting targets blind, but every once in a while I'll get it to vibrate or make a sound like I managed to tap something.) logcat reveals that basically all radio-related processes are going berserk: the NFC server is crashing and relaunching itself every second or so, and almost just as often, the system is trying to communicate with the cellular baseband and failing to do so. Also, the phone runs HOT. Probably because these processes are freaking respawning themselves every 1-2 seconds. I imagine CPU load is through the roof. (Also, as a fun test, if I try to flash the Z5c kernel back to the phone while leaving the Z3+ system image in place, the display initializes properly, but everything form text to images is all rendered hilariously huge, given both the resolution and DPI difference between the Z3+ and the Z5c.)

But none of this matters. And that's because the only reason why you would theoretically want to do this anyway is so that you can run the dirtycow exploit against the phone in order to gain temporary root and then do a dump of the TA partition. So the only things that need to be working are the USB port and eMMC access. And since both are working, I was able to successfully do exactly this to this phone while it was in this state.

I would be shocked if a similar thing were not possible with XZs (TONE-r3) using the Marshmallow kernel + system from XZ (TONE-r2)...
[Sony Xperia XZs Guides, News, & Discussion] &(*):
You would need an oem (vendor), kernel, and system .sin along with the partition layout to theoretically accomplish what you are proposing.
[Sony Xperia XZs Guides, News, & Discussion] nlra:
It only remains theoretical on the XZs...I believe that I demonstrated that the concept is sound by flashing and booting Z3+ kernel and system on a locked Z5c.

Vast, vast majority of Snapdragon-based devices -- including SD-based Xperias -- utilize a GPT partition table, not static LBA offsets hard-coded into the kernel (or passed to the kernel by the bootloader). And then all partitions are looked up by name, not sequence#, UUID/GUID, or whatever. Partitioning should be a non-issue, and it most definitely was not an issue with Z3+ code running on Z5. I would definitely be very nervous about flashing partition.sin from XZ to an XZs (or from Z3+ to a Z5). Chances are good anyway that the partition layout changed either very little or not at all between the two models, but GPT should abstract away any subtle differences.

oem, maybe. If XZs oem partition contains stuff that happens to confuse the XZ system software, and causes it to behave badly or go into a crash/restart loop, then yeah, I could see trying to flash oem along with kernel and system. Should be no biggie. It's likely, though, that even if you left XZs oem contents in place, the base of the system would work "enough" to be able to do a TA partition dump, which is all we really care about. Only thing I believe that's needed to accomplish that is an ADB shell over USB. ADB is started up early enough by the system during boot (well before the Android user environment has even rendered a single pixel on-screen) that I just don't see this being a problem.

The tricky part is actually enabling ADB while running the "wrong" kernel and system. I have war stories on this topic with the Z3+ > Z5c test. I accomplished it on there, but the XZs may be a different story. If I am given a chance to try it, I'll let y'all know.
[Sony Xperia XZs Guides, News, & Discussion] &(*):
You need oem, as it pertains to what software the kernel loads for system I believe. Partition more than likely is necessary due to the shift from legacy (M) to HAL (>=N); whether or not the architecture was implemented in M for XZ is questionable, having a look through the developer binaries at the repo from Sony might indicate it. What is more likely the case, you will need to make sure your paths for everything are in order for a mostly clean boot so that the system will accept what you propose without much fuss (like not losing adb ie flashmode).
[Sony Xperia XZs Guides, News, & Discussion] nlra:
Theory about the "major" version number of Xperia firmware versions having a uniform set of signing keys seemingly confirmed: I was able to successfully flash an XZ (F8331) Nougat 7.1.1 kernel.sin to this locked XZs (G8232) that's running Oreo and the phone took it without a complaint.

It didn't fully boot, but that's likely at least in part due to the fact I didn't bother flashing system.sin, just the kernel. Unlike when I've had an unsigned kernel flashed to an Xperia with a locked bootloader, though, the bootloader did display the normal Sony boot logo, so I'm guessing it successfully verified the signature and then chained off to the kernel, but that due to initrd and booting differences between Nougat & Oreo, it eventually hung at some point in the boot process. (Actually, just occurred to me that there would be massive mismatch between Nougat kernel and any kernel modules included with Oreo...)
[Sony Xperia XZs Guides, News, & Discussion] project_2501:
@nlra ,

With the binary provided I was able to backup/restore the TA and relock the bootloader after unlocking it (no more exclamation posting on boot)!
[Huawei Developers] Martin Bieber:
Dear HUAWEI Cast+ Kit hardware developer,

To help you get to know HUAWEI Cast+ Kit better, we have planned a series of tutorial videos, including an introduction to HUAWEI Cast+ Kit, integration tips, and demos. We have invited people who are familiar with HUAWEI Cast+ Kit to share their integration experience, including architects and partner experts. Selected highlights will be included in the HUAWEI Cast+ Kit Integration Tutorials.

The first video has now been released on HUAWEI Developers. Visit the link below to find out more. The tutorial covers the ins and outs of HUAWEI Cast+ Kit, as well as the technologies behind.

Highlights:

Why is Huawei releasing Huawei Cast+ capabilities?

HUAWEI Cast+ Kit

Benefits of Cast+ Kit

Cast+ Kit integration process

Cast+ Kit device access: requirements

Link:

https://developer.huawei.com/consumer/en/training/detail/101594803792346039

For more details about Cast+ Kit development, including a service overview, development guide, access preparation, and access to the SDK, please click the link below:

https://developer.huawei.com/consumer/en/cast-kit

Related articles:

Reimagining Cross-device Interaction, with HUAWEI Cast+ Kit

https://forums.developer.huawei.com...d=0201218196835970125&fid=0101188387844930001

A Wild New Creative Tool to Connectivity Across Screens

https://forums.developer.huawei.com...d=0201247360570280183&fid=0101188387844930001

Hardware Partnership Journey

https://forums.developer.huawei.com...d=0201266198988140027&fid=0101188387844930001
[Redmi 7A Questions & Answers] vincecabalan:
I have magisk installed and working on my Redmi 7a running MoKee 10 rom. I can't seem to install the font changer module. Does anyone know how to fix this? Thank you very much.
[Touch Diamond, MDA Compact IV ROM Development] ljazzo1:
i updated my HTC Touch Diamond (3700) and noticed one thing

after i installed the new RUU_Diamond_HTC_Asia_WWE _1.93.707.1 i checked

which rom release (settings - Device Information) i have and i was surprised.

My HTC show me:

Rom Version: 1.37.405.1 WWE <-- previous one

Rom Date: 07/13/08

Radio Version 1.00.25.05

Protocol Vers 52.29.25.12H

it seem that the new RUU_Diamond_HTC_Asia_WWE _1.93.707.1 still have the old 1.37.405.1 WWE inside plus the new Radio and new protocol

Can someone tell me why The Rom Version is still 1.37.405.1 WWE and not the new one "1.93.707.1 " i installed? Now i am confused
[Touch Diamond, MDA Compact IV ROM Development] chand4u76:
I believe the flash has not happened
[Touch Diamond, MDA Compact IV ROM Development] ljazzo1:
hm ...strange then why after flashing i have the new Radio and Protocol and also the Fltouch is different now ...any hints or idea ? I have SPL-1.40Olinex loader installed

should i maybe first do a Hard Reset and then install again ? i have my doubt that the new 1.93.707.1 has really a new rom inside

thank you
[Touch Diamond, MDA Compact IV ROM Development] honerboy:
hi..hows the memory allocation to program and storage after the flashing....whats the difference in fltouch noticed...

thanx
[Touch Diamond, MDA Compact IV ROM Development] ljazzo1:
hi again and more infos. I did a hard reset and now my htc show the correct rom release 1.93.707.1.

What i suppose is ...after the data restore from my previous rom release i saw that the HTC rom release was 1.37.405.1 WWE and not the newone. I did a restore with Level1 option , so i guess i got some system information from the previous rom backup... hmmmm strange

here step by step what i did now

- hard reset and upgraded to 1.93.707.1

- check Rom Release ...and now is ok , it show me 1.93

- execute a backup of my htc and also a registry export

when i use restore, which upgrade Level should i use?

Level1: Use this option to perfom restore operations between the same device

with different ROM revisions. For example: restoring from a KJAM ROM 2.16.9 to a KJAM AKU2 ROM version

Level2: Use this option when you wish to restore across devices and ROM versions

Level3: If your device does not boot after permorming a "level1" or "level2" restore use the "level3" operation

i am going to install all again, i am not sure i can restore my previous data and ikeep the correct rom release..

more hints, help or explanation ?

thank you
[Touch Diamond, MDA Compact IV ROM Development] ljazzo1:
I am back

i installed all my program and all is working well , but now ..i have another problem

when i go to see the phone Band i only can see 900 + 1800

anyone can tell me why ?
[Sony Xperia 1 II Questions & Answers] TheOnlyIntruder:
This is a bit of an odd issue but I've noticed occasionally that when listening to media using the speakers at low volume (below ~1/4), occasionally one speaker cuts off or channels swap. It also seems to be random which speaker cuts off but usually the left speaker is the one to cut off. If I turn the volume up, the speakers/channels restore and I can turn the volume back down.

Anyone else experience this?
[Sony Xperia 1 II Questions & Answers] TheOnlyIntruder:
I take it no one has encountered this? Although since the latest system update, I've not had it occur nearly as frequently.
[Sony Xperia 1 II Questions & Answers] Kilvoctu:
Makin' an account to add that I've been encountering this issue since I got the phone at end of July. I've seen a few reports on other messageboards of people experiencing this, too. Have you had any luck with resolving it?

I've been trying all sorts of things to try to fix this. Sony Support has unfortunately not been able to provide a solution.
[Sony Xperia 1 II Questions & Answers] TheOnlyIntruder:
Unfortunately, I still can't pin down why this happens nor have I found a solution, just the temporary mitigation of turning up the volume for it to start working again and then turning the volume back down.
[Sony Xperia 1 II Questions & Answers] Geoffxx:
could be a hardware fault
[OnePlus 6T  Questions & Answers] FreddyTheMeme:
***SOLVED***

so after installing everything following a guide, where as i couldn't open app store after i was done. i decided to uninstall everything and it went great until i restarted my phone after doing so, now i can't exit bootloader and i can only turn my phone off when it's not plugged in, anything returns to bootloader. I have tried several things here to fix it, nothing works as it doesn't show up in the adb commands.

please help me figure anything out

EDIT: I think the issue is that i deleted the cache and then proceeded to reboot my device

EDIT2: and i just locked the oem lovely

EDIT3: i did it
[OnePlus 6T  Questions & Answers] OhioYJ:
So you are stuck on the fastboot screen? ADB doesnt work on the fastboot screen, only fastboot commands. Careful what guides you follow, and make sure you don't miss any steps. From the fastboot screen you could use the fastboot ROM.

If that doesn't work you can use the MSM tool.

Remember the fastboot ROM will put OOS back on your phone. MSM will put OOS back on your phone and relock the bootloader. So not sure what you were trying to do but you may try and boot TWRP from fastboot one more time if thats what you were trying to do.
[OnePlus 6T  Questions & Answers] FreddyTheMeme:
when ever i try to boot the immage it says "PS C:\adb> fastboot boot twrp-3.4.0-0-fajita-Q-mauronofrio.img

downloading 'boot.img'...

OKAY [ 0.723s]

booting...

FAILED (remote: Failed to load/authenticate boot image: Load Error)

finished. total time: 0.731s"

but i'll try to use the MSM tool

EDIT: doesn't seem to work either, same issue "Load Error"
[OnePlus 6T  Questions & Answers] OhioYJ:
The error means something is wrong, likely just one partition, but Ive never taken the time to figure out which one, just always fixed it with the fastboot ROM. I will say Im not a fan of the 3.4.x TWRP (for this device), I removed it from my LOS guide for several reasons. It still has issues in my opinion.

For the MSM tool, if it doesnt work its almost always a driver issue. Just for clarification for the MSM tool its not supposed to be in fastboot, nothing will be on the screen while using the tool (the phone starts off).

For reference, taken from my guide here:

Volume Up + Power while turning on will boot to fastboot.

Volume Down + Power while turn on will boot to recovery.

Holding Volume Up + Power should force the phone to turn off.

Volume Up + Volume Down should put your phone in Download mode for the MSM Tool.
[OnePlus 6T  Questions & Answers] FreddyTheMeme:
so i have successfully done the msm, but from here how do i enter stock os, because when ever i try to search for updates it says none found even though i am 9, is it because my oem is unlocked? or am i still rooted? whenever i try to update it using local upgrade it says fail

edit: just read that i should try to update to 9.0.17 and then to latest
[OnePlus 6T  Questions & Answers] el80ne:
Heya, you sound really experience with regards to this so I was hoping you could save me some time by telling me if I should even bother wasting trying to revive my brick.

I've got a op7pro stuck on the bootloader unlocked screen. Research reveals I hosed it by flashing twrp to the wrong partition. Flashed it to boot instead of recovery.

I've tried to get MSMTool to recognize it by pressing volume buttons on powerup but it hasn't so far. That's pretty much the last resort isn't it? If MSM won't recognize it then I'm outta luck?

Device Manager will see my phone as an unknown device when I boot holding down the volume buttons, but MSMTool and the all-in-one tool won't.

The other time I unbricked using MSMTool I got it to work pressing volume buttons on boot and win10 immediately recognized the device as highspeed qualcomm ports.

But that was on a boot loop, this is stuck on bootloader, a far graver problem it seems. Thanks for whatever advice you could offer this hapless modder.
[Xiaomi Mi A2 Lite Guides, News, & Discussion] Aadil Gillani:
[Global] Mi A2 Lite V11.0.10.0.QDLMIXM rolling out!
[Xiaomi Mi A2 Lite Guides, News, & Discussion] SouthBohemiaMan:
[IMG="Succesfully updated"]https://ibb.co/BrSsVsd[/IMG]
[Xiaomi Mi A2 Lite Guides, News, & Discussion] a1291762:
Wow. That's gotta be some kind of record for Xiaomi :)

Mine is only 13M though. Must be a tiny update.
[Xiaomi Mi A2 Lite Guides, News, & Discussion] Albertli:
Wow! First time ever that this Android One device is actually up to date security wise.

Yes, from July update only 13MB.
[Xiaomi Mi A2 Lite Guides, News, & Discussion] penahj:
Maybe it was there before, but after updating I noticed a native screen recorder icon.

Updated: It is not native. I have a screen recorder app installed.
[Xiaomi Mi A2 Lite Guides, News, & Discussion] penahj:
Direct share not yet available.
[Xiaomi Mi A2 Lite Guides, News, & Discussion] Antho02:
strange i dont have this one and never had screen recording option
[Xiaomi Mi A2 Lite Guides, News, & Discussion] penahj:
You are right. It's not a native app. I have a screen recordering app installed. Sorry for the wrong news.