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!
Related
Got to work this morning to find out I had no mobile data left (attached image). I thought, how strange, yesterday I'd had about ~1GB usage out of my 4GB available, I of course immediately when and looked to see what had used it all and Android OS was at the top with 2.13GB (WTF?).
This also isn't the first time this has happened, I had the same last month. Can someone please explain what is going on because I know for damn sure I've not used all that, I only browsed a few web pages this morning.
Sent from my Pixel XL using Tapatalk
Stop automatic backup
thenessus said:
Stop automatic backup
Click to expand...
Click to collapse
I want my settings etc backed-up though, is there not a setting to force it to WiFi only?
Sent from my Pixel XL using Tapatalk
pairedprototype said:
I want my settings etc backed-up though, is there not a setting to force it to WiFi only?
Click to expand...
Click to collapse
My bet is your phone is not up to date and you are rooted or modded. It keeps trying to download the update. We have seen this quite a few times even with automatic system updates turned off.
Use Data Saver in settings, works a treat
TonikJDK said:
My bet is your phone is not up to date and you are rooted or modded. It keeps trying to download the update. We have seen this quite a few times even with automatic system updates turned off.
Click to expand...
Click to collapse
I agree, even the item at the top of the list is the same as when my phone does this. I was able to use FlashFire to more easily update using the OTA this month.
Just switch to the unlimited data plan..problem solved
TonikJDK said:
My bet is your phone is not up to date and you are rooted or modded. It keeps trying to download the update. We have seen this quite a few times even with automatic system updates turned off.
Click to expand...
Click to collapse
alluringreality said:
I agree, even the item at the top of the list is the same as when my phone does this. I was able to use FlashFire to more easily update using the OTA this month.
Click to expand...
Click to collapse
You are indeed correct, I am due an update, however, I'm not rooted currently although, my bootloader is unlocked as I've been assisting with getting Magisk working on stock for Pixel devices.
And what kind of idiot developer/team thought downloading OS updates over mobile data without question was okay!? I've now got to go for 2 weeks without, I'm royally p*ssed about it. Guess I'd better flash the new update then while I have a (non-cellular) internet connection.
I remember when Google targeted power users with Nexus devices, I guess this is not entirely true for Pixel devices. Big boys like to do what they want, even if that means staying on a particular version of Android because we might be testing things... I'd rather not have OS updates forced down my throat, it's the same thing that bugs me with Windows 10.
lucky_strike33 said:
Just switch to the unlimited data plan..problem solved
Click to expand...
Click to collapse
If you're willing to pay the extra, sure thing!
You can just install the factory image on your computer and then remove the w in flash all bat file by using a text editor so that way it won't delete everything. You won't need to use any data
lucky_strike33 said:
You can just install the factory image on your computer and then remove the w in flash all bat file by using a text editor so that way it won't delete everything. You won't need to use any data
Click to expand...
Click to collapse
That's what I usually do! Just not had the time to do it recently.
this is caused by update downloading and failing over and over. I went into the dev options and turned off the auto update but it did not work. I had to update the phone manually and now its fine. I think after rooting the phone and going back to stock rom this happens.
IDK man, I was rooted and was pulling like 10gb+. Flashed stock via adb and I think it's still doing it. Project fi.
This is happening to me as well on project fi. A was rooted with beans rom and burning through 7 plus gb a month. Returned to stock completely except bootloader still unlocked. Can't install the new updates and burns through data trying over and over again. I'm not sure how to proceed other then switch to unlimited data plan on T-Mobile.
FrostyOrDie said:
This is happening to me as well on project fi. A was rooted with beans rom and burning through 7 plus gb a month. Returned to stock completely except bootloader still unlocked. Can't install the new updates and burns through data trying over and over again. I'm not sure how to proceed other then switch to unlimited data plan on T-Mobile.
Click to expand...
Click to collapse
When you returned to stock did you get to the latest version?
TonikJDK said:
When you returned to stock did you get to the latest version?
Click to expand...
Click to collapse
No. This all happened since returning to stock. Today I sideloaded the August update with adb and my phone says it's on the current version finally. It seems the support people at project fi are clueless for the most part. You have to do everything yourself but they will at least credit your account for the data used by Android os if you call them and tell them what's up. They want screen shots of the data usage. So save one before you go messing with stuff
It's possible that it comes today/tomorrow at some point!!
Source: https://twitter.com/nvidiashield/status/913265527480475648
Yes, major speculating here, but usually Nvidia is very very quick with updates. SO let's all hope and pray. This COULD also be the Nvidia Spot announcement/availability.
Tomorrow 29th or today 28th. Their message is very cryptic. Google Assistant was just released for Nvidia Shield TV! Not Oreo unless they have their own announcement since Assistant one was by Google
Apparently some people are updating to Oreo already. But it looks like US only. :crying:
edit...not Oreo
kalinskym said:
Tomorrow 29th or today 28th. Their message is very cryptic. Google Assistant was just released for Nvidia Shield TV! Not Oreo unless they have their own announcement since Assistant one was by Google
Click to expand...
Click to collapse
Yes, correct. It was assistant that was released! http://www.androidpolice.com/2017/09/28/assistant-finally-come-shield-tv-looks-great/
JoeFCaputo113 said:
Yes, correct. It was assistant that was released! http://www.androidpolice.com/2017/09/28/assistant-finally-come-shield-tv-looks-great/
Click to expand...
Click to collapse
Unfurtunately only in U. S.... Hopefully there will be a way to get it, elsewhere
Kantraz said:
Unfurtunately only in U. S.... Hopefully there will be a way to get it, elsewhere
Click to expand...
Click to collapse
Wonder if changing the language to English US will force it to work like with phones. I'll have a play about tonight.
Also...from what I understand this is Nvidia Experience 6 and not Oreo. The new launcher is not yet here for the shield.
dunjamon said:
Wonder if changing the language to English US will force it to work like with phones. I'll have a play about tonight.
Also...from what I understand this is Nvidia Experience 6 and not Oreo. The new launcher is not yet here for the shield.
Click to expand...
Click to collapse
Hopefully it is enough, gonna try as soon as I get home from work!
Kantraz said:
Hopefully it is enough, gonna try as soon as I get home from work!
Click to expand...
Click to collapse
Snap! I've already told the missus to plug in the controller to get it charged up and ready. Ha!
dunjamon said:
Snap! I've already told the missus to plug in the controller to get it charged up and ready. Ha!
Click to expand...
Click to collapse
I can confirm that Google Assistant, can be enabled by changing the language
Just got the update. But it failed to install. It downloads the update and restarts the shield, but never finishes the install. Stops at about 20% on the Android System Update Screen then restarts back to the home screen asking if I want to install the Experience 6.0 update. Is it because I'm rooted? I don't have TWRP installed but I do have superuser installed....Tried 3 times.
dk1keith said:
Just got the update. But it failed to install. It downloads the update and restarts the shield, but never finishes the install. Stops at about 20% on the Android System Update Screen then restarts back to the home screen asking if I want to install the Experience 6.0 update. Is it because I'm rooted? I don't have TWRP installed but I do have superuser installed....Tried 3 times.
Click to expand...
Click to collapse
I always remove root then do the update. No TWRP either but it would always fail on me.
dk1keith said:
Just got the update. But it failed to install. It downloads the update and restarts the shield, but never finishes the install. Stops at about 20% on the Android System Update Screen then restarts back to the home screen asking if I want to install the Experience 6.0 update. Is it because I'm rooted? I don't have TWRP installed but I do have superuser installed....Tried 3 times.
Click to expand...
Click to collapse
Got #root#?!
If so, well there's your problem. You can NOT update in the conventional way once your rooted. In short you'll have to first download, and use fastboot, to flash the last 5.0.x Recovery For (Chiefly Recovery, System, and Vendor), and then most likely as not do a full system reset. Which if your unfortunate to be doing this on a Pro. Will mean about roughly 2.5h's+ of downtime. Before you'll then need to worry about the latest Update.
Unfortunately I keep telling myself to never root the damned thing again. 'Cause this IS a huge PitA! but, somehow I never learn.
JagXK8 said:
I always remove root then do the update. No TWRP either but it would always fail on me.
Click to expand...
Click to collapse
Alas One does NOT just remove root on the Shield. And, sadly 'cause of it. The only way I know of to be rid of it is flashing a new (Clean Recovery OS), and then factory resetting it fresh for the "New OS" to actually get written. Otherwise root seem to longer like a bad smell on the Shield.
And, now an aside...
Where is all this scuttlebutt about Oreo (Cookie), coming from?
Having done the above... (Sigh again!) I just finished wrapping up that part of the Install. When it occurred to me to check the Version... Which is still Android 7 (e.g. Nougat), so unless someones getting something I'm not. Then, this is not the Chocolate Wafer Cookie your looking for....
Which begs a different question. Why are they calling this "Experience 6..x", and not 5.x.x?
Ichijoe said:
Got #root#?!
If so, well there's your problem. You can NOT update in the conventional way once your rooted. In short you'll have to first download, and use fastboot, to flash the last 5.0.x Recovery For (Chiefly Recovery, System, and Vendor), and then most likely as not do a full system reset. Which if your unfortunate to be doing this on a Pro. Will mean about roughly 2.5h's+ of downtime. Before you'll then need to worry about the latest Update.
Unfortunately I keep telling myself to never root the damned thing again. 'Cause this IS a huge PitA! but, somehow I never learn.
Alas One does NOT just remove root on the Shield. And, sadly 'cause of it. The only way I know of to be rid of it is flashing a new (Clean Recovery OS), and then factory resetting it fresh for the "New OS" to actually get written. Otherwise root seem to longer like a bad smell on the Shield.
And, now an aside...
Where is all this scuttlebutt about Oreo (Cookie), coming from?
Having done the above... (Sigh again!) I just finished wrapping up that part of the Install. When it occurred to me to check the Version... Which is still Android 7 (e.g. Nougat), so unless someones getting something I'm not. Then, this is not the Chocolate Wafer Cookie your looking for....
Which begs a different question. Why are they calling this "Experience 6..x", and not 5.x.x?
Click to expand...
Click to collapse
I don't know about any Oreo update, but I updated to the new release without doing any data reset. Simply boot to fastboot and flash the downloaded system.img, boot.img, and recovery.img. No need to clear data. Then in the system you can install the OTA as normal and re-root using TWRP and Magisk/SuperSu.
eelsid said:
I don't know about any Oreo update, but I updated to the new release without doing any data reset. Simply boot to fastboot and flash the downloaded system.img, boot.img, and recovery.img. No need to clear data. Then in the system you can install the OTA as normal and re-root using TWRP and Magisk/SuperSu.
Click to expand...
Click to collapse
Can you elaborate on this? Maybe post a small guide? I am bootloader unlocked, and currently rooted, but recovery is stock. Where do I get the files you are talking about? Download, boot, and recovery img files? Thanks in advance!
bradleyw801 said:
Can you elaborate on this? Maybe post a small guide? I am bootloader unlocked, and currently rooted, but recovery is stock. Where do I get the files you are talking about? Download, boot, and recovery img files? Thanks in advance!
Click to expand...
Click to collapse
I found this guide here: https://forums.geforce.com/default/topic/667705/-guide-how-to-update-a-rooted-nvidia-shield/
I actually found this helpful guide for updating if you are on a pro and unlocked. http://nvidiashieldzone.com/2017/10/shield-tv-pro-500gb-experience-6-0-upgrade-solution/
After a few hours stock camera stopped work (after restarting or making a factory reset still the same), dont know if the update to pie has something to do.
anyone having same problem?
Here you see
reset your phone
Brugos27 said:
After a few hours stock camera stopped work (after restarting or making a factory reset still the same), dont know if the update to pie has something to do.
anyone having same problem?
Click to expand...
Click to collapse
I had the same problem, i resetted the phone via settings and this fixed it for me
Do not disturb is active
That happens when "Do not disturb" is active, deactivate it and go!
jerryortiz2100 said:
That happens when "Do not disturb" is active, deactivate it and go!
Click to expand...
Click to collapse
This helped thank you
How did you update?
Did you get the update normally? I used a VPN to get it since it was not yet being offered directly. And now I have this bug as well. So I wanted to see if it's happening to everyone or just people who updated with a VPN.
ryanhossain9797 said:
Did you get the update normally? I used a VPN to get it since it was not yet being offered directly. And now I have this bug as well. So I wanted to see if it's happening to everyone or just people who updated with a VPN.
Click to expand...
Click to collapse
It's not about how you updated, it's because of the used build which is the same like the first released beta build.
thorin0815 said:
It's not about how you updated, it's because of the used build which is the same like the first released beta build.
Click to expand...
Click to collapse
That's kind of the point of my question. Did me using vpn somewhy cause me to get the beta build for some strange reason or a mistake on their end? or is this build being OTA'd normally to other people as a stable update in some regions?
Not much to say.
When I open camera app I get a pop up saying camera failed.
I have force stopped app clear data and cache and restarted. Didn't work. I have factory reset. I got the phone back in June under Verizon.
Any tips on getting this fixed would be great.
Thanks
thayl0 said:
Not much to say.
When I open camera app I get a pop up saying camera failed.
I have force stopped app clear data and cache and restarted. Didn't work. I have factory reset. I got the phone back in June under Verizon.
Any tips on getting this fixed would be great.
Thanks
Click to expand...
Click to collapse
try to wype partition cache
UNIK97122 said:
try to wype partition cache
Click to expand...
Click to collapse
I have done that as well through bootloader. Forgot to mention. It may be a software issue. I flash a older firmware and the camera worked. I let it update and it worked but after a few hours it stopped working. I've yet to let it stay on the software version that works for more then few minutes.
thayl0 said:
I have done that as well through bootloader. Forgot to mention. It may be a software issue. I flash a older firmware and the camera worked. I let it update and it worked but after a few hours it stopped working. I've yet to let it stay on the software version that works for more then few minutes.
Click to expand...
Click to collapse
do you have the same with another camera app ?
Updates are overated... if I have a stable load that's running well I leave it alone.
I've run outdated OS's on Android for years with no major issues or forced reloads because of it.
Old firmware/software doesn't break Androids but new ones sure as hell can...
Still running on Pie on my 10+ with no plans to go to Q.
blackhawk said:
Updates are overated... if I have a stable load that's running well I leave it alone.
I've run outdated OS's on Android for years with no major issues or forced reloads because of it.
Old firmware/software doesn't break Androids but new ones sure as hell can...
Still running on Pie on my 10+ with no plans to go to Q.
Click to expand...
Click to collapse
Sadly I don't think I can go back to pie I believe there's a different bootloader version
thayl0 said:
Sadly I don't think I can go back to pie I believe there's a different bootloader version
Click to expand...
Click to collapse
Try the new Beta,it might fix it
TheViciousGames said:
Try the new Beta,it might fix it
Click to expand...
Click to collapse
Trying to find the first beta so it can update to latest. No luck so far
thayl0 said:
Sadly I don't think I can go back to pie I believe there's a different bootloader version
Click to expand...
Click to collapse
Yeah they like to lock the doors behind you... just remember the lesson.
I learned the hard way with Kitkat; the last update did nothing except make easy root impossible.
With lollipop AT&T/Samsung purposely screwed up the graphics on just that old model for contacts and the music play list making the S4+ next to unusable.
They'll say it will run better, be more secure.
BS.
Never had a OS "upgrade" that wasn't bigger, hoggier and slower then the original on Android.
Never in 6 years of running outdated OS's on Androids had to do a reload from a virus or worm.
Sure it can happen but rarely does if you don't do stupid things.
Play with it, eventually you'll sort it out
Androids wuv being played with...
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.