Updates stucked @ B101 on BL locked unmodified phone, how to official update? - Honor 7X Questions & Answers

Guys, stuck @ ancient version B101 on my honor 7X for ages.
Want Oreo with faceunlock but that damn thing doesnt show me a single update.
Tried FF and it finds all the updates for my phone but sadly the DNS/VPN mehtod doesnt work -> package checksum error.
Redownloaded the updates multiple times and tried other updates with the same result.
FF states that the files i have tried are approved.
Any chance to manually flash the downloaded full OTAs?
thx
pOpY

you can try updating via hurupdater, but you might lose your data in the process.

Thanks, will post in that thread.
pOpY

Related

Installing a "Not Approved" firmware from Firmware Finder

Hi,
My device is still stuck at B102. I tried to install the "Approved" updates in FF but they failed. I noticed that you have to come from a specific firmware to update to a new one. Like to install the B124, you have to come from B123. This concludes that updates come in sequence. However, the next software after B102 is B105 but this version is "not approved" for installation.
So my question is, has anybody tried to install a "not approved" firmware with success? What's the consequence? Will it just say it failed then boots back to normal or will it mess up my device?
Thanks for answering.
it wont install it will error out.
darkmage1991 said:
it wont install it will error out.
Click to expand...
Click to collapse
Is there any other way now?

Updating BND-L21 To Stable Stock Oreo / Any Daily Driver Oreo Custom Rom

