My phone is FUBAR'D - Google Pixel 4a 5G Questions & Answers

Wrote this message to Google support. I don't suspect I'll hear anything from anybody but I'll post here for my fellow Pixel brothers and sisters that perhaps may experience something similar. I'm disappointed. I know the phone is relatively inexpensive (cheap) and you get what you pay for (?) but this points to bad hardware, simple and plain. How does my 2019 LG G7 on android 9 (!!??) outlast a 4a5g?? I expected more but, alas it is what it is. Peace out, Pixel 4a5g.
"Over my time since I've been on Google Fi I've used and bought a few devices. I started out with a Pixel 4a, then upgraded to the 4a5g and now I'm on the 6 Pro. I love Google phones and have always been a fan since days of the Nexus devices. I was disappointed when my 4a5g started bootlooping 2 months ago. It has never been unlocked or have I attempted to flash ROMs on it. It would eventually stop and boot back up, last for a week or so then bootloop again. This time around it continued for a longer period of time. When I went to try to do a factory reset it is stuck in Fastboot saying "no valid slot to boot." Based on the research on this issue I realize the phone is pretty much dead, even though I can use Google's own Flash tool to flash factory images for it. The phone is no longer under warranty and your support doesn't give any other options than paying for repair upt to $350, which is beyond the worth of the device. I am disappointed that the phone bootlooped to the point of death after only owning the device for LESS THAN 2 YEARS. (Nov 2020). My previous device, a LG G7 that I previously had on Verizon lasted longer, and my dad still uses that phone to this day. I purchased that phone in March of 2019. I know this post will only fall on deaf ears and no one can do anything about it but for the first time in a long time I'm disappointed by a Google phone."
{
"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 not reflash since those ROMs are easily available? You have access fastboot, no?

Kaynejulian said:
Why not reflash since those ROMs are easily available? You have access fastboot, no?
Click to expand...
Click to collapse
I've been flashing and re-flashing this phone for 2 days.

What's the output? What is error code? What commands are you using? What does fastboot getvar all show?

I'm using the android flash site to flash the phone with a stock image from Google. It goes through the process with no errors, then it acts like it's going to boot, bootloops twice then goes to the pictured fastboot mode showing "no valid slot to boot." Fastboot shows the build number (android 11 or 12 depending on which I've flashed) but when i try to wipe data i get /system/bin/tune2fs is missing.

I thought mine was also. I used this site to get it back to a running rom
Web installer · ProtonAOSP
Quickly and easily install ProtonAOSP on your phone in as little as 4 minutes.
protonaosp.org

Thordim said:
I thought mine was also. I used this site to get it back to a running rom
Web installer · ProtonAOSP
Quickly and easily install ProtonAOSP on your phone in as little as 4 minutes.
protonaosp.org
Click to expand...
Click to collapse
Thanks for trying, I get file format is not recognized error message. I tried manually installing the Pixel Experience ROM and even got that ROM's recovery to flash, and flashed the ROM, all went well exactly as the website said but then it said that the phone is corrupted and bootlooped. Flashed the stock 12.1 image using the Android Flash Tool, back to above error message after 2 bootloops.

Wonder if there is any way to check NAND integrity on this device. It's like you flash and reflash and somehow it loses it "bits". Which is weird. I would be temped to try to "semi-brick" it and see if a manual flash (via fastbboot) over all the individual partitions one at a time, would resolve issue, assuing NAND is still ok. That sucks man. I'm sorry.

smokejumper76 said:
Wonder if there is any way to check NAND integrity on this device. It's like you flash and reflash and somehow it loses it "bits". Which is weird. I would be temped to try to "semi-brick" it and see if a manual flash (via fastbboot) over all the individual partitions one at a time, would resolve issue, assuing NAND is still ok. That sucks man. I'm sorry.
Click to expand...
Click to collapse
What confuses me is that even when I manually flash a custom ROM or stock image it goes through the process just fine, no error messages. It boots up, does the little G circle animation and right as it's about to go to the next screen.. bam, it reboots. Does it a second time, then immediately goes to the above-mentioned screen shot. So I think somewhere the hardware or storage drive or whatever you want to call it is broken. I wonder if I triggered it when I tried to enter fastboot during one of the times I tried to factory reset it. I dunno... I'm attempted to let the battery die then recharge and try again or something.
It's ok, I'm sort of over it.. my feelings are hurt at this point. I've been Rooting and Romming since the days of Moto Droid X2, Galaxy Note 2 (before vzw locked their bootloader) and the Nexus 6, so when I got into the Pixel phones I was relieved when I didn't feel like I didn't have to do all of that just to get the phone to feeling like it's working smoothly. I have a 4a that has a broken screen, this one and a 6 Pro (factory), so I've really liked the Google Pixel devices and the software experience. So for this to start bootlooping even without me tinkering with it for over a year is just a disappointment.

If anyone can understand it, here are screenshots of the recover.log file from the recovery screen.

Tried flashing the first Android 11 OTA image from the Google Images site, A4 October 2020 as it's a unlocked Google purchased phone. I noticed it goes through the motions but says status 0 then further that system/bin/tune2fs is missing so nothing is being written. This must be happening every time I try to flash but I'm not actually seeing that nothing's happening on the Google flash website.

Have you already tried the Android Flash Tool? Given the circumstances I would recommend checking the Force flash all partitions box.

yeah, that was the first thing i did, tried 11, 12, 13 beta, 13 official... nothing. Lineage too.

Related

xt1254 hangs on bootloader/recovery

Hi all, ive been running custom roms on my phone ever since sunshine was released for it.
In the past 6 months or so, my phone has gotten horrendously bad at booting.
When i turn it on, it will hang on the bootloader warning screen for 2 to 3 minutes before showing any sign that anything is happening.
Im really at a loss, ive done everything but a complete format and sideload.
Not really sure what other information would be required.
what should i do?
also every few days i have to go into apns and click one of the verizon ones again before my data will work, but that might just be a rom issue.
jombo2323 said:
xt1254 hangs on bootloader/recovery
Hi all, ive been running custom roms on my phone ever since sunshine was released for it.
In the past 6 months or so, my phone has gotten horrendously bad at booting.
When i turn it on, it will hang on the bootloader warning screen for 2 to 3 minutes before showing any sign that anything is happening.
Im really at a loss, ive done everything but a complete format and sideload.
Not really sure what other information would be required.
what should i do?
Click to expand...
Click to collapse
At first I thought you were saying your phone was booting to the bootloader screen or even booting to TWRP recovery, which would be very strange. That's happened to people before... which means the phone is really messed up.
But reading your actual write-up, (if you wrote it correctly) instead your phone is just NORMALLY booting. It's just taking a long time. Your phone is just staying stuck on the boot image, which is not the bootloader or recovery screens. It's just an image you see before the boot animation starts until finally you see your normal Android system GUI. In your case, it's the "bootloader warning screen" which is something you should replace.
THIS is the bootloader screen:
{
"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"
}
But instead you're seeing this, right?
It's the boot image Motorola has replaced to warn you your bootloader is unlocked. Yeah, I did it on purpose! As did you. No need to see it every day. You can flash a replacement boot image very easily in TWRP or ADB. <There's several to choose from.
WHY is it hanging on the boot image? You are right that something is wrong, but I don't think your phone is very messed up -- at least it's not booting to the bootloader screen!
You've tried clearing all the caches in TWRP? You've tried dirty flashing your ROM again? Sometimes something can get slightly corrupted and re-flashing your ROM over itself can fix the issue. Clearing all the caches in TWRP and letting all the apps re-optimize can also fix some issues.
Do you have any add-on xposed modules? I would temporarily disable all exposed modules, reboot a couple of times, see what happens? You can always re-enable them later. Xposed modules can conflict with your normal ROM functions and should be used very sparingly. Some modules like Gravity Box are really another ROM and settings in Gravity Box can conflict with settings in your ROM. But to a lesser degree so can almost any other xposed module.
Have you restored your TWRP backup which you made before all this happened? You do have a good TWRP backup, right?
Last, yeah, if none of that works, factory reset and reinstall the ROM.
Are you encrypted? I've noticed that once you encrypt the storage that the phone takes forever to boot. I haven't found any way around that and someone with more knowledge of the hardware than me mentioned that it's because the drivers for HW decrypt acceleration are missing.
I will add to this as I am having the same issue and have moved to another 32GB Turbo for the time being but now I'm having Radio issues with this one.
My 64 was encrypted, running CF's 1.0.8, xposed. Doing restoring the factory image did the same thing. Only thing is now that i think about it TWRP didn't ask for my pin for encryption though like it was before so it may not be encryped. I'm going to be doing some factory images this weekend and see if i can find out the issue and if I find anything I'll post back. Only thing that sucks is I only have one good screen between the two phones lol
Ugh, sorry for the lack of response. Ive been really busy.
To answer all questions. Ive done everything but wipe some crap with fastboot commands and performing a clean flash of the rom. Im on resurrection remix right now, i think i want to change though because my battery life is kinda ****.
Also no xposed, etc, just the basic rom.
Sorry for taking so long and thanks for the responses!

Phone had issues with crashing, and now won't even launch

Maybe you guys could help me. I'm at a loss and customer support told me to turn it off and turn it back on. I bought the Razer Phone 2 on December 27th. Around mid to late February, I had an instance where the phone crashed and was black screen, but the vibration reacted to me touching/pressing the power button. Hard resetting the phone allowed it to go back to normal. It got more frequently and more annoying, and it got to the point where multiple resets wouldn't fix it. Several times I got a screen telling me it couldn't load the android system(First image). After several instances of that screen, I tried to wipe the phone and reset it to factory, and now it's just an expensive paperweight. I can press Power+Volume Up to get to android recovery, but choosing to start up does nothing, reboot to bootloader does nothing, and pretty much everything else is useless.
Like I said, I contacted customer support, and their response was to tell me to wipe the phone and try again, which does nothing. After I said it didn't work, they said that was the best they could come up with, and that I would have to send it in and pay the costs as it was out of warranty, even though it's not even 6 months old. I tried finding a fix for it on google, and saw someone posted a similar issue, but it was fixed by power+vol up and that was the end of it, so not as far as my issue is currently. I've come to you guys as a last ditch effort to see if I could fix it before having to spend even more money to this company. This is the second phone I've got from them and both have had issues. Hoping someone saves me...
{
"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"
}
Have you unlocked your bootloader? Rooted? I'm having similar issues and I'm completely stock, I have not unlocked my bootloader or rooted or anything. If my screen goes off it won't come back but I get vibration when I press power button and I have to reset with volume up and power.
Bloodeagle said:
Maybe you guys could help me. I'm at a loss and customer support told me to turn it off and turn it back on. I bought the Razer Phone 2 on December 27th. Around mid to late February, I had an instance where the phone crashed and was black screen, but the vibration reacted to me touching/pressing the power button. Hard resetting the phone allowed it to go back to normal. It got more frequently and more annoying, and it got to the point where multiple resets wouldn't fix it. Several times I got a screen telling me it couldn't load the android system(First image). After several instances of that screen, I tried to wipe the phone and reset it to factory, and now it's just an expensive paperweight. I can press Power+Volume Up to get to android recovery, but choosing to start up does nothing, reboot to bootloader does nothing, and pretty much everything else is useless. ...Hoping someone saves me...
Click to expand...
Click to collapse
My phone does this every once in a while. I believe it's something wrong with the second pie update and without having an unlocked bootloader this isn't something that a lot can be done about.
You have access to the recovery at least, and that's good if you can find someone willing to share the update payload zip then you might be able to apply the update again over ADB. Doing so might restore your phone to working-enough condition to fully flash a factory image just be sure there's nothing corrupt in the bootstack or system image. My suggestion would be to ask around and see if anyone is willing to revert to an older version of the firmware to grab the update payload(or has one archived) so that you can try this method. It might be your best shot.
If all of that doesn't pan out, then you might be SOL unless you can wipe it over ADB/Fastboot while in the recovery or bootloader. There's a slight possibility that the phone isn't properly resetting when you do it through the recovery menu but is just deleting personal data without defaulting the configs or checking for errors. There might even be a chance that you can configure it to boot from slot B through fastboot. I'm not sure how to do that one but as far as I'm aware, when you apply updates it moves the old data to slot B so it can put fresh images in slot A(someone correct me if I'm wrong).
natefck420 said:
Have you unlocked your bootloader? Rooted? I'm having similar issues and I'm completely stock, I have not unlocked my bootloader or rooted or anything. If my screen goes off it won't come back but I get vibration when I press power button and I have to reset with volume up and power.
Click to expand...
Click to collapse
Before your issue gets to the point where your phone doesn't boot correctly like OPs, you should follow the tutorial on Razer's Dev site to unlock your bootloader so if something does happen or the issue persists, you can flash the stock firmware onto your phone with minimal issue. If you end up unlocking, DO NOT relock the bootloader. Nothing bad actually happens if you do unless you've got a custom ROM or kernel installed, then you will probably brick. I wouldn't know since I'm not willing to try relocking with non-factory images...
It's just that having the bootloader unlocked is required to flash the images from Razer so if you're having the black screen bug then you really should unlock for safety. Naturally, if you're still in warranty then try to get it fixed through Razer. This is a more "If all else fails" or " Just in case" kind of a solution for people who like fixing their own stuff or are out of warranty. Also, unlocking your bootloader gives you the ability to install Arter97's kernel and TWRP which can improve your phones stability and reduce the need to restart from the screen off bug. TWRP backups are a huge bonus, too.
Razer is not suitable for mobile phones, this phone is all bug?

Pixel 4xl bricked itself

Hey all. My wifes phone decided to brick itself. Hers is/was an unlocked unit not purchased from verizon but on their network. I noticed its now locked. It randomly reset and on boot, the screen started blinking and was unresponsive. Then it rebooted again and the "try again, factory reset" note came up at the top of the screen. Try again yielded the same pattern. So, I tried full wipe, same thing, loop back to the try again screen. Then, I tried to side load the ota. All seemed ok. Installed her sim, all good. Went to settings to change to 3 button nav and boom, fail and try again screen. Was this a delay from maybe a bad sim card? Is 3 button nav an issue? Did evil verizon lock her phone? Can they do that?
So, I ordered another 4xl because she needs a solid phone to function for work. Id still like to know if I can recover the borked unit. Any help is appreciated.
You did all the correct things. Unfortunately it sounds like a hardware issue. Anytime you factory reset you have ruled out a software issue. Further, flashing a "rescue ota" via adb that resets the phone even with a locked bootloader. You've done everything you can do, except leave the red devil.
So now, I have it working, but not trusting it. I dont dare change to 3 button nav though...hahaha Still going to use the one we bought so she has a solid phone for work.
On another note. We're now stuck in the gmail recovery loop. 2 email addresses referencing eachother for recovery of passwords. Its maddening. I thought if I could get her phone to work, there would be some google magic that may kick in.
Its all evil.
sadly my 4xl has the same problem, it seems to be a serious bug from Google and needs to be fixed. Phone can't access Fastboot mode or Recovery mode, it can only stay in 9008 mode. This situation happened when I tried to update android 12 version but failed. Hope to have help from the developer, because there will be many people facing the same situation.
Hey all.
So for carbon coupe:
1. Verizon can't just lock your phone if it is unlocked, this is something that happens during the manufacturer process. So if it randomly restarted there may be another cause.
2. You wrote that when on 3 button navigation it works fine but if you switch the phone starts boot looping. This is clearly a software issue rather than a hardware issue(there is no chip responsible for the type of navigation system), so there may be a problem with the OS. This is a good thing because it means it's fixable without the need of money.
Factory reset usually fixes most problems but not all of them, as some partition aren't changed during the process, like boot or system.
So the problem is in one of those partition, just like when you have a locked phone and after reseting it it still knows it is lock.
The solution is to flash the firmware of the phone to fix it.
For sSjBlueVN197,
if you are on this mode it's called EDL mode. If you are on this mode it means fastboot and adb aren't available. On that mode you can flash firmware to the phone, even if it is locked or bricked.
This propose of this mode is to allow developers to flash firmware if when the system is damage, and some other partitions like boot and others are also damage. It's just like an emergency mode to rescue the phone.
Anyway, for both of you, here is what you need to fix your phone:
*Keep in mind this only works on windows, and I am assuming you have ADB and Fastboot command line installed, and you have some experience using the command line, and you are using a recent version of Windows10,*
1. Remove Lmobile drivers(from device manager on windows) and install the Google one's instead. If you don't know how to do it just search on google and you will find a tutorial
2. You need to download Qualcomm drivers and QPST tool. I will leave a link to a website where you can download it.
3. After Qualcomm drivers are installed, set up QPST.
3. On your phone, if you have access to adb, run without quotes "adb reboot EDL"(for carbon coupe)
If the phone can't reach adb there are other 2 methods, one using fastboot commands and other using the testing pins(requires phone disassembly)
As my phone is working and running fine android 12 I only know the adb command.
Once on EDL mode the screen is going to be completely black, and device manager will se your phone as :
QUALCOMM HS-USB QDLOADER 9008(COM "USB port number")​or something similar.
Now you can use the QPST tool to flash the firmware and boot image, or any other software that supports EDL mode.
Here is a link to a website which explains very well how to set up and use the QPST tool and where you can download all you need.
Hope this helps you!
{
"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"
}
You are going to need also these files, that are the programmer files.
PLEASE KEEP IN MIND I DIN'T TRY OUT THIS FILES, SO THEY MAY BE FOR OTHER PHONE OR MAY NOT WORK.
So please use this files with caution, I found them on a post of XDA and they are in theory from a working Google Pixel 4XL, so they should work.
Though I didn't test them so they may just not work at all.
#mcl said:
You are going to need also these files, that are the programmer files.
PLEASE KEEP IN MIND I DIN'T TRY OUT THIS FILES, SO THEY MAY BE FOR OTHER PHONE OR MAY NOT WORK.
So please use this files with caution, I found them on a post of XDA and they are in theory from a working Google Pixel 4XL, so they should work.
Though I didn't test them so they may just not work at all.
Click to expand...
Click to collapse
hi, i have pixel 4 xl firehose but its asking for 2 more files raw program and patch file...
pixel4-XL_firehose - Google Drive
drive.google.com
#mcl , can you advices me the method that can fix this problem . so xml file can not meet this point .

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.

How to downgrade s20 fe g780g

Good afternoon and first off all sorry for my bad English. I have a s20fe and after an update my camera stop working. Mostly the front camera. The main cameras sometimes are working.After some months a new update was there and ooops ,the cameras are perfectly working. But my luck was only a few hours. A new small update,stops the camera again. I m trying to make a downgrade but no luck.My phone have android 13 , binary 4 and when i download android version 12 or 11 every time failure whith odin. Please,any suggestions is accepted.Thank you all .
If the bootloader was upgraded too you're boned unless the bootloader is unlocked.
The fifth digit is the significant one. You can roll back to a equal or higher value but not lower.
Trying a factory reset after backing up all critical data is another option. It might work.
Two is the significant digit in my case...
{
"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"
}
blackhawk said:
If the bootloader was upgraded too you're boned unless the bootloader is unlocked.
The fifth digit is the significant one. You can roll back to a equal or higher value but not lower.
Trying a factory reset after backing up all critical data is another option. It might work.
Two is the significant digit in my case...
View attachment 5906829
Click to expand...
Click to collapse
My version the digit is 4.
j120975 said:
My version the digit is 4.
Click to expand...
Click to collapse
The 5th significant digit of rom you want to load has to be 4 or higher.
I avoid doing firmware upgrades and updates if the device is running fast and stable... I'm still running Pie without issues.
blackhawk said:
The 5th significant digit of rom you want to load has to be 4 or higher.
I avoid doing firmware upgrades and updates if the device is running fast and stable... I'm still running Pie without issues.
Click to expand...
Click to collapse
I m sure you have a point there. But the problem is here now ,and i dont know what to do,to make my cams working again
j120975 said:
I m sure you have a point there. But the problem is here now ,and i dont know what to do,to make my cams working again
Click to expand...
Click to collapse
Yeah I learned the hard way. Especially true with Samsung products. It can turn into a real digital blood bath.
Clear system cache and cam app data.
Try in safe mode.
Check for updates from Samsung on Playstore and the Galaxy store.
Try a hard reboot (simulates pulling the battery).
Play with it and double check all settings.
It may take a while...
If all that fails try factory reset and don't use SmartSwitch to reload.
Unfortunately you are fried.
Those who are on Android 13 5.1 April patch.
They are condemned to android 13 permanently through odin.
From April 2023 they will not be able to download medainte odin.
luck.
mezacorleehone said:
Unfortunately you are fried.
Those who are on Android 13 5.1 April patch.
They are condemned to android 13 permanently through odin.
From April 2023 they will not be able to download medainte odin.
luck.
Click to expand...
Click to collapse
If he can't roll it back he'll need to try to find a work around assuming it's not a more mundane cause. An inconvenience... might take hours, days or weeks but eventually you'll likely resolve the issue.
Do what I said in post #7 and go from there... Androids love attention.
blackhawk said:
If he can't roll it back he'll need to try to find a work around assuming it's not a more mundane cause. An inconvenience... might take hours, days or weeks but eventually you'll likely resolve the issue.
Do what I said in post #7 and go from there... Androids love attention.
Click to expand...
Click to collapse
I personally had a weird error.
After an update, the Wi-Fi failed, rather the instability of the signal.
downgrade from android 13 to 12.
Why did the error appear when I installed android 13.
My surprise was that the error continued.
My problem was fixed in the next android 13 security patch.
What do I want to get to with this story?
Why was it not solved if I downgraded the system?
this was on a G781U.
My way of interpreting, is that the files are updated or drivers.
but they cannot be modified.
a solution to your problem of being able to downgrade, I doubt it's possible, there are ways to do it but to restore imei and things like that. but not for day to day.
mezacorleehone said:
I personally had a weird error.
After an update, the Wi-Fi failed, rather the instability of the signal.
downgrade from android 13 to 12.
Why did the error appear when I installed android 13.
My surprise was that the error continued.
My problem was fixed in the next android 13 security patch.
What do I want to get to with this story?
Why was it not solved if I downgraded the system?
this was on a G781U.
My way of interpreting, is that the files are updated or drivers.
but they cannot be modified.
a solution to your problem of being able to downgrade, I doubt it's possible, there are ways to do it but to restore imei and things like that. but not for day to day.
Click to expand...
Click to collapse
User data partition wasn't cleared?
When you mess with the firmware you're playing with fire especially if the device was running well to begin with. Anything can happen...
blackhawk said:
User data partition wasn't cleared?
When you mess with the firmware you're playing with fire especially if the device was running well to begin with. Anything can happen...
Click to expand...
Click to collapse
the device booted from 0.
after odin
The wifi problem continued after the downgrade.
My way of imagining or interpreting is,
files with android 13 wifi error, remained intact after restore via odin.
It was resolved with the following update to Android 13.
There may be problems with the camera drivers.
mezacorleehone said:
the device booted from 0.
after odin
The wifi problem continued after the downgrade.
My way of imagining or interpreting is,
files with android 13 wifi error, remained intact after restore via odin.
It was resolved with the following update to Android 13.
There may be problems with the camera drivers.
Click to expand...
Click to collapse
Factory reset to set the user partition values back to their default settings. A 3rd party app or malware can also skew that data. With any major firmware upgrades it's best to do a factory reset.
Upgrades and updates are more trouble than they're worth if the device is running well, fulfilling its mission is my view on it. I use what ever comes in handy. Current load on this N10+ will be 3yo in June. That's what Androids are capable of... I put very little time into system maintenance. It's mostly all play time.

Categories

Resources