Hello, i Hope some one can help me. I have a op5 with unlock bootloader and a custom recovery (twrp by blue) i have flash a lot rom since september 2018. But since today i have a different warning at boot.Someone can tell me what it is and how remove this warning. My phone work fine but it's not normal i think. Thank a lot
c3drik 67 said:
Hello, i Hope some one can help me. I have a op5 with unlock bootloader and a custom recovery (twrp by blue) i have flash a lot rom since september 2018. But since today i have a different warning at boot.Someone can tell me what it is and how remove this warning. My phone work fine but it's not normal i think. Thank a lot
Click to expand...
Click to collapse
That's the common warning screen when you unlocked the bootloader. Nothing more.
strongst said:
That's the common warning screen when you unlocked the bootloader. Nothing more.
Click to expand...
Click to collapse
Hello, but sorry it isn't the common warning. Since the begining i have unlock my bootloader (september or october)i have this warning. And not the first i have post. It's not the same.
Again this is a quite common warning on the one plus 5. Have you recently flashes a new ROM?
Have you updated widevile L1 in a service center? If so, that's the reason of the new warning message, nothing to worry about..
That warning is when you flashed Open Beta 10. There is an file (abl.elf) in the firmware that replaces the old warning screen to new warning screen. Nothing more, nothing less. So no worry though...
matt_simpson said:
Again this is a quite common warning on the one plus 5. Have you recently flashes a new ROM?
Click to expand...
Click to collapse
Yes i have flash a new rom yesterday.
carlese said:
Have you updated widevile L1 in a service center? If so, that's the reason of the new warning message, nothing to worry about..
Click to expand...
Click to collapse
No i didn't do that.
lekiaM said:
That warning is when you flashed Open Beta 10. There is an file (abl.elf) in the firmware that replaces the old warning screen to new warning screen. Nothing more, nothing less. So no worry though...
Click to expand...
Click to collapse
Ok thanks you for your answer. Effectivly i have flash the ob10 firmare yesterday.
c3drik 67 said:
Yes i have flash a new rom yesterday.
Click to expand...
Click to collapse
Which one? Was it the open beta?
matt_simpson said:
Which one? Was it the open beta?
Click to expand...
Click to collapse
i have flash two rom yesterday but i have flash the ob10 firmware yes.
c3drik 67 said:
Yes i have flash a new rom yesterday.
Click to expand...
Click to collapse
c3drik 67 said:
i have flash two rom yesterday but i have flash the ob10 firmware yes.
Click to expand...
Click to collapse
Well then that is the standard one plus warning page. I have it on mine.
Matt
thanks subject closed.
That's the new bootloader from beta 10. Everyone who has that installed with an unlocked bootloader will have it that way. And simply reverting to previous builds won't change it. But that's just a cosmetic change so don't worry about it.
Sent from my OnePlus 5 using XDA Labs
fjsferreira said:
That's the new bootloader from beta 10. Everyone who has that installed with an unlocked bootloader will have it that way. And simply reverting to previous builds won't change it. But that's just a cosmetic change so don't worry about it.
Click to expand...
Click to collapse
That's correct. Reverting to the previous Oreo builds won't change it because the new file in the firmware is only present in OB10, and not the older Oreo builds, so it won't be overwritten even if an older Oreo build is flashed.
However, the Nougat builds of OOS had this file present in their firmware, so flashing the firmware of any of the Nougat OOS builds will get the old warning back, theoretically.
Can i delete this file? Because i will switch to recovery or fastboot over this screen.
Thanks Paper
It's a new warning screen from the last OB 10
Khaos said:
It's a new warning screen from the last OB 10
Click to expand...
Click to collapse
Thanks for the additional information, but it's already been explained
Thread closed as OP mentioned above.
Related
guys
http://www.asus.com/zentalk/forum.php?mod=redirect&goto=findpost&ptid=14836&pid=107979
asus said they cancelled this update due to unstable update...
1st i dont know what is unstable in this version[same as previous and new bug of call screen animation
2nd lol which update came without new bugs?
3rd they removed after they heard about unlocking bootloader..something fishy right :laugh:
they will probably patch the unlock method with the next update, gonna unlock the bootloader before updating to next update.
Sent from my ASUS_Z008D using Tapatalk
luisoman2000 said:
they will probably patch the unlock method with the next update, gonna unlock the bootloader before updating to next update.
Sent from my ASUS_Z008D using Tapatalk
Click to expand...
Click to collapse
ya same here..but what they will do to unlocked phones/??
ansebovi said:
ya same here..but what they will do to unlocked phones/??
Click to expand...
Click to collapse
Maybe there just will be a check and it will abort if the BL is unlocked
But it should be easy to adapt these OTA updates to unlocked devices
ansebovi said:
ya same here..but what they will do to unlocked phones/??
Click to expand...
Click to collapse
Nothing they can do. As long as you don't flash an OTA or full stock build. They may have a way to patch it in their droidboot.
ansebovi said:
guys
3rd they removed after they heard about unlocking bootloader..something fishy right :laugh:
Click to expand...
Click to collapse
That was my first guess as well
TheSSJ said:
Maybe there just will be a check and it will abort if the BL is unlocked
But it should be easy to adapt these OTA updates to unlocked devices
Click to expand...
Click to collapse
no i am asking about bootloader[can they lock it somehow if we flash next ota]
Harfainx said:
Nothing they can do. As long as you don't flash an OTA or full stock build. They may have a way to patch it in their droidboot.
Click to expand...
Click to collapse
so how can we update from here after ??? need to modified by someone for flashing ???
jaysus145 said:
That was my first guess as well
Click to expand...
Click to collapse
ya my 1st thought too,, haha
ansebovi said:
so how can we update from here after ??? need to modified by someone for flashing ???
Click to expand...
Click to collapse
That's how it works with all custom work. Once you're off stock, you're going to have to wait for someone to post a safe update/install.
Rushing in and taking an OTA is a very common way of breaking your build. Like what we see with running an OTA while rooted. Any number of problems can come up.
They could patch any number of things that would give you a very bad day.
With the support we have here though, we'll probably have flashable, safe OTA zips within a few hours of an OTA being captured/downloaded.
Harfainx said:
That's how it works with all custom work. Once you're off stock, you're going to have to wait for someone to post a safe update/install.
Rushing in and taking an OTA is a very common way of breaking your build. Like what we see with running an OTA while rooted. Any number of problems can come up.
They could patch any number of things that would give you a very bad day.
With the support we have here though, we'll probably have flashable, safe OTA zips within a few hours of an OTA being captured/downloaded.
Click to expand...
Click to collapse
well i am from sony device..they release main update of android..and 1 bug fix,thats all...so we dont care..and no need to worry about relocking issues..
this is the first asus device...man they releasing update for every 10days..i thought we could apply just like that..but since they didnt gave unlocked bootloader tool ,i got these doubt..
and thanks for info..
so i must wait for zips which is modified for unlocked bootloader[if they trying to relock]
I honestly doubt they're going to find a way to relock it with an update, but who knows what voodoo they may come up with.
Either way, we'll grab the updates and get them ready to be flashed quickly. It's a simple process.
I highly doubt he will do anything regarding unlocking/locking bootloader. because:
1. last year they released their official tool to unlock zenfone 4,5,6 bootloader after 3-4 months of release.
2. This year when they launched the zf2 in US they hold contest and developer events via xda. Now xda is a place where no one keeps their bootloader locked. so they knew exactly where they are releasing and advertising the product.
So I dont think they would even bother about this bootloader . Maybe it is an unstable build in terms of their quality test.
Dang, and my 551 (2/16GB) is still in transit.
Was browsing the forum and this thread - has 2.19 been captured and saved somewhere else, or was everyone just downloading off ASUS servers for this OTA (when forced)?
I don't know if I would want 2.19 yet. Maybe to keep on my PC until the right time. That is, if 2.20 comes out and the BL hole is plugged, and those who were on 2.19 (and took advantage of the bootloader unlocking) still got the update successfully - if either of those two outcomes are false, I wouldn't use it.
joel.maxuel said:
Dang, and my 551 (2/16GB) is still in transit.
Was browsing the forum and this thread - has 2.19 been captured and saved somewhere else, or was everyone just downloading off ASUS servers for this OTA (when forced)?
I don't know if I would want 2.19 yet. Maybe to keep on my PC until the right time. That is, if 2.20 comes out and the BL hole is plugged, and those who were on 2.19 (and took advantage of the bootloader unlocking) still got the update successfully - if either of those two outcomes are false, I wouldn't use it.
Click to expand...
Click to collapse
Everthings here http://forum.xda-developers.com/zenfone2/general/ota-links-stock-rom-t3093999
android is open source. and roms are not illegal. so why bother? i don't think asus is interested on ours bootloader plus, other zenfone's are already unlocked
joel.maxuel said:
Dang, and my 551 (2/16GB) is still in transit.
Was browsing the forum and this thread - has 2.19 been captured and saved somewhere else, or was everyone just downloading off ASUS servers for this OTA (when forced)?
I don't know if I would want 2.19 yet. Maybe to keep on my PC until the right time. That is, if 2.20 comes out and the BL hole is plugged, and those who were on 2.19 (and took advantage of the bootloader unlocking) still got the update successfully - if either of those two outcomes are false, I wouldn't use it.
Click to expand...
Click to collapse
Even if your phone gets here on a newer version (it won't), you could always downgrade everything and unlock from there. =)
Shakalaka has backups of everything going back to like version 2.12 or 2.13.
MatteXperiaU said:
android is open source. and roms are not illegal. so why bother? i don't think asus is interested on ours bootloader plus, other zenfone's are already unlocked
Click to expand...
Click to collapse
Problem is they can't support any ROM that isn't official on the zenfone. They'll pass you off. Like most manufacturers.
These are just official update links from Asus. Not backups. Asus can shut those down at any point. Not saying they will.
See here for pre-rooted ROM backups:
http://forum.xda-developers.com/zenfone2/orig-development/rom-pre-root-img-t3079590
one more doubt..
i think 2.17 is stable build from asus without the android os drinking the battery
now i have unlocked the bootloader ,can i reflash the 2.17[asking since it doesnt have the things which enabled to unlock bootloader] ...or once unlocked,we can do anything like other brands phone?
damian5000 said:
These are just official update links from Asus. Not backups. Asus can shut those down at any point. Not saying they will.
See here for pre-rooted ROM backups:
http://forum.xda-developers.com/zenfone2/orig-development/rom-pre-root-img-t3079590
Click to expand...
Click to collapse
I downloaded the appropriate OTA the other night, so if ASUS pulls the file, I still have it and can share it on Dropbox and/or Copy.
I get the phone today! So hopefully tonight I get the OTA up to 2.18 and then wait to see what upcoming 2.20 has to offer. If we can still unlock the BL with 2.20, I will let that OTA happen. Similarly if we find out that those who unlocked their bootloaders can't take the update (at that point I will cry a little, if there is no official way to unlock BL released with the update ).
If both scenarios above are false, then I will apply my downloaded 2.19, unlock the bootloader, then accept 2.20.
Best one could do eh?
---------- Post added at 07:24 ---------- Previous post was at 07:19 ----------
ansebovi said:
one more doubt..
i think 2.17 is stable build from asus without the android os drinking the battery
now i have unlocked the bootloader ,can i reflash the 2.17[asking since it doesnt have the things which enabled to unlock bootloader] ...or once unlocked,we can do anything like other brands phone?
Click to expand...
Click to collapse
I cannot imagine it would re-lock the bootloader. Should be able to downgrade, as long as you use the whole image and not just the OTA zip.
Now you got me wondering....
joel.maxuel said:
I cannot imagine it would re-lock the bootloader. Should be able to downgrade, as long as you use the whole image and not just the OTA zip.
Now you got me wondering....
Click to expand...
Click to collapse
no i didnt mean it will relock,..
but the unlocked needed some file right..it modifies something right? ...and it is not present in old things..so can old fw run on unlocked bootloader? [or would it get bootloop or damage bootloader]
That such community, I hope they can solve my doubts, I have my moto g4 plus (XT1641) with dual sim, and unlock the Bootloader and I got cyanogenmod 13, but I found out about the soak test and returned to stock.
1.- When I enter fastboot mode it appears in yellow letters "Software Status: Modified". Is there a way to say "official" again? Does this "modified" status prevent you from receiving OTAs?
2.-What is the last compilation number? I have the compilation MPJ24.139-23.1
ThaRandomAndroid said:
That such community, I hope they can solve my doubts, I have my moto g4 plus (XT1641) with dual sim, and unlock the Bootloader and I got cyanogenmod 13, but I found out about the soak test and returned to stock.
1.- When I enter fastboot mode it appears in yellow letters "Software Status: Modified". Is there a way to say "official" again? Does this "modified" status prevent you from receiving OTAs?
2.-What is the last compilation number? I have the compilation MPJ24.139-23.1
Click to expand...
Click to collapse
You should look here http://forum.xda-developers.com/moto-g4-plus/help/staus-modified-t3522177
There are questions to your answers
strongst said:
You should look here http://forum.xda-developers.com/moto-g4-plus/help/staus-modified-t3522177
There are questions to your answers
Click to expand...
Click to collapse
I tried those methods but, don't solve my problem and doubts. But thanks anyway ?
ThaRandomAndroid said:
I tried those methods but, don't solve my problem and doubts. But thanks anyway ?
Click to expand...
Click to collapse
you should mention all things you did already, no one can look in your mind
Then don't create an thread, head over to the existing one and ask there.
ThaRandomAndroid said:
I tried those methods but, don't solve my problem and doubts. But thanks anyway
Click to expand...
Click to collapse
Modified status will not affect OTA.. as you said your build no. Is (139-23.1) , it's old, latest is (139-63)..
Just restore stock backup and check for update., May be you will get latest one..:good:
__Madddy said:
Modified status will not affect OTA.. as you said your build no. Is (139-23.1) , it's old, latest is (139-63)..
Just restore stock backup and check for update., May be you will get latest one..:good:
Click to expand...
Click to collapse
I don't have a backup... So, please do you have a link or guide? Thanks ?
ThaRandomAndroid said:
I don't have a backup... So, please do you have a link or guide? Thanks
Click to expand...
Click to collapse
See last reply on that thread, you have link already..
__Madddy said:
See last reply on that thread, you have link already..
Click to expand...
Click to collapse
I'm sorry, but I've done all the steps, but I do not get the MPJ24.139-63 update, it just tells me that I have my device updated.
What I did was return to rom stock specifically with this file (XT1640-XT1641_ATHENE_6.0.1_MPJ24.139-23.1_cid50_subsidy-DEFAULT_CFC.xml).
Please let me know if I have done something wrong.
Thank you.
ThaRandomAndroid said:
I'm sorry, but I've done all the steps, but I do not get the MPJ24.139-63 update, it just tells me that I have my device updated.
What I did was return to rom stock specifically with this file (XT1640-XT1641_ATHENE_6.0.1_MPJ24.139-23.1_cid50_subsidy-DEFAULT_CFC.xml).
Please let me know if I have done something wrong.
Thank you.
Click to expand...
Click to collapse
I have experimented a lot with my XT1643
My software status is also modified even after flashing stock rom....
But software status does not affects the phone a bit...
OTA may not come ! at least didn't in my case even after 15 days...So chill...
Currently I am running CM 14.1 Nightly which is obscenely fast than any stock rom..U can try that
Guys, I desperately need your help. I bought this MiA1 few months ago, I pressed android version in setting but it appears android Nougat logo? I am so confuse right now. Need help to flash this MiA1 to original Android One.
Another info: My MiA1 stucks at Jan 1, 2018 android security patch level.
Baseband version:
.TA.2.3.c1-00544-8953_GEN_PACK-1
macallistergavin said:
Guys, I desperately need your help. I bought this MiA1 few months ago, I pressed android version in setting but it appears android Nougat logo? I am so confuse right now. Need help to flash this MiA1 to original Android One.
Another info: My MiA1 stucks at Jan 1, 2018 android security patch level.
Baseband version:
.TA.2.3.c1-00544-8953_GEN_PACK-1
Click to expand...
Click to collapse
Can you post a screenshot of the about phone in settings? And a screenshot of the nougat logo you get?
All Mi a1 come with Nougat as stock. I got mine beginning of June. You need to use Mi Flash app to flash stock rom, https://www.getdroidtips.com/xiaomi-mi-a1-stock-firmware/ I found it here. It will format everything and re lock bootloader.
varben said:
Can you post a screenshot of the about phone in settings? And a screenshot of the nougat logo you get?
Click to expand...
Click to collapse
Weird isn't it?
Flash latest build using Fastboot
Ritik99 said:
Flash latest build using Fastboot
Click to expand...
Click to collapse
Can you send me the link sir?
macallistergavin said:
Can you send me the link sir?
Click to expand...
Click to collapse
Here you are
http://bigota.d.miui.com/V9.5.11.0....0.ODHMIFA_20180504.0000.00_8.0_1a04581058.tgz
jack_21 said:
Here you are
http://bigota.d.miui.com/V9.5.11.0....0.ODHMIFA_20180504.0000.00_8.0_1a04581058.tgz
Click to expand...
Click to collapse
Thousand of thanks sir. Btw,
Sir, i would like to seek help from you regarding my problem on the main thread. About android one oreo but then appear Nougat. What's on your mind right now about this issue? Have you ever encounter this kind of problem before?
macallistergavin said:
Thousand of thanks sir. Btw,
Sir, i would like to seek help from you regarding my problem on the main thread. About android one oreo but then appear Nougat. What's on your mind right now about this issue? Have you ever encounter this kind of problem before?
Click to expand...
Click to collapse
You are still on N but just don't know why its showing 8.0, in setting. Haven't heard anyone else face such issue.
macallistergavin said:
Thousand of thanks sir. Btw,
Sir, i would like to seek help from you regarding my problem on the main thread. About android one oreo but then appear Nougat. What's on your mind right now about this issue? Have you ever encounter this kind of problem before?
Click to expand...
Click to collapse
First reflash the firmware, then see if the Nougat logo has disappeared
Please do a full backup before flashing the firmware (contacts, sms, media files)
Short of reverting to Nougat that is -- Is there a way to get rid of the new-style bootloader-locked screen that's the first thing you see on start-boot? I'd like to replace it with the Nougat style that allows you to hit a key and go right past it. I thought I'd seen a thread on how to do that here but if anyone knows, much appreciated.
Thanks in advance.
Oh yes -- It's a oneplus 5 and basically running that latest ob18 + NoLimits.
This is easy. Download and flash the Old Bootloader Unlocked Warning zip from this post of mine, and profit!
shadowstep said:
This is easy. Download and flash the Old Bootloader Unlocked Warning zip from this post of mine, and profit!
Click to expand...
Click to collapse
Thanks so much - Probably just what I was after. I knew I'd seen it around.
hachamacha said:
Thanks so much - Probably just what I was after. I knew I'd seen it around.
Click to expand...
Click to collapse
You can just dirty flash OOS and it'll get updated again, since the OOS zip also contains the firmware (of which the bootloader is a part).
shadowstep said:
This is easy. Download and flash the Old Bootloader Unlocked Warning zip from this post of mine, and profit!
Click to expand...
Click to collapse
Worked very well - many thanks.
shadowstep said:
You can just dirty flash OOS and it'll get updated again, since the OOS zip also contains the firmware (of which the bootloader is a part).
Click to expand...
Click to collapse
I noticed that as well, but decided your first way was easier.
hachamacha said:
I noticed that as well, but decided your first way was easier.
Click to expand...
Click to collapse
If that's the case, then you can save the attached zip which has the new bootloader from OB18, in case you want to revert.
I've been trying to downgrade from the latest pie release but I always get the same error due to how Samsung has blocked bootloader downgrades. Is there anyway around this or am I stuck on Pie?
Sterben Pistole said:
I've been trying to downgrade from the latest pie release but I always get the same error due to how Samsung has blocked bootloader downgrades. Is there anyway around this or am I stuck on Pie?
Click to expand...
Click to collapse
You are probably stucked because you upgraded to the latest bootloader:
After updating bootloader to U5/S5 (as in case of G95xFXXU5DSFB) it will not be possible to downgrade it again to any U2/S2/U3/S3/U4/S4 version
Click to expand...
Click to collapse
Here's a workaround:
Backup your present baseband on TWRP, flash ALEXNDR Oreo's ROM then restore your baseband, otherwise you won't have mobile signal and your IMEI will be unknown.
So in theory the only way to downgrade to Oreo or less, is having the bootloader unlocked with TWRP right? if not, you're stuck
No Bootloader downgrade. Not possible.
Sterben Pistole said:
I've been trying to downgrade from the latest pie release but I always get the same error due to how Samsung has blocked bootloader downgrades. Is there anyway around this or am I stuck on Pie?
Click to expand...
Click to collapse
Why would you want to downgrade anyways?
cantenna said:
Why would you want to downgrade anyways?
Click to expand...
Click to collapse
I can't speak for the OP but for me it is more battery friendly, has better perfomance, allow me to debloat more apps than PIE and has better mod/theme support and looks better (didn't like Pie UI).
nemesisexsp said:
Backup your present baseband on TWRP, flash ALEXNDR Oreo's ROM then restore your baseband, otherwise you won't have mobile signal and your IMEI will be unknown.
Click to expand...
Click to collapse
Quick question for you @nemesisexsp as you seem to know what you're talking about.
I'm in the same boat as OP. attached is my SOFTWARE INFORMATION section with my baseband and whatever. Slightly different to what you've posted on your screenshot.
Can you suggest which files I should use from the ALEXANDR Oreo Mod selection? also, just the ROM, or do i need to do something with the BL files also?
I'm rooted (with TWRP), so that shouldn't be any issue.
tim455 said:
Quick question for you @nemesisexsp as you seem to know what you're talking about.
I'm in the same boat as OP. attached is my SOFTWARE INFORMATION section with my baseband and whatever. Slightly different to what you've posted on your screenshot.
Can you suggest which files I should use from the ALEXANDR Oreo Mod selection? also, just the ROM, or do i need to do something with the BL files also?
I'm rooted (with TWRP), so that shouldn't be any issue.
Click to expand...
Click to collapse
I suggest you flash the last Oreo ROM available for the S8 model (SM-G950F/FD). After you flash it you can boot normally in the ROM and see if your mobile signal is fine, if it isn't just restore your PIE baseband on TWRP.
Here's the original post in _alexndr thread where you can find the ROM link:
https://forum.xda-developers.com/showpost.php?p=75646352&postcount=2
nemesisexsp said:
I suggest you flash the last Oreo ROM available for the S8 model (SM-G950F/FD). After you flash it you can boot normally in the ROM and see if your mobile signal is fine, if it isn't just restore your PIE baseband on TWRP.
Here's the original post in _alexndr thread where you can find the ROM link:
https://forum.xda-developers.com/showpost.php?p=75646352&postcount=2
Click to expand...
Click to collapse
Thanks for the quick response.
I made backups via TWRP just incase, but it looks like everything worked. [see image]
Thank you
It's also got me thinking...
-could you install other custom roms that are Oreo-based?
-What makes Alexndr's rom special?
-Is it technically possible to install stock oreo?
tim455 said:
Thanks for the quick response.
I made backups via TWRP just incase, but it looks like everything worked. [see image]
Thank you
It's also got me thinking...
-could you install other custom roms that are Oreo-based?
-What makes Alexndr's rom special?
-Is it technically possible to install stock oreo?
Click to expand...
Click to collapse
I think you can install other ROMs. I just suggested _alexndr because it's as close to stock as possible as the OP was trying to flash via Odin. But i believe that we can't install older firmware via Odin due to the updated bootloader.
nemesisexsp said:
I think you can install other ROMs. I just suggested _alexndr because it's as close to stock as possible as the OP was trying to flash via Odin. But i believe that we can't install older firmware via Odin due to the updated bootloader.
Click to expand...
Click to collapse
Yes, many thanks.
I was trying to get as stock as possible but only found a NOTE8-to-S8 rom and nothing else stock-y. This seems perfect.
cantenna said:
Why would you want to downgrade anyways?
Click to expand...
Click to collapse
Because Pie is absolute trash on the S8 Active. Battery life went way down hill, constantly stutters like the CPU is loaded or it is thermal throttling, notification screen blanks preventing you from see any in the bar. Tapping notification doesn't always open. They ruined the camera UI. Control via bluetooth doesn't work anymore(forget the name but used to when I started my car it would automatically open Pandora and play. Instead now I have to unlock the phone and open Pandora manually".
I only wouldn't be surprised if it come out later that Samsung pulled and able and deliberately crippled devices to encourage upgrades. Joke's on them because my upgrade will be a different brand.
Robborboy said:
Because Pie is absolute trash on the S8 Active. Battery life went way down hill, constantly stutters like the CPU is loaded or it is thermal throttling, notification screen blanks preventing you from see any in the bar. Tapping notification doesn't always open. They ruined the camera UI. Control via bluetooth doesn't work anymore(forget the name but used to when I started my car it would automatically open Pandora and play. Instead now I have to unlock the phone and open Pandora manually".
I only wouldn't be surprised if it come out later that Samsung pulled and able and deliberately crippled devices to encourage upgrades. Joke's on them because my upgrade will be a different brand.
Click to expand...
Click to collapse
Sounds like you got a snapdragon USA?
cantenna said:
Sounds like you got a snapdragon USA?
Click to expand...
Click to collapse
Yepperoni
Robborboy said:
Yepperoni
Click to expand...
Click to collapse
A dev just mad project treble available fo S8+ Exynos which is pretty much what I think your ultimately after.
cantenna said:
A dev just mad project treble available fo S8+ Exynos which is pretty much what I think your ultimately after.
Click to expand...
Click to collapse
Unfortunately the S8 Active did not come in an exynos version AFAIK.
@nemesisexsp wondering, have you noticed much battery diff between Oreo and Pie?