yashsingh1/xdaforums huggingface dataset:
[Motorola Edge ROMs, Kernels, Recoveries, & Other D] Heat84:
The phone is bricked. :confused: :eek: I don't know what happened. It rebooted into the OS just fine after I did the flash. But I couldn't tell if the flash took because the window closed when it was finished and it wouldn't flash again after I put the pause command at the end of the batch file(so the window wouldn't close). I did that when I flashed the first zip you gave me but I forgot to do it this time. I wanted to reboot the phone into the bootloader screen to see what it said and to do getvar all,, but it never got there. ADB isn't seeing the phone.

I'm not worried about the data since did a thorough backup before flashing the first zip file. I hope this isn't the type of brick that's unrecoverable.:eek:
[Motorola Edge ROMs, Kernels, Recoveries, & Other D] Heat84:
I downloaded this and the instructions told me to install a Quallcomm or MTK driver. I installed this. My phone now appears in Device Manager as an unknown device with a yellow exclamation point(which disappears when I unplug the phone) with the error message: Windows has stopped this device because it has reported problems. (Code 43). And that's as far as I've gotten.

I read something about shorting 2 pins together to put it in EDL mode: https://android.stackexchange.com/questions/221973/enter-edl-mode-in-motorola-devices
[Motorola Edge ROMs, Kernels, Recoveries, & Other D] SyberHexen:
This is certainly odd, by chance did you still have lineage 20 installed or did u return to a older version?

When I return from work I'll put together a blankflash / edl reply.
[Motorola Edge ROMs, Kernels, Recoveries, & Other D] Heat84:
I still have 20 installed.
[Motorola Edge ROMs, Kernels, Recoveries, & Other D] Heat84:
Did you forget about me?
[Motorola Edge ROMs, Kernels, Recoveries, & Other D] Heat84:
So I was able to get the Quallcomm driver working. I found button combinations instructions for rebooting the phone and it seems to have worked. But I only got a tiny bit farther. What you see in the picture is 3 attempts. I don't understand why the first one is different than the other 2. Nothing was changed. It looks like the first attempt failed because I didn't have a package. The person who made the tool does a TERRIBLE job explaining how to use it.

Is the battery able to charge with the phone in this state? I'm worried that the battery will die before I can fix the phone.
[Motorola Edge ROMs, Kernels, Recoveries, & Other D] Heat84:
It would be just my luck that you were killed in a car accident on your way home from work. If that actually happened and you became a ghost, you could still help me by possessing someone else's body and doing what you were gonna do and posting it here using their body. I hope I'm joking.
[Motorola Edge ROMs, Kernels, Recoveries, & Other D] SyberHexen:
Long day at work, ended up sleeping for 14 hours lol..

blankflash below (I ran on my device to confirm validity)

blankflash_repack_RACER_RETAIL_RPDS31.Q4U-39-26-14-13.zip

drive.google.com

As you've mentioned button sequence using the unbrick tool its pretty much the same process here

1) Hold the power + vol- until you see / hear device manager reconnect the Qualcomm HS-USB QDLoader 9008 bridge

2) Shortly after step 1 run blank-flash.bat as admin (i think you hold shift and right click on the bat file in windows to run as administrator)

To note the bridge can time out if you're not fast enough or it can lock up if you're too fast (I find about 3-5 seconds after bridge connects is a good 'timing') if this happens repeat step 1

Hopefully this process goes well to rescue and at this time i recommend full re-stock via RSA afterwards RSA_Download (be sure to boot, test calls / 5G functionality)