Hi!
So i bought this phone not too long ago (about 2 months) and i heared of people getting offical oreo update
My model is the L-21 C432 with the custom version C432D001
i can't seem to get the update throught the official updater and the Huawei rom finder app fails to download the rom with both proxy and dns ways
i installed TWRP in hope of backing up the system and trying stuff on my own but that also fails as i can't backup system partition . . .
So my question is : How can i update this device to an Oreo Rom (Treble preffered) ?
mimminou said:
Hi!
So i bought this phone not too long ago (about 2 months) and i heared of people getting offical oreo update
My model is the L-21 C432 with the custom version C432D001
i can't seem to get the update throught the official updater and the Huawei rom finder app fails to download the rom with both proxy and dns ways
i installed TWRP in hope of backing up the system and trying stuff on my own but that also fails as i can't backup system partition . . .
So my question is : How can i update this device to an Oreo Rom (Treble preffered) ?
Click to expand...
Click to collapse
My opinion is there is little to no need to backup nougat. Because there is a "roll-back" firmware available and also when you upgrade to Oreo the partition table gets changed , so the twrp backup will not work anyhow.
To make ylur update, if ota is not working, then search for and use "hwota".
mrmazak said:
My opinion is there is little to no need to backup nougat. Because there is a "roll-back" firmware available and also when you upgrade to Oreo the partition table gets changed , so the twrp backup will not work anyhow.
To make ylur update, if ota is not working, then search for and use "hwota".
Click to expand...
Click to collapse
Thank you ... i made sure to look up every way possible to upgrade and yet didn't find HwOTA until you told me about it, lots of interesting stuff to learn on the tool !
i'll give it a try whne i get back home ! thanks again
EDIT : i just noticed that you are the op of the guide i followed , very detailed and well explained !
mimminou said:
Thank you ... i made sure to look up every way possible to upgrade and yet didn't find HwOTA until you told me about it, lots of interesting stuff to learn on the tool !
i'll give it a try when i get back home ! thanks again
Click to expand...
Click to collapse
So i checked the HWota methode and it seemed very legitimate .... well when i tried it i even got the EMUI logo and beneath it it says Updating ... at 100 percent the phone rebooted and .... nothing happened, not even data was erased ... well actually 2 things happened :
- My bootloader was locked back and now i have stock recovery ( which is nice tbh i was looking for ways to get it back .. and i still got the unlock code so i'm good to go )
- My phone now actually notified me that there is an OTA update to Oreo and that's the thing i was looking for .... so did it work ? kind of , did i fulfill my goal ? Yes i did and Thank you so much
mimminou said:
So i checked the HWota methode and it seemed very legitimate .... well when i tried it i even got the EMUI logo and beneath it it says Updating ... at 100 percent the phone rebooted and .... nothing happened, not even data was erased ... well actually 2 things happened :
- My bootloader was locked back and now i have stock recovery ( which is nice tbh i was looking for ways to get it back .. and i still got the unlock code so i'm good to go )
- My phone now actually notified me that there is an OTA update to Oreo and that's the thing i was looking for .... so did it work ? kind of , did i fulfill my goal ? Yes i did and Thank you so much
Click to expand...
Click to collapse
Ok, so you used hwota and the fullOTA for nougat. This made bootloder lock.?
Good to know, I was not aware of that.
But good results in the end.
mrmazak said:
Ok, so you used hwota and the fullOTA for nougat. This made bootloder lock.?
Good to know, I was not aware of that.
But good results in the end.
Click to expand...
Click to collapse
i actually used the full OTA of Oreo ... that's why i said nothing happened ... it did not update even tho it brought new features like AI Lens ...
i noticed another thing ... the write recovery bat file detected that my rom was on OREO ... which wan't the case it was still androind 7.1 EMUI 5
Well i've been running Oreo since 3 days Now
Great new features to the camera and some minor battery life improvements
mimminou said:
i actually used the full OTA of Oreo ... that's why i said nothing happened ... it did not update even tho it brought new features like AI Lens ...
i noticed another thing ... the write recovery bat file detected that my rom was on OREO ... which wan't the case it was still androind 7.1 EMUI 5
Click to expand...
Click to collapse
mimminou said:
Well i've been running Oreo since 3 days Now
Great new features to the camera and some minor battery life improvements
Click to expand...
Click to collapse
Hi, how you got android Nougat 7.1?
I bought the same phone model BND L21 C432 with Nougat 7.0 and updated to 8.0.0.330 with FF app, but after that FF never works to update to new updates like 8.0.0.331 which is the latest for our device. How can I update to latest firmware or to Nougat 7.1 manually or with HWota without unlock bootloader ? (my bootloader is locked).
Any tips will be helpful, I'm new to this tipe of phone which is flashing different from my old Galaxy S5, thank you.
Actually, the latest is 8.0.0.332 from 2 days ago.
Bosket said:
Hi, how you got android Nougat 7.1?
I bought the same phone model BND L21 C432 with Nougat 7.0 and updated to 8.0.0.330 with FF app, but after that FF never works to update to new updates like 8.0.0.331 which is the latest for our device. How can I update to latest firmware or to Nougat 7.1 manually or with HWota without unlock bootloader ? (my bootloader is locked).
Any tips will be helpful, I'm new to this tipe of phone which is flashing different from my old Galaxy S5, thank you.
Click to expand...
Click to collapse
I don't think you can do much with a locked bootloader i'm sorry
i'm also not used to this new method of flashing as i used primarely samsungs before too
There is However a service to unlock your bootloader for 4€ even after Huawei shut down the unlock website ... if you can pay that's great but if you can't or you are not willing to you can always wait as somd people will figur out the way the unlock code is generated / stored
mimminou said:
Hi!
So i bought this phone not too long ago (about 2 months) and i heared of people getting offical oreo update
My model is the L-21 C432 with the custom version C432D001
i can't seem to get the update throught the official updater and the Huawei rom finder app fails to download the rom with both proxy and dns ways
i installed TWRP in hope of backing up the system and trying stuff on my own but that also fails as i can't backup system partition . . .
So my question is : How can i update this device to an Oreo Rom (Treble preffered) ?
Click to expand...
Click to collapse
Hi, is your phone single or dual SIM?
mimminou said:
Hi!
So i bought this phone not too long ago (about 2 months) and i heared of people getting offical oreo update
My model is the L-21 C432 with the custom version C432D001
i can't seem to get the update throught the official updater and the Huawei rom finder app fails to download the rom with both proxy and dns ways
i installed TWRP in hope of backing up the system and trying stuff on my own but that also fails as i can't backup system partition . . .
So my question is : How can i update this device to an Oreo Rom (Treble preffered) ?
Click to expand...
Click to collapse
It supposed to be officiall update, so why twrp? My phone is full stock, have the fw downloaded and still failed at 5%!
aspot72 said:
It supposed to be officiall update, so why twrp? My phone is full stock, have the fw downloaded and still failed at 5%!
Click to expand...
Click to collapse
I couldn't follow what you said but to make myself clear ... i used HwOta methode and updated to Oreo .... Hwota failed but when i booted the rom i got Ota update from settings ... how ? i still don't know maybe Hwota updated the cust partition (almost certain) so my device was eligible for update ....
Now i'm rocking LOs Beta 5 and it's working fine so far except for the secondary camera Focus thing ...
mimminou said:
I couldn't follow what you said but to make myself clear ... i used HwOta methode and updated to Oreo .... Hwota failed but when i booted the rom i got Ota update from settings ... how ? i still don't know maybe Hwota updated the cust partition (almost certain) so my device was eligible for update ....
Now i'm rocking LOs Beta 5 and it's working fine so far except for the secondary camera Focus thing ...
Click to expand...
Click to collapse
Well, to make it as clear as possible, if the update is officiall why we need twrp for update? When checking the desired ROM it's approved for installation, however when trying to update at 5% it says failed. My broadband is down, so can use my phone only, and the HwOTA is for pc
aspot72 said:
Well, to make it as clear as possible, if the update is officiall why we need twrp for update? When checking the desired ROM it's approved for installation, however when trying to update at 5% it says failed. My broadband is down, so can use my phone only, and the HwOTA is for pc
Click to expand...
Click to collapse
Oh Ok
I think you need TWRP to flash the stock recovery that has "cached code"
Basically the recovery you flash will have a specific commande to flash the stock rom from a specific directory in sd card ... this is why you DON'T change the name of any Folder / File during the HwOta flashing unless you know how to mess with Updater script file
Appart from that i still don't know any method on how to do this without PC even if Ota is approved .... i suggest you to tether your Internet to your pc ... as far as i remember Emui had that feature
mimminou said:
Oh Ok
I think you need TWRP to flash the stock recovery that has "cached code"
Basically the recovery you flash will have a specific commande to flash the stock rom from a specific directory in sd card ... this is why you DON'T change the name of any Folder / File during the HwOta flashing unless you know how to mess with Updater script file
Appart from that i still don't know any method on how to do this without PC even if Ota is approved .... i suggest you to tether your Internet to your pc ... as far as i remember Emui had that feature
Click to expand...
Click to collapse
Will give it a try, thanks.

Android 9 Pie update

Soooo.....I just bought this phone, unlocked the bootloader and installed Magisk.
Today, I got a system update notification saying Android Pie is ready to download.
Anybody else getting this and if so, I have to go back to 100% stock in order to upgrade right? Then unlock BL again?
Mine isn't showing the update yet. I've got the TA-1068. Not unlocked or anything.
It is possible someone jumped the gun, releasing it too early, and they pulled it so can't download it.
Not yet available on my nokia 6.1. I think we are a couple of weeks away from the update.
Ozonethegreat said:
Soooo.....I just bought this phone, unlocked the bootloader and installed Magisk.
Today, I got a system update notification saying Android Pie is ready to download.
Anybody else getting this and if so, I have to go back to 100% stock in order to upgrade right? Then unlock BL again?
Click to expand...
Click to collapse
Which TA....?
Ozonethegreat said:
Soooo.....I just bought this phone, unlocked the bootloader and installed Magisk.
Today, I got a system update notification saying Android Pie is ready to download.
Anybody else getting this and if so, I have to go back to 100% stock in order to upgrade right? Then unlock BL again?
Click to expand...
Click to collapse
What security update level of android 8.1 are you on?
Good luck getting 100% back to stock.
I have a TA-1045 and I unlocked the bootloader and installed Magisk on the July patch of android 8.1. I get update prompts for the August security update, but the update won't install. I tried completely removing Magisk, but it stills fails with "Installation Failed". I don't think anyone has a stock recovery image (at least for TA-1045) to restore
At this point if you flash twrp/magisk you have no way of restoring to stock and accepting OTA updates. You will be stuck on the update you are on until someone figures out a way to take OTA updates or someone gets a hold of stock firmware images for your device (none yet for TA-1045)
EricH7001 said:
Which TA....?
Click to expand...
Click to collapse
TA-1045
prg318 said:
What security update level of android 8.1 are you on?
Good luck getting 100% back to stock.
I have a TA-1045 and I unlocked the bootloader and installed Magisk on the July patch of android 8.1. I get update prompts for the August security update, but the update won't install. I tried completely removing Magisk, but it stills fails with "Installation Failed". I don't think anyone has a stock recovery image (at least for TA-1045) to restore
At this point if you flash twrp/magisk you have no way of restoring to stock and accepting OTA updates. You will be stuck on the update you are on until someone figures out a way to take OTA updates or someone gets a hold of stock firmware images for your device (none yet for TA-1045)
Click to expand...
Click to collapse
I'm on the June 1st level
prg318 said:
What security update level of android 8.1 are you on?
Good luck getting 100% back to stock.
I have a TA-1045 and I unlocked the bootloader and installed Magisk on the July patch of android 8.1. I get update prompts for the August security update, but the update won't install. I tried completely removing Magisk, but it stills fails with "Installation Failed". I don't think anyone has a stock recovery image (at least for TA-1045) to restore
At this point if you flash twrp/magisk you have no way of restoring to stock and accepting OTA updates. You will be stuck on the update you are on until someone figures out a way to take OTA updates or someone gets a hold of stock firmware images for your device (none yet for TA-1045)
Click to expand...
Click to collapse
I've was able to get back to stock recovery, system and vendor using the 1043 images and my phone still shows as a 1045. So even if removing magisk, it fails, cause I'm getting the installation failed as well. I'm curious if removing magisk and relocking the bootloader will help?
Mobe1969 said:
Mine isn't showing the update yet. I've got the TA-1068. Not unlocked or anything.
It is possible someone jumped the gun, releasing it too early, and they pulled it so can't download it.
Click to expand...
Click to collapse
That makes sense cause I keep getting installation failure and not sure if it even downloaded.
Ozonethegreat said:
I've was able to get back to stock recovery, system and vendor using the 1043 images and my phone still shows as a 1045. So even if removing magisk, it fails, cause I'm getting the installation failed as well. I'm curious if removing magisk and relocking the bootloader will help?
Click to expand...
Click to collapse
Since earlier today, I was able to flash my phone with the WW images and my phone still shows up as TA-1045, radio works and everything. The Pie update isn't showing up for me yet, but I was able to update to the august update this way
prg318 said:
Since earlier today, I was able to flash my phone with the WW images and my phone still shows up as TA-1045, radio works and everything. The Pie update isn't showing up for me yet, but I was able to update to the august update this way
Click to expand...
Click to collapse
Are the WW images the chinese version I seen floating around here? If not, where did you get them?
Ozonethegreat said:
Are the WW images the chinese version I seen floating around here? If not, where did you get them?
Click to expand...
Click to collapse
Nope - don't think its Chinse - it appears to be a "global" or international version. I don't really notice a difference from my original stock.
I got it from here: https://forum.xda-developers.com/no...-to-flash-global-firmware-pl2-222e-0-t3831764
And was able to flash the "extracted version" with fastboot. I used some fastboot instructions that I found for a chinese rom and changed the filenames to match the worldwide filenames and it worked without the OST tool
Ozonethegreat said:
That makes sense cause I keep getting installation failure and not sure if it even downloaded.
Click to expand...
Click to collapse
Can you locate the downloaded OTA and post it here?
Ozonethegreat said:
Soooo.....I just bought this phone, unlocked the bootloader and installed Magisk.
Today, I got a system update notification saying Android Pie is ready to download.
Anybody else getting this and if so, I have to go back to 100% stock in order to upgrade right? Then unlock BL again?
Click to expand...
Click to collapse
Were you able to update to Android pie?
Danny1976 said:
Were you able to update to Android pie?
Click to expand...
Click to collapse
No I have not been able to. I don't even know where to look to see if the OTA even downloaded...
Ozonethegreat said:
Soooo.....I just bought this phone, unlocked the bootloader and installed Magisk.
Today, I got a system update notification saying Android Pie is ready to download.
Anybody else getting this and if so, I have to go back to 100% stock in order to upgrade right? Then unlock BL again?
Click to expand...
Click to collapse
Can you check under system partition and look for Data/OTA
---------- Post added at 04:37 PM ---------- Previous post was at 04:14 PM ----------
Ozonethegreat said:
No I have not been able to. I don't even know where to look to see if the OTA even downloaded...
Click to expand...
Click to collapse
Check system partition under data/ota.
Ozonethegreat said:
No I have not been able to. I don't even know where to look to see if the OTA even downloaded...
Click to expand...
Click to collapse
You should have pulled the OTA link from a logcat so the rest of us can download the update files and upgrade ourselves :/
I guess this OTA is a fake. No one with a Nokia 6.1 has reported getting an Android Pie notification. It's super rare that just one single person will get it.
Danny1976 said:
I guess this OTA is a fake. No one with a Nokia 6.1 has reported getting an Android Pie notification. It's super rare that just one single person will get it.
Click to expand...
Click to collapse
This. Unless OP is an insider and just dun goof'd, then I fail to see this as legit.
Slightly off-topic:
I was on the June security patch on my 6.1 until yesterday. I received an OTA notification while half asleep and got all excited thinking it was the Pie update, but no, it was the July security patch. What's interesting is that immediately after installing I received the notification for the August security patch, and promptly installed that. May just be me being lucky, but that almost imples that HMD are trying to push out the latest security updates to devices as a way of preparing for Pie maybe?
neowlchaz said:
This. Unless OP is an insider and just dun goof'd, then I fail to see this as legit.
Slightly off-topic:
I was on the June security patch on my 6.1 until yesterday. I received an OTA notification while half asleep and got all excited thinking it was the Pie update, but no, it was the July security patch. What's interesting is that immediately after installing I received the notification for the August security patch, and promptly installed that. May just be me being lucky, but that almost imples that HMD are trying to push out the latest security updates to devices as a way of preparing for Pie maybe?
Click to expand...
Click to collapse
I got the July update in July and then I got the August update on August. I don't know why yours took a while to update. Mine and other that I know, get the update for the month the same month.

12.5 update on QGGMIXM

So, this may be a dumb question but I can't seem to find the answer anywhere. I have my phone for almost two years now, and it used to get the updates the right way, until the 12.0.7, then it just stopped getting any updates, when I checked it says "no updates avaliable".
Searching yesterday, I manage to update it to 12.0.8 by changing the device region to India, but it just stopped there, I can't update to 12.5 or further.
While searching i've seen that the devices different from QGGMIXM (which mine is), like RGGMIXM already got the updates.
I even tried to install the 12.5 update (for RGGMIXM) manually and it said it could not verify the update.
Is there any way to change QGGMIXM to RGGMIXM or to get the update without changing it? Any help are appreciated
Illyve1 said:
So, this may be a dumb question but I can't seem to find the answer anywhere. I have my phone for almost two years now, and it used to get the updates the right way, until the 12.0.7, then it just stopped getting any updates, when I checked it says "no updates avaliable".
Searching yesterday, I manage to update it to 12.0.8 by changing the device region to India, but it just stopped there, I can't update to 12.5 or further.
While searching i've seen that the devices different from QGGMIXM (which mine is), like RGGMIXM already got the updates.
I even tried to install the 12.5 update (for RGGMIXM) manually and it said it could not verify the update.
Is there any way to change QGGMIXM to RGGMIXM or to get the update without changing it? Any help are appreciated
Click to expand...
Click to collapse
1/ Try to use vpn app and change to other
2/ Try method downgrade with ota on youtube
3/ Unlock bootloader and flash rom you want by twrp or mi flash tool
Kirasu2080 said:
1/ Try to use vpn app and change to other
2/ Try method downgrade with ota on youtube
3/ Unlock bootloader and flash rom you want by twrp or mi flash tool
Click to expand...
Click to collapse
1/ Just tried vpn, didn't work
2/ Neither downgrading or upgrading worked, downgrading says it's unable to downgrade and tried to upgrade says it couldn't verify the update
3/ I haven't tried this yet, but I'm guessing it'll be the only way to update it.

Question Android 13 beta 3.3 won't install ...

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

Categories

Resources