yashsingh1/xdaforums huggingface dataset:
[Moto X4 Questions & Answers] TaranScorp:
unlock your bootloader, boot TWRP, and install magisk.

Your speaking in a foreign tongue to me. I don't have a clue how do those things I never even heard of root till I bought this new phone. The company told me that on my particular phone it's harder to root.
[Moto X4 Questions & Answers] Siddhesh K:
I suppose you know sim card is used for calling purpose. It may also be used to store contacts but not other stuff. If you can manage without notification led then I'd suggest don't root. You may use moto display feature which automatically shows notifications when you peek up the device.
[Moto X4 Questions & Answers] TaranScorp:
Yea I meant Sd card. Told you I'm new to all this moto x4 stuff. I took the sim card out of my Iphone se and put it in my moto and had a instantly usable moto phone. :)
[Moto X4 Questions & Answers] Helhound0:
[MENTION=9838219]TaranScorp[/MENTION] Whoever said rooting a Moto X4 is hard, is trying to rip you off. I personally have used MANY phones that's WAY harder to root than our device. As someone else said, it's just three main steps. And will only take around 20 minutes, including all the prepwork.
[Moto X4 Questions & Answers] vidra:
If you wish to use your sd card to store your photos on it; open Camera -> Swipe Left -> Click the small wheel in the top right corner -> Save settings -> click on storage -> choose SD Card

Also, everything needed to root this phone is FREE!! if somebody is telling you otherwise he is trying to scam you.

And you can just enable the Moto Display instead of the LED light and then you don't even have to root your phone.
[Moto X4 Questions & Answers] edufur:
In general, I would recommend against rooting this phone unless you have very specific needs that just wont be satisfied without root. The reason I say that is because once you unlock this phone, you will never be able to use Google Pay unless you are rooted AND google hasn't figured out that you are rooted / unlocked. Sometimes you can trick them (with latest Magisk methods), and sometimes you cannot. Even if you re-lock your phone and go back to a stock build, it will never be able to use google pay since the tampered flag is permanent.
[8525, TyTN, MDA Vario II, JasJam General] killerjump:
Man, I didn't even plan to have alliteration, and there it is!

So, I have had my cingular 8525 for about a year right now, and in the last 2 weeks or so I have been getting some bad problems popping up. For some background, I bought the phone in Texas and was using it on the cingular network for some time when they switched to the AT&T network. I flashed VP3G's AT&T roms using hardSPL and they worked well for some time. Then, I came to Europe to do a semseter abroad. I unlocked my phone using some software I found here on the forums (don't remember exactly what it was) and got an 02 SIM card. Everything went fine, was working well until I went on holiday to Europe. I didn't really use my phone much there because it was so expensive, but as soon as I got back I started to have problems.

For about a week, my phone would just drop in and out of service in places that it had not had any trouble working in before. What would happen is, in the place where there is normally the bars for reception, there would simply be an exclamation point and any time I would try to make a call it would fail, sometimes with a message, sometimes without. Then a couple of seconds later, I would have full service again, then it would go to the exclamation point again, full service, etc. It just kept cycling through them.

So, I came to my trusty forums here to try and figure out what was wrong. I flashed a different radio (from 1.47.30.10 to 1.48.0.0) which didn't fix it. I tried downgrading my SPL from hardSPL to 1.04, then upgrading back to the most recent hardSPL v7, which didn't work. I tried putting a new OS on it, the 19900 build, which didn't work. I tried switching the radio back, which didn't work. Then I started noticing that when I was starting up my phone, I was getting a 'no GSM' dialog where it used to say the radio version. I searched around the forums, finding some different solutions for the no GSM problem, and decided to try completly reflashing to an AT&T shipped rom.

So, I downloaded the ROM from the HTC site, downgraded my SPL to 1.04 again, and started the flash process. At 11% it stopped and had an error, and after that it wouldn't leave bootloader mode. I again searched the forum and tried to use MTTY to fix it. The command 'set 14 0' didn't work but 'set 16 0' did.

