yashsingh1/xdaforums huggingface dataset:
[Touch Cruise General] hambola:
I usually have 3G turned off since I have a data connection open all day (Exchange push mail). Not using BT or Wifi regularly, can almost squeeze out 2 days from it.

YMMV, in fact everyone's does. One person's heavy usage is what someone else would consider light. So take it with a grain of salt.
[Sony Xperia 10 Questions & Answers] llamajockey:
I tried the fastboot oem lock command as well as two others that I found googling but nothing works.

I know Sony doesn't want you to be able to lock it again but if there is any way you guys know of please let me know!
[Sony Xperia 10 Questions & Answers] VelocityHD:
Yeah, i want to do that too. Please guys, let us know if there is any possibility.
[Sony Xperia 10 Questions & Answers] Nikobelyk:
Me too, so let me know

My device: Xperia 10 i4113
[Sony Xperia 10 Questions & Answers] Chronic2k13:
You can't
[Sony Xperia 10 Questions & Answers] VelocityHD:
Still nothing? :(
[Sony Xperia 10 Questions & Answers] ttocs99:
Nothing as yet unless someone goes out there way and try to re-lock it. But even then if you haven't backed up .ta for drm then the Xperia will still be not certified.
[Sony Xperia 10 Questions & Answers] Meloferz:
I read on Xperia 1 forum that they could relock bootloader and repair stock ROM with Emma software, and drm keys are back, anyone tested on Xperia 10?
[Sony Xperia 10 Questions & Answers] ttocs99:
I had used Emma to return to stock and there is no option to relock bootloader and or to get drm back.
[Sony Xperia 10 Questions & Answers] Meloferz:
https://xdaforums.com/xperia-1/help/xperia-1-drm-keys-locking-bootloader-t4079715

https://xdaforums.com/xperia-1/how-to/xperia-1-root-guide-t3938304/page16

On the latest thread, Pandemic said that you can lock with fastboot oem lock and repair with Sony companion.
[Sony Xperia 10 Questions & Answers] munjeni:
I can confirm its not possible!
[Sony Xperia 10 Questions & Answers] munjeni:
Some progress on this https://xdaforums.com/xperia-10/themes/drm-fix-drm-fix-unlocked-bootloader-53-t4138269
[Android Head-Units] CharismaKenzie:
Hi, I purchased an AVIN unit a few weeks ago for my E83 (2005 BMW x3 2.5i). I have a weird time issue that I submitted a ticket to AVIN for but they only responded with their stock answer, and I haven't heard anything since. Anyhow, the unit doesn't keep time properly. If I set the time manually it doesn't save the time when the unit is turned off. When I turn it back on again it resets to 10:05am and the date as September 2nd, 2016. If I set it to GPS time, it is an hour slow, even though it's getting the correct time zone. I have no idea how to make this right. If there was an option to just turn the time display off I would do that, but there isn't.

MCU: 023042bGs-E39-HW7-190611[B1280_170325]

App Version: 2019072501_1280x480_970

I note there is an MCU version 191118 for the E39 unit which appears to be newer, but how is that possible if it isn't November yet?
[Android Head-Units] CharismaKenzie:
AVIN got back to me and said that time must be set via GPS Sync (they are giving me mixed messages). Anyhow they provided no direction on fixing the hour out of sync issue. I installed the app "Smart TIme Sync" and sure enough it detects the hour difference, however it needs the device to be rooted to fix the issue. How difficult is it to root these devices?
[Android Head-Units] Chrisu02:
Rooting the PX6 Device with Android 8 is quiet simple, just check the following link: https://xdaforums.com/showpost.php?p=76725981&postcount=740

At Point 4, after the first line "adb connect ..." you maybe need perform the "adb disable-verity" command and reboot the device once again.

And don`t install SuperSU as application afterwards, this may cause troubles, root does also work without the app installed.

Chri
[Android Head-Units] CharismaKenzie:
Sorry, I forgot to mention I have an Android 9 unit. Is the process the same?
[Android Head-Units] Chrisu02:
Hy

Haven`t seen someone with a PX6 & Android 9 yet who rooted it,

You can try the Snapdragon Android 9 Guide https://f30.bimmerpost.com/forums/showpost.php?p=25195472&postcount=173

please give Feedback if it will work of something needs to be modified :)

