yashsingh1/xdaforums huggingface dataset:
[Moto G Android Development] MSe1969:
As indicated, I find the situation weird as well and don't really understand it, hence a hardware issue shouldn't be entirely excluded. Although indeed not first choice...

The idea of flashing Stock ROM using *their* genuine flash tool (no OEM ships their device with TWRP, hence the format of their OS files is usually not suitable for TWRP!) as a last resort usually helps to even unbrick the phones, as often even low-level techniques to even restore partitions etc. are applied. Usually, its some Windows program, some USB drivers and then you bring the device into fastboot mode and then all the stuff is flashed on low-level mode.

So please try that - when you search the net, you'll find e.g. a site offering many Moto Stock ROMs of that kind...

Further: The original OP download link of that 10 ROM thread, you have referred to, is broken - so from where did you get the ZIP file, which you have flashed?

Might be worth to have a closer look...
[Moto G Android Development] ChristianWS:
Argh, I was hoping that flashing Stock ROMs made to work with TWRP would be similar, I really hate dealing with ADB. So I need to flash everything, including the Recovery and thus, lose access to TWRP, right? Damn, such a mess I got myself into just because I wanted to see the new shiny thing

It was this one, actually: https://xdaforums.com/showpost.php?p=82781387&postcount=207

Looking back, its clear it wasn't the smartest decision to pick some random ROM, but to be fair with myself: I thought the whole idea of using a Recovery is precisely because ROMs don't make permanent changes to your device, that if you wiped System changes between ROMs aren't supposed to stick.

This is like the idea of installing Linux on your PC and then it screwing something even if you install windows on Top, it isn't intuitive, if you know what I mean. Well, lesson learned

EDIT:

Flashed using the guide, i.e. mfastboot, and to my surprise..... it didn't work. I'm going to reinstall TWRP and Reflash your ROM, I will try to find some solution without having to reflash Stock.

If nothing works I plan to send it to a guy who can open to see if the wifi module is loose or something. If anything else fails, I can at least use another device to tether wifi using Bluetooth.

Edit: Ladies and gentlemen, I fixed it.