Now, my phone boots again, but it starts up with the AT&T screen, then goes into the 19900 build OS. As it stands now, I still keep dropping in and out of service, but I am afraid to try any more fixes for fear that I will screw something up again (like locking it in bootloader mode). Any ideas of the next step I should take to fix my (probably) corrupt radio?

OS: PDAVIET build 19900

Radio: 1.47.30.10

IPL: 1.03 (from failed AT&T flash)

SPL: 1.11 (from failed AT&T flash)
[8525, TyTN, MDA Vario II, JasJam General] killerjump:
Update: I just soft reset my phone, and now the 'phone' feature of it won't even turn on when I select it in the comm manager!

Update update: As I was writing this, the phone just turned itself back on without me trying to in the comm manager. Maybe its just possessed, and I should seek the help of a priest!
[8525, TyTN, MDA Vario II, JasJam General] ultramag69:
1). Have you tried taking out the battery for a while? It seems that the hard reset is somewhat different from the soft reset and can fix this...

2). Check for bad blocks with MTTY... Remember though that sometimes the carriers put in "Bad Block" to brand the phone as theirs...

3). Try flashing a stock rom then reflashing wm6.1. This seems to help a hell of a lot of people fix the HR problem.

Hope these help you.... Cheers.:D
[Samsung Galaxy S10 Questions & Answers] gilius2k15:
I tried the following:

Download toolchain from https://android.googlesource.com/pl....9/+/e54105c9f893a376232e0fc539c0e7c01c829b1e

Download clang-4639204

sudo apt-get install -y build-essential kernel-package libncurses5-dev bzip2

sudo apt-get install flex bison

sudo apt-get install libelf-dev

export CROSS_COMPILE=/home/gilius/Desktop/tool/bin/aarch64-linux-android-

export ARCH=arm64

enter the 9820 directory

sudo -i

make xynos9820-beyond2lte_defconfig

make -j10

Am getting the following errors:

arch/arm64/Makefile:27: ld does not support --fix-cortex-a53-843419; kernel may be susceptible to erratum
arch/arm64/Makefile:57: Detected assembler with broken .inst; disassembly will be unreliable
../PLATFORM/prebuilts/clang/host/linux-x86/clang-4639204/bin/clang.real: error while loading shared libraries: libtinfo.so.5: cannot open shared object file: No such file or directory
../PLATFORM/prebuilts/clang/host/linux-x86/clang-4639204/bin/clang.real: error while loading shared libraries: libtinfo.so.5: cannot open shared object file: No such file or directory
../PLATFORM/prebuilts/clang/host/linux-x86/clang-4639204/bin/clang.real: error while loading shared libraries: libtinfo.so.5: cannot open shared object file: No such file or directory
../PLATFORM/prebuilts/clang/host/linux-x86/clang-4639204/bin/clang.real: error while loading shared libraries: libtinfo.so.5: cannot open shared object file: No such file or directory
CHK include/config/kernel.release
../PLATFORM/prebuilts/clang/host/linux-x86/clang-4639204/bin/clang.real: error while loading shared libraries: libtinfo.so.5: cannot open shared object file: No such file or directory
Cannot use CONFIG_CC_STACKPROTECTOR_STRONG: -fstack-protector-strong not supported by compiler
make: *** [Makefile:1244: prepare-compiler-check] Error 1
make: *** Waiting for unfinished jobs....
[Samsung Galaxy S10 Questions & Answers] shmsh9:
Hi,

for me : sudo ln -s /usr/lib/libtinfo.so /usr/lib/libtinfo.so.5 did the trick but I am now stuck with some assembly instructions "not existing" errors when compiling arch/arm64/kernel/vdso/gettimeofday.S

did you made any progress?

Update : linking libtinfo.so.6 to libtinfo.so.5 solved it but also failed with :

