yashsingh1/xdaforums huggingface dataset:
[Sony Xperia XZ1 Compact ROMs, Kernels, Recoveries,] j4nn:
Just to clarify a bit what we did to recover the xz1c that has been half bricked with TA partition overwrite from a different xz1c.

The phone always booted into sony flash mode when connected to usb cable, that allowed to flash .ta units.

It was possible to read out bootloader log from TA with patched newflasher, the log contained following errors:

XBoot Init
Init XBootPALAPILib
Init TA API Lib
XBOOT (1306-5035_X_Boot_MSM8998_LA1.1_O_77)
[ERROR @ hwconf.c:172]:
Failed to match dev id for hwc and input
[ERROR @ hwconf.c:249]:
Failed to verify device binding: (-1021)
[ERROR @ xboot_glue.c:496]:
failed to setup hwconfig (-1021)
single slot QseecomStartApp with parition name
Reading 4 bytes from RPMB, OK
Reading 4 bytes from RPMB, OK
Reading 4 bytes from RPMB, OK
[ERROR @ hwconf_parser.c:1980]:
Invalid input parameters
[ERROR @ xboot_glue.c:1256]:
xboot_check_reset_lock: Invalid param

We patched newflasher to allow flashing of following TA units as newflasher normally does not allow to flash them:

memcmp(unit, "000007D3", 8) == 0 || /* hardware config */
memcmp(unit, "000007DA", 8) == 0 || /* simlock */
memcmp(unit, "00000851", 8) == 0 || /* simlock signature */

As @craspo had the right TA backup from the working (locked) state of the phone, we could extract content of the above 3 ta units, convert them to .ta files compatible with newflasher and eventually flash them with the patched newflasher.

That made the phone booting to android (and to fastboot) again, even though still running a frankenstein TA content (all content from a different phone fixed with hwconfig and simlock with signature TA units restored from the TA backup of the original phone).

This "experiment" kind of shows that it is possible to run a TA from a different xz1c unit, if it is fixed with hw specific TA units.

This half recovered state allowed the phone to boot android and work normally (including GSM, LTE, wifi, GPS, ...) as kindly tested by @craspo - thank you for the testing.

This obviously would not allow to use TA from different phone unit aiming to clone imei or remove operator lock, because the above 3 ta units do contain imei, bootloader and optional lock for an operator and are signature bound to hw ids of the phone, i.e. if they are not right (crypthographically signature verified), the chain of trust would be broken and the phone would not boot at all (luckily except the boot to sony flash mode).

Still this experiment shows that we may clone other TA settings from a different xz1c unit by running foreign TA fixed with hwconfig and simlock from the original xz1c unit.
[Sony Xperia XZ1 Compact ROMs, Kernels, Recoveries,] tonsofquestions:
Very nice, congrats!

A fascinating story, and great information to have in hand.
[Sony Xperia XZ1 Compact ROMs, Kernels, Recoveries,] ahuaiab:
After entering ./renoroot, the phone displays like this

But renoroot failed
[Sony Xperia XZ1 Compact ROMs, Kernels, Recoveries,] norabitox:
[XZ1c/XZ1/XZp] temp root exploit via CVE-2019-2215 including magisk setup [Locked BL]

temp root exploit for sony xperia XZ1c/XZ1/XZp with oreo firmware by j4nn https://j4nn.github.io/ Let me present you a temp root exploit for sony xperia XZ1 Compact / XZ1 / XZ Premium phones running android oreo firmware. The exploit uses...

xdaforums.com

This is a better way to backup TA with temporary root.
[Sony Xperia XZ1 Compact ROMs, Kernels, Recoveries,] rom4nb:
Hello together,

as my very much liked Samsung S4 Mini Plus is getting more and more hindered by the only 8 GB internal memory and LineageOS 18.1 (latest that has SELinux restricted for that devide) is end of life I am happy to have found a Sony XZ1 Compact on Ebay as compact device. :)