Chri
[Samsung Galaxy S7 Questions and Answers] BertMcfallen:
Hello, I have a Galaxy S7 G930P with what I believe is the v7 bootloader on Oreo.

I've only rooted a couple times before so I'm not super experienced but this phone is worth nothing to me so I will (and have been I think) risk bricking the phone. From what I understand this is a locked bootloader, so I cannot root it at all, or at least that's what I'm seeing. When I try flashing it with many different APs including engineering ones with multiple failures in Odin.

Depending on which files I'm attempting to flash, I either get and AUTH or a RQT CLOSE error in Odin.

The error on the phone says SW REV CHECK FAIL.

It's a little late in my timezone so my writing is probably horrendous, if you need anymore information I'll be back on in the morning to supply anything else. Thanks!

also please don't roast me, I'm new to this...
[Samsung Galaxy S7 Questions and Answers] PoochyX:
The solution to your issue would be patching your boot img in magisk in tar format and then flashing that img via odin

([emoji3590]09-09-18[emoji3590])
[Samsung Galaxy S7 Questions and Answers] BertMcfallen:
Ah yes I've heard of magisk, I will start researching that right now. Thank you very much!
[Samsung Galaxy S7 Questions and Answers] PoochyX:
Anytime

([emoji3590]09-09-18[emoji3590])
[Samsung Galaxy S7 Questions and Answers] Beanvee7:
From what I've read, you can't get root on sprint and/or bootloader v7

https://xdaforums.com/showpost.php?p=77655646&postcount=882

https://xdaforums.com/showpost.php?p=77663944&postcount=901

https://xdaforums.com/showpost.php?p=77665353&postcount=902

The only root methods for the snapdragon/USA models is by using engineering bootloaders, but you have to be on the right bootloader to flash over to the engineering bootloader, which there doesn't seem to be a v7 engineering bootloader out there
[Samsung Galaxy S7 Questions and Answers] BertMcfallen:
Yeah, unfortunately I am also seeing the same things elsewhere. Thanks for the help.
[Samsung Galaxy S7 Questions and Answers] PoochyX:
Someone with root can patch your img with magisk and you can flash it in odin and it wont work however due to the fact you have a locked bootloader i believe once you flash it in Odin you will get unauthorized binary alert and your phone won't boot

([emoji3590]09-09-18[emoji3590])
[Samsung Galaxy M30 Questions & Answers] zer0C00L......:
We don't want any custom rom just please post a guide on how to flash GSI with working gcam

It'll be more than enough.
[Xiaomi Mi Mix 2 Questions & Answers] yayayeet:
Hey guys,

I am trying to install the latest microG+LineageOS build (20190722), however I get error 7 in TWRP and OrangeFox recovery.

From googling, I believe this might be an issue with the Xiaomi firmware my phone has (Oreo = 10.x or Pie 9.x)

From what I understand (might be wrong), the microG+LOS team uses the official LOS roms and adds the extra stuff, so I had a look at the official LOS thread on xda, which recommends to use MIUI Stable V10.4.1.0.

I flashed 10.4.1.0 and then tried to flash microG+LOS, but I still get Error 7, but regular LOS (20190930) works.

I tried flashing a Pie firmware and then flashing microG+LOS, but that still gives Error 7.

The OP of the official LOS thread recommends against editing the updater-script file.

What can I do?
[Touch Diamond, MDA Compact IV General] lybed:
Hi,

I placed a pre order for the Diamond about 3 weeks ago from HTC direct. They where supposed to be receiving stock tomorrow (6th June).

Sadly i received this email from them this afternoon. At least they might be more reliable!!

