Related
Hi guys, thanks for taking the time to read and respond
I got a Verizon sm-g930v Galaxy s7 and my service is through T-Mobile.
I currently have Verizons very recent nougat 7 release with security patch of February 1, 2017 and baseband G930VVRU4BQA2.
I have 2 issues which might be related and I'm trying to figure out what's the best way to do it and if it is at all possible.
1) my lte speed is crap and service inside buildings is awful. I read that there are ways to unlock the bootloader but couldn't find how to do it on my phone.
2) no ussd codes work even after factory reset, every single ussd code I put (even the one to view imei) says ussd running and then says connection problem or invalid mmi.
Is it possible to flash T-Mobile nougat firmware on my phone? Will it unlock the bootloader to allow me to unlock all lte bands?
Is there another better way to solve the above issues?
Thanks for your help!
Tnewbie said:
Hi guys, thanks for taking the time to read and respond
I got a Verizon sm-g930v Galaxy s7 and my service is through T-Mobile.
I currently have Verizons very recent nougat 7 release with security patch of February 1, 2017 and baseband G930VVRU4BQA2.
I have 2 issues which might be related and I'm trying to figure out what's the best way to do it and if it is at all possible.
1) my lte speed is crap and service inside buildings is awful. I read that there are ways to unlock the bootloader but couldn't find how to do it on my phone.
2) no ussd codes work even after factory reset, every single ussd code I put (even the one to view imei) says ussd running and then says connection problem or invalid mmi.
Is it possible to flash T-Mobile nougat firmware on my phone? Will it unlock the bootloader to allow me to unlock all lte bands?
Is there another better way to solve the above issues?
Thanks for your help!
Click to expand...
Click to collapse
hi, not bootloader unlock yet for the g930v, you can dowload and flash the g930t firmware G930TUVU4BQB1.
Thank you
albertordzcz said:
hi, not bootloader unlock yet for the g930v, you can dowload and flash the g930t firmware G930TUVU4BQB1.
Click to expand...
Click to collapse
Is there a guide for this method? And will it solve the problem?
Tnewbie said:
Is there a guide for this method? And will it solve the problem?
Click to expand...
Click to collapse
1. find/download the firmware you want to install on your phone (can find at updato.com)
2. extract the files from the firmware file to a folder
3. download/install Samsung Smart Switch
4. backup your phone settings with Samsung Smart Switch (if you have a memory card, maybe be good to remove that and back it up on PC, probably faster this way than thru Samsung Smart Switch)
5. install the latest version of Odin on your PC, open it
6. select BL/AP/CP/CSC buttons then select the matching file (BL for BL_xyz file, etc) - if you use the HOME_CSC file you will NOT have any tmobile specific features (Wifi Calling) enabled/appear, you must use the regular CSC file to add/enable these features
7. in Odin, select OPTIONS and make sure that only "Auto Reboot" and "F. Reset Time" are checked
8. put the galaxy s7 phone in download mode (turn off....while off press VolumeDown+Home+Power until a blue screen appears, press VolumeUp button to enter download mode)
9. connect the galaxy s7 phone to the PC (you should see a blue icon appear under ID:COM afterward)
10. hit START in Odin to begin the process
11. when the process is complete (PASS appears in Odin status window) the galaxy s7 will reboot and begin to install the update
ISSUE - if the phone boots to recovery mode, dm-verity verification failed....DO NOT PANIC....simply put the phone back in download mode, connect it to the PC, and in Odin ONLY select the AP file....install only that file and let the device restart, it should boot to the user menu)
NOTES - while the device is booting to the user menu, it may sit at the Tmobile splash screen an extended amount of time the initial time - please let it sit for a few minutes, and it will boot to the user menu (subsequent restarts don't have a long delay at Tmobile screen)
12. after it boots to the user menu, connect the galaxy s7 to the PC, and restore the phone using Samsung Smart Switch
albertordzcz said:
1. find/download the firmware you want to install on your phone (can find at updato.com)
2. extract the files from the firmware file to a folder
3. download/install Samsung Smart Switch
4. backup your phone settings with Samsung Smart Switch (if you have a memory card, maybe be good to remove that and back it up on PC, probably faster this way than thru Samsung Smart Switch)
5. install the latest version of Odin on your PC, open it
6. select BL/AP/CP/CSC buttons then select the matching file (BL for BL_xyz file, etc) - if you use the HOME_CSC file you will NOT have any tmobile specific features (Wifi Calling) enabled/appear, you must use the regular CSC file to add/enable these features
7. in Odin, select OPTIONS and make sure that only "Auto Reboot" and "F. Reset Time" are checked
8. put the galaxy s7 phone in download mode (turn off....while off press VolumeDown+Home+Power until a blue screen appears, press VolumeUp button to enter download mode)
9. connect the galaxy s7 phone to the PC (you should see a blue icon appear under ID:COM afterward)
10. hit START in Odin to begin the process
11. when the process is complete (PASS appears in Odin status window) the galaxy s7 will reboot and begin to install the update
ISSUE - if the phone boots to recovery mode, dm-verity verification failed....DO NOT PANIC....simply put the phone back in download mode, connect it to the PC, and in Odin ONLY select the AP file....install only that file and let the device restart, it should boot to the user menu)
NOTES - while the device is booting to the user menu, it may sit at the Tmobile splash screen an extended amount of time the initial time - please let it sit for a few minutes, and it will boot to the user menu (subsequent restarts don't have a long delay at Tmobile screen)
12. after it boots to the user menu, connect the galaxy s7 to the PC, and restore the phone using Samsung Smart Switch
Click to expand...
Click to collapse
Thank you so much for taking the time to write all this!! Will it let me go on T-Mobile lte bands after or that won't be possible until there is a bootloader unlock for the device?
Tnewbie said:
Thank you so much for taking the time to write all this!! Will it let me go on T-Mobile lte bands after or that won't be possible until there is a bootloader unlock for the device?
Click to expand...
Click to collapse
Well... no bootloader unlock to free lte bands, and give a try on this rom to find if you can use your lte bands
There is a thread here related to your issue
Take a look at this thread and you may find your answers.
https://forum.xda-developers.com/verizon-galaxy-s7/how-to/official-t-mobile-nougat-rom-verizon-t3562509
Thank you, I finally got to doing it. It was easy and I now have T-mobile OS on the phone, all Verizon stuff is gone and USSD codes now working. It seems like I was able to select all LTE bands, speed is a bit better indoors but not amazing.
Is there a reason to fully root the phone? and can someone explain what benefits would I have from rooting at this point?
Tnewbie said:
Thank you, I finally got to doing it. It was easy and I now have T-mobile OS on the phone, all Verizon stuff is gone and USSD codes now working. It seems like I was able to select all LTE bands, speed is a bit better indoors but not amazing.
Is there a reason to fully root the phone? and can someone explain what benefits would I have from rooting at this point?
Click to expand...
Click to collapse
Rooting gives you full control over the phone. Think Windows "Administrator" account.
Some things that a rooted phone can do is fully disable and uninstall stock & carrier Bloatware, install true ad blocking services, firewall control.
But, with that kind of power, it's way easier to brick your phone, or kill the performance of the device if you start changing things that shouldn't be changed.
Thank you
joe.skelly said:
Rooting gives you full control over the phone. Think Windows "Administrator" account.
Some things that a rooted phone can do is fully disable and uninstall stock & carrier Bloatware, install true ad blocking services, firewall control.
But, with that kind of power, it's way easier to brick your phone, or kill the performance of the device if you start changing things that shouldn't be changed.
Click to expand...
Click to collapse
In that case I'll stick with flashing for now since it def solved my imminent issues.
T-Mobile firmware on Verizon sm-g930v
albertordzcz said:
Well... no bootloader unlock to free lte bands, and give a try on this rom to find if you can use your lte bands
Click to expand...
Click to collapse
This is an old thread, so I am hoping on some newer information. I have been using a Verizon Galaxy S7 on T-Mobil for about a year. This past week we were in the Lake Michigan area and I found that my wife's A21 got much better reception in several areas. I have been reading here about the g930U firmware as well as the ability to flash to the current T-Mobile ROM.
I do not need to revert back to Verizon, but I need wifi calling and all the bands that are available from T-Mobile. Can just flashing to the T-Mobile for Android 8 work for me?
Dan
dlbeaty said:
This is an old thread, so I am hoping on some newer information. I have been using a Verizon Galaxy S7 on T-Mobil for about a year. This past week we were in the Lake Michigan area and I found that my wife's A21 got much better reception in several areas. I have been reading here about the g930U firmware as well as the ability to flash to the current T-Mobile ROM.
I do not need to revert back to Verizon, but I need wifi calling and all the bands that are available from T-Mobile. Can just flashing to the T-Mobile for Android 8 work for me?
Dan
Click to expand...
Click to collapse
Just flashed to the most recent t-mobile firmware on my Verizon phone successfully. Thanks to information on this thread!
@dlbeaty what did you use to flash to most recent t-mobile firmware? I have G930V Oreo I am trying to use on T-Mobile and having same issues. Would like to try to flash to resolve as well. Thanks!
Hi, I'm a total noob on this but I don't know where to start to looking for an answer.
My girlfriend went on vacation (from Chile) to the united states, her mother gave her a cell phone (her cell phone at that moment) an almost new Samsung Galaxy S7 Edge (SM-G935P) from the Sprint Network.
Before returning to Chile the cell phone was unlocked (or so they said at Spring), so here in Chile she put her local carrier SIM but the cell phone never recognized the Sim Card.
So she hard reset the cell phone. Everything went well until he had to enter the original Gmail account for the cell phone. Her mother did not remember the password so after som trial and error, they manged to reset the Google Account. But now when I try to enter de Gmail and password give me this error: Unable to sign in device due to a recent password change. try again in 24 hours, I have waited more than 24 hours and still can't activate the account.
The cell phone is still showing at her known devices in her mother's Gmail account, and the password is correct but I can't by pass the Gmail Activation, I was reading that I can downgrade to a firmware that allowed me to by pass the Samsung FRP but I don't know wich firmware I can use.
Can someone plase guide me how can I activate this cell phone.
Thank you!
edit: You were right I apologize.
If you want to get your password then whoever knows the best information will need to tell google over the phone what that information was when initially set up...birthdays, time of creation,etc-when they ask and %100 will ask. If she/you don't know it..you may never get it back... but calling their --> Customer Support <-- is your best option.
For s7 edge Android 7.0
So I found a way to bypass Google frp on Android 7.0 for the s7 edge and couple other model, it's an old way but modified. First enter into the Google account login screen where it says verify your account. All you do is simply over load it with characters. Tyler a bunch misc letters and number until you have a long good string then begine select all copy paste do this until your phone seem like it going to freeze up. I did it until it took about 2-5 mins to go through. Doing this will send you to a screen says error something went wrong. Hit enternor continue and if you notice this time when it goes back to verify your account the screen should have a black background at the top where's your notifacatioons are . Repeat 2-3-4 times overloading it and getting the error message I'm not sure exactly how many time think it suffers a on phone and Android build I just know once isn't enough to do it so do it a fewbtime it'll take awhile to get the first error but after that you should have the character line copies and ready to paste. After a couple time hit back arrow on your phone clear to where it ask to select language or start screen and emergency call if done correctly it should now give you the accessibility menu also enter into the accessibility option and modify your set up. Mess with stuff a little be careful with setting up universal switches as you can really mess yourself up. At some point in time you should be able to get your notification menu to drop down and open. When this happens hit the little setting menu button long click it and it should shortcut you to system settings. Bypassing for temporarily. Set up your setting and movie your app permissions as much as possible. Now the trick is getting my Knox downloaded open and set up on your phone. Once you do this make sure you click on both my Knox and regular device administration for know to have some control and make sure you say yes for Knox to be able to reset wipe your phone . After device administration is set and that all done go to your pc or another phone tablet whatever and log into know online and you hold re your phone connected on it white a button that says wipe this phone. Click it make sure the phone has Wi-Fi or service connected and wait for phone to wipe this should reset frp and Google verification back to being a new phone. There ya go merry Christmas
Is this fix legit?^^
Master Shredder said:
Is this fix legit?^^
Click to expand...
Click to collapse
Fцck no it ain't legit. Dude probably got baked & strung up that nonsense to laugh at folks who tried it. You could string up a petrabyte worth of miscellaneous characters so long that your phone would be permanently frozen... & you wouldn't get an error message to pop up, let alone one that would change your notification bar background color or whatever else he said
☆KØŁØЯΛĐØ☆
Master Shredder said:
Is this fix legit?^^
Click to expand...
Click to collapse
No, It's not.
I still can not remove the Samsung FRP, I've tryed all the methods I found online, but still nothing.
S7 & S7 Edge FRP [SOLVED]
Here's the real S7 & S7 Edge FRP bypass method..
Nougat 7.0+ will NOT work; You NEED to downgrade to Marshmallow. Links to Stock Firmware & FRP Removal files posted at the bottom.
- Download & extract the .zip file from my Google Drive below to your PC, then extract + run Odin
- Flash the boot.tar file that corresponds with your device (enables ADB)
- Once the device reboots to the Welcome page, run the Qualcomm.bat file (reboots to Download Mode & removes FRP Lock)
- Back in Download Mode, flash the [MM] Stock ROM (CSC_HOME keeps user data; CSC wipes user data)
You've now successfully kicked FRP's ass from the device. Congrats.
NOTICE:
- You will be able to upgrade back to Nougat 7.0 following successful FRP Removal
- I INTENTIONALLY LEFT A FEW STEPS OUT. It took me a solid week to finally crack this migraine of a phone. You WILL have to figure some parts out on your own just like I did. If you cant, why are you even here?
Stock Firmware located here: https://forum.xda-developers.com/sp...rmware-g935p-pe1-official-sprint-6-0-t3414654
FRP Removal files located here: https://drive.google.com/open?id=0B-BpyLgU2mXlbkVGUDVHWkVnM0E
☆KØŁØЯΛĐØ☆
☆KØŁØЯΛĐØ☆ said:
Here's the real S7 & S7 Edge FRP bypass method..
Nougat 7.0+ will NOT work; You NEED to downgrade to Marshmallow. Links to Stock Firmware & FRP Removal files posted at the bottom.
- Download & extract the .zip file from my Google Drive below to your PC, then extract + run Odin
- Flash the boot.tar file that corresponds with your device (enables ADB)
- Once the device reboots to the Welcome page, run the Qualcomm.bat file (reboots to Download Mode & removes FRP Lock)
- Back in Download Mode, flash the [MM] Stock ROM (CSC_HOME keeps user data; CSC wipes user data)
You've now successfully kicked FRP's ass from the device. Congrats.
NOTICE:
- You will be able to upgrade back to Nougat 7.0 following successful FRP Removal
- I INTENTIONALLY LEFT A FEW STEPS OUT. It took me a solid week to finally crack this migraine of a phone. You WILL have to figure some parts out on your own just like I did. If you cant, why are you even here?
Stock Firmware located here: https://forum.xda-developers.com/sp...rmware-g935p-pe1-official-sprint-6-0-t3414654
FRP Removal files located here: https://drive.google.com/open?id=0B-BpyLgU2mXlbkVGUDVHWkVnM0E
☆KØŁØЯΛĐØ☆
Click to expand...
Click to collapse
Hi ☆KØŁØЯΛĐØ☆, I think I ****ed up.
I follow your instructions, but after the first step (flashing boot.tar) the phone whent on a endless reboot.
Please can you help me.
☆KØŁØЯΛĐØ☆ said:
Here's the real S7 & S7 Edge FRP bypass method..
Nougat 7.0+ will NOT work; You NEED to downgrade to Marshmallow. Links to Stock Firmware & FRP Removal files posted at the bottom.
- Download & extract the .zip file from my Google Drive below to your PC, then extract + run Odin
- Flash the boot.tar file that corresponds with your device (enables ADB)
- Once the device reboots to the Welcome page, run the Qualcomm.bat file (reboots to Download Mode & removes FRP Lock)
- Back in Download Mode, flash the [MM] Stock ROM (CSC_HOME keeps user data; CSC wipes user data)
You've now successfully kicked FRP's ass from the device. Congrats.
NOTICE:
- You will be able to upgrade back to Nougat 7.0 following successful FRP Removal
- I INTENTIONALLY LEFT A FEW STEPS OUT. It took me a solid week to finally crack this migraine of a phone. You WILL have to figure some parts out on your own just like I did. If you cant, why are you even here?
Stock Firmware located here: https://forum.xda-developers.com/sp...rmware-g935p-pe1-official-sprint-6-0-t3414654
FRP Removal files located here: https://drive.google.com/open?id=0B-BpyLgU2mXlbkVGUDVHWkVnM0E
☆KØŁØЯΛĐØ☆
Click to expand...
Click to collapse
Flashing the boot image tar file causes bootloop. I believe that's also the eng boot file? For root? How do you solve bootloop? Also what marshmallow were you on before doing this?
jazzdglass said:
Flashing the boot image tar file causes bootloop. I believe that's also the eng boot file? For root? How do you solve bootloop? Also what marshmallow were you on before doing this?
Click to expand...
Click to collapse
I have not been able to fix it yet, it wasn't on MM it was Nougat.
You know another boot file I can use?
keiichitroncio said:
I have not been able to fix it yet, it wasn't on MM it was Nougat.
You know another boot file I can use?
Click to expand...
Click to collapse
There is Nougat boot files. Check xda here for Qualcomm s7 root. There's a boot file you need to flash before doing adb root.bat..this enables adb, But this also causes bootloop.
jazzdglass said:
There is Nougat boot files. Check xda here for Qualcomm s7 root. There's a boot file you need to flash before doing adb root.bat..this enables adb, But this also causes bootloop.
Click to expand...
Click to collapse
I've been reading a lot a topics here at XDA and I'm overly confused about which method or boot file to use.
I think this could be the one:
https://forum.xda-developers.com/tm...eres-how-rooted-nougat-s7-edge-g935t-t3567502
What do you think? although it is for another is for G935T no G935P
Thank you
keiichitroncio said:
I've been reading a lot a topics here at XDA and I'm overly confused about which method or boot file to use.
I think this could be the one:
https://forum.xda-developers.com/tm...eres-how-rooted-nougat-s7-edge-g935t-t3567502
What do you think? although it is for another is for G935T no G935P
Thank you
Click to expand...
Click to collapse
Just downgrade to marshmallow.. Try PJ2.. I used that. Flash the boot file provided, run Qualcomm.bat via adb.. Then flash again 6.0.1... If phone reboot after flash boot file, you'll have to be very fast, after phone boot to welcome screen, before it reboots, keep running the Qualcomm.bat till u see adb recognize device. It will say error. About phone storage. Just ignore. It has been unlocked
Starting to see how much of a headache this sh¡t was is? Took me a solid week to crack it.
Bravo @jazzdglass Props on figuring it out
KØŁØЯΛĐØ
☆KØŁØЯΛĐØ☆ said:
Starting to see how much of a headache this sh¡t was is? Took me a solid week to crack it.
Bravo @jazzdglass Props on figuring it out
KØŁØЯΛĐØ
Click to expand...
Click to collapse
Do you happen to have the exynos adb bypass code?
OMFG this freaking worked!!
☆KØŁØЯΛĐØ☆ said:
Here's the real S7 & S7 Edge FRP bypass method..
Nougat 7.0+ will NOT work; You NEED to downgrade to Marshmallow. Links to Stock Firmware & FRP Removal files posted at the bottom.
- Download & extract the .zip file from my Google Drive below to your PC, then extract + run Odin
- Flash the boot.tar file that corresponds with your device (enables ADB)
- Once the device reboots to the Welcome page, run the Qualcomm.bat file (reboots to Download Mode & removes FRP Lock)
- Back in Download Mode, flash the [MM] Stock ROM (CSC_HOME keeps user data; CSC wipes user data)
You've now successfully kicked FRP's ass from the device. Congrats.
NOTICE:
- You will be able to upgrade back to Nougat 7.0 following successful FRP Removal
- I INTENTIONALLY LEFT A FEW STEPS OUT. It took me a solid week to finally crack this migraine of a phone. You WILL have to figure some parts out on your own just like I did. If you cant, why are you even here?
Stock Firmware located here: https://forum.xda-developers.com/sp...rmware-g935p-pe1-official-sprint-6-0-t3414654
FRP Removal files located here: https://drive.google.com/open?id=0B-BpyLgU2mXlbkVGUDVHWkVnM0E
☆KØŁØЯΛĐØ☆
Click to expand...
Click to collapse
You sir are a genius. I tip my hat to you.... The only method out of....pretty much the entire internet...that actually works. To all other modders, if you follow the instructions carefully, this will work. Thank again man.:good::good::good:
I have a G935V that is stuck with FRP. I reset my password today and then happened to try to flash a new ROM (didnt know about FRP at the time).
Been trying this all day, but cant get the S7 & S7 Edge QUALCOMM.bat to run on the phone... a flashed back to MM and the Boot.rar pushes fine, but when the phone gets to the welcome screen its like my computer doesn't recognize the phone is connected. Any ideas?
This worked great on my VZW s7 (just had to get the right VZW firmware)...
@KjK89, you have to run the .bat file before the welcome screen. I basically kept running it over and over during boot and it took before th welcome screen.
Check my post about SAMSUNG S7 Nougat 7.0 frp remove
Thanks So much, the only thing that actually worked!
☆KØŁØЯΛĐØ☆ said:
Here's the real S7 & S7 Edge FRP bypass method..
Nougat 7.0+ will NOT work; You NEED to downgrade to Marshmallow. Links to Stock Firmware & FRP Removal files posted at the bottom.
- Download & extract the .zip file from my Google Drive below to your PC, then extract + run Odin
- Flash the boot.tar file that corresponds with your device (enables ADB)
- Once the device reboots to the Welcome page, run the Qualcomm.bat file (reboots to Download Mode & removes FRP Lock)
- Back in Download Mode, flash the [MM] Stock ROM (CSC_HOME keeps user data; CSC wipes user data)
You've now successfully kicked FRP's ass from the device. Congrats.
NOTICE:
- You will be able to upgrade back to Nougat 7.0 following successful FRP Removal
- I INTENTIONALLY LEFT A FEW STEPS OUT. It took me a solid week to finally crack this migraine of a phone. You WILL have to figure some parts out on your own just like I did. If you cant, why are you even here?
Stock Firmware located here: https://forum.xda-developers.com/sp...rmware-g935p-pe1-official-sprint-6-0-t3414654
FRP Removal files located here: https://drive.google.com/open?id=0B-BpyLgU2mXlbkVGUDVHWkVnM0E
☆KØŁØЯΛĐØ☆
Click to expand...
Click to collapse
Anybody looking for a fix for Galaxy S7 and S7 Edge Factory Reset Protection Bypass needs to follow these steps and you'll get past this pesky protection.
The only step that wasn't clear was this:
- Flash the boot.tar file that corresponds with your device (enables ADB)
On Odin you have to choose the boot.tar file corresponding to your model number. This is done by selecting the BL button and only that one then in Odin click Start. This might be clear for veterans to flashing phones with new firmwares but it wasn't clear for me, being the n00b that I am. Thanks again. This worked great!
(Soft-)Bricked S7 Edge/G935F with FRP lock & DRK error, but no root/OEM unlock/ADB
Hello guys,
I bought a, what I thought to be, soft bricked S7 Edge (G935F) from the bay. It was listed as having sw issues, so I thought I could easily fix the issue myself. Stupid me, this one really isn't easy to fix. I've tried a lot of different hints that I found meandering around the web, but none of them have proofed working so far. I would appreciate some help because I don't seem to be making any progress.
When I got the phone, it would boot directly into Android Recovery with a dm-verity error on the bottom.
Below is what I have tried already:
1 . First I did the obvious, factory reset and wipe partition. No change.
2. Downloaded the latest firmware with updato (SM-G935F Region DBT) and flashed with Odin. It then booted into a screen with a hazard sign and a DRK error (Device does not have DRK, please install DRK first. press any button). Then returned to Android Recovery with variations of the DRK and dm-verity error messages
3. I flashed the same firmware again. This time the phone booted up to a Samsung error that said to use SmartSwitch's Emergency recovery. I tried but it asks for a recovery code and I don't have one.
4. I used an older version of SmartSwitch which gave me the initialization option where you need to input the device model and SN - SmartSwitch decided not to cooperate and noted that the S7 edge does not support initialization
5. I tried to flash CF-autoroot but it gave an error in Odin and failed because it is "Blocked by FRP Lock". I can't boot normally into android. Any workaround?
6. I used a dm-verity workaround file (G935FXXU1DQC4_FIX_DRK_dm-verity.tar) to actually get the phone booted up- but then it asks for the account information to do away with the FRP lock. And the former owner does not want to give me his login information. In addition, none of the workarounds (bluetooth, modem terminal prompts, etc.) did work.
7. Flashed oldest Android version I could find for the G935F - 5.1.1 - this gave me a prompt right after reboot that looks like the password request for encrypting memory. default_password and variations did not work. I am still stuck with...
No Support SINGLE-SKU
Supported API: 3
dm-verity error...
failed code : 0x02
...in the recovery
8. I flashed the combination file and was able to boot into Factory Binary and used the IMEI recovery option which is supposed to fix also the DRK issue. No luck.
So, this is where I am right now. If anyone out there still has sparks of hope, I would be delighted to hear about them.
Thanks much in advance!
Conversion software and ADB Shell
Small update - I booted into factory mode again using the conversion firmware. This way, I could connect to the device via ADB and use ADB shell. There is a guide (here: https://forum.xda-developers.com/s7-edge/how-to/guide-how-to-fix-check-drk-imei-issues-t3379516) which guides through IMEI recovery using the conversion software and factory mode - that is supposed to also help with DRK issues. Did not work for me.
Another great guide (here: https://forum.xda-developers.com/no...fix-drk-dm-verity-factory-csc-serial-t3422965) used ADB shell to push and repair the DRK with some additional files. Since the device is not rooted, I did not get very far, either.
So, no progress whatsoever.
In summary, I can get the device booted up into factory mode using the conversion firmware, or, by using the dm-verity tweaked firmware, I can end up in the Google Account locked part of the initial start-up settings.
Any ideas?
Have you looked at the process to completely re-do a phone stuck in the Google auth log-in? At least that is how I understand where you are stuck. I have a phone arriving soon that I will need to re-flash to get out of that, via Odin.
JeffDC said:
Have you looked at the process to completely re-do a phone stuck in the Google auth log-in? At east that is how I understand where you are stuck. I have a phone arriving soon that I will need to re-flash to get out of that, via Odin.
Click to expand...
Click to collapse
Hi JeffDC,
Thanks a lot for the reply. How would this process look like? I have flashed the phone with all sorts of variations of Android L, M and N - plus the combination fw and the one with the dm-verity/DRK workaround which at least got the phone booted up. But then I am stuck at the google auth request.
I cannot flash anything custom since the FRP lock is on.
Hence, if there is any other way to re-do the phone as you are saying, I would live to hear about it.
https://forum.xda-developers.com/s7-edge/help/s7-edge-custom-binary-block-frp-lock-t3347688
https://forum.xda-developers.com/s7-edge/how-to/guide-how-to-fix-check-drk-imei-issues-t3379516
https://forum.xda-developers.com/no...fix-drk-dm-verity-factory-csc-serial-t3422965
JeffDC said:
https://forum.xda-developers.com/s7-edge/help/s7-edge-custom-binary-block-frp-lock-t3347688
https://forum.xda-developers.com/s7-edge/how-to/guide-how-to-fix-check-drk-imei-issues-t3379516
https://forum.xda-developers.com/no...fix-drk-dm-verity-factory-csc-serial-t3422965
Click to expand...
Click to collapse
Hi JeffDC,
Thanks a lot for the links.
Link #1: I can flash the file #1 and get the device visible for ADB by using the combination FW before starting the steps. Unfortunately, step #2 does not work due to lack of permissions. I guess because of missing root.
Links #2 and #3: These are the guides I was already referencing in my post #2 - they both do not work due to, I guess, missing root.
Smart Switch initialization
Update: I got smart switch to do the update and initialization for the device. Workaround was to use a different real serial number than the one of the actual device (I can only assume that it has got to do with country presets).
Cool stuff, all went smooth - but, still the same result. The device ends up in recovery showing the dm-verity error (failed code : 0x02) with FRP lock on and no root.
https://forum.xda-developers.com/ve...-factory-reset-protect-unlock-t3414590/page11
Interesting read, particularly ignoring the trojan squabbling.
Uses script and setup files to get around FRP.
I suggest you to re-try flashing with Odin the Stock Marshmallow Firmware. Then Boot Into Stock Recovery do a Full Wipe.
zzThrain said:
I suggest you to re-try flashing with Odin the Stock Marshmallow Firmware. Then Boot Into Stock Recovery do a Full Wipe.
Click to expand...
Click to collapse
Thanks for the recommendation. Done that (MM downgrade and full wipe) - same result, still DRK error only booting to recovery.
JeffDC said:
https://forum.xda-developers.com/ve...-factory-reset-protect-unlock-t3414590/page11
Interesting read, particularly ignoring the trojan squabbling.
Uses script and setup files to get around FRP.
Click to expand...
Click to collapse
Hi JEffDC, thanks for the follow-up hints. Very interesting read and approach. As commented in the other thread, I think the package download link in the opening post is dead. I am also curious to see 2 more complexities in action:
1. Will this work on a G935F variant (Exynos vs Snapdragon)?
2. The only way for me to get to the Google Account prompt is by using the modded dm-verity version mentioned in my first post - but I am not sure I can get ADB access enabled simultaneously
Good luck.
Deleted
Hey sathiere,
Came across this. It apparently removes the FRP before the system can start it up! Let me know what you think. I'm going to try it on a locked Edge next week or two. Seems to go right after the FRP protection file.
https://forum.xda-developers.com/galaxy-s7/help/how-to-bypass-frp-galaxy-s7-possibly-6-t3622126
and the download link works.
JeffDC said:
Hey sathiere,
Came across this. It apparently removes the FRP before the system can start it up! Let me know what you think. I'm going to try it on a locked Edge next week or two. Seems to go right after the FRP protection file.
https://forum.xda-developers.com/galaxy-s7/help/how-to-bypass-frp-galaxy-s7-possibly-6-t3622126
and the download link works.
Click to expand...
Click to collapse
Hi JeffDC, came across that thread last night - checked it out, but cannot really make sense of it just now. I will be posting directly in this one in the next minutes.
Regarding the link for the other thread - the google drive link for me shows invalid/no content...
sathiere said:
Hi JeffDC, came across that thread last night - checked it out, but cannot really make sense of it just now. I will be posting directly in this one in the next minutes.
Regarding the link for the other thread - the google drive link for me shows invalid/no content...
Click to expand...
Click to collapse
Yes, I am hoping for a response to my post there, near the end, clarifying. I think I get the method, and it's really pretty straight forward, really.
sathiere, I think basically what it does is provide two connections to the phone at the same time, one via Odin, and the other via direct ADB.
Step one is to flash a Universal boot loader, which is unlocked or can be unlocked via ADB. Now with the locked boot loader out of the way, on to getting rid of FRP.
Step two is run the. bat file which deletes the Persistence file, which is the Google encrypted setup file/FRP file. BOOM, FRP gone.
Then either stay on the Universal bootloader, or go back and flash the OEM.
Brilliant!
I have the same problem with a sm930f binary 2 boot loader. Stock Rom doesn't start and frp lock. How you fix it ? Thank you
Try this method
https://forum.xda-developers.com/general/general/solved-bypass-frp-lock-drk-error-t3779082
Hi All.
Thank you for any help you might give me in advance with this issue...
Last week, I tried to root the phone with the SM-G930P CF-Autoroot heroqltespr files with Odin found in this forum. I have rooted a few other phones but am no expert. The root after a few attempts failed (verified a few ways), however, some files must have been affected because the phone "identifies" as heroqltespr. Identifies as when I could plug into my PC heroqltespr would be the name. It was not set this way in the obvious name your device areas. I ended up doing a hard reset to clear the phone and other than the ghost naming everything was working fine.
A day or 2 ago Sprint rolled out a new OTA update which the phone installed. Since then the phone was draining battery life. After uninstalling and reinstalling the SD card today, it seems to have tripped a "Security Notice: Unauthorized Actions". That is when the trouble started. The phone started running hot, basically leaking battery power, and was all lagging. I'm assuming the CPU going Ludicrous speed.
Now, I am in a Samsung Splash screen loop, or or a recovery loop. The only thing it does is go into download mode.
I have tried flashing stock firmware, it fails. I've tried flashing with and without the SD or Sim card. Not really sure what I should be doing. The "P" version of my phone seems to be the bastard child of S7s. Any help you guys cold give me would be great. THANK YOU!
The Download Screen Reads:
Odin Mode (High Speed)
Current Binary: Samsung Official
System Status: Custom
FAP Lock: Off
Warranty Void: 8x8
Qualcomm Secure Boot: Enabled
AP SWREV: 85(2,1,1,1,1) K1 S4
I get this error when I try to flash back to stock SW REV CHECK FAIL : [ABOOT]FUSED 5 > BINARY 4
Stupid question but is your phone in a case?
Sw rev check fail : [aboot]fused 5 > binary 4
freakboysays said:
Stupid question but is your phone in a case?
Click to expand...
Click to collapse
No it isn't.
I get this error message on the download screen. SW REV CHECK FAIL : [ABOOT]FUSED 5 > BINARY 4
I fixed it.
5 > BINARY 4 error, has to do with a Version 5 bootloader Sprint came out with in 2018. The fact that this is only affected by the SM-G390P further complicates things for the average user. Users on version 5 bootloader will need to wait until/If a version 5 universal bootloader for the SM-G930U to get unbloated firmware. Information on restoring your S7 SM-G930P to where you left off before you started trying to root your phone can be found below. More info on Sprint F'n us and BL Version 5 can be found here
https://www.arencambre.com/blog/2018/01/01/fused-firmware-version-locks-samsung-s7/comment-page-1/. There was a post on XDA (which I can't find) which gave the idea that Sprint came out with this version 5 bootloader to prevent people from flashing the phones to the U version and going overseas with them.
The stock files for the first version of Sprint Version 5 bootloader firmware dated 1-1-18 can be found here:
https://www.sammobile.com/firmwares/galaxy-s7/SM-G930P/SPR/download/G930PVPS5BRA1/206876/
Unzip. Only have auto reboot and Re-partition checked as options in Odin.
If you dont mind me asking, did you ever find a way to root the G930P with the 5th bootloader updates? Is it even possible at this point in time? Im new when it comes to rooting but with the amount of time Ive spent browsing the web it seems as if there is nothing. Thanks.
tonysak said:
I fixed it.
5 > BINARY 4 error, has to do with a Version 5 bootloader Sprint came out with in 2018. The fact that this is only affected by the SM-G390P further complicates things for the average user. Users on version 5 bootloader will need to wait until/If a version 5 universal bootloader for the SM-G930U to get unbloated firmware. Information on restoring your S7 SM-G930P to where you left off before you started trying to root your phone can be found below. More info on Sprint F'n us and BL Version 5 can be found here
https://www.arencambre.com/blog/2018/01/01/fused-firmware-version-locks-samsung-s7/comment-page-1/. There was a post on XDA (which I can't find) which gave the idea that Sprint came out with this version 5 bootloader to prevent people from flashing the phones to the U version and going overseas with them.
The stock files for the first version of Sprint Version 5 bootloader firmware dated 1-1-18 can be found here:
https://www.sammobile.com/firmwares/galaxy-s7/SM-G930P/SPR/download/G930PVPS5BRA1/206876/
Unzip. Only have auto reboot and Re-partition checked as options in Odin.
Click to expand...
Click to collapse
I got screwed by this, I accidentally installed the P firmware, and now I cannot load U firmware because of this 5 > 4 error. I went to the blog you posted (arencambre), and I am only able to install the U firmware modem (CP package in Odin), everything else has to be P. And because of the P firmware, I am unable to edit APN settings to enable my native Hotspot. Is there anything I can do, besides wait for U firmware to come out with a Version 5 bootloader?
Chanman said:
I got screwed by this, I accidentally installed the P firmware, and now I cannot load U firmware because of this 5 > 4 error. I went to the blog you posted (arencambre), and I am only able to install the U firmware modem (CP package in Odin), everything else has to be P. And because of the P firmware, I am unable to edit APN settings to enable my native Hotspot. Is there anything I can do, besides wait for U firmware to come out with a Version 5 bootloader?
Click to expand...
Click to collapse
EDIT: Nevermind...sounds like you aren't on sprint.
lvpre said:
EDIT: Nevermind...sounds like you aren't on sprint.
Click to expand...
Click to collapse
Actually, I am on Sprint, and your directions were awesome, thank you so much! The only thing I had to do was change the line to:
settings put global tether_dun_apn "APNDUN,n.ispsn,,,,,,http://mms.sprintpcs.com,68.28.31.7,80,310,120,,default,dun,mms,supl"
I'm going to put a link to the thread so others can refer to it. https://forum.xda-developers.com/sprint-s7-edge/how-to/hotspot-bypass-nougat-ok-t3563446
Hi all,
EDIT: I posted this in another thread that was about two years old, where I followed the instructions that caused this: https://forum.xda-developers.com/sp...msung-galaxy-s7-sm-g930p-root-xposed-t3503599
That thread seems dead-ish and if you managed to fix this issue maybe you can help me also. Also what was lvpre's original post before he edited it, and would it apply here?
So the worst has happened - got a new (used) phone from Boost Mobile, tried this guide, and now I can only boot to the "An error has occured while updating the device software. Use the Emergency Recovery function in the Smart Switch PC software." screen. Sometimes it does take me to the original "Download mode" screen.
Now, I should be able to resolve this by flashing the original firmware correct? (As in, the firmware that was installed when it came)? Or does it just need to be firmware from the same date range that has the same bootloader? ODIN will still let me attempt flashing on this screen, but I still get the same error when I try again, which on the Download mode screen showed "SW REV CHECK FAIL : [system]Fused 4 > Binary 1"
Any advice here? My S6 bricked when somehow OEM unlock enabled itself and I can't get around the FRP lock, I will be VERY annoyed if the same thing happens with a NEW phone. If I can't fix this I am never buying Samsung again. Any advice on this is very welcome! I emailed Boost to ask them which firmware is installed (because I'm an idiot and didn't write it down but have never had flashing go this wrong before).
EDIT: Booting to recovery just shows a blue "RECOVERY BOOTING...." for a second in the corner and gives a recovery bootloop, just keeps flashing that.
EDIT: I apparently tried to flash an earlier bootloader/etc through ODIN according to the directions in the post I linked above, and after that I now have this problem. Nobody else in the thread seems to have had this problem, and your post is the closest to anything I can find on this issue. I would be in your eternal debt if you could help me out here.
PLEASE HELP!
EDIT: Theoretically if I can find the original firmware it was on I should be fine, right? Everywhere I read if flashing goes wrong you just flash the original stock on it. I guess worst case scenario I download gigs upon gigs of firmwares for Sprint 930P over the last year and find the one that sticks? Or is the fact my recovery is bootlooping and I can only go into download mode mean I'm bricked?
Hello all,
To follow up on my last post, I found success restoring to stock via this firmware:
G930PVPU4BQH1_G930PSPT4BQH1_SPR_7.0.zip
https://www.androidfilehost.com/?fid=817550096634799807
I left my original post just in case anyone messes this up the way I did. I still need root, but now I know how to reset to stock in the event this happens again.
For the record I bought a used Samsung Galaxy S7 off the Boost website.
IF YOU FOLLOW THIS GUIDE, OR ANY, MAKE SURE TO GO INTO "SETTINGS -> ABOUT PHONE" AND MARK DOWN WHAT FIRMWARE THE PHONE IS CURRENTLY ON AS STOCK. THIS WILL SAVE YOU A HEADACHE TRYING TO FIGURE OUT WHICH FIRMWARE YOU NEED TO DOWNLOAD IF THINGS GO WRONG. DO NOT PAY FOR A FIRMWARE DOWNLOAD OR USE FILESHARE SITES, GO HERE: https://simunlockremote.com/galaxy-s-series-firmware/ AND FIND THE VERSION YOU ARE ON AND IT WILL DIRECT YOU TO A FAST GOOGLE DRIVE LINK.
Thanks to all the hard work all the devs have done that have gotten use. I still need root soooooooooo if anyone knows how to do that let me know!
CHEERS! I am so happy right now
slvmecha said:
Hello all,
To follow up on my last post, I found success restoring to stock via this firmware:
G930PVPU4BQH1_G930PSPT4BQH1_SPR_7.0.zip
https://www.androidfilehost.com/?fid=817550096634799807
I left my original post just in case anyone messes this up the way I did. I still need root, but now I know how to reset to stock in the event this happens again.
For the record I bought a used Samsung Galaxy S7 off the Boost website.
IF YOU FOLLOW THIS GUIDE, OR ANY, MAKE SURE TO GO INTO "SETTINGS -> ABOUT PHONE" AND MARK DOWN WHAT FIRMWARE THE PHONE IS CURRENTLY ON AS STOCK. THIS WILL SAVE YOU A HEADACHE TRYING TO FIGURE OUT WHICH FIRMWARE YOU NEED TO DOWNLOAD IF THINGS GO WRONG. DO NOT PAY FOR A FIRMWARE DOWNLOAD OR USE FILESHARE SITES, GO HERE: https://simunlockremote.com/galaxy-s-series-firmware/ AND FIND THE VERSION YOU ARE ON AND IT WILL DIRECT YOU TO A FAST GOOGLE DRIVE LINK.
Thanks to all the hard work all the devs have done that have gotten use. I still need root soooooooooo if anyone knows how to do that let me know!
CHEERS! I am so happy right now
Click to expand...
Click to collapse
Don't take any updates. My edited post was on how to get hotspot working. There is a thread here about it, but I changed a line of code.
Switched from Sprint to T-Mobile. Am I out of luck?
lvpre said:
Don't take any updates. My edited post was on how to get hotspot working. There is a thread here about it, but I changed a line of code.
Click to expand...
Click to collapse
I've got a Galaxy S7 G930P from Sprint. I just switched to T-Mobile a couple months ago and brought my S7 phone with me. I was hoping to flash my rom to either the G930U or the G930T (T-Mobile) version, but both are still bootloader v4 and I hit the same error that everyone else on this thread was hitting.
My main problem is that my S7 phone can't send/receive MMS messages on T-Mobile, even after updating the APN settings, and, even worse for me personally - my phone gets below average reception everywhere I go, presumably because my Sprint G930P rom has locked down some of the bands that T-Mobile uses.
Aside from getting a new phone, do I have any options? Or am I stuck waiting for either a G930T or a G930U update based on bootloader 5?
jbuck2 said:
I've got a Galaxy S7 G930P from Sprint. I just switched to T-Mobile a couple months ago and brought my S7 phone with me. I was hoping to flash my rom to either the G930U or the G930T (T-Mobile) version, but both are still bootloader v4 and I hit the same error that everyone else on this thread was hitting.
My main problem is that my S7 phone can't send/receive MMS messages on T-Mobile, even after updating the APN settings, and, even worse for me personally - my phone gets below average reception everywhere I go, presumably because my Sprint G930P rom has locked down some of the bands that T-Mobile uses.
Aside from getting a new phone, do I have any options? Or am I stuck waiting for either a G930T or a G930U update based on bootloader 5?
Click to expand...
Click to collapse
If your phone is uicc [sim] unlocked from sprint... you can try the following.
1. Odin a dec/Jan firmware...like QJ3. But replace the cp slot with the file from the latest u firmware. This is the modem file.
2. When your phone starts, you will receive a pop up message, just hit cancel.
3. Install a package disabler like sabs, bk, adhell2. Disable securitylogagent . This should remove the annoying message. Sabs takes a little effort to setup, but you may need it for the disabler part. Restart after disabling.
4. Pop in sim. See if the additional bands are unlocked.
If you fail, you can always just odin back to a v5 sprint firmware. But don't try it unless you are stuck on the current firmware and your phone is doing nothing. It won't brick your phone.
While the firmware is not downloadable, modem files can downgrade one major update.
This worked for me, but I only have sprint and haven't tried it elsewhere.
Here is an article https://www.arencambre.com/blog/2018/01/01/fused-firmware-version-locks-samsung-s7/comment-page-1/
Is this triggers the knox counter ?
Hey i have samsung galaxy tab s5e lte (sm-t727v) it is unlocked verizon tab i want to flash samsung stock firmware to remove varizon boatload & pre-installed apps & also some features like call & message continuity are blocked by verizon. So can you please suggest which firmware stall i flash & how. I’ve tried flsahing sm-t727 & sm-t725 via odin but it gives error (secure check fail : Pit)
Im curious about tthis myself, but ive kind of resignes myself to the fact im probably goong to have to get an s6 directly from samsung that allows the option to unlock the bootloadr out of the box. There is a new "security update" from verizon though, im curious about what it actually patches before I update.
Sorry for the double post, but I need information by those much more experienced.
So thanks to the 3D patched Odin, my T727V is now a T727U. So basically It's like I bought the thing from Samsung with no carrier bloat and all the nice little things like calling and texting through the phone that Verizon blocks and things like that. Things is I still have no OEM unlock in the dev options, so now I have a few options. Apparently the remote OEM Unlock enable in Pie is CSC based? So obviously the csc is still registered as a VZW, so does that immediately kill the chances and thus it would be a waste of time to wait for the RMM lock (which I'm pretty sure I would have triggered), right?
Also, even though transforming the tablet into a fully featured unbranded is really nice, I still would love custom firmware, and I'm at a catch-22. If OEM Unlock is governed by the csc or imei and not the firmware, I really have no way to change either without root, which I can't accomplish without custom recovery, which of course I need OEM unlock. A question and a tidbit though, question being why I can flash between carriers and unbranded, but I cannot flash to say the Turkish T727 firmware. The interesting tidbit being in the recovery logs for the T727U firmware flash I did, one of the build.prop properties that was set at flash by the firmware is "ro.oem_unlock_supported = 1" This does NOT appear when flashing the Verizon firmware.
Edit: Welp. To any other Verizon S5e owners, flash the T727R4 US cellular firmware. OEM Unlock toggle available immediately.
purplerose1414 said:
Sorry for the double post, but I need information by those much more experienced.
So thanks to the 3D patched Odin, my T727V is now a T727U. So basically It's like I bought the thing from Samsung with no carrier bloat and all the nice little things like calling and texting through the phone that Verizon blocks and things like that. Things is I still have no OEM unlock in the dev options, so now I have a few options. Apparently the remote OEM Unlock enable in Pie is CSC based? So obviously the csc is still registered as a VZW, so does that immediately kill the chances and thus it would be a waste of time to wait for the RMM lock (which I'm pretty sure I would have triggered), right?
Also, even though transforming the tablet into a fully featured unbranded is really nice, I still would love custom firmware, and I'm at a catch-22. If OEM Unlock is governed by the csc or imei and not the firmware, I really have no way to change either without root, which I can't accomplish without custom recovery, which of course I need OEM unlock. A question and a tidbit though, question being why I can flash between carriers and unbranded, but I cannot flash to say the Turkish T727 firmware. The interesting tidbit being in the recovery logs for the T727U firmware flash I did, one of the build.prop properties that was set at flash by the firmware is "ro.oem_unlock_supported = 1" This does NOT appear when flashing the Verizon firmware.
Edit: Welp. To any other Verizon S5e owners, flash the T727R4 US cellular firmware. OEM Unlock toggle available immediately.
Click to expand...
Click to collapse
Where did you find the T727R4 firmware?
Ryche666 said:
Where did you find the T727R4 firmware?
Click to expand...
Click to collapse
Frija! Use CSC code USC on auto mode, boom. Now it's US cellular, which did not like my Verizon sim card at all, so here's a really short summary and links to much better help to do all this (knowing all risks and pitfalls etc.) and end up rooted and your Verizon sim still functioning.
Few things, one this was written up with a Verizon s5e in mind, I don't know if the PITs are different for the other carriers, so this one operates with Verizon's in mind. Two, you MUST have a patched Odin. Also standard advice of backing up everything before hand, and finally, I was dumb and had my SIM card in during the whole process. I'm not sure it had any ill effect but if you want to be super safe, go ahead and keep it out until you're on T727U firmware.
Pre-note: I have no clue if you can substitute t727v for t727u in the following write up. I wanted all traces of Verizon out of my tablet when I was figuring how to enable the Bootloader unlock. We're using the R4 BL files for the whole process so it may or may not effect anything as far as that goes.
1. Do a standard flash of the R4 official Samsung firmware. (You might have to use the us cellular pit for this flash. If so remember to use either the U or V pit for step 3.)
2. Follow AHE_XDA's fantastic guide, right now only the parts about unlocking the bootloader.
3.Once that's done, flash The AP of T727U firmware, with the cp and csc ofT727V Note: Not the BL. We do not flash anything to the BL after the R4 firmware in step 1.
Addendum: Use the Verizon pit (usa_open) when flashing to t727U the first time if you get a "could not open file on line ****" error from odin.
4: Follow the rest of AHE_XDA's guide on rooting and there you go!
purplerose1414 said:
Frija! Use CSC code USC on auto mode, boom. Now it's US cellular, which did not like my Verizon sim card at all, so here's a really short summary and links to much better help to do all this (knowing all risks and pitfalls etc.) and end up rooted and your Verizon sim still functioning.
Few things, one this was written up with a Verizon s5e in mind, I don't know if the PITs are different for the other carriers, so this one operates with Verizon's in mind. Two, you MUST have a patched Odin. Also standard advice of backing up everything before hand, and finally, I was dumb and had my SIM card in during the whole process. I'm not sure it had any ill effect but if you want to be super safe, go ahead and keep it out until you're on T727U firmware.
Pre-note: I have no clue if you can substitute t727v for t727u in the following write up. I wanted all traces of Verizon out of my tablet when I was figuring how to enable the Bootloader unlock. We're using the R4 BL files for the whole process so it may or may not effect anything as far as that goes.
1. Do a standard flash of the R4 official Samsung firmware. (You might have to use the us cellular pit for this flash. If so remember to use either the U or V pit for step 3.)
2. Follow AHE_XDA's fantastic guide, right now only the parts about unlocking the bootloader.
3.Once that's done, flash The AP of T727U firmware, with the cp and csc ofT727V Note: Not the BL. We do not flash anything to the BL after the R4 firmware in step 1.
Addendum: Use the Verizon pit (usa_open) when flashing to t727U the first time if you get a "could not open file on line ****" error from odin.
4: Follow the rest of AHE_XDA's guide on rooting and there you go!
Click to expand...
Click to collapse
anyone else have success with this? ive followed everything so far but i'm stuck trying to unlock bootloader. the option is there in developer options i can turn it on or off in there but when i power down and boot into download mode the option to unlock bootloader isnt there and it says OEM Lock On (u1)
I hate that, that was the part that was no hassle for me so I dont know where to begin...I used the December R4 us cellular firmware, if that helps at all. The same thing that unlocks the toggle should have given the long press up option in download mode. You started with a US T727 Verizon model, right? Now I had changed it to t727U first, maybe that had something to do with it?
purplerose1414 said:
I hate that, that was the part that was no hassle for me so I dont know where to begin...I used the December R4 us cellular firmware, if that helps at all. The same thing that unlocks the toggle should have given the long press up option in download mode. You started with a US T727 Verizon model, right? Now I had changed it to t727U first, maybe that had something to do with it?
Click to expand...
Click to collapse
It was cuz i was on a newer fw version for R4 (feb4) i downgraded to the Dec one and i now i have my bootloader unlocked (shows in dev settings, get notification at boot, and says oem lock off in download mode) but i keep getting a error about "only being able to flash official firmware versions (vbmeta)" . turns out this is from my KG Status being PRENORMAL instead of Checking. you can check this in download mode as well. did you have any issues with that or kknow what i'm talking about? there are guides that say to do things like roll the date back on your phone manually then check for updates but it doesnt work
---------- Post added at 05:02 PM ---------- Previous post was at 04:56 PM ----------
purplerose1414 said:
I hate that, that was the part that was no hassle for me so I dont know where to begin...I used the December R4 us cellular firmware, if that helps at all. The same thing that unlocks the toggle should have given the long press up option in download mode. You started with a US T727 Verizon model, right? Now I had changed it to t727U first, maybe that had something to do with it?
Click to expand...
Click to collapse
also i'm a little confisued about the end of your directions. I am not a Verizon Subscriber i bought this 2nd hand for a deal i am on TMO (not planning on really using data on thin atm but still) Am i correct in thinking after you flashed R4 BL AP CP and CSC, then booted into the R4 firmware and went through initial setup, then reboot to recovery to unlock bootloader and then flashed the t727u AP, left the R4 bootloader, and flasshed VZW CP and CSC? i cant seem to get mine to boot if i do that i get hash check errors when it tries to boot and spits me out into download mode. if this is the case do you remember or can you check the exact versions of CP, AP, and CSC you flashed? right now what i did was flash all R4 tars to go from 727v to 727r4, went though setup and verified i have oem unlock option in dev options then rebooted to download mode and unlocked bootloader THEN i FLASHED 727u versions of AP CP and CSC since my error with the vzw ones i mentioned earlier. Last question. should i be putting my sim in? i notice when i flash the U firmware i get a message about carrier settings update and it makes it reboot
thanks for replying btw
purplerose1414 said:
I hate that, that was the part that was no hassle for me so I dont know where to begin...I used the December R4 us cellular firmware, if that helps at all. The same thing that unlocks the toggle should have given the long press up option in download mode. You started with a US T727 Verizon model, right? Now I had changed it to t727U first, maybe that had something to do with it?
Click to expand...
Click to collapse
could you check something for me real quick? could you boot to download mode and look for "KG STATUS" and tell me what it says. i think my issue is somewhere in the processs of flashing the different firmwares KG gets set to "PRENORMAL" which acts kind of like a secondary bl lock. if i restore to the oldest vzw firmware i could find (june24) it puts it back to "CHECKING" which is good but i loose bootloader unlock in the process obviously thus the catch 22.
albinoman887 said:
could you check something for me real quick? could you boot to download mode and look for "KG STATUS" and tell me what it says. i think my issue is somewhere in the processs of flashing the different firmwares KG gets set to "PRENORMAL" which acts kind of like a secondary bl lock. if i restore to the oldest vzw firmware i could find (june24) it puts it back to "CHECKING" which is good but i loose bootloader unlock in the process obviously thus the catch 22.
Click to expand...
Click to collapse
See, as soon as I switched from T727V to T727U I stopped even seeing kg status in download mode. In my original post in this thread I thought that meant I had tripped it. I really have no clue why just switching to unbranded firmware would make that difference either. I just lucked out on the magic cocktail to unlock Verizons bootloder, I was kind of hoping it would be easy peasy for others. Like, my poor tablet went through odin every day for a straight month.
E: Just saw your edit in your post. I'll have exact firmwares I used asap. In the meantime, my hotspot worked just fine on the unbranded CP and CSC, maybe try that?
ok let me know ill be up a few more hrs
---------- Post added March 10th, 2020 at 12:19 AM ---------- Previous post was March 9th, 2020 at 11:55 PM ----------
you didnt happen to do anything outlined in this thread did you?
https://forum.xda-developers.com/tab-s5e/how-to/samsung-galaxy-tab-s5e-debloat-root-info-t3935010
i wonder if you disabled a Knox apk at the right time to make KG status go away
I'm really scared of bricking my LTE AT&T tablet if I flash the only firmware I was able to grab.
Any way to find the specific stock firmware for my sm-t727A? I've tried Frija, and went all over google to no avail; I can only find other stock firmware.
If I just want to switch to sm-t727u firmware from sm-t727v firmware without rooting do I need to go through the extra step of flashing the us cellular version first?
purplerose1414 said:
Frija! Use CSC code USC on auto mode, boom. Now it's US cellular, which did not like my Verizon sim card at all, so here's a really short summary and links to much better help to do all this (knowing all risks and pitfalls etc.) and end up rooted and your Verizon sim still functioning.
Few things, one this was written up with a Verizon s5e in mind, I don't know if the PITs are different for the other carriers, so this one operates with Verizon's in mind. Two, you MUST have a patched Odin. Also standard advice of backing up everything before hand, and finally, I was dumb and had my SIM card in during the whole process. I'm not sure it had any ill effect but if you want to be super safe, go ahead and keep it out until you're on T727U firmware.
Pre-note: I have no clue if you can substitute t727v for t727u in the following write up. I wanted all traces of Verizon out of my tablet when I was figuring how to enable the Bootloader unlock. We're using the R4 BL files for the whole process so it may or may not effect anything as far as that goes.
1. Do a standard flash of the R4 official Samsung firmware. (You might have to use the us cellular pit for this flash. If so remember to use either the U or V pit for step 3.)
2. Follow AHE_XDA's fantastic guide, right now only the parts about unlocking the bootloader.
3.Once that's done, flash The AP of T727U firmware, with the cp and csc ofT727V Note: Not the BL. We do not flash anything to the BL after the R4 firmware in step 1.
Addendum: Use the Verizon pit (usa_open) when flashing to t727U the first time if you get a "could not open file on line ****" error from odin.
4: Follow the rest of AHE_XDA's guide on rooting and there you go!
Click to expand...
Click to collapse
I get to the unlock the bootloader part but then when I go back in and try to flash the U software according to your instructions, it doesn't work. Could it be that the software has been updated since the instructions were written and it won't work now?
I have tried every version of Patched Odin and followed these directions to a T. I even went back and tried other things and can't get this to work. If someone can help me get the U software to flash on my SM-T727V, I got $20 I'll Venmo or Zelle you.
purplerose1414 said:
Frija! Use CSC code USC on auto mode, boom. Now it's US cellular, which did not like my Verizon sim card at all, so here's a really short summary and links to much better help to do all this (knowing all risks and pitfalls etc.) and end up rooted and your Verizon sim still functioning.
Few things, one this was written up with a Verizon s5e in mind, I don't know if the PITs are different for the other carriers, so this one operates with Verizon's in mind. Two, you MUST have a patched Odin. Also standard advice of backing up everything before hand, and finally, I was dumb and had my SIM card in during the whole process. I'm not sure it had any ill effect but if you want to be super safe, go ahead and keep it out until you're on T727U firmware.
Pre-note: I have no clue if you can substitute t727v for t727u in the following write up. I wanted all traces of Verizon out of my tablet when I was figuring how to enable the Bootloader unlock. We're using the R4 BL files for the whole process so it may or may not effect anything as far as that goes.
1. Do a standard flash of the R4 official Samsung firmware. (You might have to use the us cellular pit for this flash. If so remember to use either the U or V pit for step 3.)
2. Follow AHE_XDA's fantastic guide, right now only the parts about unlocking the bootloader.
3.Once that's done, flash The AP of T727U firmware, with the cp and csc ofT727V Note: Not the BL. We do not flash anything to the BL after the R4 firmware in step 1.
Addendum: Use the Verizon pit (usa_open) when flashing to t727U the first time if you get a "could not open file on line ****" error from odin.
4: Follow the rest of AHE_XDA's guide on rooting and there you go!
Click to expand...
Click to collapse
I am trying to copy your process with a Tab A 2019 unlocked, but Sprint variant with no success so far. I have bricked it a lot, but it doesn't seem to want an unlocked firmware for the same model . I haven't tried flashing it's bootloader though, out of fear of bricking it ( I have unlocked its bootloader already).
Hey guys, just found the thread. Anyone know if an unlocked SM-T727A can be OEM unlocked? I mean the bootloader. The option is always missing no matter how many time I try according to the tutorials, which makes me doubt if a branded S5e doesn't even have this capabililty. Perhaps that's why I am here seeking a chance to flash it to an SM-T727U. Thanks for anyone who replies.
Ok so after three months I turned my mind back to this topic again. And yes, I struggled for a couple of hours overnight last night and got the ATT T727A flashed with Lineage. There are a few tricks: First, the USC R4 firmware can be flashed, with the modified version (3B) of Odin, which bypasses the SHA256 error check; Second, when the USC R4 firmware (latest for now is Mar 2021 version, Android 10) is flashed, the start logo changes from slick ATT to full screen big fat US Cellular. Need to wait for a few minutes and let it do its work. Through this flash, user data will not be lost. Third, the USC R4 version does have OEM Unlock automatically present and all it needs is to flip the switch, then go to download mode to unlock the bootloader. This will erase the user data. Fourth, from then on it's all standard procedures to flash any third party roms like LineageOS with MicroG pursuant to their instructions. Four hours work made a good result, and the cellular data is usable without problem.
PS: the concept of timed OEM unlock switch (a week after factory reset) is wrong. It's non-existent so do not waste time on it. Just straigntly flash the USC R4 Version. To flash other roms like Lineage, it would be better to download the Odin with their specified version to prevent hiccups.
Wieczorkiewicz said:
Ok so after three months I turned my mind back to this topic again. And yes, I struggled for a couple of hours overnight last night and got the ATT T727A flashed with Lineage. There are a few tricks: First, the USC R4 firmware can be flashed, with the modified version (3B) of Odin, which bypasses the SHA256 error check; Second, when the USC R4 firmware (latest for now is Mar 2021 version, Android 10) is flashed, the start logo changes from slick ATT to full screen big fat US Cellular. Need to wait for a few minutes and let it do its work. Through this flash, user data will not be lost. Third, the USC R4 version does have OEM Unlock automatically present and all it needs is to flip the switch, then go to download mode to unlock the bootloader. This will erase the user data. Fourth, from then on it's all standard procedures to flash any third party roms like LineageOS with MicroG pursuant to their instructions. Four hours work made a good result, and the cellular data is usable without problem.
PS: the concept of timed OEM unlock switch (a week after factory reset) is wrong. It's non-existent so do not waste time on it. Just straigntly flash the USC R4 Version. To flash other roms like Lineage, it would be better to download the Odin with their specified version to prevent hiccups.
Click to expand...
Click to collapse
Help me ola if u r there. I have same t727a of att live outside The US. I just want to skip Att block and use SMS app, so flash Usc t727r4 via Odin patched is enough for me? And if i want update from android 9 to 10 i just do same thing with Q firmware?
i try flash USC T727R4 on ATT T727A success for first time, but Massage app still require link other SamSung phone to use. I have full funtion simcard inserted but Google massage app cant recognize too.
Btw, convert to USC is good, no ATT bloatware and now have OTA outsite The US.