Related
I have an XT907 I used with Verizon for a while in NJ, then gave it to my kid for playing games once I changed carriers (mid-contract). I've looked at the phone and it would get stuck at the red eye screen. I've gone to recovery and wiped the user data/cache, no help.
The bootloader is LOCKED (and doesn't seem eligible to unlock). I've tried using Matt Groff's Razr utility to restore the system/boot images, but my guess is that since the bootloader is locked, it won't let me overwrite critical system files. I think I may have messed something up by trying to update some of the files but not the core system files. Maybe that's not even the problem, I dunno.
I've looked at how to unlock a bootloader but it seems to require root access, which I can't get since the device is unbootable. The device is also ineligible for unlocking normally (thanks, Verizon). Now it's stuck on an infinite loop with the red eye for about 25 seconds, then reboots. Repeat forever. Do I have any other choices for recovering my system? Can the device be unlocked via fastboot (maybe a custom recovery image)? Or is the problem not even the system/boot images?
Or am I SOL? I can't go to Verizon because I bailed from the contract. Not sure if they were (somehow) responsible for messing up the phone in the first place?
blakeloverain said:
I have an XT907 I used with Verizon for a while in NJ, then gave it to my kid for playing games once I changed carriers (mid-contract). I've looked at the phone and it would get stuck at the red eye screen. I've gone to recovery and wiped the user data/cache, no help.
The bootloader is LOCKED (and doesn't seem eligible to unlock). I've tried using Matt Groff's Razr utility to restore the system/boot images, but my guess is that since the bootloader is locked, it won't let me overwrite critical system files. I think I may have messed something up by trying to update some of the files but not the core system files. Maybe that's not even the problem, I dunno.
I've looked at how to unlock a bootloader but it seems to require root access, which I can't get since the device is unbootable. The device is also ineligible for unlocking normally (thanks, Verizon). Now it's stuck on an infinite loop with the red eye for about 25 seconds, then reboots. Repeat forever. Do I have any other choices for recovering my system? Can the device be unlocked via fastboot (maybe a custom recovery image)? Or is the problem not even the system/boot images?
Or am I SOL? I can't go to Verizon because I bailed from the contract. Not sure if they were (somehow) responsible for messing up the phone in the first place?
Click to expand...
Click to collapse
Do you know what system version your device was on before this incident?
If you were on Jelly Bean - I would suggest flashing 183.46.10 (the first KitKat build) with RSD Lite - then root and unlock the bootloader.
If you were already on KitKat - then you can restore with RSD Lite.
Everything you need > http://forum.xda-developers.com/droid-razr-m/general/guide-faq-how-to-root-boot-unlock-t2869432
After rooting with the KingRoot apk apps would start crashing randomly (no message, just every running app would exit and throw me to my home screen), so I decided to factory reset. I grabbed Titanium Backup, grabbed the app backups I needed, then did the reset. Phone booted up, but now the setup wizard just crashes every run through and restarts itself, leaving my phone useless.
It may be important to know that after KingRoot, my boot screen had an unlocked lock with the text "custom" under it- I figure this means my bootloader is unlocked, but I could be wrong.
I've enabled USB Debugging through the recovery screen.
Setup Wizard (Without SIM):
Connect to Wifi network -> Next -> Crash
Skip connect to wifi -> Skip anyway -> Crash
Setup Wizard (With SIM):
Properly IDs my number and connects to 4G -> Next -> Sometimes crash
Skip Verizon Cloud -> Not Now -> Crash
Setup Verizon Cloud -> Finished Setting up -> Crash
Installing TWRP via h00ps://twrp.me/devices/samsunggalaxycoreprimequalcomm.html
Option 1 (TWRP) nogo, no previous TWRP installed
Option 2 (Odin) nogo, tried both through the website on Linux/FF and through Windows (VirtualBox). The website asks me for the PIT, then when it tries to retrieve it from the device it fails. The app on Windows doesn't ask me for it, but when trying to install it it pops up "secure check fail: recovery" on the phone's screen (the app does nothing).
Option 3 (dd) nogo, can't get an adb root shell
Rerooting through the KingRoot desktop app:
It looks like it succeeds (it's all in Chinese).
adb root gives "adbd cannot run as root in production builds"
adb shell su gives "[-] Connection to ui timed out"
Trying to remove or disable the Setup Wizard app:
ps | grep setup returns the following package names:
com.android.setupwizard (pm disable -> Unknown package)
com.google.android.setupwizard (pm disable -> Permission Denial: attempt to change component state from pid=11940, uid=2000, package uid=10014)
com.google.android.partnersetup (pm disable -> Permission Denial: attempt to change component state from pid=11958, uid=2000, package uid=10030)
com.sec.android.app.setupwizard (pm disable -> Permission Denial: attempt to change component state from pid=12180, uid=2000, package uid=1000)
kill <package> -> Operation not permitted)
pm uninstall <package> -> "Failure [DELETE_FAILED_INTERNAL_ERROR]"
pm path com.android.setupwizard -> nothing
pm path com.google.android.setupwizard -> /system/priv-app/SetupWizard/SetupWizard.apk
pm path com.google.android.partnersetup -> /system/priv-app/GooglePartnerSetup/GooglePartnerSetup.apk
pm path com.sec.android.app.setupwizard -> /system/app/SamsungSetupWizard/SamsungSetupWizard.apk
I had also sideloaded gapps-lp-20150314 (for 5.1.X) in hopes that it would fix it up.
Anything else I should try? Any stock images so I can do a complete, fresh, reinstall? I know someone here was working on getting stock everything uploaded- will that be my best bet?
Thanks!
EDIT: Additional information
Download mode returns the following strings:
ODIN MODE
PRODUCT NAME: SM-G360V
CURRENT BINARY: Samsung Offical
SYSTEM STATUS: Custom
REACTIVATION LOCK: OFF
QUALCOMM SECUREBOOT: ENABLE (CSB)
RP SWREV: S1, T2, H1, R1, A3, P1
SECURE DOWNLOAD: ENABLE
When trying to flash TWRP with ODIN add line
SECURE CHECK FAIL: recovery
I think the twrp was not for your phone. All the cores have Qualcomm snapdragon processors and I do believe most of them are LTE. I know for a fact tmobiles is an lte. The problem is Verizon paid for the kernel so they could control our access. That's why we're the last one to get anything done. Basically, by flashing the recovery, you may have soft bricked your phone since it compiles with a different kernel. Yes, Verizon has a different kernel. If you check opensource.samsung.com, you'll notice our phone is not listed. Thats thanks to Verizon. I'm pretty sure that's illegal too but I'm not a lawyer. Until we get a stock rom or someone has an idea, I do believe your phone is KIA.
Ugh, thanks verizon. However, the soft brick immediately happened after the factory reset, not the install of twrp (it kicks out of that pretty quick). I know you're working on a stock rom in another thread, anything you need to speed up the process? I'm honestly about to just get a Nexus 5 from Amazon Prime, they're pretty cheap and it's getting rough not having mobile data.
With the new OTA having just rolled out, I'm going to pull it. You'll be able to use it to recover
https://mega.nz/#!0Q1nFQ7a!pHublKgmjElaZmePKUWxTB5rlgLytu921bFIJJbII_E
Link to the new OTA.
Flash using either recovery, if you still have access or fastboot.
And TWRP is official. I found the actual name from verizon, and it matches. Careful with the OTA, I'm now soft bricked.
jaywillsoul said:
Link to the new OTA.
Flash using either recovery, if you still have access or fastboot.
And TWRP is official. I found the actual name from verizon, and it matches. Careful with the OTA, I'm now soft bricked.
Click to expand...
Click to collapse
Awesome, you're a lifesaver. I'll do this once I get back from work- can't say I really want to deal with VirtualBox USB passthrough today or that sketchy looking java/web one.
I've still got access to everything (download, recovery, adb, no fastboot though). So the linked version of TWRP (coreprimelte or whatever) is specifically for this phone? Any reason I wasn't able to successfully flash it?
Last thing- and thanks so much- what does that zip actually contain, and if it is just the OTA files, then will I still avoid the soft brick you ran into?
Unfortunately, the OTA update changed nothing. Dunno if it was supposed to (I didn't see Setup Wizard files in there) but I'll trade a soft brick for a soft brick. There was some red debug info on screen when applying, but the phone quickly rebooted afterwards. If you need me to, I could probably adb in and check the version numbers to see if it applied and/or rerun the update and capture that debug info.
Maybe all I need is a stock copy of the Setup Wizards- I should be able to sideload them over the existing versions, right?
Maybe. I'll dig through the system and see if I can find the original.
It might be a part of gapps
That's what I was thinking too, and I've tried reapplying gapps-lp-20150314.zip. I think the Setup Wizard it's crashing on isn't the stock android one, but one of the samsung/verizon ones I listed in the first post.
Found it. Once my son goes down for his nap, I'll upload it for you.
https://mega.nz/#F!BE1TVbTL!d2G2P9S1jVyV-mr8UsfAGw
That's the entire folder in /system/app
It was worth a shot, but sideloading that apk failed. The stock you are working on should be the ultimate fix though.
I uploaded the official md5 from Samsung kies 3. It's in a new thread.
AWaterFountain said:
It was worth a shot, but sideloading that apk failed. The stock you are working on should be the ultimate fix though.
Click to expand...
Click to collapse
Did the ROM work for you?
Yep, I guess I only confirmed that with jay in PM. The stock ROM he uploaded worked fantastically, just threw it in Odin and I was good to go.
AWaterFountain said:
Yep, I guess I only confirmed that with jay in PM. The stock ROM he uploaded worked fantastically, just threw it in Odin and I was good to go.
Click to expand...
Click to collapse
Good to hear! What version of odin did you use and what settings in odin do you select to get the ROM to flash?
All stock, latest version. All I had to do was throw phone into DL, put the stock rom into ap/pda, and let odin do its thing.
Thanks!
jaywillsoul said:
I uploaded the official md5 from Samsung kies 3. It's in a new thread.
Click to expand...
Click to collapse
were do i find te tread you posyed it on?
My Sons Moto X Play (UK sim free XT1562) this morning was showing a bootloader screen with "Start Up Failed" then "Your device didnt start up successfully. Use the Software Repair Assistamt on computer to repair your device". Then further down it says "hab check failed for boot / failed to verify hab image boot / failed to validate boot image". I'm guessing an update occured overnight which failed somehow?
Anyway, found a copy of the image file "X_Play_UK_Retail_XT1562_LPD23.118-10_CFC.xml.zip" and popped it on a SD card. Started boot loader, changed to recovery mode (stock UPD23.118-10), choose "apply update from sdcard" but get the message "Internal and external memory cannot be mounted". Trying it again gives "E:error opening /sdcard: Permission denied". Tried a wipe data/factory reset and wipe cache then repeat, but get the same messages.
I'm at a bit of a loss now. Any help would be much appreciated. Thanks
I would flash stock rom with RSDLite from the computer. If you dont want it to wipe everything make sure to edit the flashfile.xml and servicefile.xml and remove <step operation="erase" partition="userdata"/> and <step operation="getvar" var="max-sparse-size"/>
You will lose root and custom recovery after that though.
This message appears to me once and I reflashed with RSDLite, and until now, everything is ok
Thanks guys. Couldn't get RSDLite to recognise the phone though.
Then noticed that the image I'd downloaded was an older version (5.1.1) of android. Managed to find a new 6.0.1 version here. Still not working with flash from SDcard, but got reading about ADB, installed it and flashed each part of the rom seperately and now it works. Hooray!
Got another problem now - the phone is insisting on using a google account previously used on the phone. I know my sons email address and password which I verified works on the PC, but the phone just loops round and asks for it again each time I enter it. Doesn't seem to be an option to skip for now either - very weird!
bacus said:
Thanks guys. Couldn't get RSDLite to recognise the phone though.
Then noticed that the image I'd downloaded was an older version (5.1.1) of android. Managed to find a new 6.0.1 version here. Still not working with flash from SDcard, but got reading about ADB, installed it and flashed each part of the rom seperately and now it works. Hooray!
Got another problem now - the phone is insisting on using a google account previously used on the phone. I know my sons email address and password which I verified works on the PC, but the phone just loops round and asks for it again each time I enter it. Doesn't seem to be an option to skip for now either - very weird!
Click to expand...
Click to collapse
Make sure to install the moto x play drivers prior to opening RSDLite. You also have to be in download mode in the recovery options.
https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
Clearly your rom has a problem explaining why the email security loops unless you arent connected to internet...
Did install the moto drivers when I tried RSDLite but no good. Anyway, that's not a problem now since I've got firmware on the phone and it now boots.
The issue with it not accepting the password for the google account has probably been made worse by me. In my frustration, I changed the google password. I've now read that after you do this, you have to wait 72 hours before you can re-auth a phone with that account. Shame. Will now wait and see what happens after that.
Thanks again
Update - after waiting the 72 hours, the phone has now accepted the new google account password so we're back in business.
My son was very happy to get his phone back.
Thanks all
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