afterwards proceed to lineage wiki and start the new installation process. (don't skip copy-partitions step as thats very important)
[Motorola Edge ROMs, Kernels, Recoveries, & Other D] Heat84:
The blankflash worked. Yay and whew! Since I was able to boot into LineageOS and then reboot to the bootloader screen like I was trying to do after re-flashing the radio firmware yesterday, is it necessary to do the rescuing and reinstalling?

I noticed in the getvar log I just pulled that it says:

slot-successful:_a: yes

slot-successful:_b: no

In the last getvar log I pulled and posted here, both slots said yes. Is that a problem you were anticipating? Maybe it just says that because it hasn't booted to the B slot since the blankflash?

Also, did the reflaashing of the radio firmare I did yesterday take?
[Motorola Edge ROMs, Kernels, Recoveries, & Other D] SyberHexen:
I'm still a bit concerned about the reporting build fingerprint/baseband

here it reports

(bootloader) ro.carrier: retus
(bootloader) ro.build.fingerprint[0]: motorola/racer_retail/racer:11/RPD
(bootloader) ro.build.fingerprint[1]: S31.Q4U-39-26-14-10/15465c:user/re
(bootloader) ro.build.fingerprint[2]: lease-keys
(bootloader) ro.build.version.qcom: LA.UM.9.12.r1-08600-SMxx50.0
(bootloader) version-baseband[0]: M7250_HI20_06.18.02.74.03R RACER_NA5G_
(bootloader) version-baseband[1]: CUST
(bootloader) kernel.version[0]: Linux version 4.19.125-perf+ (nobody@and
(bootloader) kernel.version[1]: roid-build) (clang version 10.0.7 for An
(bootloader) kernel.version[2]: droid NDK, GNU ld (binutils-2.27-bd24d23
(bootloader) kernel.version[3]: f) 2.27.0.20170315) #1 SMP PREEMPT Sun M
(bootloader) kernel.version[4]: ar 27 09:45:49 EDT 2022

i still stand by using RSA and using copy-partitions.zip to be sure everything is actually fine considering you got thrown to EDL mode.

You can try using lineage-20 as.. but i can't tell if it took the radio update.

as far as bootable slots go, always the inactive reports as unbootable
[Motorola Edge ROMs, Kernels, Recoveries, & Other D] Heat84:
Is there any way to tell? Maybe I should re-flash it? But I was able to make a few calls(and counting) without having to reboot the phone. Is that something updating the radio firmware would fix?

I'm confused. I was talking about successful. In GetVar 2 they were both yes but in GetVar 3 slot b was no. In both logs unbootable was no for both slots.

Another problem I've been having since I upgraded to 20 is the OS update check says it failed even though I don't think it did. The latest update it has available is June 9th.
[Motorola Edge ROMs, Kernels, Recoveries, & Other D] SyberHexen:
Well like I mentioned you can try testing out as is if all seems well then I don't think u have to worry.

As far as updater it might be broken? You can try clearing the data of updater apk or sideload the update manually (don't forget gapps if u do)
[Motorola Edge ROMs, Kernels, Recoveries, & Other D] Heat84:
When I rebooted after installing today's OS update, the phone was thrown into EDL mode. I already Blankflashed it. By the Way , I(accidentally) found a better way to do the Blankflash: You run the batch file first(and it says <Waiting for device>), THEN you do the buttons and plug the phone in. That way, you don''t have to worry about timing the buttons and the plugging in just right. Surely I'm not the first person to discover that method? I've never seen it in any tutorial or around here though.

A few other things:

1. 5G doesn't crash the phone anymore since the radio firmware update.:cool:

2. The OS update check says it failed eventhough it didn't. I guess I won't worry about it since the OS download and update work just fine.

3. This is unrelated. Do you know why visual voicemail doesn't work or how to get it fixed? It stopped working during 19.1. I don't know if one of the OS updates caused it. I have 2 phone apps, and it doesn't work in either app, so its not an app level problem.

Edit: I happened to go back to the OS updater and saw that today's update didn't take. I'll stick with June 2nd until I get everything fixed.

Edit 2: I tried updating the OS again and it hard bricked again. I wanted to see which slot it booted into in Getvar and it was A. I wanted to try to boot with slot B., but when I tried to change slots, I got this:

Setting current slot to 'b'...
(bootloader) WARNING: Bootloader images on target slot b are not valid!!
(bootloader) There is risk of bricking HW. Please flash valid bootloader
(bootloader) into slot b before activating it. OR you could force to
(bootloader) switch to slot b by running the same command again
(bootloader) within 30 s if you understand what you're doing
FAILED (remote failure)
finished. total time: 0.200s

So I guess its hard bricking because its trying to boot with slot B?

This is from Getvar:

slot-successful:_a: no
slot-successful:_b: no
slot-unbootable:_a: no
slot-unbootable:_b: yes
[Motorola Edge ROMs, Kernels, Recoveries, & Other D] Heat84:
Ok, I fixed the slot B hard brick just by sideloading copy-partitions.zip(with slot A active). And I didn't need to do a factory reset.

Getvar now says (while slot B is active):

slot-successful:_a: yes

slot-successful:_b: yes

slot-unbootable:_a: no

slot-unbootable:_b: no
[Motorola Edge ROMs, Kernels, Recoveries, & Other D] Heat84:
This place is a ghost town these days. I guess its now my personal LineageOS support thread.😛

Anyway...

So I'm having a few phone call related problems and don't know if they have the same cause. I'm thinking firmware, but I don't know. They didn't happen until 19.1 or 20, but I don't know if the OS is the problem. Since noone else is complaining about these problems in here, it probably isn't.:

1. When I call somebody, the sound cuts out while its ringing until the otherside answers.

2. When I use WIFI calling, the other person has problems hearing me, while I hear them just fine.

3. Visual voicemail isn't working anymore.

VOLTE or lack thereof could also be the issue, but I can't tell if it's being used. When I go into the hidden settings by pasting *#*#4636#*#* into a phone app, it shows The VOLTE switch is in the ON position BUT its grayed out. I interpret that to mean that VOLTE is enabled but its not disable-able(at least with the switch), but I don't know for sure.

Is the "Use WIFI calling" setting in Mobile Data settings actually the enable/disable VOLTE setting?
[Motorola Edge ROMs, Kernels, Recoveries, & Other D] JerseyChewi:
I had similar trouble with wifi calling, but I chalked it up to my office network link being saturated. Maybe that wasn't it. I just disabled it in the end.
[Motorola Edge ROMs, Kernels, Recoveries, & Other D] Heat84:
Could be.
[Motorola Edge ROMs, Kernels, Recoveries, & Other D] Heat84:
Another thing I've been seeing lately is "WifiNative Failure" in the notification bar, but WIFI seems to be working just fine. What is this about and where am I expected to send the bug report that's created everytime this occurs? Is this a LineageOS error or an Android error? I attached the bug report.
[Motorola Edge ROMs, Kernels, Recoveries, & Other D] Heat84:
I just lost root after installing the September 1st OS update. WTF?! This hasn't happened since 17.1.😕
[Motorola Edge ROMs, Kernels, Recoveries, & Other D] SyberHexen:
Hmm maybe an issue with magisk 26.3 if you recently updated from 26.1

Was it after in-system ota?

If you manually flash rom zip in recovery though you do need to reflash magisk zip after gapps
[Motorola Edge ROMs, Kernels, Recoveries, & Other D] Heat84:
I haven't upgraded to 26.3 yet.

Yes

I don't use gapps.
[Motorola Edge ROMs, Kernels, Recoveries, & Other D] Heat84:
It happened again when I updated Magisk to 26.3. And Android uses the default keyboard when I enter my password, but uses the keyboard I usually use after that.

Also, does TWRP not support Android 13? At least with this phone? When I try to boot into it, I see the TWRP logo for half a second then the screen goes black. I can boot into Fastboot .
[Motorola Edge ROMs, Kernels, Recoveries, & Other D] Heat84:
So we're gonna have to re-root everytime we update the OS from now on?☹️

Is it possible that root WAS sticking since the middle of 17.1 because something wasn't getting updated, but now that something is getting updated and causing root to be lost?
[Motorola Edge ROMs, Kernels, Recoveries, & Other D] SyberHexen:
Boot.img replaces each flash.

Magisk is supposed to have addon.d support to survive ota but seems more like magisk issue
[Motorola Edge ROMs, Kernels, Recoveries, & Other D] Heat84:
Oh yeah, I never thought of that. Maybe the next time I re-root, I'll use an earlier version of Magisk and see what happens.
[Motorola Edge ROMs, Kernels, Recoveries, & Other D] Heat84:
I just accidentally discovered a LineageOS easter egg, but I don't know what to do with it:

1: Go to Settings>About Phone.

2: Tap LineageOS Version 3 times FAST. If you don't do it fast the easter egg won't activate.

You'll see the LineageOS logo in the center of the screen with colors around it. Everytime you tap the screen or stretch the logo (like you're stretching a picture when your viewing it) the colors change, and if you stretch it to much, it resets to the original size. Other than that, I don't know what else to do with it. I guess LineageOS developers aren't into easter eggs like Android developers are. This one seems pretty pointless. And apparently I'm the first one to discover this. I can't google it up.
[Motorola Edge ROMs, Kernels, Recoveries, & Other D] mirhl:
https://forums.lenovo.com/t5/motoro...Android-Auto-won-t-connect/m-p/5227932?page=4

This thread is for newer devices, but the theory behind is probably the same.

I can report (albeit on the stock motorola rom) that the n-th cable that I got to cycle through eventually fixed the connection on a Golf Mk7.

Supposedly (and expectably? given there's no other way all these otherwise good cables could be at fault) this should be possible to fix in software. But go figure.
[Motorola Edge ROMs, Kernels, Recoveries, & Other D] gunzflash:
Hi guys, i wanna use the Lineage os 20.0 but i don't see bugs reports or reviews for my Motorola Edge racer xt 2063-3... Worth use on main device? Have bugs? Pls someone Tell me 🙏
[Motorola Edge ROMs, Kernels, Recoveries, & Other D] Mag_e:
Hey man. It's worth it. The moto app on the phone won't work anymore but all your gestures will work. It's a great improvement over the stock OS. Make sure you install "g apps" too. The official Lineage OS tells you when to do this during the ROM installation. You have to do it before rebooting into the ROM so don't mess that part up. I gave the phone to one of my friends after reflashing it to the Moto stock ROM because he isn't tech savvy at all so he wouldn't be able to properly update it or keep it secure. Overall you should make the swap. I don't recall any other bugs. Make sure you know the radio bands and type of bands your carrier is using. Make sure those bands get selected in the network settings to make sure your service won't get interrupted (LTE/CDMA/WCDMA ect.). I made that mistake.
[Motorola Edge ROMs, Kernels, Recoveries, & Other D] gunzflash:
Thanks Man, i never knew that.. i'll try in the mourning when i wake UP and pray to do without problems. 🙏
[Motorola Edge ROMs, Kernels, Recoveries, & Other D] Mag_e:
Yeah brother. Follow the instructions on the official Lineage OS website exactly as they are written. If you have questions you can come back here and ask. I'll do my best to help. May not be right away but I will respond if you're asking me.
[Motorola Edge ROMs, Kernels, Recoveries, & Other D] Heat84:
*#*#4636#*#*

Firstly, you only need g apps for Google stuff. I switched to LineageOS to de-Googlefy my phone, so I didn't install it.

Secondly, can you help me with the radio issues? I can receive most texts, but a few of them I have to switch from wifi to mobile data to get. Mobile data works fine. I can receive calls but I can't make them. When I try to make them, the mobile network turns off and reconnects in 1 or 2G mode. But weirdly, when I'm miles away from my house, I CAN make calls. I know the phone isn't the problem because I recently replaced it for another reason and the prevoius one had the same problem. Also, the SIM card is new and the network in the area where I live is in great shape. Also, visual voicemail isn't working. It hasn't worked since I think LineageOS 17.1.

What about VOLTE/WIFI Calling? I can't tell if its provisioned.

This is from my *#*#4636#*#* settings:

Does grayed out and on mean its on but you can't turn it off, or that it is off? The last setting is grayed and off but I can turn it on. Why is there no instructions for this anywhere on the internet?
[Motorola Edge ROMs, Kernels, Recoveries, & Other D] Mag_e:
What phone do you have and what's the name of the stock ROM? Who is your carrier and what bands/type of bands do they accept? Figuring that out will help us fix your calling issue. Grayed out means you can't do anything with those settings. Most likely meaning they're disabled

Looks like those grayed settings are active. You just can't edit them there in that menu. What phone do you have? What's the name of the stock ROM? What type of bands does your carrier support?
[Motorola Edge ROMs, Kernels, Recoveries, & Other D] gunzflash:
Hi Guy, soo my phone is a Motorola Edge 2020 xt2063-3 racer, here the info about my Carrier and Stock rom. If i miss some info u can Tell me and i'll back.

My Carrier suports 4g and 5g but here 5g rarely Works as they are still implementing It.. but i see the 5g Band during the day some times.
[Motorola Edge ROMs, Kernels, Recoveries, & Other D] Heat84:
I have a Motorola Edge running LineageOS 20. My carrier supports 4G and 5G. I'm pretty sure the OS is the problem.
[Motorola Edge ROMs, Kernels, Recoveries, & Other D] Quantumstate:
Is this the right forum for the Edge 2023? if not, where?
[Motorola Edge ROMs, Kernels, Recoveries, & Other D] Heat84:
The Motorola Edge has 10 different variants with 20 different names, so its hard to keep it straight. I have the original Motorola Edge(which is what this section is for) which was called Motorola Edge when it came out, but now its also known as Motorola 5G or Motorola 2020 or Motorola 20. I'd like to go to Motorola HQ and kick some people in the nuts(or the female equivalent thereof)😡.

I just found out the phone has only been out a month-and-a-half. I guess that's why there's no section for it here yet. You could try Tom's Hardware. They reviewed it in May. Or you could try other places that reviewed it. Since it just came out, my first paragraph doesn't apply(yet). I was gonna say that it might be here under a different name. You should tell the Moderators to make a section for it.
[Motorola Edge ROMs, Kernels, Recoveries, & Other D] Quantumstate:
Thx.

Bah, I tried contacting mods here, but it mandates logging in to G**gle, and I do not use any G**gle products except Android proper. Would someone please ask them to make a forum?

What is the matter with the mods, mandating G**gle?

Well after reading the Tom's review I've gone ahead and bought a (regular) 2023 direct from Motorola. (All of them on eBat cost alot more)
[Motorola Edge ROMs, Kernels, Recoveries, & Other D] Heat84:
Thats actually above their pay grade.
[Motorola Edge ROMs, Kernels, Recoveries, & Other D] hondasoma:
SHello. I would like to buy a Motorola Edge 40 5g MTK process phone. Can this type be opened? Is there rum cooked on it? Thanks.
[Motorola Edge ROMs, Kernels, Recoveries, & Other D] mathew2214:
greetings from the Motorola One 5g ace (Kiev) community!

I am trying to bring LineageOS 17.1 to Kiev, which also uses sm7250. as such, i am inheriting quite a lot from racer's device tree to create one for Kiev.

I seem to be stuck in my efforts here, i cannot get NR to work at all on Kiev. looking at Racer's dev tree, its unclear to me what is done there to enable 5G support. Im hoping somebody familiar with Racer can point that out to me, so that i can get 5G working on Kiev.

trying to find/make an AOSP-10 device tree. help needed. cant get NR to work.

I am working on a project for Kiev. This project cannot continue unless I can build and boot lineage OS 17.1 for Kiev. Does anybody have a working device tree for this they could link me? Not including proprietary blobs of course. I have other...

xdaforums.com
[Motorola Edge ROMs, Kernels, Recoveries, & Other D] Heat84:
This place is been a ghost town over the last year or so. I don't know if its because nobody has any problems to complain about with 19.1 or 20 or because they're not using LineageOS anymore, or maybe they got a new phone that's a different make and/or model so they obviously don't need to come here anymore. Most of the posts in here over the last year are mine. I'm not a programmer and I don't think most of the other posters in here are either. I'm pretty sure the people who actually develop LineageOS don't ever post in here. They possibly lurk in here to gather Intel for their development. If they don't at least lurk in here, this thread is largely useless. Your best bet is to contact them if it's possible.

There's also a user here named SyberHexen. He made the Last TWRP for this phone, so he might be able to help you. He's been very helpful to me.
[Motorola Edge ROMs, Kernels, Recoveries, & Other D] JerseyChewi:
No posts from me because it's still working great. Honestly, the most solid ROM I've ever used.
[Motorola Edge ROMs, Kernels, Recoveries, & Other D] Heat84:
Does that include Visual Voicemail? It hasn't worked for me since early 19.1 or 17.1(I skipped 18.1). I narrowed down to LineageOS as one of the suspects, but I don't wanna flash the stock ROM just to see if that fixes Visual Voicemail. It's not important enough.
[Motorola Edge ROMs, Kernels, Recoveries, & Other D] JerseyChewi:
I didn't even know that was a thing. 😅 But no, the tab doesn't appear for me in the AOSP dialer.
[Motorola Edge ROMs, Kernels, Recoveries, & Other D] Heat84:
Neither dialer I use(stock or ACR Phone) has a Visual Voicemail tab either. When you have a message, there's a play button in the notification. It tries to show you the visual version first. Visual Voicemail just means a textual version that you can read instead of listen to. Maybe you can do both at the same time. It's been so long since Visual Voicemail has worked for me, I can't remember.🙁

Do you hear the ringing sound every time you call somebody? Until about 3 nightly updates ago, I almost never heard it since early 19.1. Now I hear it most of the time. Sometimes the call wasn't even going through. This is another problem I was having.
[Motorola Edge ROMs, Kernels, Recoveries, & Other D] JerseyChewi:
I don't make that many calls, but I don't think I've seen that issue.
[Motorola Edge ROMs, Kernels, Recoveries, & Other D] Heat84:
Neither do I.
[Motorola Edge ROMs, Kernels, Recoveries, & Other D] gunzflash:
@Heat84 Bro, did you have a problem with echo during a call? My contacts informed me that when I make or receive a call it echoes.
[Motorola Edge ROMs, Kernels, Recoveries, & Other D] Heat84:
No, I haven't had that problem.
[Motorola Edge ROMs, Kernels, Recoveries, & Other D] ttei:
I have Motorola Edge 2020 XT2063-2. I installed the latest LineageOS 20. I installed FM Radio com.caf.radio. FM Radio app scans channels, displays RDS, but there is no audio. FM Radio was working on stock Android. Do I need to change some system settings?

Thanks.
[Motorola Edge ROMs, Kernels, Recoveries, & Other D] Heat84:
I have the same problem. But there's a work around. If you record the station, you can play the recording and hear the station. The problem is, depending the app you try to play the recording with, either it won't let you while it's recording, or in the case of VLC, it will stop the recording process and commandere the file to play it. What we need is a player that will play a live recorded file without stopping the recording process. I've done this before with live radio internet streams, but not a recording from a tuner.