Goddamnit, I was searching the web and I found the solution on a brazilian forum(Which I didn't found it before cause I was using my computer, which has google setup to show english results), the solution was to edit /persist/WCNSS_qcom_wlan_factory_nv.bin by putting your Mac Address inside it, another user posted an empty file here: https://xdaforums.com/moto-g-2014/general/fix-wifi-missing-file-t3007540

I picked it up and edited, placed my Mac Address that I got from my router and placed in the file(actually I placed it two times inside what appears to be japanese quotation marks, I didn't thought it would work so I didn't put much care into it), somehow it works now, but the Mac Address isn't the one I put inside the file, so I have no idea what happened. Probably the WCNSS_qcom_wlan_factory_nv.bin was corrupted by Cosmic Radiation or something, and by replacing it with another it worked, probably didn't care what was inside, tho.

I just have a last question: How the heck did this happened? TWRP can flash /persist? Can a ROM access it? If something so crucial to the device as a whole can be messed up like this, why isn't this more secured? Either by removing access to it in TWRP or by backing the goddamn thing in those Stock Rom threads.
[Moto G Android Development] KElNT:
Need more space and speed

Hi and thanks for revive this rom!

i have a moto g xt1032 with only 8gb . What would u recommend me to choose? A or B?
[Moto G Android Development] MSe1969:
Glad, you have fixed it. As indicated, I find it weird, what has happened and really have no good idea.

However, some facts for a better understanding:

- A recovery is supposed to be able to access every partition, that's what it is for!

- I am at the moment and for the next couple of days not at home and have my falcon not with me, so I can't look into that /persist folder, which seems to be Motorola specific thing - nevertheless, I would like to know, whether is that a partition mount point or only a symlink pointing to some place in /system ?

- When a ROM is flashed as a ZIP through TWRP, what REALLY happens is that the installer script within the ZIP is executed. This script is auto-generated during the build process, but the ROM builder can influence that. And within that script, you can literally do anything, like mount partitions, access files, etc.

- Usually, the script contains instructions to mount /system, perform the backup by executing the survival scripts in /system/addon.d, then flashing the /system partition, and last restoring the addon.d stuff. (And of course flash the boot.IMG) Usually - but there could be further commands...
[Moto G Android Development] MSe1969:
Well, depending on your preferences:

a. If you absolutely want the genuine Google services, then it's A, but flash only Pico, and you will anyhow have to balance very carefully the remaining space, which is not much!

b. B therefore is my recommendation, already just because of space, but also in regards to data privacy etc. - but not everything runs with microG! This path makes sense, if you anyhow avoid intrusive apps and care for privacy
[Moto G Android Development] vegenbe:
FWIW, I have the same problem, and I don't recall making any mistakes when flashing for years...

Since nobody complained I thought my wifi chip had to be dead, but strange thing sometimes after a billion of restarts it would work...

I came to same solution as you, except I had no idea what I was doing (a.k.a. probably didn't read everything) so I just placed the empty file in the folder, and it worked. ONCE. Then after that it didn't, so I was sure the wifi is dead.

Thanks for posting this, I'll try it, even if I doesn't solve it, at least I know it's SOFTWARE :D :good:
[Moto G Android Development] ChristianWS:
I'm not advocating for a removal of features, but I think it could lock messing uncommon partitions with a big warning or something. Like, "this zip is going to mess with weird stuff, are you sure you know what you're doing?".

Like, this partition isn't even part of a backup procedure, this doesn't even exist as part of the "Stock Firmware", and that included Radio.

After what happened here I wonder how many phones were thought to have hardware issues, that could have been solved if the backup process was more throughly. It looked like hardware failure because it sticked no matter the ROM, and I really doubt TWRP would have done a backup of that partition. I was even considering buying a new phone if the hardware guy couldn't find something on the Wifi antenna because I was starting to give up.

I doubt it, otherwise it would be rewritten correctly whenever you flashed system, right?

Please report back later, I wanted to do more tests, like how you should write the file, but I'm too scared of breaking it again.

You can use B variant and flash a separate Patched PlayStore, that way you just install the PlayStore a d nothing else. My xt1033 works better with this setup than with a A Variant with Gapps
[Moto G Android Development] MSe1969:
First of all, thanks for finding a solution and posting here - I think we all have learned something new.

To conclude the TWRP discussion (I am obviously not part of the TWRP team and thus can only express my own opinion): Whilst I fully understand your frustration about what has happened, if you look how the installer script works, you will see that ANY command here is potentially harmful and taking also into consideration, that many devices in fact have additional commands here to do some specific stuff, this is difficult to implement...

The B variant delivers AuroraStore, so a patched PS in fact is only needed for very specific purposes. I have no insight to this, but has this patched PS been patched in a way to prevent the usual silent and unannounced "self-updates" of the PS itself and the Google Spy services? (e.g. an attempt to "upgrade" microG to the latest version of the Spy-services wouldn't be desirable...)
[Moto G Android Development] ChristianWS:
I feel like a warning would be a good start, it would force devs to at least explain why it need to flash weird partitions.

IMO, at the very least TWRP should have the option to backup weird partitions.

Just to end this nightmare:

While searching for a solution I've found tutorials that touched on fixing files inside /persist, one of those tutorials mentioned a folder inside it, that doesn't exist on my phone. Could anyone look in their phones and see what is inside /persist? Preferably if it's a XT1033

I'm using it, not as a way to remove Google, but to free more resources on my device. It runs better this way than with Pico Gapps, I don't think Google can reinstall everything back with the patched PlayStore(which I use due to in app purchases), since a couple of tasker things are broken due to a lack of Google Services implementation.

Also, I was reading the thread and found the above issue, the user reported most of the same things that happened when my user profile got corrupted, at the time I thought it was due to a lack of space since it happened after the phone rebooted while it was almost full.
[Moto G Android Development] KElNT:
Moto G 2013 xt 1032 8gb

Hi man! i installed the 2 versions but i couldn't install apks.

The TWRP has bugged, i had to install the image every time I installed a new rom.
[Moto G Android Development] MSe1969:
Could you please provide details, what you exactly did and how you have installed the ROM? Your description isn't clear, and what you say hasn't been reported by others (and there are quite some downloads)
[Moto G Android Development] KElNT:
Moto G 2013 xt 1032 8gb

Sry I have my device on Spanish. The device tell me that i need an external sd memory to install the apk (chrome, whatsapp, etc).

A:

1-Recovery twrp

2-Wipe Data, Cache, System... etc (less internal storage)

3-Install img twrp cause the error "7"

4-Install the rom A

5-intall pico gapps

6-Wipe normal cache

(i will prove other gapps )

B: Same but without point 5

I will prove install playstore apk only, cristian recommended me

Sry for my English :S

---------- Post added at 07:18 PM ---------- Previous post was at 07:05 PM ----------

Hi Cristian! i can't install playstore https://xdaforums.com/android/apps-games/apk-google-play-store-8-7-50-t3742256

it same me that the pack is on conflict with other existence pack that has the same name

(Solved) I installed bean gapps on B rom and it did't found, but i proved bean gapps on A rom and gz!

1) Entry recovery mod (TWRP)

2) Wipe all

3) Install the last image TWRP cause error "7"