"We have just been informed by the only official distributor of HTC products in the UK that the HTC Touch Diamond is now expected to come in on 17th June. The reason for the delay is a last minute software fix that needed to be applied. We appreciate that you have already been waiting a long time for this device, but it is better that known issues are dealt with at source rather then with a later ROM update or patch.

Please be aware that there are some grey-imports available in the UK. These are sourced from the Asian Market and thus come with warranty issues. HTC will not entertain warranty related repairs in the EU. Also, they only have a one year warranty. Also, they shipped without the software fix.

Be assured that your pre-order will be dealt with on the day the stock arrives."
[Touch Diamond, MDA Compact IV General] rorydaredkign:
I wonder if they're making sure every evice has the un-flashable spl?
[Touch Diamond, MDA Compact IV General] Pawel062:
euro spec devices i also heard will have different bands ;)
[Touch Diamond, MDA Compact IV General] chribruu:
I thought Asia and Europe used the same bands or have I misunderstood something?
[Touch Diamond, MDA Compact IV General] Caspertje19:
maybe you'r right...well...I believe in the peoples over here who spent a lot of time helping us out. So I think, they will help us out, it only takes a little bit longer....They will defintly come with a solution
[Samsung Galaxy Note 10+ Questions & Answers] BadBoy2K7:
Hello,

I just got the Samsung Galaxy Note 10+ on September 30th, SM-N975U1 variant, and I cannot toggle the OEM unlocking because it is missing. I read that this is due to the KG state of the phone and I would have to wait 7 days for it to be an option to toggle. I am trying to find out from other Note 10+ users with the same variant as mine if the option appeared after waiting 7 days?
[Samsung Galaxy Note 10+ Questions & Answers] carandcar:
Unfortunately the "U" variant does not have an unlockable bootloader. The OEM toggle is not there so that variant cannot be rooted (no USA variants can at the moment).
[Samsung Galaxy Note 10+ Questions & Answers] intruda119:
Exynos equals root.
[Samsung Galaxy Note 10+ Questions & Answers] gkennedy88:
For realsies? none of the "U" Variant... So I cant root my note 10+ SM-N975U? Dang that really grinds my gears!!!!!!!!

Leave it to samsung to figure out a new way to keep people from rooting their phones... "Hey lets get rid of the OEM unlock toggle, that way they cant unlock the bootloader and root their phone, and will have to keep all the bloatware we, and their carrier, force down their throats against their will, whether they want to or not."

I knew I never should have bought this phone. I swore 6 years ago I would never own another Samsung Device, but then they came out with this cool new phone and I wanted it so bad. I should have just waited until the pixel 4 XL came out and bought it instead.

Guess I'll Know better next time around at least, and by the time I need a new phone hopefully all phones will have the inscreen ultrasonic fingerprint reader.

I HATE YOU SAMSUNG!!!!!!!!
[Samsung Galaxy Note 10+ Questions & Answers] OnnoJ:
1. You could have informed yourself prior to buying, it is common knowledge US SD-models have locked bootloader and cannot be rooted...

2. It is merely a US-provider requirement to have locked bootloader, not Samsung's choice. Note 10/10+ is rootable in most other parts of the world..
[Samsung Galaxy Note 10+ Questions & Answers] gkennedy88:
What do u mean SD Models? Also if it's a us provider requirement then how come you can buy phones that have the OEM unlock option available on them?

Also this page is the first I even heard of it... Every time I search it shows that 7 days after you activate it the OEM unlock shows up. And on top of that just because it's not rootable at the time of purchase doesn't mean somewhere down the line someone won't figure out how to.

In fact my last phone was sold by a carrier, as carrier unlocked, and it had the bootloader toggle on it as well which made rooting a breeze.

I'm sorry but I don't agree with you... It has nothing to do with carriers, it's Samsung who has removed this feature not carriers. This is actually the first phone I've heard of that has the oem bootloader removed from the android software.

