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).
Related
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
This method is only works, if you are in Oreo
unlocked bootloader, and use custom rom,
DISCLAIMER
Not taking responsibility if it goes wrong
We have found a way to get back to stock, and relock the bootloader! for now, it only works for the XT-1635-02 because we dont have a signed stock image for any other phone model.
you can use this on any software channel!
How it works.
YOU NEED TO BE ON A CUSTOM ROM TO RELOCK THE BOOTLOADER!
1 - Download Stock ROM in the first post down below
2 - install adb minimal fastboot
3 - after install adb minimal fastboot, go to the install location and paste all the files there
5 - Copy all commands how is in this site and past it on the cmd screen and wait. (you need to press enter for the last command)
Stock Oreo Signed ROM
If u are in June bootloader Kindly use June Security Patch rom, otherwise, phone should be Brick
June Security Patch
Commands
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
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 system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash system system.img_sparsechunk.11
fastboot flash oem oem.img
fastboot erase carrier
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot oem lock
fastboot oem lock
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 system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash system system.img_sparsechunk.11
fastboot flash boot boot.img
fastboot oem lock
Now youre phone will reboot, and your phone is locked again.
I'm using this ROM here:
[ROM][Stock+] [7.1.1] Dec. Patch NPNS26.118-22-2-12 Prerooted
https://forum.xda-developers.com/moto-z-play/development/rom-nov-patch-npns26-118-22-2-8-t3717037
Do I need to perform any procedures before starting this installation?
I think fast boot erase modemmst 1 & 2 may get a result of IMEI 0 error.
talktosam said:
DISCLAIMER
Not taking responsibility if it goes wrong
We have found a way to get back to stock, and relock the bootloader! for now, it only works for the XT-1635-02 because we dont have a signed stock image for any other phone model.
you can use this on any software channel!
Click to expand...
Click to collapse
talktosam said:
So how does this differ from the method below that was posted here months ago by someone else on doing the same thing? Looks like you copied and pasted....
https://forum.xda-developers.com/moto-z-play/how-to/guide-relock-bootloader-to-lasted-stock-t3718190
Click to expand...
Click to collapse
Jimi Mack said:
talktosam said:
DISCLAIMER
Not taking responsibility if it goes wrong
We have found a way to get back to stock, and relock the bootloader! for now, it only works for the XT-1635-02 because we dont have a signed stock image for any other phone model.
you can use this on any software channel!
Click to expand...
Click to collapse
talktosam said:
So how does this differ from the method below that was posted here months ago by someone else on doing the same thing? Looks like you copied and pasted....
Yes, text is copied, but rom is different Oreo... procedure is same...
https://forum.xda-developers.com/moto-z-play/how-to/guide-relock-bootloader-to-lasted-stock-t3718190
Click to expand...
Click to collapse
Click to expand...
Click to collapse
talktosam said:
Thanks for clearing that up. So the older was to fully restore to Nougat and yours it to restore to Oreo. So being I never updated to Oreo I should restore with the old file, as I am sure yours would cause issues being I never updated to Oreo. You should clearly document that in the thread as well and not just the Title as well if this is the case. Just because most people do not thoroughly read but skim quickly and then jump without looking.
Click to expand...
Click to collapse
Jimi Mack said:
talktosam said:
Thanks for clearing that up. So the older was to fully restore to Nougat and yours it to restore to Oreo. So being I never updated to Oreo I should restore with the old file, as I am sure yours would cause issues being I never updated to Oreo. You should clearly document that in the thread as well and not just the Title as well if this is the case. Just because most people do not thoroughly read but skim quickly and then jump without looking.
Click to expand...
Click to collapse
Yes, if you are in 0xC182 Oreo bootloader, in title i mentioned its works only if u are in oreo bootloader unlocked
Click to expand...
Click to collapse
Can I use this tutorial if I have 0xC114 bootloader (february patch)???
gercdgcat said:
Can I use this tutorial if I have 0xC114 bootloader (february patch)???
Click to expand...
Click to collapse
Yes, but u are in custom rom, u can,
I was in AOSP 8.1 with Oreo bootloader (I had stock oreo before installing the ROM) and just did this procedure, everything went fine ! IMEI is safe and system works as intended, thank you !
If I have the bootloader blocked and I want to update to OREO with your tutorial which commands would I have to skip?
Dude you are a lifesaver..
---------- Post added at 12:32 PM ---------- Previous post was at 12:30 PM ----------
Mario3DS said:
I was in AOSP 8.1 with Oreo bootloader (I had stock oreo before installing the ROM) and just did this procedure, everything went fine ! IMEI is safe and system works as intended, thank you !
Click to expand...
Click to collapse
I am in the exact same situation as you. I will give this a try and report
djdelarosa25 said:
Dude you are a lifesaver..
---------- Post added at 12:32 PM ---------- Previous post was at 12:30 PM ----------
I am in the exact same situation as you. I will give this a try and report
Click to expand...
Click to collapse
Just do exactly what OP says and everything will be fine, I even recovered my Software Channel (attmx) somehow
oh and btw, you can "fix" the navbar bug in stock Oreo changing the theme with Custom Navigation Bar (it's an app)
I just did it and it fixed it completely
Mario3DS said:
Just do exactly what OP says and everything will be fine, I even recovered my Software Channel (attmx) somehow
oh and btw, you can "fix" the navbar bug in stock Oreo changing the theme with Custom Navigation Bar (it's an app)
I just did it and it fixed it completely
Click to expand...
Click to collapse
Your software channel isn't supposed to change anyway
Safety net failed, help
CTS profile match only failed. Is it because of unlocked bootloader?
The bootloader unlocked screen doesn't seem to want to go away
EDIT: My bootloader is still unlocked.
EDIT: Fixed. It wasn't mentioned that you need to enable OEM unlocking in Developer options, noobs like me might get confused. Lucky I got that sorted out
djdelarosa25 said:
The bootloader unlocked screen doesn't seem to want to go away
EDIT: My bootloader is still unlocked.
EDIT: Fixed. It wasn't mentioned that you need to enable OEM unlocking in Developer options, noobs like me might get confused. Lucky I got that sorted out
Click to expand...
Click to collapse
So... Now are you in Oreo stock with locked bootloader? In boot image only shows motorola logo? Nothing of bad key or any notification?
gercdgcat said:
So... Now are you in Oreo stock with locked bootloader? In boot image only shows motorola logo? Nothing of bad key or any notification?
Click to expand...
Click to collapse
Yup, 100% stock. No more bootloader warning message. The guide did not mention that within the custom ROM that you are using, you must have OEM Unlocking under Developer options turned on before you flash the commands.
djdelarosa25 said:
Yup, 100% stock. No more bootloader warning message. The guide did not mention that within the custom ROM that you are using, you must have OEM Unlocking under Developer options turned on before you flash the commands.
Click to expand...
Click to collapse
I think OEM Unlocking only exists in the stock ROM. Regardless of whether you're on a stock ROM already or are flashing the stock ROM, as you mentioned, OEM unlocking must be turned on for the OEM locking commands to work.
Of course, with re-locking your bootloader, it's up to you if you wish to keep OEM Unlocking enabled or disabled afterwards. If you disable it, your device will not be unlockable until you boot into system, which can be more secure but if you have any boot issues, then troubleshooting is a lot more difficult, plus you have no warranty. If you leave OEM unlocking on, then you could unlock your bootloader, but then so can anyone else with physical access to your device.
echo92 said:
I think OEM Unlocking only exists in the stock ROM. Regardless of whether you're on a stock ROM already or are flashing the stock ROM, as you mentioned, OEM unlocking must be turned on for the OEM locking commands to work.
Of course, with re-locking your bootloader, it's up to you if you wish to keep OEM Unlocking enabled or disabled afterwards. If you disable it, your device will not be unlockable until you boot into system, which can be more secure but if you have any boot issues, then troubleshooting is a lot more difficult, plus you have no warranty. If you leave OEM unlocking on, then you could unlock your bootloader, but then so can anyone else with physical access to your device.
Click to expand...
Click to collapse
OEM unlocking also exists in custom ROMs. The reason that relocking your bootloader is not possible with the stock ROM is that the option is greyed out if you have your bootloader unlocked, thus making the bootloader lock commands not work. With a custom ROM, I was able to toggle OEM unlocking on, even when my bootloader was already unlocked. This allowed the bootloader lock commands to work and make the warning message disappear.
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.
Hi All:
I have been running Pixel Experience 8.1 custom rom on my moto G5 plus and have decided I want to stick the stock rom back on and lock the bootloader. Alas I cannot as Any versions of oem.ini etc are lower than the version in Pixel and I cannot downgrade. Can anyone recommend a way round this or am I stuck until the 8.1 official OTA files become available?
Many thanks
phoenix40uk said:
Hi All:
I have been running Pixel Experience 8.1 custom rom on my moto G5 plus and have decided I want to stick the stock rom back on and lock the bootloader. Alas I cannot as Any versions of oem.ini etc are lower than the version in Pixel and I cannot downgrade. Can anyone recommend a way round this or am I stuck until the 8.1 official OTA files become available?
Many thanks
Click to expand...
Click to collapse
Well i was using ArrowOS 9.0 Pie and then I moved to stock and locked my bootloader again. You just need the firmware files. You cannot downgrade so use one of the latest files. I didn't remember on which firmware I was bt while locking the bootloader i used the 137.92-14 and it worked perfectly.
debdeep98 said:
Well i was using ArrowOS 9.0 Pie and then I moved to stock and locked my bootloader again. You just need the firmware files. You cannot downgrade so use one of the latest files. I didn't remember on which firmware I was bt while locking the bootloader i used the 137.92-14 and it worked perfectly.
Click to expand...
Click to collapse
Alas that doesn't work for me. I installed the 137.93-10 firmware then reboot into fastboot and try to run
fastboot oem lock
fastboot oem lock
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 boot boot.img
fastboot oem lock
but I cannot flash any of the files as I get Security version downgrade errors .
phoenix40uk said:
Alas that doesn't work for me. I installed the 137.93-10 firmware then reboot into fastboot and try to run
fastboot oem lock
fastboot oem lock
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 boot boot.img
fastboot oem lock
but I cannot flash any of the files as I get Security version downgrade errors .
Click to expand...
Click to collapse
Do you have the nougat backup files? Did you make any backups? Or try flashing nougat stock zip first then try locking the bootloader. Which firmware were you on when you unlocked?
debdeep98 said:
Do you have the nougat backup files? Did you make any backups? Or try flashing nougat stock zip first then try locking the bootloader. Which firmware were you on when you unlocked?
Click to expand...
Click to collapse
I don't have any backup files but I have the installer for the stock version I mentioned above which is Android 7. I can Flash back to 7 usng the adb push method but I cannot relock my boot loader. Based on that I reckon I must have unlocked the bootlocker while on an Oreo custom.
https://forum.xda-developers.com/g5...flashable-stock-builds-coming-t3830482/page35
New stock oreo firmwares.
dokwhoo said:
https://forum.xda-developers.com/g5...flashable-stock-builds-coming-t3830482/page35
New stock oreo firmwares.
Click to expand...
Click to collapse
sorted after updating to Oreo. Many thanks
phoenix40uk said:
sorted after updating to Oreo. Many thanks
Click to expand...
Click to collapse
i am also on pixel experience and want to go back to stock,
so did u flashed those twrp builds or did something else.
What is the safest way to apply the newest updates? I am still on April, been afraid to do anything without asking first.
Is there a simple way, and will I still be able to unlock/root again?
Same question. Accent being on 'safe'.
SmilingPerson said:
What is the safest way to apply the newest updates? I am still on April, been afraid to do anything without asking first.
Is there a simple way, and will I still be able to unlock/root again?
Click to expand...
Click to collapse
maybeme2 said:
Same question. Accent being on 'safe'.
Click to expand...
Click to collapse
Either flash a custom rom that's been updated with the latest security patch
Or flash an official stock firmware but remember the chances of it being the latest security patch is slim
Obviously if your device is not bootloader unlocked you can't flash custom roms - you can flash official stock firmware via fastboot but I wouldn't bother as you will already be on the latest available firmware so just wait for the next ota update to arrive
TheFixItMan said:
Either flash a custom rom that's been updated with the latest security patch
Or flash an official stock firmware but remember the chances of it being the latest security patch is slim
Obviously if your device is not bootloader unlocked you can't flash custom roms - you can flash official stock firmware via fastboot but I wouldn't bother as you will already be on the latest available firmware so just wait for the next ota update to arrive
Click to expand...
Click to collapse
See this thread ...
https://forum.xda-developers.com/moto-g7/help/ota-rooted-phone-t3956012
I copied out the important parts..
1. Download the latest firmware.
2. Install adb & fastboot
3. Flash with these commands:
Code:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp adspso.bin
fastboot flash dtbo dtbo.img
fastboot flash logo logo.bin
fastboot flash boot boot.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 system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash system_b system_b.img_sparsechunk.2
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot flash vendor vendor.img_sparsechunk.2
fastboot flash oem oem.img
fastboot flash oem_b oem_other.img
DO NOT RUN THIS ONE ---- fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
you will then need to patch boot with magisk again.
TheFixItMan said:
Either flash a custom rom that's been updated with the latest security patch
Or flash an official stock firmware but remember the chances of it being the latest security patch is slim
Obviously if your device is not bootloader unlocked you can't flash custom roms - you can flash official stock firmware via fastboot but I wouldn't bother as you will already be on the latest available firmware so just wait for the next ota update to arrive
Click to expand...
Click to collapse
The latest for the xt1962-1 retail is the August security patch. That's pretty good considering Lenovomoto.
I hit the notice for the June 1, 2019. Failed to install. Tried using the Lenovo Moto Smart Assistant and it bricked my phone. Now have to wait on Motorola to send a replacement. Very frustrated right now. WTF an OTA failed and the LMSA bricked the phone. SMH...
Don't try to apply the updates or LSMA without locking the bootloader (again) first. Afterwards unlock and reroot using same method as before. I'm sure there will be plenty of full wipes so back up accordingly.
zenful said:
Don't try to apply the updates or LSMA without locking the bootloader (again) first. Afterwards unlock and reroot using same method as before. I'm sure there will be plenty of full wipes so back up accordingly.
Click to expand...
Click to collapse
Locking the bootloader is not a cinch either.
Makes you wonder if the safest course might not be to just ignore the updates and stay with the android version you have.
Which is more dangerous, staying with the 'not-updated' working phone or trying to update and risking a bricked phone?
maybeme2 said:
Locking the bootloader is not a cinch either.
Click to expand...
Click to collapse
From my understanding, you need a signed/original boot.img that of which if you didn't make a backup of yours before rooting, than the LSMA can help. I'm thinking removing Magisk and full factory resetting will be necessary as well.
As for obtaining a copy of a signed/official boot.img
sd86 said:
Head on over to https://support.lenovo.com/us/en/downloads/ds101291 and download the tool, after installed put your phone in bootloader/fastboot mode and go through the rescue steps up until the firmware is downloaded, do not click rescue after the firmware is fully downloaded just head on over to C:\ProgramData\LMSA\Download\RomFiles and open the downloaded firmware and take the boot image from there and copy it to your fastboot tools folder and flash that boot.img check that the firmware matches the version installed on your phone before flashing the boot.img.
Click to expand...
Click to collapse
About the
fastboot oem lock
Click to expand...
Click to collapse
skuppej said:
The trick is to run `fastboot oem lock` 3x (not 2x) before flashing boot.img, and then run `fastboot oem lock` one last time after this is done.
Click to expand...
Click to collapse
(Above info found in this thread about relocking the bootloader)
maybeme2 said:
Which is more dangerous, staying with the 'not-updated' working phone or trying to update and risking a bricked phone?
Click to expand...
Click to collapse
I can't give you a definite answer, but the way I perceive this is;
Should I keep a version of my OS that does not have the most recent security updates but has been rooted?
Click to expand...
Click to collapse
I hope this info helps and brings some clarity for you.
zenful said:
Don't try to apply the updates or LSMA without locking the bootloader (again) first. Afterwards unlock and reroot using same method as before. I'm sure there will be plenty of full wipes so back up accordingly.
Click to expand...
Click to collapse
Phone was locked and not rooted. It's now FUBAR and Moto is sending me a replacement.