Related
(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?
thinks should be super easy but sadly things got F-ed up for no reason.
Hoping that someone can help me out.
I'm on a SM-N9005 model
Reactivation lock off
Knock kernel lock 0x0
I also see on the Odin mode screen that it says
"Write protection: Enable" (not sure if that's important).
On the Box the phone says sm-n9005zwexs
I downloaded the drivers from http://stockroms.net/file/Drivers/Samsung/SAMSUNG_USB_Driver_for_Mobile_Phones.exe (which is what all sites I've checked recommended).
I've tried different USB ports.
I'm using the USB 3 charger that came with the Note 3
Now I followed the instructions by downloading Odin, going into "odin mode" on the device (down volume, power and home and seeing the giant green android), the phone is detected and I select the CF-Auto Root file after clicking on PDA (in Odin 3) and sadly I end up getting a fail (specifically when it gets to 40% of the progress bar on the note 3). Since I have an N9005 I used this CF Auto Root file http://download.chainfire.eu/352/CF-Root/CF-Auto-Root/CF-Auto-Root-hlte-hltexx-smn9005.zip
I've tried both versions Odin3 1.85 and Odin 3 3.09 and they both give me a giant red FAIL.
Now when I tried to reboot my phone, I get "firmware upgrade encountered an issue"
When I try and launch KIES 3, it says that the mobile phone is not supported -_-
I really don't know what to do. At this point, screw rooting, I just want it to work -_-
I know that people don't need much of an incentive on these forums, but happy to even go as far as paying a reward to fix this
Only had the phone for a day...
I read about others that have bricked their new N3 trying to root it, and, losing their warranty in the process, (it's the first thing they check).
Seems as if most of the educated folks on this site are waiting for a safe procedure, (and I'm gonna follow their lead).
Good luck my friend, I hope you didn't ruin a $700 device :crying:
K, I had a similar problem. I accidently left KIES running in the background. Kies and ODIN don't play nice together. If you left Kies running it can cause havoc while trying to flash and seems to cause ODIN to fail no matter what version.
Thought I'd bricked my phone for a little while too...
amnesia said:
thinks should be super easy but sadly things got F-ed up for no reason.
Hoping that someone can help me out.
I'm on a SM-N9005 model
Reactivation lock off
Knock kernel lock 0x0
I also see on the Odin mode screen that it says
"Write protection: Enable" (not sure if that's important).
On the Box the phone says sm-n9005zwexs
I downloaded the drivers from http://stockroms.net/file/Drivers/Samsung/SAMSUNG_USB_Driver_for_Mobile_Phones.exe (which is what all sites I've checked recommended).
I've tried different USB ports.
I'm using the USB 3 charger that came with the Note 3
Now I followed the instructions by downloading Odin, going into "odin mode" on the device (down volume, power and home and seeing the giant green android), the phone is detected and I select the CF-Auto Root file after clicking on PDA (in Odin 3) and sadly I end up getting a fail (specifically when it gets to 40% of the progress bar on the note 3). Since I have an N9005 I used this CF Auto Root file http://download.chainfire.eu/352/CF-Root/CF-Auto-Root/CF-Auto-Root-hlte-hltexx-smn9005.zip
I've tried both versions Odin3 1.85 and Odin 3 3.09 and they both give me a giant red FAIL.
Now when I tried to reboot my phone, I get "firmware upgrade encountered an issue"
When I try and launch KIES 3, it says that the mobile phone is not supported -_-
I really don't know what to do. At this point, screw rooting, I just want it to work -_-
Click to expand...
Click to collapse
It's much more helpful when trying to troubleshoot the failure if you actually paste the full log from Odin. The "write protection enabled" thing is not part of the problem. That's bootloader protection and you want it on, because it protects you from flashing the wrong device bootloader and bricking your device.
If you can still get into download mode, you have nothing to worry about. In general, it's good to redownload the ROM again, make sure that it passes the md5 check, reboot, and reflash.
You don't have a brick. So you are lucky. Boot into download mode and flash N9005 ROM, preferably same one or later version.
Here - http://samsung-updates.com/device/?id=SM-N9005
Get for your region or any other one. Cheers!
And yh! UNINSTALL KIES! Leaving the drivers
Hi there,
This is what I get in Odin
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-hlte-hltexx-smn9005.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> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
thanks for that, I've gone ahead and downloaded the KSA version since I bought mine in Qatar and there was no Qatar ROM.
Just to be clear, what's the best way to flash it to my phone?
In my case I didn't have KIES running. I've also uninstalled it to be sure.
Kies seems to be useless since it doesn't event detect the note 3 as a supported device.
One more post. Tried three different cables now (Nokia, HTC One, and the Note 3 cable).
Tried all the different ports on my iMac (I'm on VMWARE Windows 8)
Tried downloading a stock ROM, tried Flashing with N9005 KSA version.
Got the same exact error, Complete(Write) operation failed
Are you trying to Root ur phone or Flash Stock ROM?
Same problem.
I have the self same problem.
I was trying to root the Note 3 (LTE) and got the FAIL error in red on ODIN 3.09.
Do I continue to try to root, or do I need to reinstall the stock ROM?
Any assistance appreciated for this idiot newbie.
Sothai said:
I have the self same problem.
I was trying to root the Note 3 (LTE) and got the FAIL error in red on ODIN 3.09.
Do I continue to try to root, or do I need to reinstall the stock ROM?
Any assistance appreciated for this idiot newbie.
Click to expand...
Click to collapse
Are you running 4.4 or 4.3?
Which root method are you using?
Thanks for the fast reply! I am running 4.4.2 and was attempting the ibitimes listed for method, but I am not yet allowed to post links. (Root Galaxy Note 3 LTE on Android 4.4.2 N9005XXUENB4 Stock Firmware [GUIDE])
The method said to get ODIN 3.09 and the CF Root package, which I did. Does this help, or can I provide any further info?
Sothai said:
Thanks for the fast reply! I am running 4.4.2 and was attempting the ibitimes listed for method, but I am not yet allowed to post links. (Root Galaxy Note 3 LTE on Android 4.4.2 N9005XXUENB4 Stock Firmware [GUIDE])
The method said to get ODIN 3.09 and the CF Root package, which I did. Does this help, or can I provide any further info?
Click to expand...
Click to collapse
Download and extract this file and flash through included odin.
amnesia said:
One more post. Tried three different cables now (Nokia, HTC One, and the Note 3 cable).
Tried all the different ports on my iMac (I'm on VMWARE Windows 8)
Tried downloading a stock ROM, tried Flashing with N9005 KSA version.
Got the same exact error, Complete(Write) operation failed
Click to expand...
Click to collapse
KSA has Jellybean 4.3 up to now that means u r trying to flash 4.3, before root process on which version u were, jelly bean or kitkat, I am not sure but your phone is seems to be for Singapore.
OK, many thanks. Downloading now.
It seems to be quite a large file, as my system says 44 minutes remaining - does that sound correct? May I ask what the file contains to be so large? Thanks!
Sothai said:
OK, many thanks. Downloading now.
It seems to be quite a large file, as my system says 44 minutes remaining - does that sound correct? May I ask what the file contains to be so large? Thanks!
Click to expand...
Click to collapse
It's about 20 meg in size. It contains odin and the cf auto root tar file.
OK, it's downloading, so delete the copies of ODIN and CF Root that I already have and use the ones in that bundle, yes?
I must admit that I am panicking here. The phone won't boot as it is, so I hope this will unbrick it as well as root it...
Sothai said:
OK, it's downloading, so delete the copies of ODIN and CF Root that I already have and use the ones in that bundle, yes?
I must admit that I am panicking here. The phone won't boot as it is, so I hope this will unbrick it as well as root it...
Click to expand...
Click to collapse
Yes use the one in the bundle.
Can you boot your phone in download mode though?
:crying::crying::crying: I can`t flash my S4 SGH-M919V with odin, i try to flash any firmware lollipop 5.0.1 of GT-I9505 that is the same thing and others firmwares of 4.4.4 of the same model but always send me FAIL abort the operation.
I don`t know why when I put my s4 in odin mode show this information in small letters:
ODIN MODE
PRODUCT NAME: SGH-M919V
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
KNOX KERNEL: 0x0
KNOX WARRANTY VOID: 0x1
CSB-CONFIG-LSB: 0x30
WRITE PROTECTION: Enabled
MMC BURTS MODE: Enabled
One question the last lines maybe is the problem write protection enabled or not? if is yes the problem how i can fix it for flash any firmware on my s4 thanks for your time (if this post is in the wrong section please change thanks again) i hope solutions XDA-Developers
http://forum.xda-developers.com/galaxy-s4-tmobile is where you need to go for issues with your device, as that forum has far more people familiar with your S4. This is the international S4 forum.
Now, regarding Odin, you should be using a recent version of Odin (current is 3.10), the original cable connected directly to the computer, not using a hub, and not have Kies running. You may also need Samsung's drivers if you haven't installed Kies or downloaded them from Samsung, so if you haven't already downloaded them, do so. That said, attempting to flash an I9505 ROM to your device is automatically going to fail. Odin verifies the model number and other parameters in the S4 before it allows a flash to proceed. Naturally, the model numbers don't match and thus flashing the ROM will not work.
Write protection and MMC bursts modes are supposed to be enabled, so you can eliminate that as a concern.
Thanks for your anwer bro but so to try install a firmware of the same model of mine and the same error
Post your Odin log, so we can see where it fails.
This is mi phone information: i have install Albe95 rom
AP:I9505XXUHOA7
CP:M919VVLUFNH3
CSC:I9505OXAHOA7
This is the Error with any versión of odin and any firmware stock forma this model or :
Enter CS for MD5..
Check MD5.. Do not unplug the cable..
Please wait..
I9505XXUHOB7_I9505YXYHOB5_I9505XXUHOB7_HOME.tar.md5 is valid.
Checking MD5 finished Sucessfully..
Leave CS..
Added!!
Odin v.3 engine (ID:17)..
File analysis..
SetupConnection..
Initialzation..
Get PIT for mapping..
Firmware update start..
SingleDownload.
sbl1.mbn
NAND Write Start!!
FAIL! (Auth)
Complete(Write) operation failed.
All threads completed. (succeed 0 / failed 1)
Any solution? Thank s
I read some post and say it that write protection is enable never can't flash any firm help
Seriously? After telling you that you cannot install an I9505 ROM on your device and explaining why you can't, you're still trying?
YOU CANNOT INSTALL AN I9505 ROM ON A T-MOBILE S4! All attempts to do so will automatically fail. The only stock ROMs that will work on your device are T-Mobile ROMs.
What part of the above do you not understand? Tell me now so I can dumb things down.
i m understand all above OK
this log show with any firmware for the phone or t-mobile firmware men i triying to install stock firmwares for my mobile ok and don`t work of any way but thanks for your time and help :good::good::good: i waiting for more solutions or i read the link than you put above
@LE_17: I apologize for snapping. However I thought I had made it reasonably clear that you could not install an I9505 ROM on your device. Apparently this wasn't the case. In any event, your ROM is here.
that s ok bro no problem
thank s for your time but the link of the firmware that you post i have in my PC downloaded and when i flash it send the same error i dont know why :crying::crying::crying:
You may want to try a different computer completely. Odin is sometimes weird like that. It could also be that the ROM you're currently using may require some steps to get the correct version of Android back on the device, especially if going down from Android 5.x to Android 4.4.4.
Strephon Alkhalikoi said:
You may want to try a different computer completely. Odin is sometimes weird like that. It could also be that the ROM you're currently using may require some steps to get the correct version of Android back on the device, especially if going down from Android 5.x to Android 4.4.4.
Click to expand...
Click to collapse
You gave him a version for the T-mobile variant. He has a different variant. He has the SGH-M919V. It's really confusing al those different models.
Try to flash the latest version from here.
http://www.sammobile.com/firmwares/database/SGH-M919V/#firmware
if it fails, try different usb port and different usb cable.
Try using the latest version of Odin (v3.10.6) and see if you can flash the correct firmware for your rom.
http://forum.xda-developers.com/showthread.php?t=2711451
Try using a different USB port if its failing again and make sure your USB drivers are up to date
Ok man i try it thanks for your time and answer post the result
Lennyz1988 said:
You gave him a version for the T-mobile variant. He has a different variant. He has the SGH-M919V. It's really confusing al those different models.
Click to expand...
Click to collapse
Well color me silly. I did miss that, and I'm sure the OP did too as he mentioned already having that ROM.
LE_17 said:
Ok man i try it thanks for your time and answer post the result
Click to expand...
Click to collapse
If you're trying to flash the official Lollipop update for the S4, use the Canadian version. I tried using the Rogers version (as Videotron uses Rogers' network) from SamMobile and it worked perfectly well. I was even able to change my CSC to Rogers and get the update through Kies.
Disclaimer: If you choose to try this, it is at your own risks. I cannot be held responsible if your phone gets damaged in any way nor can I guarantee the results.
No need for this anymore! The SGHM919V has gotten the Lollipop update this morning.
All,
I've spent the better part of the last two days trying with zero success to downgrade my Verizon Galaxy S4 SCH-I545 from 5.0.1 to 4.4.2. I've read dozens of pages on various forums, both on general instructions for the procedure as well as pages relating directly to the fault I'm seeing. In short, I get the Complete(Write) operation failed error in Odin. The reason I'm trying to do this is a general disappointment in Lollipop, it has slowed the phone down (I need to kill off all apps at least once a day just to keep performance up) and I've enjoyed none of the "benefits" of Lollipop on the phone. It's been so bad I've deliberately ignored all requests my Tab 4 makes to upgrade to Lollipop.
I've tried the firmware reflash using Odin 3.04 as well as 1.85. I've tried both versions on two different computers, one running Windows 7 Home, the other running XP. I've run them standard, and on Win7 as Administrator. Fresh reboots. The Win7 has Kies (not running) and the WinXP computer has never had Kies, just downloaded the current Samsung USB drivers. I've tried running two different firmwares downloaded from Sammobile, on each machine, with every combination I can think of. I'm using the factory USB cable plugged directly into the motherboard on each machine. I've varied the moment I plug the phone into the cable based on various recommendations, waiting until Odin is already running, or getting the phone in download mode first then plugging in, etc. I've also tried re-running the update again immediately on failure, and again after rebooting the phone back into Download mode, trying multiple times in a row without closing down Odin, and then alternately restarting everything after each failure. Basically I've tried pretty much everything I've read, and it feels like I'm following the rules of an old gypsy woman, if I update the phone at midnight while swinging a dead rooster over my head, standing on my left foot only, all will go ok. Only nothing goes ok.
This is the complete error I get in Odin 3.04:
<ID:0/012> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I545VRUFNG6_I545VZWFNG6_I545VRUFNG6_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/012> Odin v.3 engine (ID:12)..
<ID:0/012> File analysis..
<ID:0/012> SetupConnection..
<ID:0/012> Initialzation..
<ID:0/012> Get PIT for mapping..
<ID:0/012> Firmware update start..
<ID:0/012> aboot.mbn
<ID:0/012> NAND Write Start!!
<ID:0/012>
<ID:0/012> Complete(Write) operation failed.
<ID:0/012> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
The first four lines happen almost immediately. Then it seems to wait or hang for about 45 seconds (meanwhile one CPU maxes out), afterwards the rest of the lines pretty much spit out instantly. On the phone the display changes slightly, one little tick mark appears on the progress bar, then nothing else. The phone appears to be locked and needs a very long hold of the power button to shut off. These symptoms appear identical regardless of which computer I use, or which version of Odin I use, which makes me suspect the phone is the culprit rather than the software/hardware of either computer. I figure if I had, for example, a corrupted firmware file it would fail somewhere down the line in the install, or even after it's dumped the file to the phone.
One thing that worried me (and I NEVER found any mention of this in any directions) is the amount of available space on the phone. With the bloatware on the phone (7.07GB of "miscellaneous files"?!?) I only have 2.76GB free on the internal memory, and the firmware file is 2.4GB. I'm assuming that it all needs to copy to internal memory first. After my first failed attempts I checked space available and I had less than 2.4GB free. After clearing cache and a few apps I got it up to 2.76GB.
USB debugging is on, battery level is full or high on the phone, reactivation lock is off, the phone connects to either computer just fine and interfaces with Windows Explorer, I can see and access files on the phone via My Computer without any error.
I saw one page describing using Heimdall as a wholly different idea, it seemed MUCH more complex and my gut reaction is it looks like it would be easier to brick the phone. Is there some manual way I can dump the firmware to the phone and get it to read the file such that it doesn't require a computer?
Anything else to suggest? In general I still like the phone and don't have a great deal of interest in upgrading, but it's getting frustrating enough that I'm considering junking the phone.
Thanks in advance,
Ryan
Try a different Odin version. 3.09 worked fine for flashing modems and bootloaders on my device.
Whe should not forget that Odin is a leaked software.
GDReaper said:
Try a different Odin version. 3.09 worked fine for flashing modems and bootloaders on my device.
Whe should not forget that Odin is a leaked software.
Click to expand...
Click to collapse
Well, my first attempt with 3.09 is doing something different. I have no idea if it's working or not. It's gone as far as Checking MD5 finished Successfully, then it's been on "Leave CS..." for the past 15 minutes or so. No change on the phone's screen. I have no idea if it's hung, or downloading, working, etc. Guess I'll let it sit there unless someone can tell me what's going on. Thanks!
Diddler77 said:
Well, my first attempt with 3.09 is doing something different. I have no idea if it's working or not. It's gone as far as Checking MD5 finished Successfully, then it's been on "Leave CS..." for the past 15 minutes or so. No change on the phone's screen. I have no idea if it's hung, or downloading, working, etc. Guess I'll let it sit there unless someone can tell me what's going on. Thanks!
Click to expand...
Click to collapse
Got pissed and disconnected it after about 45 minutes. Switched to my desktop/Win7 machine. With the bigger monitor I could see that the whole time it was sitting on "Leave CS" it wasn't doing a thing, it now gave me the option to hit the 'Start' button at the bottom of the screen. I LOVE applications that don't let you resize to fit odd sized monitors (like my old Netbook).
So, I hit 'Start', and it pretty much immediately fails. Some of the error messages are differerent though, here's the whole thing:
<ID:0/012> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I545VRUFNG6_I545VZWFNG6_I545VRUFNG6_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/012> Odin v.3 engine (ID:12)..
<ID:0/012> File analysis..
<ID:0/012> SetupConnection..
<ID:0/012> Initialzation..
<ID:0/012> Get PIT for mapping..
<ID:0/012> Firmware update start..
<ID:0/012> SingleDownload.
<ID:0/012> aboot.mbn
<ID:0/012> NAND Write Start!!
<ID:0/012> FAIL! (Auth)
<ID:0/012>
<ID:0/012> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
What I find most interesting is the 5th and 4th line from the bottom, Write start followed by FAIL! (Auth). I interpret it as Odin failed to get authorization from the phone to perform the write function. Any other ideas? Going to try Odin 3.10.6 next.
Diddler77 said:
Going to try Odin 3.10.6 next.
Click to expand...
Click to collapse
Yeah, same problems on both computers, both new versions of Odin. Did notice something this time around on the phone's screen that I hadn't noticed before, though it seems to happen in all versions of Odin. Two lines appear on the phone when I hit 'Start' in Odin:
START [224,1440]
SW. REV CHECK FAIL : FUSED : 8, BINARY : 6
The numbers after FUSED and BINARY are very difficult to read. Above is my best guess. Any of them may be a 0 or an 8.
Thanks!
Have you tried flashing the rom together with a pit file?
Make sure you also tick?"re-partition" when you do it.
GDReaper said:
Have you tried flashing the rom together with a pit file?
Make sure you also tick?"re-partition" when you do it.
Click to expand...
Click to collapse
That I have not tried. From what I gather I need a PIT file specific to the model. Any idea where I can get it? In terms of the end result, what's the difference between using the PIT and re-partitioning compared to what I've been trying? Like, why do both options exist?
Thanks!
You need a pit file specific to the storage size of your device.
With a pit file, the phone storage will be repartitioned. Something like you would do on a pc when you need more storage on one partition. Only that here you don't get to choose the size.
I am not that familiar with pit files. But it is worth a try, since everything else failed.
GDReaper said:
You need a pit file specific to the storage size of your device.
With a pit file, the phone storage will be repartitioned. Something like you would do on a pc when you need more storage on one partition. Only that here you don't get to choose the size.
I am not that familiar with pit files. But it is worth a try, since everything else failed.
Click to expand...
Click to collapse
Dont the firmwares originally come with pit files ?
Deathvirus said:
Dont the firmwares originally come with pit files ?
Click to expand...
Click to collapse
From what little I gather from the simple Odin instructions page, some firmwares are packaged with additional files. The two versions I've downloaded from sammobile for my device type only contained a single tar.md5 file when unzipped.
Check http://forum.xda-developers.com/galaxy-s4-verizon if you haven't already done so, but I think you're going to have a problem trying to downgrade, as your device has a locked bootloader. The bootloader being locked is primarily designed to prevent root, but it also has the effect of preventing downgrades. If it didn't have that capability, users could simply flash a bootloader that could be compromised, obtain root, and remove the bloatware.
You posted your question in the International S4 forum, and international devices don't lock their bootloaders, which is why no one has really picked up on this until now. The only reason I picked up on the possibility of it being your bootloader is because I own an international device yet live in the US, so I'm acutely aware of the locked bootloaders foisted upon us by AT&T and Verizon.
It is my understanding that Odin fails after trying to flash aboot.mbn because the ROM being flashed has a bootloader that is older than the bootloader currently installed on the phone.
Some models of the s4, such as the Canadian version (sgh-i337m) can be flashed from stock LP to stock KK using Odin without issue.
You're right about the age of the bootloader being a reason why downgrading fails. You're also right that most devices can downgrade without issue. However, the OP's device is not one of them. He happens to have one of the models with a locked bootloader, and to the best of my recollection, the locked bootloader means you cannot downgrade, period.
Strephon Alkhalikoi said:
Check http://forum.xda-developers.com/galaxy-s4-verizon if you haven't already done so, but I think you're going to have a problem trying to downgrade, as your device has a locked bootloader.
Click to expand...
Click to collapse
If this is true, I'm really ticked off. What a waste of time. You'd think that somewhere, on ANY of the forums and websites someone would have mentioned that my device is crippled in this manner. Every single site makes Odin sound like the silver bullet.
Why is there even firmware available for Verizon GS4's then?
Understand I'm not ungrateful for the advice, I do appreciate it. Just venting.
-sigh-
100% true, and it's not limited to Verizon either. AT&T also locks the bootloader. As to mentioning it, it likely is mentioned in the AT&T and Verizon S4 General forums, but you won't find that information here. As I mentioned, this is the International S4 forum, and we don't have locked bootloaders to deal with.
I know it sucks, but this is what we deal with in the US. That's why for my next device I went with a Nexus.
I don't have a PIT file for OF4 firmware on the SM-S975L (Straight Talk variant) so the downgrade failed as for OP, I'm stuck in download mode with a yellow triangle.
Yeah, Verizon released this phone to Straight Talk evidently. I'm locked tight and basically hard bricked. Wicked pissed, too. Since Kies says phone model not supported. CANNOT restore.
Nexus it probably is. This phone was a waste of money.
Or at least...that was until I found a hack that let me install the old Jellybean kernel! http://forum.xda-developers.com/gal...ariant-of4-t3279890/post64511525#post64511525
Only problem is, sure, you can get your kitkat kernel back, but I wasn't successful probably because NB1 firmware was Verizon firmware at the time of my flash so my CSC didn't work, but since they're both JellyBean I got root. But as long as they're the same carrier my hack should work. Link me your firmware, I can let you try. It'll trip the hell out of KNOX though. I used Odin 3.07. It requires some by-hand hex editing. When you gain root you can disable Knox to flash other things with SuperSU.
@LupineDream: Of course you weren't successful in changing kernels. The SM-S975L is not a CDMA (i.e. Verizon) phone, but uses T-Mobile towers. The SCH-R970G is the other Straight Talk S4 and it used Sprint as a carrier. Verizon does not allow MVNOs access to their LTE network, which is how you can tell that you're NOT on Verizon.
The bootloader on Straight Talk S4 devices is not locked down like the OP's bootloader. Otherwise it would not be possible to install custom ROMs to the device. I have a distinct feeling that your hack will not work. Not because it's incorrect as you clearly had success, but because of the locked bootloader on the device, which is designed to prevent the very thing you successfully accomplished on your Straight Talk device.
To restore your phone to working condition, download the S975L firmware from sammobile and flash it through the BL slot in Odin. Then sell it and get a Nexus.
Hey, if I found a workaround for obtaining root on the ATT variant, users of that phone now have an fstab and an (almost complete) list of partitions and mount points for a device tree. So I hope that information at least made their lives better. In knowing they can indeed flash a kernel with said workaround. The device list, fstab, and mount points are all in my root guide now. Since after reflashing the boot image by itself the device boots again and has maintained root status, though with broken WiFi which can be fixed with a custom kernel. Oh well, at least users of my phone get a custom ROM., at least if you've got the ATT variant. All the info is in my thread for ATT variants. I' don't have my stock kernel, however. But it isn't an issue as for what I've provided, I think its enough to get a custom one for the ATT variants. Still going to sell and get my Nexus. But left it with a bang I suppose. I'll hack a locked bootloader until I'm blue in the face if it means I got root. You are indeed right, though. It isn't for ME to keep around, but please note that before I was even able to flash a kernel, I had to hack it. It was displaying secure boot status and would not allow flashing of anything. I was told they where all locked. I was never able to root OF4 before because of "locked conditions" where NB1 refused to flash before my hack.
I'm going shopping soon. Maybe I'll get the Verizon variant on the side to see if I can force my way in through another one of these types of loopholes. After all, my device would not flash a kernel before I did what I did to it...I was able to disable knox and allow kernel flashing by doing so. Through SuperSU. That bit was set before I did what I did to the device. All it takes is flashing of the NB1 kernel to Verizon through tricking knox it's official firmware and enough know-how to get the system to boot well enough to be able to inject root.
My device still won't flash non-official firmware or recovery. Because of a verification check in the kernel. I tried. Sig fai on kernel. But, now that Knox can be disabled, all it takes is an if/of dd flash of modified aboot in adb and then anything is possible at that point. I looked into loki_tool for always passing signature check passed to hardware knox. And clearing out EERAM before knox gets a chance to react. Loki'fied aboots satisfy knox pretty well I'd say.
The ROM displayed there iis for the Verizon variant by the way. I found Verizon-related apks in system.img.ext4. Even without the modem, it still won't flash. Have a download, rename it, extract the tar and hex edit look through the file. Yep, that's a verizon variant ROM.
One question, however, is does hardware knox do a checksum on aboot? That would pretty much make this argument a moot point.
Ask Chainfire. He needed to know about how Knox functioned so he could get SuperSU to disable it.
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