Related
Hi guys,
I'm using Honor 7x BND-AL10C675 (Indian). I wanted to get back to stock as emui 8 stable rolled out. I was running emui 8 beta and I was stuck so I flashed the stock recovery, re locked bootloader, and downloaded the EMUI 8 update.app file from "Huawei firmware finder". Now, I created the "dload" folder in sd card and pressing both volume buttons and power button, I tried to install the firmware.
It says "The update failed" at 5% and I tried it many times. Maybe it's a mismatch or incompatible. Now, I can't go back to my twrp backup as stock recovery was installed. I can't flash recovery or rom using fastboot as it requires unlocked bootloader. To unlock bootloader, I need to enable "OEM UNLOCK" in settings and I can't boot into system as everything is wiped when I relocked the bootloader. So I'm basically stuck.
The only things I can do now is to install the stock firmware using the dload method. However, I need the right update.app file so I can install using install the firmware. I can't use Nougat file as I guess we can't go back to Nougat from Oreo. So I need EMUI 8 firmware BND AL10C675.
I can't find it anywhere, so Could someone miraculously post a download link or the file here? What should I be doing?
Thetpcguy said:
Hi guys,
I'm using Honor 7x BND-AL10C675 (Indian). I wanted to get back to stock as emui 8 stable rolled out. I was running emui 8 beta and I was stuck so I flashed the stock recovery, re locked bootloader, and downloaded the EMUI 8 update.app file from "Huawei firmware finder". Now, I created the "dload" folder in sd card and pressing both volume buttons and power button, I tried to install the firmware.
It says "The update failed" at 5% and I tried it many times. Maybe it's a mismatch or incompatible. Now, I can't go back to my twrp backup as stock recovery was installed. I can't flash recovery or rom using fastboot as it requires unlocked bootloader. To unlock bootloader, I need to enable "OEM UNLOCK" in settings and I can't boot into system as everything is wiped when I relocked the bootloader. So I'm basically stuck.
The only things I can do now is to install the stock firmware using the dload method. However, I need the right update.app file so I can install using install the firmware. I can't use Nougat file as I guess we can't go back to Nougat from Oreo. So I need EMUI 8 firmware BND AL10C675.
I can't find it anywhere, so Could someone miraculously post a download link or the file here? What should I be doing?
Click to expand...
Click to collapse
you need this?
http://pro-teammt.ru/firmware-database/?firmware_model=BND-AL10+8.0.0.320&firmware_page=0
Thats' so fast!! I really thank you for coming at rescue for a fellow XDA member. Thanks for the link and I couldn't find the link myself really. Do you have any idea which file I should download? there is one full Ota MF and other two are just Ota MF. Maybe full Ota mf? I guess I downloaded the firmware from the app from these guys or website only on my android phone. I will do it now on my laptop now. Let's hope it works!! Thanks again
mrmazak said:
you need this?
http://pro-teammt.ru/firmware-database/?firmware_model=BND-AL10+8.0.0.320&firmware_page=0
Click to expand...
Click to collapse
Thats' so fast!! I really thank you for coming at rescue for a fellow XDA member. Thanks for the link and I couldn't find the link myself really. Do you have any idea which file I should download? there is one full Ota MF and other two are just Ota MF. Maybe full Ota mf? I guess I downloaded the firmware from the app from these guys or website only on my android phone. I will do it now on my laptop now. Let's hope it works!! Thanks again
mrmazak said:
you need this?
http://pro-teammt.ru/firmware-database/?firmware_model=BND-AL10+8.0.0.320&firmware_page=0
Click to expand...
Click to collapse
I downloaded it but the update failed again. I guess the file is not the right one for this model but I don't know why it's listed as the right model. I thought I could install stock Emui 8 Rom by downloading from "firmware finder" so I just locked myself out of all the options now. Such a shame
Thetpcguy said:
I downloaded it but the update failed again. I guess the file is not the right one for this model but I don't know why it's listed as the right model. I thought I could install stock Emui 8 Rom by downloading from "firmware finder" so I just locked myself out of all the options now. Such a shame
Click to expand...
Click to collapse
I'm not positive on the correct DLOAD method
I think you extract the update.zip to dload folder on sdcard.
The whole zip package, not just the update.app
Thetpcguy said:
I downloaded it but the update failed again. I guess the file is not the right one for this model but I don't know why it's listed as the right model. I thought I could install stock Emui 8 Rom by downloading from "firmware finder" so I just locked myself out of all the options now. Such a shame
Click to expand...
Click to collapse
Did you do this guide?
https://forum.xda-developers.com/showpost.php?p=73954487&postcount=240
I followed all the steps and I guess it's more complicated for me. I was stuck with an older build number although I changed different ROMS. Maybe because of that the update doesn't authenticate and fails to install the firmware. I don't know but also it maybe that the firmware isn't for my exact model. I just don't know and my phone is as good as bricked and I"m taking it to service centre.
What's more hurting is that, I Locked myself out of all the options. I mean I have the bootloader unlock code, Twrp backup but I just went through a one way route so confidently that it would work and I locked bootloader, flashed stock recovery. It's such a shame that HUAWEI DOESN'T RELEASE THE STOCK FIRMWARE EVEN AFTER ALMOST 6 MONTHS OF THE HONOR 7X RELEASE. If they had the stock firmware available just like Xiaomi, I wouldn't have had all this trouble.
I don't know why no one raises the voice. I really hate Huawei for this and I'll make sure I won't recommend these phones to anyone.
Thetpcguy said:
I followed all the steps and I guess it's more complicated for me. I was stuck with an older build number although I changed different ROMS. Maybe because of that the update doesn't authenticate and fails to install the firmware. I don't know but also it maybe that the firmware isn't for my exact model. I just don't know and my phone is as good as bricked and I"m taking it to service centre.
What's more hurting is that, I Locked myself out of all the options. I mean I have the bootloader unlock code, Twrp backup but I just went through a one way route so confidently that it would work and I locked bootloader, flashed stock recovery. It's such a shame that HUAWEI DOESN'T RELEASE THE STOCK FIRMWARE EVEN AFTER ALMOST 6 MONTHS OF THE HONOR 7X RELEASE. If they had the stock firmware available just like Xiaomi, I wouldn't have had all this trouble.
I don't know why no one raises the voice. I really hate Huawei for this and I'll make sure I won't recommend these phones to anyone.
Click to expand...
Click to collapse
Any update you got for the problem... Ian also stuck for same reason... If you have any update pls let me know...?
---------- Post added at 05:13 PM ---------- Previous post was at 05:13 PM ----------
Thetpcguy said:
I followed all the steps and I guess it's more complicated for me. I was stuck with an older build number although I changed different ROMS. Maybe because of that the update doesn't authenticate and fails to install the firmware. I don't know but also it maybe that the firmware isn't for my exact model. I just don't know and my phone is as good as bricked and I"m taking it to service centre.
What's more hurting is that, I Locked myself out of all the options. I mean I have the bootloader unlock code, Twrp backup but I just went through a one way route so confidently that it would work and I locked bootloader, flashed stock recovery. It's such a shame that HUAWEI DOESN'T RELEASE THE STOCK FIRMWARE EVEN AFTER ALMOST 6 MONTHS OF THE HONOR 7X RELEASE. If they had the stock firmware available just like Xiaomi, I wouldn't have had all this trouble.
I don't know why no one raises the voice. I really hate Huawei for this and I'll make sure I won't recommend these phones to anyone.
Click to expand...
Click to collapse
Any update you got for the problem... Ian also stuck for same reason... If you have any update pls let me know...
srvm1983 said:
Any update you got for the problem... Ian also stuck for same reason... If you have any update pls let me know...
---------- Post added at 05:13 PM ---------- Previous post was at 05:13 PM ----------
Any update you got for the problem... Ian also stuck for same reason... If you have any update pls let me know...
Click to expand...
Click to collapse
Phone is sold as a scrap for 2000 RS (30$ approx) There was no way to revive it after losing that fastboot and getting that above said error state.
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.
Hi guys
So recently there was some uploads to Firmware Finder of some BETA's of EMUI 9 of China models BUT please be sure to read this before you try anything with this beta sofware.
I recently, about a week ago when the BETA came out I was really excited like maybe you are but I did a mess noone on this Forum could fix literally.
DO NOT FOLLOW ANY PROCEDURE OF THIS!
Now what I did was:
1. I unlocked both FRP and bootloader of my device.
2. I flashed TWRP recovery
3. I backup my oem-info (ANE-LX1C432) and copied it to my sd card
4. I flashed the oem-info of the chinese model (ANE-AL00) which I copied to my sd card
5. I flashed the Hurupdater with all necessary files from the Firmware Finder.
6. Rebooted phone and it booted normally.
7. Setup screen did not appear and EMUI 9 took me directly to the home screen, I had no google play services of course since it's a chinese ROM, almost no system apps but gestures were present and quite smooth and fast actually. The ROM was fast.
8. Went to Settings-->System-->Developer options-->OEM unlocking was gray which I found pretty weird but then I searched Google and in China they do not have that option on Developer settings so maybe that's why it was gray.
Anyway since this option was gray I thought (stupidly) that maybe after a factory reset the option would become changeable again. It didn't. At that time the phone did a factory reset and afterwords by bootloader become "Relocked" and FRP was "locked. At that time system was unbootable no matter what you try.
Tried multiple commands via fastboot but since FRP is locked you can't do anything that change the system, even the FRP unlock code I got which I payed for (20€) did not work (Not sure why either but I think it's because since my oem-info changed the IMEI was changed randomly or something like it). I thought the command "fastboot boot twrp.img" would work right? but nope, nothing allowed.
Second thing I tried was the dload packages of course. I tried all kinds of packages. Tried the one I installed, the ANE-AL00C01 (9.0.1.100) one. Didn't work as it is the same version. Tried to downgrade for an older EMUI 9 beta package like ANE-AL00C01 (9.0.1.41) and did not work either.
Packages above ^ were from the Firmware so nothing is signed by Huawei.
Then I tried signed packages both from this ANE-AL00 model and my model ANE-LX1C432 but nothing seemed to work.
Only thing I thought of was to flash motherboard firmware which I looked deep into the FCC certification tests you can find this on Google:
https://fccid.io/QISANE-LX1/Test-Report/BLE-Test-report-3742444
Which tells us the motherboard base software version for my model is ANE-LX1 8.0.0.41(SP1C900).
But we don't have access to it of course since it's motherboard official software from Huawei, so maybe only some official Huawei Repair Center have the right tools for this.
BUT, on easy firmware you can get it for 15€. Easy firmware is trusted and they do have an unofficial tool that can flash official motherboard software.
Now before I tried it, I sent my phone to warranty. And I gotta say, I was not very confident about it. I sent it for repair on 6 of February and I said the phone couldn't boot and I installed a beta version via Hicare app (this is how I maybe thought they could believe me), by the way the eRecovery was in chinese so I said I installed a chinese official beta from Huawei from Hicare XDDDDDDDDD
Do you know what they did? It was not an official Huawei Repair Center, although I do have one in my country, it was just one authorized by Huawei, they said the phone didn't boot as well OK, but then they just replaced the whole motherboard due to a IMEI issue, flashed the base firmware from EMUI 8.
After that I payed nothing since it was on warranty, got "a new phone" pretty much, charging port is new but battery is the same I think, and learned something interesting, NEVER FLASH CHINESE OEM-INFO's !!!!!!!!
But seriously, I'm an IT Technician and I thought I had so much luck here because if they knew what I did I would have to pay for the repair and quite a lot (just the motherboard is 200€ btw) !
Altough I was quite pissed cause why the fk wouldn't they just flashed the board software again? YIKES
Anyways, I'm happy, while I had no phone I trusted my old moto g 2014 (titan) with sailfish OS 3 and I then realised how much I want a fkin Sony Xperia X or XA2 so I can have
that best OS of all time and still have those nasty android apps
And if you need a guide for the correct installation of EMUI 9 Chinese beta , please contact @qouet or check his thread here:
https://forum.xda-developers.com/huawei-p20-lite/development/port-nova3e-official-rom-to-ane-lx1-t3897076
I'm not sure how is it going but too have the gapps you gotta work a bit i guess,
People like me with a P20 Lite main phone, just wait for stable versions or flash european versions without changing oem-info's please Don't make the mistake I did and almost buy a new phone
Cheers to all!
AS
Did you try to change oeminfo using HwOTA?
Zerogoki_00 said:
Did you try to change oeminfo using HwOTA?
Click to expand...
Click to collapse
I woulded have tried but since I can't flash or boot a twrp image you can't do much on those cases HwOTA relies on a TWRP recovery.
Thanks!
AS
Is there already Dark Theme on EMUI 9? Thanks.
Sent from my ONEPLUS A6003 using XDA-Developers Legacy app
gelo01 said:
Is there already Dark Theme on EMUI 9? Thanks.
Sent from my ONEPLUS A6003 using XDA-Developers Legacy app
Click to expand...
Click to collapse
Hey
For now I only know that the feature is only present on Huawei Mate 20RS, Mate 20X and Mate 20 Pro due to higher capacity batteries, here's the official info:
https://consumer.huawei.com/uk/support/faq/have-you-tried-the-new-dark-interface-from-emui-9/
But maybe it will come eventually in the future for all Huawei phones with EMUI 9 as a standard feature but for now nope...
Cheers,
AS
Hello,
I received my oneplus 9 pro (global) the other day, and it's been working great. I rooted it no problem with a boot image I found on xda, and patched it using magisk manager. However, whenever I try to download the newest update, it fails every time. The first time it says that it's paused, and that it will continue whenever you press resume. I press resume, and then it says a problem occurred.
I tried to delete the .OTA folder, but it's no where to be found. I also tried to factory reset, as well as flashing the unpatched boot image, but it did not work.
Here's the link as to where I found the global boot image
[GUIDE] [Magisk] [Unlock / ROOT / Keep Root] OOS 13.1.0.500
Different variants of Magisk that are available for use : Magisk Variant Stable / Beta / Canary Release Official Android / OOS OOS 11 and above Maintainer topjohnwu Project Link GitHub Zygisk No...
forum.xda-developers.com
if it is not the right version, or if there's a way to restore the original boot image, please let me know!
Andrew8578 said:
Hello,
I received my oneplus 9 pro (global) the other day, and it's been working great. I rooted it no problem with a boot image I found on xda, and patched it using magisk manager. However, whenever I try to download the newest update, it fails every time. The first time it says that it's paused, and that it will continue whenever you press resume. I press resume, and then it says a problem occurred.
I tried to delete the .OTA folder, but it's no where to be found. I also tried to factory reset, as well as flashing the unpatched boot image, but it did not work.
Here's the link as to where I found the global boot image
[GUIDE] [Magisk] [Unlock / ROOT / Keep Root] OOS 13.1.0.500
Different variants of Magisk that are available for use : Magisk Variant Stable / Beta / Canary Release Official Android / OOS OOS 11 and above Maintainer topjohnwu Project Link GitHub Zygisk No...
forum.xda-developers.com
if it is not the right version, or if there's a way to restore the original boot image, please let me know!
Click to expand...
Click to collapse
Same here, was literally just googling for help.
vibrantliker said:
Same here, was literally just googling for help.
Click to expand...
Click to collapse
As far as I know, you can't take an OTA (incremental update) with either an unlocked bootloader or root. Not sure which of these is the actual culprit. I'm on the Global version (AA) and just flashed the full BA update. All is working well, only downside is that Dolby Atmos doesn't have the equalizer on the EU (BA) version. Everything else including 5G is working as it should, just like on previous versions of the OnePlus devices I've had (3T, 5, 6T, 7Pro and 8Pro).
zoman7663 said:
As far as I know, you can't take an OTA (incremental update) with either an unlocked bootloader or root. Not sure which of these is the actual culprit. I'm on the Global version (AA) and just flashed the full BA update. All is working well, only downside is that Dolby Atmos doesn't have the equalizer on the EU (BA) version. Everything else including 5G is working as it should, just like on previous versions of the OnePlus devices I've had (3T, 5, 6T, 7Pro and 8Pro).
Click to expand...
Click to collapse
I'm from the US, so I don't know if the network band will be the same, if so as good on the BA version.
If anything, i'll just wait for the official Global release on their website. It's just infuriating to see something that annoys me get fixed, such as the white navigation bar in split screen, and not being able to update.
Andrew8578 said:
I'm from the US, so I don't know if the network band will be the same, if so as good on the BA version.
If anything, i'll just wait for the official Global release on their website. It's just infuriating to see something that annoys me get fixed, such as the white navigation bar in split screen, and not being able to update.
Click to expand...
Click to collapse
I'm in the USA and the bands (TMobile) work fine. No difference that I can see on this device or previous using the BA builds until the AA builds get going. Every OnePlus device has been this way for me.
Andrew8578 said:
I'm from the US, so I don't know if the network band will be the same, if so as good on the BA version.
If anything, i'll just wait for the official Global release on their website. It's just infuriating to see something that annoys me get fixed, such as the white navigation bar in split screen, and not being able to update.
Click to expand...
Click to collapse
You may not want to hold your breath on that one. For whatever reason, oneplus does not release full OTA zips for AA half the time. (WTF ONEPLUS). Because of this, I long since started flashing BA over my global phone. As the gentleman said up above, it works absolutely perfectly.
zoman7663 said:
As far as I know, you can't take an OTA (incremental update) with either an unlocked bootloader or root. Not sure which of these is the actual culprit. I'm on the Global version (AA) and just flashed the full BA update. All is working well, only downside is that Dolby Atmos doesn't have the equalizer on the EU (BA) version. Everything else including 5G is working as it should, just like on previous versions of the OnePlus devices I've had (3T, 5, 6T, 7Pro and 8Pro).
Click to expand...
Click to collapse
can I just flash the BA version on top of my current rom (AA) and not lose anything? I just got done reinstalling everything, and it was a pain. I don't want to do this a 3rd time, if I can avoid it.
I never had any issues with rooting/being unlocked and updating on my previous OnePlus phones... this is a new one for me.
On 8t I had to use EU..google is who releases OTAs for all variants except EU, which is still directly from oneplus. Rooting broke OTAs for me as well on any other rom besides EU...also I have 9pro, which I local updated to EU zip b4 flashing magisk_boot.img and I already received new update since rooting and all is good.
I just flashed BA on top on my current rom via system update (you have to click the cog wheel top right and put the OTA zip on your root directory)
Nothing changed and the navigation bar in split screen is indeed fixed, meaning this is the latest version.
Thanks again for letting me know about this!
zoman7663 said:
As far as I know, you can't take an OTA (incremental update) with either an unlocked bootloader or root. Not sure which of these is the actual culprit. I'm on the Global version (AA) and just flashed the full BA update. All is working well, only downside is that Dolby Atmos doesn't have the equalizer on the EU (BA) version. Everything else including 5G is working as it should, just like on previous versions of the OnePlus devices I've had (3T, 5, 6T, 7Pro and 8Pro).
Click to expand...
Click to collapse
zoman7663 said:
I'm in the USA and the bands (TMobile) work fine. No difference that I can see on this device or previous using the BA builds until the AA builds get going. Every OnePlus device has been this way for me.
Click to expand...
Click to collapse
I'd be careful about flashing an international build for a global variant as EU regulations could be stricter, and most times are, with respect to signal strength, emissions, and other factors. Might work fine now, but there are different variants for a reason and one specific to the EU for a reason (laws are vastly different).
bulletbling said:
I'd be careful about flashing an international build for a global variant as EU regulations could be stricter, and most times are, with respect to signal strength, emissions, and other factors. Might work fine now, but there are different variants for a reason and one specific to the EU for a reason (laws are vastly different).
Click to expand...
Click to collapse
Noted, thanks for the info.
So best way then is to unroot and hope that the problem is not because of the bootloader? What's the safest way to unroot these phones. I'm on AA version (I'm new to One Plus, previously used Pixel 2 XL)
drmorrowa2 said:
So best way then is to unroot and hope that the problem is not because of the bootloader? What's the safest way to unroot these phones. I'm on AA version (I'm new to One Plus, previously used Pixel 2 XL)
Click to expand...
Click to collapse
What I want to know too!
drmorrowa2 said:
So best way then is to unroot and hope that the problem is not because of the bootloader? What's the safest way to unroot these phones. I'm on AA version (I'm new to One Plus, previously used Pixel 2 XL)
Click to expand...
Click to collapse
To unroot, go into magisk and click uninstall. Do know that I have tried this already and system update still won't go through. It appears it's being picky about the bootloader being unlocked I think. This is weird because on my OnePlus 7 pro, I did not have this issue and all I had to do was go to Magisk, uninstall ---> restore images, then do the OTA, and then have Magisk install to second slot, and then I would go back to system update, allow it to reboot, and I would still be rooted.
bulletbling said:
To unroot, go into magisk and click uninstall. Do know that I have tried this already and system update still won't go through. It appears it's being picky about the bootloader being unlocked I think. This is weird because on my OnePlus 7 pro, I did not have this issue and all I had to do was go to Magisk, uninstall ---> restore images, then do the OTA, and then have Magisk install to second slot, and then I would go back to system update, allow it to reboot, and I would still be rooted.
Click to expand...
Click to collapse
geez, I hope we don't have to relock and unlock for every update. I guess for the time being, there's no reason to be unlocked, but when custom ROM's start rolling out, that's going to be a major headache. I wonder if/when the updates are posted on One Plus website, will the updates work, or will root/unlock still prevent it?
I really want that update as I'm reading it made the battery much better. What to do!
I'm curious. so for a brand new phone why are you guys rooting it? It is not loaded with bloat ware (at least as much as samsung fpr example.) there are no custom roms yet, and oneplus is pushing updates to fix bugs. I think I'll wait till custom roms show up and then consider rooting.
TPXX said:
I'm curious. so for a brand new phone why are you guys rooting it? It is not loaded with bloat ware (at least as much as samsung fpr example.) there are no custom roms yet, and oneplus is pushing updates to fix bugs. I think I'll wait till custom roms show up and then consider rooting.
Click to expand...
Click to collapse
I root only for Viper4android but I'd like to unroot and relock bootloader again if it means I can get the updates.
I never reverse this process though. What are the best steps?
vibrantliker said:
I root only for Viper4android but I'd like to unroot and relock bootloader again if it means I can get the updates.
I never reverse this process though. What are the best steps?
Click to expand...
Click to collapse
My last rooting experience was on an S7. Afraid I can't help you with this one.
Hi there,
Just like the title says.
Xprivacylua won't' work on Android 13 for me. what I was wondering is whether I can downgrade without flashing the bootloader.
I am going to follow the following guide but am afraid to get a bricked phone
How to Bypass Anti Rollback Mechanism in Pixel 6A/6/6 Pro
This guide will show you how to bypass Anti Rollback Mechanism while doing a downgrade from Android 13 to Android 12 on Pixel 6A/6/6 Pro.
www.droidwin.com
Thank you all
------------------------add---
finally managed to downgrade to Android 12, just add --force before update:
fastboot --force update image-oriole-sq3a.220705.001.b2.zip (m phone is pixel6)
then reboot, then choose factory reset.
credits @Bunnehbunn
If you do it, regardless if you succeed or fail, you and your phone shall forever be remembered. And this day
forth shall always be named bush911 Pixel 6 Pro Day. And it shall be written and stories will be told from one generation to the next.
If you do it, the inner Yoda in me tells me to tell you to make sure you flash BOTH slots. Godspeed.
smokejumper76 said:
If you do it, regardless if you succeed or fail, you and your phone shall forever be remembered. And this day
forth shall always be named bush911 Pixel 6 Pro Day. And it shall be written and stories will be told from one generation to the next.
If you do it, the inner Yoda in me tells me to tell you to make sure you flash BOTH slots. Godspeed.
Click to expand...
Click to collapse
You've made my day
I am going to wait and see for several days before proceeding as I just know how to flash-all, I have never flashed step by step or flashed to the specific slots.
I know that Android 12 worked just fine with Android 13's bootloader, but that was before I actually upgraded to 13. After I fully upgraded to 13, I wasn't willing to test downgrading everything but the bootloader since I would have to wipe in order to have app data be consistent with the Android version.
I'm pretty sure in my thread a user (sooooo many posts this week since the update, it's all running together) that yesterday a user reported that downgrading everything but the bootloader worked just fine. Android 12 worked fine. If you do this, remember to wipe (and have a backup of anything you want to keep from your internal storage), and downgrade on both slots, not just your active slot.
roirraW edor ehT said:
I'm pretty sure in my thread a user (sooooo many posts this week since the update, it's all running together) that yesterday a user reported that downgrading everything but the bootloader worked just fine. Android 12 worked fine.
Click to expand...
Click to collapse
Oh, I have to find that post. I knew someone was talking about trying that but didn't see that they actually did. Let's see how good of a friend search really is to me
roirraW edor ehT said:
I know that Android 12 worked just fine with Android 13's bootloader, but that was before I actually upgraded to 13. After I fully upgraded to 13, I wasn't willing to test downgrading everything but the bootloader since I would have to wipe in order to have app data be consistent with the Android version.
I'm pretty sure in my thread a user (sooooo many posts this week since the update, it's all running together) that yesterday a user reported that downgrading everything but the bootloader worked just fine. Android 12 worked fine. If you do this, remember to wipe (and have a backup of anything you want to keep from your internal storage), and downgrade on both slots, not just your active slot.
Click to expand...
Click to collapse
Is downgrading on both slots a must? I have just flashed Android 13 bootloader on both slots. For now chrome (stable, beta and development) keeps crashing. I can't even finish writing this reply on Chrome.
tried clearing the cache, restarting etc., ended up with no luck . It turned out that Chrome often closes itself within no more than 5 minutes of browsing after downloading to Android 12
Post before crashing
.
bush911 said:
Is downgrading on both slots a must?
Click to expand...
Click to collapse
If you want to run Android 12 instead of 13, and you've already flashed 13 to both slots, or at least 13's bootloader to both slots (which you should definitely do if you haven't), then yes, you should downgrade both slots and wipe to start fresh.
You can't expect both Android 12 and Android 13 to operate with the same app data, so having a different version of Android on the other slot isn't going to do you any favors.
bush911 said:
I have just flashed Android 13 bootloader on both slots. For now chrome (stable, beta and development) keeps crashing. I can't even finish writing this reply on Chrome.
tried clearing the cache, restarting etc., ended up with no luck . It turned out that Chrome often closes itself within no more than 5 minutes of browsing after downloading to Android 12
Post before crashing
.
Click to expand...
Click to collapse
Try a factory reset?
Lughnasadh said:
Oh, I have to find that post. I knew someone was talking about trying that but didn't see that they actually did. Let's see how good of a friend search really is to me
Click to expand...
Click to collapse
Here my friend. Also in the OP.
Partial quote:
I tried this as soon as I upgraded to 13 and yes you can downgrade down to Android 12 after upgrading with no noticable issues. The radio and every other image but the bootloader can be downgraded. But I only tried 003, 004 July images for oriole so I don't know about anything lower personally.
Click to expand...
Click to collapse
roirraW edor ehT said:
Here my friend. Also in the OP.
Partial quote:
Click to expand...
Click to collapse
Ok, you are now officially a better friend to me than search is. Sorry search...
Thank you!!!
Lughnasadh said:
Ok, you are now officially a better friend to me than search is. Sorry search...
Thank you!!!
Click to expand...
Click to collapse
You can join the ranks of such like my boss at work (where we use Google officially for everything including company mail). They chat me to ask me for a link to a particular file that's in Google Drive, or to find a particular email for them.
Just kidding about joining the ranks! You're welcome!
roirraW edor ehT said:
Here my friend. Also in the OP.
Partial quote:
Click to expand...
Click to collapse
I guess it would just as easy to remove the bootloader line from the flash-all.bat script and just use flash-all???
It's good to know for sure that we can downgrade though and that it's only the bootloader version that is important and not other parts of the OS.
Lughnasadh said:
I guess it would just as easy to remove the bootloader line from the flash-all.bat script and just use flash-all???
It's good to know for sure that we can downgrade though and that it's only the bootloader version that is important and not other parts of the OS.
Click to expand...
Click to collapse
Absolutely, I agree on both parts.
Hi, I have a question here, as long as I don't update the latest bootloader (>= 1.2 ?), it shouldn't trigger the anti rollback mechanism? My pixel 6 with Android 13 now has a bootloader version of oriole-slider-1.1-8167057, but the bootloader version in this official page has been updated to slider-1.2-8739948.
I pulled the AOSP 13 (branch android-13.0.0_r2), built it locally (userdebug mode), and flashed it without the bootloader because there is no bootloader.img in the build output. And the phone successfully booted.
I've never flashed the Android 13 factory image, so i got away with the risk of ARB?
enderdzz said:
Hi, I have a question here, as long as I don't update the latest bootloader (>= 1.2 ?), it shouldn't trigger the anti rollback mechanism? My pixel 6 with Android 13 now has a bootloader version of oriole-slider-1.1-8167057, but the bootloader version in this official page has been updated to slider-1.2-8739948.
I pulled the AOSP 13 (branch android-13.0.0_r2), built it locally (userdebug mode), and flashed it without the bootloader because there is no bootloader.img in the build output. And the phone successfully booted.
I've never flashed the Android 13 factory image, so i got away with the risk of ARB?
Click to expand...
Click to collapse
I'm surprised with that old of a bootloader you were able to boot Android 13, you're running a bootloader from April. Also I'm surprised you weren't bricked after booting Android 13 because it does increment the anti-rollback counter.
https://cs.android.com/android/platform/superproject/+/android-13.0.0_r2:device/google/gs101/interfaces/boot/1.2/BootControl.cpp;l=226
drivers/soc/google/boot_control/boot_control_sysfs.c - kernel/gs - Git at Google
I'm guessing your bootloader version is old enough to not have the bits implemented so it just doesn't care, but that's weird because the July Android 12 bootloaders do have the bits and will not load if the counter is incremented by Android 13.
I wouldn't recommend continuing to run like this and would update to the August Android 13 bootloader because there's no telling what might be happening wrong under the hood. Example is that the August Android 13 bootloader it is able to boot Android 12 but because of interface differences it is a broken experience.
June 20, 2023 TQ3A.230605.010.A1 T-Mobile/MVNOs / June 13, 2023 TQ3A.230605.010 Global - Root Pixel 6 Pro [Raven]
Pixel 6 Pro [Raven] Updated May 13, 2023 Note that more than three users have said that 34.0.1 (even May 10, 2023's binary update of 34.0.1) did not work correctly for them. I recommend sticking with 33.0.3 (just below these quotes) Someone...
forum.xda-developers.com
So yeah if you're correct then it's possible you did get away with it as your firmware is too old to have implemented it. However this is not a supported firmware-software configuration.
Thank you for your reply!
Namelesswonder said:
I'm surprised with that old of a bootloader you were able to boot Android 13, you're running a bootloader from April.
Click to expand...
Click to collapse
Yeah. This bootloader came from the factory image `oriole-sp2a.220405.004`.
Namelesswonder said:
https://cs.android.com/android/platform/superproject/+/android-13.0.0_r2:device/google/gs101/interfaces/boot/1.2/BootControl.cpp;l=226
Click to expand...
Click to collapse
I also noticed this piece of code, but I'm not sure if it was compiled into bootloader.img or boot.img? If it's in bootloader.img, that's a good explanation, because I didn't flash this version (after June) of bootloader so the A13 now isn't restricted by anti-rollback.
BTW I am also curious why the device is not flashed bootloader.img when running `fastboot flashall -w`, even though there is a compiled bootloader.img file in the output directory.
enderdzz said:
Thank you for your reply!
Yeah. This bootloader came from the factory image `oriole-sp2a.220405.004`.
I also noticed this piece of code, but I'm not sure if it was compiled into bootloader.img or boot.img? If it's in bootloader.img, that's a good explanation, because I didn't flash this version (after June) of bootloader so the A13 now isn't restricted by anti-rollback.
BTW I am also curious why the device is not flashed bootloader.img when running `fastboot flashall -w`, even though there is a compiled bootloader.img file in the output directory.
Click to expand...
Click to collapse
That code is not in the bootloader, the bootloader is closed source. The code is part of the bootcontrolhal ([email protected]) on Android and runs on a successful boot of Android. The other code is the sysfs device being called by the HAL, that code is in the kernel.
I don't know if your device actually had the anti-rollback counter incremented, because a system monitor call is made and the source code for TZ/TEE/Titan are also closed source. Your device might've never incremented the counter because the firmware used by them just don't have the ability to, but it's just speculation.
And flashall doesn't flash bootloaders or radios, it only flashes Android system partitions defined by the product information. You can follow the steps here to flash them.
June 20, 2023 TQ3A.230605.010.A1 T-Mobile/MVNOs / June 13, 2023 TQ3A.230605.010 Global - Root Pixel 6 Pro [Raven]
Pixel 6 Pro [Raven] Updated May 13, 2023 Note that more than three users have said that 34.0.1 (even May 10, 2023's binary update of 34.0.1) did not work correctly for them. I recommend sticking with 33.0.3 (just below these quotes) Someone...
forum.xda-developers.com
Namelesswonder said:
That code is not in the bootloader, the bootloader is closed source. The code is part of the bootcontrolhal ([email protected]) on Android and runs on a successful boot of Android. The other code is the sysfs device being called by the HAL, that code is in the kernel.
I don't know if your device actually had the anti-rollback counter incremented, because a system monitor call is made and the source code for TZ/TEE/Titan are also closed source. Your device might've never incremented the counter because the firmware used by them just don't have the ability to, but it's just speculation.
And flashall doesn't flash bootloaders or radios, it only flashes Android system partitions defined by the product information. You can follow the steps here to flash them.
June 20, 2023 TQ3A.230605.010.A1 T-Mobile/MVNOs / June 13, 2023 TQ3A.230605.010 Global - Root Pixel 6 Pro [Raven]
Pixel 6 Pro [Raven] Updated May 13, 2023 Note that more than three users have said that 34.0.1 (even May 10, 2023's binary update of 34.0.1) did not work correctly for them. I recommend sticking with 33.0.3 (just below these quotes) Someone...
forum.xda-developers.com
Click to expand...
Click to collapse
Thank you very much! I'm much more clear now.
enderdzz said:
Thank you very much! I'm much more clear now.
Click to expand...
Click to collapse
That's good.
Have a question, while you were on Android 13 with the Android 12 bootloader, was everything working right? Nothing crashing or throwing errors? With the Android 13 bootloader on Android 12 having issues with DRM and web browsers crashing it would be interesting to know if the same was also true for you when you were on the opposite scenario.
Namelesswonder said:
That's good.
Have a question, while you were on Android 13 with the Android 12 bootloader, was everything working right? Nothing crashing or throwing errors? With the Android 13 bootloader on Android 12 having issues with DRM and web browsers crashing it would be interesting to know if the same was also true for you when you were on the opposite scenario.
Click to expand...
Click to collapse
Yes, I'm also interested in this topic.
I've only tested webview browser tester 101.0.4951.61 and NNAPI. No problems found so far. I will update here if I encounter any new problems
I'll experience it deeply, won't flash another system or bootloader for a while. Since I flashed the userdebug version, which I think is not as feature-rich as the factory image, but it let me have root access.
I also checked `dmesg` info and didn't find anything abnormal except that it keeps reporting `init: Control message: Could not find 'aidl/android.hardware.biometrics.fingerprint.IFingerprint/default' for ctl .interface_start from pid: 467 (/system/bin/servicemanager)`, I think it's not a big deal. And no useful log about the anti-rollback counter, which maybe needs some reverse engineering.
enderdzz said:
Yes, I'm also interested in this topic.
I've only tested webview browser tester 101.0.4951.61 and NNAPI. No problems found so far. I will update here if I encounter any new problems
I'll experience it deeply, won't flash another system or bootloader for a while. Since I flashed the userdebug version, which I think is not as feature-rich as the factory image, but it let me have root access.
I also checked `dmesg` info and didn't find anything abnormal except that it keeps reporting `init: Control message: Could not find 'aidl/android.hardware.biometrics.fingerprint.IFingerprint/default' for ctl .interface_start from pid: 467 (/system/bin/servicemanager)`, I think it's not a big deal. And no useful log about the anti-rollback counter, which maybe needs some reverse engineering.
Click to expand...
Click to collapse
If WebView applications didn't crash within minutes of launching them then that means the DRM library should either be working or just not segfaulting like it does with Android 12 on 13 bootloader.
The fingerprint scanner HAL not working is completely understandable, part of the bootloader flash also carries the fingerprint scanner's firmware, and we know that one of the big things with Android 13 is that the fingerprint scanner is somewhat more reliable, so it definitely has changed between Android 12 to 13.
Interesting stuff, will be cool to see where it can go, but man is it sketchy to recommend people still on Android 12 to downgrade to April and then try flashing the Android 13 system images, real possibility of making bricks.