Develop Bugs

Downgrade to original 7.1.2

Hi,
Is it possible to downgrade to 7.1.2 and have my phone completely stock?
I mean like it was, no rooted or something else..
Now I have the latest oreo version from google.
Thanks

thanasisglt said:
Hi,
Is it possible to downgrade to 7.1.2 and have my phone completely stock?
I mean like it was, no rooted or something else..
Now I have the latest oreo version from google.
Thanks
Click to expand...
Click to collapse
Yes just flash latest 7.1 bullhead image and then relock bootloader and you will have your device like stock but why would you downgrade?!

Yes just flash latest 7.1 bullhead image and then relock bootloader and you will have your device like stock but why would you downgrade?!
Click to expand...
Click to collapse
My device is slower than 7.1.2 and also I don't like the layout.
Is there any guide how to do that?
Thanks

thanasisglt said:
My device is slower than 7.1.2 and also I don't like the layout.
Is there any guide how to do that?
Thanks
Click to expand...
Click to collapse
Sorry to answer hours after but I didn't got any notifications...
So, download,
platform tools : https://developer.android.com/studio/releases/platform-tools
Latest 7.1.2 build : https://dl.google.com/dl/android/aosp/bullhead-n2g48c-factory-45d442a2.zip
Then exctract the content of the 7.1.2 build in the platform tools folder then connect you smartphone to your PC in bootloader mode (vol down + power button).
Finally in the platform tools folder you will find a file named flashall.bat, simply execute it and you are done, your device will be on stock 7.1.2
PS: This guide was done assuming you know how to lock and unlock your bootloader if not...tell me ? (kidding happy to help ? ).

francos21 said:
Sorry to answer hours after but I didn't got any notifications...
So, download,
platform tools : https://developer.android.com/studio/releases/platform-tools
Latest 7.1.2 build : https://dl.google.com/dl/android/aosp/bullhead-n2g48c-factory-45d442a2.zip
Then exctract the content of the 7.1.2 build in the platform tools folder then connect you smartphone to your PC in bootloader mode (vol down + power button).
Finally in the platform tools folder you will find a file named flashall.bat, simply execute it and you are done, your device will be on stock 7.1.2
PS: This guide was done assuming you know how to lock and unlock your bootloader if not...tell me (kidding happy to help ? ).
Click to expand...
Click to collapse
Thanks a lot for the guidance!
Unfortunately, I don't know how to unlock and lock the bootloader. I 've never done this before and always had my device stock. Any advice would be helpful!
Thanks

thanasisglt said:
Any advice would be helpful!
Click to expand...
Click to collapse
Read the instructions.

thanasisglt said:
Thanks a lot for the guidance!
Unfortunately, I don't know how to unlock and lock the bootloader. I 've never done this before and always had my device stock. Any advice would be helpful!
Thanks
Click to expand...
Click to collapse
NOTE : unlocking bootloader will erase all your data!!!
NOTE 2 : If you lock your bootloader without the factory image flashed you will brick your device so no more usable!!!!! So personnaly I don't recommand you to do that because you don't need that to return on Android 7 it's just a "security" for your data.
NOTE 3 : read this guide too because it's more complete and what you are going to do is a bit risky(I speak for locking bootloader) , really! Don't want a message saying "you forgot this line, my device is lost ? ...".
So let's start fun things ?
Go in developer options and enable oem unlock and USB debugging.
Then reboot in bootloader mode and connect your device to your computer.
After that open the prompt command from the extracted platform tools folder by right clicking in this folder with the maj key down.
In this command windows write the following line:
fastboot oem unlock
Or .\fastboot oem unlock if your are on windows 10 (windows is blue instead of black).
When the bootloader is unlocked you can flash a custom recovery then instal a ROM/kernel or flash the factory image.
When you have flashed the factory image (stock ROM...) you can lock the bootloader with this line(same method)
fastboot oem lock (add .\ for windows 10).
Tell me if you need further help ? .