scripts/selinux/genheaders/genheaders.c:19:

./security/selinux/include/classmap.h:251:2: erreur: #error New address family defined, please update secclass_map.

251 | #error New address family defined, please update secclass_map.

| ^~~~~

make[3]: *** [scripts/Makefile.host:102: scripts/selinux/genheaders/genheaders] Error 1

make[2]: *** [scripts/Makefile.build:673: scripts/selinux/genheaders] Error 2

make[1]: *** [scripts/Makefile.build:673: scripts/selinux] Error 2

make: *** [Makefile:607: scripts] Error 2

I am currently trying it on archlinux and the ncurses5-compat-libs package didn't put a new library in my path I will try later on another distro see if it's just a library error.

Update 2 :

Compiled fine using rhel 8, I had to install ncurses compat libs and create a symbolic link from python2 to python in my $PATH.
[Samsung Galaxy S10 Questions & Answers] Akugila:
Does it boot?

Does your kernel boot?

Mine, keep stuck at Samsung logo
[Samsung Galaxy S10 Questions & Answers] shmsh9:
Non, I can't even go further the unlocked warning screen, but my repacking of the image is wrong, my new image is always lighter than the original, I am using magiskboot to do it. How are you doing it ?
[Samsung Galaxy S10 Questions & Answers] Akugila:
try AIK

Ahh, fool me. it's stuck at warning screen too (forgot there are another samsung logo during boot)

I use AIK [https://xdaforums.com/showthread.php?t=2073775] for packing, the size is the same with original (I use "Image" file)
[Samsung Galaxy S10 Questions & Answers] floor51:
kernel build error: expected parameter declarator

Did you get these compilation errors?

In file included from kernel/bounds.c:10:

In file included from ./include/linux/page-flags.h:10:

In file included from ./include/linux/bug.h:5:

In file included from ./arch/arm64/include/asm/bug.h:37:

In file included from ./include/asm-generic/bug.h:16:

In file included from ./include/linux/kernel.h:14:

./include/linux/printk.h:149:24: error: expected parameter declarator

static inline __printf(1, 2) __cold

^

./include/linux/printk.h:149:24: error: expected ')'

./include/linux/printk.h:149:23: note: to match this '('

static inline __printf(1, 2) __cold

^

./include/linux/printk.h:149:23: error: this function declaration is not a prototype [-Werror,-Wstrict-prototypes]

static inline __printf(1, 2) __cold

^

void

./include/linux/printk.h:149:29: error: expected ';' after top level declarator

static inline __printf(1, 2) __cold

^
[Samsung Galaxy S10 Questions & Answers] floor51:
Linaro 4.9.4 aarch64-linux-gnu compiler tools for S10 5G kernel build

I found that using the Linaro 4.9.4 aarch64-linux-gnu compiler tools solved this:

https://releases.linaro.org/compone...4.9.4-2017.01-x86_64_aarch64-linux-gnu.tar.xz

I was previously using the toolchain that is in ianmacd's github repo here:

https://github.com/ianmacd/beyond2l...p/gcc-cfp-jopp-only/aarch64-linux-android-4.9

I changed this:

#CROSS_COMPILE ?= $(srctree)/toolchain/gcc-cfp/gcc-cfp-jopp-only/aarch64-linux-android-4.9/bin/aarch64-linux-android-

...to:

CROSS_COMPILE ?= ~/dev/projects/android/kernel/gcc-linaro-4.9.4-2017.01-x86_64_aarch64-linux-gnu/bin/aarch64-linux-gnu-

I also used Linaro for CLANG_TRIPLE.

And I used clang for CC:

CC = ~/dev/projects/android/kernel/clang-4639204/bin/clang

...from here:

https://android.googlesource.com/pl...archive/android-9.0.0_r1/clang-4639204.tar.gz

All that info would have helped me a lot anyway. Hope it helps someone. Not that I've tried the image on device yet.
[Samsung Galaxy S10 Questions & Answers] JPNZ4:
Hey,

I have managed to build the kernel by following the instructions in the samsung readme.

$ export ANDROID_MAJOR_VERSION=p
$ make ARCH=arm64 exynos9820-d2s_defconfig
$ make ARCH=arm64

I end up with an Image file and Image.gz with the same Image file inside. I'm not sure if this has built correctly as people talk about being able to use Android kitchen or similar unpacker to unpack and repack the img file. With the Image file I receive it is incompatible with Android Kitchen and another Perl unpacker I have tried.

When you compile your kernel do you get an Image.img file? Or the same as me, just Image, and if so, how do you make it usable?
[Samsung Galaxy S10 Questions & Answers] jamesBean:
glad to hear that you could build the kernel.

could you please elaborate which build env you used and which version?

make clean destroys my build env and i needed some patches to make it even compile in the first place.

could you run the kernel successfully on the device?
[Samsung Galaxy S10 Questions & Answers] papitoonichan:
How can it be to compile a kernel for Android 13?
[OnePlus 5T  Questions & Answers] srs5694:
I took delivery of a Tesla Model 3 on March 30 of this year. At the time, it was running Tesla's software 2019.5.15, but within a day it had upgraded to 2019.8.4, then 2019.8.5, then 2019.12.1 a couple of days ago, and finally to 2019.12.1.1 today. Through all of this, I've had no problems with Bluetooth connections to my OnePlus 5t phone for media streaming; however, I have had problems with placing and receiving phone calls, and the problem has gotten worse with Tesla's 2019.12.1 or 2019.12.1.1 (I'm not sure which).

