Database Users

How to enable OEM

Hello, so I downloaded my phones stock firmware (G9006v) and it had a lot of chinese bloatware and after some time it started saying "unfortunately google play services has stopped working" and after some time nothing from google works, even google play doesn't open up. I rooted my phone using CF auto root and then I wanted to install TWRP to install custom ROM, but then I learned that I need to enable OEM or bootloader, but when I go to developer settings there's no OEM unlocker or something like that, I watched a lot of videos, but couldn't figure it out. I saw that I can use ADB, but that's very complicated (for me). Isn't there a bit easier way to unlock bootloader? And by the way, when I go to recovery mode there's a line that says: reboot to bootloader, when I press on it, it just takes my to download mode (maybe it should do that, I don't know). I really need Your help, cause I want my phone back. Thank You

1. if not OEM-unlock, bootloader is unlocked (which is, for ALL S5 models except North American Verizon, T-Mobile AT&T, etc.)
2. flash a recovery in download-mode with Odin.

Galaxy Watch not compatible after unlocking bootloader, ANYBODY?

So yesterday I decided to attempt to root my 6T got passed to unlock bootloader process and hit a wall trying to complete TWRP install and root. So i bailed on the operation with just achiving bootloader unlock.
I turn my phone back on with the fresh install from unlocking the bootloader and got all my apps installed. I went to connect my Galaxy Watch that was connected and working fine prior to unlocking and now the Galaxy Wear App is telling me
that my "System Software is not compatible" WTF it was just working fine!! Technoloy Gods why must you loath me in such ways???:crying::silly:
Any one with insight to this problem i will say a prayer to the TECH GODS to protect from such curses!!:angel:
THANK yOU!

Probably need magisk to hide the bootloader unlock. Does Google pay work?

Works fine here. I restored the app via OnePlus switch from my other device and didn't have a single issue since then.

Flash another kernel and you'll be able to download the apps on the play store

bignu77 said:
So yesterday I decided to attempt to root my 6T got passed to unlock bootloader process and hit a wall trying to complete TWRP install and root. So i bailed on the operation with just achiving bootloader unlock.
I turn my phone back on with the fresh install from unlocking the bootloader and got all my apps installed. I went to connect my Galaxy Watch that was connected and working fine prior to unlocking and now the Galaxy Wear App is telling me
that my "System Software is not compatible" WTF it was just working fine!! Technoloy Gods why must you loath me in such ways???:crying::silly:
Any one with insight to this problem i will say a prayer to the TECH GODS to protect from such curses!!:angel:
THANK yOU!
Click to expand...
Click to collapse
Apk Mirror, Galaxy Gear Plug in, sideload and your good to go

My Gear S3 works flawlessly. I'm on the TMO variant with international 9.0.5 ROM, rooted.

Thanks Bud!
This was the route that work for me Thanks for the much needed insight!:highfive:
shremi said:
Flash another kernel and you'll be able to download the apps on the play store
Click to expand...
Click to collapse

Trying to enable WiFi Calling on my Note 4 N910V

I have a Galaxy Note 4 SM-N910V that I successfully rooted a couple of years ago. I played it safe and installed the stock ROM per the instructions, N910VVRU2BPA1_N910VVZW2BPA1_VZW [5.1.1 Stock FW]. I also have TWRP installed. The issue I'm having now is I'm working in a building that I get no service whatsoever, except at the front door. It's terrible, but someone told me I should use WiFi calling, since we have WiFi throughout the building. He had me all pumped up until I realized I didn't have the option for WiFi calling on my Note 4. After researching it, I believe you must have at least Android 6.0.1 (Marshmallow).
Can someone confirm this or tell me what I need to do so I can enable this wonderful feature called WiFi calling on my phone? This would be a godsend for me. I've been told that since I have TWRP installed I can pretty much install and test any roms, but I've been afraid to because I figured there has to be more to it than that.
Thank you!

Modify_inc said:
I have a Galaxy Note 4 SM-N910V that I successfully rooted a couple of years ago. I played it safe and installed the stock ROM per the instructions, N910VVRU2BPA1_N910VVZW2BPA1_VZW [5.1.1 Stock FW]. I also have TWRP installed. The issue I'm having now is I'm working in a building that I get no service whatsoever, except at the front door. It's terrible, but someone told me I should use WiFi calling, since we have WiFi throughout the building. He had me all pumped up until I realized I didn't have the option for WiFi calling on my Note 4. After researching it, I believe you must have at least Android 6.0.1 (Marshmallow).
Can someone confirm this or tell me what I need to do so I can enable this wonderful feature called WiFi calling on my phone? This would be a godsend for me. I've been told that since I have TWRP installed I can pretty much install and test any roms, but I've been afraid to because I figured there has to be more to it than that.
Thank you!
Click to expand...
Click to collapse
I'm almost certain that is a marshmallow feature. If you can see the option but it's grayed out and you can't turn it on then there's a fix for that. Otherwise you would need to upgrade to 6.0.1 and you'll have to go through the bootloader unlock method with a 6.0.1 bootloader is the only obstacle. If you don't update the bootloader your wifi won't work with the 6.0.1 roms.
Use this link for a guide to unlock your bootloader.
If you see the option but it's grayed out then follow this guide.

kevintm78 said:
I'm almost certain that is a marshmallow feature. If you can see the option but it's grayed out and you can't turn it on then there's a fix for that. Otherwise you would need to upgrade to 6.0.1 and you'll have to go through the bootloader unlock method with a 6.0.1 bootloader is the only obstacle. If you don't update the bootloader your wifi won't work with the 6.0.1 roms.
Use this link for a guide to unlock your bootloader.
If you see the option but it's grayed out then follow this guide.
Click to expand...
Click to collapse
Thank you for the reply and the link! I wish it were only greyed, but no, I do not have the option at all.
Regarding the bootloader, the link you provided shows in the title that it is for N910VVRU2CQI2, but I have N910VVRU2BPA1. I did originally have N910VVRU2CQI2, but to root my phone, I was told to flash the N910VVRU2BPA1_N910VVZW2BPA1_VZW [5.1.1 Stock FW] ROM to my phone.
Will I need to revert back to N910VVRU2CQI2 or can I still follow the instructions to unlock the bootloader with my current N910VVRU2BPA1 baseband version?
Thank you, again!

Modify_inc said:
Thank you for the reply and the link! I wish it were only greyed, but no, I do not have the option at all.
Regarding the bootloader, the link you provided shows in the title that it is for N910VVRU2CQI2, but I have N910VVRU2BPA1. I did originally have N910VVRU2CQI2, but to root my phone, I was told to flash the N910VVRU2BPA1_N910VVZW2BPA1_VZW [5.1.1 Stock FW] ROM to my phone.
Will I need to revert back to N910VVRU2CQI2 or can I still follow the instructions to unlock the bootloader with my current N910VVRU2BPA1 baseband version?
Thank you, again!
Click to expand...
Click to collapse
No you're already at the right starting point. Just start at the step where you flash the combination firmware of BPA1_CPD1. After that the process is the same as @ryanbg posted in the original unlock method.
If you want, these are the steps I did:
1. Power down, pull the battery for 3 seconds, then boot into Download Mode
2. Using Odin, flash the BPA1\CPD1 hybrid firmware
3. Once that's done flashing reboot to recovery and factory reset. Then reboot and let that firmware install
4. Once you've gotten past all the setup part you'll want to power off again and boot to download mode again
5. Using Odin, flash the CQI2 aboot and then reboot. From this point on the process is the same as before.
6. Enable developer options, turn on USB debugging and turn on "allow unknown sources" in the security settings.
7. At this point, you'll want to have your spare SD card in and go ahead and open a command window from the same location that you have the samsung_unlock_n4-fix file in. In my case it was in my download folder and the easiest way to do that is to open that window, hold down the shift button, then right click. You should see an option that says "open command window here" then click that to open.
8. Once you open the terminal enter this command: adb devices
9. Then this command: adb push samsung_unlock_n4-fix /data/local/tmp/
10. Then install kingroot and let it start rooting. Be sure to keep the terminal open and your phone connected.
11. Once kingroot starts the rooting process do not let the phone go to sleep. Just keep a finger on the screen.
12. When kingroot gets past 50 -60 percent, enter this command in the terminal: adb shell
13. If you enter adb shell and it gives an error or says your offline, just unplug the Usb from your phone and plug it right back in. Then enter the adb shell command
14. As soon as kingroot says you're rooted, enter this command in the terminal: su (You have to grant root permission on the phone and continue)
15. Then this command: cd /data/local/tmp/
16. Then this command: chmod 777 samsung_unlock_n4-fix
17. Then this command: ./samsung_unlock_n4-fix
18. Once the scripts starts it will ask you if you want to continue, just type out: yes
Then it will do it's thing, back up your bootloader, and then power your phone down when it's done.
19. Once powered down, PULL OUT YOUR SD CARD, and boot back into Download Mode
20. Using Odin, flash Twrp and immediately boot into recovery when Odin reboots your phone.

kevintm78 said:
No you're already at the right starting point. Just start at the step where you flash the combination firmware of BPA1_CPD1. After that the process is the same as @ryanbg posted in the original unlock method.
If you want, these are the steps I did:
Click to expand...
Click to collapse
Thanks for all your help, I finally got around to upgrading it. Everything went smooth and I am finally running MM 6.0.1 but unfortunately, I still can't find the feature for Wi-Fi Calling. I do now have a Advanced Calling option under Settings, which I believe you must have to use WiFi Calling, but I can't find the WiFi Calling anywhere to enable it. I must say, I'm really disappointed, yet still proud of myself that I didn't brick my phone in the upgrade process.
So, any suggestions as to why I can't find WiFi Calling on MM 6.0.1?

So no one has any ideas why I would still not have the wifi calling after installing the 6.0.1 MM? Is there a security or other update that I now need to install to get this feature? I installed the Jasmine v6 rom, if that makes any difference. Is there a way I can install 7.0 Nougat on this device, and would it likely provide the wifi calling feature or likely be a waste of time and effort?
I'm using Safelink with my Verizon phone, but they are no help, though they do say they support wifi calling as long as I can enable it on the phone. Is it possible Verizon could tell me what I need even though I don't have service with them but do use their towers?
Sorry for so many questions, I just really need wifi calling and can't understand why I don't have the option for it using 6.0.1.

I found an app named WiFi Calling while browsing through my phone directory. It looks like a system file, so shouldn't that mean the phone should have it? Is my Jasmine ROM keeping it from working or is it likely something else?
I'm now using Jasmine v7, if that makes any difference.

Help! Now my wife has no phone
kevintm78 said:
No you're already at the right starting point. Just start at the step where you flash the combination firmware of BPA1_CPD1. After that the process is the same as @ryanbg posted in the original unlock method.
Click to expand...
Click to collapse
I tried to do the same for my wife since she has the same exact phone running 5.1.1 with root. Everything appeared to be going fine, but after performing the last step (flashing the N910VVRU2CQL1_PartialFirmware_DevEd.tar.md5.7z via Odin) and rebooting the phone, it now goes into a boot loop. It will load the Samsung logo for about 20-30 seconds, then reboot every time. I can still access TWRP from recovery and I have cleared Dalvik and Cache, but it still does the same thing. I also reflashed JasmineROM_v7.0_N910VVRU2CPF3, cleared Dalvik and Cache again, but still the same boot loop. It does still show the word Custom under the Samsung logo at boot, so I assume that is good news. Doesn't that mean the bootloader is still unlocked or something?
If it helps, the part of the process that had me concerned was after unlocking the bootloader. I powered off the phone, and then tried to load the recovery menu so I could factory reset the phone and clear the cache, but the recovery menu never appeared. It did show the Android fix-it guy for the recovery for about 10 seconds then a short progress bar under it for about 5 seconds, then it went straight to the Samsung logo. It never did give me the actual recovery menu, just the Android fix-it guy animation, which I thought was odd because I've always had the recovery menu pop up after that.
I made a complete backup using TWRP before attempting this upgrade. So, can I just restore it or are there other steps I need to perform before I attempt to revert back?

Did you ever get this resolved? I have been having an issue since mid-July where my phone does not send or receive texts or calls within half a mile radius of my office but otherwise works great everywhere else. I don't have to be in the building...I can be standing in the parking lot, parked at a nearby building/area, or driving down the street in vicinity of the area and nothing. When I try to send a text, I get a message stating there's no service. When I try to call, the phone goes from 4G with four bars to 4G with zero bars and is stuck on "dialing". When I end the call, it goes back up to four bars.
I have tried contacting Verizon many times and they tell me I need to enable WiFi calling but I don't have the Advanced Calling option in my settings. I am also running 5.1.1 on a rooted SM-N910V. Today when I spoke to them, they told me that even though my phone shows 4G, I really only had 1G service. I find this explanation ridiculous because if this was the case, I would have problems in other areas too and not just in the middle of the 8th largest urbanized area in Louisiana (while elsewhere in the same urbanized area, the phone works great). They told me I needed to do a system update which will cause me to lose root.

HTC 10 Home button/sensor not working?

HI,
I just got a NIB, HTC 10 Verizon phone that came with Oreo. I immediately unlocked the bootloader, installed latest TWRP and installed Lineage 14.1 Nougat...same version that's running successfully on another HTC 10 VZW I own.
However I just noticed the home button/sensor apparently isn't working, nothing happens when I press or hold it. I unlocked it so fast I really don't know if it worked in the stock rom or not. I tried installing the microg version of Lineage 14.1 and am seeing same issue. I can't find any setting I might have forgotten about to enable it, and the settings there are for it (long press etc) are set.
Does anyone know on an HTC 10 with latest Verizon Oreo, did something change in the firmware so that I need to run an Oreo rom to make it work?
Is there anyway I can test the home button in a terminal or some such to see if it's physically not working? It just seems unlikely to me that a new phone would have a DOA button/sensor and feel like i'm missing something.
thanks

generalnod said:
HI,
I just got a NIB, HTC 10 Verizon phone that came with Oreo. I immediately unlocked the bootloader, installed latest TWRP and installed Lineage 14.1 Nougat...same version that's running successfully on another HTC 10 VZW I own.
However I just noticed the home button/sensor apparently isn't working, nothing happens when I press or hold it. I unlocked it so fast I really don't know if it worked in the stock rom or not. I tried installing the microg version of Lineage 14.1 and am seeing same issue. I can't find any setting I might have forgotten about to enable it, and the settings there are for it (long press etc) are set.
Does anyone know on an HTC 10 with latest Verizon Oreo, did something change in the firmware so that I need to run an Oreo rom to make it work?
Is there anyway I can test the home button in a terminal or some such to see if it's physically not working? It just seems unlikely to me that a new phone would have a DOA button/sensor and feel like i'm missing something.
thanks
Click to expand...
Click to collapse
It doesn't work because you need to have Nougat firmware in order to run LOS 14.1. So you can either downgrade your firmware, or go to LOS 16.
But I'm curious how you could have possibly unlocked the bootloader on a Verizon 10. The only way to unlock the bootloader on that variant is to have s-off, which in of itself would require you to send the phone to the Sunshine team if you're on Oreo...

Tarima said:
It doesn't work because you need to have Nougat firmware in order to run LOS 14.1. So you can either downgrade your firmware, or go to LOS 16.
Click to expand...
Click to collapse
Thanks, I was about to return the phone, seems like an odd quirk doesn't work on 14.1 does on 15.1 and 16. I do not have s-off so I don't think I can downgrade the firmware, without sending it to sunshine (think i read can also send to htc?) first.
However I did find a LOS 15.1 unofficial rom, that so far seems to be working, but haven't popped in the sim yet.
https://forum.xda-developers.com/ht...lineageos-15-1-unofficial-builds-pme-t3808812
And you're correct home button works! I might see if I can compile a Microg version of that 15.1 LOS
Tarima said:
But I'm curious how you could have possibly unlocked the bootloader on a Verizon 10. The only way to unlock the bootloader on that variant is to have s-off, which in of itself would require you to send the phone to the Sunshine team if you're on Oreo...
Click to expand...
Click to collapse
I followed what I think is pretty much the standard procedure
https://wiki.lineageos.org/devices/pme/install
The only unexpected parts where enable oem unlock being greyed out, requiring a connection to the internet at which point it became ungreyed and let me check it. Also in those instructions there's some confusion regarding 'fastboot' / bootloader / download mode, things need to be done in download mode now.
https://forum.xda-developers.com/on...ken-failed-t3263170/post78869656#post78869656
thanks for your help

generalnod said:
Thanks, I was about to return the phone, seems like an odd quirk doesn't work on 14.1 does on 15.1 and 16. I do not have s-off so I don't think I can downgrade the firmware, without sending it to sunshine (think i read can also send to htc?) first.
However I did find a LOS 15.1 unofficial rom, that so far seems to be working, but haven't popped in the sim yet.
https://forum.xda-developers.com/ht...lineageos-15-1-unofficial-builds-pme-t3808812
And you're correct home button works! I might see if I can compile a Microg version of that 15.1 LOS
I followed what I think is pretty much the standard procedure
https://wiki.lineageos.org/devices/pme/install
The only unexpected parts where enable oem unlock being greyed out, requiring a connection to the internet at which point it became ungreyed and let me check it. Also in those instructions there's some confusion regarding 'fastboot' / bootloader / download mode, things need to be done in download mode now.
https://forum.xda-developers.com/on...ken-failed-t3263170/post78869656#post78869656
thanks for your help
Click to expand...
Click to collapse
Glad you were able to solve it.
What the last part tells me is that it wasn't an official Verizon device, since as I said you can't enable oem unlocking and unlock the bootloader on those. Nevertheless it seems you have an unlocked bootloader anyway, which is good. With that said, you can probably downgrade even without s-off, and there is a (risky) procedure on how to do that around. I don't think you'll need it now though since you're up and running.

Same same?
generalnod said:
Thanks, I was about to return the phone, seems like an odd quirk doesn't work on 14.1 does on 15.1 and 16. I do not have s-off so I don't think I can downgrade the firmware, without sending it to sunshine (think i read can also send to htc?) first.
However I did find a LOS 15.1 unofficial rom, that so far seems to be working, but haven't popped in the sim yet.
https://forum.xda-developers.com/ht...lineageos-15-1-unofficial-builds-pme-t3808812
And you're correct home button works! I might see if I can compile a Microg version of that 15.1 LOS
I followed what I think is pretty much the standard procedure
https://wiki.lineageos.org/devices/pme/install
The only unexpected parts where enable oem unlock being greyed out, requiring a connection to the internet at which point it became ungreyed and let me check it. Also in those instructions there's some confusion regarding 'fastboot' / bootloader / download mode, things need to be done in download mode now.
https://forum.xda-developers.com/on...ken-failed-t3263170/post78869656#post78869656
thanks for your help
Click to expand...
Click to collapse
I bought my HTC 10 Verizon on eBay new other which they explained is either a store model or excess stock.
HTC 10 32GB 6545LVW Glacier Silver (Verizon)+Unlocked GSM Smartphone Cell Phone https://ebay.us/rLPGq8
download mode said that it was locked s-on.
htc_pmewl
mid-2ps650000
this came with android 6.0.1
oem unlock was not listed in the developer options.
The sunshine app APK was able to gain temporary root and confirm compatibility but failed to unlock on the first attempt. I had many items disabled so I did a factory reset and was able to gain S off using the app but my download mode still says locked.
I installed TWRP through a DB and was able to then install 14.1 15.1 and 16 lineageos.
I tried 16.O then switch to 15.1 then switched to 14.1 then back to 15.1 and then back to 14.1 via twrp backup.
Everything works great except my home button and fingerprint sensor did not work on 15.1 or 16. They both work on 6.0.1 stock and lineageos 14.1. I tried on 15.1 and 16 to enable the additional buttons to use the fingerprint button as the home button and it still did not work.
I'm also not able to backup system image the air says that it's mounted as read only. It seems to get about 90% done and says fails to write in the log.
I can back up everything else using TWRP such as data and system just not system image.

resolved
benjuken said:
I bought my HTC 10 Verizon on eBay new other which they explained is either a store model or excess stock.
HTC 10 32GB 6545LVW Glacier Silver (Verizon)+Unlocked GSM Smartphone Cell Phone https://ebay.us/rLPGq8
download mode said that it was locked s-on.
htc_pmewl
mid-2ps650000
this came with android 6.0.1
oem unlock was not listed in the developer options.
The sunshine app APK was able to gain temporary root and confirm compatibility but failed to unlock on the first attempt. I had many items disabled so I did a factory reset and was able to gain S off using the app but my download mode still says locked.
I installed TWRP through a DB and was able to then install 14.1 15.1 and 16 lineageos.
I tried 16.O then switch to 15.1 then switched to 14.1 then back to 15.1 and then back to 14.1 via twrp backup.
Everything works great except my home button and fingerprint sensor did not work on 15.1 or 16. They both work on 6.0.1 stock and lineageos 14.1. I tried on 15.1 and 16 to enable the additional buttons to use the fingerprint button as the home button and it still did not work.
I'm also not able to backup system image the air says that it's mounted as read only. It seems to get about 90% done and says fails to write in the log.
I can back up everything else using TWRP such as data and system just not system image.
Click to expand...
Click to collapse
-------------------------------------------
after the steps above, I installed this
3.18.605.13_combined_NoBoot_Twrp3.2.1-4_firmware.zip using htc_fastboot
wiped
then this
lineage-16.0-20190310-UNOFFICIAL-pme.zip using twrp from sd card
open_gapps-arm64-9.0-aroma-20190316 (add more zips in the same install)
now the fingerprint setup and home button are working without turning it on in settings > system > additional buttons.
still locked s-off is showing in download mode.
all fixed

DeGoogle SM-P555 without MicroG or Nanodroid?

My goal is to remove Google bloatware and trackers from my tab while still being able to use GMail and Google Drive, generally improve my privacy. However I ran into multiple issues following this tutorial for my SM-P555:
I don't know and I don't think I successfully unlocked the bootloader. There is no OEM unlock option and I can't reboot my device into fastboot and use the fastboot command to unlock it.
Can't check info through dialing codes like *#*#7378423#*#*. Calling it says that the number isn't registered on my network.
Rebooting into bootloader reboots into download/Odin mode
Fastboot can't detect my device
When I installed Magisk through TWRP (seems like a successful installation) but when I check the Magisk app, it says "Installed N/A"
Direct installation of Magisk fails
Selecting and patching my ROM's boot.img fails in Magisk too
However, when checking with a Root Checker app, it says that my device has root access.
When running SmaliPatcher, it generates folders and not a ZIP (but that's probably because the Knox patch class wasn't found and just isn't supported and maybe I should just uncheck it)
My tablet is now getting hot even though there is no background activity
These are the issues that I can remember from the top of my head. I've been at this for more than 2 days now. Can anyone help me?
To anyone also with the same model and issues, please feel free to share them.