Related
Been busy, still have not unlocked/rooted my 6P.
I've got the OTA for N 7.0 waiting to install - is there anything that will screw me up from fastboot flashing back to a previous image if I take the OTA to 7.0 and then do the fastboot flashing unlock and unlock the phone while on 7.0.
I'm guessing it should be like all Nexus devices still where you can always go back, but I have noticed some people having issues when trying to downgrade. If it trips anything up I'll wait, but if I can take the OTA and then unlock, rooting, downgrade, upgrade, ROM, etc as usual, I'll give N a go first.
Sent from my Nexus 6P using Tapatalk
You should be able to do everything you said in your post. I've done the same things multiple times with no problems whatsoever. That's the beauty of a Nexus device.
10-4. Previous Nexus experience with the n7 2013 was that way, just had seen some people having brick issues while trying to downgrade
Sent from my Nexus 6P using Tapatalk
Norcalz71 said:
10-4. Previous Nexus experience with the n7 2013 was that way, just had seen some people having brick issues while trying to downgrade
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
That was due to TWRP 3.0.2-1 having a bug restoring EFS partitions. If you are fastboot flashing a factory MM image, you should be fine.
Sent from my Nexus 6P using Tapatalk
Since you're stock, locked and unrooted... YMMV
On multiple forums, it was suggested that right vendor.img should work for downgrade
I installed Android 7 Nougat by flashing WETA 8 ROM on unlocked bootloader
To revert to Marshmallow, I was able flash the vendor.img along with radio.img and bootloader.img and then MM ROM from https://androidfilehost.com/?w=files&flid=88221
aviralmsharma said:
Since you're stock, locked and unrooted... YMMV
On multiple forums, it was suggested that right vendor.img should work for downgrade
I installed Android 7 Nougat by flashing WETA 8 ROM on unlocked bootloader
To revert to Marshmallow, I was able flash the vendor.img along with radio.img and bootloader.img and then MM ROM from https://androidfilehost.com/?w=files&flid=88221
Click to expand...
Click to collapse
in my past experience with fastboot flashes, I never messed with any vendor.img. Is this a new thing?
My thought was to hop to 7.0, give it a run, and if necessary I would factory reset and fastboot flash myself back to 6.0.1. All stock, then go from there.
Norcalz71 said:
in my past experience with fastboot flashes, I never messed with any vendor.img. Is this a new thing?
My thought was to hop to 7.0, give it a run, and if necessary I would factory reset and fastboot flash myself back to 6.0.1. All stock, then go from there.
Click to expand...
Click to collapse
I too learnt about the vendor.img recently
The dev for WETA ROM included this in change log : "WETA V5.0 *reflashing vendor.img is essential for this update"
Since you are on stock ROM, would this for you?
http://www.gsmarena.com/heres_how_t...n_to_marshmallow_on_your_nexus-blog-17197.php
aviralmsharma said:
I too learnt about the vendor.img recently
The dev for WETA ROM included this in change log : "WETA V5.0 *reflashing vendor.img is essential for this update"
Since you are on stock ROM, would this for you?
http://www.gsmarena.com/heres_how_t...n_to_marshmallow_on_your_nexus-blog-17197.php
Click to expand...
Click to collapse
Vendor has been a thing all through MM, too. It includes binaries that allow Android to run and is updated with each new build. So, every ROM or monthly security update requires a matching vendor to work.
Sent from my Nexus 6P using Tapatalk
ultyrunner said:
Vendor has been a thing all through MM, too. It includes binaries that allow Android to run and is updated with each new build. So, every ROM or monthly security update requires a matching vendor to work.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Good to know! Thanks ultyrunner
ultyrunner said:
Vendor has been a thing all through MM, too. It includes binaries that allow Android to run and is updated with each new build. So, every ROM or monthly security update requires a matching vendor to work.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
10-4, but it just accompanies all the other images with each build stack? I DL'd 6.0.1 and looks like it's in there.
Big problems if you mismatch vendor.img and other img builds?
Sent from my Nexus 6P using Tapatalk
Norcalz71 said:
10-4, but it just accompanies all the other images with each build stack? I DL'd 6.0.1 and looks like it's in there.
Big problems if you mismatch vendor.img and other img builds?
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Yes, vendor is in each build of factory image. Many on here can't be bothered flashing from bootloader so they wait for someone to make a zip. If you have a mismatched vendor, you will get an error message on boot and your phone will likely exhibit anything from FCs of apps to bootloops to whatever.
Sent from my Nexus 6P using Tapatalk
My phone is unlocked and rooted. It wants to download the OTA but I know that Motorola says on their site you will have problems with the OTA. Should I download it or Should I flash a ROM.
mongoose96 said:
My phone is unlocked and rooted. It wants to download the OTA but I know that Motorola says on their site you will have problems with the OTA. Should I download it or Should I flash a ROM.
Click to expand...
Click to collapse
You must be PURE stock to take an OTA update, or it will fail and bootloop... Flash a rom if you wish.
What i did was make a back up of everything just incase and then look up the ota version on your phone and get it in the rom section and look up twrp flashable OTAs and just flash it. you might lose root but its easy to get back if you flash magisk again.
You can found the right guide here:
https://forum.xda-developers.com/g5-plus/how-to/guide-complex-ota-update-magisk-rooted-t3688175
does anyone have fastboot stock rom?
siddhesh9146 said:
does anyone have fastboot stock rom?
Click to expand...
Click to collapse
Of the current version? lol, no, we wish... we are averaging 3-6 months behind OTA releases for full ROM images, if we get them at all. Moto does not officially provide them, so they have to be leaked somehow, and sources are completely dried up yet, but it's getting there. :/
Hi. Can I get Oreo Ota for mi xt1670 with rooted device but locked BL? I'm on stock everything. Thanks.
mortadelax said:
Hi. Can I get Oreo Ota for mi xt1670 with rooted device but locked BL? I'm on stock everything. Thanks.
Click to expand...
Click to collapse
You can't be rooted with a locked bootloader so your question is obsolete.
You can apply to OTA with an unlocked bootloader.
You can't if you're rooted or changed anything else in /system or /vendor.
Sent from my Moto G5 Plus using XDA Labs
Wolfcity said:
You can't be rooted with a locked bootloader so your question is obsolete.
You can apply to OTA with an unlocked bootloader.
You can't if you're rooted or changed anything else in /system or /vendor.
Sent from my Moto G5 Plus using XDA Labs
Click to expand...
Click to collapse
Thanks for the reply. Very clear! Please I need more help. The thing is...I don't want the oreo ota right now. This is my mother's phone so I don't want any problem. Nougat is just fine for now. So I need to stop the upgrade notification spam. I believe I must unlock BL, then root, then freeze the upgrader app. Is that correct? I can't force stop the app. That's for now.
I've read bad reviews about oreo battery drain and other stuff. That's why I'm trying to avoid it.
If someday I want it, maybe will install some rom.
Thanks bro.
EDIT. Does this make sense? Or should I stay stock everything and take the ota/ignore the spam everyday?
EDIT 2. Another question. What happen if I take the oreo ota, and i don't like it. Can I unlock BL, root, install some nougat rom, as a pseudo downgrade?
mortadelax said:
Thanks for the reply. Very clear! Please I need more help. The thing is...I don't want the oreo ota right now. This is my mother's phone so I don't want any problem. Nougat is just fine for now. So I need to stop the upgrade notification spam. I believe I must unlock BL, then root, then freeze the upgrader app. Is that correct? I can't force stop the app. That's for now.
I've read bad reviews about oreo battery drain and other stuff. That's why I'm trying to avoid it.
If someday I want it, maybe will install some rom.
Thanks bro.
EDIT. Does this make sense? Or should I stay stock everything and take the ota/ignore the spam everyday?
EDIT 2. Another question. What happen if I take the oreo ota, and i don't like it. Can I unlock BL, root, install some nougat rom, as a pseudo downgrade?
Click to expand...
Click to collapse
Oreo ist absolutely fine, no problems with it.
I haven't heard of any issues like increased battery drain, for me nothing changed at all regarding battery and the rest is also working flawlessly.
It would be a lot of action to unlock and root the device just to stop the updater service.
If you don't have any other plans that need root privileges I recommend just taking the OTA (s).
If you want to run another ROM later you can always unlock the bootloader, install TWRP, root the device and install any kind of custom ROM, Nougat, Oreo or Pie. There are also TWRP flashable stock firmwares which make it easy to move between different stock versions.
Sent from my Moto G5 Plus using XDA Labs
Wolfcity said:
If you want to run another ROM later you can always unlock the bootloader, install TWRP, root the device and install any kind of custom ROM, Nougat, Oreo or Pie. There are also TWRP flashable stock firmwares which make it easy to move between different stock versions.
Click to expand...
Click to collapse
That's good. A pseudo downgrade is possible. Thanks man. I'll think about it. And yes, the root privileges is just for stopping the updater.
Cheers
EDIT. Man, are you sure about this? Taking the Oreo Ota, and in the future unlock BL, root and install whatever rom?
mortadelax said:
That's good. A pseudo downgrade is possible. Thanks man. I'll think about it. And yes, the root privileges is just for stopping the updater.
Cheers
EDIT. Man, are you sure about this? Taking the Oreo Ota, and in the future unlock BL, root and install whatever rom?
Click to expand...
Click to collapse
Yes I am.
Just check some of the custom ROM threads, there are some that need stock Nougat as base but the most of them need Oreo. For custom ROMs there are no up/downgrading problems, that's only the case for stock firmwares.
And as said above, there are TWRP flashable stock builds that doesn't have these problems too and will bring you to whatever stock firmware you want, not just pseudo. (Here:
https://forum.xda-developers.com/g5...o-twrp-flashable-stock-builds-coming-t3830482 )
So if you're on stock Oreo after unlocking the bootloader and flashing TWRP all options are open for you. Just don't forget to make a full nandroid backup incl. EFS and persist before you flash anything.
Sent from my Moto G5 Plus using XDA Labs
Hi, does anyone know if it is possible to downgrade S8 oreo to Nougat without a PC?
sorry, doubt it, not unless you did a full image backup with TWRP...
The easiest way is using smart switch, but un-register yourself from the beta program and ensure all your data is backed up as it will wipe the phone.
Sent from my SM-G950F using Tapatalk
I have a US XT1687 on LineageOS (2017-09-19 build), and I would like to flash the latest stock firmware (which I believe is the April NPNS25.137-93-10 update), while also continuing to receive future OTA updates
The fastboot stock firmware thread was closed.
I found these files https://mirrors.lolinet.com/firmware/moto/potter/official/RETAIL/ but I don't see the 93-10 update.
Can I flash the 93-4 update from that site via fastboot and then get the 93-10 update via OTA?
Thanks!
I believe it depends on what bootloader version you were on before. If you were on 93-4 or earlier, then theoretically you should be fine. If you were on the 93-10 version of the bootloader and attempted to flash to the 93-4 stock rom, and then take an OTA from there, you are very likely going to hard-brick your device.
There are a lot of active threads about flashing back to stock and losing IMEI and enhanced LTE, so I wouldn't risk it. Out of curiosity why would you want to flash back to stock Nougat? IMO the camera is worse and you're rolling back to an older OS.
dunderball said:
I believe it depends on what bootloader version you were on before. If you were on 93-4 or earlier, then theoretically you should be fine. If you were on the 93-10 version of the bootloader and attempted to flash to the 93-4 stock rom, and then take an OTA from there, you are very likely going to hard-brick your device.
There are a lot of active threads about flashing back to stock and losing IMEI and enhanced LTE, so I wouldn't risk it. Out of curiosity why would you want to flash back to stock Nougat? IMO the camera is worse and you're rolling back to an older OS.
Click to expand...
Click to collapse
I'm actually still on Nougat. The last time I flashed a new ROM was back in September (the LineageOS build I'm using is from 2017-09-19). So my bootloader is likely whatever the latest one was around that time.
From what I read, it seemed like people were losing their IMEI and VoLTE after flashing 8.1 custom ROMs, which I haven't done, so I figured I was safe. Maybe I'm misunderstanding?
Yousie642 said:
I'm actually still on Nougat. The last time I flashed a new ROM was back in September (the LineageOS build I'm using is from 2017-09-19). So my bootloader is likely whatever the latest one was around that time.
From what I read, it seemed like people were losing their IMEI and VoLTE after flashing 8.1 custom ROMs, which I haven't done, so I figured I was safe. Maybe I'm misunderstanding?
Click to expand...
Click to collapse
Ah I wasn't aware that you were on a nougat version of LOS. I would still back up all partitions just in case.
dunderball said:
Ah I wasn't aware that you were on a nougat version of LOS. I would still back up all partitions just in case.
Click to expand...
Click to collapse
Is that different from doing a NAND backup in TWRP?
Yousie642 said:
Is that different from doing a NAND backup in TWRP?
Click to expand...
Click to collapse
Nope it's the same.
Yousie642 said:
I have a US XT1687 on LineageOS (2017-09-19 build), and I would like to flash the latest stock firmware (which I believe is the April NPNS25.137-93-10 update), while also continuing to receive future OTA updates
The fastboot stock firmware thread was closed.
I found these files https://mirrors.lolinet.com/firmware/moto/potter/official/RETAIL/ but I don't see the 93-10 update.
Can I flash the 93-4 update from that site via fastboot and then get the 93-10 update via OTA?
Thanks!
Click to expand...
Click to collapse
Here's a mirror of the 93-10 firmware, it can be found in this thread.
https://drive.google.com/file/d/16Bfp3nVfvKMURAeKagOaOImX-lvJrYBF/view?usp=drivesdk
The source is the Motorola secure cloud but not everyone was able to download it from there.
If you changed to a custom rom in September 2017 you should have been on August security patch which is the firmware NPNS25.137-33-11.
But you should be good to go with 93-10.
As written above make sure to have a full nandroid, especially of EFS.
Sent from my Moto G5 Plus using XDA Labs
dunderball said:
Nope it's the same.
Click to expand...
Click to collapse
Wolfcity said:
Here's a mirror of the 93-10 firmware, it can be found in this thread.
https://drive.google.com/file/d/16Bfp3nVfvKMURAeKagOaOImX-lvJrYBF/view?usp=drivesdk
The source is the Motorola secure cloud but not everyone was able to download it from there.
If you changed to a custom rom in September 2017 you should have been on August security patch which is the firmware NPNS25.137-33-11.
But you should be good to go with 93-10.
As written above make sure to have a full nandroid, especially of EFS.
Sent from my Moto G5 Plus using XDA Labs
Click to expand...
Click to collapse
Thanks dudes! I actually found my old adb folder and saw I had the files for NPN25.137-83 extracted there, so I'm pretty sure that's what I'm on. Seems like it still won't be an issue though.
What I am worried about now is losing VoLTE if I ever decide to go back to a custom ROM. Though, from what I understand, as long as I have an EFS backup, I can fix it. Is that right?
Yep you should be fine. I didn't have issues when going from stock to custom. Still -- I'd try out an Oreo rom before jumping back to stock.
dunderball said:
Yep you should be fine. I didn't have issues when going from stock to custom. Still -- I'd try out an Oreo rom before jumping back to stock.
Click to expand...
Click to collapse
Y'know, it didn't actually occur to me, and this may be a silly question, but now I'm wondering if there's actually any need to run a stock firmware update before going to newer custom ROMs? The reason I ask is because this was a thing with my Nexus 5x. Newer LineageOS builds sometimes needed a bootloader and radio update.
So I just bought a verizon LG v20 which has 8.0.0 on it. Simple question. Can I still downgrade using upercut and LGUP and then use dirty santa. I found the correct Firmware on lg-drivers and have it all ready and set. Some posts are saying that you can some people say you can't downgrade. I am just trying to figure out which is right. YES I searched multiple posts...
1. Can I downgrade when the phone arrives?
2. Can I still use dirty santa when I downgrade?
3. Why do some say patched and some say not? Is that because some models firmware are non-downgradeable?
---------- Post added at 02:32 AM ---------- Previous post was at 02:30 AM ----------
[/COLOR]
stevieshae said:
So I just bought a verizon LG v20 which has 8.0.0 on it. Simple question. Can I still downgrade using upercut and LGUP and then use dirty santa. I found the correct Firmware on lg-drivers and have it all ready and set. Some posts are saying that you can some people say you can't downgrade. I am just trying to figure out which is right. YES I searched multiple posts...
1. Can I downgrade when the phone arrives?
2. Can I still use dirty santa when I downgrade?
3. Why do some say patched and some say not? Is that because some models firmware are non-downgradeable?
Click to expand...
Click to collapse
Yes you can downgrade, probably only need to use the regular LG up, downgrade to a security patch prior to Dec 2016, follow the dirty santa instructions, flash updated twrp, within twrp standard wipe, format data, flash rom, flash magisk
Sent from my LG-H910 using XDA Labs
cnjax said:
---------- Post added at 02:32 AM ---------- Previous post was at 02:30 AM ----------
[/COLOR]
Yes you can downgrade, probably only need to use the regular LG up, downgrade to a security patch prior to Dec 2016, follow the dirty santa instructions, flash updated twrp, within twrp standard wipe, format data, flash rom, flash magisk
Sent from my LG-H910 using XDA Labs
Click to expand...
Click to collapse
Its that easy?
Yes. But I'll suggest before hand updating to the firmware version of your choice, and dumping it with LGUP (same tool you use to flash firmware packages). There's a lack of flashable stock ROMs for the v20 variants, so you'll be stuck on an ancient firmware version after rooting. Once you've flashed the DirtySanta engineering bootloader, you can flash back part of the dump (minus aboot and recovery), allowing you to keep TWRP/Engineering Bootloader while still having the system version of your choice.
crumbling9999 said:
Yes. But I'll suggest before hand updating to the firmware version of your choice, and dumping it with LGUP (same tool you use to flash firmware packages). There's a lack of flashable stock ROMs for the v20 variants, so you'll be stuck on an ancient firmware version after rooting. Once you've flashed the DirtySanta engineering bootloader, you can flash back part of the dump (minus aboot and recovery), allowing you to keep TWRP/Engineering Bootloader while still having the system version of your choice.
Click to expand...
Click to collapse
Not necessarily true as the majority of the updated stock custom build roms flash full firmware
Sent from my LG-H910 using XDA Labs
cnjax said:
Not necessarily true as the majority of the updated stock custom build roms flash full firmware
Sent from my LG-H910 using XDA Labs
Click to expand...
Click to collapse
Yea, but those updated stock custom build also pack a bunch of other crap you may or may not want. Its much better to start from fresh, do your own debloating, then pick and choose what you want. There's also the side benefit of not having to deal with AFH's godawful download speed. The VS995 has stock KDZ so restoring from stock isn't a big problem, but having your own dump on hand let you get back to the latest (or close to latest) system update and skip 2-3gb of OTAs
crumbling9999 said:
Yea, but those updated stock custom build also pack a bunch of other crap you may or may not want. Its much better to start from fresh, do your own debloating, then pick and choose what you want. There's also the side benefit of not having to deal with AFH's godawful download speed. The VS995 has stock KDZ so restoring from stock isn't a big problem, but having your own dump on hand let you get back to the latest (or close to latest) system update and skip 2-3gb of OTAs
Click to expand...
Click to collapse
I just want a rom like Lineage OS or something that allows custom sets for my device. I am getting confused? just flash this rom with lg up, then use dirty santa, then install the rom correct? I haven't rooted since my nexus 6p since vzw locks the pixel and pixel 2 xl bootloaders -_- ... attached a screenshot of the rom.. its got 3k downloads and is marked 2016-12-24 3691(downloads) SO I assume I flash this first. then do the dirtsanta exploit? My last question is how do I install roms with these newer devices? Do I format everything(I got an sd card) and just keep the sd card clean? Would love some info!
Heres the link to the screenshot I tried adding. https://lg-firmwares.com/lg-vs995-firmwares/#tab=firmwares
Need some help, can't get root or super su to work. keeps saying device not rooted. after flashing stock twice. and redoing dirty santa. Here is the forum post to reduce spam.
https://forum.xda-developers.com/v20/help/v20-dirty-santa-help-t3897601
stevieshae said:
Need some help, can't get root or super su to work. keeps saying device not rooted. after flashing stock twice. and redoing dirty santa. Here is the forum post to reduce spam.
https://forum.xda-developers.com/v20/help/v20-dirty-santa-help-t3897601
Click to expand...
Click to collapse
You have to install Magisk/SuperSu to keep TWRP, otherwise the system will replace it with stock recovery everytime it boots. If you already have the Engineering Bootloader installed by following DirtySanta up to Step 3, just reboot into fastboot (hold volume down while phone is off, plug cable) and reflash TWRP with fastboot.