And besides that if you buy the carrier unlocked version of the note 10+ it should be your choice what you do with it not carriers and not manufactures.

Oh also I found an article (link below) Where someone managed to root the note 10+ SM-N975U with a patched boot image, which I would assume would also work for SM-N975U1 as well.

So like I said it's only a matter of time before someone figured out how to root it anyway. And my post was me griping at Samsung for doing what they did, and staying if I had waited I could have gotten a device that is made by a company that isn't actively trying to thwart rooting.

Link: http://androidbiits.com/root-samsung-galaxy-note-10-plus-sm-n975u-sm-n975u1-easily/
[Samsung Galaxy Note 10+ Questions & Answers] OnnoJ:
SD=Snapdragon, the SoC of the N975U/N975U1 phones. Those devices for US market have the locked bootloader.

The models with Exynos SoC (Samsung's own SoC), in models of most international markets N975F have working OEM unlock option and thereby unlockable bootloader.

Why would Samsung provide unlockable bootloader for one part of the world, but not for US where phones have US SoC (I.c. Snapdragon)? You tell me...

Maybe you can join this club: https://xdaforums.com/galaxy-note-10+/how-to/bounty-sm-n975u1-note-10-usa-unlocked-t4006249
[Samsung Galaxy Note 10+ Questions & Answers] elliwigy:
lol they sure get a lot of clicks with that fake news
[Samsung Galaxy Note 10+ Questions & Answers] wrecklesswun:
try setting a lock. i've had this same issue and thats what worked for me. Although when i unlock and root, it factory reset which sucked.
[Samsung Galaxy Note 10+ Questions & Answers] isaacpixel:
Well why not do a oneplus/google thing where unlocked versions have unlockable bootloaders while carrier versions don't?
[Samsung Galaxy Note 10+ Questions & Answers] RCALL:
Note 10+ Snapdragon

It is a nice device stock, after flashing the N975U1 firmware with ODIN, and disabling (at least), about 150 system-apps with ADB, it is fast and efficient.

I can't imagine how nice the Note 10+ would be with administrative rights.
[Philips, Sony, TCL Android TV] miljenko:
I would be grateful if somebody can give me an advice. I have Philips 43PUS7303 with Oreo OS in it. When I use Android assistant it always open YouTube app as a search result, never execute command or open option. How to use Assistant for anything else but YouTube search?
[Philips, Sony, TCL Android TV] Toengel:
Hi,

GA is not available in every country... which country is your TV set up?

Toengel@Alex
[Philips, Sony, TCL Android TV] miljenko:
Bosnia

On my Nokia 7 Plus it is working properly

Edit: Actually there is no option in TV to choose country only language. It is same if I choose English, Serbian, Bosnian
[Philips, Sony, TCL Android TV] Toengel:
Hi,

when you make a factory reset, you can chose the country... and language... afaik...

Toengel@Alex
[Off-topic] mrrocketdog:
[MENTION=5938622]timvonlee[/MENTION] , great share :)

i know i'm rooted because i laughed at/could identify with 97% of these. roflmao
[Off-topic] Ambient_:
This was a nice read. Making go back too top so all the xda users find enjoyment.
[Off-topic] AXONUS:
-You know you're rooted when you literally feel like you don't need to have food and keep doing the things which are meaning-less to others :D
[ZTE Blade S6 ROMs, Kernels, Recoveries, & Other De] lightwars:
[I]DISCLAIMER[/I]
[COLOR="red"]Do not mirror my builds![/COLOR] Please post a link to this thread instead.

All information and files — both in source and compiled form — are provided on an as is basis.
No guarantees or warranties are given or implied. The user assumes all risks of any damages
that may occur, including but not limited to loss of data, damages to hardware, or loss of
business profits. Please use at your own risk. Note that unless explicitly allowed by the
warranty covering your device, it should be assumed that any warranty accompanying your
device will be voided if you tamper with either the system software or the hardware.

Introduction

Features