4) Install A rom

5) install Bean Gapps https://xdaforums.com/android/software/gapps-dynamic-gapps-t3487192

6) wipe data cache and reboot system

7) if you have little storage space, try entry recovery and wipe data again
[Moto G Android Development] MSe1969:
You must not install the play store apk as "update" over the FakeStore, which is delivered with the variant B.

Instead, you need to delete the file /system/priv-app/FakeStore/FakeStore.apk and the FakeStore directory.

Afterwards, assuming your apk is named PhoneSky.apk, you need to copy it into /system/priv-app/PhoneSky/PhoneSky.apk - do that from TWRP
[Moto G Android Development] MSe1969:
I spotted two things:

1. Error 7

What is your exact device model? I mean the XT number (remove the back cover to see it)

Which TWRP do you use? From where did you download it? Which version number?

When exactly occurs the Error 7?

2. No sdcard

Can you check (e.g. in TWRP root shell), whether you have a symlink called /sdcard and whether that points to a valid target, sth. like /storage/emulated/0

As indicated before, don't have my falcon device here, so don't remember, could also be something with storage and legacy.

If not, your issue will be solved, when you restore it.

To all reading: please check and report the exact target of the /sdcard symlink - thanks
[Moto G Android Development] burzutto:
Hello,

First thanks for all the work. This rom is fantastic, finally I can use my old phone which would otherwise have become obsolete.

I installed variant B on my XT1032 and everything went smooth (unlocked bootloader, updated bootloader, installed TWRP, wiped as per instructions and installed B variant).

The only issue I'm having is with Whatsapp notifications (installed from Aurora store).

For some reason I do not receive messages as they arrive but just all at the same time when I unlock the phone screen.

I have tried to set WA notifications to highest priority and set to interrupt even on lock screen and when do not disturb is selected, but to no avail.

Any idea what could this be?

Many thanks in advance.
[Moto G Android Development] Scranalot:
via adb:

falcon:/ # ls -lh sdcard
lrwxrwxrwx 1 root root 21 1970-01-01 01:00 sdcard -> /storage/self/primary

Then:

falcon:/ # ls -lh /storage/self/primary
lrwxrwxrwx 1 root root 19 1970-05-20 16:15 /storage/self/primary -> /mnt/user/0/primary

And then:

falcon:/ # ls -lh /mnt/user/0/primary
lrwxrwxrwx 1 root root 19 2020-07-25 15:48 /mnt/user/0/primary -> /storage/emulated/0

HTH ;)
[Moto G Android Development] KElNT:
Moto G 2013 xt 1032 8gb

1: model: xt1032

TWRP 3.4.0 from original page https://dl.twrp.me/falcon/twrp-3.4.0-0-falcon.img.html

error 7: I don't now exactly but i found this problem on google and solve it installing img of my twrp

2. I don't have sdcard slot, my device only has internal storage

Option A is work with bean gapps
[Moto G Android Development] MSe1969:
Regarding TWRP - have you tried to use an older version (see also discussion, when you scroll back), e.g. 3.2.1 ?

Indeed, the /sdcard symlink points to the Internal memory in Android, also for devices having an external SD slot.

The link to an external SD, which however is not present in the XT1032, would be /external_sd.

Therefore I repeat my question: Does that /sdcard link work on your device?
[Moto G Android Development] Scranalot:
1. As MSe1969 states - try using TWRP v 3.2.1 - I know it is an older version of TWRP but works fine for these older Falcon phones with this ROM, which has an older base, (though MSe1969 keeps it up to date with his developement).

