yashsingh1/xdaforums huggingface dataset:
[Moto G4 Plus Questions & Answers] mel2000:
Finally updated to the June 2017 patch.

Am now updated to NPJ25.93-14.5

ElementalX kernel was still installed afterwards

All apps still installed altho some not working right

Root no longer installed

WiFi does not stay in ON position, cannot connect

Still only able to boot to system only via TWRP-> Bootloader->Start button

Tried updating to Magisk-v14.0.zip via TWRP

Encountered "please restore stock boot image" message

Restored boot saved from original TWRP install

Magisk-v14.0.zip install via TWRP successful

Once again, my XT1644 phone will no longer boot to system, only TWRP. This time I can't even get to system via bootloader.

Any troubleshooting assistance appreciated. I am particularly concerned that ElementaX kernel did not need to be reinstalled and am wondering if the WiFi connect issue is related to that. However, first I need to be able to boot to system. Thanks.
[Moto G4 Plus Questions & Answers] strongst:
you had already NPJS25.93-14.8 and then flashed NPJS25.93-14.8 from that thread https://xdaforums.com/moto-g4-plus/how-to/amazon-prime-moto-g4-update-t3665900 is that right?

The security level is the same, but the version from the post above is for Amazon devices. How did you updated?
[Moto G4 Plus Questions & Answers] mel2000:
Sorry for the delayed response. Due to faults of my own, I was unable to complete the June 2017 update via TWRP so I need to start from scratch.

I never flashed the NPJS25.93-14.8. I was trying to flash NPJS25.93-14.5 firmware via TWRP and messed up when trying to flash Magisk with my original boot image. Now my phone won't boot out of TWRP even through the bootloader method.

So I'm at square one again. I need the NPJS25.93-14.5 firmware for flashing with the OEM Flash.bat script. However, the only XDA xt1644 firmware I can find points to "ATHENE_NPJS25.93-14-8_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip," which is for the Amazon variant.

Any assistance with locating the XT1644 retail June 2017 NPJ25.93-14.5 update firmware will be greatly appreciated. Thanks.
[Moto G4 Plus Questions & Answers] echo92:
Just to clarify, were you able to flash the NPJ25.93-14-5 TWRP flashable via TWRP, and got the boot loop when attempting to root via magisk? Are you still able to boot into TWRP recovery from the bootloader? You mentioned attempting to root with the stock kernel (rather than the ElementalX kernel) which might be the source of the boot failure.

If you're not able to access TWRP, then it sounds like you need the NPJS25.93-14-4 March 2017 firmware (the NPJS25.93-14-8 firmware is for retail, but it appears US devices are on a different update path). To the best of my knowledge, there is currently no NPJ25.93-14-5 firmware available. However, from what I've read, the march stock firmware wasn't flashed, only the TWRP flashable? If so, your bootloader and GPT should still be on the march patch level (as the TWRP backup only touches your system and boot kernel, and thus doesn't formally update your device to the latest patch level - for that, you'd need a completely stock device).

If the only updating that was done was flashing the TWRP flashable of NPJ25.93-14-5, then here's the link for the march 2017 firmware https://www.androidfilehost.com/?fid=889764386195899847

Of course, as mentioned before, this will remove TWRP, root and may wipe your device, so firstly I'd check to see if from the bootloader menu you can reboot to TWRP. In TWRP you can connect your device to your computer and copy over your key files.

I'd also suggest, if you're able to access TWRP if you can reflash the NPJ25.93-14-5 TWRP flashable and see if that lets you boot. You may have to wipe cache or data. Then, hopefully, you'll be able to root again using a custom kernel (after backing up the stock Motorola kernel).
[Moto G4 Plus Questions & Answers] mel2000:
Thanks for your prompt response echo92.

No continuous bootlooping, I just can't boot to system anymore, only TWRP.

I can only boot to TWRP. Bootloader reboot brings me back to TWRP.

All updating was done with ElementalX kernel intact.

