Hello everyone, so after flashing the current soak test with recovery stock(OPJ.28.108) i unlocked bootloader and flashed magisk 17.1 (which updated to 18.0 recently).
With TWRP in order to avoid any issues, i deleted the ota app from /priv-app and flashed 8.1 aroma gapps, stayed in stock kernel, due to sources not available yet.
How will i update to newer soak tests or final release when they come? Can i flash them with MinimalADB Fastboot? @Jleeblanch's TWRP Flashable one, uses 7.0 Firmware, from what i know.
Now that you've unlocked your bootloader, you can fastboot flash the stock firmware from this thread to return to the stock firmware. However, you may get errors when fastboot flashing the bootloader.img or gpt.bin (partition table), probably saying you can't downgrade or something along those lines.
If a newer version of the soak test or an official version becomes available, you should be able to easily update, but we won't know for sure until that time comes.
In my thread there is a TWRP flashable version of Stock 7.0 and the Oreo soak test 8.1.0, just so you know.
Jleeblanch said:
In my thread there is a TWRP flashable version of Stock 7.0 and the Oreo soak test 8.1.0, just so you know.
Click to expand...
Click to collapse
Oh really? Thanks for the help dude!
If previous soak tests have been anything to go by, we'll likely have to wait for the next soak test update to be leaked. Motorola only releases soak test updates to those users that have applied to its soak test program. If you've flashed the soak test from XDA, Motorola won't send you an update, so we'd have to wait for someone on the test program to provide a copy of said update/updates. However, the aforementioned TWRP versions of the soak test should be updated if we can find the next soak test update.
Guys, quick question, after a soak test begins, how long can we expect before a final version?
Edduardoa said:
Guys, quick question, after a soak test begins, how long can we expect before a final version?
Click to expand...
Click to collapse
About 2-3 months if the soak test doesn't encounter significant or serious bugs - from how long previous soak tests have taken. Expect the release to take longer if there are serious bugs or ones that are hard to fix.
Unless you're part of the soak test itself, there's no guarantee we'll see soak test updates between now and the final release. It depends on whether someone can capture them and leak them to XDA.
Jleeblanch said:
However, you may get errors when fastboot flashing the bootloader.img or gpt.bin (partition table), probably saying you can't downgrade or something along those lines.
Click to expand...
Click to collapse
Which one is the safer downgrade? Yours TWRP Flashable or Fastboot ignoring the "oem_lock" commands? I'm currently with the Oreo ROM, Partition and Bootloader.
xSamukaBRx said:
Which one is the safer downgrade? Yours TWRP Flashable or Fastboot ignoring the "oem_lock" commands? I'm currently with the Oreo ROM, Partition and Bootloader.
Click to expand...
Click to collapse
Though I've not tried this, I think the TWRP flashable would be the safer bet, given TWRP doesn't affect the bootloader or GPT. Furthermore, OTA updates with this set up may likely fail to install before they did any damage to your device.
However, I'm not sure if downgrading in this manner may cause you to lose IMEI or SIM usage, so you may wish to read up on a few of the IMEI threads on this forum before proceeding.
So installing a twrp flashable soak test won't effect/upgrade the bootloader?
If that's the case what if I actually wanted to do that using twrp?
Henry Markle said:
So installing a twrp flashable soak test won't effect/upgrade the bootloader?
If that's the case what if I actually wanted to do that using twrp?
Click to expand...
Click to collapse
Shouldn't do, since TWRP doesn't appear to have the security authorisation to write to the bootloader or GPT.
By the same thought, you'd have to fastboot flash the GPT or bootloader. However, fastboot may not let you flash an older bootloader/GPT (e.g. from Oreo to Nougat) and block you reporting a security downgrade error. This, I don't think you can downgrade your bootloader or GPT
echo92 said:
Though I've not tried this, I think the TWRP flashable would be the safer bet, given TWRP doesn't affect the bootloader or GPT. Furthermore, OTA updates with this set up may likely fail to install before they did any damage to your device.
However, I'm not sure if downgrading in this manner may cause you to lose IMEI or SIM usage, so you may wish to read up on a few of the IMEI threads on this forum before proceeding.
Click to expand...
Click to collapse
@xSamukaBRx, as @Jleeblanch mentioned, that the TWRP flashable Stock ROMs don't have "fastboot erase modemst1" and "fastboot erase modemst2", so you won't lost IMEI.
If you have never touched your persist partitions, then even if you lose IMEI, it can be fixed so no worries about that. However, I would strongly recommend to take EFS backup right now as your device shows IMEI in settings i.e you have a working efs now.
Edit: As @echo92 mentions in the next post, that OTA updates will erase modemst1 and mdoemst2.
I would recommend it is better to fix persist now since everything if working fine to avoid imei problem in future altogether.
Nobody knows what Official Oreo would do to the persist. In the worst case there might be some restriction which would prevent us from fixing/changing persist.
Heeth21 said:
@xSamukaBRx, as @Jleeblanch mentioned, that the TWRP flashable Stock ROMs don't have "fastboot erase modemst1" and "fastboot erase modemst2", so you won't lost IMEI.
If you have never touched your persist partitions, then even if you lose IMEI, it can be fixed so no worries about that. However, I would strongly recommend to take EFS backup right now as your device shows IMEI in settings i.e you have a working efs now.
Click to expand...
Click to collapse
In addition to the good points made above, try to avoid flashing the Nougat stock ROM (not referring to the TWRP flashable) and use OTA updates if you were previously on stock Oreo. Besides the possible risk of hard bricking, many if not all the OTA updates we have erase modemst1/modemst2 (your EFS, I think) as part of their update script, then rebuild modemst1/st2 on the next boot. Thus, you may then lose IMEI as your baseband and other partitions become mismatched and then you may have to try the persist repair.
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.
If some of the more experienced people here could check my steps for returning to stock, I'd really appreciate it. I have some questions and also want to confirm that I correctly understand how to do some of the others. Thanks.
My XT-1575 is running 6.0 build number MPHS24-49-18-16. I would like to change ROMs (probably to Lineage OS 14.1) but be able to return to the same build at a later time. I do not want to update the Moto firmware to 7.0.
Steps:
1) Use the instructions in the thread: [GUIDE] [XT1575] Return to stock and relock bootloader by @acejavelin
2) Download the latest 6.0 factory image available (MPHS24.49-18-8) with the link in the thread and place it in the adb platform-tools directory
3) Open a command prompt in the platform-tools directory and issue the commands listed in the thread to flash the firmware. This will not lock the bootloader because this is an earlier build.
4) As shown in the thread, go to @annoyingduck's post (post #366) to get the OTA .zip to go from 18-8 to 18-16
5) This needs to be sideloaded.Is TWRP used for this? Will TWRP still be in recovery after running the commands in step 3? Do I need to flash TWRP to recovery? When I flash the OTA, will this replace TWRP with the stock recovery?
6) Is there an additional step(s) to lock the bootloader? The instructions say flashing an older build will fail at locking the bootloader. Instead, the OTA is flashed manually, but how does the bootloader get relocked?
7) Are there any additional steps to return to official status to pass safetynet and get OTAs?
xdafan15 said:
If some of the more experienced people here could check my steps for returning to stock, I'd really appreciate it. I have some questions and also want to confirm that I correctly understand how to do some of the others. Thanks.
My XT-1575 is running 6.0 build number MPHS24-49-18-16. I would like to change ROMs (probably to Lineage OS 14.1) but be able to return to the same build at a later time. I do not want to update the Moto firmware to 7.0.
Steps:
1) Use the instructions in the thread: [GUIDE] [XT1575] Return to stock and relock bootloader by @acejavelin
2) Download the latest 6.0 factory image available (MPHS24.49-18-8) with the link in the thread and place it in the adb platform-tools directory
3) Open a command prompt in the platform-tools directory and issue the commands listed in the thread to flash the firmware. This will not lock the bootloader because this is an earlier build.
4) As shown in the thread, go to @annoyingduck's post (post #366) to get the OTA .zip to go from 18-8 to 18-16
5) This needs to be sideloaded.Is TWRP used for this? Will TWRP still be in recovery after running the commands in step 3? Do I need to flash TWRP to recovery? When I flash the OTA, will this replace TWRP with the stock recovery?
6) Is there an additional step(s) to lock the bootloader? The instructions say flashing an older build will fail at locking the bootloader. Instead, the OTA is flashed manually, but how does the bootloader get relocked?
7) Are there any additional steps to return to official status to pass safetynet and get OTAs?
Click to expand...
Click to collapse
All of these questions are answered in the threads you referenced...
1) Yup, that's fine.
2) Same, remember to extract it... Although I would recommend extracting it to a unique directory and add platform-tools to your path
3) Correct, sort of... You cannot use an older firmware to lock, but there are specific commands to attempt a lock and to just flash. When downgrading be aware gpt.bin (partition table) and bootloader.img may fail and that is normal.
4) Yup, good there
5) Sideload in this regard is accomplished through stock recovery, start stock recovery and select "Apply update from ADB" then execute "adb sideload update.zip"
6) Your only option at this time to lock the bootloader is to flash a Nougat firmware image... We do not have a Marshmallow 18-16 image and without one you cannot lock the bootloader, no matter how much you downgrade.
7) "Official" status is not required to pass SafetyNet API check on Marshmallow or Nougat, but you must have a purely stock /boot, /recovery, and /system partition. On Nougat you must also have a locked bootloader. The only way to get back to "Official" status is to flash an official firmware image and then take an official OTA successfully.
Thanks for your help, @acejavelin! Some further clarifying questions-
acejavelin said:
3) Correct, sort of... You cannot use an older firmware to lock, but there are specific commands to attempt a lock and to just flash. When downgrading be aware gpt.bin (partition table) and bootloader.img may fail and that is normal.
Click to expand...
Click to collapse
I assumed I would just copy and paste the commands you provided exactly as listed. Is that OK? Or do I need to substitute the commands you showed at the bottom:
fastboot oem fb_mode_set instead of fastboot oem lock begin
fastboot oem fb_mode_clear instead of fastboot oem lock
Or it doesn't matter?
acejavelin said:
6) Your only option at this time to lock the bootloader is to flash a Nougat firmware image... We do not have a Marshmallow 18-16 image and without one you cannot lock the bootloader, no matter how much you downgrade.
Click to expand...
Click to collapse
And the way to do this is to flash NPH25.200-22 from adb fastboot as shown in your other thread, correct? Can I also take the Moto OTA from 18-16 (the one I am currently being offered)?
acejavelin said:
7) "Official" status is not required to pass SafetyNet API check on Marshmallow or Nougat, but you must have a purely stock /boot, /recovery, and /system partition. On Nougat you must also have a locked bootloader. The only way to get back to "Official" status is to flash an official firmware image and then take an official OTA successfully.
Click to expand...
Click to collapse
So you are saying that if I follow the instructions to return to 18-16 I will be able to recieve OTAs and will pass safetynet. Only downside is that my bootloader will remain unlocked?
By flashing the Nougat image, my bootloader can be locked (part of the sequence of commands)
but only by doing this plus accepting a future OTA will the status return to "official"?
[/QUOTE]
xdafan15 said:
Thanks for your help, @acejavelin! Some further clarifying questions-
I assumed I would just copy and paste the commands you provided exactly as listed. Is that OK? Or do I need to substitute the commands you showed at the bottom:
fastboot oem fb_mode_set instead of fastboot oem lock begin
fastboot oem fb_mode_clear instead of fastboot oem lock
Or it doesn't matter?
Click to expand...
Click to collapse
Using the 'oem lock' commands will fail, and it will get stuck in fb_mode that you have to clear. Better to just use the fb_mode commands up front.
xdafan15 said:
And the way to do this is to flash NPH25.200-22 from adb fastboot as shown in your other thread, correct? Can I also take the Moto OTA from 18-16 (the one I am currently being offered)?
Click to expand...
Click to collapse
Guess I am confused... if you flash NPH25.200-22 you won't be offered 18-16 OTA, but will likely be offered the NPHS25-201.1 update. If you are on 18-8 and are pure stock you can accept the 18-16 update, and within 24 hours after that is successfully applied you should be offered the Nougat update(s).
xdafan15 said:
So you are saying that if I follow the instructions to return to 18-16 I will be able to recieve OTAs and will pass safetynet. Only downside is that my bootloader will remain unlocked?
By flashing the Nougat image, my bootloader can be locked (part of the sequence of commands)
but only by doing this plus accepting a future OTA will the status return to "official"?
Click to expand...
Click to collapse
You can chose whether to lock the bootloader or not by flashing the Nougat image, the question is which do you want? Just flashing an image won't make your software status "official" in most cases. We have seen some cases where it does, but we don't know why and in most cases it will stay unofficial until you accept an OTA update, then somehow it miraculously becomes official. The key to remember here is once you accept an OTA that is a higher version than the stock images we have, you have no way to lock the bootloader, so if you want to lock your bootloader in your current state the only possible way is to flash the NPH25.200-22 image using the locking commands, because if you don't lock at this point and accept an OTA update you cannot relock the bootloader until (or if) we get a newer factory image.
One more thing to keep in mind, if you accept an OTA to Nougat or manually upgrade, and decide to downgrade to Marshmallow, it is possible, but once this is done do NOT accept any OTA updates back to Nougat, it will hard brick... and I mean perma-brick such that a mainboard replacement is necessary to fix it, which Moto won't do because you unlocked the bootloader, so basically the phone is trash.
@acejavelin, thanks again and sorry for asking so many questions. For those of us who only play around at this stuff, it is hard to keep this all in our heads. Especially since a wrong move can hard brick the phone as you mentioned.
acejavelin said:
Guess I am confused... if you flash NPH25.200-22 you won't be offered 18-16 OTA, but will likely be offered the NPHS25-201.1 update. If you are on 18-8 and are pure stock you can accept the 18-16 update, and within 24 hours after that is successfully applied you should be offered the Nougat update(s).
Click to expand...
Click to collapse
Interesting- You say if I return to stock 18-8, Moto will offer me the 18-16 OTA first, I won't be offered Nougat directly?
Since I would want to relock the bootloader, is there any reason not to just go directly from Lineage OS to NPH25.200-22?
The string of commands to issue (shown in the "return to stock" thread) is the same whether it is a MM or Nougat image that is being flashed, correct?
acejavelin said:
One more thing to keep in mind, if you accept an OTA to Nougat or manually upgrade, and decide to downgrade to Marshmallow, it is possible, but once this is done do NOT accept any OTA updates back to Nougat, it will hard brick... and I mean perma-brick....
Click to expand...
Click to collapse
If I downgrade to MM and then flash the NPH25.200-22 image, at that point is it again OK to take an OTA to NPHS25-201.1 with causing problems?
Does it matter if the Nougat version I was originally on before downgrading was 200-22 vs 201.1?
Thanks again!
xdafan15 said:
@acejavelin, thanks again and sorry for asking so many questions. For those of us who only play around at this stuff, it is hard to keep this all in our heads. Especially since a wrong move can hard brick the phone as you mentioned.
Interesting- You say if I return to stock 18-8, Moto will offer me the 18-16 OTA first, I won't be offered Nougat directly?
Since I would want to relock the bootloader, is there any reason not to just go directly from Lineage OS to NPH25.200-22?
The string of commands to issue (shown in the "return to stock" thread) is the same whether it is a MM or Nougat image that is being flashed, correct?
If I downgrade to MM and then flash the NPH25.200-22 image, at that point is it again OK to take an OTA to NPHS25-201.1 with causing problems?
Does it matter if the Nougat version I was originally on before downgrading was 200-22 vs 201.1?
Thanks again!
Click to expand...
Click to collapse
Yes
No
Yes, except watch the number of sparse chunks
Yes, as long as you flash the full image and not as an OTA.
No
I guess this conversation is going all over the place... are you wanting to return to stock and lock the bootloader or run a custom ROM? You can't really do both. If you want to return to stock, that depends on your current version, if you want to run custom there are less constraints. This is a 2 year old device, just pick one and go with it.
Thanks for your patience with me, @acejavelin.
My intent is to switch to Lineage OS now, but make sure I understand the correct steps to return to stock in the future if I want to. I wanted to confirm that info before everyone is gone from the Moto X Pure forum. I tend to keep my phones for a long time.
I think I've got it now, but I do want to ask 1 more clarifying question:
I asked "If I downgrade to MM and then flash the NPH25.200-22 image, at that point is it again OK to take an OTA to NPHS25-201.1 with causing problems?"
and you answered
"Yes, as long as you flash the full image and not as an OTA."
Do you mean
(A) as long as I flash the full 25.200-22 image and then take the OTA (which motorola will offer to me at that point to get to 25-201.1),
OR
(B) did you mean after flashing the image to get to 25.200-22, I cannot take the OTA to 25-201.1, but must wait until (if) someone posts the image file for 25-201.1 and flash that?
Sorry for asking so many questions. I really appreciate it
xdafan15 said:
Thanks for your patience with me, @acejavelin.
My intent is to switch to Lineage OS now, but make sure I understand the correct steps to return to stock in the future if I want to. I wanted to confirm that info before everyone is gone from the Moto X Pure forum. I tend to keep my phones for a long time.
I think I've got it now, but I do want to ask 1 more clarifying question:
I asked "If I downgrade to MM and then flash the NPH25.200-22 image, at that point is it again OK to take an OTA to NPHS25-201.1 with causing problems?"
and you answered
"Yes, as long as you flash the full image and not as an OTA."
Do you mean
(A) as long as I flash the full 25.200-22 image and then take the OTA (which motorola will offer to me at that point to get to 25-201.1),
OR
(B) did you mean after flashing the image to get to 25.200-22, I cannot take the OTA to 25-201.1, but must wait until (if) someone posts the image file for 25-201.1 and flash that?
Sorry for asking so many questions. I really appreciate it
Click to expand...
Click to collapse
Honestly, the smart bet would be to flash the NPH25.200-22 image, then do NOT take any OTA. Then go ahead and flash TWRP and LineageOS. You can always go back to the full image without issues of "downgrading".
At this time the 25.200-22 image is the newest we have and downgrading can never be perfect. If there is no reason to take the OTA (like you are going to just flash Lineage anyway), then don't take it... At least you have an easy out.
The main reason for this is we don't have an image for 25-201.2 and we don't know when, or even if, we ever will. For example, we never did get an image of Marshmallow 18-16 and at this point I doubt we ever will.
Thanks for the excellent support, @acejavelin! That's why I love XDA.
@acejavelin I was on official (stock) 7.0, build NPH25.200-23. I installed unofficial LOS 14.1 (by Hashbang) because I have the N modem, and official LOS 14.1 only supports the M modem. I later decided to go back to stock. As we all know the NPH25.200-23 factory images have not yet been (or ever will be) released, so I followed your guide on how to revert to stock, except I flashed the available NPH25.200-22 partitions (the ones that flashed, anyway, minus the ones that gave Preflash Validation Error) without relocking the bootloader, and now I am back to NPH25.200-22. I also immediately received the notification for the -23 OTA but I did not install it. My question is this: Can I accept the -23 OTA or will I risk bricking? I never downgraded to M, I only had unofficial LOS 14.1 builds, and now the stock -22 build.
My battery is acting all weird, shutting down at about 70%, plugging it again and showing 50%. When I boot, if I unplug it will immediately shut down. Basically it's plugged in the whole time. I have no idea what's causing this, the fact that I flashed unofficial LOS, or because of a faulty battery since I had changed it before flashing LOS), or because of partitions mismatch. So I'm trying to narrow it down and pinpoint the cause. But it seems that every time I try something, it makes the battery worse.
The battery is probably reaching the end of it's life...
You can accept the -23 OTA, the risks are minimal if everything you told me is correct.
acejavelin said:
The battery is probably reaching the end of it's life...
You can accept the -23 OTA, the risks are minimal if everything you told me is correct.
Click to expand...
Click to collapse
Thanks for the reply. Are you sure that taking the OTA on mismatched partitions (bootloader and gpt from -22 and everything else from -23) would not brick? There have been cases like that in the past (https://forum.xda-developers.com/moto-x-2014/general/warning-hard-bricking-downgrading-t3116379) on the Moto X 2nd Gen because the updater script did not have the correct checks to prevent a brick. Maybe it was the case when downgrading to a previous full version i.e. from 5.1 to 4.4.4, or just on older phones/older versions. Do we know if the updater script from -22 to -23 has to correct checks to prevent a brick?
discovery94 said:
Thanks for the reply. Are you sure that taking the OTA on mismatched partitions (bootloader and gpt from -22 and everything else from -23) would not brick? There have been cases like that in the past (https://forum.xda-developers.com/moto-x-2014/general/warning-hard-bricking-downgrading-t3116379) on the Moto X 2nd Gen because the updater script did not have the correct checks to prevent a brick. Maybe it was the case when downgrading to a previous full version i.e. from 5.1 to 4.4.4, or just on older phones/older versions. Do we know if the updater script from -22 to -23 has to correct checks to prevent a brick?
Click to expand...
Click to collapse
Your not downgrading... Either it will work or the checks will fail. The chances of bricking are minimal.
The issue of the MM vs. N modems is part of the reason I started this thread. My understanding was that official Lineage OS 14.1 would only work properly if the phone was still running MM firmware because LOS 14.1 was not configured to handle the N modem as written above by @discovery94. It seems like the unofficial LOS 14 by @Hashbang173 has some problems, so it seemed safer to stay on MM. But @acejavelin's advice to me was to upgrade to N before switching ROMS which would seem to severely limit choices of ROMs
I guess the options are stay on MM and have a large selection of ROMS (including official LOS 14.1)
or upgrade to N and only select form Hashbang's LOS, RR by LuisG, and AOSP EX by Obsolete1,
or maybe upgrade to N, then extract the modem from MM stock firmware and flash it to avoid the modem mismatch problem.
Have I summed this up properly?
acejavelin said:
Your not downgrading... Either it will work or the checks will fail. The chances of bricking are minimal.
Click to expand...
Click to collapse
So the OTA was unsuccessful. The recovery first showed installing update, then displayed "Error", and then the phone rebooted and displayed an update not successful screen (Images attached). I guess the only way is to use the factory images, but I won't even get my hopes up for that.
Does anyone know about this ?
The last version of the firmware that got OTA'ed to my phone is POTTER_RETAIL_7.0_NPNS25.137-93-8.
The only twrp backup of the firmware I have is while it was on POTTER_RETAIL_7.0_NPNS25.137-93-4.
When I tried to flash the phone with v 93-4 using fastboot, I got denied because of the version being older than that of the bootloader. But the problem is that I was able to erase prior to attempting writing ...
I need to re-install a stock rom in the phone, but POTTER_RETAIL_7.0_NPNS25.137-93-8 cannbot be found anywhere yet.
I though about twrp-flashing the phone with my 93-4 backup, but I am hesitant, I fear bricking the phone.
Is there any alternative to patience while waiting for POTTER_RETAIL_7.0_NPNS25.137-93-8_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip eventually appearing somewhere ?
Or, in other words, knowing that the last OTA to my phone installed v 93-8, is there any way to flash POTTER_RETAIL_7.0_NPNS25.137-35-5_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip for instance ?
CanadianGixxerman said:
I though about twrp-flashing the phone with my 93-4 backup, but I am hesitant, I fear bricking the phone.
Click to expand...
Click to collapse
An older version (your twrp backup) will work with a newer bootloader, however you can't do any OTAs. An OTA will try to apply the same changes to the bootloader that were already made, resulting in a hard brick - though the OTA would fail anyway since you don't have an intact /oem partition. You will have a functional phone, and you can get back on track after 93-8 images or Oreo are released.
I know because I'm in a similar situation. I wanted to update from 93-4 to 93-8, and I had an intact /system image backup, but /oem was mounted before so I had to flash it via fastboot. Little did I know it was from the wrong channel (retus instead of reteu), resulting in the OTA updating everything except for oem and messing stuff up, so I just flashed a 93-4 twrp backup. Everything works, patiently waiting for Oreo.
bazinga137 said:
I just flashed a 93-4 twrp backup.
Click to expand...
Click to collapse
Just curious. Did you have a full system image backup through twrp or just the system partition? I have a twrp backup of 93-8 stock boot, logo, oem, recovery, and system PARTITIONS which I thought would allow me to restore and take ota. However, since doing that I've read that system needs to be the full IMAGE backup through twrp. Confused so I haven't restored to take the 93-10 update which I got notification of yesterday.
craigl14 said:
Just curious. Did you have a full system image backup through twrp or just the system partition? I have a twrp backup of 93-8 stock boot, logo, oem, recovery, and system PARTITIONS which I thought would allow me to restore and take ota. However, since doing that I've read that system needs to be the full IMAGE backup through twrp. Confused so I haven't restored to take the 93-10 update which I got notification of yesterday.
Click to expand...
Click to collapse
Honestly, I am not sure. I did a twrp back up with the default selected partitions. But it turned out that this backup is not reliable. The phone does boot up on it, but suffers from applications crashes all over. Last I discovered is that the phone itself was not working for a phone, meaning making receiving calls is not possible.
craigl14 said:
Just curious. Did you have a full system image backup through twrp or just the system partition? I have a twrp backup of 93-8 stock boot, logo, oem, recovery, and system PARTITIONS which I thought would allow me to restore and take ota. However, since doing that I've read that system needs to be the full IMAGE backup through twrp. Confused so I haven't restored to take the 93-10 update which I got notification of yesterday.
Click to expand...
Click to collapse
It needs to be an image backup for OTAs. Unlike a regular backup, image backups are block-by block pristine copies, and restoring them preserves dm-verity and all /system checks. On the other hand the /oem partition cannot be backed up as an image (I asked GtrCraft, the official maintainer of twrp for some moto devices), and since OTAs also check if /oem has been tampered with, the update fails.
Updates will only pass if /oem has never been mounted, and you have a system image backup.
bazinga137 said:
It needs to be an image backup for OTAs. Unlike a regular backup, image backups are block-by block pristine copies, and restoring them preserves dm-verity and all /system checks. On the other hand the /oem partition cannot be backed up as an image (I asked GtrCraft, the official maintainer of twrp for some moto devices), and since OTAs also check if /oem has been tampered with, the update fails.
Updates will only pass if /oem has never been mounted, and you have a system image backup.
Click to expand...
Click to collapse
Dumb question...How do I know if the oem partition is tampered with or has never been mounted? I am rooted with elementalx kernel and supersu. TWRP partition stock backup made immediately after taking 93-8 update and before flashing twrp, rooting, etc. I know I am hosed without the system IMAGE as far as ota's go, but I'm just trying to learn.
I'm in the same boat. Pretty much stuck on 93-8 forever until a new full image is released somewhere. I might just move onto a custom Oreo rom.
dunderball said:
I'm in the same boat. Pretty much stuck on 93-8 forever until a new full image is released somewhere. I might just move onto a custom Oreo rom.
Click to expand...
Click to collapse
Well, I did that. I have tried a few cutom roms : Pixel Exprerience, Resurection Remix, AOSP extended, AOSiP and Dirty Unicorns. The latter and AOSiP are those I find the most reliable. Avoid PE and RR, too buggy, AOSP-E has issues with SIM/SDcard here.
But I will want to go back to stock moto rom when I can (ie : full 93-8 load fastboot flashable is released).
If moto had been quicker to release Oreo AND fix the wifi bug, I would not have given up on retus.
I guess I have an even more fundamental dumb question than my twrp restore issue and maybe it belongs in another thread. Aside from advanced excel formulas, I have no programming experience of any kind, let alone android. However, it seems to me that if I have a full firmware package for 93-4 (which I do) and a "blur" ota update file that takes it to 93-8 (which I do), I should be able to create a full 93-8 firmware package file myself from those two files without waiting on the file hosting sites. Maybe this is way too advanced a process but it seems to me this is 1+2=3 variety.
craigl14 said:
I guess I have an even more fundamental dumb question than my twrp restore issue and maybe it belongs in another thread. Aside from advanced excel formulas, I have no programming experience of any kind, let alone android. However, it seems to me that if I have a full firmware package for 93-4 (which I do) and a "blur" ota update file that takes it to 93-8 (which I do), I should be able to create a full 93-8 firmware package file myself from those two files without waiting on the file hosting sites. Maybe this is way too advanced a process but it seems to me this is 1+2=3 variety.
Click to expand...
Click to collapse
Your device now being at 93-8 is what's in the way. It seems like you can restore your twrp 93-4 on it, but you won't be able to relock the BL, hence OTA will not work.
CanadianGixxerman said:
Your device now being at 93-8 is what's in the way. It seems like you can restore your twrp 93-4 on it, but you won't be able to relock the BL, hence OTA will not work.
Click to expand...
Click to collapse
Sorry for the confusion. My restore issue is with the fact that I did not make a full system image twrp backup of stock 93-8. If I had, I would be able to restore and take ota's (assuming the oem issue doesn't interfere which I don't know about).
My last question is more fundamental and broader. There are quite a few people waiting on firmware updates. It just seems to me that if I have a full firmware package and an update package for that firmware, I should be able to create a newly updated full firmware package independent of what happens to be on my phone at any one time. Again, maybe really stupid and way beyond my capabilities.
I'm on a slightly same boat as OP, but I don't have my backup since I thought it was on my SD and wiped my phone, with the backup only there. I was on 93-8 when I wiped. Would getting a 93-4 backup work?
This question might of been answered but I did not see it when I read through this thread.
craigl14 said:
Sorry for the confusion. My restore issue is with the fact that I did not make a full system image twrp backup of stock 93-8. If I had, I would be able to restore and take ota's (assuming the oem issue doesn't interfere which I don't know about).
My last question is more fundamental and broader. There are quite a few people waiting on firmware updates. It just seems to me that if I have a full firmware package and an update package for that firmware, I should be able to create a newly updated full firmware package independent of what happens to be on my phone at any one time. Again, maybe really stupid and way beyond my capabilities.
Click to expand...
Click to collapse
I took a full backup of my system image through twrp, and I was on 93-8. I'll upload it when I have time and you can give it a try.
CanadianGixxerman said:
[...] but you won't be able to relock the BL, hence OTA will not work.
Click to expand...
Click to collapse
Why would you need to relock the BL to take an OTA?
craigl14 said:
My last question is more fundamental and broader. There are quite a few people waiting on firmware updates. It just seems to me that if I have a full firmware package and an update package for that firmware, I should be able to create a newly updated full firmware package independent of what happens to be on my phone at any one time. Again, maybe really stupid and way beyond my capabilities.
Click to expand...
Click to collapse
Sadly you can't apply an OTA to the firmware images, if that's what you're thinking. They need to be signed by moto to be flashable through fastboot. And if you'd want to provide someone with a twrp backup of a firmware higher than theirs, their bootloader would need to be updated too, via an OTA.
bazinga137 said:
if that's what you're thinking.
Click to expand...
Click to collapse
Thanks. That's exactly my question. So the answer is that Motorola controls the process. Makes sense. Any thoughts on my oem mounting question?
craigl14 said:
Thanks. That's exactly my question. So the answer is that Motorola controls the process. Makes sense. Any thoughts on my oem mounting question?
Click to expand...
Click to collapse
I really can't think of a way of checking the mount count of Android partitions, and I haven't found anything online.
I discovered the mount counter thingy when sweeping through logs of a failed OTA. I'm really not sure where the OTA script reads it from.
craigl14 said:
Sorry for the confusion. My restore issue is with the fact that I did not make a full system image twrp backup of stock 93-8. If I had, I would be able to restore and take ota's (assuming the oem issue doesn't interfere which I don't know about).
My last question is more fundamental and broader. There are quite a few people waiting on firmware updates. It just seems to me that if I have a full firmware package and an update package for that firmware, I should be able to create a newly updated full firmware package independent of what happens to be on my phone at any one time. Again, maybe really stupid and way beyond my capabilities.
Click to expand...
Click to collapse
I made a full backup of 93-8, but still i can't lock bootloader. We need complete firmware, until then, Lineage OS is the answer.
---------- Post added at 11:55 PM ---------- Previous post was at 11:52 PM ----------
bazinga137 said:
Why would you need to relock the BL to take an OTA?
Click to expand...
Click to collapse
No idea, i saw this first time now on Motorola. On any other manufacturers i could lock bootloader, and even get OTA updates just by flashing stock recovery and having unlocked bootloader was not a problem.
If your device was formally updated to NPNS25.137-93-8 (March 2018 security patch), then you could try to flash the NPNS25.137-93-4 (Jan 2018 security patch) update again as you previously tried (link to the Jan 2018 stock firmware for EU/US and Asia devices: https://mirrors.lolinet.com/firmware/moto/potter/official/RETAIL/ ). You may wish to ignore the security downgrade errors (you cannot downgrade bootloaders anyway, presumably to prevent you opening security vulnerabilities) when you flash, which should just be for GPT and bootloader. You may also see 'image signed with bad key' for recovery and boot as well, but verify those partitions, and the other partitions report [OKAY] after flashing. That way, you should have a NPNS25.137-93-4 system, with a NPNS25.137-93-8 bootloader, and when you boot you should have a device reporting with fully stock NPNS25.137-93-4. The next OTA you should receive is the NPNS25.137-93-8 OTA and then the NPNS25.137-93-10 April 2018 security patch OTA, which should bring you up to the latest stock firmware.
By reflashing the NPNS25.137-93-4 firmware, this should also restore your OEM partition to being untampered (read only status?), as should your system partition (which should be read only, I recall that swiping to allow modifications in TWRP sets your system partition to read-write, which causes the OTA to fail).
Normally, I would advise against downgrading and using OTA updates, as this is a prime way of hard bricking. However, in this case you are downgrading your device firmware to the firmware directly preceding the newest firmware you had (i.e. downgrading to NPNS25.137-93-4 from NPNS25.137-93-8), with the next OTA being NPNS25.137-93-8, which brings you back up to the build you had, this may be safe. To your device, you are flashing the same bootloader from the NPNS25.137-93-8 OTA as currently on your device, which should not hard brick.
If you previously had stock NPNS25.137-93-10, then I cannot recommend this procedure as you'll be downgrading two firmware versions (and you'll have to wait for newer stock firmware to be leaked), else if you try flashing NPNS25.137-93-4 onto the April 2018 firmware and try using OTA updates, you may hard brick and have a pricey paperweight. I also do not know if this will work by cross-flashing from the NPN25.137-92 series of updates either.
Of course, as the NPNS25.137-93-4 firmware is older than your bootloader, you will not be able to re-lock your bootloader (you'll need a newer firmware, probably the April 2018 or newer security patch stock firmware), but being back on full stock, you should be eligible for OTAs provided you only downgraded from NPNS25.137-93-8 (and that March 2018 security patch was the latest stock firmware on your device).
If you are truly concerned about hard bricking, then I would follow other member's suggestions in this thread and stay with TWRP flashables of the stock ROM, as they do not usually affect the bootloader.
Any questions or comments before you perform this procedure, please ask.
bazinga137 said:
I really can't think of a way of checking the mount count of Android partitions, and I haven't found anything online.
I discovered the mount counter thingy when sweeping through logs of a failed OTA. I'm really not sure where the OTA script reads it from.
Click to expand...
Click to collapse
Thanks. Weird. Sorry for hijacking this thread. But if my process were to take OTA after which it reboots, then IMMEDIATELY reboot into bootloader, fastboot BOOT into twrp (not flash it) and take a backup of boot, logo, oem, recovery and system (FULL IMAGE), how would that change oem?
CanadianGixxerman said:
Well, I did that. I have tried a few cutom roms : Pixel Exprerience, Resurection Remix, AOSP extended, AOSiP and Dirty Unicorns. The latter and AOSiP are those I find the most reliable. Avoid PE and RR, too buggy, AOSP-E has issues with SIM/SDcard here.
But I will want to go back to stock moto rom when I can (ie : full 93-8 load fastboot flashable is released).
If moto had been quicker to release Oreo AND fix the wifi bug, I would not have given up on retus.
Click to expand...
Click to collapse
What's buggy about PE? I was just about to try it...
I've just captured the Official OPP28.85-16 OTA for retail cedric and I'm posting it here. I'm on retbr channel but this will work on any retail device. If you're on another updated channel, I don't know what would happen if you installed this.
Notice that to install this YOU MUST be on NPPS25.137-93-2-5 to install these, since OTA's are not full firmwares like fastboot files, but instead they're patchings tailored to be applied upon a specific firmare - NPPS25.137-93-2-5 in this case.
Another particular detail is that the OTA file (gotten directly from my credric) lists the Blur Version as Blur_Version.25.361.10.cedric.retail.en.US, but curiously, the fastboot version for the same firmware ( which you can download here) lists it as Blur_Version.28.41.15.cedric.retail.en.US
Someone also reported in another thread that they just sideloaded this upon the Second Soak test. I wouldn't doubt it since this is what should happen to regular soak testers, but if you do it, DO IT AT YOUR OWN RISK
I also won't post instructions on how to install this since they're already available here
Download
Gdrive: https://drive.google.com/file/d/149hrGFpuWUgAvJr02McYNwJVaqSvllYO/view?usp=sharing
That's it.
changelog?
Has anyone already tried it?
Since this is a (Delta) OTA Update that expects NPPS25.137-93-2-5 (Blur_Version.25.361.10) it should be correctly named "block_delta-ota-Blur_Version.25.361.10-28.41.15.cedric.retail.en.US" in my view.
Someone also reported in another thread that they just sideloaded this upon the Second Soak test.
Click to expand...
Click to collapse
I'm on the 2nd soak test update OPP28.85-13.
Just tried to flash the update from SD card and ADB sideload.
Update failed due to wrong version.
E3002: Package expects build thumbprint of 8.1.0/OPP28.85-16/0400:user/release-keys or 7.0/NPPS25.137-93-2-5/10:user/release-keys; this device has 8.1.0/OPP28.85-13/789a:user/release-keys.
JoeDoe0 said:
Since this is a (Delta) OTA Update that expects NPPS25.137-93-2-5 (Blur_Version.25.361.10) it should be correctly named "block_delta-ota-Blur_Version.25.361.10-28.41.15.cedric.retail.en.US" in my view.
I'm on the 2nd soak test update OPP28.85-13.
Just tried to flash the update from SD card and ADB sideload.
Update failed due to wrong version.
E3002: Package expects build thumbprint of 8.1.0/OPP28.85-16/0400:user/release-keys or 7.0/NPPS25.137-93-2-5/10:user/release-keys; this device has 8.1.0/OPP28.85-13/789a:user/release-keys.
Click to expand...
Click to collapse
seems like it can be updated. from. soak test then, but I never heard nor did I find anything about OPP25. 85-16 build. maybe there was a third soak test and we don't know about it
Works perfect
Hi,
i used the above Image in Germany and i am now on Oreo 8.1
Everything works perfect. First i had a little bit trouble due to an old Version of ADB Tools, but after Update ADB to current Version the Update to Oreo took something around 30min.
Build 28.85-16
Oreo 8.1
Software Channel reteu
Patch Level 01.08.2018
bori321 said:
Hi,
i used the above Image in Germany and i am now on Oreo 8.1
Everything works perfect. First i had a little bit trouble due to an old Version of ADB Tools, but after Update ADB to current Version the Update to Oreo took something around 30min.
Build 28.85-16
Oreo 8.1
Software Channel reteu
Patch Level 01.08.2018
Click to expand...
Click to collapse
On which version you were before update?
Firmware
Hi,
before update to Oreo i flashed NPPS25.137-93-2-5 Firmware and after that the Image from this thread.
Worked perfect.
Alex
I tried to post a Screenshot but it was not possible because i am a new member...
Update failed due to wrong version.
E3002: Package expects build thumbprint of 8.1.0/OPP28.85-16/0400:user/release-keys or 7.0/NPPS25.137-93-2-5/10:user/release-keys; this device has 8.1.0/OPP28.85-13/789a:user/release-keys.
Click to expand...
Click to collapse
freeZbies said:
seems like it can be updated. from. soak test then, but I never heard nor did I find anything about OPP25. 85-16 build. maybe there was a third soak test and we don't know about it
Click to expand...
Click to collapse
Update fails from OPP28.85-13 since it expects either OPP28.85-16 which is the latest Oreo build (that I want to update to) or the latest Nougat NPPS25.137-93-2-5.
There is no OPP25. 85-16 build! I think you misread the error message.
BTW I updated from OPP28.85-13 to -16 using the full fastboot version and it worked out perfectly.
JoeDoe0 said:
Update fails from OPP28.85-13 since it expects either OPP28.85-16 which is the latest Oreo build (that I want to update to) or the latest Nougat NPPS25.137-93-2-5.
There is no OPP25. 85-16 build! I think you misread the error message.
BTW I updated from OPP28.85-13 to -16 using the full fastboot version and it worked out perfectly.
Click to expand...
Click to collapse
yeah, I actually misread it, now I see it.
Anyways, flashing it from fastboot doesn't prove anything. but seems like Cedric can be upgraded from the soak test to final version using this ota. Idk because I used fastboot myself too, since I had already modified my system partition.
AsusZenFone3Deluxe said:
changelog?
Click to expand...
Click to collapse
seriously?
stop joking, Motorola doesn't release changelogs.
but I'll try:
updated from nougat to oreo?
duhhh
how is speaker quality in this build ?
because there is some issues in previous oreo builds
Speaker
Hi,
i would say that for my ears the speaker sounds better than it was with Nougat.
After a few days of testing everything works really good and i have not found anything not working or any problems.
Alex
bori321 said:
Hi,
before update to Oreo i flashed NPPS25.137-93-2-5 Firmware and after that the Image from this thread.
Worked perfect.
Alex
I tried to post a Screenshot but it was not possible because i am a new member...
Click to expand...
Click to collapse
how do you get back to NPPS25.137-93-2-5
I followed the steps from this Thread: https://forum.xda-developers.com/g5/development/stock-upgrade-to-official-stock-oreo-8-t3823598
- Unlocked bootloader (don't know of this is necessary)
- back to NPPS25.137-93-2-5 via the commands from the thread i linked (without the lines:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
)
- via ADB sideload with the Oreo download from this thread to Oreo.
Alex
ahmedAZ said:
how is speaker quality in this build ?
because there is some issues in previous oreo builds
Click to expand...
Click to collapse
In my experience the quality is better than on previous oreo builds.
ahmedAZ said:
how do you get back to NPPS25.137-93-2-5
Click to expand...
Click to collapse
if you have an unlocked bootloader download NPPS25.137-93-2-5 Flashable Zip here and flash it with twrp
bori321 said:
I followed the steps from this Thread: https://forum.xda-developers.com/g5/development/stock-upgrade-to-official-stock-oreo-8-t3823598
- Unlocked bootloader (don't know of this is necessary)
Alex
Click to expand...
Click to collapse
to flash official Motorola files there's no need to unlock the bootloader.
you've just unnecessarily voided your warranty
@freeZbies
Hey is that twrp stock rom (137-93-2-5) the only thing we need to flash before going for the ota ? Cause I've been told that we needed to be on a completely unmodified system partition in order to receive the ota. In that case just flashing twrp stock wouldn't be sufficient right?
https://forum.xda-developers.com/g5...o-official-stock-oreo-8-t3823598/post77713117
Chekm8Qc said:
@freeZbies
Hey is that twrp stock rom (137-93-2-5) the only thing we need to flash before going for the ota ? Cause I've been told that we needed to be on a completely unmodified system partition in order to receive the ota. In that case just flashing twrp stock wouldn't be sufficient right?
https://forum.xda-developers.com/g5...o-official-stock-oreo-8-t3823598/post77713117
Click to expand...
Click to collapse
I dont know if the twrp version would be valid. To apply an OTA, your system must matchbit by bit, so the most guaranteed way is to flash that firmware via fastboot, but you could try flashing the twrp version, and in case it works, you could post the results here.
just dont forget that if the ota fails youll soft brick ur phonr and will only be able to recover it via fastboot
freeZbies said:
I dont know if the twrp version would be valid. To apply an OTA, your system must match stick bit by bit, so the most guaranteed way is to flash that firmware via fastboot, but. you could try flashing the twrp version, and in case it. woeks you could post the results here.
just dont forget that if the ota fails youll soft brick ur phonr and will only be able to recover it via fastboot
Click to expand...
Click to collapse
Thanks I'll keep that in mind
Being soft bricked,, wouldn't I be able to use twrp still? Like to flash a valid rom or one of my backups?
Anyways I can't really try it that way since the update hasn't come to me yet I'm on software channel Retca.
Edit : right I forgot that I could just use the official ota available here if I would like to test it.
Chekm8Qc said:
Thanks I'll keep that in mind
Being soft bricked,, wouldn't I be able to use twrp still? Like to flash a valid rom or one of my backups?
Anyways I can't really try it that way since the update hasn't come to me yet I'm on software channel Retca.
Edit : right I forgot that I could just use the official ota available here if I would like to test it.
Click to expand...
Click to collapse
being soft bricked doesnt necessarily mean you can recover it through twrp. OTA's are different of twrp flashables in that it modifies things beyond system partition. I've seen reports from people with other motorola devices who applied an OTA while having a modified system partition, and even though they were able to boot to twrp, flashing a custom Rom or restore a backup wouldn't make the phone boot. Their phones weren't hard bricked, but still they had to fastboot to recover their phones. Anyways, why don't you flash the Twrp flashable if, it's already available (considering you have an unlocked bootloader).
I'm case you have a locked bootloader you may fastboot without executing "fastboot erase userdata" in case you want to try. I did it without losing my data (although I was already in Opp 28.85-16)
but after all I really advice you to flash the twrp zip if u can
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...