Hello to this amazing community,
I have recently tried for the first time to root my device.
Being unaware of the XDA community, I used this guy's guide - https://theunlockr.com/2016/11/29/root-motorola-moto-g4-moto-g4-plus/ .
As I went through the steps of unlocking, booting TWRP and installing superSU, I found out that the device won't start anymore, though the bootloader was still working at that point.
Unfortunately, that guide didn't emphasized the importance of first backing-up the system with TWRP.
Panicking, I even ended up wiping the entire device.
So I started my sisyphic journey of reviving the phone.
Being clueless of OEM stock versions etc. at this point, I thought that I should look for a fresh TWRP backup someone did after purchasing my exact Moto G4 Plus model - XT1644 so I ended up recovering the version that this dear guy has uploaded:
https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1644-stock-unmodified-6-t3536448
Happy as I was that the machine would finally start, I found out I was running an old Marshmallow version - exactly as the title says.
Still, I assumed that new OTA versions will be available and my device will be upgraded to the most up-to-date version.
Surprisingly for a rookie as me, checking for software updates showed " Your device's software is up to date".
So I search for a more up-do-date OEM stock version, and I have found the following version - NPJS25.93-14-13 here:
https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
I ran the bash file to flash the OEM while keeping the device unlocked.
The device has loaded finally with the familiar up-to-date version, and an available OTA update appeared.
I immediately ran the update.
That's when I first became familiar with the term "Brick". The device became completely dead.
Now, thanks to siddhesh9146 inceredible thread I managed to revive the device:
https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761
I went through his steps, installed BlankFlash, flashed the latest gpt and bootloader and flashed version NPJS25.93-14-10.
The device will finally work! I would realize then, that the latest version is actually ATHENE_NPJS25.93-14-13 ,
And again, the device won't show any updates available.
So, finally, here are my questions:
1. What could I have done wrong in first place? Was it a wrong superSU version that caused the problem? (In case my rooting aspirations will return)
2. What caused the device to turn brick? I realize it has to do with downgrading version, but after I wiped the device, I only upgraded versions.
3. In general, when OTA are available? Only the newest stock version would receive OTA? Will I have to manually upgrade versions from now on?
4. Could I upgrade now to NPJS25.93-14-13 using the version that siddhesh9146 presented without wiping my entire phone? What exactly should I flash to do so?
5. What are the precautions I have to take while doing so? Is there a risk my phone will tun brick again?
Thanks!
Good to hear your device is working again, seems like it's been through a journey.
1)When you originally rooted, were you on stock Nougat (7.0)? If so, those rooting guides will not work and are likely for Marshmallow 6.0 systems only. What they fail to mention is that attempting to root whilst still on the stock Motorola Nougat kernel likely causes your device to not boot. The Nougat 7.0 stock kernel for our devices seems to be much stricter than the Marshmallow kernel when it comes to anti-rooting protections. Thus, we generally need to flash a custom kernel onto our devices before rooting - either with SuperSU or magisk. An example of a working guide for rooting on stock Nougat Moto G4/Plus is here: https://forum.xda-developers.com/mo...de-root-moto-g4-plus-supersu-android-t3587918
2)Do you remember what the OTA you received was? I don't think there's an OTA for a build later than NPJS25.93-14-13 out yet. That suggests that the NPJS25.93-14-13 flash didn't work - did you check if the bash script reported [OKAY] after each command? By brick, do you mean the device had a blinking LED light, and there was no screen, and you were unable to boot to the bootloader and/or recovery? If the flash didn't work, then you may have taken a Marshmallow to Nougat OTA (NPJ25.93-14) which may have corrupted your device bootloader in the process.
3)OTAs are generally available for a particular build and for a particular software channel when they are released. For NPJS25.93-14-13, that's currently the latest build for EU/UK, Brazil and India devices, and there's word that there's a February 2018 OTA coming soon (no sign of it yet).
However, for your device (XT1644), if you are on the retUS - retail US - software channel, your device is on a different update path - NPJ25.93-14.7 would be the corresponding September 2017 patch for retUS software channel devices. NPJS25.93-14-10 is not one of the builds deployed to the retUS, and as such the Motorola servers may not issue you an OTA patch, regardless of whether the firmware would work. There have been reports of NPJS25.93-14-10 and NPJS25.93-14-13 working on US devices without issue, but you may not receive OTA updates.
You could manually update to NPJS25.93-14-13 using the OTA here, provided that you fully flashed the NPJS25.93-14-10 stock ROM (including GPT and bootloader, system, modem, boot, recovery, OEM, DSP, FSG). If you did not fully flash, you may be risking another hardbrick. https://forum.xda-developers.com/showpost.php?p=74973505&postcount=7
4)If you want to flash the NPJS25.93-14-13 stock ROM to be safe, or attempt to cross flash to the Sept 2017 NPJ25.93-14.7 firmware without wiping your data, you can use the following flashing commands. Be warned that you may have to factory reset if your device becomes unstable, so backup anyway. I would recommend manually flashing these commands:
a)copy and paste the first command to the ADB terminal
b)press enter, wait for [OKAY] to appear.
c) copy the next command, individually and in order, to the terminal, repeat b) and c) until you get to the end of the list.
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.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 system system.img_sparsechunk.7
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot reboot
These commands omit the fastboot erase userdata, preserving your data, and omit the OEM locking commands, which would lock your bootloader and erase your data in the process as well. Bear in mind that cross flashing can be risky, however, you may have to flash the NPJ25.93-14.7 update if you wish to receive OTA updates for the retUS software channel, if you are on that software channel. Link for the NPJ25.93-14.7 stock firmware if you wish to try: https://androidfilehost.com/?fid=817906626617945295
5)Generally, the main source of hard bricks I've noted has been users have been on stock Nougat (particularly the March 2017-latest) builds. They downgrade their device to stock Marshmallow firmware, which goes okay. However, in most - if not all - cases, their bootloaders are not downgraded, so you have a system and bootloader mismatch, with a newer Nougat bootloader but an older system than their bootloader patch level. For example, a B1:06 June 2017 patch level bootloader but a July 2016 Marshmallow system patch level.
The OTA checks that are performed are mainly on the system side i.e is your device on the July 2016 system patch? Are your system, OEM, recovery, boot etc. partitions unmodified and match the expected checksums for this OTA patch? If so, then install. However, in the updater script, there is no such check for the bootloader - the OTA updates appear to assume your bootloader is of the same patch level as your system. Normally, for a locked bootloader or for a user that has only updated their device, that assumption holds.
The issue we have here is that the system was downgraded to Marshmallow, so that assumption no longer holds. As the OTA updates are signed by Motorola, they have authorisation to write to your bootloader. That means this OTA can overwrite your bootloader, and if it's applying older code, can corrupt your newer Nougat bootloader and thus hard brick your device, which necessitates a blankflash to repair.
In other words, if you downgrade your device firmware, do not use or install OTA updates. If you do downgrade, only update with stock firmware that is as new or newer than your bootloader patch level. If your device is on the same patch level , then you should be able to use OTA updates. However as mentioned above, you need to be on the correct build for your device software channel as well to receive OTA updates from Motorola.
Related
I have a G4 Plus which i've flashed with a stock ROM. The phone is running Marshmallow 6.0.1 and the build number is: MPJ24.139-48 - the patch level is 1 May 2016. When I hit 'update' it doesn't update to July 2016 which is the latest available patch in the UK.
Does anyone have a UK marshmallow rom for the G4 Plus which I can load onto the phone and then update to the July 2016 patch??
Any help would be fantastic. Thanks in advance.
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images
Select I agree and then moto g from the dropdown menu. The instructions are fairly straightforward. XT1625 works for your device. Bootloader probably does not need to be unlocked if not downgrading**
Then execute the following
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot reboot
Edit: Use 7-Zip to extract the tarball from tgz file, and then again extract the files from the tarball.
**I'm not sure though, select allow oem unlocking in developer options just in case
mrinmaydhar - thank you very much. I will try that out now.
Which stock ROM did you flash, btw?
You may like to look at this stock ROM here https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1643-updated-signed-t3460695
Though it's for XT1643, I've previously successfully flashed it onto a UK XT1642, dual SIM G4 Plus and had no issues. It also brings the July security patch and build 139-63/64, and from what I remember, kept the EMEA baseband and IMEI numbers for both SIM ports.
echo92 said:
Which stock ROM did you flash, btw?
You may like to look at this stock ROM here https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1643-updated-signed-t3460695
Though it's for XT1643, I've previously successfully flashed it onto a UK XT1642, dual SIM G4 Plus and had no issues. It also brings the July security patch and build 139-63/64, and from what I remember, kept the EMEA baseband and IMEI numbers for both SIM ports.
Click to expand...
Click to collapse
Thanks i'll try that because it sounds like you've had a good success with it!
I flashed this one: ATHENE_MPJ24.139-48_cid50_subsidy-DEFAULT_CFC.xml
It worked but it was stuck on the 1st May 2016 security patch and kept saying it was up to date and wouldn't upgrade further.
Quick update: I tried echo's rom link because the other one had issues - WiFi wouldn't work.
Echo's xt1643 rom works well. It also includes the July 2016 patch level as mentioned in the posts above.
My next question is: when Nougat arrives, I assume we'll be able to upgrade to it. Will the nougat upgrade install the recovery file? For whatever reason, I don't think my recovery file installed properly when I flashed the rom. Just wondering ifnNougat will overwrite it when it is released?
motogfalcon said:
Quick update: I tried echo's rom link because the other one had issues - WiFi wouldn't work.
Echo's xt1643 rom works well. It also includes the July 2016 patch level as mentioned in the posts above.
My next question is: when Nougat arrives, I assume we'll be able to upgrade to it. Will the nougat upgrade install the recovery file? For whatever reason, I don't think my recovery file installed properly when I flashed the rom. Just wondering ifnNougat will overwrite it when it is released?
Click to expand...
Click to collapse
Nice one, from the sounds of it, everything's working
As for Nougat (whenever it arrives in the UK and Europe!), you should be receiving an OTA update, since you're up to the latest MM 139-63/64 build for our region. It also should flash onto your device provided no modifications have been made to the recovery/system (bootloader lock/unlock doesn't appear to matter).
What did you see that suggested your recovery wasn't properly installed? If it was an error such as 'not signed' or 'bad key', but reported OK after flashing, don't worry about it.
I got the 'not signed' message. Excellent! All seems to be working well. Looking forward to when Motorola release Nougat. It's a shame they haven't kept on top of the security patches because its a great device I think! Thanks again!
motogfalcon said:
Excellent! All seems to be working well.
Click to expand...
Click to collapse
What is your software channel now? Still retgb ?
Yes retgb. Apparently Lenovo are releasing Nougat soon in the UK so hopefully I'll get it on the retgb channel
Hi,
I have a complete stock moto g4 plus XT1642, with firmware build number NPJS25.93-14-4 (march security update), retgb.
I didn't get the June security update, and I the phone insists that my software is up to date..
I am not interested in rooting my phone. How can I force it to update?
(I also have the same problem with another retgb moto g4 non-plus..).
Thanks!
Yeah, retgb updates seem to be taking a little while to deploy... Like your experience, I was waiting for updates on the retgb channel too... Then I updated using the captured updates on XDA, which appeared to have worked okay
You've got 2 routes:
1) You can download the June 2017 OTA update from here to your device: https://drive.google.com/drive/folders/0B-GUyOfb8OgzR1VrQ1NHWDVmWE0
This is the same update that was on XDA, just mirrored to my Google Drive as the original link does not appear to work.
File name:Blur_Version.25.201.4.athene.retail.en.US.zip
Size: 56 MB
md5 checksum: 4ce250195b2eb71c960ec3b6579bc9d0
Ensure your device is fully updated to NPJS25.93-14-4 (bootloader should be version B1:05), you have a stock recovery, unmodified system and baseband (baseband version should end in .62R), as this update requires the March 2017 update. If your bootloader is still locked, this should all be applicable. Then:
Boot to stock recovery (notes on how to access stock recovery are here: https://forum.xda-developers.com/showpost.php?p=72981796&postcount=58 )
Select 'apply update from SD card'
Locate the Blur_Version.25.201.4.athene.retail.en.US.zip on your device
Install update.
You may wish to wipe cache before rebooting.
Now, you should be updated to June 2017. There's also the September 2017 OTA (requiring the June 2017 patch) which you can apply in the same fashion: https://forum.xda-developers.com/moto-g4-plus/how-to/captured-ota-september-security-patch-t3680367
I successfully flashed the June 2017 OTA onto my XT1642, retgb (so same as yours) that had previously been running on NPJS25.93-14-4 and have had no issues - my network provider, 3 UK, works well
2) If you want to, you can jump straight to the September 2017 stock build, which is running on my XT1642, and this is the method I chose to update (as I was rooted too, so needed a near clean start). I think it should be suitable for the Moto G4 too that you have, but you may wish to check the following stock ROM thread to confirm.
a) Download the September 2017 stock ROM (NPJS25.93-14-10): https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
b)Set up ADB as directed in the above post. Extract the ROM files in the same folder as your ADB terminal (so you should see files like oem.img and bootloader.img mixed with adb.exe and fastboot.exe)
c)If you wish to keep your data and do not need to re-lock your bootloader (i.e. your bootloader is already locked, or unlocked) and are simply updating, you could use the following fastboot commands to keep your data intact. Back up your data just in case your system becomes unstable and needs a factory reset, though I did not notice any corruption of my data. The initial boot was a little slow (presumably to rebuild caches and update links as necessary):
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.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 system system.img_sparsechunk.7
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot reboot
These commands should update your GPT, bootloader, recovery, system and modem to NPJS25.93-14-10, Sept 2017 patch. Though you could edit one of the flashing scripts - provided in the stock ROM thread - to match the above commands, I preferred to manually copy each command and execute the commands, checking each command flashed. As with anything affecting the firmware of your device, take your time in flashing. Using the September 2017 stock ROM, my XT1642 is still running happily with the September security patch (and seems smoother too )
Bear in mind that with the June and September updates, the bootloader is updated to version B1:06. Thus, it makes downgrading risky. From the sounds of it, you're not interested in rooting/downgrading, so this might not be for you anyway. Just a heads up that downgrading from the June or September 2017 stock ROMs (e.g. by flashing the older stock ROM without flashing GPT/bootloader) and then accepting OTA updates may cause a device to hard brick. We have ways of attempting to rescue a device in this state but I really wouldn't like to try them if at all possible.
Good luck whichever route you choose
Hi, I'm trying to get my phone back to normal state. It was on Nougat 7.0 I would like to get it on 6.0.1. but I'm so new know where to begin. It's also a Republic Wireless (not a major carrier) so I'm not sure how to start messing with this thing. I ran in to a problem last night trying to put on Magisk because I wanted the option of hiding root and it got stuck in a bootloop. I wasn't sure i could get it back but i did with Lineage OS now I'm trying to get it back to some degree of what I had it. I would like tips putting on Android 7.0 if I choose to upgrade to it again but mostly I want to know a way to put it on A Marshmallow.
1)Rooting on stock Motorola Nougat ROMs is different to rooting on 6.0.1. Due to the stricter anti-rooting measures on stock 7.0 kernels, you need a custom kernel (e.g. ElementalX), else you'll bootloop as you've discovered. If you wish to root in future on stock 7.0, this guide might be useful: https://forum.xda-developers.com/mo...de-root-moto-g4-plus-supersu-android-t3587918 You can use magisk instead of SuperSU.
2)If you want to go back to stock Nougat, are you on the retus software channel (might be under Settings, but I'm not sure if it'll show up on Lineage OS)? If you are, then this NPJ25.93-14.7 firmware might be for your device https://androidfilehost.com/?fid=817906626617945295 Please doublecheck that this is the correct firmware for your device before flashing. Also, be aware that flashing stock ROMs will wipe TWRP, your data and may wipe your internal storage, so back up before flashing. Nougat stock ROM firmware may also offer better compatibility for the custom Nougat/Oreo ROMs out there.
3)If you previously were on stock Nougat, can I ask why you wish to downgrade to Marshmallow (MM)? There's MM (6.0.1) stock ROMs out there (MPJ24.139-64, which should be the latest US build for MM: https://androidfilehost.com/?fid=312978532265364350 ). However, if you were on stock Motorola Nougat previously, especially on the June/September 2017 stock Motorola ROMs, I personally would advise against downgrading, or if you do choose to flash stock Marshmallow, do not accept OTA updates to update (e.g. to Nougat). If you downgraded, then in this case you'll have a Marshmallow system, but a Nougat bootloader - bootloaders typically won't downgrade. By taking a MM to Nougat OTA, you may corrupt your bootloader and hard brick your device (i.e. won't turn on, blinking LED, not recognised by your computer etc, device not usable and data not accessible.). We do have a way to recover a device hardbricked, but it's a last resort really. https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761 Custom MM and Nougat ROMs don't mess with the bootloader, so should be safer.
I leave it up to you about what you wish to do with your device. Good luck whatever you choose.
How do I install the firmware? I tried flashing it in twrp, and it said invalid zip
endleesss said:
How do I install the firmware? I tried flashing it in twrp, and it said invalid zip
Click to expand...
Click to collapse
Stock ROM firmware zips are not flashable in TWRP. You need fastboot to flash stock ROMs (following a procedure like https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 ), bear in mind that flashing these stock ROMs will usually replace TWRP with the stock recovery. Also they will revert your device to full stock.
Erasing your data will also happen unless you omit the erase userdata command, but if you're switching from a custom ROM back to stock, you may have to erase data anyways for stability.
Thank you!
Hoping this will help someone, this is what happened to me:
My phone is XT1625 Build # NPJ25.93-14.7
I flashed TWRP, then backed up, then flashed supersu. resulting in bootloop, i restored using the twrp back up, still bootloop.
To fix, download stock firmware: download https://androidfilehost.com/?fid=817906626617945295
Unzip the file, then in In adb run these commands one at a time.:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.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 system system.img_sparsechunk.7
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
Phone is back to stock
My moto g4 plus, model XT1643 was hardbricked, i installed blank flash on it, it has rebooted into bootloader mode of blankflash with no android logo, and has locked oem of my phone. I cannot install a stock rom now as the oem is locked and when unlocking oem from cmd prompt its asking me to enable oem from from developer options, which i cannot do as my mobile is not booting. Please help as to how can i install stock rom into it as my bootloader and oem is locked now. Any help would be appreciated, thanks.
tried to pass the last stock if I am not mistaken version that is or updated passes without being with bootloader unlocked.
Pranav_dp said:
My moto g4 plus, model XT1643 was hardbricked, i installed blank flash on it, it has rebooted into bootloader mode of blankflash with no android logo, and has locked oem of my phone. I cannot install a stock rom now as the oem is locked and when unlocking oem from cmd prompt its asking me to enable oem from from developer options, which i cannot do as my mobile is not booting. Please help as to how can i install stock rom into it as my bootloader and oem is locked now. Any help would be appreciated, thanks.
Click to expand...
Click to collapse
Following a blankflash, you can only boot into the bootloader, which is normal. It seems that using a blankflash sets your bootloader to be locked, regardless of if it was previously unlocked in the first place. Provided you can flash a stock ROM, your bootloader should become unlocked again.
Have you tried flashing the April 2018 fastboot stock ROM from https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 ? The guide there should be useful in how to reflash stock firmware to your device, and as it's the newest firmware that has been leaked, should rescue your device.
If you want to keep your bootloader unlocked and try to save your data, then try the following flashing commands instead of the ones in the guide. Be aware that you may have to factory reset your device should it boot but be unstable.
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.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 system system.img_sparsechunk.7
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot reboot
These commands should flash the April 2018 GPT, bootloader, system and modem to your device. Please try to avoid hardbricks in the future by only flashing stock firmware as new or newer than your bootloader, and please do not use old OTA updates.
echo92 said:
Following a blankflash, you can only boot into the bootloader, which is normal. It seems that using a blankflash sets your bootloader to be locked, regardless of if it was previously unlocked in the first place. Provided you can flash a stock ROM, your bootloader should become unlocked again.
Have you tried flashing the April 2018 fastboot stock ROM from https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 ? The guide there should be useful in how to reflash stock firmware to your device, and as it's the newest firmware that has been leaked, should rescue your device.
If you want to keep your bootloader unlocked and try to save your data, then try the following flashing commands instead of the ones in the guide. Be aware that you may have to factory reset your device should it boot but be unstable.
These commands should flash the April 2018 GPT, bootloader, system and modem to your device. Please try to avoid hardbricks in the future by only flashing stock firmware as new or newer than your bootloader, and please do not use old OTA updates.
Click to expand...
Click to collapse
Thank you so much, I've restored the stock rom following your guidelines, my phone is working fine but im not able to install any OTA updates after that. Should i just skip any OTA updates from now on, please advice. Thank you.
Pranav_dp said:
Thank you so much, I've restored the stock rom following your guidelines, my phone is working fine but im not able to install any OTA updates after that. Should i just skip any OTA updates from now on, please advice. Thank you.
Click to expand...
Click to collapse
If you flashed the April 2018 security patch stock firmware, there are currently no OTA updates, the April 2018 security patch is the latest available.
If you fully flashed the latest firmware as I mentioned, you should be okay to use OTA updates. Just in future please remember to not use OTA updates if you downgraded your device by flashing old stock firmware.
i have here one xt1640 dead for ota OPJ28.111-22 upgrade.. is possible put in Fastboot for Blank Flash Repair?
Daroas said:
i have here one xt1640 dead for ota OPJ28.111-22 upgrade.. is possible put in Fastboot for Blank Flash Repair?
Click to expand...
Click to collapse
Without a blankflash new enough to flash to the device, I don't think so. You'd have to consider a JTAG repair, a motherboard replacement or buy a new device.
Hello,
This afternoon i got the notifiction for the update to andriod 8.1, most of the time newer is better so i installed the update. My phone however has 1 problem, the screen burns in very fast. This could be stoped in andriod 7.1.1 with the blue light filter (or night filter). This option however isnt present anymore in andriod 8.1. To stop the burn in i tried multiple apps to get some sort of blue light filter, none of them worked, or just werent as good as the build in option in andriod 7.1.1. my question is: is there a way and a guide to downgrade my phone back to andriod 7.1.1?
Zagre said:
Hello,
This afternoon i got the notifiction for the update to andriod 8.1, most of the time newer is better so i installed the update. My phone however has 1 problem, the screen burns in very fast. This could be stoped in andriod 7.1.1 with the blue light filter (or night filter). This option however isnt present anymore in andriod 8.1. To stop the burn in i tried multiple apps to get some sort of blue light filter, none of them worked, or just werent as good as the build in option in andriod 7.1.1. my question is: is there a way and a guide to downgrade my phone back to andriod 7.1.1?
Click to expand...
Click to collapse
Have you tried https://play.google.com/store/apps/details?id=com.eyefilter.nightmode.bluelightfilter ? Reported to be working fine on 8.1
In addition to strongst's suggestion, if you're okay with unlocking your bootloader, you could flash a custom kernel and adjust your RGB colour settings with a kernel manager. Of course, unlocking your bootloader will erase your device in the process.
I would recommend against downgrading to stock 7.0 unless you are certain you will not use OTA updates - using OTA updates whilst downgrading is an excellent way to hard brick your device and turn it into an expensive paperweight.
strongst said:
Have you tried https://play.google.com/store/apps/details?id=com.eyefilter.nightmode.bluelightfilter ? Reported to be working fine on 8.1
Click to expand...
Click to collapse
yes i tried that, it does work but just nog as good as the build in blue light filter in 7.1 (for example the top row of icons arent affected)
echo92 said:
In addition to strongst's suggestion, if you're okay with unlocking your bootloader, you could flash a custom kernel and adjust your RGB colour settings with a kernel manager. Of course, unlocking your bootloader will erase your device in the process.
I would recommend against downgrading to stock 7.0 unless you are certain you will not use OTA updates - using OTA updates whilst downgrading is an excellent way to hard brick your device and turn it into an expensive paperweight.
Click to expand...
Click to collapse
If i would install lineage os 14.1 wich is based on android 7.1.2. would that still brick my phone?
can i go back with lineage os based on a older version of andriod or do i need to use a version of lineage os that is at least on par with my current android version (8.1)?
https://forum.xda-developers.com/moto-g4-plus/development/rom-cyanogenmod-14-1-t3522101
Zagre said:
yes i tried that, it does work but just nog as good as the build in blue light filter in 7.1 (for example the top row of icons arent affected)
If i would install lineage os 14.1 wich is based on android 7.1.2. would that still brick my phone?
can i go back with lineage os based on a older version of andriod or do i need to use a version of lineage os that is at least on par with my current android version (8.1)?
https://forum.xda-developers.com/moto-g4-plus/development/rom-cyanogenmod-14-1-t3522101
Click to expand...
Click to collapse
Custom roms won't change your bootloader, so there's no risk to brick your device
strongst said:
Custom roms won't change your bootloader, so there's no risk to brick your device
Click to expand...
Click to collapse
Thanks for the help, i hope installing lineage will fix my problem
strongst said:
Custom roms won't change your bootloader, so there's no risk to brick your device
Click to expand...
Click to collapse
i am looking at the lineage os tutorial: https://wiki.lineageos.org/devices/athene/install. they unlock the bootloader here, but changeing my bootloader could brick my phone, or is unlocking and changeing the bootloader not the same?
Zagre said:
i am looking at the lineage os tutorial: https://wiki.lineageos.org/devices/athene/install. they unlock the bootloader here, but changeing my bootloader could brick my phone, or is unlocking and changeing the bootloader not the same?
Click to expand...
Click to collapse
It's not the same
echo92 said:
In addition to strongst's suggestion, if you're okay with unlocking your bootloader, you could flash a custom kernel and adjust your RGB colour settings with a kernel manager. Of course, unlocking your bootloader will erase your device in the process.
I would recommend against downgrading to stock 7.0 unless you are certain you will not use OTA updates - using OTA updates whilst downgrading is an excellent way to hard brick your device and turn it into an expensive paperweight.
Click to expand...
Click to collapse
to downgrade to nougat do i have to run all normal commands or have to skip any of then?
lucascerqueira said:
to downgrade to nougat do i have to run all normal commands or have to skip any of then?
Click to expand...
Click to collapse
I will preface this with I do not recommend downgrading to Nougat. If you do, do not use OTA updates. Using OTA updates may hard brick your device and we cannot help you then.
If you still really want to downgrade, you will need an unlocked bootloader. That will erase your device, so back up accordingly.
Then, for flashing stock Nougat (if you're previously on stock Oreo - custom ROMs do not count, only stock firmware), you can omit the fastboot OEM lock begin commands. You will not be able to lock your bootloader whilst downgrading. All other fastboot commands as usual (including the erase commands). You may wish to omit GPT and bootloader since you cannot downgrade GPT and bootloader.
The command list would be similar to this:
Code:
[I]fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img[/I]
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.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 system system.img_sparsechunk.7
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
Commands in italics are optional (fastboot will block you and complain of security downgrade errors).