Related
Hello ladies and gents,
So I'm a total noob and I think I bricked my phone.
I got root by using the motochopper tool
then I went for custom recovery, but I think I flashed the verizon version instead of the ATT version (I was trying to install the Google Wallet fix with a custom rom)
Rebooted the phone, I get an unlock symbol and samsung custom
I can boot into recovery mode and I still have root access / command line.
The phone either boots to black screen with a oscillating blue light or if I go into the other mode it says 'downloading'
Anything I can do to get my phone back working? Did I totally brick it?
Yes, if you see anything on the screen, that would be a soft brick, you are getting the unauthorized screen, then you need another kernel for sure, lets start there...
You really should either put your device in your information screen or tell us what type of device you have, that is very important.
I can not tell you what kernel, not knowing what device has the problem.
I see you mentioned att, is it US or Canadian version?
These are a must when you are seeking help.
I have the AT&T US Version of the S4, 1337
And now it seems I've made it worse, I reinstalled a new Rom, now I can't boot into recovery at all. It goes blank after the Samsung custom screen. Still can ADB into it though.
TheAxman said:
Yes, if you see anything on the screen, that would be a soft brick, you are getting the unauthorized screen, then you need another kernel for sure, lets start there...
You really should either put your device in your information screen or tell us what type of device you have, that is very important.
I can not tell you what kernel, not knowing what device has the problem.
I see you mentioned att, is it US or Canadian version?
These are a must when you are seeking help.
Click to expand...
Click to collapse
Do you have any type backup? Have you tried, power off phone. hold down power button and volume up at same time, when it vibrates, let go of the power button, it should go into recovery, and lets try restoring your backup.
Your problem is you have the wrong kernel loading, flash a ATT kernel once in the recovery, it will boot.
willenglishiv said:
I have the AT&T US Version of the S4, 1337
And now it seems I've made it worse, I reinstalled a new Rom, now I can't boot into recovery at all. It goes blank after the Samsung custom screen. Still can ADB into it though.
Click to expand...
Click to collapse
Just ODIN flash the stock firmware for ATT I337 and re-root? That's what I would try.
blyndfyre said:
Just ODIN flash the stock firmware for ATT I337 and re-root? That's what I would try.
Click to expand...
Click to collapse
Actually Ax has the best solution if he can get to recovery... your way will work but by far to many steps for something that simple...
just saying!!
sloanster said:
Actually Ax has the best solution if he can get to recovery... your way will work but by far to many steps for something that simple...
just saying!!
Click to expand...
Click to collapse
I agree Ax's solution is simpler, but OP said that he cannot boot to recovery.
And now it seems I've made it worse, I reinstalled a new Rom, now I can't boot into recovery at all. It goes blank after the Samsung custom screen. Still can ADB into it though.
Click to expand...
Click to collapse
blyndfyre said:
I agree Ax's solution is simpler, but OP said that he cannot boot to recovery.
Click to expand...
Click to collapse
But he can adb so he can push the kernel onto his phone and flash in recovery
Edit: my bad, he did say he can't boot into recovery. Odin is his best bet.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
he hasn't answered the get into recovery yet, nor has he said he has a backup. I was trying a simple solution. Then we can move on to the odin back.
TheAxman said:
he hasn't answered the get into recovery yet, nor has he said he has a backup. I was trying a simple solution. Then we can move on to the odin back.
Click to expand...
Click to collapse
Hope it gets it worked out!!!
The main thing is he's got options...:angel:
Hi All,
I just got an SPH-i337 yesterday and attempted to Root + Install Mod.
I ended up rooting and installing Safestrap (TWRP 2.6.x.x). Upon first use I backed up my current OS to a removable SD card using the utility in TWRP. I then, because I was not clear on how to download install CM which was what I was going to, installed ROM Manager and selected CM without setting up a ROM slot. I think this is where I went wrong.
Upon reboot, I was unable to access the Stock ROM and had no options to go to CM. When I attempted to perform a restore from my backup on SD it failed as well and keeps going to the Android recovery screen (not TWRP).
I'm now just trying to go back to stock and have tried using both Heimdall and Odin to no avail. Odin at least provides an error message:
SW REV. CHECK FAIL: Fused:4, Binary:1. What does this mean? That I'm attempting to use an image (.tar.md5 file) which is not current? Is there a way that I can still recover my phone?
..also, please let me know if there are pieces of information that I'm missing. I don't have much to go off of since the firmware and other information (I believe) is not able to be accessed.
Again I just got the phone yesterday. I also have about 40 tabs open that are full of searches that I've been doing regarding this. As yet, no luck.
revolut10n said:
..also, please let me know if there are pieces of information that I'm missing. I don't have much to go off of since the firmware and other information (I believe) is not able to be accessed.
Again I just got the phone yesterday. I also have about 40 tabs open that are full of searches that I've been doing regarding this. As yet, no luck.
Click to expand...
Click to collapse
Look for the mk2 tar files. And do a lot of reading. You went wrong in a number of different areas
revolut10n said:
Hi All,
I just got an SPH-i337 yesterday and attempted to Root + Install Mod.
I ended up rooting and installing Safestrap (TWRP 2.6.x.x). Upon first use I backed up my current OS to a removable SD card using the utility in TWRP. I then, because I was not clear on how to download install CM which was what I was going to, installed ROM Manager and selected CM without setting up a ROM slot. I think this is where I went wrong.
Upon reboot, I was unable to access the Stock ROM and had no options to go to CM. When I attempted to perform a restore from my backup on SD it failed as well and keeps going to the Android recovery screen (not TWRP).
I'm now just trying to go back to stock and have tried using both Heimdall and Odin to no avail. Odin at least provides an error message:
SW REV. CHECK FAIL: Fused:4, Binary:1. What does this mean? That I'm attempting to use an image (.tar.md5 file) which is not current? Is there a way that I can still recover my phone?
Click to expand...
Click to collapse
revolut10n said:
..also, please let me know if there are pieces of information that I'm missing. I don't have much to go off of since the firmware and other information (I believe) is not able to be accessed.
Again I just got the phone yesterday. I also have about 40 tabs open that are full of searches that I've been doing regarding this. As yet, no luck.
Click to expand...
Click to collapse
Safestrap only works with other TW ROMS, so your first issue was trying to use CM. Second, it's not official TWRP and is not even installed to the recovery partition so using ROM Manager was your second issue. Trying to boot into recovery normally will take you to stock recovery since it isn't installed in the recovery partition, there should be a splash screen that comes up after the Samsung Galaxy S4 screen asking to either press for recovery or continue. If that works, you can use the backup from there. If it's gone, you have to use ODIN. The reason you get that SW REV. CHECK FAIL is because you're trying to flash an older firmware than you have. Depending on if you were on 4.2.2 or 4.3 you will either need the MF3 or MK2 .tar.md5 respectively.
jd1639 said:
Look for the mk2 tar files. And do a lot of reading. You went wrong in a number of different areas
Click to expand...
Click to collapse
Thanks for pointing me to those files. I'm sure I did go wrong in a few places as I felt that I was largely just winging it.. There's a TON of information out there. Is there anything specific that I was more wrong than the rest?
revolut10n said:
Thanks for pointing me to those files. I'm sure I did go wrong in a few places as I felt that I was largely just winging it.. There's a TON of information out there. Is there anything specific that I was more wrong than the rest?
Click to expand...
Click to collapse
Deadly sin said it all. Cm and rom manager. Here are the files you need http://forum.xda-developers.com/showthread.php?p=49687770
Thanks everyone. Hell of an introduction to Android, I have to say considering I just got off the WinPhone bandwagon yesterday (been using it for ~7 years).
revolut10n said:
Thanks everyone. Hell of an introduction to Android, I have to say considering I just got off the WinPhone bandwagon yesterday (been using it for ~7 years).
Click to expand...
Click to collapse
The s4 is a very difficult phone to use custom roms on. Once you're back up and running start here and read a lot before doing anything with it http://forum.xda-developers.com/showthread.php?p=42320391
jd1639 said:
The s4 is a very difficult phone to use custom roms on. Once you're back up and running start here and read a lot before doing anything with it http://forum.xda-developers.com/showthread.php?p=42320391
Click to expand...
Click to collapse
Now you tell me - after I've been trying to do this for 12+ hours. Many thanks though - it looks like the MK2 AiO files are working.
jd1639 said:
The s4 is a very difficult phone to use custom roms on. Once you're back up and running start here and read a lot before doing anything with it http://forum.xda-developers.com/showthread.php?p=42320391
Click to expand...
Click to collapse
Unfortunately, it seems that I can't use the method listed directly on that page on account of running the MK2 baseband. If I'm going to go forward it looks like I'll have to use SafeStrap and unofficial TWRM + TW mods for the time being.
Of course, if something about what I'm saying is wrong, I'd be glad to hear it.
revolut10n said:
Unfortunately, it seems that I can't use the method listed directly on that page on account of running the MK2 baseband. If I'm going to go forward it looks like I'll have to use SafeStrap and unofficial TWRM + TW mods for the time being.
Of course, if something about what I'm saying is wrong, I'd be glad to hear it.
Click to expand...
Click to collapse
Check my last Post #50 it should get u an idea and where to find related link. Also check that MK2 INDEX & ROM LIST ....:good:
So I apparently made a a mistake somewhere because I get this error when I try to boot my phone now. Ironically the whole reason I wanted to install a customer recovery was to have a safe way to recover in case something like this happened.... I just Odined this file recently, not sure if that helps or anything. I am not sure what to do at this point so any help would be greatly appreciated.
That little message is perfectly normal. You have nothing to worry about
thatsupnow said:
That little message is perfectly normal. You have nothing to worry about
Click to expand...
Click to collapse
You could have elaborated on that, but I appreciate the reassurance. I ended up reflashing to the file I linked to and starting over. This time installing safestrap instead since apparently the other two are not compatible with Verizon phones.
Hi everyone, I've searched and tried some solutions for this but the problem is the display is permanently black, not even samsung logo is displayed on bootup.
My GT-i9505 has a CWM recovery installed and a custom ROM, and today it notified me that SU Binary needs to be updated, so I updated it and it said Success, recommend to reboot, which I did.
It seemed to boot up but the display was constantly black. Manually turned it off by holding down power button, then restarted but still nothing.
I have Odin and samsung drivers etc, just not sure if I should try and flash a stock/new Custom ROM from Odin or if theres an easier way to do it (maybe someone can guide me thru the CWM recovery and be my eyes since my screen is Black?)
Please and thank you.
First of all, you better switch to TWRP.
Second, maybe try flashing a SuperSU zip through the recovery.
If that doesn't work, then try dirty flashing your current rom again.
GDReaper said:
First of all, you better switch to TWRP.
Second, maybe try flashing a SuperSU zip through the recovery.
If that doesn't work, then try dirty flashing your current rom again.
Click to expand...
Click to collapse
Thanks for the goble-de-goop, I have no idea what you are saying (this is n00b friendly forum topic!) and how can I even try that when there's nothing but blackness on my screen?
It is booting and running, touch is working etc but I'm completely blind. Can someone please try to help with n00b friendly suggestions, will flashing a new Custom ROM work? And I'd like to know what has happened after the SU binary update that caused screen/backlight to become non-functional...
Just to point out, I'm not being rude I am being up-front, the first reply I get from here is exactly what I expected, not n00b friendly but more of a suggestion from a nerd who wants to show the other readers that he really 'knows his stuff', however un-useful it is.
I know a little but not enough to solve this on my own, I'm hoping someone out there see's this and unselfishly suggests something without turning it into debate about n00bs not asking the right questions in the right place at the right time!
My phone doesn't work, I need it to work, stupid SU binary update has screwed it, please help!
Pandemic_ said:
Thanks for the goble-de-goop, I have no idea what you are saying (this is n00b friendly forum topic!) and how can I even try that when there's nothing but blackness on my screen?
It is booting and running, touch is working etc but I'm completely blind. Can someone please try to help with n00b friendly suggestions, will flashing a new Custom ROM work? And I'd like to know what has happened after the SU binary update that caused screen/backlight to become non-functional...
Just to point out, I'm not being rude I am being up-front, the first reply I get from here is exactly what I expected, not n00b friendly but more of a suggestion from a nerd who wants to show the other readers that he really 'knows his stuff', however un-useful it is.
I know a little but not enough to solve this on my own, I'm hoping someone out there see's this and unselfishly suggests something without turning it into debate about n00bs not asking the right questions in the right place at the right time!
My phone doesn't work, I need it to work, stupid SU binary update has screwed it, please help!
Click to expand...
Click to collapse
...err...wow...
do you have a HDMI adaptor cable aka MHL adaptor or a chromecast type device at home ? it maybe that your screen has just died and that it's nothing to do with the binary (if it's booting normally albeit with a blank screen).
_neutron_ said:
...err...wow...
Click to expand...
Click to collapse
Starting to think XDA is not the right place to ask for help...
3mel said:
do you have a HDMI adaptor cable aka MHL adaptor or a chromecast type device at home ? it maybe that your screen has just died and that it's nothing to do with the binary (if it's booting normally albeit with a blank screen).
Click to expand...
Click to collapse
Good idea, I do have chromecast but will need mini HDMI cable/adaptor to check. Although it would be massive odds against random screen death, since it was immediately after reboot from SU binary.
Thanks for the intelligent reply, glad to see there are still some helpful people here.
if you can borrow a lead and your screen is being mirrored you can download an image file of TWRP and flash it with flashify from the store. I doubt screen mirroring works from the recovery
http://play.google.com/store/apps/details?id=com.cgollner.flashify
unzip the attached file and copy it to your SDcard then find it within the flashify app...
Awesome OK that gives me a starting point TY. When I connect the MHL adapter will it mirror automatically or will I have to try to blindly press the mirror symbol? I haven't used an MHL adapter/cable before. If it works then I'll use Flashify and hope it restores the phone screen.
if it's going to work it will work without any selecting of options, it's automatic...
If the you run out of solutions, you could flash a stock ROM back to your phone as this will bring the phone back to the factory settings; however, you will lose your data and installed apps.
If you decide to flash back to stock using Odin, I suggest launching Odin, uncheck everything except f.reset time, connect the phone in download mode, flash the rom, when you see the word "reset" in the status window, remove the USB cable from the phone, remove the battery, wait 5 seconds and replace the battery, boot into recovery, perform a factory reset, and reboot. Be sure to use the stock firmware from sammobile.com for your phone.
Pandemic_ said:
Thanks for the goble-de-goop, I have no idea what you are saying (this is n00b friendly forum topic!) and how can I even try that when there's nothing but blackness on my screen?
It is booting and running, touch is working etc but I'm completely blind. Can someone please try to help with n00b friendly suggestions, will flashing a new Custom ROM work? And I'd like to know what has happened after the SU binary update that caused screen/backlight to become non-functional...
Just to point out, I'm not being rude I am being up-front, the first reply I get from here is exactly what I expected, not n00b friendly but more of a suggestion from a nerd who wants to show the other readers that he really 'knows his stuff', however un-useful it is.
I know a little but not enough to solve this on my own, I'm hoping someone out there see's this and unselfishly suggests something without turning it into debate about n00bs not asking the right questions in the right place at the right time!
My phone doesn't work, I need it to work, stupid SU binary update has screwed it, please help!
Click to expand...
Click to collapse
Since you said you have CWM recovery and a rom installed I assumed you would knew how to flash stuff. Unless they were flashed by somebody else?
Anyway, flashing SuperSU.zip is as easy as googling for the zip then boot into recovery and flash the zip file.
Unless the recovery is dark too. Then that's a problem.
And flashing the rom again is done the same way. No need for TVs and chromecasts.
Theoretically, flashing the SuperSU.zip should work, as it replaces the binaries.
Flashing the rom should work too. Unless you have a dead screen. Then no software can fix it.
When you're using apps that modify system files things like this can happen. Something may have went wrong during the update.
@GDReaper he's already said "how can I even try that when there's nothing but blackness on my screen?" to your suggestion of flashing via recovery so MHL will help him
1) to see if the phone is running normal minus the screen
2) to replace CWM as you suggested without using recovery (which he won't be able to do even with MHL).
3mel said:
@GDReaper he's already said "how can I even try that when there's nothing but blackness on my screen?" to your suggestion of flashing via recovery so MHL will help him
Click to expand...
Click to collapse
So I probably misunderstood him. He said it is booting and so I thought that, during the booting, the screen works, and only when you are about to go into the OS the screen is black (As it happened to me before). My bad.
If the screen is black during the whole process it means the screen is busted. And it was probably just a coincidence, as I don't really see how updating the su binaries can damage the screen.
GDReaper said:
So I probably misunderstood him. He said it is booting and so I thought that, during the booting, the screen works, and only when you are about to go into the OS the screen is black (As it happened to me before). My bad.
If the screen is black during the whole process it means the screen is busted. And it was probably just a coincidence, as I don't really see how updating the su binaries can damage the screen.
Click to expand...
Click to collapse
Ok thanks man, it's dark in recovery too unfortunately. Will update again after trying the MHL cable. :good:
Pandemic_ said:
Ok thanks man, it's dark in recovery too unfortunately. Will update again after trying the MHL cable. :good:
Click to expand...
Click to collapse
Ok. Then it is definitely a screen problem. Changing software won't fix it.
You have to get a new screen.
I've tried the cable, no output to HDMI though. Phone is operating but in complete black screen from power on. Have tried to tap the screen mirroring button blindly (by touching all the top system buttons one by one) but no change. This leads me to think it is a software/firmware issue, somehow the SU binary has affected graphics output???
So my only chance now is try to flash using Odin? I have downloaded a new Custom ROM, ResurrectionRemix-M-v5.6.4-20160223-jfltexx but I think I can only flash that one using recovery which will be difficult blind, unless someone can give me precise button sequence. Unfortunately I can't remember exactly what recovery I have on there, but I think it may be the touch version...
I flashed TWRP using Odin no probs, but still no use as screen is still blank from power on.
I was going to revert to stock first but sammobile.com downloads at only 15kb/s so I'm not waiting 2 days for that 1.5gb download.
Can someone please give me a link to a good download for my GT-i9505, that I can flash with Odin. I want a light Custom ROM but if not possible to flash from PC then I'll try stock first.
Thanks,
Hi guys, I have a similar problem. I had a notification saying I need to "Update the #SU Binary". There was issues with the update, it gave me the option of restarting or trying the update again. I selected to try the update again. It failed again and now the screen is black with constant error messages, saying "Unfortunately, Galaxy Apps has stopped", "Unfortunately, S Health has stopped". Pretty much the same error message recurring with every app that would normally run on start up, then the phone just reboots itself every 5 minutes after the error messages have all done a round. I am desperate to recover the data on the phone.
Pandemic_ said:
I flashed TWRP using Odin no probs, but still no use as screen is still blank from power on.
I was going to revert to stock first but sammobile.com downloads at only 15kb/s so I'm not waiting 2 days for that 1.5gb download.
Can someone please give me a link to a good download for my GT-i9505, that I can flash with Odin. I want a light Custom ROM but if not possible to flash from PC then I'll try stock first.
Thanks,
Click to expand...
Click to collapse
SamFirm should speed things up.
---------- Post added at 07:37 AM ---------- Previous post was at 07:34 AM ----------
leNoobe said:
Hi guys, I have a similar problem. I had a notification saying I need to "Update the #SU Binary". There was issues with the update, it gave me the option of restarting or trying the update again. I selected to try the update again. It failed again and now the screen is black with constant error messages, saying "Unfortunately, Galaxy Apps has stopped", "Unfortunately, S Health has stopped". Pretty much the same error message recurring with every app that would normally run on start up, then the phone just reboots itself every 5 minutes after the error messages have all done a round. I am desperate to recover the data on the phone.
Click to expand...
Click to collapse
There isn't much you can do. Backup user data and factory reset.
Hello, I'm new here.
I have a problem.
I forgot the PIN lock of my SM-G360F LTE (with Android 4.4.4), and I would like to keep all my files & documents inside it.
I don't have USB Debug enabled and I don't have a Samsung Account, so there's no easy way I can connect the phone to a computer.
What can I do to save my datas?
I've already tried flashing a Custom Recovery with Odin, but I haven't found a compatible one.
Please, give me an advice on what I should do.
Not sure if this will work for your version but it can't hurt to try. It worked for my stock unrooted SM-G360T1
http://forum.xda-developers.com/gal...emoving-frp-protection-samsung-t3275584/page4
Let me know if this works for you
hatchet13rydin69 said:
Not sure if this will work for your version but it can't hurt to try. It worked for my stock unrooted SM-G360T1
http://forum.xda-developers.com/gal...emoving-frp-protection-samsung-t3275584/page4
Let me know if this works for you
Click to expand...
Click to collapse
It doesn't work (or I'm missing something) just because I can't unlock my screen lock to install the APK.
If I'm missing something, please tell me.
What I'm looking for is a way to enable USB Debug mode without unlocking the screen (something like a Custom Recovery mode).
Read the entire post including he comments cuz that link I posted is a step by step guide to unlocking the phone. If the phone has not been factory reset yet then do that first so it causes the phone to go to the Google email verification page then follow the in the link step by step and you will have the phone unlocked. What you are doing with this guide is making a custom path to the settings menu for the phone enabling you to do a factory reset from the backup/reset setting. By doing so you will remove the link to any and all accounts that have been uses on the phone this making the device start just as it would had you bought it from the store and was doing the initial setup. Let me know if you get stick anywhere or need help
hatchet13rydin69 said:
Read the entire post including he comments cuz that link I posted is a step by step guide to unlocking the phone. If the phone has not been factory reset yet then do that first so it causes the phone to go to the Google email verification page then follow the in the link step by step and you will have the phone unlocked. What you are doing with this guide is making a custom path to the settings menu for the phone enabling you to do a factory reset from the backup/reset setting. By doing so you will remove the link to any and all accounts that have been uses on the phone this making the device start just as it would had you bought it from the store and was doing the initial setup. Let me know if you get stick anywhere or need help
Click to expand...
Click to collapse
But if I factory reset my phone, I will lose all my data, which I don't want to. Or via this "Backup/Reset" setting am I keeping my data?
Sorry for all this questions, but I'm pretty confused...
You will lose your data as this is the master factory reset but you can back up everything while in this menu to your Google account. After you factory reset go through the initial setup and come back to this menu and restore from your Google account
Can I backup my photos, music, documents etc. on my Google account? And how do I do it before resetting the phone?
sfn1701 said:
Can I backup my photos, music, documents etc. on my Google account? And how do I do it before resetting the phone?
Click to expand...
Click to collapse
Check out this guide here on lifehacker...
https://lifehacker.com/5976036/simp...droid-phone-from-the-desktop-no-root-required
Works great and doesn't require root to get it done. I know it is a lil different from what I mentioned earlier but I totally spaced this method until earlier today. Hope this helps you.
Man, my main problem is I can't enable USB debugging, having the screen locked! So I can't use any ADB method.
As far as I know there is no other way to backup your data without using adb methods without a custom recovery. Have you tried flashing twrp for your device and doing a full nandroid that way? I know that twrp has a compatible version for your device. Just search the forums here for you specific device model and flash using Odin 3.10
Here is the link to the twrp website go here to make sure you model is supported then download the tar.md5 file for tour device and flash using odin. Make sure to Uninstaller lies from your pc to avoid any issues with odin
http://twrp.me/
I had already tried flashing twrp, but when I tried to boot in recovery I did get a Bootloop and the "Recovery is not seandroid enforced" error.
sfn1701 said:
I had already tried flashing twrp, but when I tried to boot in recovery I did get a Bootloop and the "Recovery is not seandroid enforced" error.
Click to expand...
Click to collapse
Are you using the hardware keys to boot to recovery (volume up+home+Power buttons)? If you try to boot to recovery from any other method it will cause a recovery loop. It's a known issue with all variants of this divice. It's gonna show the "Recovery is not seandroid enforcing" but it will go into recovery.
Of course, I'm using Home+VolUp+Power.
Im out of ideas outside of trying to flash twrp again through Odin
sfn1701 said:
I forgot the PIN lock of my SM-G360F LTE (with Android 4.4.4), and I would like to keep all my files & documents inside it.
Click to expand...
Click to collapse
You can just try reflashing the stock firmware for your region in the AP slot of Odin from here.
http://sammobile.com/firmwares/database/SM-G360F/
It should keep all your data while it resets everything else like new.
bogarty said:
You can just try reflashing the stock firmware for your region in the AP slot of Odin from here.
http://sammobile.com/firmwares/database/SM-G360F/
It should keep all your data while it resets everything else like new.
Click to expand...
Click to collapse
But will flashing stock firmware remove the frp lock? Sorry still a lil new to all this and just trying to gain knowledge of everything I can.
hatchet13rydin69 said:
But will flashing stock firmware remove the frp lock? Sorry still a lil new to all this and just trying to gain knowledge of everything I can.
Click to expand...
Click to collapse
Yes. In fact, if you've tripped factory reset protection (FRP), it is the only way to fix it. Here's an example of where this worked for someone else. Read my comment here:
http://forum.xda-developers.com/showthread.php?p=65016084
Then also read the response that follows. Use the correct firmware for your device though at the link i gave above.
bogarty said:
Yes. In fact, if you've tripped factory reset protection (FRP), it is the only way to fix it. Here's an example of where this worked for someone else. Read my comment here:
http://forum.xda-developers.com/showthread.php?p=65016084
Then also read the response that follows. Use the correct firmware for your device though at the link i gave above.
Click to expand...
Click to collapse
I followed this guide here earlier his year and it worked without any problems
http://forum.xda-developers.com/gal...emoving-frp-protection-samsung-t3275584/page1
I'm still using the device that I used this guide for. Have recently rooted and installed twrp. Going to flash slimpickens rom later tonight
hatchet13rydin69 said:
I followed this guide here earlier his year and it worked without any problems
http://forum.xda-developers.com/gal...emoving-frp-protection-samsung-t3275584/page1
Click to expand...
Click to collapse
I understand that that guide has helped people and that's a good thing for sure. It's just that it's really the absolute most difficult way to fix a device that's under an FRP lock, as it's many steps rather than just the one step of flashing the stock firmware.
bogarty said:
I understand that that guide has helped people and that's a good thing for sure. It's just that it's really the absolute most difficult way to fix a device that's under an FRP lock, as it's many steps rather than just the one step of flashing the stock firmware.
Click to expand...
Click to collapse
I appreciate the help and insight. Will definitely keep this in mind in case I ever run into this problem again.