My device is international version (G98441) with latest Sony Android 9 ROM installed (47.2.A.11.228)

I want now to backup the DRM keys before I try a custom ROM.

I have some questions:

Question1: I understood that it is necessary to go back to a Android 8 Sony Stock ROM before backup the DRM keys. I read that you have to take care already at this step and I am not really sure whether there is something special to consider that is not found in the first post but in some other linked threads.

I found this here: https://xdaforums.com/t/xz1-compact-pie-to-oreo-downgrade.3890302/#post-78794330

Are these files arleady removed in the images uploaded for the XZ1C in the first post of this thread?

Question 2: I am aware that even with backup of DRM keys I will never be able to re-lock the bootloader with the XZ1C again. If necessary, how can I get most closest back to stock? My guess:

Get original SONY ROM (which one? the one I extracted the DRM keys with or the latest Android 9 one) with XPeri Tool

Flash the ROM with newflasher

Restore DRM Keys before unlock bootloader

Use Stock ROM

Question 3: As I understand, I would have all functionalities (Sony Camera, DRM for Netflix, OTA which will not be new one) but there will always be the warning with the unlocked bootloader when I boot up the phone. Is that right or do I even have drawbacks with the backup DRM keys?

Last question: does it make sense to restore the DRM keys before unlocking the bootloader even though I wan to use a current android custom ROM (e.g. LineageOS 20.1) with the device?

Thank you for your answers. :)
[Sony Xperia XZ1 Compact ROMs, Kernels, Recoveries,] j4nn:
No, stock firmware posted contains all the stuff as downloaded from sony.

You would restore drm key right after unlock, no need to "restore" it more times after that.

Just flash the latest stock fw and use the kernel hiding booloader unlock to get to locked state close.

Unfortunately that would probably not be enough for difficult apps likes latest google pay or netflix. You would probably need some more hacks, like spoofing device fw build id to a device which was not released with hardware attestation support.

Cannot help any further in this field, as I am not using apps that need this level of unlock hiding.

Yes, the warning would stay forever there after bootloader unlock, regardless drm key restored or not.

With bootloader unlock there are drawbacks that google services and other apps can detect that and it may be difficult to hide this, so some apps may not work or work with less/restricted features.

This has not been the case in early days of these phones.

But apparently I hear that it still can be circumvented.

The biggest drawback may be that sony stock camera app is not supported on roms with android newer than version 10 - there is alternative camera app that works, but the quality and features may not be the same as sony stock camera app (with drm key restored).

Maybe yes, I hear there is an experimental version of stock camera with limited features there too, but cannot comment more on that as I did not test it myself yet.

I would recommend to backup drm key before unlock and restore it after just because it can be done and it cannot hurt. Use the alternative (faster) exploit as linked above by norabitox (and also linked in the 1st post of this thread).
[Sony Xperia XZ1 Compact ROMs, Kernels, Recoveries,] rom4nb:
Hi j4nn. Thank you for your help! :)

I managed to bakckup my DRM keys, the exploit using bindershell worked like a charm.

This is what I did:

I downgraded the SONY firmware from Pie to Oreo

I used the ROM G8441_47.1.A.8.49

I deleted the persist*.sin file

I deleted 9 *.ta files in the root directory of the unpacked rom but kept the ta-file in the /boot subfolder

I then flashed with newflasher

After downgrade all keys were still there when I checked

I backuped TA-partition while still locked

I was using not the renoroot exploit described here but the bindershell exploit from here)

bindershell failed at the first attempt to get root shell, I simply executed bindershell a second time and then it worked immediately

I unlocked the bootloader

Hint for LInux users: I had to set udev rules that the XZ1C is recognized by fastboot, I roughly followed the instructions here

My file 99-android.rules for udev rules looked like this:

