yashsingh1/xdaforums huggingface dataset:
[Moto G4 Plus Guides, News, & Discussion] pastorbob62:
I have the XT1625 non Amazon retail version. I downloaded the OTA update, booted into the bootloader, and flashed the following stock files:

fastboot oem fb_mode_set

fastboot flash boot boot.img

fastboot flash recovery recovery.img

fastboot flash system system.img_sparsechunk.0

fastboot flash system system.img_sparsechunk.1

fastboot flash system system.img_sparsechunk.2

fastboot flash system system.img_sparsechunk.3

fastboot flash system system.img_sparsechunk.4

fastboot flash system system.img_sparsechunk.5

fastboot flash system system.img_sparsechunk.6

fastboot flash logo logo.bin

I then booted the phone, waited for the OTA notification and told it to install it. My phone booted into the bootloader. I then selected recovery from the bootloader and the update ran automatically. Rebooted the phone from the bootloader and I was updated with all of my data and info intact. Obviously I lost root and TWRP but that was easily remedied. Also reflashed the logo so as to eliminate the unlocked bootloader warning.

It took about 20 minutes for the update to complete, then another 15 for the initial boot to update all of my apps. Also, be certain you have the correct stock firmware before flashing anything. I compared the version numbers in the .txt file that was in my firmware file to the versions on my phone. They matched perfectly.

Be patient, verify versions and you won't be disappointed. Above all make backups of everything before flashing.
[Moto G4 Plus Guides, News, & Discussion] Lapwolf:
The conundrum is whether the XT1625 software version is the same for the XT1644 (both Retail US).
[Moto G4 Plus Guides, News, & Discussion] pastorbob62:
I would say not. The XT1644 is a G4 plus. The XT1625 is just a G4. Numerous features that are different. For example, the camera is 16 mega pixel on the 1644 while it is only 13 mega pixel on the 1625. Also, the 1625 does not have the fingerprint scanner. You need to find the firmware that is specific to your phone. Otherwise you risk bricking your phone.
[Moto G4 Plus Guides, News, & Discussion] Lapwolf:
I tend to agree with that assessment. The only reason I question that is on Motorolas site:

https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images

They only publish the XT1625 recovery image, not the XT1644 image and it turns out that it's the Amazon version with ads...

Edit: It turns out that it will work but who wants the ads???
[Moto G4 Plus Guides, News, & Discussion] pastorbob62:
Not sure why they only provide the Amazon version. I used the .48 version (non Amazon) for the fastboot steps then used the OTA download to update the normal way. I suspect there will be a version of the .64 non Amazon available eventually, but who knows. I agree that the Amazon version would be a step down for sure. If it comes to that or staying on what I now have then I will stay put. But since my OTA update now works I can't see it becoming an issue.
[Moto G4 Plus Guides, News, & Discussion] Lapwolf:
Do you have a link to the non-Amazon version you downloaded?

Thanks!
[Moto G4 Plus Guides, News, & Discussion] pastorbob62:
https://androidfilehost.com/?fid=24572369242687085
[Moto G4 Plus Guides, News, & Discussion] matt_man:
What does "fastboot oem fb_mode_set" do. I didn't see that command listed in the thread explaining how to update. http://xdaforums.com/moto-g4-plus/how-to/guide-sucsessfull-ota-update-rooting-t3472658
[Moto G4 Plus Guides, News, & Discussion] Bender1987:
[MENTION=5779024]matt_man[/MENTION]

This command is only needed when you want to relock your bootloader, but you need a second fb_lock command at the end. So in this case it's a mistake.
[Moto G4 Plus Guides, News, & Discussion] Lapwolf:
OK, here's what I did and it worked perfectly to accept the OTA update to 64:

fastboot oem fb_mode_set

fastboot flash system system.img_sparsechunk.0

fastboot flash system system.img_sparsechunk.1

fastboot flash system system.img_sparsechunk.2

fastboot flash system system.img_sparsechunk.3

fastboot flash system system.img_sparsechunk.4