Installation instructions

Changelog:

Downloads

Sources

FAQ

Thanks To/Credits

*aquaris-dev team
*aymende7
*PacMM79
*LineageOS team
*many others

XDA:DevDB Information

Unofficial LineageOS 16.0 [PQ3A.190801.002] P839F30, ROM for the ZTE Blade S6

Contributors

lightwars

ROM OS Version: 9.x Pie

ROM Kernel: Linux 3.10.x

Based On: LineageOS 16.0

Version Information

Status: Beta

Current Beta Version: 20191213

Beta Release Date: 2019-12-22

Created 2019-10-04

Last Updated 2019-12-22
[ZTE Blade S6 ROMs, Kernels, Recoveries, & Other De] roomrom:
many thanks for the new version, i will tested later :good: :highfive:

Hello, works on my ZTE Blade S6 Plus (p839f50)

but only with a fixed updater-script

from Folder: lineage-16.0-20191002-UNOFFICIAL-p839f30.zip\META-INF\com\google\android

the bold text must delete and than save the file

after the start my phone , i have a error message with bluetooth is deactivated

updater-script - original

https://filehorst.de/d/crqjwnjI

updater-script - fixed

https://filehorst.de/d/cbmctorj
[ZTE Blade S6 ROMs, Kernels, Recoveries, & Other De] lightwars:
new update is in the op.

just small changes and updated security patch level.
[ZTE Blade S6 ROMs, Kernels, Recoveries, & Other De] Kurt Krummbein:
Anybody tested with EU device?

... at the moment no time to test myself (to much effort to keep my other devices up-to-date ;)), just wanted to ask if anybody already tested on EU device (and forgot to post ;) ).

Gtz

Kurt
[ZTE Blade S6 ROMs, Kernels, Recoveries, & Other De] Kurt Krummbein:
Answer my own request, gave it a try, didn't boot, screen stayed black and device went into fastboot-mode ... restored my nandroid-backup of stock-EU-B15 :(.

Next time, i format system and just install rom without gapps and addon-su.

Gtz

Kurt
[ZTE Blade S6 ROMs, Kernels, Recoveries, & Other De] lightwars:
Hello Kurt,

please, if you find the time to do another test. Download the attached zip extract the boot.img and copy it to your device, flash it with twrp right after installing the lineage zip through twrp. report back if something different happens.

I splited the dtb from the zImage and attached the almost stock eu dtb, so maybe we are lucky. But I have not find any big differences in analyzing the dts of EU vs AS and kernel defconfigs EU vs AS.

I can show this files too, if somebody has a better understanding of this.
[ZTE Blade S6 ROMs, Kernels, Recoveries, & Other De] Kurt Krummbein:
Hi!

Well, i loaded the def's and config's into WinMerge and did a compare ... in the def's there are some different addresses, but i have now clue what the meaning of that all is :confused: :angel:. The config files look like beeing from different kernel versions, there are some options which don't exist in both, one is modularised, the other is not ... all in all quite strange.

Ok, i made a try with the boot_eu.img:

- Made a factory reset

- Flashed the LOS.zip

- Wiped caches

- unzipped the boot.img

- copied it to boot partition with dd if=boot_eu.img of=/dev/block/bootdevice/by-name/boot

- reboot

... screen goes black, one buzz .... nothing. One the PC the fastboot device appears and that's it. I was looking for tombstones, but couldn't find any ... they are stored to /data/tombstones, are they? I'm not sure, the kernel i getting up high enough to mount /data.

Cheers

Kurt