SUBSYSTEM=="usb", ATTR{idVendor}=="0fce", ATTR{idProduct}=="51f4", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="0fce", ATTR{idProduct}=="0dde", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="0fce", ATTR{idProduct}=="b00b", MODE="0666"

With these udev rules, the phone was properly detected in fastboot mode (blue LED when Phone is started with Volume up pressed) (you can check in the terminal with fastboot devices)

I restored the TA-partition with bindershell exploit (this time root shell worked with first attempt) while still on the same Oreo firmware -> it seemed to work, before restoring TA-partition the camera only made green images, now it is working again

Before I continue with TWRP/custom ROMs etc. I have two questions:

Question 1: Since I flashed the OREO firmware, the battery status indicator is stuck at 20% and not changing (see attached screenshot below). What went wrong here?

Question 2: On Oreo Firmware, I went to Service Menu -> Service tests -> Security (see screenshot 2 below) and noticed:

"Rooting status DONE" is because the boot loader is now unlocked? (I have no permanent root via magisk or similar installed yet)

SOMC FIDO Key says NOT PROVISIONED, also SOMC Attest Key -> is this also due to bootloader unlocking, even though I restored the TA-partition?

Android Attest Key says PROVISIONED

Should I first flash the original Sony PIE firmware I received the phone with (again deleting persist*.sin and *.ta files in the root directory of the firmware)?

I would like the battery status to be working again before I do something else. Thank you.
[Sony Xperia XZ1 Compact ROMs, Kernels, Recoveries,] j4nn:
I am sorry, no idea, maybe except there may be battery "history info", that may be used with charging on stock firmware - I guess it could have been in Qnovo partition.

There is Qnovo sin image flashed with stock firmware, which seems empty, effectively erasing previous Qnovo content when flashing stock firmware.

It might be connected to that.

But I never heard of any such problem with battery charging.

If there was not any unrelated hw failure coincidence, I would expect battery charging to get back to normal.

Maybe you can try to power off the phone and plug it to charge "offline"?

It is a bit different mode for charging, it might help.

Yes, this is normal, "rooting" here refers just to "bootloader unlock"

The errors in security screen are there because the firmware detects unlocked bootloader state.

You need to follow the links in the guide to use kernel hiding bootloader unlock to get the security screen working as in the locked state.
[Sony Xperia XZ1 Compact ROMs, Kernels, Recoveries,] rom4nb:
Thanks for your answer j4nn. I tried to follow your advice and left it charging all night while switched off. This morning even the charging screen switched off showed that charging state is only 20% and switching on it also is still 20%.

This is unfortunate and it was since I flashed the Android 8 Oreo firmware (before temp root and backup of DRM keys and before unlocking my bootloader). So something in the downgrade seems to have damaged the battery stats.

In the settings I can see charging state 20% (it never changed to any other number since I have flashed Oreo, be it connected to USB or disconnected) and batterydata not available, see attached screen shot.

Any ideas what could help? Should I flash the Android 9 Pie firmware and again delete persist*.sin and the *.ta files in the root directory of the firmware?

Should I again leave the one ta-file in the boot directory?
[Sony Xperia XZ1 Compact ROMs, Kernels, Recoveries,] norabitox:
adb shell

su

restorecon -RF /persist

reboot

You might want to try this.
[Sony Xperia XZ1 Compact ROMs, Kernels, Recoveries,] norabitox:
It shouldn't damage your device.

I was able to repair a problem with the proximity sensor using this command before.

I don't really understand it, but I think it might be some kind of persistence-related initialization (?).
[Sony Xperia XZ1 Compact ROMs, Kernels, Recoveries,] j4nn:
I can think only of Qnovo partition as mentioned before.

But there has not ever been reported that flashing that would ever cause any trouble.

It is very strange.

I am sorry, but I do not have any more ideas.

You can try to flash the newest stock pie firmware to see if it changes anything.

And yes, do it as you have written, removing the files and keeping .ta and others in boot.

