yashsingh1/xdaforums huggingface dataset:
[Moto E (2020)] Cyb3rSl4v3:
clarifying a few points above-

- i had forgotten the twrp install step of via .zip (including magiskboot and ramdisk-recovery.cpio stuffs). I.e. I was just able to use the lineage171 recovery to install its build, but just not to install itself as twrp can (perhaps an a/b magisk thing, not sure maybe I saw that was a known thing until lineage adds that functionality? Perhaps I could reuse the twrp zip, or presumably better start building twrp from github now that I'm past the point of having a building lineage tree to use for that purpose)

- indeed MLBM can replace the orange bootloader unlocked splash/logo (which unlike moto-g-2015, is shown after a few milliseconds of the normal seperate logo image). But it doesn't look like there is a way (yet?) with MLBM to effect the 'N/A' text/font/color which remains (again, presumably obscurable if you put an area of white pixels over it on your custom replacement)

- my specific 17.1(and 18.1) build issue with device/motorola/ginna/libshims/Android.mk not-so-much-of-a-workaround-because-simdetection/calling-no-longer-works was a result of this-

"

FAILED: finishing build rules ...

Error: makefile error

Output:

ESC[1mdevice/motorola/ginna/libshims/Android.mk: ESC[31merror:ESC[0mESC[1m "libqsap_shim (SHARED_LIBRARIES android-arm64) missing libqsap_sdk (SHARED_LIBRARIES android-arm64)" ESC[0m

You can set ALLOW_MISSING_DEPENDENCIES=true in your environment if this is intentional, but that may defer real problems until later in the build.

ESC[1mdevice/motorola/ginna/libshims/Android.mk: ESC[31merror:ESC[0mESC[1m "libqsap_shim (SHARED_LIBRARIES android-arm) missing libqsap_sdk (SHARED_LIBRARIES android-arm)" ESC[0m

You can set ALLOW_MISSING_DEPENDENCIES=true in your environment if this is intentional, but that may defer real problems until later in the build.

ESC[1mbuild/make/core/main.mk:972: ESC[31merror: ESC[0mESC[1mexiting from previous errors.ESC[0m

"

At one point, still even earlier in noob mode, I guessed and tried treating (iirc) /vendor/{lib,lib64}/libqsap_sdk.so as perhaps missing device blobz, and/or went with ALLOW_MISSING_DEPENDENCIES=true. Maybe I'll try again now that I've otherwise got a successful build. I'm doing all this just using the 3 android_ repos from github.com/motoe7. Let me know if I should be using any of the other repos.
[Moto E (2020)] Cyb3rSl4v3:
github.com/LineageOS/android_system_qcom seems to be the answer to my libshims/libqsap_sdk.so issue. I now have a build that at first glance at least is a good reproduction with the addition that speaker out now works for me. Still no in-call volume control. Though as I typed that I see that I seem to be getting crashes similar to what I first reported here but were fixed with the update build. I'll skim my logs a bit...
[Moto E (2020)] Cyb3rSl4v3:
and seeing the recent git commits and motog7/17.1/nightlies thread (and my log) it seems I can live without MotoActions for the timebeing. I may try toggling some of the recentish audiofx things at some point to see if that gets the in-call volume control working. Also, /d/gapps seems to not apply without root, but I'll try building 18.1 again.
[Moto E (2020)] googleverifysux:
Is this ROM mostly functional? RE: Voice, data, sms? Is it Gapps free?

Just got this phone yesterday & want to start w/ an aged, working build before experimenting further. Open to other suggestions, just want to be free of Goog apps & framework...

Thanks to all who have taken the time to make this affordable phone tweekable.
[Moto E (2020)] Lahpyrcopa:
From my experience it is 80% stable with certain glitches that occur.
[Moto E (2020)] Sewdohe:
I've tried flashing multiple different build of this ROM, and everything is working great, except when I try to flash GAPPS (anything besides pico) and I get an error about having no space on my /system partition.

When flashing PICO gapps, the installation finishes, but the OS fails to boot afterwards.

Any ideas? I've tried Lineage 17 and 18 now and can't get either to work.
[Moto E (2020)] Sewdohe:
It is gapps free, and everything is working on my Moto E. Can't get GAPPS to flash for the life of me though.
[Moto E (2020)] Electimon:
Recommend to use LOS 18.1 Modded instead
[Samsung Galaxy Note 20 Guides, News, & Discussion] evnStevn:
Good Morning Everyone!

Since I was unsuccessful adding a couple of jpeg files to my original post a few days ago, I've included them here! Enjoy!
[Galaxy Tab S Q&A, Help & Troubleshooting] ThatsaMech:
Hi. I've got a SMT700 that I purchased new and have used for several years with only minor troubles(Having to reconnect the battery occaisonally) and recently I had a new issue come up I've no idea how to fix. My knowledge on this stuff has extremely large holes in it, so I may have missed something obvious. I've been poking around all week trying to figure it out to no avail.

Anyway, the issue: My daughter was using the tablet and it became unresponsive. I popped the back off and fixed the battery cable(It had come out) and after doing so it flat out refused to turn on. Wouldn't boot in recovery or anything else I could think of. So I plugged it in overnight and let it charge just to make sure, since I wasn't sure if it had had much of one when it turned off. Will not turn on. If you push the power button while it's plugged in, the status of the charge(Says 100%) will blank out and then it resets like I just plugged it in. I've found that if I try to boot it in Recovery, it will come up just fine - if I unplug it, it turns off instantly. If I reset it, it turns off and goes back to the charge status screen as if I just plugged it in. It just has the Samsung firmware installed, I believe fully updated(I rarely check it since the tablet is old and it's literally just used for Disney+ for the kid lately) I'm at loss for what could it causing it or what I can do to fix it. Anyone seen this and able to point me in the right direction? Thanks for your time.

Oh. And I have tried plugging it into the computer, but it doesn't even register as plugged in(Can't do recovery or anything) - that didn't really surprise me, it wouldn't charge that way before so I didn't think it would work.
[Moto E (2020)] Electimon:
OrangeFox Recovery Project

/*
* Your warranty is now void.
*
* We're not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this recovery
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/

OrangeFox is FREE SOFTWARE

Supports Treble, Custom Roms

Credits

* TeamWin - for TWRP

* The OrangeFox Team - for your hard work

* All our testers - for your patience and help

FEATURES:

* Updated with latest TWRP commits

* Built-in support for installing init.d functionality

* Built-in support for installing Magisk

* AromaFM

* Flashlight

* Password, torch, led

* Support for Custom ROMs

* Superb new UI and themes

* OrangeFox theme engine:

- choice of theme (black, dark, etc)

- choice of color scheme

- choice of splash screen

* Alternative lockscreen

* And many more!

DOWNLOADS

My Website: https://1pwn.ixmoe.com/android/ginna/recoveries/ofox/

INSTALLATION

1. Download the OrangeFox zip to your device

2. Reboot to your existing OrangeFox (or other custom TWRP-based) Recovery

3. Install the OrangeFox zip as a normal zip installer

4. The device will automatically reboot into OrangeFox recovery after installation (allow this to happen)

5. Enjoy!

FAQ and Guides

: https://wiki.orangefox.tech/en/guides

Contributors

@Electimon, @RohanHasabe8

Source Code: https://gitlab.com/OrangeFox

Version Information

Status: Stable

Current Stable Version: R11.0

Stable Release Date: 1-29-2021

Last Updated: 6-1-2021

6-1-2021:

* Touch is fixed for new panel variants of ginna (ofoxginna2.img, ofoxginna2.zip)
[Moto E (2020)] atsalchenberg:
I love this recovery it works great
[Moto E (2020)] Lostwon:
1pwn.tk is down....

Please mirror.
[Moto E (2020)] Lostwon:
THANKS
[Moto E (2020)] Hypercore:
This is hands down the best Android Recovery I have ever used. Amazing work on this. Thank you for creating such a work of art.
[Moto E (2020)] isasharaf:
Thank You very much for your awesome work!
[Moto E (2020)] googleverifysux:
Mirror?

Hope it's cool for me to put this right here....

index - powered by h5ai v0.30.0 (https://larsjung.de/h5ai/)

index - powered by h5ai v0.30.0 (https://larsjung.de/h5ai/)

2pwn.tk

Thanks Electimon & Co!
[Moto E (2020)] googleverifysux:
Anyone have a hint as to why none of my recoveries have touchscreen support? Have tried booting & flashing all .img's below, to no avail. When I install zip installer, I only get scary 'unable to boot' log in bootloader(paraphrasing).

On earlier TWRP's w/out lockscreen, as soon as I enter 'adb shell twrp sideload', the screen starts fuzzing and adb connection is lost/unusable. I have seen the issue w/ Focal? panel driver, but at least one of the TWRP img claims to support said display.

Anyone have some insight?

Tried:

Electimon's ofoxginna

TWRP-3.4.0-0-ginna-2020-12-08

twrp-3.5.0_10-0-ginna

twrp-3.5.0_10-1-ginna

twrp-3.5.1_10-0-ginna

twrp-3.5.2_10-0-ginna

twrp-dbg-3.5.0-47-ginna
[Moto E (2020)] Keven11:
I have tried all of these. The only one that I had any issues with was TWRP 3.4.0.0 and they were minor bugs. OfoX works great, and is my favourite to use as it is 64 bit. The issues you are experiencing more than likely are caused by either your device, or installation process.
[Moto E (2020)] Keven11:
I have found that OfoX is the only one that the installer zip works better than flashing img's. It sounds like you might have an issue with your device's micro USB port.
[Moto E (2020)] googleverifysux:
Booting & flashing Recovery is a fairly straightforward task, yet always no touch(regardless which A/B part, or both). I have used several cables but no joy. Also, have flashed XT2052-1_GINNA_RETUS_10_QPGS30.82-105-2, boots but no touch; XT2052-1_GINNA_RETUS_10_QPGS30.82-105-4 boots w/ black screen, hear the "Hello Moto" of bootloader gif; and latest XT2052-1_GINNA_RETUS_10_QPGS30.82-135-2 repeatedly reloaded(& rooted w/ Magisk) without any troubles any of the times.

I did note when I run my flash/bat file, it adds _a to all Android partitions but the Supers, regardless if I'm in A or B partition. Have created a bat leading w/ "fastboot set_active b", reboot bootloader, followed by all <image>_b pre-set and have to insert "fastboot set_active b" before the Supers or it is back on the A partition by the time flashfile completes. No stock FW, even the latest, has ever booted successfully on B partition, either. I wonder if my B part is corrupted, or if there's new security/safety features I am ignorant of? I did attempt to flash CopyPartitions zip in installed LOSRecovery(Button-nav), but most partitions(data/system/???) failed to mount... and copy, presumably. I am at a loss. The "X won't work until Google sucks my data soul dry" notifications on stripped/disabled/firewalled stock apps are driving me nuts.

Edit: Thanks for replying. I was rushed when I tapped my response and in hindsight it may have come across as unappreciative.
[Moto E (2020)] Keven11:
I'm always happy to help where, and when I am able. It does sound like you may have a corrupted device. Have you ever tried to flash the bootloader_b? If so, that is more than likely the issue. The device has no bootloader_b partition, and attempts to flash to it can cause some strange issues. The supers don't need separate a/b slots as it is handled internally. I hope this helps. Have you tried to blankflash the device and start from scratch? If not, that's what I would recommend. Here's a link to the Moto e telegram group. If you have more issues I would recommend checking it out. There are some very knowledgeable people there. https://t.me/motoe7
[Moto E (2020)] googleverifysux:
That's probably it. Unsure if I flashed stock before trying TWRP, but is possible.

Unsure how to blankflash a working device, I have the Ginna file from lolinet & may have win drivers from reviving my G7 Power.

Will pursue that avenue. Thanks for the insight, will delve further into the latest A/B changes.
[Moto E (2020)] Keven11:
Sorry.... After a little thought on my part, I realized that what I said about dynamic A/B devices not having a bootloader_b partition was incorrect. I misinterpreted a message from a friend about it. From what I understand, most A/B devices don't have a bootloader_b, and flashing to it isn't necessarily the cause of your issues, but switching slots without a complete understanding of the partition layout, and workings of the system can lead to weird issues such as what you are looking at. Don't get me wrong... I am not saying that you don't have a "complete" or a good understanding of A/B slots and how they work. I don't fully grasp it myself, and I don't mess around with switching slots unless I am certain of the need and what the outcome will be.... That was what I meant.

So, all that aside... As long as your CID is intact then you shouldn't have a losing battle on your hands. Which version of stock firmware did your device come with as OEM? I'm assuming it is a retail phone, as you mentioned flashing the retus firmware. Is that correct? I have the xt2052-1. I am in Canada and it's the retca version, but The latest FW for me is QPGS.30-82-141-3. If it would help you I can send you any data, info, or images you need to get it back going. I would prefer to stick to the retca FW. So, if you can make that for you I will flash any of the stock FW version you see on lolinet that closest matches your's and pull whatever you need before I allow it to connect to a network of any kind to get the cleanest images possible.... Let me know if there is anything I can do to help you get it back working. I'd be happy to help.
[Moto E (2020)] googleverifysux:
If post below is still applicable, I have a pretty good idea as I spent most of lockdown flashing ROMs on my XT1955-1. Besides 1 hard brick(don't recall exact reason) I never had any problem running recoveries/ROMs on either partition.

https://xdaforums.com/t/guide-the-n...titions-and-other-op6-idiosyncrasies.3816123/

CID? Cell ID? Similar or same as IMEI? IDK, but the phone works 100% on Tmo in the US using latest FW(RETUS_10_QPGS30.82-135-2). Pretty sure it had latest FW originally, manu date on box( 03/25) is weeks after 135-5 release date. Paid full, unactivated price from retail(Best Buy) w/ no branding or subsidies.

Unsure what files I would need from another phone. When I flash any FW partition(eg: fastboot flash recovery recovery.img) the CL always adds _a to the part(eg: fastboot flash recovery_a recovery.img), unless I explicitly type fastboot flash recovery_b recovery.img.

Getvar results:

(bootloader) current-slot: a

(bootloader) running-boot-lun: 0

(bootloader) running-slot: _a

(bootloader) slot-suffixes: _a,_b

(bootloader) slot-count: 2

(bootloader) slot-successful:_a: Yes

(bootloader) slot-successful:_b: No

(bootloader) slot-bootable:_a: Yes

(bootloader) slot-bootable:_b: Yes

(bootloader) slot-retry-count:_a: 5

(bootloader) slot-retry-count:_b: 0
[Moto E (2020)] Keven11:
That was a great write-up. I am going to have to read it when I am fully awake. It's 5:30 am here.

As long as you haven't seen the error: CID 0xDEAD then it should still be intact. CID is different from the IMEI it combines a few variables and cannot be easily duplicated. Sorry for the bad explanation...again not awake or all there yet.

Here is the getvar I just ran on my moto e.

(bootloader) current-slot: b

(bootloader) running-boot-lun: 0

(bootloader) running-slot: _b

(bootloader) slot-suffixes: _a,_b

(bootloader) slot-count: 2

(bootloader) slot-successful:_a: Yes

(bootloader) slot-successful:_b: Yes

(bootloader) slot-bootable:_a: Yes

(bootloader) slot-bootable:_b: Yes

(bootloader) slot-retry-count:_a: 6

(bootloader) slot-retry-count:_b: 6

I will consult with someone who knows a hell of a lot more than I do and get back to you with what I am able to find out.
[Moto E (2020)] Keven11:
Actually, I think I have a flashtool that will help. Which OS are you running?
[Moto E (2020)] dpsnoke:
I am in the exact same boat as googleverifysux. I also can not downgrade to a older stock rom as well. If i do the screen is black and boots into bootloader or boots but no touch screen.

I have Moto e 2020 XT2052-1 with build number QPGS30.82-135-5.

I have tried all the TWRP and Orangefox recoveries and the touch screen does not work on any of them. I was able to Flash Lineage recovery and install some of the custom roms available at https://androidforums.com/threads/roms-android-10.1331940/

but no touch screen after they boot into the rom.

I even flashed PizzaG kernel but after that with a stock rom touch screen stops working.

I have checked in my sys/devices/virtual/touchscreen/..vendor and it shows Chipone.

any thoughts about a recovery image or why my touch screen is not working in them.

i have noticed in the getvar results after installing any old stock rom or custom rom it says ro.build.fingerprint is QPGS30.82-135-5

Almost like if you dont flash whats in the fingerprint it will not work.

I am tech savvy and can provide you with any info you might need. I am sure Im not the only one with this issue.

Also i have windows 10 with a Linux VM.

Thanks so much in advance.
[Moto E (2020)] Keven11:
Ok, I have a custom built flash tool for the Moto e xt2052 that PizzaG put together. It's the 6th revision of it so you know it has been thoroughly tested. It has unbricked mine more times than I care to count. Let me know if you want to try it, and I will up it and give you guys a link. As far as what the root of the issue is I am not certain yet. I'm going to look into it further when I get a chance. If that fails I can pull a complete NANDroid with all partitions included from a fresh clean flashed stock ROM, and you guys can flash whatever it is that you need.
[Moto E (2020)] dpsnoke:
I would love to try the flash tool. Thanks. Let me know if there's anything you need from us. I have tried just about everything. Good thing is I haven't bricked it and can always get back the stock rom on it.
[Moto E (2020)] googleverifysux:
I would almost welcome a brick to enable the use of blankflash and knowing I am truly back to square 1. Is it possible to force Qualcomm drivers to load for working phone in Windows?

dpsnoke:

Are you able to flash latest stock FW to both partitions and successfully boot? My B part has never booted any ROM. Had to boot to LOS Recovery on A, fastbootd to switch to B and then flash LOS Rec to get recovery to finally boot on B. Still no joy, as system & data are still unmountable(encrypted?).

And are you using MagiskManager-v8.0.0?

I have read of problems w/ Android 11 & latest Magisk(droidwin.com), wonder if those problems have been included in more recent 10 updates...

*** Unrelated or Related: No tinfoil hat required:

Magisk developer John Wu leaves Apple to join Google on the Android security team

John Wu, better known as topjohnwu, the developer of Magisk, has left Apple to work at Google on the Android security team.

www.xda-developers.com

At this point, I have to reload fresh RETUS, root w/ Magisk & neuter the stock garbage to get a functioning phone. When my current work project is completed, I will have time to recommence testing(1.5 - 2 weeks). Until then, I will chime in if I have something new to add.
[Moto E (2020)] Electimon:
People with non working touch, do note that your device has new touch chip unsupported by our kernel. Waiting on motorola to release new sources.
[Moto E (2020)] googleverifysux:
Thanx for the 411, Electimon!

Hopefully, one day, I will be able to undo the damage I have wrought upon my phone.
[Moto E (2020)] dpsnoke:
Do you use LMSA or RSD Lite? I was able to Flash 135-2 on partition a, then it did a auto update to 135-5 on partition b. If I load bootloader and and change back to partition a then do a factory reset in recovery i can get back into 135-2. I am not sure what damage you might have done to your phone. I have done everything to mine to brick it but have not. as of now i am not rooting it. keeping it stock. Also you can use this tiny fastboot app. https://mirrors.lolinet.com/software/windows/TinyFastbootScript/

Just put the stock recovery rom unzipped in the same folder as Tiny fastboot like this and run flash.bat. Select option 5 for a full firmware and factory reset. I have even downgraged from 135-5 to 135-2 using this. Also i think 135 is the lowest these new phones can go with the new kernel. You were right. I was not able to get a rom to load off partition b untill the OTA update took place. Partition b is not the root of our problems so i would not worry about it. Install 135-2 and let the OTA do the update. After the update you will see partition b as active. If you want to go back to parition a you can just do a fatory reset and it will boot from partition a which is 135-2. Hope im making since.
[Moto E (2020)] googleverifysux:
Thanks Dpsnoke(& Kevin11?), I d/l'ed a copy & will take a look. Before I do anything else I will wait for the display driver to see what needs to be addressed. If things work as in previous models, as soon as Recovery can mount system & data, a flash of copyparts zip should remedy the situ.

I hope. We'll see.
[Moto E (2020)] Electimon:
We'd prefer if you just linked the official site for TinyFastbootScript

lolinet mirrors - firmware, software, iso etc.

lolinet mirrors - powered by h5ai

mirrors.lolinet.com
[Moto E (2020)] dpsnoke:
Sorry about that. I edited my post. Thanks for all your help.
[Moto E (2020)] Keven11:
Well, I had no clue that Moto released another variation of the xt2052-1 with a different touch chip. That is good to know. I should have asked which your's was to begin with. Here is that flash tool. There is a Windows batch file(zipped), and a Linux bash script. Both were built by PizzaG. I hope this helps.
[Moto E (2020)] Keven11:
I found this write up on slots was quite well written. https://source.android.com/devices/tech/ota/ab#slots
[Moto E (2020)] Electimon:
Touch is fixed, please reread the post.
[Moto E (2020)] The Knuckle:
I'm kinda new to all this but trying to degoogle and debloat my moto e.

Pretty sure I just did something out of sequence or missing a step.

I've been trying to install TWRP and Magisk. Ended up getting Magisk installed using a patched image and ADB. and tried all TWRP files and ended up getting 3.5.0 to boot but no touch screen function. Which lead me to Orange Fox.

I followed the quide and was able to install and boot into Orange Fox Recovery but the step where you need to install the Zip File within OFox on the cell phone wont install.

I get this error;

-This device is an A/B device

-But it also has a recovery partition!

-I cannot find magiskboot. Quitting!

Updater process ended with error; 1 Error install Zip File ofoxginna2.zip

Thanks for any help!! so many hours into this.
[Moto E (2020)] Keven11:
Which variant do you have? ....XT2052-? New touch chip I assume? If so, that might be the issue.
[Moto E (2020)] JimboRingo:
Noob here, i have followed the steps on the wiki and have the same error as post #32 (I cannot find magiskboot. Quitting!). I tried with ofoxginna2.zip as i thought it might handle my variant which has a Chipone chip.

I can follow up where the poster left of:

XT2052-1

Chipone touchscreen (/sys/devices/virtual/touchscreen/ICNL9911C/)

Build QPGS30.82-135-7

What is the consequence if this step cannot be done? Thanks!
[Moto E (2020)] Keven11:
The consequence would be not being able to use the touchscreen. So your only option (if you went ahead) would be to use a mouse through an OTG adapter. I don't recommend it.

I think you need to boot into any recovery(for this device) using fastboot boot "recovery".img. From there you can flash the OfoX.zip then reboot to recovery (should boot into OfoX now). Then flash magisk from there. Also, your device has the "old" touch chip. So you would need the ofoxginna.img/zip. Not the #2. I hope this helps.