I lost booting to system after I flashed Magisk. I had to swap the current boot.img for the original one in order for Magisk flash to proceed without error. After that "success" I can only boot into TWRP, not in to system. So for now I'm looking for the NPJ25.93-14-5 retail XT1644 firmware to flash via the OEM Flash.bat script. I want to start from scratch.
[Moto G4 Plus Questions & Answers] echo92:
Appreciate the replies, so it sounds like attempting to restore the NPJ25.93-14-5 backup in TWRP didn't work. Just to clarify, the process was:

Booted into TWRP

Wipe system, Dalvik, cache and data.

Restored the NPJ25.93-14-5 system (which should include the stock boot kernel, the one by hudsoncm) from the backup provided.

Rebooted?

As I mentioned previously, there currently is no NPJ25.93-14-5 firmware to flash - it's too new at the moment. However, since you used TWRP to attempt to flash the updated system, as I understand it, then your bootloader might still be at the March 2017 patch level (should be version B1:05 as reported in the bootloader screen). Thus, provided you didn't use the OTA to update (which I don't think you would have, as you've still had TWRP and ElementalX when updating, both of which would fail an OTA update, since stock OTA updates require a stock kernel, stock recovery and unmodified system to flash), you might still be able to revert back to the March 2017 NPJS25.93-14-4 firmware, then update to the June 2017 update.

A few things:

Flashing this firmware is assuming (at least from my point of view) that you did not revert back to the March 2017 stock firmware to flash the June OTA to your device, is that correct? If you did, please let us know before attempting to flash the March 2017 firmware.

The March 2017 firmware is, as I recall, universal for Moto G4/Plus devices, including your XT1644. Link here: https://www.androidfilehost.com/?fid=889764386195899847

You will need fastboot to flash the stock ROM, and as previously mentioned, this will wipe TWRP, root and may wipe your device, so back up and transfer your files off your device.

Once formally updated to the June 2017 update, be very careful until the stock NPJ25.93-14-5 firmware is leaked/released. I imagine you can still root but you'll need to make sure you take TWRP backups of your system and kernel before you root.
[Moto G4 Plus Questions & Answers] mel2000:
Thanks again for your reply echo92.

Correct, except that the phone showed that ElementalX was still intact. But the build was definitely NPJ25.93-14-5.

Is there a way to check my bootloader patch level via TWRP?

My first mistake was to attempt an OTA with my existing modified system. Afterwards, everything remained intact and the build was still NPJ25.93-14-4, but I was no longer able to boot seamlessly into the system mode. I always had to go through bootloader reboot to get to my system. I then tried the TWRP NPJ25.93-14-5 update, which appeared to work even though I didn't swap back to stock kernel or stock boot.img before doing the update. Afterwards I still had to boot into my system mode via the bootloader reboot. I only swapped boot.img to stock just before flashing Magisk zip. After that I was no longer able to boot into system mode.

My TWRP update flashed to the June build NPJS25.93-14-5. I'm willing to revert to the March build to start from scratch if possible.

I started the June firmware update with the original March firmware, which was already there upon purchase.

I appreciate your continued assistance.
[Moto G4 Plus Questions & Answers] mel2000:
That sounds right.

https://i.imgur.com/qx7VmMp.jpg

BL: B1.05 (sha-8a1de8c, 2017-02-15 15:53:47)

Baseband: M8952_70030.25.03.62R ATHENE_RETUSA_CUST

I used my current system's boot when applying the OTA. Afterwards I could no longer seamlessly boot into my system. Had to get there via bootloader reboot.

I didn't opt to use the stock kernel in TWRP before the OTA.

I restored stock boot from original Nandroid taken just after TWRP was installed, with no other phone modifications.

I'm quite willing to start from a pristine March build, then let the phone update to the June build. All before manually adding TWRP/ElementalX/Magisk + flash logo.bin, as I did before. I've checked that only Magisk needs updating to a newer version.

I'm assuming the March+June firmware updates will update the final firmware as needed. I've saved screenshots of everything and will let Google update apps etc.

That's my plan if you agree with my bootloader stats. Thanks again.
[Moto G4 Plus Questions & Answers] mel2000:
I made a Nandroid backup of my xt1644 just after installing TWRP. Original boot.img, no other mods than TWRP. No ElementalX, no logo.bin and no Magisk. Could restoring that backup take me to the condition where I could safely use the June OTA update?
[Moto G4 Plus Questions & Answers] echo92:
If TWRP was allowed to make modifications (during the firstly time TWRP was booted into), then no, restoring this backup may still mean OTA updates fail. I think the OTA detects if the system has been modified at any point, including if TWRP set read write access.