francos21 said:
NOTE : unlocking bootloader will erase all your data!!!
NOTE 2 : If you lock your bootloader without the factory image flashed you will brick your device so no more usable!!!!! So personnaly I don't recommand you to do that because you don't need that to return on Android 7 it's just a "security" for your data.
NOTE 3 : read this guide too because it's more complete and what you are going to do is a bit risky(I speak for locking bootloader) , really! Don't want a message saying "you forgot this line, my device is lost ...".
.
Click to expand...
Click to collapse
Thanks again!
I have to lock the bootloader if I downgrade because bank apps don't work if the device is not stock as far as I know..
other than that I don't mind to be unlocked and playing with custom roms..

thanasisglt said:
Thanks again!
I have to lock the bootloader if I downgrade because bank apps don't work if the device is not stock as far as I know..
other than that I don't mind to be unlocked and playing with custom roms..
Click to expand...
Click to collapse
That's actually not true, at least I think as I don't use bank apps that don't accept that my bank app is accepting root too ?
But seriously, from where did you catch the info?

francos21 said:
That's actually not true, at least I think as I don't use bank apps that don't accept that my bank app is accepting root too
But seriously, from where did you catch the info?
Click to expand...
Click to collapse
I have read comments from developers to advice users whose apps are not functional that the devices should not be rooted and generally should be stock.
Anyways..I will think it again if I continue to the procedure..
PS: I hate the layout of oreo..these white (like LG) squared app icons are simply terrible!

thanasisglt said:
I have read comments from developers to advice users whose apps are not functional that the devices should not be rooted and generally should be stock.
Anyways..I will think it again if I continue to the procedure..
PS: I hate the layout of oreo..these white (like LG) squared app icons are simply terrible!
Click to expand...
Click to collapse
Android layout can be changed easily and having latest Android security offer security and latest features and performances patchs, anyway it's your decision.

thanasisglt said:
I have read comments from developers to advice users whose apps are not functional that the devices should not be rooted and generally should be stock.
Anyways..I will think it again if I continue to the procedure..
PS: I hate the layout of oreo..these white (like LG) squared app icons are simply terrible!
Click to expand...
Click to collapse
Just keep in mind that unlocking the bootloader and flashing the original rom will NOT result in a rooted phone. If you do the this and relock the bootloader, then your phone will be in a totally stock NON ROOTED state. So any concerns that you have regarding root don't apply here.

I am still on 7.1.2 too because of the performance/lag issues in 8.1
... I never upgraded... Is it still really that bad in 8.1 ? Or better with latest patches?
Sent from my [device_name] using XDA-Developers Legacy app

_giwrgos_ said:
Just keep in mind that unlocking the bootloader and flashing the original rom will NOT result in a rooted phone. If you do the this and relock the bootloader, then your phone will be in a totally stock NON ROOTED state. So any concerns that you have regarding root don't apply here.
Click to expand...
Click to collapse
Hi,
my device got bootlooped. Warranty expired 20 days ago and the cost was too high to repair.
So, I followed an online tutorial, flashed my phone and came back to life.
The issue is that the bootloader is unlocked and I cannot use android pay (it says that the device is somehow altered)
Although banking apps work normally.
Is it ok to relock the bootloader?
(what if the device get bootloop again? / is it possible to brick my device? / could I use another way to bypass and activate android pay?)
Thanks

thanasisglt said:
Hi,
my device got bootlooped. Warranty expired 20 days ago and the cost was too high to repair.
So, I followed an online tutorial, flashed my phone and came back to life.
The issue is that the bootloader is unlocked and I cannot use android pay (it says that the device is somehow altered)
Although banking apps work normally.
Is it ok to relock the bootloader?
(what if the device get bootloop again? / is it possible to brick my device? / could I use another way to bypass and activate android pay?)
Thanks
Click to expand...
Click to collapse
Firstly let me tell you that I am assuming that you have flashed an official stock rom, if you didn't then just ignore what I am saying!
I never heard of anyone bricking the device just by locking the bootlader. The worst thing that can happen is to get a bootloop indeed, but if you just unlock the bootloader again then it should be fixed. Bricking the device just by locking the bootloader sounds totally impossible to me at least. I don't know if there is another way to bypass this and activate android pay but even if there is personally I will not have trusted it.

