Database Users

Android M help

Hello! I have just upgraded to Android M and I have two quick questions: 1 is , is it a problem if my system did not have any problems updating , even though I am S-OFF and my boot-loader is unlocked, this system being installed from a zip? 2 is, I do not have the brightness bar in the notification area, and that is a feature I used to use a lot, yet it isn't there, and I can't find it anywhere in settings. Please help on the second one and tell me if this is supposed to happen or not, also BTW in the boot loader it says System status: official, but it is S-OFF and the boot loader is unlocked.

1-Did you unlock the bootloader or it was unlocked when you got the phone? maybe you have the developer edition phone.
2-I think this option is not available for the M9+ you need to use an app like Brightness slider control or any other app from google play

Reply
About your first question: I was the one who unlocked the boot loader because I had the clean slate ROM installed and just reverted to stock, yet the stock ROM was a very old version and because it was S-OFF and the boot loader was unlocked I feared that I might not get the marshmallow update, yet I decided to try and install the update anyways, and to my surprise it worked flawlessly. Is this normal lol

Having ghost touch problems every now and then

My brother has a RETIN Athene running stock ROM with latest April patch and he's been complaining about frequent ghost touches. He'd often find his phone call, text someone at random, apps opening automatically and what not. I've suggested him to do a factory reset but I'd like to know if this can be solved without a factory reset. I had already unlocked his bootloader earlier to let him try a custom ROM as the stock was getting sluggish so if needed, a fastboot ROM can be flashed as well if it comes to that.
He recently got a QC 3.0 charger from Motorola but the problem has been going on before that (if he recalls correctly). Could this be because of the charge as I remember his G4 plus had some occasional ghost touches when his phone was new but that only happened while it was being charged.
I'm open to any advice and tips. His phone is barely usable now.
Update: I did a cache wipe from recovery a few minutes ago and noticed that his recovery was showing the the following info:
oem_locked
Software status: Official
Maybe I relocked the bootloader when flashing stock back then. Do I need to unlock bootloader again with "fastboot oem unlock"?

Ghost touch is no software issue. It is hardware. There is no solution. Just do not use your phone under sunset, and what about brightness - change to automatic, or if you wanna no automatic make less brightness 1/3-1/5 point. But again not use under sun
Edit: you can not relock bootloader if you already unlocked it. And if bootloder is unlocked, do not use ota updates (any: security and os). if you do, your phone will be bricked again

gioyocho said:
Ghost touch is no software issue. It is hardware. There is no solution. Just do not use your phone under sunset, and what about brightness - change to automatic, or if you wanna no automatic make less brightness 1/3-1/5 point. But again not use under sun
Edit: you can not relock bootloader if you already unlocked it. And if bootloder is unlocked, do not use ota updates (any: security and os). if you do, your phone will be bricked again
Click to expand...
Click to collapse
I see... I'll tell him to change the brightness to auto. Do you think upgrading to a new phone is better and the only available solution?
Also, after I flashed the fastboot ROM a while ago, he has updated to all the following OTAs without any issues, that's how he's on the April patch. No hard brick, nothing.

gioyocho said:
Ghost touch is no software issue. It is hardware. There is no solution. Just do not use your phone under sunset, and what about brightness - change to automatic, or if you wanna no automatic make less brightness 1/3-1/5 point. But again not use under sun
Edit: you can not relock bootloader if you already unlocked it. And if bootloder is unlocked, do not use ota updates (any: security and os). if you do, your phone will be bricked again
Click to expand...
Click to collapse
You can relock your bootloader. And the bricking kicks in only if you flash OTAs when rooted or on a custom recovery. Generally when you have system modifications.

corlatemanuel said:
You can relock your bootloader. And the bricking kicks in only if you flash OTAs when rooted or on a custom recovery. Generally when you have system modifications.
Click to expand...
Click to collapse
Well, no system modifications were done. That's why the OTAs were successful

downgrading problem oreo to nougat s8

hello,
i managed to get the phone back to get in download mode. stock everything, no root whatsoever. my goal is to root my phone and i have experience doing so but i guess i was just unlucky this time.
i tried searching allover the internet for a fix, searching xda etc.
first off: my device is running oreo 8.0 and it's type is G950FX.
I want to downgrade to 7.0 because FRP lock is on, i did turn on oem lock before starting however i am unable to log in to my old google account connected to my phone.
when i try to flash any bootloader i get SW REV CHECK FAIL DEVICE 2, BINARY 1. i tried almost any trick in the book like downloading 7.0 from sammobile, flashing using odin.
the things i run into when flashing are:
1.can't flash the bootloader, probably because of frp lock.
2. when i don't flash the bootloader for 7.0 i get dm-verity error 0x2.
3. when i only flash 8.0 oreo pda & csc and then flash 7.0 pda on top i do get to boot but i get encryption interrupted error.
4. i am able to boot in 8.0 but can't get past the frp.
i'm out of answers, i really hope anyone can help me out of this situation as i want to use my phone.
Help is much appreciated!
edit: i tried flashing multiple versions of android 7.0 but i keep getting sw rev check fail bootloader device 2 binary 1
i basicly want to do this, a downgrade: https://forums.androidcentral.com/s...s8-plus/878062-how-downgrade-oreo-nougat.html
the problem is i didn't sign out of google or samsung accounts before resetting to factory

You can't. You have a new bootloader v2.
A simple search gives you this answer, if you have u2 and CRED bootloader installed you are stuck. No way to go back anymore.