There is a thing I am seeing for the first time in your log and that is the following like there:

Battery level: 0 unsupported command

It seems the latest newflasher version now checks about battery level to avoid flashing when battery is too low.

But checking this in newflasher sources, it just tries to read Battery var and check the value, so I cannot imagine how this could influence battery behavior during fw flashing in any way.

What level of battery you had before starting the downgrade flashing?

How long your battery usually last before you needed to fully charge it again?
[Sony Xperia XZ1 Compact ROMs, Kernels, Recoveries,] rom4nb:
Hi norabitbox and j4nn, thank you for your hints.

The battery was really fine before I changed anything with the latest SONY Pie firmware. When I received the device from ebay, the service menu showed a battery capacity of about 2400 mAh, about 89% of the specified 2700 mAh. I could use the device for days, in idle the battery status hardly dropped and even using it a lot, it lasted 2 days (very impressive!). The battery status indicator dropped when I used it, slower in idle, faster when screen on, and rose - both switched on and switched off - when connected to charging. Everything as expected.

I also wrote in the Newflasher thread and the developer there said I should not delete any *.ta-files or other files. Persist*.sin and "dangerous" ta-files would be skipped automatically.

I think I will try the following this afternoon after work:

Flash again the latest Pie SONY firmware that I got from Xperifirm with the same localization it had when I received it (Germany o2). I will again delete ta-files and the persist*.sin file, because the "original" files should still be present before I used Newflasher the first time, right?

If this does not work, I will need to find out how to get root with Magisk on the Pie firmware (I have never done this before, but it should be possible now as the bootloader is unlocked I suppose, right?) and try the command @norabitbox recommended.

I will report, how it went for me.
[OnePlus 6 Questions & Answers] MadHatter01:
I got my OnePlus 6 the other day and loaded the P beta. Before putting anything on it I was testing what works and found out that I was not able to be text message. I could send but not receive. When I downgraded back to 8.1 everything worked perfect. I know the beta says VoLte is broken (did not have issues making and receiving calls). Any suggestions to fix it, I bought the phone to play with P mostly. I can deal with most bugs, but I need to be able to receive text and pic messages. I am using T-Mobile and no other SIM cards.
[OnePlus 6 Questions & Answers] iamterence:
You literally bought the OP6 mostly just to play with Android P??
[OnePlus 6 Questions & Answers] MadHatter01:
I have a Samsung S9+. I am tired of Samsung slow updates. So I thought I would give this a try. I bought it because of faster updates and very good specs.
[OnePlus 6 Questions & Answers] RetroFX:
me too....
[Xiaomi Redmi Note 5 Pro Questions & Answers] Hridul P.K:
I am on 9.2.7 stable now but I am facing some minor issue when I googled up I saw some post about People saying 9.2.4 is the best version

Is it better than 9.2.7?
[Xiaomi Redmi Note 5 Pro Questions & Answers] vaisakmct:
Ya its better than 9.2.7

Just check back portrait its zoomed image but its not happen in 9.2.4

New beta roms are better 8.5.11
[Xiaomi Redmi Note 5 Pro Questions & Answers] RupeshRN:
I am Currently 9.2.4 out of Box and I not update till.

Portrait mode and Battery Backup Great minimum 8 Hour Screen on time in 9.2.4.

I am always check review of next update and after I update. :)
[Xiaomi Mi A1 Questions & Answers] Ahmed Al-Sayed:
The problem is that my Google play books app keeps disabling itself randomly, every time that happens i have to go to settings and enable it again but it disable itself again after a short time. My play movies app has the same issue either. I have been facing this issue since the first time i bought my device. I tried flashing custom roms but the issue still present .

Does anyone have any idea what causes this ?
[Device Reviews and Information] o-I-c:
Intel® Pentium® Silver Processor Series formerly Gemini Lake

