yashsingh1/xdaforums huggingface dataset:
[Huawei P40 Pro Guides, News, & Discussion] COREopa:
I have found a guide that uses Phyton to brute force it.

Might try this when i got a new daily driver to see if it works.

Droidwin - How to unlock bootloader on Huawei devices via brute force
[Huawei P40 Pro Guides, News, & Discussion] badmania98:
That is for Android/EMUI bellow 10.
[Huawei P40 Pro Guides, News, & Discussion] deadofgamers:
Has anyone found a solution?

Test Point Cable ? Harmony TP Cable can it work?
[Huawei P40 Pro Guides, News, & Discussion] badmania98:
Save your time. It is not possible.
[Huawei P40 Pro Guides, News, & Discussion] deadofgamers:
No problem, I'll wait and see if there's an opportunity later...

Sigmakey box and test point already unlocked (youtube video)

But for this 1 device I'm not going to drop nearly $439

as soon as there is a solution please contact me privately

Wait Wait Wait X Time...
[Huawei P40 Pro Guides, News, & Discussion] mafury:
2050 arrives tomorrown. Still no possible? thanks.
[Huawei P40 Pro Guides, News, & Discussion] deadofgamers:
Any solution? 😔🙏

I really need the root
[Huawei P40 Pro Guides, News, & Discussion] LavX.hu:
There'll be an option if Huawei wants to do so. Without them, there is no chance, unfortunately. I have waited for two years, but the only solution is to switch to a non-Huawei phone. I don't understand why Huawei created barriers.
[Moto E (2020)] Electimon:
/*
* Your warranty is now void.
*
* I am 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 ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/

LineageOS Modded is a free, community built, aftermarket firmware distribution of Android 11 (R), which is designed to increase performance and reliability over stock Android for your device.

LineageOS Modded is based on the Android Open Source Project and LineageOS with extra contributions from many people within the Android community.

All the source code for LineageOS Modded is available in the LineageOS Modded Github repo.

What's working?

Everything as far as I can tell...

Installation

1. Boot into twrp

2. Advanced -> ADB Sideload -> Swipe

3. adb sideload copy-partitions.zip

4. Go back into sideload mode

5. adb sideload lineage.zip

6. Wipe Data

7. Reboot to bootloader

8. fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img

Downloads: http://1pwn.ixmoe.com/android/ginna/los-18.1/lineage-18.1-20210621-HOMEMADE-ginna.zip

Notes

This ROM comes with Google Apps!

This ROM comes with Customizations that are not apart of LineageOS

Sources: https://github.com/motoe7

Credits: @electimon, @RohanHasabe8, betaxab

Jan 27 2021: Fix Safetynet, fix touch issues, fix some other issues

Jan 28 2021: Fix PIP mode

Jan 30 2021: Fix Hotspot

June 2 2021: Fix touch for ginna models with the new panel

June 15 2021: Fix touch for focaltech panels

June 20 2021: June Patch, fix safetynet and other little stuff
[Moto E (2020)] anthony.d:
Awesome, been waiting for this, thanks very much! Had some errors while loading copy-partitions.zip but the image flashed and seems to be working well. Look forward to future versions with SELinux enforcing and also without gapps (but maybe that's not likely with no opengapps for 11?)

Would be great if there was a way to remove the obtrusive "device can't be trusted" message at boot. It can be just as trusted as my desktop PC ffs. At least moto allows the bootloader unlock without much trouble.
[Moto E (2020)] Electimon:
hi, selinux is enforcing also there will be no version without gapps sorry
[Moto E (2020)] anthony.d:
No worries about the gapps, i'm grateful to have a lineage rom for this device.

I tried flashing again. Pardon if the details below are excessive, I don't fully understand the process, and the dual-slice device config. Here's what happened:

copy-partitions gets to 47%, then fails with the following error:

Partition vendor_a

dd: /dev/block/dm-4: write error: No space left on device

installed lineage again, this time went to slot B. rebooted back into TWRP and tried copy-partitions again (to see if it was different after lineage had been installed in both slots) and this time it succeeded. Installed lineage again, this time to slot A. Wiped the device, rebooted, and I still get the selinux error. If it's relevant, the device model is XT2052-1.

Also want to add: I applied disable-verity both times, and cmd line output indicated writing to vbmeta_a and vbmeta_b.
[Moto E (2020)] Electimon:
weird, how are you checking for enforcing?

android_device_motorola_ginna/BoardConfig.mk at efea8269c9a6a232d8ba38b0629a61eb590b2db5 · motoe7/android_device_motorola_ginna

Contribute to motoe7/android_device_motorola_ginna development by creating an account on GitHub.

github.com

you can see here that permissive is commented out, the rom is enforcing.
[Moto E (2020)] Cyb3rSl4v3:
I installed the rom mainly as a reference against the no speaker (except in calls) issue I'm having with 17.1. Also I'll note there the issue isn't jacksensing as I had guessed. A soundfile playback autopauses on headphone removal. With 18.1 here I do get speaker output, however one bug I noticed for me (boostmobile-sku:mot20526anb/xt2052-6) (also present in 0206 17.1) is that in-call volume adjust doesn't work. The indicator moves, but the actual volume does not. I'll send some logcats. Seems to be stuck at what is probably supposed to be max volume.
[Moto E (2020)] Cyb3rSl4v3:
Is there a standard/safe way to uninstall gapps via scripted adb commands immediately after install? I experimented with a crude attempted pm uninstall/disable/disable-user of all com.google.* packages but was not too surprised when the result failed to boot past the lineageos boot animation.
[Moto E (2020)] Electimon:
I'm unsure of that
[Moto E (2020)] Cyb3rSl4v3:
I finally figured out how to build 18.1 on my 8g-ram system such that I don't have to worry about uninstalling gapps (amongst other motivations). I'll post details once I've done another less manual build. The trickiest part was that the 17.1 workaround of setting JAVA_TOOL_OPTIONS/_JAVA_OPTIONS to -Xmx6g wasn't getting used by metalava in 18.1. I ended up editing the last line of out/soong/host/linux-x86/bin/metalava and putting it in there which finally worked. Perhaps tools/metalava/gradle.properties is the right place. My first pass doesn't have carrier data/call service working, but that may be because I did something with TimeService to get it to compile. In any event, I think the 16g minimum warning from the build system is more than a bit confusing combined with the metalava java heap issues. I may try a 4g-ram build sometime just for amusement... It just seemed inconceivable that there really was a 16g-ram requirement. I know even phones come with 16g these days, but still. Of course my hope is to see a cheap phone of mine self-hosting one of these days. Perhaps with some high end microsd card or an otg drive for swap partition and build tree...
[Moto E (2020)] Cyb3rSl4v3:
I haven't quite done a fully automated build yet, but tools/metalava/gradle.properties didn't work for me. Then I found that the metalava (wrapper) script was build/soong/scripts/jar-wrapper.sh, and adding a next to last line of-- javaOpts+=("-Xmx6g") --seems to work. I also now better understand device/motorola/ginna/lineage.dependencies and seem to be able to reproduce this image sans gapps (though an selinux issue i haven't looked too much at yet). I may focus more on 17.1 until 18.1 becomes more generally official. I also seem to be getting occasional sigsegvs with jre/metalava dumping hs_err_pid*.logs. However thus far a simple rerun of brunch/ginna has never reproduced the problem.
[Moto E (2020)] fddm:
Camera apps have quite a lag related to camera apiv2. Haven't had time to debug, but Open Camera works perfect as it defaults to the old api.
[Moto E (2020)] Spaceminer:
Do we have system read/write on these builds and does magisk work?
[Moto E (2020)] fddm:
Idk about system r/w, but Magisk works fine. This is also a really good rom. Stable and nearly everything works.
[Moto E (2020)] Spaceminer:
I checked, it has system rw. I can't believe how fast my LTE speeds are too. 7-10MBs vs 50kbs on stock. The only thing holding me back is no full screen toggle for apps, and the in call volume is stuck at the maximum at all times. Soon as those get fixed I'm running this 24/7.
[Moto E (2020)] RaceyMcRacerson:
2+ months now with 18.1 on my daily driver.

No hardware issues.

Ofox recovery.

Magisk 21.4 thru the latest canary build have worked as far as I can tell.

No volume troubles.

Can mount system RW.

My only setback is that I don't have access to around 9Gb on /data and /sdcard, including /sdcard/Android/obb

I can set perms any way in terminal and in recovery terminal 0777, 0655, etc., but upon reboot, I cannot read or write.

Can read and write to /system and /system_root, no problem.

This is possibly due to me forgetting to wipe encrypted /data after first flash? I wiped after first boot, no change.

Then, started the flash process from scratch and wiped before first boot, but must have missed something.

The file and folder names are not random characters.

One of those things I thought will work out when I get around to it, but now just found my pics are being saved to a folder in the mystery space, and I need to place a .zip in *./obb.

Im learning, A/B is new to me.

Maybe my mistake will help someone when I find a solution.

I am open to suggestions, lessons, and any other info, even if I should already know it.

I will report when something changes.
[Moto E (2020)] Spaceminer:
I never had this issue so I'm guessing it's something to do with encryption. I would try clean flashing LOS to both slots then formatting data using the type "yes" option to remove encryption. Are you using adoptable storage by chance?
[Moto E (2020)] Mr.Conkel:
How can I install this rom via recovery, I have never used side load. Why is it not booting? What is wrong. I flashed rom in slot B with twrp in slot A sorry still a little new with this device. But regardless it is not booting whatsoever and I am confused as to why
[Moto E (2020)] Spaceminer:
Flash it to both slots and format data before booting up.
[Moto E (2020)] Mr.Conkel:
Is there any benefit of having it flashed to both? Cause I did get it working. There's not currently anything on slotB
[Moto E (2020)] Spaceminer:
Not that I'm aware of. I've never got it to boot without flashing to both slots though. Did you use the zip, or fastbootd images?
[Moto E (2020)] Mr.Conkel:
I used the zip. I mean either way its working lol. Both slots could be flash I honestly have no earthly idea haha
[Moto E (2020)] jasonmerc:
Thinking about picking up a Moto E 2020 (USA variant? if they still do that). How's stability with this ROM? Do all, if not MOST, features work? If it's good enough for a daily driver I might pick one up to replace my dying X4 with its constant signal issues and connectivity drops.
[Moto E (2020)] fddm:
Use this ROM on my main phone and it's really very good. Fast and stable and provides a better experience than stock IMO. I'm a bit behind on updates now, but I do experience a finicky(but usable) camera.

Even though I personally like it, I'm not sure I'd recommend it to others. This is a low end phone that had a very short production run and sports really unimpressive hardware.
[Moto E (2020)] jasonmerc:
Thanks for the feedback. Honestly, I'm not too worried about "features". If an Android phone can use Telegram and stream YouTube, then I'm happy. Only reason I bought an X4 before was because it was on clearance and the cheapest thing in the store... I too like to hunt for the cheapest moddable thing I can, and this new Moto E seems like a good replacement for my screwy X4.

Does using another app with its own drivers, like OpenCamera, alleviate the finnicky camera?

EDIT: If you don't mind saying too, can you tell me how signal is? Like what carrier you use and if it drops frequently? Dropped bars/dropped LTE is a HUGE problem with my X4.
[Moto E (2020)] fddm:
I thought it had initially, but it does not. You basically need to either close and reopen the camera app or switch between the front and rear cameras to get it working. The camera can still crash afterwards, easily reproducible by zooming in and out a few times. Over all not that bad though. At least I haven't been bothered enough to debug and try to solve the issue.

I'd mark the mobile connectivity as average, it doesn't drop randomly or anything like that. It doesn't reconnect as soon as I would like when the device returns to a serviced area. I often end up toggling airplane mode rather than waiting. Suppose it would waste too much battery to poll aggressively when signal is lost.
[Moto E (2020)] Sewdohe:
Just flashed the latest build on here from stock, and everything seems fine but the touch screen isn't responsive....tried earlier builds, but all that I've tried thus far won't read my SIM card, even after a factory reset.

Any ideas? I'd really like to breathe new life into this old dog.
[Moto E (2020)] Electimon:
Waiting on motorola to release new sources to support the new touchscreen chip.
[Moto E (2020)] Sewdohe:
Any timeframe on this, or maybe even a best guess? Or do you have a solution for the ROM not reading my sim card?

Also, if there is ANYTHING I can do to help this ROM along, please let me know. I'm not experienced with Java, but I'm a long time web developer and have been dabbling in Rust/Systems programming lately. I'd love to help out.
[Moto E (2020)] jasonmerc:
Sorry to butt in here, but if you could list the variant of Moto E 2020 you have that might help. Perhaps with the sim card thing, it only affects certain carrier versions, or the dual sim version, for example (I know nothing about the variants of this phone, I was just listing examples)

Should be in Settings>About Phone>Hardware if you're looking for the model number of your device. Once we get that I can walk you through the process of generating some logs that might help debug the problem too.
[Moto E (2020)] Sewdohe:
Okay, So I have the XT2052-1. It was purchased at Walmart, so I think that actually makes it the trac-phone version of the phone?
[Moto E (2020)] jasonmerc:
I didn't know Tracfone versions could be unlocked for custom ROMs, that's actually pretty cool

So now it's just a matter of taking the right log. On the F-Droid store there's an app called MatLog Libre. This can read and export logcats, but I think it needs root permissions. You can either get it in the F-Droid store or directly download the APK itself HERE.

Download the app and run it, there should be a "play" option to allow it to take logs. Do a test at first to make sure it all works. Then move onto the real deal: capturing the issue. If you can do a specific thing to make your issue happen, press play, do the thing so the issue happens, and then pause/export it. If your issue happens at random, make sure it's "on play" once your phone starts up, then as soon as you notice the issue again jump over to the app and pause/export the logcat

Since this is an unofficial ROM, post it up on here (or check the OP, they may have requested bug reports go elsewhere) and the maintainer of this can take a look and see what the issue is
[Moto E (2020)] googleverifysux:
I bought my XT2025-1 from Best Buy w/ no activation or subsidies. After enetering my Simple Wireless SIM the phone auto-populated a TFWAP APN... I presume that is TracPhone? IDK what TF is, nor care beyond the signal sucked. I created a T-Mobile APN* and it works much more better. I never had a problem detecting SIM, however.

* Tmo APN= I did have to sneak up on it & save it BEFORE entering the last entry, APN type. 1st time I hit save nothing saved/populated in my APN list. I believe the dun is shunned, if problems persist, try omitting dun & try.

**Further thought, could have not saved b/c orig source had MNC:260. Is an old source, but it may still allow unlimited tethering, IDK, never tried it.

***Also, could try IPv6 protocols. Don't recall why, but I reverted mine to IPv4 to work around some issue or another in the past.

​
[Moto E (2020)] Sewdohe:
Okay, I'll try this tonight. The newest build doesn't have working touchscreen, so I can't use that, and older builds won't read the SIM card so I guess a logcat taken at any time would work? I have to re-flash the ROM. I'm sitting on stock rooted ATM and honestly it's really great with GravityBox and Magisk Modules. This has been really confusing for me as the last time I rooted a phone it was the first gen Moto E and Xposed was the big thing at the time lol
[Moto E (2020)] jasonmerc:
So the older ROMs work with the screen but not sim, but it sounds like the newer ROMs work with the sim but not the screen? I think we may have pinpointed the problem there.

If this is the case, it sounds like 2 things happened since the last build: SIM card changes happened, and touchscreen changes happened in the code. We can check the OP's sources on GitHub and see their changes they made to their custom Lineage trees and such. We can figure out a middle ground that has both sim AND touchscreen working, and whip up a custom ZIP for you guys with the tracfone variant.

I've never done anything like this myself, but if this scenario as I described it here is how it's really playing out, it would be a good time for me to learn. Should be simple enough... we just use Github's change tracker system to find out 2 things: what fixed the sim and what broke the touchscreen. We start with the old sources (screen works and sim doesnt) and cherry pick ONLY the fixes that apply to the sim card. Then rebuild the ROM with those custom sources. If it works, we can upload our changes to Github and call it a tracfone branch of the sources just for you tracfone guys.
[Moto E (2020)] Electimon:
How about we fix current sources instead of forking off a branch for tracfone guys 🤣

Just need a logcat.
[Moto E (2020)] Electimon:
Touch is now fixed for models with the new panel! -42
[Moto E (2020)] fddm:
Touchscreen has not been working for me since the kernel change with the recent builds labeled HOMEMADE. The Device Info HW app shows the driver as "fts_ts". My best guess after comparing the kernel configs is the missing option CONFIG_TOUCHSCREEN_FOCALTECH_0FLASH_MMI.

Non-working logcat (lineage-18.1-20210602-HOMEMADE-ginna.zip)

logcat_20210602.txt

drive.google.com

Spoiler content hidden.

Working logcat (lineage-18.1-20210321-UNOFFICIAL-ginna.zip)

logcat_20210321.txt

drive.google.com

Spoiler content hidden.

Dmesg

dmesg.txt

drive.google.com
[Moto E (2020)] Electimon:
Thanks for the report, since I switched kernels in #40-42 I forgot to import the focaltech driver. I'm compiling the new build right now.
[Moto E (2020)] fddm:
No luck with the latest build (lineage-18.1-20210610-HOMEMADE-ginna.zip)

logcat_20210610.txt

drive.google.com

I checked the kernel config and it is identical to the previous build.

Sorry if you already know this, I just thought it'd be better to report back anyway.
[Moto E (2020)] Electimon:
Sorry for the delay, try this https://build.lolinet.com/file/lineage/ginna/lineage-18.1-20210612-HOMEMADE-ginna.zip
[Moto E (2020)] fddm:
Sorry I'm late, I just got to test and confirm that touch is working now. Thank you!
[Moto E (2020)] Electimon:
june patch, read post
[Moto E (2020)] RootGod007:
Still am without touch screen xt2052-6 have tried every rom available currently on userdebug 18. Hints or links would be cool
[Moto E (2020)] Electimon:
Did you try to flash latest version ?
[Moto E (2020)] RootGod007:
Yes got it working with ginnahomade. Can't move media from internal to SD... Also have to set selenux to enforce via terminal after reeboot
[Moto E (2020)] fddm:
I hit this as well, I think it's a "DocumentsUI" issue. There is no file picker or dialogue to grant access to storage. No idea about selinux though. It is "enforcing" on my device and even safetynet works.
[Moto E (2020)] RootGod007:
Another issue, device says no sim when I have a working sim on it. Any fixes??
[Moto E (2020)] fddm:
You will have to share a logcat to help identify the issue. There are a bunch of tutorials here if you don't know how to produce one.
[Moto E (2020)] RootGod007:
I do someone said that installing the operating system without the SIM card in would do the correct is this true
[Moto E (2020)] RootGod007:
I havea boost xt2052-6 trying to use qlink sim card
[Moto E (2020)] kcv_earner:
I followed these steps:

1. Boot into twrp

2. Advanced -> ADB Sideload -> Swipe

3. adb sideload copy-partitions.zip

4. Go back into sideload mode

5. adb sideload lineage.zip

6. Wipe Data

7. Reboot to bootloader

8. fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img

Using this image:

Downloads: http://2pwn.tk/android/ginna/los-18.1/lineage-18.1-20210621-HOMEMADE-ginna.zip

But, now I cannot activate wifi or cellular data.
[Moto E (2020)] fuzzbob:
hi there

i've been running this rom for thw last couple monthsand am so thankful to be able to have lineage on sich an affordable device.big kudos!

everything except for SAF seems to be working ao far. the storage access is a bit clumsy. i use material filea app in root mode which allows me to access the external SD card

through the roor directory. and some apps allow materialfiles to broker the storagelocation (eg. magisk module install) but with other app the lack of SAF will lead to crashes when attempting to save files or set directory settings...

all in all very nice and functional for me. just means i changed my phone habbits a bit (no more youtube downloading hehe)

############

type: N57C9

model: xt2052-1 (i believe but possibly xt2052dl or xt2052-6 (type marking seems ambigous?))

build:

lineage_ginna-userdebug 11 RQ3A.210605.005 eng.jenkin.20210621.151854 dev-keys
[Moto E (2020)] Electimon:
Discontinued, los-modded 12 is coming soon
[Moto E (2020)] kcv_earner:
Let us know when it is ready
[Moto E (2020)] Sewdohe:
any eta? I'm guessing crdroid 12 is waiting on this release as well :b
[Moto E (2020)] TheFunkDotor:
im getting tons of random reboots. I tried the most recent and the 06/21 build. this problem doesnt persist on stock rom

i cant even go an hour without a reboot

is this normal
[Moto E (2020)] fuzzbob:
I've been trying to get this to build.

lineage.dependencies

had to add some commas as it was invalid and not parsable

erros with

lunch ginna-userdebug

had to create and initialize kernel & vendor by hand as specified in

lineage_ginna.mk

commented out

$(call inherit-product, vendor/partner_gms/products/gms_go_2gb.mk)

and set BUILD_GMS to "no"

also had to set

export ALLOW_MISSING_DEPENDENCIES=true

I believe eventually I rand into an issue of GCC tools missing from the repo

I believe Android 12 switched to CLANG but I am not sure

I recently installed lineage-18.1-20210623-HOMEMADE-ginna-non_gapps.zip from https://2pwn.tk/android/ginna/los-18.1/ and it is a huge improvement over my manually de-googled version (which had broken file SAF handling) - alas it is still very outdated. Hoping that Android 12 will come around soon... I'd really like to help get this device supported by Lineage. Just a little noobish about it all.
[Moto E (2020)] fuzzbob:
So I have a chance at accessing fast internet and a beefy build machine for a while. Here are the steps I took attempting to build LOS-modded

Model: Moto E 2020 (xt2052-1)

Build number "lineage_ginna-eng 11 RQ3A.210605.005 eng.root.20210623.130639 test-keys"

Spoiler content hidden.

Not sure if I did anything terribly wrong. This is where I'm stuck at the moment... If lineage 19 is the place to be I'd love to help where I can, once I have a working build :)
[Moto E (2020)] Electimon:
You need to clone vendor/motorola/ginna
[Moto E (2020)] TaiAurori:
Touch does not appear to work on my phone running the latest no GApps build. Using the June 12 build linked above works, however.