Bricked device? Tried to downgrade to oreo help?

Hello, I tried downgrading today to oreo (from official version of pie) because I wanted to root and flash resuruction remix rom. I unlocked my bootloader and then I installed android oreo from the website for pixel 2 xl, copied the files into the adb directory and ran the "flash-all" batch file. But now my device is stuck at the google screen with the unlcoked lock image, before this screen it says that my device is corrupt. How can I solve this issue and go back to oreo?
Thanks

abdane said:
Hello, I tried downgrading today to oreo (from official version of pie) because I wanted to root and flash resuruction remix rom. I unlocked my bootloader and then I installed android oreo from the website for pixel 2 xl, copied the files into the adb directory and ran the "flash-all" batch file. But now my device is stuck at the google screen with the unlcoked lock image, before this screen it says that my device is corrupt. How can I solve this issue and go back to oreo?
Thanks
Click to expand...
Click to collapse
Please list your exact steps trying to flash back to Oreo.
Unless I am mistaken (it does happen) I was under the impression flashing the 8.1 factory image was all that's needed to return to stock Oreo.
List your steps/process (and files used) and let's see if someone can't help you out.

Initially, I unlocked my bootloader and data was wiped, then I installed android 8.1 (the recommended version from resuruction remix rom forum) and extracted the files into the directory of adb, then I ran "flash-all" and it was running, then at the end it showed a fail error and now my device is not booting up, I can only access fastboot mode

abdane said:
Hello, I tried downgrading today to oreo (from official version of pie) because I wanted to root and flash resuruction remix rom. I unlocked my bootloader and then I installed android oreo from the website for pixel 2 xl, copied the files into the adb directory and ran the "flash-all" batch file. But now my device is stuck at the google screen with the unlcoked lock image, before this screen it says that my device is corrupt. How can I solve this issue and go back to oreo?
Thanks
Click to expand...
Click to collapse
Could be your Android PlatformTools are out of date?

abdane said:
Initially, I unlocked my bootloader and data was wiped, then I installed android 8.1 (the recommended version from resuruction remix rom forum) and extracted the files into the directory of adb, then I ran "flash-all" and it was running, then at the end it showed a fail error and now my device is not booting up, I can only access fastboot mode
Click to expand...
Click to collapse
If I am reading your steps right...
My suggestion is flash vanilla Oreo.
I wouldnt be surprised of there is some parition structure change that the Modded ROM is screwing up.
get back to vanilla
Mod after being stabel

parakleet said:
If I am reading your steps right...
My suggestion is flash vanilla Oreo.
I wouldnt be surprised of there is some parition structure change that the Modded ROM is screwing up.
get back to vanilla
Mod after being stabel
Click to expand...
Click to collapse
Im sorry, what do you mean by vanilla oreo? You mean the very first oreo ROM?

parakleet said:
If I am reading your steps right...
My suggestion is flash vanilla Oreo.
I wouldnt be surprised of there is some parition structure change that the Modded ROM is screwing up.
get back to vanilla
Mod after being stabel
Click to expand...
Click to collapse
abdane said:
Im sorry, what do you mean by vanilla oreo? You mean the very first oreo ROM?
Click to expand...
Click to collapse
I think the suggestion is that you flash the stock factory 8.1 image found on the Google site (the link to it is in my 9x and 8x links in my sig).
I agree with this.
Fastboot the factory 8.1 image using the flash-all, leave the -w in so you wipe any fragments, and you should have a brand new, fresh start.

Az Biker said:
I think the suggestion is that you flash the stock factory 8.1 image found on the Google site (the link to it is in my 9x and 8x links in my sig).
I agree with this.
Fastboot the factory 8.1 image using the flash-all, leave the -w in so you wipe any fragments, and you should have a brand new, fresh start.
Click to expand...
Click to collapse
I think I confused you guys, sorry, what i did is that I flashed the STOCK version of 8.1 Oreo, I wanted to downgrade from pie. I installed the official one from google and ran the "flash-all" command and failed at vendor_b

