Database Users

[Q] Issues Using Odin3+1.61

Hiya, I recently tried to follow k0nane's howto on getting Froyo DK17 flashed onto my phone, but as expected, things did not go well. I managed to root my phone using the one click method, installed ClockworkMod, backed up my ROM, contacts, SMS messages, et cetera. Unfortunately, that's about the only thing that went right in my case.
Before I start, I will admit that this is the first time I'm attempting this, though I did receive much help from a friend who has already successfully flashed her phone, so if in doubt, please assume I don't know what I'm talking about!
I installed Android SDK, did the whole adb thing, and made sure my Samsung drivers were up to date (64 bit system). I then proceeded to download the file in that thread that included Odin, the new PIT, and the new modem. I then downloaded the next file that included the ROM and kernel and put the ROM in my SDcard.
Then I went about starting Odin up and loaded the files into their respective slots. The new PIT in the PIT slot, and, get this, the new modem in the PDA slot. I learned much later that the new modem should have been in the Phone slot, but let us continue. I then put my phone in download mode and connected it to the computer via USB, and Odin quickly recognized the device with a COM# in a yellow box, so I reckoned things were going pretty dandy, but alas, the following message dashed my hopes a mere three seconds after I hit START.
<ID:0/006> Added!!
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> param.lfs
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
So I hopped onto the respective IRC chat for the Samsung Epic 4G, and the kind folks there pointed out that the modem should have gone into the Phone slot, so I tried again the proper way and I still got the same failure.
My phone is now rendered inoperable because a recovery boot via presents me with a cute drawing of a phone that is connected to a computer, but a warning triangle separates the two. Same thing when I try to normally boot. Fortunately I can still access download mode, so I don't believe my phone is bricked. Interestingly enough, despite these blocks, I somehow did manage to get into the Clockworkmod recovery screen by doing some weird series of steps where I have the USB plugged in, the battery pulled, the USB pulled, then the battery and USB reconnected and at some moment there I would slide out the keyboard, then, without even touching a button, it would get into the recovery screen.
Using this weird workaround, I wiped everything and restored my backed up ROM and all that snaz, but upon rebooting the system I was again greeted warmly by the cute image of the dysfunctional marriage between my phone and computer.
So upon further advice from the folks at the IRC chat, I tried to flash my phone back to stock specifications using the DI18 and corresponding PIT file in the same method. But alas, I get the exact same result and well, at this time I'm getting a wee bit concerned. But by now, the folly of trying to flash my phone in the early hours of the morning and during Thanksgiving, no less, begins to rear its ugly head and I end up sleeping.
Cue sunrise and I'm up trying to make best of my situation, and I post a few times on k0nane's thread describing my problems, and a guy there says I should try the same process on another computer, so I do, and that fail with the same result. Then I hop onto IRC again, and the nice guys there say I should try Heimdall, so I do (after reading its readme), and lo and behold Heimdall does not seem to be able to recognize my device.
I guess my question is where one might find a problem in my procedures. I swear I did everything right and to the letter, but perhaps a new pair of eyes could be prove to be more insightful and help point out my mistakes. Granted the feeling of ruining a 500 dollar phone isn't exactly something I'd brag about to my friends, but I am rather enjoying life without a phone.
For now, anyways, haha.
------------------------------
tl;dr Odin recognizes my phone, but fails within 3 seconds with the following message
<ID:0/006> Added!!
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> param.lfs
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
help?

It sounds like you have done a lot of research and educated yourself prior to attempting your first flash. Major props to you for that as most people don't.
My $0.02 about your issues...I had something similar happen once when I forgot to uncheck "F. Reset Time" before starting the flash. If that's not the problem then I'd try a different cable. Next step would be to try a different version of Odin, there are plenty floating around these forums.
Good luck!

hongseong said:
Hiya, I recently tried to follow k0nane's howto on getting Froyo DK17 flashed onto my phone, but as expected, things did not go well. I managed to root my phone using the one click method, installed ClockworkMod, backed up my ROM, contacts, SMS messages, et cetera. Unfortunately, that's about the only thing that went right in my case.
Before I start, I will admit that this is the first time I'm attempting this, though I did receive much help from a friend who has already successfully flashed her phone, so if in doubt, please assume I don't know what I'm talking about!
I installed Android SDK, did the whole adb thing, and made sure my Samsung drivers were up to date (64 bit system). I then proceeded to download the file in that thread that included Odin, the new PIT, and the new modem. I then downloaded the next file that included the ROM and kernel and put the ROM in my SDcard.
Then I went about starting Odin up and loaded the files into their respective slots. The new PIT in the PIT slot, and, get this, the new modem in the PDA slot. I learned much later that the new modem should have been in the Phone slot, but let us continue. I then put my phone in download mode and connected it to the computer via USB, and Odin quickly recognized the device with a COM# in a yellow box, so I reckoned things were going pretty dandy, but alas, the following message dashed my hopes a mere three seconds after I hit START.
<ID:0/006> Added!!
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> param.lfs
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
So I hopped onto the respective IRC chat for the Samsung Epic 4G, and the kind folks there pointed out that the modem should have gone into the Phone slot, so I tried again the proper way and I still got the same failure.
My phone is now rendered inoperable because a recovery boot via presents me with a cute drawing of a phone that is connected to a computer, but a warning triangle separates the two. Same thing when I try to normally boot. Fortunately I can still access download mode, so I don't believe my phone is bricked. Interestingly enough, despite these blocks, I somehow did manage to get into the Clockworkmod recovery screen by doing some weird series of steps where I have the USB plugged in, the battery pulled, the USB pulled, then the battery and USB reconnected and at some moment there I would slide out the keyboard, then, without even touching a button, it would get into the recovery screen.
Using this weird workaround, I wiped everything and restored my backed up ROM and all that snaz, but upon rebooting the system I was again greeted warmly by the cute image of the dysfunctional marriage between my phone and computer.
So upon further advice from the folks at the IRC chat, I tried to flash my phone back to stock specifications using the DI18 and corresponding PIT file in the same method. But alas, I get the exact same result and well, at this time I'm getting a wee bit concerned. But by now, the folly of trying to flash my phone in the early hours of the morning and during Thanksgiving, no less, begins to rear its ugly head and I end up sleeping.
Cue sunrise and I'm up trying to make best of my situation, and I post a few times on k0nane's thread describing my problems, and a guy there says I should try the same process on another computer, so I do, and that fail with the same result. Then I hop onto IRC again, and the nice guys there say I should try Heimdall, so I do (after reading its readme), and lo and behold Heimdall does not seem to be able to recognize my device.
I guess my question is where one might find a problem in my procedures. I swear I did everything right and to the letter, but perhaps a new pair of eyes could be prove to be more insightful and help point out my mistakes. Granted the feeling of ruining a 500 dollar phone isn't exactly something I'd brag about to my friends, but I am rather enjoying life without a phone.
For now, anyways, haha.
------------------------------
tl;dr Odin recognizes my phone, but fails within 3 seconds with the following message
<ID:0/006> Added!!
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> param.lfs
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
help?
Click to expand...
Click to collapse
put it in the phone slot not the pda slot to bypass the pda bug