This earlier explanation by MSe1969 might help:

I have 2 Moto G Falcons, an XT1032 & an XT1033. Some time ago I updated my TWRP to v.3.3.0 on both but because of this reason, just above, I downgraded to v.3.2.1 - having said that I don't recall having any issue using either TWRP version.

2. There are no sdcard slots in any Moto G Falcon phone as far as I'm aware - only internal storage.

I think the message:

Is basically TWRP reporting back that he has insufficient space on his internal storage to install these apps. This is always going to be a problem with 8GB storage.

I have the 'B' variant installed on both my Falcons & on their own they take up about

******* This misleading *******

6GB

******* Please see here: *******

https://xdaforums.com/showpost.php?p=83238085&postcount=447

but I am fortunate the both of my devices have 16GB.

Finally KElNT regarding:

Connect your PC/laptop to your device via adb

Then access the phones shell:

adb shell

then issue the commands below see if they produce the same results:
[Moto G Android Development] leolap84:
Same problem

Hi, I am having exactly the same problem you had, with the same MAC addres shown... so I think there is something in this particular rom that is messing up the wifi when installed... anyway I am trying to solve the problem but I can not fint the /persist folder.

I am trying to find it using the file explorer in TWRP, but without succes. Can you please explain what you did exactly? thanks
[Moto G Android Development] ChristianWS:
I know you fixed, sorry for the delay, but if you're interested in it, I download the patched play store here

I flashed Magisk and installed an apk of a Root Explorer from some questionable sources
[Moto G Android Development] vegenbe:
It worked the first time then went back to not working, I can't really understand, the first time I did this it worked for a day... But it seems fixable, the first time I fixed it by messing with the profiles and that worked for a few days only so go figure...

[data]

[lost+found]

[properties]

[prov]

.bt_nv.bin

WCNSS_qcom_wlan_factory_nv.bin

You need to root the device to access the system files.
[Moto G Android Development] rahlzel:
Confirmed: DO NOT use the latest TWRP versions to flash these ROMs.

When I used TWRP v3.4.0 (latest version as of this postdate for Moto G Falcon) it gave the error "Error E1001: Failed to update system image"

Flashing TWRP v3.2.1 as noted in OP's instructions is the fix.

On a side note, I couldn't get my added Google account to sync when using Variant B, so therefore couldn't use Google Voice, GMail, Contacts, etc. Variant A seems to be working well, though. I'm sure I'm not well enough acquainted with MicroG or something else on my end, assuming it is possible.

Thanks for this.
[Moto G Android Development] MSe1969:
microG is intended to make (non-Google) apps with Google dependencies work, and thus targets data privacy oriented people, who focus on alternatives to the Google Eco system. Kind of a compromise, to use certain parts of the G* infrastructure without having to use their spyware on your device.

However, if you really would like to stick to the Google Eco system itself with your Google account (GMail, Google Voice, Contacts, ...), you should use the genuine Gapps with variant A.

The site shadow53.com (in general worth reading) e.g. shows some ways how to even integrate genuine Google apps with microG, but it also focuses on alternatives.
[Moto G Android Development] rahlzel:
Yeah, I use Google with everything except my top level security concerns. Everything else - Contacts, mail, Drive, Maps, etc. - I've been ingrained in Google for years. Sounds like option A was better for me.

And thank you for the detailed instructions. I don't do this often enough to follow other ROM posts with 3 or 4 steps and that's it. You actually took the time to explain all the important stuff.
[Moto G Android Development] peelie:
hope not stepping bounds by asking about another OS but has anyone tried the e project? https://e.foundation/get-support/

thanks
[Moto G Android Development] MSe1969:
If you would like to try out /e/, just go for it - but that's really off-topic in regards to this thread.
[Moto G Android Development] peelie:
hi thx for response, it is still beta, and don't think it is as good as this rom;

just curious to see if anyone took plunge with it : )
[Moto G Android Development] ChrisRM:
/e/

Looked at it after the previous post but nothing leapt out as significantly better than this ROM. So, didn't feel like messing my falcon about for little gain.
[Moto G Android Development] phpbb3:
Nice!