fastboot flash system system.img_sparsechunk.5

fastboot flash system system.img_sparsechunk.6

fastboot flash system system.img_sparsechunk.7

fastboot oem fb_mode_clear

fastboot reboot

I don't know if I really needed fb_mode_* but it didn't hurt. Thanks for pointing me the right direction!
[Moto G4 Plus Guides, News, & Discussion] galaxoid:
I wonder what's the correct firmware package for this phone:

XT1642

channel reteu

Firmware MPJ24.139-23.4

I tried to flash this to get OTA working XT1621-XT1622-XT1642_ATHENE_MPJ24.139-23.4_cid50_subsidy-DEFAULT_CFC.xml.zip. Phone didn't boot after that. Luckily I found backup from July that I had made right after I got the phone. Restoring boot and system got it working again.
[Moto G4 Plus Guides, News, & Discussion] Lapwolf:
That appears to be the Asian version though I don't know what the differences are. What did you modify that ultimately lead to the OTA update failing?
[Moto G4 Plus Guides, News, & Discussion] galaxoid:
Only the following:

- unlock bootloader

- temporarily load TWRP

- backuped boot and system

- Installed SuperSU from TWRP

- Changed system DPI with abd shell wm density command

After restoring boot and system OTA still fails with dead android symbol and text "Error". Very frustrating. Any suggestions what I should try?
[Moto G4 Plus Guides, News, & Discussion] Bender1987:
Have you flashed Logo.bin?
[Moto G4 Plus Guides, News, & Discussion] galaxoid:
Not that I know of.
[Moto G4 Plus Guides, News, & Discussion] Lapwolf:
I would reload system, boot, and recovery and then try the OTA.
[Moto G4 Plus Guides, News, & Discussion] Bender1987:
[MENTION=2718638]galaxoid[/MENTION]

You can also try to sideload the OTA-Update file with stock recovery, maybe you can see the reason in the log.
[Moto G4 Plus Guides, News, & Discussion] galaxoid:
I would try this, but I can't find the OTA file from my phone. It did download it and I have used the later option several times today, but there's no directory described in this guide:

http://xdaforums.com/moto-g4-plus/how-to/guide-sucsessfull-ota-update-rooting-t3472658

Should that directory /data/data/com.motorola.ccc.ota/app_download be in internal storage, SD card or where?
[Moto G4 Plus Guides, News, & Discussion] Bender1987:
[MENTION=2718638]galaxoid[/MENTION]

Are you rooted? It not, you don't have access to the folder.

Gesendet von meinem Nexus 9 mit Tapatalk
[Moto G4 Plus Guides, News, & Discussion] galaxoid:
Yeah, figured that out. I had removed the root trying to install the OTA. I re-rooted, copied the file to sdcard, loaded TWRP with fastboot, restored my backup of root and system.

Sideload complains that system partition has unexpected contents. So it seems my backup is not good and OTA will not accept it.

Does anybody know if stock firmware for my phone can be downloaded from somewhere? Not sure if the file from filefactory is good for euret channel phone.
[Moto G4 Plus Guides, News, & Discussion] Bender1987:
[MENTION=2718638]galaxoid[/MENTION]

What is your build no and sku XT1644?

Gesendet von meinem Nexus 9 mit Tapatalk
[Moto G4 Plus Guides, News, & Discussion] galaxoid:
XT1642 (dual sim)

channel reteu

Firmware MPJ24.139-23.4

Baseband M8952_70004.04.03.32R ATHENE_EMEA_DSS_CUST

Flashed system from http://www.filefactory.com/file/1pq...24.139-23.4_cid50_subsidy-DEFAULT_CFC.xml.zip using mfastboot and OTA sideload went through without issues. I tried this previously, but didn't notice that flashing multiple parts of system needs mfastboot instead of fastboot and my phone didn't boot at all. The instructions I had were using fastboot command so didn't realize there was something wrong.