Oooh, thanks for the replies! I don't think I can get a micro USB cable right at this moment, but...
I did try the Phone method, and at first it seemed to actually start flashing, but it got stuck at factoryfs.rfs for quite a while, so I restarted the process and now it will just fail like it did before in about three seconds. Not sure what's gong on here, but it was nice to see it exhibiting some semblance of working up until it began hanging at factoryfs.rfs!
More helpful tips would be greatly appreciated!

Are you exiting Odin, disconnecting the phone, rebooting the phone into DL mode BEFORE trying to flash again? Odin will fail forever if you simply try to restart the process without the steps above.

I sure am!
I also think it has to do something with the param.lfs file since Odin always seems to fail once it encounters it (and it does so early on!).
Thanks again ^^

Ok have you tried to redownload the tar file it could be corrupted.You should be putting the whole tar file unopened in PDA leaving all the other slots empty and using the correct pit file that comes with odin.It is ok to leave the reset time option set it will not hurt anything.

Hiya, yes I have redownloaded the file and tried to no avail. I tried with both the PIT provided in the [How To] Return to Stock / Fix Bricked Epic and the one provided in the DK17 flash (some victory PIT). I tried all combinations with the .tar.md5 in both PDA and Phone positions, and I'm getting the same termination at the param.lfs file.
Eeek @[email protected]

hongseong said:
Hiya, yes I have redownloaded the file and tried to no avail. I tried with both the PIT provided in the [How To] Return to Stock / Fix Bricked Epic and the one provided in the DK17 flash (some victory PIT). I tried all combinations with the .tar.md5 in both PDA and Phone positions, and I'm getting the same termination at the param.lfs file.
Eeek @[email protected]
Click to expand...
Click to collapse
Forget about DK17 for a minute and try flashing DI18 with the new odin and pit, if that doesn't work download art3mis's DK05 extended that has the old odin and use that. Pit in pit, and the tar in pda.
Sent from my SPH-D700 using XDA App

hongseong said:
Hiya, yes I have redownloaded the file and tried to no avail. I tried with both the PIT provided in the [How To] Return to Stock / Fix Bricked Epic and the one provided in the DK17 flash (some victory PIT). I tried all combinations with the .tar.md5 in both PDA and Phone positions, and I'm getting the same termination at the param.lfs file.
Eeek @[email protected]
Click to expand...
Click to collapse
Was Re-Partition checked during any of your attempts?

For the longest time no, but then I talked to noobnl and he asked me to try to put it into both re-partition mode and phone bootloader update mode. It just hung at "DO NOT TURN OF TARGET" and that was it. He warned me that it could brick it, but I guess I got lucky and it didn't.
So yes, I did check re-partition mode, but not until I tried all aforementioned tips in every combination possible.