After reading the last few pages of this thread I have been able to revert back to my original microg configuration while still maintaining my Plex app licensing through a patched playstore.

So happy to be able to trim the fat back off this device as the app licensing was my only reason for switching to gapps in the first place for this phone.

It truly is incredible how much of a difference there is in loading times and UI snappiness without Google fat in the way.

Thanks folks for your contributions.
[Moto G Android Development] phpbb3:
New screenshots. Note that the storage is with a full compressed twrp backup also on local storage.

PS mail me your 16gb xt1034 ;)
[Moto G Android Development] MSe1969:
New builds with August 2020 ASB patches

Hi all,

new builds are up with Sec. string 2020-08-05 and updated webviews to M84 - they will soon be offered as OTA, too:

A. Default LineageOS 14.1 with substratum and microG patch

https://sourceforge.net/projects/li...1-20200808-UNOFFICIAL-oms-falcon.zip/download

B. Hardened build with pre-installed microG and F-Droid, patched for substratum

https://sourceforge.net/projects/li...0200807-UNOFFICIAL-mG-oms-falcon.zip/download

Happy flashing!

Regards, M.
[Moto G Android Development] Scranalot:
I don't know if this comment was directed towards me as I have XT1032 & XT1033 - but they are both 16 GB & I had been posting in the previous 2 pages - specifically about:

Prompted by reading your post I looked again at my devices & what I had posted & have come to the conclusion that it is misleading - so apologies to all concerned & I will amend my previous post to reflect this.

Here is pictorial view of what is available & consumed in storage on my daily driver - its fairly self explanatory but as a guess I would suggest that as a fresh base install with just the ROM apps is probably in the order of about 2 GB & not 6 GB - again apologies if I have mislead anybody :o:
[Moto G Android Development] Scranalot:
Cheers

Thanks once again for the latest update :good:
[Moto G Android Development] PhillipJC:
Thank you for new build. :)
[Moto G Android Development] seawoofer:
Snapdragon's DSP, the Hexagon, within which CheckPoint Security has found over 400 different flaws.

DEF CON Safe Mode - Slava Makkaveev - Pwn2Own Qualcomm Compute DSP for Fun and Profit
[Moto G Android Development] phpbb3:
Hahaha thanks for your in-depth look but nope I was not talking to you specifically, but rather plugging that I am looking for a 16gb var and if anyone wants to mail me their old one on the cheap they should let me know maybe we can strike a deal.

Still lots of space on the 8gb var if, like me, your device install is purpose-driven as a tool and not an all-capable device.
[Moto G Android Development] Scranalot:
No not looking to sell at the moment - I actually went & specifically bought a second falcon over a year ago for 2 reasons - dual-sim because some areas I go to have poor coverage for my main carrier & as a backup in case this one packs up. Well you prompted me to set things straight on here anyroad ;)
[Moto G Android Development] lapikaki:
sorry for ask, but can you make a rom like this for the moto x play? :confused:
[Moto G Android Development] MSe1969:
I only build for devices, which I own (or at least have physical access to)
[Moto G Android Development] MSe1969:
Hi,

not sure, what your intention was to post this link, found it very interesting, but got aware already otherwise...

- Make forum participants aware? => Security interested people got already aware from many sources...

- Want to know how bad it is? => Some of the flaws require to install a bad apk, others could even be triggered by simply playing a crafted video file, so pretty bad!

- Want to know, whether this device is affected in particular? => I'd say yes, because it uses a Qualcomm SoC

- Want to know, whether I can do something about it when providing the next builds? => I can only watch out for what is going on in general and how mitigations would find their way into ROMs... Based on that, there may or may not be options...

As in fact, driver updates would have to come from QC, who usually don't care too much about their non-current products (as their customers are supposed to always buy their new stuff to maintain or increase the board of directors' bonus levels), I am not too optimistic about the whole situation.

:(

As long as there is no pressure coming from device manufacturers (*haha*, they also want you to buy their newest stuff, so even wondering whether they have the audacity to advertising this in favor of their newest device generations) or political pressure (QC is *American* and not e.g. Chinese or Russian...), well - judge yourself...

EDIT: Not blaming you for posting the link, just telling you all my thoughts.
[Moto G Android Development] seawoofer:
Yes, my intention was to know these things.

Thankyou very much..