i'm on u2 and CRED bootloader. i did search for this indeed but i didn't want to give up.
do you think there will be ever be a way to get back into my phone again?

If you have FRP lock good luck. I haven't seen a way yet.

I know it's been 5 months and you've probably either gotten rid of the phone or it's sitting in a dusty bin somewhere, but have you tried Galaxy Reaper? It's a pretty legit FRP bypass tool.
Edit: Scratch that. It's apparently been patched since I last knew it to work. Just wanted to double check, and sure enough..

Fail Auth error when installing TWRP

I just got this phone today, and I want to root it and use custom ROM, but having troubles. Previously did this on an S6 and it was fairly easy.
Was following one guide, and was getting Fail Auth error from Odin.
Now trying to follow this guide:
https://forum.xda-developers.com/galaxy-s8/how-to/guide-how-to-install-twrp-root-galaxy-t3752480
But I don't even have OEM unlock in Developer options....
I'm still running 8.0 android. But an update is available, should I update to 9.0?
Please help
Edit:
In an effort to find a way to get the OEM unlock , i found this:
https://www.the***********.com/fix-missing-oem-unlock-toggle-samsung-galaxy-devices/
"The method below has stopped working on the newer firmware released in or after August 2018. In most situations, your device will be forcibly locked and the OEM Unlock toggle will be missing. Ensure that you insert a SIM card, connect to your network, and NOT REBOOT your Galaxy device for straight 7 Days (168 Hours)."
Is this accurate? Would it have to be a sim that's currently network activated if so? I was thinking of continuing to use the active sim in the s6, and an old sim in the s8 until I have it all set up. Also, if I have to wait a week, I probably might as well update to 9.0 that samsung is providing.
Thoughts? Suggestions?

ukie.int said:
I just got this phone today, and I want to root it and use custom ROM, but having troubles. Previously did this on an S6 and it was fairly easy.
Was following one guide, and was getting Fail Auth error from Odin.
Now trying to follow this guide:
https://forum.xda-developers.com/galaxy-s8/how-to/guide-how-to-install-twrp-root-galaxy-t3752480
But I don't even have OEM unlock in Developer options....
I'm still running 8.0 android. But an update is available, should I update to 9.0?
Please help
Edit:
In an effort to find a way to get the OEM unlock , i found this:
https://www.the***********.com/fix-missing-oem-unlock-toggle-samsung-galaxy-devices/
"The method below has stopped working on the newer firmware released in or after August 2018. In most situations, your device will be forcibly locked and the OEM Unlock toggle will be missing. Ensure that you insert a SIM card, connect to your network, and NOT REBOOT your Galaxy device for straight 7 Days (168 Hours)."
Is this accurate? Would it have to be a sim that's currently network activated if so? I was thinking of continuing to use the active sim in the s6, and an old sim in the s8 until I have it all set up. Also, if I have to wait a week, I probably might as well update to 9.0 that samsung is providing.
Thoughts? Suggestions?
Click to expand...
Click to collapse
You will need OEM unlocked in developer menu to flash twrp etc. As for getting unlocked you can try different variations of the date method. I have 2 S8's one Oreo one pie both with twlrp, etc got OEM by using a variation of the date method. If not you will have to wait.
As to updating to pie well personal choice my daily driver is still on Oreo while my other phone is on pie.
As to the method the thread you quoted is still valid but a bit outdated as it doesn't take into account of rrm state ( and kg state introduced in pie ). This guide is more up to date but is basically the same procedure but includes RMM fix.
https://forum.xda-developers.com/sa...w-to/guide-root-install-twrp-samsung-t3747535
Also be aware the have been updates to twrp as well.

Yea, I've been trying various date methods, but none of them worked for me. The lack of OEM is likely the issue here, so I'll probably just have to wait for a week to proceed

Re-Lock Bootloader on Galaxy Tab A T510?

Does anyone know if it is possible to re-lock the bootloader on the Galaxy Tab A T510? If so, would I begin with flashing back to stock firmware then disabling OEM unlock in developer options or following different steps? I certainly want to avoid bricking the device. I've searched for a solution but can't seem to find anything. Thanks!

dlehmanusa said:
Does anyone know if it is possible to re-lock the bootloader on the Galaxy Tab A T510? If so, would I begin with flashing back to stock firmware then disabling OEM unlock in developer options or following different steps? I certainly want to avoid bricking the device. I've searched for a solution but can't seem to find anything. Thanks!
Click to expand...
Click to collapse
You need to download the latest stock firmware either from Samsung or Sammobile and use Odin to flash it. DO NOT DISABLE OEM!!!! That has nothing to do with locking the bootloader. Flashing the stock ROM will do that. The OEM enable only disables the FRP lock which makes you login with the same google account used BEFORE a factory reset. If you are sure you know that account login and password, the FRP lock isn't a problem.
edit: The problem with the FRP lock is that people will often create a new google account login and password when first setting up their tablet. And because you only have to do that once, they tend to forget one or the other. Then, if they do a factory reset without the OEM enabled, they are locked out of the tablet.

Thanks for the detailed information and clarification. Your help is much appreciated!

The T510 doesn't have a locked bootloader.

ashyx said:
The T510 doesn't have a locked bootloader.
Click to expand...
Click to collapse
No, but it does "lock" the tablet from getting OTA updates.

I have reflashed the stock firmware however I'm still receiving the following message during boot..."The bootloader is unlocked and the software on this device cannot be verified". Is there a way to remove this message? I am planning to return the device and I want to reset everything. Thanks!