Attend XDA's Second Annual Developer Conference, XDA:DevCon 2014!
5,809,424 Members 36,232 Now Online
XDA Developers Android and Mobile Development Forum

[Q] Unable to flash Galaxy tab 3 10.1 GT-P5210

Tip us?
 
r2d23cpo
Old
(Last edited by r2d23cpo; 31st August 2014 at 05:11 PM.)
#11  
Member
Thanks Meter 72
Posts: 97
Join Date: Jan 2014
Quote:
Originally Posted by AppleAssassin View Post
Also, with that cwm file you sent. How can I use it with odin because it is a .img file and not .tar or .md5?
You are definitely right! I just realized that. Looks like the developer @moonbutt74 assumed we all had a recovery all ready and did not make an Odin Package!!

If you have a linux machine you could: Extract "recovery.img" from "PhilzAdvCWM-6_55_0-gtP-5210-v2.zip" then do
Code:
tar -H ustar -c recovery.img > recovery.tar
md5sum -t recovery.tar >> recovery.tar
mv recovery.tar recovery.tar.md5
Windows does not allow you to do this easily. Here are some code compile to do that in cigwin. I called it img2tar,

Code:
1) Download and extract the img2tar.rar to your desktop.
2) Navigate to img2tar Folder
3) Open "PhilzAdvCWM-6_55_0-gtP-5210-v2.zip"  and using winrar or winzip extract "recovery.img" and place a copy inside img2tar Folder
4) Double click in Runme.bat
5) Now you should see "recovery.tar.md5" witch is a Odin type file.
KK 4.4.2 is a trick Android Rom. If you let the TAB to reboot automatically after you install recovery with Odin, chances are that su or recovery will fail. So I suggest you deselect "Auto Reboot" only let "F.Reset Time" This is not a tutorial in ODIN I suggest anyone read more about it. In particular DO NOT mark "RE-Partition" it is very dangerous. That is there for very Special occasions.

Odin

1) Turn Off your TAB.
2) Run Odin 3.07
3) Hook the cable to the TAB3
4) Press Just [Power]+[Volume Down] this is enogth in my tab. But if you Prefer [Power]+[Volume Down]+[Menu] Your Tab should Show the Warning! Screen and the Yellow Triangle. Nothing should be shown oin Odin yet.
5) As the test read [Volume Up] to Continue. Your Tab3 shows now the Android and read Downloading. Your PC did a "Beep" acnoledging the Driver is ready. Odin now shows in First Slot of "ID:COM" a Blue data that Reads "0:[COMx]" where x is a number for comport. Number does not mater. This tell you ODIN as recognized your Device.
6) Options: Now make sure check-mark ONLY for "F.Reset Time" is selected. Nothing more. Please read my warning before.
7) Files [Download] select check mark of PDA
8) Press PDA and Navigate to where you have your recovery in you case "img2tar\recovery.tar.md5"
9) "Message" window . Odin tell you the status in this window. you should see

Code:
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
So be smart wait!!
10) Then is file is validated you will see
Code:
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> recovery.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS.
11) Now after you see Successful Odin is ready. If you do not see there is something wrong.
12) Now we can press "START"
13) You should see ID:COM with progress bar. TAB3 shows a progress bar too. On top it reads "Recovery". With time you should read in Message
Code:
<ID:0/011> Odin v.3 engine (ID:11)..
<ID:0/011> File analysis..
<ID:0/011> SetupConnection..
<ID:0/011> Initialzation..
<ID:0/011> Get PIT for mapping..
<ID:0/011> Firmware update start..
<ID:0/011> recovery.img
<ID:0/011> NAND Write Start!! 
<ID:0/011> RQT_CLOSE !!
<ID:0/011> RES OK !!
14)You need to wait until Blue "Recovery" change to "Reset". Remember TAB3 will not boot automatically since we deselect. So Once we see reset we know it is ready.
15) Now we go to the TAB3 and press [Power]+[Volume UP] to get into recovery. This is important since some time recovery fails if we let the TAB3 reboot in to OS. KitKat bad behavior will screw our recovery on purposed.
16) navigate if you like to see your new recovery
17) Here is what I do different at this time I go and install super su again. This is the only su that we have test that survive Kitkat attack=>http://download.chainfire.eu/452/Sup...erSU-v2.02.zip
18) Now reboot.


Now I had also attached the files with philz inside. I hope there is no problem. But if for any reason any of the authors complain, I will delete this and/or authorize moderators to do it them self. It is only been done to help AppleAssassin and with the cause in fact that this file is not available in Odin form yet. @moonbutt74 Can you please add to your folder an ODIN type of file for all of your Recoveries. I know many will appreciate that.

But Please note that I have left the ing2tar mechanism so that any can transform their *.img in to tar.md5 and do it them self!

Quote:
Originally Posted by AppleAssassin View Post
I'm not complaining about odin. I'm expecting odin to do its job, and it seems to do it but my tab perpetually reboots after I "flash" the file and try to enter recovery mode
Forget me for saying "complaining". Be smart. I understood you say you can get in to Recovery! So why use Odin again!!!!

In any case I have provided you the files.

Please Note, I had Test the files my self, but I give no warranties on it used. Do it at your own risk.
Attached Files
File Type: rar img2tar.rar - [Click for QR Code] (1.52 MB, 36 views)
The Following User Says Thank You to r2d23cpo For This Useful Post: [ Click to Expand ]
 
