So you have decided, or maybe trying to decide, to invest a good chunk of money into a Developer Edition S5 instead of a retail version. Here are a few tips and general information that you need to know before you start to "tinker" with the Developer Edition S5:
1) The Developer Edition S5 can only be obtained from the Samsung online store (site). When you receive the S5 you should understand that it is going to look, feel and perform exactly like the retail version of the S5. The only way you can tell the difference is to pull the battery and look for the words "Developer Device" printed on the S5's board under the battery. You will have all the bloat etc that a retail version has. The only difference is that your bootloader, unlike the retail version, is unlocked. The phone will come with the latest version of Android that Samsung currently supports...the same version as the retail S5.
2) After your initial boot, and before you do anything else, go to settings>security and disable (uncheck) the Reactivation Lock. If you don't do that before "tinkering" with your phone you stand a very good chance of successfully bricking your phone while flashing a recovery or rooting your phone. Next go to About Phone>Build Number and tap it about 6-7 times and enable Developer Option and then enable USB Debugging.
3)A word of advice: Never, never take an OTA update. If you do, you stand a real good chance of locking your bootloader. Samsung has never released a OTA update specifically for their Developer Edition phones. Allowing a retail OTA update to download and install on you Developer Edition will most likely lock your bootloader for good. Sending it back to Samsung will not help you. They will not unlock your phone, and you cannot unlock your phone. You are stuck with a very expensive retail version of the S5. Keeping the Developer Edition up to date is not a problem. Our developer community does a great job taking the latest updates and creating ROMs that are safe to flash on our devices. It may take them a day or two, but it happens.
4) Installing a custom recovery...the first step: First, download and install the latest Samsung drivers on you PC. Then download and install on your PC the latest version of ODIN. Version 3.07 also works if that is what you already have. I recommend TWRP as the best custom recovery to use. Download the latest version of TWRP and place it on you PC. Start ODIN. Power off your phone and then holding down the volume down - button and the power button boot into Download Mode. Once in Download Mode connect your phone to your PC using the supplied USB/charging cable. Wait for ODIN to recognize your phone (phone info will appear in the ID:COM window in ODIN). In the Message window in ODIN find the TWRP .tar you downloaded and highlight it with your cursor. Select the PDA block in ODIN. Now select start. Allow ODIN to do its thing. Do not disconnect your phone until you get the Green Pass notification in ODIN. Disconnect your phone and reboot. You now have a custom recovery installed. NOW DO A BACKUP using your TWRP recovery. Do it right now!!
5)Rooting: After installing a custom recovery (TWRP), download the latest version of SuperSU and place it in your internal storage or external sdcard. Boot your phone into Recovery, wipe cache and delvek, you can also do a Factory Reset if you choose, then select install, find the SuperSU .zip, and flash it. Reboot. Now you are rooted. You can confirm (recommended) that you are rooted by installing Root Checker from the Play Store and running it.
6). OK, you have a custom recovery and rooted. You can now take advantage of the benefits of an unlocked bootloader. There are a number of good ROMs you can flash in the Android Development Section. Caution...Do not flash a ROM that says "Retail". Most developers will say whether it is safe for Developer Phones. There are also some AOSP ROMs that are "Works In Progress" in the Unified Section. You can flash those, but they are not quite ready for prime time yet.
7) Just a reminder: Do not take an OTA. Do not flash Retail Firmware.
Thanks!
Been reading and reading, and reading some more to learn all I can about my Developer Edition. Appreciate this post, and the concise information. :good:
ruh roh
I had S5 dev edish for 2+ years with TWRP + rooted 4.4.2, and life was great. Then when I went to sell it I thought I would update it first to 6.0.1.
1.) Was that a horrible mistake??
2.) If I locked the bootloader by flashing stock 6.0.1, how can I confirm this?
3.) Is my only option to have Samsung revert/unlock the phone to 4.4.2? Or can I root 6.0.1?
4.) If you were selling it on ebay, I assume it's more valuable as 4.4.2 root/unlock than dumb retail 6.0.1?
P.S. I've spent over an hour trying to find these answers myself.
If you have a dev ed then it shouldn't lock the bootloader even if you go to MM.
It's not really worth more one way or the other unless someone is looking for a device already rooted, ready to go.
To check if locked:
Power off
Hold home button, down volume button, and power together
At warning screen, press up volume button
On "Downloading" screen - look to see if it says "Mode: Developer"
(If it does, you're unlocked)
If you're locked, I believe you can just go back to Lollipop, root, and unlock again using this thread:
http://forum.xda-developers.com/ver...t/rd-unlocking-galaxys-s5-bootloader-t3337909
Add this to the list - BACK UP YOUR ABOOT AND PUT IT IN A SAFE PLACE
OK, here goes. I am running COS 12.1, rooted, with an unlocked bootloader. I recently upgraded to Android Pay after using Google Wallet for NFC payments for years on my old GS4 and my OnePlus One.
At first, I was unable to add my payment card due to being rooted. Easily fixed, I unrooted using SuperSU to do a full unroot and was able to add my card and complete the app setup.
The showstopper is that whenever I try to use it at a merchant, I end up with a screen that says Confirm your password - you must unlock to use Android Pay. No matter how many times I enter my password it just keeps asking over and over. I disabled the quick unlock feature under lock screen settings just in case that was the issue, but it made no difference. An ongoing support case with Google just came back with the following:
"The specific error message that you saw means that your device can't support Android Pay's advanced security. It seems that the phone manufacturer has modified the operating system to the point where it is no longer compatible with our software. You may want to use Android Pay on a different device for the most secure payments."
So, has anyone running COS 12.1 had any luck with Android Pay? Thoughts, comments, suggestions are all welcome.
Hurricane Andrew said:
OK, here goes. I am running COS 12.1, rooted, with an unlocked bootloader. I recently upgraded to Android Pay after using Google Wallet for NFC payments for years on my old GS4 and my OnePlus One.
At first, I was unable to add my payment card due to being rooted. Easily fixed, I unrooted using SuperSU to do a full unroot and was able to add my card and complete the app setup.
The showstopper is that whenever I try to use it at a merchant, I end up with a screen that says Confirm your password - you must unlock to use Android Pay. No matter how many times I enter my password it just keeps asking over and over. I disabled the quick unlock feature under lock screen settings just in case that was the issue, but it made no difference. An ongoing support case with Google just came back with the following:
"The specific error message that you saw means that your device can't support Android Pay's advanced security. It seems that the phone manufacturer has modified the operating system to the point where it is no longer compatible with our software. You may want to use Android Pay on a different device for the most secure payments."
So, has anyone running COS 12.1 had any luck with Android Pay? Thoughts, comments, suggestions are all welcome.
Click to expand...
Click to collapse
Yes I have also fyi - there is also another thread talking bout Android pay and what we got it working on and which roms it does not work with. Did you try it with root enabled?
playya said:
Yes I have also fyi - there is also another thread talking bout Android pay and what we got it working on and which roms it does not work with. Did you try it with root enabled?
Click to expand...
Click to collapse
I first tried it with root enabled, then when that didn't work I did the full unroot. I will try with just disabling SU over the weekend and see what happens.
Hurricane Andrew said:
I first tried it with root enabled, then when that didn't work I did the full unroot. I will try with just disabling SU over the weekend and see what happens.
Click to expand...
Click to collapse
yeah with stock no need to full unroot. you can have bootloader unlocked root added and all that. Its just when you set it up make sure its stock root and not by using the supersu zip file. My findings was when I flashed Supersu it did not work but if I flashed stock rom then let TWRP inject root it worked. Of course I unchecked the option in supersu set up Android Pay then found one of those coke machines that take Android pay and tested it out.
The gps in my handset is not working properly and I've tried switching between different profiles, updating firmware and also turning on performance mode but nothing works.
After some research, i found that there might be a problem with the device's gps.config file, to alter which, I'd have to root the device.
I've had experience with rooting with my previous phone Moto E 1st gen, and i've also gotten permission to unlock the bootloader from Xiaomi but the stupid tool keeps getting stuck at 50% and displays "Couldn't verify device".
I've even looked that up and tried logging out and logging in back in my Mi Account and also tried shutting down and again booting it into the fastboot mode and unlocking again but I haven't been able to do so till now.
Can somebody help me? I'm not really familiar with the Mi's whole rooting scene. For now, unlocking the bootloader or rooting is not even required. The only thing that matters right now is my gps to work.
thwartfulGUY said:
The gps in my handset is not working properly and I've tried switching between different profiles, updating firmware and also turning on performance mode but nothing works.
After some research, i found that there might be a problem with the device's gps.config file, to alter which, I'd have to root the device.
I've had experience with rooting with my previous phone Moto E 1st gen, and i've also gotten permission to unlock the bootloader from Xiaomi but the stupid tool keeps getting stuck at 50% and displays "Couldn't verify device".
I've even looked that up and tried logging out and logging in back in my Mi Account and also tried shutting down and again booting it into the fastboot mode and unlocking again but I haven't been able to do so till now.
Can somebody help me? I'm not really familiar with the Mi's whole rooting scene. For now, unlocking the bootloader or rooting is not even required. The only thing that matters right now is my gps to work.
Click to expand...
Click to collapse
You should try flashing a DEVELOPER ROM Provided by xiaomi itself.
A DEVELOPER ROM already have root permissions, and Even doesn't void your warranty.:fingers-crossed:
And after rooting you can try changing the gps.conf file located in root/system/etc .... (If you're in India) you can freely ask me for Indian configured gps file
sarfaraax said:
You should try flashing a DEVELOPER ROM Provided by xiaomi itself.
A DEVELOPER ROM already have root permissions, and Even doesn't void your warranty.:fingers-crossed:
And after rooting you can try changing the gps.conf file located in root/system/etc .... (If you're in India) you can freely ask me for Indian configured gps file
Click to expand...
Click to collapse
Actually I did flash the miui 8 developer rom but there was no option to enable root in either the developer options or security options.
I HAVE A SM-G930F S7
GOT IT FROM ONE OF THOSE RENT TO OWN PLACES AND IT IS STUCK WITH THERE FIRMWARE
and i can not upgrade to the latest nougat build
was wondering how do i determine what the factory shipped firmware should be so i could download
it from sammobile... but i can not find my region code on the site..
I LIVE IN SAGINAW,MICHIGAN USA
any help would be appreciated
BASEBAND: G930FXXU1APB4
BUILD NUMBER:MMB29K.G930FXXU1APB4_RAC_V1.0.0
WOULD LIKE TO BE ABLE TO UPGRADE
I'm coming across the same issue - did you ever figure it out? I'm thinking of flashing a stock firmware (but can only find an updated one), then rooting. But without being able to access developer options, I'm leary of doing even that.
stgibson said:
I'm coming across the same issue - did you ever figure it out? I'm thinking of flashing a stock firmware (but can only find an updated one), then rooting. But without being able to access developer options, I'm leary of doing even that.
Click to expand...
Click to collapse
It might depend on who your carrier is.
Not being able to access developer options? What are you talking about? Go to system settings>about>build number or system settings>about>software info>build number or something similar, find the "build number" or "build no.", tap it 7 or 8 times quickly untli you see the notification that you've unlocked developer options.
Sent from my LGL84VL using Tapatalk
Droidriven said:
It might depend on who your carrier is.
Not being able to access developer options? What are you talking about? Go to system settings>about>build number or system settings>about>software info>build number or something similar, find the "build number" or "build no.", tap it 7 or 8 times quickly untli you see the notification that you've unlocked developer options.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
Thanks, @Droidriven! I'm going to be using it on AT&T, then on China Unicom. And I want it unlocked. Thus why I got the G930f, not g930a. This phone hasn't locked me out of the system (yet). I did manage to find a build with the same base as mine (G930FXXU1APB4 at https://updato.com/firmware-archive-select-model?record=07054BA22E5811E6815B0CC47A44B7B2). But my build is MMB29K.G930FXXU1APB4_RAC_v1.0.0, and device status says "custom". When I go into the software info, I can tap on everything else and get a "greyed" response, but not when I tap on build number. Seems to be a locked down version. [Edit: downloading a "developer options" app lets me get to it.] That said, I think this thread (https://forum.xda-developers.com/galaxy-s7/how-to/s7-sm-g930f-rent-center-lock-workaround-t3518682) may work, even though my device hasn't locked me out like some people have had. I'll try that method this morning with the similar stock build and see.
My main concern is causing an issue because of not having USB debugging and /or OEM unlock enabled. Especially if I go straight to a newer version that may require the pin unlock for boot (I saw one of the stock rom pages, can't find it again right now, with 8.0 roms had warnings all over that pin unlock on boot had to be enabled prior to flashing, otherwise you'd flash it and it'd ask for the pin and no luck).
So do you see any problem being able to flash according to the link above without the developer options enabled? [Edit: now that I can get access to developer options through the app, I'm less worried.]
For future reference, this worked, following the instructions (modified slightly here) by bishopag at https://forum.xda-developers.com/galaxy-s7/how-to/s7-sm-g930f-rent-center-lock-workaround-t3518682 worked, using the G930FXXU1APB4 baseband at https://updato.com/firmware-archive-select-model?record=07054BA22E5811E6815B0CC47A44B7B2.
1. Install one of the "bootloader options" from Play Store, use it to ensure that OEM unlock and USB debugging (optional?) are enabled
2. Download the Stock firmware of your choice from Sammobile [or from above link]
3. Unzip/unrar it and pull out the BL and CP for bootloader and modem
4. Grab TWRP from https://dl.twrp.me/herolte/twrp-3.2.3-0-herolte.img.tar.html
5. Grab Odin 3.12 from http://odindownload.com/SamsungOdin/#.WFBEZsmB3mE
6. Put the Device in Download Mode (Hold Vol Down, Power, Home)
7. Use Odin to flash TWRP to the device (AP)
8. Reboot into Recovery Mode (Hold Vol Up, Power, Home)
9. In TWRP use Advanced Wipe to Wipe everything except the SD Card. If it fails use Reset Data first, then Wipe
10. Go to Advanced -> Terminal Command -> hit "Select"
11. type these comands
dd if=/dev/zero of=/dev/block/sda11
dd if=/dev/zero of=/dev/block/sda13
(Note: I got a message that storage was full, but on inspection I could see that the data had been written based on input & output bytes)
12. Do a factory reset with the recovery
13. Reboot into Download mode from TWRP Reboot menu
14. Use Odin to Flash the BL, CP, and AP
15. That's it. Wait for it to boot and setup (might take 5-10 min)
stgibson said:
Thanks, @Droidriven! I'm going to be using it on AT&T, then on China Unicom. And I want it unlocked. Thus why I got the G930f, not g930a. This phone hasn't locked me out of the system (yet). I did manage to find a build with the same base as mine (G930FXXU1APB4 at https://updato.com/firmware-archive-select-model?record=07054BA22E5811E6815B0CC47A44B7B2). But my build is MMB29K.G930FXXU1APB4_RAC_v1.0.0, and device status says "custom". When I go into the software info, I can tap on everything else and get a "greyed" response, but not when I tap on build number. Seems to be a locked down version. [Edit: downloading a "developer options" app lets me get to it.] That said, I think this thread (https://forum.xda-developers.com/galaxy-s7/how-to/s7-sm-g930f-rent-center-lock-workaround-t3518682) may work, even though my device hasn't locked me out like some people have had. I'll try that method this morning with the similar stock build and see.
My main concern is causing an issue because of not having USB debugging and /or OEM unlock enabled. Especially if I go straight to a newer version that may require the pin unlock for boot (I saw one of the stock rom pages, can't find it again right now, with 8.0 roms had warnings all over that pin unlock on boot had to be enabled prior to flashing, otherwise you'd flash it and it'd ask for the pin and no luck).
So do you see any problem being able to flash according to the link above without the developer options enabled? [Edit: now that I can get access to developer options through the app, I'm less worried.]
Click to expand...
Click to collapse
I'm very familiar with flashing stock firmware on Samsung devices but I'm not familiar with the things that you are freaking out about.
Flashing a full stock firmware "should" remove the custom binary, it should say "official" when you're done.
As for build number, that shouldn't matter so much, as long as you are flashing a firmware that is meant for your model number. If you'll be using it on AT&T then flashing the AT&T stock firmware for G930F "should" work.
I've never encountered the issues that you are running circles around so I'm not sure my advice will do you any good. I don't want to walk you into any issues that I'm not sure I can help you solve.
Edit: It looks like the member that posted above has the solution you need, give it a try.
Sent from my LGL84VL using Tapatalk
PREWARNING
THIS GUIDE IS !!ONLY!! FOR N9600 (INTERNATIONAL Snapdragon Model)
DO NOT ATTEMPT ON SPRINT, VERIZON, T-MOBILE, AT&T, OR ANY OTHER US (United States) MODEL PHONE.
BEWARE!! N960U or N960U1 HAS A LOCKED BOOTLOADER WHICH CAN NEVER BE UNLOCKED!
IF YOU ATTEMPT TO ROOT ON ANY US MODEL, YOU WILL BRICK YOUR PHONE!
If you have an N9600 international snapdragon model, please proceed. If not, read for your pleasure or future consideration but DO NOT attempt on a US model.
This guide can also be useful for N960F or N960FD international Exynos models, but you would have to change some things like use the right links.
==================================================================================================
Intro Notes:
I REPEAT: THIS GUIDE IS !!ONLY!! FOR N9600 (INTERNATIONAL Snapdragon Model)
If you have an N9600 international snapdragon model, please proceed. If not, read for your pleasure or future consideration but DO NOT attempt on a US model.
After much thought, research, reading, and contemplation, between Note 8, Galaxy S9+, and Note 9, I have decided on the Note 9.
Out of the available options for rooting, there are the devices, N960F, N960FD, and N9600.
Of course, N960F N960FD are Exynos. Unfortunately, these will not work on Verizon, so I would have to switch to T-Mobile. To stay on Verizon it would have to be N9600.
Ultimately, I decided on N9600. Why? Because with Detonator, I can root the N9600 on Verizon, and it's the only model that I can use on Verizon fully rooted. (There is a partial root on N960U, the US Snapdragon variant, but the root is only partial and will have bugs or may not wok.) I could root with a partial root the Note 8 US version, but it is not that much cheaper and it would only be a partial root, so I decided on N9600.
You can root fine on the Exynos versions, but you could not use Detonator for WIFI calling and other features on Verizon.
Rooting Guide
0. Battery must be above 82% before rooting.
1. Root N9600 using TWRP method (Beta)
PLEASE READ ALL INSTRUCTIONS THERE FOR ROOTING.
https://forum.xda-developers.com/ga...ecovery-twrp-galaxy-note9-snapdragon-t3845536
(Official XDA Magisk Install Guide, don't follow directly just reference)
2. RMM State Fix (Prevent "Prenormal")
IMMEDIATELY after getting into TWRP, flash the RMM-State_Bypass_Mesa_v2.zip (linked below).
If you do not, then you will get locked out for 7 days in the event you flash anything or flash a new OS or downgrade to Oreo, etc.
You have to do this EVERY TIME you flash something to prevent RMM state to going to "Prenormal" which means wait 7 days before you can flash any non-samsung firmware.
3. How to fix: Stuck on Prenormal and didn't bypass, OEM Unlock missing
You might be stuck because you didn't do the RMM bypass above. In this event, you will be blocked from flashing custom binaries including TWRP. The only thing you will be able to flash is original Samsung firmware.
How to bypass now? There are two solutions for solving Prenormal RMM state. I have done both successfully. There is a third but it rarely seems to work (date hack, available at many sites.)
METHOD 1: Long way around. Wait 7 days.
First wipe your whole device again and reflash your original OS in ODIN. If you don't do this then it's possible that after 7 days, OEM unlock will not show up.
Now wait 7 days.
Do not reboot your device, just for good measure. I did reboot my device, several times, and it still appeared after 7 days and a reboot. Don't know if you'll have the same luck.
The second time after turning on OEM Unlock, however, when it wiped my device, I did NOT reflash the whole OS again. And, after 7 days again, it did NOT show up.
METHOD 2: I waited 7 days, but no OEM unlock! Solution: Chimera application for windows. NOT FREE!
I was tired of waiting so I decided to try it, and it worked.
Activate Developer options
Activate USB Debugging (in Developer Options)
DISABLE "Verify apps via USB" (in Developer Options)
Go to https://chimeratool.com/
Buy the 3 days trial.
Download after paying in PayPal.
Install full application and all drivers. Don't customize it just install full.
Put your phone into Download mode
Turn off phone.
Hold Bixby & Volume Down
Plug phone into PC.
Press volume up at prompt. Download mode will be activated.
Now in Chimera application in Windows it will find your phone.
Choose the option "UNLOCK".
Choose the sub option, "RMM Unlock".
SUCCESS!! NO WAITING!! OEM Unlock activated. Worth every penny in my opinion (because it wasn't too many pennies).
Proceed to install TWRP and DO NOT FORGET TO INSTALL RMM BYPASS AFTER EVERY SINGLE FLASHING OF ANYTHING!!
4. After rooted, flash Detonator
File: Verizon EFS/CSC Detonator: Detonator v3 for Oreo 8.1 (linked in file list below)
(There is no Detonator for Pie on Verizon as of this writing, only Oreo)
0. Download DETONATOR_XXX_OREO_VZW_EFS-CSC_vx.x_INT_TEKHD.zip to your phone.
Maybe just copy to your SD card, easiest way.
In order to flash detonator, in TWRP select every box on the Mount screen (OTB will not be available unless you have one connected, but everything else).
Backup all partitions via TWRP.
Then go to Install (in TWRP) and flash the zip file for Detonator which applies to you. (Do NOT flash right after flashing a ROM!; First boot ROM at least one time… then go back to TWRP and flash Detonator)
After you successfully flash detonator and there are no errors, now if you want to remove the Verizon boot screen now go ahead and flash (through Install screen in TWRP) the Samsung BootAnimation zip on the Detonator website. This will replace your boot with the stock black samsung boot.
After doing these, please remember to flash the RMM State zip file. Always do this again after every flash of anything in TWRP!
Detonator features (from the website):
*With the Verizon Detonator you will get:
– VoLTE, Wifi-Calling /4G/LTE/ONLINE services & features.
– AdAway
– AppLock
– OperaMax (VPN/Data Saving)
– Caller ID & Spam Protection
– Phone and messaging Firewall
– Floating Messages
– Screencast/ScreenRecorder
– Ultra Data Saving Mode
– When booting for the first time… turn off “Confirm Network Connection” Under Settings -> Connections… (*IF AVAILABLE*) (see image below)
Changelog for Verizon Detonator:
v3 – CSC Features added / Wi-Fi Calling APK Update
vPRE-2.2 – Smart Manager Device Security Fix
vPRE-2.1 – Added Mobile Data Toggle to Power Menu.
vPRE-2 – Fixed XML Code / Features Added
vPRE-1 – Initial Release. (Test Phase)
NOTE: After installing Detonator, WIFI Calling button disappeared. I confirmed that I do NOT have WIFI calling, sadly. It doesn't work.
Test it by turning on airplane mode, then connecting to WIFI, then try to make a call. You will get a popup with option to turn on WIFI calling. If you try, it will result in an error, "Unable to activate WIFI Calling at this time, please try again later".
There is presently no solution I am aware of, but maybe someone else knows how, search the forums. Also maybe it has to do with the particular OS I decided to use. I could start over from scratch and try again, but it would be a lot of work and I am out of time for now.
Keep in mind you have to activate on Verizon (see below) before trying to make a call.
5. ACTIVATE ON VERIZON:
Activating on Verizon cannot be done through their site, it will result in an error that your device is incompatible, so don't bother with that.
0. In order to activate you just need an already working SIM card.
Activate a new Verizon SIM card on your PREVIOUS device.
If you need an excuse say you need it for your new phone and YOU will activate it yourself right in the store. Then say it's not working let's try activating on my old phone first.
After the new SIM is working on your OLD phone, leave the store and go home. Now, at your leisure remove the SIM from your old phone and now insert it into your N9600.
Reboot. Now you will be activated on Verizon! (NOTE: YOU MUST ALREADY HAVE DONE DETONATOR, FOLLOW ALL STEPS ABOVE FIRST.)
After you do the rooting below, you'll get messages from SecurityLogAgent saying "security error your device was modified, reboot to revert the changes". You can eliminate this by going into Titanium Backup and FREEZE the following:
SecurityLogAgent
Security policy updates
Software update
Configuration Update
6. Magisk Manager
Boot into phone. If you see Magisk Manager it means you are rooted, probably.
To check it open the Magisk Manager app on your phone.
Feel free to update Magisk. I updated it in the app to 19.3 for Magisk and the installer (flashed from the zip in TWRP) is 7.2
Tap to start safetynet, and accept all prompts.
Reboot
Test if rooted by installing Titanium Backup. If it asks for SuperSU permission then Grant, and it means you are rooted!
7. After rooted, install Xposed
Download xposed from the link in the files section below. If you have a Note 9 on Oreo 8.1 then your file is the SDK 27 for Arm64.
In TWRP, flash the zip file.
Now flash the RMM State zip file. Always do this again after every flash of anything in TWRP!
Backup if desired.
Boot your phone.
Go to the xposed links and get the APK file for xposed. This will be the app you use to manage xposed.
WARNING:
One or more of the settings in the xposed module GravityBox [O] causes bugs and removes your Verizon compatibility. In order to solve the error "No SIM card inserted" (but it is inserted!), what you have to do is to go back into TWRP, and do all steps for the Detonator instructions that I wrote above (it will NOT wipe your device, so don't worry). Once you re-flash Detonator, your Verizon will work again and the SIM card message will be gone.
WARNING 2:
There was another xposed module that caused a similar issue but worse. The issue in reference is you get a black screen at the lock screen but nothing can come up but the reboot menu. You cannot get into the phone. I was about to consider having to factory reset before I solved the issue. Since the issue was an xposed module, then the solution is to:
Download the most recent arm64 xposed uninstaller .zip file from here: https://dl-xda.xposed.info/framework/uninstaller/
Boot into TWRP, flash the xposed uninstaller zip.
Clear the cache and dalvik cache like it suggests using that button on the screen there.
Now flash the RMM State zip file. Always do this again after every flash of anything in TWRP!
Reboot into your phone, your problem is now solved!
Finally, go into Xposed Installer and find the Module that was causing the issue, long-press on it and choose uninstall. I know you want to keep it, but it's too bad, you can re-download it later, you will be unable to simply unselect it. You have to uninstall it.
Now you can go back into TWRP and reinstall xposed.
Last step: flash the RMM State zip file. Always do this again after every flash of anything in TWRP!
Files Needed
ODIN: https://odindownload.com/
- Odin 13.3.1
TWRP: https://forum.xda-developers.com/devdb/project/?id=29220#downloads
- TWRP_3.2.3-0_N9600_beta3.tar.md5
- boot.img (he recommends to use this, see tutorial)
- Encryption disabler.zip
MAGISK: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
- Magisk 16.7 19.3 (can I use latest version 19.3? Answer: YES, I used 19.3 without any problems.)
USB DRIVERS: https://developer.samsung.com/galaxy/others/android-usb-driver-for-windows
- SAMSUNG_USB_Driver_for_Mobile_Phones.zip
BYPASS RMM STATE: https://forum.xda-developers.com/showpost.php?p=75360965
- RMM-State_Bypass_Mesa_v2.zip
DETONATOR: http://tekhd.com/detonator-o/
- DETONATOR_N9_OREO-8.x_VZW_EFS-CSC_v3_INT_TEKHD.zip
DIRECT LINK (VZW v3): https://androidfilehost.com/?fid=11410963190603842742
MIRROR: https://mega.nz/#!cP52EYKS!L9Oc7nihQ2RoXddZPAPXCPdVLvzhXq3VZtaZXGzBtDQ
(link is was down but I have the file which I uploaded for you: [EDIT: TekHD link is back up now! The domain was expired but I spent some time on the phone with GoDaddy trying to renew their domain for them, maybe the dev was able to see it since I told them to reach out to him specifically. GoDaddy refused to let me donate to renew his domain for him. Again update it appears the site is down again. But not expired this time, it just says "pageok". I do have all the data from that site so I will upload it for the community sometime.]
XPOSED (for Oreo 8.1): https://dl-xda.xposed.info/framework/sdk27/arm64/
- xposed-v90-sdk27-arm64-beta3.zip
XPOSED UNINSTALLER (to fix a bad module. See Warning 2.): https://dl-xda.xposed.info/framework/uninstaller/
- xposed-uninstaller-20180117-arm64.zip
OREO 8.1 FIRMWARE (for downgrade):
- N9600ZHS1ASB1 / N9600OWA1ARL5 (N9600 8.1 Oreo 2019-02-01 Chile) https://www.sammobile.com/firmwares/galaxy-note9/SM-N9600/CHL/download/N9600ZHS1ASB1/259310/
- N9600ZHU1ARG6 / N9600OWA1ARG6 (N9600 8.1 Oreo 2018-07-01 Dom Rep) https://www.sammobile.com/firmwares/galaxy-note9/SM-N9600/CDR/download/N9600ZHU1ARG6/231741/
- N9600ZHU1ARG6 / N9600OWE1ARG6 (N9600 8.1 Oreo 2018-07-01 Ecuador) https://www.sammobile.com/firmwares/galaxy-note9/SM-N9600/ALE/download/N9600ZHU1ARG6/231755/
** These three files have been removed from sammobile as of today 2019-05-25, because they were there yesterday. You can still view directly but they will no longer show on the page for the N9600 because sammobile is no longer showing any Oreo (8.0, 8.1) firmwares for the N9600 on their site, only Pie firmwares (9). It's likely these will be removed soon, so I will upload mirrors to the firmwares once they are finished downloading.
(NOTE: DO NOT download firmware N9600ZHS1ASA7_N9600OWT1ARK1_SAM because it will after initializing forcefully change your boot branding to a bright baby blue screen with Movistar carrier branding instead of a normal black samsung boot screen. This will be removed by re-flashing so it's harmless, just annoying. Instead use the above linked. So far I have only tested N9600ZHS1ASB1 above which is fine, it is on the Clara carrier and installs minimal carrier bloat which can be removed after rooting. I linked the other two which I will try as they use pre-August 2018 firmware so hopefully I can get the OEM Unlock to show since I didn't know about the RMM state fix before flashing Pie down to Oreo.)
UPDATE:
This guide is now completed and released. The steps are fully working to get your N9600 working on Verizon.
Someone asked me if regular calling works if they don't have WIFI. Of course. Your phone will fully work on Verizon as normal. In addition to fully working, WIFI calling also works (for some firmwares).
UPDATE 2:
DEAR EVERYONE:
Sorry it took so long for me to upload the files. It appears that TekHD website is now dead for good. It's been down for months. So, since I already had downloaded all the content from the website, including the website pages themselves, I'm now uploaded everything from TekHD for your use. I'm also including all of my rooting files for your use and enjoyment.
Will update the links here when the uploads complete. Enjoy!
EDIT: Here's the link!
https://mega.nz/#F!UbZFSAwC!FObELw39ZmADygAJOFVlyw
-
[moved content from here into original post]
[reserved]
I used a exynos S9+ and I'm using a note 9 exynos on Verizon. You don't need to flash anything because if you use shortcutmaster to bring up Ims settings, with root of course, you can enable all you need.
But you don't have wifi calling or several other things right?
I also had to do a RMM state flash. But I didn't know and now I am blocked from doing anything for a week after downgrading OS. Wish someone would have told me ahead of time. The hacks to change date to bypass and re-enable OEM lock DOES NOT WORK. Trying many things, wasted my whole saturday needlessly.
I finally got the OEM unlock to show.
STEPS:
1. Using Odin flash the whole OS from sammobile. I used 8.1 which is compatible with Detonator.
2. During setup, DO NOT CONNECT TO INTERNET.
3. Choose a date some time in the past like a month or even a year ago. I chose a year ago.
4. finish setup disabling everything.
5. General Management → Date and time. DISABLE Automatic date and time.
6. Enable developer options.
a. Settings > About phone
b. tap seven times on ‘Build number’
7. Settings > Developer options > DISABLE Auto update system
8. It will not work unless you also log into a samsung account.
a. Connect to internet now.
b. Cloud and accounts > Accounts > Add account
c. Sign in or create a new Samsung account.
d. You have to log in and add the account, go back and it should say added.
9. DISCONNECT FROM INTERNET
10. Go to date and time. Choose a date in the future. I chose a few months in the future.
11. Settings > Software update > tap on Download updates automatically (it will error because not connected. It's fine. Don't connect!)
12. REBOOT
13. Settings > Developer options. The OEM unlock option should be visible now.
I think the above is what I did. I might have the order above wrong because I tried so many times I can't remember if that's the exact order. I think it is, but if it doesn't work try a few different ways and eventually you'll get it.
EDIT: When I tried again, above does not work so I must not have remembered what I did perfectly, OR for some reason it just didn't work the second time.
[.]
Before I bust out the Type-C cable, I must ask, will this work on the Sprint variant?
Any plan to ad sprint to the list
eastside08 said:
Before I bust out the Type-C cable, I must ask, will this work on the Sprint variant?
Click to expand...
Click to collapse
NO!!! BEWARE, N960U or N960U1 HAS A LOCKED BOOTLOADER.
IF YOU ATTEMPT TO ROOT ON ANY US MODEL, YOU WILL BRICK YOUR PHONE!
The ONLY Snapdragon model that can be rooted is the INTERNATIONAL N9600. I specifically bought the N9600 for this. This N9600 has an unlocked bootloader.
I was planning on running Detonator on the Oreo 8.1 since the developer TekHD has not yet developed a Detonator for Pie on Verizon. Plus, I read that many people prefer Oreo over Pie. Moreover, Oreo will have more dev support than Pie since Pie is still very new.
I am still working on this so will continue progress updates.
Right now I am stuck because I didn't know about the RMM State so I am stuck on Prenormal, which means 7 days waiting. I had gotten the OEM unlock to show because I was going to disable and re-enable OEM unlock, and when I proceeded it wiped, and then changed to Prenormal preventing from installing TWRP again.
If I had known ahead of time, I could have flashed the RMM fix zip while I had TWRP on there and could have avoided this fiasco. If I get OEM unlock to show again then I will use that to avoid future lockouts.
Right now I am downloading a July 2018 version of Oreo 8.1. I tried flashing several Oreo 8.1 and that is easy with Odin, but could not get the OEM unlock to show up again no matter what I tried. According to this page** (link below), the method of switching the time doesn't work on pre- August 2018 firmwares. That's not entirely accurate as I got it to show up the first time, but I may be stuck now.
So in an effort to try anything, I am downloading and will flash the earlier version of 8.1 from July. Then will try the date method to try to get it to show up. Hopefully it works.
** NOTE: link from above is https://www.thecustom droid.com/prenormal-rmm-state-on-samsung-galaxy-guide/ (remove the space between custom and droid)
For future reference, guides go in the guides section, not development.
Update: I can't get OEM unlock to show up and ran out of time. So, I have to take the long way around and wait a week for it to show up. So, I'll be back on Sunday if OEM unlock shows up.
Im guessing this trips knox ?
why put 'Verizon Full Rooting Guide' when rooting has nothing to do with carriers.
the guide is to get verizon csc on a n9600. you should change the way you named the thread if you dont want to get a gazilion questions from n960u uers.
i sure am confused.
are you able to root a international note9 and use it on verizon network in the usa, or not?
i know elliwigy is working on getting root for a specific model of note9, i think for the usa unlocked or verizon locked model, but it's not useable on stock firmware yet.
UPDATE:
After 7 days, a reboot, and pressing check for updates (but not updating), then checking for the OEM unlock, it did in fact show up.
Unfortunately, enabling OEM unlock also factory resets your phone which AGAIN puts the 7 day lock - which is f*ing ridiculous.
So now I have to wait ANOTHER 7 days before proceeding, so that Prenormal will be able to go to Normal and I can flash TWRP and custom binaries.
Will update again in another week.
bober10113 said:
why put 'Verizon Full Rooting Guide' ... if you dont want to get a gazilion questions from n960u uers.
Click to expand...
Click to collapse
Please note the tag [N9600], if N960U users fail to read the full title, that's their fault. I put all the disclaimers in red anyway just in case, so they can know.
This indeed is about using an international N9600 on Verizon in the USA. I am still working on this and as per my previous post, in another week once the 7 day wait period is over again so I can finish the root and flashing, then I will continue to update about how to get the N9600 working on Verizon.
It is worth noting that you are required to root the N9600 in order to use Detonator.
siriom said:
Im guessing this trips knox ?
Click to expand...
Click to collapse
The answer to this is Yes. It trips Knox. You cannot root without tripping Knox.
dumbfone said:
are you able to root a international note9 and use it on verizon network in the usa, or not?
i know elliwigy is working on getting root for a specific model of note9, i think for the usa unlocked or verizon locked model, but it's not useable on stock firmware yet.
Click to expand...
Click to collapse
The answer to this is hopefully yes, and I have known others to get the N9600 working on Verizon. But I have to wait another week before I can proceed, so please check back next week to see my progress and additional instructions.
Hello everyone,
I have wonderful and amazing news. I have completed fully rooting my Note 9 N9600 and also getting it fully working on Verizon. I am updating the original post now with the details and remaining steps.
It's worth noting that after the second 7 days, OEM unlock would NOT show up. I waited hours more, but still no luck. Instead, I used an application called Chimera which I actually paid for in order to get OEM unlock to finally show up, and it worked.
Update: See the above completed and updated guide.
zxzxzxzxzxzxzxzxzx said:
Update: See the above completed and updated guide.
Click to expand...
Click to collapse
so the way to do it is just flashing the latest detonator?
http://tekhd.com/detonator/
(apparently with full wifi calling support too..)
http://tekhd.com/detonator-o/#vzwdetonator
(or go to detonator telegram channel for possibly modded comunity version...rumor i heard)
implicitly, people probably already know how to root by following the steps outlined from the snapdragon thread..