Related
OTA - You may BRICK your phone if you have a modified recovery(TWRP,etc) and you try to take an OTA.
OTA will fail if magisk is present.
see
https://forum.xda-developers.com/mo...p-flashing-t3813498/post77011495#post77011495
bump
hello
bumpsi
It is well known since ages, at least since Android 4 where this block oriented OTA was first implemented, that OTA will fail if recovery, boot or system partition is modified. Any root solution modifies at least boot or system and will prevent OTA to run through. Modified recovery should also stop the OTA (do not flash TWRP since long time, so I am not that sure about this on newer Android, at least until Android 6 Lollipop it did).
So: No one could ever successfully take OTA without uninstalling root and twrp if installed. This is valid and well known for nearly all Android devices, not only Motorola. It is known.
Brick on Moto devices is dangerous. It happens if you downgrade your system, but bootloader never is able to get downgraded. So the OTA tries to update the bootloader assuming it is old, but it already is current. This may result in a hard brick where flashing is not possible anymore. You are on the safe side if you do not restore a backup of a system with a previous bootloader, and do not flash older firmware.
So: No one is supposed to brick the Motorola smartphone via OTA if no firmware downgrade ever is done.
Just doing OTA with root will NOT do a greater harm than a failed OTA. There will be some installation log mentioning "there is partition xyz modified, I will not install the OTA". The system will run as before without update. If it doesn't because of some error in the update mechanism, it will suffice to flash the currently installed or some newer firmware to recover the device, there should occur no brick. Root is not the reason for brick in combination with OTA. Older firmware is.
So: What is your reason to bump this wrong worded warning?
KrisM22 said:
bumpsi
Click to expand...
Click to collapse
Kris, please stop spamming the forum. You bumped two threads, repeatedly
many thanks for bumping this important post!
interesting sig.
Hi, recently I bought my Moto Z2 Play (XT1710-09).
I really wanted to root my phone, but because of some weird bug, it soft-bricked it. Fortunately I had Absolute backup of whole internal storage so I have Original files.
Also I have not flashed TWRP, I have only fastbooted TWRP (Which is propably why I soft-bricked my phone)
So my question is very easy. Is it possible to lock bootloader if I have recovered back whole system and all it's files by stock files with which it (Moto Z2 Play XT1710-09) arrived?
Also the phone is fully functioning at the moment, with original files mantionet above, but it can't make working OTA updating process. And it's pain in ass, because the update manager is still apearing with new update...
So I have decided to lock bootloader even if it means to wipe all personal data and factory reset. Just for sake of getting rid of that stupid OTA updatete fullscreen pop up, that I have a new update waiting to be downloaded and installed.
You may ask as well "Why do you want to lock bootloadert insted of buying Titanium backup pro and freezing that update manager". The reason is simple. I'm afraid of rooting my phone again, because last time, it soft-bricked it and next time, it may full-brick it.
I've relocked my bootloader twice, once on Nougat and once after upgrading to Oreo:
https://forum.xda-developers.com/z2-play/how-to/close-bootloader-lineageos-losing-imei-t3769479
Surely there is a fastboot command somewhere (which I think I saw in another thread) without having to flash some firmware?
https://forum.xda-developers.com/showpost.php?p=77270030&postcount=9
So that does mean. As long as I have 100% of stock files with which it come to me, it will lock?
julesism said:
I've relocked my bootloader twice, once on Nougat and once after upgrading to Oreo:
https://forum.xda-developers.com/z2-play/how-to/close-bootloader-lineageos-losing-imei-t3769479
Click to expand...
Click to collapse
Every firmware I try fails to lock my bootloader, validation fails because non of them are above the security level of my device before I unlocked. Is there any newer firmwares ?
Hello.
First, sorry for my bad english, I hope you will understand what I say.
I bought a MotoG5 in France just after Chrismas, the retailer is Fnac.
He stays stuck with NPPS25.137-93-14 with Android 7.0 and with 1 july security patch.
He is really slow for booting, and YouTube playback is not smooth.
I'm pretty sure it comes from the fact that the ROM is not optimised, so I was searching for Oreo update but looks like it doesn't work with my firmware.
Can someone tell me if is it possible to change my ROM for having a smooth experience on this phone ?
Thanks, and have a nice day.
If I were you just wait until the oreo official ota rolls out (it's already started in some regions & obviously no one will know what you will get it)
Obviously you could flash specifically firmware & use the soak test ota but why bother - do it wrong you hard brick your device
Do it right you still may have issues updating it in the future
Just be patient if you want oero
If you want a custom rom use lineageos 14.1
elio612 said:
Hello.
First, sorry for my bad english, I hope you will understand what I say.
I bought a MotoG5 in France just after Chrismas, the retailer is Fnac.
He stays stuck with NPPS25.137-93-14 with Android 7.0 and with 1 july security patch.
He is really slow for booting, and YouTube playback is not smooth.
I'm pretty sure it comes from the fact that the ROM is not optimised, so I was searching for Oreo update but looks like it doesn't work with my firmware.
Can someone tell me if is it possible to change my ROM for having a smooth experience on this phone ?
Thanks, and have a nice day.
Click to expand...
Click to collapse
As long as you just flash boot, system (sparse chunk 0 thru 4), oem, non-hlos.bin, oem, fsg and dsp you should be all fine up/downgrading to any firmware version (when upgrading you may need to also flash bootloader).
People say all around here in XDA that's its "impossible to downgrade" Moto phones, this is all a myth.
I just downgrade my Cedric from stock Oreo to stock nougat. Only thing you need to know is:
1.NEVER downgrade bootloader... EVER... This will immediately hardbrick any motorola phone.
2.When you fastboot, there's no need to flash gpt.bin (at least on Cedric, I never do that, as I don't know what might happen).
3.erase Cedric's modemst1 and modemst2 and never see your imei again (I also don't understand why people say it's necessary to do this. When fastbooting a Motorola phone I always erase only cache and user data and never had problem)
4. You can downgrade to any firmware (since the newest bootloader will support the old firmwares) as long as you just flash system, fsg, dsp and oem and boot (it's not necessary to flash recovery, it will turn back to stock on the first boot.
5. To relock your bootloader.. You just need to flash the same files cited above.
freeZbies said:
People say all around here in XDA that's its "impossible to downgrade" Moto phones, this is all a myth.
Click to expand...
Click to collapse
It is impossible to fully downgrade. You can only partially downgrade, which doesn't allow to relock the bootloader on an older version. If you flash the latest soak test OTA you have to wait a fastboot version of the upcoming official, non-soak update comes out to be able to relock the bootloader because at that point you can't even go back to the latest fastboot flashable version of Nougat (though if you try to flash it, you won't hard brick the phone).
My recommendation would be to wait until the stable version of Oreo comes out and is flashable through fastboot.
freeZbies said:
When you fastboot, there's no need to flash gpt.bin (at least on Cedric, I never do that, as I don't know what might happen).
Click to expand...
Click to collapse
Flashing gpt.bin (re)creates partition scheme. If flash fails, partition scheme will mess up, which will end up in hardbrick.
fstabman said:
It is impossible to fully downgrade. You can only partially downgrade
Click to expand...
Click to collapse
True. I'm currently on stock Nougat but my bootloader is on B8.31, which is Oreo's BL version. As I can't Downgrade BL, once I downgraded the system
I didn't receive any OTA notifications anymore (due to mismatching BL version)
fstabman said:
If you flash the latest soak test OTA you have to wait a fastboot version of the upcoming official.
Click to expand...
Click to collapse
Also true. That's why after I downgraded from the official Oreo to Nougat I don't get any update notifications anymore(Oreo has already been out for a few weeks around here).
fstabman said:
which doesn't allow to relock the bootloader on an older version.
Click to expand...
Click to collapse
Not true AT ALL. I've relocked my bootloader after downgrading my phone and it's okay. Once you type "fastboot oem lock" twice on fastboot you just need to flash what fastboot demands you to, which is system, boot and oem. Recovery, dsp, modem and bootloader are not demanded, so you can theoretically relock any Motorola phone in any firmware version, using any firmware you want. I can't attest that for every device with the Motorola flag but I've already downgraded and relocked moto G2 and moto E5 - besides Cedric - using fastboot and never had any problems so far.
I think people come up with these stories in fear they might brick their devices but never try for themselves, so they come here and spread myths about the impossibility of relocking your device without ever paying attention to fastboot's own instrucrions on how to flash the device.
I really think that if the fastboot relock method didn't really accept downgrades it would make no sense for it to exist, since you'll presumably not always have a newer firmware version available to relock your device, because under the premise of unlocking your BL its assumed that you will move to an unnoficial OS and under the premise of relocking its assumed you'll have to downgrade/go back to stock. It's all logic. If fastboot didn't allow downgrades as a means of relocking bootloader, the relocking feature would not have a lot of sense unless it could be secured that every device would always have an updated firmware version available, one after the other, which is not only a false statement but also makes no sense.
In other words, this stories about not being able to downgrade/having to flash newer firmware to relock BL are all plain bull****. Relocking your bootloader never had anything to do with your firmware version afaik (I never had trouble doing it my self at least. Can't say for Others)
freeZbies said:
True. I'm currently on stock Nougat but my bootloader is on B8.31, which is Oreo's BL version. As I can't Downgrade BL, once I downgraded I didn't receive any OTA notifications anymore
Also true. That's why after I downgraded from the official Oreo to Nougat I don't get any update notifications anymore(Oreo has already been out for a few weeks around here).
Not true AT ALL. I've relocked my bootloader after downgrading my phone and it's okay. Once you type "fastboot oem lock" twice on fastboot you just need to flash what fastboot demands you to, which is system, boon and oem. Recovery, dsp, modem and bootloader are not demanded, so you can theoretically relock any Motorola phone in any firmware version, using any firmware you want. I can't attest that for every device with the Motorola flag but I've already downgraded and relocked moto G2 and moto E5 - besides Cedric - using fastboot and never had any problems so far.
I think people come up with these stories in fear they might brick their devices but never try for themselves, so they do here and spread myths about the impossibility of relocking your device but it makes no sense. I really think that if the fastboot relock method didn't really accept downgrades it would make no sense for it to exist, since you'll presumably not always have a newer firmware version available to relock your device if it was really as they say.
In other words, this is all plain bull****. Relocking your bootloader never had anything to do with your firmware version afaik (I never had trouble doing it my self at least. Can't say for Others)
Click to expand...
Click to collapse
So should I be "on safe side", if I lock bootloader with NPPS25.137-93-8 image but NPPS25.137-93-14 installed right now?
fstabman said:
It is impossible to fully downgrade. You can only partially downgrade, which doesn't allow to relock the bootloader on an older version. If you flash the latest soak test OTA you have to wait a fastboot version of the upcoming official, non-soak update comes out to be able to relock the bootloader because at that point you can't even go back to the latest fastboot flashable version of Nougat (though if you try to flash it, you won't hard brick the phone).
My recommendation would be to wait until the stable version of Oreo comes out and is flashable through fastboot.
Click to expand...
Click to collapse
Andrej_SK said:
So should I be "on safe side", if I lock bootloader with NPPS25.137-93-8 image but NPPS25.137-93-14 installed right now?
Click to expand...
Click to collapse
Yes. Take care of backing up your efs partition using twrp 64 bits first.
After that, download an official (signed) fastboot firmware and flash only system sparcechunks, oem and boot - in other words, do what fastboot tells you.
Dont "fastboot erase" anything but cache and user data and u should be fine. This command has been known for ages as being the cause of lost Imei (on moto g2 I think it broke if u erased the fsg partition, on Cedric its modem that breaks your Imei if erased).
If you for some reason have problems with signal/Sim cards not working, then u may flash the other partitions(fsg, dsp, and Non-hlos[modem])
I say these Because there may be incompatibilities related to The modem. For example, when downgrading from Oreo to NPPS25.137-93-2-5 using fastboot, everything went fine, but if I upgrade from npps25-137-93-2-5 to Oreo and don't flash modem And fsg, signal will not work. Also, if I downgrade from Oreo to Nougat using twrp and I don't flash fsg, fingerprint scanner wont work.
But in essence, as long as you don't "fastboot erase" anything unnecessary and don't touch bootloader (and seemingly gpt.bin, as someone mentioned above) , you should be safe.
freeZbies said:
Once you type "fastboot oem lock" twice on fastboot you just need to flash what fastboot demands you to, which is system, boot and oem.
Click to expand...
Click to collapse
The problem is, it fails at validating oem when trying to relock. At least on my end, after updating NPPS25.137-93-2-5 > First Oreo OTA > Second OTA > Back to NPPS25.137-93-2-5.
fstabman said:
It is impossible to fully downgrade. You can only partially downgrade, which doesn't allow to relock the bootloader on an older version. If you flash the latest soak test OTA you have to wait a fastboot version of the upcoming official, non-soak update comes out to be able to relock the bootloader because at that point you can't even go back to the latest fastboot flashable version of Nougat (though if you try to flash it, you won't hard brick the phone).
My recommendation would be to wait until the stable version of Oreo comes out and is flashable through fastboot.
Click to expand...
Click to collapse
fstabman said:
The problem is, it fails at validating oem when trying to relock. At least on my end, after updating NPPS25.137-93-2-5 > First Oreo OTA > Second OTA > Back to NPPS25.137-93-2-5.
Click to expand...
Click to collapse
Interesting.. Are you sure all files are signed? What error fastboot gives you?
I'll try making a video later today showing that it is possible to do it, so that u can see it.
freeZbies said:
Interesting.. Are you sure all files are signed? What error fastboot gives you?
I'll try making a video later today showing that it is possible to do it, so that u can see it.
Click to expand...
Click to collapse
Code:
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:oem: not found
target reported max download size of 536870912 bytes
sending 'oem' (188494 KB)...
OKAY [ 6.023s]
writing 'oem'...
(bootloader) Security version downgrade
(bootloader) Image o failed validation
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 6.093s
I tried with 93-2-3 as well and get the same invalid signed image issue.
A question though, if the bootloader were to lock successfully after doing this (and since it still has some files from Oreo to prevent hard bricking), would it actually receive any OTAs?
fstabman said:
Code:
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:oem: not found
target reported max download size of 536870912 bytes
sending 'oem' (188494 KB)...
OKAY [ 6.023s]
writing 'oem'...
(bootloader) Security version downgrade
(bootloader) Image o failed validation
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 6.093s
I tried with 93-2-3 as well and get the same invalid signed image issue.
A question though, if the bootloader were to lock successfully after doing this (and since it still has some files from Oreo to prevent hard bricking), would it actually receive any OTAs?
Click to expand...
Click to collapse
Really, the error you've been getting has to be related to you being unable to downgrade, since it attests the image is signed (error for unsigned I made says "unsigned or corrupt image).
Yep, seems like I was wrong, I might just have been lucky never to get an error like that before
Anyways, have you tried npps25-137-93-2-5 yet? It's the latest security patch (July) released in Brazil. I'm now somewhat confused lol.
Anyways, relocking your BL doesn't allow you to get otas, since some of the partitions will remain in the newest version, and that's long been known to render your phone unable to receive otas (I guess all partition's hashs are checked against stock ones before ota) and it will also not get your warranty back, so it's kind of useless unless you just want to test to see if u can downgrade OR if u want to go back to stock and never modify the device again.
EDIT: I was wrong, if you're on untouched stick you'll get OTA's, regardless of being unlocked or not.[/B] I thought I wouldn't receive OTA's anymore because it took me more than 2 weeks for me to get an OTA notification after it had already rolled out in Brazil, whereas for other updates I had gotten it really early By the way, I had other people confirm me that I wouldn't get it if I had modified my phone, but that's not true because when I got the OTA notification I had a rooted phone with lots of mosifixatiins. So I'm here to rectify this post and say that I was wrong: if you're on stock and there's an update rolling out, you should be getting it sooner or later regardless of your phone being rooted or not, but trying to apply the OTA in a modified phone will brick your device.
Anyways, I find it very strange that you're getting this error only when flashing the oem partition. You shouldn't be able to flash any of them.
If u want, I can send u the signed oem image I used to relock mine. I'm sure it won't cause any conflicts or glitches since this partition only contains some carrier bloat ware alongside some Motorola apks. I'm not sure if it will be Flash able alongside npp93-2-3 files during the same oem lock operation, due to mismatching firmware versions, but I think it'd be worth trying.
freeZbies said:
Anyways, have you tried npps25-137-93-2-5 yet? It's the latest security patch (July) released in Brazil. I'm now somewhat confused lol.
Click to expand...
Click to collapse
Yep, tried that one. I tried many different, older versions as well (got a hard brick or two as well, but I could restore it without issues). I can flash oem as long as it's not after I used the fastboot oem lock command twice. I do that and I am no longer able to do it.
Anyways I think I'll wait til Oreo stable comes out, all I was interested in was having the ability to take OTA updates again. Hopefully it will come out soon.
Well. If you wanted Official Oreo you wouldn't get it anyways.
But now that you said I'm curious to say how I managed to downgrade & relock without EVER getting that message.
To tell you the truth, I've seen many fastboot errors already, but this one is pretty new to me.
freeZbies said:
Well. If you wanted Official Oreo you wouldn't get it anyways.
But now that you said I'm curious to say how I managed to downgrade & relock without EVER getting that message.
To tell you the truth, I've seen many fastboot errors already, but this one is pretty new to me.
Click to expand...
Click to collapse
Did you downgrade from the first Oreo soak test or the second, more recent one?
fstabman said:
Yep, tried that one. I tried many different, older versions as well (got a hard brick or two as well, but I could restore it without issues). I can flash oem as long as it's not after I used the fastboot oem lock command twice. I do that and I am no longer able to do it.
Anyways I think I'll wait til Oreo stable comes out, all I was interested in was having the ability to take OTA updates again. Hopefully it will come out soon.
Click to expand...
Click to collapse
By the way could you tell me what exactly got your phone hard bricked?
freeZbies said:
By the way could you tell me what exactly got your phone hard bricked?
Click to expand...
Click to collapse
Doing a downgrade while flashing gpt.bin and bootloader with version B8.24.
Hello, I'm quite new. I downgraded from Pie to Oreo with Miflash a couple of years ago cause I had wifi problems. I got V9.6.11.0.ODLMIFF now. I want lock bootloader and keep updating via OTA. Which version should I install? stock version? Or some Pie version? I will lose all data of the phone right ? And where I can get the ROM? The old links I had not working now. Thanks
If you want security updates you have to use Android 10 but it's got some "known issues" you may not like. 11.0.16.0
https://bigota.d.miui.com/V11.0.16.0.QDLMIXM/daisy_global_images_V11.0.16.0.QDLMIXM_20201225.0000.00_10.0_79e5becb5f.tgz
If you just want to go back to Pie, you may as well get the last version. 10.0.20.0
There's a list of stock images here:
[FASTBOOT] [daisy] Xiaomi Mi A2 Lite FASTBOOT Images
Disclaimer I am not responsible for bricked devices or anything like that. YOU are choosing to make these modifications, and if you point your finger at me for messing up your device, I will laugh at you. Here are the current fastboot links for...
forum.xda-developers.com
That page also has install instructions if you aren't familiar.
Thanks @a1291762 Yes I prefer something stable so I'll install 10.0.20.0. I enter into fastboot mode and flash with miflash(clean all) right?
And I'm wondering if It is possible to lock the bootloader to update via OTA in the future? (clean and lock) It is possible with that version or you need to install the first Android 8.1.0 [V9.6.4.0.ODLMIFF] ?
Nidea180 said:
prefer something stable so I'll install 10.0.20.0. I enter into fastboot mode and flash with miflash(clean all) right?
And I'm wondering if It is possible to lock the bootloader to update via OTA in the future? (clean and lock) It is possible with that version or you need to install the first Android 8.1.0 [V9.6.4.0.ODLMIFF] ?
Click to expand...
Click to collapse
I haven't used miflash only the fastboot scripts. But I believe miflash has a lock bootloader option. As long as you are also flashing all of the partitions, it's safe to use. Note that you do not need a locked bootloader to OTA.
You can use that version (10.0.20.0). There is no need to use an older one.
If you are downgrading you need to flash a newer modem because it fails if you downgrade the modem firmware. That makes it trickier to flash and lock. Replacing the file works with the fastboot scripts.
After install, you will need to immediately enable developer mode to disable automatic system updates. Otherwise your phone will install Android 10 automatically.
Thanks it has been helpful. So can I update via OTA after install a fastboot ROM, no matter if bootloader is lock or unlock? Is that possible when you downgrade?
Nidea180 said:
Thanks it has been helpful. So can I update via OTA after install a fastboot ROM, no matter if bootloader is lock or unlock? Is that possible when you downgrade?
Click to expand...
Click to collapse
Yes. OTA only requires the A/B partitions to be unmodified. You can have an unlocked bootloader.
If you root with Magisk or install TWRP then your partitions will be modified. If you don't do that, you can OTA without issue.
Nidea180 said:
Thanks @a1291762I'll install 10.0.20.0
Click to expand...
Click to collapse
FWIW: I am lending my phone to somebody else, and didn't want them to have to put up with Android 10's quirks (particularly the need to reboot regularly) so I put the phone into fastboot mode and used flash_all_lock_crc.sh from the Android 9 (10.0.20.0) fastboot image. https://bigota.d.miui.com/V10.0.20....0.PDLMIXM_20200327.0000.00_9.0_2baf524aaf.tgz
Since I didn't have an Android 11 ROM handy, I left the 10.0.20.0 modem image in there, but it seems to be fine (for my single SIM in slot 2). I guess the modem thing (needing to flash a newer image) only applies to Android 8?
Before I let the phone on the network, I enabled developer mode and turned off automatic updates. Disabling the notification category Google Play Services -> System Update should prevent any prompts to install system updates.
Having issues installing beta 3.3 on my 6 pro.. did a factory reset then tried installing it. First time it took forever to install and phone rebooted and had missing operating system so I had to factory reset.. second time I got a failed to install message.. rebooted the phone and it said no operating system please visit this link from another device.. rebooted then phone worked normal.. what is going on here ? Phone is purchased from att, so idk if it's considered global version but whatever either way . Is there something stopping it from being installed? Was trying to do all this OTA.. thanks kinda new to it
I'm not sure if it being an att version has anything to do with it or not.. maybe the version google releases is only working on unlocked global models?? Someone shine some light on this..
You can use https://flash.android.com/ to flash with a computer.
So why would the flash tool work but not the ota method ?? Really curious cause when the official comes out hopefully I can flash that ota without any issues.. right now I opted out of the beta cause I really want the ota method to work and it doesn't ..
Can someone tell me why the ota wouldn't install ? Installed it the way I installed any other update on the phone through check for updates.. Id rather get ota working vs hassling with a computer to install it. That can mess things up if done wrong .
Is it failing to ota install the beta cause of a locked bootloader ? It does fine with install ota security patches on Android 12. Trying to install 13 ota on the phone itself fails.. I don't see why that would be though ?
@Redbeardkevv Welcome to XDA. Instead of posting multiple times in a row, please use the Edit button to edit your post and just add to it, in the future.
Official Google Android Flash Tool (OEM Unlocking needs to be toggled on - you may not have to manually unlock the bootloader - the "site" will do that on its own)
^ That Google site has saved many users on XDA. It has revived or corrected a mistake on their devices (mine too, once) when even flashing the full factory image didn't fix the problem. I have no idea what exactly it does that manually flashing doesn't. I normally use the full factory image zip, and that alone sometimes fixes issues that users have when they have issues flashing via the OTA method.
Oem unlocking toggled on isn't an option on this phone , purchased at att . I'll just wait till they release the official ota. But what would of been holding it up and making the installs corrupt??
Redbeardkevv said:
Oem unlocking toggled on isn't an option on this phone , purchased at att . I'll just wait till they release the official ota. But what would of been holding it up and making the installs corrupt??
Click to expand...
Click to collapse
Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developer.android.com
Important excerpt:
Android Flash Tool guides you step-by-step through the process of flashing your device—there's no need to have tools installed—but you will need to unlock your device and enable USB Debugging in Developer options.
Click to expand...
Click to collapse
If I remember correctly from other AT&T variant Pixel 6 Pro users in this section, once you pay off the phone and/or own the phone for long enough, AT&T should carrier unlock the phone, and that will likely make it so that you can OEM Unlocking and unlock the bootloader. (this also applies to T-Mobile, but does not apply to Verizon)
Well it's a far ways from being paid off I'll just add that .. what are my flashing options ? Also why would a security patch install just fine, then I enroll into beta ,try to install it, and bam it won't install and is corrupt install. Just doesn't seem right to me.. should I just wait until official release early August and then the OTA install from phone will work ?
Why would a security patch install without any issue , but I go to install this beta 13 and it fails and is corrupt . Same method as installing a security patch , only difference is beta won't install . Will it install correctly OTA when they release the final version in August ???
Redbeardkevv said:
Why would a security patch install without any issue , but I go to install this beta 13 and it fails and is corrupt . Same method as installing a security patch , only difference is beta won't install . Will it install correctly OTA when they release the final version in August ???
Click to expand...
Click to collapse
Firstly, unlocked bootloader is required to flash custom or beta firmware. While you can sideload OTA packages on a locked bootloader, I would highly recommend against doing so as you may end up with no way to recover your device.
When installing a beta, it is generally best to wipe and perform a clean flash. OTA is not recommended because beta software by nature is not yet suitable for public release, and may not appropriately handle everything correctly coming from older firmware.
As has been mentioned before, I recommend you use the Android Flash Tool to flash the beta. To ensure you have a fresh start, tick the Wipe device and Force flash all partitions boxes. Do not re-lock the bootloader.
So in short, wait for the official ota to roll out in August and install from phone then?? Cause I won't be able to unlock bootloader , phones not paid off... Would this explain why it's failing to install an beta from within the phone itself cause the bootloader's locked? So I have to wait for official ota rollout like I said earlier ??
Redbeardkevv said:
So in short, wait for the official ota to roll out in August and install from phone then?? Cause I won't be able to unlock bootloader , phones not paid off... Would this explain why it's failing to install an beta from within the phone itself cause the bootloader's locked? So I have to wait for official ota rollout like I said earlier ??
Click to expand...
Click to collapse
Most likely. I doubt the beta will pass signature verification until it is updated to public release.
So not passing signature verification would be the reason it won't install ( ota ) most likely ? I'm just confused why a patch will install ota but the beta cannot .. must have something to do with bootloader being locked and it not being an official verified release or something
Just curious
Redbeardkevv said:
Just curious
Click to expand...
Click to collapse
Yes, you need the bootloader unlocked. So you cannot use those builds - only officially released OS builds.
NippleSauce said:
Yes, you need the bootloader unlocked. So you cannot use those builds - only officially released OS builds.
Click to expand...
Click to collapse
Well that explains it not installing and saying corrupted install ... Lol
Redbeardkevv said:
Well that explains it not installing and saying corrupted install ... Lol
Click to expand...
Click to collapse
It's a beta, so there will be issues for sure (but your last comment said you are getting an error [device is corrupt] that was common a few months ago so read on). You don't need to have an unlocked bootloader to enroll in the beta. Tons of users on Verizon and AT&T with a locked BL have installed the beta. Most are fine, some have had issues.
I wouldn't install a Beta on a locked BL. Why risk it? If something goes wrong, you'll need to get a warranty replacement. Seems like such a hassle.
For your issue, since you said you're getting a device corrupt message. This message is caused by q few different things (there's a thread on here about it). To fix it, users needed to do a factory reset in recovery mode. If you really wanted to try installing the beta (and you understand the risks), you'd probably need to: go to recovery mode and perform a wipe/factory reset.
From there, you could install the latest stable ota (via recovery mode) then see if the beta will update for you (via beta enrollment like you are trying to do), or directly flash the beta ota (link below). I'm just not sure if you can flash a beta ota image, over a stable build. I haven't tried it but according to xda, you can be on Android 12, and flash the Beta 13 ota (instructions found here).
There's two ways to flash an Android image: ota builds via recovery mode (doesn't require BL unlock) and factory image via fastboot which can be done manually or using Google's web flash tool (flash.android.com) - both if these require BL unlock.
You can find all the latest image downloads here. Google strongly recommends to flash the beta with an unlocked bootloader using their flash web tool. It's a beta so I would stay away until you can unlock your bootloader. Don't risk it. But I still think it might be a good idea for you to eventually perform a factory reset from recovery mode, since you are seeing the device is corrupt error message.
Had same problem, tried installing it twice and gave up