Thanks for your great help, I learned a lot working with this phone!
[Moto G4 Plus Guides, News, & Discussion] Bender1987:
[MENTION=2718638]galaxoid[/MENTION]

Should be the same as mine ;)

I also flashed system, boot and logo from this one:

https://drive.google.com/open?id=0B8Pa0dVQxQjHbXVneTRjN0pfQW8
[Moto G4 Plus Guides, News, & Discussion] galaxoid:
Here we go again...

Finally got the Nougat update for Europe and guess what? Or course it fails to install again.

Sideload gives Error 7 with something related to system partition. Restoring the backup I made right after OTA updating to latest 6.0.1 doesn't help.

My phone was completely stock after I finally got the latest 6.0.1. OTA installed. I didn't have root or anything, only unlocked bootloader. TWRP was never flashed to the phone, only temporarily loaded with fastboot boot command.

Does anybody have stock ROM for the following so that I could try to flash the system partition to see if it helps with OTA this time:

XT1642 (dual sim)

channel reteu

Firmware MPJ24.139-63

Baseband M8952_70009.08.03.48R ATHENE_EMEA_DSDS_CUST
[Moto G4 Plus Guides, News, & Discussion] echo92:
I've successfully flashed this MM 6.0.1 ROM onto my XT 1642 (retgb channel) https://xdaforums.com/moto-g4-plus/how-to/moto-g4-plus-xt1643-updated-signed-t3460695 . I also got the error 7 after attempting to flash stock recovery (though this was trying to overwrite TWRP) - guessing there was a mismatch between the recovery and the system. A clean flash of the linked ROM allowed me to download and install the Nougat OTA (NPJ25.93-14) via the stock recovery.

Though your experience may vary, after flashing the MM ROM, my device was updated to 139-63/64 with EMEA baseband, July 2016 security patch, and still on the retgb channel. Also, I had both SIM slots functioning with active IMEIs. Good luck though. :)
[Moto G4 Plus Guides, News, & Discussion] galaxoid:
Thanks!

This version worked for me too, no data was lost, IMEIs correct, still on reteu channel. Nougat OTA went through without problems.
[General Accessories] Flammable98:
I am using 2 phones as home survilance system and one is the camera. Its old phone galaxy mini 2 but works very good for this. i just make handmace holder and place it as camera and battery drains faster idk why only mobile data set to on and AtHome Streamer (camera app) I am not at the place where camera phone is and i just see that remains with this app and 3G remaining time around 4hrs on battery. If i plug it into charger is ok but if i leave it plugged all the time battery will ruin?! Battery recharging cycles and idk about this and is there any build in mechanism or app to customize pattery recharging because i think if there is 100% will stop automaticly charging but app will drain some % and at 98-99% phone will start again to charge and when hit 100% will stop then again same and i will ruin battery.

How to plug always to charger but set only to rechgarge at 1% for example and all the time before reach 1% to stay and do not recharge but WITH PLUGGED CHARGER CABLE
[Huawei MediaPad M2] beast.in.black:
Reserved

Reserved
[Huawei MediaPad M2] beast.in.black:
Reserved 2
[Nexus 7 (2013) Android Development] nbehary:
THIS IS NO LONGER BEING UPDATED

This was just about a direct copy of the ROM here I created due to the dev including opengapps in his builds: http://xdaforums.com/nexus-7-2013/orig-development/p-aosp-n-7-0-google-shame-t3448008

They are no longer doing that, so I am focusing on contributing to that. The v0.6 build there is equivalent and a bit better than the v0.6.1 build here. Just use their's. (Leaving the links here for now, but really don't use them. )

Full credit to [MENTION=4318865]DevSwift1[/MENTION] for all his work on this thus far. (and the other contributors listed below). Seriously, the work they have done is a thing of beauty and I'm only doing this out of necessity of doing the right thing. (I'd rather not be, but I said I would and it may be fun.)

What works:

Audio

Brightness

GPU Acceleration

Bluetooth

Wifi

GPS

NFC

Location services

Camera and video recording

Video playback

MTP

Sensors

Bugs:

- very poor 1080p video recording quality

- Google seems to think you are using a 2012 N7. I pulled part of the fix for that since it was only part and broke the build. It should be worked out next build. (or, the next build)

You can dirty flash, but you may need to uninstall and re-install any Google Apps you installed from the Play Store.

Change Log

V0.6.1

- Uses kernel that is not vulnerable to CVE-2016-2059. (@zaclimon's with [MENTION=4318865]DevSwift1[/MENTION]'s patches to compile it on GCC 4.9. The stock N7 kernel was never vulnerable to that CVE and neither was that one which isn't heavily modified from it.)

V0.6

- Updated to Android-7.0.0_r6, NRD90U, Sept 6, 2016 Security Patch. (I think r4 was actually the security patch. Not sure if there is more in r6.)

- Note that this is missing the fix for CVE-2016-2059 which was part of the Sept Security Update, but resides in the kernel which isn't part of the AOSP build. I'm fixing that and will have an updated ROM or flashable kernel soon. (Hopefully. Building the kernel is new to me)

V0.5.1

- Fork of DevSwift1's V0.5 with Gapps removed.

- Location Services works with wifi

Sources:

https://github.com/nbehary/manifest

Download:

v0.6.1

V0.6

Very Unsupported, experimental Download for Deb

This builds correctly from my fork of Devswift1's stuff which included Deb. I have no idea if it works.

v0.6.1 (Just the new Kernel for CVE-2016-2059)

V0.X (it should be about v0.6 if it works. Same sources except the parts that are different between the devices.)

Get Gapps from here: (The Micro Edition is the largest that will install due to size constraints on the System partition.)

http://opengapps.org/

contributors:

DevSwift1

zaclimon

parrotgeek1
[Nexus 7 (2013) Android Development] vkk178:
I was able to get micro Gapps installed with about 90m free space using the original ROM..(Will that cause issues ?? ) . Actually downloaded minigapps ,but created a gapps-config to install micro . I noticed that without Google search being a system app ,it gets killed quite quickly and takes time to load .That seems to have gone
[Nexus 7 (2013) Android Development] nbehary:
Doing that should be fine I'd think. The only issue is running out of space and as long as you aren't doing that there shouldn't be issues. (I only recommend nano since that is what I have been using and it worked for me so far.)
[Nexus 7 (2013) Android Development] binglejellsx2:
Unless the ROM itself gets 90mb bigger in future updates, micro should always fit. Technically, nothing should be writing to /system after install since it's usually locked anyways. Any free space in that partition just sits idle, unused.
[Nexus 7 (2013) Android Development] Extreemator:
Any custom kernels works on it? Because stock is garbage. I saw nexus 5 reports of 6.0 versions working on 7.0
[Nexus 7 (2013) Android Development] NeoDaemon:
You can mark this as fixed [MENTION=3286382]nbehary[/MENTION]

Thanks to you and to [MENTION=4318865]DevSwift1[/MENTION] this has been posible thanks to him and i encourage him to continue working on this port, it's amazing so far and there are many users out there that thank you for your hard work and for giving this rom to the community. Thanks!

Also thanks to the rest of developers.

Beautiful widgets now locates correctly, and so many other apps like Waze or Meteogalicia (local weather apps) Thank you.

[IMG="Locates correctly"]http://i.imgur.com/w6bGTye.png[/IMG]
[Nexus 7 (2013) Android Development] Jay Rock:
I get this when flashing. Afterwards attempting to flash gapps indicates that I'm still on Android 6.0.1.
[Nexus 7 (2013) Android Development] Jay Rock:
Never mind. Just had to boot into the system and flash gapps afterwards.
[Nexus 7 (2013) Android Development] binglejellsx2:
I've been following all of these 7.0 ROM threads since the beginning. It looks like enough fixes have been done to this rom (thanks to the work of ALL the devs involved) for me to finally install it. Great job everyone!

DISCLAIMER FOR THE REST OF THE POST: Not for noobs or the faint of heart

I just dirty flashed this right over the last official MM and full device encryption enabled. For the most part things went smoothly. The only thing (and it's quite a lot for me) I had to do was uninstall and re-install, through the Play Store, just about everything from Google. The only app that didn't crash was Play Games - almost anything else with a Google account crashed, including MightyText (I originally suspected this was because I used nano GApps, which removed most GApps from /system - but YouTube Creator Studio and MightyText debunk that theory). After doing this everything seems to be running smoothly, but I'll continue to monitor battery usage. AOSP Calendar and Contacts have been disabled, in favor of the Google versions.

The biggest reason I wanted N was so I could use Night Mode and get rid of Twilight. The option is still baked into AOSP even though it won't appear in the Quick Settings shade. Download Night Mode Enabler from Play Store and the option returns.
[Nexus 7 (2013) Android Development] rbradmag:
Clean flashed 0.5.1, immediately rebooted back into recovery and flashed OpenGapps Pico and SuperSU 2.78 while wiping Dalvik and Cache between each step.

Everything works perfectly including the restoring of my Titanium app backups.

Thanks for supporting this device!
[Nexus 7 (2013) Android Development] FingerMove:
Sorry for being off-topic, but Twilight is really bad compared to Chainfire's CF.lumen. Twilight adds a kind of overlay, while CF.lumen does it with root and a driver, which makes the screen not look washed out or blurry like Twilight. It's free, too. Otherwise there's the live display one in every CyanogenMod based rom.
[Nexus 7 (2013) Android Development] binglejellsx2:
Thanks, but now that Im on Nougat, I have a native solution available. The reason I used Twilight is because I don't root anymore. I'm aware of other solutions, but these days I'm looking for the simple stuff.

This ROM is exactly what I was looking for.
[Nexus 7 (2013) Android Development] anykill:
Can I skip tracks with volume keys?
[Nexus 7 (2013) Android Development] dadymon53:
Any get system ui tuner working?
[Nexus 7 (2013) Android Development] Nevermindthelabel:
Yes. Just help the settings wheel down for a few seconds, nothing too crazy. Just use it to display battery percentage
[Nexus 7 (2013) Android Development] nbehary:
V0.6 is up on the main page. It just merges in the Sept Security Update.
[Nexus 7 (2013) Android Development] nbehary:
Going to say likely not. I just tried ElementalX, with all default settings, and it boots to recovery. There may be ones that will (in theory there can be, this uses the stock 6.0 kernel far as I can tell).

It really is in the kernel dev's wheelhouse to fix things for a new Android release. I totally don't want to get into that world. Did enough messing around in the Linux Kernel in the 90's.

That said, if there are things on the AOSP side I can do to help things work, I can look into that.
[Nexus 7 (2013) Android Development] Extreemator:
So it boots to OS with elementalX? Or boots only to recovery?
[Nexus 7 (2013) Android Development] Nevermindthelabel:
Glitch kernel has a version that is compatible, but I have not used it yet
[Nexus 7 (2013) Android Development] nbehary:
It boots to recovery. I think it got as far as showing the logo for a split second before rebooting into recovery. (I also was wrong about this being stock maybe. It was compiled too recently, and not by Google. Not sure where it came from, since it is just a Binary in the repos. Could still be a very slightly modified, if at all, 6.0.1 stock.)
[Nexus 7 (2013) Android Development] nbehary:
And, best way forward with this. Which 6.x kernels work on the N5? Can you try them if there are flo/deb equivalents and let me know what happens. (That would help me determine if there is something I can do to make them work if they don't)
[Nexus 7 (2013) Android Development] Nevermindthelabel:
Blu_Spark works on Nougat, and I have heard the latest release of elementalx works too
[Nexus 7 (2013) Android Development] nbehary:
Do they have updated flo* versions? Don't feel like looking, but I want to say the N5 is close enough to the N6 or N5X, kernel-wise that they could be using sources from one of them to get it working on the N5. Razor (better term), is going to be harder.

*- I said deb too, which usually the same I think, but I can't support deb (but also have it on my mind since I am seeing if I can build "0.6", won't be quite the same probably, of this for it to be nice while the dust I caused settles.
[Nexus 7 (2013) Android Development] Nevermindthelabel:
No unfortunately. Last elementalx was August security patch, and the N5 elementalx that boots Nougat is the September release. Blu doesn't have a N7 version. Although the rom I'm running on my N5 did just release a custom kernel here http://xdaforums.com/showpost.php?p=68629673&postcount=194 that may be of some use
[Nexus 7 (2013) Android Development] tungdil:
Currently I have version R251 "N" running with v0.5 without problems. The nice thing is that it allows running Nougat as primary on a "MultiROMed" device still allowing to boot into secondary ROMS :good:
[Nexus 7 (2013) Android Development] manulemaboul:
Last time I tried it, camera and sensors werent't working tho
[Nexus 7 (2013) Android Development] NeoDaemon:
Wiped System, Dalvik&ART, Cache

Flashed 0.6

Rebooted onto recovery again

Flashed Gapps micro

Flashed Supersu

Flashed AdAway_systemless_hosts_v2 so adaway works

So far it's working nicely. Thanks!!
[Nexus 7 (2013) Android Development] tungdil:
Camera and sensors are both working fine for me (clean flash v0.5, glitch-kernel and SuperSU v2.77beta) this wasn't the case with v0.4.
[Nexus 7 (2013) Android Development] ReelFiles:
Are you planning on adding any features or fixing the 1080p bug?
[Nexus 7 (2013) Android Development] manulemaboul:
Good to know, it was indeed on 0.4, gonna flash 0.5 then, thanks :)
[Nexus 7 (2013) Android Development] Droid_JD:
anyone else having problems with streaming video? YouTube and Netflix work fine, but xfinity, CNN, HBO, etc. Crash when o hit play. Any ideas? Running clean flash v 5.
[Nexus 7 (2013) Android Development] biontx:
Running v0.6: still the following security vulnerability CVE-2016-2059

Running v0.6 : great work!!!

However: still the following security vulnerability CVE-2016-2059

Tested with 'QuadRooter Scanner'

https://play.google.com/store/apps/details?id=com.checkpoint.quadrooter

>>

https://www.codeaurora.org/projects/security-advisories/linux-ipc-router-binding-any-port-control-port-cve-2016-2059

>>

fix:

https://source.codeaurora.org/quic/la/kernel/msm-3.18/commit/?id=9e8bdd63f7011dff5523ea435433834b3702398d

>>

Could this be fixed please?
[Nexus 7 (2013) Android Development] rbradmag:
Thanks for the heads-up. Just installed Glitch kernel r-521-full-N. Installed smoothly and everything works nicely. Great to have DTTW again.
[Nexus 7 (2013) Android Development] ingluisg:
google play not working, google play services has stopped
[Nexus 7 (2013) Android Development] swiftyste:
Thanks for the clean version.

I had a lot of problems with the gapps being included.

No issues so far.

But security vulnerability CVE-2016-2059. Needs to be fixed asap but apart from that great work
[Nexus 7 (2013) Android Development] tiny4579:
One of the cve for quadrooter is blobs. I'm not sure it will be fixed on older releases. I'm not sure if the fix for that cve is blobs or kernel.
[Nexus 7 (2013) Android Development] Ænimal:
People here are doing this stuff for free on their spare time, so don't push..
[Nexus 7 (2013) Android Development] swiftyste:
I'm not pushing!!!!

Its called letting them know so think before you comment without people like me there would be hidden bugs.

Theses guys are the best and its great that they are posting. And doing this in there free time

but with bugs like this it can't be ignored

This is a really important. Do you want someone to take over your device. Probably not

So if you got nothing nice to say don't say anything at all
[Nexus 7 (2013) Android Development] thereal_bigjake:
Are you using one of those apps to detect? They don't work...
[Nexus 7 (2013) Android Development] swiftyste:
QuadRooter scanner