LPDDR4 8GB/128GB Windows 10 Mini PC Intel Dual Band AC WIFI Gigabit LAN Bluetooth HDMI 2 TV Mount

Processor: Gemini Lake N5000

CPU: Gemini Lake N5000 , Quad Core

GPU: Intel HD Graphic 605

RAM: 8G LPDDR4

ROM: 128G eMMC

Communication

WIFI: 2.4/5.8G WiFi, 802.11ac

Bluetooth: Bluetooth4.0

LAN: 1000M

Media

Decoder Format: H.264,H.265

Video format: 4K,4K x 2K,ASF,AVC,AVI,DAT,FLV,ISO,MP4,RM,RMVB,RV,TS,VOB,V P9,WMV

Audio format: AAC,AC3,ACC,APE,DDP,DTS,MKA,MP3,MPEG,OGA,OGG,RM,Tr ueHD,WAV,WMA

Photo Format: BMP,GIF,JPEG,JPG,PNG

Interface 1* 3.5mm Audio

1* DC Power Port

2* HDMI 2.0

1* LAN

1* Reset Port

1* TF Card Slot

2* USB3.0

2* USB2.0

Other Features

Language: Multi-language

Other Functions: ISO Files

HDMI Function: HDCP

Remote Controller Battery: 2pcs x AAA batteries

Support 5.1 Surround Sound Output: Yes

Power Power Consumption.: 18W

Power Type: External Power Adapter Mode

Power Supply: Charge Adapter

Dimension&Weight Product weight: 0.3370 kg

Package weight: 0.7900 kg

Product size (L x W x H): 11.90 x 11.90 x 2.00 cm / 4.69 x 4.69 x 0.79 inches

Package size (L x W x H): 13.65 x 12.90 x 8.55 cm / 5.37 x 5.08 x 3.37 inches

Package Contents

1 x Beelink S2 Mini PC

1 x Power Adapter

1 x English User Manual

1 x Mini PC Bracket

review soon ;)
[Device Reviews and Information] ajaxxa:
hi, I need to buy a mini-pc windows, but it seems that on the net you don't find the model I'm looking for!

Where can I buy a beelink SII 8GB / 128GB HD Graphics 605?

In general, however, these mini-PCs do not offer much choice ... especially beelink.
[Huawei Mate 10  Questions & Answers] themagicalmage22:
I have tried installing through ADB and used the one provided by KingOfMezi. Have also tried the automated installation of CATUVA21. It always brings me to the Huawei eRecovery. I have unlocked bootloader, USB Debugging is on too.
[Huawei Mate 10  Questions & Answers] usman400:
First indicate which version are you in, Noughat or Oreo ??? I say so bcoz there are separate recoveries for

the 2 versions of Android available here @ XDA

Also indicate what happens when you try to flash the TWRP after fastboot command, does it say

FAILED or any error or it installs properly ? Send screenshot of your fastboot command and its result
[Huawei Mate 10  Questions & Answers] beatme07:
If i were you dont install twrp now. On huawei nova 2i because the device is new. Developers of twrp have some issue to backup all of the system data. So it is useless and remember you cant update OTA. I rooted and install twrp now i regret. Because stock roms and software update are hard to find. And you cant flash it so easy. Im just giving you an idea.
[OnePlus 6 Questions & Answers] SAMVREMIX:
Anyone else notice apps reload way to often? I have the 6gb model and apps reload after the 7th or 8th app. Only having about 40-50% ram utilisation. Anyone had the same issue. I had a OnePlus 3 before this where I could change the amount off apps open. Can we do the same on this phone too?
[OnePlus 6 Questions & Answers] :
I've noticed that as well.
[OnePlus 6 Questions & Answers] harigavara:
Even i could see the apps in recent apps list are reloading
[OnePlus 6 Questions & Answers] snaker445:
Yes. Same here. But the only app that is reloading is the Tapatalk app.
[Xiaomi Redmi Note 5 Pro Questions & Answers] SamdAbnormal:
Can anyone tell how to activate the game booster mode?

