yashsingh1/xdaforums huggingface dataset:
[Sony Xperia XA1 Questions & Answers] Juan_X:
Hello forum. I'm trying to bring back a Xperia XA1 Plus from a softbrick. The phone didn't had Untrusted Sources, Debug Mode or Unlock OEM options enabled before the brick. Also, I already managed to unlock the bootloader via Flashtool. I also got all the drivers installed.

The thing is, when I try to flash the stock ROM (official, downloaded from XperiFirm) I get the following log on Flashtool.

----------------------------------------------------------------------------------------

09/044/2021 11:44:08 - INFO - Selected Bundle for Sony Xperia XA1 Plus(G3423). FW release : 48.1.A.2.21. Customization : Customized AR

09/044/2021 11:44:08 - INFO - Preparing files for flashing

09/045/2021 11:45:29 - INFO - Please connect your device into flashmode.

09/045/2021 11:45:41 - INFO - Using Gordon gate drivers version 3.2.0.0

09/045/2021 11:45:42 - INFO - Opening device for R/W

09/045/2021 11:45:42 - INFO - Device ready for R/W.

09/045/2021 11:45:42 - INFO - Reading device information

09/045/2021 11:45:42 - INFO - Phone ready for flashmode operations.

09/045/2021 11:45:42 - INFO - Opening TA partition 2

09/045/2021 11:45:42 - INFO - Current device : G3423 - CQ3000RPBC - 1313-5936_R1B - 1309-1869_48.1.A.2.122 - GENERIC_48.1.A.2.122

09/045/2021 11:45:42 - INFO - Closing TA partition

09/045/2021 11:45:42 - INFO - Start Flashing

09/045/2021 11:45:42 - INFO - No loader in the bundle. Searching for one

09/045/2021 11:45:42 - INFO - No matching loader found

09/045/2021 11:45:42 - WARN - No loader found or set manually. Skipping loader

09/045/2021 11:45:42 - INFO - Loader : S1_Root_4a6c - Version : S1_Boot_MT6757_O0.MP103_207 / Boot version : S1_Boot_MT6757_O0.MP103_207 / Bootloader status : ROOTABLE

09/045/2021 11:45:42 - INFO - Max packet size set to 8M

09/045/2021 11:45:42 - INFO - USB buffer size set to 512K

09/045/2021 11:45:43 - INFO - Parsing boot delivery

09/045/2021 11:45:44 - INFO - Found a template session. Using it : C:\Users\Juan Cruz\.flashTool\firmwares\prepared\48.1.fsc

09/045/2021 11:45:44 - INFO - Set loader configuration : [00 01 00 00 00 0C]

09/045/2021 11:45:44 - INFO - Opening TA partition 2

09/045/2021 11:45:44 - INFO - Writing TA unit 00002774. Value : 01

09/045/2021 11:45:44 - INFO - Closing TA partition

09/045/2021 11:45:44 - INFO - Flashing finished.

09/045/2021 11:45:44 - INFO - Please unplug and start your phone

09/045/2021 11:45:44 - INFO - For flashtool, Unknown Sources and Debugging must be checked in phone settings

09/045/2021 11:45:50 - INFO - Device disconnected

-------------------------------------------------------------------------------------------------------------------------

I've searched all the internet for all the posibilities, but nothing works. If anybody knows what's the deal here, I'll appreciate the help. Best regards.
[Touch Diamond, MDA Compact IV General] hallur84:
Hi,

I've had my Diamond for a bit more than 2 months now.

Recently I had an odd problem with it.

The touch screen seems to be busted.

The display works fine. However, it doesn't respond to any of my touch commands and it seems like someone is touching the screen randomly, as in, random clicks on the screen.

The hardware buttons work fine, it's just the touch interface of the screen.

First I assumed it was a ROM related problem, as this happened just after I installed Shine On. So I went back to the original ROM again, but the problem persisted. Then I tried another ROM, but same problem!

Therefore I suspect the hardware.

Am I right to assume that the screen is built up of several layers? Such as the TFT screen it self, the touch part, protective glass part, etc.?

