Hello,
Can I downgrade completly with the bootloader on Marshmallow and then upgrade to Nougat?
I want to lock my bootloader.
My G2 bricked after doing this. But I don't know if this would happen to my G4 Plus again
inFiniTyz_Z said:
Hello,
Can I downgrade completly with the bootloader on Marshmallow and then upgrade to Nougat?
I want to lock my bootloader.
My G2 bricked after doing this. But I don't know if this would happen to my G4 Plus again
Click to expand...
Click to collapse
If you wish to simply re-lock your bootloader, the easiest thing is to flash this fastboot stock ROM (which is Nougat) and use the locking script as directed in the first post. https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369 Of course, this may wipe your data - so back up, and the relocking may or may not work, in which case you may have to wait for a more up to date fastboot stock ROM to become available.
If you were to downgrade to Marshmallow, you cannot downgrade your bootloader and GPT partitions, at best, your existing bootloader would try to prevent you from downgrading those partitions. At worst, you'll brick your device again if you were to flash those - though we've got possible ways of fixing that, it's not a route I'd want to go down. Flashing the rest of Marshmallow is no problem, however, ensure you have the correct MM firmware for your device and territory.
Will this version work for my country(Germany) without OTA trouble?
inFiniTyz_Z said:
Will this version work for my country(Germany) without OTA trouble?
Click to expand...
Click to collapse
Should be okay to flash - the 93-14 build appears to be the global build that was deployed by Motorola, and should be eligible for the 93-14.4 (March 2017 security update) whenever that arrives in the EU/UK I've flashed the stock ROM onto my XT1642 several times without issue.
echo92 said:
Should be okay to flash - the 93-14 build appears to be the global build that was deployed by Motorola, and should be eligible for the 93-14.4 (March 2017 security update) whenever that arrives in the EU/UK I've flashed the stock ROM onto my XT1642 several times without issue.
Click to expand...
Click to collapse
THANK YOU IT WORKED AND THE WARNING DISAPPEARED. I am on Nougat, locked and its working like a charm
I WOULD KISS YOUR BUTT IF ITS HAVE TO BE
I was wondering how many and what updates everyone else have received and when?
I'm currently on the April 2017 security update and I received that in early June I believe.
I'm hoping Huawei can at least be excused by the fact they're working on an Oreo update instead of doing security updates and bug fixes (highly doubtful though). Mine is a Nordic unlocked model by the way.
So are anyone else receiving security updates?
Not here, in Spain. The thing is, I don't see any security patch coming till next EMUI version arrives, hopefully before the end of the year.
Not sure if this helps, but I found some way opening another security gap
As far as I figured out, you need 3 files for the update to work:
update.zip
update_full.zip (or update_full_WAS-XXX_hw_eu.zip)
update_data_full_public.zip
I am sure, FirmwareFinder or any other tool might come in handy doing so. The next thing you'd need would be TWRP which is available as some beta build somewhere on this forum. Then you'd have to unlock the bootloader and root your device to get TWRP on it. I'd recommend doing some research on this as you might have to get some code for "fastboot oem unlock"...
Flash the files listed above the way they're listed.
Few mins ago Moto pushed February security patch for RETBR.
Download it here:
https://motoota.lolinet.com/index.p....26.241.15.addison.retail.en.US&carrier=retbr
You need to be on build NPNS26.118-22-2-12 to flash this update!
Interesting. And it's not part of soak test? I would have expected them to release 8.0 finally, they are long overdue
Artim_96 said:
Interesting. And it's not part of soak test? I would have expected them to release 8.0 finally, they are long overdue
Click to expand...
Click to collapse
Just the security patch. Although islt coincided with the Oreo update in China. Let's hope that's in preparation for retbr Oreo.
Artim_96 said:
Interesting. And it's not part of soak test? I would have expected them to release 8.0 finally, they are long overdue
Click to expand...
Click to collapse
I presume they will push Oreo in few hours.
rafikowy said:
I presume they will push Oreo in few hours.
Click to expand...
Click to collapse
That will be great. Even though I'll wait for a .xml.zip, on the one hand I accidentally did a downgrade (and I have no idea of the bootloader of September and December patch are different enough to cause bricking with OTAs) and I think my phone is due for a factory reset. It reboots very randomly and even though battery life is great I'm told it should be even better. Let's see if that does the fix
I'm on RETEU, but when I try to use Motorola Device Manager it says that the host is not available because of maintenance... let's hope that they are pushing OREO
8cpaiw said:
I'm on RETEU, but when I try to use Motorola Device Manager it says that the host is not available because of maintenance... let's hope that they are pushing OREO
Click to expand...
Click to collapse
Forget stupid device manager, it's not detecting anything, it's just as bad as RSD lite
Artim_96 said:
Forget stupid device manager, it's not detecting anything, it's just as bad as RSD lite
Click to expand...
Click to collapse
Hahahah true, but I'm still hoping for the best outcome
Already available for RETIN and RETUS. I'm guessing this is the last nougat patch, hopefully Oreo is next
If it is the Nougat Feb 2018 security patch, then those that were on the Oreo soak test then downgraded back to Nougat may want to be careful. If you've updated to Oreo previously, then you may still have an Oreo bootloader even if you downgraded to Nougat again. As this appears to be a Nougat OTA update (with a Nougat bootloader), I don't know if flashing this Feb 2018 OTA onto a device previously flashed with stock Oreo soak test firmware may result in a hard brick (as the OTA may overwrite your bootloader), and if it does end in a hard brick, I don't know if the current blankflashes will work on a corrupted Oreo bootloader. I'm hoping I'm wrong on this, but regardless, just be careful.
echo92 said:
If it is the Nougat Feb 2018 security patch, then those that were on the Oreo soak test then downgraded back to Nougat may want to be careful. If you've updated to Oreo previously, then you may still have an Oreo bootloader even if you downgraded to Nougat again. As this appears to be a Nougat OTA update (with a Nougat bootloader), I don't know if flashing this Feb 2018 OTA onto a device previously flashed with stock Oreo soak test firmware may result in a hard brick (as the OTA may overwrite your bootloader), and if it does end in a hard brick, I don't know if the current blankflashes will work on a corrupted Oreo bootloader. I'm hoping I'm wrong on this, but regardless, just be careful.
Click to expand...
Click to collapse
You are 100% right :good:
echo92 said:
If it is the Nougat Feb 2018 security patch, then those that were on the Oreo soak test then downgraded back to Nougat may want to be careful. If you've updated to Oreo previously, then you may still have an Oreo bootloader even if you downgraded to Nougat again. As this appears to be a Nougat OTA update (with a Nougat bootloader), I don't know if flashing this Feb 2018 OTA onto a device previously flashed with stock Oreo soak test firmware may result in a hard brick (as the OTA may overwrite your bootloader), and if it does end in a hard brick, I don't know if the current blankflashes will work on a corrupted Oreo bootloader. I'm hoping I'm wrong on this, but regardless, just be careful.
Click to expand...
Click to collapse
If I'm reading the info in fastboot correctly, the Feb update does include an updated bootloader:
C1.14 (sha-a62b7ae, 2018-02-21 16:09:43)
echo92 said:
If it is the Nougat Feb 2018 security patch, then those that were on the Oreo soak test then downgraded back to Nougat may want to be careful. If you've updated to Oreo previously, then you may still have an Oreo bootloader even if you downgraded to Nougat again. As this appears to be a Nougat OTA update (with a Nougat bootloader), I don't know if flashing this Feb 2018 OTA onto a device previously flashed with stock Oreo soak test firmware may result in a hard brick (as the OTA may overwrite your bootloader), and if it does end in a hard brick, I don't know if the current blankflashes will work on a corrupted Oreo bootloader. I'm hoping I'm wrong on this, but regardless, just be careful.
Click to expand...
Click to collapse
It happened to me ... Lack of attention completely. How should I proceed? Wait for a new flash file?
SherlockDk said:
It happened to me ... Lack of attention completely. How should I proceed? Wait for a new flash file?
Click to expand...
Click to collapse
If the blankflashes in the other thread don't work, then you may either:
1)Have to wait for a newer blankflash to get leaked. These are Motorola internal development tools and as such aren't generally available - as they're also signed by Motorola, we may not be able to make them ourselves. The ones we have either came with the factory stock ROM or a leak from a generous Motorola engineer. You may be lucky and a blankflash may be included if an Oreo factory stock ROM comes out (not the usual fastboot ROM, a full factory image).
2)Have to pay to have your motherboard replaced, which seems to be 60-70% of the cost of a new device as far as I understand, so you may wish to put that money towards a new device instead.
I'm sorry I don't have better news, hard bricks are very difficult to resolve without the proper tools. You may wish to research making a loader image (a partition level copy of a working device, loaded onto an SD card), but it's not a definite rescue method.
Full fastboot stock software including February security patch:
https://rsdsecure-cloud.motorola.co...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
rafikowy said:
Full fastboot stock software including February security patch:
https://rsdsecure-cloud.motorola.co...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Click to expand...
Click to collapse
I'm on RETEU. If I flash this Rom over fastboot - will I stay on RETEU or get RETBR?
fernseher said:
I'm on RETEU. If I flash this Rom over fastboot - will I stay on RETEU or get RETBR?
Click to expand...
Click to collapse
You will stay on RETEU. The link I provided is RETAIL version.
Hey can i use these files for my guide? This save me some time
rafikowy said:
Full fastboot stock software including February security patch:
https://rsdsecure-cloud.motorola.co...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Click to expand...
Click to collapse
Bad url
rafikowy said:
Full fastboot stock software including February security patch:
https://rsdsecure-cloud.motorola.co...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Click to expand...
Click to collapse
If you still have that file, please upload it to androidfilehost or somewhere.
Hi everyone
I recently got a Verizon Pixel and i want to roll back to Android 8.1 Oreo, i am currently on Android P DP2 with a locked bootloader, i've enabled OEM Unlocking (done under Android P DP2) but didn't want to unlock the bootloader! how can i roll back safely! do i need to unlock the bootloader! if my bootloader is unlocked can i lock it back! what are the possible issues/benefits if a bootloader kept unlocked!
Thank you.
Just unenroll from android beta program by visiting android beta website and you will get an ota which will revert you back to android 8.1.0
I've heard that some people who did, got a softbrick after the OTA update! I want to roll back manually.
hbforce said:
I've heard that some people who did, got a softbrick after the OTA update! I want to roll back manually.
Click to expand...
Click to collapse
You have two options then first One sideload the latest ota file of 8.1.0 which is of june. And then wipe your internal storage . For doing this you won't have to unlock your bootloader . And the second One is unlock your bootloader and flash the latest factory image of android 8.1.0.. Backup your data because both will cause you to lose your data.
Ziauddin_Sameer said:
You have two options then first One sideload the latest ota file of 8.1.0 which is of june. And then wipe your internal storage . For doing this you won't have to unlock your bootloader . And the second One is unlock your bootloader and flash the latest factory image of android 8.1.0.. Backup your data because both will cause you to lose your data.
Click to expand...
Click to collapse
Thanks for the clarification, I have one more question, do you advise to let my bootloader unlocked or should I lock it back, knowing that I have a Verizon Pixel!
hbforce said:
Thanks for the clarification, I have one more question, do you advise to let my bootloader unlocked or should I lock it back, knowing that I have a Verizon Pixel!
Click to expand...
Click to collapse
If u are into custom roms or rooting types things and customizing your phone then you should leave it unlocked .. as yours is verizon one you may not be able to unlock it in the future. Otherwise lock it .. ??
hbforce said:
Thanks for the clarification, I have one more question, do you advise to let my bootloader unlocked or should I lock it back, knowing that I have a Verizon Pixel!
Click to expand...
Click to collapse
Pixel's are finicky as far as relocking the bootloader due to AVB and dm-verity. I highly recommend against relocking these phones unless they are COMPLETELY STOCK. Also if it is a Verizon device you will not be able to unlock it again without using an exploit which is a bit hard to find and a bit scammy
I am thinking about getting this phone as it’s on sale now. Is the phone be able to be unlocked and rootable out of the box? What if it’s updated to latest version? Will it still be able to be unlocked and rootable?
Theoretically, yes, you can root, till you are on Oreo with June Security Patch. And you have to pay for that. Nokia had disabled the bootloader unlock vulnerability with the August patch.
My device came with August patch, unlucky me xD.
However, I know one guy who managed to convince Nokia service centre to downgrade his device to Oreo June Patch, back from Pie. He's also rooted and flashed GSI on his 6.1 Plus.