Hello. I've come across the serious problem with my OnePlus 9 Pro 12GB LE2125. It constantly freezes and restart itself after OOS12 update. It's absolutely unusable in OOS12 - literary works for few minutes then freeze with restart. It happens even at the stage of initial setup after factory reset. The only way to make the phone working again is rolling back to OOS 11 using factory tool - MSM Download Tool. Nothing else helps. Tried factory reset it before updates and after - the same issue. Never saw something like that. Not sure wether it's software problem at this stage. So phone works with no issues in OOS 11 only. Please help!
If even after flashing with MSM you're encountering the same problem, it may as well be sone kind if hardware problem, triggered by some specific driver in OOS12.
You got a warranty on your phone?
ekin_strops said:
If even after flashing with MSM you're encountering the same problem, it may as well be sone kind if hardware problem, triggered by some specific driver in OOS12.
You got a warranty on your phone?
Click to expand...
Click to collapse
I wouldn't ask the question if I had a warranty .
WarVic[NZ] said:
I wouldn't ask the question if I had a warranty .
Click to expand...
Click to collapse
And you got the answer technically speaking.
If I've understood correctly, now warranty on phone, caused by modding. Everything works on os11 but not os12.
What is the model and original country your phone is from?
From the feel of the thread, you've rolled back to complete original phone stock, undone all your mods, model number changes, flashed original firmware? effectively making the phone think it's back to factory settings?
Could there be something you've missed ? Is there there a guide on this forum / OnePlus community forum you can check to see if there are any additional steps?
The goal being take it 100% back to factory ( if this is even possible ) - can someone confirm if this is actually possible? I ask in that if it is sent to OnePlus, you'll have a way to pass all their warranty checks
可以尝试重新安装当前版本的oos12
Or may be a virus.., not shure..
In my case a female friend send me a link to a stupid video with whatsapp. I open the video & after i close it the phone shuts off. Just like yourse.
What i did:
1_Factory reset. No good.
2_Reinstall the OOS rom. No good.
3_Go back to OB 1. (I was on OOS OB 3 or 4) . No good.
4_MSM tool made my phone functional. After i did all the updates on OOS Stable (to rool out all the possible things i give up OB) & phone works well.
European phone model & living in Europa. Now i use ColorOS 12.1 C.61
AndyC76 said:
If I've understood correctly, now warranty on phone, caused by modding. Everything works on os11 but not os12.
What is the model and original country your phone is from?
From the feel of the thread, you've rolled back to complete original phone stock, undone all your mods, model number changes, flashed original firmware? effectively making the phone think it's back to factory settings?
Could there be something you've missed ? Is there there a guide on this forum / OnePlus community forum you can check to see if there are any additional steps?
The goal being take it 100% back to factory ( if this is even possible ) - can someone confirm if this is actually possible? I ask in that if it is sent to OnePlus, you'll have a way to pass all their warranty checks
Click to expand...
Click to collapse
No modding of any kind was ever made. It's US model LE2125. Perfectly works in Android 11 with all updates. Once the phone is updated to Android 12 it becomes unusable - freezes and restarts inself all the time, even at the stages of initial setup. The only thing helps is rolling back to Android 11 via MSM Download factory utility. Factory resets before and after update don't help. I live in New Zealand, bought the phone on eBay. I can't send it to the USA official Oneplus service for repair for obvious reasons. Pretty sure that the phone would passsed all checks and would be replaced by warranty but.... I missed nothing. Something is telling me that it's hardware related issue with is triggered by Android 12.
null0seven said:
Or may be a virus.., not shure..
In my case a female friend send me a link to a stupid video with whatsapp. I open the video & after i close it the phone shuts off. Just like yourse.
What i did:
1_Factory reset. No good.
2_Reinstall the OOS rom. No good.
3_Go back to OB 1. (I was on OOS OB 3 or 4) . No good.
4_MSM tool made my phone functional. After i did all the updates on OOS Stable (to rool out all the possible things i give up OB) & phone works well.
European phone model & living in Europa. Now i use ColorOS 12.1 C.61
Click to expand...
Click to collapse
Apart from changing OS from Oxygen to ColorOS, I tried the steps you did. Didn't help either. Againg, suspect hardware issue - some mainboard component or device is malfunctioning in Android 12.
zhijiaqu said:
可以尝试重新安装当前版本的oos12
Click to expand...
Click to collapse
I did it. Still the same issue.
WarVic[NZ] said:
No modding of any kind was ever made. It's US model LE2125. Perfectly works in Android 11 with all updates. Once the phone is updated to Android 12 it becomes unusable - freezes and restarts inself all the time, even at the stages of initial setup. The only thing helps is rolling back to Android 11 via MSM Download factory utility. Factory resets before and after update don't help. I live in New Zealand, bought the phone on eBay. I can't send it to the USA official Oneplus service for repair for obvious reasons. Pretty sure that the phone would passsed all checks and would be replaced by warranty but.... I missed nothing. Something is telling me that it's hardware related issue with is triggered by Android 12.
Click to expand...
Click to collapse
Worth logging on the official OnePlus community forum, you'll need to to a steer from the others on this thread about MSM. Perhaps leave it out for the first thread, but follow the advice of the majority.
I logged that my phone since ungrading to A12, no longer auto powers on ( scheduled ) or sounds alarm when switched off. They'll ask you to submit logs. They've confirmed it was a bug and will be addressed.
Related
Hello,
i have the same issue as described in the thread below and shown in this video ==> https://vid.me/NGc5
== > http://www.asus.com/zentalk/forum.php?mod=viewthread&tid=41205&extra=page=1&page=1
i have been suffering from same issue since the .90 update, i tried flashing the 1.1GB file using adb which didn't solve the issue along with the yesterday update
anyone having the same problem?
i want to flash the older .63 version, but using adb it says that it can't flash older version than the current version , anyone can help with that ?
@Asus_USA
any info please
I downgraded the rom to a version from July, yet the same issue persist
Seems like a member mentioned somewhere else that the. 90 update might have broken some hardware using code that is not reversible
Waiting for any feedback from Asus
Sent from my GT-N7000 using Tapatalk
That's actually a screen or onboard video issue.... I see this on laptops all the time
Frankenberrie said:
That's actually a screen or onboard video issue.... I see this on laptops all the time
Click to expand...
Click to collapse
the weird thing that it only happened after the .90 update and several users are reporting it
And some software works fine, like whatsapp where the screen is normal while inside it
Sent from my GT-N7000 using Tapatalk
more users are reporting the same issue on the zentalk forum, good luck all avoiding this
no one else here on the forum suffering from the same issue ? any ideas for troubleshooting or solving ?
@ASUS_Khang
can you please confirm that this is a software issue that will be solved through an update and not a hardware failure ?
AhmadOkda said:
no one else here on the forum suffering from the same issue ? any ideas for troubleshooting or solving ?
Click to expand...
Click to collapse
I am also having this SAME issue ! I have unlocked my bootloader, root access, and flashed the 2.40.97 update again, I tried downgrading, it won't let me install and lower update over an higher one. and I can't get twrp recrovery to stay after the flash, it always goes back to the stock recovery. Also I know whats causing the problem. it's the Auss / powered by intel animated screen , First you have the Asus splash screen, Then the Animated Asus / Intel animation Then the boot animation screen. after unocking my bootloader, and changing the boot animation. I can tell you for sure, the Asus / Intel animation that is causing the issue !. I don't know where this animation is stored on the phone, if anyone knows. maybe we can restore of get rid of it. Anyway my phone is pretty much useless right now, can't use the keypad on the call screen, and can't even see the bottom half of the phone, IT's NOT a hardware problem. like some people have said. it's that dam Asus / Intel animation at starup.
I tried downgrading (using fastboot and abd) to every available firmware and nothing solved this problem
IMHO I think that the 90 upgrade triggered a bug while flashing boot partition
Sent from my GT-N7000 using Tapatalk
UPDATE.. I was able to install cm-12.1-20151011-UNOFFICIAL-Z00A.zip 2015-10-11 01:29 Using Windroid UIniversal Android toolkit. and it worked. and TWRP also the recovery.
Unlocked bootloader, rooted phone, installwd TWRP. Flashed boot, droidboot, with WW. 2.12.40.09 Z00A Then installed cm-12.1-20151011-UNOFFICIAL-Z00A.zip 2015-10-11 01:29 . The screen problem IS still there ! \ Anyone else have any ideas ? ~ Travis
My phone (ZE551ML) developed the same issue. When flashing back to stock didn't work, I sent it in for an warranty RMA. A part was replaced and the phone sent immediately back. Not a word to me about the unlocked bootloader. Just make sure if you send it in, that you state you did flash attempt flashing to stock, and make sure the phone is as close to stock as you can get. Factory reset the phone and go.
I tried last week 3 times I got an RMA & then an advanced RMA and i'm getting the run around from them. they even had the hold of 344.00 on my checkings account to the advanced RMA and then THEY canceled the RMA and everytime I talked to them 3 different customer support people then said " sorry we're updating our systems call back tomorrow. " I got told that 3 times and I've called 4 times. the phone is pretty much useless at the moment.
If they send the phone back to you, the part that was replaced on mine is "90AZ00A1-M02610". Dunno if you can get that part yourself and have it repaired by a third party, but other than that I wouldn't know what to do in your situation.
ArmchairWizard said:
If they send the phone back to you, the part that was replaced on mine is "90AZ00A1-M02610". Dunno if you can get that part yourself and have it repaired by a third party, but other than that I wouldn't know what to do in your situation.
Click to expand...
Click to collapse
...This is the Hardware model# of the whole device, not just a part inside , buy a new phone and you have this yourself !
At least for those in Canada, here a short review for my "advanced replacement" experience:
I used the Chat on their website to get a RMA#, then got a confirmation email with a sort of howto. They mentioned to use Fedex or UPS to send the defective device in and noted not to long to wait to do this otherwise the hold on my creditcard... you know! So i sent the package 3 days later with UPS, cost me a bit over CA$60 with insurance and tracking.
Just the other day i got email from Purolator (a Canada only parcel service) to print a return sticker. No one from ASUS mentioned this to me - $60 wasted
The replacement phone came also with Purolator, ASUS emailed me a tracking# but NOT wich carrier they used. Cost me a few hours and a couple phone calls to find out and re-route the package to my workplace.
ASUS did not use a original case, just a folded carton as they stated the replacement would be a new device. In case i decide to sell the phone i don't have original carton
Start to install all my usual App's etc. found that the phone does not receive any GPS signals, so it seems i changed a not usable screen into a not working GPS
For me, this was my last ASUS for a very long time!
Finally got my Advanced RMA going. can't wait to get a working phone, as soon as I do. Going root & unlock bootloader and install CM 12.1 I'm DONE with ASUS's bloatware ! ~ T
I am having the same problem. I have gotten my screen to work, but it still glitches. Is the only solution to send it in?
jeisenhart34 said:
I am having the same problem. I have gotten my screen to work, but it still glitches. Is the only solution to send it in?
Click to expand...
Click to collapse
I think so, I tried to fix it, flash with 2.20.40.97 Four times now, the problem is still there, rooted, unlocked bootloader, and installed CM 12.1 thinking it would get rid of the problem, it didn't. I think the problem is in the boot partition now. I also flashed the splash screen, and the boot animation. the problem is still there, EVEN after returning this phone back to stock to RMA it. the problem is still there.
Rattraps123 said:
I think so, I tried to fix it, flash with 2.20.40.97 Four times now, the problem is still there, rooted, unlocked bootloader, and installed CM 12.1 thinking it would get rid of the problem, it didn't. I think the problem is in the boot partition now. I also flashed the splash screen, and the boot animation. the problem is still there, EVEN after returning this phone back to stock to RMA it. the problem is still there.
Click to expand...
Click to collapse
I contacted Asus and I have to send my phone in. If you haven't dropped your phone, Asus will overnight you a new one for $25. I dropped my phone so they will repair it free of charge if the damage from the drop isn't what caused the issue. Otherwise I'm going to have to pay.
I request all to first please understand the problem and give me suggestions as this gets slightly bonkers.
Thanks in advance.
So I had my OnePlus3 A3003 repaired for water Damage from a professional non OnePlus service called Yaantra. They basically replaced the Mother Board is what they say.
I have no reason to doubt, the Phone works flawlessly, everything is working nicely, from the camera to the battery performance and charging and SOT, the performance is as expected.
Only it runs on Oxygen OS 3.1.2.
Now I first got an OTA update notification for 4.5.1 and I immediately started downloading and attempted install. It went through the whole cycle of installing smoothly and after the first reboot, it splashed a linux Penguin Logo and then turned off, never turned back on. I manually pressed the power button after a long time but it again showed the Penguin for a few seconds and powered off. I figured that the phone is bricked. (this time my boot loader was Locked)
I had to follow the 2nd Method of the Mega Unbrick guide and got my phone up and running back on 3.1.2
I still get the OTA update but this time i thought I'll download the latest stable build of 5.0.1 and install it via ADB sideload. with the appropriate recovery
The phone got bricked again.
Then I thought of Installing regular TWRP after unlocking bootloader and flashed 5.0.1, No luck. had to unbrick it again.
Then I tried bluspark.
Then I flashed Experience OS with the latest firmware. It went through the entire cycle and installed but this time after it turned off and on again I was greeted to a new error.
it was in red saying "Battery does not match" in English and then in some Asian language. I was able to unbrick from that state as well.
After that I have tried Lineage OS but with same result. I get "Battery does not match"
Then I unbricked the device and i tried #*808# and checked Charger option. it says "itech_3000mah" that doesn't sound original, is it?
Basically no matter what I flash my phone gets bricked.
With Custom ROMs I get the "Battery does not match error"
With Official ROM I get the penguin Logo.
I've tried all sorts of Combination of Recovery and ROMs to no luck.
So far the only thing I haven't tried is flashing another Kernal.
Have to come back to 3.1.2 after unbricking which works flawlessly every time with no problems AT ALL. I wish to upgrade to the latest Official build of OOS (but i am ok with unofficial as well)
Alright, this is a new one.
Have you checked your system information with the app "AIDA64"? Download that app, and post a screenshot of what's under the System tab.
thes3usa said:
Alright, this is a new one.
Have you checked your system information with the app "AIDA64"? Download that app, and post a screenshot of what's under the System tab.
Click to expand...
Click to collapse
Thanks for the eyeball
AbhiM7 said:
Thanks for the eyeball
Click to expand...
Click to collapse
Okay, although AIDA64 doesn't indicate that your Motherboard is a Chinese mockup Mobo, I still suspect that the "Penguin" logo is some kind of third-party under the hood software.
Have you tried the unbrick tool which includes 5.x.x?
thes3usa said:
Okay, although AIDA64 doesn't indicate that your Motherboard is a Chinese mockup Mobo, I still suspect that the "Penguin" logo is some kind of third-party under the hood software.
Have you tried the unbrick tool which includes 5.x.x?
Click to expand...
Click to collapse
Oh I thought there was only the 3.1.2 available in the unbrick tool.
I would appreciate a link for the 5.x.x unbricking tool.
Which should hopefully include all he required firmware and recovery stuff.
What are other ways I can know if my Mobo is a Chinese mock-up?
AbhiM7 said:
Oh I thought there was only the 3.1.2 available in the unbrick tool.
I would appreciate a link for the 5.x.x unbricking tool.
Which should hopefully include all he required firmware and recovery stuff.
What are other ways I can know if my Mobo is a Chinese mock-up?
Click to expand...
Click to collapse
Hi firstly, you shouldnt have trusted your OnePlus3 with 3rd party service like Yaantra. After service they will deny any changes to your hardware and ask stupid questions "isn't your phone receiving call when we gave it back?"
After seeing your posts, it seems that they didn't flash the device properly. I seriously doubt your battery has been Jacked and replaced with some 3rd party mockup.
A simple search in forums can lead you to 5.x.x unbricking tool.
And your final question. If your phone doesn't bootup even after this, most probably you're dealing with some kind of mockup in the chipset.
Did you solve this issue? If so post how here so that others can use it later.
Thanks
SivaMaxwell said:
Hi firstly, you shouldnt have trusted your OnePlus3 with 3rd party service like Yaantra. After service they will deny any changes to your hardware and ask stupid questions "isn't your phone receiving call when we gave it back?"
After seeing your posts, it seems that they didn't flash the device properly. I seriously doubt your battery has been Jacked and replaced with some 3rd party mockup.
A simple search in forums can lead you to 5.x.x unbricking tool.
And your final question. If your phone doesn't bootup even after this, most probably you're dealing with some kind of mockup in the chipset.
Did you solve this issue? If so post how here so that others can use it later.
Thanks
Click to expand...
Click to collapse
I am downloading this msm recovery
https://forum.xda-developers.com/on...k-phone-msmdownloadtool-v3-0-6-t3575801/page2
and try for now.
I'll post my experience soon.
An official technician from OnePlus told me that fake batteries don't work well / won't find with OnePlus at all so there is 99% chance that it's not a mock-up.
thes3usa said:
Okay, although AIDA64 doesn't indicate that your Motherboard is a Chinese mockup Mobo, I still suspect that the "Penguin" logo is some kind of third-party under the hood software.
Have you tried the unbrick tool which includes 5.x.x?
Click to expand...
Click to collapse
The penguin is the old school linux kernel panic screen. It used to come on when kernel panic prevented the device from booting.
What I am thinking is that is not the right board for that device, which explains the battery error. The custom rom battery error could be gotten around I am sure. Just so it boots.
zelendel said:
The penguin is the old school linux kernel panic screen. It used to come on when kernel panic prevented the device from booting.
What I am thinking is that is not the right board for that device, which explains the battery error. The custom rom battery error could be gotten around I am sure. Just so it boots.
Click to expand...
Click to collapse
I see, do you know how can I get around the battery error?
And should I flash a new kernal to get around the Linux penguin warning?
What are my options other than the mega unbricking with a newer version of OOS
AbhiM7 said:
I see, do you know how can I get around the battery error?
And should I flash a new kernal to get around the Linux penguin warning?
What are my options other than the mega unbricking with a newer version of OOS
Click to expand...
Click to collapse
Sure. You will have to hook up the device to the pc while it is trying to boot and grabbing a logcat. This will tell you exactly what is failing. The build a rom that goes around the issue.
To be honest. I don't know what will work for sure but the logcat will tell you just what you need to know.
Piece of advice. If you are gonna do repairs like this. Do them yourself. Even if you fail you will be sure of the parts at least which you can't be with amature repair techs. Too many use knock off parts.
zelendel said:
Sure. You will have to hook up the device to the pc while it is trying to boot and grabbing a logcat. This will tell you exactly what is failing. The build a rom that goes around the issue.
To be honest. I don't know what will work for sure but the logcat will tell you just what you need to know.
Piece of advice. If you are gonna do repairs like this. Do them yourself. Even if you fail you will be sure of the parts at least which you can't be with amature repair techs. Too many use knock off parts.
Click to expand...
Click to collapse
Am not that much of an expert. I don't know about using logcat but I just read a little about it and am going to try.
I'll post my experience soon.
Should I also take the phone to an official OnePlus technician and ask them to check if the chipset/battery is a mock up, they should be able to tell right?
AbhiM7 said:
Am not that much of an expert. I don't know about using logcat but I just read a little about it and am going to try.
I'll post my experience soon.
Should I also take the phone to an official OnePlus technician and ask them to check if the chipset/battery is a mock up, they should be able to tell right?
Click to expand...
Click to collapse
That depends on how good they are but to be honest if it is a really good fake then it may fool even the best. But it cant hurt.
Actually I got stuck in the same situation. I also tried different ROMs but with custom ones I get the Replace Battery error and with official Roms I get the penguin. Is there any way to get rid of the Battery error by modifying the kernel or something?
You've a motherboard of OP3T not OP3
Try oneplus 3t full ota
Cheers
Hi guys,
There is a system update to Android 11, anyone tried it? Is it worth to update? And it will be reset the phone or migrate the data?
Bye,
Gábor Auth
auth.gabor said:
Hi guys,
There is a system update to Android 11, anyone tried it? Is it worth to update? And it will be reset the phone or migrate the data?
Bye,
Gábor Auth
Click to expand...
Click to collapse
No issues for me so far.
Seems faster to me than Android 10 and I'm liking it in terms of UI changes
I didn't need to reset.
tech_infinity said:
No issues for me so far.
Seems faster to me than Android 10 and I'm liking it in terms of UI changes
I didn't need to reset.
Click to expand...
Click to collapse
My previous Nokia (7 plus) was updated with factory reset... so now I ask before update it...
auth.gabor said:
My previous Nokia (7 plus) was updated with factory reset... so now I ask before update it...
Click to expand...
Click to collapse
Oh that's weird. That shouldn't happen, Nokia probably messed up.
Hi Nokia 8.1 users.
Did you also lost fast charging after update to A11? MY phone i charging very slow now and drain very fast
Dear all.
Just bought a used Nokia 8.1.
When I started it up, I did reset it to factory then attached it to the wifi (no sim yet) it updated to 11 (was still on 9). TBH I pushed yet without even realizing straight away.
There is no fingerprint option anywhere
At first I freaked out that the phone is a dud but I've seen multiple forums everywhere mentioning this problem but no solution works (multiple restart including safe mode, with or without screen lock setup, complete factory reset etc). The most obvious one is this one:https://community.phones.nokia.com/discussion/59389/fingerprint-option-missing
Should I give up and try to return the phone? (HArd - I'll probably have to go through paypal process) ?
Is it worth trying to install a custom rom? Could I downgrade to 10 or even 9?
Is there a command line query or even a dial code I could use to know whether it is a hardware issue or a firmware issue? If the former, I should definitively return it. IF the latter - then it would be unethical to actually return it
THX a lot
You guys know how to downgrade nokia 8.1 from android 11 to 9? Im having a lot of issues in android 11. thanks in advance
Hello
Before few days ago, i received official ota update to android 11 of my motorola g5g plus.
I was very happy, that finally the android 11 is here and immediately updated my device(big big mistake)
After the update process, my phone start to be more and more laggy.I use it only at 90hz refresh rate and sometimes when i use it is goes on frames, which is madness..
I am really unhappy about that..I don't want to factory reset my phone.
Any possible way to resolve this lag issue or return easy to android 10 and never update again?
I do not play games or other heavy stuffs..
just ebay calls browsing nothing so heavy...
ideas guys?
You could use the Moto Flash Tool to flash the latest version of 10 - note that you'll (very probably) have to do a data wipe when asked to avoid problems afterwards.
To be sure, I'd check with @vache as to whether a downgrade is possible, but I don't see why not.
giociampa said:
You could use the Moto Flash Tool to flash the latest version of 10 - note that you'll (very probably) have to do a data wipe when asked to avoid problems afterwards.
To be sure, I'd check with @vache as to whether a downgrade is possible, but I don't see why not.
Click to expand...
Click to collapse
Thanks.I am new in the motorola world( untill now only xiaomi, and downgrade there was not a good idea).Maybe will try the factory reset, if work will stay with android 11, but really hate to do factory reset...
galev_90 said:
Thanks.I am new in the motorola world( untill now only xiaomi, and downgrade there was not a good idea).Maybe will try the factory reset, if work will stay with android 11, but really hate to do factory reset...
Click to expand...
Click to collapse
Check in settings for blur, and turn it off and see if that helps. Sorry, I don't use stock so I'm not sure exactly where it is. Developer settings maybe, or display
Beetle84 said:
Check in settings for blur, and turn it off and see if that helps. Sorry, I don't use stock so I'm not sure exactly where it is. Developer settings maybe, or display
Click to expand...
Click to collapse
Thank you.
This method work at the moment.In the developer settings it is located..Hope with some next build to be fixed the things and the blur work.
Sad news again.Phone become laggy again even on only 90hz refresh rate with turned off blur.Yesterday the phone work fine, today i woke up and surprise lagging on normal stuffs like scroling across the screen or open menu app and etc.I am almost sure that it run on less than 60hz.Absolutely dissapointing....
Thank you motorola.Last phone from this brand...
Hello community,
I have a Oneplus 8 pro laying around with unlocked bootloader, Magisk, (possibly TWRP), and a firmware which was one of the first in around may 2020.
The issue is, I want to use this phone now, but I cannot update it throught the full package of OxygenOS updater. It gives "update failed" at the 0% mark. It seems I cannot update through the conventional way. After some thinking, it might be unsuccessful as I am not even sure what firmware it runs.
The next step I wanted to take was go back to stock through the TWRP backup that was made in june 2020 (I'm not sure if it even has this backup), yet I now read it is unrecommended to use TWRP. I am not even sure if TWRP was working at that time (where would the backup be located?).
And finally I read OxygenOS 12 might ruin the phone if things are not done right due to firmware mix-up in case of the memory.
What now? Can anyone help me with some steps and advice to get the phone to at least the latest software, and preferably working with Magisk (included call recorder)?
Thanks in advance.
If your OS is fast, stable and fulfilling its mission let it be!!! The age is irrelevant if Android 9 or higher.
Don't fix it if it's not broken... if you value your time and device functionality.
blackhawk said:
If your OS is fast, stable and fulfilling its mission let it be!!! The age is irrelevant if Android 9 or higher.
Don't fix it if it's not broken... if you value your time and device functionality.
Click to expand...
Click to collapse
All works like a charm currently, except that VoWIFI tends to fail and not reconnect. Any ideas on that?
And what about security patches?
Thanks
Unfortunateburden said:
All works like a charm currently, except that VoWIFI tends to fail and not reconnect. Any ideas on that?
And what about security patches?
Thanks
Click to expand...
Click to collapse
Let me put it this way, this heavily used stock N10+ hasn't been updated in over 3 years, still running on Pie.
Current load is over 2.5 yo, still fast and stable with minimal maintenance.
Security simply isn't a issue. Nothing's got through with only some simple protocols being used to secure it. One is wifi, disabled, I never use it. This what Android is capable of...
blackhawk said:
Let me put it this way, this heavily used stock N10+ hasn't been updated in over 3 years, still running on Pie.
Current load is over 2.5 yo, still fast and stable with minimal maintenance.
Security simply isn't a issue. Nothing's got through with only some simple protocols being used to secure it. One is wifi, disabled, I never use it. This what Android is capable of...
Click to expand...
Click to collapse
Sounds good.
What if someone really requires to have Wifi working because they have zero reception inside?
Unfortunateburden said:
Sounds good.
What if someone really requires to have Wifi working because they have zero reception inside?
Click to expand...
Click to collapse
You'll have to work that out. For me wifi is a hugh security risk. Since I have a grandfathered unlimited data plan wifi is irrelevant.
You could use a signal booster...
blackhawk said:
You could use a signal booster...
Click to expand...
Click to collapse
Not legal in every country sadly.
Back to my first question, do you have any steps to get back to stock if I ever wanted to?
You could use the MSM tool and factory reset it back to OOS10 and from there on update it OTA.
Deavy said:
You could use the MSM tool and factory reset it back to OOS10 and from there on update it OTA.
Click to expand...
Click to collapse
Thanks alot!