Database Develop

Firmware: EVA-L09-hw-eu-V001 (???)

Good evening folks!
I've been lurking around in this amazing forum for some time now, but now i need a little bit of help.. I have searched my ass off in here and out there in google city, but can't find squat!
So...
I have this Huawei P9 that used to be EVA-L09C432B182 until yesterday when i tried to update/upgrade to C432B360 dload style. It went great i thought, 100% and succeed message. Then it rebooted to eRecovery...
I tried to update the HW_EU the same way - 99% Fail message.
I've tried update via Huawei updater as you can see in the picture below. I also tried unbrick/refurbish via Huawei updater but all that happened on Hisuite you can also see in the picture. The circle of nothing kept going for hours.
What my EVA can do? Enter eRecovery (which helps me nothing), fastboot/rescue mode (Huawei updater kinda recognizes my device, Hisuite does not.) and force update three button method (Here i get a message when trying to flash anything from ext. sd card: "Not compatible with this version, download the right software". Or something to that matter.)
If you take a look at the picture i've tried to embed below, you'll see that Huawei updater recognizes my phone as
Hardware: EVA-L09
Firmware: EVA-L09-hw-eu-V001 (Never seen or heard of!)
C- version: C000
D- version: D000
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
My question is; What can i do with this?
I'm not rooted.
[/COLOR]Phone locked.
FRP Unlock
Windows recognize as: HI3650, Huawei Android Interface.
I'll appreciate all and any links, downloads, guides, tools.. Ideas you might have!
Squirrel.
Norway

try to do "systemgjenoppretting" what happens then ?
ofcorse, swich in hisuite to "no proxy'

I have the same problem mate , i don't know what can i do . Did you try to wipe cache etc?

Arnys said:
try to do "systemgjenoppretting" what happens then ?
ofcorse, swich in hisuite to "no proxy'
Click to expand...
Click to collapse
Hisuite answers with "your device is not supported, contact local service..."

pindlosz1 said:
I have the same problem mate , i don't know what can i do . Did you try to wipe cache etc?
Click to expand...
Click to collapse
Yeah, i tried. Wipe cache - Fail. Factory reset - Fail.

Something actually happening after trying custom rom method on Huawei updater with hisuit IP/Port set manually .
Lets hope it lasts!

It helped you?

pindlosz1 said:
It helped you?
Click to expand...
Click to collapse
Don't know yet, it's going reeealy slow. I'll keep you posted!

It was going so great...
And then not so much..

I was stuck in a similar sort of place, I used a program called DC Phoenix, which I found in these forums. You have to pay a fee of 15 euros which gives you access to force flash a rom. It worked perfectly on mine after I had exhausted other options. Its part of dc unlocker. Hope that helps

Natchi said:
I was stuck in a similar sort of place, I used a program called DC Phoenix, which I found in these forums. You have to pay a fee of 15 euros which gives you access to force flash a rom. It worked perfectly on mine after I had exhausted other options. Its part of dc unlocker. Hope that helps
Click to expand...
Click to collapse
Hey!
Do you know if this Is a guaranteed succeed solution? I'll look into it. Definitely worth the 15Euros if it actually works magic!
Thanks.

Theres a forum thread somewhere on here, I cant find it at the minute, but there were numerous good reviews

Tried using SRK and update extractor. See pic.
Anyone know what i can do with this "command not allowed"?
No time for school, work or family with this **** going on..!

Natchi said:
I was stuck in a similar sort of place, I used a program called DC Phoenix, which I found in these forums. You have to pay a fee of 15 euros which gives you access to force flash a rom. It worked perfectly on mine after I had exhausted other options. Its part of dc unlocker. Hope that helps
Click to expand...
Click to collapse
I did this too , phone starts normally and it's full working but i have to write NCK code (simlock ?) . How can i repair this ?

I would try and flash a full rom using the dload method just to make sure. I flashed B136 after I reset mine to take it back to original and let it updat to b166 ota

Phoenix woke my phone up again! Thanks!! Now I'm on Nrd90m though, hoping to bring back stock.

Help
Look_Squirrel said:
Phoenix woke my phone up again! Thanks!! Now I'm on Nrd90m though, hoping to bring back stock.
Click to expand...
Click to collapse
I had the same problem, what did you do to fix it?

I downloaded DC phoenix from DC unlocker page. Bought 15 credits ≈ 15 euro
Downloaded full b361 for EVA-L09. Then followed instructions given by the program. I can explain better when I'm on my laptop if needed?
Still have no built-in camera, no BT, no NFC and no built-in flashlight..