At any rate, you've got a custom logo.bin, which TWRP doesn't touch (you can see in the backup logo isn't listed), so an OTA would still fail. You could restore the back up, then flash the stock recovery and stock logo.bin from the fastboot ROM, but if the system was modified by TWRP, your have to reflash the system too.

Easiest way as I mentioned above, is to flash the March 2017 stock firmware. Your bootloader and system are at the March patch level, so you should be okay to flash then you'd be able to update. Of course, after you've updated to June, make a backup and discard your backups made on the march 2017 build to limit confusion.
[Moto G4 Plus Questions & Answers] mel2000:
OK, I'm going to download the March 2017 firmware and install it with the OEM Flash.bat script.

I notice that OEM Flash.bat script is the same as the script code you listed below with the exception of the following additional lines: 2 at the top, and 3 just before the reboot command.

fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img

fastboot erase userdata
fastboot erase customize
fastboot erase clogo

If there's any concern with those lines please let me know. Thanks.
[Moto G4 Plus Questions & Answers] echo92:
Shouldn't be a concern to omit those:

GPT and bootloader are the same build as what you will flash, so there's not much point to re flashing these positions. You can flash them if you wish to.

Erase userdata, as the command suggests, erases your data (don't know if it also wipes your internal storage), we're omitting this to keep your data, as I mentioned previously. However, if your device ends being unstable, you may have to factory reset (the equivalent of executing this command).

Erase customise and erase clogo are wiping custom additions made by Motorola at the factory, e.g if you requested to have your name put on the logo.

The only one you'd have to consider is the erase userdata, our original aim was to keep your data. However, if you've backed up and want a really clean slate, you may wish to include the command.

EDIT: just saw the NPJ25.93-14-5 update available for flashing. https://www.androidfilehost.com/?fid=673368273298984458 use the flashing script rather than the commands I have
[Moto G4 Plus Questions & Answers] mel2000:
Thanks for your prompt reply. I'm going to run the script without those five lines.

Is that NPJ25.93-14-5 update file the equivalent of the June OTA? If so, do I need to use the March 2017 firmware at all, or can I just use the file above? I'm just trying to be very very careful before I start the process.
[Moto G4 Plus Questions & Answers] echo92:
The update I linked is the full firmware (i.e needs to be flashed in fastboot and the bootloader), which needs to be flashed with the OEM flash script or full commands (including GPT and bootloader).

I downloaded it and the about file inside has the same build number as the OTA that you were receiving a notification about.

BUILD REQUEST INFO:
SW Version: athene-user 7.0 NPJ25.93-14.5 5 release-keysM8952_70030.25.03.64R
MBM Version: B1.06
Modem Version: M8952_70030.25.03.64R
FSG Version: FSG-8952-05.30.03
Build Fingerprint: motorola/athene/athene:7.0/NPJ25.93-14.5/5:user/release-keys

VERSION INFO FOUND UNDER 'ABOUT PHONE' SCREEN:
System Version: 25.231.5.athene.retail.en.US
Model number: Moto G (4)
Android Version: 7.0
Baseband Version: M8952_70030.25.03.64R
Build Number: athene-user 7.0 NPJ25.93-14.5 5 release-keys
Build Date: Thu Jul 20 03:28:39 CDT 2017

OTHER MISC VERSION INFO:
Subsidy Lock Config: slcf_rev_d_default_v1.0.nvm
Regulatory Info (eLabel): regulatory_info_default.png
Blur Version: Blur_Version.25.231.5.athene.retail.en.US
Version when read from CPV: athene-user 7.0 NPJ25.93-14.5 5 release-keys

However, I can't install it, though as you can see above it had the same bootloader version as the retail June 2017 build (B1:06).

If you're not confident about this update, then you can flash the March 2017 firmware (using the commands I mentioned), update via OTA then compare your bootloader and your baseband to the above info. If your updated device matches the info, suggesting this firmware and the OTA update are the same patch level, then I'd suggest downloading the NPJ25.93-14.5 update for reverting back to stock in future. Attempts to revert to the march 2017 firmware when you've formally updated via OTA may cause you issues otherwise.
[Moto G4 Plus Questions & Answers] mel2000:
Thanks so much for everything echo92. I'm going to directly fastboot NPJ25.93-14.5 as discussed.

EDIT: The NPJ25.93-14.5 June 2017 update was a complete success!!! I want to thank everyone for their precise and patient assistance with getting my phone updated and in full working order.

As expected, TWRP, ElementalX, unlocked bootlogo and Magisk will need to be reflashed, but I've done all that before. I'm relieved that my internal drive contents are intact. And yes, I plan on saving the NPJ25.93-14.5 update folder on my PC.
[Moto G4 Plus Questions & Answers] mel2000:
Everything is fine on the latest xt1644 June update but the phone freezes at the 'bootloader unlocked' screen.

Uninstalled Magisk Manager

Flashed Magisk uninstaller.zip

Flashed Magisk v14.zip

Wiped cache/Dalvik

Rebooted

Any troubleshooting help appreciated. Thanks.
[Moto G4 Plus Questions & Answers] echo92:
That's a normal error message, as TWRP isn't signed. Do you get an [OKAY] at some point, indicating the flag has occurred? If so, reboot directly back to recovery to fix TWRP (else the stock recovery will over write TWRP), TWRP should load up and then you should be able to reboot as normal.
[Moto G4 Plus Questions & Answers] mel2000:
Thanks again. I rebooted and all is fine (except for Magisk).
[HTC U11  Questions & Answers] dbGHOST:
Last night I realized that everything was blurred out in all apps using camera.

Haven't used camera since Aug. 25 so I'm not sure when did it start.

Tried the focus slide in Pro mode but nothing changes.

Currently on ViperU 1.7.0 with ElementalX 1.05.

Pretty much factor out the software issue by:

Dirty flash ViperU 1.7.0, clear cache only.

Full wipe then flash ViperU 1.7.0.

Flash RUU.

And everything I did since Aug. 25:

ElementalX 1.04 -> 1.05.

ViperU 1.6.0 -> 1.7.0, dirty flash, with EK 1.05 and ViPER4Android.

Sunshine 3.5.9, 1st test didn't go through so I close it, and 2nd one went through. Didn't S-OFF after that.

No dropping or touching liquid.

Reading, chatting, and surfing.

Guess I have to send it for warranty.

Even worse is I bought this one (DTWL) in China since the 128g version wasn't available here in US, so I need to send it to China.
[HTC U11  Questions & Answers] doyou37:
Try increasing/decreasing the exposure
[LeEco Le 2 Questions & Answers] cjcool_123:
best battery backup rom of nougat for x526 plsss suggest with all camera working?
[LeEco Le 2 Questions & Answers] sahil.kalka:
try mokee
[Zuk Z1 Q&A, Help & Troubleshooting] sjv3377:
The way video recorder record videos, the same video it shoots even while selecting slow motion 60 fps or 30 fps or any such settings.

Unable to use slow mo feature, is there any app or firmware update ? Help appreciated. Thanks!
[Zuk Z1 Q&A, Help & Troubleshooting] Dhruvshelke588:
Slo mo works for 1080p, 720p and lower resolutions.
[Zuk Z1 Q&A, Help & Troubleshooting] jai krishna:
Wrong section, read the forum rules before posting these kinda things.

......

Thread closed

.........
[Zuk Z1 Q&A, Help & Troubleshooting] surya ayrus:
Use footej camera app
[Zuk Z1 Q&A, Help & Troubleshooting] Dhruvshelke588:
Used it. No stabilization at any resolutions.
[Zuk Z1 Q&A, Help & Troubleshooting] surya ayrus:
Then try cm13 ROM I heard tats great in recording 4k video and slow motion video
[Samsung Galaxy J7 ROMs, Kernels, Recoveries, & Oth] parth111999:
Awesome Beginning [MENTION=8467616]smartass08[/MENTION]
[Samsung Galaxy J7 ROMs, Kernels, Recoveries, & Oth] Hassaan24:
Good work Bro
[Samsung Galaxy J7 ROMs, Kernels, Recoveries, & Oth] GraveDigger:
Awesome work mate! Hope this lagging will be fixed.
[Samsung Galaxy J7 ROMs, Kernels, Recoveries, & Oth] mbk999:
woowww

WeLcome nubzzz

Thanks for the rom
[Samsung Galaxy J7 ROMs, Kernels, Recoveries, & Oth] THAlmendra:
Good work bro, thanks
[Samsung Galaxy J7 ROMs, Kernels, Recoveries, & Oth] Oves786:
Owsome start to killll allll.

Nicw work mate........
[Samsung Galaxy J7 ROMs, Kernels, Recoveries, & Oth] suraj bagal:
Is it compatible with SM-J700F
[Samsung Galaxy J7 ROMs, Kernels, Recoveries, & Oth] Ruturaj Kadam:
Yes
[Samsung Galaxy J7 ROMs, Kernels, Recoveries, & Oth] rochakz:
nop

and dont expect it until magic happens
[Samsung Galaxy J7 ROMs, Kernels, Recoveries, & Oth] furkhan67:
Gr8 work bro???
[Samsung Galaxy J7 ROMs, Kernels, Recoveries, & Oth] smartass08:
Thanks guys....
[Samsung Galaxy J7 ROMs, Kernels, Recoveries, & Oth] mbk999:
Who is [MENTION=4436329]noob91[/MENTION] bc
[Samsung Galaxy J7 ROMs, Kernels, Recoveries, & Oth] smartass08:
My bro.
[Samsung Galaxy J7 ROMs, Kernels, Recoveries, & Oth] mbk999:
I don't care about him. Change it to mbk999 bhosdike
[Samsung Galaxy J7 ROMs, Kernels, Recoveries, & Oth] Jrangel2000003:
In my oppinion is the best rom based on aosp in the 2018 :y

Greatest work!! Amazing!!!! :victory:

---------- Post added at 06:38 PM ---------- Previous post was at 06:37 PM ----------

Valió la pena esperar por una buena rom
[Samsung Galaxy J7 ROMs, Kernels, Recoveries, & Oth] Atalla1974:
Galaxy j7 SM-710FN

Can u pls make this rom for the galaxy j7 SM-710FN (2016) ?
[Samsung Galaxy J7 ROMs, Kernels, Recoveries, & Oth] Jrangel2000003:
Bugs: Laggy, Mic, VoLTE

Also audio not working
[Samsung Galaxy J7 ROMs, Kernels, Recoveries, & Oth] Axxer9:
Substratum?
[Samsung Galaxy J7 ROMs, Kernels, Recoveries, & Oth] xcosby:
Wait for j7 prime
[Samsung Galaxy J7 ROMs, Kernels, Recoveries, & Oth] smartass08:
Ok
[Samsung Galaxy J7 ROMs, Kernels, Recoveries, & Oth] xcosby:
will you do ?
[Samsung Galaxy J7 ROMs, Kernels, Recoveries, & Oth] smartass08:
Idk
[Samsung Galaxy J7 ROMs, Kernels, Recoveries, & Oth] Axxer9:
And why do not you respond to me? is it compatible with substratum?
[Samsung Galaxy J7 ROMs, Kernels, Recoveries, & Oth] smartass08:
Yes it is...hit like if you liked my work
[Samsung Galaxy J7 ROMs, Kernels, Recoveries, & Oth] Axxer9:
Ok ok thanks sure

---------- Post added at 11:34 PM ---------- Previous post was at 11:10 PM ----------

one last question to try the rom, is it ok for normal daily use?
[Samsung Galaxy J7 ROMs, Kernels, Recoveries, & Oth] @amoghs:
Bro rom is superb.
[Samsung Galaxy J7 ROMs, Kernels, Recoveries, & Oth] Gautham Asir:
Audio not working

---------- Post added at 08:27 AM ---------- Previous post was at 08:27 AM ----------

Any bug fixes
[Samsung Galaxy J7 ROMs, Kernels, Recoveries, & Oth] sonangrai:
coolest aosp ROM upto now

Good battery

Only bug is audio

Good luck for

FIXING it
[Samsung Galaxy J7 ROMs, Kernels, Recoveries, & Oth] hd_scania:
Fresh installed your crDroid and problems are:

Lagging by sometimes and by random

Parts of apps are backed up but NOT THEIR APP-DATA

No sounds are but I need to very often listen to my music under VLC

Hopes to fix them asap.:)
[Samsung Galaxy J7 ROMs, Kernels, Recoveries, & Oth] Mohammedelsir3:
Sound didn't work+lagging alot
[Samsung Galaxy J7 ROMs, Kernels, Recoveries, & Oth] jodytejada:
Any fix for the robotic voice record ?
[Samsung Galaxy J7 ROMs, Kernels, Recoveries, & Oth] VivekAarav:
Made my day bro GREAT work..good luck for fixing..few bugs?
[Samsung Galaxy J7 ROMs, Kernels, Recoveries, & Oth] DmitryVT:
Hello. Very good firmware, just sound please repair.
[Honor 8 Questions & Answers] TweakingTweaker:
In Fastboot mode when FRP Lock text is green does that mean locked or unlocked?
[Honor 8 Questions & Answers] ayush rao:
If it is locked it will say locked in green colour.
[Honor 8 Questions & Answers] TweakingTweaker:
My unit says "FRP Lock" so I guess it is locked yet any google accounts have been cleared from the unit. Hmm :confused:
[Honor 8 Questions & Answers] sikica133:
try enabling oem unlocking in developer options
[Honor 8 Questions & Answers] TweakingTweaker:
Now I get why it was that way, thanks a lot man! :good:
[Mogul, XV6800 ROM Development] c0mputerp0et:
Firstly UPS to dcd no2 and all the rest for such awesome work. I find myself making a new rom for my own use on a daily now.

I'm a Mac user but have to use Parallels w/ XP to put my rom's on my Mogul. Most times this fails mid update. It's not in the same place every time and sometimes completes ( rarely )

The mogul is seen by XP. Active Sync picks it up and connects. I'm able to browse the phone/mem card. AND the RUU completes sometimes, leaving me with a phone & rom that boots.

When I use my friends XP machine the same rom's install perfectly, every time. So I know at the very least the rom's I create are good.

Does anyone have experience with this issue?
[Mogul, XV6800 ROM Development] anthonyandrews:
bootcamp

BOOT CAMP.....Thats is the answer for you, I hope.....

The reason why I say "I hope"...is that you need an Intel Processor to use it....if your mac is Intel bases, make a minimal partition with a minimum install of XP...(thats what I did)...

I use this partition ONLY for flashing my ROM.

If you DON'T have an Intel mac.....

1. Get more RAM

2. make sure you close all other open programs.

3. Make sure that you are not using an disk intensive activities.....(IE: uploading/downloading, virus scans, backups etc...)

4. Make sure that you do not do ANYTHING while flashing the ROM.

5. Make sure that your computer's SLEEP is disabled.....

6. For good measure, temporarily set parallels for parallels performance and NOT background applications.

7. If you know how, disable any unneeded services running in your WINDOWS Parallel....

8. If possible, make yourself a Win98 parition for parallels and you might have better results.

Remember, ANYTHING you do outside of parallels could affect the flash.
[Mogul, XV6800 ROM Development] allanak:
I've experienced a different issue using Parallels on my mac. When I first flashed it, I got stuck in bootloader. Every time I'd hook it up to the computer it would tell me the device was already in use and that Parallels couldn't use the device. A reboot of the computer and/or the phone didn't help multiple times. I had to break out an old dell laptop with XP on it just to get it to exit the BL.
[Mogul, XV6800 ROM Development] thirdeyeopen23:
i use vmware fusion on my mac under leopard, i can flash and do anything just fine..., maybe you should try fusion. Works for me
[Mogul, XV6800 ROM Development] geeserver:
Same here, Try VM FUSION... I had problems sending data to flash over usb with Parallels.
[Mogul, XV6800 ROM Development] shadowreader:
Another vote for VMware fusion and Leopard. I have done numerous flashes without issue. Boot camp is a pain but is the ultimate in compatibility. I find that vmware gets the job done for everything I need to do including flashing roms and unlocking the Mogul.