This difficulty is noted specifically on the Galaxy Tab A6 10.1 (SM-T580 and the SM-T585)
After searching through XDA Forums for a solution, I, along with others are at a loss. This Custom binary blocked by frp lock is rather difficult and exibits 4 different ways of showing itself. All but one has basically the same symptoms, which are:
1. Startup goes to bootloop. One version displays Custom binary blocked by frp lock on the Logo Screen.
2. Download Mode is accessible, but not usable. Not accepting of official stock firmware. Also Custom binary blocked by frp lock shown here in another version.
3. Recovery mode inaccessable. Redirects to a screen similar to Download Mode. In upper left, Custom binary blocked by frp lock is displayed. (This one was my device. I solved issue by flashing "Binary 4 FRP Unlock" via Odin. Others could not solve issue).
4. Same symptoms as 1 and 2. However Recovery mode was accessable, not usable. Custom binary blocked by frp lock also present.
I've tried everything I can find on it. Downgrade, flash Binaries 3 and Binaries 4. Flash TWRP, Flash stock firmware. OEM Unlock, 3 files, 4 files, repair files. Nothing seems to work.
Does anyone familiar with this have any good ideas that I haven't used or thought of? This ones got me baffled!
Solution for some, not all.
Casper Young said:
This difficulty is noted specifically on the Galaxy Tab A6 10.1 (SM-T580 and the SM-T585)
However I'm beginning to hear of it on other varients of the Tab A.
Here's the files most people that have a Galaxy Tab A SM-T580 or SM-T585. will need'
SM-T580 Binary 4 FRP Unlock
https://drive.google.com/open?id=1iXrZR2E7m6Ai5InAw8u3lzeLhb3ThRo5
SM-T580 U4 Binaries (this is a two pack. Flash 1 then flash 2 in the AP section)
1. https://drive.google.com/open?id=1rX_luP_0W4ygdloIr2Gr9TCSfqFyaTK-
2.https://drive.google.com/open?id=1xsw4GVYtNMJhiMXV2cR2jaJvToG_n6Pi
For anyone that has symptoms 1,2 and 3. either one of the files I put here may work. After that you can flash the official firmware to your device. Flashing the binary files often reset the device. I have the 4 file for the T580 if anyone needs it.
Click to expand...
Click to collapse
I realize this is a bit old but I am at a loss with a t580.. I think I am confused at this point..I have odin and have replaced the .ini file with one you have listed. what happens next? I think I need a bit more instructions.. the other two files give a bad binary code...also you mention the 4 file for the t580.. nothing I find has 4 files.. only 3 ... no CP file. Thanks for any info..
cnicely said:
I realize this is a bit old but I am at a loss with a t580.. I think I am confused at this point..I have odin and have replaced the .ini file with one you have listed. what happens next? I think I need a bit more instructions.. the other two files give a bad binary code...also you mention the 4 file for the t580.. nothing I find has 4 files.. only 3 ... no CP file. Thanks for any info..
Click to expand...
Click to collapse
It may seem old but people are still having this difficulty and I seem to be the only one who bothers to investigate as well as try to help.
Tablets normally do not use the CP file which is for phone operations.
Here's my copy of the current 4file software. You'll notice it has two CSC files one labled HOME. You put one of in the CSC section of Odin3 when flashing. Which one depends on if you want to keep your application data or not. If you wish to keep your application data use the one labled "HOME"
https://drive.google.com/open?id=1zvhwUfSRW44V1ZwEsHLRvlh-T0M79ks9
Okay so you're stuck in some kind of Custom Binary FRP lock, can you define which of the 4 scenarios you are having?
Slightly of track, it seems this issue may come up with other and newer devices, so I'll tell you where the binary identifier of your device can be found. Our device currently has the firmware listed as T580UEU4CSC1. The U4 is the binary level of the bootloader I don't know what the U is for but the 4 represents the binary structure that has to be matched. Whatever binary number that may change to, it will always be in the same place.
The following two files are flashed one at a time. They are labeled somewhat use the one with a 1 first. Place it in the AP section on Odin3 and flash. You can either uncheck the reboot option or be prepared to go to download mode while the device reboots. by holding Power+Volume Down+ Home Button. Once back in Download mode place the second file in the AP section and flash. Be aware this method was used on another device than mine. It is one that came up during research and worked for someone I was assisting after the first method failed.
1. https://drive.google.com/open?id=1rX_luP_0W4ygdloIr2Gr9TCSfqFyaTK-
2. https://drive.google.com/open?id=1xsw4GVYtNMJhiMXV2cR2jaJvToG_n6Pi
I can't currently locate my Combination or Repair files. It may be the first link I sent you. They should be listed with BL, AP and the two CSC files you only use one of. They go in their respective spaces and there isn't a CP file.
The file you mentioned as ini was not that when I first uploaded it and has somehow changed. It was a patched Odin3 that worked better for this issue so it looks like I have two files to locate in my vast file system that I'll put up here by tomorrow. The patched Odin3 and the U4 Binary Unlock. Meanwhile...
This is the file that got me out of Custom Binary FRP Lock. Place it in the AP section of Odin3 and flash. Right after that, reboot to Download Mode and flash in the 4 file.
https://drive.google.com/file/d/1Rip0qIGo-GbzFdH55s1vIpe6f1aqYKbD/view
Hopefully that works for you.
Hi, thanks for your post. Does it work also for the T585? It's exactly T585XXU2BQK5
ParadiseEagle87 said:
Hi, thanks for your post. Does it work also for the T585? It's exactly T585XXU2BQK5
Click to expand...
Click to collapse
The method works but the files here will not work for you because your device is using a binary 2. Although the T580 and the T585 are essentialy the same device yours can access the network and uses the CP file. I'll save you some time with this link. https://combinationfirmware.com/downloads/t585xxu2apl1/
Casper Young said:
The method works but the files here will not work for you because your device is using a binary 2. Although the T580 and the T585 are essentialy the same device yours can access the network and uses the CP file. I'll save you some time with this link. https://combinationfirmware.com/downloads/t585xxu2apl1/
Click to expand...
Click to collapse
Hi, thanks for the link but there is now "Download" button except for other versions like T585XXU2ARC2 and T585XXU2AQC1 but no download button for T585XXU2APL1
Thank you
Thank you for the reply. I will work on this early next week. Hopefully I can follow everything..from what I read I think I understand a bit more than I did. Thank you again for the effort you put in to help out those of us who are not "into" this on a regular basis.
Thank you
WHOHOO!!! I did it...not sure what I did but I did it. I tried both unlock files and the combination put me in factory binary mode.. I could check and test everything but didn't know what else to do.. If I remember correctly I then did the 4 files (again) and when it rebooted it came up without the FRP. but It appears to be running fine. Thanks to Casper Young for the time taken to help out...can't express enough my appreciation for the time and effort you gave.
ParadiseEagle87 said:
Hi, thanks for the link but there is now "Download" button except for other versions like T585XXU2ARC2 and T585XXU2AQC1 but no download button for T585XXU2APL1
Click to expand...
Click to collapse
Are you still having difficulties? Sorry I didn't respond sooner, I was on vacation. Let me know if you still need assisstance.
Thank Casper for this interesting post.
Do I understand you correctly, that this solution only helps to recover from a FRP lock situation and flash back the original firmware, but does not allow you to install a custom rom on the device?
Bass3rr said:
Thank Casper for this interesting post.
Do I understand you correctly, that this solution only helps to recover from a FRP lock situation
Click to expand...
Click to collapse
Maybe you do, maybe you don't. You would have to clarify what type of FRP you are experiencing. There are two types. The most commonly known FRP situation has to do with the Google Account Sign in. This is the one where the device can somewhat be accessed but only goes as far as the Google sign in page and you're stuck there because you don't have the proper password to get past it and into the device to use it.
No, this is not that kind of FRP!
This one has to do with when someone roots and/or flashes a corrupt or bad file into their Android and overloads the binaries (the operating system) and you can get stuck at various places but cannot use the device, flash a custom Rom or the Official software into the device and therefore it's rendered useless for the time being. It does not let you get to the sign in page. It does not let you use Recovery. It only seems to bootloop then shut down or stay on or locked on that screen. It does not seem to let you use Odin3 to flash files to return it to normal. And you'll get a red letter notice at the top of the screen saying "Custom Binaries Blocked by FRP Lock.".
Is that discriptive enough to answer your question?
Thanks for your reply Casper.
I was experiencing the second type (red letter notice).
After an earlier failed attempt and reading on this forum, I was aware of the requirement to delete the Google account prior to flashing. After ODIN flashing TWRP, custom Rom and no verity, i used my own Google account for testing . Everything seemed to work just fine. After I deleted my own Google account and installed my daughter's, I got the FRP lock upon the next reboot.
Am I still doing something wrong?
Hello, i have a T-585 in my hands, that has no recovery, no nothing. The only way i can boot up device is in Download mode, and in a blank blue screen ( i guess it is the same download mode, but without any text on screen, the background color is the same though). The problem is, i can't flash any rom on it, even stock rom, i get an error everytime. Newest rom won't flash through Odin (tried different versions), gives me error, if i try older rom, i get an error, it seems i need binary 6 to flash something. It has a FRP lock too. Don't really know what to do. If anyone has any ideas how to fix this, please help. I have been searching an trying to fix this 5 nights in a row, but no luck and no success.
Re-emrgence
mezablusa said:
Hello, i have a T-585 in my hands, that has no recovery, no nothing. The only way i can boot up device is in Download mode, and in a blank blue screen ( i guess it is the same download mode, but without any text on screen, the background color is the same though). The problem is, i can't flash any rom on it, even stock rom.
Click to expand...
Click to collapse
With the exception of the words written in red letters it sounds like you may have come to the right place. Well let's find out if you're somehow in Binary FRP Lock. Did you recently try to flash in a cutom ROM or Root firmware? As far as I'm aware the T580 and the T585 can use the same files but it's been a while and I'd have to check. Here's what it sounds like you're dealing with. Are you being redirected to a blue screen with nothing on it? Now that's odd because on mine I tried to go to Recovery Mode and got redirected to the Download mode screen which is light blue, however, mine had the words "Custom Binaries Blocked by FRP Lock" You not having it there is a first that I've heard. But so far I've noticed 5 or 6 different versions of this and only half have managed to correct the matter. Let's see. First your going to need the Odin3.13B Patched Downlader and let me see if I can find the files you may need, or at least lead you to them.
Odin3.13.1B,
https://drive.google.com/drive/folders/1YCiv190uj7Cu_Yu_2onmYe3kbaDduhbl
The current firmware for the T585 should be,
Build No. T585XXU6CSK1
So yes this would indicate your device is running the U6 Binaries. Here's a combination file you should be able to use.
https://drive.google.com/file/d/1cpWRqDUQZmUhE5xoKuyc4BptCWT7X9DQ/view
And then flash in the official stock firmware.
Casper Young said:
With the exception of the words written in red letters it sounds like you may have come to the right place. Well let's find out if you're somehow in Binary FRP Lock. Did you recently try to flash in a cutom ROM or Root firmware? As far as I'm aware the T580 and the T585 can use the same files but it's been a while and I'd have to check. Here's what it sounds like you're dealing with. Are you being redirected to a blue screen with nothing on it? Now that's odd because on mine I tried to go to Recovery Mode and got redirected to the Download mode screen which is light blue, however, mine had the words "Custom Binaries Blocked by FRP Lock" You not having it there is a first that I've heard. But so far I've noticed 5 or 6 different versions of this and only half have managed to correct the matter. Let's see. First your going to need the Odin3.13B Patched Downlader and let me see if I can find the files you may need, or at least lead you to them.
Odin3.13.1B,
https://drive.google.com/drive/folders/1YCiv190uj7Cu_Yu_2onmYe3kbaDduhbl
The current firmware for the T585 should be,
Build No. T585XXU6CSK1
So yes this would indicate your device is running the U6 Binaries. Here's a combination file you should be able to use.
https://drive.google.com/file/d/1cpWRqDUQZmUhE5xoKuyc4BptCWT7X9DQ/view
And then flash in the official stock firmware.
Click to expand...
Click to collapse
Hello, i've been away for a few days, thank you for the reply, i'll try to use files that You put out tomorow, and give You an update. If this works, You're a magician.
I didn't try to Root or flash custom rom on this tablet. A friend gave it to me because it had a cracked screen, so i could change it. Also it was left for sometime and wasn't used, so was completely discharged. I changed the screen and charged it, but it wouldn't boot up, so i thought it maybe had failed to update or something, tried to flash a Stock rom, but it wouldn't flash through Odin. Older ones give the binary error so i need a U6, tried different of those, but still no luck. At the end I even thought maybe that there may be some physical damage ( friends kid steped on it, that's how the screen got cracked), but doesn't look like it.
I have a minor problem downloading frp unlock. Google doesn't let me download it. Sorry, you can't view or download this file at this time. I guess i have to wait some time....
Ok, so i managed to download the zip file from GDrive, but there is a password on the archive. I can't extract files from the archive, it has a password.
Found the password under some Youtube video. Tried to flash the Combination with Odin, it failed. Here's the log from Odin.
<ID:0/003> Removed!!
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1301)..
<ID:0/003> File analysis..
<ID:0/003> Total Binary size: 1366 M
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Tried adding a PIT file while flashing too, but i had the same result.
mezablusa said:
I have a minor problem downloading frp unlock. Google doesn't let me download it. Sorry, you can't view or download this file at this time. I guess i have to wait some time....
Ok, so i managed to download the zip file from GDrive, but there is a password on the archive. I can't extract files from the archive, it has a password.
Found the password under some Youtube video. Tried to flash the Combination with Odin, it failed. Here's the log from Odin.
<ID:0/003> Removed!!
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1301)..
<ID:0/003> File analysis..
<ID:0/003> Total Binary size: 1366 M
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Tried adding a PIT file while flashing too, but i had the same result.
Click to expand...
Click to collapse
Are you certain that the firmware you are trying to flash is for your specific model number?
When you flash via Odin, disable the "re-partition" option in Odin.
Sent from my SM-S767VL using Tapatalk
Droidriven said:
Are you certain that the firmware you are trying to flash is for your specific model number?
When you flash via Odin, disable the "re-partition" option in Odin.
Click to expand...
Click to collapse
Yes, i'm certain. What other firmware could I flash on sm-t585? The only other firmware i could think of flashing would be for t580, but i didn't try to do that. I tried older version roms for t585, but i got an error on tablet screen because of binary 6.
So the only rom i can try to flash is the newest with U6, at least i don't get an error on tablet screen, but Odin still fails.
When I flash i have enabled only auto reboot and F.reset time. Re-partition option is disabled.
I'm kind of lost at this point...
mezablusa said:
Yes, i'm certain. What other firmware could I flash on sm-t585? The only other firmware i could think of flashing would be for t580, but i didn't try to do that. I tried older version roms for t585, but i got an error on tablet screen because of binary 6.
So the only rom i can try to flash is the newest with U6, at least i don't get an error on tablet screen, but Odin still fails.
When I flash i have enabled only auto reboot and F.reset time. Re-partition option is disabled.
I'm kind of lost at this point...
Click to expand...
Click to collapse
When you flash the U6 firmware and it fails, can you tell me if it gives you any specific errors ?
Can you tell me at which step in the flashing process it fails?
Have you tried using different versions of Odin?
Have you tried using a different PC?
Sent from my SM-S767VL using Tapatalk
Related
Before marking this as a duplicate, please note that I've gone through almost every thread on this and different possibilities, but nothing had worked.
This morning, I rooted my AT&T Samsung Galaxy S5 (US) using towelroot. The root was successful. Next I downloaded Superuser from the Play Store (not the Chainfire one). It said it needed to update something using recovery mode, but it failed with an error. So, I ignored it and continued using the phone. Next, I downloaded the Google Now Launcher from Android L, to get Material Design. I installed Sliding Explorer from the Play Store to access root files. I also got a simple text edit app. To get Material Design, I needed to change ro.build.version.codename=REL to =L in build.prop. When I did and tried to save, it said access denied, so I changed permissions (oops!) to allow the file to be saved. Still didn't work for some reason so I saved the file as build.prop somewhere else and cut and pasted it in. Then, I rebooted my device and it got stuck on the boot screen with the Samsung Galaxy S5 logo with powered by Android beneath it.
What I've tried:
- I have wiped data, the cached, but there is no advanced option for me to wipe dalvik in the stock recovery for the Galaxy S5.
- When I try to use ADB, my device shows up as sideload and sideloading a ROM goes to 100% but ends up in an error. I cannot run ADB Shell, which ends in error:close.
- Using Odinv3 Build 3.09, I think, gets stuck on connecting to the phone, while Odinv3 Build 1.85, I think, gets fails at Complete(Write) error after something to do with NAND write.
My device drivers are all updated, and I've tried different USB ports, even different PC's. Nothing works. How can I fix this? Thanks!
I am allergic to posts that use Urgent in the title. Obviously you'd like to regain use of your phone ASAP. But how that makes your post more important than someone else's is a mystery. Nevertheless, I'm sure that someone else will be along soon to help you.
If you don't find something more expedient, the most reliable solution for a non-bricked phone is to Odin flash a full, stock firmware image that matches your baseband version.
.
fffft said:
I am allergic to posts that use Urgent in the title. Obviously you'd like to regain use of your phone ASAP. But how that makes your post more important than someone else's is a mystery. Nevertheless, I'm sure that someone else will be along soon to help you.
If you don't find something more expedient, the most reliable solution for a non-bricked phone is to Odin flash a full, stock firmware image that matches your baseband version.
.
Click to expand...
Click to collapse
Problem is, as I said, Odin has errors every time I try to flash, different ports and even different PC's. Maybe I'm not doing it correctly? And I'm sure I get the correct version.
Sorry for the Urgent ?.
tforkan99 said:
Problem is, as I said, Odin has errors every time I try to flash, different ports and even different PC's. Maybe I'm not doing it correctly? And I'm sure I get the correct version.
Sorry for the Urgent ?.
Click to expand...
Click to collapse
You've made some ill advised mods. Now we need more information. Post as many details as you can so that we can spot were the exact problem is.
Paste the exact error from both Odin vetsions here.
Is this originally an ATT phone?
Regular model (i.e. not the special unlocked Developer version)?
Do you know if it the new re-activation lock feature is enabled?
Do you know the phone's baseband /exact firmware version?
Do you have a recent backup?
Are you still able to boot to recovery mode (vol up + home + power)?
Did you ever successfully use Odin with this phone before the bootloop happened?
Perhaps you could remove the Urgent from your title? Edit /Delete > Go Advanced
.
fffft said:
You've made some ill advised mods. Now we need more information. Post as many details as you can so that we can spot were the exact problem is.
Paste the exact error from both Odin vetsions here.
Is this originally an ATT phone?
Regular model (i.e. not the special unlocked Developer version)?
Do you know if it the new re-activation lock feature is enabled?
Do you know the phone's baseband /exact firmware version?
Do you have a recent backup?
Are you still able to boot to recovery mode (vol up + home + power)?
Did you ever successfully use Odin with this phone before the bootloop happened?
Perhaps you could remove the Urgent from your title? Edit /Delete > Go Advanced
.
Click to expand...
Click to collapse
Odin3 v3.09: Stuck on "SetupConnection"
Odin3 v1.85:
<ID:0/005> NAND Write Start!!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<ID:0/005> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
Yes, originally ATT
Regular model
Don't know about re-activation lock
I think the firmware version is the problem. The last update was the one from ATT that added Yellowpages and Lookout in May. Don't know version. I've been download an April build so maybe that's why there is an error. My phone says "SW REV CHECK FAIL : [aboot]Fused 2 > Binary 1" which apparently occurs when downgrading. Maybe if I can get an updated ROM, I can use Odin? And I've seen suggestions to use Odin3 v3.04, but same error with the April build. I can't find the May build anywhere.
Maybe this will work?:http://forum.xda-developers.com/showthread.php?t=2737257 But it's .zip and I can't flash it with Odin.
I have a Kies backup, that's it. This always happens to me . I'm always too lazy to back up my devices.....
Yes recovery mode works and I can get into ADB Sideload.
Nope, never used Odin before. never tried.
I may have something here!
http://forum.xda-developers.com/showthread.php?t=2785185
My firmware is G900AUCU2AND3.
I will update after following the guide.
It works! The only thread that I needed in the world and I couldn't find until after I wiped my device....
Device successfully restored to functionality.
tforkan99 said:
Device successfully restored to functionality.
Click to expand...
Click to collapse
Great to hear.
As I commented at the outset, all you needed to do was restore a full, stock firmware image to recover. Ideally one that matches your existing baseband. Which is essentially what that thread did. Collected all of the pieces to do a 100% reversion to stock.
I've written similar posts for Verizon and TMobile. Was in fact just rewriting the Verizon one for you when you updated the thread. Anyway, good work. Give yourself a pat on that back and promise to make more backups this time.
.
Ego?
fffft said:
I am allergic to posts that use Urgent in the title. Obviously you'd like to regain use of your phone ASAP. But how that makes your post more important than someone else's is a mystery. Nevertheless, I'm sure that someone else will be along soon to help you.
If you don't find something more expedient, the most reliable solution for a non-bricked phone is to Odin flash a full, stock firmware image that matches your baseband version.
.
Click to expand...
Click to collapse
I'm allergic to egocentric attitudes when it comes to answers in a Q & A thread.
tforkan99 said:
It works! The only thread that I needed in the world and I couldn't find until after I wiped my device....
Device successfully restored to functionality.
Click to expand...
Click to collapse
Happy to hear it that worked out for you!
Hi there
I've got a problem and I don't know what might be the easiest and fastest way to get access to data on my Galaxy S4 without having to use its screen as it does no longer work after it fell to the ground a couple of weeks ago. Since this incident, the screen is no longer displaying any picture and does no longer recognize touch screen inputs.
First, I feared that I have not enabled USB debugging mode on my phone but when I connected it to my PC, it was listed with status Unauthorized in ADB shell. As I am using another Galaxy S4 phone in the meantime which belongs to a colleague of mine, I was able to see that a Galaxy S4 phone is only listed with status Unauthorized in ADB shell when it has USB debugging mode enabled. Surprised and pleased I hoped being able to get access to my Galaxy S4 with cracked screen. Unfortunately, it seems that the screen on my Galaxy S4 has to be unlocked first and a confirmation dialog for USB debugging be confirmed in order I can access it with ADB shell.
Last week, I bought a 5in1 MHL adapter and I am able to view the screen on a TV screen. As the touch screen seems to be completely damaged, I have to enter the PIN first and press OK. If I am able to manage this, what would be the easiest way to get access to my phone, which procedure do you recommend? Is there possibly another and easier way to get access to data which is on my Galaxy S4 without having to use the screen?
It seems as I am very close to get access to my phone and I hope to accomplish this goal with your help. I thank you for all your replies, tips and hints in advance!
Cheers
Paul
seanpaul00 said:
Hi there
I've got a problem and I don't know what might be the easiest and fastest way to get access to data on my Galaxy S4 without having to use its screen as it does no longer work after it fell to the ground a couple of weeks ago. Since this incident, the screen is no longer displaying any picture and does no longer recognize touch screen inputs.
First, I feared that I have not enabled USB debugging mode on my phone but when I connected it to my PC, it was listed with status Unauthorized in ADB shell. As I am using another Galaxy S4 phone in the meantime which belongs to a colleague of mine, I was able to see that a Galaxy S4 phone is only listed with status Unauthorized in ADB shell when it has USB debugging mode enabled. Surprised and pleased I hoped being able to get access to my Galaxy S4 with cracked screen. Unfortunately, it seems that the screen on my Galaxy S4 has to be unlocked first and a confirmation dialog for USB debugging be confirmed in order I can access it with ADB shell.
Last week, I bought a 5in1 MHL adapter and I am able to view the screen on a TV screen. As the touch screen seems to be completely damaged, I have to enter the PIN first and press OK. If I am able to manage this, what would be the easiest way to get access to my phone, which procedure do you recommend? Is there possibly another and easier way to get access to data which is on my Galaxy S4 without having to use the screen?
It seems as I am very close to get access to my phone and I hope to accomplish this goal with your help. I thank you for all your replies, tips and hints in advance!
Cheers
Paul
Click to expand...
Click to collapse
Use this post as reference.
http://forum.xda-developers.com/showpost.php?p=62398797&postcount=213
You need to modify a kernel (or ask someone who can), change to the values in the post above. And flash it trough download mode.
Then you can use the app (also in that topic from the post above), to manage your s4. Good luck.
Hi Lennyz
Thank you for your quick response.
In the meantime I've tried several times to enable my phone with an USB mouse over OTG cable but whenever I switched back to the the TV where I could see my phone's screen over MHL, I recognized that I did not manage to press the OK button after I have pressed all 4 digits of the PIN.
After several more unsuccessful attempts I prepared a MacBook for building a kernel on my own. I've installed Xcode, MacPorts and Repo now but I've not managed yet to build the kernel. I probably have to find a developer who would build such a kernel for me to get one in a timely manner.
Can you probably tell me, which steps I would have to follow when I would have got a kernel with USB debugging enabled and set to insecure (for not having to allow the RSA key)?
In the meantime, I've read through more tutorials, guides etc. regarding building a kernel for android. Now, I understand that modifying a kernel means that I have to build a new boot.img. For this, I need the Samsung firmware which suits the firmware running on my Galaxy S4. I connected my phone to a Windows PC and the following information are shown in the device properties in My Computer:
Galaxy S4 Model: GT-I9505
Firmware version: I9505XXUGNG8
I downloaded the firmware version from opensource.samsung.com.
I have read on a website, that a boot.img file can be extracted with abootimg -x boot.img into several parts including a configuration file named bootimg.cfg, the stock kernel and ramdisk. OK, understood, but, I don't have a boot.img and I can't get the boot.img from my Galaxy S4 because this would require that I can connect to it through ADB which does not work in my case.
Since I can't run Linux on one of my PCs as they have not enough free harware ressources, I would greatly appreciate if somebody would build a kernel/boot.img with the three properties in the build.prop file in order I can access the phone through ADB without having to confirm an RSA key or the like.
seanpaul00 said:
In the meantime, I've read through more tutorials, guides etc. regarding building a kernel for android. Now, I understand that modifying a kernel means that I have to build a new boot.img. For this, I need the Samsung firmware which suits the firmware running on my Galaxy S4. I connected my phone to a Windows PC and the following information are shown in the device properties in My Computer:
Galaxy S4 Model: GT-I9505
Firmware version: I9505XXUGNG8
I downloaded the firmware version from opensource.samsung.com.
I have read on a website, that a boot.img file can be extracted with abootimg -x boot.img into several parts including a configuration file named bootimg.cfg, the stock kernel and ramdisk. OK, understood, but, I don't have a boot.img and I can't get the boot.img from my Galaxy S4 because this would require that I can connect to it through ADB which does not work in my case.
Since I can't run Linux on one of my PCs as they have not enough free harware ressources, I would greatly appreciate if somebody would build a kernel/boot.img with the three properties in the build.prop file in order I can access the phone through ADB without having to confirm an RSA key or the like.
Click to expand...
Click to collapse
You are making it harder then it have to be.
You can also download a custom TW Lollipop kernel here on XDA. Look for tutorial how to extract and repack it. Then modify the kernel and flash it using Heimdall.
Lennyz1988 said:
You are making it harder then it have to be.
You can also download a custom TW Lollipop kernel here on XDA. Look for tutorial how to extract and repack it. Then modify the kernel and flash it using Heimdall.
Click to expand...
Click to collapse
Hi Lennyz
Your post gives me the idea, that I may get any kernel here on XDA, probably with the only exception that it has to be for the GT-I9505 edition Galaxy S4. So, after I read your post, I didn't care about numbers like GNG8 or the like anymore and was just looking for a TouchWiz KitKat kernel. I have found two kernels which might fit my needs:
Hulk Kernel: http://forum.xda-developers.com/galaxy-s4/i9505-develop/kernel-hulk-kernel-v1-stweaks-based-t3050469
Kushans Kernel http://forum.xda-developers.com/galaxy-s4/i9505-develop/deknoxed-touchwiz-kitkat-rom-t3040574 (should be the URL)
I have now put the boot.img files I downloaded from the two threads above into tar.md5 files, so they should be ready to be flashed.
My uncertainties at this moment are about the kernel edition (working with KitKat android version?) and the location it will be flashed on my phone (location on the internal storage). Somebody please tell me if I am going to do the right thing:
Root my phone with cf auto root
Flash boot.tar.md5 through Odin (will do this on a Windows PC as I am currently not familiar with Heimdall)
Many thanks in advance.
Hi there
Some more hours later, I have found a kernel linked here on XDA, unpacked, modified the relevant values in default.prop, repacked and now flashed it to my Galaxy S4. Some weeks before, I have already rooted my Galaxy S4, I am not sure if the root process worked, I only saw that Odin told me "PASS" in the end and my phone booted again and my PC has recognized it. After flashing the kernel through Odin 3.07, my phone seems to be in a bootloop now. I tried reflashing, removing the battery for a minimum of 30 seconds, but my phone still vibrates every 3 seconds when I turn it on. I don't have an idea what I should do now. I tried to wipe the cache partition through Stock recovery, but my phone is still vibrating every 3 seconds. Do you have an idea what I could do next? My phone is still recognized by Odin.
I have downloaded the stock kernel, linked in this thread:
http://forum.xda-developers.com/galaxy-s4/i9505-develop/ref-kernel-stock-collection-i9505-t2868241
Download is on this site:
https://drive.google.com/folderview?id=0B9kl3vPBnwHaY1FxU0drQ0E3RVk&usp=sharing#list
It is the stock kernel Kernel_Stock_GNG8.tar.md5 I have downloaded, so it is the kernel which should fit to my stock KitKat GNG8 ROM.
I have unpacked the boot.img file with the splitbootimg python script. After modifying the settings in default.prop, I repacked the boot.img with repackbootimg and the output of the split python script and the base address from the output uf unpackbootimg.
This is the output in Odin 3.07:
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> boot.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> boot.img
<ID:0/007> NAND Write Start!!
<ID:0/007> RQT_CLOSE !!
<ID:0/007> RES OK !!
<ID:0/007> Removed!!
<ID:0/007> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
Isn't there somebody who has an idea what might help in my situation?
Shall I upload the boot.img file I have modfied somewhere in order someone can verify that I have done it correctly?
Many thanks in advance.
seanpaul00 said:
Isn't there somebody who has an idea what might help in my situation?
Shall I upload the boot.img file I have modfied somewhere in order someone can verify that I have done it correctly?
Many thanks in advance.
Click to expand...
Click to collapse
I think it would be better to use a custom 4.4.2 kernel with the modified paramaters. Those kernels should just boot.
Try this one:
http://forum.xda-developers.com/showthread.php?t=2590246
Maybe @alucard_24 is even willing to cook a 4.4.2. kernel with those paramaters already changed. But you have to ask him yourself.
Lennyz1988 said:
I think it would be better to use a custom 4.4.2 kernel with the modified paramaters. Those kernels should just boot.
Try this one:
http://forum.xda-developers.com/showthread.php?t=2590246
Maybe @alucard_24 is even willing to cook a 4.4.2. kernel with those paramaters already changed. But you have to ask him yourself.
Click to expand...
Click to collapse
Hi Lennyz
Thank you for your quick answer!
I may have luck, I unpacked the kernel and noticed, that the three parameters are set like they need to be meaning:
ro.secure=0
ro.debuggable=1
ro.adb.secure=0
I am just a bit confused about the warnings I have read a lot of times saying I should be careful and only use a kernel which fits to my ROM. As you say I might use the kernel of alucard_24, this lets me assume that it should work with probably different versions of Android KitKat. I will give it a try and report about the result.
I seem to be stuck in a pickle, and at this rate this phone is seeing a swift throw to the curb by my friend who had given me this phone after getting his new one.
So, he had given me the phone and I was glad to finally move on from my issue-ridden HTC One M8, which was essentially on it's last legs. Even this low quality phone was more usable than the piece of junk I have. I got to work, and I installed the RebornROM, and I had went ahead to delete some of the bloatware.
However, it seems that my dumb self removed a Samsung app, and it seems to have triggered the FRP lock. I didn't think it was a big deal, seeing as how reverting back to stock was apparently most people's fix. I saw the Realterm fix, however I have 0 access to the home at all, and no SIM card. I downloaded the firmware, and I started up Odin to flash the stock firmware on. I was met with an error that I can only find scarce info on, and on YouTube it seems to be from Indian tech channels who are telling me to buy z3x-tools, and I'm not here to go ahead and try to do that.
To be more specific, my particular error is: SW REV. CHECK FAIL. DEVICE: 2. BINARY: 1. I could not find info on this error from xda, and I'm confused really. What's going on here?
As per promise to my friend, if I fail to find anything on this issue by tomorrow, the phone meets it's doom by the curb. After all, I'd really like to not use this janky phone anymore, as I'm quite tired of being unable to do nothing (to be more specific, it's using an older version of Cyanogen because I can't afford to use Sunshine to upgrade my bootloader and S-OFF, and everything on the phone is slowly stopping to work, in particular my camera app crashes instantly, flashlight does not work, a good chunk of the left side of my touch screen has stopped responding and I've had to use one-handed mode to text, along with flipping the screen, and it is a gigantic mess of issues.)
Please help out, xda. I've got nothing else I can really do for this phone, and here I was figuring this would just be an easy night of fixing the damn thing.
After some fiddling, I have now gotten an error on startup that isn't even the FRP lock anymore; it's a notice telling me to use the Smart Switch app's emergency backup. Attempted to install it, and after jumping through multiple hoops and several fixes, I am stumped at "Error 1152: Temporary files failed to copy" upon attempting to open it's installer.
Pushing on, I have received a new error. I instead am just attempting to install the AP file, and I now receive another error: KERNEL REV. CHECK FAIL. DEVICE:1, BINARY:0. Even more fun, because there's even less information on this one. In fact, I have only found others crying for help as I am. Regardless, I am now trying the other 3 files. BL outright fails to download, CP has replaced the screen I saw originally, instead putting the kernel error up top instead of the old FRP lock error I'd get. CSC seems to have put the FRP lock error back though. Afterward, I had a feeling that maybe BL will work now? I simply got my usual old SW REV error I mentioned already.
From here, I learned of an issue here. I think I need a different AP file. My phone is the MetroPCS version. The only reason I say this is because I realized the AP file caused the Smart Switch error, then CP -> CSC brought me back to the failure. The KERNEL REV issue occurs when trying to use my AP, with these logs:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1203)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
This leads me to think perhaps I have a corrupted file. However, I have found 1 single link for the firmware. Perhaps someone can help me?
Can you get into recovery and see which firmware you are on? Does your phone boot into the os? I've been through a lot of these issues. I just recently didn't have a sim, so no real term, and had the Google lock, but there is a way out of it.
This leads me to think perhaps I have a corrupted file. However, I have found 1 single link for the firmware. Perhaps someone can help me?[/QUOTE]
Drunkpilot said:
Can you get into recovery and see which firmware you are on? Does your phone boot into the os? I've been through a lot of these issues. I just recently didn't have a sim, so no real term, and had the Google lock, but there is a way out of it.
This leads me to think perhaps I have a corrupted file. However, I have found 1 single link for the firmware. Perhaps someone can help me?
Click to expand...
Click to collapse
[/QUOTE]
Cannot get into the OS, recovery, anything. All I can do is enter download mode. The FRP lock prevents anything else.
Cannot get into the OS, recovery, anything. All I can do is enter download mode. The FRP lock prevents anything else.[/QUOTE]
I ran into the same issue on another on5 when I had unlocked it for a friend, rooted it, then stupidly took off oem unlock and and rebooted to give back to him. I had to Odin the exact firmware I was running in order for it to work and fix the phone. I was running a t mobile older version ( an APF1) while trying to flash an (APL1) which wouldn't allow me to flash the AP partition in Odin. Once I flashed the full APF1 firmware with a factory reset, it booted normally, but unrooted, of course. Finding the correct firmware should hopefully fix your problem if your circumstances were like mine.
Check out these links. There are also other links and other threads to check out as well. Also check out sammobile.com as they have the the stock firmware for this phone.
whodisname said:
Have you tried this?
https://9to5google.com/2015/11/03/how-to-to-bypass-factory-reset-protection-samsung-phone-hack/
Sent from my SM-G550T1 using XDA-Developers mobile app
---------- Post added at 09:11 PM ---------- Previous post was at 09:09 PM ----------
http://visihow.com/ADB_commands_to_bypass_Google_Account_Verification
Click to expand...
Click to collapse
You can also pm me for link to my drive account as I have both of the baseband versions of this firmware. Hope this helps
----edit-----
Here's another thread to check out as well. Make sure to use the latest version of odin as well. Oh and one more thing it you're gonna use any custom Rom on this device I suggest only using the one by @SuperStars as all the others are for the Indian variant and will cause sound yo not work at all on any other Varian even though they claim to work for the metro/tmobile variants. Superstars can be found here:
https://forum.xda-developers.com/sa...to/stock-rom-on5-flashable-metro-pcs-t3476919
hatchet13rydin69 said:
Check out these links. There are also other links and other threads to check out as well. Also check out sammobile.com as they have the the stock firmware for this phone.
You can also pm me for link to my drive account as I have both of the baseband versions of this firmware. Hope this helps
----edit-----
Here's another thread to check out as well. Make sure to use the latest version of odin as well. Oh and one more thing it you're gonna use any custom Rom on this device I suggest only using the one by @SuperStars as all the others are for the Indian variant and will cause sound yo not work at all on any other Varian even though they claim to work for the metro/tmobile variants. Superstars can be found here:
https://forum.xda-developers.com/sa...to/stock-rom-on5-flashable-metro-pcs-t3476919
Click to expand...
Click to collapse
Unfortunately, all of these are not the solutions to my issues. I require the AP, CP, CSC, etc. versions of the firmware that can be sent through Odin. I have no access to my recovery or OS due to the lock already being on.
All the links I sent you were to the odin flashable .tar files which is all the files needed to get your phone up and going again. Most of the links will show the download as a zip file which you would extract after downloading then use odin to flash the extracted files to your phone
hatchet13rydin69 said:
All the links I sent you were to the odin flashable .tar files which is all the files needed to get your phone up and going again. Most of the links will show the download as a zip file which you would extract after downloading then use odin to flash the extracted files to your phone
Click to expand...
Click to collapse
Are you sure? I downloaded from every link and it seemed to be a standard recovery .zip file from each one; that or the link was expired, deleted, etc.
Hi, my device is Moto g4 plus. I have removed frp and flashed stock rom and flashed hw network. Got my network back but if i open camera, it says"camera is busy" even if I install third-party camera application also not working. Even flashlight also not working and missing option from quick pull option. Even if i install flashlight application also it says no flashlight detected. Plz help me with some solution for this issue...
Aashakmeeran said:
Hi, my device is Moto g4 plus. I have removed frp and flashed stock rom and flashed hw network. Got my network back but if i open camera, it says"camera is busy" even if I install third-party camera application also not working. Even flashlight also not working and missing option from quick pull option. Even if i install flashlight application also it says no flashlight detected. Plz help me with some solution for this issue...
Click to expand...
Click to collapse
wrong forum
Sorry to bump this, but I need a response to this now. I have no files to flash and my old phone just bricked, so...
Can anyone help me out? I need an Odin flash in order to do anything, in which nobody has provided me any reliable file. The last guy in the thread earlier from a couple months ago gave me broken links instead of anything, and then didn't respond after I made him aware of this. Someone please.
Drunkpilot said:
Can you get into recovery and see which firmware you are on? Does your phone boot into the os? I've been through a lot of these issues. I just recently didn't have a sim, so no real term, and had the Google lock, but there is a way out of it.
This leads me to think perhaps I have a corrupted file. However, I have found 1 single link for the firmware. Perhaps someone can help me?
Click to expand...
Click to collapse
[/QUOTE]
How did you get past the FRP lock?
F0rZ3r0 said:
Sorry to bump this, but I need a response to this now. I have no files to flash and my old phone just bricked, so...
Can anyone help me out? I need an Odin flash in order to do anything, in which nobody has provided me any reliable file. The last guy in the thread earlier from a couple months ago gave me broken links instead of anything, and then didn't respond after I made him aware of this. Someone please.
Click to expand...
Click to collapse
Hi there. Did you ever get an Odin link that worked? Is that the best/only way to unlock a Galaxy on5 Metro PCS?
davizzyus said:
Hi there. Did you ever get an Odin link that worked? Is that the best/only way to unlock a Galaxy on5 Metro PCS?
Click to expand...
Click to collapse
I have no clue. I never got a Odin link that worked. I need it to make my phone work, which is why I'm asking, since nobody seems to have what I'm asking for.
https://drive.google.com/file/d/0B7K3zIeKabE8aHo5NlVMLXpNdUU/view
Use the PL1 firmware. The most spread around one is the PF1, these should work. If not, I'm not sure what to say. Browse a bit more until you can find a solution. This fixed my phone finally.
F0rZ3r0 said:
https://drive.google.com/file/d/0B7K3zIeKabE8aHo5NlVMLXpNdUU/view
Use the PL1 firmware. The most spread around one is the PF1, these should work. If not, I'm not sure what to say. Browse a bit more until you can find a solution. This fixed my phone finally.
Click to expand...
Click to collapse
What kind of phone? How did you load the firmware? Did it bypass the Google lock?
davizzyus said:
What kind of phone? How did you load the firmware? Did it bypass the Google lock?
Click to expand...
Click to collapse
1. Umm... MetroPCS On5. :b
2. ODIN.
3. I didn't have a Google lock, I had a FRP lock triggered by custom binaries.
F0rZ3r0 said:
1. Umm... MetroPCS On5. :b
2. ODIN.
3. I didn't have a Google lock, I had a FRP lock triggered by custom binaries.
Click to expand...
Click to collapse
okay so i had this very same problem a few months back then got a new phone(on moto g5 plus now). the only way i could find to defeat FRP was flashing the "home csc" in odin. i HAD it but idk what happened must have deleted it when i got rid of the phone but im looking for it again also because i am fixing a friends On5. when i find it ill upload it!
i have the T580 32GB of a friend here, that does not work at the moment (and maybe never again ) - the problem is that on startup it only gives this message in red letter :
could not do normal boot invalid kernel length
Click to expand...
Click to collapse
the only thing i can do is get into download mode - but i fail when i try to install a stock rom via odin - after NAND Write Start!! it times out and gives me a fail.
i already tried a 3 different odin versions and adroid 6.0, 7.0 and 8.01 Stock Rom for SM-T580 but no luck so far.
another problem is my friend does not know what the android version he was on before that hapend - and the tablet has Samsung FRP on.
maybe some of the experts here have an advice what i can try otherwise this tab a is really bricked - furthermore i wonder how this could happen as my friend swears he did not try to put twrp or anything else onto the tablet ....
Have you tried flashing TWRP using ODIN? (AP Slot)
i do not know if flashing twrp is a good idea as i do not know if oem unlock is enabled - and as it does not boot up i cannot switch it on in developer options
ilovebytes said:
i do not know if flashing twrp is a good idea as i do not know if oem unlock is enabled - and as it does not boot up i cannot switch it on in developer options
Click to expand...
Click to collapse
Wouldn't it simply fail if OEM unlocking was disabled? I don't know honestly. I'd try it if no other solutions come up.
ilovebytes said:
i have the T580 32GB of a friend here, that does not work at the moment (and maybe never again ) - the problem is that on startup it only gives this message in red letter :
the only thing i can do is get into download mode - but i fail when i try to install a stock rom via odin - after NAND Write Start!! it times out and gives me a fail.
i already tried a 3 different odin versions and adroid 6.0, 7.0 and 8.01 Stock Rom for SM-T580 but no luck so far.
another problem is my friend does not know what the android version he was on before that hapend - and the tablet has Samsung FRP on.
maybe some of the experts here have an advice what i can try otherwise this tab a is really bricked - furthermore i wonder how this could happen as my friend swears he did not try to put twrp or anything else onto the tablet ....
Click to expand...
Click to collapse
I think you are going about it wrong. Instead of booting to download mode, try booting to recovery mode via Home, Vol Up and Power and then selecting Factory Reset. This is always necessary before you can use download to flash a ROM via Odin and it might make using Odin unnecessary.
of course i tried to get into receovery mode but the problem is i can't - when i do home, vol up and power absolutely nothing happens, i only get into download mode
edit: i believe FRP is the Problem this prevents odin from writing the files to the tablet - as it allways times out with :
Complete(Write) operation failed.
Click to expand...
Click to collapse
what i do not really understand is why FRP does not let odin flash an original samsung firmware ?
[QUOTE what i do not really understand is why FRP does not let odin flash an original samsung firmware ?[/QUOTE]
This sounds more like a binary issue. I have reason to believe you are what's called an FRP Binary Lock. Recovery is usually inaccessable or re-routed and you cannot "seem" to use Odin3 but in fact you can. This issue you apparently are having sounds oddly like some issues I've had on these devices and is often a result of bad Rooting or invalid firmware being installed. This overloads the binaries and puts the device in a locked mode with symptoms of an inaccessible Recovery a difficult to use Odin3 or a bootloop. Most of the time I hear of a notification somewhere of an FRP lock. If this is the situation you are in here is a link to a page of mine that will give you the files to helpfully solve your issue. Let me know if that works or not.
https://forum.xda-developers.com/general/help/custom-binary-blocked-frp-lock-2019-t3979661
Casper Young said:
If this is the situation you are in here is a link to a page of mine that will give you the files to helpfully solve your issue. Let me know if that works or not.
https://forum.xda-developers.com/general/help/custom-binary-blocked-frp-lock-2019-t3979661
Click to expand...
Click to collapse
it sounds like i am in the same situation and i tried your files but it does not let me download them through odin - i also wrote you a pm maybe you find the time to answer me.
i really wonder how this could happen as my friend swears he did never try to flash anything onto the tab, and i really believe him as he absolutely knows nothing about flashing or where to get a firmware and not even how to get into dl mode ....
ilovebytes said:
it sounds like i am in the same situation and i tried your files but it does not let me download them through odin - i also wrote you a pm maybe you find the time to answer me.
i really wonder how this could happen as my friend swears he did never try to flash anything onto the tab, and i really believe him as he absolutely knows nothing about flashing or where to get a firmware and not even how to get into dl mode ....
Click to expand...
Click to collapse
The situation I was suspecting is a "Custom Binaries are Blocked by FRP Lock" to which you would have seen a notification of it in one of 4 ways. Your situation is somewhat similar because you cannot access Recovey and although Download Mode is accessable it appears useless. Your device is not Bricked. A bricked device is unusable in any way and these days most devices can be restored.
You do seem to be having some difficulties that are usually common with binary issues. You can in fact use Odin3 but how is the question. Usually one can flash in the Stock firmware and that returns the device to normal. When it becomes impossible to flash in stock firmware or anything else it seems, to my experiance has always been a Binary issue. I will provide a link to the 4File Official firmware. And instructions for you to properly use it for your needs.
SM-T580 Official Stock Firmware 4Files
https://drive.google.com/open?id=1zvhwUfSRW44V1ZwEsHLRvlh-T0M79ks9
I'll assume you know something about using Odin3. Unzip the file to your desktop. There are 4 files but you'll only use 3 of them. You can use the patched version of Odin3.13B or you can use Odin3.14. Place the files in their respective places. BL, and AP are easy enough to see where they go. Now there is a file labeled CSC and one labeled HOME CSC. You will only use one of them. The CSC file returns your app data to factory settings (it erases everything). The Home CSC file keeps the app data. So it's your choice which one you choose. These are Official Firmware Files so you should be able to flash them in. Should that not work for you my most likely answer would be that your binaries are the issue and that is why you can't as of yet use Odin sucessfully. Does Odin even try to initiate a flash then stalls or does it do nothing altogether?
There are two different Binary files for the SM-T580 that I have. I would suggest using the Binary 4 FRP first. f I recall correctly the Odin3.13B patched version was made for this. Place the file in the AP section and try flashing it. You should get a few gears on the screen turning if it applied, or maybe not. If that fails use the U4 Binary Unlock file. It is only after you flash in the binary files that you can then install the Stock Firmware. It is the overloaded binaries that prevent the use of Odin as you may be experiancing. I am also including the Knox cleaner in case you need to reset it.
SM-T580 Binary files:
Binary 4 FRP Unlock
https://drive.google.com/open?id=1iXrZR2E7m6Ai5InAw8u3lzeLhb3ThRo5
U4 Binaries. This is two files. Flash one at a time using the AP section. They are labeled 1rst or 2nd
1. https://drive.google.com/open?id=1rX_luP_0W4ygdloIr2Gr9TCSfqFyaTK-
2. https://drive.google.com/open?id=1xsw4GVYtNMJhiMXV2cR2jaJvToG_n6Pi
Knox Cleaner: Also flashed in using the AP section of Odin3
https://drive.google.com/open?id=1EolYe9auY9jslYSpSgHoon_YB00D2noV
Good Luck and let me know if this helps or not.
lewmur said:
I think you are going about it wrong. Instead of booting to download mode, try booting to recovery mode via Home, Vol Up and Power and then selecting Factory Reset. This is always necessary before you can use download to flash a ROM via Odin and it might make using Odin unnecessary.
Click to expand...
Click to collapse
Only if they could get into Recovery they may be able to reset it.
I have never once needed to go to Recovery to do "anything" before using Odin3 to flash.
The only time I've had to go there (repetedly) and reset was when trying to get past FRP Google Account Protection. Sometimes it takes out the page I want to get to and I need to reset it to get to it again. This is "not" always neccesary before flashing a ROM which rewrites the device programing.
sorry for double post
@Casper Young
thanks for your help so far, i am gonna try your suggestions on weekend when i have a bit more spare time - hope i can get the tab running again
Hi all, I know somewhat about flashing but when it comes to PIT file I have absolutely no idea. Just read about what it is. Now the question, from where I would get my phone's PIT file. I cannot extract it from phone as only download screen is accessible on it. Details are phone are below,
S7 Edge - 32 GB
SM-G935F
Country : Pakistan
Current Binary: Samsung Official
System Status: Custom
FRP Lock: OFF
Warrant Void: 0 (0x0000)
RP SWREV: B:8 K:5 S:7
I remember that B:8 was actually 7 but I think I flashed (unsuccessful) next binary so it got updated.
I need the PIT file. Does it also holds internal storage capacity information ?
Can anyone help ?
Hy, Hope you have found the solution.
If you havent then here is a clue about PIT file. It is located in Firmware>csc*tar.md5>*.pit
Chaudhry69 said:
Hy, Hope you have found the solution.
If you havent then here is a clue about PIT file. It is located in Firmware>csc*tar.md5>*.pit
Click to expand...
Click to collapse
Nope, gave up flashing on that phone. It is still in my drawer, just sitting there
As a matter of fact pit (partition information table if memory serves me right) does hold the information for storage. But, I wonder how you ended up screwing it, it's like the most unbrickable thing. What is the error odin showing when you flash the firmware.
I would recommend xsg latest build from samfirm as it contains csc for Pakistan.
Chaudhry69 said:
As a matter of fact pit (partition information table if memory serves me right) does hold the information for storage. But, I wonder how you ended up screwing it, it's like the most unbrickable thing. What is the error odin showing when you flash the firmware.
I would recommend xsg latest build from samfirm as it contains csc for Pakistan.
Click to expand...
Click to collapse
Well I did nothing to start with. I tried to factory reset to phone from settings and ended up on boot loop. Have been trying flashing since then but of no use. Someone said its memory might be bad, dont know what other reason could be there. Strange if memory went bad of this phone, its too early for that. I have my HTC sensation which I started some time back and that was working fine .
It just starts flashing, progress bar starts and then file copy fails after a little while.
Chaudhry69 said:
As a matter of fact pit (partition information table if memory serves me right) does hold the information for storage. But, I wonder how you ended up screwing it, it's like the most unbrickable thing. What is the error odin showing when you flash the firmware.
I would recommend xsg latest build from samfirm as it contains csc for Pakistan.
Click to expand...
Click to collapse
message <ID:0/003> Complete(Write) operation failed. is the message i get while flashing. I have another thread https://forum.xda-developers.com/t/...ery-stock-rom-unrooted.4157363/#post-84324697 in which someone helped me but in the end i was still not able to flash. It starts copying, progress bar starts and then fails after a while. Can you please share the link you mnetioned on sam firmware xsg ? Maybe I can try one more time.
lazers378 said:
message <ID:0/003> Complete(Write) operation failed. is the message i get while flashing. I have another thread https://forum.xda-developers.com/t/...ery-stock-rom-unrooted.4157363/#post-84324697 in which someone helped me but in the end i was still not able to flash. It starts copying, progress bar starts and then fails after a while. Can you please share the link you mnetioned on sam firmware xsg ? Maybe I can try one more time.
Click to expand...
Click to collapse
Well, as the nice folks over there said, region doesn't matter. It is true somewhat if you are not after some very specefic feature like vowifi, volte etc. For your peace of mind, here is a link to XSG Firmware, pick the latest. How to flash;
Download the firmware greater than or equal to your current bl, k and S ver.
Extract the zip.
Extract pit from csc.
Deselect auto reboot. Select all other options.
Attach pit and flash all except home_csc.
Why it happened?
Either the flash is damaged, Can be Million reasons other than age.
OR Some how bootloader or modem is messed up.
Latter will be fixed by an odin flash. If nothing works give twrp a try. Knox will trip but better than having a dead phone. If twrp works, install stock debloated rom and enjoy the company of a legendary deveice while it lasts.