michaelbsheldon said:
Could be your Android PlatformTools are out of date?
Click to expand...
Click to collapse
I just uninstalled it, installed the latest version and still not working :/

I am trying to fastboot the files separately: bootloader, boot, radio, system and vendor images. They all pass except for the vendor image, it always fails there (Data write failure unknown error). Any help?

abdane said:
I just uninstalled it, installed the latest version and still not working :/
Click to expand...
Click to collapse
If you are for sure unlocked and critical unlocked, next step is to unzip everything in the Google factory image (about 25 files), then
use this with instructions listed: https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
It's fixed things for me several times when I just could not get results with flash-all.bat.

Alright, wow finally I got it to work. THe issue was either the cable or the port, I was using the originisl type-c to type c cable, tried my old LG G5 typeA to type c and worked fine, wow. Thanks for the help everyone!!! Phone is back and alive

abdane said:
Alright, wow finally I got it to work. THe issue was either the cable or the port, I was using the originisl type-c to type c cable, tried my old LG G5 typeA to type c and worked fine, wow. Thanks for the help everyone!!! Phone is back and alive
Click to expand...
Click to collapse
I thought you already read over my 8x or 9x guides, or I would've mentioned that in the first place
8x Guide:
-have a 2.0 USB in case your 3.0 USB doesn't work properly
-Reboot PC, change between 2.0 and 3.0 cables, and change USB ports if having trouble using fastboot
9x Guide:
*Unlocked bootloader and Critical_unlock completed.
*Latest SDK Tools found here
*USB 2.0 & 3.0 cables available (trust me)

hi dude, I have the same problem with you , have you solved yet?
after flash the factory image android o , it shows device corrupt..

Az Biker said:
I thought you already read over my 8x or 9x guides, or I would've mentioned that in the first place
8x Guide:
-have a 2.0 USB in case your 3.0 USB doesn't work properly
-Reboot PC, change between 2.0 and 3.0 cables, and change USB ports if having trouble using fastboot
9x Guide:
*Unlocked bootloader and Critical_unlock completed.
*Latest SDK Tools found here
*USB 2.0 & 3.0 cables available (trust me)
Click to expand...
Click to collapse
This exact info should be a sticky on every single thread!!

CyberpodS2 said:
This exact info should be a sticky on every single thread!!
Click to expand...
Click to collapse
I just created a "troubleshooting thread" for this situation in the 2 XL guides section
Link in my sig.
Should be much easier to point people to these steps before we spend two pages trying to help out just to find out it was a USB cable, or old SDK tools

Ble_Ale said:
hi dude, I have the same problem with you , have you solved yet?
after flash the factory image android o , it shows device corrupt..
Click to expand...
Click to collapse
I've had this happened a couple of times no Rhyme or Reason the only way out of it is to flash The Flash all with the -w. I believe it has something to do with Googles security.
Edit. I take that back I've switched to the other slot before and restored a backup and gotten out of it if that other slot isn't corrupt

I thought Android Pie has a mandatory "Anti Roll back" feature that prevents going back to Android Oreo?
That is not true then?!

samteeee said:
I thought Android Pie has a mandatory "Anti Roll back" feature that prevents going back to Android Oreo?
That is not true then?!
Click to expand...
Click to collapse
unless you do fastboot flashing unlock and fastboot flashing unlock_critical it is not possible to roll back.
if you do both above you can over-write the critical partitions allowing the roll-back.
the general population would not be doing these, so in essence they do block rolling back to earlier versions, but in a disaster situation it can be done.

uicnren said:
unless you do fastboot flashing unlock and fastboot flashing unlock_critical it is not possible to roll back.
if you do both above you can over-write the critical partitions allowing the roll-back.
the general population would not be doing these, so in essence they do block rolling back to earlier versions, but in a disaster situation it can be done.
Click to expand...
Click to collapse
Got it. Thanks for the explanation.

Can’t get out of bootloader

Guys I need your help and I’m desperate to someone get me to the right dirrection.
I just got a pixel 2 xl, I unlock the bootloader and root with twrp. I try to install a lineage os rom with the gaps and it looks like everything when the well. I erase the cache and free I reboot it went back to the bootloader screen. From that point I have been spending all day trying to get back to factory or at least trying to install any other rom with out any luck. It someone can help me out I will be more than happy to send a Starbucks card or something. I just got the phone,

I forgot to mention that when I try to use the and side load it says something about the e drive, like if there es no drive on my phone

rectangularspace said:
Guys I need your help and I’m desperate to someone get me to the right dirrection.
I just got a pixel 2 xl, I unlock the bootloader and root with twrp. I try to install a lineage os rom with the gaps and it looks like everything when the well. I erase the cache and free I reboot it went back to the bootloader screen. From that point I have been spending all day trying to get back to factory or at least trying to install any other rom with out any luck. It someone can help me out I will be more than happy to send a Starbucks card or something. I just got the phone,
Click to expand...
Click to collapse
Do you know and understand how you use fastboot or the Deuces script to flash factory images to return you to stock OS?

Well not really. But I follow many instrucciones from differents post and nothing

rectangularspace said:
Well not really. But I follow many instrucciones from differents post and nothing
Click to expand...
Click to collapse
Read over this thread. Then let us know if you need help. https://forum.xda-developers.com/pi...de-reference-8x-oreo-to-t3826330/post77530335
Also, if you have twrp installed, you can flash the OTA zip that corresponds to your current OS version :good:

I do have twrp installed the problem is that I don’t have the zip on the phone to install the ota file.

Try with deceus Script (Just search for it) and select repair bootloop. It will download the factory Image and flash it on a and b partition then your phone will boot again. But your data will be lost :/

Ok., I will let you guys know thank you