This was a week ago and I've been using my old HTC since (waiting for a reply from HTC customer service which haven’t replied yet! :mad: ). However, three days ago I tried the Diamond again, and it seems to work flawless..!

So, I'm wondering if anyone else has seen this intermediate problem? Or if anyone has suggestions what could cause this problem?

Thanks for reading :)
[Touch Diamond, MDA Compact IV General] T!nk:
Same s*it!

Hey mate.

I am experiencing the same problem as you do. The touchscreen does not respond or not accurate enough oder in a completelly different ponint than is poninted at. Readjusting screen helps for a while, soft-reset helps for a while. Sometimes it goes away without doing anything special. Did HTC finally answer your E-Mail?

I'd like to have this fixed as soon as possible.

Edit: I noticed that this problem disappears at once if TF3D is deactivated. Let'S see about that....
[Touch Diamond, MDA Compact IV General] b0t:
Hi,

even though there are probably several other threads concerning this issue, this seems to be the most recent one.

Do you use a (genuine?) screen protector?

I do.

I suppose this problem is caused by the tremendous heat* when the device is used and a screen protector that had been applied wrongly.

I might have applied the screen protector wrongly so there are a few very small (almost invisible?) bubbles (i.e. hot air expands(?) - I don't know the technical term),

since I had to remove the screen protector once because of dust..(does the glue lose its stickiness?)

I don't know if it's because of the bubbles, but I'm quite sure it's because of the screen protector.

Has anyone noticed this behavior without using a screen protector?

(I'm going to buy new screen protectors if neccessary, but I don't want to pay ~25€ if it's not)

*= I've adjusted my screen when my device was "cold".

Edit: I've probably found the reason for this issue: there's a deformation (caused by HTC) on the bottom of the screen(at the end of the screen protector) - there's a hole without glue (but air) - everything works fine while closing the hole by pressing the screen protector on the surface of the device.

I'm going to upload a picture later.

Edit2: The picture is now online. The fact that there's a hole isn't new of course, but no one seems to have linked these two issues so far.

(Correct me if I'm wrong)

The hole wasn't that big first but it grew because of all the testing:D

I've cut the lower part of the screen protector off now until I have a new one, although it doesn't look that great anymore..

Edit3: Ok, it's the hole and not the screen protector - I guess I have to get a new Diamond from my provider since it's a manufacturing defect..
[Android Q&A, Help & Troubleshooting] nthp999:
I want to use Xposed Module to display an AlertDialog and warn user whenever the target application is executed on the background, so how can I do that. I was using a thread to display dialog; however, it didn't work.
[Moto G 5G ROMs, Kernels, Recoveries, & Other Devel] h3xmind:
DISCLAIMER: I'm not responsible if you brick or damage your phone in any way by using this recovery. It is always advisable to fully backup your phone before playing around with recoveries, custom roms and similar stuff.

What has been tested and works:

- Touchscreen

- Installing flashable zips

- Flashing images

- Flashing the recovery itself

- Creating backups (to internal storage, sdcard or OTG)

- Restoring from backups

- Terminal

- adb

- Rebooting to system, recovery, bootloader, ...

That doesn't mean that other things don't work. It just means they weren't tested yet. As I proceed with testing I will update the above list.

Usage (without flashing)

# boot to bootloader
adb reboot bootloader

# boot to recovery
fastboot boot twrp-3.5.2_10-kiev.img

If you want to flash you have 2 options

# boot to bootloader
adb reboot bootloader

# ********* OPTION 1 *********
# Flash to active slot (replace <slot> with either a or b, depending on the current active slot).
# Of course, you can flash to both by first specifying a and then b.
fastboot flash recovery_<slot> twrp-3.5.2_10-kiev.img

# ********* OPTION 2 *********
# boot to recovery
fastboot boot twrp-3.5.2_10-kiev.img

# Once in the recovery, copy the twrp image file to your internal storage
adb push twrp-3.5.2_10-kiev.img /sdcard/Download

# Then go to Install, then Install image, select the twrp image you pushed before.
# Then select the Recovery partition and swipe to confirm.
# Before swiping you will have the option to decide if you want to flash to both slots.

Download: google drive

Sources will be posted in due time and this post will be updated accordingly.

Built for: Motorola Moto G 5G (Motorla One 5G Ace)

My model: XT2113-3 (kiev)

Credits 👏🙏

To the guys over here for the device tree, especially to SyberHexen for providing me with useful information.
[Moto G 5G ROMs, Kernels, Recoveries, & Other Devel] h3xmind:
reserved
[Moto G 5G ROMs, Kernels, Recoveries, & Other Devel] PEACH-PIT:
Great!
[Moto G 5G ROMs, Kernels, Recoveries, & Other Devel] codeOps64:
Tested on my Moto G 5G XT2113-3. Seems to work properly. Good job. Awaiting to flash it.
[Moto G 5G ROMs, Kernels, Recoveries, & Other Devel] clintongsan:
It shouldn't brick my device as long as I use it as a boot command and not flash, right? Is this associated with Hexen's version of unofficial twrp-3.5.2_10.0_BT-1.3??
[Moto G 5G ROMs, Kernels, Recoveries, & Other Devel] codeOps64:
It won't brick. I used it. (only once) :)
[Moto G 5G ROMs, Kernels, Recoveries, & Other Devel] h3xmind:
By doing fastboot boot recovery.img you will not brick anything. However, I cannot guarantee for any of the functions in the recovery. They should be thoroughly tested before. I used it to fully backup my phone, I used the terminal and adb. Rebooting works, but I haven’t had a chance to test other functions.

Until now I didn’t even know that there’s already another twrp. I thought, judging by the posts in this forum, that there was a recovery in which the touchscreen didn’t work until you decrypted the filesystem with a password/PIN/…

I compiled the kernel by myself. I turned off some CONFIG_XYZ flags in order to be able to load the drivers that I manually extracted from my device. I packed the kernel in the recovery in which I modified some files in order to load the driver at the right point. I’ll post the full tutorial when I have time.
[Moto G 5G ROMs, Kernels, Recoveries, & Other Devel] PEACH-PIT:
Hexen's released twrp is just that.

Since the touchscreen-related problems have not been completely fixed, only the source has been released.

The one released here is the first fully functional twrp.
[Moto G 5G ROMs, Kernels, Recoveries, & Other Devel] Tomspector:
Compile the zip for install, I will be the Gina pig for flashing lol.

I need to redo my phone anyway so it's no big deal.
[Moto G 5G ROMs, Kernels, Recoveries, & Other Devel] h3xmind:
Great to have guinea pigs LOL. Thanks for your help, man.

Here it is: google drive

Let me know how it goes. I would have tested it by myself, but if something goes wrong I don't have time today and tomorrow for fixing stuff and I really need my phone.

P.S.: I repeat something that I already stated before. I'm a developer with many years of experience in different fields, but this is my first project of this kind, so many of the things (including building this installer) are new to me.
[Moto G 5G ROMs, Kernels, Recoveries, & Other Devel] Tomspector:
I will do it now,

I would help

I will do it now
[Moto G 5G ROMs, Kernels, Recoveries, & Other Devel] Tomspector:
It installs find but does not boot to it.

Installed this way

Ran fastboot boot twrp. Img

Then installed it while booted to twrp. Img

Zip says it installs fine but hangs during boot.

Mine is the metro version ace
[Moto G 5G ROMs, Kernels, Recoveries, & Other Devel] h3xmind:
Ok, thanks. I think the best thing is that I test it myself and fix it. I’ll post it when it works. Thank you for your willingness. I’ll remove the file from google drive.
[Moto G 5G ROMs, Kernels, Recoveries, & Other Devel] Tomspector:
I did not clear my data, I did not feel like redoing my phone today,

It may be that
[Moto G 5G ROMs, Kernels, Recoveries, & Other Devel] Tomspector:
where can I get the latest rom for my phone with the last I tried lilionet roms but it's not there yet
[Moto G 5G ROMs, Kernels, Recoveries, & Other Devel] h3xmind:
Ok, thanks for your help. I won't be testing anything tomorrow. I have a day off with my family 🌞
[Moto G 5G ROMs, Kernels, Recoveries, & Other Devel] h3xmind:
Should be here: https://mirrors.lolinet.com/firmware/moto/kiev/official/
[Moto G 5G ROMs, Kernels, Recoveries, & Other Devel] h3xmind:
Anyway, I flashed it by doing the following:

# boot to bootloader
adb reboot bootloader

# boot to twrp
fastboot boot twrp-3.5.2_10-kiev.img

# push the recovery image to the Download folder
adb push twrp-3.5.2_10-kiev.img /sdcard/Download

Once inside the recovery I went to Install, then Install image, once I selected the twrp-3.5.2_10-kiev.img file that I previously pushed, twrp asked me on which partition I would like to flash it. I selected the Recovery partition. (Although I ask myself why does the phone have a separate recovery partition if it is an A/B device. I still have to figure this out. :unsure: Normally in these devices one would have to pack the recovery into the boot imate and than flash the whole thing to the boot partition.)

Then I rebooted to recovery and it took me directly to twrp. (y) The problem, however, is that the touch screen didn't work anymore. So, I guess I got myself some extra work :cool: But it'll be fun. I can't wait to put my hands on it. :)

Did you manage to find the rom for your phone?
[Moto G 5G ROMs, Kernels, Recoveries, & Other Devel] h3xmind:
I tried Hexen's recovery. It's easily fixable to make the touch work. It took me two minutes. I'll let the guys working on it know how to do it. But first I have to figure out why does the touch screen stop working once you flash the recovery.
[Moto G 5G ROMs, Kernels, Recoveries, & Other Devel] Tomspector:
I

There was an update the other day, I want to use the latest rom, I have the last rom from the link you sent already, I just wanted not to do it again lol

Yea Yea I am lazy, I work with code all week and don't wanna on the weekends

Thanks for the link though.
[Moto G 5G ROMs, Kernels, Recoveries, & Other Devel] Tomspector:
There has to be some sort of trigger when the asking for the pin or password is engaged.

That's not allowing the drivers to load.
[Moto G 5G ROMs, Kernels, Recoveries, & Other Devel] fosgate3:
I was able to flash TWRP fine but for some reason, I cannot install SU or Magisk. I tried both and I get "error creating fstab" each time. I feel pretty certain I'm doing something wrong. I be pretty new to this.
[Moto G 5G ROMs, Kernels, Recoveries, & Other Devel] Tomspector:
It's not you the file has errors and is not done yet.

You got further than I did
[Moto G 5G ROMs, Kernels, Recoveries, & Other Devel] fosgate3:
Well, I actually got it rooted but I ended up using Magisk. I used the Magisk zip file found here and moved it into the phone's internal storage. Then I booted into TWRP and installed the zip just like it was. Everything installed fine and according to root checker, I am rooted. :) This was on a Motorola One 5G Ace (aka Moto G 5G), XT2113-2.
[Moto G 5G ROMs, Kernels, Recoveries, & Other Devel] Tomspector:
Nice, so how did you flash twrp?

I have the same phone as you.

Xt2113-2
[Moto G 5G ROMs, Kernels, Recoveries, & Other Devel] fosgate3:
Pre-First: I turned on developer options and usb debugging, then unlocked my bootloader.

First: I downloaded and installed the USB drivers from Motorola, then downloaded ADB drivers, SDK Tools, and the TWRP img file associated with this thread.

Second: I extracted the file packages for each ADB drivers and the SDK Tools file to my Downloads folder.

Third: I created an easily accessible folder on my C:\ drive. I called it AndroidADB and put all the ADB files and the SDK Tools files in it. I also put the TWRP file downloaded from here into the same folder and renamed it to TWRP.

Fourth: I downloaded Magisk from the link I provided in the previous post (this link).

Fifth: I moved the downloaded (and unzipped) Magisk file to the phone's internal storage. Just double-clicked the phone in my computer and pasted it there).

Sixth: I connected my phone and booted to fastboot (Power off, hold power and volume down button until the fastboot screen appears)

Seventh: Once that was done, I opened a command prompt with administrator privileges (I run Win10 Pro 64bit), then entered the following commands:

cd C:\AndroidADB

fastboot devices

fastboot flash recovery twrp.img

Eighth: After that, there should be some verification in the ADB window on the computer that the image was flashed. When I saw that, I used the volume up button to boot into recovery mode. TWRP loaded at that point.

Ninth: Select Install and the screen showed all the files I had on the phone. I selected the Magisk zip file I put on there. It installed it completely. I can't remember if it rebooted on its own or if I had to instruct it to but either way, it rebooted.

Tenth (and last step): I went to the Google Play Store, downloaded, and installed Root Checker. I ran it and it indicated I was rooted.

I hope this works for you.
[Moto G 5G ROMs, Kernels, Recoveries, & Other Devel] fosgate3:
I may have spoken too soon. For some reason, my texting feature isn't working correctly. I have the ability to send but apparently not the ability to receive. I sent a text earlier and never heard from the person. 30 mins later, I put the SIM in another android phone I use as a spare and found that the person received the text and replied. I just never saw a reply.
[Moto G 5G ROMs, Kernels, Recoveries, & Other Devel] h3xmind:
Great to hear it worked. Do you have password or PIN protection on your phone? If yes, when you booted to recovery did the touchscreen work? Because yesterday I tried to flash and the touchscreen didn't work. So, if I flash it doesn't work, if I just boot into it, it works. I already have an idea what could be the problem and if I'm right it's easily fixable. I'm just curious to know if you had the same issues.

EDIT: the touchscreen issue was solved. It never existed. I flashed the wrong file :D
[Moto G 5G ROMs, Kernels, Recoveries, & Other Devel] h3xmind:
Thanks for your feedback. It might be that the unzip binary is not included in the release, although this would be strange since I tested flashing zips and it worked. I'll verify and fix if needed.

EDIT: I checked and the unzip binary is there as expected. In fact, you managed to install the other zip just fine. Therefore I'm not sure why the NO UNZIP warning.

EDIT 2: According to this installing Magisk through recovery is not recommended anymore. I'm not there yet since I first need to thoroughly test some other features of the recovery. But I'll get into installing Magisk asap and update.
[Moto G 5G ROMs, Kernels, Recoveries, & Other Devel] Skel40:
Can someone confirm if this has been tested on model XT2113-2 Kiev?
[Moto G 5G ROMs, Kernels, Recoveries, & Other Devel] Tomspector:
Read the post above yours.

Mine is xt2113-2 metro pcs

It installs fine, but does not boot to it.

If you run it from fastboot

"Fastboot boot twrp.img it works fine."

I tested what I could while running it everything works for me.

The issue is problems when it's installed.

While in fastboot boot twrp. Img

I installed twrp.zip

I renamed the file to twrp.zip if your wondering.

It installs fine, will not boot to twrp, but boots to the system fine.

Android version

QZKS30.Q4-40-55-4
[Moto G 5G ROMs, Kernels, Recoveries, & Other Devel] Tomspector:
For those asking the latest magisk installs fine you just have to rename magisk.apk to magisk.zip to install it
[Moto G 5G ROMs, Kernels, Recoveries, & Other Devel] Tomspector:
Thanks.

According to the twrp website your supposed to install twrp.zip while running from within twrp.img

Fastboot boot twrp.img

Then install twrp.zip.

Here is the link

Motorola One Vision

Disclaimer:Team Win strives to provide a quality product. However, it is your decision to install our software on your device. Team Win takes no ...

twrp.me

The phone is different but instructions are the same.
[Moto G 5G ROMs, Kernels, Recoveries, & Other Devel] fosgate3:
The touchscreen worked fine for me and I don't have a PIN/password. The problem I had was with texting: I can send but I don't receive.
[Moto G 5G ROMs, Kernels, Recoveries, & Other Devel] fosgate3:
Pardon my ignorance here but if I wanted to start the root process over from scratch, what should I do? I want to try rooting it again but with SU instead of Magisk.
[Moto G 5G ROMs, Kernels, Recoveries, & Other Devel] Tomspector:
It's not magisk, I had the same issue even before root, it was Google messages, I switched to textra and worked fine ever since
[Moto G 5G ROMs, Kernels, Recoveries, & Other Devel] h3xmind:
I remember having the same issues with Huawei. I had to change the app for messaging.
[Moto G 5G ROMs, Kernels, Recoveries, & Other Devel] fosgate3:
Oh really? If that's all there is to it, then I'm good. I'm going to give that a shot and see.
[Moto G 5G ROMs, Kernels, Recoveries, & Other Devel] Tomspector:
Textra you can get from the playstore,

After install goto settings in textra, then customize notifications then define notifications, tapping opens, change to full app.
[Moto G 5G ROMs, Kernels, Recoveries, & Other Devel] codeOps64:
As fosgate3 indicated, it sure was tested on XT2113-2. I myself tested it on XT2113-3. There are some minor things that are needed to be tweaked though. h3xmind, one of the brillant minds here; is working on it and will tell us as soon as its fully functional. :)

If you want to try/test it yourself, then use fastboot boot twrp.img.

EDIT : If you want to install it then no worries, its functional.
[Moto G 5G ROMs, Kernels, Recoveries, & Other Devel] Tomspector:
Yep just change the app
[Moto G 5G ROMs, Kernels, Recoveries, & Other Devel] Tomspector:
Here is a screen shot of what modules are installed on my phone.

I have had a few ask
[Moto G 5G ROMs, Kernels, Recoveries, & Other Devel] fosgate3:
Do you have a suggestion regarding which app? I just changed it to one I got from the Play Store but it still isn't receiving texts. In fact, I tried four different texting apps and none of them work with regard to receiving texts.
[Moto G 5G ROMs, Kernels, Recoveries, & Other Devel] Tomspector:
Whats the rom version you have?

They fixed an issue with sms and this rom is the one that sms issues was fixed.

Also if you reflash by fastboot the rom has 10 super.img_sparsechunk. files not 9.

Use this in fastboot to flash

Just copy the commands

fastboot getvar max-sparse-size

fastboot oem fb_mode_set

fastboot flash partition gpt.bin

fastboot flash bootloader bootloader.img

fastboot flash vbmeta vbmeta.img

fastboot flash radio radio.img

fastboot flash bluetooth BTFM.bin

fastboot flash dsp dspso.bin

fastboot flash logo logo.bin

fastboot flash boot boot.img

fastboot flash dtbo dtbo.img

fastboot flash recovery recovery.img

fastboot flash super super.img_sparsechunk.0

fastboot flash super super.img_sparsechunk.1

fastboot flash super super.img_sparsechunk.2

fastboot flash super super.img_sparsechunk.3

fastboot flash super super.img_sparsechunk.4

fastboot flash super super.img_sparsechunk.5

fastboot flash super super.img_sparsechunk.6

fastboot flash super super.img_sparsechunk.7

fastboot flash super super.img_sparsechunk.8

fastboot flash super super.img_sparsechunk.9

fastboot erase carrier

fastboot erase userdata

fastboot erase metadata

fastboot erase ddr

fastboot oem fb_mode_clear

fastboot reboot

Use this rom or higher

Android 10 QZKS30.Q4-40-55-4

If you flash with only 9 sparsehunk it will not work correctly. I did the same as you.

https://mirrors.lolinet.com/firmware/moto/kiev/official/ download
[Moto G 5G ROMs, Kernels, Recoveries, & Other Devel] h3xmind:
If none of them worked the problem might be elsewhere. Try resetting wifi, mobile and Bluetooth settings. You should find that somewhere under Settings -> System ...