From C900 to C432

Hi, I have a Honor 5C. I found a guide on hihonor forum for downgrading from Nogaut to MM, everything went, but if I go in the info it says "model number hi6250" and build number "NEM-C900B151", which are not mine. How do I put the NEM-L51C432B130 ROM I had before?

dont use hihonor next time... you should have extracted uödate.aöp f4om B100 and flawh wit with 3 buttons....

What can I do now? Nothing?

McCartney said:
What can I do now? Nothing?
Click to expand...
Click to collapse
try correct B100 update.app thru 3 buttons.... if this doesnt work try flashing recovery etc thru adb and then try 3 buttons. that should do it. make sure all files are correct ones, messing with recovery can lead to hard brick.

thelous said:
try correct B100 update.app thru 3 buttons.... if this doesnt work try flashing recovery etc thru adb and then try 3 buttons. that should do it. make sure all files are correct ones, messing with recovery can lead to hard brick.
Click to expand...
Click to collapse
I've already tried flashing the B120 and the B130 but it does not work. The only way is to put the TWRP? And since my phone is now recognized as "hi6250" there may be problems?

McCartney said:
I've already tried flashing the B120 and the B130 but it does not work. The only way is to put the TWRP? And since my phone is now recognized as "hi6250" there may be problems?
Click to expand...
Click to collapse
try installing stock recovery.img again thru adb, i dont remember all img files you need to make new recovery work and try it then, its in xda anyways.

McCartney said:
Hi, I have a Honor 5C. I found a guide on hihonor forum for downgrading from Nogaut to MM, everything went, but if I go in the info it says "model number hi6250" and build number "NEM-C900B151", which are not mine. How do I put the NEM-L51C432B130 ROM I had before?
Click to expand...
Click to collapse
Similar thing happened to me from messing about flashing different recoveries and roms. Went from c432 to c900. The only difference is that c432 is European region and c900 is global. It worked fine all the while it was showing c900 but I just put the update.app from b130 in dload folder on sd card and used 3 button method. You lose all your data but we all do backups-you too I'm sure, so no problems there.
Sent from my NEM-L51 using XDA Labs

In the next day try with unlock bootloder and TWRP. It's the only way.

Do you think this rollback Russian (screen) and then the c432, can I solve it?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

hi, do you managed to rollback to NEM-L51C432B130, i have de same problem. thanks

wilcaro said:
hi, do you managed to rollback to NEM-L51C432B130, i have de same problem. thanks
Click to expand...
Click to collapse
What it is your current firmware?!

PalakMi said:
What it is your current firmware?!
Click to expand...
Click to collapse
this is a honor 5c nem-l51 it was on nougat and i returned to marshmallow
now i have:
model: hi6250
build: NEM-C900B072
EMUI 4.1.1
android: 6.0
and finally i want to return on nougat
how to do this ?
thank you for your reply