I never tried making phone calls in the day or so I had Tesla's 2019.5.15, but I did with 2019.8.x, with about a 50% success rate. Sometimes it would work fine, but other times I'd get very stuttery sound, as if the connection was cutting in and out about ten times per second. Initially, I was running LineageOS 15.1; however, in part because I hoped to resolve this problem, I updated my phone to LineageOS 16 about two weeks ago. That update did not fix the problem, unfortunately, but it also did not make it any worse.

Since my car has updated to 2019.12.1 or 2019.12.1.1, though, the problem has gotten worse: Now, when I try to place a call, at best I'll hear a brief click, short series of clicks, or beep, and then I get silence. When receiving a call, the phone rings, I hear a ring tone over the Tesla's audio system, and the Tesla's screen shows an incoming call. I can answer the call via the Tesla's screen, but again, I get no audio. Worse than all of this, sometimes, on both incoming and outgoing calls, the Tesla's screen has gone completely blank a few times. This isn't guaranteed to happen, but it's happened at least four times to me today as I've been testing things.

Some of what I've tried, with no success:

Adjusting volume settings on both the car and the phone

De-pairing the phone and the car, rebooting both, and then re-pairing them

Updating the phone to the very latest LineageOS build (lineage-16.0-20190428-nightly-dumpling-signed.zip)

Using "developer mode" Android options to adjust every Bluetooth option I could find (AVRCP version, audio codec, audio sample rate, bits per sample, channel mode [stereo vs. mono], LDAC codec)

Testing with both incoming and outgoing calls

This same phone works fine with a Bluetooth headset. On my previous car (a 2017 Chevy Volt), I had few problems, although on about 5% of the calls, I did experience the stuttering audio problem that kicked up to 50% frequency with the Tesla before it stopped working altogether.

I've gone to Tesla's Web site and used their "contact us" link to file a bug report (although there was no "bug report" option, so it may not get routed correctly).

Does anybody here have any other ideas of what I could do, short of replacing my phone or installing another Android version? (I'm really trying to avoid the pain of setting everything up again!)
[OnePlus 5T  Questions & Answers] sam3000:
Hello again from TMF (turok3000) :). Can confirm I see exactly the same as you (lineage 16.0 + tesla 2019.12.1.1).

