yashsingh1/xdaforums huggingface dataset:
[Moto E4 (Qualcomm) ROMs, Kernels, Recoveries, & Ot] AesopRock127:
This ROM is now working perfectly on my metropcs xt1765. The only issues I'm having are even though I flashed the optional no verity zip magisk still claims me to be encrypted and tries to preserve force encryption and therefore I am failing safetynet check for both. Also my visual voicemail was not working so to fix it I wanted to reflash to stock for a bit to backup the stock VV app and the flash my backup of this ROM install VISUAL voicemail and apply the backup from the stock app. for whatever reason I have tried many many different stock ROMs from this website and others and they ALL say the zip is corrupted and the install fails. This may not be due to the RR ROM or more likely its my amateurish install. But I can flash backups just fine I can't figure put how to get back to stock. Any ideas on either of those anyone?

And by amateurish install because of my issues with twrp I had trouble installing by the OP's instructions. Twrp wouldn't flash through fastboot I could only boot to it temporarily and then I couldn't save a backup or flash any zips excepy for this ROM because they would fail and hang on updating partitions.... So I'm guessing because of the encryption and the fact I was booted into twrp instead of a flashed version of twrp it caused those issues. But since this ROM worked perfectly I was able to open up this ROM and download flashify and use that app to flash twrp an optional no verity zip and installed gapps through gapps updater I got off google and then I was able yo use twrp to create a nanodroid backup and flash things successfully through twrp so that's what I mean by amateurish install..... That's why I want to specify I think the issues I'm experiencing are NOT common to this ROM although I can't be sure. All in all, great ROM, love the customization available on the setting menu

EDIT: I know this is already really long and I apologize but I had a lot to say and its possible I could help someone who is having trouble and is patient enough to read tthrough my rantings but.... I really think the video fix zip on pg 2 post 12 by KyleBryant should be posted on the OP because otherwise videos don't work..... At least they didn't for me and this zip quickly and easily fixed it....

FURTHER EDIT: And now I see a post on the same page also by KyleBryant that seems like it might fix my safetynet issue.... Hmm trying now.
[Moto E4 (Qualcomm) ROMs, Kernels, Recoveries, & Ot] madbat99:
You have to format data to remove prior encryption. And not just wipe, format.
[Moto E4 (Qualcomm) ROMs, Kernels, Recoveries, & Ot] AesopRock127:
Thank you for your quick reply. I understand that that makes sense for you to say to me, it is good advice, however, I am not a total newbie, I tried this and it was also one of the things that hung on updating partitions. I tried wipe, advanced wipe, and format. All would hang on updating partitions and I would need to reboot after this and there would be no change.
[Moto E4 (Qualcomm) ROMs, Kernels, Recoveries, & Ot] madbat99:
Did you try putting the TWRP image on your SD card and, while booted into TWRP, select install, then install image, and select the twrp.img and the recovery partition to flash it to. Then see if it sticks that way.
[Moto E4 (Qualcomm) ROMs, Kernels, Recoveries, & Ot] AesopRock127:
So my issue is long over. in case I wasn't clear I solved this stuff, just was wondering if my 2 actual complaints were due to my install method or the ROM.

I did try what you said but it hung at updating partition. for some reason I wasn't able to flash directly from twrp had to use flashify to flash twrp before I could effectively use twrp. Booting it seemed to just make everything stop at updating partitions.....
[Moto E4 (Qualcomm) ROMs, Kernels, Recoveries, & Ot] madbat99:
I forgot you said you got it flashed with Flashify. But if you flashed no Verity opt encrypt or magisk after formatting data you should not have been encrypted.
[Moto E4 (Qualcomm) ROMs, Kernels, Recoveries, & Ot] sidgallup:
What version of GAPPS should i dowload? ARM, ARM64, X86, X86-64?
[Moto E4 (Qualcomm) ROMs, Kernels, Recoveries, & Ot] HigherStateD:
ARM
[Moto E4 (Qualcomm) ROMs, Kernels, Recoveries, & Ot] sidgallup:
Installed this on a Boost Moto e4, everything works fine EXCEPT voice calls, whenever i make or receive a call i cant hear anything, dead silent on both ends. Tested mic and ear piece with a Whatsapp voice message and both work fine.

