When I went to check for the October update I found that the System Update option was missing from the system settings. I side loaded the OTA and it's still not there. Before that I could still find it in the settings search but tapping it didn't take me anywhere, now it's gone completely.
I'm on stock with Magisk 17.2, going core mode only didn't help either. Anyone have an idea how to get it back short of a factory reset?
waaagh313ph4n7 said:
When I went to check for the October update I found that the System Update option was missing from the system settings. I side loaded the OTA and it's still not there. Before that I could still find it in the settings search but tapping it didn't take me anywhere, now it's gone completely.
I'm on stock with Magisk 17.2, going core mode only didn't help either. Anyone have an idea how to get it back short of a factory reset?
Click to expand...
Click to collapse
Screenie of System->advanced please
bobby janow said:
Screenie of System->advanced please
Click to expand...
Click to collapse
There you go:
{
"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"
}
waaagh313ph4n7 said:
There you go:
Click to expand...
Click to collapse
How did you get System UI Tuner in the menu? Did you use the app in the PS? Can you try to uninstall that? I don't even see advanced in the menu where the update check is. Heck, I'd just do a factory reset at this point if that doesn't work because something is messed up.
bobby janow said:
How did you get System UI Tuner in the menu? Did you use the app in the PS? Can you try to uninstall that? I don't even see advanced in the menu where the update check is. Heck, I'd just do a factory reset at this point if that doesn't work because something is messed up.
Click to expand...
Click to collapse
I can't even remember how I got it, I don't think it was intentional and certainly no app. The advanced menu just expands like this, it's always been like that for me:
Oh well, thanks anyway!
waaagh313ph4n7 said:
I can't even remember how I got it, I don't think it was intentional and certainly no app. The advanced menu just expands like this, it's always been like that for me:
Oh well, thanks anyway!
Click to expand...
Click to collapse
I presume you're on stock unrooted Android 9. If so it's time to bite the bullet and do a factory reset. If you're rooted and bl unlocked then I'm not your guy. I haven't bl unlocked for a couple of years now or even rooted my devices. (although that could change if my VZW Pixel 2 can get temp root) So with the various slots and possibility of soft bricking I hope someone else jumps in to help. Good luck.
Oh I just looked back and your rooted and bl unlocked. Sorry, I don't really know how to help. But if it were my device I would flash the October factory image with a full wipe and start all over. But as noted I'm not rooted or unlocked. Just out of curiosity, did you buy the device used?
Related
I dont know how, but a red F has appeared at my screen, and dont know how to removed it, has anyone had the same problem? any idea how to remove it? (is it a malware/virus? is it from an application ?)
thanx
{
"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"
}
Is it only on your lockscreen, or always visible?
if i remove lockscreen(disable pattern) is always, with lockscreen it remains at lockscreen
Petrovski80 said:
Is it only on your lockscreen, or always visible?
Click to expand...
Click to collapse
tabon said:
if i remove lockscreen(disable pattern) is always, with lockscreen it remains at lockscreen
Click to expand...
Click to collapse
Never saw something like this. Did it occur out of the blue or after flashing a ROM?
(judging from your non-stock battery icon I take assume you're on a custom ROM)
it just appeared, also i did a full clean new rom flash(wiped everything), but i restored my data (only the data from my apps/apk) and when someone called me,it appeared again,its weird
Petrovski80 said:
Never saw something like this. Did it occur out of the blue or after flashing a ROM?
(judging from your non-stock battery icon I take assume you're on a custom ROM)
Click to expand...
Click to collapse
tabon said:
it just appeared, also i did a full clean new rom flash(wiped everything), but i restored my data (only the data from my apps/apk) and when someone called me,it appeared again,its weird
Click to expand...
Click to collapse
Does it happen on stock ROM/kernel?
i have the stock kernel, my rom is stock,just deoxeded
tabon said:
i have the stock kernel, my rom is stock,just deoxeded
Click to expand...
Click to collapse
In that case I don't have any advice I'm afraid. I even googled it because I never saw something like it, doesn't yield any useful info. Could be some samsung driver causing Android to display this red f, but that's just speculation.
If it remains, I'd return to factory images, relock the bootloader and claim warranty.
yeah, i googled it too,and couldnt find a single post, the only reasonably thing is that it may be a virus or something, and it came back with the data restore, i cant think of something else, thank you for your time though
Petrovski80 said:
In that case I don't have any advice I'm afraid. I even googled it because I never saw something like it, doesn't yield any useful info. Could be some samsung driver causing Android to display this red f, but that's just speculation.
If it remains, I'd return to factory images, relock the bootloader and claim warranty.
Click to expand...
Click to collapse
you have an app doing that.
Try going through each of your backed up apps, to see if you can find the app that's causing this.
i killed each running app in the backround, and i found it, its an app named "Android lost" , never had a problem with it, dont know why it just happended (also it had long to time to do an update, so to say that was something in the update)
weird.
Glad you got it sorted out.
Petrovski80 said:
Glad you got it sorted out.
Click to expand...
Click to collapse
thank you guys, i ll monitoring it for 1-2 days
Hi All
I had installed Ditto Note 3 v4_RC2 later the phone started to hang and restart, so i decided to flash 4.4.2 (stock) via Odin and i was successful. But the status is being displayed as " Custom " . I have 8 months warranty left. Please guide me in getting back to official status. :crying:
I hope in the three hours since posting you've solved this issue. All it would take is a small amount of research.
IF you researched and are still unsure please get back in touch, with details
EmptyArea said:
I hope in the three hours since posting you've solved this issue. All it would take is a small amount of research.
IF you researched and are still unsure please get back in touch, with details
Click to expand...
Click to collapse
No success !!
First i flashed with Kitkat stock rom
Second i re-rooted
Third i reset the counter using triangle away
When i reset the counter it shows official status in download mode , but in settings still it is custom.
please help!!
Entropy: the reason why if you drop a drop a broken egg, you don't get one that's new
shonith said:
No success !!
First i flashed with Kitkat stock rom
Second i re-rooted
Third i reset the counter using triangle away
When i reset the counter it shows official status in download mode , but in settings still it is custom.
please help!!
Click to expand...
Click to collapse
Details sir, it's all about the details.... There's more than one way to crack an egg - few people are going to waste their time speculating how you did it...
What precisely is your goal / why are you doing this?
Which KK ROM exactly, from where?
How did you root?
Which Triangle away version, from where, what exactly did you do?
--
1 free speculation:
If all you care is about the settings option, I think you might be able to just open triangle away click "allow tracker to run" and then reboot into download mode, then just hold the power button down until it reboots again.
Are you sure you didn't see this?
Arsaw said:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You must root your device for installing this rom/mod. so now your warranty is void. if anything happens to you or your phone is solely your resposibility.
We don't allow chefs/devs/themers to use the files added or modded by us in this ROM.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
shonith said:
No success !!
First i flashed with Kitkat stock rom
Second i re-rooted
Third i reset the counter using triangle away
When i reset the counter it shows official status in download mode , but in settings still it is custom.
please help!!
Click to expand...
Click to collapse
Make a factory reset now and it will show official in settings ?
Sent from my GT-I9506 using Tapatalk
I had a n Orange locked device and have since supercided, s-offed and now running latest stock WW Rom. However, I get the below and wondering if there's anyway to disable the reporting whilst staying otherwise stock or stock and rooted.
{
"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"
}
Sent from my HTC One_M8 using Tapatalk
stuart0001 said:
I had a n Orange locked device and have since supercided, s-offed and now running latest stock WW Rom. However, I get the below and wondering if there's anyway to disable the reporting whilst staying otherwise stock or stock and rooted.
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
I am having the same issue, the best I could do is freeze udove which is apparently the app that does the reporting. When I did this I could no longer open the Tell HTC section in settings so I am assuming it freezes the reporting.
Alaris said:
I am having the same issue, the best I could do is freeze udove which is apparently the app that does the reporting. When I did this I could no longer open the Tell HTC section in settings so I am assuming it freezes the reporting.
Click to expand...
Click to collapse
Thanks for that. After a quick search it seems mybreeze.apk is also a potential culprit so I've frozen that too. :good:
Just remember to back up udove and don't get rid of it as you will need it in place for OTA
Is it actually reporting or is that message just the result of an unlocked boot loader? I haven't seen any activity from any of those apps.
ashyx said:
Is it actually reporting or is that message just the result of an unlocked boot loader? I haven't seen any activity from any of those apps.
Click to expand...
Click to collapse
As your phone is S-OFF it's technically deemed a test device, hence the warning being permanent. It does nothing to the use of the phone so just ignore it
EddyOS said:
As your phone is S-OFF it's technically deemed a test device, hence the warning being permanent. It does nothing to the use of the phone so just ignore it
Click to expand...
Click to collapse
It wouldn't bother people if it were just device related. If you read the statement, it clearly states that it will collect "personally identifiable information such as your name, phone number, precise location..." you get the point. WTF do they need all of this for just for turning off the security of these devices? That's ridiculous and a great infringement to our human rights and privacy and nobody says a thing about it. They don't need our personal information, just device info, so why would they need to know who **** Murcy or Horace P. is? Secondly, why is S-Off a nice automatic way of considering the device a "test device" if its not like we're probing the thing or anything, just flashing roms and enabling features that can be pulled off on any other non HTC device once the boot loader is unlocked. Who gives a company born in the late 90s so much rights over the privacy of their users?
Anyways, can anyone give me a thorough way of disabling this? I'm not scared of a bootloop or failure of the alarm app, I just feel that if they have such right, we have a right to get rid of it.
As the title says, I installed the ASUS Official Unlock tool (and didn't really read it, as you should) and it attempted a boot unlock without SU. The funny thing is, it did exactly what it said it would do and rebooted into the Bootloader. The Bootloader said (and still does) it was a success and that the phone will reboot in 5 seconds. Which is fine, except it's doing that every single time I enter the Bootloader. I can't get it to stop doing that so I can actually do the root and re-do the unlock. The phone still functions perfectly fine otherwise.. any advice? (Yes, I can get it into recovery mode) Hopefully that didn't ban me from OTA.
EDIT: It also turned my boot screen white, and I also tried to use the sideloader, but I already have the latest ASUS firmware so that didn't help. However, in my loader I noticed some weird stuff showing about a MOD_SDUPDATE.ZIP not being found.. I don't know what's that about. It was doing that before I tried to use the sideloader.
{
"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"
}
dunno what exactly happened, but you can do " Using Stock.zip from ASUS site:" from here, that should fix basically everything: http://forum.xda-developers.com/zenfone2/general/guide-to-apply-ota-bootloop-rooted-zf2-t3127835
P.S.: your data won't be lost, however your app ache will be cleared, meaning you'll be logged out everywhere. So if you have some game and no account, that game state will be lost.
So I tried that, first with the ROM that's installed on the phone the .97 version. Then with the original version. It appears to actually install the .97 version, but that does absolutely nothing for the phone and if I try an older version it just tells me it can't flash an older version. Should flashing the same version over-top have taken care of the problem? Doesn't look like it did anything. The boot loader is probably unlocked, but I can't keep it in ADB mode long enough to do anything useful and you can't sideload a recovery to my knowledge.
EDIT: I named the file wrong in my tiredness. I did it again and loaded in recovery...
EDIT2: That did not work.
You're in a lot of company... There's a couple of threads about this with ASUS reps also saying the same thing....
ultramag69 said:
You're in a lot of company... There's a couple of threads about this with ASUS reps also saying the same thing....
Click to expand...
Click to collapse
I don't actually know what you mean by that? With the ASUS unlocking tool causing it to reboot in the bootloader improperly or the booting of the file from Recovery?
The phone isn't actually "broken" but now... I can't do anything to it without the use of ADB.. Which blows.
EDIT: Also, can you point me to these threads?
http://forum.xda-developers.com/zenfone2/general/official-asus-ze551ml-bootloader-unlock-t3224747
The tool is causing this for multiple users. Check the thread above.
m3t4lw01f said:
http://forum.xda-developers.com/zenfone2/general/official-asus-ze551ml-bootloader-unlock-t3224747
The tool is causing this for multiple users. Check the thread above.
Click to expand...
Click to collapse
Thanks a lot, I figured I could dig some information out of the thread. My search just didn't turn it up. Looks like a lot more people are having this issue than I figured.
bewaffled1 said:
Thanks a lot, I figured I could dig some information out of the thread. My search just didn't turn it up. Looks like a lot more people are having this issue than I figured.
Click to expand...
Click to collapse
Yep. We're hoping @ASUS_Khang gets a solution from HQ next week to get us back on track!
New update
{
"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 install it? Did you notice any changes to battery life or anything else?
Also, just received the notification for F20.
nabril15 said:
Did you install it? Did you notice any changes to battery life or anything else?
Click to expand...
Click to collapse
i download and install. last night
now. waiting for OxygenOS 13.1 Update
brmbjn said:
i download and install. last night
Click to expand...
Click to collapse
Ok. Great. Congratulations.
Do you notice any difference in behavior? Incremental updates sometimes have side effects.
nabril15 said:
Ok. Great. Congratulations.
Do you notice any difference in behavior? Incremental updates sometimes have side effects.
Click to expand...
Click to collapse
only january security patch hehehehhe...................
brmbjn said:
only january security patch hehehehhe...................
Click to expand...
Click to collapse
Right, but it also fixed a couple of more things, as stated in the screenshot. A lot of people reported battery life concerns after installing F18, which also only updated the security patch.
I notice that phone is a bit slower. Like its not 120hz
My install fails every time at 27%. I have tried local upgrade as well.
Same and restoring images through Magisk also fails... I think it's due to TWRP
nabril15 said:
Did you install it? Did you notice any changes to battery life or anything else?
Click to expand...
Click to collapse
After 2 day. battery life is not bad.
sbcrumb said:
My install fails every time at 27%. I have tried local upgrade as well.
Click to expand...
Click to collapse
if it fails at 27% you have to go to magisk, hit uninstall and hit restore image, go back to software update and do the local update
luckylui said:
Same and restoring images through Magisk also fails... I think it's due to TWRP
Click to expand...
Click to collapse
it's not TWRP... did you follow the tutorial : Remove OOS13 Orange state message text? if you did then you have to restore the original abl.img which should have saved in your sdcard directory as abl.img.bak
Alberhasky said:
if it fails at 27% you have to go to magisk, hit uninstall and hit restore image, go back to software update and do the local update
Click to expand...
Click to collapse
wish that worked. But still failed.
Alberhasky said:
it's not TWRP... did you follow the tutorial : Remove OOS13 Orange state message text? if you did then you have to restore the original abl.img which should have saved in your sdcard directory as abl.img.bak
Click to expand...
Click to collapse
It's weird.. first time this has ever happened. Maybe because I installed TWRP the wrong way and didn't follow the correct steps for oos13. I didn't do the orange state message since it doesn't bother me and I was able to update the past two updates without a problem.