P.S.: one thing i forgot to mention ... i coulnd't find the "OEM unlock" swich in the stock system anywhere and the bootloader seems to be quite dumb, many commands from fastboot just end in a "command unknown", perhaps there's something left to do on my side (tweak in build.prop etc ... googleed for it no result :( ).
[ZTE Blade S6 ROMs, Kernels, Recoveries, & Other De] lightwars:
Thanks for testing. You used the reboot system button of twrp I guess. Have you tried to reboot by pressing the power button?

I can think of two things: There is some flag in the kernel source which is called download_mode. I have seen that some devices have different default values! At the moment the value is 0, devices like the ones from bq with msm8916/msm8939 used this too, but devices from oppo with msm8939 uses a value of 1 as default. We can try this one.

Or there is a mask, which defines the restart reason so to speak says the device which mode to boot to. Here we have some differences in the meaning of the bits, a different bit shifting is used.

I can not really think that one of these causes your device to boot into download mode, because the recovery uses the same kernel on both region variants...
[ZTE Blade S6 ROMs, Kernels, Recoveries, & Other De] Kurt Krummbein:
Ok, tried it ... same result. Then did a (perhaps a bit wired) test, just restored boot from my nandroid-backup. With this, the white ZTE bootscreen comes up and after some seconds it reboots to twrp.

Perhaps the dumb-bootloader refuses to boot with AS keys ... otherwise it wouldn't boot recovery. Strange puzzle.

Cheers

Kurt
[ZTE Blade S6 ROMs, Kernels, Recoveries, & Other De] lightwars:
It is okay to do some unusual testings. I was doing this sort of things also, back then.

I'm not sure I get you, when you write about AS keys. Do you mean the fingerprint in the build.prop? I think I used the ones from the eu version. Maybe they build in some kind of kernel version check inside the bootloader, but only for the eu and other versions.:confused:

The cause is, that android needs an advanced kernel, so we can not use the stock kernel to boot newer android version like nougat, oreo or pie.

Sorry, I can not be of much help here, because I do not have a device with eu or some other region version. But we can try do some changes, if you like to do some more testing and maybe get something like a log, last_kmseg or ramoops. We should look to activate some of them.
[ZTE Blade S6 ROMs, Kernels, Recoveries, & Other De] lightwars:
Hello [MENTION=4179977]Kurt Krummbein[/MENTION],

if you find the time please post the info you get by issuing this commands in the adb shell or on your phone in a terminal:

su
cat /sys/zte_board_id/board_id
cat /proc/device-tree/model
cat /proc/device-tree/compatible

Do this on your rom or stock rom you are using a the moment. Thank you.

For reference mine output is this:

Blade-S6:/ # cat /sys/zte_board_id/board_id
wrbA
Blade-S6:/ # cat /proc/device-tree/model
Qualcomm Technologies, Inc. MSM 8939 MTP
Blade-S6:/ # cat /proc/device-tree/compatible
qcom,msm8939-mtp qcom,msm8939 qcom,mtp

It could be that the eu variant uses another device tree inside the kernel, because the bootloader request that, but we have only this model available.
[ZTE Blade S6 ROMs, Kernels, Recoveries, & Other De] Kurt Krummbein:
Mine is:

cat /sys/zte_board_id/board_id

wrbA-EUROPE

cat: /proc/device-tree/model: No such file or directory

cat: /proc/device-tree/compatible: No such file or directory

ls /proc/device-tree

/proc/device-tree: No such file or directory

Attached my build.prop ... perhaps this sheds some light ;).

Thx

Kurt
[ZTE Blade S6 ROMs, Kernels, Recoveries, & Other De] lightwars:
Sorry for that, I forgot that the stock kernel did not expose the device tree.

But I think I remeber the info about the model is in the logcat after boot up...

Please try this ones in a terminal on the phone or via adb shell, they should work.

su
Blade-S6:/ # cat /sys/devices/soc0/hw_platform
MTP
Blade-S6:/ # cat /sys/devices/soc0/soc_id
239
[ZTE Blade S6 ROMs, Kernels, Recoveries, & Other De] Kurt Krummbein:
mine is:

cat /sys/devices/soc0/hw_platform

MTP

cat /sys/devices/soc0/soc_id

268

cat /sys/devices/soc0/image_version

10:LRX22G:eng.root.20150808.123811

Gtz

Kurt