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..
Related
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
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
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
Read the first 3 posts before you proceed.
For Android 10 go here
https://forum.xda-developers.com/galaxy-a20/how-to/android-10-q-guide-a20-t4095589
For a20e go here
A20e Root,Kernel, TWRP and custom ROM
Root & TWRP from Xyn XDotnest https://forum.xda-developers.com/galaxy-a20/development/recovery-twrp-3-4-0-0-galaxy-a20e-a202f-t4141767 Orange Fox Recovery from @Royna...
forum.xda-developers.com
WARNING: Rooting your phone may be dangerous.
Rooting a device may void the warranty on the device. It may also make the device unstable or if not done properly, may completely brick the device. XDA-Developers or the author does not take any responsibility for your device. Root at your own risk and only if you understand what you are doing!
Advantages of rooting:
Once you root your device you can install flashable zip files and custom ROMs.
You can backup all your apps and data using Titanium Backup.
You can customize your device according to your needs by deleting unwanted system apps and using Deathly Adiutor to modify the kernel.
View attachment 4802662
Disadvantages of Rooting:
Once you root your device, your device warranty will be void.
After rooting yourndevice may become unstable.
You may not be able to upgrade OTA in the future.
This method should root your Samsung Galaxy SM-A205X (all models except SM-A205U and SM-A205DL).
It was developed for the U2 bootloader (June 2019 firmware)
This method does not work for the a20s (A207X)
This method can be used to root other Samsung phones including the a20e( post#77 post#180, post#256)
Quick Root and TWRP for A205xx
https://forum.xda-developers.com/galaxy-a20/how-to/guide-quick-root-twrp-galaxy-a20-t4069423
You'll find it much quicker.
Repair Firmware
This site contains
1. Full repair firmware
2. Combination firmware
3. Fix dm verify
4. Root instructions and unpatched boot images
https://www.full-repair-firmware.com/search?q=A20
More firmware (some are even prerooted)
https://www.needromarab.com/1/122/SAMSUNG
Samfirm Tool for really fast downloads
https://samfirmtool.com/samfirm-v0-5-0
Useful videos
Instructions
A. Prepare boot image
1. Download magisk manager apk
2. Download the exact firmware (including upgrade date) for your device from https://samfrew.com or https://www.samfirmware.net/ or https://www.full-repair-firmware.com/search?q=A20 or
https://samfw.com/
3. Use zarchiver to copy AP_20xxxxxxxx.md5 to download directory. It will extract it from the zip.
4. Rename AP_20xxxxxxxx.md5 to AP_20xxxxxxx.tar and extract using zarchiver
5. Copy boot.img.Iz4 to download directory and extract (resulting in boot.img)
6. Use magisk manager to patch boot.img (use top install) result magisk_patched.img
(If using Magisk (Canary) patch, options should be remove dm-verity and not via recovery, but allowing Persist Encrypt.)
7. Rename magisk_patched.img to boot.img
9. Use zarchiver to compress boot.img to boot.tar. If you have a A205xx June firmware (U2 bootloader), you can use my one of you're willing to take a risk. View attachment boot.zip. Just unzip it first.
9a. For a20e users, try this boot.img https://forum.xda-developers.com/showpost.php?p=81649257&postcount=260
10. Copy boot.tar to Windows pc or Windows Virtualbox.
11. On phone developer options in settings unlock OEM and enable usb debugging
(If using Linux
9. Don't compress `boot.img`
10. install heimdall flash with `sudo apt install heimdall-flash`, if you want front-end install it with `sudo apt install heimdall-flash-frontend`)
B. Unlock bootloader
Useful video
12. Backup data. It will be wiped.
13. Turn phone off
14. Hold vol- and vol+ and plug in power cable attached to pc then release vol up to enter unlock screen.
15. Follow the instructions to unlock
(You might need to long press vol up to unlock bootloader)
vol + to select yes to confirm.
17. Press power key to unlock bootloader.
18. Reboot and reactivate developer options and enable usb debugging. Don't enter too much data at this stage as you will lose it again later.
C. Flash boot image.
19. Turn phone on in bootloader (download) mode (Hold power and vol+ to enter recovery mode then select bootloader download mode)
20. Connect phone to computer.
21. Use Odin in Windows to add boot.tar to phone. (Select AP). Some people recommend adding the other firmware parts to their slots at the same time.
22. Restart phone
23. select bootloader
24. Select factory reset (this will wipe data)
25. Restart phone
26. install data
26. install magisk manager
27. If green phone is rooted.
View attachment 4802665
28. Of red select install/direct install
29. Advanced tick both.
30. Install root checker and verify root
If Something Goes Wrong
Go here
https://forum.xda-developers.com/galaxy-a20/how-to/crash-recovery-t4068369
If you get a DTBO error after updating Magisk, flash this vbmeta https://drive.google.com/file/d/1-dogButfxKGlx_x2tSROOBDiq90SDlmc/view
(If using Linux
To flash:
20. Detect device with `heimdall detect`
21. Flash the `boot.img` with `heimdall flash --BOOT {location of the boot.img, you can also just drop the file into terminal and terminal should auto-fill it}` ex: `heimdall flash --BOOT '/home/utku/Programlar/ext/boot.img'`
P.S: an easy way to boot into download mode is `adb reboot bootloader`)
If you want to remove the warning messages on the boot screen
try this.
https://forum.xda-developers.com/galaxy-a30/how-to/hide-bootloader-warning-unlocked-t3954589
The images shown on the A30 thread aren't suitable for the A20 so I have included some better ones here.
View attachment 4803752
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You can use this param.tar to make these changes easier.
https://forum.xda-developers.com/showpost.php?p=80169262&postcount=91
You can now move on to install TWRP
This TWRP was originally designed for Android 9 but works perfectly with Android 10 and also has MTP built-in.
https://forum.xda-developers.com/ga...overy-twrp-3-3-1-0-galaxy-a10-exynos-t4013481
physwizz collection
A collection of guides, kernels and ROMs. Guides Complete Guide to the A20 GSIs for the A20 Quick Root and TWRP for the A20 Making my First Kernel for the A20 A20 Rooting Guide Making Your Own ROM Making Your Own Version of QwizzROM-a20...
forum.xda-developers.com
Mine
Discussion page.
https://forum.xda-developers.com/t/samsung-galaxy-a20
On the lighter side of rooting....
From the A30 forum:
https://forum.xda-developers.com/galaxy-a30/how-to/hide-bootloader-warning-unlocked-t3954589
Works for A20 too
jajk said:
On the lighter side of rooting....
From the A30 forum:
https://forum.xda-developers.com/galaxy-a30/how-to/hide-bootloader-warning-unlocked-t3954589
Works for A20 too
Click to expand...
Click to collapse
Another reason to merge. This is a procedure for removing those annoying error messages on startup screens.
A205U owners complaining about not being able to oem unlock bootloader might want to study this:
https://forum.xda-developers.com/android/software/patched-odin-3-13-1-t3762572
It looks like a way to switch to another unlockable firmware version.
Please, need magisk_patched.img file for SM-A205F.
jajk said:
A205U owners complaining about not being able to oem unlock bootloader might want to study this:
https://forum.xda-developers.com/android/software/patched-odin-3-13-1-t3762572
It looks like a way to switch to another unlockable firmware version.
Click to expand...
Click to collapse
Yeah tried that option. Samsung has our model on a bootloader 2, means our device won't accept flashing from any other firmware but the original non-modded firmware only.
Tried prince Odin,patched Odin all versions, tried Heimdall etc..
Error is ...boot secure check failed..
I've tried to flash firmware a205G only with fail error Everytime.
Psa I've had my a205u for 10 days no OEM unlock option.
Main reason why I'm not buying another Samsung phone.
Bought a Moto g7 and the g7 power ..I rooted both within 10 min from purchase. Motorola emailed me my bootloader unlock code . Fastboot flashed and Bam good to go. I'm done .
jhjhjhjhjhjh said:
Bought a Moto g7 and the g7 power ..I rooted both within 10 min from purchase. Motorola emailed me my bootloader unlock code . Fastboot flashed and Bam good to go. I'm done .
Click to expand...
Click to collapse
^^^^^^^^^^^^^^^^^^^^^^^THIS ALL DAY. I swapped mine out for the G7 Power and already done rooted, flashed, and wrote a guide while all the 205u users are waiting for the mythical OEM Unlock to magically appear which it ain't gonna. Sammy can kiss my techie ass...we are officially divorced. I won't even go back and buy an old Sammy like I wanted to (was thinking about getting that S7 edge). It's me and Moto for now.
jhjhjhjhjhjh said:
Yeah tried that option. Samsung has our model on a bootloader 2, means our device won't accept flashing from any other firmware but the original non-modded firmware only.
Tried prince Odin,patched Odin all versions, tried Heimdall etc..
Error is ...boot secure check failed..
I've tried to flash firmware a205G only with fail error Everytime.
Psa I've had my a205u for 10 days no OEM unlock option.
Main reason why I'm not buying another Samsung phone.
Bought a Moto g7 and the g7 power ..I rooted both within 10 min from purchase. Motorola emailed me my bootloader unlock code . Fastboot flashed and Bam good to go. I'm done .
Click to expand...
Click to collapse
Maybe Samsung has an issue with US tariffs.
Samsung have certainly turned an essentially good piece of hardware into a pile of rubbish with mega-invasive bloatware. I have barely started to strip back the garbage and the phone is springing to life. Need a working TWRP before getting too keen as the path back to functionality is long and arduous without a way of restoring partitions if anything gets screwed up. Here is what the phone looks like with Google Play junk removed plus a bit of Samsung bloat removed - not everyone is ready to kick the Alphabet addiction I know, but it has become an absolute monster that eats battery and cpu cycles....apart from the privacy invasion side of it
I am finding that many unknown, non-visible apps with innocent sounding names or "security" inferred in the name are likely to be ad server or data mining software - I got wise to this with my first and last Xiaomi device
jajk said:
Samsung have certainly turned an essentially good piece of hardware into a pile of rubbish with mega-invasive bloatware. I have barely started to strip back the garbage and the phone is springing to life. Need a working TWRP before getting too keen as the path back to functionality is long and arduous without a way of restoring partitions if anything gets screwed up. Here is what the phone looks like with Google Play junk removed plus a bit of Samsung bloat removed - not everyone is ready to kick the Alphabet addiction I know, but it has become an absolute monster that eats battery and cpu cycles....apart from the privacy invasion side of it
I am finding that many unknown, non-visible apps with innocent sounding names or "security" inferred in the name are likely to be ad server or data mining software - I got wise to this with my first and last Xiaomi device
Click to expand...
Click to collapse
I used titanium backup first. Now I'll debloat.
physwizz said:
Maybe Samsung has an issue with US tariffs.
Click to expand...
Click to collapse
The US doesn't have an issue with South Korea on tariffs, despite Trump's big mouth.
The problem is that Sammy wants to be essentially Apple Android. And that is what's driving this crap in the same of "security". Knox has been like the devil and even sentient since it came to power almost like Skynet. And all of this started when Verizon offered Sammy big bucks to lock it down ala Kyocera with the S5 era - which coincidentially is the last great breath of air they had to give.
They don't care about the developer models either - look in the forums, many of them are just as locked down.
Sammy knows ain't that many phone companies left in the US; Tmobile done bought out half the cell companies and AT&T got the other half in a duopoly, meaning they and other companies can continue this path of nanny phones on the general public that are going for more personalized computers they can't control than actual phones that work. Most Americans aren't going to turn to GooPhone nor will many XDA devs develop any type of TWRP or rom for those types. And that means they can dangle a bells and whistle carrot while their demographic signs their privacy away.
I ain't a fan of Lenovo-Moto, but at least they let half the phone companies unlock the variant to their devices. Sammy, on the other hand, does not and is playing Xiaomi type of games on that bootloader.
Articul8Madness said:
The US doesn't have an issue with South Korea on tariffs, despite Trump's big mouth.
The problem is that Sammy wants to be essentially Apple Android. And that is what's driving this crap in the same of "security". Knox has been like the devil and even sentient since it came to power almost like Skynet. And all of this started when Verizon offered Sammy big bucks to lock it down ala Kyocera with the S5 era - which coincidentially is the last great breath of air they had to give.
They don't care about the developer models either - look in the forums, many of them are just as locked down.
Sammy knows ain't that many phone companies left in the US; Tmobile done bought out half the cell companies and AT&T got the other half in a duopoly, meaning they and other companies can continue this path of nanny phones on the general public that are going for more personalized computers they can't control than actual phones that work. Most Americans aren't going to turn to GooPhone nor will many XDA devs develop any type of TWRP or rom for those types. And that means they can dangle a bells and whistle carrot while their demographic signs their privacy away.
I ain't a fan of Lenovo-Moto, but at least they let half the phone companies unlock the variant to their devices. Sammy, on the other hand, does not and is playing Xiaomi type of games on that bootloader.
Click to expand...
Click to collapse
I find it strange that the US version is the only one that can't unlock the bootloader.
The rest of us are all unlocked and rooted.
physwizz said:
I find it strange that the US version is the only one that can't unlock the bootloader.
The rest of us are all unlocked and rooted.
Click to expand...
Click to collapse
It aint strange, its common. Before it was locked exclusively to Verizon; after the S3 it became more and more carriers. Then the dev models started being locked up but "open".
Articul8Madness said:
It aint strange, its common. Before it was locked exclusively to Verizon; after the S3 it became more and more carriers. Then the dev models started being locked up but "open".
Click to expand...
Click to collapse
Mine is locked to Vodafone but I can still unlock the bootloader.
physwizz said:
Mine is locked to Vodafone but I can still unlock the bootloader.
Click to expand...
Click to collapse
Same here.
Did you mod your param.tar (to change the warnings at startup) file by any chance? Would you be able to attach it at all? I was gonna download the firmware but it's taking 9 hours.
Thanks.
burningcreation said:
Same here.
Did you mod your param.tar (to change the warnings at startup) file by any chance? Would you be able to attach it at all? I was gonna download the firmware but it's taking 9 hours.
Thanks.
Click to expand...
Click to collapse
I've downloaded the 2 pics and I modified one to contain my name.
I will try the mods shortly.
The Samsung Galaxy A71 model SM-A716U by AT&T which has a normally unlockable bootloader has thanks to afaneh92 been unlocked. And he has made a TWRP version for it. Mine is now rooted with TWRP installed.
The version of TWRP was just built today by afaneh92 and it may still need a few tweaks per afaneh92 to be fully ready for prime time but so far it seems to be working fine. He was also very helpful in installing TWRP and getting root done on this model.
I'm not sure of all the details regarding how this locked bootloader is unlocked but it is a pay service that involves using your phones DID number which is then used to make a customized file for your specific phone and is flashed with Odin. Using afaneh92 for this it had a waiting time of only a couple minutes to get the file.
See this thread for afaneh92's info to get your bootloader unlocked on this model if you want root and TWRP:
Samsung Galaxy Bootloader Unlocks for normally unlockable Bootloaders
If there is interest I'll detail the steps to get all this done. I didn't have all the details when I started so I got help from afaneh92 via Telegram for the process. You will need to have Telegram either on your PC or phone to communicate with afaneh92 and to get the needed info and file built for your phone.
When you decide to unlock your bootloader these directions will help you be prepared and will avoid tying up afaneh92 too much as I know he barely gets any time to sleep with all that he does Since I'll assume you are not unlocking your bootloader for fun of an unlock the directions below will help you get Root and TWRP installed. TWRP is the easiest way to install Magisk and get root.
First you will want to do a complete backup of your phone. I suggest Samsung Smart Switch or MyBackup Pro or both
Then you need to get your phones DID number. You can see it on the download screen. Easy way to get into download is to turn off your phone, then hold volume up and volume down and the plug in USB cable to your computer (charger may also work). Then when you see the aqua color screen hit volume up to go into download mode. There are a couple other methods listed on the page afaneh92 has in the link above.
Save the DID number and it will be good to take a picture of the Download screen also as afaneh92 may request that.
Make sure you have the patched version of Odin from here:
https://forum.xda-developers.com/attachments/odin3-v3-14-1_3b_patched-zip.5158507/
Also get multidisabler.zip and vbmeta_disabled.tar if you don't have it.
Multidisabler.zip can be found here: https://forum.xda-developers.com/t/pie-10-11-system-as-root-
multidisabler-disables-encryption-vaultkeeper-auto-flash-of-stock-recovery-proca-wsm-cass-etc.3919714/
Also get the Magisk.zip file from here: https://github.com/topjohnwu/Magisk/releases/download/v21.4/Magisk-v21.4.zip
Then get on Telegram to contact afaneh92 from his link for his channel in the link above. Once you make payment he will get the .tar file for your phone. It can be just a couple minutes or a day or so I believe depending on his source being available. Mine only took a couple minutes. Once you have the fix file
for the bootloader unlock you will use the patch Odin to flash it to the AP section. Upon reboot the phone will take a little while to start up as it's like a factory reset and your data is wiped.
After you have gone through the phone setup wizard you will want to reset Odin, go into Download mode again and flash vbmeta_disabled.tar to the USER_DATA section in Odin. And if afaneh92 has TWRP available you can flash it into the AP section at the same time. Before pressing start in Odin be ready to quickly press volume up and power button once the phone reboots and the screen goes black. The release when you see the Logo. The you will be in TWRP.
Use adb to push multidisabler.zip onto your phone. Since data is encrypted at this point there is no use in
copying it there ahead of time. Just use "adb push multidisabler.zip /" which will copy it to root of phone storage where you can see it with TWRP. After flashing it do not wipe cache / Dalvik.
Then in TWRP choose Format data and type yes to confirm. Then reboot TWRP into recovery (TWRP)
In TWRP flash multidisabler.zip Then format data and answer Yes.
Then the best way to install Magisk is to flash it now from TWRP with "Install".
Reboot and check whether Magisk Manager is installed. If for some reason it isn’t installed automatically,
manually install Magisk Manager and with Wifi on allow it to do any updates.
Here is one other way to get your DID number (also shown in afaneh92's message thread above):
adb shell getprop ro.boot.em.did
or by Android terminal: getprop ro.boot.em.did
After talking to afaneh92 I believe he will be ready to release TWRP for the Galaxy A71 in a day or two. I am not sure yet if it will cover all the Snapdragon A71's or which exact models as I haven't asked about that but the one I tested today seems to work very well on the A716U.
This thread is where you can now get TWRP : [RECOVERY][UNOFFICIAL] TWRP for Galaxy A71 5G (Snapdragon)
Confirmed legitimate. Currently running his custom TWRP as well. He reaponded quickly too. It is worth the money to me.
So nobody's addressed the million-dollar question. What does Afeneh92 charge for this service?
Also, do we need to be on a specific version for this to work? I haven't updated my phone since I bought it because I've been waiting for a root method to be developed. Would he be able to root if I update to the latest software? Will I be able to update it after he roots it?
edit: nevermind the first question, it looks like the current price is $65 for the A71 5G.
droidzer1 said:
The Samsung Galaxy A71 model SM-A716U by AT&T which has a normally unlockable bootloader has thanks to afaneh92 been unlocked. And he has made a TWRP version for it. Mine is now rooted with TWRP installed.
The version of TWRP was just built today by afaneh92 and it may still need a few tweaks per afaneh92 to be fully ready for prime time but so far it seems to be working fine. He was also very helpful in installing TWRP and getting root done on this model.
I'm not sure of all the details regarding how this locked bootloader is unlocked but it is a pay service that involves using your phones DID number which is then used to make a customized file for your specific phone and is flashed with Odin. Using afaneh92 for this it had a waiting time of only a couple minutes to get the file.
See this thread for afaneh92's info to get your bootloader unlocked on this model if you want root and TWRP:
Samsung Galaxy Bootloader Unlocks for normally unlockable Bootloaders
If there is interest I'll detail the steps to get all this done. I didn't have all the details when I started so I got help from afaneh92 via Telegram for the process. You will need to have Telegram either on your PC or phone to communicate with afaneh92 and to get the needed info and file built for your phone.
Click to expand...
Click to collapse
What makes a bootloader More difficult to unlock compared to otherways? Asking because curious.
droidzer1 said:
The Samsung Galaxy A71 model SM-A716U by AT&T which has a normally unlockable bootloader has thanks to afaneh92 been unlocked. And he has made a TWRP version for it. Mine is now rooted with TWRP installed.
The version of TWRP was just built today by afaneh92 and it may still need a few tweaks per afaneh92 to be fully ready for prime time but so far it seems to be working fine. He was also very helpful in installing TWRP and getting root done on this model.
I'm not sure of all the details regarding how this locked bootloader is unlocked but it is a pay service that involves using your phones DID number which is then used to make a customized file for your specific phone and is flashed with Odin. Using afaneh92 for this it had a waiting time of only a couple minutes to get the file.
See this thread for afaneh92's info to get your bootloader unlocked on this model if you want root and TWRP:
Samsung Galaxy Bootloader Unlocks for normally unlockable Bootloaders
If there is interest I'll detail the steps to get all this done. I didn't have all the details when I started so I got help from afaneh92 via Telegram for the process. You will need to have Telegram either on your PC or phone to communicate with afaneh92 and to get the needed info and file built for your phone.
Click to expand...
Click to collapse
Hey man is yours from ATT ? I got my mom one and wanted to useon Cricket AIO . ATT owns Cricket and uses same network so does Safelink . Well cricket sim works for 5 mins no problem the says the imei is uncompatible. Safelink sim works fine . Are there some gsi for this phone ? That may help it or modules to spoof lol .
Hey was wondering if anyone has or can make a backup of modemst1 and modemst2 for A 71 5g snapdragon ? I had an issue registering on network and found a guide using fastbootcommands to erase those and that would fix it. However now it won't recognize any sim card and I've downgraded and did Ota to 3.0 again after formatting data in twrp. I ve tried twrp backup and that didn't fix it .
droidzer1 said:
After talking to afaneh92 I believe he will be ready to release TWRP for the Galaxy A71 in a day or two. I am not sure yet if it will cover all the Snapdragon A71's or which exact models as I haven't asked about that but the one I tested today seems to work very well on the A716U.
Click to expand...
Click to collapse
Hi,
You mentioned the A71 A716U and in the OP mention "AT&T". Is that what the A716U is? The AT&T model?
I ask because I just bought two of them, but they're Unlocked and someone else is using it with my Carrier (MetroPCS, now called Metro by T-Mobile) and so it didn't mention which Carrier the model normally ties to.
If so, I still use this same BootLoader Unlocker that he creates, right? I definitely want to Root both phones.
I didn't see the steps for Rooting here (I think you mentioned listing the steps), but I'll keep looking.
Thank You,
hi Zeus i believe the A716U is the north american A71 5G and diffrent cell carriers can be flashed for the firmware part, the carrier lock is i think controlled by you but you've got to ask your cell provider to unlock it carrier wise if you owe nothing for the device and it it isnt blacklisted or stolen the imei, also the devices are usually? branded one particular carrier, to find that out go into download mode and it should have a csc cell provider code at the top. =) hope this helps?
Hi,
I went to the link where the "multidisabler.zip" file is and got that, but when I looked for the "vbmeta_disabled.tar" file, I don't see it on that page. Where can I get that one, please?
I ask, because I've never heard of that one before and so I don't know if it's specific for this phone and so was worried about just grabbing any file from wherever (on XDA) with that name.
Thanks!
mysticjp said:
hi Zeus i believe the A716U is the north american A71 5G and diffrent cell carriers can be flashed for the firmware part, the carrier lock is i think controlled by you but you've got to ask your cell provider to unlock it carrier wise if you owe nothing for the device and it it isnt blacklisted or stolen the imei, also the devices are usually? branded one particular carrier, to find that out go into download mode and it should have a csc cell provider code at the top. =) hope this helps?
Click to expand...
Click to collapse
Oh, maybe I wasn't clear (my fault). I don't mean the Cell Carrier. I bought that part Unlocked. I'm talking about Unlocking the BootLoader.
Thank you for taking the time to respond! I appreciate it!
Hi no bootloader unlock for DUE4 yet thank you