r2d23cpo
Old
(Last edited by r2d23cpo; 31st August 2014 at 03:55 PM.)
#12  
Member
Thanks Meter 72
Posts: 97
Join Date: Jan 2014
Finally uploaded the Philz tar.md5
Code:
http://d-h.st/j6y
As I say as soon any possible author complains I will delete lt. So be quick.
 
AppleAssassin
Old
#13  
Junior Member - OP
Thanks Meter 0
Posts: 8
Join Date: Aug 2014
Quote:
Originally Posted by r2d23cpo View Post
You are definitely right! I just realized that. Looks like the developer @moonbutt74 assumed we all had a recovery all ready and did not make an Odin Package!!

If you have a linux machine you could: Extract "recovery.img" from "PhilzAdvCWM-6_55_0-gtP-5210-v2.zip" then do
Code:
tar -H ustar -c recovery.img > recovery.tar
md5sum -t recovery.tar >> recovery.tar
mv recovery.tar recovery.tar.md5
Windows does not allow you to do this easily. Here are some code compile to do that in cigwin. I called it img2tar,

Code:
1) Download and extract the img2tar.rar to your desktop.
2) Navigate to img2tar Folder
3) Open "PhilzAdvCWM-6_55_0-gtP-5210-v2.zip"  and using winrar or winzip extract "recovery.img" and place a copy inside img2tar Folder
4) Double click in Runme.bat
5) Now you should see "recovery.tar.md5" witch is a Odin type file.
KK 4.4.2 is a trick Android Rom. If you let the TAB to reboot automatically after you install recovery with Odin, chances are that su or recovery will fail. So I suggest you deselect "Auto Reboot" only let "F.Reset Time" This is not a tutorial in ODIN I suggest anyone read more about it. In particular DO NOT mark "RE-Partition" it is very dangerous. That is there for very Special occasions.

Odin

1) Turn Off your TAB.
2) Run Odin 3.07
3) Hook the cable to the TAB3
4) Press Just [Power]+[Volume Down] this is enogth in my tab. But if you Prefer [Power]+[Volume Down]+[Menu] Your Tab should Show the Warning! Screen and the Yellow Triangle. Nothing should be shown oin Odin yet.
5) As the test read [Volume Up] to Continue. Your Tab3 shows now the Android and read Downloading. Your PC did a "Beep" acnoledging the Driver is ready. Odin now shows in First Slot of "ID:COM" a Blue data that Reads "0:[COMx]" where x is a number for comport. Number does not mater. This tell you ODIN as recognized your Device.
6) Options: Now make sure check-mark ONLY for "F.Reset Time" is selected. Nothing more. Please read my warning before.
7) Files [Download] select check mark of PDA
8) Press PDA and Navigate to where you have your recovery in you case "img2tar\recovery.tar.md5"
9) "Message" window . Odin tell you the status in this window. you should see

Code:
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
So be smart wait!!
10) Then is file is validated you will see
Code:
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> recovery.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/011> Removed!!
<ID:0/011> Added!!
11) Now after you see Successfull...Added this means Odin is ready. If you do not see theis something is wrong.
12) Now we can press "START"
13) You should see ID:COM with progress bar. TAB3 shows a progress bar too. On top it reads "Recovery". With time you should read in Message
Code:
<ID:0/011> Odin v.3 engine (ID:11)..
<ID:0/011> File analysis..
<ID:0/011> SetupConnection..
<ID:0/011> Initialzation..
<ID:0/011> Get PIT for mapping..
<ID:0/011> Firmware update start..
<ID:0/011> recovery.img
<ID:0/011> NAND Write Start!! 
<ID:0/011> RQT_CLOSE !!
<ID:0/011> RES OK !!
14)You need to wait until Blue "Recovery" change to "Reset". Remember TAB3 will not boot automaticly sinec we deselect. So Once we see reset we know it is ready.
15) Now we go to the TAB3 and press [Power]+[Volume UP] to get into recovery. This is important since some time recovery fails if we let the TAB3 reboot in to OS. KitKat bad behavior will screw our recovery on purposed.
16) navigate if you like to see your new recovery
17) Here is what I do different at this time I go and install super su again. This is the only su that we have test that survive Kitkat attack=>http://download.chainfire.eu/452/Sup...erSU-v2.02.zip
18) Now reboot.


Now I had also attached the files with philz inside. I hope there is no problem. But if for any reason any of the authors complain, I will delete this and/or authorize moderators to do it them self. It is only been done to help AppleAssassin and with the cause in fact that this file is not available in Odin form yet. @moonbutt74 Can you please add to your folder an ODIN type of file for all of your Recoveries. I know many will appreciate that.

But Please note that I have left the ing2tar mechanism so that any can transform their *.img in to tar.md5 and do it them self!



Forget me for saying "complaining". Be smart. I understood you say you can get in to Recovery! So why use Odin again!!!!

In any case I have provided you the files.

Please Note, I had Test the files my self, but I give no warranties on it used. Do it at your own risk.
It works!
 
r2d23cpo
Old
#14  
Member
Thanks Meter 72
Posts: 97
Join Date: Jan 2014
It has to work, i am Perfect.

Just kidding. I am glad you resolve your problem. Remember thanks to @moonbutt74 Philz CWM and chainfire that really the guys that make this possible.
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes