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.
Related
https://github.com/SkyEmie/huawei-honor-unlock-bootloader
Perhaps we can work with this?
borgqueenx said:
https://github.com/SkyEmie/huawei-honor-unlock-bootloader
Perhaps we can work with this?
Click to expand...
Click to collapse
Wonderful App, Unfortunately Huawei patched this vulnerability.
After 5 unsuccessful attempts, The Phone reboots itself to prevent the algorithm from working.
JazonX said:
Wonderful App, Unfortunately Huawei patched this vulnerability.
After 5 unsuccessful attempts, The Phone reboots itself to prevent the algorithm from working.
Click to expand...
Click to collapse
We dont know if this is a security fix or not. Maybe with some luck its a bug that could be circumvented somehow.
borgqueenx said:
We dont know if this is a security fix or not. Maybe with some luck its a bug that could be circumvented somehow.
Click to expand...
Click to collapse
There is a workaround for the reboots described in this pull request https://github.com/SkyEmie/huawei-honor-unlock-bootloader/pull/16
I don't know if it is merged, but the guy forked the repo and implemented it I think -> https://github.com/mschabhuettl/huawei-honor-unlock-bootloader
xchatter said:
There is a workaround for the reboots described in this pull request https://github.com/SkyEmie/huawei-honor-unlock-bootloader/pull/16
I don't know if it is merged, but the guy forked the repo and implemented it I think -> https://github.com/mschabhuettl/huawei-honor-unlock-bootloader
Click to expand...
Click to collapse
I've read through the commits, Looks like a possible solution _ But I'm not seeing any success stories yet.
Also, continuously rebooting your phone maybe over a 1000 times is not really a good idea.
Have you tried this on your device or waiting for someone else to take one for the team ?
I note that fastboot files are included in this methods. Is it even possible to get latest huawei phones to fastboot?
JazonX said:
I've read through the commits, Looks like a possible solution _ But I'm not seeing any success stories yet.
Also, continuously rebooting your phone maybe over a 1000 times is not really a good idea.
Have you tried this on your device or waiting for someone else to take one for the team ?
Click to expand...
Click to collapse
Hi there,
I don't have any Huawei device right now. Only one P20 Pro for my wife but I unlocked it with a code back then.
I had a Mate 30 Pro but sold. Waiting for some stable google services solutions and I will buy again.
borgqueenx said:
I note that fastboot files are included in this methods. Is it even possible to get latest huawei phones to fastboot?
Click to expand...
Click to collapse
Yes no problem at all.
ADB reboot bootloader works just fine, the usual white bootloader screen. No FRP lock though, which explains the "missing" switch in Developer Options.
Fastboot reboot, then reboots the phone as normal.
Didn't try any other commands.
Just waiting to get my pro plus to try this. Anyone else?
Any way to try it without erasing all the data? After hours of installing all the google apps it's not easy to just erase it.
GabiTM said:
Any way to try it without erasing all the data? After hours of installing all the google apps it's not easy to just erase it.
Click to expand...
Click to collapse
Unfortunately not. Although if all data is erased, it should have successfully completed its task and then you have a unlocked bootloader.
If no unlocked bootloader, your data should be kept on the device.
GabiTM said:
Any way to try it without erasing all the data? After hours of installing all the google apps it's not easy to just erase it.
Click to expand...
Click to collapse
Make a backup with HiSuite on PC : Which you can restore later if the operation is successful.
Your data will only be erased if the Bootloader gets unlocked. At the attempt / trying stage It won't trigger a data wipe.
If the bootloader does get unlocked, It will be a massive win which is totally worth doing the google installations again.
Maybe next time onwards you can use Titanium Backup to backup apps and data., Push the Google Apps from the system dump of P30 Pro EMUI 10 to the Mate 30 / P40 Pro devices to have Playstore certified GMS, Host level adblocking and many more life-saving solutions.
Sorry guys and gals but the script doen't work on P40 Pro.
Fastboot works and the script reboots the phone but commands like oem unlock and oem info don't work.
{
"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"
}
Any other ideas?
That is unfortunate. I dont think we can do more then. Will request a lock for this topic if no one else gives ideas this week.
Thanks for trying!
GabiTM said:
Sorry guys and gals but the script doen't work on P40 Pro.
Fastboot works and the script reboots the phone but commands like oem unlock and oem info don't work.
Any other ideas?
Click to expand...
Click to collapse
Huawei have probably taken away the unlocking option from the bootloader seeing as they don't support unlocking anymore.
There's no "FRP unlock" switch in Developer Options like on previous models (p10/20/30 etc) either which implies the same.
Shame, would have been nice to find a potential "backdoor" to unlock & root! With Magisk able to be installed, that would have solved all the Google/uncertified problems people are having.
The "Phone Finder" error message is interesting though, I assume you tried it with that disabled? I think iPhone's have a similar block... Maybe you can't unlock the handset with that turned on?
colthekid said:
Huawei have probably taken away the unlocking option from the bootloader seeing as they don't support unlocking anymore.
There's no "FRP unlock" switch in Developer Options like on previous models (p10/20/30 etc) either which implies the same.
Shame, would have been nice to find a potential "backdoor" to unlock & root! With Magisk able to be installed, that would have solved all the Google/uncertified problems people are having.
The "Phone Finder" error message is interesting though, I assume you tried it with that disabled? I think iPhone's have a similar block... Maybe you can't unlock the handset with that turned on?
Click to expand...
Click to collapse
The chance to find a security engineer/hacker that wants to dedicate time into finding a exploit and unlocking without incentive other then getting media attention, is quite low.
borgqueenx said:
The chance to find a security engineer/hacker that wants to dedicate time into finding a exploit and unlocking without incentive other then getting media attention, is quite low.
Click to expand...
Click to collapse
Can we start a gofundme or something similar, money is a good incentive.
GabiTM said:
Can we start a gofundme or something similar, money is a good incentive.
Click to expand...
Click to collapse
Nope, because this is a very well paid job.
It could start to be attractive if you also count the media attention at minimum 50k dollar.
If I was in Huawei shoes I would just unlock the bootloader again. Don't see what they gain from keeping them locked, while on the same time unlocking then might boost new device sales a bit
Gatos7 said:
If I was in Huawei shoes I would just unlock the bootloader again. Don't see what they gain from keeping them locked, while on the same time unlocking then might boost new device sales a bit
Click to expand...
Click to collapse
Just like I thought...
The ban will cost them sure a lot sales off smartphones... And also aocked bootloader ?
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
Hi i have a strange problem. I tried searching to no avail. When i turn on WiFi, eventually after some time i loose cell service completely and have an X on the bars. The moment i turn off WiFi the service comes back turn it back on gone again. If i restart the phone everything works perfect but eventually the problem comes right back.
Some facts that i have to mention.
I am rooted with Magisk.
I do have Lsposed Riru
I do have the WiFi and volte fix
Besides that im fully on a stock ROM and stock kernel. I am aware these things might be the cause but i wanted to know if anyone out there experienced such an issue. I am on the T-Mobile network in USA Device about me bow
{
"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"
}
I
Just am update. If anyone else faves this I THINK I may have fixed it , but will update if its not true. After trying literally everything from apn settings, WiFi settings , going through all my apps, even getting a new sim nothing worked. Then it hit me, this phone has 2 sim slots. I switched from sim tray 1 to sim tray 2. So far its been 3 days without any service loss. I also want to add that vowifi and volte was also cutting out randomly which I noticed after this post and when it cut out even if I still had bars calls and texts wouldn't go through, this was all related it seems because since I switched trays that too hasn't happened. I'll keep you all posted if this changes, but if anyone else faces this problem I would definitely recommend trying to switch sim trays slots.
Just another follow-up, if anyone is following lol. My issue is not fixed as I thought. While changing the sim tray seemed to have momentarily fixed the problem it sadly came back. Although, im not so much as loosing signal as I originally was, but basically both Volte OR VOwifi vanish, and when they do I cant make or receive calls, even with full bars. Data works fine. If I reboot the phone it works again. I found most times if I put it in airplane mode, reconnect wifi, then take off airplane mode it also fixes the issue temporarily fixxes like restarting but this issue ALWAYS returns, and returns randomly. I cant find any trigger or pattern.
my friend, I am facing the same problem and it is on android 12, do you find any solution?
Arkopelos said:
my friend, I am facing the same problem and it is on android 12, do you find any solution?
Click to expand...
Click to collapse
Sadly im still dealing with it. The only thing that helped was switching sim slot, however after so.e time the problem still returned.
my friend, I am facing the same problem and it is on android 12, do you find any solution?
MajicDroidPirate said:
Sadly im still dealing with it. The only thing that helped was switching sim slot, however after so.e time the problem still returned.
Click to expand...
Click to collapse
Have you tried the existing custom roms, could they solve our problem?
Arkopelos said:
my friend, I am facing the same problem and it is on android 12, do you find any solution?
Have you tried the existing custom roms, could they solve our problem?
Click to expand...
Click to collapse
I havent, I am considering it, its just allot of work to backup and restore everything , there is a reason I chose a phone with enormous memory I have unbelievably allot of stuff on it lol. If it was something I knew for sure would fix it I would he more inclined to try , but maybe one day I will. If you happen to try any and it solves it I would really appreciate you letting me know.
This is not related but I will ask. Did you downgrade your phone to unlock bootloader?
osomakohj said:
This is not related but I will ask. Did you downgrade your phone to unlock bootloader?
Click to expand...
Click to collapse
Never updated it to begin with lol I stayed on android 11
Which version of a11 your that can be unlock bootloader?
Scroll up lol all my info is posted above
MajicDroidPirate said:
Hi i have a strange problem. I tried searching to no avail. When i turn on WiFi, eventually after some time i loose cell service completely and have an X on the bars. The moment i turn off WiFi the service comes back turn it back on gone again. If i restart the phone everything works perfect but eventually the problem comes right back.
Some facts that i have to mention.
I am rooted with Magisk.
I do have Lsposed Riru
I do have the WiFi and volte fix
Besides that im fully on a stock ROM and stock kernel. I am aware these things might be the cause but i wanted to know if anyone out there experienced such an issue. I am on the T-Mobile network in USA Device about me bowView attachment 5637931View attachment 5637933
I
Click to expand...
Click to collapse
Your problem might related with persist partition
osomakohj said:
Your problem might related with persist partition
Click to expand...
Click to collapse
How do I do I fix it?
MajicDroidPirate said:
How do I do I fix it?
Click to expand...
Click to collapse
Try to flash this. https://forum.xda-developers.com/t/request-persist-img-for-the-rog-phone-3-android-11.4413885/ via TWRP or fastboot. Most of wifi or carrier problem is because persist partition being corrupt. feedback if anything good happen
osomakohj said:
Try to flash this. https://forum.xda-developers.com/t/request-persist-img-for-the-rog-phone-3-android-11.4413885/ via TWRP or fastboot. Most of wifi or carrier problem is because persist partition being corrupt. feedback if anything good happen
Click to expand...
Click to collapse
which partition do i select to flash it to?
Boot
DTBO
Recovery
VBMEta
VBMeta System
Super
MajicDroidPirate said:
which partition do i select to flash it to?
Boot
DTBO
Recovery
VBMEta
VBMeta System
Super
Click to expand...
Click to collapse
Fastboot flash persist persist.img
osomakohj said:
Fastboot flash persist persist.img
Click to expand...
Click to collapse
First download the file persist.rar from thread https://forum.xda-developers.com/t/request-persist-img-for-the-rog-phone-3-android-11.4413885/ then extract it to folder with adb and fastboot driver. then flash the persist partition with the code above
osomakohj said:
First download the file persist.rar from thread https://forum.xda-developers.com/t/request-persist-img-for-the-rog-phone-3-android-11.4413885/ then extract it to folder with adb and fastboot driver. then flash the persist partition with the code above
Click to expand...
Click to collapse
Okay, I flashed it that took effort to find a working cable lol
I will update you and let you know if the problem comes back! thanks for your help!!
Umm this just made a brand new problem thst I never had. My fingerprint reader stopped working and now the fingerprint is visible in the screen no! Stop
Screenshot
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.
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.