Related
My Phone Info:
Single sim 2gb ram + 16gb rom
Hello folks I've been searching for a nougat update for XT-1644, but unable to find over the xda if anyone of you havs upgraded your xt-1644 then kindly tell the procedure here, Thanks.
Here is my About Phone Info.
http://cloud.tapatalk.com/s/589c8f61b2eab/Screenshot_20170209-203359.png
http://cloud.tapatalk.com/s/589c8f48b01b2/Screenshot_20170209-203401.png
You mean a method like this? https://forum.xda-developers.com/moto-g4-plus/how-to/xt1644-stock-marshmallow-to-nougat-t3540022
If you download the 93-14 Nougat firmware, that's the latest version. Nougat OTAs currently only exist for the 93-11 firmware.
echo92 said:
You mean a method like this? https://forum.xda-developers.com/moto-g4-plus/how-to/xt1644-stock-marshmallow-to-nougat-t3540022
If you download the 93-14 Nougat firmware, that's the latest version. Nougat OTAs currently only exist for the 93-11 firmware.
Click to expand...
Click to collapse
Sorry didn't find that,
One more question i have unlocked my bootloader will it work? I mean will i be able to flash this 7.0?
waseemmayaa said:
Sorry didn't find that,
One more question i have unlocked my bootloader will it work? I mean will i be able to flash this 7.0?
Click to expand...
Click to collapse
Yes, your bootloader status won't matter - as long as that's all you've done. As I understand it, the update via stock recovery only cares if the rest of your phone has been modified - if you've still got a stock bootloader, stock recovery and stock kernel (from MM, provided it's up to date), it should work and you should be eligible for future OTAs.
The only hurdle I could see happening is that the build of Marshmallow expected by the OTA and your phone's current OS build do not match, in which case it won't install. Thus, you may have to consult one of the fastboot Nougat 93-11 or 93-14 threads to install, which you'll have to do if your system is modified past the bootloader.
Here are a couple for your perusal:
https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369
https://forum.xda-developers.com/moto-g4-plus/how-to/android-7-0-install-nougat-official-t3531612
echo92 said:
Yes, your bootloader status won't matter - as long as that's all you've done. As I understand it, the update via stock recovery only cares if the rest of your phone has been modified - if you've still got a stock bootloader, stock recovery and stock kernel (from MM, provided it's up to date), it should work and you should be eligible for future OTAs.
The only hurdle I could see happening is that the build of Marshmallow expected by the OTA and your phone's current OS build do not match, in which case it won't install. Thus, you may have to consult one of the fastboot Nougat 93-11 or 93-14 threads to install, which you'll have to do if your system is modified past the bootloader.
Here are a couple for your perusal:
https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369
https://forum.xda-developers.com/moto-g4-plus/how-to/android-7-0-install-nougat-official-t3531612
Click to expand...
Click to collapse
Thanks for the brief info, it means i have to flash it via fastboot and if that works fine then I'll be able to get OTA, but for your info, I've unlocked bootloader and installed Official TWRP but if i flash any of the firmware (given above) will i face bootloop kinda stuffs? I am scared if something goes wrong then i will even not able to restore nandroid backup. Hope you gotta help me.
Thanks.
waseemmayaa said:
Thanks for the brief info, it means i have to flash it via fastboot and if that works fine then I'll be able to get OTA, but for your info, I've unlocked bootloader and installed Official TWRP but if i flash any of the firmware (given above) will i face bootloop kinda stuffs? I am scared if something goes wrong then i will even not able to restore nandroid backup. Hope you gotta help me.
Thanks.
Click to expand...
Click to collapse
I see you've received a response in the other thread regarding if XT1644 will accept the update; given you've flashed TWRP, if you wish to be very safe, I would suggest re-installing your Marshmallow ROM so you have a stock install before proceeding to Nougat. There's nothing stopping you from directly flashing Nougat, and the fastboot method for either Nougat build may correctly overwrite the relevant files, the only way is to try the procedure. Don't use the TWRP backup images of Nougat - they don't contain updates to your baseband modem and other core parts of your device - they are only meant to be used once your entire phone is updated to Nougat.
If you wish to restore back to stock MM before flashing Nougat, here's links to stock firmware for XT1644: https://forum.xda-developers.com/moto-g4-plus/how-to/xt1644-firmware-t3454980
But either way, read all the instructions first, ensure you've got all the firmware and tools you need installed/downloaded, your phone has at least 50 % battery and plenty of time, and you should be okay.
I am not responsible for your bricked phone or pigeon poo on your toupe. Do at your own risk.
Many thanks to @SupahCookie for idea and motivation!
INTENTIONALLY DOES --NOT-- LOCK BOOTLOADER!!!
Get factory images here:
https://forum.xda-developers.com/mo...ock-images-t3736767/post75236696#post75236696
THIS GUIDE IS FOR FACTORY/STOCK ROMs - NOT YOUR AVERAGE CUSTOM ROM which may not have bootloaders!!! (thanks!!!!! @echo92 )
FIX:
IF YOU ARE ABLE TO GET TO FASTBOOT THIS SHOULD WORK.
IF YOU HAVE 8.x bootloaders AND ARE DOWNGRADING TO 7, use "Alternative to RSDlite" below.
1 boot to win - 7 or 10 works fine.
2 boot phone to fastboot, and connect phone to computer.
3 start RSDlite
pick a ROM. I believe I used a 7.1.1 rom
3Nov9-ADDISON_NPNS26.118-22-2-8_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
RSDlite installed it and fixed the problem.
- -
I was then able to use RSDlite to install @rafikowy 's signed 8.0 . - going up from 7 to 8.
- -
- -
If you are on 8.x bootloaders and want to go to 7.x bootloaders, use this (RSDlite throws an error and stops):
ALTERNATIVE TO RSDlite:
1 I used 7zip to extract that 7.1.1 zip (or any ROM zip) into a folder x,
2 add all the adb and fastboot junk to folder x,
3 add the attached file (rename it to flash.bat) to folder x.
4 boot phone to fastboot and connect to computer.
5 click on flash.bat - it throws a lot of "slot" errors but works just fine.
6 reboot your phone if it hasn't already and go through the 7.x install stuffs.
7 you will not show an IMEI if you are coming from an 8.x bootloader. However, it IS there.
NOTE: you may need to add a line to the flash.bat if there are more/less sparsechunk's in your FACTORY/STOCK ROM...
THIS IS NOT FOR CUSTOM ROMs!!!!!!!
EDIT: 3-8-19: I just did this myself to go back very briefly to 7.1 - be sure you don't flash TWRP to it if your going to take OTAs - it will brick it. boot to TWRP if you need TWRP briefly: fastboot boot twrpimg.img
----------
If you can boot to fastboot screen, you can do anything.
Never OTA a ROM if you have modified recovery (TWRP, etc) or if magisk is present.
https://forum.xda-developers.com/mo...p-flashing-t3813498/post77011495#post77011495
I changed the attached file to add pause and reboot and exit to make it slightly more automated.
I have successfully used this many times going back and forth. If you can boot to fastboot screen, you can save your phone and flash anything you want.
You may wish to advise users that if they downgrade to Nougat not to use Nougat OTA updates. The reason being that a downgraded stock Oreo device may still have the Oreo bootloader on it. Thus, attempting to use Nougat OTA updates may hard brick their device (as the bootloader is likely corrupted, meaning no fastboot).
Users could either use the Feb 2018 NPN26.118-22-2-17 firmware from your link https://mirrors.lolinet.com/firmware/moto/addison/official/RETAIL/ as that was the last Nougat firmware (and thus no Nougat OTA updates) or avoid using OTA updates whilst downgraded.
echo92 said:
You may wish to advise users that if they downgrade to Nougat not to use Nougat OTA updates. The reason being that a downgraded stock Oreo device may still have the Oreo bootloader on it. Thus, attempting to use Nougat OTA updates may hard brick their device (as the bootloader is likely corrupted, meaning no fastboot).
Users could either use the Feb 2018 NPN26.118-22-2-17 firmware from your link https://mirrors.lolinet.com/firmware/moto/addison/official/RETAIL/ as that was the last Nougat firmware (and thus no Nougat OTA updates) or avoid using OTA updates whilst downgraded.
Click to expand...
Click to collapse
Interesting. I used the above GUIDE to go up and down a number of times on my phone (about 20 total) , installing and running on both 7 and 8, and then went down to a Nov 7.1.1 and let it ota all the way up to 8.0 and that is what I am using now. I found that when i used a factory zip, and the above procedure, it corrected the bootloaders to the appropriate version that i was flashing - either RSDlite or the more manual path which ignores the errors worked for me.
Using the above procedure , you get the correct bootloaders, which are in the zip.
Please correct me if i am wrong!
KrisM22 said:
Interesting. I used the above GUIDE to go up and down a number of times on my phone (about 20 total) , installing and running on both 7 and 8, and then went down to a Nov 7.1.1 and let it ota all the way up to 8.0 and that is what I am using now. I found that when i used a factory zip, and the above procedure, it corrected the bootloaders to the appropriate version that i was flashing - either RSDlite or the more manual path which ignores the errors worked for me.
Using the above procedure , you get the correct bootloaders, which are in the zip.
Please correct me if i am wrong!
Click to expand...
Click to collapse
That's intriguing - we saw previously on Z Play that users downgrading their stock firmware (e.g. https://forum.xda-developers.com/moto-z-play/help/hard-brick-moto-z-play-patch-abril-t3782927 )and then using OTA updates hard bricked their device (hence the number of users asking for a blankflash, as fastboot no longer works). I don't know if these users hard bricked by downgrading their firmware too far and then flashed an OTA radically different to their previous firmware, or whether it's a risk that's taken by any downgrading of firmware.
When you used fastboot, did you see any 'security downgrade errors' when you flashed the bootloader, and is your bootloader version now C180, as you've flashed the Oreo OTA?
echo92 said:
That's intriguing - we saw previously on Z Play that users downgrading their stock firmware (e.g. https://forum.xda-developers.com/moto-z-play/help/hard-brick-moto-z-play-patch-abril-t3782927 )and then using OTA updates hard bricked their device (hence the number of users asking for a blankflash, as fastboot no longer works). I don't know if these users hard bricked by downgrading their firmware too far and then flashed an OTA radically different to their previous firmware, or whether it's a risk that's taken by any downgrading of firmware.
When you used fastboot, did you see any 'security downgrade errors' when you flashed the bootloader, and is your bootloader version now C180, as you've flashed the Oreo OTA?
Click to expand...
Click to collapse
YES - that's why I wrote these 3 guides - before, it was quite possible to wind up with a bootloader mix - esp depending on the zip you use! - factory/stock only!!!
I added a line to the guide saying that it is only intended to be used for the factory/stock zips as these have (I believe) the bootloaders appropriate to the ROM.
Many thanks for pursuing this! - I wonder if we'll have to exclude certain ROMs that are in the factory lists?????
echo92 said:
That's intriguing - we saw previously on Z Play that users downgrading their stock firmware (e.g. https://forum.xda-developers.com/moto-z-play/help/hard-brick-moto-z-play-patch-abril-t3782927 )and then using OTA updates hard bricked their device
Click to expand...
Click to collapse
If you have TWRP (or I assume any custom recovery) present when you try to ota, it can download just fine and then reboot to the update. I had TWRP and wound up in a situation where my phone would only boot to twrp no matter what I flashed or restored. I booted phone to fastboot, RSDlite'ed that 11-09-17 factory zip and all was well. In that particular case I did not fully install 7.x but immediately RSDlite'ed rafikowy's 8.0 signed stock and went on with my testing. Since then I always boot to TWRP rather than intalling it and do my thing. (thanks @jceballos )
When you used fastboot, did you see any 'security downgrade errors' when you flashed the bootloader, and is your bootloader version now C180, as you've flashed the Oreo OTA?
Click to expand...
Click to collapse
Sorry - since it throws a million errors I never look at it if it works.
The particular build I am on at the moment - is BL: C1.82
This one started from that Nov '17 build and ota'ed all the way to 8.0 Apr.
I root and unroot as needed per rafikowy's method but using a boot to TWRP - never an install TWRP.
I'll put up a new guide ref ota and recovery and brick.
KrisM22 said:
If you have TWRP (or I assume any custom recovery) present when you try to ota, it can download just fine and then reboot to the update. I had TWRP and wound up in a situation where my phone would only boot to twrp no matter what I flashed or restored. I booted phone to fastboot, RSDlite'ed that 11-09-17 factory zip and all was well. In that particular case I did not fully install 7.x but immediately RSDlite'ed rafikowy's 8.0 signed stock and went on with my testing. Since then I always boot to TWRP rather than intalling it and do my thing. (thanks @jceballos )
Sorry - since it throws a million errors I never look at it if it works.
The particular build I am on at the moment - is BL: C1.82
This one started from that Nov '17 build and ota'ed all the way to 8.0 Apr.
I root and unroot as needed per rafikowy's method but using a boot to TWRP - never an install TWRP.
I'll put up a new guide ref ota and recovery and brick.
Click to expand...
Click to collapse
1) If you have TWRP, then using an OTA will fail - as you've not got stock recovery (and likely other modifications, including possibly a system partition set to read-write status). As you noted, having TWRP seems to cause a bootloop when rebooting - I'm not sure if the OTA sets a boot flag to stay in recovery until the update is completed. For the G4/Plus, there's a possible solution by wiping the misc partition but I don't know if there's a similar partition for Z Play devices: https://forum.xda-developers.com/moto-g4/help/troubleshooting-twrp-boot-loop-ota-t3714325
The only other solution I've seen is a clean flash of the stock ROM to get your device booting properly.
Booting to TWRP rather than flashing would mean your stock recovery is still present on your device. The only downside is if you need to make modifications, you'd need your computer to boot to TWRP.
2)BL C1.82 seems to be the bootloader provided by the Oreo April 2018 security patch update, so your device looks to be on the right bootloader. It's still curious that the Nov 2017 firmware worked whereas countless other 'factory' stock ROMs caused hard bricks when downgraded to and then OTA updates were installed.
As you mentioned, custom ROMs don't have bootloaders and thus don't care about your bootloader version usually (though I've seen some ROMs require a certain bootloader). However, stock ROMs and stock OTA updates do have bootloaders, which is why downgrading can be risky.
echo92 said:
1) If you have TWRP, then using an OTA will fail - as you've not got stock recovery (and likely other modifications, including possibly a system partition set to read-write status). As you noted, having TWRP seems to cause a bootloop when rebooting - I'm not sure if the OTA sets a boot flag to stay in recovery until the update is completed. For the G4/Plus, there's a possible solution by wiping the misc partition but I don't know if there's a similar partition for Z Play devices: https://forum.xda-developers.com/moto-g4/help/troubleshooting-twrp-boot-loop-ota-t3714325
The only other solution I've seen is a clean flash of the stock ROM to get your device booting properly.
Booting to TWRP rather than flashing would mean your stock recovery is still present on your device. The only downside is if you need to make modifications, you'd need your computer to boot to TWRP.
2)BL C1.82 seems to be the bootloader provided by the Oreo April 2018 security patch update, so your device looks to be on the right bootloader. It's still curious that the Nov 2017 firmware worked whereas countless other 'factory' stock ROMs caused hard bricks when downgraded to and then OTA updates were installed.
As you mentioned, custom ROMs don't have bootloaders and thus don't care about your bootloader version usually (though I've seen some ROMs require a certain bootloader). However, stock ROMs and stock OTA updates do have bootloaders, which is why downgrading can be risky.
Click to expand...
Click to collapse
Downgrading is a piece of cake if you don't use RSDlite - it throws an error and stops. Using the bat file it can happily throw all the errors it wants and all I care is at the end I have what I want.
It does indeed change the entire environment when you bat file the zip contents. You can bat file to get from 8 to 7 and then use RSDlite to flash a different 7 OR 8 zip file. There is no resulting difference in whether you RSDlite it or bat file it - the bat file simply comes from the .xml file that is within the zip. There is very little or no difference between that among addison factory/stock zips. Other zips are different (custom ROMs.)
Grab any factory/stock zip for addison and expand it and you will see modems, bootloaders, indeed absolutely everything you would find on that phone if you went to a store and bought it. SupahCookie simply added a couple lock command lines because it was intended for folks who somehow thought that if phone was locked they could take it back to the store and get their money back. Or some such. I found that ATT folk didn't care if you were on CM or whatever if you just needed to swap SIMs or whatever.
I DON'T want to lock the phone as it prevents me from modifying forever. Oh yeah that reminds me I was going to post the obligatory guide (again) about how to flash a white boot logo so you don't get that message - it's still there LOL but since the font is in white, you can't see it.
I have a Moto Z2 Play and used this to get out of a rather sticky situation.. My IEMI shows 0 now and I'm curious if there's a way to fix this? Also, You say you've done OTA updates? My phone is telling my I have some, is it safe to try?
Necrowr said:
I have a Moto Z2 Play and used this to get out of a rather sticky situation.. My IEMI shows 0 now and I'm curious if there's a way to fix this? Also, You say you've done OTA updates? My phone is telling my I have some, is it safe to try?
Click to expand...
Click to collapse
Thanks for feedback and great on success.
IMEI will show zero if using oreo, It will show again if using N. Remember that if you go from O to N you need to use the "Alternative to RSD" as RSD will simply throw an error and stop.
If you have TWRP and/or Magisk you must get rid of them before ota - if twrp present you will soft brick and have to do alternative again - flash a stock recovery. Simply uninstalling/flash magisk will probably not be enough - it will likely d/l but error part way through update. If you are sitting on rafikowy's stock oreo, and haven't modified it, you should be fine. I know Apr and June are out there. I flashed his stock 8.0 and took June fine. Z2 should be no different though of course I can't guarantee it
If you have success, let us know what you have done so others looking in will know. Thanks!
KrisM22 said:
Thanks for feedback and great on success.
IMEI will show zero if using oreo, It will show again if using N. Remember that if you go from O to N you need to use the "Alternative to RSD" as RSD will simply throw an error and stop.
If you have TWRP and/or Magisk you must get rid of them before ota - if twrp present you will soft brick and have to do alternative again - flash a stock recovery. Simply uninstalling/flash magisk will probably not be enough - it will likely d/l but error part way through update. If you are sitting on rafikowy's stock oreo, and haven't modified it, you should be fine. I know Apr and June are out there. I flashed his stock 8.0 and took June fine. Z2 should be no different though of course I can't guarantee it
If you have success, let us know what you have done so others looking in will know. Thanks!
Click to expand...
Click to collapse
I actually flashed to this: ALBUS_C_7.1.1_NPS26.118-24_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip Which is a 7.1.1 variant and it is showing 0 when I check settings and when I dial *#06#. However upon connecting to the computer and running mfastboot getvar imei it returned a value. I only did the steps above which would mean I don't have TWRP or Magisk (when I fastboot and click recovery I get "no command")
****** Additional information *********
XT1710-01 Duel Sim Variant
I started your steps, only being able to access fastboot. The device would throw an error (I don't recall exactly but it ended up showing me them in the bootloader logs) whenever I tried to start it, or go to recovery. #DefinitelyThoughtItWasDead
Necrowr said:
I actually flashed to this: ALBUS_C_7.1.1_NPS26.118-24_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip Which is a 7.1.1 variant and it is showing 0 when I check settings and when I dial *#06#. However upon connecting to the computer and running mfastboot getvar imei it returned a value. I only did the steps above which would mean I don't have TWRP or Magisk (when I fastboot and click recovery I get "no command")
****** Additional information *********
XT1710-01 Duel Sim Variant
I started your steps, only being able to access fastboot. The device would throw an error (I don't recall exactly but it ended up showing me them in the bootloader logs) whenever I tried to start it, or go to recovery. #DefinitelyThoughtItWasDead
Click to expand...
Click to collapse
What rom was on phone when you got it and what have you done to it? Has it ever run 8.x?
original country of phone?
The bat file will always throw a lot of slot errors.
https://mirrors.lolinet.com/firmware/moto/albus/official/RETUS/
or
https://mirrors.lolinet.com/firmware/moto/albus/official/RETAIL/
might have some stock ROMs of interest...
KrisM22 said:
What rom was on phone when you got it and what have you done to it? Has it ever run 8.x?
original country of phone?
The bat file will always throw a lot of slot errors.
might have some stock ROMs of interest...
Click to expand...
Click to collapse
It had 7.1.1 stock. I rooted it, and then flashed Resurrection Remix (which was yes 8.1 I believe) and the upgraded bootloader. I then found out my service wouldn't work with that.. so I attempted to flash back to stock which gave me a flurry of issues.. eventually getting to nothing but fastboot working. Flashed back to working with your guide to 7.1.1
If it helps in in fastboot it tells me BL: C0.CD
Necrowr said:
It had 7.1.1 stock. I rooted it, and then flashed Resurrection Remix (which was yes 8.1 I believe) and the upgraded bootloader. I then found out my service wouldn't work with that.. so I attempted to flash back to stock which gave me a flurry of issues.. eventually getting to nothing but fastboot working. Flashed back to working with your guide to 7.1.1
If it helps in in fastboot it tells me BL: C0.CD
Click to expand...
Click to collapse
Custom ROMs won't usually update the bootloader (even if they are newer) as stock ROMs typically only have the bootloader firmware.
You could look into flashing the stock Oreo albus 8.0 ROM https://forum.xda-developers.com/z2-play/how-to/fastboot-rom-oreo-retail-via-fastboot-t3786153 or the 8.0 June 2018 firmware https://forum.xda-developers.com/z2-play/how-to/fastboot-rom-albusretail8-0-0opss27-76-t3822195 but please check that firmware has been released for your device variant.
I don't know if updating your baseband to stock Oreo formally may fix your IMEI issue.
Necrowr said:
It had 7.1.1 stock. I rooted it, and then flashed Resurrection Remix (which was yes 8.1 I believe) and the upgraded bootloader. I then found out my service wouldn't work with that.. so I attempted to flash back to stock which gave me a flurry of issues.. eventually getting to nothing but fastboot working. Flashed back to working with your guide to 7.1.1
If it helps in in fastboot it tells me BL: C0.CD
Click to expand...
Click to collapse
"BL: C0.CD" even right after flashing that albus 7.1.1 using "alternative" above?
What happens if you flash one of the oreo roms from the links I gave you above?
Yeah, RR wouldn't change bootloaders... so you upgraded bootloaders independendently?- that could easily lead to a soft brick... -
I read RR on Z2 and it says nothing about bootloaders even though it says 8.1 based, so i wonder if it needs 7.x bootloaders? I did not read entire thread...
In a reverse, I would wonder if you put an 8 on there if you wouldn't see your IMEI. (On the Z if you flash 8 You won't see the IMEI until you return to 7.)(wondering if z2 is reversed)
KrisM22 said:
"BL: C0.CD" even right after flashing that albus 7.1.1 using "alternative" above?
What happens if you flash one of the oreo roms from the links I gave you above?
Yeah, RR wouldn't change bootloaders... so you upgraded bootloaders independendently?- that could easily lead to a soft brick... -
I read RR on Z2 and it says nothing about bootloaders even though it says 8.1 based, so i wonder if it needs 7.x bootloaders? I did not read entire thread...
In a reverse, I would wonder if you put an 8 on there if you wouldn't see your IMEI. (On the Z if you flash 8 You won't see the IMEI until you return to 7.)(wondering if z2 is reversed)
Click to expand...
Click to collapse
Yes, right after flashing that is the BL that fastboot is showing me. I don't recall updating the bootloader so to speak, however RR did require an updated variant of twrp which I flashed 3.2.2 I believe to get (unsure if that would have changed the bootloader or not). I also tried flashing a stock Oreo (which you've stated stock Roms usually only have the bootloaders so maybe somewhere during this process I updated it?). I wish I had all the notes for what I did to give more precise information, but I'm in a position where I really need my phone so I kinda just panicked and started flashing things when my service wouldn't work.
I'm highly considering trying to run an OTA (though very afraid of bricking). - On a side note though, it wouldn't even tell me I had OTA's until I did the steps in the original post here (doing the different 7.1.1. and 8.0 flashes, it wouldn't ever tell me I had updates, and now it does).
*** Edit ***
Looks like I'm able to enter stock recovery, which makes me believe everything is stock at the moment.
Necrowr said:
Yes, right after flashing that is the BL that fastboot is showing me. I don't recall updating the bootloader so to speak, however RR did require an updated variant of twrp which I flashed 3.2.2 I believe to get (unsure if that would have changed the bootloader or not). I also tried flashing a stock Oreo (which you've stated stock Roms usually only have the bootloaders so maybe somewhere during this process I updated it?). I wish I had all the notes for what I did to give more precise information, but I'm in a position where I really need my phone so I kinda just panicked and started flashing things when my service wouldn't work.
I'm highly considering trying to run an OTA (though very afraid of bricking). - On a side note though, it wouldn't even tell me I had OTA's until I did the steps in the original post here (doing the different 7.1.1. and 8.0 flashes, it wouldn't ever tell me I had updates, and now it does).
*** Edit ***
Looks like I'm able to enter stock recovery, which makes me believe everything is stock at the moment.
Click to expand...
Click to collapse
If you flashed a stock O that would have changed bl to O, but doing the above with the stock 7.1.1 would have changed them back to N. No matter (other than academic) that you don't remember the path - flashing a stock anything reverts it to that point in time. However, IMEI may have been moved - don't know. It will likely show on EITHER 7.x or 8.x stock - just don't know which.
If you flash a stock 8.x from those links I gave you above, it should offer you ota, ASSUMING there are any at this point in time(Z has 2). Adding Magisk at any point seems to hose you for receiving any more ota's - don't understand why, even with magisk uninstall, so that would mean going back to the latest stock and losing what you have (which is why I try to take a TBPro and copy that backup to PC (because re-flashing 8.x stock will likely reset internal storage.).
yes, if you enter stock recovery, you are likely at stock, though you could reflash the latest 7 or 8 stock to be sure, depending on which you want to use as base. Since 8 is having security fixes released, I choose 8 and will likely have no more interest (no time!) in 7.
So, ran the OTA and it was fine running the update and staying on N. I also downloaded the OTA for Oreo, when trying to update the recovery error'd out. It looked like the error said "Error in modem unexpected results" or something similar.
Necrowr said:
So, ran the OTA and it was fine running the update and staying on N. I also downloaded the OTA for Oreo, when trying to update the recovery error'd out. It looked like the error said "Error in modem unexpected results" or something similar.
Click to expand...
Click to collapse
did it offer to let you d/l it again? you could try that.
However, there exist O stock zips in those links I gave you so you could just flash the latest...
Hello everyone, i installed the leaked soak test with the "apply update from SD card" on stock recovery after locking my bootloader.
One week later, i unlocked it again and flashed TWRP for rooting with magisk.
Even with root tweaks i still face problems with soak 8.1, due to the lack of custom kernels.
So i decided to flash Stock N (1st April) with the TWRP Flashable zip from @Jleeblanch , how i avoid IMEI loss doing that? If i backup Oreo's EFS with TWRP, it will be compatible if i try to restore it after flashing, or it's not even necessary?
The TWRP flashable zip files by @Jleeblanch does not have the commands "fastboot erase modemst1" and "fastboot erase modemst2" so your IMEI will be fine. However Stock Oreo does mess up with IMEI.
Flash TWRP flashable Stock Nougat by Jleeblanch. You will not lose IMEI, but there will still be a problem of persist (i.e you will lost IMEI if you flash Stock ROM via fastboot). So to fix persist, follow this thread: [Guide] [XT16XX] [Solve] Moto G4/Plus IMEI=0 issue
Losing IMEI is a persist related problem (Soak Test 8.1, and all 64bit Pie ROMs are causing this). So if you fix persist, then you will never lose IMEI.
I recommend you to take backup of EFS before this process (i.e while having a bad persist and working EFS) and also after fixing persist (i.e while having a good persist and working EFS).
EFS backup by Lyuu's TWRP takes a backup of EFS, fsg and persist.
Since you upgraded to Soak test from a locked bootloader, I strongly oppose moving back to Stock Nougat. Even if you go back to Nougat, MAKE SURE THAT YOU NEVER DO ANY OTA UPDATE. Whenever Official Oreo comes out, either flash it by fastboot or by TWRP flashable zip file (Jleeblanch said that he will make one for Official Oreo too once it's released)
Heeth21 said:
The TWRP flashable zip files by @Jleeblanch does not have the commands "fastboot erase modemst1" and "fastboot erase modemst2" so your IMEI will be fine. However Stock Oreo does mess up with IMEI.
Flash TWRP flashable Stock Nougat by Jleeblanch. You will not lose IMEI, but there will still be a problem of persist (i.e you will lost IMEI if you flash Stock ROM via fastboot). So to fix persist, follow this thread: [Guide] [XT16XX] [Solve] Moto G4/Plus IMEI=0 issue
Losing IMEI is a persist related problem (Soak Test 8.1, and all 64bit Pie ROMs are causing this). So if you fix persist, then you will never lose IMEI.
I recommend you to take backup of EFS before this process (i.e while having a bad persist and working EFS) and also after fixing persist (i.e while having a good persist and working EFS).
EFS backup by Lyuu's TWRP takes a backup of EFS, fsg and persist.
Since you upgraded to Soak test from a locked bootloader, I strongly oppose moving back to Stock Nougat.
Click to expand...
Click to collapse
Rajat's 64bit TWRP doesn't have EFS Backup option here. I will try Lyuu's
Thanks for the help.
xSamukaBRx said:
Rajat's 64bit TWRP doesn't have EFS Backup option here. I will try Lyuu's
Thanks for the help.
Click to expand...
Click to collapse
Read the second post again, I have edited it.
Heeth21 said:
Since you upgraded to Soak test from a locked bootloader, I strongly oppose moving back to Stock Nougat. Even if you go back to Nougat, MAKE SURE THAT YOU NEVER DO ANY OTA UPDATE. Whenever Official Oreo comes out, either flash it by fastboot or by TWRP flashable zip file (Jleeblanch said that he will make one for Official Oreo too once it's released)
Click to expand...
Click to collapse
I kinda fear it auto-updating, so i'll make sure to delete the "3c_ota" app from /priv-app
EDIT: Already know the risks of taking OTA with unlocked bootloader or after downgrade...
Heeth21 said:
Since you upgraded to Soak test from a locked bootloader, I strongly oppose moving back to Stock Nougat. Even if you go back to Nougat, MAKE SURE THAT YOU NEVER DO ANY OTA UPDATE. Whenever Official Oreo comes out, either flash it by fastboot or by TWRP flashable zip file (Jleeblanch said that he will make one for Official Oreo too once it's released)
Click to expand...
Click to collapse
What about Lineage-based 7.1.2 32 bits ROMs? Can i flash them without issue? Already flashed Stock N
with TWRP, and It worked fine. Just want to know.
Please don't tell me i need the fastboot Stock N, i can't flash that anymore i think. :crying:
xSamukaBRx said:
What about Lineage-based 7.1.2 32 bits ROMs? Can i flash them without issue? Already flashed Stock N
with TWRP, and It worked fine. Just want to know.
Please don't tell me i need the fastboot Stock N, i can't flash that anymore i think. :crying:
Click to expand...
Click to collapse
Yes you can flash Custom ROMs from TWRP, however, I don't think you should right now.
I got my device hard bricked randomly from Custom ROM. idk what caused it, maybe some changes which I did or something else. If a similar thing were to happen with you, there's no guarantee whether the current blankflash would work or not.
Heeth21 said:
Yes you can flash Custom ROMs from TWRP, however, I don't think you should right now.
I got my device hard bricked randomly from Custom ROM. idk what caused it, maybe some changes which I did or something else. If a similar thing were to happen with you, there's no guarantee whether the current blankflash would work or not.
Click to expand...
Click to collapse
Even through i just want a pure lineage OS instead of a custom based on it (too many stuff comes with a risk, right?), i better not try...
Hey guys, I tried flashing the stock moto oreo rom (october patch) through 1. flashing via fastboot and 2. twrp flashable rom.
Both methods worked but I lost my IMEI, regardless of which method I flashed the rom with.
I had made two EFS & Persist backups (one from resurrection remix rom and one from a twrp nougat june patch rom) and tried to restore them after flashing the moto oreo rom, but no success.
Can anyone help me with this? I really want to use the stock oreo rom!
Please help guys!
What version of twrp?
twrp which error during restore?
Ever flashed someone else's persist file when you were on stock?
I too am in the same boat, I upgraded to 8with the smart assist no isshes. and when trying to restore my efs and persits (backed up from android 7) with twrp it just doesnt work, hope someone has a fix
twrp-3.2.3-1-potter
for me
my imei also shows up in my settings but doenst work
vonwap said:
I too am in the same boat, I upgraded to 8with the smart assist no isshes. and when trying to restore my efs and persits (backed up from android 7) with twrp it just doesnt work, hope someone has a fix
twrp-3.2.3-1-potter
for me
my imei also shows up in my settings but doenst work
Click to expand...
Click to collapse
Refer to this post - https://forum.xda-developers.com/showpost.php?p=77359949&postcount=2
And the FAQ "On soak test 2 or later, I have my IMEI but no signal. What can I do?"
NZedPred said:
Refer to this post - https://forum.xda-developers.com/showpost.php?p=77359949&postcount=2
And the FAQ "On soak test 2 or later, I have my IMEI but no signal. What can I do?"
Click to expand...
Click to collapse
Thank you
I installed the twrp flashable stock and I got my 3g back, i did the OTA update and now I think its bricked, It will only boot to twrp :crying:
vonwap said:
Thank you
I installed the twrp flashable stock and I got my 3g back, i did the OTA update and now I think its bricked, It will only boot to twrp :crying:
Click to expand...
Click to collapse
Try flashing one of the full flashable zips from that thread, get the last one. But in the installer, do not select firmware.
Hopefully that will get you going again. And no, don't ever install an ota.
NZedPred said:
Try flashing one of the full flashable zips from that thread, get the last one. But in the installer, do not select firmware.
Hopefully that will get you going again. And no, don't ever install an ota.
Click to expand...
Click to collapse
Thanks for all your help is there any way to fix OTA updates? like relocking bootloader? or should I just leave that unlocked ?
I just installed \POTTER_NPNS25.137-93-4_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
and am getting a 3g \ H signal now but its a different sim card and service from original card, seems to be working now
Is it just oreo that screws everything up , I know this is all over but its not very straight forward
im no android expert clearly
vonwap said:
Thanks for all your help is there any way to fix OTA updates? like relocking bootloader? or should I just leave that unlocked ?
I just installed \POTTER_NPNS25.137-93-4_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
and am getting a 3g \ H signal now but its a different sim card and service from original card, seems to be working now
Is it just oreo that screws everything up , I know this is all over but its not very straight forward
im no android expert clearly
Click to expand...
Click to collapse
Bootloader doesn't matter, can stay unlocked.
And the IMEI/4g problem is Nougat only, never heard of someone who lost something on Oreo or when updating to it.
If you flash latest Oreo firmware for your region (endings with 17-xx are US, 13-xx is for the rest as far as I know) you should be good to go.
Just got the xt1687 usa model retus software channel... Is it safe to flash potter roms on here?
itcanbdone said:
Just got the xt1687 usa model retus software channel... Is it safe to flash potter roms on here?
Click to expand...
Click to collapse
What firmware? 7.0 or 8.1? If you are on 8.1 it's as safe as it ever is to flash a custom ROM.
If you're still on 7.0 you should update first and in any case make a full nandroid backup incl. Persist and EFS before you flash anything.
Sent from my Moto G5 Plus using XDA Labs
Currently on 7.0 so unlock bootloader n twrp after update? Thanks
itcanbdone said:
Currently on 7.0 so unlock bootloader n twrp after update? Thanks
Click to expand...
Click to collapse
Yes. If you can update via OTA that should be the way to go. If you can't flash full Motorola signed fastboot 8.1 firmware:
https://mirrors.lolinet.com/firmware/moto/potter/official/
Unlock the BL on Motorola website, boot to or flash TWRP and make a full nandroid incl. persist.
After that you shoud be good to go and flash custom ROMS. Check whether the selected ROM needs 7.0 or 8.1 as base, almost all of them need stock Oreo.
Sent from my Moto G5 Plus using XDA Labs
Oh yeah, I'm rusty.. Software channel duh, linux gets its stuff there... I guess it is potter xt1687, which is odd though as a website said it wasn't potter.. Anyway, looking in the gsm arena and checking against other variants of our g5 plus, it seems that everything but the radios are the same so is it safe to flash variants backing up the original radio? Thank you very much
itcanbdone said:
Oh yeah, I'm rusty.. Software channel duh, linux gets its stuff there... I guess it is potter xt1687, which is odd though as a website said it wasn't potter.. Anyway, looking in the gsm arena and checking against other variants of our g5 plus, it seems that everything but the radios are the same so is it safe to flash variants backing up the original radio? Thank you very much
Click to expand...
Click to collapse
You wrote you're on the retus channel and model is 1687. Here are the firmwares for your device, the second one ( OPS28.85-17-6-2) is the latest and last build, flash that one and everything should be fine:
https://mirrors.lolinet.com/firmware/moto/potter/official/RETUS/
You still know how to fastboot flash? Unzip firmware to ADB/Fastboot folder etc.?
Here's a post I made for someone else, it includes a link to a flashall.bat, put in in there too so you don't have to manually flash all partitions, just double-click it and it'll run all the commands for you.
https://forum.xda-developers.com/g5...solve-imei0-explanation-t3825147/post80478329
Sent from my Moto G5 Plus using XDA Labs
So I was on stock and flashed twrp after successful unlock of bootloader. After backing up, got stuck at bootloader before any further changes made, yet it was booting fine with bootloader before that.. Saw in a post to flash stock after re locking bootloader, then unlick again...
I skipped that just to get a rom on, now running havoc 9.0 but cannot seem to root as the two su & magisk arent cuttin it in twrp.
Are you really telling me I gotta revert back to stock and flash root in stock to get root?
If so, couldnt i just flash havoc 8.1 and root that way.
Yes i still remember how to flash via adb. Thank you very much
itcanbdone said:
So I was on stock and flashed twrp after successful unlock of bootloader. After backing up, got stuck at bootloader before any further changes made, yet it was booting fine with bootloader before that.. Saw in a post to flash stock after re locking bootloader, then unlick again...
I skipped that just to get a rom on, now running havoc 9.0 but cannot seem to root as the two su & magisk arent cuttin it in twrp.
Are you really telling me I gotta revert back to stock and flash root in stock to get root?
If so, couldnt i just flash havoc 8.1 and root that way.
Yes i still remember how to flash via adb. Thank you very much
Click to expand...
Click to collapse
I'm not sure that I understand everything. After flashing (official) TWRP and making a nandroid you weren't able to boot to system, only to bootloader?
Have you updated to 8.1 stock Oreo before?
Havoc needs that definitely:
https://forum.xda-developers.com/g5-plus/development/rom-havoc-os-v2-2-t3906282/post79018816
It won't make any sense to revert to stock and root it because after flashing havoc root will be lost anyway. What do you mean with "the two su & Magisk aren't cuttin it in TWRP"? (English is not my native language)
Why two? There should be magisk only to flash.
So the goal seems to be making TWRP work correctly when running havoc to be able to flash magisk.zip and boot to system.
Can you post a recovery log after the attempt to flash magisk from TWRP (the function is in TWRP/ advanced/log.)
Can you boot to havoc directly now?
Are you able to reach TWRP?
I need the error message that appears when you try to flash magisk, should be in the log.
And what is it about two things, su AND magisk?
Magisk.zip is the su binary.
Please provide some more information and sorry if it's me who don't understand something.
Sent from my Moto G5 Plus using XDA Labs
- I got root after all. Seems I was just flashing no verity before root and it was suppise to be after.
- there was a super su which I'd rather have to mod things with but neither worked until i figured out as mentioned above
- now I'm trying to get gaps to work..
- also having problem flashing rom withou encryption, it keeps forcing it encrypted.
- here is link to 3 images of what i've got currently:
https://mega.nz/#F!q3pVQIDJ!kwfNgjMEEssa97rrZJjWHg
Thanks
itcanbdone said:
- I got root after all. Seems I was just flashing no verity before root and it was suppise to be after.
- there was a super su which I'd rather have to mod things with but neither worked until i figured out as mentioned above
- now I'm trying to get gaps to work..
- also having problem flashing rom withou encryption, it keeps forcing it encrypted.
- here is link to 3 images of what i've got currently:
https://mega.nz/#F!q3pVQIDJ!kwfNgjMEEssa97rrZJjWHg
Thanks
Click to expand...
Click to collapse
Never use SuperSU alongside with magisk but I think you know that now.
To remove encryption: It's not enough to wipe data in TWRP, you have to format it (the option where you have to confirm with "Yes" and not just wipe). That will wipe your internal storage too.
Only formatting data in TWRP will remove the encryption and the Disable_Dm-Verity_ForceEncrypt_02.04.2019.zip will keep it decrypted. Make sure usb debugging is enabled.
Boot to TWRP and flash ROM and Gapps (both in one action without a reboot in between).
Now flash the no verity-force encryption.zip.
You can reboot to system now but you can also flash the magisk.zip directly afterwards, it helps to keep the data partition encrypted too.
I flash everything in a row.
Check that thread: https://forum.xda-developers.com/g5-plus/how-to/guide-how-to-remove-device-encryption-t3863586
(page 2)
Sent from my Moto G5 Plus using XDA Labs
Thanks for the encryption link.. Any idea on the pros n cons on encryption in the world of flashing zips and modding?
I see pros n cons on google search for encryption but not from developments perspective
itcanbdone said:
Thanks for the encryption link.. Any idea on the pros n cons on encryption in the world of flashing zips and modding?
I see pros n cons on google search for encryption but not from developments perspective
Click to expand...
Click to collapse
I decrypt my device, for example to have access to /data in case of a bootloop because of a magisk module. I don't like the idea of not physically seeing parts of my partitions or even not being able to edit it.
From the sight of security it's better to encrypt naturally. It depends a bit how old your device is and what you want to do with it.
I never lost my device or it was getting stolen so as long it's in my pocket I don't need encryption.
But that's just my personal opinion.
Sent from my Moto G5 Plus using XDA Labs
Hey so I found a really cool way to decrypt but ROM after it's already been encrypted and you have all your stuff in it, I figured it out on accident. What I did was simply did a backup through TWRP and formatted the drive. When I restored the drive it was decrypted! And all this time everyone ever told me that you cannot decrypt. Pretty cool. Actually found this out by switching to a ROM and then going back anyway maybe people should know this? Hope it helps thanks for all the pointers