I would say you're best off posting here: https://xdaforums.com/oneplus-5t/development/rom-lineageos-16-0-pie-oneplus-5t-t3843026

Do you happen to have tried with latest stock oxygenos ? I'm guessing not since you mention not wanting setup hassle (I'm in a similar situation).
[OnePlus 5T  Questions & Answers] srs5694:
Thanks for the suggestion of posting in another thread. I've done so, with a few updates.

I did back up the phone and tried installing stock OxygenOS as a test; however, the installation went badly -- it hung with a spinning logo on first boot. Thus, I restored my (mostly) working configuration. I may give it another try later, but there's only so much time I can invest in this sort of thing each day.
[OnePlus 5T  Questions & Answers] crash4fun:
Any luck with this? I also have a Tesla Model 3 and the same exact problem as you. I'm using crDroid but it is largely based on LineageOS.

Maybe there is something I can try? I messed with all the dev options for bluetooth.
[OnePlus 5T  Questions & Answers] srs5694:
I've worked around it by re-installing OnePlus's OxygenOS. I'd prefer LineageOS or something else more open, but for the moment, switching to OxygenOS seems like the only solution. A caveat: I haven't tried any recent build (from the last month or so). It's conceivable it's been fixed and I just don't know it yet. Also, some others, using OnePlus phones other than the 5t (IIRC, the OnePlus 6 and/or 3) report that reverting to OxygenOS does not help them. If you've got a 5t, though, reverting to OxygenOS, although a nuisance, may be worth trying. There's a thread tracking the problem on a Tesla forum here:

https://teslamotorsclub.com/tmc/threads/bluetooth-problems-on-phone-calls-only.150774/

The problem is common on LineageOS for multiple phones, but it also occurs on some other phones, even including some iPhones. At least one unofficial LineageOS build is not affected; but that build may have been tweaked or rely on proprietary drivers. Overall, then, it looks like more of a Tesla problem than a phone problem, but it's hard to be sure without digging into the code and running diagnostics that I'm not competent to do.
[OnePlus 5T  Questions & Answers] crash4fun:
Ah well thanks for getting back. That is disheartening, as I had been using OOS since I got the phone on release day & finally thought I should try something different. It sounds like I'm gonna have to go through all the efforts to revert back to OOS.

For reference, it did not work for me using crDroid builds from 6/23/19 and 6/30/19.

I'll use Tesla's feedback system to put my "vote" in towards fixing these bluetooth issues.
[OnePlus 5T  Questions & Answers] crash4fun:
My Model 3 received an update yesterday to 2019.24.4 and the Bluetooth calling works! Just thought you should know. I'll cross post on TMC.
[Moto Z2 Force  Questions & Answers] Loperaco:
Hi everybody.

As I know that it is possible that someone wants to know why I need a deep cable here is a super summary of my catastrophe:

I made a root in my Z2 Force with the bootloader unlocked (thanks to the number that Motorola gives to do that) and with the SU, after that I knew (not before, damn) that some applications don't work on root cell phones (****) among these my bank app, Netflix app, Fox app (**** **** ****), even using the Root Cloak app and others like that the result is that they don't work, so I needed to return to the unroot state, until there everything manageable, buuuuuuuuut, when I had to flash the stock ROM I downloaded the wrong version (fuuuuuuuck), the result was that the cell phone doesn't recognize the SIM cards, doesn't allow the use of WIFI, my IMEI was lost (wtf!) and when I try to flash again (in fastboot) with the correct ROM stock the bootloader doesn't leave me because it says "Flashing_locked", (what? but if I already unlocked it before !, well no, the ****ing cell phone doesn't recognize that, if I try to unblock it through the fastboot commands give as results that the process was satisfactory, but when restarting the bootloader it says NO, I'm still locked mother****er ! ...........

