Related
Hi, my Nexus is on Android 5.0.1 (LRX22C). I haven't rooted or unlocked the bootloader; everything is totally stock. But I'm unable to successfully install the Android 5.1 OTA update. My phone downloads it, verifies it, then reboots to begin the installation process. After working on the update for a while, I see an error message (with an android on its back and a red "X"). The phone stays on that screen for a while, then eventually reboots without having installed the update. I've tried clearing cache, and it doesn't help. Anyone have any ideas?
carrot34 said:
Hi, my Nexus is on Android 5.0.1 (LRX22C). I haven't rooted or unlocked the bootloader; everything is totally stock. But I'm unable to successfully install the Android 5.1 OTA update. My phone downloads it, verifies it, then reboots to begin the installation process. After working on the update for a while, I see an error message (with an android on its back and a red "X"). The phone stays on that screen for a while, then eventually reboots without having installed the update. I've tried clearing cache, and it doesn't help. Anyone have any ideas?
Click to expand...
Click to collapse
Some more info please. What carrier are you using? Was your phone purchased from that carrier or somewhere else?
Evolution_Freak said:
Some more info please. What carrier are you using? Was your phone purchased from that carrier or somewhere else?
Click to expand...
Click to collapse
Thanks! I'm on T-Mobile, and bought the phone from Google Play.
carrot34 said:
Thanks! I'm on T-Mobile, and bought the phone from Google Play.
Click to expand...
Click to collapse
Are you familiar with sideload?
---------- Post added at 09:42 PM ---------- Previous post was at 09:37 PM ----------
Check out my thread on OTA's.
http://forum.xda-developers.com/showthread.php?t=2992919
In post #2, there's a link to the OTA files thread. Take the one that is specifically for T-Mobile. LRX22C to LMY47M.
Evolution_Freak said:
Are you familiar with sideload?
Click to expand...
Click to collapse
Yeah, I've sideloaded before with other devices, but I'd like not to have deal with wiping my phone to unlock the bootloader right now. I'd thought that by not rooting or messing with the bootloader, I'd keep things simple and be able to easily apply OTA updates. So I'm very frustrating that this isn't working. Any idea why this might be happening?
Thanks!
Alan
carrot34 said:
Yeah, I've sideloaded before with other devices, but I'd like not to have deal with wiping my phone to unlock the bootloader right now. I'd thought that by not rooting or messing with the bootloader, I'd keep things simple and be able to easily apply OTA updates. So I'm very frustrating that this isn't working. Any idea why this might be happening?
Thanks!
Alan
Click to expand...
Click to collapse
No, you do not need to wipe or unlock to sideload. Post #3 in the thread I linked, simple instructions on sideloading.
As for why this is happening, anyone's guess but it could, somehow, have something to do with your device having the T-Mobile Sim and being from Google play.
Evolution_Freak said:
No, you do not need to wipe or unlock to sideload. Post #3 in the thread I linked, simple instructions on sideloading.
As for why this is happening, anyone's guess but it could, somehow, have something to do with your device having the T-Mobile Sim and being from Google play.
Click to expand...
Click to collapse
OK, I'll give it a shot. Thanks! Any idea which OTA I want? I'm guessing it's LMY47M, since I'm on a T-Mobile SIM, even though the device was bought from Google? Need I worry that that build isn't up on Google's "Factory Images for Nexus Devices" page? And is there any risk that installing an update this way will make it more complicated to get OTA updates in the future? (I was hoping that by doing things the official way this time, I could avoid having to monkey around with stuff like this.)
Thanks!
Alan
carrot34 said:
OK, I'll give it a shot. Thanks! Any idea which OTA I want? I'm guessing it's LMY47M, since I'm on a T-Mobile SIM, even though the device was bought from Google? Need I worry that that build isn't up on Google's "Factory Images for Nexus Devices" page? And is there any risk that installing an update this way will make it more complicated to get OTA updates in the future? (I was hoping that by doing things the official way this time, I could avoid having to monkey around with stuff like this.)
Thanks!
Alan
Click to expand...
Click to collapse
Yes, you want the LRX22C to LMY47M OTA as I said before. No, you don't need to worry about it not being on the images page. Also a no for it affecting your ability to get OTA's in the future. On a Nexus, this is pretty much as official as getting the OTA natively.
OK, an update: got an error installing the update any way I tried, even after a factory reset. Called Google support, and they're replacing the phone for me.
ODIN FLASHABLE STOCK FIRMWARE
For the Samsung Galaxy Tab S2 - SM-T817P
**** UPDATE: JUNE 30, 2016 - For personal reasons, I am unable to continue to host the flashable tars or any other files for this device. Links have been removed. Moderators, please delete this thread or freeze it.
Sorry for the inconvenience.
These are untampered, unaltered, original firmware in the event that you need to recover from a soft brick or otherwise desire to / need to restore to out-of-box.
NOTE THIS WILL NOT RESET THE KNOX WARRANTY VOID COUNTER.
This will only restore original Samsung firmware
I will add links to new versions when they are released.
DOWNLOAD LINKS:
USE PASSWORD: XDAdevelopers
Password is case sensitive
5.1.1 - OL1 - Released December 23rd 2015 - Link Deleted
5.1.1 - OJ5 - Released November 11th 2015 - Link Unavailable
5.1.1 - OH6 - Initial Version Released September 11th 2015 - Link Deleted
Use ODIN 3.10.7 which can be downloaded at http://androidcentral.us/2013/11/download-odin/
** IF RESETTING, OR RECOVERING FROM A SOFT BRICK, After Flashing, boot to recovery and perform a factory reset or manually wipe /data and /data/media **
Thanks for this, alwwys good to have a copy of the stock firmware on hand.
**** UPDATE: JUNE 30, 2016 - For personal reasons, I am unable to continue to host the flashable tars or any other files for this device. Links have been removed. Moderators, please delete this thread or freeze it.
Sorry for the inconvenience.
**** UPDATE: JUNE 16 2016 - For personal reasons, I will soon be unable to host the flashable tars or any other files. June 30 I will be removing download links. I encourage you to download now. If anyone else wants to host or start a new thread, be my guest. If you host, I would be more than happy to link here.
Otherwise, June 30th, All links will be removed and I will be asking XDA Mods to close and/or delete this thread. Sorry for the inconvenience.
What's the difference between the Sprint version and the normal SM-T815? Is it possible to flash the Sprint firmware on a normal SM-T815?
P3CO said:
What's the difference between the Sprint version and the normal SM-T815? Is it possible to flash the Sprint firmware on a normal SM-T815?
Click to expand...
Click to collapse
NO absolutely not. I assume by "normal SM-T815" you mean WiFi Only? The image for the T817P contains both the radio for the 3G/4G LTE/Spark and Wifi, and is specifically meant for that specific model. If you try to flash it to yours, it might potentially HARD BRICK - as in no way to recover. It becomes a $400 - $800 (depending on what model) paperweight. Always only flash the OEM software for your specific model only.
If you're unable to find the firmware for your device, PM me and I can locate, host and send you a link for it.
What specifically is your model number? after the T-815 is there a letter? T-815X... what is X?
typefortytardis said:
NO absolutely not. I assume by "normal SM-T815" you mean WiFi Only? The image for the T817P contains both the radio for the 3G/4G LTE/Spark and Wifi, and is specifically meant for that specific model. If you try to flash it to yours, it might potentially HARD BRICK - as in no way to recover. It becomes a $400 - $800 (depending on what model) paperweight. Always only flash the OEM software for your specific model only.
If you're unable to find the firmware for your device, PM me and I can locate, host and send you a link for it.
What specifically is your model number? after the T-815 is there a letter? T-815X... what is X?
Click to expand...
Click to collapse
T815 is actually the LTE model, so not much different to the t817p.
Don't know why anyone would want to flash carrier firmware to an international model anyway unless they are attempting to use it with that network?
Unfortunately this is not always possible due to differences in the radio.
I'm adding a password due to bots downloading the file.
The Password is: XDAdevelopers
P3CO said:
What's the difference between the Sprint version and the normal SM-T815? Is it possible to flash the Sprint firmware on a normal SM-T815?
Click to expand...
Click to collapse
Some firmware for the international LTE model T815 is in the thread for the stock firmware collection here, and in my posts like this one and this one. Also see the very useful tool in this thread.
The stock firmware for T815 is still 5.0.2, not 5.1.1, if that was the reason for your question.
GidiK said:
Some firmware for the international LTE model T815 is in the thread for the stock firmware collection here, and in my posts like this one and this one. Also see the very useful tool in this thread.
The stock firmware for T815 is still 5.0.2, not 5.1.1, if that was the reason for your question.
Click to expand...
Click to collapse
Your tool was not able to decrypt the update it downloaded unfortunately. The update hasn't been pushed to Samsung Smart Switch yet so I can't grab and host the MD5 yet. And I have not been able to trick the OTA into downloading it yet even using xposed and wanam to set a fake system status. If you are able to update the decryption method, do let me know and I'll give it another go
typefortytardis said:
Your tool was not able to decrypt the update it downloaded unfortunately. The update hasn't been pushed to Samsung Smart Switch yet so I can't grab and host the MD5 yet. And I have not been able to trick the OTA into downloading it yet even using xposed and wanam to set a fake system status. If you are able to update the decryption method, do let me know and I'll give it another go
Click to expand...
Click to collapse
Not my tool, I was just pointing to the thread of the tool I used to download the firmware for the T815.
For T817P, SPR, the OJ5 seems indeed to be known in OTA mode, but not available for download yet; this also happened for T815 and that delay lasted about a day.
Does anyone have a OJ5 stock odin tar for SM-t817? I have twrp but the boot.img provided put me in a boot loop & I didn't make a backup like a noob.
Edit : Actually I think it was the super su zip (BETA-SuperSU-v2.52.zip)
The tablet is not usable @ all & it's actually a Christmas present for my son that I just wanted to setup & get going. So plz anyone with the file can use smart switch to download it would be greatly appreciated.
Thanks in advanced
Nvm, I'm on OJ5 (sprint variant t817p) & everything including boot.img & su zip work on the latest update. :highfive:
I'm bricked. I have a sprint t817p on latest firmware, and i keep getting frp lock fails on anything i flash in odin and i cant get to recovery, and it will not boot. I cant find the latest tar file, and all the older ones fail. Can anyone assist?
liquidhaste said:
I'm bricked. I have a sprint t817p on latest firmware, and i keep getting frp lock fails on anything i flash in odin and i cant get to recovery, and it will not boot. I cant find the latest tar file, and all the older ones fail. Can anyone assist?
Click to expand...
Click to collapse
I still have not had a chance to update mine. I am not certain why, but newer softwares for a lot of samsung devices have been hard to come by lately *suspiciously looks at Samsung*. Also I am out of town til the 20th of January.
As far as frp lock, or "Factory Reset Protection", you forgot to go into developer settings and enable "OEM Unlock".
It is basically like Samsung's 5.0 "Reactivation Lock", except this is enabled by default and encompasses KNOX verification. It cannot be circumvented now. HOWEVER.... there are TWO THINGS I can think of you can try (If anyone else has anything to add, please do)
1.) Try using the OH6 ROM with ODIN. Yes it's one edition older but it might work. I bricked by Galaxy Note5 after going to the latest firmware and forgot to disable FRP Lock (by enabling "OEM Unlock" under developer settings). Reflashing with ODIN worked. Then Flash your recovery, go into recovery, and format /data /system and /cache and dump the Dalvik/ART cache. Then boot back to download mode and re-flash the same ROM. Upgrade to most recent via OTA, then re root.
It worked when I ran into FRP lock errors with my note 5. it might work for you. It will not let you do anything that is not official samsung. Be prepared to log in with your samsung account info once you finally boot if you registered that before you bricked.
2.) Go to a Sprint store, pretend you're a tech illiterate and say after your cousin or someone messed with it, that happened. Sprint (most locations and employees anyways - try another if one fails) stick with the original pro-development attitude towards Android and will generally look the other way - and flash back the correct software or warranty replace it for you (YES EVEN IF KNOX IS Tripped)
TRY #1 first. It fixed my note which was bricked by FRP.
*Meant to type OH6 not AA1. That was a place holder while I typed (and tried to find the version info)
I already tried to flash oh6 and it won't take it. Probably going to try the tech illiterate route. To make matters potentially worse. It wasn't even on oj5 it was the newest update released Dec 23 (don't have the build number handy), I just found that out late last night. Fortunately Knox is not tripped though, I never made it that far. I guess forgetting to check oem unlocking will prevent a flash but not prevent said flash from corrupting your boot.img? Weaksauce.
typefortytardis said:
[...] and will generally look the other way - and flash back the correct software or warranty replace it for you (YES EVEN IF KNOX IS Tripped).
Click to expand...
Click to collapse
Really? I thought (and heard here and there) that once you tripped KNOX, you have no chance to make your clsims on the warranty. Please prove me wrong
Depressed T.Bear said:
Really? I thought (and heard here and there) that once you tripped KNOX, you have no chance to make your clsims on the warranty. Please prove me wrong
Click to expand...
Click to collapse
You do not. Once KNOX is tripped, your warranty is void. You are no longer eligible to turn in a claim.
However, certain carriers (however they organize their purchasing contracts) have it to where they are authorized to process, handle and fulfill the warranty. Sprint is one of those carriers in the US. And a lot of times you have in store agents that either do not get paid enough to care or otherwise still hold true to the original pro development spirit of Android.
I personally replaced 3 Galaxy S5 devices that had KNOX tripped. That store started actually checking my KNOX thing and didn't let a 4th happen so Samsung probably did not credit them, but my account was never charged back. I did it a 4th time at another Sprint store.
liquidhaste said:
I already tried to flash oh6 and it won't take it. Probably going to try the tech illiterate route. To make matters potentially worse. It wasn't even on oj5 it was the newest update released Dec 23 (don't have the build number handy), I just found that out late last night. Fortunately Knox is not tripped though, I never made it that far. I guess forgetting to check oem unlocking will prevent a flash but not prevent said flash from corrupting your boot.img? Weaksauce.
Click to expand...
Click to collapse
Then yes if you did not trip KNOX, you should have no problem pretending to be tech illiterate and having them swap it out for you or reflash it for you.
If they reflash, take it home and use Samsung SmartSwitch to do an "erase / initialization / reset" (however it is worded). Sprint might also be too lazy and just use the romfile and not the reset romfile which is equivalent to a "dirty flash". So go home and use Samsung Smart Switch to start fresh.
Then make sure you enable "OEM Unlock" under development settings next time you attempt root.
ashyx told me I should find someone with this tablet and the newest update that is still on a stock firmware, if they can possible make a backup of the boot.img and system.img using TWRP. This should help others who are stuck with the issues i'm reading on this post as well as the tablet I'm trying to fix now.
Thanks for reading
So here we have stock files pulled from the Motorola Firmware Team on AFH Just mirrored for your convenience
I cant include the firmware for Verizon & Att due to the fact there bootloaders are NOT unlocked. Therefore if somebody reads this and corrects me, they cant flash it.
I have the stock files and Flash Alls made by me and @Uzephi
Sprint Flash Alls made @Uzephi
Latest https://androidfilehost.com/?fid=889964283620761146
June https://androidfilehost.com/?fid=962021903579487984
Flash All T-Mobile made by me
August https://drive.google.com/file/d/1MW4JWa8Zij36hsO0u41Zf-9a6OT3FpbA/view?usp=drivesdk
June https://drive.google.com/file/d/0B1tqDJm_qQf4YWxreUJSWXJWeVk/view?usp=drivesdk
To use the flash all for Sprint and T-Mobile you simply unzip the file and put your phone into fastboot mode and hit flashall.bat and that's it. I have already included the fastboot file in the zip.
Requests: If you have a request for firmware please leave a message below.
Credits: @Uzephi
Motorola Firmware Team https://androidfilehost.com/?w=profile&uid=24269982087010314
Tested
Just tested the T-Mobile one and all worked perfect.
Will it work to downgrade from the OTA update yesterday?
crackerjack9249 said:
Will it work to downgrade from the OTA update yesterday?
Click to expand...
Click to collapse
Yes, i was on the Tmobile update 26.5 and it downgraded just fine.
Is it possible to flash a Verizon rom on sprint moto z2 force?
I got permission denied and now phone says corrupt won't boot, and to visit Motorola website unlock bootloader. Do I have to unlock bootloader first? How can I fix this?
lrosado said:
I got permission denied and now phone says corrupt won't boot, and to visit Motorola website unlock bootloader. Do I have to unlock bootloader first? How can I fix this?
Click to expand...
Click to collapse
I would say yes
Sent from my SM-N930F using XDA-Developers Legacy app
I am unable to enable one unlock since the phone bricked once I tried to install this. It wont boot. Any suggestions on how to get my device unbricked or any way to enable one unlock using adb?
Any chance we could get a tmo flash all of the august update?
Hasn't been released yet
Any way to fully lock this backup? Long story short the IMEI reads 0 and this didnt fix the issue, but I need to phone to be 100% stock.
matistight said:
Any way to fully lock this backup? Long story short the IMEI reads 0 and this didnt fix the issue, but I need to phone to be 100% stock.
Click to expand...
Click to collapse
I did a warranty exchange when this happened to me.
---------- Post added at 06:03 AM ---------- Previous post was at 06:01 AM ----------
Question, is there a way to make the bootloader not say you've unlocked and flashed different software?
Also, can I just flash the stock boot?
anyone got stock boot img for t-mobile? if so can you send me a link please
Does anyone know if I can run the fasboot command to lock the bootloader after I've flashed this? I need to take mine back in for an exchange.
charlatan01 said:
Does anyone know if I can run the fasboot command to lock the bootloader after I've flashed this? I need to take mine back in for an exchange.
Click to expand...
Click to collapse
fastboot oem lock
cfriendr said:
fastboot oem lock
Click to expand...
Click to collapse
Yeah, I know the command. I was just wondering if that was all it takes and if it worked. Sorry my question was so vague.
charlatan01 said:
Yeah, I know the command. I was just wondering if that was all it takes and if it worked. Sorry my question was so vague.
Click to expand...
Click to collapse
It half-worked for me. During boot-up, it doesn't give me the "unlocked bootloader" warning, but it *does* give me a "The OS installed is different" message. Looks similar, but the text is yellow instead of orange.
cfriendr said:
It half-worked for me. During boot-up, it doesn't give me the "unlocked bootloader" warning, but it *does* give me a "The OS installed is different" message. Looks similar, but the text is yellow instead of orange.
Click to expand...
Click to collapse
I'm trying to get rid of the "your device has loaded a difference operating system". Did you find the way to get the phone back to 100% stock?
First off, wanna give a HUGE THANKS to joemossjr for releasing this package AND for that .bat installer! Long story short, I was about to either claim warranty or Jump! (T-Mobile insurance/upgrade program) due to me trying to hook a USB Thumbdrive in over USB OTG (Kingston 16GB) and then there were slowdowns and app crashes, everywhere... heck it was to the point where I kept getting spammed with android.process.acore keeps crashing messages! Couldn't use many internet apps, no phone calls, and could barely text just to name a few.
I do got a suggestion though: is it possible to have a modified version of the June ROM package on Sprint & T-Mobile to where instead of having the stock boot.img, you can have the modified version with the Magisk root access? That would be great and somewhat of a convenience (YMMV; I used this patched boot.img on the 26.2 version and both system updates & t-mobile visual voicemail setup kept falling flat on its face everytime)
Thanks again, YOU ARE THE MAN!!!
Hello all, i have searched endlessly on this site and didnt quite find my answer. Or didnt understand what to do, as i am not up to speed to what everything means. A little background...
i bought a used t713 not knowing it was "bricked?" (MDM/FRP). When i first powered it on i was unable to do anything as the home screen does not allow anything to be done. The message "Device turned off, contact IT" appears. Cant access settings nor turn it off.
In my desperate attemps to do a hard reset without being able to turn it off, i reset the tablet then pressed the combination of keys and got it to the "andriod recovery" screen. Tried to "wipe data/factory reset" but was not successful due to mdm. What makes my case unique is that i cant access anything such as setting so any youtube vids or other posts does not really help. Aside from the fact that i do not understand what anything means... Odin vs flashing vs rooting vs etc.
Can anyone provide a solution where a total newbie can follow the instructions?
Please see the attached photos for issues and tablet software version. ***once i figure out how***
So i cant figure out how to post the pics but below is the info from the "Android Recovery" screen
samsung/gts28vewifixx/gts28vewifi
7.0/NRD90M/T713XXU2BQD3
Also, i was able to ender the download mode, which i figured is Odin mode. From there i can see the following options:
FRP LOCK: ON
Secure Dowload: Enable.
with the info provided above what would be my first step?
Flash via odin? Then do a FRP bypass?
If you can enter Download Mode, then flash it with the latest of Android 6 and proceed to bypass FRP
This FRP lock is a joke because many can do it without any problem as long they read and do it properly
h
Beut said:
If you can enter Download Mode, then flash it with the latest of Android 6 and proceed to bypass FRP
This FRP lock is a joke because many can do it without any problem as long they read and do it properly
Click to expand...
Click to collapse
Is there any specific odin version to use? From reading there are a few places to get Android 6... sammobile?
The Odin version is not important as long as it’s close to the latest one. Search Google FRP bypass you will see many discussions from this forum. Read carefully what others did, you will see it’s a piece of cake.
You need to read In order to see mistakes others did too and why they failed.
I'm in the same situation. A used SM-T713 that has FRP lock on. I've researched the web and seen every YouTube scam there is. I've downloaded oldest firmware available on Sammobile and flashed with ODIN. I've also used the newest firmware available from Sammobile. Notta. I am so very very frustrated. There are about a bazillion people with this situation and I cannot find a one that has managed to bypass the FRP lock. If you know how to help, OMG, I would be sooooooooo very grateful. I'm not new to flashing. I have rooted many phones, flashed many ROMS, very familiar with TWRP and Superuser and Chainfires cfautoroot. Is there any hope? Of do I just smash the heck out of this thing and burn it to a puddle of plastic in the middle of my living room????
CanadaHugh said:
I'm in the same situation. A used SM-T713 that has FRP lock on. I've researched the web and seen every YouTube scam there is. I've downloaded oldest firmware available on Sammobile and flashed with ODIN.?
Click to expand...
Click to collapse
You should be patient , FRP is a joke as long as you know how. In order to bypass, you should be specific what build you currently have.
Forget the Android 7 because most methods which don't use OTG cable are not working. The best way is downgrade to Android 6.
I don't have this model but the most popular methods are using Talk Back to open chrome, Hot Spot to create new users, and using Assist to open chrome.
You see a lot of youtube videos which are not working because most posters don't understand a method only work with certain build and model.
As long as you can open Chrome to download needed apps , FRP will be gone . I can bypass FRP on 5 different Samsung tablets so it's not a rocket science as long as you know which method works and uses it.
This is an example of method using Talk Back
https://www.youtube.com/watch?v=fhP_egvc6v0
Thank you for taking time to reply. I've seen this exact message you pasted here. I've tried to do all 3 possibilities offered with no success. I have current os of nugat. I've got backup from sammobile. Also used Odin to attempt downgrade to 6...fail because ftp lock prevents flash in odin. Tried talk back. ..the L during tutorial is prevented. So, for me anyway, this is rocket science! Please allow me the dignity of being able to read, search, view, attempt. ...every conceivable avenue for solution.
My device is SM-T713 running latest update of Nougat with FRP lock on. I do not know the previous user name and password so can not bypass FRP. Does this explanation clarify my dilemma? Do you possibly have a blueprint of the rocket science? Most of the Web results lead to dead end spams.
I see a common mistake of failing to bypass FRP: using methods only work with Android 6. All methods I mentioned only work with Android 6, use it to bypass FRP a tablet with Nougat is pointless because it's not applicable.
Downgrade to Android 6, you need to flash 3 files BL, AP, and CSC. Common mistake when downgrade is just flashing the AP file only.
This is an example of failing to downgrade
https://forum.xda-developers.com/showpost.php?p=76148948&postcount=9
I have done downgraded Android 7 to Android 6 hundred times without any issue to bypass FRP.
Again, thank you for taking time to reply. I sincerely appreciate your efforts.
Sent from my SM-N900W8 using Tapatalk
As long as you can downgrade, I am sure you can bypass FRP as Android 6 has many security flaws that a certain method will work.
Like SM-T280 , it's Lollipop but I can only use Talk Back method with older build. SM-T670, SM-T377 also is Lollipop but I have to use Hot Spot method with the current build.
SM-T560, Hot Spot method only works with older builds of Android 6, the latest build of Android 6 has to use Assist method.
SM-T580, P580 I can bypass FRP on both Android 6 and 7, but the method used in Android 7 will trigger Knox count.
These are few examples what can be done to bypass FRP on 6 different Samsung tablets . It's the same like a certain move in self defense, you cannot use it in every single situation or position. Apply wrongly, you will be hit or fail. As long as you know which one will work, FRP lock is a joke to me.
Beut said:
As long as you can downgrade, I am sure you can bypass FRP as Android 6 has many security flaws that a certain method will work.
Like SM-T280 , it's Lollipop but I can only use Talk Back method with older build. SM-T670, SM-T377 also is Lollipop but I have to use Hot Spot method with the current build.
SM-T560, Hot Spot method only works with older builds of Android 6, the latest build of Android 6 has to use Assist method.
SM-T580, P580 I can bypass FRP on both Android 6 and 7, but the method used in Android 7 will trigger Knox count.
These are few examples what can be done to bypass FRP on 6 different Samsung tablets . It's the same like a certain move in self defense, you cannot use it in every single situation or position. Apply wrongly, you will be hit or fail. As long as you know which one will work, FRP lock is a joke to me.
Click to expand...
Click to collapse
Thank you for taking time to explain the joke
Seriously, this security lock is a joke as I can do with ease on different Samsung tablets. Read this forum you will see, newbies would have troubles to unlock their tablets
but eventually they are able to bypass this FRP lock. So again, it's not a rocket science, you need to be patient and try different methods.
I started the same like yours, didn't know what to do. However, by learning and practicing, I do actually see it's a piece of cake as long as you understand which method can apply to a certain build or OS.
Beut said:
I see a common mistake of failing to bypass FRP: using methods only work with Android 6. All methods I mentioned only work with Android 6, use it to bypass FRP a tablet with Nougat is pointless because it's not applicable.
Downgrade to Android 6, you need to flash 3 files BL, AP, and CSC. Common mistake when downgrade is just flashing the AP file only.
This is an example of failing to downgrade
https://forum.xda-developers.com/showpost.php?p=76148948&postcount=9
I have done downgraded Android 7 to Android 6 hundred times without any issue to bypass FRP.
Click to expand...
Click to collapse
So i downloaded odin, samsung drivers and 7zip. As well as APK6 firmware (latest Android 6 fw i found on updato). From the APK6 download, there was only one tar.md5 file. Question is should i find fw that has the 3 seperate files or running the one i have in AP should work?
Flash the AP file only, it may not erase user data and factory reset. You can try it, it may pass Odin but starts at the same lock screen again.
If you need the BL and CSC files, I could upload for you, but this is an US version.
Beut said:
Flash the AP file only, it may not erase user data and factory reset. You can try it, it may pass Odin but starts at the same lock screen again.
If you need the BL and CSC files, I could upload for you, but this is an US version.
Click to expand...
Click to collapse
So i was able to downgrade the firmware to APK6, with only the AP file but i was greeted with an "to start up device enter password" message. Something i havent seen before... not same lock screen
Tried to do factory reset and failed due to mdm.
https://drive.google.com/file/d/1pwDFqzrl3Dqt9V6ZpDCz60tOutmmpYOM/view?usp=sharing
Flash again with BL, AP, and CSC , this is US firmware.
Beut said:
https://drive.google.com/file/d/1pwDFqzrl3Dqt9V6ZpDCz60tOutmmpYOM/view?usp=sharing
Flash again with BL, AP, and CSC , this is US firmware.
Click to expand...
Click to collapse
Thanks for the files. Flashed all three files and was still greeted with the enter password screen. Mdm still prevents factory reset when trying to resetthru recovery menu. Any other pointers?
Gamma35 said:
Thanks for the files. Flashed all three files and was still greeted with the enter password screen. Mdm still prevents factory reset when trying to resetthru recovery menu. Any other pointers?
Click to expand...
Click to collapse
Are you on marshmallow now or nougat?
ashyx said:
Are you on marshmallow now or nougat?
Click to expand...
Click to collapse
I am on marshmallow.
Hi All. First post so please be gentle.
After searching and googlingfor a long time, i have tried a few ways to root my S20 FE (4G).
I have tried KingRoot, no success.
I have tried going down the flashing route, but I am greeted with 'Only official can be flashed (recovery) and (vbmeta) - i have tried flashing the vbmeta disabled.... I also tried using Magisk to create a modified AL file and then flashing it back, but that gave the same result as above.
I have unlocked the bootloader, made a mess first time, so flashed back to stock. Re-locked and unlocked bootloader again.
I'm hoping there is a simple thing that I have got wrong, or forgotten to do etc.
Searches of google for the error message about official firmware etc. turned up a few results, but they all seemed to be flashing other stuff, which it seems i cannot do.
Any ideas?
tonyboy_23 said:
Hi All. First post so please be gentle.
After searching and googlingfor a long time, i have tried a few ways to root my S20 FE (4G).
I have tried KingRoot, no success.
I have tried going down the flashing route, but I am greeted with 'Only official can be flashed (recovery) and (vbmeta) - i have tried flashing the vbmeta disabled.... I also tried using Magisk to create a modified AL file and then flashing it back, but that gave the same result as above.
I have unlocked the bootloader, made a mess first time, so flashed back to stock. Re-locked and unlocked bootloader again.
I'm hoping there is a simple thing that I have got wrong, or forgotten to do etc.
Searches of google for the error message about official firmware etc. turned up a few results, but they all seemed to be flashing other stuff, which it seems i cannot do.
Any ideas?
Click to expand...
Click to collapse
Here is a guide: https://www.naldotech.com/root-samsung-galaxy-s20-fe-magisk/
tonyboy_23 said:
Hi All. First post so please be gentle.
After searching and googlingfor a long time, i have tried a few ways to root my S20 FE (4G).
I have tried KingRoot, no success.
I have tried going down the flashing route, but I am greeted with 'Only official can be flashed (recovery) and (vbmeta) - i have tried flashing the vbmeta disabled.... I also tried using Magisk to create a modified AL file and then flashing it back, but that gave the same result as above.
I have unlocked the bootloader, made a mess first time, so flashed back to stock. Re-locked and unlocked bootloader again.
I'm hoping there is a simple thing that I have got wrong, or forgotten to do etc.
Searches of google for the error message about official firmware etc. turned up a few results, but they all seemed to be flashing other stuff, which it seems i cannot do.
Any ideas?
Click to expand...
Click to collapse
there is only one method that is going to work for you, that method is linked above.
the problem with instructions can be when you don't know what they mean and the way they're written assumes you should.
there are many steps and they are all crucial (like unlocking the bootloader first).
if you don't understand what something means paste it here and ask, people will help you.
bininga59 said:
Here is a guide: https://www.naldotech.com/root-samsung-galaxy-s20-fe-magisk/
Click to expand...
Click to collapse
Thank you. I have followed the guide to the letter. My screen (in dl mode) is showing OEM bootloader thingy lock is OFF... but I am still getting the 'only official...' error message when trying to flash the boot tar file made in the guide
3mel said:
there is only one method that is going to work for you, that method is linked above.
the problem with instructions can be when you don't know what they mean and the way they're written assumes you should.
there are many steps and they are all crucial (like unlocking the bootloader first).
if you don't understand what something means paste it here and ask, people will help you.
Click to expand...
Click to collapse
Thank you. I feel i understood what I was supposed to do in each step, but i still get the only official... message. The lock is showing as 'OFF' on the DL screen, but it still blocks me.
tonyboy_23 said:
Thank you. I feel i understood what I was supposed to do in each step, but i still get the only official... message. The lock is showing as 'OFF' on the DL screen, but it still blocks me.
Click to expand...
Click to collapse
The switch in developer mode MUST be like this (picture), otherwise you cannot flash or root custom roms, custom kernels, etc.
I've read that sometimes you have to wait a few days for it to show up as unlocked finally. also you can't lock a brand new phone instantly, you've got use it a few days too.
bininga59 said:
Here is a guide: https://www.naldotech.com/root-samsung-galaxy-s20-fe-magisk/
Click to expand...
Click to collapse
this guide is for SM-G780F, the model is SM-G780G, the guide is for exynos version, i have the snapdragon version but without 5g(SM-G780G), since the chipset is different, i cant see how it works
leokratos17 said:
this guide is for SM-G780F, the model is SM-G780G, the guide is for exynos version, i have the snapdragon version but without 5g(SM-G780G), since the chipset is different, i cant see how it works
Click to expand...
Click to collapse
rooting is pretty universal at the moment barring a couple OEM specifics. pretty much all Samsung phones root the same way.
thanks you guys, i was able to root, first time the device booted, i got bootloop, but i reseted to factory and boom, rooted and working flawless
leokratos17 said:
thanks you guys, i was able to root, first time the device booted, i got bootloop, but i reseted to factory and boom, rooted and working flawless
Click to expand...
Click to collapse
I have the same version, sm g 780g without the 5g (Brazilian version) can you help me to root?
leokratos17 said:
thanks you guys, i was able to root, first time the device booted, i got bootloop, but i reseted to factory and boom, rooted and working flawless
Click to expand...
Click to collapse
I also have this s20fe G780G 4g model I'm from Brazil, make a Tutorial help and...
The "OEM unlock" option I missed first but suddenly, after updates of the pre-installed apps and reboots, I got it.
I haven't tried to root as far and directly on front of my vacation.
Hit a wall trying to unlock BL, enabled in dev options and adb into DL mode but LONG PRESS VOL UP is not working! So there is no way to actually unlock BL!??!!?
WTF?