I'm unable to use Android Pay - I'm not rooted, the boot loader is RELOCKED but when I try and add my card I get the dreaded "Google is unable to verify that your device or software running on it is Android compatible" error.
So, I was wondering, is it the fact that I did previous unlock my boot loader or something else stopping me.
BTW, Vendor: hw Country: eu, running C432B170.
Cheers.
No joy either
Same problem here. Imported mine and have done nothing but update to latest version of official roms (tried a couple of different ones today as well) and I get the same error. No rooting, purposely held off doing so so I could try Android Pay. SafetyNet Helper says the "CTS profile match" is false. My wild stab in the dark is that it is something to do it with it being identified as an international handset or handset from a non-Android pay supported country.
Had a web chat with an Android Pay helpdesk monkey and they had me reboot and reinstall a few times. They've also had me send some screenshots but I'm not holding out much hope for a useful reply.
captainkibble said:
CTS
Click to expand...
Click to collapse
CTS or CSC?
themissionimpossible said:
CTS or CSC?
Click to expand...
Click to collapse
CTS. Just double checked.
Maybe it's the same thing as CSC for Samsung phones.
In case, this might represent the target market for that phone, and that market might not yet be allowed to use Android Pay.
I'm using the single SIM version, NXT-L09, I managed to add my card but when I tried to pay for something in store I got the unable to verify.... message pop up on screen.
It also fails the CTS profile match in Safetynet helper
Android Pay worked for me today
I gave safetynet helper another try and this time it said my device passed. Re added my card to it and then used it on a London bus.
Using a Mate 8 NXT-L09C636B170
I too am able to use Android Pay. It started working for me last Thursday. While I had an open support ticket with the Android Pay help desk I periodically checked to see if it had started working. Eventually it did. I was able to add cards, SafetyNet Helper passed it's check and I was able to make payments. Result.
The same day, Android Pay help desk got back to me regarding my support ticket (there had been some backwards and forwards with logs, screenshots and the like). They concluded that Android Pay would not work because my phone was rooted. It isn't and has never has been. They had me send screenshots of multiple root checkers that displayed that the phone was not rooted *before* they came to this conclusion. I guess they just wanted the ticket closed and that was the most convenient excuse.
I've put it down to enough people reporting handsets not working that the Google added more phones to the "approved list" and help desks don't know what they are talking about.
My build number is NXT-L29C636B180
Hm.. Well this was interesting to read. Thanks for the updates saying that Android Pay does in fact (hopefully) work! I'm going to to get the L29 International dual SIM version soon so I was curious... I'll update when I get it and test it out
Mine still doesn't work - I then tried upgrading to B320 and I can't even add a card now whereas before I did eventually allow me to add a card. I'm cheesed off with it. Bootloader Locked no root and no Android Pay on a L29C432B320
gnasher666 said:
Mine still doesn't work - I then tried upgrading to B320 and I can't even add a card now whereas before I did eventually allow me to add a card. I'm cheesed off with it. Bootloader Locked no root and no Android Pay on a L29C432B320
Click to expand...
Click to collapse
Same here...
bh4714 said:
Same here...
Click to expand...
Click to collapse
I've downgraded to B170 and now have Android Pay working.
The high level process was:
All done via the help of SRK Tool http://forum.xda-developers.com/mate-8/development/tool-srk-tool-huawei-t3369797
1) Unlock Boot Loader
2) Install Custom Recovery
3) Root Phone
4) Change to oeminfo and custom.bin eu (c432) - Even though I already was
5) Copy Full Update.app for C432B153 to dload folder
6) Flash stock recovery
7) Boot recovery and allow update to install
8) Factory Reset
9) Copy Update.app for C432B170 to dload folder
10) Boot recovery and allow update to install
I'm not sure how but following this process (although I've listed the steps from memory and not in front of my Laptop I did this on) I ended up with a Bootload LOCKED C432B170 and Android Pay works. I've not - nor will I update to and EMUI 4.1 version until they are released as OTA updates that my phone asks me to install
Android Pay was working fine on B103, I've upgraded to B321 via dload and now got pop up info that my device is incompatible with android pay. Any ideas?
Sent from Huawei Mate 8
Just one question
Hi,
Which recovery should I flash? the one for EMUI 4.1 or 4.0?
thanks
I believe Android Pay will not work with EMUI 4.1. I wish we were warned about this before we were allowed to flash to 320 or 321. No warning with the update links. Sucks!
Sent from my HUAWEI NXT-L29 using XDA-Developers mobile app
Hello,
received the Phone with the t-mobile branding (german version).
What i did is to use the official device unlock from Sony so be able to flash another Firmware.
Then i downloaded the generic DE from the FlashTool, and flashed it.
This failed because the rom was already on Android 7.
I did not manage to aquire the -9090 Rom in Android 6.0.1
So i flashed the central europe version.
First problem: this version does not (yet?) update to Android 7 - and actualy is NOT the version i wanted to have in the end.
Second problem: The camera app did not work anymore (already in use)
So i've read through this forum, and got the information, i need to re-unlock the device.
Did that, camera works.
However now i always get "this device is not trusted"
What i actualy want to have:
- A stock ROM in german, whcih gets OTA updates.
- Working Stock-Apps
- No warning when starting the Phone.
I do not care wether the warning is disabled, or simply not shown because of another bootloader. There should simply be no annoying warning.
I also have the exact same phone twice (mine, and the one for my girlfriend) in case this help somehow. In theory the best situation would be to hard-sync every single byte on the disk (i assume?)
I did not read anything about "do not flash currently, as this will make you loose your drm keys forever and the stock camera will no more work at all". But after watching this forum for some days now, it seems that exactly that has happened? So using a locked bootloader will not work anymore due to lost and unrecoverable drm keys? I cannot copy them from the other phone? So i need to replace the bootloader with another one to get rid of the message? And i also need to reflash the firmware as soon as FlashTool supports Android 7?
In the end a total piece of crap, because of a goddamn branding -.-
What would you guys recommend to do now? Just want to make it work without an error or unsecure warning displayed at every boot.
You did not need to unlock to flash another firmware.
Now you have unlocked you can't use the camera without keeping it unlocked and if it is unlocked you will get the warning message.
Just flash a 6.0 ftf from a region with the update then you will get the ota update
Ps, there are plenty of warnings on the Sony site about drm keys that you must have visited to get your unlock code...
And you cannot copy drm keys from another device
Hi guys, i have a galaxy s7 of a customer that doesn't absolutely remember email and password for his google account connected to the phone(and so it's OEM Locked).
i tried to follow many guides on the forum but this happened:
i can't root the phone (because the FRP is locking the Flash),
nor install 6.0.1 (because of the error "sw rev check fail device 2 binary 1")
i can't use bluetooth method to skip setup guide (it was fixed in 6.0.1)
i can't use RealTerm because it can't make me save the number to proceed the guide(also fixed in 6.0.1)
what can i do? how do i bypass the FRP? or how do I downgrade to 6.0.1?
Downgrading can be a problem caused by the bootloader, make sure you try to flash a stock ROM with the same version bootloader as shown with this number
G930FXXU2ERD5
The customer would have had to enter a secondary / recovery email while making that Google account, tell them to check their other email addresses for confirmation emails around the time they set up the phone, then they can find the email address of the google account and reset the password to that email address
You have to downgrade to 6.0 and then there are plenty of ways to unlock.
Download 6.0 and latest firmware.
In Odin
1st and 3rd field from old firmware
2nd and 4th field from new firmware
If You need guide how to unlock from 6.0 let me know
LaHunnid said:
You have to downgrade to 6.0 and then there are plenty of ways to unlock.
Download 6.0 and latest firmware.
In Odin
1st and 3rd field from old firmware
2nd and 4th field from new firmware
If You need guide how to unlock from 6.0 let me know
Click to expand...
Click to collapse
1st and 3rd field in ODIN is Bootloader & Modem
If you flash new firmware to 2nd and 4th you'll end up with new firmware flashed with old bootloader and it won't boot most likely / brick
*Detection* said:
1st and 3rd field in ODIN is Bootloader & Modem
If you flash new firmware to 2nd and 4th you'll end up with new firmware flashed with old bootloader and it won't boot most likely / brick
Click to expand...
Click to collapse
I did that and it didn't brick
LaHunnid said:
I did that and it didn't brick
Click to expand...
Click to collapse
AP is the system / OS, you're telling OP to flash a new version of Android (AP) with an old bootloader, in order to downgrade to 6.0.1, your method would not downgrade anything other than bootloader & modem and old bootloader with new OS will almost certainly brick
To downgrade you need to flash old bootloader (BL) & old Android 6.0.1 (AP), and probably old modem (CP), CSC is the only thing left
And as already stated, downgrading the BL is the problem that prevents most people from downgrading in the first place
check out my tutorial https://forum.xda-developers.com/galaxy-s7/how-to/g930f-frp-unlock-helps-99-g930f-t3791424
Massive thanks
S6unbricker said:
check out my tutorial https://forum.xda-developers.com/galaxy-s7/how-to/g930f-frp-unlock-helps-99-g930f-t3791424
Click to expand...
Click to collapse
I've been absolutely stuck for days trying to sort out the bloody FRP lock on an S7 (SM-G930F) that had been gifted to my wife by my father-in-law where he hadn't removed the accounts before passing it over.
My wife then did an update that the phone requested when it started up and that went wrong at which point I get involved and factory reset it...oh BIG mistake... and that's where my problems started made worse by the fact my father-in-law couldn't remember which account he had setup on the phone....or even the password to possible accounts!! I consider myself to be well versed in all things tech but I had absolutely no idea FRP existed and was absolutely baffled when i saw the message on the screen after flashing the stock firmware (G930FXXU2DRB6) that was on there according to the recovery mode. I've been trying so many different things over the past week all current methods failed...then I came across this one...which had seemed to be blocked by admins but I was able to click on the link in the 2nd post and grab the password from the readme in the first, which i must admit made it a bit dubious and not sure why @S6unbricker felt the need to do that but there's no issues it doesn't go to a stupid survey site or anything it just goes to a text file on mega which has one line and that's the password!
I followed the method to the letter and, to my surprise and joy, it's actually worked a treat...the S7 is no longer a paper weight!!!
Massive thanks to @S6unbricker :good: ...any chance of re-posting but without the password on the file or putting the password in the post?
Frp doesn't block eng bootloader...after u flash eng boot u can simply use Abd command to remove. Or the longer method flash factory binaries. Enable oem unlock (most important part). Then flash stock rom make sure to remove userdata.img ....on a side note wondering if adding the Samsung retail app and activating it, then using the login data to remove the app via factory data reset might work.
deshaney said:
Frp doesn't block eng bootloader...after u flash eng boot u can simply use Abd command to remove. Or the longer method flash factory binaries. Enable oem unlock (most important part). Then flash stock rom make sure to remove userdata.img ....on a side note wondering if adding the Samsung retail app and activating it, then using the login data to remove the app via factory data reset might work.
Click to expand...
Click to collapse
From my experience the combination roms (which I presume you are referring to when you say eng bootloader) didn't solve my issue. Yes I could get them on the phone and boot into them, change the settings or use adb but obviously I don't want the factory binary to stay on there so as soon as I flashed it back to the current firmware, back to square one!
Most poeple advised to use HOME CSC instead of CSC when flashing from combination rom back to stock but I couldn't get odin to flash with HOME CSC.
No I'm referring to the boot.img file. Combination ROMs don't enable su access via she'll.
Samsung s7
Ok I know this is an old Post but I'm brand new to Odin and all the unlock lingo.. can anyone explain to me how to downgrade to bypass the frp on my Galaxy I just bought , I'm very tech savvy just need a walkthrough any help would be greatly appreciated
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..
I accidentally purchased credits for dc-unlocker/HCU instead of the three day option (which I have since purchased and used to unlock my bootloader using a hardware TP) so if these are of any use to someone else let me know.
Hello. Can i use that to unlock my P20 Pro?
flaryx said:
Hello. Can i use that to unlock my P20 Pro?
Click to expand...
Click to collapse
Unfortunately they're no longer available, but you can use the same software to unlock the P20 Pro like I did. It's a little bit of a process, but I've got notes from when I did it if you are interested and I think I spent about 20 EUR for the 3 day licence of dc-unlocker/HCU. In the end I did it with the hardware test point because my back cover was loose and I intended to replace the battery anyway (it was bulging)
asozio said:
Unfortunately they're no longer available, but you can use the same software to unlock the P20 Pro like I did. It's a little bit of a process, but I've got notes from when I did it if you are interested and I think I spent about 20 EUR for the 3 day licence of dc-unlocker/HCU. In the end I did it with the hardware test point because my back cover was loose and I intended to replace the battery anyway (it was bulging)
Click to expand...
Click to collapse
Can you tell me the process please. I was thinking of buying the 3 day license or MOS but i don't know if I can do it or not (don't have any expertise on anything hardware related)
flaryx said:
Can you tell me the process please. I was thinking of buying the 3 day license or MOS but i don't know if I can do it or not (don't have any expertise on anything hardware related)
Click to expand...
Click to collapse
I unlocked my P20 Pro using a hardware testpoint, the HCU software, and a lot of time. I would suggest reading the information below, gathering all the tools/software/ROMS/IMGS you need and asking any questions before you purchase a licence or attempt this process.
WARNING!!!! THIS WILL ERASE YOUR PHONE COMPLETELY!!!
I would suggest making sure if you are going to purchase the 3 day license (this is what I did) that you are available to work on the phone for a couple of days (maybe buy it just before the weekend?) as if you run into any issues you won't have much time to fix them.
WARNING!!!! THIS WILL ERASE YOUR PHONE COMPLETELY!!!
BE CAREFUL TO PURCHASE THE THREE DAY LICENSE AT THE CHECKOUT NOT THE CREDITS (I MADE THIS MISTAKE AS YOU CAN PROBABLY TELL FROM THIS THRED)
Otherwise, the steps I went through are below, as well as some of the links to things I found helpful during the process:
1. SOFTWARE VERSION - It was not possible to unlock the bootloader on version 10 of the OS, so you will require HiSuite (https://consumer.huawei.com/au/support/hisuite/) to downgrade or dc-phoenix to flash an earlier version. I used 9.0.0.168 for my phone (Model: CLT-L29) so will reference that in all the steps below, but use the corresponding version for your phone (whichever you downgrade to from HiSuite should be fine?)
2. TESTPOINT - I used the hardware test point (next to the camera once the back cover is removed) but apparently this is possible using the software test point process (I am uncertain of the exact process for this, but there is a guide on the dc-unlocker site somewhere)
3. ADP/FASTBOOT RECOVERY UNLOCKING - Once the HCU software has provided a new code (or if you already have one) you can use fastboot oem unlock <code> where the <code> is the bootloader unlock code to unlock.
WARNING!!!! THIS WILL ERASE YOUR PHONE COMPLETELY!!!
4. ALTERNATIVE OS INSTALLATION - In my case I installed LineageOS 16 using an old guide (https://web.archive.org/web/20210726230701/https://depl0y.com/posts/P20-Pro-LineageOS-Guide/) which will only work (even the official version) if you patch the Lineage installation (update-script requires editing or replacement)
Install TWRP
Enable USB debugging
adb reboot bootloader
fastboot flash recovery_ramdisk twrp-3.7.0_9-0-charlotte.img
Hold VOL-UP & VOL-DOWN
fastboot reboot
You should now be in TWRP.
Flash LineageOS (and gapps)
In TWRP go to Advanced > ADB Sideload
adb sideload adb sideload lineage-16.0-20210211-nightly-charlotte-signed-modified.zip
adb sideload open_gapps-arm64-9.0-nano-20220215.zip
In TWRP go to Reboot > Bootloader
fastboot flash recovery_ramdisk RECOVERY_RAMDISK_9.0.0.168.img
fastboot reboot recovery
You should now be in the stock recovery. If not, boot into stock recovery
Select Wipe data / factory reset
Reboot system now
THE P20 WILL ONLY BOOT WITH THE STOCK RECOVERY, SO REPLACE IT AFTER USING TWRP
5. WEBVIEW FIX FOR GOOGLE APPS - DO NOT SET UP WIFI DURING INSTALL!
Download com.google.android.webview.apk from apkmirror and copy to the device. Install using the default file manager and reboot the phone. Sign in to Google and update webview, google apps, etc
6. ROOT ACCESS - MAGISK
Install apk (copy to storage and run from files) for Magisk and patch RECOVERY_RAMDISK_9.0.0.168.img.
Reboot into bootloader and flash to recovery: fastboot flash recovery_ramdisk RECOVERY_RAMDISK_9.0.0.168_magisk_patched-25200_8akQl.img
TO BOOT PHONE WITH ROOT BOTH VOLUME UP AND POWER BUTTONS NEED TO BE HELD AT STARTUP!