Sent from my Redmi note 5 pro running on miui 9.2.7.0
[Xiaomi Redmi Note 5 Pro Questions & Answers] gohan456:
go into the security app, scroll down and pick the booster, then there is a list of games to pick. picking them starts them with the booster.
[Xiaomi Redmi Note 5 Pro Questions & Answers] sharmasrb:
It just cleans your ram. I recommend not using it. We are not running gingerbread these days. Nougat can handle ram management by itself. Also kryo chip is fast enough to handle heavy games. No need to clear ram
[Xiaomi Redmi Note 5 Pro Questions & Answers] gohan456:
ya they should have atleast added an change resolution option like samsungs game booster.
[OnePlus 6 Questions & Answers] Contivity:
Hi All,

This is my first time using 1+ and noticed that I can't change the nav bar color. I tried to use the NavBar app on the playstore, but the setting doesn't stick for home screen using Nova. Anyone know how to change it?
[OnePlus 6 Questions & Answers] brangalm:
Would also like to know. Sometimes it's dark, sometimes it's light. Hate the inconsistency!
[OnePlus 6 Questions & Answers] Link_of_Hyrule:
I'd rather just have it be black all the time until they can add fast app switching and swiping up on the right side for recents as options to gestures.
[OnePlus 6 Questions & Answers] Zedrox:
It appears they have made the default navbar colour white, which is incredibly annoying.
[OnePlus 6 Questions & Answers] Elpatii:
Guys, use gestures options! The only missing feature with gestures is the lack of fast switching to the latest recent app, yes...
[OnePlus 6 Questions & Answers] jpde:
"Just use the device in a different manner" is not a valid response to "I'd prefer the ability to x".
[LG Stylo 2 Plus Questions & Answers] Validfire:
So, first off... I know this is a BIG no no... wasn't thinking, it was late at night, and I was having some issues getting LG Bridge to recognize my device... made a stupid mistake. Point is... I'm now stuck in a bootloop with the message "Your device is corrupt. It cannot be trusted and will not boot."

Doesn't seem like I can boot into recovery, however I have noted that the default Factory Reset shortcut still lets me through: PWR + Vol Down, but the menus appear to do nothing helpful. I know I'm about as hard-bricked as one can get, but if anyone has a solution... help an idiot out.
[LG Stylo 2 Plus Questions & Answers] -Nahue-:
No worries, you're safe i literally did the same thing yesterday and almost had a heart attack, unplug the phone (if it's plugged), and i'm asuming you've already got Fastboot installed.

Hold the Vol+ Button while plugging in the cable, that should send you into the bootloader, on your computer, open up a cmd where fastboot is, and type in "fastboot.exe oem unlock" (If you have windows that is)

Then do "fastboot.exe reboot" and that should be fixed.
[HTC Wings] rakusson:
hi,

I am using Ubuntu 7.10 and I wanted to do OBEX file transfer through bluetooth by accessing my HTC S730 drive (I am able to do in my old Nokia 6280). However, I failed to do so. Do HTC S730 does not provie OBEX file transfer? or, is there any other way? I will hoping your warm reply. Thanks
[HTC Wings] arpy:
OBEX

Do you look close enought?There is a option named OBEX File Transfer in Bluetooth-Options, enabling the Bluetooth-Explorer and share files in specific folder...:cool:

You have to take a look into your BT-Settings...and enable incoming beams...and dont ask me...
[HTC Wings] 10332007:
I dont know too much about it myself but if the phones BT is more up to date than your old phone you might need to update the software you are using to push?

Dont think Nokia runs WM so it might have functioned a little differently in their OS...
[HTC Wings] bigflavor:
didn't read any of the posts:

http://msdn2.microsoft.com/en-us/library/aa916361.aspx

does this help?
[HTC Wings] bigflavor:
I'll length my post.