Well, that's why I need a deep cable, to flash with the (foolish) "Flasing_locked" status. So, the problem is basically that I found on the Internet those who do the deep cable with micro-usb, I haven't found how to do it with a usb-c cable. In the cases with micro-usb you only have to bridge the black and green wires and "ta dah" everything is done, in others I also see in micro-usb the pin 4 is jumpered with pin 1 in the micro-usb connector, but on the usb-c cable I have something like 20 pins and more than 4 cables, so I don't know how I can do the deep cable with a usb-c.

Please, I need help :crying:
[Moto Z2 Force  Questions & Answers] fast69mopar:
I think there is another way to go about this than putting your devices into Qualcomm 9008. That is what you are wanting the EDL Deep Cable for, right? Instead of that, why not try this thread here, https://xdaforums.com/z2-force/how-to/how-to-return-to-stock-sprint-t3694783, and see if Uzephi's method doesnt get you back to stock. If for some reason his flashall doesnt work, then I would suggest using a blankflash for your version of Android to wipe the slate clean and then use the return to stock method for your device.
[Moto Z2 Force  Questions & Answers] Loperaco:
Okay ! I'm going to try those two options and I'll write you what happens.

Thanks !
[Moto Z2 Force  Questions & Answers] Loperaco:
Well, I'm here again.

I tried the two methods that you kindly indicated to me:

1. https://xdaforums.com/z2-...print-t3694783 The Flashall.bat file really does not do anything different than being an automated flash of what you can usually do manually, I mean, it does the flash using the fastboot file by file, so because it's the same process (but automated) I got the same result, when the Flashall.bat file tries to send / flash the files the response status is Failed, because the flashing status in the bootloader is locked.

2. Blankflash metod. This method seems to work when the cell phone is bricked and does not enter the bootloader, and that is not my case because I can access the cell phone, for example if I connect the cell phone to the computer in:

a) the boot manager mode, the "Device Manager" recognizes it as "Android Device / Motorola ADB Interface"

b) started the ROM (and activated the "USB Debugging"), the "Device Manager" also recognizes it as "Android Device / Motorola ADB Interface"

c) QCOM mode (selected from the bootloader) the "Device Manager" recognizes it as "Qualcomm HS-USB Diagnostics 9092".

Anyway, if I run the blank-flash file in:

a) bootloader mode, the CMD shows "waiting device" and does nothing

b) started the ROM (and activated the "USB Debugging"), the CMD shows "waiting device" and does nothing

c) QCOM mode (selected from the bootloader), the CMD shows "waiting for the device" and does nothing (this same result with or without the activation of "USB Debugging")

So I'm still the same, I think my only option is Deep Cable, what do you think?
[Moto Z2 Force  Questions & Answers] 41rw4lk:
To use blankflash you need to be in 9008 mode, since you have adb working try issuing the command 'adb reboot-edl' or 'adb reboot edl' can't recall at the moment. You'll know when you're in edl/9008 mode because the screen will be blank and the device will recognize as 9008. If you can't reboot to edl through adb, go to fastboot and try 'fastboot oem blankflash' again you'll know when you're ready for blankflash because the device will recognize as 9008. If the commands don't take, boot into QCOM mode and try 'fastboot oem blankflash'

*To unlock the bootloader you need to select oem unlock in settings. If it's greyed out you need to connect to internet and sign into google. Try bluetooth connection or a cable since wifi and mobile is borked at the moment.
[Moto Z2 Force  Questions & Answers] 41rw4lk:
You need drivers so that your pc and the phone can communicate, here is a link and it also has a verified blankflash.zip that has worked many times for others in the past. The process is a bit hit and miss, meaning it can be finicky on some pcs. Make sure you use a usb 2.0 port off the mobo, and not a 3.0+ or a hub port, they're not all so universal and can cause problems, so stick to 2.0 mobo ports.

https://xdaforums.com/showpost.php?p=77623934&postcount=5