EDIT 2: ISSUE SOLVED. Go to the bottom of this comment for how to get it done right. Credits to @rizkyxculture and @orma1
So I'm one of those people that just jumped onto the Pie release as soon as it came out, and realized only afterwards that it was by far the worst update I could've hoped for. It completely broke the focus on my GCam, (and added on top an absolutely crap UI that is in every way a downgrade from oreo's UI). I wasn't too depressed initally though, as I guessed I could easily downgrade to a previous stock version. Now after reading some posts here and there I realized that I cannot roll back my device thanks to some anti-rollback feature the Xiaomi gods implemented in Pie, and that rolling back results in a bootloop. I've seen some threads where they give a separate EFS file IIRC, but I'm quite skeptical about using it as it contains IMEI info that is unique to every device, so it might conflict with my own IMEI. Hence why I'm hesistant to flash my phone and probably face a repair bill involving a motherboard change as a consequence.
So my question is, what exactly should I do to safely revert back to Oreo (that absolutely guaranteed works, retaining IMEI and everything else), and if not, how can I fix GCam on this phone?
Aside from that I did check whether the anti-rollback feature was enabled or not using the commands, to be sure:
adb reboot bootloader
fastboot getvar anti
and got the result:
anti:
Which makes me think it's just some dud. So am I good to just flash the oreo xiaomi stock rom using xiaomi flash tool by unlocking the bootloader first?
EDIT: I'm running the March 5 security patch.
EDIT 2: Sorry for necroing this thread, but just to clear things up a bit, from my own experience, and include and clarify what @orma1 said below in this thread so you don't have to scroll down. Before all this, make sure you have SYSTEM WIDE ADB AND FASTBOOT INSTALLED for simplicity's sake.
All credits go to @orma1 and @rizkyxculture for your amazing efforts into this <3. None of it is mine, so thank them in their respective comments/threads if you wish to.
1. REMOVE ALL PASSWORDS AND FINGERPRINTS BEFORE PROCEEDING WHILE IN PIE, and do CLEAN DATA WIPE (do not choose the relock bootloader in Mi Flash Tool).
2. Do everything in that guide sent, and at the end, where rizky mentions flashing November update after the TWRP restore, don't do it. Instead, re-flash the March update. Thanks @orma1 for your comment. If your phone just straight up boots like mine did, without bootlooping, just power it off and go to fastboot again. Link to guide: https://forum.xda-developers.com/mi-a1/how-to/tutorial-downgrade-9-0-to-8-1-edl-imei-t3879624.
3. Once your phone boots normally, go to developer options, and uncheck the automatic system updates to prevent it from going to pie automatically later on. in the future. Install GCam at this stage if you wish (follow manual installation guide on XDA). Link: https://forum.xda-developers.com/showpost.php?p=75541654&postcount=98
4. After you've installed GCam (which is why you're probably doing all this in the first place, or not, regardless), chances are you still want to keep your warranty (and for security reasons) and therefore you should relock your bootloader, else the servicemen are just going to see that BIG warning at your phone's boot, and are likely revoke any warranty straight up. To do this, simply go back to fastboot and type the command below in Command Prompt and WHILE FIRMLY PRESSING AND HOLDING THE VOLUME DOWN BUTTON (or copy paste the line below WHILE FIRMLY PRESSING AND HOLDING THE VOLUME DOWN BUTTON):
fastboot oem lock
Once it says okay, type the following command:
fastboot reboot
Done. Now reboot, go to system update, and download and install the November update. Enjoy your still in warranty Mi A1 with Oreo and/or GCam (just make sure you uninstall the apk when giving it to the service center should you ever need to service it). Also, the power down button press prevents the auto data wipe function from activating. Have fun.
Also I have verified this works even on the April 2019 update. Just don't update any further, else I can't be sure.
Nafis-ul-Islam said:
So I'm one of those people that just jumped onto the Pie release as soon as it came out, and realized only afterwards that it was by far the worst update I could've hoped for. It completely broke the focus on my GCam, (and added on top an absolutely crap UI that is in every way a downgrade from oreo's UI). I wasn't too depressed initally though, as I guessed I could easily downgrade to a previous stock version. Now after reading some posts here and there I realized that I cannot roll back my device thanks to some anti-rollback feature the Xiaomi gods implemented in Pie, and that rolling back results in a bootloop. I've seen some threads where they give a separate EFS file IIRC, but I'm quite skeptical about using it as it contains IMEI info that is unique to every device, so it might conflict with my own IMEI. Hence why I'm hesistant to flash my phone and probably face a repair bill involving a motherboard change as a consequence.
So my question is, what exactly should I do to safely revert back to Oreo (that absolutely guaranteed works, retaining IMEI and everything else), and if not, how can I fix GCam on this phone?
Aside from that I did check whether the anti-rollback feature was enabled or not using the commands, to be sure:
adb reboot bootloader
fastboot getvar anti
and got the result:
Anti:
Which makes me think it's just some dud. So am I good to just flash the oreo xiaomi stock rom using xiaomi flash tool by unlocking the bootloader first?
EDIT: I'm running the March 5 security patch.
Click to expand...
Click to collapse
If you can't find documentation of anyone else successfully downgrading from Pie to Oreo with this specific device, then no one knows what is or isn't safe. In this case, you'll be taking a shot in the dark.
If you "can" find documentation of someone successfully downgrading, just do what they did.
Other than that, you'll have to blaze your own new trail.
Sent from my LGL84VL using Tapatalk
Droidriven said:
If you can't find documentation of anyone else successfully downgrading from Pie to Oreo with this specific device, then no one knows what is or isn't safe. In this case, you'll be taking a shot in the dark.
If you "can" find documentation of someone successfully downgrading, just do what they did.
Other than that, you'll have to blaze your own new trail.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
Guess I'll just stick to pie and bite the sand and live with it till someone gets a solid, working method...
As a second thought, if I make a backup of everything (system, boot, etc. etc.) in TWRP and then carry out the flashing process, will reflashing those backups restore my device in case of a brick?
Nafis-ul-Islam said:
So I'm one of those people that just jumped onto the Pie release as soon as it came out, and realized only afterwards that it was by far the worst update I could've hoped for. It completely broke the focus on my GCam, (and added on top an absolutely crap UI that is in every way a downgrade from oreo's UI). I wasn't too depressed initally though, as I guessed I could easily downgrade to a previous stock version. Now after reading some posts here and there I realized that I cannot roll back my device thanks to some anti-rollback feature the Xiaomi gods implemented in Pie, and that rolling back results in a bootloop. I've seen some threads where they give a separate EFS file IIRC, but I'm quite skeptical about using it as it contains IMEI info that is unique to every device, so it might conflict with my own IMEI. Hence why I'm hesistant to flash my phone and probably face a repair bill involving a motherboard change as a consequence.
So my question is, what exactly should I do to safely revert back to Oreo (that absolutely guaranteed works, retaining IMEI and everything else), and if not, how can I fix GCam on this phone?
Aside from that I did check whether the anti-rollback feature was enabled or not using the commands, to be sure:
adb reboot bootloader
fastboot getvar anti
and got the result:
Anti:
Which makes me think it's just some dud. So am I good to just flash the oreo xiaomi stock rom using xiaomi flash tool by unlocking the bootloader first?
EDIT: I'm running the March 5 security patch.
Click to expand...
Click to collapse
Just flashing oreo from pie should cause IMEI loss.
I used the method from here: https://forum.xda-developers.com/mi-a1/how-to/tutorial-downgrade-9-0-to-8-1-edl-imei-t3879624
although I had to do his method a little differently.
also make sure if you can to backup your data as you can lose it in the process.
first of all, after oreo march update flash, my phone did boot but with no IMEI.
second of all, flashing November update after restoring IMEI caused bootloop, instead you need to flash march update again. afterwards your phone should boot with the correct IMEI (you can double check with the one on your phone's box) . worked for me with two Mi A1s.
after all of this I was able to update to 8.1 November update via system update in the settings.
and lastly I made sure to disable automatic system update from developer settings.
Good luck!
Wanted to post same question.
As you described, there is method for downgrade but you are restoring someone else EFS partition, for that i am skeptical too.
Should we just downgrade as usual to Oreo using Mi Flash Tool? Or that thread is the only way of downgrading to Oreo?
Will i backup my IMEI if i backup EFS partition trought TWRP (Running Lineage OS 16.0)
Meme :D said:
Wanted to post same question.
As you described, there is method for downgrade but you are restoring someone else EFS partition, for that i am skeptical too.
Should we just downgrade as usual to Oreo using Mi Flash Tool? Or that thread is the only way of downgrading to Oreo?
Will i backup my IMEI if i backup EFS partition trought TWRP (Running Lineage OS 16.0)
Click to expand...
Click to collapse
I was skeptical at first too, but after using this method I compared the new IMEI to the one I have on the phone's box and they matched.
So this method restores your IMEI and not the IMEI of the one who created the backup.
Downgrade as usual resulted for me in lost IMEI (which means the phone is basically useless because the sim bluetooth and wifi don't work) so you shouldn't do it.
Using the method you talked about you restore boot and efs. boot will probably won't be the same as it's not the same android version and it is also a custom rom.
Anyways, using the method I sent should help you downgrade to stock oreo successfully with your IMEI.
orma1 said:
I was skeptical at first too, but after using this method I compared the new IMEI to the one I have on the phone's box and they matched.
So this method restores your IMEI and not the IMEI of the one who created the backup.
Downgrade as usual resulted for me in lost IMEI (which means the phone is basically useless because the sim bluetooth and wifi don't work) so you shouldn't do it.
Using the method you talked about you restore boot and efs. boot will probably won't be the same as it's not the same android version and it is also a custom rom.
Anyways, using the method I sent should help you downgrade to stock oreo successfully with your IMEI.
Click to expand...
Click to collapse
Thanks, will see about all this.
orma1 said:
I was skeptical at first too, but after using this method I compared the new IMEI to the one I have on the phone's box and they matched.
So this method restores your IMEI and not the IMEI of the one who created the backup.
Downgrade as usual resulted for me in lost IMEI (which means the phone is basically useless because the sim bluetooth and wifi don't work) so you shouldn't do it.
Using the method you talked about you restore boot and efs. boot will probably won't be the same as it's not the same android version and it is also a custom rom.
Anyways, using the method I sent should help you downgrade to stock oreo successfully with your IMEI.
Click to expand...
Click to collapse
Sorry for my delayed response firstly, I'm currently in the countryside and the network here is *God awful*. I'll definitely check this out when I get back home this Saturday hopefully. How did you back up though? Did you boot temporarily to TWRP in fastboot and then backup everything to an external storage?
Nafis-ul-Islam said:
Sorry for my delayed response firstly, I'm currently in the countryside and the network here is *God awful*. I'll definitely check this out when I get back home this Saturday hopefully. How did you back up though? Did you boot temporarily to TWRP in fastboot and then backup everything to an external storage?
Click to expand...
Click to collapse
I used the backup from this thread
https://forum.xda-developers.com/mi-a1/how-to/tutorial-downgrade-9-0-to-8-1-edl-imei-t3879624
It's a backup of someone else's efs and boot patiotions. At first I thought too that restoring someone else's backup should result in me getting his IMEI.
But after trying to restore through this backup My IMEI changed from 0 to the one on my phone's original box meaning I got my own IMEI. the method there worked perfectly for me and now I am rocking 8.1 Oreo November update with Magisk and TWRP. the only thing is that following step 10 in the tutorial there resulted in a bootloop for me. Instead I followed the suggestion of one of the comments saying that instead of flashing November update after restoring IMEI you need to flash the same March update you flashed before. this time my phone booted with IMEI and I updated to 8.1 November through OTA.
Did you downgraded succesfully?
Meme :D said:
Did you downgraded succesfully?
Click to expand...
Click to collapse
I was able to downgrade successfully following this guide: https://forum.xda-developers.com/mi-a1/how-to/tutorial-downgrade-9-0-to-8-1-edl-imei-t3879624
In step 10 you need to flash oreo march update again and not November update as mentioned as flashing November update caused me bootloop.
afterwards you can update to November update via System update in the settings.
besides this I followed the tutorial exactly and was able to downgrade two Mi A1s.
I have successfully downgraded my Mi A1 with this thread
"Tutorial Downgrade 9.0 to 8.1 No EDL, No IMEI Problem & No Signal Problem"
Also im a 14 Yr old nearly 15 on April 20.
I was afraid too, now I'm on Nougat )
Just follow this tutorial : https://forum.xda-developers.com/mi-a1/how-to/tutorial-downgrade-9-0-to-8-1-edl-imei-t3879624
Before doing anything, boot TWRP and create a full backup of your system, after that transfer it to your PC. Probably you don't need it but better safe than sorry.
After you will flash March firmware, your phone will boot but you will not have signal, it's okay. Thing is, you don't lose the IMEI, it's still there, but somehow you lose the signal. Boot TWRP again, create a backup of your boot and EFS, you will see TWRP folder in your phone, go there and you will see a backup. Remove your backup files and replace them with the one from the guide, then you can restore them without issues (you will see a modem error, ignore it). Restart and let it boot a bit, then go to bootloader again, flash March firmware again (don't flash the November one! ignore that from the guide) and the signal will be back. If you do this, I doubt you will lose your IMEI somehow. I never lost mine, it's the same from the box.
Good luck! Make sure you go in developer settings after and disable automatic updates or you will be back to Pie. I rooted my phone so it can't update.
Just flashed it now, and it's working perfectly as orma1 described. I can't thank you enough <3
Nafis-ul-Islam said:
Just flashed it now, and it's working perfectly as orma1 described. I can't thank you enough <3
Click to expand...
Click to collapse
I'm happy to help
but all the credit goes to rizkyxculture for finding this method and ibooth2004 for correcting us to flash March update again instead of the November one.
so glad i read this and got the courage to go back, now downloading november ota, pie on this device is so bad, and cant even use gcam.
Marcos OC said:
so glad i read this and got the courage to go back, now downloading november ota, pie on this device is so bad, and cant even use gcam.
Click to expand...
Click to collapse
I agree the system's performance on pie is horrible and also the mic volume is low which is very annoying.
Related
Ok, I unlocked bootloader and rooted. No issues at all.
Now, I was curious on relocking the bootloader & load stock rom.
The method that I used to flashed the firmware was the Autoflash, something like that.
Now what I did was extracted all the files within that folder. And click the autoflash, mijiggy. Lol
But I believe the most current firmware was MPH24.49-18
BUT I had MPHS24.49-16 - from what I can recall.
Pretty sure that was the latest on the site.
After flashing the phone, it successfully with any issues. The root is no longer present.
But no matter how many times that I add "fastboot oem lock" which does say okay - finished.
I still get that bootloader is unlocked, after it told me it was finished, no errors....
The other issue is upgrading the software OTA, failed!
As far as the radio part, I hope it still works. I don't have an extra Sprint sim card. But I'm pretty sure it will be ok.
Appreciate your help and time to read my crazy thread..lol
Sent from my Portable
PassatSport15 said:
Ok, I unlocked bootloader and rooted. No issues at all.
Now, I was curious on relocking the bootloader & load stock rom.
The method that I used to flashed the firmware was the Autoflash, something like that.
Now what I did was extracted all the files within that folder. And click the autoflash, mijiggy. Lol
But I believe the most current firmware was MPH24.49-18
BUT I had MPHS24.49-16 - from what I can recall.
Pretty sure that was the latest on the site.
After flashing the phone, it successfully with any issues. The root is no longer present.
But no matter how many times that I add "fastboot oem lock" which does say okay - finished.
I still get that bootloader is unlocked, after it told me it was finished, no errors....
The other issue is upgrading the software OTA, failed!
As far as the radio part, I hope it still works. I don't have an extra Sprint sim card. But I'm pretty sure it will be ok.
Appreciate your help and time to read my crazy thread..lol
Click to expand...
Click to collapse
A few problems here... First off, you likely had MPHS24.49-18-16 not just 16 (I don't think there is such a version) and the one your using MPHS24.49-18 is really old, it's the original MM firmware from Moto's website (the one on Moto's site is very old and dated incorrectly). We don't have the 18-16 image yet, so you cannot relock or even effectively fix this.
Also, you used a tool to flash, so when pieces failed to flash, you didn't even know it... And now you are in a mixed state with a ROM that is partially -18 and part 18-16, which is why an OTA won't take.
When you relock a Moto device, you don't just enter "fastboot oem lock" like a Nexus device, there is a process where you start with "fastboot oem lock begin" then flash a complete, signed factory image, wipe, and end with "fastboot oem lock" in one process.
Many parts to this process went wrong... Right now you are just kind of stuck.
BTW, relocking the bootloader has no effective gains except security... You will still be able to see in a glance it was unlocked from the bootloader screen or a fastboot command and the unlocked bootloader warning screen will still be there (you have to flash a custom logo to make it go away).
Did you make a backup of your stock ROM with TWRP prior to rooting? Restoring the backup with TWRP along with stock recovery is usually going to be the simplest and easiest way to go back to full stock.
As acejavelin stated, there really is no benefit to relocking the bootloader except from a security standpoint. As long as the stock ROM and recovery are restored to preroot condition with no system mods, you can take OTAs regardless of bootloader status.
acejavelin said:
First off, you likely had MPHS24.49-18-16 not just 16 (I don't think there is such a version) and the one your using MPHS24.49-18 is really old
Click to expand...
Click to collapse
My apologies for giving the incorrect info.
When I had purchased the phone about 3 weeks ago.
I upgraded the latest software update via Sprint OTA.
acejavelin said:
And now you are in a mixed state with a ROM that is partially -18 and part 18-16, which is why an OTA won't take.
Click to expand...
Click to collapse
What would be the best route for me to learn.?
The phone is not going anywhere. It is a backup phone, current have a Note 5. So I might as well take advantage of the opportunity.
Being that I'm mixed with 16 - 18 firmware, should I get the latest MM? Or am I just Fubarred..lol
Now what is the latest MM that I can download? Only because I would like to do an OTA when Nougat comes out.
I guess my goal is to start fresh again which seems impossible for now..
Any advice would be greatly appreciated! Thank you again!
Sent from my Portable
PassatSport15 said:
My apologies for giving the incorrect info.
When I had purchased the phone about 3 weeks ago.
I upgraded the latest software update via Sprint OTA.
What would be the best route for me to learn.?
The phone is not going anywhere. It is a backup phone, current have a Note 5. So I might as well take advantage of the opportunity.
Being that I'm mixed with 16 - 18 firmware, should I get the latest MM? Or am I just Fubarred..lol
Now what is the latest MM that I can download? Only because I would like to do an OTA when Nougat comes out.
I guess my goal is to start fresh again which seems impossible for now..
Any advice would be greatly appreciated! Thank you again!
Click to expand...
Click to collapse
I think 18-12 is the latest we have so far, but trying to flash it would not help... Your best bet at this point is either custom ROM or wait until we can get the image for 18-16. The problem here is Moto's don't support downgrading, it can be done but it often leaves you in a mixed state.
You could try flashing the latest version we have available manually (don't use a tool) and it might be close enough to able to OTA from there. You have some though, rumor has it initial surveys for an upgrade on the Pure just went out to MFN users this week, assuming it is the Nougat upgrade trial then once it starts you have 4-6 weeks barring any problems they encounter before public release. Assuming of course that history repeats itself and Lenovo follows the same path as Moto has previously.
So basically I'm saying have patience... We don't know when (or really if) we will get the current firmware image, sometimes it's quick and sometimes it takes months.
Update on my xt1575, that I could not take an OTA, it gave me an error - unsuccessful.
My original software was MPHS24.49-18-16, December update, latest software.
Well, I went ahead unlocked the bootloader, installed TWRP, then rooted....
Days later I had decided to unroot, so I would be able to take the OTA.
While I unrooted my device, it was successful, but could not take the updates at all.
Now I reflashed again, in this order below.
Autoflash Script with MPHS24.49-18-8.
Reboot the phone, checked if it was unrooted (No root)
Now I went to software update, and the phone did it's upgrade, like last time. Did the update, device rebooted and it was SUCCESSFUL!
I am finally back to the original software MPHS24.49-18-16
Which was December 2016 update.
Sent from my Portable
I've decided that I'm not really ready for Oreo on this phone until Lineage 15.1 is final with all features ported. I'm going back to stock and I'm wondering - are there any side effects to doing so? I've heard that people have permanently lost VoLTE, had IMEI issues, etc. I'm very wary of trying anything that I'm not sure about... does anyone have information on this?
Many thanks.
Make sure you use latest software for your region, also whether retail version or not.
Other than that good luck
Ray
I flashed the stock ROM for my device and it's running just fine with no errors. I pass SafetyNet and my bootloader says I'm on the official firmware.
The IMEI issue seems to be related to stock fastboot.
So you can either skip flashing that or flash a TWRP flashable stock ROM.
bornlivedie said:
The IMEI issue seems to be related to stock fastboot.
So you can either skip flashing that or flash a TWRP flashable stock ROM.
Click to expand...
Click to collapse
By saying "skip flashing that" what do you mean?
Jrhotrod said:
By saying "skip flashing that" what do you mean?
Click to expand...
Click to collapse
Fastboot ROM, I think
If you fastboot flash stock rom and have Oreo 8.1 as your system now, don't do it!. You will lose voLTE and will most likely lose 4g (avoidable by skipping the two modem wipe commands). Until official Oreo, there may be no way to get voLTE back for those (myself included) who lost it. Unfortunately, even official Oreo may not fix the voLTE, it could be borked forever.
As said above, right now, safest way to go stock is to flash the twrp version, however, you still lose 4g unless the modem commands are removed from the updater-script or, you backup your efs partition in twrp of your current working system, restoring it over stock rom.
I didn't notice any side effects. Though I probably lost VoLTE, but since I didn't even know it existed or that people used voices to communicate on these things, it didn't really affect me I guess.
Yesterday though, I went like this -> Unlocked Stock -> Pixel XP -> OmniRom - Unlocked Stock NO IMEI -> Pixel XP -> Locked Stock. And I think I'm going back to Pixel XP today lol.
C--Dog said:
I didn't notice any side effects. Though I probably lost VoLTE, but since I didn't even know it existed or that people used voices to communicate on these things, it didn't really affect me I guess.
Yesterday though, I went like this -> Unlocked Stock -> Pixel XP -> OmniRom - Unlocked Stock NO IMEI -> Pixel XP -> Locked Stock. And I think I'm going back to Pixel XP today lol.
Click to expand...
Click to collapse
Wait - so locking your bootloader after flashing stock fixes the issue?
Fixes what issue? The IMEI thing? There's a whole thread on it. And one way was to flash Pixel, then flash stock. It's a little more complicated than that, but that's the gist.
I think VoLTE is not getting fixed, if that's what you meant.
C--Dog said:
Fixes what issue? The IMEI thing? There's a whole thread on it. And one way was to flash Pixel, then flash stock. It's a little more complicated than that, but that's the gist.
I think VoLTE is not getting fixed, if that's what you meant.
Click to expand...
Click to collapse
You may be about to save me. You got a link to that thread?
Edit: And no, I really don't care about VoLTE. Only reason I would is if I sell this phone to some Indian (which I won't, this phone is amazing)
Jrhotrod said:
You may be about to save me. You got a link to that thread?
Edit: And no, I really don't care about VoLTE. Only reason I would is if I sell this phone to some Indian (which I won't, this phone is amazing)
Click to expand...
Click to collapse
Here ya go:
https://forum.xda-developers.com/g5-plus/help/restore-imei-0-moto-g5-xt1687-t3739808
Even the TWRP Stock ROM destroyed my IMEI. Don't try
Since the Oreo update, notifications from ALL play store apps are barely audible. Built in/system sounds are not effected. Have tried uninstalling/reinstalling apps, and a factory reset. Issue still persists. Like so low that I can't even hear them with the volume on max unless the phone is right next to my head.
Phone is not rooted and never has been. It is also NOT the Amazon variant, it is non carrier specific purchased from Walmart. Do I just need to follow a rooting guide for Oreo, then simply fastboot flash stock 7.0 & be sure to disable the update service afterwards? Do I need to worry about bootloader stuff or anything else? Or just flash the stock 7.0 image as is?
plastic_green_head said:
Since the Oreo update, notifications from ALL play store apps are barely audible. Built in/system sounds are not effected. Have tried uninstalling/reinstalling apps, and a factory reset. Issue still persists. Like so low that I can't even hear them with the volume on max unless the phone is right next to my head.
Phone is not rooted and never has been. It is also NOT the Amazon variant, it is non carrier specific purchased from Walmart. Do I just need to follow a rooting guide for Oreo, then simply fastboot flash stock 7.0 & be sure to disable the update service afterwards? Do I need to worry about bootloader stuff or anything else? Or just flash the stock 7.0 image as is?
Click to expand...
Click to collapse
I would suggest that the only way to do it safely is to unlock and root, then do a clean flash of the TWRP flashable nougat builds.
If you go from Oreo to nougat you will lose your IMEI, unless you change ownership of specific files and folders in your persist partition. There's no way to do that without root.
https://forum.xda-developers.com/g5-plus/development/twrp-flashable-stock-builds-t3813351
NZedPred said:
I would suggest that the only way to do it safely is to unlock and root, then do a clean flash of the TWRP flashable nougat builds.
If you go from Oreo to nougat you will lose your IMEI, unless you change ownership of specific files and folders in your persist partition. There's no way to do that without root.
https://forum.xda-developers.com/g5-plus/development/twrp-flashable-stock-builds-t3813351
Click to expand...
Click to collapse
Thanks. It looks like backing up my persist & ESF should eliminate any worries regarding loss of IMEI.
plastic_green_head said:
Thanks. It looks like backing up my persist & ESF should eliminate any worries regarding loss of IMEI.
Click to expand...
Click to collapse
Well if by backing up you mean backing up persist and efs on Oreo then u might have issues. I dont think Oreo backup would work on Nougat. There was a thread tho on this exact topic. So you need to leave out gpt and some other partition if u fastboot flash it. You cannot downgrade the bootloader. I'm sure u know that. Safer way would be to flash via TWRP.
GL:good:
debdeep98 said:
Well if by backing up you mean backing up persist and efs on Oreo then u might have issues. I dont think Oreo backup would work on Nougat. There was a thread tho on this exact topic. So you need to leave out gpt and some other partition if u fastboot flash it. You cannot downgrade the bootloader. I'm sure u know that. Safer way would be to flash via TWRP.
GL:good:
Click to expand...
Click to collapse
Hmmmm. TWRP it is then. I have plenty of experience with TWRP, but I haven't flashed a phone in MANY years. One thing about the page you linked to. It states "An important note for those who have flashed custom Oreo roms. It is a frequent issue regarding Oreo roms that the device's IMEI is set to 0 in certain conditions."
So since my phone is on stock ota Oreo & not a custom Oreo rom... do I need to even worry about losing IMEI? Maybe I should ask in that thread?
plastic_green_head said:
Maybe I should ask in that thread?
Click to expand...
Click to collapse
Yes that sounds good.
Please mirror.
ui_print("Target: motorola/aljeter/aljeter:9/PPP29.41/b1fe5:user/release-keys");
Download
As far as I know, you must be on the Sept. patch. So, you must downgrade firmware first. It also appears to be for the Aljeter only, so I don't know if it'll work on the Jeter.
I am not responsible for any bricked devices.
1. Downgrade to OPP27.91-143 first.
2. Extract gpt_main0.bin from the ota zip and flash it in fastboot.
fastboot flash partition gpt_main0.bin
3. Reboot to recovery, and apply the OTA update from your sdcard.
4. Let the system restart. It'll take about 10min.
Could anyone verify?
Figures it's for Aljeter. Makes me wonder if Jeter will get it at all.
yes it is for aljeter and is working fine
Spaceminer said:
Please mirror.
ui_print("Target: motorola/aljeter/aljeter:9/PPP29.41/b1fe5:user/release-keys");
Download
As far as I know, you must be on the Sept. patch. So, you must downgrade firmware first. It also appears to be for the Aljeter only, so I don't know if it'll work on the Jeter.
These installation steps need confirmation. I am not responsible for any bricked devices.
1. Downgrade to OPP27.91-143 first.
2. Extract gpt_main0.bin from the ota zip and flash it in fastboot.
fastboot flash partition gpt_main0.bin
3. Reboot to recovery, and apply the OTA update from your sdcard.
4. Let the system restart. It'll take about 10min.
Click to expand...
Click to collapse
Tested and working on G6 Play do Brasil!
Up and running in UK. G6 Play XT1922-2, Carrier: ID Mobile (Carphone Warehouse), retgb.
Can't get root though, Magisk won't install for me in TWRP. Unable to mount storage or OEM. Not that fussed about that though.
Butter smooth, no glitches so far, no random reboots, battery life is great but still under observation.
Eddster3000 said:
Up and running in UK. G6 Play XT1922-2, Carrier: ID Mobile (Carphone Warehouse), retgb.
Can't get root though, Magisk won't install for me in TWRP. Unable to mount storage or OEM. Not that fussed about that though.
Butter smooth, no glitches so far, no random reboots, battery life is great but still under observation.
Click to expand...
Click to collapse
That's a Pie/Magisk problem. Easy fix...
1. Format /data in TWRP using the "yes" option. Then reboot directly back into recovery.
2. Mount /vendor then flash the universal dm-verity disabler by zackptg5.
3. Reboot directly into recovery once more and flash Magisk.
4. Reboot normally, and install the Magisk manager app manually. Done.
(Magisk should disable encryption and verity, but I've never had it work %100 of the time for both. Hence the disabler.)
Spaceminer said:
That's a Pie/Magisk problem. Easy fix...
1. Format /data in TWRP using the "yes" option. Then reboot directly back into recovery.
2. Mount /vendor then flash the universal dm-verity disabler by zackptg5.
3. Reboot directly into recovery once more and flash Magisk.
4. Reboot normally, and install the Magisk manager app manually. Done.
(Magisk should disable encryption and verity, but I've never had it work %100 of the time for both. Hence the disabler.)
Click to expand...
Click to collapse
Thanks @Spaceminer !!!! I'll give it a go. I thought at first that I might need to make some sort of patched boot image and faff about quite a bit but your instructions are clear and straightforward.
I must say I'm impressed with the G6 Play. I had a Nexus 6P and a Pixel both of which died on me from physical and customisation fatigue. I could afford a flagship so got this to see be through and I haven't had one complaint yet.
The handful of Pie features and esthetics have been implemented well by Motorola and battery life is still epic on this device.
Edit: rooted and fully set up how I usually have my daily driver handset. Pie is so tasty!
Eddster3000 said:
Up and running in UK. G6 Play XT1922-2, Carrier: ID Mobile (Carphone Warehouse), retgb.
Can't get root though, Magisk won't install for me in TWRP. Unable to mount storage or OEM. Not that fussed about that though.
Butter smooth, no glitches so far, no random reboots, battery life is great but still under observation.
Click to expand...
Click to collapse
Ta for taking the plunge and testing mate! Was beginning to think we'd never get this thing, glad to know it works on the same model number as I've got
Now to figure out the exact detailed step-by-step to getting this going, considering I'm actually on the November update...
picopi said:
Ta for taking the plunge and testing mate! Was beginning to think we'd never get this thing, glad to know it works on the same model number as I've got
Now to figure out the exact detailed step-by-step to getting this going, considering I'm actually on the November update...
Click to expand...
Click to collapse
Op is a step by step. Literally. Downgrade to Sept = Flash the build specified. Except the bootloader etc.
Flash the gpt.bin from the new build, apply update.
madbat99 said:
Op is a step by step. Literally. Downgrade to Sept = Flash the build specified. Except the bootloader etc.
Flash the gpt.bin from the new build, apply update.
Click to expand...
Click to collapse
Well yeah, I know that much. I meant the extra stuff like unlocking bootloader and downgrading the firmware etc lol. Ta for the extra info, mind.
Extra questions though because despite being having novice experience of doing phone flashing stuff, I've never touched a soak test for official firmware before...but I'm guessing I'll have to move back to Oreo temporarily to get the official Pie update...? Or will it just shift up from this soak test version?
Anyone get this working with the xt1922-7?
Donavonn said:
Anyone get this working with the xt1922-7?
Click to expand...
Click to collapse
No dice! The bootloader won't accept the gpt.bin. I think the recovery partition is the only thing that gets expanded though, so... I think if someone makes a back up of Pie in TWRP, then I can make it work on our phone. My idea is this.
1. Restore a Pie system backup using twrp, including the boot.img.
2. Use fastboot to flash the modem, oem.img, and vendor.img. Basically flash every part that isn't a patch file.
3. Hope that crap works.
I think that, or something similar would make it happen. I'll be the lab rat if someone wants to upload a system backup.
Spaceminer said:
No dice! The bootloader won't accept the gpt.bin. I think the recovery partition is the only thing that gets expanded though, so... I think if someone makes a back up of Pie in TWRP, then I can make it work on our phone. My idea is this.
1. Restore a Pie system backup using twrp, including the boot.img.
2. Use fastboot to flash the modem, oem.img, and vendor.img. Basically flash every part that isn't a patch file.
3. Hope that crap works.
I think that, or something similar would make it happen. I'll be the lab rat if someone wants to upload a system backup.
Click to expand...
Click to collapse
Haha yes! Someone get this guy a backup! Also, if it does work, the UI and everything can be changed to English, right?
Okay quick question, considering it was said "Flash the build specified except bootloader etc."; what is meant by "etc" here? Which parts of the older firmware should I avoid flashing. I know I gotta get in on that sparsechunk action but what about the other stuff like fsg, modem, boot etc? Sorry for asking what's probably a very obvious question but I don't wanna accidentally bugger my phone up trying to get this working
Donavonn said:
Haha yes! Someone get this guy a backup! Also, if it does work, the UI and everything can be changed to English, right?
Click to expand...
Click to collapse
Yes, it should be possible on the first setup. I think if it works, LTE probably won't without an APN edit. That's what happens when I flash xt1922-5 RETUS firmware anyways.
picopi said:
Okay quick question, considering it was said "Flash the build specified except bootloader etc."; what is meant by "etc" here? Which parts of the older firmware should I avoid flashing. I know I gotta get in on that sparsechunk action but what about the other stuff like fsg, modem, boot etc? Sorry for asking what's probably a very obvious question but I don't wanna accidentally bugger my phone up trying to get this working
Click to expand...
Click to collapse
Flash every part of the old firmware that you are able to. The bootloader and gpt.bin usually fail to flash if they are older than your current version. You should still try anyways. If they fail, just continue flashing the next items in line.
Spaceminer said:
Flash every part of the old firmware that you are able to. The bootloader and gpt.bin usually fail to flash if they are older than your current version. You should still try anyways. If they fail, just continue flashing the next items in line.
Click to expand...
Click to collapse
Righto. Just to clarify, I'm gonna need to unlock my bootloader to make this downgrade happen, right?
picopi said:
Righto. Just to clarify, I'm gonna need to unlock my bootloader to make this downgrade happen, right?
Click to expand...
Click to collapse
Official firmware should flash without any issue on a locked bootloader. That's my understanding. I don't know if this is %100 accurate. Every Motorola I've ever had, I unlocked the bootloader immediately. So, I've never had to test this.
Spaceminer said:
Official firmware should flash without any issue on a locked bootloader. That's my understanding. I don't know if this is %100 accurate. Every Motorola I've ever had, I unlocked the bootloader immediately. So, I've never had to test this.
Click to expand...
Click to collapse
Righto. In that case I'll report back with my findings, but yeah I'd imagine it should work fine as well. We'll see, fingers crossed.
So the new security patch bricked my 8 pro into qualcomm crash dump screen.
I have done no funny business at all, yes my bootloader is unlocked and yes I have root. But it is only for basic things like titanium backup and permission ruler. I have never done anything crazy with my phone, never even flashed a rom, my phone has been rooted for well over a year and I always install all the security patches so this was super random and I'm pissed off.
Anyways I cannot find a video about recovering the phone without erasing everything and I thought this was only necessary when you DON'T have an unlocked bootloader. I thought it was possible to flash oxygen with fastboot and it fixes the problem. But I just dont know exactly how to do this and I didnt want to screw up anything. I'm totally fine with losing root and having the bootloader locked again I just really want to save my data. Any help and I would be grateful, because at this point I'm going to work tommorow without my phone.
one way... MSM tool and ITS deleting all your files
beterman said:
one way... MSM tool and ITS deleting all your files
Click to expand...
Click to collapse
wow man, this literally came from the security patch
If phone is accessible via ADB ( no bootloop ! ) then you can pull the data of interest by means of ADB-commands to a connected computer.
Look inside here:
[TOOL][ADB][WIN]Android Partitions Backupper / Cloner
Hi all, wrote a Windows CMD script that backups / clones partitions of an Android device via ADB because I wasn't content with any 3rd-party APK what claims to do this job. The backups /clones are stored on Windows computer as...
forum.xda-developers.com
Codeman785 said:
So the new security patch bricked my 8 pro into qualcomm crash dump screen.
I have done no funny business at all, yes my bootloader is unlocked and yes I have root. But it is only for basic things like titanium backup and permission ruler. I have never done anything crazy with my phone, never even flashed a rom, my phone has been rooted for well over a year and I always install all the security patches so this was super random and I'm pissed off.
Anyways I cannot find a video about recovering the phone without erasing everything and I thought this was only necessary when you DON'T have an unlocked bootloader. I thought it was possible to flash oxygen with fastboot and it fixes the problem. But I just dont know exactly how to do this and I didnt want to screw up anything. I'm totally fine with losing root and having the bootloader locked again I just really want to save my data. Any help and I would be grateful, because at this point I'm going to work tommorow without my phone.
Click to expand...
Click to collapse
Far as I'm aware the security patch was incremental and not a full update, seeing as you're rooted then I'd advise against installing incremental updates, when you update get the full one and pull the boot image for instances just like this.
Easiest way out of this is MSM although if you can obtain the boot image from 9.9 then you may be able to save it by booting that image / patched image.