Also, I forgot to mention that it looks like that I don’t have a OS installed ( twrp is telling me that every time i try to get out to the get out of the twrp menu. At this point i haven’t don’t anything mention in this post because I’m resetting my computer nd I’m installing right now the android sdk software.

You don't have to install the full Android SDK software for the job you're trying to do. You can download the latest Fastboot commands and ADB through Google, or even XDA(somewhere).
I've installed adb to my Windows commands, so once in recovery, when I need a file, I just "adb push file.zip /sdcard/".
No worries though. You'll be back up and running. ?
Edit: Also, if you still have data on your phone, you can check using the file explorer on TWRP. If you do, you can adb pull anything you want to keep.

@rectangularspace Link to the standalone platform tools HERE. This is all you need.

Guys. It's working now. I follow the instructions and when I execute the batch I notice that it was missing some files but it did worked, I was able to start over. One thing I notice is that play store was not updating the apps , I had to reboot a couple of times even force stop play store and it looks like is working. I was gonna ask, it's been a long time since I was in Android, if I decide to update to os 9 (pie) if I don't like it, can I downgrade to any previous OS?

rectangularspace said:
Guys. It's working now. I follow the instructions and when I execute the batch I notice that it was missing some files but it did worked, I was able to start over. One thing I notice is that play store was not updating the apps , I had to reboot a couple of times even force stop play store and it looks like is working. I was gonna ask, it's been a long time since I was in Android, if I decide to update to os 9 (pie) if I don't like it, can I downgrade to any previous OS?
Click to expand...
Click to collapse
Yes, but going down from 9 to 8 will cause/require a data wipe.

rectangularspace said:
Guys. It's working now. I follow the instructions and when I execute the batch I notice that it was missing some files but it did worked, I was able to start over. One thing I notice is that play store was not updating the apps , I had to reboot a couple of times even force stop play store and it looks like is working. I was gonna ask, it's been a long time since I was in Android, if I decide to update to os 9 (pie) if I don't like it, can I downgrade to any previous OS?
Click to expand...
Click to collapse
Why did you decide to install Oreo?? There will be no further security or functionality updates for 8.1. The next monthly update to Pie should be the first Monday of next month (October 1st) if you don't get a OTA nag before then.

I have the update available to install on my settings. But what I'm looking for is to start over on rooting my pixel 2 xl. But after last experience I'm a little conservative when it comes to mess with the phone. I'm reading right now the post where it says to do the critical unlock for the phone but I don't know witch bootloader version I have. Can you guys help me out

I have tmz10n version on my bootloader. It means that I need to do the critical unlock? By the way I did already unlock my bootloader and i Haven lock it again. And I think at some point when I was having trouble with my phone to put it back to run I did also the critical unlock process.

rectangularspace said:
I have tmz10n version on my bootloader. It means that I need to do the critical unlock? By the way I did already unlock my bootloader and i Haven lock it again. And I think at some point when I was having trouble with my phone to put it back to run I did also the critical unlock process.
Click to expand...
Click to collapse
You only need to do the unlock process one time, BUT there are two separate unlock commands which include unlock_critical. If in doubt you can use fastboot device-info or getvar to check the current status. Make sure you are using the latest version of the platform tools I linked to above. One word of caution... don't EVER re-lock your bootloader or you WILL run into problems. Even if you are returning the phone to Google for RMA you do not need to re-lock it.

My bad, after unlock my bootloader I haven't look back again. So it is unlock right now. Thank you for advised. For what I read the only way to unlock it it will be by running the command fastboot right? If I upgrade to pie using the upgrade available in my settings right now, it will not lock the bootloader right?

rectangularspace said:
My bad, after unlock my bootloader I haven't look back again. So it is unlock right now. Thank you for advised. For what I read the only way to unlock it it will be by running the command fastboot right? If I upgrade to pie using the upgrade available in my settings right now, it will not lock the bootloader right?
Click to expand...
Click to collapse
I meant the only way to lock the bootloader will be thru a fastboot command.

rectangularspace said:
I meant the only way to lock the bootloader will be thru a fastboot command.
Click to expand...
Click to collapse
Yes, once you have successfully unlocked the phone in fastboot using the two separate commands, you will never have to do it again, AND flashing anything will not re-lock the bootloader. Please read over Nathan's GUIDE HERE to confirm you have done this correctly (and completely). Once this is done you can flash OTA's , full Google images, custom roms, etc. Lastly, if you are properly unlocked you cannot brick your phone. No matter how bad it gets, you will always have a path to restore the phone to it's original state. Don't hesitate to take the OTA being offered on your phone. It will take you to 9.0 without losing data or locking anything. :good:

Downgrade to emui 5

I got a Huawei mate se and didn't realize that allowing it to update to Android o would block the bootloader unlock tool. Is there anyway to downgrade my firmware so I can unlock my bootloader?

voldomart13 said:
I got a Huawei mate se and didn't realize that allowing it to update to Android o would block the bootloader unlock tool. Is there anyway to downgrade my firmware so I can unlock my bootloader?
Click to expand...
Click to collapse
There is a roll-back ROM on firmware finder. As long as it shows your IMEI as approoved, it should install.
That's the nice clean way.
There is a dirty ( possibly dangerous way ) by using the nougat service ROM. That ROM is for bnd-L21, so not sure how an unlocked bootloader will handle it. It has worked on unlocked before.

mrmazak said:
There is a roll-back ROM on firmware finder. As long as it shows your IMEI as approoved, it should install.
That's the nice clean way.
There is a dirty ( possibly dangerous way ) by using the nougat service ROM. That ROM is for bnd-L21, so not sure how an unlocked bootloader will handle it. It has worked on unlocked before.
Click to expand...
Click to collapse
I have been attempting to use firmware finder but I can't wrap my head around actually pushing the update. I heard you need an outdated version of hisuite but no one specifies what version. Any help is appreciated =)

voldomart13 said:
I have been attempting to use firmware finder but I can't wrap my head around actually pushing the update. I heard you need an outdated version of hisuite but no one specifies what version. Any help is appreciated =)
Click to expand...
Click to collapse
Insttall firmware finder from playstore.
In the app select the "hamburger" menu, from top left corner. Select instructions. Either watch videos, or read the text guides

mrmazak said:
Insttall firmware finder from playstore.
In the app select the "hamburger" menu, from top left corner. Select instructions. Either watch videos, or read the text guides
Click to expand...
Click to collapse
The mobile app as far as I can tell doesn't work on newer versions of android. They even have a disclaimer mentioning that the app only works for older devices now.

voldomart13 said:
The mobile app as far as I can tell doesn't work on newer versions of android. They even have a disclaimer mentioning that the app only works for older devices now.
Click to expand...
Click to collapse
You are not on 8.1, the app can work.
But I was only referencing the app for the guides linked inside.
You should be able to use it to flash b330. Which should work in DC

mrmazak said:
You are not on 8.1, the app can work.
But I was only referencing the app for the guides linked inside.
You should be able to use it to flash b330. Which should work in DC
Click to expand...
Click to collapse
My bad I am on 8.0 to be specific bnd-l34 8.0.0.341(c567) and as much as I've tried I can not get it to work on the phone following along on the videos. They are using the app on emui 5.0 not 8.0. It doesn't work anymore on 8.0

All there videos revolve around emui 5.0 or lower. It stopped working with 8.0

voldomart13 said:
My bad I am on 8.0 to be specific bnd-l34 8.0.0.341(c567) and as much as I've tried I can not get it to work on the phone following along on the videos. They are using the app on emui 5.0 not 8.0. It doesn't work anymore on 8.0
Click to expand...
Click to collapse
Because the locked bootloader, you can only use the firmwares that are approoved.
Chances are , the only one that's approoved is the b330
And if not , then only option is the service-rom. Followed by dc-unlock, then the hwota and correct ROM
It has been done.
There should be confirmation back in the mate thread somewhere.

mrmazak said:
Because the locked bootloader, you can only use the firmwares that are approoved.
Chances are , the only one that's approoved is the b330
And if not , then only option is the service-rom. Followed by dc-unlock, then the hwota and correct ROM
It has been done.
There should be confirmation back in the mate thread somewhere.
Click to expand...
Click to collapse
Which mate thread?

voldomart13 said:
Which mate thread?
Click to expand...
Click to collapse
I'm searching. I know i have recommended this process many times, and got many success responses. But I am striking out in finding threads with confirmed responses.
This search only shows 4 found matches for the search info. One does fit real good, but the author has made it sound , not real credible.
https://forum.xda-developers.com/search/forum/7100?query=unlock mate service-rom#posts

mrmazak said:
Because the locked bootloader, you can only use the firmwares that are approoved.
Chances are , the only one that's approoved is the b330
And if not , then only option is the service-rom. Followed by dc-unlock, then the hwota and correct ROM
It has been done.
There should be confirmation back in the mate thread somewhere.
Click to expand...
Click to collapse
What about this method? https://www.getdroidtips.com/full-guide-install-stock-firmware-huawei-smartphone/

mrmazak said:
I'm searching. I know i have recommended this process many times, and got many success responses. But I am striking out in finding threads with confirmed responses.
This search only shows 4 found matches for the search info. One does fit real good, but the author has made it sound , not real credible.
https://forum.xda-developers.com/search/forum/7100?query=unlock mate service-rom#posts
Click to expand...
Click to collapse
This post you made here sounds doable.
This service rom so far has been only thing we found that will load with three button method (dload)
But it is not a full rom to keep on device. It needs you to follow up with flashing fullOTA of your correct version after.
https://www.androidfilehost.com/?fid...83647474828964
1. Unzip download
2. copy the dload folder to root of sdcard
3. power on phone holding all three buttons
4. After phone finishes and reboots, unlock frp and bootloader, if needed
5. Use Huru or HWOTA to flash correct firmware for your model/ region.
Enlighten me what is huru or hwota? If I were to flash this does it boot up into android or is it non functional?

voldomart13 said:
This post you made here sounds doable.
This service rom so far has been only thing we found that will load with three button method (dload)
But it is not a full rom to keep on device. It needs you to follow up with flashing fullOTA of your correct version after.
https://www.androidfilehost.com/?fid...83647474828964
1. Unzip download
2. copy the dload folder to root of sdcard
3. power on phone holding all three buttons
4. After phone finishes and reboots, unlock frp and bootloader, if needed
5. Use Huru or HWOTA to flash correct firmware for your model/ region.
Enlighten me what is huru or hwota? If I were to flash this does it boot up into android or is it non functional?
Click to expand...
Click to collapse
Yes, this should leave you able to boot. And with build level that should allow DC unlocked to give you the code.
Remember like I said before this is kind of a dirty way around and 'could' have issues unknown. Like what if DC does not give you a code, you would then be stuck . (Though you are stuck now)
Huru and hwota are very similar. They both use TWRP to give custom flashing control.
Hwota uses modified stock recovery to flash full ota files.
Huru repacks full ota files so that TWRP can flash them.
Since doth start with TWRP , bootloader unlock is needed.

mrmazak said:
Yes, this should leave you able to boot. And with build level that should allow DC unlocked to give you the code.
Remember like I said before this is kind of a dirty way around and 'could' have issues unknown. Like what if DC does not give you a code, you would then be stuck . (Though you are stuck now)
Huru and hwota are very similar. They both use TWRP to give custom flashing control.
Hwota uses modified stock recovery to flash full ota files.
Huru repacks full ota files so that TWRP can flash them.
Since doth start with TWRP , bootloader unlock is needed.
Click to expand...
Click to collapse
I see. And say dc cant get a code I would be stuck no way of recovery? Man I miss the days of samsung phones and using odin for upgrade/downgrade =/ been doing this stuff since samsung captivate days.

voldomart13 said:
I see. And say dc cant get a code I would be stuck no way of recovery? Man I miss the days of samsung phones and using odin for upgrade/downgrade =/ been doing this stuff since samsung captivate days.
Click to expand...
Click to collapse
Just spent most of the morning going back and forth with someone else with mate see, and they just did restored his device with the service ROM.
I do not now what he was restoring from, but he ended up with "unknown model" and default build number of 8.0.0.46
This is because of (probably) some data corrupt issue making the flash go bad. But he was able to run the ROM and unlock boooader.
Difference is he already had his unlock code.
https://forum.xda-developers.com/honor-7x/help/dload-method-stuck-5-t3821898

voldomart13 said:
I see. And say dc cant get a code I would be stuck no way of recovery? Man I miss the days of samsung phones and using odin for upgrade/downgrade =/ been doing this stuff since samsung captivate days.
Click to expand...
Click to collapse
Have you seen this guide?
It is for "official" hisuite roll-back
I have not rolled back so do not know it it works though.(I checked with my device, it shows no downgrade available)
I know the roll-back firmwarm listed on firmware finder was listed as "bond" and not "bnd". So this means not available "officially"
https://usermanual.wiki/Huawei/EMUI...roid70OperationInstructionpdf.1621060771/help

OTA update for my Pixel 2 XL?

So I have determined my Pixel unfortunately has the Verizon brand and can't unlock the bootloader. When I bought it Android 11 was installed and I would still like to take it back to Android 10. According to what I read I can sideload, I think the term is, an OTA image without unlocking the bootloader. Is that correct brfore I think about trying? My blink light is intermittent and the weather widget doesn't work, figured maybe if I backed up I could have better success. Thanks....

Yes. Sideloading an OTA update should work regardless of the lock status of the bootloader as the package is signed by Google.

Strephon Alkhalikoi said:
Yes. Sideloading an OTA update should work regardless of the lock status of the bootloader as the package is signed by Google.
Click to expand...
Click to collapse
OK thanks for reaffirming that for me. If I get enough nerve to try this I will give it a shot, if it doesn't go well is there a way to back out to the present status of Android 11?

bcsman said:
OK thanks for reaffirming that for me. If I get enough nerve to try this I will give it a shot, if it doesn't go well is there a way to back out to the present status of Android 11?
Click to expand...
Click to collapse
There are ways. Unfortunately I don't know if the locked bootloader will stymie those ways.

Strephon Alkhalikoi said:
There are ways. Unfortunately I don't know if the locked bootloader will stymie those ways.
Click to expand...
Click to collapse
Yes kind of figured as much....