Any ideas on what could be the problem?
[Moto E4 (Qualcomm) ROMs, Kernels, Recoveries, & Ot] HigherStateD:
Apn settings maybe? Just a guess
[Moto E4 (Qualcomm) ROMs, Kernels, Recoveries, & Ot] skullkid383:
Look here https://xdaforums.com/moto-e4/moto-...rom-resurrection-remix-moto-e4-t3689903/page2
[Moto E4 (Qualcomm) ROMs, Kernels, Recoveries, & Ot] sidgallup:
You mean the audiofix.zip file right? I think i know what happnened, i flashed the very first release, i didnt notice the list was in incremental versions from top to bottom, LOL. Il just dirty flash the latest build then, Thanks for your help.
[Moto E4 (Qualcomm) ROMs, Kernels, Recoveries, & Ot] skullkid383:
Yes I was meaning audio fix
[Moto E4 (Qualcomm) ROMs, Kernels, Recoveries, & Ot] CrazzyGamma:
I flashed this rom to my phone last night i am just wondering if anyone can tell me if there is any new updates and if so can you please provide me with a link
[Moto E4 (Qualcomm) ROMs, Kernels, Recoveries, & Ot] HigherStateD:
Latest update is in the first post. It's from January I believe.
[Moto E4 (Qualcomm) ROMs, Kernels, Recoveries, & Ot] CrazzyGamma:
all i see on the first post is

Created 2017-10-16

Last Updated 2017-10-21

nothing released this year everything is showing 2017

---------- Post added at 12:55 AM ---------- Previous post was at 12:51 AM ----------

i flashed the last one shown here or did i flash an older one by mistake https://androidfilehost.com/?w=files&flid=223811
[Moto E4 (Qualcomm) ROMs, Kernels, Recoveries, & Ot] HigherStateD:
On the ROM download link, the latest file is 12062017
[Moto E4 (Qualcomm) ROMs, Kernels, Recoveries, & Ot] Zsheoran:
LTE Works?
[Moto E4 (Qualcomm) ROMs, Kernels, Recoveries, & Ot] HigherStateD:
Yes, but not at full speed.
[Moto E4 (Qualcomm) ROMs, Kernels, Recoveries, & Ot] crimsonrommer:
link is gone
[Moto E4 (Qualcomm) ROMs, Kernels, Recoveries, & Ot] Dr_Wolodya:
"not found" on ROM link from first post. Anyone have other links?
[Moto E4 (Qualcomm) ROMs, Kernels, Recoveries, & Ot] madbat99:
Try the searching "woods" on androidfilehost. Might find something.
[Moto E4 (Qualcomm) ROMs, Kernels, Recoveries, & Ot] Dr_Wolodya:
Woods - is mtk-version of E4. So, I will try to find - perry (qualcomm-based version).
[Moto E4 (Qualcomm) ROMs, Kernels, Recoveries, & Ot] madbat99:
Oh, Carlos built for mtk. I thought This one is for woods. Bad memory dude, sorry. If you want Perry, check here

Or the Moto e4 telegram group.

Releases are here

Moto E4 Releases

Updated and *working* ROM and custom kernel releases for 'perry'

https://t.me/E4Releases
[Moto E4 (Qualcomm) ROMs, Kernels, Recoveries, & Ot] sidgallup:
Anyone has a link for the latest release? i messed up my phone and need to do fresh install, link on first post says its deleted from server... thanks
[Moto E4 (Qualcomm) ROMs, Kernels, Recoveries, & Ot] RebelLion_:
https://androidforums.com/threads/r...ction-remix-v7-1-2-for-moto-e4-perry.1290953/
[Moto E4 (Qualcomm) ROMs, Kernels, Recoveries, & Ot] smartech:
any luck with the network carrier?

is this rom unlocks the network carrier?