wilcaro said:
this is a honor 5c nem-l51 it was on nougat and i returned to marshmallow
now i have:
model: hi6250
build: NEM-C900B072
EMUI 4.1.1
android: 6.0
and finally i want to return on nougat
how to do this ?
thank you for your reply
Click to expand...
Click to collapse
You simply need to change from C900 to C432 (sorry but I don't know how)

PalakMi said:
You simply need to change from C900 to C432 (sorry but I don't know how)
Click to expand...
Click to collapse
this is the problem
thanks anyway

wilcaro said:
this is the problem
thanks anyway
Click to expand...
Click to collapse
It is bad that honor didn't release nougat for C900 5C, you only got to change cust to C432

PalakMi said:
It is bad that honor didn't release nougat for C900 5C, you only got to change cust to C432
Click to expand...
Click to collapse
i found many users that have this problem but no solution

That's even worse

I really understand your problem, I spent hours and hours finding a solution, and I managed to find it, and it's not that hard.
1. Download Firmware Finder via Google Play Store.
2. Open it, swipe to the right, and tap on settings.
3. Tap on Use proxy to install. It will ask you to download another app, go ahead and do it.
4. Now go back to Firmware Finder and tap on "Add model", and then input the model you have without the Bxxx firmware number.
5. Tap on the model number in the main menu, and select the B351 firmware that is 2.01GB in size. You will see "FullOTA-MF-PV" under it. This is crucial for the update to be successful.
6. Now tap on "Get an update through proxy"
7. Go to your WiFi settings, press and hold on your network and go to Modify
8. Now, go to Advanced Options and enter a manual proxy. The adress is "localhost" and the port is "8.8.8.8"
9. Now, go to your Updater and download the firmware as a regular update.
10. You should be good to go! If the update hangs, go ahead and delete the proxy, and the update will finish. The nice thing is that it doesn't affect your data!
Hope it helped!

firmware finder 10.0.0.159

Anyone had a crack at installing this yet. It says it's ok for instillation

dlevick said:
Anyone had a crack at installing this yet. It says it's ok for instillation
Click to expand...
Click to collapse
I tried but without success:
https://forum.xda-developers.com/showpost.php?p=82397809&postcount=22

braunie said:
I tried but without success:
https://forum.xda-developers.com/showpost.php?p=82397809&postcount=22
Click to expand...
Click to collapse
My original firmware P20 Pro is C432
I got it working with the following config
You need HiSuite Proxy + Hisuite
https://forum.xda-developers.com/showpost.php?p=82469033&postcount=1585
(this is not the exact link but use the keywords and id given below)
CLT-LGRP2-OVS 10.0.0.159 http://update.dbankcdn.com/TDS/data/...55/v386542/f1/
CLT-AL00-CUST 10.0.0.170(C00) http://update.dbankcdn.com/TDS/data/...55/v387582/f1/
CLT-AL00l-PRELOAD 10.0.0.4(C00R1) http://update.dbankcdn.com/TDS/data/...55/v347044/f1/
One thing that was different.
After it finished recovery, I quickly unplugged the USB before my PC could recognise my phone and before my phone finished restarting.
Possibly after phone rebooting the first time, my phone tries to send a package to hisuite but it didn't get the right response or something which causes it to have an invalid signature or something.
So yeah make sure to unplug your USB as soon as it finishes, do not wait til it rebooted

blue_panther9_9 said:
My original firmware P20 Pro is C432
I got it working with the following config
You need HiSuite Proxy + Hisuite
https://forum.xda-developers.com/showpost.php?p=82469033&postcount=1585
(this is not the exact link but use the keywords and id given below)
CLT-LGRP2-OVS 10.0.0.159 http://update.dbankcdn.com/TDS/data/...55/v386542/f1/
CLT-AL00-CUST 10.0.0.170(C00) http://update.dbankcdn.com/TDS/data/...55/v387582/f1/
CLT-AL00l-PRELOAD 10.0.0.4(C00R1) http://update.dbankcdn.com/TDS/data/...55/v347044/f1/
One thing that was different.
After it finished recovery, I quickly unplugged the USB before my PC could recognise my phone and before my phone finished restarting.
Possibly after phone rebooting the first time, my phone tries to send a package to hisuite but it didn't get the right response or something which causes it to have an invalid signature or something.
So yeah make sure to unplug your USB as soon as it finishes, do not wait til it rebooted
Click to expand...
Click to collapse
Anyone else verify this yet?

Is there a walkthrough somewhere to get this hisuite proxy to work. Having difficulties getting this to happen. Firmware finder was so much handier ?

Any attempts to root yet, or how's the status of the bootloader after 10.?
I am very tempted to try it, but it can't root, I'd rather get a new phone

blue_panther9_9 said:
My original firmware P20 Pro is C432
I got it working with the following config
You need HiSuite Proxy + Hisuite
https://forum.xda-developers.com/showpost.php?p=82469033&postcount=1585
(this is not the exact link but use the keywords and id given below)
CLT-LGRP2-OVS 10.0.0.159 http://update.dbankcdn.com/TDS/data/...55/v386542/f1/
CLT-AL00-CUST 10.0.0.170(C00) http://update.dbankcdn.com/TDS/data/...55/v387582/f1/
CLT-AL00l-PRELOAD 10.0.0.4(C00R1) http://update.dbankcdn.com/TDS/data/...55/v347044/f1/
One thing that was different.
After it finished recovery, I quickly unplugged the USB before my PC could recognise my phone and before my phone finished restarting.
Possibly after phone rebooting the first time, my phone tries to send a package to hisuite but it didn't get the right response or something which causes it to have an invalid signature or something.
So yeah make sure to unplug your USB as soon as it finishes, do not wait til it rebooted
Click to expand...
Click to collapse
Hi! Can you share a walk-through from the beginning please. I am having trouble making HISuite Proxy and Hisuite work. Every time I try I get "No internet Connection". Also I would like to how to write the Package URL, I copy the complete link upto *.zip however it only pastes uptill */f1/
Looking forward to your reply.

There is a way to do it in firmware finder post here in the forum, but you need to know that your phone will be rebranded to the Chinese firmware, so for me has no sense to do it, I can wait one month more until official release ?
kamranyusuf said:
Hi! Can you share a walk-through from the beginning please. I am having trouble making HISuite Proxy and Hisuite work. Every time I try I get "No internet Connection". Also I would like to how to write the Package URL, I copy the complete link upto *.zip however it only pastes uptill */f1/
Looking forward to your reply.
Click to expand...
Click to collapse

Luis2k33-XDA said:
There is a way to do it in firmware finder post here in the forum, but you need to know that your phone will be rebranded to the Chinese firmware, so for me has no sense to do it, I can wait one month more until official release
Click to expand...
Click to collapse
Thank you! I think I will wait for another month or two before trying the methods in the firmware finder. As I have read people have soft brink their phones trying to do it.

You must warning the people that the phone with this method is rebranded to Chinese firmware clt-l00
blue_panther9_9 said:
My original firmware P20 Pro is C432
I got it working with the following config
You need HiSuite Proxy + Hisuite
https://forum.xda-developers.com/showpost.php?p=82469033&postcount=1585
(this is not the exact link but use the keywords and id given below)
CLT-LGRP2-OVS 10.0.0.159 http://update.dbankcdn.com/TDS/data/...55/v386542/f1/
CLT-AL00-CUST 10.0.0.170(C00) http://update.dbankcdn.com/TDS/data/...55/v387582/f1/
CLT-AL00l-PRELOAD 10.0.0.4(C00R1) http://update.dbankcdn.com/TDS/data/...55/v347044/f1/
One thing that was different.
After it finished recovery, I quickly unplugged the USB before my PC could recognise my phone and before my phone finished restarting.
Possibly after phone rebooting the first time, my phone tries to send a package to hisuite but it didn't get the right response or something which causes it to have an invalid signature or something.
So yeah make sure to unplug your USB as soon as it finishes, do not wait til it rebooted
Click to expand...
Click to collapse

Used Hisuite and Hisuite proxy to move my P20 Pro CLT-L04 (Canada) to android 10.0.0.159
Everything work. I will post more about the process and effects later.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
fb

fbriere56 said:
Used Hisuite and Hisuite proxy to move my P20 Pro CLT-L04 (Canada) to android 10.0.0.159
Everything work. I will post more about the process and effects later.
fb
Click to expand...
Click to collapse
By any chance would you post the process getting it to work, cheers

Look at your private message I can't post URL because my profile is too new.
You have all the information in the private messages that I have send to you.
Screenshot for the others:
fb

Warning: Today my phone is showing as not certified.
Booting into the bootloader... I have many options now. (update via usb etc)
For now don't do it if you don't understand what you are doing.

fbriere56 said:
Warning: Today my phone is showing as not certified.
Booting into the bootloader... I have many options now. (update via usb etc)
For now don't do it if you don't understand what you are doing.
This is looking like my bootloader is unlocked now.
Click to expand...
Click to collapse
I won't do it at all so, seems like it's not worth the risk, but thank you for sending the messages.

I'm doing the update in a different way right now. Using PRELOAD and CUST from 9.1 and my region (Canada) C792.
If it work, the phone will be certified.
fb

fbriere56 said:
I'm doing the update in a different way right now. Using PRELOAD and CUST from 9.1 and my region (Canada) C792.
If it work, the phone will be certified.
fb
Click to expand...
Click to collapse
Let us know the results please. Thanks

I inatalled emui 10 on my p20 pro with you settings today and everything is working just fine.

It's normal, cause maybe 159 firmware is not out and verified from Huawei and Google, it's happened sometimes with my phone when I updated firmware through modded hisuite, let me know if your method of update with cust and preload of your region of 9.1 works
Regards
fbriere56 said:
Warning: Today my phone is showing as not certified.
Booting into the bootloader... I have many options now. (update via usb etc)
For now don't do it if you don't understand what you are doing.
This is looking like my bootloader is unlocked now.
Click to expand...
Click to collapse

@fbriere56
Did you try to root version 10?

Question Unresponsive touchscreen

I am on a global firmware, version 12.5.4, and sometimes the touchscreen becomes really unresponsive to the point that the device is almost unusable. I am aware that this is a known issue, has anyone found a permanent fix? Is this still a thing on more recent ROMs?
I feel this is not acceptable on a top-of-the-line phone like the MI 11 Ultra.

You must activate antiflicker in display settings and select "custom" in "prevent accidental edge touches". This is a workaround and improve this issue, still it may occur from time to time. Otherwise you can update to the latest 12.5.6.0, so far in this version I haven't seen this problem (although with those settings enabled)

xNAPx said:
You must activate antiflicker in display settings and select "custom" in "prevent accidental edge touches". This is a workaround and improve this issue, still it may occur from time to time. Otherwise you can update to the latest 12.5.6.0, so far in this version I haven't seen this problem (although with those settings enabled)
Click to expand...
Click to collapse
Thank you. Anti flickering mode is nice. But the problem still persist. No update is available yet but buying best of best by MI and you get this small irritating UI issues is actually very bad.

Unfortunately the workaround only reduce it

Since the 12.5.6.0 touch issues are complete gone for me.
Thx god, the issues were frustratin sometimes

comediiian said:
Since the 12.5.6.0 touch issues are complete gone for me.
Thx god, the issues were frustratin sometimes
Click to expand...
Click to collapse
Hey bro, are you on RKAMIXM? And is your device rooted or unlocked bootloader? Or as original as it is out of box?

hassanaliyeh said:
Hey bro, are you on RKAMIXM? And is your device rooted or unlocked bootloader? Or as original as it is out of box?
Click to expand...
Click to collapse
Yeah, running Global Stable, Bootloader is unlocked but device is unrooted.
No need for root on my side

comediiian said:
Yeah, running Global Stable, Bootloader is unlocked but device is unrooted.
No need for root on my side
Click to expand...
Click to collapse
Thanks,
Just confirmed my theory, I couldn't update to 12.5.6 because of locked bootloader

You can push the update with advanced features. To activate them you need to press on miui button 6/7 times. After that download the latest .ZIP package (recovery update) and when in the updater select on the 3 dots in the up right "choose installation package"

xNAPx said:
You can push the update with advanced features. To activate them you need to press on miui button 6/7 times. After that download the latest .ZIP package (recovery update) and when in the updater select on the 3 dots in the up right "choose installation package"
Click to expand...
Click to collapse
I did that already and it stopped midway with stable recovery update, I had to format factory reset device and reupdate to original 12.5.4 to be able to use device normally.. And with only incremental update, it gave me an error saying cannot update with unofficial release.

May I ask you what did you download please?

Stable update 12.5.6 - local update- went all good, once reached the point to restart phone, then it fails after restart with veeeeeery slow phone and almost unresponsive, took 10mins to unlock screen instead of split of a sec.
Tried to flash a new 12.5.6 and 12.5.4 by fastboot, failed no matter what I do as bootloader is locked. The only way I got away with it was download 12.5.4 and local update it after I factory reset device which didn't help with smoothness but was needed to access local update again

AFAIK there is no fastboot 12.5.6.0 update, only recovery. I would suggest to re download the update as the one you downloaded might have been corrupted

xNAPx said:
AFAIK there is no fastboot 12.5.6.0 update, only recovery. I would suggest to re download the update as the one you downloaded might have been corrupted
Click to expand...
Click to collapse
Hi, about flashing the latest ver, this one is beta no? If i do flash it will i lose ota updates?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Why you should lose OTA updates? It is stable beta

Updated manually to 12.5.6 and the problem seems finally gone.

If your bootloader is locked I'd recommend not to update.
If it is locked and you successfully update please let me know

thyrel said:
Updated manually to 12.5.6 and the problem seems finally gone.
Click to expand...
Click to collapse
I confirm that, problem is gone. System is super smooth and reactive. Close to perfection

xNAPx said:
Why you should lose OTA updates? It is stable beta
Click to expand...
Click to collapse
I don't know, just got the phone 2 days ago. I'm trying not to mess with anything I'm not sure of.
Sorry if that seemed stupid but i do not want to risk it.
So if i update using that file I'm fine? Also is it the correct file or it should be bigger??

Usually recovery ZIP is smaller than fastboot. Onestly I pushed manually the update through OTA from stable 12.5.4.0 and everything went perfectly. Even with root and of course I have bootloader unlocked. Don't know what can go wrong if you have bootloader locked

Question Unable to update Android (NE2213 of unknown origin)

I bought a slightly used 10 Pro (NE2213) from the local ebay. I am based in Bulgaria.
Phone is in great condition and has no sign of wear and tear. HOWEVER....
1. The Camera app keeps crashing.
2. Half of my pictures show as black squares in my Gallery. I don't know if they're not being saved or the previews are glitchy.
That's a big deal to me, because I bought this phone for my wife, so she can take photos of our baby.
So I thought I'd go ahead and update the software of the phone. It has Android 11. No matter what I do, it is impossible to get the update to install. "Extraction failed. Please try again".
I tried resetting the phone to factory settings several times, I tried turning on Developer Mode to install it manually, I tried installing Oxygen Updater from the Playstore, but I was never able to get past this error.
What am I missing here and what can I do? Please help.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Did you try to do a local upgrade with the update downloaded from OxygenUpdater?

TheNewHEROBRINE said:
Did you try to do a local upgrade with the update downloaded from OxygenUpdater?
Click to expand...
Click to collapse
Yes, I downloaded the package from OxygenUpdater. Then turned on Developer mode, but the Local Upgrade button from the 3 dots on the top right was always greyed out. OxygenUpdater says I need to install pending updates first, and then use their tool. I was never able to get past the screenshot above. :\

That's a nice tip...on the oxygen updater posts, there is one to restore your phone form Android 13, use that full package to flash OOS 12 again and you're good to go.

zopostyle said:
That's a nice tip...on the oxygen updater posts, there is one to restore your phone form Android 13, use that full package to flash OOS 12 again and you're good to go.
Click to expand...
Click to collapse
Please excuse my ignorance.
How do I "use a package to flash OOS 12 again"? Keep in mind I have Android 11, not 13. and that it's my first time having to do something like this. Does my phone need to be rooted for that?
I appreciate your patience and help, this is my first time having to deal with phone mods.

He said that he has the local update option grayed out so he can't install any package manually. Maybe it's grayed out because there is already another update downloaded. You should try to disable automatic updates and then delete the downloaded update from the internal memory of the phone, it should be in a folder called .Ota. If you can't see that folder you need to enable the option to show hidden files.

My best guess is use the NE2213 Full Downgrade ZIP. It should upgrade you to Android 12 and it's their only released FULL recovery zip so, it's your best bet.
However, seeing as you are on Android 11, some people here might want a dump of some images first, hahaha. It's widely believed this phone does not ship with Android 11

Download this package
https://oxygenos.oneplus.net/2370_sign_NE2215_11_A_OTA_0130_all_bb1e47_10100001.zip
And apply it using this apk https://oxygenos.oneplus.net/OPLocalUpdate_For_Android13.apk
Source: https://oxygenupdater.com/article/346/
You don't need to do anything more, but I would recommend you to unlock your bootloader just for precaution if something goes wrong.
Remember to have a full battery before starting the process and I strongly recommend to download from your PC or from oxygen updater to make sure that the package didn't corrupted

zopostyle said:
Download this package
https://oxygenos.oneplus.net/2370_sign_NE2215_11_A_OTA_0130_all_bb1e47_10100001.zip
And apply it using this apk https://oxygenos.oneplus.net/OPLocalUpdate_For_Android13.apk
Source: https://oxygenupdater.com/article/346/
You don't need to do anything more, but I would recommend you to unlock your bootloader just for precaution if something goes wrong.
Remember to have a full battery before starting the process and I strongly recommend to download from your PC or from oxygen updater to make sure that the package didn't corrupted
Click to expand...
Click to collapse
I agree with this. I think it's the best option.

ivan_10pro said:
Please excuse my ignorance.
How do I "use a package to flash OOS 12 again"? Keep in mind I have Android 11, not 13. and that it's my first time having to do something like this. Does my phone need to be rooted for that?
I appreciate your patience and help, this is my first time having to deal with phone mods.
Click to expand...
Click to collapse
The phone released with Android 12 dude, not 11... If I remember correctly there was an Android 11 preview but it was never official so it may be a test device or ambassador device.
My first thoughts would be... Send it back... There's zero reasons why you can't as you're covered for things just like this.... If it's eBay then you should really use PayPal so you're covered.
Beyond that you can use the rollback package to roll back to the earlier versions of android 12, this will flash 2213 onto the device, just Google OnePlus community rollback and you'll find it.
Few other things, are you sure it's a 2213 or a region changed Chinese variant? Did it come in a box? Does that state 2213?
Either way this issue shouldn't be occurring, I'd be sending that back buddy.