bubby323 said:
Forget about DK17 for a minute and try flashing DI18 with the new odin and pit, if that doesn't work download art3mis's DK05 extended that has the old odin and use that. Pit in pit, and the tar in pda.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Oh, I was trying to flash DI18 the entire time (I gave up trying to flash DK17 last night, haha ^^ But I'll try your DK05 extended tip right now! Sorry I missed this ><

Okay, so using artemis' DK05 extended package and older Odin, I get a different readout
<ID:0/006> Added!!
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> boot.bin
But it just stalls at boot.bin forever, and I've tried this several times, so...
I think the moral of the story here is that I'm unlucky
But yeah, that's what's happened so far. Thanks for the continued help, everyone!

Read thru this thread and just thought I'd ask --- Did you pull your MicroSD card from the phone and then make an attempt to flash? While I wouldnt think it would matter, I saw on another forum that its always a good idea to pull the MicroSD before Odin --- and I've always done that. Not sure it matters, but it couldnt hurt to try. Also, you being able to get into that Download mode means all isnt lost~ Don't give up~
Do you have another PC available to attempt the flashing on? I use a Windows 7 x64 system, but I always do my flashing on a XP x86 system. Its surprising how finicky Odin can be, so it couldnt hurt to try another PC....
Or not, just a couple suggestions.
Best of luck

marsknight said:
Read thru this thread and just thought I'd ask --- Did you pull your MicroSD card from the phone and then make an attempt to flash? While I wouldnt think it would matter, I saw on another forum that its always a good idea to pull the MicroSD before Odin --- and I've always done that. Not sure it matters, but it couldnt hurt to try. Also, you being able to get into that Download mode means all isnt lost~ Don't give up~
Do you have another PC available to attempt the flashing on? I use a Windows 7 x64 system, but I always do my flashing on a XP x86 system. Its surprising how finicky Odin can be, so it couldnt hurt to try another PC....
Or not, just a couple suggestions.
Best of luck
Click to expand...
Click to collapse
I tried to do it on another laptop in the house, but I ran into the same errors, but I'll try the microSD card trick soon
Thanks for the words of encouragement! I'm continuing to work on this problem, though I am a bit anxious to see how I can live without a cell phone...

im stuck with the same problem... and the messed up thing is i used odin before on this phone with win7 64bit... now i wish i never try updating to the new modem...

spent sooo much time on this and nothing im just gonna put it away b4 i smash it with a hammer... back to win mo...

Eeek, well, I think I'm going to scale back my attempts at fixing this for the moment. I'd be flat out lying if I said this wasn't a little bit frustrating, so I'm going to just relax before I make this fiasco ruin my Thanksgiving break for me. I'm most likely going to just purchase a cheap used flip phone and see through the rest of my contract with Sprint after changing my plan accordingly (no need for a data plan with a cheapo flip phone, and CERTAINLY no need for the 10USD WiMax surcharge, ^^; ).
That isn't to say that I'm not very thankful for all y'alls help, because I am, and this forum is awesome (along with the IRC chat!). Plus, not everything is *that* bleak; I mean, now I have a device that can charge batteries AND a 16GB microSD card freed up for other uses. So, thank you for all the help, and I hope y'all have a nice day!

Odin always seems to work for me windows 7 64bit and I have the 32bit drivers for the phone maybe try to deletethe old ones and install the 32bit drivers
Sent from my SPH-D700 using XDA App

Couple of questions and suggestions. Have you tried flashing just the modem in the proper slot(phone) with the proper pit file. I WOULD SUGGEST YOU TRY IT WITH THE OLDER ODIN(not 1.6) and the older pit. Then I would suggest you try to flash the full tar for DI18 with the older odin and no pit file. I have flashed my phone dozens of times with no pit as long as its the full tar. I could be wrong but I believe the pit is for partial system flashing. The only option I have checked on the left hand side of odin is reboot fwiw. Lastly, others have hinted at it too, odin is very finicky, try and try again. Always close down odin and restart it between attempts, and rebooting the computer seems to help others, and pull the phone battery and re-enter download mode each time too. Good luck, don't give up, if you can get into download mode all is not lost.
sent from an Epic4g through the cosmos

[Q] Bricked it?

After I finally got back into recovery from a flash that did not work like it was supposed to I restored the backup I had made and now all I get is the first screen
Vibrant
Samsung
I fouled up bad I am sure... have the phone less that 48 hours and I think i bricked it... What can I do now to get this thing back to factory so I can start over and hopefully not mess up this time?

I assume you went from froyo, to an eclair backup.
You will need to ODIN back. This can be found in the Dev Section Bible.
Once you ODIN back to stock JFD.... once you are on JFD, you can follow the steps in my noob guide to get on a custom rom correctly.
Hope it helps.

Good news is: You did NOT brick your phone, you got it stuck in a boot loop, something did not match from what was on it and whatever you flashed.
Here is a good way to get back to stock and start over, let me know if you make it OK.
Link: http://androidspin.com/2010/08/09/how-to-restore-or-recover-your-samsung-vibrant/
Good luck, just follow carefully and will be smooth and easy.

OK, So I finally got the phone to go to Download mode and I have odin, but before I make it worse. which files do I need and/or which specific thread will walk me through Odin. I found this site while waiting for a response *hope posting outside link is not against rules* http://factoidz.com/how-to-use-odin-to-flash-your-samsung-galaxy-s/

Ok i Brickeedd Mines Too yesterday...because i lik to do thinqs and learn more and moree...i juxx learnedd how to fix it.....if yuh brickdd it.....gett dhe odin shyt on your computer aloq with all the files that it needs....afta yuh got the files...........make sure yuh fone is of......
1...hold volume up and volume down>>both a the same time
2....conect the USB Cablee.....yuhhh now in download mode.....so go to odin and yuh should know what to do....
remember jusst preess volume up and volume down....dont preess power...

the pit and tar files in the link from androidspin are what you want. Not sure what version of ODIN they are using, but you want to make sure it's the latest ODIN version. I placed a link to it in the noob guide just in case. You can try with the version you have, just know if it hangs up, get the newest version.

caliga4221 said:
OK, So I finally got the phone to go to Download mode and I have odin, but before I make it worse. which files do I need and/or which specific thread will walk me through Odin. I found this site while waiting for a response *hope posting outside link is not against rules* http://factoidz.com/how-to-use-odin-to-flash-your-samsung-galaxy-s/
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=849028 should be everything there you need to odin back.

Great, I am downloading the tar file they linked now and the version of odin i got was i think from your thread it says 1.7 when its open.
Right now I have it open and it sees the phone. I have the pit file selected just waiting on tar to finish .. abut 30% done on this crappy free wifi my town provides.

caliga4221 said:
Great, I am downloading the tar file they linked now and the version of odin i got was i think from your thread it says 1.7 when its open.
Right now I have it open and it sees the phone. I have the pit file selected just waiting on tar to finish .. abut 30% done on this crappy free wifi my town provides.
Click to expand...
Click to collapse
make sure you uncheck the checkbox "RE-PARTITION" before you start...............................................................................................

Actually, I would not touch those buttons.

OK, all files finished and I followed the steps on AndroidSPIN but now I have conflicting instructions.
Guide says only use * Auto Reboot and * F. Reset Time
s15274n said use Re-Partition too... So this is what I have so far but Im not clicking anything till I verify It looks right to be sure I dont foul it up more.
Edit: wow pic came out so small its hard to see , here is link to raw img
http://oi53.tinypic.com/1zbb18o.jpg

according to your picture everything is good just hit start and you should be good.

caliga4221 said:
OK, all files finished and I followed the steps on AndroidSPIN but now I have conflicting instructions.
Guide says only use * Auto Reboot and * F. Reset Time
s15274n said use Re-Partition too... So this is what I have so far but Im not clicking anything till I verify It looks right to be sure I dont foul it up more.
Edit: wow pic came out so small its hard to see , here is link to raw img
http://oi53.tinypic.com/1zbb18o.jpg
Click to expand...
Click to collapse
I have used the Odin that came from Androspin and that is why I screamed to uncheck the third checkbox "re-partition" because for some reason the first time you start it, it is checked. STRICTLY: use only the two check boxes the guide mentions, if not you'll have issues as others have experience.

So it has been sitting for almost 15 min saying the same thing
<ID:0/005> Added!!
<ID:0/005> Odin v.3 enging (ID:5)..
<ID:0/005> File Analysis..
<ID:0/005> SetupConnection..
Thats it, thats as far as it goes. I dont know what to do, Task Manager shows the Process and Application active but with 0% activity and around 6600k memory use steady.

caliga4221 said:
So it has been sitting for almost 15 min saying the same thing
<ID:0/005> Added!!
<ID:0/005> Odin v.3 enging (ID:5)..
<ID:0/005> File Analysis..
<ID:0/005> SetupConnection..
Thats it, thats as far as it goes. I dont know what to do, Task Manager shows the Process and Application active but with 0% activity and around 6600k memory use steady.
Click to expand...
Click to collapse
did you uncheck re-partition before start?

yes.
I found another site where it said that you just had to put the phone back into download mode that sometimes when that happens its because something didnt connect right. I did that , closed odin with task manager, took out the battery and restarted the process. this time it worked. it looks like im back on stock again, at least it all looks right and seems to work. I was able to redownload all my apps, just have to start over from scratch.
My question now is where do I find the stock 2.2 update. Maybe it would be better to get to 2.2 stock before I start messing around with 2.2 roms and stuff again.

No, don’t go to stock Froyo. It's full of bugs and is a nightmare. Let me get back to my computer and i'll show you where to go.
Sent from my SGH-T959 using XDA App

roumenjr said:
No, don’t go to stock Froyo. It's full of bugs and is a nightmare. Let me get back to my computer and i'll show you where to go.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
OK, ty. If I have learned anything it is to be patient and wait on the experts when they say wait. Look forward to the info.

Go here first and root your phone, super easy:
http://forum.xda-developers.com/showthread.php?t=803682

roumenjr said:
Go here first and root your phone, super easy:
http://forum.xda-developers.com/showthread.php?t=803682
Click to expand...
Click to collapse
Done. Opened TI Backup and confirmed it asked for root rights and got them.

[Guide] The Beginner's Guide to the T-Mobile Galaxy Tab 10.1 4G (SGH-T859)

(Updated: March 12, 2012)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
As many desperate users have noticed, there is practically no information available for the users of the Magenta flavored GT 10.1 on XDA.
The purpose of this post is twofold:
First, to help you get the most out of your tablet.
Second, to teach you essential information that will keep you from taking fatal leaps of faith, explaining some of the Android jargon that confuses many newcomers.
Disclaimer: Proceed with caution. This guide will be updated to ensure accuracy, but does not claim perfection.
Table of Contents:
0. FAQ
I. How to root the T-Mobile Galaxy Tab 10.1
II. How to use a mobile phone's SIM card and corresponding Data Plan with the Tablet (in lieu of the mobile broadband plan/SIM that T-Mobile requires)
III. Removing T-Mobile Bloatware
IV. Basic Navigation
V. Installing ROMs
VI. HELP! I SCREWED UP! or How to Restore your Tablet to Stock (Original) Settings
C. Frequently Reported "Problems"
Guides:
0. FAQ
I will use this Section to quickly answer some of the questions I have found on this forum.
Will my T-Mobile Tablet fit in the regular Galaxy Tab 10.1 case?
Yes. The two devices have the same dimensions.
Can I make voice calls?
Voice calling is not fully functional yet. If you search some of seo's posts, you may be able to get partial calling capabilities. It is likely that within the coming weeks, we will have working GSM Voice calls.
ICS?
Yes. Section V.
To be continued.
I. How to root the T-Mobile Galaxy Tab 10.1
=What Exactly IS Rooting?=
Rooting means obtaining access to the root directory of the device (/). (Think of it as the "Desktop" directory, the most basic location).
At ship, an Android device will not let you access any folders above /sdcard/, which you see when your device is mounted to your computer through the USB drive.
This is a problem. Why? Because if you want to install ROMs or system apps (which I will cover in later sections), you must have access to /.
=To Root Your T-Mobile Galaxy Tab 10.1=
Rooting involves installing Superuser, which is an application akin to Firewall. It can allow or deny Root access by other applications.
Rooting also requires you to make a few binary code changes.
To automate this process,
1. Follow djR3Z's tutorial here: (http://forum.xda-developers.com/showthread.php?t=1239185)
I suggest following it to the end so you do not have to return to it for installing a Custom Recovery (covered later in Section IV).
You do not have to understand what it is yet; I will explain everything later, I promise.
This method works perfectly on the T-Mobile tablet, because the way the file systems are organized is identical between a Galaxy Tab 10.1 and the T-Mobile one (but not the 10.1v).
Check here for feedback from T-Mobile tablet users. (http://forum.xda-developers.com/showthread.php?t=1335846)
II. How to use a mobile phone's SIM card and corresponding Data Plan with the Tablet (in lieu of the mobile broadband plan/SIM that T-Mobile requires).
When you receive your tablet, T-Mobile will put a soft-lock that disables data usage from a regular phone's SIM card. They would rather have you commit to two different data plans (one for the phone, another for the tablet) so you do not have an all-purpose device. That is why you cannot make GSM voice calls from the T-Mobile Galaxy Tab 10.1 (yet), although your device is physically capable, and is also the reason you cannot use some of the Samsung features built in to other tablets.
T-Mobile is able to restrict your access by comparing your IMEI (International Mobile Equipment Identity) number to their database, which will have that device registered as a Tablet (which requires a mobile broadband plan).
You can get around this problem by deleting your IMEI, which automatically assigns you a new IMEI that makes your tablet identify itself as a generic device rather than a Samsung Galaxy Tab 10.1. You do not lose any functionality; you are just able to "disguise" your tablet as a phone.
=How To Solve This Problem=
**NOTE: Please use discretion. I am not aware of the legalities surrounding this solution. What I do know is that you are not stealing any data by using your SIM card on a different device, whether it be your phone or tablet. It is no different from putting your SIM card in a friend's phone and using the internet. As long as you stay below your allotted amount, I cannot see any problems following this method.
Terms you should understand prior to proceeding:
Root: gaining access to the root directory of your device, where system files are stored.
R/W: Read and write. This means that you can make changes to the files.
R/O: Read only. This means you can only view the files.
/: this is the root directory.
/sdcard: This is the folder where all your visible files (through USB connection) are stored.
/efs: This is where your IMEI is stored.
IMEI: International Mobile Equipment Identity, self-explanatory.
1. Ensure device is rooted. (Section I)
2. Download the Root Explorer Application (https://market.android.com/details?id=com.speedsoftware.rootexplorer&hl=en)
3. Open Root Explorer, Grant Superuser Permissions.
I suggest you get used to moving about Root Explorer before proceeding.
4. Navigate to the Root directory (/)
5. Press the Mount R/W button at the top left. This allows you to make modifications.
6. Copy your efs folder and navigate to /sdcard; paste your efs folder into this directory to make a backup of your IMEI information.
7. Return to Root directory (/) and open efs folder (/efs)
8. Click on the Three Bars at the top right corner, press "Multi-Select."
9. Select all the files (excluding ".." which just returns to the previous folder).
10. Press Delete.
11. Press ".." to return to root (/)
12. Press Mount R/O.
13. Restart your tablet.
14. Disable Wi-Fi.
15. Wait until the tablet recognizes your SIM card (It will say Auto-Update of Time).
16. Open Browser and try to access any website other than t-mobile.com
17. If all was successful, it should say 4G next to your signal strength.
Credit: huynhct (http://forum.xda-developers.com/showthread.php?t=896932)
III. Removing T-Mobile Bloatware
Make sure your tablet is Rooted before proceeding (Section I).
1. Download Root Uninstaller from the Market (free). https://market.android.com/details?id=com.rootuninstaller.free
2. Open the app and grant Superuser Permissions.
3. Freeze or Uninstall the system apps you do not need.
IV. Basic Navigation
=The Two Modes=
There are two modes built into Android devices that allow direct software installation.
The first is the Download Mode, which lets your device communicate with Odin (Third Party, Windows-based software that allows you to flash (replace) files on your device.) The primary use of this mode is to install a new Recovery Mode or fully resetting your device.
While in this mode, it will say "Do not turn off target." As long as you have no active transfers between the device and the computer, it is safe to turn off the tablet and restart.
The second is the Recovery Mode which allows you to install .zip that can alter system files. The primary use of the Recovery Mode is to flash ROMs (Literally Read-Only Memory, but in the Android world, custom, usually third-party developed software for your device). Read more about ROMs in Section V.
=Clockwork Recovery Mode=
When you first purchase your device, it will have a stock Android system recovery, which will not let you install .zip files (which is how kernels and ROMs are stored). Therefore, you must flash the Clockwork Recovery Mode if you ever plan on installing ROMs.
If you would like Clockwork, go to Section I, click on the link to djR3Z's tutorial, and follow ◄●Flashing a Custom Recovery●► to get the Clockwork Recovery Mode.
=To Enter Download/Recovery Mode=
1. Turn off your device.
2. Hold the power button and the volume down button (Left) together until two icons show up.
3. The one on left is the Recovery Mode and the one on the Right (Downloading...) is the Download Mode.
4. Use the volume down button to move between Recovery Mode and Download Mode and press the Power button to enter the selected mode.
Once inside the Recovery Mode, you navigate with the volume buttons and use the power button to select an option.
V. Installing ROMs
"The T-Mobile Tab isn't 4G, but HSPA+, the same as the international P7500. The only difference is it supports T-Mobile's funky AWS bands." - BarryH_GEG
=What is a ROM?=
Section IV touched upon what a ROM is - firmware for your device.
Custom ROMs usually employ tweaks that allow greater functionality and speed.
This is why a lot of users will install custom ROMs for their device.
ROMs can also let you unofficially update to versions of Android not yet supported by your carrier or device manufacturer.
=What about T-Mobile GT 10.1s?=
As I understand, we T-Mobile users CAN flash P75XX (P7500, P7510 models) ROMs to our tablet, although doing so would mean we may lose some functionality (especially ROMs designed for the Wi-Fi tablet and therefore does not support mobile data).
The list of known compatible ROMs follows. If you have information regarding compatibility of specific ROMs, please reply to this topic.
=Compatibility List=
T-Mobile Galaxy Tab 10.1 4G Optimized Roms
Confirmed Compatible ROMs (pershoot does not recommend installing ROMs not designed for your device; proceed with caution. They will boot and work as intended.):
For ICS Roms, make sure your Clockwork Mod is the latest version. You can download it here:
http://dev-host.org/IRb
RECOMMENDED: [ROM][Nightlies][03-02-2012]CM9 T-Mobile Galaxy Tab 10.1 4G: ICS Snapshot: http://download.cyanogenmod.com/?device=p4tmo
[ROM][GT-P7500] CM9 KANG (ICS Preview) 3G WORKING! http://forum.xda-developers.com/showthread.php?t=1461240
[ROM][KANG]CM9 ICS P75xx Preview 01/11/12 (http://forum.xda-developers.com/showthread.php?t=1425631)
[ROM] [ICS] Android Open Kang Project (http://forum.xda-developers.com/showthread.php?t=1459287)
To be updated.
Confirmed Incompatible ROMs:
[ROM][CWM][EUR][3G] BroodComb GT-P7500 XWKG9 V1
To be updated.
=How Do I Install a ROM?=
The basic process for installing a ROM is as follows:
1. Download the .zip that contains the files and place it on the main directory of your tablet (/sdcard/).
2. Access Clockwork Recovery Mode (Section IV).
3. If you are flashing an entirely new ROM, you typically have to "wipe data/factory reset."
4. Select Install zip from sdcard.
5. Locate your ROM's .zip file on your main directory, and select it.
6. Confirm install.
7. "reboot system now"
8. The first boot will take a while.
**Note: Most ROM developers recommend that after the device reaches the Welcome screen on first boot, you leave it alone for TEN minutes, as tempting as it is to play with it, to let everything settle. Then, restart your device, complete the welcome/basic registration wizard, and restart a second time.
This will ensure proper, fluid operation.
Individual ROMs may have varying directions.
Follow the directions given by the developer.
VI. HELP! I SCREWED UP! or How to Restore your Tablet to Stock (Original) Settings
Tablet won't boot? Best friend just became a brick?
Have no fear. As long as there are some signs of life in your tablet, you should be able to recover from almost any problem.
Solution: Restore your tablet to factory settings (this wipes all your data and returns to Stock firmware).
=Prerequisites=
Download and extract on your computer: http://www.hotfile.com/dl/138873533/bd475a6/T859UVKJ3_T859TMBKJ3_TMB.zip.html
Zip password: samfirmware.com
This file holds all the data your T-Mobile tablet originally ships with. DO NOT use for ANY other Galaxy Tab 10.1 device.
=Restoration=
1. Open Odin (Included in the root.zip folder from Section I).
2. Put your tablet into Download mode (refer to Section IV)
3. Plug the tablet into the computer.
4. Now in Odin, below ID:COM, it should have a yellow box with text inside, indicating that the device is connected.
5. Make sure Auto Reboot and F. Reset time are checked, and click "PDA" under "Files [Download]"
6. Navigate to the folder where you have downloaded "T859UVKJ3_T859UVKJ3_T859TMBKJ3_HOME.tar.md5" and double click on the file.
7. After ensuring that the PDA file has been selected, press "Start."
8. BE PATIENT. Even if Odin stops responding. Just leave everything alone. A blue progress bar should start filling below the Android logo on your tablet. When it is finished, it will enter the Recovery Mode and wipe all your data, then restart automatically.
9. Upon boot, which may take an unusually long time the first time, the tablet will be in original factory conditions.
10. If you get a boot-loop (tablet keeps restarting), enter Recovery Mode (Refer Section IV), go to "- wipe data/factory reset," and "select Yes --...", then restart the tablet. If this does not solve the issue, follow the 9 previous steps again.
C. Frequently Reported "Problems"
When I long press the power button, the device just shuts off instead of giving me options.
This is normal behavior for the T-Mobile ROM. If you install another compatible ROM, it will show you the boot/sound options.
My Browser keeps redirecting to the T-Mobile Website.
You are probably using a mobile SIM card, not a mobile broadband SIM card. Go to Section II for a solution.
My lockscreen does not work.
Mixed results have been obtained from using Odin to revert to stock (Section VI). A Custom ROM solves this problem.
Guide is to be continued.
-tjdwowh

What an awesome post for those that have tmo 10.1's
Sent from my SCH-I800 using xda premium

Can anyone confirm that "djR3Z's" tutorial works to hack tmobile 10.1 SGH-t859
?????!!!!!

peachfuzzdubstep said:
Can anyone confirm that "djR3Z's" tutorial works to hack tmobile 10.1 SGH-t859
?????!!!!!
Click to expand...
Click to collapse
Yes it does work.
http://forum.xda-developers.com/showthread.php?t=1335846

have anyone tried to flash modem.bin to make phonecalls?

alfredojra said:
have anyone tried to flash modem.bin to make phonecalls?
Click to expand...
Click to collapse
I have tried it, but it does not work.
Also, you would have to mess around with the AndroidManifest.xml on a few of the system apps to get the device to show the Phone app or receive calls.
There is no simple solution that you are probably looking for.
However, there is a ROM for the 10.1v that enables phone calls, albeit partially.
http://forum.xda-developers.com/showthread.php?t=1223131
I have not tried flashing it yet. So flash at your own risk.
If you experience problems, look at Section VI of this thread to revert to stock.

Awesome post; I don't even have a 4g tab and I'm giving thanks! We need a lot more of these (and a lot less of the "when will we get ICS" and "my homescreen is so laggy" threads....)

Thanks so much, this Guide is very much appreciated. I should get my SGH-T859 this week. What about a carrier unlock?

Use this to unlock. http://forum.xda-developers.com/showthread.php?t=1336659.
I will update the guide.
Edit: For future reference, instead of downloading that app, simply deleting the efs folder MIGHT be sufficient. I will try with a different carrier's SIM card and let you know.

tjdwowh said:
Use this to unlock.
http://forum.xda-developers.com/showthread.php?t=1336659.
Will update guide.
Edit: I am not sure if simply deleting the efs folder would be sufficient. I will try with a different carrier's SIM card and let you know.
Click to expand...
Click to collapse
That's the one I was going to try when I got mine. I just have not seen any confirmation that it works, until now.

Anyone having problems extracting the samsung firmware .zip file? I'm not even getting prompted for the password so it seems as the file is corrupt. I've tried it with WinRar and the built in windows unzipping application.

GrandMstrBud said:
Anyone having problems extracting the samsung firmware .zip file? I'm not even getting prompted for the password so it seems as the file is corrupt. I've tried it with WinRar and the built in windows unzipping application.
Click to expand...
Click to collapse
Try redownloading. If it doesnt work, I will reupload it for you.

tjdwowh said:
Try redownloading. If it doesnt work, I will reupload it for you.
Click to expand...
Click to collapse
I have downloaded it twice and same thing. I'll try it at work and see if it extracts.
Tried it on another machine and same thing.

I just copied the link from this site:
http://www.mod2xtreme.com/showthread.php?t=11752
I will upload it right now and put up a mirror.

GrandMstrBud said:
That's the one I was going to try when I got mine. I just have not seen any confirmation that it works, until now.
Click to expand...
Click to collapse
It worked for me

I am having an issue doing the restore it keeps failing.
Says this in odin: <ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T859UVKJ3_T859UVKJ3_T859TMBKJ3_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> cache.img
<ID:0/003> NAND Write Start!!
<ID:0/003> hidden.img
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
On tablet it says partition size is small
Can anyone tell me what I am doing wrong or what else i should be doing to get the restore to work?

kanice27 said:
I am having an issue doing the restore it keeps failing.
Says this in odin: <ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T859UVKJ3_T859UVKJ3_T859TMBKJ3_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> cache.img
<ID:0/003> NAND Write Start!!
<ID:0/003> hidden.img
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
On tablet it says partition size is small
Can anyone tell me what I am doing wrong or what else i should be doing to get the restore to work?
Click to expand...
Click to collapse
Make sure your tablet's driver is installed.
If you cannot solve the issue, try using a different USB port, different computer, etc. I have tested the file on multiple occasions and can verify that it works.

Good writeup.Now I know where to go to when a stable version of ICS is released.
As for the unlock,I followed all the instructions given by dagentboy and it worked for me.The rooting video for the P7500 also helped me to successfully root the T859.
Thanks for the thread.

Great post, and exactly what I was looking for.
Any chance of making this a sticky?

The carrier unlock method via SGS Unlock pro doesn't seem to be working. When I boot up it still asks for the carrier unlock code.
EDIT, wrong app. I had the one for the Vibrant purchased and was using that. Downloaded and purchased the right one and it works perfect. Is the serial number supposed to be all zeros?

Cannot mount '/data' in twrp. Is there anything left for me to try?

I am afraid i have turned my galaxy tab 4 7" (sm-t230) into an expensive coaster at this point.
It doesn't do much of anything anymore. When it's booted it does nothing but show the samsung logo sparkling and when i start it into twrp just about anything i do ends with "cannot mount '/data' and not much else.
the local storage shows 0 and through the filemanager i see there are the folders but no files inside the folders.
Ofcourse i am well aware that i must've done goofed somewhere in my enthousiastic attempt to install a custom rom and the increasingly frantic attempts after that somehow resulted in the tab not booting past the samsung logo to fix it (from trying other roms to using odo in different configs to get anything on it that worked, including kernels and such) probably only added to the result which i described above. I know that, if this is irreversably killed the tablet i have only myself to blame.
But somehow i still have a sparkle of hope there is a way to fix the damage my stupidity has caused. It's still trying to boot and when i try to install for example the stockrom rom zipfile the progress bar dutyfully progresses until its end and the message "successfull" even shows in blue. When i put the tablet into download mode Odin still gives the all clear like it should but it seems like its teasing me with those things. When i boot it stops at the logo and when i go into twrp and do anything it fails to mount '/data' and some actions result in other failures to mount folders.
So.... IS there anything i can still do? (flashing the stock samsung rom wont work at all by the way, from twrp)
any help in getting any rom doing anything similar to working would be an improvement and appreciated.

So you say you've tried reinstalling the stock rom in TWRP, have you tried flashing a stock official firmware file with Odin?

thisisapoorusernamechoice said:
So you say you've tried reinstalling the stock rom in TWRP, have you tried flashing a stock official firmware file with Odin?
Click to expand...
Click to collapse
Well, no. Not through Odin. I haven't been able to find, much less download, the tar version of the one for my region. I'm in the Netherlands and so i guess i am looking for either a specifically dutch or an international or european version.
I have found the zip version for my region and spent almost 12 hours downloading it (after spending hours to find a host that would actually start the download without either survey terror or payed account registration torture.)
twrp doesn't like it though and simply fails.
[update]i cannot believe my stupidity. Your post made me wonder if the zip file contained the tar file i was looking for. It (ofcourse) did and i am now extracting it. I shall try to Odin it onto the tablet in download mode and post the results here.
I noticed the region i have isn't listed in the list you linked to. If you want it i can put it in my dropbox, google drive or onedrive for you so you can download it. the filename is T230XXU0AOD2_T230PHN0AOD3_PHN.zip and the region is the netherlands.
[/update]

deuZige said:
Well, no. Not through Odin. I haven't been able to find, much less download, the tar version of the one for my region. I'm in the Netherlands and so i guess i am looking for either a specifically dutch or an international or european version.
I have found the zip version for my region and spent almost 12 hours downloading it (after spending hours to find a host that would actually start the download without either survey terror or payed account registration torture.)
twrp doesn't like it though and simply fails.
[update]i cannot believe my stupidity. Your post made me wonder if the zip file contained the tar file i was looking for. It (ofcourse) did and i am now extracting it. I shall try to Odin it onto the tablet in download mode and post the results here.
I noticed the region i have isn't listed in the list you linked to. If you want it i can put it in my dropbox, google drive or onedrive for you so you can download it. the filename is T230XXU0AOD2_T230PHN0AOD3_PHN.zip and the region is the netherlands.
[/update]
Click to expand...
Click to collapse
It's a good thing there's no audio recording of what i shouted here the last 30 seconds to a minute. Everything seemed to go perfectly in Odo. I started the tablet in download mode, started Odo, and connected the usb cable. then clicked ap and selected the tar file and removed the tick at f.reset time. then i clicked start. heres the messages odo gave me... errr i mean odin:
Code:
<ID:0/004> Added!!
<ID:0/004> Removed!!
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T230XXU0AOD2_T230PHN0AOD3_T230XXU0AOD2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<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> timh.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> obm.bin
<ID:0/004> loke_1st.bin
<ID:0/004> loke_2nd.bin
<ID:0/004> DTim.Primary
<ID:0/004> DTim.Recovery
<ID:0/004> DTim.CP
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img
<ID:0/004> radio.img
<ID:0/004> cache.img
<ID:0/004> hidden.img
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/004> Removed!!
Odin showed the green square with pass and the tablet rebooted.
and didn't go further than the samsung logo.
which it show still.... i have exhausted my most vile, evil and offensive curseword vocabulary shouting (which my neighbours will probably not appreciate as it's 01:35 am right now) before starting to write this reply....
i guess i am, truely inescabably, F worded now ain't i??
i am so depressed right now i can't even tell ya.
anyway, any suggestions?
(thanks for taking the time to read my sorrows and replying by the way. it IS really appreciated.)

just another reply to mention that i tried the same as the above with the tick at f.reset time and got the same result.
staring at the samsung logo in dispair right now....

deuZige said:
just another reply to mention that i tried the same as the above with the tick at f.reset time and got the same result.
staring at the samsung logo in dispair right now....
Click to expand...
Click to collapse
Did you reboot into recovery and factory reset? That should clean things up. I had to do that every time I flashed a firmware through Odin.
Sent from my ZTE_N9511 using Tapatalk

DUHAsianSKILLZ said:
Did you reboot into recovery and factory reset? That should clean things up. I had to do that every time I flashed a firmware through Odin.
Sent from my ZTE_N9511 using Tapatalk
Click to expand...
Click to collapse
i hadn't.
no i have, and i still get no further than the samsung logo.
the recovery was nothing like twrp though and it had loads of errors. again and...
AAAAH!!
OMG!!
YESYESYES!!!!
you guys are like gods to me now. As i was typing this reply the samsung galaxy welkom screen sprang to life and is now waiting for me to configure stuff!!! It seems to have worked!!!!!!!
I will not publicly explain the circumstances (i did in a pm to poorlychosenname) but trust me when i say you have no idea how much of a good deed you guys did here today!!!
I am truely and greatly indebted to both you guys/galls and if there is anything i can do for you, now or in the future, please ask and i will do anything i can to help!!!!
I am literally in teart right now!!!
Thank you!!!!

deuZige said:
i hadn't.
no i have, and i still get no further than the samsung logo.
the recovery was nothing like twrp though and it had loads of errors. again and...
AAAAH!!
OMG!!
YESYESYES!!!!
you guys are like gods to me now. As i was typing this reply the samsung galaxy welkom screen sprang to life and is now waiting for me to configure stuff!!! It seems to have worked!!!!!!!
I will not publicly explain the circumstances (i did in a pm to poorlychosenname) but trust me when i say you have no idea how much of a good deed you guys did here today!!!
I am truely and greatly indebted to both you guys/galls and if there is anything i can do for you, now or in the future, please ask and i will do anything i can to help!!!!
I am literally in teart right now!!!
Thank you!!!!
Click to expand...
Click to collapse
No problem! Let "us" know if you get any data errors or so. My guess is that you had an messed up data partition since I've seen a few with the same thing.
If data is still messed up, flash back twrp, go to wipe, hit advanced wipe, then tick the data then hit "repair or change file systems" something like that and hit repair. Then slide the slider.
If that doesn't work... go to wipe , theb hit advanced wipe, tick data, hit "repair or change file systems" then format it to ext4
Sent from my ZTE_N9511 using Tapatalk

DUHAsianSKILLZ said:
No problem! Let "us" know if you get any data errors or so. My guess is that you had an messed up data partition since I've seen a few with the same thing.
If data is still messed up, flash back twrp, go to wipe, hit advanced wipe, then tick the data then hit "repair or change file systems" something like that and hit repair. Then slide the slider.
If that doesn't work... go to wipe , theb hit advanced wipe, tick data, hit "repair or change file systems" then format it to ext4
Sent from my ZTE_N9511 using Tapatalk
Click to expand...
Click to collapse
honestly, i have tested taking pictures, uploading them to google and i have added all new accounts where i could. That worked without error, and the picture worked, and uploaded. I am doing nothing else until i get back home tomorrow from the park where i'll be taking pictures of my son.
When those are safe, i'll do whatever you want!!!
again, i cannot express the greatness of my gratitude for this!!
[supplemental]
i must sleep now. gnight!!!
[/consciousness]

Seems like everything is working fine! No need for wiping and formatting data if you have no more issues. I guess your good to go!
Sent from my ZTE_N9511 using Tapatalk

Hey I'm sorry I never got back to you, and I feel like a total moron for forgetting to tell you to factory reset, glad @DUHAsianSKILLZ took care of things for @deuZige, I hope everything's OK going forward and I'll be happy to help if I can if it isn't.

Custom binary blocked by frp lock 2019

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