---------- Post added at 06:01 PM ---------- Previous post was at 05:53 PM ----------

I have the moto E4 xt1765 metropcs version , there is no to much info about this device, it has the qualcomm cpu, I install the LineageOS 14 v. but I cant get the sim card work, is it posible with this rom get the network carrier work on this device?

by the way the download link is dead:(
[Moto G5 Guides, News, & Discussion] infixremix:
I'd like to say thanks to the live chat for this info

This is pretty much a fail safe recovery

If this fails we have no luck till blank flash

1. Make sure the phone is plugged into a wall charger

2. Press and hold the VOL DOWN key

3. While still holding the VOL DOWN key, press and hold the POWER key

4. Hold both keys down for over 120 seconds. This is more than 2 minutes and will seem like a long time, it will help to time this to ensure the customer holds the keys long enough. Note, it must be more than 2 minutes!

5. After holding the keys down for more than two minutes, release the POWERkey first and then release the VOL DOWN key a few seconds later.

6. The Fastboot screen will display, and the Normal Reboot option will be highlighted

7. Press the VOL UP key and the device will reboot normally or go into fastboot
[Moto G5 Guides, News, & Discussion] CypherPotato:
Working for you? Plz reply
[Moto G5 Guides, News, & Discussion] AcciolyF:
Did it work for u? Reply
[Moto G5 Guides, News, & Discussion] infixremix:
Can you test if u have this problem
[Moto G5 Guides, News, & Discussion] infixremix:
I haven't tested its what they do to fix some hard bricked devices
[Moto G5 Guides, News, & Discussion] AcciolyF:
Not really, my device isn't even recognized by my notebook system. :(
[Moto G5 Guides, News, & Discussion] infixremix:
Do this it should take u to recovery
[Moto G5 Guides, News, & Discussion] Yukyud:
dont work dude i trie on my phone (moto g5)
[Moto G5 Guides, News, & Discussion] carlapazin:
not work for me too

i've tried in so many ways and the only way I can find my phone in my pc is qualcomm something 9008
[Moto G5 Guides, News, & Discussion] takoa:
This method does not work. I've tried five times and nothing.

Almost fifteen minutes pressing buttons.
[Moto G5 Guides, News, & Discussion] infixremix:
I'm here to help , not to be treated like a piece of dirt u can stamp on
[Moto G5 Guides, News, & Discussion] Exanneon:
If there is an issue with the actual bootloader such as it missing, then this method obviously won't work, you can't simply summon it if you don't have it.

If this is meant for booting one into recovery then it couldn't be done if for example the user had no recovery partition, and could not flash a recovery as their device is not recognised by another which had the ability to flash via fastboot.

Has there ever been an incident in which this method has worked?
[Moto G5 Guides, News, & Discussion] takoa:
I do not understand what you mean
[Android Q&A, Help & Troubleshooting] wacccim:
hi briefly i wanted to install a costum rom i didn t do a backup and wipe data and i remove everything but sadly the costum rom i wanted to install which is lineages didn t pass it gives me error 225 any help i have trwp installed as recovery i am using the one that i rooted my phone with the phone now without rom it's stucked in boot i can go to trwp or fastboot mode that s it won't shutdown what can i do to install rom

or backup the oficial rom

any suggestion hekp will be appreciated
[Sprint Samsung Galaxy S III] pravus87:
I can flash back to stock via the SkipSoft Unified Android Toolkit, but not matter how far back I go, the only 3rd party ROM that will not get stuck on a never-ending bootscreen after install is CM 11-20150831-SNAPSHOT-XNG3CAO3FN-d2lte. Not even the CM nightlies that came immediately before or after would work once this was installed.

I would like to try something newer if there is a stable Lollipop, Marshmallow, or Nougat ROM you would recommend. I don't use as a phone anymore, so I don't even need cellular data to work.

Thank you very much to anyone that even takes a look at this.

More info...

Model Number

1HZGY

Android version

4.4.4

Baseband version

L710VPUDOH1

Kernel version

3.4.104-cyanogenmod-g3652409

build04@cyanogenmod #1

Mon Aug 31 16:36:33 OCT 2015

Build number

cm_d2lte-userdebug 4.4.4 KTU84Q bdfbe2c9c2

test-keys

SELinux status

Enforcing
[Sprint Samsung Galaxy S III] madbat99:
This forum is for the Sprint S3, but I don't recognize your model number. Sprint is SPH-L710

If you do In fact have the Sprint model, I have many ROM suggestions. Including nougat ROMs. Also make sure you have the most up to date TWRP. Don't search d2lte anymore, they are no longer unified LTE builds. Sprint is d2spr, att is d2att, etc.
[Sprint Samsung Galaxy S III] pravus87:
It is definitely the sprint model. And I don't search for d2lte - I know that was a very short term thing for CM. Nothing else will flash and then boot though. Even tried using d2spr nightlies that were released after the 8/31/2015 d2lte snapshot.

I was using TWRP v3+ already but I used their official app to flash latest version, as per your advice. Now device only boots to download mode.

No worries as this is not my daily driver. I do hope to get it fixed, though.

Am I going to have to use the toolkit to flash stock and try again or is there a way to progress from here?
[Sprint Samsung Galaxy S III] madbat99:
Wow never seen that from installing TWRP. Do you have the triband model by chance?

I would try Odin back to stock and flash TWRP again. I usually get TWRP right from their site.

Are you wiping data and factory resetting (including internal storage) before trying to boot these ROMs? It is required for the newer ROMs. Octos has a good nougat build. Commotio is pretty solid too. I'm running lineage right now and it's perfect.

https://xdaforums.com/galaxy-s3-sprint/development/rom-octos-t3532535/post70408050

https://xdaforums.com/galaxy-s3-spr...samsung-galaxy-s3-vanir-t3006645/post58268135

https://download.lineageos.org/d2spr

https://dl.twrp.me/d2spr/
[Sprint Samsung Galaxy S III] pravus87:
That was a first for me too. TWRP has always been fairly easy to install and update.

Not sure if this is the triband but I assume that is more expensive and that it is not the standard model Sprint was pushing, so I doubt it. Is there a way for me to check?

Yes I was wiping data, cache, system and internal storage wit each install. I had an AT&T Samsung Galaxy S3 and an AT&T LG G3 that I did a lot of flashing on, so I am familiar with the basics. I tried flashing lineage and commotio recently with no luck and had to install the final CM11 snapshot again.

Will flash back to stock and will try again. If I recall, the final update is only OTA. Do I need to take it before moving on?

Thanks for your help!
[Sprint Samsung Galaxy S III] madbat99:
Shouldn't need all updates, but it's not a bad idea. If the model has a "t" on the end then it's a triband. That one can be troublesome.
[Sprint Samsung Galaxy S III] pravus87:
Sorry for the delay. I had some issues restoring stock with one PC and was too stubborn to try on a different PC until yesterday.

Was able to get stock working, rooted and I installed TWRP 2.7.x and then updated to the latest (3.1.x). I then wiped all partitions from TWRP and sideload installed latest Commotio and opengapps. Same issue - stuck on the boot screen (animated water).

Anything left to try? Confirmed it is not the triband. Thanks again.

UPDATE: just tested with latest CarbonROM. Issue persists :(
[Sprint Samsung Galaxy S III] madbat99:
I've been stuck on boot animation on a few fresh installs of ROMs. If I let it sit there for 5 mins or so then hold power until it reboots, it usually boots up. Where KitKat ROMs used to say building dalvik cache, or whatever the particular ROM had, newer nougat ROMs do not. The boot animation plays while it establishes art caches. It can take awhile on a fresh install.
[Sprint Samsung Galaxy S III] pravus87:
Tried flashing Commotio again and held down power to reboot after about 5min on boot screen. Waited over 10 mins the second time and still no luck. Just reboot again and will give it until the battery dies. Let me know if you have any other suggestions. Thanks again.

UPDATE: Tried with latest CarbonROM and latest LineageOS builds as well. None will boot. Old CM11 snapshot build still installs and boots without issue.
[Sprint Samsung Galaxy S III] madbat99:
Have you formatted data? Switching between KitKat and nougat you have to wipe internal storage.

I would "format data" not just wipe (in case of any encryption) and also do a factory reset in recovery.
[Sprint Samsung Galaxy S III] pravus87:
Yes - I have wiped everything, including internal storage and used the "format data" option. I have tried ADB sideloading each of the ROMs mentioned with everything wiped. I've also tried removing the external SD card, copying the ROMs to it from a PC, reinserting into the phone and attempting install that way. Still, no luck.
[Sprint Samsung Galaxy S III] madbat99:
Wow, that is thorough. Maybe make sure non of your ROM or gapps packages are corrupt (check md5 or sha1, etc.)

What gapps are you using? I usually use open gapps for 7.1x arm, mini or micro. Beans gapps also work well. Just make sure they are for 7.1.

Maybe try to boot the ROM without gapps ( just a shot in the dark). Are you flashing any other mods with it? I think Commotio comes rooted with magisk.
[Sprint Samsung Galaxy S III] pravus87:
I have tried with 7.0 and 7.1 opengapps arm pico but I haven't been doing so during troubleshooting so as to isolate the issue. I tried once with Commotio and once with CarbonROM in case they needed it for some reason, but since no luck, I figure I'll wait to flash gapps once I get a successful boot.

I downloaded all ROMs with Free Download Manager, which does a pretty good job at maintaining file integrity and working through connection hangups, but I will try downloading with Firefox by itself and verifying the checksums to be sure. Will get back to you - thanks again.
[Sprint Samsung Galaxy S III] madbat99:
Happy to help
[Sprint Samsung Galaxy S III] pravus87:
I downloaded Commotio and CarbonROM again and verified the md5s. All good there. I wiped everything except OTG again and tried installing from the SD card (formatted as well before the ROMs were copied over). Still stuck on boot animations. I attempt a power button restart after about 10mins a couple times then I let it sit for 30+min without any success.

Hope we haven't reached the end of the line yet. I'm very curious about what could be causing this.
[Sprint Samsung Galaxy S III] madbat99:
Well I'm stumped. Have you tried LineageOS? These ROMs are all based on Lineage. Sometimes there is a bad nightly that refuses to clean flash and it spreads to all other ROMs. Maybe try a build from a few weeks back (or even a month if you can find one) and if that boots then you can update to the newest with a dirty flash.

I see you did try LineageOS and tried some older builds.

Well, I can maybe make a backup of a fresh install after first boot and upload it for you. You can try restoring it on your phone and see if it boots. You would have to have the folders created on your phone (or external sd card). Like

"TWRP/backups/* your phones serial number*/*name of backup*"

Obviously without the quotes and stars and with your devices actual serial number. Only thing is, backups are pretty big files.
[Sprint Samsung Galaxy S III] pravus87:
I did not try Lineage or Vanir again like I did Commotio and CarbonROM to verify the md5s. I will try them and some older builds of each.

I sincerely appreciate the offer. I would certainly be willing to download a large backup if you would be willing to take the time to clean install and upload. Let me try the remaining steps you listed first, though. Don't want you to have to spend time doing all that if we can get it working another way.

Thanks again. Will keep you posted!
[Sprint Samsung Galaxy S III] pravus87:
Downloaded, verified and copied all these files to a freshly formatted SD card, inserted into the phone, booted TWRP 3.1.1-0 and wiped Dalvik / ART Cache, System, Data, Internal Storage, and Cache before each install:

B140-commotio-d2spr-10-17-2017.zip

CARBON-CR-5.1-MOO-RELEASE-d2spr-20171018-0000.zip

cm-11-20150831-SNAPSHOT-XNG3CAO3FN-d2lte.zip

cm-12.1-20151117-SNAPSHOT-YOG7DAO1K7-d2spr.zip

lineage-14.1-20170731-nightly-d2spr-signed.zip

lineage-14.1-20171030-nightly-d2spr-signed.zip

OCT-N-WEEKLY-20170811-2058-d2spr.zip

vanir_d2spr_5.1.1.102615.zip

vanir_d2spr_6.0.122916.zip

vanir_d2spr_7.0.010417.zip

vanir_d2spr_7.1.101817.zip

Only ol' reliable (CM 11 d2lte 8/31/15 snapshot) will boot.

This phone was fully updated with all OTA updates before I ever attempted to root, install a custom recovery or ROM about a year or so ago. I remember having issues even then, not being able to get any CM version to boot except for that one, which was already old at the time.

For kicks, I tried dirty flashing the CM 12 d2spr 11/17/15 snapshot over ol' reliable in hopes that it would boot and I would be able to dirty flash all the way to an Oreo build. It didn't work.

Also, each time I have flashed back to stock to retry, I have used the *NJ2 build.

Not sure if any of that matters, but trying to think of anything that may help pinpoint the issue.

If no other ideas, I would like to take you up on your offer and try a TWRP backup of a fresh install of any recent, stable ROM from you device, if you would be so kind to upload.

Thanks again for the help. For what it is worth, it has been fun troubleshooting this. I'm too afraid to do anything with my S8, but miss the fun I had with my AT&T S3 (never had any issues with custom ROMs, but I also didn't take all the OTA updates) and my AT&T LG G3, which got blue screen disease.
[Sprint Samsung Galaxy S III] madbat99:
Mine is on nj2 as well. Mine takes a little while to boot, but not hours lol.

I'll see if I can backup a fresh build today. I won't be able to upload until tomorrow (no wifi at home right now). I can likely upload when I get to work, I get there pretty early. I'll pm you a link when it's done.

Really don't know why that's the only thing that will boot for you. It has been fun trying to get it to though.

I'll flash LineageOS (most recent) with open gapps mini. I'll boot to the setup wizard and then make a backup. Hope this works, mostly cause I'm kinda out of ideas, lol.
[Sprint Samsung Galaxy S III] pravus87:
Thank you. No rush - whenever you have time.

I don't get it either. I waited a long time to post about it because I assumed there was something simple I was overlooking that I would eventually figure out. Not sure this will work if nothing else has, but I can't wait to give it a shot.
[Sprint Samsung Galaxy S III] madbat99:
I have a fresh backup made. Just booted to LineageOS setup wizard start screen and booted back to recovery for full backup. Named it cup_of_sugar with the date. Flashed it with open gapps mini.

Don't forget the folder structure (so TWRP will find it for restore). TWRP/BACKUPS/serial number/name of backup

You can make a backup of something small (like cache) on external sd and TWRP will create the folders for you. Then just delete that backup (last folder only) and drop this one in.

I'll upload it to Dropbox tomorrow morning. Probably around 6:45 a.m. central time. Depending on how long it takes to upload.

I hope this works.

Fingers crossed :cool:
[Sprint Samsung Galaxy S III] madbat99:
Pm sent with link
[Sprint Samsung Galaxy S III] pravus87:
Thanks for sharing this so quickly. The restore was successful, but can't get passed the boot animation. :crying:

Held down power to reboot after about 10 minutes with no luck the second time.

If you think of anything else, please let me know. For now, I'll assume the phone will die with ol' reliable on it. Thanks for everything. :highfive:
[Sprint Samsung Galaxy S III] madbat99:
Wtf. Dang it. I really thought that would do it. There has to be something going on with that I got to figure this out
[Sprint Samsung Galaxy S III] pravus87:
Well, I certainly wasn't going to stop trying, but I figured it was time to let you move on to other wayward users. :D

Any idea what is different about that d2lte build that would allow it to boot when no d2spr released before or after it will?
[Sprint Samsung Galaxy S III] pravus87:
Well, I certainly wasn't going to stop trying, but I figured it was time to let you move on to other wayward users. :D

Any idea what is different about that d2lte build that would make it boot when no d2spr ROM released before or after it will?